TIA-880-A-2007 MAP Enhancements for CDMA Packet Data Service (C-PDS)《MAP增强型CDMA分组数据服务(C-PDS)》.pdf

《TIA-880-A-2007 MAP Enhancements for CDMA Packet Data Service (C-PDS)《MAP增强型CDMA分组数据服务(C-PDS)》.pdf》由会员分享，可在线阅读，更多相关《TIA-880-A-2007 MAP Enhancements for CDMA Packet Data Service (C-PDS)《MAP增强型CDMA分组数据服务(C-PDS)》.pdf（204页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-880-A-2007 APPROVED: SEPTEMBER 1, 2007 REAFFIRMED: AUGUST 15, 2012 TIA-880-A (Revision of TIA-880) September 2007MAP Enhancements for CDMA Packet Data Service (C-PDS) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstanding

2、s between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect precl

3、ude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publicat

4、ions are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport

5、 to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No.

6、 3-4720-RV1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editi

7、ng process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pendi

8、ng patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA

9、will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices

10、 suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether

11、designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other S

12、SO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the

13、 records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate

14、products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR US

15、E, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REG

16、ULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREI

17、N, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWIS

18、E, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-880-AREVISION HISTORYCopyright Telecommunications Industry Association 2

19、007. All rights reserved.This document is subject to change.Revision Date RemarksTIA/EIA/IS-8802002-07 Initial publication.TIA-880-A2007-04 First Revision.TIA-880-A(No Text On This Page)TIA-880-AiContentsEditorial Conventions . viiForeword. viiAssumptions vii1 Introduction .11.1 Objective 11.2 Scope

20、 . 11.3 Organization 12 References12.1 Normative References .13 MAP Chapter 1 Modifications.33.1 SYMBOLS AND ABBREVIATIONS . 34 MAP Chapter 3 Modifications.54.1 CDMA Packet Data Service (C-PDS). 54.1.1 C-PDS Invocation from an Idle MS. 64.1.2 C-PDS Invocation During an Active Circuit Call 74.1.3 C-P

21、DS Invocation After Handoff. 84.1.4 Post Handoff Recovery on Unsuccessful Packet Data Session Initiation 94.1.5 Simultaneous Circuit and C-PDS Handoff - Packet Releases First . 104.1.6 Successful Intersystem Hard Handoff of an Active Packet Data Session . 134.1.7 Successful Intersystem Hard Handoff

22、of an Active Packet Data Session with Re-Registration . 154.1.8 Successful Intersystem Hard Handoff of an Active packet Data Session Authen-tication Failure Prior to After-Handoff Registration . 174.1.9 Successful Intersystem Hard Handoff of an Active packet Data Session Registra-tion Failure After

23、Handoff . 204.1.10 C-PDS Hard Handoff with Subsequent Circuit Termination 234.1.11 C-PDS Hard Handoff with Subsequent Circuit Origination . 254.1.12 Simultaneous Circuit and C-PDS Handoff - Voice Releases First . 274.1.13 Simultaneous Circuit and C-PDS Handoff - Voice Releases First - With Re-Regis-

24、tration . 294.1.14 C-PDS HandoffBack . 324.1.15 C-PDS HandoffToThird. 344.2 C-PDS for IOS v4.3 364.2.1 Network Initiated Dormant State Re-Activation of MS in Neighbor MSC (same packet registration zone, same PCF and PDSN) . 364.2.2 Network Initiated Dormant State Re-Activation of MS in Neighbor MSC

25、(same packet registration zone, same PCF and PDSN) following inter-MSC active circuit call handoff 40TIA-880-AiiAnnex A: C-PDS Hard Handoff Including A-Interface and Packet Data Network Information Flows435 Protocol Modification 475.1 Message Transfer Part475.2 MAP Chapter 5 “Signaling Protocol” Mod

26、ifications 475.2.1 MAP OPERATIONS .485.2.1.1 Operation Specifiers .485.2.1.2 Operation Definitions .485.2.1.3 AddService 495.2.1.4 DropService .515.2.1.5 FacilitiesDirective2 535.2.1.6 HandoffBack2 575.2.1.7 HandoffToThird2 625.2.1.8 InformationForward 675.2.1.9 InterSystemPage2 695.2.1.10 InterSyst

