Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC) over S9 reference point; Stage 3 (3GPP TS 29.215 version 15.2.0 Release 15)

RTS/TSGC-0329215vf20

General Information

Status
Published
Publication Date
09-Oct-2019
Current Stage
12 - Completion
Completion Date
10-Oct-2019
Ref Project

Buy Standard

Standard
ETSI TS 129 215 V15.2.0 (2019-10) - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC) over S9 reference point; Stage 3 (3GPP TS 29.215 version 15.2.0 Release 15)
English language
91 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 129 215 V15.2.0 (2019-10)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and Charging Control (PCC) over S9 reference point;
Stage 3
(3GPP TS 29.215 version 15.2.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 29.215 version 15.2.0 Release 15 1 ETSI TS 129 215 V15.2.0 (2019-10)



Reference
RTS/TSGC-0329215vf20
Keywords
GSM,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 enregistrée à la
Sous-Préfecture de Grasse (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 without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment 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.
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.

© ETSI 2019.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 29.215 version 15.2.0 Release 15 2 ETSI TS 129 215 V15.2.0 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 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 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This 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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 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 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

---------------------- Page: 3 ----------------------
3GPP TS 29.215 version 15.2.0 Release 15 3 ETSI TS 129 215 V15.2.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 8
1 Scope . 9
2 References . 9
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 10
4 S9 Reference Point . 11
4.1 Overview . 11
4.2 Reference model . 11
4.3 Functional ele me nts . 12
4.3.1 H-PCRF . 12
4.3.1.0 General . 12
4.3.1.1 Home routed access . 12
4.3.1.2 Visited Access . 13
4.3.2 V-PCRF . 13
4.3.2.0 General . 13
4.3.2.1 Home routed access. 13
4.3.2.2 Visited access . 13
4.4 PCC, QoS, and IP flow mobility routing Rules and NBIFOM routing Rules . 14
4.4.1 PCC Rule definition . 14
4.4.2 QoS Rule definition . 15
4.4.2a IP flow mobility routing Rule definition. 15
4.4.2b Void . 15
4.4.2c NBIFOM routing Rule definition . 15
4.4.3 Operations on PCC rules . 15
4.4.4 Operations on QoS Rules . 15
4.4.5 Operations on IP flow mobility routing Rules . 15
4.4.6 Void . 16
4.4.7 Operations on NBIFOM routing Rules . 16
4.5 PCC procedures over S9 Reference Point . 16
4.5.1 General . 16
4.5.1.1 S9 Session Establishment . 16
4.5.1.2 S9 Session Termination . 17
4.5.1.3 Event Triggers . 17
4.5.1.3.1 Provisioning of Event Triggers . 17
4.5.1.3.2 Reporting of deployed Event Triggers . 18
4.5.1.4 Multiple BBERF scenarios . 18
4.5.1.5 Provisioning and validation of Default EPS Bearer authorized QoS . 18
4.5.1.6 Provisioning of Authorized QoS per APN . 19
4.5.1.7 Bearer Control Mode Selection . 20
4.5.1.8 Access Network Information Reporting . 20
4.5.2 Home-Routed access. 20
4.5.2.1 S9 Session/Subsession establishment/modification . 20
4.5.2.2 Provision of QoS Rules by the H-PCRF . 22
4.5.2.3 S9 Session/Subsession Termination Initiated by the V-PCRF . 23
4.5.2.4 S9 Session/Subsession Termination Initiated by the H-PCRF . 23
4.5.2.5 Multiple BBERF Handling . 24
4.5.2.5.1 General . 24
4.5.2.5.2 Handling of multiple BBERFs associated with the same IP-CAN session during handover . 24
4.5.2.5.3 Handling of two BBERFs with flow mobility within the same IP-CAN session . 25
4.5.2.6 Deferred Session Linking Handling . 25
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.215 version 15.2.0 Release 15 4 ETSI TS 129 215 V15.2.0 (2019-10)
4.5.2.7 Session Linking Handling When Multiple PDN Connection to a single APN is supported . 26
4.5.3 Visited Access . 26
4.5.3.1 Request PCC and QoS Rules . 26
4.5.3.2 PCC and QoS Rules Provisioning . 29
4.5.3.3 S9 Session/Subsession Termination Initiated by V-PCRF. . 30
4.5.3.4 S9 Session/Subsession Termination Initiated by the H-PCRF. . 31
4.5.3.5 Multiple BBERF Handling . 31
4.5.3.6 Rx Over S9 . 32
4.5.3.6.1 General . 32
4.5.3.6.2 Event Handling . 32
4.5.3.6.2.1 V-AF Subscription to Notification of Signalling Path Status . 32
4.5.3.6.2.2 Reporting of Signalling Path Status . 32
4.5.3.6.2.3 Reporting IP-CAN Type Change Notification . 32
4.5.3.7 Deferred Session Linking Handling . 33
4.5.3.8 Session Linking Handling When Multiple PDN Connection to a single APN is supported . 33
4.5.3.9 IP flow mobility support . 34
4.5.3.10 Application Detection and Control . 34
4.5.3.10.1 General . 34
4.5.3.10.2 Void . 35
4.5.3.10.3. Void . 35
4.5.3.10.4. Application Detection Information . 35
4.5.3.10.5. ADC Rule Derivation . 35
4.5.3.11 NBIFOM support . 36
4.5.4 IMS Emergency services . 36
4.5.5 Extended bandwidth support for EPC supporting Dual Connectivity (E-UTRAN and 5G NR) . 36
5. S9 Protocol . 37
5.1 Protocol Support . 37
5.2 Initialization, maintenance and termination of connection and session. 37
5.3 S9 specific AVPs . 38
5.3.0 General . 38
5.3.1 Subsession-Decision-Info . 38
5.3.2 Subsession-Enforcement-Info . 39
5.3.3 Subsession-Id . 40
5.3.4 Subsession-Operation . 40
5.3.5 Void . 40
5.3.6 Multiple-BBERF-Action . 40
5.3.7 DRA-Deployment . 41
5.3.8 DRA-Binding . 41
5.4 S9 re-used AVPs . 41
5.4.0 General . 41
5.4.1 Use of the Supported-Features AVP on the S9 reference point . 41
5.5 S9 Messages . 44
5.5.1 S9 Application . 44
5.5.2 CC-Request (CCR) Command . 44
5.5.3 CC-Answer (CCA) Command . 45
5.5.4 Re-Auth-Request (RAR) Command . 45
5.5.5 Re-Auth-Answer (RAA) Command . 46
5.5.7 Trigger-Establishment-Request (TER) Command . 46
5.5.8 Trigger-Establishment-Answer (TEA) Command . 47
5.6 S9 specific Experimental-Result-Code AVP values . 47
5.6.1 General . 47
5.6.2 Success . 47
5.6.3 Permanent Failures . 47
5.6.4 Transient Failures . 47
Annex A (normative): Access specific aspects, Fixed Broadband Access interworking with
EPC . 49
A.1 Scope . 49
A.2 Definitions and abbreviations . 49
A.2.1 Definitions . 49
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.215 version 15.2.0 Release 15 5 ETSI TS 129 215 V15.2.0 (2019-10)
A.2.2 Abbreviations . 49
A.3 Reference points and Reference model . 49
A.3.0 General . 49
A.3.1 S9a Reference Point . 50
A.3.2 S9 Reference Point . 50
A.3.3 Reference Model . 50
A.4 Functional Elements . 59
A.4.0 PCRF . 59
A.4.1 V-PCRF . 60
A.4.2 H-PCRF . 61
A.4.3 BPCF . 61
A.5 PCC procedures over S9a Reference Point . 62
A.5.1 Session Establishment over S9a . 62
A.5.1.1 EPC-Routed traffic . 62
A.5.1.1.1 S9a Session Establishment Trigger by PCRF . 62
A.5.1.1.2 S9a Session Establishment . 63
A.5.1.2 NSWO traffic . 63
A.5.1.2.1 S9a* Session Establishment . 63
A.5.2 Session Termination over S9a . 63
A.5.2.1 EPC-Routed Traffic . 63
A.5.2.1.1 S9a Session Termination initiated by the (V-) PCRF . 63
A.5.2.2 NSWO Traffic . 64
A.5.2.2.1 S9a* Session Termination initiated by the BPCF . 64
A.5.2.2.2 S9a* Session Termination initiated by the (V-) PCRF . 64
A.5.3 Session Modification over S9a . 65
A.5.3.1 EPC-Routed traffic . 65
A.5.3.1.1 S9a Session Modification initiated by the (V-) PCRF . 65
A.5.3.1.2 S9a Session Modification initiated by the BPCF . 65
A.5.3.2 NSWO traffic . 66
A.5.3.2.1 S9a* Session Modification initiated by the (V-) PCRF . 66
A.5.3.2.2 S9a* Session Modification initiated by the BPCF . 66
A.5.4 Handling of QoS information . 66
A.5.4.1 EPC-routed traffic . 66
A.5.4.2 NSWO traffic . 66
A.6 PCC procedures over S9 Reference Point . 67
A.6.1 Session Establishment over S9 . 67
A.6.1.1 EPC-Routed Traffic . 67
A.6.1.1.1 S9 Session Establishment Triggered by H-PCRF . 67
A.6.1.1.2 S9 Session Establishment . 67
A.6.1.2 NSWO Traffic . 68
A.6.2 Session Termination over S9 . 68
A.6.2.1 EPC-Routed traffic . 68
A.6.2.1.1 S9 Session Termination initiated by the H-PCRF . 68
A.6.2.1.2 S9 Session Termination initiated by the V-PCRF . 68
A.6.2.2 NSWO Traffic . 69
A.6.2.2.1 S9 Session Termination initiated by the V-PCRF . 69
A.6.2.2.2 S9 Session Termination initiated by
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.