This chapter describes how Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) Diameter Gateway maps the Diameter messages for Diameter Sy Protocol defined in 3GPP TS 29.219 Version 12.0. For more information, see the 3GPP Specification detail:
http://www.3gpp.org/ftp/Specs/html-info/29219.htm
Table 4-1 lists the compliance information for Diameter Sy protocol sections.
Table 4-1 Diameter Sy Section Compliance
| Section Number | Section | Status | Notes |
|---|---|---|---|
|
1 |
Scope |
No requirement |
- |
|
2 |
References |
No requirement |
- |
|
3 |
Definitions, symbols, and abbreviations |
No requirement |
- |
|
3.1 |
Definitions |
No requirement |
- |
|
3.2 |
Symbols |
No requirement |
- |
|
3.3 |
Abbreviations |
No requirement |
- |
|
4 |
Sy reference point |
No requirement |
- |
|
4.1 |
Overview |
No requirement |
- |
|
4.2 |
Sy reference model |
Supported |
- |
|
4.3 |
Subscriber spending limits |
Supported |
Diameter Gateway supports pending policy counters. |
|
4.4 |
Functional elements |
Supported |
- |
|
4.4.1 |
PCRF |
Not applicable |
Section applies to policy and charging rules function (PCRF). |
|
4.4.2 |
OCS |
Supported |
- |
|
4.5 |
Spending limits procedures over Sy reference point |
No requirement |
- |
|
4.5.1 |
Initial/Intermediate spending limit report request |
No requirement |
- |
|
4.5.1.1 |
General |
Supported |
- |
|
4.5.1.2 |
Detailed behavior of the PCRF |
Not applicable |
Section applies to PCRF. |
|
4.5.1.3 |
The behavior of the OCS |
Partially supported |
The Online Charging System (OCS) will always return the DIAMETER_ERROR_UNKNOWN POLICY_COUNTERS error whenever a policy counter is requested that is either unknown or not applicable to the subscriber. This behavior is not configurable. Pending policy counters will always be provided if they are present in the OCS data. When the syRejectNoCounters attribute is set to false or not set, OCS will not return the DIAMETER_ERROR_NO_AVAILABLE_POLICY_COUNTERS error. Instead, it will generate the Spending-Limit-Answer (SLA) success notification with no policy counters and subscribe to the Sy session to receive updates on any future policy counter changes. |
|
4.5.2 |
Spending limit report |
No requirement |
- |
|
4.5.2.1 |
General |
Supported |
- |
|
4.5.2.2 |
The behavior of the OCS |
Supported |
Pending policy counters will always be provided if they are present in the OCS data. In the case of a general Sy subscription (where no policy counters are specifically defined in the original Spending-Limit-Request (SLR)), OCS will always report the policy counter changes. This includes the change where a subscriber is associated with a new policy counter, which was not present at the time of the initial SLR. |
|
4.5.2.3 |
Detailed behavior of the PCRF |
Not applicable |
Section applies to PCRF. |
|
4.5.3 |
Final spending limit report request |
No requirement |
- |
|
4.5.3.1 |
General |
Supported |
- |
|
4.5.3.2 |
Detailed behavior of the PCRF |
Not applicable |
Section applies to PCRF. |
|
4.5.3.3 |
The behavior of the OCS |
Supported |
- |
|
5 |
Sy protocol |
No requirement |
- |
|
5.1 |
Protocol support |
No requirement |
- |
|
5.1.1 |
Use of Diameter base protocol |
Supported |
- |
|
5.1.2 |
Void |
No requirement |
- |
|
5.1.3 |
Accounting functionality |
No requirement |
- |
|
5.1.4 |
Transport protocol |
Supported |
Supports Transmission Control Protocol (TCP) and Stream Control Transmission Protocol (SCTP). |
|
5.1.5 |
Advertising application Support |
Supported |
- |
|
5.1.6 |
Use of the Supported-Features attribute-value pair (AVP) |
Not supported |
The negotiation of supported features is not supported by Diameter Gateway. |
|
5.2 |
Initialization and maintenance of connection and session |
Supported |
- |
|
5.3 |
Sy specific AVPs |
Supported |
- |
|
5.3.1 |
Policy-Counter-Identifier AVP |
Supported |
- |
|
5.3.2 |
Policy-Counter-Status AVP |
Supported |
- |
|
5.3.3 |
Policy-Counter-Status-Report AVP |
Supported |
- |
|
5.3.4 |
SL-Request-Type AVP |
Supported |
- |
|
5.3.5 |
Pending-Policy-Counter-Information AVP |
Supported |
- |
|
5.3.6 |
Pending-Policy-Counter-Change-Time AVP |
Supported |
- |
|
5.4 |
Sy reused AVPs |
Partially supported |
The Logical-Access-Id and Physical-Access-Id AVPs are not defined in the standard Diameter Gateway configuration. |
|
5.5 |
Sy specific Experimental-Result-Code AVP values |
No requirement |
- |
|
5.5.1 |
General |
Supported |
- |
|
5.5.2 |
Permanent failures |
Supported |
- |
|
5.5.3 |
Transient failures |
Supported |
- |
|
5.6 |
Sy messages |
No requirement |
In the case of a general Sy subscription (where no policy counters are requested in the SLR), the OCS will not return the DIAMETER_ERROR_NO_AVAILABLE_POLICY_COUNTERS error by default. Instead, it will return a success SLA report and subscribe to the Sy session for updates on any new counters that are added to the given subscriber during the session. You can disable the generation of SLA reports by setting the syRejectNoCounters attribute to true. |
|
5.6.1 |
Command-Code values |
Supported |
- |
|
5.6.2 |
Spending-Limit-Request (SLR) command |
Supported |
- |
|
5.6.3 |
Spending-Limit-Answer (SLA) command |
Supported |
- |
|
5.6.4 |
Spending-Status-Notification-Request (SNR) command |
Supported |
- |
|
5.6.5 |
Spending-Status-Notification-Answer (SNA) command |
Supported |
- |
|
5.6.6 |
Session-Termination-Request (STR) command |
Supported |
- |
|
5.6.7 |
Session-Termination-Answer (STA) command |
Supported |
- |
|
Annex A (normative): |
User identity for fixed broadband access network convergence |
No requirement |
- |
|
Annex B (informative): |
Change history |
No requirement |
- |
Table 4-2 lists the compliance information for Diameter Spending Limit commands.
Table 4-2 Diameter Spending Limit Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
Spending-Limit-Request (SLR) |
Supported |
- |
|
Spending-Limit-Answer (SLA) |
Supported |
- |
Table 4-3 lists the compliance information for Spending-Limit-Request AVPs.
Table 4-4 lists the compliance information for Spending-Limit-Answer AVPs.
Table 4-4 Spending-Limit-Answer AVPs
| Diameter AVP | Status | Notes |
|---|---|---|
|
Session-Id |
Supported |
- |
|
Result-Code |
Supported |
- |
|
Experimental-Result |
Supported |
- |
|
Policy-Counter-Status-Report |
Supported |
- |
|
-- Policy-Counter-Identifier |
Supported |
- |
|
-- Policy-Counter-Status |
Supported |
- |
|
-- Pending-Policy-Counter-Information |
Supported |
- |
|
-- -- Policy-Counter-Status |
Supported |
- |
|
-- -- Pending-Policy-Counter-Change-Time |
Supported |
- |
|
Failed-AVP |
Supported |
- |
Table 4-5 lists the compliance information for Diameter Spending Status Notification commands.
Table 4-5 Diameter Spending Status Notification Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
Spending-Status-Notification-Request (SNR) |
Supported |
- |
|
Spending-Status-Notification-Answer (SNA) |
Supported |
- |
Table 4-6 lists the compliance information for Spending-Status-Notification-Request (SNR) AVPs.
Table 4-7 lists the compliance information for Spending-Status-Notification-Answer (SNA) AVPs.
Table 4-8 lists the compliance information for Diameter Session Termination commands.
Table 4-8 Diameter Session Termination Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
Session-Termination-Request (STR) |
Supported |
- |
|
Session-Termination-Answer (STA) |
Supported |
- |
Table 4-9 lists the compliance information for Session-Termination-Request (STR) AVPs.
Table 4-10 lists the compliance information for Session-Termination-Answer (STA) AVPs.