27、emSetup .725.2.1.11 SMSDeliveryBackward .765.2.1.12 SMSDeliveryForward 785.2.2 MAP PARAMETERS .805.2.2.1 Parameter Identifiers 805.2.2.2 Parameter Definitions.815.2.2.3 CallingFeaturesIndicator 815.2.2.4 CDMA2000HandoffInvokeIOSData845.2.2.5 CDMA2000HandoffResponseIOSData .855.2.2.6 CDMACallMode 865

28、.2.2.7 CDMAConnectionReferenceInformation .905.2.2.8 CDMAMSMeasuredChannelIdentity 915.2.2.9 CDMAServiceOptionConnectionIdentifier .925.2.2.10 CDMAServiceConfigurationRecord .935.2.2.11 InterMSCCircuitID.945.2.2.12 PDSNAddress 955.2.2.13 PDSNProtocolType .965.2.2.14 Profile 975.2.2.15 QoSPriority 98

29、5.2.2.16 ReleaseReason .1005.2.2.17 Service Reference Identifier 101Annex-A IOS Version-4.1 (A1 to TIA/EIA-41 Mapping).1026 MAP Procedure Modifications 1136.1 Terminating Call Tasks1136.1.1 MS Termination Alerting1136.2 Facilities Directive 2 (handoff Forward) 1156.2.1 Serving MSC Initiating a Facil

30、ities Directive 21156.2.2 Target MSC Receiving a FacilitiesDirective2 INVOKE1226.2.3 Target MSC Handoff Forward126TIA-880-Aiii6.3 HANDOFFBACK2 (Shoe Lace Prevention) 1296.3.1 Serving MSC Initiating a Handoff Back 2 1296.3.2 Target MSC Receiving a HandoffBack2 INVOKE 1336.3.3 Target MSC HandoffBack2

31、1366.4 Handoff-to-Third2 (Path Minimization) . 1386.4.1 Serving MSC Initiating a Handoff-To-Third2 1386.4.2 Tandem MSC Receiving a HandoffToThird2 INVOKE 1426.4.3 Anchor MSC Receiving a HandoffToThird2 INVOKE 1476.4.4 MSC Initiating a FacilitiesDirective2 for Path Minimization. 1516.5 Intersystem An

32、swer . 1556.5.1 MSC Awaiting InterSystemAnswer . 1556.5.2 Anchor or Serving MSC Initiating InterSystemAnswer. 1566.5.3 Tandem MSC Receiving an InterSystemAnswer INVOKE 1576.6 Intersystem Setup 1606.6.1 MSC Initiating an Intersystem Setup 1606.6.2 MSC Receiving InterSystemSetup INVOKE . 1626.7 Regist

33、ration Cancellation 1666.7.1 MSC Receiving RegistrationCancellation INVOKE 1666.8 Registration Notification . 1686.8.1 MSC Initiating MS Registration . 1686.9 Add Service . 1716.9.1 Target (New Serving) MSC Initiation of Add Service . 1716.9.2 Anchor MSC Receiving an AddService INVOKE. 1726.9.3 Tand

34、em MSC Receiving an AddService INVOKE 1746.10 Drop Service . 1766.10.1 MSC Initiating a Drop Service . 1766.10.2 MSC Receiving a DropService INVOKE. 1786.11 Operation Timer Values 1816.12 Information Forward . 1826.12.1 MSC Receiving an InformationForward INVOKE . 1826.13 Packet Data Session Re-Acti

35、vation . 185TIA-880-AivLIST OF TABLESTable 1 MTP Message Priority Values for MAP Operations .47Table 2 Operation Specifiers 48Table 3 Summary of MAP Operations .48Table 4 FE Combinations for DROPSERV51Table 5 FacilitiesDirective2 INVOKE Parameters .53Table 6 HandoffBack2 INVOKE Parameters.57Table 7

36、HandoffBack2 RETURN RESULT Parameters 60Table 8 MAP Parameter Identifiers 80Table 9 CallingFeaturesIndicator parameter.82Table 10 CDMA2000HandoffInvokeIOSData parameter 84Table 11 CDMA2000HandoffResponseIOSData parameter85Table 12 CDMACallMode parameter 86Table 13 CDMACallMode value86Table 14 CDMACa

37、llMode value87Table 15 CDMAConnectionReferenceInformation parameter.90Table 16 CDMAMSMeasuredChannelIdentity parameter .91Table 17 CDMAServiceOptionConnectionIdentifier parameter 92Table 18 CDMAServiceConfigurationRecord parameter 93Table 19 PDSNAddress parameter .95Table 20 PDSNProtocolType paramet

