1、 International Telecommunication Union ITU-T Q.3307.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(03/2012) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 7 Protocol at the interface between
2、inter-domain policy decision physical entities (Ri interface) Amendment 1 Recommendation ITU-T Q.3307.1 (2009) Amendment 1 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 FUNCTION
3、S 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 O
5、F 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 organization within the NGN Q.3
6、100Q.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 control protocols supplementary serv
7、ices 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.3307.1 (2009)/Amd.1 (03/2012) i Recommendation ITU-T Q.3307.1 Resource control protocol No. 7 Protocol at the interfa
8、ce between inter-domain policy decision physical entities (Ri interface) Amendment 1 Summary Amendment 1 to Recommendation ITU-T Q.3307.1 specifies additions of two attribute value pairs (AVPs) which are Restoration-Indication AVP and Downgraded-Indication AVP. The addition requires to modify the in
9、itial reservation procedures (i.e., clauses 7.2.1 and 7.2.2) and to add new AVP information (i.e., clause 10.4) of ITU-T Q.3307.1. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.3307.1 2009-06-29 11 1.1 ITU-T Q.3307.1 (2009) Amd. 1 2012-03-29 11 ii Rec. ITU-T Q.3307.1 (2009)/Amd.1 (
10、03/2012) 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 of ITU. ITU-T is responsible
11、 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 topics for study by the ITU-T s
12、tudy 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 prepared on a collaborative bas
13、is 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 may contain certain mandatory
14、 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 express requirements. The us
15、e 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 the use of a claimed Intellectual Property Right. ITU takes no
16、 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 of intellectual property,
17、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 2012 All rights reserved. No p
18、art of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.3307.1 (2009)/Amd.1 (03/2012) iii Table of Contents Page 1) Clause 2, References . 1 2) Clause 7, Procedures . 1 3) Clause 10.4.10, Media-Component-Description AVP: 6 Rec. IT
19、U-T Q.3307.1 (2009)/Amd.1 (03/2012) 1 Recommendation ITU-T Q.3307.1 Resource control protocol No. 7 Protocol at the interface between inter-domain policy decision physical entities (Ri interface) Amendment 1 1) Clause 2, References Revise reference to ITU-T Y.2111 as shown below: ITU-T Y.2111 Recomm
20、endation ITU-T Y.2111 (201108), Resource and admission control functions in next generation networks. 2) Clause 7, Procedures Additions of the restoration and the QoS downgrade indication steps in the initial reservation and session modification procedures 2a) Modify clause 7.2.1 as indicated: 7.2.1
21、 Procedures at the originating PD-PE The originating PD-PE performs admission control based on requirements from the SCE of the originating domain. The originating PD-PE is required to request an authorization for the session from the peer PD-PE by sending an AA-Request (AAR) message. This AAR messa
22、ge is required to contain a new Session-Id. The AAR may contain an Authorization-Lifetime AVP as an indication of the maximum lifetime that it is requesting. The AAR can optionally include an Auth-Session-State AVP as an indication of the originating PD-PEs preference for stateful or stateless opera
23、tion. The originating PD-PE may include the Operation-Indication AVP to indicate whether the peer PD-PE must perform NAPT control and network address translation (NAT) traversal functions or QoS resource reservation or both after receiving the AAR. The originating PD-PE is required to include the co
24、rresponding Media-Component-Description AVP(s) into the message, if the session description information (SDI) is already available. The originating PD-PE can optionally include the Flow-Grouping AVP(s) to request a particular grouping for IP flows described within the service description. This is di
25、stributed to the forwarding plane. When providing a given Media-Component-Description AVP in the initial AAR, the originating PD-PE can optionally request the peer PD-PE to commit the requested resources by setting the Flow-Status AVP to the value ENABLED, ENABLED-UPLINK or ENABLED-DOWNLINK. Alterna
26、tively, the originating PD-PE can optionally perform this in two phases using separate reserve and commit operations. If commitment is done in two phases, the Flow-Status AVP value of the initial AAR is required to be set to DISABLED. 2 Rec. ITU-T Q.3307.1 (2009)/Amd.1 (03/2012) If, based on local c
27、onfiguration data, the originating PD-PE determines that address translation needs to occur on the user plane (e.g., the PE-PE implements NAT, or NAPT, or hosted NAPT procedure) the following action is performed. After the originating PD-PE receives an SDI that is associated with the endpoint served
28、 by it, the originating PD-PE is required to include the Binding-Information AVP with the Input-List AVP. The originating PD-PE can optionally include the SDP-Direction AVP along with the Binding-Information AVP to indicate whether the address set in the Output-list AVP is expected to be received in
29、 the AA-Answer (AAA) in either of the following: originating core network; or peer core network. If required (e.g., in cases where the served endpoint is behind a hosted-NAPT), the originating PD-PE can optionally include the Latching-Indication AVP set to “LATCH“. Based on local configuration data,
30、 the originating PD-PE can optionally include the TLM-PE-Identifier AVP in AAR to indicate the TLM-PE related to the user. For the purpose of QoS profile correlation in a peer PD-PE lying within an access network, the originating PD-PE is required to include within the AAR a correlation identifier i
31、n the form of: the User-Name AVP or; the Globally-Unique-IP-Address AVP. The User-Name AVP is defined in IETF RFC 3588. The Globally-Unique-IP-Address AVP is defined in ETSI ES 283 034. The originating PD-PE can optionally specify the Reservation-Priority AVP in the AAR and/or within a Media-Compone
32、nt-Description AVP of the AAR. The originating PD-PE can optionally specify the Specific-Action AVP in the AAR with the events it wants to be informed. The originating PD-PE may contain the Restoration-Indication AVP within a Media-Component-Description AVP in the AAR to indicate whether the QoS of
33、a request can be restored or not. The originating PD-PE may contain the Downgraded-Indication AVP within a Media-Component-Description AVP in the AAR to indicate whether the QoS of a request has been downgraded or not. The originating PD-PE is required to examine the content of any Auth-Session-Stat
34、e AVP it receives in the AAA message. If such an AVP is present and indicates stateful operation, the originating PD-PE is required to include the same Session-Id value in subsequent messages relating to this session as it is placed in the initial AAR. If a received Auth-Session-State AVP indicates
35、stateless operation, the originating PD-PE is required to store the value of the Class AVP(s) which are present in the AAA message. The originating PD-PE is required to include the stored Class AVP(s) in any message it sends to the peer PD-PE related to the same session. The originating PD-PE is req
36、uired to store the contents of the Binding-Output-List AVP received within the Binding-Information AVP contained in the AAA message for future use. The action of the originating PD-PE is a matter of policy when it does not receive the AAA, or when the AAA arrives after an internal timer has expired,
37、 or when the AAA arrives with an indication different from DIAMETER_SUCCESS. Rec. ITU-T Q.3307.1 (2009)/Amd.1 (03/2012) 3 2b) Modify clause 7.2.2 as indicated: 7.2.2 Procedures at peer PD-PE The peer PD-PE can optionally honour the preference indicated in the Auth-Session-State AVP, or can optionall
38、y make an independent decision based on local policy (whether or not it has received an Auth-Session-State AVP). If an Auth-Session-State AVP was present in the initial AAR or if the peer PD-PE chooses stateless operation for the current session, the peer PD-PE is required to return an Auth-Session-
39、State AVP in the AAA to indicate its decision. In stateful operation, the peer PD-PE stores the Session-Id value received in the AAR. The same Session-Id value will be present in subsequent commands relating to this session, as described in IETF RFC 3588. The peer PD-PE can optionally use the receiv
40、ed Session-Id values to locate the session context information in order to act on the commands. In stateless operation, the peer PD-PE does not store the received Session-Id. Instead, it generates, one or more Class AVPs based on local policy data (possibly the contents of the AAR and of messages re
41、ceived over other interfaces). The one or more Class AVPs will contain the information needed for the peer PD-PE to reconstruct its state when it receives additional messages relating to the same user session. This information can optionally include: a unique string identifying the session correspon
42、ding to the initial AAR; the address(es) of the TRC-PE(s) involved in the session; the address of the PE-PE involved in the session. The Class AVP(s) is required to be returned to the originating PD-PE in the AAA message. The peer PD-PE also forwards equivalent state-preserving tokens to the TRC-PE(
43、s) and PE-PE when it communicates with them. Then the peer PD-PE receives those tokens back again in messages from TRC-PE(s) and PE-PE. The peer PD-PE can optionally acquire user profile information from the TLM-FE in the NACE according to the TLM-PE-Identifier AVP if present. If the Operation-Indic
44、ation AVP is present, the peer PD-PE may use it to determine whether the initial AAR is for: NAT control only: In NAT control only, peer PD-PE is required to exercise NAPT control and NAT traversal function control at the PE-PE based on the information indicated by the Binding-Information AVP and op
45、tionally SDP-Direction AVP. QoS resource reservation only: In QoS resource reservation only, peer PD-PE is required to perform QoS resource reservation based on the information indicated by the Resource-Reservation-Mode AVP and media information. QoS resource reservation and NAT control: In QoS reso
46、urce reservation and NAT control, peer PD-PE shall perform both of the actions requested. If the Resource-Reservation-Mode AVP is present, the peer PD-PE is required to use it to determine whether the initial AAR is for: authorization only (pull mode); authorization and reservation (push mode, first
47、 phase of two-phase operation); or authorization, reservation and commitment (push mode, single-phase operation). 4 Rec. ITU-T Q.3307.1 (2009)/Amd.1 (03/2012) The operation indicated by the Resource-Reservation-Mode AVP applies to all IP flows identified by the AAR message. If the Resource-Reservati
48、on-Mode AVP is not consistent with the Flow-Status AVP for individual components and sub-components, the request is recommended to be rejected. A request for authorization only (pull mode) cannot be indicated in the absence of the Resource-Reservation-Mode AVP. However, the peer PD-PE can infer a re
49、quest for authorization from the AAR message. This is done without involvement of the originating PD-PE if Flow-Status AVP for a given media component or sub-component is set to DISABLED (3). Peer PD-PE also can infer a request for authorization if Flow-Status AVP is set to any variant of ENABLED (0), (1), or (2). The peer PD-PE is required to use the contents of the AAR in order to enforce any functions needed over the Rt and Rw interfaces whenever it recognizes that policy enforcement functions are requested on th
