1、 International Telecommunication Union ITU-T Y.2018TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2009) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models Mobility management
2、and control framework and architecture within the NGN transport stratum Recommendation ITU-T Y.2018 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
3、 middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.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
4、Y.1100Y.1199 Architecture, access, network capabilities and resource management 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 I
5、PTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099Quality 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
6、.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Future networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 For further details, ple
7、ase refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2018 (09/2009) i Recommendation ITU-T Y.2018 Mobility management and control framework and architecture within the NGN transport stratum Summary Recommendation ITU-T Y.2018 specifies the architecture and functional requirements for the man
8、agement of logical location information, as defined in Recommendation ITU-T Q.1707 and control of mobility in the NGN transport stratum. It addresses all types of device mobility as defined in Recommendation ITU-T Q.1706. It draws heavily from Recommendations ITU-T Q.1707, ITU-T Q.1709, and ITU-T Q.
9、1708, but maps their content into the framework provided by Recommendation ITU-T Y.2012. History Edition Recommendation Approval Study Group 1.0 ITU-T Y.2018 2009-09-12 13 ii Rec. ITU-T Y.2018 (09/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency
10、 in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (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
11、 standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every 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
12、 is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness
13、to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is
14、achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the 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. INTELLEC
15、TUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, wheth
16、er asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are caution
17、ed that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU
18、. Rec. ITU-T Y.2018 (09/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 3 4.1 Functions 3 4.2 Functional entities 3 4.3 Functional blocks 4 4.4 Other . 4 5 Conventions 5 6 Archit
19、ecture model and concepts 5 6.1 General concepts 5 6.2 IP mobility management selection principles . 6 6.3 High level functions . 6 6.4 Functional entities 8 6.5 Reference points . 12 7 Procedures 23 7.1 Overview of mobility procedures . 23 7.2 Network attachment, IP configuration, and mobility loca
20、tion management 25 7.3 Handover 30 8 Security considerations . 37 8.1 Security threats . 37 8.2 Security requirements . 37 Appendix I Architecture reference model . 38 I.1 Non-roaming architecture and scenarios 38 I.2 Roaming architecture and scenarios . 39 Appendix II Mapping between functions defi
21、ned in Rec. ITU-T Y.2018 and IETF entities . 43 II.1 The IETF mobility architectures 43 Appendix III Mapping between Rec. ITU-T Y.2018 and 3GPP functions . 47 III.1 Introduction 47 III.2 References 47 III.3 Architectural scenarios . 47 III.4 Mapping from 3GPP entities to Y.2018 entities 50 Bibliogra
22、phy. 52 Rec. ITU-T Y.2018 (09/2009) 1 Recommendation ITU-T Y.2018 Mobility management and control framework and architecture within the NGN transport stratum 1 Scope This Recommendation describes an architecture of mobility management and control functions (MMCFs) for the NGN transport stratum. This
23、 architecture includes the definitions of the functional entities of MMCF and the scenarios for interactions with the other NGN functional components: NACF, RACF, SCF and the access and core transport functional blocks within the forwarding plane. This Recommendation considers the types of mobility
24、management described in ITU-T Q.1706. This version of the Recommendation is limited to mobility of a single device, as opposed to the movement of sessions from one device to another (session mobility). It is further limited, as indicated by the Recommendation title, to support of IP-based mobility i
25、n the transport stratum. In this it differs from ITU-T Q.1707 in that the latter also considers support of mobility in the service stratum. This Recommendation provides mechanisms to achieve seamless mobility if network conditions permit, but does not provide any mechanism to deal with service adapt
26、ation if the post-handover quality of service is degraded from the quality of service before handover. This Recommendation uses the term “location information“. That information is currently limited to logical location information as defined by clause 6.3.2 of ITU-T Q.1707. The management of physica
27、l (geographic) location information is for further study. This Recommendation assumes that mobility is a service, explicitly specified by parameters in the user service profile. This Recommendation makes no assumption as to whether the mobility service parameters are located in the transport user pr
28、ofile or the service user profile, but assumes that they are accessible to the functional entities that need to use them. This Recommendation is not dependent on specific access technologies, and supports handover across different technologies. 2 References The following ITU-T Recommendations and ot
29、her 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 Recommendation are therefore encourage
30、d 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 give it, as a stand-alone documen
31、t, 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 Q.1708 Recommendation ITU-T Q.170
32、8/Y.2805 (2008), Framework of location management for NGN. ITU-T Q.1709 Recommendation ITU-T Q.1709/Y.2806 (2008), Framework of handover control for NGN. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. 2 Rec. ITU-T Y.2018 (09/2009) ITU-
33、T Y.2014 Recommendation ITU-T Y.2014 (2008), Network attachment control functions in next generation networks. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2008), Resource and admission control functions in next generation networks. IETF RFC 4282 IETF RFC 4282 (2005), The Network Access Identifier. 3 D
34、efinitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 handover ITU-T Q.1706. 3.1.2 seamless handover ITU-T Q.1706. 3.1.3 service continuity ITU-T Q.1706. 3.2 Terms defined in this Recommendation NOTE For convenience, this Recommendation uses the
35、 terms “mobility“ and “mobile UE“ to imply service continuity at a minimum, with the intent to achieve seamless handover. This is explicitly contrasted with nomadicity, although the latter is included in the broader definition of ITU-T Q.1706. This Recommendation defines the following terms: 3.2.1 a
36、ccess service authorizer: A network operator that authenticates a UE and establishes the UEs authorization to receive Internet service. 3.2.2 access service provider: The operator of the access network to which the UE is attached. 3.2.3 adaptive QoS resource management: The network capability which
37、may afford dynamic QoS assurance to mobile UE according to network capability, user preference and service administration policies during handover. With this capability, the network may dynamically change the QoS resources granted to the individual flows of a session upward or downward within the ra
38、nge set by the application. 3.2.4 anchor point: A location in the forwarding plane above which movement of the terminal equipment within a certain topological scope is masked by the provision of mobility service at layer 3. “Above“ means “on the side away from the user equipment (UE)“. There may be
39、more than one anchor point on the path between the UE and a correspondent entity. 3.2.5 anchoring network: The network within which an anchor point resides. 3.2.6 candidate access point (or network): An access point or network being evaluated as a possible new point of attachment (new serving access
40、 network) after handover. 3.2.7 handover latency: A delay in delivery of user data during handover due to the use of buffering as part of the handover procedure. 3.2.8 handover quality: The degree of impairment experienced by the user during the period of handover. This can range from cut-off (loss
41、of service continuity) to a degree of impairment unnoticeable by most users. The latter condition is taken as the working definition of seamless handover. 3.2.9 host-based mobility: A mode of operation whereby the mobile UE takes an active role in the provision of mobility service at layer 3, in par
42、ticular by contacting the mobile service provider directly to invoke this service after gaining network access. Rec. ITU-T Y.2018 (09/2009) 3 3.2.10 integrated scenario: A scenario in which the same AAA infrastructure is used to authorize both transport and mobility service, so that a common set of
43、user credentials is used to gain access to both services. 3.2.11 mobility service authorizer: A network operator that authenticates a UE and establishes the UEs authorization to receive mobility service. It is assumed in the network-based case that this authorization covers the affected components b
44、oth in the anchoring network and in the access network. 3.2.12 mobility service provider: A network operator that provides mobility service. In the case of network-based mobility, this term refers specifically to the operator of the anchoring network, taking note that the access service provider is
45、actually the operator of the equipment providing the tunnel lower end. 3.2.13 network-based mobility: A mode of operation whereby the mobile UE does not take an active role in the provision of mobility service at layer 3. 3.2.14 post-handover quality of service: The quality of service experienced af
46、ter any transient conditions due to handover have passed. 3.2.15 proactive QoS reservation: Reservation of QoS resources in advance of handover. 3.2.16 serving access point (or network): The access point (or network) providing service to the UE before handover. 3.2.17 split scenario: A scenario in w
47、hich mobility service is authorized by a separate AAA infrastructure from that which authorizes transport service. Thus, in general two sets of user credentials are required to complete the authorization process. This Recommendation assumes that the credentials for mobility service are obtained from
48、 the UE during the network attachment process, but leaves the details to other Recommendations. 3.2.18 target access point (or network): An access point or network which has been selected as the intended new point of attachment (new serving access network) after handover. 3.2.19 tunnel: An IP-in-IP
49、tunnel as provided by the various varieties of mobile IP. 3.2.20 tunnel lower end: The end of the tunnel closest to the UE. 3.2.21 tunnel upper end: The end of the tunnel furthest from the UE, coinciding with the anchor point. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: 4.1 Functions HCF Handover Control Functions HDF Handover Decision Function L2HCF Layer 2 Handover Control Function L3HCF Layer 3 Handover Control Function L3HEF Layer 3 Handover Execu
