TIA-1160-A-2012 Network PMIP Support.pdf

1、 TIA-1160-A August 2012Network PMIP Support 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 assisting the purchaser

2、 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 and Publications. Ne

3、ither 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 such action, TIA d

4、oes 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 responsibility of t

5、he 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. TIA-PN-1160-A, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be appr

6、oved 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 rights (“IPR”), inc

7、luding 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 requested, all in acc

8、ordance 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 parties involved,

9、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 Document contai

10、ns 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 mandatory, alternat

11、e 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 encouragement of voluntary d

12、isclosure (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 Patent(s) or pub

13、lished 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, EXPRESS OR IMPLI

14、ED, 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 EXPRESSLY DISCLAIMS ANY

15、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 DOCUMENT OR PRODUCED OR

16、 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 DAMAGES FOR LOS

17、S 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 ELEMENT OF THE USE

18、OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. X.S0061-A v1.0 Revision History Revision Description of Changes Date Rev 0 v1.0 Publication December 2008 Rev A v1.0 Publication version of Revision A, version 1.0 August 2012 X.S0061-A v1.0 1 2 3 4 5

19、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 56 57 58 59 i Network PMIP Support Contents Network PMIP Support . i Contents . i List of Figures .iii List of Tables . iv Foreword v 1 Introduction 1 1.1

20、 Scope 1 1.2 Document Convention . 1 1.3 References 1 1.3.1 Normative References 1 1.3.2 Informative References 3 2 Definitions, Symbols and Abbreviations 4 2.1 Definitions . 4 2.2 Symbols and Abbreviations . 4 3 PMIPv4 Operation . 6 3.1 Protocol Stack 6 3.2 PDSN Requirements 9 3.2.1 Authentication

21、and Authorization Support for PMIP Service 9 3.2.2 IP Address Assignment 9 3.2.3 PMIP4 Tunnel Management 10 3.2.4 Ingress Address Filtering . 13 3.3 HA Requirements 13 3.3.1 IP Address Assignment with PMIP4 13 3.3.2 IP Address/HN Prefix Release with PMIP4 . 14 3.3.3 PMIP4 Tunnel Management 14 3.4 AT

22、 Requirements . 15 3.5 VAAA Requirements . 15 3.5.1 RADIUS . 15 3.6 HAAA Requirements . 17 3.6.1 Network PMIP4 Key Management 17 3.6.2 RADIUS . 17 4 PMIPv6 Operation . 22 4.1 Protocol Stack 22 4.2 PDSN Requirements 25 4.2.1 Authentication and Authorization Support for PMIP6 Service 25 X.S0061-A v1.0

23、 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 56 57 58 59 ii 4.2.2 IP Address Assignment 25 4.2.3 PMIP6 Tunnel Management 27 4.2.4 Ingress Address Filtering . 29 4.3 LMA Requirements 29 4.3

24、.1 IP Address Assignment with PMIP6 29 4.3.2 IP Address/HN Prefix Release with PMIP6 . 30 4.3.3 Authentication Protocol Support 30 4.4 AT Requirements . 31 4.5 VAAA Requirements . 31 4.6 HAAA Requirements . 33 4.6.1 Network PMIP6 Key Management 33 4.6.2 RADIUS . 33 5 Call Flows 37 5.1 Address Assign

25、ment: Simple IPv4 with PMIPv4 37 5.2 Address Assignment: Simple IPv6 with PMIP4 39 5.3 Address Assignment: Simple IPv4 with PMIP6 41 5.4 Address Assignment: Simple IPv6 with PMIP6 43 6 Network PMIP RADIUS Attributes . 45 6.1 PMIP-Based-Mobility-Capability 46 6.2 PMIP-HA-Info-IPv4-Service . 47 6.3 PM

26、IP-HA-Info-IPv6-Service . 49 6.4 PMIP-Multiple-HA-LMA-Capability 51 6.5 PMIP-Supplementary-HA-Info-IPv4-Service 52 6.6 PMIP-Supplementary-HA-Info-IPv6-Service 54 X.S0061-A v1.0 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

27、45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 iii LIST OF FIGURES Figure 1 Control Plane Protocol Stack for Simple IPv4/v6 over PMIPv4 Operation . 6 Figure 2 PPP free (HDLC free) User Plane Protocol Stack for Simple IPv4 with PMIP4 Operation 7 Figure 3 PPP based (HDLC based) User Plane Protocol Stack

28、 for Simple IPv4 with PMIP4 Operation 7 Figure 4 PPP free (HDLC free) User Plane Protocol Stack for IPv6 with PMIP4 Operation 8 Figure 5 PPP based (HDLC based) User Plane Protocol Stack for IPv6 with PMIP4 Operation 8 Figure 6 Control Plane Protocol Stack for Simple IPv4/Simple IPv6 with PMIPv6 Oper

29、ation 22 Figure 7 PPP free(HDLC free) User Plane Protocol Stack for Simple IPv4 with PMIP6 Operation 23 Figure 8 PPP based (HDLC based) User Plane Protocol Stack for Simple IPv4 with PMIP6 Operation 23 Figure 9 PPP free(HDLC free) User Plane Protocol Stack for Simple IPv6 with PMIP6 Operation 24 Fig

30、ure 10 PPP based (HDLC based) User Plane Protocol Stack for Simple IPv6 with PMIP6 Operation 24 Figure 11 Simple IPv4 Address Assignment with PMIP4 37 Figure 12 Simple IPv6 Address Assignment with PMIP4 39 Figure 13 Simple IPv4 Address Assignment with PMIP6 41 Figure 14 Simple IPv6 Address Assignmen

31、t with PMIP6 43 Figure 15 Radius Attribute Format . 45 Figure 16 PMIP-Based-Mobility-Capability VSA 46 Figure 17 PMIP-HA-Info-IPv4-Service VSA . 47 Figure 18 PMIP-HA-Info-IPv6-Service VSA . 49 Figure 19 PMIP-Multiple-HA-LMA-Capability VSA 51 Figure 20 PMIP-Supplementary-HA-Info-IPv4-Service VSA 52 F

32、igure 21 PMIP-Supplementary-HA-Info-IPv6-Service VSA 54 X.S0061-A v1.0 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 56 57 58 59 iv LIST OF TABLES Table 1 Additional RADIUS Attributes exchan

33、ged between PDSN and AAA during Access Authentication and Authorization for Supporting Network PMIP for IP Services . 20 Table 2 RADIUS Attributes exchanged between HA and AAA for Supporting PMIP4 . 21 Table 3 Network PMIP Specific RADIUS VSAs 45 X.S0061-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

34、 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 56 57 58 59 v FOREWORD (This foreword is not part of this document.) This document was prepared by 3GPP2 TSG-X. This document is the first revision of this specification. This docume

35、nt is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date and an identifying change in version number as follows: X.S0061 -X version n.0 where: X an uppercase numerical or alphabetic character 0, A, B, C, that represents

36、 the revision level. n a numeric string 1, 2, 3, that indicates an point release level. X.S0061-A v1.0 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 56 57 58 59 vi This page is left blank in

37、tentionally. X.S0061-A v1.0 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 56 57 58 59 1 1 Introduction This document defines the stage-2 and stage-3 requirements for supporting PMIP between

38、PDSN and LMA/HA. This document describes PMIP based Simple IP address assignment, and PMIP tunnel management. This document applies to both 1x packet data system and HRPD system. 1.1 Scope The scope of this document covers support for PMIPv4 and PMIPv6 between PDSN and LMA/HA, called network PMIP. I

39、t includes network PMIP based Simple IP address assignment and network PMIP tunnel management. The transport between PDSN and HA/LMA may use IPv4 or IPv6. 1.2 Document Convention “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no devia

40、tion is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or

41、course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. All fields that are marked as “Reserved”

42、 shall be filled with zeros by the sender of that field, and shall be ignored by the receiver of that field. 1.3 References 1.3.1 Normative References This section provides references to other specifications and standards that are necessary to implement this document. References are either specific

43、(identified by date of publication, revision identifier, and version number) or non-specific. For a specific reference, subsequent revisions may not apply. For a non-specific reference, the latest revision applies. 1 3GPP2 C.S0024-B Version 3.0, “cdma20001High Rate Packet Data Air Interface Specific

44、ation”, June 2012. 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000is a registered trademark of the Telecommunications Industry Association (TI

45、A-USA) in the United States. X.S0061-A v1.0 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 56 57 58 59 2 2 3GPP2 A.S0008-C v4.0, “Interoperability Specification (IOS) for High Rate Packet 2 D

46、ata (HRPD) Radio Access Network Interfaces with 3 Session Control in the Access Network”, April 2012. 3 IETF: RFC 5563, Leung, et al., “WiMAX Forum / 3GPP2 Proxy Mobile IPv4”, February 2010. 4 IETF: RFC 6245, Yegani, et al., “Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4”, May 20

47、11. 5 IETF: RFC 2131, Dorms, “Dynamic Host Configuration Protocol”, March 1997. 6 IETF: RFC3046, Patrik, “DHCP Relay Agent Information Option”, January 2001. 7 IETF: RFC4039, Park, et.al., “Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)”, March 2005. 8 IETF: RFC35

48、43, Glass, et.al., “Registration Revocation in Mobile IPv4”, August 2003. 9 IETF: RFC 3775, D. Johnson, et.al., “Mobility Support in IPv6”, June 2004. 10 IETF: RFC2794, Calhoun, et.al., “Mobile IP Network Access Identifier Extension for IPv4”, March 2000. 11 IETF: RFC4862, Thomson, et. al., “IPv6 St

49、ateless Address Autoconfiguration”, September 2007. 12 IETF: RFC3041, Narten, et.al., “Privacy Extensions for Stateless Address Autoconfiguration in IPv6”, January 2001. 13 IETF: RFC4861, Narten, et.al., “Neighbor Discovery for IP Version 6 (IPv6)”, September 2007. 14 IETF: RFC3012, Parkins, et.al., “Mobile IPv4 Challenge/Response Extensions”, November 2000. 15 3GPP2: X.S0011, “cdma2000 Wireless IP Network Standard”. 16 IETF: RFC4861, Narten, et.al., “Neighbor Discovery for IP Version 6 (IPv6)”, September 2007. 17 IETF: RFC 5846, Mu