1、 TIA-2001.2-E-2 (Addendum to TIA-2001.2-E) October 2011Interoperability Specification (IOS) for cdma2000 Access 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-me
3、mber 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 p
5、roblems 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. 3-4545.2-RV5-AD2, formu
6、lated 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 us
7、e 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 applicat
8、ions 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 a
9、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 prov
10、ided 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 st
11、andard, 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 lett
12、ers 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 public
13、ations 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, designs
14、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 MERCHANTABI
15、LITY 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 SA
16、FETY 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 WITHO
17、UT 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 ADVISED
18、 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. Revision History Date Publication Description June 2007 A.S0012-D v1.0 For features supported,
19、 refer to the Overview 11, section 1.1. August 2009 A.S0012-D v2.0 Updates to support 1x air interface enhancements, EVRC-WB 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 0, and bug fixes.
20、TIA-2001.2-E-2 i Table of Contents 1 2 Foreword vi 3 1.0 Introduction . 1 4 1.1 Overview . 1 5 1.1.1 Purpose . 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 2.0 General Prot
21、ocol Requirements . 7 14 2.1 Physical Layer (Layer 1) . 7 15 2.2 Link Layer (Layer 2) . 8 16 2.3 Use of ATM 9 17 2.3.1 ATM Adaptation Layer 9 18 2.3.2 Use of ATM AAL5 for Transmission of IP Datagrams 9 19 2.4 IP Transport Considerations 9 20 2.4.1 IP Topologies 9 21 2.4.2 IP Network and Transport Sp
22、ecifications (Layers 3/4) 10 22 2.4.2.1 Addressing .10 23 2.4.2.2 Routing 10 24 2.4.2.3 Flow Association .10 25 2.4.3 IP Performance Specifications .10 26 2.4.4 Transport Network IP Quality of Service (QoS) Framework 10 27 2.4.5 IP Security Framework Specifications .11 28 2.5 Use of TCP .11 29 2.5.1
23、 Message Delimiting in TCP .11 30 2.5.2 TCP Connection Establishment .13 31 2.5.3 TCP Connection Release .13 32 2.6 Use of GRE 13 33 2.6.1 GRE Attributes 16 34 2.6.1.1 Short Data Indicator .16 35 2.6.1.2 Flow Control Indication .16 36 2.6.1.3 IP Flow Discriminator .17 37 2.6.1.4 Segmentation Indicat
24、ion 18 38 2.6.2 Relationship of GRE tunnel to Quality of Service .18 39 2.6.3 GRE Protocol Usage for VoIP SOs .19 40 2.7 Use of RTP .19 41 2.8 Use of SUA 19 42 2.9 Base Station Application Part.19 43 2.9.1 The BS Management Application Part 20 44 2.9.2 The Direct Transfer Application Part 20 45 2.10
25、 Use of SCTP .20 46 3.0 Interface Specific Protocol Requirements 23 47 3.1 A1, A2, and A5 Interfaces 23 48 3.1.1 Signaling Connection Transport Protocol Options 23 49 3.1.2 User Traffic Connection Transport Protocol Options 24 50 3.1.3 Use of ANSI SS7 Transport (Layer 2) .24 51 3.1.3.1 Field of Appl
26、ication .25 52 3.1.3.2 Message Transfer Part .25 53 3.1.3.2.1 General 25 54 3.1.3.2.2 Level 1 (Chapter 2 of 21) .25 55 TIA-2001.2-E-2 ii 3.1.3.2.3 Level 2 (Chapter 3 of 21) .26 1 3.1.3.2.4 Level 3 (Chapter 4 of 21) .26 2 3.1.3.2.5 Testing and Maintenance (Chapter 7 of 21) .29 3 3.1.3.2.6 Interface F
27、unctions .29 4 3.1.3.2.7 Overload Control (Message Throughput Congestion) 29 5 3.1.3.3 SCCP Transport Layer Specification (SCCP Functions) .29 6 3.1.3.3.1 Overview .29 7 3.1.3.3.2 Primitives (Chapter 1 of 22) .30 8 3.1.3.3.3 SCCP Messages (Chapter 2 of 22) .30 9 3.1.3.3.4 SCCP Formats and Codes (Cha
28、pter 3 of 22) 32 10 3.1.3.3.5 SCCP Procedures (Chapter 4 of 22) .32 11 3.1.3.4 Use of the SCCP 34 12 3.1.3.4.1 Connection Establishment 34 13 3.1.3.4.1.1 Establishment Procedure - Case 1 34 14 3.1.3.4.1.2 Establishment Procedure - Case 2 36 15 3.1.3.4.2 Connection Release .39 16 3.1.3.4.3 Abnormal S
29、CCP Release 40 17 3.1.3.4.3.1 SCCP Release by BS: Loss of SCCP Connection Information 40 18 3.1.3.4.3.2 SCCP Release by MSC: Loss of SCCP Connection Information 41 19 3.1.3.4.4 SCCP Reference Generation Philosophy 41 20 3.1.3.4.5 SCCP Transfer of DTAP and BSMAP Messages .42 21 3.2 A1p and A2p Interf
30、aces 46 22 3.2.1 Performance Specifications .46 23 3.2.2 A1p Transport Protocol .46 24 3.2.2.1 Physical Layer (L1) Specification for A1p 47 25 3.2.2.2 Layer 2 Specification for A1p .47 26 3.2.2.3 Use of IP for A1p .47 27 3.2.2.4 QoS Specifications for A1p .47 28 3.2.2.5 Security Specifications for A
31、1p .47 29 3.2.2.6 Use of the SUA for A1p 47 30 3.2.2.6.1 SUA Connection Establishment48 31 3.2.2.6.1.1 Establishment Procedure - Case 1 48 32 3.2.2.6.1.2 Establishment Procedure - Case 2 49 33 3.2.2.6.2 Connection Release .50 34 3.2.2.6.3 Abnormal SUA Release 51 35 3.2.2.6.3.1 SUA Release by BS: Los
32、s of SUA Connection Information .51 36 3.2.2.6.3.2 SUA Release by MSCe: Loss of SUA Connection Information 52 37 3.2.2.6.4 SUA Transfer of DTAP and BSMAP Messages .52 38 3.2.2.7 Base Station Application Part on A1p .56 39 3.2.2.8 Use of SCTP 56 40 3.2.3 A2p User Traffic Transport Protocol .56 41 3.2
33、.3.1 Physical Layer (L1) Specification for A2p 59 42 3.2.3.2 Layer 2 Specification for A2p .59 43 3.2.3.3 Use of IP for A2p .59 44 3.2.3.4 QoS Specifications for A2p .59 45 3.2.3.5 Security Specifications for A2p .60 46 3.3 A3 and A7 Interfaces60 47 3.3.1 Performance Specifications .60 48 3.3.1.1 Pe
34、rformance Specification for IP Protocol Stacks .61 49 3.3.2 A3 User Traffic Transport Requirements 61 50 3.3.2.1 ATM-Based User Traffic Transport 62 51 3.3.2.1.1 Physical Layer (L1) Specification .62 52 3.3.2.1.2 Use of ATM 62 53 3.3.2.1.3 Use of AAL2 .62 54 3.3.2.2 IP-Based User Traffic Transport 6
35、2 55 3.3.2.2.1 Physical Layer (L1) Specification .62 56 TIA-2001.2-E-2 iii 3.3.2.2.2 Layer 2 Specification 62 1 3.3.2.2.3 Use of IP .63 2 3.3.2.2.4 QoS Specifications 63 3 3.3.2.2.5 Security Specifications63 4 3.3.3 A3/A7 Signaling Transport Requirements .63 5 3.3.3.1 ATM-Based Signaling Protocol St
36、ack .64 6 3.3.3.1.1 Use of Physical Layer .64 7 3.3.3.1.2 Use of ATM 64 8 3.3.3.1.3 Use of AAL5 .64 9 3.3.3.1.4 Use of IP .64 10 3.3.3.1.5 Use of TCP .65 11 3.3.3.2 IP-Based Signaling Protocol Stack 65 12 3.3.3.2.1 Use of Physical Layer .65 13 3.3.3.2.2 Layer 2 Specification 65 14 3.3.3.2.3 Use of I
37、P .65 15 3.3.3.2.4 QoS Specifications 66 16 3.3.3.2.5 Security Specifications66 17 3.3.3.2.6 Use of SCTP .66 18 3.4 A8 and A9 Interfaces66 19 3.4.1 Use of TCP 67 20 3.4.2 Use of UDP 67 21 3.4.3 Use of GRE 68 22 3.5 A10 and A11 Interface .68 23 3.5.1 Use of UDP 69 24 3.5.2 Use of GRE 69 25 26 27 TIA-
38、2001.2-E-2 iv List of Figures 1 2 Figure 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
39、 Interface Signaling Protocol Reference 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
40、Establishment Refusal 35 13 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 me
41、ssage in an SCCP 17 DT1 message 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
42、3.1.3.4.3.2-1 MSC Initiated SCCP 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
43、 3.2.2.6.1.2-1 SUA Connection 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 Inform
44、ation 52 30 Figure 3.2.3-1 Protocol 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 .5
45、9 36 Figure 3.2.3-7 Protocol 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 St
46、ack 69 42 Figure 3.5-2 A10 User Traffic Protocol Stack69 43 44 45 TIA-2001.2-E-2 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
47、3.2.2.6.4-2 Use of SUA 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-2 vi Foreword 1 2 This foreword is not part of this standard. 3 4 This document was produced by TSG
48、-A of the Third Generation 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 10 11 TIA-2001.2-E-2 1 Section 1 1.0 Introduction 1 2 1.1 Overview 3 T
49、his 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 model, and to indicate any 8 unique aspects of these protocols that are relevant to the Interoperability Specification 9 (IOS). 10 1.1.2 Scope 11 This document contains generic and specific requirements for the IOS interfaces. The 12 document contains the generic protocol descri
