ITU-T Y 2807-2009 MPLS-based mobility capabilities in NGN (Study Group 13)《在下一代网络(NGN)中 基于多协议标签交换(MPLS)的移动性能力 13号研究组》.pdf

《ITU-T Y 2807-2009 MPLS-based mobility capabilities in NGN (Study Group 13)《在下一代网络(NGN)中 基于多协议标签交换(MPLS)的移动性能力 13号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 2807-2009 MPLS-based mobility capabilities in NGN (Study Group 13)《在下一代网络(NGN)中 基于多协议标签交换(MPLS)的移动性能力 13号研究组》.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Y.2807TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2009) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Generalized mobility MPLS-based mobility capabilities in NGN Recom

2、mendation ITU-T Y.2807 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.

3、400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource manageme

4、nt Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y

5、.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network contr

6、ol architectures and protocols Y.2500Y.2599 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2807 (01/2009) i Recommendation ITU-T Y.2807 MPLS-based mobility capabilities in NGN Summary Recommendation ITU-T Y

7、.2807 describes MPLS-based mobility capabilities in an NGN environment where the MPLS technology is deployed in the NGN core IP network. The MPLS-based mobility capabilities seek to provide QoS-enabled mobility support in NGN. This Recommendation identifies service requirements, functional requireme

8、nts, functional architecture and mobility scenarios for support of QoS-enabled terminal mobility in NGN using MPLS-based capabilities. Source Recommendation ITU-T Y.2807 was approved on 23 January 2009 by ITU-T Study Group 13 (2009-2012) under Recommendation ITU-T A.8 procedures. Keywords Handover,

