1、 International Telecommunication Union ITU-T Q.3223TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2009) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Signalling and control requirements and protocols to support attachment in NGN environments Requirements a
2、nd protocol for the interface between a transport location management physical entity and a policy decision physical entity (Ru Interface) Recommendation ITU-T Q.3223 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC
3、 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 OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.
4、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.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOL
5、S 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 AND PROTOCOLS FOR THE NGN Q.3000Q.3999 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099
6、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 environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369 Service and session control protocols Q.3400Q.3499 Service and
7、 session control protocols supplementary services Q.3600Q.3649 NGN applications Q.3700Q.3849 Testing for NGN networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3223 (06/2009) i Recommendation ITU-T Q.3223 Requirements and protocol for the inter
8、face between a transport location management physical entity and a policy decision physical entity (Ru Interface) Summary Recommendation ITU-T Q.3223 describes requirements and protocol for the Ru interface between a transport location management physical entity (TLM-PE) in a network attachment cont
9、rol entity (NACE) and a policy decision physical entity (PD-PE) in a resource and admission control entity (RACE) of ITU-T next generation network (NGN) release 1. Source Recommendation ITU-T Q.3223 was approved on 29 June 2009 by ITU-T Study Group 11 (2009-2012) under Recommendation ITU-T A.8 proce
10、dures. Keywords Network attachment, next generation network (NGN), Ru interface. ii Rec. ITU-T Q.3223 (06/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The
11、 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 telecommunications on a worldwide basis. The World Telecommunication Standar
12、dization 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 the procedure laid down in WTSA Resolution 1. In some areas of information t
13、echnology 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 both a telecommunication administration and a recognized operating agency. Comp
14、liance 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 all of these mandatory provisions are met. The words “shall“ or some other ob
15、ligatory 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 RIGHTS ITU draws attention to the possibility that the practice or implementa
16、tion 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 ITU members or others outside of the Recommendation development process. As
17、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 this may not represent the latest information and are therefore strongly urged
18、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. Rec. ITU-T Q.3223 (06/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions
19、 2 3.1 Terms defined elsewhere 2 4 Abbreviations and acronyms 2 5 Ru interface. 3 5.1 Overview 3 5.2 Reference point. 3 5.3 Physical entities 3 6 Signalling requirements 4 6.1 Transport resource information 5 6.2 Transport resource information indication . 7 6.3 Transport resource release notificati
20、on 7 7 Procedure descriptions 7 7.1 General . 7 7.2 Procedures on the Ru interface. 8 8 Selection and the use of the protocol 13 8.1 Security. 13 8.2 Accounting . 13 8.3 Sessions 13 8.4 Transport protocol 13 8.5 Routing considerations . 13 8.6 Application advertisement 14 9 Ru protocol specification
21、 14 9.1 Commands 14 9.2 Result-Code AVP values 17 9.3 AVPs. 17 9.4 Use of namespaces . 20 10 Security considerations. 20 Bibliography. 21 Rec. ITU-T Q.3223 (06/2009) 1 Recommendation ITU-T Q.3223 Requirements and protocol for the interface between a transport location management physical entity and
22、a policy decision physical entity (Ru Interface) 1 Scope This Recommendation defines the requirements and protocol for the Ru interface (identical to the TC-TC1 interface defined in ITU-T Y.2012) between a transport location management physical entity (TLM-PE) in a network attachment control entity
23、(NACE) and a policy decision physical entity (PD-PE) in a resource and admission control entity (RACE) of ITU-T NGN release 1 architecture. Whenever applicable, this Recommendation specifies the requirements for the Ru interface referring to the Diameter base specifications. Whenever needed, extensi
24、ons to Diameter-based specifications are provided in this Recommendation. 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 w
25、ere 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 valid ITU-T Recommen
26、dations 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.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2014 Recommendat
27、ion 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. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1.
28、ETSI TS 129 229 ETSI TS 129 229 v8.6.0 (2009), Digital cellular telecommunication system (Phase 2+); Universal Mobile Telecommunications system (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol. ETSI TS 129 329 ETSI TS 129 329 (2006), Digital cellular telecommunication system (Phase 2
29、+); Universal Mobile Telecommunications system (UMTS); Sh interface based on the Diameter protocol; Protocol details. ETSI TS 183 017 ETSI TS 183 017 (2007), Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER pr
30、otocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification. ETSI ES 283 034 ETSI ES 283 034 v1.5.0 (2008), Telecommunications and Internet converged Services and Protocols for Advanced Netw
31、orking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the Diameter protocol. 2 Rec. ITU-T Q.3223 (06/2009) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 authentication ITU-T Y.2014: A property by which the corre
32、ct identifier of an entity or party is established with a required assurance. The party being authenticated could be a user, subscriber, home environment or serving network. 3.1.2 authorization b-ITU-T X.800: The granting of permission based on authenticated identification. NOTE In some contexts, au
33、thorization may be granted without requiring authentication or identification, e.g., emergency call services. 3.1.3 customer premises equipment (CPE) ITU-T Y.2014: One or more devices allowing a user to access services delivered by NGN. NOTE This includes devices under user control commonly referred
34、 to as home gateway (HGW) or terminals (TE), etc., but not network-controlled entities such as access gateways. 3.1.4 attribute-value pair (AVP) ETSI ES 283 034: Corresponds to an information element in a Diameter message. NOTE See b-IETF RFC 3588 for details. 4 Abbreviations and acronyms This Recom
35、mendation uses the following abbreviations and acronyms: ABNF Augmented Backus-Naur Form AM-PE Access Management Physical Entity AVP Attribute-Value Pair CPE Customer Premises Equipment HGWC-PE Home Gateway Configuration Physical Entity IMS Internet Protocol Multimedia Subsystem IPSec Internet Proto
36、col Security NACE Network Attachment Control Entity NACF Network Attachment Control Function NAC-PE Network Access Configuration Physical Entity NAPT Network Address and Port Translation NAS Network Access Server NASS Network Attachment Sub-System P-CSCF Proxy Call Session Control Function PD-PE Pol
37、icy Decision Physical Entity PE-PE Policy Enforcement Physical Entity QoS Quality of Service RACE Resource and Admission Control Entity RACF Resource and Admission Control Function Rec. ITU-T Q.3223 (06/2009) 3 RFC Request For Comments SCE Service Control Entity SCTP Stream Control Transport Protoco
38、l SDP Session Description Protocol SIP Session Initiation Protocol TAA-PE Transport Authentication and Authorization Physical Entity TLM-PE Transport Location Management Physical Entity TRC-PE Transport Resource Control Physical Entity TUP-PE Transport User Profile Physical Entity 5 Ru interface 5.1
39、 Overview The network attachment control function (NACF) maintains information about IP-connectivity access sessions associated with user equipment connected to the NGN. This information is stored in the transport location management physical entity (TLM-PE) and it is pushed to or pulled from the PD
40、-PE in the RACE when the initial attachment is established or the PD-PE needs the information to make a decision (see Figure 5-1): 5.2 Reference point This clause describes the Ru reference point. Q.3223(09)_F5.1SCENAC-PEAM-PETUP-PETAA-PETLM-PEPD-PES-TC1RuScope of thisRecommendationRACENACEHGWC-PEFi
41、gure 5-1 Ru reference point 5.3 Physical entities Table 5-1 indicates the mapping from the functional entities to the physical entities implementing them. 4 Rec. ITU-T Q.3223 (06/2009) Table 5-1 Mapping from functional to physical entities concerned with the Ru reference point Functional entity Abbr
42、ev. Physical entity Abbrev. Service control functions SCF Service control entity (e.g., implementation of P-CSCF) SCE Network attachment control functions NACF Network attachment control entity NACE Resource and admission control functions RACF Resource and admission control entity RACE Policy decis
43、ion functional entity PD-FE Policy decision physical entity PD-PE Transport location management functional entity TLM-FE Transport location management physical entity TLM-PE 5.3.1 Transport location management physical entity (TLM-PE) The transport location management physical entity (TLM-PE) is a p
44、hysical entity that implements the functionalities of the transport location management functional entity (TLM-FE) defined in the NACF. The TLM-PE registers the association between the IP address allocated to the terminal and related network location information provided by the NAC-PE, for example,
45、access transport equipment characteristics, line identifier (logical access ID), IP edge identity, etc. The TLM-PE registers the association between network location information received from the NAC-PE and geographical location information. The TLM-PE may also store the identity of a user or a term
46、inal to which the IP address has been allocated (information received from the TAA-PE), as well as the user network QoS profile and user preferences regarding the privacy of location information. In case the TLM-PE does not store the identity/profile of the user/terminal, the TLM-PE shall be able to
47、 retrieve this information from the TAA-PE. The TLM-PE responds to location queries from service control functions and applications. The actual information delivered by the TLM-PE may take various forms (e.g., network location, geographical coordinates, postal address, etc.), depending on agreements
48、 with the requestor and on user preferences regarding the privacy of its location. The TLM-PE interfaces with the NAC-PE to establish the association between the IP address, which is allocated by the NAC-FE to the end-user equipment, and the line ID. The TLM-PE also registers user network profile in
49、formation (received from the TAA-PE at authentication) to make this profile information available to the RACE during authentication of the terminal. The TLM-PE is able to correlate the information received from NAC-PE and TAA-PE based on the logical access ID. 5.3.2 Policy decision physical entity (PD-PE) The PD-PE is a physical entity that implements the functionalities of the policy decision functional entity (PD-FE) defined in ITU-T Y.2111, which coordinates the resource reservation requests rec
