ATIS 1000651-1996 Mobility Management Application Protocol (MMAP).pdf

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000651.1996(R2011) Mobility Management Application Protocol (MMAP) ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, enterta

2、inment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Networks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operational Support. In addition, num

3、erous Incubators, Focus and Exploratory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect, IPv6 and Convergence. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member a

4、nd major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, please visit . AMERICAN NATIONAL STANDARD Approval of an American National Standard requir

5、es review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affect

6、ed interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; the

7、ir existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in

8、 no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to

9、the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or wit

10、hdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer their existence does not in any respect preclude anyone, whether he has approvedthe standards or not,

11、from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall ha

12、ve the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should be ad-dressed to the secretariat or sponsor whose name appears on the title pageof this standard.CAUTION NOTICE: This Amer

13、ican National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards mayreceive current information on all standard

14、s by calling or writing the AmericanNational Standards Institute.Published byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 1996 by Alliance for Telecommunications Industry SolutionsAll rights reserved.No part of this publication may be reproduced in anyf

15、orm, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of Americainsert code hereiForewordii1 Scope, purpose, and application .12 Normative references .13 Definitions and acronyms24 Overview65 Protocol architecture 76 Operat

16、ions descriptions 147 ASN .60Table1 Mapping of MMAP operations to TCAP component and package types.9Figures1 Functional model .72 Protocol architecture83 MMAP Object identifier tree60AnnexesA Physical scenarios .93B Bibliography 95ContentsPageiiForeword (This foreword is not part of American Nationa

17、l Standard T1.651-1996.)T1S1 began addressing PCS requirements in ad-hoc committees in 1993.In response to the industrys desire to have a standard solution for supportof PCS mobility, T1S1 established the Mobility Management ApplicationProtocol subworking group in 1994 with a charter to create a sta

18、ge 3 pro-tocol for supporting the mobility management requirements of the radiosystems defined by T1P1 and TR46 over the T1P1 C and D interfaceand the TR46 A interface.This document is the first issue of the MMAP to address the immediateindustry needs. Future issues are planned to support aspects su

19、ch asadditional radio systems, alternate functional distributions, additional inter-faces, convergence function definitions, and additional services.This standard contains two annexes, which are for information only andare not considered part of this standard.Suggestions for improvement of this stan

20、dard will be welcome. Theyshould be sent to the T1 Secretariat, c/o Alliance for TelecommunicationsIndustry Solutions, 1200 G Street, NW, Suite 500, Washington, DC 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards Committee on Telecommunications, T1. Committ

21、eeapproval of the standard does not necessarily imply that all committeemembers voted for its approval. At the time it approved this standard, theT1 Committee had the following members:A. K. Reilly, ChairmanG. H. Peterson, Vice-ChairmanO. J. Gusella, Jr., SecretaryW. Zeuch, Senior EditorR. McNealy,

22、Technical EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech Services, Inc. Laurence A. YoungRichard Wood (Alt.)Bell Atlantic Corporation John W. SeazholtzRoger Nucho (Alt.)Bellcore.James C. StaatsE. R. Hapeman (Alt.)BellSouth Telecommunications, Inc. William J. McNamara

23、, IIIMalcolm Threlkeld, Jr. (Alt.)Cincinnati Bell Telephone Andy McIntyreLinda Price (Alt.)GTE Telephone Operations .Bernard J. HarrisRichard L. Cochran (Alt.)McCaw Cellular Communications.David HolmesLeo Nikkari (Alt.)National Telephone Cooperative Association .Joseph M. FlaniganNYNEX .James F. Bas

24、kinMichael Brusca (Alt.)Pacific Bell Sal R. TesoroPuerto Rico Telephone Company.Segundo RuizAlberto E. Morales (Alt.)SBC Communications, Inc. C. C. BaileyJoseph MendozaSprint Local Telecommunications Division.Robert P. McCabeHarold L. Fuller (Alt.)iiiUS Telephone Association (USTA) Dennis ByrnePaul

25、K. Hart (Alt.)US WestJames L. EitelDarryl Debault (Alt.)INTEREXCHANGE CARRIERSAT associationapplication contextassociation control service elementTerms from CCITT Recommendation X.219:invoker-application-entity; invokerperformer-application-entity; performerrequestoracceptorremote operationsremote o

26、peration service elementTerms from ISO/IEC 9545:single association control functionsingle association object3.2 AcronymsACSE Association Control Service ElementAE Application EntityAEI Application Entity InvocationALS Application Layer StructureAP Application ProcessAPDU Application Protocol Data Un

27、itAPI Application Programmer InterfaceASE Application Service ElementASN Abstract Syntax NotationBRI Basic Rate InterfaceCCAF Call Control Agent FunctionCCF Call Control FunctionCCT Composite CDMA/TDMACDMA Code Division Multiple AccessANSI T1.651-19965DSS1 Digital Subscriber Signaling System No. 1ES

28、N Electronic Serial NumberFE Functional EntityHLR Home Location RegisterIDN Interface Directory NumberIMEI International Mobile Equipment IdentifierIMSI International Mobile Subscriber IdentityISDN Integrated Services Digital NetworkISO International Standards OrganizationLA Location AreaMIN Mobile

