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

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000651.a.1996(R2011) Mobility Management Application Protocol (MMAP) - Extensions ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the infor

2、mation, entertainment 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. I

3、n addition, numerous 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 (3G

4、PP), a member and 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

5、Standard requires 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 ma

6、terially affected 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

7、 voluntary; their 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 standa

8、rds and will in 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 b

9、e addressed to 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,

10、 revise, or withdraw 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 sta

11、ndards or not, 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

12、person shall have 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 NO

13、TICE: This American 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

14、on all standards by calling or writing the AmericanNational Standards Institute.Published byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 1997 by Alliance for Tellecommunications Industry SolutionsAll rights reserved.No part of this publication may be re

15、produced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of Americainsert code hereiForeword .iv1 Scope, purpose, and application11.1 Scope .11.2 Purpose 11.3 Application 12 Normative references 13 Definitions

16、and acronyms 23.1 Definitions.23.2 Acronyms34 Overview.44.1 Document structure .44.2 Functional architecture 45 Protocol architecture .55.1 Application layer structure .55.2 Mapping of mobility management operations .55.2.1 Mapping to ROSE .55.2.2 Mapping to NCAS55.2.3 Mapping to TCAP 56 Operations

17、descriptions.96.1 PACS operations descriptions .96.1.1 RACF SCF operations96.1.1.1 Common operations used by PACS .96.1.1.2 PACS specific operations 96.1.2 RACF RACF operations .96.1.2.1 Common operations used by PACS .96.1.2.2 PACS specific operations 96.2 CDMA operations descriptions.96.2.1 RACF S

18、CF operations96.2.1.1 Common operations used by CDMA 96.2.1.2 CDMA specific operations .96.2.2 RACF RACF operations .96.2.2.1 Common operations used by CDMA 96.2.2.2 CDMA specific operations .96.2.2.2.1 CDMA facilities directive 3.96.3 PCS 1900 operations descriptions .136.3.1 RACF SCF operations .1

19、36.3.1.1 Common operations used by PCS1900136.3.1.2 PCS 1900 specific operations136.3.1.2.1 Activate SS .136.3.1.2.2 Activate trace mode.156.3.1.2.3 Deactivate SS .176.3.1.2.4 Deactivate trace mode.196.3.1.2.5 Erase SS.206.3.1.2.6 Forward check SS indication .226.3.1.2.7 Forward SMS 236.3.1.2.8 Get

20、password25ContentsPageii6.3.1.2.9 Interrogate SS.266.3.1.2.10 Process unstructured SS request.286.3.1.2.11 Ready for SM 306.3.1.2.12 Register password.326.3.1.2.13 Register SS.346.3.1.2.14 Reset 366.3.1.2.15 Restore data .376.3.1.2.16 Unstructured SS notify.386.3.1.2.17 Unstructured SS request .406.

21、3.1.2.18 Validate MO SMS426.3.2 RACF RACF operations .436.3.2.1 Common operations used by PCS1900436.3.2.2 PCS 1900 specific operations436.3.3 Dialogue control operations .436.3.3.1 Open.436.3.3.2 Accept.446.3.3.3 Close 446.3.3.4 Refuse 456.3.3.5 User abort.456.3.3.6 Provider abort .466.4 Composite

22、CDMA/TDMA (CCT) operations descriptions.466.5 TDMA operations descriptions .466.6 Common operations descriptions.476.6.1 RACF SCF operations.476.6.1.1 Call indication .476.6.1.2 Routing request.486.6.2 RACF RACF operations 497 ASN 507.1 PACS ASN517.1.1 PACS abstract syntax517.1.2 PACS ASEs 517.2 CDM

23、A ASN .517.2.1 CDMA abstract syntax .517.2.2 CDMA ASEs557.3 PCS1900 ASN.567.3.1 PCS1900 abstract syntax 567.3.2 PCS1900 ASEs .677.4 CCT ASN 697.4.1 CCT abstract syntax697.4.2 CCT ASEs.717.5 TDMA ASN717.5.1 TDMA abstract syntax .717.5.2 TDMA ASEs 717.6 Common ASN .717.6.1 Common abstract syntax .717.

24、6.2 Common ASEs76Tables1 Mapping of PCS1900 operations to TCAP package and component types 6Pageiii2 Mapping of common operations to TCAP package and component types 83 Mapping of PCS1900 dialogue control operations to TCAP package types .8Figures1 MMAP object identifier tree for PCS1900 .56AnnexA S

25、ignalling flows .78PageivForeword (This foreword is not part of American National Standard T1.651a-1996.)This document is a supplement to ANSI T1.651-1996. It provides changesand additional operations for the RACF-SCF and RACF-RACF interfaces.This standard has one annex. Annex A is informative and i

26、s not consideredpart of this standard; that is, this annex does not include requirements forthis specification, but provides information about this specification.Suggestions for improvement of this standard will be welcome. They shouldbe sent to the T1 Secretariat, c/o Alliance for Telecommunication

27、s IndustrySolutions, 1200 G Street, N.W., Suite 500, Washington, D.C. 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards Committee on Telecommunications, T1. Committeeapproval of the standard does not necessarily imply that all committeemembers voted for its

28、approval. At the time it approved this standard, theT1 Committee had the following members:Gerald H. Peterson, ChairmanE. R. Hapeman, Vice-ChairmanAlvin Lai, SecretaryRobin Rossow, Senior EditorShankar Govindasamy, Technical EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeri

