ema _wireless_commands

Download EMA _Wireless_Commands

Post on 26-Dec-2015




23 download

Embed Size (px)


CAI Commands


  • CAI SPECIFICATION FOR WIRELESSEricsson Multi Activation 5.0

  • Copyright

    Ericsson AB 2007 - All Rights Reserved


    No part of this document may be reproduced in any form without the writtenpermission of the copyright owner.

    The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing.

    Ericsson shall have no liability for any error or damage of any kind resultingfrom the use of this document.

    This document is a general guide, instruction and description of the EricssonMulti Activation product or applicable parts thereof. However, an Ericsson MultiActivation system installation may be configured partially or in a number of otheralternative ways. Consequently, configurations of Ericsson Multi Activationsystems may vary between different installations, hence such differencesmay also result in variations in the Ericsson Multi Activation system behavior,capacity as well as other limitations.

    If in any doubt, please contact your local Ericsson support for further advise.

    Trademark List

    Ericsson is the trademark or registered trademark of Ericsson AB. All otherproducts or service names mentioned in this document are trademarks of theirrespective companies.

    155 10-CSH 150 82 Uen C 2007-01-24



    1 Introduction 11.1 Prerequisites 11.2 Scope 21.3 Objectives 32 CAI Overview 52.1 General 52.2 Distributed Configuration 6

    3 Communication Protocol 93.1 General 93.2 Transport and Network Layer 103.3 Session and Presentation Layer 13

    4 Message Formats 174.1 Character Representation 174.2 Message Request Format 174.3 Message Response Format 19

    5 Control Commands 215.1 Login 215.2 Logout 215.3 Message Response 22

    6 HLR Subscription 256.1 Composite Parameter Definitions 256.2 Customers Service Orders (CSO) 706.3 Request and Response Parameters 846.4 HLR Subscriber Data Abbreviations 986.5 HLRSUB Message Response 106

    7 FNR Subscription 1217.1 Customers Service Orders 1217.2 Request and Response Parameters 1377.3 FNR Subscriber Data Abbreviations 1407.4 FNRSUB Message Response 140

    155 10-CSH 150 82 Uen C 2007-01-24


    8 IMSI Change Over 1498.1 Customers Service Orders 1498.2 Request and Response Parameters 1558.3 IMSICH Message Response 157

    9 AUC Subscription 1619.1 Composite Parameter Definitions 1619.2 Customers Service Orders 1639.3 Request and Response Parameters 1689.4 AUCSUB Message Response 170

    10 EIR Subscription 17310.1 Customers Service Orders 17310.2 Request and Response Parameters 18310.3 Message Response 186

    11 CMS11HLR Subscription 19311.1 Composite Parameter Definitions 19311.2 Customers Service Orders 19411.3 Request and Response Parameters 20211.4 CMS11HLR Subscriber Data Abbreviations 20511.5 CMS11HLR Message Response 217

    12 CMS11AC Subscription 22112.1 Customers Service Orders 22112.2 Request and Response Parameters 23212.3 CMS11AC Message Response 235

    13 MPC Subscription 23913.1 Composite Parameter Definitions 23913.2 Customers Service Orders 24113.3 Request and Response Parameters 25613.4 MPCSUB Message Response 259

    14 AAA Subscription 26314.1 Composite Parameter Definitions 26314.2 Customers Service Orders 27214.3 Request and Response Parameters 28714.4 AAASUB Message Response 291

    155 10-CSH 150 82 Uen C 2007-01-24


    15 Appendix A (Graphical Structure) 29515.1 Example 1 29515.2 Example 2 29515.3 Example 3 296

    16 Appendix B (Typical X.25 Configuration) 29716.1 The Interface Section: 29816.2 The Link Section: 29816.3 The X.25 (packet level) Section: 29917 Appendix C (Error Recovery) 30318 Appendix D (New or Changed NEs and MOs in Ericsson

    Multi Activation 4.0) 305Glossary 307

    Reference List 313

    155 10-CSH 150 82 Uen C 2007-01-24


    155 10-CSH 150 82 Uen C 2007-01-24


    1 Introduction

    The Customer Administration Interface (CAI) is the interface between a CASsystem and Ericsson Multi Activation. The interface simplifies the access todifferent kinds of Network Elements (NE) by introducing one homogenousinterface for all Network Elements.

    The document Customer Administration Interface (CAI) (EPK/NK-96:073) isgeneric and describes the CAI syntax and protocol in general terms, whereasthis Ericsson Multi Activation document is the specific description of theinterface between a CAS and Ericsson Multi Activation for management ofHLR, EIR, AUC and etc. of the respective relevant versions.

    CAI controls all protocol conversions for the specific Network Element.

    Figure 1 The CAI concept

    1.1 PrerequisitesIn this document, it is assumed that the user:

    have basic knowledge of Ericsson Multi Activation.

    have proper authority to use Ericsson Multi Activation.

    have common knowledge about third-party documentation.

    have common knowledge of Ericsson systems.

    have sound knowledge of the Network Elements.

    1155 10-CSH 150 82 Uen C 2007-01-24


    1.2 ScopeThis document specifies the CAI protocol for subscription/equipmentadministration towards Ericsson GSM 900/1800/1900 networks, hereinspecified as GSM network. The supported releases of the GSM network are:

    a GSM 900/1800 R6.1

    b GSM 1900 R3

    c GSM R8/R9/R9.1/R9.2/R10/R11

    d WCDMA R1.5/R2/R3/R4/R5

    The document defines in detail the actions that may be performed and theresponses to be expected.

    The following core network databases are supported:

    a Home Location Register (HLR)The HLR application based on a modular concept provides flexibility invarious network. It offers not only common maintenance and developmentmethodology and well-proven process for introducing new and enhancedfunctionality, but also trouble-free and seamless inter-working betweendifferent nodes.

    b Equipment Identity Register (EIR)The EIR helps to detect and trace phone handset counterfeiting andhandset subsidy fraud.

    c Authentication Centre (AUC)The AUC generates authentication and ciphering data according tothe European Telecommunications Standards Institute (ETSI) GSMspecifications.

    d Flexible Number Register (FNR)The FNR node is a high capacity entity designed to cope with the handlingof large number series and minimal call setup delays.

    The NE redundancy concept in Ericsson Multi Activation support redundantHLRs as well as paired network elements such as FNR/NP and AUC.

    For further information about the Ericsson Multi Activation redundancy concept,see Function Specification Ericsson Multi Activation 5.0.

    2 155 10-CSH 150 82 Uen C 2007-01-24


    1.3 ObjectivesThe aim of this document is to make it possible to integrate a CAS with EricssonMulti Activation. For specific low level parameters, additional documents (seeReference) must be used.

    3155 10-CSH 150 82 Uen C 2007-01-24


    4 155 10-CSH 150 82 Uen C 2007-01-24


    2 CAI Overview

    2.1 GeneralThe CAI is capable of handling independent multiple sessions towards CAS.From each session all authorized Network Elements are accessible.

    Figure 2 The Ericsson Multi Activation Message Flow

    A provisioning operation initiated from the CAS to Ericsson Multi Activation isreferred as a Customer Service Order (CSO).A CSO contains a Managed Object (MO) and one of the following actions:

    GET (to display an MO)

    CREATE (to create an MO)

    5155 10-CSH 150 82 Uen C 2007-01-24


    DELETE (to delete an MO) SET (to modify an MO)The MO contains the information to be transferred to or fetched from theNetwork Element. Each MO type corresponds to a specific network elementfunction.

    Actions that influence network data are called provisioning operations andare logged by CAI. It is possible to see Network Service Orders (NSOs) thathave been sent, Network Element responses and the result of the completeprovisioning operation.

    CAI has a security system which can be used to prevent non-authorizedoperators from accessing data in the networks. This is implemented by meansof access control. Any hostile attempt will result in an error response to CAS.

    All provisioning operations are synchronized, which means that there are noprovisioning operation queues in CAI.

    The NE redundancy concept sends data to the primary NE and then to thesecondary NE. Only commands that change data for the subscribers areduplicated (create/set/delete). This concept is available for HLR, FNR and AUC.In general, CAI supports the full set of MOs. However, a site may be configurednot to have support for certain NEs. In such a case, an error explaining thatthe configuration did not allow the action is responded when CAI is trying toaccess non-supported MOs.

    2.2 Distributed ConfigurationEricsson Multi Activation also has a routing concept that supports thedistribution of CSOs to other CAI compliant nodes without processing. Theconcept is called Distributed Configuration (DC). This concept allows a numberof CAI applications to be interconnected to form one logical application.

    6 155 10-CSH 150 82 Uen C 2007-01-24


    Figure 3 Distribution of Managed ObjectsEricsson Multi Activation forward CSOs to another CAI complaint nodeaccording to the routing definition. The destination may have the same setof MOs (another Ericsson Multi Activation for load sharing purpose) or atotally separate set of MOs (e.g., WGPSUB - Wir