ITU-T Q 3228-2016 Signalling requirements and protocol at the M1 interface between the transport location management physical entity and the mobile location management physical ent.pdf

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 Q.3228 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2016) SERIES Q: SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS Signalling requirements and protocols for the NGN Signalling and control requirement

2、s and protocols to support attachment in NGN environments Signalling requirements and protocol at the M1 interface between the transport location management physical entity and the mobile location management physical entity (P) Recommendation ITU-T Q.3228 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND

3、 SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC 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

4、 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. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.10

5、99 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS

6、AND PROTOCOLS FOR THE NGN Q.3000Q.3709 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099 Network data organization within the NGN Q.3100Q.3129 Bearer control signalling Q.3130Q.3179 Signalling and control requirements and protocols to support attachment in NGN

7、environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369 Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary services Q.3600Q.3616 Service and session control protocols supplementary services based on SIP-IMS Q.3617Q.3639 NGN applications Q

8、.3700Q.3709 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN Q.3710Q.3899 TESTING SPECIFICATIONS Q.3900Q.4099 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3228 (08/2016) i Recommendation ITU-T Q.3228 Signalling requirements and protocol at the M1 interface betwee

9、n the transport location management physical entity and the mobile location management physical entity (P) Summary Recommendation ITU-T Q.3228 provides the protocol for the interface between the TLM-PE of the NACE and the MLM-PE (P) of the MMCE. M1 interface allows distribution of information from t

10、he TLM-PE to the MLM-PE (P). This Recommendation supports information flows across the M1 reference point as specified in Recommendation ITU-T Y.2018. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Q.3228 2016-08-29 11 11.1002/1000/12984 Keywords Mobile location management

11、physical entity, MLM-PE(P), M1 interface, TLM-PE, transport location management physical entity * To access the Recommendation, 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

12、-en. ii Rec. ITU-T Q.3228 (08/2016) 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 Sector (ITU-T) is a permanent organ o

13、f 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 every four years, establishes the topi

14、cs 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, the necessary standards are prep

15、ared 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 voluntary. However, the Recommendation ma

16、y 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 negative equivalents are used to e

17、xpress requirements. The use of such words does not suggest that compliance with the Recommendation is required of any 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 Pr

18、operty 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 Recommendation, ITU had not received notice

19、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:/www.itu.int/ITU-T/ipr/. ITU 2016

20、 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.3228 (08/2016) 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 Recom

21、mendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 M1 interface 3 6.1 Overview 3 6.2 Physical entities 3 7 Signalling requirements 3 7.1 Indication of host-based mobility . 4 7.2 Indication of network-based mobility 5 8 Description of procedures . 6 8.1 General . 6 8.2 Procedures on the

22、M1 interface 6 9 Use of Diameter-based protocol . 9 9.1 Securing Diameter messages 9 9.2 Accounting functionality 9 9.3 Use of sessions . 9 9.4 Transport protocol 9 9.5 Routing considerations . 9 9.6 Advertising application support . 10 10 Message specification . 10 10.1 Commands 10 10.2 Experimenta

23、l-Result-Code AVP values . 12 10.3 Attribute-value pairs . 12 10.4 Use of namespaces . 14 11 Security considerations . 14 Appendix I Mapping to mobility signalling requirements for IMT-2020 15 Bibliography. 16 Rec. ITU-T Q.3228 (08/2016) 1 Recommendation ITU-T Q.3228 Signalling requirements and prot

24、ocol at the M1 interface between the transport location management physical entity and the mobile location management physical entity (P) 1 Scope This Recommendation specifies the protocol for the M1 interface ITU-T Y.2014 between the TLM-PE and the MLM-PE (P). The M1 reference point supports delive

25、ry of the information, including mobility service. 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 editions indicated were valid. All Recommen

26、dations 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 valid ITU-T Recommendations is regularly pu

27、blished. 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.3230 Recommendation ITU-T Q.3230 (2012), Signalling requirements and protocol at the M13 interface between the transport location management and networ

28、k information distribution physical entities. ITU-T Q.3232 Recommendation ITU-T Q.3232 (2014), Signalling requirements and protocol at the Nc interface between the transport location management physical entity and the transport authentication and authorization physical entity. ITU-T Y.2014 Recommend

29、ation ITU-T Y.2014 (2010), Network attachment control functions in next generation networks. ITU-T Y.2018 Recommendation ITU-T Y.2018 (2009), Mobility management and control framework and architecture within the NGN transport stratum. ETSI TS 129 229 ETSI TS 129 229 V13.0.0 (2016), Digital cellular

30、telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229 version 13.0.0 Release 13). ETSI TS 129 329 ETSI TS 129 329 V12.6.0 (2016), Digital cellular telecommunications sy

31、stem (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 version 12.6.0 Release 12). ETSI ES 283 034 ETSI ES 283 034 V2.2.0 (2008), Telecommunications and Internet converged Services and Protocols for Advan

