1、 TIA-1137.100 November 2011Basic IP Service for Converged Access Network Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improveme
2、nt 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 member or non-member of TIA from manufacturing or selling products not confor
3、ming 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 adopted by TIA in accordance with the American National Standards Institute
4、(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 all safety problems associated with its use or all applicable regulatory
5、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, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no
6、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 process. The use or practice of contents of this Document may involve the use of i
7、ntellectual 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 patent applications are claimed and called to TIAs attention, a statement from the
8、 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 neither be a party to discussions of any licensing terms or conditions, which ar
9、e 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 suggested or provided in the Manual have been complied with as respects the Document
10、 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 designated as a standard, specification, recommendation or otherwise), whether such r
11、eference 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 for IPR or letters of assurance relating to any such Normative Reference; (ii) TIA
12、s 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 records or publications of the other SSO shall not constitute identification to TIA
13、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 products, designs or services or any claims of compliance with the contents of the Do
14、cument. 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, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPE
15、RTY 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 REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE RE
16、FERRED 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, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUE
17、NTIAL 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 POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMA
18、GES 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 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 5
19、1 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 References5 3 Access Authentication and Authorization6 3.1 Protocol Stack6 3.2 Authentication Method and Key
20、 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 8 3.4.1 RADIUS 9 3.4.2 Diameter 10 3.5 AGW Requirements.10 3.5.1 RADIUS 10 3.5.2 Diameter 13 3.6 HAAA Requirements.15 3.6.1 RADIUS 15 3.6.2 Diameter 16 4
21、 RAN Proxy Mobile IPv4 Tunnel Operation.17 4.1 Protocol Stack17 4.2 PMIP Key Management.18 4.3 eBS/SRNC Behavior19 4.4 AGW Requirements.19 4.4.1 Single PMIP Binding.20 4.4.2 Multiple PMIP Binding .20 4.4.3 Signaling-Only PMIP Binding 21 4.4.4 Data Notification .21 4.5 Binding Type Extension CVSE .23
22、 4.6 GRE Tunnel Endpoint Extension CVSE .23 4.7 Data Notification NVSE 24 4.8 Data Notification Timer NVSE24 5 ERP Operation .25 5.1 Protocol Stack25 5.2 AT Requirements.26 X.S0054-100-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
23、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 26 5.4 AGW Requirements.26 5.4.1 RADIUS 26 5.4.2 Diameter 28 5.5 HAAA Requirements.30 5.5.1 RADIUS 30 5.5.2 Diameter 30 5.6 RAN PMIP4 Tunnel Operation31 6 Simple IPv4 Operation .32 6.1 Protocol Stack 32 6.2
24、 AGW Requirements.32 6.2.1 IP Address Assignment32 6.2.2 IP Address Release 33 6.2.3 DHCPv4 Support.33 6.2.4 Ingress Address Filtering.33 6.3 AT Requirements .33 6.3.1 IP Address Assignment34 6.3.2 IP Address Release 34 6.3.3 DHCPv4 Support.34 7 Simple IPv6 Operation .35 7.1 Protocol Stack 35 7.2 Co
25、mmon Service Specification35 7.3 AGW Requirements.35 7.3.1 IP Address Assignment36 7.3.2 IP Address Release 36 7.3.3 Stateless DHCPv6 Support 36 7.3.4 Ingress Address Filtering.36 7.4 AT Requirements .36 7.4.1 IP Address Assignment37 7.4.2 IP Address Release 37 7.4.3 Stateless DHCPv6 Support 37 8 Se
26、ssion Management38 8.1 HAAA Requirements.38 8.1.1 RADIUS 38 8.1.2 Diameter 38 8.2 AGW Requirements.39 8.2.1 RADIUS 39 8.2.2 Diameter 39 9 LinkID Format40 10 Call Flows 41 10.1 Access Authentication and Authorization41 10.1.1 Access Authentication and Authorization with R-UIM/CSIM43 X.S0054-100-0 v1.
27、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 PMIP Tunnel Operation.46 10.3 PMIP Tunnel Operation with Multiple Binding 48 10.3.1 PMIP Tunnel Operation for
28、Initial Power Up48 10.3.2 PMIP Tunnel Operation for Subsequent Route Adding or Connection Setup (Scenario 1) .49 10.3.3 PMIP Tunnel Operation for Subsequent Route Adding or Connection Setup (Scenario 2) .51 10.3.4 PMIP Tunnel RL Deregistration53 10.3.5 Signaling Only PMIP-Registration for Multiple P
29、MIP Binding Case.54 10.3.6 Signaling Only PMIP-Registration for Single PMIP binding case55 10.3.7 Signaling Only PMIP Deregistration.57 10.4 MSK Derivations .58 10.5 Re-authentication Protocol (ERP)59 10.5.1 ERP Procedure.60 10.5.2 Key Hierarchy for Access Authentication .61 10.5.3 PMIP Key Hierarch
30、y for PMIP between SRNC/eBS and AGW.62 10.6 Simple IPv4 Address Assignment62 10.6.1 Simple IPv4 Addressing with DHCP Rapid Commit Option 62 10.6.2 Simple IPv4 Addressing using DHCP.63 10.7 Simple IPv6 .65 10.8 Simple IP Address Release Procedure .66 10.8.1 Simple IPv4 Address Release Procedure.66 10
31、.8.2 Simple IPv6 Address Release Procedure.67 X.S0054-100-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 List of Figures iv LIST OF FIGURES Figure 1. EAP-AAA Protocol St
32、ack for RADIUS . 6 Figure 2. EAP-AAA Protocol Stack for Diameter . 7 Figure 3. Protocol Stack for PMIP Data Path. 17 Figure 4. Protocol Stack for PMIP Signaling Path. 18 Figure 5. Binding Type Extension CVSE 23 Figure 6. GRE Tunnel Endpoint Extension CVSE. 23 Figure 7. Data Notification Extension NV
33、SE 24 Figure 8. Data Notification Extension NVSE 24 Figure 9. Protocol Stack for ERP Operation with RADIUS. 25 Figure 10. Protocol Stack for ERP Operation with Diameter. 26 Figure 11. Control and User Plane Protocol Stack for Simple IPv4 Operation 32 Figure 12. Control and User Plane Protocol Stack
34、for Simple IPv6 Operation 35 Figure 13. LinkID Format 40 Figure 14. Initial Access Authentication and Authorization 41 Figure 15. Initial Access Authentication and Authorization with R-UIM/CSIM. 44 Figure 16. PMIP Tunnel Operation (without multiple bindings) . 46 Figure 17. PMIP Tunnel Operation wit
35、h multiple bindings (Initial Power Up) . 48 Figure 18. PMIP Tunnel Operation with Connection Setup or Route Adding (Scenario 1). 50 Figure 19. PMIP Tunnel Operation with Connection Setup or Route Adding (Scenario 2). 52 Figure 20. RL PMIP Deregistration . 53 Figure 21. Signaling Only PMIP Registrati
36、on 54 Figure 22. Signaling Only PMIP Registration for Single PMIP binding case 56 Figure 23. PMIP Deregistration . 57 Figure 24. MSK Derivations 58 Figure 25. ERP Procedure 60 Figure 26. Key Hierarchy for Access Authentication 61 Figure 27. PMIP Key Hierarchy for the PMIP between AN and AGW. 62 Figu
37、re 28. Simple IPv4 Addressing using DHCP Rapid Commit Option 63 Figure 29. Simple IPv4 Addressing using DHCP 64 Figure 30. Simple IPv6 Address Assignment. 65 Figure 31. IP Address Release upon Timer Expiration 66 Figure 32. IP Address Release before Timer Expiration 67 Figure 33. IPv6 Address Releas
38、e upon Timer Expiration 67 Figure 34. IPv6 Address Release before Timer Expiration 68 X.S0054-100-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 v List of TablesLIST OF
39、TABLES Table 1. Occurrence of RADIUS Attributes between SRNC and AGW for Access Authentication and Authorization .11 Table 2. Occurrence of RADIUS Attributes between AGW and AAA for Access Authentication and Authorization .12 Table 3. Occurrence of Diameter AVPs between SRNC and AGW for Access Authe
40、ntication and Authorization .13 Table 4. Occurrence of Diameter AVPs between AGW and AAA for Access Authentication and Authorization .14 Table 5. Additional RADIUS Attributes between AGW and AAA for Access Authentication and Authorization used for ERP.27 Table 6. Additional RADIUS Attributes between
41、 AGW and SRNC for Access Authentication and Authorization used for ERP.27 Table 7. RADIUS Attributes between eBS and AGW for ERP.28 Table 8. Additional Diameter AVPs between AGW and AAA during Access Authentication and Authorization using ERP .29 Table 9. Additional Diameter AVPs between AGW and SRN
42、C during Access Authentication and Authorization using ERP .29 Table 10. Diameter AVPs between eBS and AGW for ERP .30 Table 11. RADIUS Messages used for Session Management between HAAA and AGW .38 Table 12. Diameter Command used for Session Management between HAAA and AGW 39 X.S0054-100-0 v1.0 1 2
43、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 Revision History vi REVISION HISTORY Revision Date Remarks 0 December 2007 Initial release X.S0054-100-0 v1.0 1 2 3 4 5 6 7 8 9 10 11
44、 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 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
45、 document is part of a multi-part document consisting of multiple parts that together describes Converged 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
46、version number as follows: X.S0054-100-X version n.0 where: X an uppercase numerical or alphabetic character 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” identi
47、fy 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 particularly suitable, without mentioning or excluding others, that a certain course of action is prefe
48、rred 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 permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and
49、 capability, whether material, physical or causal. This page is left blank intentionally. X.S0054-100-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 1.1 Scope 1 1 Introduction1 Introduction This document defines the stage-2 and stage-3 requirements for Simple IP access to the Converged Access Network supporting Ultra Mobile BroadbandTM(UMBTM)1Wireless access. 1.1 Scope This document is part of a multi-part document. The multi-part documen
