1、 TIA DOCUMENT Link Layer Assisted Service Options for Voice-over-IP: Header Removal (SO 60) and Robust Header Compression (SO 61) TIA-923 MAY 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of NOTICE TIA Engineering Standa
2、rds and Publications are designed 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 the
3、ir particular need. The existence of such Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non-TIA members, either d
4、omestically or internationally. TIA DOCUMENTS TIA Documents contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural par
5、t of the development of a American National Standard (ANS). Further details of the development process are available in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm TIA Documents shall be reviewed on a five year cycle by the formulating Committe
6、e and a decision made on whether to reaffirm, revise, withdraw, or proceed to develop an American National Standard on this subject. Suggestions for revision should be directed to: Standards that a 9 certain course of action is preferred but not necessarily required; or that (in the negative 10 form
7、) a certain possibility or course of action is discouraged but not prohibited. “May” 11 and “need not” indicate a course of action permissible within the limits of the standard. 12 “Can” and “cannot” are used for statements of possibility and capability, whether 13 material, physical, or causal. 14
8、4. Footnotes appear at various points in this specification to elaborate and further clarify 15 items discussed in the body of the specification. 16 5. Unless indicated otherwise, this document presents numbers in decimal form. 17 6. Binary numbers are distinguished in the text by the use of single
9、quotation marks. In 18 some tables, binary values may appear without single quotation marks if table notation 19 clearly specifies that values are binary. The character x is used to represent a binary 20 bit of unspecified value. For example xxx00010 represents any 8-bit binary value such 21 that th
10、e least significant five bits equal 00010. Hexadecimal numbers (base 16) are 22 distinguished in the text by use of the form 0xhh where hh represents a string of 23 hexadecimal digits. For example, 0x2fa1 represents a number whose binary value is 24 10111110100001 and whose decimal value is 913. Not
11、e that the exact number of bits 25 in the binary representation of a hexadecimal number strictly depends on the 26 implementation requirements for the variable being represented. 27 7. All integers are in network byte order (big-endian). Specifically, the figures in this 28 document provide a multi-
12、octet numeric representation where the most significant octet 29 appears first. The most significant bit in any octet occupies bit position 0. 30 8. cdma2000 is a registered trademark of the Telecommunications Industry Association 31 (TIA-USA). 32 TIA-923 1-1 1 INTRODUCTION 1 1.1 Overview 2 These te
13、chnical requirements form a standard for the Link-Layer Assisted (LLA) Service 3 Options. Service Option 60 (SO60) defines a variable rate Voice-over-IP (VoIP) service option for 4 transport of header-removed IP/UDP/RTP packets carrying speech frames. Service Option 61 5 (SO61) defines a variable ra
14、te Voice-over-IP (VoIP) service option for transport of header-6 compressed IP/UDP/RTP packets carrying speech frames. 7 1.2 Terms and Numeric Information 8 Base Station An entity in the Public Radio Telecommunications System, other than 9 a mobile station, used for radio telecommunications with mob
15、ile 10 stations. 11 Codec The combination of an encoder and decoder in series 12 (encoder/decoder). 13 Data block The unit of information exchanged between the multiplex sublayer and 14 a service or Upper Layer Signaling. 15 Decoder Generally, a device for the translation of a signal from a digital
16、16 representation into an analog format. For this standard, a device which 17 converts speech encoded in the format specified in this standard to 18 analog or an equivalent PCM representation. 19 Encoder Generally, a device for the translation of a signal into a digital 20 representation. For this s
17、tandard, a device which converts speech from 21 an analog or its equivalent PCM representation to the digital 22 representation described in this standard. 23 Forward Traffic One or more forward CDMA channels used to transport user 24 Channel and signaling traffic from the base station to the mobile
18、 station. 25 Fundamental A portion of a traffic channel, which includes a Forward 26 Channel Fundamental Channel and a Reverse Fundamental Channel. 27 Medium Access Entity that controls the access to and from Upper Layer 28 Control Signaling, Data Services, and Voice Services to Physical Layer29 res
19、ources. 30 Mobile Station A station in the Public Radio Telecommunications System intended to 31 be used while in motion or during halts at unspecified points. It is 32 assumed that mobile stations include portable units (e.g., hand-held 33 personal units) and units installed in vehicles. 34 Multipl
20、ex Option The ability of the multiplex sublayer and lower layers to be tailored to 35 provide special capabilities. A multiplex option defines such 36 characteristics as the frame format and rate decision rules (see also 37 Multiplex Sublayer). 38 TIA-923 1-2 Multiplex Sublayer One of the conceptual
21、 layers of the system that multiplexes and 1 demultiplexes primary traffic, secondary traffic, and signalling traffic 2 (see 3). 3 Primary Traffic Data bits from a service that has its traffic type in the Service 4 Configuration Record set to Primary. 5 Primitive An abstract, atomic implementation i
22、ndependent representation of an 6 interaction between a service user and its service provider. 7 Radio Configuration A set of Forward Traffic Channel and Reverse Traffic Channel 8 transmission formats that are characterized by physical layer 9 parameters such as transmission rates, modulation charac
23、teristics, 10 and spreading rate. 11 Reverse Traffic One or more reverse CDMA channels on which data and signaling 12 Channel are transmitted from a mobile station to a base station. 13 Secondary Traffic Data bits from a service that has its traffic type in the Service 14 Configuration Record set to
24、 Secondary. 15 Service The set of attributes used by the mobile station and the base station 16 Configuration during Traffic Channel operation for building and interpreting 17 Record Traffic Channel frames. 18 Service Option A service capability of the system. Service options represents services 19
25、such as voice, data, or facsimile etc. 20 Service Option A particular instance or session in which the service defined by 21 Connection a service option is used. 22 Service Reference A unique number assigned to each connected or dormant 23 Identifier service option instance. 24 Signaling Traffic Con
26、trol messages that are carried between the mobile station and the 25 base station on the Traffic Channel. 26 System Time The time reference used by the system. System time is synchronous to 27 Universal Coordinate Time (except for leap seconds) and uses the same 28 time origin as GPS time. All base
27、stations use the same System Time 29 (within a small margin of error). Mobile stations use the same System 30 Time, offset by the propagation delay from the base station to the 31 mobile station. 32 Traffic Channel One or more CDMA channels on which data and signaling are 33 transmitted between a mo
28、bile station and a base station (see Forward 34 Traffic Channel and Reverse Traffic Channel). 35 For the purpose of this standard, the terms transmitting side and receiving side are used in 36 relation to the type of interaction with the multiplex sublayer. Specifically, the transmitting side 37 ref
29、ers to the HRU-HRL pair for which the HRL application is supplying data to the multiplex 38 sublayer. Similarly, the receiving side refers to the HRU-HRL pair for which the HRL application 39 is receiving data from the multiplex sublayer. 40 TIA-923 1-3 1.3 Symbols and abbreviations 1 BS Base Statio
30、n. 2 CCP Context Check Packet, defined in RFC 3242. 3 CN Correspondent Node (peer RTP endpoint). 4 CRC Cyclic Redundancy Check. 5 CSP Context Synchronization Packet, defined in RFC 3242. 6 FCH The Physical Layer Fundamental Channel. 7 GRE Generic Routing Encapsulation, defined in RFC 2784 and RFC 28
31、90. 8 HR Header size Reduction. 9 HRL Header size Reduction component in the Lower layer (in the BS and in the 10 MS). 11 HRU Header size Reduction component in the Upper layer (in the PDSN and in 12 the MS). 13 IP Internet Protocol, defined in RFC 791. 14 LLA ROHC Link-Layer Assisted ROHC profiles.
32、 There are two profiles. RFC 3242 15 defines 0-byte support for U/O-mode. RFC 3408 adds 0-byte support for 16 R-mode. 17 LSB Least Significant Bit. 18 MAC Medium Access Control. 19 MuxPDU Multiplex Sublayer Protocol Data Unit. One or more data blocks combined 20 according to multiplex option rules.
33、21 MS Mobile Station. 22 MSB Most significant bit. 23 NHP No Header Packet, defined in RFC 3242. 24 PCF Packet Control Function. 25 PDSN Packet Data Serving Node. 26 PDU Protocol Data Unit. An atomic set of data, header information, and control 27 information that is provided by a service user to a
34、service provider. 28 RC Radio Configuration. 29 ROHC RObust Header Compression, defined in RFC 3095. 30 ROHC RTP ROHC RTP is the IP/UDP/RTP profile 1 defined in RFC 3095. 31 TIA-923 1-4 RRP ROHC RTP Packet, defined in RFC 3095. 1 RTP Real-time Transport Protocol, defined in RFC 1889. 2 SDU Service D
35、ata Unit. 3 SR_ID Service Reference Identifier. A number used to identify a specific service 4 instance. 5 UDP User Datagram Protocol defined in RFC 768. 6 1.4 References 7 The following standards and 3GPP2 specifications contain provisions that, through reference in 8 this text, constitute provisio
36、ns to this document. At the time of publication, the editions 9 indicated were valid. All referenced publications are subject to revision, and parties to 10 agreements based on this document are encouraged to investigate the possibility of applying 11 the most recent editions of the works indicated
37、below. ANSI and TIA maintain registers of 12 currently valid national standards published by them. 13 3GPP2 Specifications and SDO Standards 1. 3GPP2: C.S0001-0 v3.0 ARIB: CWTS: TIA: TIA/EIA/IS-2000.1-2 TTA: TTC: Introduction to cdma2000Standards for Spread Spectrum Systems Addendum 2 2. 3GPP2: C.S0
38、002-0 v3.0 ARIB: CWTS: TIA: TIA/EIA/IS-2000.2-2 TTA: TTC: Physical Layer Standard for cdma2000Spread Spectrum Systems Addendum 2 3. 3GPP2: C.S0003-0 v3.0 ARIB: CWTS: TIA: TIA/EIA/IS-2000.3-2 TTA: TTC: Medium Access Control (MAC) for cdma2000Spread Spectrum Systems Addendum 2 4. 3GPP2: C.S0004-0 v3.0
39、 ARIB: CWTS: TIA: TIA/EIA/IS-2000.4-2 TTA: TTC: Signaling Link Access Control (LAC) for cdma2000Spread Spectrum Systems Addendum 2 5. 3GPP2: C.S0005-0 v3.0 ARIB: CWTS: TIA: TIA/EIA/IS-2000.5-2 TTA: TTC: Upper Layer (Layer 3) Signaling for cdma2000Spread Spectrum Systems Addendum 2 TIA-923 1-5 6. 3GP
40、P2: C.S0006-0 v3.0 ARIB: CWTS: TIA: TIA/EIA/IS-2000.6-2 TTA: TTC: Analog Signaling Standard for cdma2000Spread Spectrum Systems Addendum 2 7. 3GPP2: A.S0011-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.1-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Network Interfaces Part 1 Overvie
41、w 8. 3GPP2: A.S0012-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.2-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Network Interfaces Part 2 Transport 9. 3GPP2: A.S0013-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.3-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Networ
42、k Interfaces Part 3 Features 10. 3GPP2: A.S0014-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.4-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Network Interfaces Part 4 (A1, A2, and A5 Interfaces) 11. 3GPP2: A.S0015-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.5-B TTA: TTC: Interoperabilit
43、y Specification (IOS) for cdma2000Access Network Interfaces Part 5 (A3 and A7 Interfaces) 12. 3GPP2: A.S0016-0 v2.0 ARIB: CWTS: TIA: TIA/EIA/IS-2001.6-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Network Interfaces Part 6 (A8 and A9 Interfaces) 13. 3GPP2: A.S0017-0 v2.0 ARIB:
44、CWTS: TIA: TIA/EIA/IS-2001.7-B TTA: TTC: Interoperability Specification (IOS) for cdma2000Access Network Interfaces Part 7 (A10 and A11 Interfaces) TIA-923 1-6 IETF Standards 14. RFC 768, User Datagram Protocol, August 1980 15. RFC 791, Internet Protocol, September 1981. 16. RFC 1889, A Transport Pr
45、otocol for Real Time Applications, January 1996 17. RFC 2784, Generic Routing Encapsulation (GRE), March 2000 18. RFC 2890, Key and Sequence Number Extensions to GRE, September 2000 19. RFC 3095, RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP and uncompressed, July 2001
46、 20. RFC 3242, RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP, April 2002 21. RFC 3243, Requirements and Assumptions for ROHC 0-byte IP/UDP/RTP compression, April 2002 22. RFC 3408, Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assi
47、sted RObust Header Compression (ROHC) Profile, December 2002 cdma2000is a registered trademark of the Telecommunications Industry Association 1 (TIA-USA). 2 3 TIA-923 2-1 2 LINK-LAYER ASSISTED SERVICE OPTIONS 1 2.1 General Description 2 The LLA service options each provide one-way or two-way voice c
48、ommunications by providing 3 for transport of header-removed (SO60) or header-compressed (SO61) IP/UDP/RTP packets 4 between the base station and the mobile station. The base station will connect the service 5 option to a Packet Control Function (PCF) and from there to a Packet Data Serving Node 6 (
49、PDSN), where header compression or header removal takes place. The service options are 7 designed for the transport of voice application data between a mobile station and some 8 correspondent node on the IP network, and they each require the use of an associated packet 9 data service option (SO33) instance connected to the same PDSN. This specification outlines 10 procedures for initializing the LLA service options and the interface to the multiplex sublayer; 11 the actual header compression or header removal procedures are outside the sc
