ETSI TS 183 060 V2.1.1 (2009-04)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Subsystem (RACS); Re interface based on the DIAMETER protocol

DTS/TISPAN-03118-NGN-R2

General Information

• Status: Published
• Publication Date: 16-Apr-2009
• Technical Committee: TISPAN 3 - TISPAN Protocols
• Current Stage: 12 - Completion
• Due Date: 10-Apr-2009
• Completion Date: 17-Apr-2009

Standards Content (Sample)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Resource and Admission Control Subsystem (RACS);
Re interface based on the DIAMETER protocol

2 ETSI TS 183 060 V2.1.1 (2009-04)

Reference
DTS/TISPAN-03118-NGN-R2
Keywords
interface, network, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
Individual copies of the present document 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 dispute, 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 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 following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being 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
3 ETSI TS 183 060 V2.1.1 (2009-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Overview . . 8
5 Procedure descriptions . 9
5.1 General . 9
5.2 A-RACF initiated procedures . 11
5.2.1 Procedures at the A-RACF . 11
5.2.1.1 High level description . 11
5.2.1.2 Initial Policy Installation Request . 11
5.2.1.3 Policy modification request . 13
5.2.1.4 Policy termination request . 13
5.2.1.5 Event notification . 14
5.2.1.5.1 Events . 14
5.2.1.5.2 Event subscription . 14
5.2.1.5.3 Event notification . 14
5.2.1.6 Policy Query Request . 15
5.2.2 Procedures at the RCEF . 16
5.2.2.1 High level description . 16
5.2.2.2 Initial policy installation request . 16
5.2.2.3 Policy modification request . 19
5.2.2.4 Policy termination request . 21
5.2.2.5 Event notification . 22
5.2.2.6 Policy Query Request . 23
5.3 RCEF initiated procedures . 25
5.3.1 Procedures at the A-RACF . 25
5.3.1.1 High level description . 25
5.3.1.2 Traffic policy activation request . 25
5.3.1.3 Traffic policy modification request . 25
5.3.1.4 Traffic policy deactivation request . 26
5.3.2 Procedures at the RCEF . 26
5.3.2.1 High level description . 26
5.3.2.2 Traffic policy activation request . 26
5.3.2.3 Traffic policy modification request . 27
5.3.2.4 Traffic Policy Deactivation Request . 27
6 Use of the DIAMETER base protocol. 27
6.1 Securing DIAMETER messages . 27
6.2 Accounting functionality . 27
6.3 Use of sessions . 28
6.4 Transport protocol . 28
6.5 Routing considerations . 28
6.6 Advertising Application support . 28
7 DIAMETER application. 29
7.1 Commands . 29
7.1.1 Policy-Install-Request (PIR) command . 29
7.1.2 Policy-Install-Answer (PIA) command . 30
ETSI
4 ETSI TS 183 060 V2.1.1 (2009-04)
7.1.3 CC-Request (CCR) command. 30
7.1.4 CC-Answer (CCA) Command . 31
7.2 Experimental-Result-Code AVP values . 31
7.2.1 Success . 31
7.2.2 Transient failures . 32
7.2.3 Permanent failures . 32
7.3 AVPs . 33
7.3.1 AVPs Defined in the Present Document . 33
7.3.1.1 Policy-Rule-Install AVP . 33
7.3.1.2 Policy-Rule-Remove AVP . 33
7.3.1.3 Policy-Rule-Definition AVP . 33
7.3.1.4 Policy-Rule-Base-Name AVP . 34
7.3.1.5 Policy-Rule-Name AVP . 34
7.3.1.6 Policy-Rule-Report AVP . 34
7.3.1.7 Policy-Rule-Status AVP . 35
7.3.1.8 Traffic-Flow AVP . 35
7.3.1.9 Policy-Update-Request AVP. 35
7.3.2 AVPs imported from ITU-T NGN-GSI/DOC - 127 . 36
7.3.2.1 Traffic-Descriptor-UL AVP (ITU-T NGN-GSI/DOC - 127) . 36
7.3.2.2 Traffic-Descriptor-DL AVP (ITU-T NGN-GSI/DOC - 127) . 36
7.3.2.3 Maximum-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) . 36
7.3.2.4 Committed-Data-Rate AVP (ITU-T NGN-GSI/DOC - 127) . 36
7.3.2.5 Committed-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) . 37
7.3.2.6 Excess-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) . 37
7.3.2.7 PI-Request-Type AVP (ITU-T NGN-GSI/DOC - 127) . 37
7.3.2.8 PI-Request-Number AVP (ITU-T NGN-GSI/DOC - 127). 37
7.3.3 AVPs Imported From TS 129 212 . 37
7.3.3.1 QoS-Information AVP (TS 129 212) . 38
7.3.3.2 ToS-Traffic-Class AVP (TS 129 212). 38
7.3.3.3 Event-Trigger AVP (TS 129 212) . 38
7.3.3.4 Precedence AVP (TS 129 212) . 39
7.3.3.5 Reporting-Level AVP (TS 129 212) . 39
7.3.3.6 Rule-Failure-Code AVP . 40
7.3.4 AVPs imported from RFC 4006 . 40
7.3.5 AVPs imported from TS 129 209 . 41
7.3.5.1 Flow-Description AVP (TS 129 209) . 41
7.3.5.2 Flow-Number AVP (TS 129 209) . 42
7.3.5.3 Flows AVP (TS 129 209) . 42
7.3.5.4 Flow-Status AVP (TS 129 209) . 42
7.3.6 AVPs Imported From RFC 4005 . 42
7.3.6.1 Called-Station-Id AVP (RFC 4005) . 43
7.4 Use of namespaces . 43
7.4.1 AVP codes . 43
7.4.2 Experimental-Result-Code AVP values . 43
7.4.3 Command Code values . 43
7.4.4 Application-ID value . 43
Annex A (informative): Differences compared to ITU-T Rw and 3GPP Gx specifications . 44
History . 45

