TIA-2001 2-E-2010 Interoperability Specification (IOS) for cdma2000 Access Network Interfaces C Part 2 Transport.pdf

1、 TIA-2001.2-E January 2010 Interoperability Specification (IOS) forcdma2000Access Network Interfaces Part 2 Transport NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating i

2、nterchangeability 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-member of TIA from manufacturing

3、 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 accordance with the America

4、n 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 problems associated with its us

5、e 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. PN-3-4545.2-RV5, formulated under the cognizance of t

6、he 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 use or practice of contents of th

7、is 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 applications are claimed and called to

8、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 party to discussions of any lic

9、ensing 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 provided in the Manual have been co

10、mplied 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 standard, specification, recommen

11、dation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4th edition) 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 a

12、ny 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 publications of the other SSO shall

13、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 or services or any claims of c

14、ompliance 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 MERCHANTABILITY AND ITS NONINFRINGEMENT O

15、F 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 SAFETY OR HEALTH EFFECTS OF THE

16、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 WITHOUT LIMITATION ANY AND ALL INDI

17、RECT, 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 OF THE POSSIBILITY OF SUCH DA

18、MAGES. 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 i Table of Contents 1 2 1.0 Introduction 1 3 1.1 Overview 1 4 1.1.1 Purpose . 1 5 1.1.2 Scope 1 6 1.2 Reference

19、s 1 7 1.2.1 Normative References 1 8 1.2.2 Informative References. 3 9 1.3 Terminology . 3 10 1.3.1 Acronyms 3 11 1.3.2 Definitions 6 12 2.0 General Protocol Requirements 7 13 2.1 Physical Layer (Layer 1) 7 14 2.2 Link Layer (Layer 2) 8 15 2.3 Use of ATM 9 16 2.3.1 ATM Adaptation Layer 9 17 2.3.2 Us

20、e of ATM AAL5 for Transmission of IP Datagrams 9 18 2.4 IP Transport Considerations . 9 19 2.4.1 IP Topologies 9 20 2.4.2 IP Network and Transport Specifications (Layers 3/4). 10 21 2.4.2.1 Addressing 10 22 2.4.2.2 Routing . 10 23 2.4.2.3 Flow Association 10 24 2.4.3 IP Performance Specifications 10

21、 25 2.4.4 IP Quality of Service (QoS) Framework 10 26 2.4.5 IP Security Framework Specifications 11 27 2.5 Use of TCP . 11 28 2.5.1 Message Delimiting in TCP 11 29 2.5.2 TCP Connection Establishment 13 30 2.5.3 TCP Connection Release 13 31 2.6 Use of GRE. 13 32 2.6.1 GRE Attributes . 16 33 2.6.1.1 S

22、hort Data Indicator 16 34 2.6.1.2 Flow Control Indication 16 35 2.6.1.3 IP Flow Discriminator 17 36 2.6.1.4 Segmentation Indication . 18 37 2.6.2 Relationship of GRE tunnel to Quality of Service 18 38 2.6.3 GRE Protocol Usage for VoIP SOs 19 39 2.7 Use of RTP . 19 40 2.8 Use of SUA. 19 41 2.9 Base S

23、tation Application Part. 19 42 2.9.1 The BS Management Application Part . 20 43 2.9.2 The Direct Transfer Application Part . 20 44 2.10 Use of SCTP. 20 45 3.0 Interface Specific Protocol Requirements 23 46 3.1 A1, A2, and A5 Interfaces 23 47 3.1.1 Signaling Connection Transport Protocol Options . 23

24、 48 3.1.2 User Traffic Connection Transport Protocol Options. 24 49 3.1.3 Use of ANSI SS7 Transport (Layer 2) 24 50 3.1.3.1 Field of Application 25 51 3.1.3.2 Message Transfer Part 25 52 3.1.3.2.1 General. 25 53 3.1.3.2.2 Level 1 (Chapter 2 of 21) 25 54 3.1.3.2.3 Level 2 (Chapter 3 of 21) 26 55 TIA-

25、2001.2-E ii 3.1.3.2.4 Level 3 (Chapter 4 of 21) 26 1 3.1.3.2.5 Testing and Maintenance (Chapter 7 of 21) 29 2 3.1.3.2.6 Interface Functions 29 3 3.1.3.2.7 Overload Control (Message Throughput Congestion). 29 4 3.1.3.3 SCCP Transport Layer Specification (SCCP Functions) 29 5 3.1.3.3.1 Overview 29 6 3

