1、 TIA-2001.2-E-1 (Addendum to TIA-2001.2-E)January 2010 Interoperability Specification (IOS) forcdma2000Access Network Interfaces Part 2 Transport 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 NOTICE TIA Engineering Standards and Publications are d
2、esigned to serve the public interest through eliminating misunderstandings 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 ex
3、istence of such Standards and Publications shall not in any respect 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-TI
4、A members, either domestically or internationally. Standards 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 par
5、ties adopting the Standard or Publication. This Standard does 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
6、applicability of regulatory limitations before its use. (From Project No. PN-3-4545.2-RV5-AD1, 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 Docu
7、ment 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 issued patents, or copyrights, owned by one or more parties. TIA makes no s
8、earch 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 Manual. TIA takes no position with reference to, and disclaims any obligatio
9、n 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 or judge whether proposed licensing terms or conditions are reasonable or
10、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 Normative References to a document published by another organization (“other S
11、SO”) 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 elements (as defined in the TIA Engineering Manual, 4th edition) then (i) TIA d
12、isclaims 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 Engineering Manual Section 6.5.1) of Essential Patent(s) and published pendin
13、g 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 patent applications. TIA does not enforce or monitor compliance with the cont
14、ents 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, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCU
15、RACY 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 RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WA
16、RRANTIES 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 WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRE
17、CT 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 OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTR
18、ACT, 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 HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITA
19、TIONS. TIA-2001.2-E-1 Table of Contents 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 1.0 Introduction 1 1.1 Overview 1 1.1.1 Purpose . 1 1.1.2 Scope 1 1.2 References 1 1.2.1 Normative Refer
20、ences 1 1.2.2 Informative References. 3 1.3 Terminology . 3 1.3.1 Acronyms 3 1.3.2 Definitions 6 2.0 General Protocol Requirements 7 2.1 Physical Layer (Layer 1) 7 2.2 Link Layer (Layer 2) 8 2.3 Use of ATM 9 2.3.1 ATM Adaptation Layer 9 2.3.2 Use of ATM AAL5 for Transmission of IP Datagrams 9 2.4 IP
21、 Transport Considerations . 9 2.4.1 IP Topologies 9 2.4.2 IP Network and Transport Specifications (Layers 3/4). 10 2.4.2.1 Addressing 10 2.4.2.2 Routing . 10 2.4.2.3 Flow Association 10 2.4.3 IP Performance Specifications 10 2.4.4 Transport Network IP Quality of Service (QoS) Framework . 10 2.4.5 IP
22、 Security Framework Specifications 11 2.5 Use of TCP . 11 2.5.1 Message Delimiting in TCP 11 2.5.2 TCP Connection Establishment 13 2.5.3 TCP Connection Release 13 2.6 Use of GRE. 13 2.6.1 GRE Attributes . 16 2.6.1.1 Short Data Indicator 16 2.6.1.2 Flow Control Indication 16 2.6.1.3 IP Flow Discrimin
23、ator 17 2.6.1.4 Segmentation Indication . 18 2.6.2 Relationship of GRE tunnel to Quality of Service 18 2.6.3 GRE Protocol Usage for VoIP SOs 19 2.7 Use of RTP . 19 2.8 Use of SUA. 19 2.9 Base Station Application Part. 19 2.9.1 The BS Management Application Part . 20 2.9.2 The Direct Transfer Applica
24、tion Part . 20 2.10 Use of SCTP. 20 3.0 Interface Specific Protocol Requirements 23 3.1 A1, A2, and A5 Interfaces 23 3.1.1 Signaling Connection Transport Protocol Options . 23 3.1.2 User Traffic Connection Transport Protocol Options. 24 3.1.3 Use of ANSI SS7 Transport (Layer 2) 24 3.1.3.1 Field of A
25、pplication 25 3.1.3.2 Message Transfer Part 25 3.1.3.2.1 General. 25 3.1.3.2.2 Level 1 (Chapter 2 of 21) 25 3.1.3.2.3 Level 2 (Chapter 3 of 21) 26 i TIA-2001.2-E-1 3.1.3.2.4 Level 3 (Chapter 4 of 21) 26 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 3
26、6 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 3.1.3.2.5 Testing and Maintenance (Chapter 7 of 21) 29 3.1.3.2.6 Interface Functions 29 3.1.3.2.7 Overload Control (Message Throughput Congestion). 29 3.1.3.3 SCCP Transport Layer Specification (SCCP Functions) 29 3.1.3.3.1 Overview 29 3.
27、1.3.3.2 Primitives (Chapter 1 of 22) 30 3.1.3.3.3 SCCP Messages (Chapter 2 of 22) 30 3.1.3.3.4 SCCP Formats and Codes (Chapter 3 of 22). 32 3.1.3.3.5 SCCP Procedures (Chapter 4 of 22) 32 3.1.3.4 Use of the SCCP . 34 3.1.3.4.1 Connection Establishment . 34 3.1.3.4.1.1 Establishment Procedure - Case 1
28、. 34 3.1.3.4.1.2 Establishment Procedure - Case 2. 36 3.1.3.4.2 Connection Release 39 3.1.3.4.3 Abnormal SCCP Release . 40 3.1.3.4.3.1 SCCP Release by BS: Loss of SCCP Connection Information. 40 3.1.3.4.3.2 SCCP Release by MSC: Loss of SCCP Connection Information . 41 3.1.3.4.4 SCCP Reference Genera
29、tion Philosophy. 41 3.1.3.4.5 SCCP Transfer of DTAP and BSMAP Messages 42 3.2 A1p and A2p Interfaces 46 3.2.1 Performance Specifications 46 3.2.2 A1p Transport Protocol 46 3.2.2.1 Physical Layer (L1) Specification for A1p. 46 3.2.2.2 Layer 2 Specification for A1p 46 3.2.2.3 Use of IP for A1p 46 3.2.
30、2.4 QoS Specifications for A1p 47 3.2.2.5 Security Specifications for A1p 47 3.2.2.6 Use of the SUA for A1p . 47 3.2.2.6.1 SUA Connection Establishment. 47 3.2.2.6.1.1 Establishment Procedure - Case 1. 48 3.2.2.6.1.2 Establishment Procedure - Case 2. 49 3.2.2.6.2 Connection Release 50 3.2.2.6.3 Abno
31、rmal SUA Release. 51 3.2.2.6.3.1 SUA Release by BS: Loss of SUA Connection Information 51 3.2.2.6.3.2 SUA Release by MSCe: Loss of SUA Connection Information. 52 3.2.2.6.4 SUA Transfer of DTAP and BSMAP Messages 52 3.2.2.7 Base Station Application Part on A1p 56 3.2.2.8 Use of SCTP .56 3.2.3 A2p Use
32、r Traffic Transport Protocol 56 3.2.3.1 Physical Layer (L1) Specification for A2p. 59 3.2.3.2 Layer 2 Specification for A2p 59 3.2.3.3 Use of IP for A2p 59 3.2.3.4 QoS Specifications for A2p 59 3.2.3.5 Security Specifications for A2p 60 3.3 A3 and A7 Interfaces 60 3.3.1 Performance Specifications 60
33、 3.3.1.1 Performance Specification for IP Protocol Stacks 61 3.3.2 A3 User Traffic Transport Requirements . 61 3.3.2.1 ATM-Based User Traffic Transport . 62 3.3.2.1.1 Physical Layer (L1) Specification 62 3.3.2.1.2 Use of ATM. 62 3.3.2.1.3 Use of AAL2 62 3.3.2.2 IP-Based User Traffic Transport. 62 3.
34、3.2.2.1 Physical Layer (L1) Specification 62 3.3.2.2.2 Layer 2 Specification . 62 ii TIA-2001.2-E-1 3.3.2.2.3 Use of IP 63 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 3.3.2.2.4 QoS Specifications. 63 3.3.2.2.5 Security Specifications. 63 3.3.3 A3/A7 Signaling Transport Requirem
35、ents 63 3.3.3.1 ATM-Based Signaling Protocol Stack 64 3.3.3.1.1 Use of Physical Layer 64 3.3.3.1.2 Use of ATM. 64 3.3.3.1.3 Use of AAL5 64 3.3.3.1.4 Use of IP 64 3.3.3.1.5 Use of TCP 65 3.3.3.2 IP-Based Signaling Protocol Stack . 65 3.3.3.2.1 Use of Physical Layer 65 3.3.3.2.2 Layer 2 Specification
36、. 65 3.3.3.2.3 Use of IP 65 3.3.3.2.4 QoS Specifications. 66 3.3.3.2.5 Security Specifications. 66 3.3.3.2.6 Use of SCTP 66 3.4 A8 and A9 Interfaces 66 3.4.1 Use of TCP . 67 3.4.2 Use of UDP. 67 3.4.3 Use of GRE. 68 3.5 A10 and A11 Interface . 68 3.5.1 Use of UDP. 69 3.5.2 Use of GRE. 69 iii TIA-200
37、1.2-E-1 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 Figure 2-1 Transport Network Reference Model . 7 Figure 2.5.1-1 Delimiting Messages in an IOS Application TCP Byte Stream 12 Figure 2.6-1 GRE Encapsulate
38、d User Traffic 14 Figure 2.6-2 3GPP2 GRE Frame. 14 Figure 2.6-3 Attribute Format . 15 Figure 2.9-1 A1 or A1p Interface Signaling Protocol Reference Model. 20 Figure 3.1.1-1 A1 Signaling Protocol Stack. 24 Figure 3.1.2-1 A2 User Traffic Protocol Stacks. 24 Figure 3.1.2-2 A5 User Traffic Protocol Stac
39、ks. 24 Figure 3.1.3.4.1.1-1 SCCP Connection Establishment 35 Figure 3.1.3.4.1.1-2 SCCP Connection Establishment Refusal. 35 Figure 3.1.3.4.1.2-1 SCCP Connection Establishment with a Handoff Request message in an SCCP Connection Request message 36 Figure 3.1.3.4.1.2-2 SCCP Connection Refusal During H
40、andoff 37 Figure 3.1.3.4.1.2-3 SCCP Connection Establishment with a Handoff Request message in an SCCP DT1 message. 37 Figure 3.1.3.4.1.2-4 SCCP Connection with Handoff Failure via DT1. 38 Figure 3.1.3.4.1.2-5 SCCP Connection Refused reply to a null SCCP Connection Request 39 Figure 3.1.3.4.3.1-1 BS
41、 Initiated SCCP Release: BS Lost SCCP Connection Information 40 Figure 3.1.3.4.3.2-1 MSC Initiated SCCP Release: MSC Lost SCCP Connection Information . 41 Figure 3.1.3.4.4-1 SLR/DLR Usage 42 Figure 3.2.2-1 A1p Signaling Protocol Stack. 46 Figure 3.2.2.6.1.1-1 SUA Connection Establishment 48 Figure 3
42、.2.2.6.1-2 SUA Connection Establishment Refusal . 49 Figure 3.2.2.6.1.2-1 SUA Connection Establishment During Handoff . 50 Figure 3.2.2.6.1.2-2 SUA Connection Refusal During Handoff 50 Figure 3.2.2.6.3.1-1 BS Initiated SUA Release: BS Lost SUA Connection Information 51 Figure 3.2.2.6.3.2-1 MSCe Init
43、iated SUA Release: MSCe Lost SUA Connection Information . 52 Figure 3.2.3-1 Protocol stack for EVRC and SMV 57 Figure 3.2.3-2 Protocol stack for PCM (G.711) . 57 Figure 3.2.3-3 Protocol Stack for 13k 58 Figure 3.2.3-4 Protocol Stack for DTMF . 58 Figure 3.2.3-5 Protocol Stack for EVRC-B 58 Figure 3.
44、2.3-6 Protocol Stack for EVRC-WB 59 Figure 3.2.3-7 Protocol Stack for EVRC-NW 59 Figure 3.3.2-1 A3 User Traffic Protocol Stack. 61 Figure 3.3.3-1 A3 and A7 Signaling Protocol Stack 64 Figure 3.4-1 A9 Signaling Protocol Stack. 67 Figure 3.4-2 A8 User Traffic Protocol Stack. 67 Figure 3.5-1 A11 Signal
45、ing Protocol Stack. 69 Figure 3.5-2 A10 User Traffic Protocol Stack. 69 iv TIA-2001.2-E-1 List of Tables 1 2 3 4 5 6 7 8 9 Table 3.1.3.4.5-1 Use of the User Data Field in SCCP Frames . 42 Table 3.1.3.4.5-2 Use of SCCP for BSMAP and DTAP Messages . 43 Table 3.2.2.6.4-1 Use of the User Data Field in S
46、UA Frames . 53 Table 3.2.2.6.4-2 Use of SUA for BSMAP and DTAP Messages . 53 Table 3.3.1-1 Delay Budget Requirements . 60 Table 3.3.1.1-1 A3/A7 Mapping Between Traffic Classes and Service-Level QoS . 61 v TIA-2001.2-E-1 vi 1 2 3 4 5 (This page intentionally left blank.) TIA-2001.2-E-1 1.0 Introducti
47、on 1 2 1.1 Overview 3 4 5 This document contains the protocol definitions and transport requirements for the interfaces defined in this specification. 1.1.1 Purpose 6 7 8 9 10 The purpose of this document is to describe the transport protocols and protocol stacks used on the interfaces, which make u
48、p the logical network model, and to indicate any unique aspects of these protocols that are relevant to the Interoperability Specification (IOS). 1.1.2 Scope 11 12 13 14 15 16 17 This document contains generic and specific requirements for the IOS interfaces. The document contains the generic protoc
49、ol descriptions that are used through all of the IOS interfaces. In addition, protocol stack and transport network requirements for each IOS interface are contained in this document. Details of the IOS application and signaling layer messages are contained in the respective interface documents 14, 15, 16, and 17. 1.2 References 18 19 20 21 22 References are either normative or informative. A normative reference is used to include another document as a mandatory part of a 3rd Generation Partnership Project 2 (3GPP2) specification. Documents that provide additional