ETSI
5 ETSI TS 183 060 V2.1.1 (2009-04)
Intellectual 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 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 (http://webapp.etsi.org/IPR/home.asp).
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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
ETSI
6 ETSI TS 183 060 V2.1.1 (2009-04)
1 Scope
The present document defines a specification based on DIAMETER for use at the Re Reference Point between the
TISPAN NGN Access-Resource Admission Control Function (A-RACF) and the Resource Control Enforcement
Function (RCEF).
Whenever it is possible the present document specifies the requirements for this 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
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.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 282 003 (V2.0.0): "Telecommunications and Internet converged Services and Protocols
for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS):
Functional Architecture".
[2] IETF RFC 2960: "Stream Control Transmission Protocol".
[3] IETF RFC 3588: "Diameter Base Protocol".
[4] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".
[5] IETF RFC 3554: "On the Use of Stream Control Transmission Protocol (SCTP) with IPSec".
[6] ITU-T NGN-GSI/DOC - 127: "ITU-Telecommunication Standardization Sector, Draft
Recommendation Q.rcp3.3 - Diameter Alternative Version 0.2.0".
[7] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and
charging control over Gx reference point (3GPP TS 29.212)".
[8] IETF RFC 4006 (2005): "Diameter Credit-Control Application".
[9] ETSI TS 129 209 (V6.7.0): "Universal Mobile Telecommunications System (UMTS); Policy
control over Gq interface (3GPP TS 29.209)".
ETSI
7 ETSI TS 183 060 V2.1.1 (2009-04)
[10] IETF RFC 4005 (2005): "Diameter Network Access Server Application".
[11] IANA Private Enterprise Numbers.
NOTE: See http://www.iana.org/assignments/enterprise-numbers
[12] ETSI ES 283 026 (V2.4.1): "Telecommunications and Internet converged Services and Protocols
for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS
reservation information exchange between the Service Policy Decision Function (SPDF) and the
Access-Resource and Admission Control Function (A-RACF) in the Resource and Protocol
specification" .
[13] IETF RFC 5431 (2009):"Diameter ITU-T Rw Policy Enforcement Interface Application".
[14] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ITU-T Recommendation Q.3303.3: "Protocol at the interface between the policy decision physical
entity (PD-PE) and the policy enforcement physical entity (PE-PE) (Rw interface): Diameter".
[i.2] ETSI TS 129 210: "Universal Mobile Telecommunications System (UMTS); Charging rule
provisioning over Gx interface (3GPP TS 29.210)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
activation: operation of binding a Policy-Rule to a Transport Resource based on the transport resource classifier
Attribute-Value Pair (AVP): corresponds to an Information Element in a DIAMETER message
NOTE: See RFC 3588 [3].
deactivation: operation of un-binding a Policy-Rule to a Transport Resource
dynamic policy rule: subcategory of policy rules in which the ownership belongs to the A-RACF and any
installation/modification/removal of the policy are performed using Re interface
Explicit Event Subscription: model for Event Subscription in which the A-RACF explicitly subscribes for the
notification of particular event(s)
Implicit Event Subscription: model for Event Subscription in which the list of event(s) that needs to be reported to the
A-RACF is configured on the RCEF
installation: operation of providing a new, non-existing, Policy-Rule to the RCEF
modification: operation of modifying an existing Policy-Rule(s), providing a new Policy-Rule(s), or removing an
existing Policy-Rule associated with a Transport Resource
ETSI
8 ETSI TS 183 060 V2.1.1 (2009-04)
Policy Rule: QoS Policy which defines how the data traffic should be handled by the RCEF, including:
• cata traffic classification definition;
• traffic forwarding definition based on the classification;
• traffic statistics generation definition based on the classification.
Provisioned Policy Rule: subcategory of policy rules in which the ownership belongs to the provisioning system and
any installation/ modification/ removal of the policy can only be triggered by the provisioned system
removal: operation of removing an existing Policy-Rule in the RCEF
Transport Resource: Network Element on which a Policy Rule needs to be activated
Transport Resource Classifier: parameter or set of parameters identifying a given Transport Resource
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
AVP Attribute-Value Pair
CCA Credit-Control Answer
CCR Credit-Control Request
CEA Capabilities-Exchange-Answer
CER Capabilities-Exchange-Request
IANA Internet Assigned Numbers Authority
IETF Internet Engineering Task Force
PIA Policy-Install-Answer
PIR Policy-Install-Request
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
SPDF Service-based Policy Decision Function
4 Overview
The Resource Control Enforcement Function (RCEF) defined in ES 282 003 [1] performs policy enforcement functions
under control of the A-RACF.
The RCEF main functions are:
• Enforcement of the policies defined by the access provider.
• Οpening and closing of gates in order to allow only authorized traffic to flow; marks IP packets in accordance
with the filtering criteria received from the A-RACF.
Policing of upstream and downstream traffic to ensure that the traffic remains within the authorized limits.
The traffic policies are provided by the A-RACF to the RCEF through the Re reference point.
ETSI
9 ETSI TS 183 060 V2.1.1 (2009-04)
AF
Rf
Gq’
Rd’, Ri’
RACS
e4
NASS
Rq
Rr
SPDF
x-RACF
Re Ia
Scope of the
Present
Specification
RCEF BGF
BTF
Transport Processing Functions

