《TIA-835.2-C-2-2008.pdf》由会员分享，可在线阅读，更多相关《TIA-835.2-C-2-2008.pdf（54页珍藏版）》请在三一文库上搜索。
1、 TIA STANDARD cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services TIA-835.2-C-2 E (Addendum to TIA-835-C) May 2008 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance Copyright Telecommunicati
2、ons Industry Association Provided by IHS under license with EIALicensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- NOTICE TIA Engineering Standards and Publications are designed to serve the public interest throu
3、gh 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 existence of such Standards and Publications
4、 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-TIA members, either domestically or internat
5、ionally. 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 parties adopting the Standard or Publication.
6、 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 applicability of regulatory limitations be
7、fore its use. (From Project No. 3-4732.2-RV3-AD2, 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 Document may be amended, modified or changed in t
8、he 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 search or investigation for IPR. When IPR cons
9、isting 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 obligation to investigate or inquire into, the scope o
10、r 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 non-discriminatory. TIA does not warrant or r
11、epresent 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 SSO”) engaged in the formulation, development
12、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 disclaims any duty or obligation to search or
13、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 pending patent applications shall apply; and (iii)
14、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 contents of the Document. TIA does not certify, i
15、nspect, 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 ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRI
16、ATENESS 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 WARRANTIES REGARDING THE CONTENTS COMPLIANCE WI
17、TH 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. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=B
18、oeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- 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 AN
19、Y 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 CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBIL
20、ITY 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 LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/591
21、0770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E i Content 1 GLOSSARY AND DEFINITIONS 2 2 REFERENCES 3 3 SIMPLE IP OPERATION 4 3.1 COMMON SERVICE SPECIFICATION 4 3.1.1 PPP SESSION 4 3.2 PDSN REQUIREMENTS 4 3.2.1 PPP
22、 SESSION 4 3.2.2 RADIUS SUPPORT. 9 3.2.3 INGRESS ADDRESS FILTERING 10 3.3 RADIUS SERVER REQUIREMENTS. 11 3.4 MS REQUIREMENTS. 12 3.4.1 PPP SESSION 12 4 MOBILE IPV4 OPERATION 15 4.1 COMMON SERVICE SPECIFICATION 15 4.1.1 PPP SESSION 15 4.1.2 MOBILE IP 15 4.1.3 DYNAMIC HOME AGENT AND HOME ADDRESS ASSIG
23、NMENT 15 4.1.4 DYNAMIC HOME AGENT AND HOME ADDRESS ASSIGNMENT 16 4.1.5 HA REQUIREMENTS FOR GRE TUNNELING SUPPORT. 16 4.1.6 MN REQUIREMENTS FOR GRE TUNNELING SUPPORT 17 4.1.7 GRE CVSE AND TUNNELING PROCEDURES. 17 4.2 PDSN REQUIREMENTS 18 4.2.1 PPP SESSION 18 4.2.2 MIP REGISTRATION 19 4.2.3 RADIUS SUP
24、PORT. 21 4.2.4 IP SECURITY SUPPORT 22 4.2.5 INGRESS ADDRESS FILTERING 23 4.3 HOME AGENT REQUIREMENTS. 24 4.3.1 MULTIPLE REGISTRATIONS. 24 4.3.2 MIP AUTHENTICATION SUPPORT. 24 4.3.3 IPSEC SUPPORT 25 4.3.4 DYNAMIC HOME AGENT ASSIGNMENT. 26 4.3.5 DNS ADDRESS ASSIGNMENT 26 4.4 RADIUS SERVER REQUIREMENTS
25、. 26 4.4.1 DYNAMIC HOME AGENT ASSIGNMENT. 27 4.4.2 MN-HA SHARED KEY DISTRIBUTION 27 4.4.3 IKE PRE-SHARED SECRET DISTRIBUTION PROCEDURE. 27 4.4.4 DNS ADDRESS ASSIGNMENT 28 4.5 MS REQUIREMENTS. 28 4.5.1 PPP SESSION 28 4.5.2 MIP REGISTRATION 29 4.6 DNS SERVER IP ADDRESS NVSE 31 5 SIMULTANEOUS SERVICES
26、32 6 IP REACHABILITY SERVICE 33 6.1 SIMPLE IPV4 OPERATION 33 6.2 MOBILE IP OPERATION. 33 6.2.1 DNS UPDATE BY THE HOME RADIUS SERVER. 34 6.2.2 DNS UPDATE BY THE HA. 34 6.3 SIMPLE IPV6 OPERATION 35 Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing
27、Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E ii ANNEX A: IKE/ISAKMP PAYLOADS (NORMATIVE) 36 ANNEX B: CERTIFICATES (NORMATIVE). 39 ANNEX C: PDSN TIMERS (NORMATIVE) 41 Copyright Telecommunications Industry A
28、ssociation Provided by IHS under license with EIALicensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E iii Figures Figure 1 - Max PPP Inactivity Timer Packet 8 Figure 2- NVSE for DNS server IP addre
29、ss 31 Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E iv Tables Table 1 - Occurrence of RADIUS Attribute
30、s for Simple IP 10 Table 2 - Home Agent and Home Address Scenarios 15 Table 3 - Description of Scenarios 16 Table 4 - Occurrence of RADIUS Attributes for Mobile IP. 27 Table 5 - MS Registration Scenarios. 30 Copyright Telecommunications Industry Association Provided by IHS under license with EIALice
31、nsee=Boeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E 1 General Description This Chapter describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Si
32、mple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the users assigned IP address as described in the IP Reachability Service capability. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/59
33、10770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E 2 1 Glossary and Definitions 1 See X.S0011-001-C. 2 Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/591077
34、0001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E 2. References 3 2 References 1 See X.S0011-001-C. 2 Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/5910770001
35、 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E 4 3 Simple IP Operation 1 This section describes the requirements and procedures for Simple IP operation for both IPv4 2 RFC 791 and IPv6 RFC 2460. In this document, Simple
36、IP refers to a service in which an MS is 3 assigned an IP address and is provided IP routing service by an access provider network. The 4 MS retains its IP address as long as a radio networkRadio Access Network (RAN) that has 5 connectivity to the same Serving PDSN serves it. IP address mobility bey
37、ond the Serving PDSN 6 and secure access to a home network are beyond the scope of this document. 7 3.1 Common Service Specification 8 The common requirements for several network elements (e.g., PDSN and MS) for Simple IP 9 operation are described here. 10 3.1.1 PPP Session 11 PPP shall be the data
38、link protocol between the MS and the PDSN. The PPP session shall be 12 established prior to any IP datagram being exchanged between the MS and the PDSN. Only one 13 PPP session shall be supported between the MS and the PDSN. 14 PPP shall be supported as defined in the following standards with any li
39、mitations or extensions 15 described in this document. 16 Point to Point Protocol RFC 1661; 17 PPP in HDLC-like Framing RFC 1662; 18 IPCP RFC 1332 (for IPv4); 19 IPv6CP RFC 2472 (for IPv6); 20 CHAP RFC 1994; 21 PAP RFC 1334. 22 PPP encryption is not supported in this document. 23 3.2 PDSN Requiremen
40、ts 24 The PDSN shall support Simple IP operation for both IPv4 and IPv6. 25 3.2.1 PPP Session 26 3.2.1.1 Establishment 27 If the PDSN supports multiple service instances, refer to X.S0011-004-C for details of PPP 28 negotiation, otherwise, when an R-PA10 connection of SO type 33/59 is established it
41、 shall send 29 an LCP Configure-Request for a new PPP session to the MS. 30 PPP shall support transparency in accordance with Section 4.2 of RFC 1662. The PDSN shall 31 attempt to negotiate a control character mapping with the minimum number of escaped 32 characters by proposing an ACCM of 0x0000000
42、0. 33 3.2.1.2 Termination 34 The PDSN shall close the PPP session if there is no established R-PA10 or P-P session for the 35 MS. If the PPP session timer is used and has expired, or if Always On service is not enabled and 36 the PPP inactivity timer for a PPP session expires, the PDSN shall close t
43、he PPP session. The 37 PDSN may receive the Always On attribute with value 1 from the Home RADIUS server in order 38 to activate the Always On service for a user. If the PDSN receives the Always On attribute with 39 value 1, it shall send the indicator to the RNRAN as indicated in 4. 40 Copyright Te
44、lecommunications Industry Association Provided by IHS under license with EIALicensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 02:42:11 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-835.2-C-2 E 5 Upon receiving the Always On attribute with value 1 from the Home
45、RADIUS server the PDSN 1 shall utilize the expiration of the PPP inactivity timer and the procedures described in Section 2 3.2.1.8 to determine if the PPP session should be closed. 3 When the PDSN determines that the PPP session shall be closed, it shall determine if an LCP 4 Terminate-Request shou
46、ld be sent to the MS. For an Always On session, the PDSN shall send 5 an LCP Terminate-Request to the MS. The PDSN should also send LCP Terminate-Request to a 6 non-Always On session unless it has previously received the All Dormant Indicator NVSE. 7 The PDSN shall clear the R-PA10 and/or P-P sessio
47、n whenever the associated PPP session is 8 closed. If the PDSN receives IP packet(s) for an MS for which there is no established PPP 9 session, the PDSN shall silently discard the packet(s). The PDSN shall close the R-PA10 and 10 associated P-P session if it receives an LCP Terminate-Request message
48、 from the MS. 11 3.2.1.3 PPP Session Authentication 12 The PDSN shall support the two authentication mechanisms: CHAP and PAP. The PDSN shall 13 also support a configuration option to allow an MS to receive Simple IP service without CHAP or 14 PAP. The PDSN shall propose CHAP in an initial LCP Configure-Request message that the 15 P