ETSI TS 129 217-2017 Universal Mobile Telecommunications System (UMTS) LTE Policy and Charging Control (PCC) Congestion reporting over Np reference point (V14 2 0 3GPP TS 29 217 ve.pdf

1、 ETSI TS 1Universal Mobile TelPolicy andCongestion rep(3GPP TS 29.2TECHNICAL SPECIFICATION129 217 V13.6.0 (2017elecommunications System (LTE; nd Charging Control (PCC); eporting over Np reference po.217 version 13.6.0 Release 1317-01) (UMTS); point 13) ETSI ETSI TS 129 217 V13.6.0 (2017-01)13GPP TS

2、29.217 version 13.6.0 Release 13Reference RTS/TSGC-0329217vd60 Keywords LTE,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 Grass

3、e (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified with

4、out the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of t

5、he 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 documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your c

6、omment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI

7、. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo a

8、re Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade 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 217 V13.6.0 (

9、2017-01)23GPP TS 29.217 version 13.6.0 Release 13Intellectual Property Rights 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

10、 found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IP

11、R Policy, no investigation, including IPR searches, has been 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 Thi

12、s Technical Specification (TS) has been produced by ETSI 3rd 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 correspondi

13、ng ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ ar

14、e to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 217 V13.6.0 (2017-01)33GPP TS 29.217 version 13.6.0 Release 13Co

15、ntents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Np reference point 7g34.1 Overview 7g34.2 Np reference model 8g34.3 Functional elements 8g34.3.1 R

16、CAF 8g34.3.2 PCRF 9g34.3.3 H-PCRF 9g34.3.4 V-PCRF 9g34.4 Procedures over Np reference point . 9g34.4.1 RUCI Report . 9g34.4.1.1 General 9g34.4.1.2 Non-aggregated RUCI report 10g34.4.1.3 Aggregated RUCI report . 10g34.4.2 Reporting Restriction Provisioning . 10g34.4.3 UE mobility between RCAFs . 11g3

17、4.4.4 Removal of UE context . 11g34.4.5 Race condition handling . 12g35 Np protocol . 12g35.1 Protocol support . 12g35.2 Initialization, maintenance and termination of connection and session 12g35.3 Np specific AVPs . 12g35.3.1 General 12g35.3.2 Aggregated-Congestion-Info AVP . 13g35.3.3 Aggregated-

18、RUCI-Report AVP 13g35.3.4 Congestion-Level-Definition AVP . 14g35.3.5 Congestion-Level-Range AVP . 14g35.3.6 Congestion-Level-Set-Id AVP 14g35.3.7 Congestion-Level-Value AVP 14g35.3.8 Congestion-Location-Id AVP . 14g35.3.9 Conditional-Restriction AVP 15g35.3.10 eNodeB-Id AVP 15g35.3.11 IMSI-List AVP

19、 . 15g35.3.12 RCAF-Id AVP 16g35.3.13 Reporting-Restriction AVP . 16g35.3.14 RUCI-Action AVP 16g35.4 Np re-used AVPs 17g35.4.1 General 17g35.4.2 Use of the Supported-Features AVP on the Np reference point . 17g35.5 Np specific Experimental-Result-Code AVP values 18g35.5.1 General 18g35.5.2 Success 18

20、g35.5.3 Permanent Failures . 18g35.5.4 Transient Failures . 18g3ETSI ETSI TS 129 217 V13.6.0 (2017-01)43GPP TS 29.217 version 13.6.0 Release 135.6 Np messages . 19g35.6.1 Non-Aggregated-RUCI-Report-Request (NRR) command 19g35.6.2 Non-Aggregated-RUCI-Report-Answer (NRA) command 19g35.6.3 Aggregated-R

21、UCI-Report-Request (ARR) command 20g35.6.4 Aggregated-RUCI-Report-Answer (ARA) command 20g35.6.5 Modify-Uecontext-Request (MUR) command . 20g35.6.6 Modify-Uecontext-Answer (MUA) command . 21g3Annex A (informative): Change history . 22g3History 23g3ETSI ETSI TS 129 217 V13.6.0 (2017-01)53GPP TS 29.21

22、7 version 13.6.0 Release 13Foreword 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 contents of t

23、he 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 document un

24、der 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 217 V13.6.0 (2017-01)63GPP TS 29.217 versi

25、on 13.6.0 Release 131 Scope The present document provides the stage 3 specification of the Np reference point. The functional requirements and the stage 2 specifications of the Np reference point are contained in 3GPP TS 23.203 2. The Np reference point lies between the RAN Congestion Awareness Func

26、tion (RCAF) and the Policy and Charging Rules Function (PCRF) for the non-roaming case, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario. NOTE: If not specified explicitly, the PCRF also means H-PCRF for the home-routed

27、scenario or V-PCRF in the visited access scenario in the specification. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, v

28、ersion number, etc.) 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 document), a non-specific reference implicitly refers to the latest version

29、of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.203: “Policy and charging control architecture“. 3 3GPP TS 29.213: “Policy and Charging Control signalling flows and QoS parameter mapping“. 4 IETF RFC 4005: “Diameter N

30、etwork Access Server Application“. 5 IETF RFC 4006: “Diameter Credit Control Application“. 6 3GPP TS 29.229: “Cx and Dx interfaces based on Diameter protocol; Protocol details“. 7 IETF RFC 3588: “Diameter Base Protocol“. 8 3GPP TS 23.401: “GPRS enhancements for E-UTRAN access“. 9 3GPP TS 23.060: “Ge

31、neral Packet Radio Service (GPRS); Service description; Stage 2“. 10 3GPP TS 29.215: “Policy and Charging Control (PCC) over S9 reference point; Stage 3“. 11 3GPP TS 29.061: “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“.

32、12 3GPP TS 29.274: “3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)“. 13 ITU-T Recommendation E.212: “The international identification plan for mobile terminals and mobile users“. 14 3GPP TS 29.212: “Policy and Charging Control (PCC); Reference points“. 15 IETF RFC 7683:

33、 “Diameter Overload Indication Conveyance“. 16 IETF RFC 7944: “Diameter Routing Message Priority“. ETSI ETSI TS 129 217 V13.6.0 (2017-01)73GPP TS 29.217 version 13.6.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given

34、in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. Home Routed Access: Roaming scenario where the PCEF is located in the HPLMN. In a Home Routed roaming scenario, the UE obtains acces

35、s to the packet data network from the HPLMN. RAN user plane congestion: RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time. NOTE: Short-duration traffic bursts is a normal condition at any traf

36、fic load level, and is not considered to be RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator configuration) is considered a normal mode of operation and might not be RAN user plane congestion. Visited Access (also known as local breakout): Roaming

37、scenario where the PCEF is located in the VPLMN. In a Visited Access Roaming scenario, the UE obtains access to the packet data network from the VPLMN. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation def

38、ined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. AF Application Function ARR Aggregated RUCI Report Request ARA Aggregated RUCI Report Answer DRMP Diameter Routing Message Priority H-PCRF Home PCRF MUR Modify Uecontext Request M

39、UA Modify Uecontext Answer NRR Non-Aggregated RUCI Report Request NRA Non-Aggregated RUCI Report Answer PCC Policy and Charging Control PCRF Policy and Charging Rule Function RCAF RAN Congestion Awareness Function RUCI RAN User Plane Congestion Information V-PCRF Visited PCRF 4 Np reference point 4.

40、1 Overview The Np reference point is located between the RCAF and the PCRF for the non-roaming scenario, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario. The Np reference point is used for: - Reporting the RUCI from the

41、 RCAF to the PCRF; - Provisioning the Reporting Restriction from the PCRF to the RCAF; - The User Equipment (UE) mobility between RCAFs; - The removal of the UE context in the RCAF. ETSI ETSI TS 129 217 V13.6.0 (2017-01)83GPP TS 29.217 version 13.6.0 Release 13The stage 2 level requirements for the

42、Np reference point are defined in 3GPP TS 23.203 2. Signalling flows related to Np interface are specified in 3GPP TS 29.213 3. Refer to Annex G of 3GPP TS 29.213 3 for Diameter overload control procedures over the Np interface. Refer to Annex J of 3GPP TS 29.213 3 for Diameter message priority mech

43、anism procedures over the Np interface. 4.2 Np reference model The relationships between the involved functional entities are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 3 . PCRFg3Npg3RCAFg3Figure 4.2.1: Np reference model NOTE: For the home-rout

44、ed access scenario, the RCAF interacts with the H-PCRF. For the visited access scenario, the RCAF interacts with the V-PCRF. Figure 4.2.2: Void Figure 4.2.3: Void 4.3 Functional elements 4.3.1 RCAF The RCAF is a functional element which reports RAN User Plane Congestion Information (RUCI) via the Np

45、 interface to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. RUCI includes the following information: - The user id (e.g. IMSI) identifying the UE impacted by congestion; - PDN ID for which congestion information is reported; - Congestion

46、level information (either congestion level value or congestion level set id) of the UE impacted by congestion; - eNodeB identifier, ECGI or SAI identifying the eNodeB, E-UTRAN cell or Service Area respectively, serving the UE if a conditional restriction to restrict location reporting is not enabled

47、. NOTE 1: In case of E-UTRAN, whether the eNodeB identifier or the ECGI are included in the RUCI is up to operator configuration in the RCAF. The RCAF sends the RUCI to the PCRFs serving the UEs PDN connections as follows: - For a PDN connection in a non-roaming scenario the RCAF reports the RUCI to

48、 the PCRF; - For a PDN connection in a local breakout scenario, based on operator configuration, the RCAF reports the RUCI to the V-PCRF; - For a PDN connection in a home routed scenario, based on the roaming agreement with the HPLMN and operator configuration, the RCAF reports the RUCI to the H-PCR

49、F NOTE 2: Reporting of congestion information to the HPLMN may be used e.g. in case of a group of PLMNs which belong to a single business entity. ETSI ETSI TS 129 217 V13.6.0 (2017-01)93GPP TS 29.217 version 13.6.0 Release 13The RCAF determines whether a given PDN connection is served in a local breakout or a home routed roaming scenario based on the APN operator identifier received as part of the APN information from the MME or the SGSN as documented in 3GPP TS 23.401 8 and 3GPP TS 23.060 9, respectively. NOTE 3: Opera