Figure 1: RACS Reference Model
5 Procedure descriptions
5.1 General
The following clauses describe the realization of the functional procedures of the Re Reference Point (defined in the
RACS specification ES 282 003 [1]) using the Diameter commands described in clause 7.1. This involves describing a
mapping between the Information Elements defined in the RACS specification (ES 282 003 [1]) and DIAMETER
AVPs. Procedures across the Re Reference Point can be divided into two categories:
• A-RACF initiated procedures (push mode): Policy operations are initiated by A-RACF. A-RACF decides on
the appropriate traffic policies and activates those in RCEF.
• RCEF initiated procedures (pull mode): Policy operations are initiated by RCEF. In response to a request from
RCEF, A-RACF shall decide on and activate the appropriate traffic policies in RCEF.
ETSI
10 ETSI TS 183 060 V2.1.1 (2009-04)
Figure 2 illustrates the policy-rule life cycle for provisioned type of policy-rules and various states the policy-rule may
go through.
Modify Activate
Install
Inactive Active
Deactivate
Remove
Remove
Removed
NOTE 1: Install/Modify/remove transitions may be initiated by the provisioning systems or the network element
management system. The details of such interface is outside the scope of the present document.
NOTE 2: Activate/Deactivate transitions are initiated using the Re interface.
NOTE 3: The activation operation may result in applying quality of service [QoS] parameters and procedures
defined in the policy rule to the transport resource.
NOTE 4: The deactivation process results in unbinding a policy from the network transport resource.
Figure 2: Policy rule life cycle (Provisioned)
Figure 3 illustrates the policy-rule life cycle for Dynamic type of policy-rules and varies states it may go through.
Install and Activate
Active
Deactivate
Removed
NOTE 1: Dynamic policy-rule can only exist on the RCEF if and only if it is associated with a transport resource
through the interaction between A-RACF and RCEF.
NOTE 2: "Deactivate" a policy rule can be a result of:
- Modifying transport resource applied policy-rules. For detail on modification, see clause 5.2.1.3.
- Terminating the transport resources session.
NOTE 3: The activation operation may result in applying quality of service [QoS] parameters and procedures
defined in the policy rule to the transport resource.
Figure 3: Policy rule life cycle [Dynamic]
ETSI
11 ETSI TS 183 060 V2.1.1 (2009-04)
5.2 A-RACF initiated procedures
5.2.1 Procedures at the A-RACF
5.2.1.1 High level description
The A-RACF is the DIAMETER Server.
The policy operations that the A-RACF may support include the installation, activation, modification, deactivation and
removal of Policy Rules on the RCEF:
• In order to activate one or several Policy Rules, or to Install and Activate one or several Policy Rules, the
A-RACF sends an initial Policy-Install-Request (PIR) Command containing at least one Policy Rule to the
RCEF. The PI-Request-Type AVP contains the value INITIAL_REQUEST. Each Policy Rule is described in
the Policy-Rule-Install AVP. The Policy-Rule-Install AVP shall contain a Policy-Rule-Definition AVP. At
least one Transport Resource Classifier shall be included in the Policy-Rule-Definition AVP, in order to
indicate the Transport Resource Classifier(s) associated with the Policy Rule(s).
• In order to modify Policy Rule(s) previously activated on a given Transport Resource, the A-RACF sends a
PIR Command with the PI-Request-Type AVP set to the value UPDATE_REQUEST. During the
Modification procedure, a Policy Rule previously activated for the Transport Resource may be modified or
deactivated and removed (uninstalled).
• In order to deactivate and remove all Policy Rule(s) previously activated for given Transport Resource
Classifier(s), the A-RACF sends a PIR Command to the RCEF, with the PI-Request-Type AVP set to
TERMINATION_REQUEST. The Termination Request shall contain the Transport Resource Classifier(s).
The A-RACF may query the RCEF for the currently activated Policy Rules:
• Query of the supported Policy Rules.
• Query of the list of Policy Rules associated with a given Transport Resource.
• Query of the details of particular Policy Rules associated with a given Transport Resource.
5.2.1.2 Initial Policy Installation Request
The Initial Policy Installation Request is a PIR command with the PI-Request-Type AVP set to INITIAL_REQUEST.
The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3] to indicate
implicitly terminated sessions.
The A-RACF may include one or several Event-Trigger AVP(s) in order to subscribe to the notification of particular
event(s).
The Policy-Rule-Install AVP is used to describe the Policy Rule(s). The A-RACF shall include at least one
Policy-Rule-Install AVP in the Initial PIR:
• In order to install and activate a new Policy Rule, the Policy-Rule-Definition AVP shall be used:
- Policy-Rule-Name AVP shall be included in the Policy-Rule-Definition AVP.
- The Flow-Status AVP shall be included in the Policy-Rule-Definition AVP. The value shall be set to
ENABLED-UPLINK (0) or ENABLED-DOWNLINK (1) in order to request the activation of the
corresponding Policy Rule:
ENABLED-UPLINK shall be used to describe a Policy Rule relative to the outgoing direction on
the RCEF.
ENABLED-DOWNLINK shall be used to describe a Policy Rule relative to the incoming direction
on the RCEF.
ETSI
12 ETSI TS 183 060 V2.1.1 (2009-04)
If Policy Rules for each direction need to be specified, several Policy-Rule-Definition AVPs will be
included.
- The QoS-Information AVP may be included in the Policy-Rule-Definition AVP:
The Max-Requested-Bandwidth-UL AVP and Traffic-Descriptor-UL AVP may be included in
order to describe the bandwidth profile of a Policy-Rule-Definition AVP with a Flow-Status equal
to ENABLED-UPLINK.
The Max-Requested-Bandwidth-DL AVP and Traffic-Descriptor-DL AVP may be included in
order to describe the bandwidth profile of a Policy-Rule-Definition AVP with a Flow-Status equal
to ENABLED-DOWNLINK.
The ToS-Traffic-Class AVP may be included in order to associate the Policy Rule with a Traffic
Class:
- The same ToS-Traffic-Class is associated with both the uplink and the downlink directions
when both directions are used.
- The Reporting-Level may be included in the Policy-Rule-Definition AVP.
- The Precedence AVP shall be included in the Policy-Rule-Definition AVP.
• In order to activate a specific Policy Rule predefined at the RCEF, Policy-Rule-Name AVP shall be used as a
reference for that Policy Rule.
• In order to activate a group of Policy Rules predefined at the RCEF, the Policy-Rule-Base-Name AVP may be
used.
In order to identify the Transport Resources to which the Policy Rule applies, the A-RACF shall include at least one of
the following Transport Resource Classifiers within the Policy-Rule-Definition AVP:
• Logical-Access-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular
Logical-Access-Id.
• Physical-Access-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular bearer
resource upon which the Policies should be enforced.
• Framed-IP-Address AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular IP Session.
- The Address-Realm AVP may be added if the Framed-IP-Address AVP is also included, in order to
associate the Policy-Rule-Definition AVP(s) with a particular Globally Unique IP Address.
• Called-Station-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Transport
Resource on the RCEF.
• The User-Name AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular End User.
• Zero, one or several Flow-Description AVP(s) may be included in the Policy-Rule-Definition AVP, in order to
associate a given Policy Rule with IP Flows.
• ToS-Traffic-Class AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Traffic
Class.
• The A-RACF may include one or several of these Transport Resource Classifiers.
- In case several Transport Resource Classifiers are included, they shall match with each others.
ETSI
13 ETSI TS 183 060 V2.1.1 (2009-04)
5.2.1.3 Policy modification request
The Policy Modification Request is a PIR Command with the PI-Request-Type AVP with the value
UPDATE_REQUEST.
The A-RACF shall include the Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3].
The A-RACF may include one or several Event-Trigger AVP(s) in order to subscribe to the notification of particular
event(s). Event-Trigger AVPs that were specified in the corresponding Initial PIR or in previous Policy Modification
Requests, remain valid even if they are not specified in the Policy Modification Request.
In order to remove a previously activated Policy Rule(s) associated with the Transport Resource, the A-RACF may
include one or several Policy-Rule-Remove AVP(s) as main AVP(s):
• In order to remove a Policy Rule previously activated on the Transport Resource, the A-RACF shall include
the Policy-Rule-Name AVP in the Policy-Rule-Remove AVP.
• In order to remove a group of Policy Rules previously activated on the Transport Resource, the A-RACF shall
include the Policy-Rule-Base-Name AVP in the Policy-Rule-Remove AVP.
In order to modify Policy Rules previously activated for the Transport Resource, the A-RACF may include one or
several Policy-Rule-Install AVP(s) as main AVP(s):
• The A-RACF shall include the Policy-Rule-Definition AVP:
- The A-RACF shall include a known Policy-Rule-Name AVP.
- The A-RACF may update the Policy-Rule-Definition.
In particular, the A-RACF may instruct the RCEF to deactivate and remove a Policy Rule
previously associated with the Transport Resource, by changing the Flow-Status in the
Policy-Rule-Definition AVP to REMOVED.
In order to install and activate new Policy Rule(s) on the RCEF, the A-RACF may include one or several
Policy-Rule-Install AVP(s) as main AVP(s).
• Each Policy-Rule-Install AVP shall be specified as described in clause 5.2.1.2.
- In particular, the A-RACF shall include a new Policy-Rule-Name AVP.
In order to activate Policy Rules pre-defined on the RCEF, the A-RACF may include one or several Policy-Rule-Install
AVP(s) as main AVP(s). Each Policy-Rule-Install AVP shall be specified as follows:
• Policy-Rule-Name AVP shall be used as a reference for that Policy Rule.
• The Policy-Rule-Base-Name AVP shall not be included if the Policy-Rule-Name AVP is included.
In order to activate a group of Policy Rules pre-defined on the RCEF, the A-RACF may include one or several
Policy-Rule-Install AVP(s) as main AVP(s). Each Policy-Rule-Install AVP shall be specified as follows:
• Policy-Rule-Base-Name AVP shall be used as a reference for that group of Policy Rules.
• The Policy-Rule-Name AVP shall not be included if the Policy-Rule-Base-Name AVP is included.
5.2.1.4 Policy termination request
In order to deactivate and remove all Policy Rule(s) previously activated on a Transport Resource, the A-RACF sends a
PIR Command to the RCEF, with the PI-Request-Type AVP set to TERMINATION_REQUEST.
The Policy Termination-Request shall include the Transport Resource Classifier of the corresponding Transport
Resource.
In the case of pre-defined Policy Rule on the RCEF (e.g. identified by Policy-Rule-Base-Name), the A-RACF may only
be authorized to deactivate the pre-defined Policy Rule.
ETSI
14 ETSI TS 183 060 V2.1.1 (2009-04)
5.2.1.5 Event notification
5.2.1.5.1 Events
Depending on the policy installed, the RCEF may initiate communication with A-RACF to notify certain event occurred
on the network element, according to the event A-RACF may decide to modify / remove existing policies, install new
policies or escalate the event to higher layer.
Event type is identified within the CCR message according to clause 7.3.3.3.
The following is a list of supported events:
• Loss of bearer.
• Recovery of bearer.
• RCEF malfunction.
• Resource modification.
5.2.1.5.2 Event subscription
Two mechanisms are supported on the Re Reference Point:
• Explicit Event Subscription: The A-RACF may request to be notified of certain events (e.g. bearer failure) by
specifying them in the Event-Trigger AVP of the Initial PIR command or of the subsequent Policy
Modification Request(s).
• Implicit Event Subscription: Configuration/provisioning at the RCEF indicates which events need to be
reported to the A-RACF: as such, the A-RACF may not need to explicitly subscribe for the notification of the
occurrence of particular events.
5.2.1.5.3 Event notification
A CCR from the RCEF to the A-RACF indicates the occurrence of particular events (Explicit or Implicit Event
Subscription).
As soon as one of the expected AVPs is missing, the A-RACF denies the entire CCR and returns a CCA command with
the Result-Code AVP with the value DIAMETER_MISSING_MANDATORY_AVP [3]. This is the case if:
• either the Session-Id AVP is missing;
• or the Service-Context-Id AVP is missing;
• or Auth-Session-State AVP is missing;
• or the CC-Request-Type AVP is missing;
• or the CC-Request-Number AVP is missing;
• or the CCR command does not contain at least one Policy-Rule-Report AVP;
• or the CCR command does not include at least one of Logical-Access-Id AVP, Framed-IP-Address AVP,
Called-Station-Id AVP or User-Name AVP;
• or one of Origin-Host AVP, Origin-Realm AVP, Destination-Realm AVP is missing;
• or the Event-Trigger AVP is missing;
• or the Auth-Application-Id AVP is missing.
The A-RACF determines the impacted Policy(ies) from the Policy-Rule-Name AVP or Policy-Rule-Base-Name AVP
specified in the Policy-Rule-Report AVP.
ETSI
15 ETSI TS 183 060 V2.1.1 (2009-04)
The A-RACF determines the subsequent action (e.g. the A-RACF may want to remove a Policy), A-RACF may
implement the subsequent action using one of the following methods:
• Respond to the CCR command with CCA command that does not include any policy alteration and then
follow up with a PIR command to alter active policies (if needed) as per clause 5.2.
• Include policy alteration request within the CCA command as described below. In the case of any failure
during the modification of the active policy, RCEF is required to communicate the failure to A-RACF using
Event Notification as per clause 5.2.1.5.2
The A-RACF answers to the RCEF with a CCA command and includes the following AVPs:
• Session-Id, CC-Request-Type, CC-Request-Number AVPs are the same as in the corresponding CCR.
• Result-Code AVP.
• Policy-Rule-Install AVP if a Policy needs to be installed or updated, as a consequence of the event.
• Policy-Rule-Remove AVP if a Policy previously installed needs to be removed.
• Auth-Session-State AVP with the value NO_STATE_MAINTAINED (1) [3].
• In order to identify the Transport Resources to which the Policy Rule applies, the A-RACF shall include at
least one of the following Classifiers:
- Logical-Access-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular
Logical-Access-Id.
- Framed-IP-Address AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular IP
Session.
The Address-Realm AVP may be included if the Framed-IP-Address AVP is included, in order to
associate the Policy Rule with a particular Globally Unique IP Address.
- Called-Station-Id AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular
Transport Resource on the RCEF.
- The User-Name AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular End User.
- Zero, one or several Flow-Description AVP(s) may be included in the Policy-Rule-Definition AVP, in
order to associate a given Policy Rule with IP Flows.
- ToS-Traffic-Class AVP in order to associate the Policy-Rule-Definition AVP(s) with a particular Traffic
Class.
- The A-RACF may include one or several of these Transport Resource Classifiers.
In case several Transport Resource Classifiers are included, they shall match with each others.
5.2.1.6 Policy Query Request
The Policy Query Request is a PIR command with the PI-Request-Type AVP set to QUERY_REQUEST.
Several Query levels are supported:
• In order to query the RCEF for the list of Policy Rules supported by the RCEF, the A-RACF shall not include
any Transport Resource Classifier, and shall not include any Policy Rule.
• In order to query the RCEF for the list of Policy Rules currently associated with a given Transport Resource,
the A-RACF shall include the Transport Resource Classifier, and shall not include any Policy Rule.
• In order to query the RCEF for the details about particular Policy Rule(s), the A-RACF shall include the
Transport Resource Classifier and the Policy Rule(s) for which details are requested.
ETSI
16 ETSI TS 183 060 V2.1.1 (2009-04)
5.2.2 Procedures at the RCEF
5.2.2.1 High level description
The RCEF is the DIAMETER Client.
• A PIR Command with the PI-Request-Type AVP set to INITIAL_REQUEST is interpreted by the RCEF as an
Initial Policy Install Request.
• A PIR Command with the PI-Request-Type AVP set to UPDATE_REQUEST is interpreted by the RCEF as a
Policy Modification Request.
• A PIR Command with the PI-Request-Type AVP set to TERMINATION_REQUEST is interpreted by the
RCEF as a Policy Termination Request.
• A PIR Command with the PI-Request-Type AVP set to QUERY_REQUEST is interpreted by the RCEF as a
Policy Query
...