ITU-T Q 1708-2008 Framework of location management for NGN (Study Group 19)《下一代网络(NGN)的位置管理框架 19号研究组》.pdf

《ITU-T Q 1708-2008 Framework of location management for NGN (Study Group 19)《下一代网络(NGN)的位置管理框架 19号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1708-2008 Framework of location management for NGN (Study Group 19)《下一代网络(NGN)的位置管理框架 19号研究组》.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Q.1708/Y.2805TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2008) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for IMT-2000 SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORK

2、S Next Generation Networks Generalized mobility Framework of location management for NGN Recommendation ITU-T Q.1708/Y.2805 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIO

3、NS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No.

4、 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS

5、OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.1708/Y.2805 (10/2008) i Recommendation ITU-T Q.

6、1708/Y.2805 Framework of location management for NGN Summary Recommendation ITU-T Q.1708/Y.2805 specifies the framework of IP-based location management for next generation networks. The location management is responsible for mapping among user identifier and location identifiers of the user equipmen

7、t. This Recommendation describes the design considerations, functional architecture, and information flows for the location management function. Source Recommendation ITU-T Q.1708/Y.2805 was approved on 14 October 2008 by ITU-T Study Group 19 (2005-2008) under Recommendation ITU-T A.8 procedure. Key

8、words Location management, NGN. ii Rec. ITU-T Q.1708/Y.2805 (10/2008) 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 Sec