26、.1.3.3.2 Primitives (Chapter 1 of 22) 30 7 3.1.3.3.3 SCCP Messages (Chapter 2 of 22) 31 8 3.1.3.3.4 SCCP Formats and Codes (Chapter 3 of 22). 32 9 3.1.3.3.5 SCCP Procedures (Chapter 4 of 22) 33 10 3.1.3.4 Use of the SCCP . 34 11 3.1.3.4.1 Connection Establishment . 34 12 3.1.3.4.1.1 Establishment Pr

27、ocedure - Case 1. 35 13 3.1.3.4.1.2 Establishment Procedure - Case 2. 36 14 3.1.3.4.2 Connection Release 40 15 3.1.3.4.3 Abnormal SCCP Release . 41 16 3.1.3.4.3.1 SCCP Release by BS: Loss of SCCP Connection Information. 41 17 3.1.3.4.3.2 SCCP Release by MSC: Loss of SCCP Connection Information . 41

28、18 3.1.3.4.4 SCCP Reference Generation Philosophy. 42 19 3.1.3.4.5 SCCP Transfer of DTAP and BSMAP Messages 43 20 3.2 A1p and A2p Interfaces 47 21 3.2.1 Performance Specifications 47 22 3.2.2 A1p Transport Protocol 47 23 3.2.2.1 Physical Layer (L1) Specification for A1p. 47 24 3.2.2.2 Layer 2 Specif

29、ication for A1p 47 25 3.2.2.3 Use of IP for A1p 47 26 3.2.2.4 QoS Specifications for A1p 48 27 3.2.2.5 Security Specifications for A1p 48 28 3.2.2.6 Use of the SUA for A1p . 48 29 3.2.2.6.1 SUA Connection Establishment. 48 30 3.2.2.6.1.1 Establishment Procedure - Case 1. 49 31 3.2.2.6.1.2 Establishm

30、ent Procedure - Case 2. 50 32 3.2.2.6.2 Connection Release 51 33 3.2.2.6.3 Abnormal SUA Release. 52 34 3.2.2.6.3.1 SUA Release by BS: Loss of SUA Connection Information 52 35 3.2.2.6.3.2 SUA Release by MSCe: Loss of SUA Connection Information. 53 36 3.2.2.6.4 SUA Transfer of DTAP and BSMAP Messages

31、53 37 3.2.2.7 Base Station Application Part on A1p 57 38 3.2.2.8 Use of SCTP . 57 39 3.2.3 A2p User Traffic Transport Protocol 57 40 3.2.3.1 Physical Layer (L1) Specification for A2p. 59 41 3.2.3.2 Layer 2 Specification for A2p 59 42 3.2.3.3 Use of IP for A2p 59 43 3.2.3.4 QoS Specifications for A2p

32、 60 44 3.2.3.5 Security Specifications for A2p 60 45 3.3 A3 and A7 Interfaces 60 46 3.3.1 Performance Specifications 60 47 3.3.1.1 Performance Specification for IP Protocol Stacks 61 48 3.3.2 A3 User Traffic Transport Requirements . 61 49 3.3.2.1 ATM-Based User Traffic Transport . 62 50 3.3.2.1.1 Ph

33、ysical Layer (L1) Specification 62 51 3.3.2.1.2 Use of ATM. 62 52 3.3.2.1.3 Use of AAL2 62 53 3.3.2.2 IP-Based User Traffic Transport. 62 54 3.3.2.2.1 Physical Layer (L1) Specification 63 55 3.3.2.2.2 Layer 2 Specification . 63 56 TIA-2001.2-E iii 3.3.2.2.3 Use of IP 63 1 3.3.2.2.4 QoS Specification

34、s. 63 2 3.3.2.2.5 Security Specifications. 63 3 3.3.3 A3/A7 Signaling Transport Requirements 64 4 3.3.3.1 ATM-Based Signaling Protocol Stack 64 5 3.3.3.1.1 Use of Physical Layer 64 6 3.3.3.1.2 Use of ATM. 64 7 3.3.3.1.3 Use of AAL5 64 8 3.3.3.1.4 Use of IP 65 9 3.3.3.1.5 Use of TCP 65 10 3.3.3.2 IP-

