ETSI TS 129 211-2007 Universal Mobile Telecommunications System (UMTS) Rx Interface and Rx Gx signalling flows (V6 4 0 3GPP TS 29 211 version 6 4 0 Release 6)《全球移动通信系统(UMTS) Rx接口和R.pdf

1、 ETSI TS 129 211 V6.4.0 (2007-06)Technical Specification Universal Mobile Telecommunications System (UMTS);Rx Interface and Rx/Gx signalling flows (3GPP TS 29.211 version 6.4.0 Release 6)ETSI ETSI TS 129 211 V6.4.0 (2007-06) 1 3GPP TS 29.211 version 6.4.0 Release 6 Reference RTS/TSGC-0329211v640 Key

2、words UMTS 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 doc

3、ument can 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 disp

4、ute, the 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 E

5、TSI documents 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 wri

6、tten permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo a

7、re Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 129 211 V6.4.0 (2007-06) 2 3GPP TS 29.211 version 6.4.0 Release 6 Intellectual Property Rig

8、hts IPRs essential 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

9、, or potentially 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:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been

10、 carried out by ETSI. No guarantee 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

11、 Generation Partnership Project (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,

12、 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 211 V6.4.0 (2007-06) 3 3GPP TS 29.211 version 6.4.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions

13、6 3.2 Abbreviations .7 4 Rx reference point 7 4.1 Overview 7 4.2 Rx reference model 8 4.3 Functional elements and capabilities9 4.3.1 Charging Rules Function (CRF) .9 4.3.2 Application Function (AF)9 5 FBC Procedures over Rx9 5.1 CRF 9 5.1.1 Initial Provision of Session Information .9 5.1.2 Modifica

14、tion of Session Information 9 5.1.3 FBC Gate function10 5.1.4 AF Session Termination .10 5.1.5 Bearer Release 10 5.1.6 Other Bearer Events10 5.2 AF.10 5.2.1 Provision of Service Information at session establishment.10 5.2.2 Session modification.11 5.2.3 FBC Gate function11 5.2.4 Void 11 5.2.5 AF Ses

15、sion Termination .11 5.2.6 Bearer Release 11 5.2.7 Other Bearer Events11 6 Binding the AF Session Information to the Bearers.11 7 Rx Protocol.12 7.1 Protocol Support.12 7.1.1 Advertising application support12 7.1.2 Experimental-Result-Code AVP values12 7.2 Securing Diameter messages12 7.3 Rx message

16、s .13 7.3.1 AA-Request (AAR) command13 7.3.2 AA-Answer (AAA) command13 7.3.3 Re-Auth-Request (RAR) command13 7.3.4 Re-Auth-Answer (RAA) command 14 7.3.5 Session-Termination-Request (STR) command .14 7.3.6 Session-Termination-Answer (STA) command14 7.3.7 Abort-Session-Request (ASR) command .15 7.3.8

17、Abort-Session-Answer (ASA) command15 7.4 Re-used AVPs for Rx Protocol.15 8 Rx/Gx Signalling Flows .17 8.1 AF session establishment or modification17 8.2 Request of Charging Rule 19 8.3 Removal of Charging Rules at AF session release.21 8.4 Bearer Release22 ETSI ETSI TS 129 211 V6.4.0 (2007-06) 4 3GP

18、P TS 29.211 version 6.4.0 Release 6 Annex A (normative): Support for SIP forking 26 A.1 Resources for early media for forked responses.26 A.2 Updating the Charging Rules information at the final answer .26 Annex B (informative): Change history .27 History 28 ETSI ETSI TS 129 211 V6.4.0 (2007-06) 5 3

19、GPP TS 29.211 version 6.4.0 Release 6 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership 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 co

20、ntents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase 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

21、document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 211 V6.4.0 (2007-06) 6 3GPP TS

22、29.211 version 6.4.0 Release 6 1 Scope The present document provides the stage 3 specification of the Rx reference point interface. The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.125 2. The Rx reference point is used to exchange Flow

23、Based Charging information between the Charging Rules Function (CRF) and the Application Function (AF). Whenever it is possible the present document specifies the protocol by reference to specifications produced by the IETF within the scope of Diameter and to the Gq specification 3GPP TS 29.209 4. T

24、he present specification also provides detailed signalling flows for FBC procedures over the interfaces that correspond to Rx and Gx reference points. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Referen

25、ces 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 reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM d

26、ocument), 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 23.125: “Overall high level functionality and architecture impacts of flow based charging; Stage

27、2“. 3 3GPP TS 29.210: “Charging rule provisioning over Gx interface“. 4 3GPP TS 29.209: “Policy control over Gq interface“. 5 IETF RFC 3588: “Diameter Base Protocol“. 6 3GPP TS 33.210: “3G Security; Network Domain Security (NDS); IP network layer security“. 7 IETF RFC 4005: “Diameter Network Access

28、Server Application“. 8 IETF RFC 4006: “Diameter Credit Control Application“. 9 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 3 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 3GPP TS 23.125 2

29、and the following apply: Application Function (AF): element offering application(s) that use IP bearer resources. NOTE: One example of an AF is the P-CSCF of the IM CN subsystem. ETSI ETSI TS 129 211 V6.4.0 (2007-06) 7 3GPP TS 29.211 version 6.4.0 Release 6 AF Session: an application level session e

30、stablished by an application level signalling protocol offered by the AF that requires 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. Attribute-Value Pair (AVP): See RFC 3588 5, corresponds to an Inform

