1、 ETSI TS 129 209 V6.8.0 (2011-10) Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209 version 6.8.0 Release 6) Technical Specification ETSI ETSI TS 129 209 V6.8.0 (2011-10)13GPP TS 29.209 version 6.8.0 Release 6Reference RTS/TSGC-0329209v680 Keywords U
2、MTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document c
3、an be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, th
4、e reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI doc
5、uments is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written pe
6、rmission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Tra
7、de Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 209 V6.8.0 (2011-10)23GPP TS 29.209 version 6.8.0 Release 6Intellectual Property Rights IPRs essentia
8、l or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially
9、Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarante
10、e can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (
11、3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be
12、found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 209 V6.8.0 (2011-10)33GPP TS 29.209 version 6.8.0 Release 6Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations .
13、 7g34 Gq interface 7g34.1 Overview 7g34.2 Gq reference model 8g34.3 Functional elements and capabilities 8g34.3.1 Policy Decision Function (PDF) . 8g34.3.2 Application Function (AF) 8g35 Policy control procedures . 9g35.1 PDF 9g35.1.1 Initial authorization of QoS resources 9g35.1.2 Resource reservat
14、ion . 9g35.1.3 Gate function 9g35.1.4 Session modification . 9g35.1.5 Bearer modification 10g35.1.6 Revoke authorization 10g35.1.7 Indication of bearer release . 10g35.2 AF . 10g35.2.1 Initial authorization of QoS resources 10g35.2.2 Resource reservation . 10g35.2.3 Gate function 11g35.2.4 Session m
15、odification . 11g35.2.5 Revoke authorization 11g35.3 IMS related P-CSCF procedures 11g35.3.1 Provisioning of Service Information at P-CSCF . 11g35.3.2 Enabling of IP Flows at P-CSCF 12g36 Gq protocol . 12g36.1 Protocol support . 12g36.1.1 Advertising application support 13g36.2 Securing Diameter mes
16、sages 13g36.3 Gq messages . 13g36.3.1 AA-Request (AAR) command 13g36.3.2 AA-Answer (AAA) command 13g36.3.3 Re-Auth-Request (RAR) command 14g36.3.4 Re-Auth-Answer (RAA) command 14g36.3.5 Session-Termination-Request (STR) command . 14g36.3.6 Session-Termination-Answer (STA) command 15g36.3.7 Abort-Ses
17、sion-Request (ASR) command . 15g36.3.8 Abort-Session-Answer (ASA) command 15g36.4 Experimental-Result-Code AVP values . 16g36.5 Gq specific AVPs . 16g36.5.1 Abort-Cause AVP . 17g36.5.2 Access-Network-Charging-Address AVP 17g36.5.3 Access-Network-Charging-Identifier AVP. 17g36.5.4 Access-Network-Char
18、ging-Identifier-Value AVP 17g36.5.5 AF-Application-Identifier AVP 17g3ETSI ETSI TS 129 209 V6.8.0 (2011-10)43GPP TS 29.209 version 6.8.0 Release 66.5.6 AF-Charging-Identifier AVP 17g36.5.7 Authorization-Token AVP 18g36.5.8 Flow-Description AVP . 18g36.5.9 Flow-Grouping AVP. 18g36.5.10 Flow-Number AV
19、P . 19g36.5.11 Flows AVP 19g36.5.12 Flow-Status AVP 19g36.5.13 Flow-Usage AVP 20g36.5.14 Specific-Action AVP 20g36.5.15 Void 21g36.5.16 Max-Requested-Bandwidth-DL AVP . 21g36.5.17 Max-Requested-Bandwidth-UL AVP . 21g36.5.18 Media-Component-Description AVP . 21g36.5.19 Media-Component-Number AVP . 22
20、g36.5.20 Media-Sub-Component AVP 22g36.5.21 Media-Type AVP 22g36.5.22 RR-Bandwidth AVP . 22g36.5.23 RS-Bandwidth AVP 22g36.5.24 SIP-Forking-Indication AVP 23g3Annex A (normative): Support for SIP forking 24g3A.1 Support for SIP forking 24g3A.1.1 Authorization of resources for early media for forked
21、responses . 24g3A.1.2 Updating the authorization information at the final answer . 24g3Annex B (informative): Change history . 25g3History 26g3ETSI ETSI TS 129 209 V6.8.0 (2011-10)53GPP TS 29.209 version 6.8.0 Release 6Foreword This Technical Specification has been produced by the 3rdGeneration Part
22、nership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an inc
23、rease in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhanceme
24、nts, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 209 V6.8.0 (2011-10)63GPP TS 29.209 version 6.8.0 Release 61 Scope The present document provides the stage 3 specification of the Gq interface. The fu
25、nctional requirements and the stage 2 specifications of the Gq interface are contained in 3GPP TS 23.002 2 and 3GPP TS 23.207 3. The Gq interface is used for session based policy set-up information exchange between the Policy Decision Function (PDF) and the Application Function (AF). Whenever it is
26、possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. 2 References The following documents contain provisi
27、ons which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific refere
28、nce, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS
29、23.002: “Network architecture“. 3 3GPP TS 23.207: “End-to-end Quality of Service (QoS) concept and architecture“. 4 3GPP TS 29.207: “Policy control over Go interface“. 5 3GPP TS 29.208: “End-to-end Quality of Service (QoS) signalling flows“. 6 IETF RFC 3588: “Diameter Base Protocol“. 7 IETF RFC 4005
30、: “Diameter Network Access Server Application“. 8 IETF RFC 2234: “Augmented BNF for syntax specifications: ABNF“. 9 IETF RFC 3520: “Session Authorization Policy Element“. 10 3GPP TS 33.210: “3G Security; Network Domain Security (NDS); IP network layer security“. 11 IETF RFC 3556: “Session Descriptio
31、n Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth“. 12 IETF RFC 4566: “SDP: Session Description Protocol“. 13 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 14 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3“. ETSI ETSI TS 12
32、9 209 V6.8.0 (2011-10)73GPP TS 29.209 version 6.8.0 Release 63 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply: Application Function (AF): element offering applications that require th
33、e control of IP bearer resources. NOTE: The AF is capable of communicating with the PDF to transfer dynamic QoS-related application information. One example of an AF is the P-CSCF of the IM CN subsystem. AF session: established by an application level signalling protocol offered by the AF that requi
34、res a session set-up with explicit session description before the use of the service NOTE: One example of an application session is an IMS session. AF session signalling: used to control the AF session NOTE: One example of AF session signalling is SIP/SDP. Attribute-Value Pair (AVP): See RFC 3588 6,
35、 corresponds to an Information Element in a Diameter message. 3.2 Abbreviations For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply: AAA AA-Answer AAR AA-Request AF Application Function ASA Abort-Session-AnswerASR Abort-Session-Request AVP Att
36、ribute-Value PairGCID GPRS Charging ID IANA Internet Assigned Numbers Authority NASREQ Network Access Server Application P-CSCF Proxy - Call Session Control Function PDF Policy Decision Function RAA Re-Auth-Answer RAR Re-Auth-Request SBLP Service Based Local Policy SDI Session Description Informatio
37、n STA Session-Termination-Answer STR Session-Termination-Request4 Gq interface 4.1 Overview The Gq interface is used for the service-based policy set-up information exchange between the PDF and the AF, e.g. the P-CSCF. As defined in the stage 2 specifications (3GPP TS 23.207 3), this information is
38、used by the PDF for the Service Based Local Policy (SBLP) decisions. The PDF exchanges the policy information with the GGSN as specified in 3GPP TS 29.207 4. The Gq interface may be an intra- or inter-domain interface. One PDF shall be able to serve more than one AF and one given AF may interact wit
39、h a number of PDFs, although on an AF session basis, it shall interact with only a single PDF. ETSI ETSI TS 129 209 V6.8.0 (2011-10)83GPP TS 29.209 version 6.8.0 Release 6Signalling flows related to the Gq interface are specified in 3GPP TS 29.208 5. 4.2 Gq reference model The Gq interface is define
40、d between the PDF and the AF. The Gq interface may be an intra- or inter-domain interface. The PDF is in the same PLMN as the GGSN. The relationships between the different functional entities involved are depicted in figure 4.1. IP BS Manager GGSN IP BS Manager UMTS BS Manager Translation/mapping fu
41、nction Go Gq UE PEP (Policy Enforcement Point) PDF (Policy Decision Function)AF (Application Function)IP BS Manager AF Client Translation/mappingfunction UMTS BS Manager AF session signallingNOTE: For clarity in the diagram, the network elements that are not involved in SBLP are not presented here (
42、e.g. radio network elements, SGSN, etc). Figure 4.1: Gq interface architecture model 4.3 Functional elements and capabilities 4.3.1 Policy Decision Function (PDF) The PDF acts as a Policy Decision Point for service based local policy control. The PDF makes the policy decisions based on the session a
43、nd media related information obtained from the AF via the Gq interface. The PDF shall exchange the decision information with the GGSN via the Go interface. 4.3.2 Application Function (AF) The AF is an element offering applications that require the control of IP bearer resources (e.g. UMTS PS domain/
44、GPRS domain resources). One example of an application function is the P-CSCF. The AF shall use the Gq interface to exchange service based policy information with the PDF. ETSI ETSI TS 129 209 V6.8.0 (2011-10)93GPP TS 29.209 version 6.8.0 Release 65 Policy control procedures 5.1 PDF 5.1.1 Initial aut
45、horization of QoS resources When receiving an initial AA-Request from the AF, the PDF allocates Authorization-Token. The PDF shall store the Diameter base protocol Session-Id received in the AA-Request message for the Authorization-Token. If the AA-Request contains the Media-Component-Description At
46、tribute-Value Pair(s) (AVP(s) the PDF shall authorize the required QoS resources and store the SBLP for the session based on the service information. If the AA-Request contains Flow-Grouping AVP(s), the PDF shall only authorize the QoS if the IP flows are distributed to PDP contexts in a way that is
47、 allowed by the Flow-Grouping AVP(s). The PDF sends the allocated token in the Authorization-Token AVP to the AF in the AA-Answer message. 5.1.2 Resource reservation When receiving a bearer authorization request from the Go interface, the PDF shall authorize the request according to the stored SBLP
48、for the session, if available. For a bearer authorization request with a new authorization token the PDF shall behave as described within the present paragraph: If the SBLP is not available for the session, or if the AF has instructed the PDF to do so, the PDF shall send the Re-Auth_Request message
49、with the SERVICE_INFORMATION_REQUEST indication in the Specific-Action AVP to the AF to request the service information. When receiving the Media-Component-Description AVP(s) in the Re-Auth-Answer message, the PDF shall authorize the required QoS resources and shall store the SBLP for the session. If SBLP is available for the session butauthorization for unknown flow identifiers is being requested, and the AF has not instructed the PDF to contact it at bearer authorization, the PDF shall deny the authorization without contact
