1、 TIA-1116 November 2010 Mobile IPv4 Enhancements 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 purc
2、haser 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 Publication
3、s. 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 such action,
4、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 responsibility
5、 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-0262, formulated under the cognizance of the TIA TR-45 Mobile and Personal Communications Systems Standards, TR-45.8 Sub
6、committee on Core Networks- Mobile and Personal Communications Standards). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION S
7、TANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these docu
8、ments either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permis
9、sion. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (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 ma
10、y 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”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search o
11、r 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 accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to in
12、vestigate 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, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-dis
13、criminatory. 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 contains one or more Normative References to a document published by another organization (“other SSO”) en
14、gaged in the formulation, development 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, 4thedition) then (i) TIA disclaims
15、 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 disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent
16、 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 published pending patent applications. TIA does not enforce or monitor compliance with the contents of
17、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 IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF
18、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 AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES
19、 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 RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR IN
20、DIRECT, 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 LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BRE
21、ACH 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 OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3
22、GPP2 X.S0044-0 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 60 i Document Title: Mobile IPv4 Enhancements CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative Re
23、ferences2 2.2 Informative References2 3 Definitions, Symbols and Abbreviations3 3.1 Definitions .3 3.2 Symbols and Abbreviations .3 4 General Requirements and Backward Compatibility .5 5 MIP4 Key Derivation.6 5.1 MN-AAA Key and associated SPI.6 5.2 MN-HA key and associated SPI 6 6 MS Requirements.8
24、7 PDSN Requirements 9 8 AAA Requirements10 9 HA Requirements.11 10 Allocation of Home Agent in Visited Network12 10.1 Dynamic MIP4 HA Assignment in the Visited Network using RADIUS .12 11 FA-HA Mobility Security Association.14 11.1 Call Flow Example for Using RADIUS to Distribute FA-HA MSA.15 12 AAA
25、 VSAs and Version Capability Extensions 18 12.1 RADIUS VSAs18 12.1.1 MIP4-HA-Local-Assignment-Capability 18 12.1.2 HA-Realm19 12.1.3 FA-HA-MSA-Request.19 12.1.4 FA-HA-MSA.20 12.1.5 MIP4-Enhancements-Support20 12.2 Version Capability Extension 21 3GPP2 X.S0044-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
26、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 60 ii LIST OF FIGURES Figure 1 Dynamic Allocation of an HA in a Visited Network Using RADIUS Protocol .12 Figure 2 HA assignment by VAAA in Visited Network A and han
27、doff to Visited Network B if RADIUS is used to distribute FA-HA MSA16 Figure 3 MIP4-HA-Local-Assignment-Capability VSA.18 Figure 4 HA-Realm VSA19 Figure 5 FA-HA-MSA-Request VSA .19 Figure 6 FA-HA-MSA VSA .20 Figure 7 MIP4-Enhancemnts-Support VSA20 3GPP2 X.S0044-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 1
28、4 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 60 iii LIST OF TABLES Table 1 VSA Cross Reference.18 Table 2 List of PDSN Capabilities.21 3GPP2 X.S0044-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 2
29、1 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 60 iv FOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is a new specification. This document contains enhancements to X.S
30、0011-D and later versions for the ability to dynamically allocate a Mobile IPv4 Home Agent in a visited network. This document supplements the functionality as specified in X.S0011-D and later versions and supersedes those documents where indicated. The protocols used to implement this functionality
31、 are defined by several IETF RFCs as listed in the References section. This document ties together the use of those protocols in a cdma2000 network to accomplish the functionality needed to allocate a Home Agent in a visited network to an MS. This document is subject to change following formal appro
32、val. 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.S0044-X-n where: X an uppercase numerical or alphabetic character A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indica
33、tes a point release level. This document uses the following conventions: “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as
34、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 course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permi
35、ssible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. 3GPP2 X.S0044-0 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
36、 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1 1 Introduction X.S0011-D 2 describes how a Mobile IPv4 MS can request and be granted or denied the dynamic allocation of a Home Agent in its home network. This document describes the following aspects of this functionality. 1. How the MS can indicate i
37、ts willingness to accept a Home Agent in the visited network 2. How the visited network signals its willingness (or not) to allocate a Home Agent 3. How the MS users home network signals its willingness (or not) to allow visited network allocation of a Home Agent 4. How the keys needed to establish
38、a security association between the MS and visited network Home Agent are derived and distributed This document describes methods for the dynamic allocation of a Home Agent in a visited network using RADIUS 1. This document does not define Diameter based protocols. Chapter 2, section 4 of 2 specifies
39、 the use of Mobile IPv4 by an MS and the interactions/interfaces between the MS, PDSN and other elements of the access network involved in the establishment of a Mobile IPv4 session. The same method used for allocating a Home Agent in a visited network is also applicable for allocating a Home Agent
40、in an MS users home network. Implementations of Mobile IPv4 Enhancements presented in this document are expected to conform to the RFCs referenced in this document with any extensions or limitations as given in this document. 1.1 Scope This document provides additional functionality to the functiona
41、lity specified in 2 and later versions. It supports the allocation of a Home Agent in a visited network when a user is operating in a network that is not its home network. 3GPP2 X.S0044-0 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
42、 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 2 2 References 2.1 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this Specification. At the time of publication, the editions indicated were valid. All st
43、andards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. References are either specific (identified by date of publication, edition number, version number, et
44、c.) or non-specific. For a specific reference, subsequent revisions do not apply. For non-specific reference, the latest version applies. In the case of a reference to a 3GPP2 document, a non-specific reference implicitly refers to the latest version of that document in the same Release as the prese
45、nt document. 1 IETF: RFC 2865; C. Rigney, Remote Authentication Dial In User Service (RADIUS), June 2000. 2 3GPP2: X.S0011-D v2.0; cdma2000 Wireless IP Network Standard, October 2008. 3 IETF: RFC 5295: J. Salowey, et. al., Specification for the Derivation of Root Keys from an Extended Master Session
46、 Key (EMSK), August 2008. 4 National Institute of Standards and Technology: “Secure Hash Standard”, FIPS 180-2, With Change Notice 1 dated February 2004, August 2002. 5 IETF: RFC 2002; Perkins, IPv4 Mobility, May 1995. 6 3GPP2: X.S0028-200; Access to Operator Service and Mobility for WLAN Interworki
47、ng. 2.2 Informative References There is no informative reference specified in this document. 3GPP2 X.S0044-0 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 60 3 3 Definitions
48、, Symbols and Abbreviations This section contains definitions, symbols and abbreviations that are used throughout the document. 3.1 Definitions Home Network A mobile stations home network is the network owned by the operator with whom the mobile station user has a business relationship via a service
49、 subscription. Visited Network A visited network is a network with a coverage area which includes the current location of a mobile station, and that network is not the mobile stations home network. A visited network may or may not provide service to the mobile station depending on the business relationship between the users home network and the visited network, as well as the mobile stations (and its user) authentication and authorization status. Serving Network The serving network can be the home network or the v