31、ation Element in a Diameter message. Binding: the CRF process of associating IP flows described in AF Service Information with bearers. IP flow: a unidirectional flow of IP packets with the same source IP address and port number and the same destination IP address and port number and the same transp

32、ort protocol. Port numbers are only applicable if used by the transport protocol. Packet Flow: a specific user data flow carried through the Traffic Plane Function. A Packet Flow can be an IP flow. Service Information: The set of information conveyed from the AF to the CRF over the Rx interface to b

33、e used as a basis for Flow Based Charging decisions at the CRF, including information about the AF session (e.g. application identifier, type of media, bandwidth, IP address and port number) and parameters controlling the CRF behavior. The encoding of the Service Information is provided in 3GPP TS 2

34、9.209 4. 3.2 Abbreviations For the purposes 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-Answer ASR Abort-Session-Request AVP Attribute-Value PairCCA Credit-Control-Answer CCR Cred

35、it-Control-Request CRF Charging Rules Function FBC Flow Based Charging IANA Internet Assigned Numbers Authority IM IP Multimedia RAA Re-Auth-Answer RAR Re-Auth-Request STA Session-Termination-Answer STR Session-Termination-RequestTPF Traffic Plane Function 4 Rx reference point 4.1 Overview The Rx in

36、terface is used to exchange Flow Based Charging control information between the Charging Rules Function (CRF) and the Application Function (AF). As defined in the stage 2 specifications (3GPP TS 23.125 2), this information is used by the CRF for the Flow Based Charging (FBC) decisions. The CRF excha

37、nges the Flow Based Charging control information with the Traffic Plane Function (TPF) as specified in 3GPP TS 29.210 3. The Rx interface may be an intra- or inter-domain interface. One CRF shall be able to serve more than one AF and one given AF may interact with a number of CRFs, although on an AF

38、 session basis, it shall interact with only a single CRF. ETSI ETSI TS 129 211 V6.4.0 (2007-06) 8 3GPP TS 29.211 version 6.4.0 Release 6 Signalling flows related to the both Rx and Gx interfaces are specified in clause 8 in this specification. 4.2 Rx reference model The Rx interface is defined betwe

39、en the CRF and the AF. The CRF is in the same PLMN as the TPF. The relationships between the different functional entities involved are depicted in figure 4.1a and 4.1b Traffic Plane Function (TPF) Gx Online Charging SystemService Data Flow Based Credit Control Charging Rules Function (CRF) CAMEL SC

40、P Gy Rx AF Figure 4.1a: Rx interface architecture model for service data flow based online bearer charging Traffic Plane Function (TPF) Offline Charging System Gx Charging Rules Function (CRF) Gz Rx AF Figure 4.1b: Rx interface architecture model for service data flow based offline bearer charging E

41、TSI ETSI TS 129 211 V6.4.0 (2007-06) 9 3GPP TS 29.211 version 6.4.0 Release 6 4.3 Functional elements and capabilities 4.3.1 Charging Rules Function (CRF) The Charging Rules Function provides Service Data Flow level Charging Rules to the TPF and informs AF about bearer session events. The CRF makes

42、the Charging Rule decisions which may be based on the session and media related information obtained from the AF via the Rx reference point, the bearer and subscriber related information obtained from the TPF over the Gx reference point, and subscriber and service related data the CRF may be aware o

43、f. The CRF shall provision Charging Rules the TPF via the Gx reference point. The CRF may also provide policy control like functions based on Charging Rules provisioning to the TPF. The CRF reports, via the Rx reference point, bearer events from the TPF to the AF, e.g. bearer release and bearer esta

44、blishment. 4.3.2 Application Function (AF) The AF is an element offering applications that require the Flow Based Charging of IP bearer resources (e.g. UMTS PS domain/GPRS domain resources). One example of an application function is the P-CSCF. The AF shall use the Rx reference point to provide sess

45、ion information to the CRF. 5 FBC Procedures over Rx 5.1 CRF 5.1.1 Initial Provision of Session Information When receiving an initial AA-Request from the AF, the CRF shall check if it contains the Media-Component-Description Attribute-Value Pair(s) (AVP(s) and if so, the CRF shall store the received

46、 Service Information. If the Specific Action AVP is present in the AAR command the CRF shall store the requested notification for the related bearers. The CRF shall check whether the received Service Information requires Charging Rules to be provisioned towards existing bearer(s). The CRF identifies

47、 suitable bearers using the binding mechanisms described in clause 6. If the CRF identifies that Charging Rules need to be provisioned, the CRF shall immediately send a Diameter RA-Request to the TPF for each of the affected bearer(s) to trigger the TPF to request Charging Rules using a Diameter CC-

48、Request. The CRF shall provide the Charging Rules to the TPF within the CC-Answer. The CRF shall then send an AA Answer back to the AF. If the CRF needs to terminate the Rx session before it has sent the AA Answer, the CRF shall send the AA Answer immediately and before the AS Request. 5.1.2 Modific

49、ation of Session Information If the AA-Request from the AF is received for a Diameter session already active (due to an AF session modification), the CRF shall update the Service Information with the new information received. Due to the updated Service Information, the CRF may send a Diameter RA-Request to the TPF for each of the affected bearer(s) to trigger the TPF to request Charging Rules using a Diameter CC-Request. The CRF shall use the CC-Answer to install new Charging Rules and/or, to modify or remove the currently installed Ch