TIA-835-D-2011 cdma2000 Wireless IP Network Standard《Cdma2000无线IP网络标准》.pdf

1、 TIA-835-D September 2011cdma2000 Wireless IP Network Standard NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assi

2、sting 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 or selling products not conforming to such Standards a

3、nd 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 American National Standards Institute (ANSI) patent policy. By

4、 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 use or all applicable regulatory requirements. It is the

5、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-4732-RV4, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Docum

6、ent 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 this Document may involve the use of intellectual property rig

7、hts (“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 TIAs attention, a statement from the holder thereof is reque

8、sted, 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 licensing terms or conditions, which are instead left to the pa

9、rties 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 complied with as respects the Document or its contents. If the

10、 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, recommendation or otherwise), whether such reference consists of man

11、datory, 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 letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragemen

12、t 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 not constitute identification to TIA of a claim of Essential

13、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 compliance with the contents of the Document. ALL WARRANTIES,

14、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 OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSL

15、Y 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 CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMEN

16、T 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 INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING

17、 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 DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELE

18、MENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-835.1-D Content i Content 1 1 INTRODUCTION. 3 2 2 GLOSSARY AND DEFINITION. 5 3 2.1 ACRONYMS . 5 4 2.2 DEFINITIONS 7 5 3 REFERENCES 15 6 3.1 NORMATIVE REFERENCES . 15 7 3.1.1 IETF. 1

19、5 8 3.1.2 3GPP2 AND TIA 18 9 3.1.3 ITU-T. 19 10 3.2 INFORMATIVE REFERENCES. 19 11 3.2.1 3GPP2 AND TIA 19 12 4 PROTOCOL REFERENCE MODELS. 20 13 4.1 NETWORK REFERENCE MODELS 20 14 4.2 SIMPLE IP 21 15 4.3 MIP4. 22 16 4.4 MIP6. 26 17 4.5 RADIUS . 28 18 19 TIA-835.1-D List of Figures ii List of Figures 1

20、 Figure 1 - Reference Model for Simple IP Access with Fast Handoff. 20 2 Figure 2 - Reference Model for MIP Access with Fast Handoff 21 3 Figure 3 - Protocol Reference Model for Simple IP Access 22 4 Figure 4 - Protocol Reference Model for Simple IP Access During Fast Handoff 22 5 Figure 5 - Protoco

21、l Reference Model for MIP4 Control and IKE . 23 6 Figure 6 - Protocol Reference Model for MIP4 User Data 23 7 Figure 7 - Protocol Reference Model for MIP4 Control and IKE During Fast Handoff 24 8 Figure 8 - Protocol Reference Model for MIP4 User Data During Fast Handoff. 24 9 Figure 9 - Protocol Ref

22、erence Model for Signaling for Fast Handoff 25 10 Figure 10 - Protocol Reference Model for User Data for Fast Handoff. 25 11 Figure 11- Protocol Reference Model for MIP6 Control 26 12 Figure 12- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling. 26 13 Figure 13- Protocol Refe

23、rence Model for MIP6 User Data in RO mode. 27 14 Figure 14- Protocol Reference Model for MIP6 Control during Fast Handoff . 27 15 Figure 15- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling during 16 Fast Handoff. 28 17 Figure 16- Protocol Reference Model for MIP6 User Data

24、in RO mode during Fast Handoff 28 18 Figure 17 - RADIUS Protocol Reference Model 29 19 20 TIA-835.1-D List of Tables iii List of Tables 1 Table 1- Revision History 2 2 3 TIA-835.1-D Revision History 1 Revision History: 1 Revision Date Comments December 2000 Initial Publication Revision A May 2001 Ad

25、ded specification or clarification for the following items: New mechanism for PDSN/HA pre-shared secret distribution for IKE Security status is replaced by IKE Pre-shared Secret Request attribute New counters G15 and G16 for MIP signaling Clarifications with respect to counters G1 and G2 A new indic

26、ator in RADIUS stop message to indicate session still in progress (to avoid release of the IP address) Removal of RADIUS accounting fields H1, I2, and I3 New accounting session to be created when F1, F2 accounting fields vary Non-zero and zero IP address in IP Configuration option in IPCP is treated

27、 as Simple IP by PDSN. MIP is supported with null IP address configuration option (i.e., not included). The Active Time attribute format changed from standard RADIUS encoding to 3GPP2 specific encoding. Revision B September 2002 This document has been revised to support the following features: Simul

28、taneous multiple service instances concept introduced. RTP/UDP/IP Header Reduction Schemes Differentiated Services QoS Policy Fast handoff for data call (i.e., tunneled PPP between PDSNs) Dynamic Home Agent allocation with RADIUS Optional support for DNS server address auto configuration in MS Alway

29、s On support IP Reachability Service with dynamic DNS update Simple IPv6 Remote address based accounting Revision C August 2003 New format: the document is split into 6 chapters identified by YYYYY.xxx-C, where YYYY is the document number and xxx is the chapter number. Multiple Service Instance supp

30、ort LLAROHC Header Compression and LLA Header Removal Enhanced CRTP as an additional compression scheme Dynamic flow mapping/treatment PrePaid Packet Data service (phase 1) PDSN/HA Resource management Accounting support for 1xEVDV Packet Data Inactivity Timer IKE/IPsec clarifications IP Reachability