35、Based Signaling Protocol Stack . 65 11 3.3.3.2.1 Use of Physical Layer 65 12 3.3.3.2.2 Layer 2 Specification . 65 13 3.3.3.2.3 Use of IP 65 14 3.3.3.2.4 QoS Specifications. 66 15 3.3.3.2.5 Security Specifications. 66 16 3.3.3.2.6 Use of SCTP 66 17 3.4 A8 and A9 Interfaces 66 18 3.4.1 Use of TCP . 67

36、 19 3.4.2 Use of UDP. 68 20 3.4.3 Use of GRE. 68 21 3.5 A10 and A11 Interface . 68 22 3.5.1 Use of UDP. 69 23 3.5.2 Use of GRE. 69 24 25 TIA-2001.2-E 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

37、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 Figure 3.1.1-1 A1 Signaling Protocol Stack. 24 9 Figure 3.1.2-1 A2 User Traffic Protocol Stacks. 24 10 F

38、igure 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. 36 13 Figure 3.1.3.4.1.2-1 SCCP Connection Establishment with a Handoff Request 14 message in a SCCP Connection Request message .

39、37 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 17 message in an SCCP DT1 message 38 18 Figure 3.1.3.4.1.2-4 SCCP Connection with Handoff Failure via DT1. 39 19 Figure 3.1.3.4.1.2-5 SCCP Connection Refu

40、sed reply to a null SCCP Connection Request 40 20 Figure 3.1.3.4.3.1-1 BS Initiated SCCP Release: BS Lost SCCP Connection Information 41 21 Figure 3.1.3.4.3.2-1 MSC Initiated SCCP Release: MSC Lost SCCP Connection Information . 42 22 Figure 3.1.3.4.4-1 SLR/DLR Usage 43 23 Figure 3.2.2-1 A1p Signalin

41、g Protocol Stack. 47 24 Figure 3.2.2.6.1.1-1 SUA Connection Establishment 49 25 Figure 3.2.2.6.1-2 SUA Connection Establishment Refusal . 50 26 Figure 3.2.2.6.1.2-1 SUA Connection Establishment During Handoff . 51 27 Figure 3.2.2.6.1.2-2 SUA Connection Refusal During Handoff 51 28 Figure 3.2.2.6.3.1

42、-1 BS Initiated SUA Release: BS Lost SUA Connection Information 52 29 Figure 3.2.2.6.3.2-1 MSCe Initiated SUA Release: MSCe Lost SUA Connection Information . 53 30 Figure 3.2.3-1 Protocol stack for EVRC and SMV 58 31 Figure 3.2.3-2 Protocol stack for PCM (G.711) . 58 32 Figure 3.2.3-3 Protocol Stack

43、 for 13k 58 33 Figure 3.2.3-4 Protocol Stack for DTMF . 59 34 Figure 3.2.3-5 Protocol Stack for EVRC-B 59 35 Figure 3.3.2-1 A3 User Traffic Protocol Stack. 62 36 Figure 3.3.3-1 A3 and A7 Signaling Protocol Stack 64 37 Figure 3.4-1 A9 Signaling Protocol Stack. 67 38 Figure 3.4-2 A8 User Traffic Proto

44、col Stack. 67 39 Figure 3.5-1 A11 Signaling Protocol Stack. 69 40 Figure 3.5-2 A10 User Traffic Protocol Stack. 69 41 42 TIA-2001.2-E v List of Tables 1 2 Table 3.1.3.4.5-1 Use of the User Data Field in SCCP Frames . 43 3 Table 3.1.3.4.5-2 Use of SCCP for BSMAP and DTAP Messages . 44 4 Table 3.2.2.6

45、.4-1 Use of the User Data Field in SUA Frames . 54 5 Table 3.2.2.6.4-2 Use of SUA for BSMAP and DTAP Messages . 54 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 TIA-2001.2-E vi 1 (This page intentionally left bla

46、nk.) 2 3 4 5 TIA-2001.2-E 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

47、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

48、 document contains the generic protocol descriptions that are used through all of the IOS 13 interfaces. In addition, protocol stack and transport network requirements for each IOS 14 interface are contained in this document. Details of the IOS application and signaling 15 layer messages are contain

49、ed in the respective interface documents 14, 15, 16, and 16 17. 17 1.2 References 18 19 1.2.1 Normative References 20 The following standards contain provisions which, through reference in this text, 21 constitute provisions of this standard. At the time of publication, the editions indicated 22 were valid. All standards are subject to revision, and parties to agreements based on this 23 standard are encouraged to investigate the possibility of applying the most recent editions 24 of the standards indicated below. ANSI and TIA maintain registers of currently vali