29、tech Services, Inc. Laurence A. YoungRichard Wood (Alt.)ATuseful for statistics, billing, and call trace operationsactual_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 p

30、ilots and RACF addresshard_Handoff_Parameters - information needed by the source RTF to perform hard handoffforward_Power_Control - information regarding various power control parameters needed by themobiletranscoder_Hnadoff_Time - alternate time for transcoder handoff indicated by the target RCF du

31、ring adrop source procedureresp_Service_Config_Rec - indicates the granted service configurationANSI T1.651a-199612resp_Service_Option_List - indicates the state information for the granted service option(s)facilities_Directive_Error - identifies an errorcause - provides additional information regar

32、ding the failureparameter_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

33、_Parameter_ValueFeature_InactiveMissing_ParameterRequested_Information_UnavailableCause - see IS-651 Part IIIbFaulty_Parameter - see IS-41CANSI T1.651a-1996136.3 PCS 1900 operations descriptions6.3.1 RACF SCF operations6.3.1.1 Common operations used by PCS1900PCS1900 does not utilize any RACF-to-SCF

34、 common operations.6.3.1.2 PCS 1900 specific operations6.3.1.2.1 Activate SSName: Activate_SSDirection: RACF - SCFDescription:This operation is used between the RACF and the SCF to activate a supplementary service.Operational Rules:The activation procedure is used to activate a supplementary service

35、 in the HSCF. The activationprocedure is a fully transparent communication between the RTF and the HSCF.When the RTF initiates the supplementary service activation, the RACF transfers the informationreceived from the RTF to the SCF in the Activate_SS request without checking the contents of theservi

36、ce request.Upon receipt of the Activate_SS request, the SCF further transfers the information to the HSCFwithout checking the contents of the service request. When the SCF receives the response from theHSCF, it will transfer the information to the RACF in the Activate_SS response without checking it

37、scontents.The RACF will further transfer the information contained in the Activate_SS response to the RTF.Note that password may be needed for activation of some supplementary services. In those casesthe Get_Password operation is performed before the response of the Activate_SS is returned.ROSE Oper

38、ation Class: Class 2Parameters:Name Type Usage Request:ss_Code SS_Code Mbasic_Service Basic_Service_Code OResponse:Success:fwd_Info Forwarding_Info Ocall_Barring_Info Call_Barring_Info Oss_Data SS_Data OErrors:activate_SS_Error see definitions below MParameter Definitions:ss_Code - This parameter in

39、dicates the supplementary service which the PCSsubscriber wants to activate.ANSI T1.651a-199614basic_Service - This parameter indicates for which basic service groups therequested supplementary service(s) should be activated. If it is notincluded, the activation request applies to all basic services

40、.fwd_Info - This parameter is returned if the activation request concerns CallForwarding.call_Barring_Info - This parameter is returned if the activation request concerns CallBarring.ss_Data - This parameter is returned if the activation request concerns forexample Call Waiting.Error Definitions:sys

41、tem_Failure - The task cannot be performed because of a problem in anotherentity.data_Missing - An optional parameter required by the context is missing.unexpected_Data_Value - A data type is formally correct but its value or presence isunexpected in the current context.bearer_Service_Not_Provisione

42、d- This error is returned only if not even a subset of the requestedbearer service group has been subscribed to.tele_Service_Not_Provisioned- This error is returned only if not even a subset of the requestedteleservice group has been subscribed to.call_Barred - The access to supplementary services h

43、as been barred.illegal_SS_Operation - The operation violates the rules applicable to the particularsupplementary service.ss_Error_Status - The operation on the supplementary service is incompatible with thecurrent status of the service.ss_Subscription_Violation - The action requested on the suppleme

44、ntary service is incontradiction with the subscription.ss_Incompatibility - The action on the supplementary service is incompatible with thestatus of another supplementary service.negative_PW_Check - The requested password has not been provided or it has beenprovided but does not match the valid one

45、.number_Of_PW_Attempts_Violation- The RTF has attempted to access password controlledsupplementary services using an erroneous password more thanthree times.ANSI T1.651a-1996156.3.1.2.2 Activate trace modeName: Activate_Trace_ModeDirection: RACF SCFDescription:This operation is used between the RACF

46、 and the SCF to deactivate a supplementary service.Operational Rules:The deactivation procedure is used to deactivate a supplementary service in the HSCF. Thedeactivation procedure is a fully transparent communication between the RTF and the HSCF.When the RTF initiates the supplementary service deac

47、tivation, the RACF transfers the informationreceived from the RTF to the SCF in the Deactivate_SS request without checking the contents of theservice request.Upon receipt of the Deactivate_SS request, the SCF further transfers the information to the HSCFwithout checking the contents of the service r

48、equest. When the SCF receives the response from theHSCF, it will transfer the information to the RACF in the Deactivate_SS response without checking itscontents.The RACF will further transfer the information contained in the Deactivate_SS response to the RTF.ROSE Operation Class: Class 2Parameters:N

49、ame Type Usage Request:ss_Code SS_Code Mbasic_Service Basic_Service_Code OResponse:Success:fwd_Info Forwarding_Info Oss_Data SS_Data OErrors:deactivate_SS_Error see definitions below MParameter Definitions:ss_Code - This parameter indicates the supplementary service which the PCSsubscriber wants to deactivate.basic_Service - This parameter indicates for which basic service groups therequested supplementary service(s) should be deactivated. If it isnot included, the deactivation r