31、 enhancements Enhancements to Always On Enhancements to Simple IPv6 Revision B September This is an addendum to correct errors and omissions in the Revision TIA-835.1-D Revision History 2 Version 2.0 2004 B Version 1.0 of this document. Revision D 2006 IPv6 Mobility Support for end-to-end QoS (MS-PD

32、SN QoS signaling) Hot-lining MS-PDSN Version/Capabilities Indication Short Data Burst Indication Support RAN-PDSN Flow control Support DHCPv4 and DHCPv6 IP Reachability for MIPv6 Auxiliary Service Connection SO67 support. Table 1- Revision History1 TIA-835.1-D 1. Introduction 3 1 Introduction 1 This

33、 document defines requirements for support of wireless packet data networking capability on 2 a third generation wireless system based on cdma20001. This document supports the services 3 and architecture in 1. 4 This document defines the two methods for accessing public networks (Internet) and priva

34、te 5 networks (intranets): Simple IP and MIP. It describes the required Quality of Service, Security, 6 Mobility Management, and Accounting capabilities needed to support both methods. IETF 7 protocols are widely employed whenever possible to minimize the number of new protocols 8 required and to ma

35、ximize the utilization of well accepted standards. 9 This document is organized into a series of related chapters, some of which address capabilities 10 common to both IP access service types: MIP and Simple IP, and others may describe 11 capabilities applicable to a specific IP access service. The

36、chapters included in this series are: 12 Chapter 1 cdma2000Wireless IP Network Standard: Introduction. 13 Chapter 2 cdma2000Wireless IP Network Standard: Simple IP and MIP Access Services. 14 Chapter 3 cdma2000Wireless IP Network Standard: Packet Data Mobility and Resource 15 Management. 16 Chapter

37、4 cdma2000Wireless IP Network Standard: Quality of Service and Header 17 Reduction. 18 Chapter 5 cdma2000Wireless IP Network Standard: Accounting Services and 3GPP2 19 RADIUS VSAs. 20 Chapter 6 cdma2000Wireless IP Network Standard: PrePaid Packet Data Service. 21 In this set of documents we refer to

38、 other documents in the set strictly by their chapter numbers 22 as in Chapter 1. 23 Chapter 1 This chapter presents an overview of the document content, and contains the 24 complete glossary and definitions applicable to all the chapters. It describes the 25 network and protocol reference models fo

39、r the wireless IP Network entities: 26 PDSN, HA and RADIUS server. 27 Chapter 2 This chapter describes the basic IP access services: Simple IPv4/IPv6, MIP6 and 28 MIP4 with Dynamic Home Agent, and Home IP address Assignment. It also 29 addresses the security requirements between the Wireless IP Netw

40、ork nodes: 30 PDSN, HA and RADIUS servers. The chapter includes other capabilities such as 31 Always On, multiple simultaneous MIP4/IPv6 and Simple IPv4/IPv6 packet data 32 session, IP Reachability Service, DHCP support and Hot-Lining. 33 Chapter 3 This chapter describes packet data intra-PDSN, inte

41、r-PDSN handoff as well as 34 inter-PDSN fast handoff capabilities and the RAN requirements. The chapter 35 includes mechanisms for PDSN and HA resource management and provisioning 36 1cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizatio

42、nal Partners (OPs) of 3GPP2. When applied to goods and services, the cdma2000 mark certifies their compliance with cdma2000 standards. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.

43、 TIA-835.1-D 1. Introduction 4 of dormancy timers in the RAN. This chapter also includes support for RAN-1 PDSN Flow Control and Short Data Burst indication. 2 Chapter 4 This chapter describes user Differentiated services capability, multiple service 3 connections, flow mapping and treatment, and MS

44、-PDSN QoS signaling. The 4 chapter also includes a detailed description of Link Layer Assisted Robust 5 Header compression and Header Removal treatment to support Voice over IP 6 Service over an auxiliary service connection. In addition, this chapter adds 7 Auxiliary Service Connection SO67 support

45、that allows for the efficient transport 8 of IP packets from the PDSN to the RAN without HDLC-like framing and PPP 9 encapsulation. 10 Chapter 5 This chapter describes source IP address and remote IP address based 11 accounting and detailed procedures required for this series of standards. It also 1

46、2 includes a description of the 3GPP2 RADIUS VSAs required to support this 13 series of standards. 14 Chapter 6 This chapter describes the PrePaid Packet Data Service for the Wireless IP 15 Network users and includes the PrePaid service architecture, the detailed 16 procedures and the requirements o

47、n the Wireless IP Network elements. 17 18 “Shall” and “shall not” identify requirements to be followed strictly to conform to this document 19 and from which no deviation is permitted. “Should” and “should not” indicate that one of several 20 possibilities is recommended as particularly suitable, wi

48、thout mentioning or excluding others, that 21 a certain course of action is preferred but not necessarily required, or that (in the negative form) a 22 certain possibility or course of action is discouraged but not prohibited. “May” and “need not” 23 indicate a course of action permissible within th

49、e limits of the document. “Can” and “cannot” are 24 used for statements of possibility and capability, whether material, physical or causal. 25 .26 TIA-835.1-D 2. Glossary and Definitions 5 2 Glossary and Definition 1 2.1 Acronyms 2 A10 RAN-PDSN Interface 3 AAA Authentication, Authorization, and Accounting 4 ACCM Asynchronous Control Character Map 5 AH Authentication Header 6 AVP Attribute Value Pair 7 BA Binding Acknowledgement 8 BU Binding Update 9 BCE Binding Cache Entry 10 BCMCS Broadcas