1、 TIA-2001.2-E-3 (Addendum to TIA-2001.2-E) November 2012Interoperability Specification (IOS) for cdma2000Access Network Interfaces- Part 2 Transport NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers
2、 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 preclude any member or non-m
3、ember 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 Publications are adopted by TIA
4、 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 to address all safety
5、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. TIA-PN-2001.2-E-3, for
6、mulated 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 editing process. The
7、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 pending patent applic
8、ations 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 will neither be
9、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 suggested or pr
10、ovided 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 designated as a
11、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 SSO for IPR or le
12、tters 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 records or publ
13、ications 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 products, design
14、s 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 USE, ITS MERCHANTA
15、BILITY 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 REGULATION, OR THE
16、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 HEREIN, INCLUDING WIT
17、HOUT 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 OTHERWISE, EVEN IF ADVIS
18、ED 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-2001.2-E-3 Revision History Date Publication Description June 2007 A.S0012-D v1.0 For fe
19、atures supported, refer to the Overview 11, section 1.1. August 2009 A.S0012-D v2.0 Updates to support 1x air interface enhancements, EVRC-W B on A2p, EVRC-NW on A2 and A2p and bug fixes. May 2011 A.S0012-D v3.0 Support for callback of an emergency call origination, EVRC-NW capacity operating point
20、0, and bug fixes. August 2012 A.S0012-D v4.0 Support for EVRC-B, EVRC-WB, EVRC-NW, EVRC-NW2K, USSD, MSC-BS indication of Device Type and bug fix TIA-2001.2-E-3 (This page intentionally left blank.) TIA-2001.2-E-3 i Table of Contents 1 2 Foreword vi 3 1.0 Introduction. 1 4 1.1 Overview . 1 5 1.1.1 Pu
21、rpose 1 6 1.1.2 Scope . 1 7 1.2 References . 1 8 1.2.1 Normative References 1 9 1.2.2 Informative References 3 10 1.3 Terminology . 3 11 1.3.1 Acronyms . 3 12 1.3.2 Definitions 6 13 1.4 Documentation Conventions 6 14 2.0 General Protocol Requirements. 7 15 2.1 Physical Layer (Layer 1) 7 16 2.2 Link
22、Layer (Layer 2) . 8 17 2.3 Use of ATM 9 18 2.3.1 ATM Adaptation Layer 9 19 2.3.2 Use of ATM AAL5 for Trans mission of IP Datagrams . 9 20 2.4 IP Transport Considerations. 9 21 2.4.1 IP Topologies . 9 22 2.4.2 IP Network and Transport Specifications (Layers 3/4) 10 23 2.4.2.1 Addressing . 10 24 2.4.2
23、.2 Routing . 10 25 2.4.2.3 Flow Association 10 26 2.4.3 IP Performance Specifications 10 27 2.4.4 Transport Network IP Quality of Service (QoS) Framework 10 28 2.4.5 IP Security Framework Specifications 11 29 2.5 Use of TCP 11 30 2.5.1 Message Delimiting in TCP 11 31 2.5.2 TCP Connection Establishme
24、nt 13 32 2.5.3 TCP Connection Release . 13 33 2.6 Use of GRE . 13 34 2.6.1 GRE Attributes 16 35 2.6.1.1 Short Data Indicator . 16 36 2.6.1.2 Flow Control Indication. 16 37 2.6.1.3 IP Flow Discriminator 17 38 2.6.1.4 Segmentation Indication 18 39 2.6.2 Relationship of GRE Tunnel to Quality of Service
25、 . 18 40 2.6.3 GRE Protocol Usage for VoIP SOs . 19 41 2.7 Use of RTP 19 42 2.8 Use of SUA . 19 43 2.9 Base Station Application Part 19 44 2.9.1 The BS Management Application Part 20 45 2.9.2 The Direct Transfer Application Part 20 46 2.10 Use of SCTP . 20 47 3.0 Interface Specific Protocol Requirem
26、ents . 23 48 3.1 A1, A2, and A5 Interfaces 23 49 3.1.1 Signaling Connection Transport Protocol Options 23 50 3.1.2 User Traffic Connection Transport Protocol Options. 24 51 3.1.3 Use of ANSI SS7 Transport (Layer 2) 24 52 3.1.3.1 Field of Application 25 53 3.1.3.2 Message Transfer Part 25 54 3.1.3.2.
27、1 General 25 55 TIA-2001.2-E-3 ii 3.1.3.2.2 Level 1 (Chapter 2 of 21) 25 1 3.1.3.2.3 Level 2 (Chapter 3 of 21) 26 2 3.1.3.2.4 Level 3 (Chapter 4 of 21) 26 3 3.1.3.2.5 Testing and Maintenance (Chapter 7 of 21) 29 4 3.1.3.2.6 Interface Functions 29 5 3.1.3.2.7 Overload Control (Message Throughput Cong
28、estion) 29 6 3.1.3.3 SCCP Transport Layer Specification (SCCP Functions). 29 7 3.1.3.3.1 Overview 29 8 3.1.3.3.2 Primitives (Chapter 1 of 22) . 30 9 3.1.3.3.3 SCCP Messages (Chapter 2 of 22) 30 10 3.1.3.3.4 SCCP Formats and Codes (Chapter 3 of 22) . 32 11 3.1.3.3.5 SCCP Procedures (Chapter 4 of 22)
29、. 32 12 3.1.3.4 Use of the SCCP . 34 13 3.1.3.4.1 Connection Establishment . 34 14 3.1.3.4.1.1 Establishment Procedure - Case 1 34 15 3.1.3.4.1.2 Establishment Procedure - Case 2 36 16 3.1.3.4.2 Connection Release. 39 17 3.1.3.4.3 Abnormal SCCP Release . 40 18 3.1.3.4.3.1 SCCP Release by BS: Loss of
30、 SCCP Connection Information. 40 19 3.1.3.4.3.2 SCCP Release by MSC: Loss of SCCP Connection Information. 41 20 3.1.3.4.4 SCCP Reference Generation Philosophy 41 21 3.1.3.4.5 SCCP Transfer of DTAP and BSMAP Messages . 42 22 3.2 A1p and A2p Interfaces 46 23 3.2.1 Performance Specifications . 46 24 3.
31、2.2 A1p Transport Protocol 46 25 3.2.2.1 Physical Layer (L1) Specification for A1p 47 26 3.2.2.2 Layer 2 Specification for A1p 47 27 3.2.2.3 Use of IP for A1p 47 28 3.2.2.4 QoS Specifications for A1p 47 29 3.2.2.5 Security Specifications for A1p . 47 30 3.2.2.6 Use of the SUA for A1p 47 31 3.2.2.6.1
32、 SUA Connection Establishment . 48 32 3.2.2.6.1.1 Establishment Procedure - Case 1 48 33 3.2.2.6.1.2 Establishment Procedure - Case 2 49 34 3.2.2.6.2 Connection Release. 50 35 3.2.2.6.3 Abnormal SUA Release . 51 36 3.2.2.6.3.1 SUA Release by BS: Loss of SUA Connection Information. 51 37 3.2.2.6.3.2
33、SUA Release by MSCe: Loss of SUA Connection Information. 52 38 3.2.2.6.4 SUA Transfer of DTAP and BSMAP Messages . 52 39 3.2.2.7 Base Station Application Part on A1p. 56 40 3.2.2.8 Use of SCTP 56 41 3.2.3 A2p User Traffic Transport Protocol. 56 42 3.2.3.1 Physical Layer (L1) Specification for A2p 59
34、 43 3.2.3.2 Layer 2 Specification for A2p 59 44 3.2.3.3 Use of IP for A2p 59 45 3.2.3.4 QoS Specifications for A2p 59 46 3.2.3.5 Security Specifications for A2p . 60 47 3.3 A3 and A7 Interfaces. 60 48 3.3.1 Performance Specifications . 60 49 3.3.1.1 Performance Specification for IP Protocol Stacks 6
35、1 50 3.3.2 A3 User Traffic Transport Requirements . 61 51 3.3.2.1 ATM-Based User Traffic Transport 62 52 3.3.2.1.1 Physical Layer (L1) Specification 62 53 3.3.2.1.2 Use of ATM . 62 54 3.3.2.1.3 Use of AAL2 62 55 3.3.2.2 IP-Based User Traffic Transport 62 56 TIA-2001.2-E-3 iii 3.3.2.2.1 Physical Laye
36、r (L1) Specification 62 1 3.3.2.2.2 Layer 2 Specification 62 2 3.3.2.2.3 Use of IP . 63 3 3.3.2.2.4 QoS Specifications 63 4 3.3.2.2.5 Security Specifications . 63 5 3.3.3 A3/A7 Signaling Transport Requirements 63 6 3.3.3.1 ATM-Based Signaling Protocol Stack 64 7 3.3.3.1.1 Use of Physical Layer. 64 8
37、 3.3.3.1.2 Use of ATM . 64 9 3.3.3.1.3 Use of AAL5 64 10 3.3.3.1.4 Use of IP . 64 11 3.3.3.1.5 Use of TCP . 65 12 3.3.3.2 IP-Based Signaling Protocol Stack 65 13 3.3.3.2.1 Use of Physical Layer. 65 14 3.3.3.2.2 Layer 2 Specification 65 15 3.3.3.2.3 Use of IP . 65 16 3.3.3.2.4 QoS Specifications 66 1
38、7 3.3.3.2.5 Security Specifications . 66 18 3.3.3.2.6 Use of SCTP. 66 19 3.4 A8 and A9 Interfaces. 66 20 3.4.1 Use of TCP . 67 21 3.4.2 Use of UDP 67 22 3.4.3 Use of GRE 68 23 3.5 A10 and A11 Interface 68 24 3.5.1 Use of UDP 69 25 3.5.2 Use of GRE 69 26 27 28 TIA-2001.2-E-3 iv List of Figures 1 2 Fi
39、gure 2-1 Transport Network Reference Model . 7 3 Figure 2.5.1-1 Delimiting Messages in an IOS Application TCP Byte Stream 12 4 Figure 2.6-1 GRE Encapsulated User Traffic 14 5 Figure 2.6-2 3GPP2 GRE Frame 14 6 Figure 2.6-3 Attribute Format. 15 7 Figure 2.9-1 A1 or A1p Interface Signaling Protocol Ref
40、erence Model. 20 8 Figure 3.1.1-1 A1 Signaling Protocol Stack 24 9 Figure 3.1.2-1 A2 User Traffic Protocol Stacks . 24 10 Figure 3.1.2-2 A5 User Traffic Protocol Stacks . 24 11 Figure 3.1.3.4.1.1-1 SCCP Connection Establishment 35 12 Figure 3.1.3.4.1.1-2 SCCP Connection Establishment Refusal . 35 13
41、 Figure 3.1.3.4.1.2-1 SCCP Connection Establishment with a Handoff Request message in an SCCP 14 Connection Request message. 36 15 Figure 3.1.3.4.1.2-2 SCCP Connection Refusal During Handoff 37 16 Figure 3.1.3.4.1.2-3 SCCP Connection Establishment with a Handoff Request message in an SCCP 17 DT1 mes
42、sage 37 18 Figure 3.1.3.4.1.2-4 SCCP Connection with Handoff Failure via DT1 38 19 Figure 3.1.3.4.1.2-5 SCCP Connection Refused reply to a null SCCP Connection Request 39 20 Figure 3.1.3.4.3.1-1 BS Initiated SCCP Release: BS Lost SCCP Connection Information 40 21 Figure 3.1.3.4.3.2-1 MSC Initiated S
43、CCP Release: MSC Lost SCCP Connection Information 41 22 Figure 3.1.3.4.4-1 SLR/DLR Usage . 42 23 Figure 3.2.2-1 A1p Signaling Protocol Stack 46 24 Figure 3.2.2.6.1.1-1 SUA Connection Establishment 48 25 Figure 3.2.2.6.1-2 SUA Connection Establishment Refusal 49 26 Figure 3.2.2.6.1.2-1 SUA Connection
44、 Establishment During Handoff 50 27 Figure 3.2.2.6.1.2-2 SUA Connection Refusal During Handoff 50 28 Figure 3.2.2.6.3.1-1 BS Initiated SUA Release: BS Lost SUA Connection Information 51 29 Figure 3.2.2.6.3.2-1 MSCe Initiated SUA Release: MSCe Lost SUA Connection Information 52 30 Figure 3.2.3-1 Prot
45、ocol stack for EVRC and SMV 57 31 Figure 3.2.3-2 Protocol stack for PCM (G.711) . 57 32 Figure 3.2.3-3 Protocol Stack for 13k. 58 33 Figure 3.2.3-4 Protocol Stack for DTMF . 58 34 Figure 3.2.3-5 Protocol Stack for EVRC-B . 58 35 Figure 3.2.3-6 Protocol Stack for EVRC-WB. 59 36 Figure 3.2.3-7 Protoco
46、l Stack for EVRC-NW 59 37 Figure 3.3.2-1 A3 User Traffic Protocol Stack . 61 38 Figure 3.3.3-1 A3 and A7 Signaling Protocol Stack 64 39 Figure 3.4-1 A9 Signaling Protocol Stack 67 40 Figure 3.4-2 A8 User Traffic Protocol Stack . 67 41 Figure 3.5-1 A11 Signaling Protocol Stack 69 42 Figure 3.5-2 A10
47、User Traffic Protocol Stack . 69 43 44 45 TIA-2001.2-E-3 v List of Tables 1 2 Table 3.1.3.4.5-1 Use of the User Data Field in SCCP Frames 42 3 Table 3.1.3.4.5-2 Use of SCCP for BSMAP and DTAP Messages . 43 4 Table 3.2.2.6.4-1 Use of the User Data Field in SUA Frames 53 5 Table 3.2.2.6.4-2 Use of SUA
48、 for BSMAP and DTAP Messages . 53 6 Table 3.3.1-1 Delay Budget Requirements 60 7 Table 3.3.1.1-1 A3/A7 Mapping Between Traffic Classes and Service-Level QoS 61 8 9 10 TIA-2001.2-E-3 vi Foreword 1 2 This foreword is not part of this document. 3 4 This document was produced by TSG-A of the Third Gener
49、ation Partnership Project 2. This document was 5 developed in accordance with the procedural guidelines of 3GPP2 and its Organizational Partners, and 6 represents the consensus position of these groups. 7 8 9 TIA-2001.2-E-3 1 Section 1 1.0 Introduction 1 2 1.1 Overview 3 This document contains the protocol definitions and transport requirements for the 4 interfaces defined in this specification. 5 1.1.1 Purpose 6 The purpose of this document is to describe the transport protocols and protocol stacks 7 used on the interfaces, which make up the logical network
