1、 International Telecommunication Union ITU-T Q.3314TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2012) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Requirements and protocol at the interface between the mobile location manageme
2、nt physical entity used as a proxy and the central instance of the mobile location management physical entity (M9 interface) Recommendation ITU-T Q.3314 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTO
3、MATIC WORKING Q.4Q.59 FUNCTIONS 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 SPECIFICAT
4、IONS OF SIGNALLING SYSTEM No. 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
5、 Q.1700Q.1799 SPECIFICATIONS 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 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099 Network data o
6、rganization within the NGN Q.3100Q.3129 Bearer control signalling Q.3130Q.3179 Signalling and control requirements and protocols to support attachment in NGN environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369Service and session control protocols Q.3400Q.3499 Service and session contro
7、l protocols supplementary services Q.3600Q.3649 NGN applications Q.3700Q.3849 Testing for next generation networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3314 (05/2012) i Recommendation ITU-T Q.3314 Requirements and protocol at the interface
8、 between the mobile location management physical entity used as a proxy and the central instance of the mobile location management physical entity (M9 interface) Summary Recommendation ITU-T Q.3314 provides the signalling requirements and protocol for the M9 interface between the mobile location man
9、agement physical entity as proxy (MLM-PE(P) and the MLM-PE as the central instance (MLM-PE(C) specified in Recommendation ITU-T Y.2018. The M9 interface provides information from the MLM-PE(P) and the MLM-PE(C) to registration/update and query mobility location information in both host-based and net
10、work-based mobility cases. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.3314 2012-05-22 11 Keywords M9 interface, MMCF, mobility control. ii Rec. ITU-T Q.3314 (05/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field o
11、f 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 standardizing
12、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 is covered by
13、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 to indicate bot
14、h 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 achieved when
15、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. INTELLECTUAL PROPERTY
16、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, whether asserted by
17、 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, implementers are cautioned that th
18、is 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 2013 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU
19、-T Q.3314 (05/2012) iii Table of 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 2 5 M9 interface 3 5.1 Overview 3 5.2 M9 reference model 3 5.3 Physical entities and capabilities 3 6 Proto
20、col specifications 4 6.1 Location binding registration/update request/response 5 6.2 Mobility location query request/response 5 7 Message specification . 7 7.1 Use of Diameter base protocol . 7 7.2 Diameter base protocol message mapping on the M9 interface . 8 7.3 Diameter base protocol message form
21、ats on the M9 interface . 10 8 Security considerations . 15 Appendix I High-level information flow at M9 16 I.1 Mobility location binding registration/update during network attachment 16 I.2 Mobility location binding registration/update during handover . 17 I.3 Route optimization considerations for
22、network-based handover . 19 Bibliography. 22 Rec. ITU-T Q.3314 (05/2012) 1 Recommendation ITU-T Q.3314 Requirements and protocol at the interface between the mobile location management physical entity used as a proxy and the central instance of the mobile location management physical entity (M9 inte
23、rface) 1 Scope This Recommendation defines the protocol for the M9 interface between the mobile location management physical entity as proxy (MLM-PE(P) and the MLM-PE as the central instance (MLM-PE(C) specified in ITU-T Y.2018. The M9 reference point provides the information flows to register and u
24、pdate mobility location information in both host-based and network-based mobility cases specified in ITU-T Y.2018. In the network-based mobility case, the MLM-PE(P) sends the location registration and/or update request to the MLM-PE(C). In the host-based mobility case, the user equipment (UE) sends
25、the location registration and/or update request to the MLM-PE(P), which will forward it to the MLM-PE(C). The M9 reference point also provides the information flows for retrieving the binding location information regarding UEs reachability. The MLM-PE(P) holds the binding information between mobile
26、user ID (or persistent address) and temporary address (or lower tunnel end point address). The MLM-PE(C) holds the binding information between mobile user ID (or persistent address), and address of the MLM-PE(P). The MLM-PE(P) may identify the corresponding MLM-PE(C) by extracting the home domain fr
27、om the mobile user ID. The MLM-PE(P) may initiate route optimization through this interface. 2 References The following 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 e
28、ditions 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 listed below. A list of the currently v
29、alid 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 Y.2018 Recommendation ITU-T Y.2018 (2009), Mobility management and control framework and architecture within th
30、e NGN transport stratum. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. ETSI ES 283 034 ETSI ES 283 034 (2008), e4 interface based on the Diameter protocol. ETSI ES 283 035 ETSI ES 283 035 (2008), e2 interface based on the Diameter protocol. ETSI TS 129 229
31、 ETSI TS 129 229 (2010), Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229 version 9.3.0 Release 9). ETSI TS 129 272 ETSI TS 129 272 v9.2.0 (2010), Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol
32、(3GPP TS 29.272 version 9.2.0 Release 9). 2 Rec. ITU-T Q.3314 (05/2012) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 authentication b-ITU-T Y.2014: A property by which the correct identifier of an entity or party is established with a
33、 required assurance. The party being authenticated could be a user, subscriber, home environment or serving network. 3.2 Terms defined in this Recommendation 3.2.1 location information (Based on the definition given in b-ITU-T Q.1001): Actual location of the mobile station (e.g., PLMN, MSC area, loc
34、ation area, as required). 3.2.2 location registration (Based on the definition given in b-ITU-T Q.1741.3): The procedure to register its presence in a registration area when the user equipment enters a new registration area. 3.2.3 nomadism (Based on the definition given in b-ITU-T Q.1761): Ability o
35、f the user to change his network access point after moving; when changing the network access point, the users service session is completely stopped and then started again, i.e., there is no session continuity or hand-over possible. NOTE It is assumed that the normal usage pattern is that users shutd
36、own their service session before moving to another access point. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ATM Asynchronous Transfer Mode AVP Attribute-Value Pair FQDN Fully Qualified Domain Name GPRS General Packet Radio Service GTP GPRS Tunnell
37、ing Protocol HDC-PE Handover Decision and Control Physical Entity ID Identification MLM-FE Mobile Location Management Functional Entity MLM-PE Mobile Location Management Physical Entity MMCF Mobility Management Control Functions MLM-PE(C) An instance of the MLM-PE performing the Central mobile locat
38、ion management role MLM-PE(P) An instance of the MLM-PE performing the Proxy mobile location management role MPLS Multiprotocol Label Switching NACF Network Attachment Control Function NAT Network Address Translation NID-PE Network Information Distribution Physical Entity NIR-PE Network Information
39、Repository Physical Entity PD-PE Policy Decision Physical Entity Rec. ITU-T Q.3314 (05/2012) 3 PPP Point-to-Point Protocol RACF Resource Admission and Control Function SCTP Stream Control Transport Protocol TLM-PE Transport Location Management Physical Entity UE User Equipment VCI Virtual Circuit Id
40、entifier VPI Virtual Path Identifier 5 M9 interface 5.1 Overview This Recommendation specifies the protocol for the M9 reference point. The M9 reference point provides the information flows to register and update mobility location information via the M9 interface specified in ITU-T Y.2018 in both th
41、e host-based and network-based mobility cases. The M9 reference point also provides the information flows for retrieving the binding location information regarding the UEs reachability. Therefore, two operations may occur at the M9 interface as follows: mobility location binding registration and/or
42、update mobility location query. 5.2 M9 reference model Figure 5-1 describes the M9 reference architecture. This illustration can be used as the initial architecture. Figure 5-1 M9 reference model 5.3 Physical entities and capabilities 5.3.1 Mobile location management physical entity (MLM-PE) The MLM
43、-PE has the following responsibilities: in the case of network-based mobility, initiating location registration on behalf of the UE; processing location registration messages sent from, or on behalf of the UE; optionally, maintaining the binding between the mobility service user ID and persistent IP
44、 address assigned to the UE; MLM-PEHDC-PENID-PENIR-PEMMCF (P)M10M12M11NACFRACFMMCF (C)MLM-PEHDC-PENID-PENIR-PEM10M9M8M1TLM-PEPD-PEUEM3M12M114 Rec. ITU-T Q.3314 (05/2012) management of the binding between the persistent IP address assigned to the UE and its temporary IP address, in the case of host-b
45、ased mobility, or the address of the lower tunnel end point, in the case of network-based mobility; optionally, holding two location bindings for the mobile UE by marking the binding for the serving network as active state and marking the binding for target network as standby state; supporting separ
46、ation of control and data plane by allowing the MLM-PE address and data forwarding end point address (i.e., tunnel end point address) to be different; indication of a new mobility location binding and distribution of binding information to the HDC-PE. The MLM-PE has two roles, as proxy (MLM-PE(P) an
47、d as the central instance (MLM-PE(C). The MLM-PE(P) and MLM-PE(C) roles may be co-located in specific deployments providing only host-based mobility. The MLM-PE(C) provides a central point of contact for correspondent nodes (e.g., the service control function (SCF). The MLM-PE(P) and MLM-PE(C) toget
48、her provide hierarchical location management. The MLM-PE(P) holds and updates the binding between mobile user ID, persistent address, and temporary/lower tunnel end point address. The MLM-PE(C) holds the binding between mobile user ID, persistent address, and address of the MLM-PE(P). The MLM-PE(P)
49、may identify the corresponding MLM-PE(C) by extracting the home domain from the mobile user ID. The MLM-PE(P) consists of the following functions: In the host-based case, it provides the first point of contact for location registration for mobile users. As such, it appears as a proxy for the MLM-PE(C) from the point of view of the UE, while appearing as a proxy for the UE from the point of view of the MLM-PE(C). The mobile UE obtains the address of the MLM-PE(P) in the attachment proce