9、MMCF, MPLS, NGN, QoS, terminal mobility. ii Rec. ITU-T Y.2807 (01/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization S

10、ector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets ev

11、ery four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purvi

12、ew, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is volun

13、tary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the

14、negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve t

15、he use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommend

16、ation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at htt

17、p:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2807 (01/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Term

18、s defined in this Recommendation. 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Requirements for MPLS-based mobility capabilities. 4 6.1 Service requirements 4 6.2 Functional requirements . 4 7 Functional architecture for support of MPLS-based mobility capabilities. 5 7.1 Network environment. 5

19、 7.2 Functional architecture . 7 8 Mobility scenarios using MPLS-based mobility capabilities . 9 8.1 Case of intra-AN mobility 9 8.2 Case of inter-AN mobility 10 8.3 Case of inter-CN mobility 10 9 Security considerations. 10 Appendix I Functional procedures using MPLS-based mobility capabilities. 11

20、 I.1 Location registration. 11 I.2 Service registration. 11 I.3 Handover 12 Appendix II Information flows using MPLS-based mobility capabilities 15 II.1 Location registration. 15 II.2 Location update 17 II.3 Location query/response for user data transmission 20 Bibliography. 24 iv Rec. ITU-T Y.2807

21、(01/2009) Introduction In NGN, it is expected that a variety of the existing and new wired/wireless access network technologies are supported, such as WLAN, xDSL and 2G/3G mobile technologies, etc. Various services ranging from real-time multimedia services to data transfer services to a fixed or a

22、mobile user are expected to be supported by the NGN, and such services may be provided with different QoS commitment levels, i.e., from best-effort up to more stringent QoS levels. Multiprotocol label switching (MPLS) is a key transport technology in NGN. Deployment of the MPLS technology in the NGN

23、 core IP network can provide significant assurance in the delivery of the desired QoS for a variety of services and applications. Given the objective of fixed-mobile convergence in NGN, this Recommendation describes the MPLS-based capabilities required to provide QoS-enabled terminal mobility in NGN

24、. This includes the support of terminal mobility across different fixed and mobile networks as well as in different mobility scenarios including intra-access network, inter-access network and inter-core network scenarios. Rec. ITU-T Y.2807 (01/2009) 1 Recommendation ITU-T Y.2807 MPLS-based mobility

25、capabilities in NGN 1 Scope The objective of this Recommendation is to describe the MPLS-based capabilities required to provide QoS-enabled terminal mobility in NGN. More specifically, this Recommendation identifies service requirements, functional requirements, functional architecture and mobility

26、scenarios for support of QoS-enabled terminal mobility in NGN using MPLS-based capabilities. This Recommendation builds on general mobility management functionalities described in ITU-T Q.1707 for support of the NGN mobility related requirements described in b-ITU-T Y.2201. 2 References The followin

27、g ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommen

28、dation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not giv

29、e it, as a stand-alone document, the status of a Recommendation. ITU-T Q.1706 Recommendation ITU-T Q.1706/Y.2801 (2006), Mobility management requirements for NGN. ITU-T Q.1707 Recommendation ITU-T Q.1707/Y.2804 (2008), Generic framework of mobility management for next generation networks. ITU-T Y.15

30、41 Recommendation ITU-T Y.1541 (2006), Network performance objectives for IP-based services. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2006), Resource and admission control functions in Ne

31、xt Generation Networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 access network ITU-T Q.1707: A network that is characterized by a specific wired/wireless access technology. 3.1.2 core network ITU-T Q.1707: An architectural term

32、related to the part of an NGN network, which is independent of a specific access technology. 3.1.3 handover ITU-T Q.1706: The ability to provide services with some impact on their service level agreements to a moving object during and after movement. 3.1.4 mobility ITU-T Q.1706: The ability for the

33、user or other mobile entities to communicate and access services irrespective of changes of the location or technical environment. 2 Rec. ITU-T Y.2807 (01/2009) 3.1.5 mobility management ITU-T Q.1706: The set of functions used to provide mobility. These functions include authentication, authorizatio

34、n, location updating, paging, download of user information and more. 3.1.6 session b-ITU-T Y.2091: A temporary telecommunications relationship among a group of objects in the service stratum that are assigned to collectively fulfil a task for a period of time. A session has a state that may change d

35、uring its lifetime. Session-based telecommunications may, but need not be, assisted by intermediaries. Session-based telecommunications can be one-to-one, one-to-many, many-to-one, or many-to-many. 3.1.7 terminal mobility ITU-T Q.1706: This is the mobility for those scenarios where the same terminal

36、 equipment is moving or is used at different locations. The ability of a terminal to access telecommunication services from different locations and while in motion, and the capability of the network to identify and locate that terminal. 3.2 Terms defined in this Recommendation This Recommendation de

37、fines the following term: 3.2.1 end user : The actual user of the products or services. NOTE The end user consumes the product or service. Further, an end user may or may not be responsible for concluding contracts for the services subscribed to and for paying for these services (i.e., an end user m

38、ay or may not be a subscriber). 3.2.2 roaming: This is the ability of the users to access services according their user profile while moving outside of their subscribed home network, i.e., by using an access point of a visited network. This requires the ability of the user to get access in the visit

39、ed network, the existence of an interface between home network and visited network, as well as a roaming agreement between the respective network operators. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: 2G 2nd Generation 3G 3rd Generation A-HCF Acces

40、s Handover Control Function A-LMF Access Location Management Function A-MMCF Access Mobility Management Control Function AN Access Network A-RACF Access Resource and Admission Control Function C-HCF Central Handover Control Function C-LMF Central Location Management Function C-MMCF Central Mobility

41、Management Control Function CN Core Network C-RACF Core Resource and Admission Control Function CUE Correspondent User Equipment FTTH Fibre-To-The Home GMA Global Mobility Agent Rec. ITU-T Y.2807 (01/2009) 3 HCF Handover Control Function HDSF Handover Decision Sub-Function ID Identifier IP Internet

42、Protocol IS Information Server L2 Layer 2 LER Label Edge Router LID Location Identifier LMA Local Mobility Agent LMF Location Management Function LSP Label Switched Path LSR Label Switching Router MM Mobility Management MMCF Mobility Management Control Function MPLS Multiprotocol Label Switching MSC

43、S Mobile Service Control System NACF Network Attachment Control Function NGN Next Generation Networks P-CSC-FE Proxy Call Session Control Functional Entity PoA Point of Attachment QoS Quality of Service RACF Resource and Admission Control Function RAN Radio Access Network S-CSC-FE Serving Call Sessi

44、on Control Functional Entity SCF Service Control Function TCF Transport Control Function TF Transport Function UE User Equipment UID User Identifier WLAN Wireless Local Area Network W-LAN/MAN Wireless Local Area Network/Metropolitan Area Network xDSL x Digital Subscriber Line 5 Conventions In this R

45、ecommendation: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. 4 Rec. ITU-T Y.2807 (01/2009) The keywords “is recommended“ indicate a requirement which is recommended

46、 but which is not absolutely required. Thus, this requirement need not be present to claim conformance. The keywords “can optionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementa

47、tion must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. The terms “terminal“ and “UE“ are used interchangeably in this Recommend

48、ation. 6 Requirements for MPLS-based mobility capabilities 6.1 Service requirements This clause identifies the service requirements for the MPLS-based mobility capabilities in NGN. The MPLS-based mobility capabilities are required to: Support terminal mobility ITU-T Q.1706 in order to allow the UE t

49、o maintain its ongoing services while moving around. NOTE 1 Mobility in NGN may impact the QoS delivered to the UE by NGN provisioning, since the various access networks connected to an NGN core may differ with respect to the QoS level they can provide to the UE. Therefore, NGN may be required to support QoS adaptation mechanisms. Support the IP QoS classes and associated performance requirements specified in ITU-T Y.1541. NOTE 2 ITU-T Y.1541 recommends the selection of the specific QoS classes based on the applic