1、 ETSI TS 1Universal Mobile TelService capabover(3GPP TS 29.1TECHNICAL SPECIFICATION129 154 V13.1.0 (2016elecommunications System (LTE; ability exposure functionalityer Nt reference point .154 version 13.1.0 Release 1316-04) (UMTS); ity 13) ETSI ETSI TS 129 154 V13.1.0 (2016-04)13GPP TS 29.154 versio
2、n 13.1.0 Release 13Reference RTS/TSGC-0329154vd10 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 Grasse (06) N 7803
3、/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 without the prior
4、 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 the present do
5、cument 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the fo
6、llowing 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. The content of the PD
7、F 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 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI
8、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 154 V13.1.0 (2016-04)23GPP TS 29.154
9、 version 13.1.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 found in ETSI SR 000 3
10、14: “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 IPR Policy, no investigat
11、ion, 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 This Technical Specificati
12、on (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 corresponding ETSI deliverables. T
13、he 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“ are to be interpreted as
14、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 154 V13.1.0 (2016-04)33GPP TS 29.154 version 13.1.0 Release 13Contents Intellectual Pro
15、perty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Nt reference point . 6g34.1 Overview 6g34.2 Nt Reference Model . 6g34.3 Functional elements 6g
16、34.3.1 PCRF 6g34.3.2 SCEF. 7g34.4 Procedures over the Nt reference point 7g34.4.1 Negotiation for future background data transfer . 7g34.5 PCRF selection . 7g35 Nt protocol 8g35.1 Protocol support . 8g35.2 Initialization, maintenance and termination of connection and session 8g35.3 Nt specific AVPs
17、8g35.3.1 General 8g35.3.2 Network-Area-Info-List AVP . 9g35.3.3 Reference-Id AVP. 9g35.3.4 Transfer-Request-Type AVP 9g35.3.5 Time-Window AVP 9g35.3.6 Transfer-End-Time AVP 9g35.3.7 Transfer-Start-Time AVP . 9g35.3.8 Transfer-Policy AVP 9g35.3.9 Transfer-Policy-Id AVP 10g35.3.10 Number-Of-UEs AVP. 1
18、0g35.4 Nt re-used AVPs . 10g35.4.1 General 10g35.4.2 Use of the Supported-Features AVP on the Nt reference point 11g35.5 Nt specific Experimental-Result-Code AVP values . 11g35.5.1 General 11g35.5.2 Success 11g35.5.3 Permanent Failures . 11g35.5.4 Transient Failures . 12g35.6 Nt messages 12g35.6.1 C
19、ommand-Code Values 12g35.6.2 Background-Data-Transfer-Request (BTR) command . 12g35.6.3 Background-Data-Transfer-Answer (BTA) command . 12g3Annex A (informative): Change history . 14g3History 15g3ETSI ETSI TS 129 154 V13.1.0 (2016-04)43GPP TS 29.154 version 13.1.0 Release 13Foreword This Technical S
20、pecification (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 corresponding ETSI deliv
21、erables. 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“ are to be inter
22、preted 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. The contents of the present document are subject to continuing work within the TSG and may cha
23、nge 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 increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 pres
24、ented 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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in
25、 the document. ETSI ETSI TS 129 154 V13.1.0 (2016-04)53GPP TS 29.154 version 13.1.0 Release 131 Scope This document defines the protocol for Nt reference point. The functional requirements and the stage 2 specifications of the Nt reference point are contained in 3GPP TS 23.203 2. The Nt reference po
26、int lies between Service Capability Exposure Function (SCEF) and Policy and Charging Rules Function (PCRF). 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 da
27、te of publication, edition number, version 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 impl
28、icitly 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.203: “Policy and charging control architecture“. 3 IETF RFC 3588: “Diameter Base Protocol“. 4 IETF RFC 4006: “Diameter Credit Control
29、 Application“. 5 3GPP TS 29.214: “Policy and Charging Control over Rx reference point“. 6 3GPP TS 29.274: “3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)“. 7 IETF RFC 5719: “Updated IANA Considerations for Diameter Command Code Allocations “. 8 IETF RFC 2234: “Augmented
30、 BNF for syntax specifications “. 9 3GPP TS 29.213: “Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping“. 10 IETF RFC 7683: “Diameter Overload Indication Conveyance“. 11 3GPP TS 29.229: “Cx and Dx interfaces based on Diameter protocol; Protocol details“. 12 I
31、ETF draft-ietf-dime-drmp-02: “Diameter Routing Message Priority“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.90
32、5 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. ETSI ETSI TS 129 154 V13.1.0 (2016-04)63GPP TS 29.154 version 13.1.0 Release 133.2 Abbreviations For the purposes of the present document, the abbre
33、viations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. ASP Application Service Provider BTA Background Data Transfer Answer BTR Background Data Transfer Request
34、 DRA Diameter Routing Agent DRMP Diameter Routing Message Priority PCRF Policy and Charging Rules Function SCEF Service Capability Exposure Function SPR Subscription Profile Repository 4 Nt reference point 4.1 Overview The Nt reference point is located between the PCRF and the SCEF. The Nt reference
35、 point is used for: - Reporting the transfer policies from the PCRF to the SCEF; The stage 2 requirements for Nt reference point are defined in TS 23.203 2. Refer to Annex G of 3GPP TS 29.213 9 for Diameter overload control procedures over the Nt interface. Refer to Annex J of 3GPP TS 29.213 9 for D
36、iameter message priority mechanism procedures over the Nt interface. 4.2 Nt Reference Model The Nt reference point resides between the SCEF and PCRF. The relationship between the two functional entities is depicted in figure 4.2-1. The overall PCC architecture is depicted in subclause 3a of 3GPP TS
37、29.213 9. SCEFg3Ntg3PCRFg3Figure 4.2-1: Nt reference model NOTE: For roaming case, the SCEF is always in the H-PLMN and always contact the H-PCRF. 4.3 Functional elements 4.3.1 PCRF The PCRF is a functional element that encompasses policy control decision and flow based charging control functionalit
38、ies. The PCRF shall use the information received from SCEF and other available information to determine one or more transfer policies for background data to the application service provider. The PCRF shall provide the transfer policies to SCEF together with a reference ID. The PCRF receives the sele
39、cted transfer policy from the SCEF and stores it in the SPR together with the reference ID. ETSI ETSI TS 129 154 V13.1.0 (2016-04)73GPP TS 29.154 version 13.1.0 Release 134.3.2 SCEF The SCEF is a functional element which provides a means to securely expose the services and capabilities provided by 3
40、GPP network interfaces. The SCEF is triggered by an AF which requests for the negotiation with the PCRF for providing necessary policy to transfer background data. 4.4 Procedures over the Nt reference point 4.4.1 Negotiation for future background data transfer Based on the SCS/AS request, the SCEF s
41、hall send the Background-Data-Transfer-Request (BTR) command including the Transfer-Request-Type AVP with the value TRANSFER_POLICY_REQUEST(0), it shall also include the ASP identifier within the Application-Service-Provider-Identity AVP, volume of data per UE within the CC-Output-Octets AVP for dow
42、nlink volume and/or the CC-Input-Octets AVP for uplink volume, or the CC-Total-Octets AVP for total volume regardless direction, expected number of UEs within the Number-Of-UEs AVP and desired time window within the Time-Window AVP. The Time-Window AVP shall include desired start time within the Tra
43、nsfer-Start-Time AVP and desired end time within the Transfer-End-Time AVP. The SCEF may also provide network area information within Network-Area-Information-List AVP. Once the PCRF receives the BTR command, the PCRF shall retrieve all existing transfer policies stored for any ASP from the SPR. Whe
44、n all existing transfer policies are retrieved, the PCRF shall determine one or more transfer policies based on the information received from the SCEF and other available information (e.g. network policy, congestion level (if available), load status estimation for the required time window and networ
45、k area, existing transfer policies) and respond with a Background-Data-Transfer-Answer (BTA) command including the possible transfer policies within Transfer-Policy AVP (s) and a reference ID within Reference-Id AVP. The Transfer-Policy AVP(s) shall include the Time-Window AVP, the Rating-Group AVP,
46、 it may also include an Max-Requested-Bandwidth-DL AVP and/or an Max-Requested-Bandwidth-UL AVP. NOTE 1: If only one Transfer-Policy AVP is included in the BTA command, the PCRF sends a request to the SPR to store the reference ID together with the transfer policy and corresponding network area info
47、rmation(if available). If there are more than one Transfer-Policy AVPs included in the BTA command, the PCRF waits for the transfer policy selected by the SCS/AS before communicating with the SPR. If there is more than the one transfer policy provided from the PCRF to the SCEF in the BTA command, wh
48、en the SCEF receives the selected transfer policy from the SCS/AS, the SCEF shall send Background-Data-Transfer-Request (BTR) command to the PCRF including the Transfer-Request-Type AVP set to the value TRANSFER_POLICY_NOTIFICATION (1), the SCEF shall also include the reference ID in the Reference-I
49、d AVP and the identity of the selected transfer policy within the Transfer-Policy-ID AVP. NOTE 2: When receiving the BTA command from the PCRF, if there is only one transfer policy included, the SCEF forwards the transfer policy to SCS/AS. If there is more than the one transfer policy included, the SCEF forwards these transfer policies to the SCS/AS and waits for the answer including the identity of the transfer policy selected by the SCS/AS. The PCRF shall acknowledge the BTR command by sending Background-Data-Transfer-Answer (BTA)
