1、 TIA-1137.100-1-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.100-1 June 2009MIPv4 Specification in Converged Access Network Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between man
2、ufacturers 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 shall not in any respect preclude any membe
3、r 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 internationally. Standards and Publications are adop
4、ted 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. This Standard does not purport to address a
5、ll 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 before its use. (From Project No. 3-0291.100-A
6、D1-RF1, 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 the standards development or any editing pr
7、ocess. 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 consisting of patents and published pending pa
8、tent 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 or validity of any claims of IPR. TIA will
9、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 represent that procedures or practices sugg
10、ested 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 or publication of standards (whether desig
11、nated 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 any duty or obligation to search or investigate the records of any other SSO fo
12、r 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) Information as to claims of IPR in the reco
13、rds 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, inspect, test or otherwise investigate produ
14、cts, 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 APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, IT
15、S 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 WITH ANY APPLICABLE STATUTE, RULE OR REGULATI
16、ON, 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 INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, IN
17、CLUDING 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, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EV
18、EN 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. X.S0054-100-0 v2.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
19、 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 ContentsBasic IP Services for Converged Access Network Specification CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References4 3 Access Authent
20、ication and Authorization6 3.1 Protocol Stack6 3.2 Authentication Method and Key Management 7 3.2.1 MSK Derivation 7 3.2.2 PMK Derivation 7 3.3 AT Requirements.7 3.3.1 R-UIM/CSIM Support Requirements8 3.4 SRNC/eBS Requirements 9 3.4.1 RADIUS 9 3.4.2 Diameter 10 3.5 AGW Requirements.11 3.5.1 RADIUS 1
21、1 3.5.2 Diameter 13 3.6 HAAA Requirements.15 3.6.1 RADIUS 16 3.6.2 Diameter 16 4 RAN Proxy Mobile IPv4 Tunnel Operation.18 4.1 Protocol Stack18 4.2 PMIP Key Management.19 4.3 eBS/SRNC Behavior20 4.3.1 Generic Notification 20 4.4 AGW Requirements.21 4.4.1 Single PMIP Binding.23 4.4.2 Multiple PMIP Bi
22、ndings23 4.4.3 Signaling-Only PMIP Binding 23 4.4.4 Data Notification .23 4.5 Binding Type Extension CVSE .25 4.6 GRE Tunnel Endpoint Extension CVSE .25 4.7 Data Notification NVSE 26 4.8 Data Notification Timer NVSE26 5 ERP Operation .27 5.1 Protocol Stack27 5.2 AT Requirements.28 X.S0054-100-0 v2.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 60 Contents ii 5.3 eBS Procedures 28 5.4 AGW Requirements.28 5.4.1 RADIUS 28 5.4.2 Diameter 30 5.5 HAAA Requirements.32 5.5.1 RADIU
24、S 32 5.5.2 Diameter 33 5.6 RAN PMIP4 Tunnel Operation33 6 Simple IPv4 Operation .34 6.1 Protocol Stack 34 6.2 AGW Requirements.34 6.2.1 IP Address Assignment34 6.2.2 IP Address Release 35 6.2.3 DHCPv4 Support.35 6.2.4 Ingress Address Filtering.36 6.3 AT Requirements .36 6.3.1 IP Address Assignment36
25、 6.3.2 IP Address Release 37 6.3.3 DHCPv4 Support.37 7 Simple IPv6 Operation .38 7.1 Protocol Stack 38 7.2 Common Service Specification38 7.3 AGW Requirements.38 7.3.1 IP Address Assignment39 7.3.2 IP Address Release 39 7.3.3 Stateless DHCPv6 Support 39 7.3.4 Ingress Address Filtering.39 7.4 AT Requ
26、irements .40 7.4.1 IP Address Assignment40 7.4.2 IP Address Release 40 7.4.3 Stateless DHCPv6 Support 40 8 Session Management41 8.1 HAAA Requirements.41 8.1.1 RADIUS 41 8.1.2 Diameter 41 8.2 AGW Requirements.42 8.2.1 RADIUS 42 8.2.2 Diameter 42 9 LinkID Format44 10 Call Flows 46 10.1 Access Authenti
27、cation and Authorization46 10.1.1 Access Authentication and Authorization with R-UIM/CSIM48 X.S0054-100-0 v2.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 iii Contents10.2 P
28、MIP Tunnel Operation.51 10.3 PMIP Tunnel Operation with Multiple Binding 53 10.3.1 PMIP Tunnel Operation for Initial Power Up53 10.3.2 PMIP Tunnel Operation for Subsequent Route Adding or Connection Setup (Scenario 1) .55 10.3.3 PMIP Tunnel Operation for Subsequent Route Adding or Connection Setup (
29、Scenario 2) .57 10.3.4 PMIP Tunnel RL Deregistration59 10.3.5 Signaling Only PMIP-Registration for Multiple PMIP Binding Case.60 10.3.6 Signaling Only PMIP-Registration for Single PMIP binding case61 10.3.7 Signaling Only PMIP Deregistration.63 10.4 MSK Derivations .64 10.5 Re-authentication Protoco
30、l (ERP)65 10.5.1 ERP Procedure.66 10.5.2 Key Hierarchy for Access Authentication .67 10.5.3 PMIP Key Hierarchy for PMIP between SRNC/eBS and AGW.68 10.6 Simple IPv4 Address Assignment68 10.6.1 Simple IPv4 Addressing with DHCP Rapid Commit Option 68 10.6.2 Simple IPv4 Addressing using DHCP.69 10.7 Si
31、mple IPv6 .71 10.8 Simple IP Address Release Procedure .72 10.8.1 Simple IPv4 Address Release Procedure.72 10.8.2 Simple IPv6 Address Release Procedure.73 X.S0054-100-0 v2.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
32、46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Figures iv LIST OF FIGURES Figure 1. EAP-AAA Protocol Stack for RADIUS . 6 Figure 2. EAP-AAA Protocol Stack for Diameter . 7 Figure 3. Protocol Stack for PMIP Data Path. 19 Figure 4. Protocol Stack for PMIP Signaling Path. 19 Figure 5. Binding Typ
33、e Extension CVSE 25 Figure 6. GRE Tunnel Endpoint Extension CVSE. 25 Figure 7. Data Notification Extension NVSE 26 Figure 8. Data Notification Extension NVSE 26 Figure 9. Protocol Stack for ERP Operation with RADIUS. 27 Figure 10. Protocol Stack for ERP Operation with Diameter. 28 Figure 11. Control
34、 and User Plane Protocol Stack for Simple IPv4 Operation 34 Figure 12. Control and User Plane Protocol Stack for Simple IPv6 Operation 38 Figure 13. LinkID Format 44 Figure 14. Levels of LinkID. 45 Figure 15. Initial Access Authentication and Authorization 46 Figure 16. Initial Access Authentication
35、 and Authorization with R-UIM/CSIM. 49 Figure 17. PMIP Tunnel Operation (without multiple bindings) . 51 Figure 18. PMIP Tunnel Operation with multiple bindings (Initial Power Up) . 54 Figure 19. PMIP Tunnel Operation with Connection Setup or Route Adding (Scenario 1). 56 Figure 20. PMIP Tunnel Oper
36、ation with Connection Setup or Route Adding (Scenario 2). 58 Figure 21. RL PMIP Deregistration . 59 Figure 22. Signaling Only PMIP Registration 60 Figure 23. Signaling Only PMIP Registration for Single PMIP binding case 62 Figure 24. PMIP Deregistration . 63 Figure 25. MSK Derivations 65 Figure 26.
37、ERP Procedure 66 Figure 27. Key Hierarchy for Access Authentication 67 Figure 28. PMIP Key Hierarchy for the PMIP between AN and AGW. 68 Figure 29. Simple IPv4 Addressing using DHCP Rapid Commit Option 69 Figure 30. Simple IPv4 Addressing using DHCP 70 Figure 31. Simple IPv6 Address Assignment. 71 F
38、igure 32. IP Address Release upon Timer Expiration 72 Figure 33. IP Address Release before Timer Expiration 73 Figure 34. IPv6 Address Release upon Timer Expiration 73 Figure 35. IPv6 Address Release before Timer Expiration 74 X.S0054-100-0 v2.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
39、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 v List of TablesLIST OF TABLES Table 1. Occurrence of RADIUS Attributes between SRNC and AGW for Access Authentication and Authorization.12 Table 2. Occurrence of RADIUS Attributes be
40、tween AGW and AAA for Access Authentication and Authorization.12 Table 3. Occurrence of Diameter AVPs between SRNC and AGW for Access Authentication and Authorization.14 Table 4. Occurrence of Diameter AVPs between AGW and AAA for Access Authentication and Authorization.15 Table 5. Additional RADIUS
41、 Attributes between AGW and AAA for Access Authentication and Authorization used for ERP 29 Table 6. Additional RADIUS Attributes between AGW and SRNC for Access Authentication and Authorization used for ERP 29 Table 7. RADIUS Attributes between eBS and AGW for ERP 30 Table 8. Additional Diameter AV
42、Ps between AGW and AAA during Access Authentication and Authorization using ERP.31 Table 9. Additional Diameter AVPs between AGW and SRNC during Access Authentication and Authorization using ERP.31 Table 10. Diameter AVPs between eBS and AGW for ERP.32 Table 11. RADIUS Messages used for Session Mana
43、gement between HAAA and AGW.41 Table 12. Diameter Command used for Session Management between HAAA and AGW42 X.S0054-100-0 v2.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 R
44、evision History vi REVISION HISTORY Revision Date Remarks 0 v1.0 December 2007 Initial release 0 v2.0 August 2008 Bug fix release for the initial release X.S0054-100-0 v2.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 4
45、6 47 48 49 50 51 52 53 54 55 56 57 58 59 60 vii ForewordFOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is a new specification. This document is part of a multi-part document consisting of multiple parts that together describes Converge
46、d Access Network. This document 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.S0054-100-X version n.0 where: X an uppercase numerical or alphabetic chara
47、cter 0, A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indicates an 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 permi
48、tted. “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 course of act
49、ion 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. This page is left blank intentionally. X.S0054-100-0 v2.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 1.1 Scope 1 1 Introduction1 Introduction This document defines the stage-2 and stage-3 requiremen
