1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.2813 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Generalized mobility Mobility man
2、agement framework for applications with multiple devices Recommendation ITU-T Y.2813 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.2
3、00Y.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 Y.1100Y.1199 Ar
4、chitecture, 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 IPTV over NGN Y.
5、1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.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 En
6、hancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING
7、Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications,
8、 computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2813 (02/2016) i Recommendation ITU-T Y.2813 Mobility management framework for
9、applications with multiple devices Summary Recommendation ITU-T Y.2813 describes a mobility management framework that facilitates various seamless multimedia services using multiple devices. This Recommendation identifies the design considerations, requirements, functional architecture and informati
10、on flows for supporting various applications involving users with multiple devices. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.2813 2016-02-13 13 11.1002/1000/12710 Keywords Mobility management, multiple devices, seamless service, switchover, NGN. * To access the Reco
11、mmendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.2813 (02/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations s
12、pecialized agency 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 th
13、em with a view to 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-
14、T Recommendations 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
15、 for conciseness 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
16、Recommendation is 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 a
17、ny party. INTELLECTUAL PROPERTY RIGHTSITU 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 Prope
18、rty Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, imp
19、lementers are cautioned 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 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior writ
20、ten permission of ITU. Rec. ITU-T Y.2813 (02/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 2 5 Overview of Mobility Management (MM) for applications with multiple d
21、evices . 3 6 Requirements of MM for applications with multiple devices 6 6.1 Cooperation between MM functions and capabilities to handle multiple devices 6 6.2 Support of network-based control scheme . 7 6.3 Alignment with ITU-T Y.2018 and ITU-T Q.1707 7 6.4 Identification of user and multiple devic
22、es 7 6.5 Support of the device switchover . 7 6.6 Support for authentication and authorization of user and devices . 7 7 Functional architecture for applications with multiple devices 7 7.1 Transport stratum 7 7.2 Service stratum . 9 8 MM procedure for applications with multiple devices . 9 8.1 Proc
23、edure for registration . 9 8.2 Procedure for applications with one-to-multiple devices . 10 8.3 Procedure for applications with multiple devices-to-one . 11 8.4 Procedure for applications with multiple devices-to-multiple devices 13 9 Security considerations . 13 Appendix I Use case of application b
24、ased on MIP . 14 I.1 Use case overview 14 I.2 Deployment scenario of application with multiple devices using MIP 14 Bibliography. 17 Rec. ITU-T Y.2813 (02/2016) 1 Recommendation ITU-T Y.2813 Mobility management framework for applications with multiple devices 1 Scope The objective of this Recommenda
25、tion is to develop a mobility management (MM) framework for applications involving users with multiple devices. To enable seamless services between those users, it is required to provide the functions of location management and handover control for a set of devices sharing a communication session. T
26、his Recommendation specifies design considerations, service scenarios, requirements, functional architecture and information flows for mobility support in applications with multiple devices. 2 References The following ITU-T Recommendations and other references contain provisions which, through refer
27、ence 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 encouraged to investigate the possibility of applying the most
28、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 document, the status of a Recommendation. ITU-T Q.1706 Recomm
29、endation 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.1708/Y.2805 (2008), Framework of location management for N
30、GN. ITU-T Q.1709 Recommendation ITU-T Q.1709/Y.2806 (2008), Framework of handover control for NGN. ITU-T Y.2018 Recommendation ITU-T Y.2018 (2009), Mobility management and control framework and architecture within the NGN transport stratum. 3 Definitions 3.1 Terms defined elsewhere This Recommendati
31、on uses the following terms defined elsewhere: 3.1.1 mobility ITU-T Q.1706: The ability for the user or other mobile entities to communicate and access services irrespective of changes of the location or technical environment. 3.1.2 mobility management ITU-T Q.1706: The set of functions used to prov
32、ide mobility. These functions include authentication, authorization, location updating, paging, download of user information and more. 3.1.3 network-based mobility management ITU-T Q.1707: A mobility management scheme in which the MM signalling is performed (or controlled) by the network entities, o
33、n behalf of the UE. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 2 Rec. ITU-T Y.2813 (02/2016) 3.2.1 handover: (Definition based on ITU-T Q.1706) The ability to provide services with some impact on their service level agreements to a moving object during
34、and after movement. 3.2.2 multiple devices: A set of individual user devices operated by and connected through the user. Bundling multiple devices belonging to the user together as a virtual set has the functionality as if there is only one device rather than multiple devices. One example of the usa
35、ge using multiple devices is multi-screen environment. A user can have multiple devices such as TV, PC, mobile phone, digital album, etc. Each device belonging to the user can compose one logical set with the users. A user sometimes can have more than two sets of devices depending on the situation.
36、However, in this Recommendation, one device set per user is considered. 3.2.3 switchover: The manual switch (or change) from one device to another device that belongs to the same user, to meet the needs of that user. It is assumed that, in a handover scenario, the user can move and roam between acce
37、ss networks using one single device within the mobility management framework. However, in this Recommendation it is assumed that the user can select and change devices, from among multiple devices, in a switchover scenario. 3.2.4 applications with multiple devices: When more than two user devices ar
38、e used for a single application scenario such as one source multi use, etc. Three types of applications using multiple devices are taken in consideration in this Recommendation: One-to-multiple devices, multiple devices-to-one device and multiple devices-to-multiple devices applications. One-to-mult
39、iple devices application: It refers to application between a single entity (or sender) and a bundle of entities (or multiple receivers). Application with one source multi use is one example which consists of one content source on the sender side, and multiple devices on the receiver side. Multiple d
40、evices-to-one application: It refers to an application between a bundle of entities (or multiple senders) and a single entity (or receiver). Multiple devices-to-multiple devices application: It refers to an application between two bundles of entities comprising device sets. Both sender and receiver
41、are made up of a bundle of devices that communicate with each other. 3.2.5 activated device: A user device that is selected by the user and is currently in use for on-going application. 3.2.6 deactivated device: A user device that is neither selected nor used by the user for application. Deactivated
42、 device can become an activated device based on users selection. 3.2.7 seamless service: A service that is implemented in such way that it will ensure that users will not experience any service disruptions while changing the point of attachment or while changing devices. 4 Abbreviations and acronyms
43、 This Recommendation uses the following abbreviations and acronyms: AAA Authentication, Authorization and Accounting A-MMCF Access MMCF C-MMCF Central MMCF HCF Handover Control Function IMSI International Mobile Subscriber Identifier LMF Location Management Function MM Mobility Management Rec. ITU-T
44、 Y.2813 (02/2016) 3 MMCF Mobility Management Control Function NACF Network Attachment Control Function NAI Network Access Identifier NGN Next Generation Network OSMU One- source Multi- use RACF Resource Admission and Control Function SCF Service Control Function UE User Equipment URI Uniform Resourc
45、e Identifier URL Uniform Resource Locator Wi-Fi Wireless Fidelity 5 Overview of Mobility Management (MM) for applications with multiple devices The number of new services provided for smart devices is rapidly increasing. Connecting to the Internet with a smart phone while enjoying multimedia service
46、s on a smart TV has become common nowadays as we enter a “one person multi-devices era“. One of the most widely used communication services using multiple devices is the multi-screen service. It provides multimedia contents for various devices such as TV, PC, tablet PC and mobile phone without inter
47、ruption while switching between these devices. For example, a user can watch video with TV at home, with a smart phone in an outdoor area and with a PC in the office. Cloud computing technology which distributes and stores contents using a local server system for sharing between devices is one of th
48、e approaches to realize multi-screen service. However it is only applicable to one source with multiple receivers and is generally implemented at session layer and application layer for sharing contents. Thus the management of application sessions and corresponding information to manage multiple dev
49、ices can cause scalability problem as the number of devices increase. There are similarities between applications involving users with multiple devices and mobility service in many ways. For instance, both services handle the identification of devices, managing the location of devices and controlling data transmission to devices in cases of device switchover and device movement. Therefore a mobility management framework including location management and handover control may be used for applications wit
