TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf

上传人:registerpick115 文档编号:1060117 上传时间:2019-03-31 格式:PDF 页数:56 大小:707.90KB
下载 相关 举报
TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf_第1页
第1页 / 共56页
TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf_第2页
第2页 / 共56页
TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf_第3页
第3页 / 共56页
TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf_第4页
第4页 / 共56页
TIA-1137 220-A-2009 Network PMIP Support《网络PMIP支持》.pdf_第5页
第5页 / 共56页
点击查看更多>>
资源描述

1、 TIA-1137.220-A-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.220-A June 2009Network PMIP Support NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating i

2、nterchangeability 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 member or non-member of TIA from manufacturing

3、 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 adopted by TIA in accordance with the America

4、n 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 all safety problems associated with its us

5、e 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.220-RV1-RF1, formulated under the cognizance o

6、f 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 process. The use or practice of contents of

7、 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 patent applications are claimed and called

8、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 neither be a party to discussions of any

9、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 suggested or provided in the Manual have been

10、 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 designated as a standard, specification, recom

11、mendation 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 for IPR or letters of assurance relating to

12、 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 records or publications of the other SSO shal

13、l 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 products, designs or services or any claims of

14、 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, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT

15、 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 REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF TH

16、E 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, INCLUDING WITHOUT LIMITATION ANY AND ALL IN

17、DIRECT, 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 POSSIBILITY OF SUCH

18、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.P0054-220-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 3

19、8 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i ContentsNetwork PMIP Support CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References3 3 Simple IPv4 with PMIP Operation.4 3.1 Protocol Stack4 3.2 AGW Requirements.5 3.2.1 Authenticati

20、on and Authorization Support for PMIP Service .6 3.2.2 IP Address Assignment .6 3.2.3 IP Address Release 6 3.2.4 PMIP4 Tunnel Management7 3.2.5 PMIP6 Tunnel Management8 3.2.6 DHCPv4 Support.9 3.2.7 Ingress Address Filtering.9 3.3 HA Requirements 9 3.3.1 IP Address Assignment with PMIP4 .9 3.3.2 IP A

21、ddress Release with PMIP49 3.3.3 PMIP4 Tunnel Management10 3.4 LMA Requirements .10 3.4.1 IP Address Assignment with PMIP6 .10 3.4.2 IP Address Release with PMIP611 3.5 AT Requirements.11 3.6 VAAA Requirements.11 3.6.1 RADIUS 11 3.7 HAAA Requirements.12 3.7.1 Network PMIP4 Key Management for simple

22、IPv4 Services .12 3.7.2 RADIUS 12 4 Simple IPv6 with PMIP Operation.15 4.1 Protocol Stack15 4.2 AGW Requirements.16 4.2.1 Authentication and Authorization Support for PMIP Service .16 4.2.2 IPv6 Address Assignment16 4.2.3 IPv6 Address Release 17 4.2.4 PMIP4 Tunnel Management17 4.2.5 PMIP6 Tunnel Man

23、agement18 4.2.6 Stateless DHCPv6 Support19 4.2.7 Ingress Address Filtering.19 4.3 HA Requirements 19 X.P0054-220-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 60 Contents

24、ii 4.3.1 IP Address Assignment with PMIP4 .19 4.3.2 IP Address Release with PMIP419 4.3.3 PMIP4 Tunnel Management20 4.4 LMA Requirements20 4.4.1 IP Address Assignment with PMIP6 .20 4.4.2 IP Address Release with PMIP621 4.5 AT Requirements .21 4.6 VAAA Requirements.21 4.6.1 RADIUS 21 4.7 HAAA Requir

25、ements.22 4.7.1 Network PMIP4 Key Management for Simple IPv6 Service 22 4.7.2 RADIUS 22 5 PMIP Based Inter-AGW Handoff 25 5.1 AGW Requirements.26 5.2 HA/LMA Requirements.26 5.3 eBS Behavior .27 5.4 SRNC Requirements27 5.5 AT Requirements .27 5.6 HAAA Requirements.27 6 Call Flows 28 6.1 Simple IPv4 w

26、ith PMIP4 Addressing using DHCP Rapid Commit Option28 6.2 Simple IPv4 with PMIPv4 Addressing using DHCP .29 6.3 Simple IPv6 with PMIP4 Call Flow.31 6.4 Simple IPv4 with PMIPv6 Call Flow.33 6.5 Simple IPv6 with PMIPv6 Call Flow.35 6.6 PMIP4 Based inter-AGW Active Handoff.36 6.7 PMIP6 Based inter-AGW

27、Active Handoff.39 X.P0054-220-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 60 iii List of FiguresLIST OF FIGURES Figure 1 Control Plane Protocol Stack for Simple IPv4 wit