9、tor (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 ever

10、y 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 purview

11、, 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 volunta

12、ry. 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 n

13、egative 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 th

14、e 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 Recommenda

15、tion, 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 http

16、:/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 Q.1708/Y.2805 (10/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined in ITU-T Q.170

17、7 1 3.2 Terms defined in this Recommendation. 2 4 Abbreviations 2 5 Design considerations. 3 5.1 MM identifiers 3 5.2 LM operations 4 5.3 LM for data packet delivery . 5 6 Functional reference architecture . 5 6.1 Functional entities 5 6.2 Reference points . 6 7 Information flows for non-roaming UE

18、8 7.1 Host-based LM . 8 7.2 Network-based LM. 9 8 Information flows for roaming UE. 10 8.1 Host-based LM . 11 8.2 Network-based LM. 12 Bibliography. 13 iv Rec. ITU-T Q.1708/Y.2805 (10/2008) Introduction This Recommendation describes the framework of mobility management (MM) for next generation netwo

19、rks (NGN). This work has been motivated from the observation that NGN continues to evolve towards the convergence of fixed and wireless/mobile networks, and thus mobility management is an essential functionality needed to provide seamless mobility to NGN users and services. This Recommendation is a

20、part of the MM framework for NGN. The MM framework will be designed with a series of Recommendations, rather than a single Recommendation, as a suite of the framework of mobility management for NGN. The design of the MM framework includes a variety of technical issues to be addressed. Those design i

21、ssues are associated with a wide variety of mobility scenarios and protocols. The MM framework Recommendations are: Recommendation Q.1707/Y.2804: Generic framework of mobility management for next generation networks; Recommendation Q.1708/Y.2805: Framework of location management for NGN; Recommendat

22、ion Q.1709/Y.2806: Framework of handover control for NGN; Rec. ITU-T Q.1708/Y.2805 (10/2008) 1 Recommendation ITU-T Q.1708/Y.2805 Framework of location management for NGN 1 Scope This Recommendation describes the framework of IP-based location management (LM) for NGN, which includes design considera

23、tions, functional architecture, and information flows for location management. This Recommendation focuses on terminal mobility when mobile terminals move around and change their IP addresses in the NGN. This Recommendation also focuses on the mobility management (MM) schemes that operate in the net

24、work or IP layers, whereas the issues on the mobility support in the service stratum will be addressed in another Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendati

25、on. 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 recent edition of the Recommendations and other references li

26、sted 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 Recommendation ITU-T Q.1706/Y.2801 (2006), Mobility management requ

27、irements 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.1709 Recommendation ITU-T Q.1709/Y.2806 (2008), Framework of handover control for NGN. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General ove

28、rview of NGN. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for Next Generation Networks. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2014 Recommendation ITU-T Y.2014 (2008),

29、 Network attachment control functions in next generation networks. ITU-T Y.2091 Recommendation ITU-T Y.2091 (2007), Terms and definitions for next generation networks. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2006), Resource and admission control functions in next generation networks. 3 Definitions

30、 3.1 Terms defined in ITU-T Q.1707 This Recommendation uses the following terms defined in ITU-T Q.1707: 3.1.1 location identifier (LID): A topological location identifier of a UE. An IP address can be used as a location identifier. Refer also to ITU-T Y.2091. 2 Rec. ITU-T Q.1708/Y.2805 (10/2008) 3.

31、1.2 user identifier (UID): A series of digits, characters and symbols or any other form of data that are used to identify a subscriber (user) or user equipment in the NGN. Refer also to ITU-T Y.2091. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 pers

32、istent LID (PLID): A LID that does not change even when a mobile user equipment (MUE) moves across different access networks or IP subnets. 3.2.2 temporary LID (TLID): A LID that changes when a mobile user equipment (MUE) moves across different access networks or IP subnets. 3.2.3 LID binding update

33、 (LBU): An operation of location management to manage the mapping between persistent LIDs (PLIDs) and temporary LIDs (TLIDs). 4 Abbreviations This Recommendation uses the following abbreviations: ALM Access Location Management ALM-FE Access Location Management Functional Entity CLM Central Location

34、Management CLM-FE Central Location Management Functional Entity CoA Care of Address CUE Corresponding User Equipment DHCP Dynamic Host Configuration Protocol FE Functional Entity FRA Functional Requirements and Architecture for NGN HCF Handover Control Function HoA Home Address HSDPA High Speed Down

35、link Packet Access ID Identifier IMSI International Mobile Subscriber Identifier IP Internet Protocol L3 Layer 3 LBU LID Binding Update LID Location Identifier LM Location Management LMF Location Management Function LM-FE Location Management FE MIP Mobile IP MIPv6 Mobile IPv6 MM Mobility Management

36、Rec. ITU-T Q.1708/Y.2805 (10/2008) 3 MMCF Mobility Management Control Function MUE Mobile User Equipment NACF Network Attachment Control Function NAI Network Access Identifier NGN Next Generation Network PLID Persistent LID RACF Resource Admission Control Function TF Transport Function TLID Temporar

37、y LID UE User Equipment UID User Identifier URI Uniform Resource Identifier Wi-Fi Wireless Fidelity WiMAX Worldwide interoperability for Microwave Access 5 Design considerations 5.1 MM identifiers The identifiers for MM can be classified into user ID (UID) and location ID (LID). The location ID can

38、be further classified into persistent LID (PLID) and temporary LID (TLID). 5.1.1 User identifier (UID) A UID represents a user or UE in the NGN. The UID can be in a variety of formats such as uniform resource identifier (URI), network access identifier (NAI), international mobile subscriber identifi

39、er (IMSI), etc. In this Recommendation, it is assumed that a UID is given to a user that has subscribed to the NGN mobility service. 5.1.2 Location identifier (LID) The location management (LM) functionality is used to keep track of mobile user equipments (UEs) in the network by identifying and main

40、taining the location information of the concerned mobile UEs. Such location information or location identifier (LID) is classified into physical LID and logical LID. The physical LID represents the geographical location of the mobile UE. The logical LID includes an IP address for routing/forwarding

41、IP packets to the mobile UE in the network. This Recommendation does not consider the physical or geographical LID. This Recommendation considers only the logical LID, and focuses on the use of the IP address as LID. From the point of view of IP-based LM, a logical LID, or IP address, can be further

42、 classified into persistent LIDs (PLIDs) and temporary LIDs (TLIDs). 5.1.3 Persistent LID (PLID) A typical example of PLID is the home address (HoA), which is defined in the mobile IP (MIP). When a mobile UE (MUE) is connected to the network at the initial power-on, a PLID should be statically or dy

43、namically allocated to the MUE. In order to support session continuity of MUEs, the PLID may not be changed, even if an MUE moves into another IP subnet. In this sense, this LID is called persistent. In some cases, however, a 4 Rec. ITU-T Q.1708/Y.2805 (10/2008) PLID may be newly configured, for exa

44、mple, when the MUE is reconnected to the network after a failure or power-off, or when it enters a new local domain in a localized MM scheme. 5.1.4 Temporary LID (TLID) A typical example of TLID is the care-of address (CoA) of MIP. When an MUE moves into another IP subnet, it will obtain a new TLID,

45、 as seen in the example of MIPv6 CoA. In host-based LM, a TLID should be dynamically allocated to the MUE, possibly through DHCP. In network-based LM, an IP address of the concerned access router may be used as TLID of an MUE. 5.2 LM operations IP-based LM is used to manage the mappings between UID

46、and PLID, and between PLID and TLID for each MUE. In this respect, LM operations consist of: UID binding operation for mapping between UID and PLID; LID binding operation for mapping between PLID and TLID. This Recommendation focuses on the LID binding operation. On the other hand, it is noted that

47、paging management is one of the essential functionalities that can be used with location management. However, the IP-based paging function is for further study. The paging function is outside the scope of this Recommendation. 5.2.1 UID binding operation The UID binding operation is used to manage th

48、e mapping between the UID and the PLID for each mobile UE. A UID is assigned to an NGN user on the subscription basis, whereas a PLID represents an IP address. The UID binding information should be registered when an MUE gets a PLID. Such information will be updated if the PLID is re-configured by t

49、he MUE. It is noted that UID binding operation schemes are quite dependent on the type of UID associated with the user (e.g., URI, IMSI, or UE identifier, etc.). This implies that there may be a variety of schemes or scenarios for UID binding management. This Recommendation does not deal with the details of UID binding management schemes. 5.2.2 LID binding operation The LID binding operation is used to manage the mapping between PLID and TLID for each mobile UE. The LID binding update (LBU) operation will be used for LID bindin