29、Identification NumberMMAP Mobility Management Application ProtocolMTP Message Transfer PartNANP North American Numbering PlanNCAS Non-Call Associated SignalingOAMuseful for statistics, billing, and call trace operationssearch_Window search window size used by mobile to search for traffic channel(s)a

30、ctual_Confidentiality desired mode for SME and VPhandoff_Power_Level the target RCF desired RTF handoff power levelneighbor_List target RCF neighbor information, e.g., neighbor pilots and RACF addressfacilities_Directive_Error identifies an errorcause provides additional information regarding the fa

31、ilureparameter_In_Error a parameter in errorError Definitions:Error_Code this can be one of the following values:Unrecognized_MINUnrecognized_ESNMIN_HLR_MismatchOperation_Sequence_ProblemResource_ShortageOperation_Not_SupportedTrunk_UnavailableParameter_ErrorSystem_FailureUnrecognized_Parameter_Valu

32、eFeature_InactiveMissing_ParameterRequested_Information_UnavailableCause see TIA IS-651 Part IIIbFaulty_Parameter see TIA IS-41CANSI T1.651-1996186.3 PCS 1900 operations descriptionsThe operations defined in this clause assume the distribution of functionality as identified below. Theoperations are

33、defined as peer-to-peer operations between functional entities. When functionalentities are physically connected through intermediate nodes, the assumption is that a logicalassociation exists between the entities for the exchange of information via the operations.Visited SCF functionality1. Registra

34、tion procedurePerforms location updating.2. Service request procedureProcesses the service request of the personal terminal.RACF functionality1. Authentication procedureObtains authentication information from the Home SCF and personal terminal and compares theresults to determine if the subscriber i

35、s valid.2. Identity procedureObtains information about the subscriber or personal terminal from the personal terminal.3. Subscriber temporary identityPerforms the assignment of the subscribers temporary identifier.4. Locate personal terminalLocates the personal terminal.5. Detached subscribersMainta

36、ins the status of the subscriber in relation to the personal terminal.6. Ciphering processInitiates the encryption process and maintains information about the encryption algorithms andencryption keys.7. HandoverPerforms the handover process and maintains information about the cells. Notifies the vis

37、ited SCFwhen handover occurs in order to update location area.ANSI T1.651-1996196.3.1 RACF SCF operations6.3.1.1 Common operationsPCS 1900 does not utilize any RACF-to-SCF common operations.6.3.1.2 PCS 1900 specific operations6.3.1.2.1 PCS 1900 authentication information requestName: Authentication_

38、Information_RequestDirection: RACF - SCFDescription:This operation is used to obtain authentication information from the SCF for use in the authenticationprocess in the RACF.Operational Rules:When the RACF determines that it needs to update its authentication information regarding a specificsubscrib

39、er, it initiates an authentication information request to the SCF. The authentication parametersgiven by the SCF consist of a list of triplets. A set of one to five authentication triplets are transferredfrom the SCF to the RACF, if the outcome of the operation was successful. If the SCF cannot prov

40、idethe RACF with triplets, an empty response is returned. The RACF may then re-use the oldauthentication triplets.ROSE Operation Class: Class 2Parameters: Name Type Usage Request:subscriber IMSI MResponse:Success:authentication_Info Authentication_Set_List OErrors:authentication_Info_Error see defin

41、itions below MParameter Definitions:subscriber identifies the subscriber to be authenticatedauthentication_Info a list of RAND, SRES, and Kc triplets for use in the authentication processError Definitions:unknown_Subscriber subscription does not exist.system_Failure task cannot be performed because

42、of a problem in another entity.data_Missing an optional parameter required by the context is missing.unexpected_Data_Value data type is formally correct but its value or presence is unexpected in thecurrent context.ANSI T1.651-1996206.3.1.2.2 PCS 1900 update location requestName: Update_Location_Req

43、uestDirection: RACF - SCFDescription:This operation is used by the RACF to register and update the location information of a subscriberstored in the SCF.Operational Rules:Update_Location is an operation needed to keep track of where personal terminals are located. Apersonal terminal includes the ter

44、minal equipment, and the User Identity Module (UIM) whichcontains the subscriber identity (IMSI). The location information of each personal terminal is definedby a Location Area (LA) identity. The address of the RACF controlling an LA is stored in the SCF. ALocation Area covers one or more cells. An

45、 RACF can control one or several LAs. The maximum sizeof an LA is limited to the area controlled by one RACF. Personal terminals may move within an LAwithout updating their location information in the RACF, and within all LAs of one single RACFwithout updating location information in the SCF.A locat

46、ion updating procedure is initiated by a personal terminal when it has moved to a newLocation Area. If the new LA is controlled by an RACF other than the previous one, then the newRACF initiates an Update_Location operation toward the SCF. It sends the identity of the subscriber(IMSI) and the addres

47、s of the RACF to the SCF.The RACF can optionally allocate a local subscriber identity for the personal subscriber. It issignificant only to the particular RACF. It is used in signaling with the SCF to optimize access to thesubscriber data record in the RACF.ROSE Operation Class: Class 2Parameters: Name Type Usage Request:subscriber IMSI Mshort_Message_Address ISDN_Address_String Mracf ISDN_Address_String Mlocal_Subscriber LMSI OResponse:Success:home_SCF ISDN_Address_String MErrors:update_Location_Error see definitions below M