38、er 96Table 21 Profile Macro .97Table 22 IOS Version-4.1 IS-2000 Channel Identity(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)102Table 23 IOS Version-4.1 IS-2000 Service Configuration Record(Handoff required, Handoff Re-quest) to (FACDIR2, HANDBACK2, HANDTHIRD2).104Table 24

39、IOS Version-4.1 IS-2000 Cell Identifier List(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)104Table 25 IOS Version-4.1 IS-2000 Channel Identity(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)105Table 26 IOS Version-4.1 IS-2000 Channel Identity(Handoff r

40、equired, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)106Table 27 IOS Version-4.1 IS-2000 Service Configuration Record(Handoff required, Handoff Re-quest) to (FACDIR2, HANDBACK2, HANDTHIRD2).107Table 28 IOS Version-4.1 IS-2000 Non-Negotiable Service Configuration Record(Handoff re-quired, Han

41、doff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)107Table 29 IOS Version-4.1 Hard Handoff Parameters(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)108Table 30 IOS Version-4.1 Cell Identifier List(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2)109Table 3

42、1 IOS Version-4.1 Extended Handoff Direction Parameters(Handoff required, Handoff Re-quest) to (FACDIR2, HANDBACK2, HANDTHIRD2).109Table 32 IOS Version-4.1 IS-2000 Cell Identifier List(Handoff required, Handoff Request) to (FACDIR2, HANDBACK2, HANDTHIRD2) (concluded)110Table 33 IOS Version-4.3 Packe

43、t Session Identity (BS Service Request) to (ISPAGE2) (Rev-A) (continued) .111Table 34 Target MSC FacilitiesDirective2 Response.125Table 35 Target MSC HandoffBack2 Response.135Table 36 Tandem MSC HandoffToThird2 Response.146Table 37 Anchor MSC HandoffToThird2 Response. .150Table 38 MSC Awaiting Inter

44、SystemAnswer Response 156Table 39 Tandem MSC InterSystemAnswer Response158TIA-880-AvTable 40 MSC InterSystemSetup Response 165Table 41 Anchor MSC AddService Response . 173Table 42 Tandem MSC AddService Response 175Table 43 Receiving MSC DropService Response . 180Table 44 Operation Timer Values181Tab

45、le 45 Serving MSC InformationForward Response. 184TIA-880-AviLIST OF FIGURESFigure 1 C-PDS Invocation from an Idle MS 6Figure 2 C-PDS Invocation During an Active Circuit Call .7Figure 3 C-PDS Invocation After Handoff 8Figure 4 Post Handoff Recovery on Unsuccessful Packet Data Session Initiation .9Fi

46、gure 5 Simultaneous Circuit and C-PDS Handoff - Packet Releases First.10Figure 6 Successful Intersystem Hard Handoff of an Active Packet Data Session .13Figure 7 Successful Intersystem Hard Handoff of an Active Packet Data Session with Re-Registra-tion .15Figure 8 Successful Intersystem Hard Handoff

47、 of an Active packet Data Session Authentication Failure Prior to After-Handoff Registration 18Figure 9 Successful Intersystem Hard Handoff of an Active packet Data Session Registration Fail-ure After Handoff.21Figure 10 C-PDS Hard Handoff with Subsequent Circuit Termination 23Figure 11 C-PDS Hard H

48、andoff with Subsequent Circuit Origination25Figure 12 Simultaneous Circuit and C-PDS Handoff - Voice Releases First27Figure 13 Simultaneous Circuit and C-PDS Handoff - Voice Releases First - With Re-Registration 30Figure 14 C-PDS HandoffBack32Figure 15 C-PDS HandoffToThird 34Figure 16 Network Initia

49、ted Dormant State Re-Activation of MS in Neighbor MSC (same packet reg-istration zone, same PCF and PDSN) 37Figure 17 Network Initiated Dormant State Re-Activation of MS in Neighbor MSC (same packet reg-istration zone, same PCF and PDSN) following inter-MSC handoff 41Figure A-1: C-PDS Handoff Including A-Interface and Packet Data Network Information Flows .43Figure A-2: C-PDS Handoff Including A-Interface and Packet Data Network Information Flows (con-cluded) .44TIA-880-A123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960