1、 TIA-2001.2-E-4 (Addendum to TIA-2001.2-E) April 2014Interoperability 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 an
2、d 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-memb
3、er 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 in
4、 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 pro
5、blems 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. Any use of trademarks in this document are
6、for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-2001.2-E-4, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committe
7、e 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 use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or is
8、sued 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 applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Man
9、ual. 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 party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine o
10、r judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures 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 Norma
11、tive References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elemen
12、ts (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 letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engin
13、eering 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 publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending paten
14、t 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 or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED,
15、INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILI
16、TIES 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 SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY
17、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 WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS
18、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 OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HERE
19、OF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-2001.2-E-4 Revision History Date Publication Description June 2007 A.S0012-D v1.0 For features supported, refer to the Overview 11, section 1.1. August 2009 A.S0012-D v2.0 Updates to support 1x air interface enhanceme
20、nts, 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. August 2012 A.S0012-D v4.0 Support for EVRC-B, EVRC-WB, EVRC-NW, EVRC-NW2K, USSD, MSC-BS indication of Device Ty
21、pe and bug fix March 2014 A.S0012-D v5.0 Support for USSD on common channel, M2M IOS and bug fix. TIA-2001.2-E-4 (This page intentionally left blank.) TIA-2001.2-E-4 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
22、.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 Layer (Layer 2) 8 17 2.3 Use of ATM . 9 18 2.3.1 AT
23、M Adaptation Layer 9 19 2.3.2 Use of ATM AAL5 for Transmission 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.2 Routing . 10 25 2.4.2.3 Flow Association 10 26 2.4
24、.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 Establishment . 13 32 2.5.3 TCP Connection Release 13
25、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 18 40 2.6.3 GRE Protocol Usage for VoIP S
26、Os 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 Requirements 23 48 3.1 A1, A2, and A5 Interfaces 2
27、3 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.1 General . 25 55 i TIA-2001.2-E-4 3.1.3.
28、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 Congestion) 29 6 3.1.3.3 SCCP Tran
29、sport 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) 32 12 3.1.3.4 Use of the SCCP .
30、 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 SCCP Connection Information 40 19 3.1
31、.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.2.2 A1p Transport Protocol 46 25 3.2.2.1 P
32、hysical 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 SUA Connection Establishment . 48 32
33、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 SUA Release by MSCe: Loss of SUA Connectio
34、n 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 43 3.2.3.2 Layer 2 Specification for A2p
35、 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 61 50 3.3.2 A3 User Traffic Transport Requi
36、rements . 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 ii TIA-2001.2-E-4 3.3.2.2.1 Physical Layer (L1) Specification 62 1 3.3.2.2.2 Layer 2
37、 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 3.3.3.1.2 Use of ATM 64 9 3.3.3.1.3 U
38、se 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 17 3.3.3.2.5 Security Specifications
39、 . 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 iii TIA-2001.2-E-4 List of Figures 1 2 Figure 2-1 Transport Network Ref
40、erence 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 Reference Model . 20 8 Fig
41、ure 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 Figure 3.1.3.4.1.2-
42、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 message . 37 18 Figure
43、 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 SCCP Release: MSC
44、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 Establishm
45、ent 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 Protoco
46、l 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 Protocol Sta
47、ck 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 Use
48、r Traffic Protocol Stack 69 43 44 45 iv TIA-2001.2-E-4 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 for B
49、SMAP 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 v TIA-2001.2-E-4 Foreword 1 2 This foreword is not part of this document. 3 4 This document was produced by TSG-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 vi TIA-2001.2-E-4 1.0 Introduction 1 2 1.1 Overview 3 This document contain