32、ced Networks (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol. ETSI ES 283 035 ETSI ES 283 035 V3.1.1 (2015), Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMETER protocol. 2 Rec. ITU-T Q.3228 (08/2016) IETF RFC 4960 IETF RFC

33、 4960 (2007), Stream Control Transmission Protocol. IETF RFC 6733 IETF RFC 6733 (2012), Diameter Base Protocol. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 security association b-IETF RFC 2401: A simplex “connection“ that affords sec

34、urity services to the traffic carried by it. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: 3GPP 3rd Generation Partnership Project AAA Authentication, Authorization and Accounting AM-PE Access Management

35、 Physical Entity ABNF Augmented Backus-Naur Form AVP Attribute-Value Pair CPE Customer Premises Equipment HDC-PE Handover Decision and Control Physical Entity IP Internet Protocol IPsec IP security protocol MLM-PE Mobile Location Management Physical Entity MMCE Mobility Management and Control Entity

36、 MMCF Mobility Management and Control Function NACE Network Attachment Control Entity NACF Network Attachment Control Function NAC-PE Network Access Configuration Physical Entity NGN Next Generation Network SCTP Stream Control Transmission Protocol TAA-PE Transport Authentication and Authorization P

37、hysical Entity TLM-PE Transport Location Management Physical Entity TUP-PE Transport User Profile Physical Entity UE User Equipment 5 Conventions None. Rec. ITU-T Q.3228 (08/2016) 3 6 M1 interface 6.1 Overview This information flow is used to distribute several types of information from the TLM-PE t

38、o the MLM-PE(P) defined in the stage 2 specification ITU-T Y.2014 and ITU-T Y.2018. The M1 interface allows the exchange of information about mobility service parameters. Figure 6-1 Reference points between the NACF and the MMCF ITU-T Y.2018 6.2 Physical entities 6.2.1 Transport location management

39、physical entity (TLM-PE) The TLM-PE is assumed to be able to contact the NAC-PE via an internal reference point to obtain the persistent and temporary IP addresses. In the host-based mobility case, the information passed from the TLM-PE includes the keying material derived from the UE authentication

40、 procedure to support the security association between the MLM-PE(P) and the UE. Also, it may include mobility service user ID, persistent IP address of the user, and binding between mobile user ID and persistent IP address. In the case of network-based mobility, the transferred information includes

41、 the identifier or persistent address, the address of the MLM-PE(C) instance for this connection, and may include the lower tunnel end point address and other parameters relating to mobility service. 6.2.2 Mobility location management physical entity (MLM-PE) When the TLM-PE indicates network-based

42、mobility service to the MLM-PE(P), this indication will trigger the mobile location registration procedure, and indirectly trigger handover. 7 Signalling requirements Reference point M1 allows the TLM-PE to interact with the MLM-PE(P) for pushing mobility service parameters, such as keying material

43、and anchor address. The TLM-PE holds keying material, anchor address, etc. in the mobility service parameters information shown in Table 7-1 and pushes keying material to MLM-PE(P). The M1 reference point should allow information exchange as follows: information about mobility service parameters is

44、pushed by the TLM-PE to MLM-PE(P). 4 Rec. ITU-T Q.3228 (08/2016) Table 7-1 Information about mobility service parameters in TLM-PE Parameter Description Received from Address of MLM-PE(C) The address of the instance of the MLM-PE containing the mobile address binding information. NAC-PE Address of M

45、LM-PE(P) The address of the MLM-PE instance which sends the location registration. Keying Material The material used for the security association between the UE and MMCE. TAA-PE Mobility Protocol Type The type of mobility protocol, such as host-based or network-based mobility. Anchor point address T

46、he upper tunnel end point address, from the point of view of the UE. Tunnel end point address The tunnelling end point address for the network node which works as UEs proxy (lower tunnel end point). The following information flows shall be used on the M1 interface: Indication of host-based mobility;

47、 Indication of network-based mobility. Figure 7-1 shows the information flows between the TLM-PE and the MLM-PE(P) through the M1 interface. Figure 7-1 Information flow 7.1 Indication of host-based mobility In the host-based mobility case, the transferred information includes the keying material der

48、ived from the UE authentication procedure, in support of the security association required between the MLM-PE(P) and the UE. The information passed from the TLM-PE to the MLM-PE(P) may also include: mobility service user ID; persistent IP address of the user; binding between mobile user ID and persi

49、stent IP address. The TAA-PE obtains these mobility service parameters from an AAA entity in the mobile subscribers home network. How the TAA-PE determines that mobility service is to be provided and that mobility service parameters are required is out of the scope of this Recommendation. The contents of the “indication of host-based mobility“ primitive described in ITU-T Y.2018 are shown in Table 7-2. Rec. ITU-T Q.3228 (08/2016) 5 Table 7-2 Indication of host-based mobility