1、 TIA-872-A-2004 APPROVED: MAY 1, 2004 REAFFIRMED: SEPTEMBER 19, 2013 TIA-872-A (Revision of TIA/EIA/IS-872) May 20043GPP2 All-IP Core Network Enhancements for Legacy MS Domain- Step 1 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misu
2、nderstandings 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 r
3、espect preclude 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
4、and Publications 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
5、 not purport 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
6、 Project No. PN-3-4934-UGRV1-RF1, 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 dev
7、elopment or any editing 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 patent
8、s and published pending 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 an
9、y claims of IPR. TIA 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 pr
10、ocedures or practices 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 o
11、f standards (whether 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 r
12、ecords of any other SSO 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
13、 claims of IPR in the 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 o
14、therwise investigate 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 PAR
15、TICULAR PURPOSE OR USE, 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
16、 STATUTE, RULE OR REGULATION, 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 CON
17、TENTS CONTAINED HEREIN, 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
18、LIABILITY OR OTHERWISE, 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-872-A Legacy MS Domain Step 1 1 2 3 4 5 6 7 8 9 10
19、11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 CONTENTS List of Figures .iii List of Tables.iii Foreword .iii Revision Historyiv 1 Introduction1 1.1 Scope .1 1.2 References1 1.3 Terminology 3 1.4 Architectural
20、 Principles .3 1.5 Legend .4 1.6 Abbreviations.5 2 LMSD SYSTEM REQUIREMENTS 6 2.1 General Requirements6 2.2 New Network Entities6 2.2.1 MSCe.6 2.2.2 MGW-and-MRFP6 2.3 New Reference Points7 2.3.1 Reference Point 39 7 2.3.2 Reference Point xx 7 2.3.3 Reference Point yy 7 2.3.4 Reference Point zz.7 3 L
21、egacy MS Domain Stage-2 8 3.1 LMSD Architecture .8 3.2 Reference Points 10 3.2.1 Reference Point 13 10 3.2.2 Reference Point 14 10 3.2.3 Reference Point 27 IOS-A2 10 3.2.4 Reference Point 27 IOS-A5 10 3.2.5 Reference Point 34 10 3.2.6 Reference Point 39 11 3.2.7 Reference Point xx 11 3.2.8 Reference
22、 Point 48 IOS-A1 11 3.2.9 Reference Point yy 12 3.2.10 Reference Point zz.12 57 58 59 60 i Contents 3.2.10.1 Working Assumptions12 3.3 Network Entities 13 TIA-872-A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
23、49 50 51 52 53 54 55 56 57 58 59 Contents ii 3.3.1 Legacy MS Domain Support (LMSDS) 13 3.3.2 Media Gateway and Media Resource Function Processor 15 3.4 Legacy MS Domain Scenarios.163.4.1 Call Delivery to an Idle MS on Another MSCe.16 3.4.2 Call Delivery Serving Network Fails to Respond 21 3.4.3 CFD
24、Invocation with No Answer or No Response to Page.23 3.4.4 Call Clearing Initiated by the MS26 3.4.4.1 Call Clearing Initiated by the PSTN.284 Legacy MS Domain Stage-3 30 4.1 SIP-T/SIP INVITE Request.30 4.1.1 Example INVITE Request.31 4.1.2 ISUP IAM Generation .324.2 SIP-T/SIP Response Codes32 TIA-87
25、2-A LIST OF FIGURES 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 Figure 3.1 Legacy MS Domain Support for Circuit Mode IP Transport Call Delivery .9 Figure 3.2.10 SIP-T Protocol Stack for
26、 Reference Point zz13 Figure 3.4.1 Call Delivery to an Idle MS on Another MSCe17 Figure 3.4.2 Call Delivery Serving Network Fails to Respond21 Figure 3.4.3 CFD Invocation with No Answer or No Response to Page 24 Figure 3.4.4 Call Clearing Initiated by the MS .26 Figure 3.4.5 Call Clearing Initiated
27、by the PSTN .28 LIST OF TABLES Table 3.2.6: Megaco Package Support11 Table 3.2.7: Megaco Package Support11 Table 4.1: Required Headers within the INVITE Request.30 Table 4.2.1: Supported Response Codes.33 FOREWORD This 3GPP2 Wireless IP Network Architecture Model depicts packet mode operations and g
28、ateway information. 57 58 59 60 iii List of Figures TIA-872-A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 REVISION HISTORY Rev. Date Remarks 0 December 2000 Initial Publication Addendum 1 March 2004 Editorial Enhancements 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
29、 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 3GPP2 TSG-X / TIA TR-45.2 iv TIA-872-A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 1 INTRODUCTION 1.1 Scope This recommendation supports the 3GPP2 All-IP Step 1 Evolution Path by providing Stage-1, 2 and 3 for the architecture
30、 identified in Figure 3.1, “Legacy MS Domain Support for Circuit Mode IP Transport Call Delivery”. The Legacy MS Domain provides support for existing MSs (e.g., analog, IS-95-A, IS-95-B, IS-2000) in an IP core network environment. The Legacy MS Domain supports the features and capabilities provided
31、in a legacy network in a manner transparent to the user. New features and capabilities supported by the IP core network may be made available to subscribers where they are supported by MS capabilities. This document specifies signaling reference point zz (MSCe-to-MSCe). This reference point supports
32、 Media Gateway-to-Media Gateway bearer streams (i.e., yy reference point). The yy reference point is used as a bearer facility for legacy voice calls and is specified in 3GPP2-4. 1.2 References 3GPP2 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 3GPP2-1 3GPP2
33、: S.R0059, Legacy MS Domain Step 1 System Requirements; May 2002 3GPP2-2 3GPP2: S.R0037 v3.0, All-IP Network Architecture Model for cdma20001Spread Spectrum Systems; September 2003 TIA: TSB151, IP Network Reference Model (NRM) for cdma2000 Spread Spectrum Systems; January 2004 TTC: TS-3GB-S.R0037-0
34、v3.0; IP Network Reference Model (NRM) for cdma2000 Spread Spectrum Systems 3GPP2-3 3GPP2: A.S0001-A v2.0, 3GPP2 Access Network Interfaces Interoperability Specification Revision A (3G-IOS v4.1.1) Revision A; June 2001 CCSA: CCSA-MC-A.S0001-A v2.0; 3GPP2 Access Network Interfaces Interoperability Sp
35、ecification Revision A (3G-IOS v4.1.1) Revision A TIA: TIA-2001-A; Interoperability Specifcations (IOS) for cdma2000 Access Network Interfaces (2001); August 2001 57 58 59 60 1.1 Scope 1 1 Introduction 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards
36、of the Organizational Partners (OPs) of 3GPP2. When applied to goods and services, the cdma2000mark certifies their compliance with cdma2000standards. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in th
37、e United States. TIA-872-A 3GPP2-4 3GPP2: X.S0018, Legacy Mobile Station Domain (LMSD) Step 1; May 2003 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 1 Introduction 2 1.2 Referen
38、ces TIA: TIA-930, Legacy Mobile Station Domain (LMSD) Step 1;January 2003 TTA: TTAT.3G-X.S0018 v1.0.0, Legacy Mobile Station Domain (LMSD) Step 1 TTC: TS-3GB-X.S0018-0 v1.0.0, Legacy Mobile Station Domain (LMSD) Step 1 3GPP2-5 3GPP2: N.S0005, Cellular Radiotelecommunications Intersystem Operations C
39、CSA: YD/T-1031-1999; Cellular Radiotelecommunications Intersystem Operations TIA: ANS/TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations; September 1997 TTA: TTAE.3G-N.S0005; Radiotelecommunications IntersystemOperations TIA: TIA/EIA/IS-737, IS-41-C Enhancements to Support Circuit
40、 Mode Services; May 1998 3GPP2-7 3GPP2: N.S0029-0 v1.0, Circuit TIA/EIA-41-D Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1, Revision: 0; June 2002 TIA: TIA-880, TIA/EIA-41-D Based Network Enhancements for CDMAPacket Data Service (C-PDS), Phase-1; July 2002 TTC: TS-3GB-N.S0
41、029-0v1.0, Circuit TIA/EIA-41-D Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1, Revision: 0 CCITT-1 Recommendation G.711 (1988) Pulse Code Modulation (PCM) of Voice Frequencies. IETF-3 RFC 3398, Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiati
42、on Protocol (SIP) Mapping 3GPP2-6 3GPP2: N.S0008, Circuit Mode Services TTC: JP-3GB-N.S0008, Circuit Mode Services CCITT IETF IETF-1 RFC 3261, SIP: Session Initiation Protocol IETF-2 RFC 3372, SIP for Telephones (SIP-T): Context and Architectures IETF-4 RFC 2960, Stream Control Transmission Protocol
43、 IETF-5 RFC 0793, Transmission Control Protocol TIA-872-A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 IETF-6 RFC 0768, User Datagram Protocol IETF-7 RFC 0791, Internet Protocol IETF-8 R
44、FC 3015, Megaco Protocol Version 1.0 IETF-9 RFC 3312, Integration of Resource Management and SIP IETF-10 RFC 3204, MIME media types for ISUP and QSIG Objects 1.3 Terminology This document uses the following “verbal forms” and “verbal form definitions”: a. “shall” and “shall not” identify items of in
45、terest that are to be strictly followed and from which no deviation is recommended, b. “should” and “should not” indicate items of interest that are highly desirable and particularly suitable, without identifying or excluding other items; or (in the negative form) indicate items of interest that are
46、 not desirable, are not particularly suitable, or are not recommended but not prohibited, and c. “may” and “may not” indicate items of interest that are optional but permissible within the limits of this recommendation. 1.4 Architectural Principles The statements contained in this section shall guid
47、e the development of the All-IP network architecture 3GPP2-2. While these statements are too general to be treated as specific requirements, they form a set of principles meant to govern the overall development of the All-IP network, they are: a. The All-IP network architecture shall be independent
48、of the underlying Layer 1 and Layer 2 protocols through the use of IP-based protocols. b. The All-IP core network shall be independent of the access network. The core network shall have the ability to support multiple access network technologies (e.g., cable, radio access technologies, wireless LAN,
49、 DSL). The core network should have the ability to support access networks as they evolve and as new access technologies are identified. This implies that network functions such as call control and service control should be independent of access functions. How this independence is maintained for mobility management and location-based services (which may be dependent on access technology) is for further study. c. A phased migration of existing networks to the All-IP network shall be possible. d. All pertinent interfaces in the Al