28、h PMIP4 Operation 4 Figure 2 Control Plane Protocol Stack for Simple IPv4 with PMIPv6 Operation 5 Figure 3 User Plane Protocol Stack for Simple IPv4 with PMIP4/PMIP6 Operation.5 Figure 4 Control Plane Protocol Stack for Simple IPv6 with PMIP4 Operation 15 Figure 5 Control Plane Protocol Stack for Si

29、mple IPv6 with PMIPv6 Operation 15 Figure 6 User Plane Protocol Stack for Simple IPv6 with PMIP4/PMIP6 Operation.16 Figure 7 Illustration of PMIP Based Inter-AGW Active Handoff 26 Figure 8 Simple IPv4 Address Assignment using DHCPv4 Rapid Commit Option.28 Figure 9 Simple IPv4 with PMIP Address Assig

30、nment using DHCP.30 Figure 10 Simple IPv6 Address Assignment 32 Figure 11 Simple IPv4 Address Assignment using DHCPv4 Rapid Commit Option.34 Figure 12 Simple IPv6 Address Assignment 35 Figure 13 PMIP4 Based Inter-AGW Active Handoff .37 Figure 14 PMIP6 Based Inter-AGW Active Handoff .40 X.P0054-220-A

31、 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 Tables iv LIST OF TABLES Table 1 Additional RADIUS Attributes exchanged between AGW and AAA during Access Authentic

32、ation and Authorization for Supporting Network PMIP4/PMIP6 for IPv4 Services.14 Table 2 RADIUS Attributes exchanged between HA and AAA for Supporting PMIP4.14 Table 3 Additional RADIUS Attributes Exchanged between AGW and AAA during Access Authentication and Authorization for Supporting Network PMIP

33、 for IPv6 Services.24 X.P0054-220-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 60 v Revision HistoryREVISION HISTORY Revision Date Remarks 0 v1.0 December, 2007 Initial r

34、elease 0 v2.0 August, 2008 Bug fix for the initial release A v1.0 August, 2008 Revision A X.P0054-220-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 60 Foreword vi FOREWORD

35、 (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This 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 b

36、e modified, it will be re-released with a change of release date and an identifying change in version number as follows: X.S0054-220-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 poi

37、nt 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 particula

38、rly 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 permissible wi

39、thin the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. X.P0054-220-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 4

40、9 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 supporting PMIP between AGW and HA/LMA. This document describes PMIP based Simple IP address assignment and PMIP based inter-AGW handoff. 1.1 Scope This document

41、 is part of a multi-part document consisting of multiple parts that together describes Converged Access Network operation. The scope of this document covers support for PMIP between AGW and HA, called network PMIP. It includes network PMIP based Simple IP address assignment and network PMIP based in

42、ter-AGW mobility. X.P0054-220-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 60 2 References 2 2.1 Normative References2 References 2.1 Normative References This section pr

43、ovides references to other specifications and standards that are necessary to implement this document. 1 3GPP2: C.S0084-0 v2.0, “Ultra Mobile Broadband (UMB)TM 1Air Interface”, September 2007. 2 3GPP2: A.S0020-0 v1.0, “Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Acces

44、s Network Interfaces”, November 2007. 3 3GPP2: X.S0054-100-0 v2.0, “Basic IP Services for Converged Access Network Specification”, December 2007. 4 3GPP2: X.S0054-110-0 v2.0, “MIP4 Specification in Converged Access Network Specification”, December 2007. 5 3GPP2: X.S0054-210-0 v1.0, “CMIP based Inter

45、-AGW Handoff”, December 2007. 6 IETF: draft-leung-mip4-proxy-mode Editor Note: The above document is a work in progress and should not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informationa

46、l purposes only. 7 IETF: draft-yegani-gre-key-extension Editor Note: The above document is a work in progress and should not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informational purposes

47、 only. 8 IETF: draft-ietf-mip4-dsmipv4 Editor Note: The above document is a work in progress and should not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informational purposes only. 9 IETF: RF

48、C 2131, Dorms, “Dynamic Host Configuration Protocol”, March 1997. 10 IETF: RFC3046, Patrik, “DHCP Relay Agent Information Option”, January 2001. 11 IETF: RFC4039, Park, et.al., “Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)”, March 2005. 12 IETF: RFC3543, Glass,

49、et.al., “Registration Revocation in Mobile IPv4”, August 2003. 1Ultra Mobile BraoadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). X.P0054-220-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 60 2.2 Informative References 3 2 References13 IETF: RFC 3775, D. Johnson, et.al., “Mobility Support in IPv6”, June 2004. 14 IETF: RFC2794, Calhoun, et.al., “Mobile IP Network Acces

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1