This chapter describes how Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) Diameter Gateway maps the Diameter messages for Diameter Sh Protocol defined in 3GPP TS 29.329 Version 12.0. For more information, see the 3GPP Specification detail:
http://www.3gpp.org/ftp/Specs/html-info/29329.htm
Table 5-1 lists the compliance information for Diameter Sh protocol sections.
Table 5-1 Diameter Sh 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 |
Abbreviations |
No requirement |
- |
|
4 |
General |
No requirement |
- |
|
5 |
Use of the Diameter base protocol |
Supported |
- |
|
6 |
Diameter application for Sh interface |
Supported |
- |
|
6.1 |
Command-Code values |
Partially supported |
Profile-Update-Request and Profile-Update-Answer are not supported |
|
6.1.1 |
User-Data-Request (UDR) Command |
Supported |
- |
|
6.1.2 |
User-Data-Answer (UDA) Command |
Supported |
- |
|
6.1.3 |
Profile-Update-Request (PUR) Command |
Not supported |
- |
|
6.1.4 |
Profile-Update-Answer (PUA) Command |
Not supported |
- |
|
6.1.5 |
Subscribe-Notifications-Request (SNR) Command |
Supported |
- |
|
6.1.6 |
Subscribe-Notifications-Answer (SNA) Command |
Supported |
- |
|
6.1.7 |
Push-Notification-Request (PNR) Command |
Supported |
- |
|
6.1.8 |
Push-Notifications-Answer (PNA) Command |
Supported |
- |
|
6.2 |
Result-Code attribute-value pair (AVP) values |
No requirement |
- |
|
6.2.1 |
Success |
Supported |
- |
|
6.2.2 |
Permanent Failures |
No requirement |
- |
|
6.2.2.1 |
DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100) |
Not applicable |
- |
|
6.2.2.2 |
DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) |
Not supported |
- |
|
6.2.2.3 |
DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102) |
Not supported |
- |
|
6.2.2.4 |
DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) |
Not supported |
- |
|
6.2.2.5 |
DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104) |
Not supported |
- |
|
6.2.2.6 |
DIAMETER_ERROR_TOO_MUCH_DATA (5008) |
Not supported |
- |
|
6.2.2.7 |
DIAMETER_ERROR_TRANSPARENT_DATA OUT_OF_SYNC (5105) |
Not supported |
- |
|
6.2.2.8 |
DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) |
Not supported |
- |
|
6.2.2.9 |
DIAMETER_ERROR_SUBS_DATA_ABSENT (5106) |
Supported |
Generated in absence of requested Data-Reference preferences. |
|
6.2.2.10 |
DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107) |
Not applicable |
- |
|
6.2.2.11 |
DIAMETER_ERROR_DSAI_NOT_AVAILABLE (5108) |
Not supported |
- |
|
6.2.2.12 |
DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002) |
Not supported |
- |
|
6.2.3 |
Transient Failures |
No requirement |
- |
|
6.2.3.1 |
DIAMETER_USER_DATA_NOT_AVAILABLE (4100) |
Not supported |
- |
|
6.2.3.2 |
DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) |
Not supported |
- |
|
6.3 |
Attribute-value pairs (AVPs) |
No requirement |
- |
|
6.3.1 |
User-Identity |
Supported |
- |
|
6.3.2 |
Mobile station international subscriber directory number (MSISDN) |
Supported |
- |
|
6.3.3 |
User-Data |
Supported |
- |
|
6.3.4 |
Data-Reference |
Supported |
Used to identify the preferences requested by the policy and charging rules function (PCRF) |
|
6.3.5 |
Service-Indication |
Not supported |
- |
|
6.3.6 |
Subs-Req-Type |
Supported |
- |
|
6.3.7 |
Requested-Domain |
Not supported |
- |
|
6.3.7A |
Requested-Nodes |
Not supported |
- |
|
6.3.8 |
Current-Location |
Not supported |
- |
|
6.3.9 |
Server-Name |
Not supported |
- |
|
6.3.10 |
Identity-Set |
Not supported |
- |
|
6.3.11 |
Supported-Features |
Not supported |
- |
|
6.3.12 |
Feature-List-ID |
Not supported |
- |
|
6.3.13 |
Feature-List |
Not supported |
- |
|
6.3.14 |
Supported-Applications |
Not supported |
- |
|
6.3.15 |
Public-Identity |
Supported |
- |
|
6.3.16 |
Expiry-Time |
Supported |
- |
|
6.3.17 |
Send-Data-Indication |
Supported |
- |
|
6.3.18 |
DSAI-Tag |
Not supported |
- |
|
6.3.19 |
Wildcarded-Public-Identity |
Not supported |
- |
|
6.3.20 |
Wildcarded-IMPU |
Not supported |
- |
|
6.3.21 |
Session-Priority |
Not supported |
- |
|
6.3.22 |
One-Time-Notification |
Not supported |
- |
|
6.3.23 |
Serving-Node-Indication |
Not supported |
- |
|
6.3.24 |
Repository-Data-ID |
Not supported |
- |
|
6.3.25 |
Sequence-Number |
Not supported |
- |
|
6.3.26 |
Pre-paging-Supported |
Not supported |
- |
|
6.3.27 |
Local-Time-Zone-Indication |
Not supported |
- |
|
6.3.28 |
UDR-Flags |
Not supported |
- |
|
6.3.29 |
Call-Reference-Info |
Not supported |
- |
|
6.3.30 |
Call-Reference-Number |
Not supported |
- |
|
6.3.31 |
AS-Number |
Not supported |
- |
|
6.3.32 |
OC-Supported-Features |
Not supported |
- |
|
6.3.33 |
OC-OLR |
Not supported |
- |
|
6.4 |
Use of namespaces |
No requirement |
- |
|
6.4.1 |
AVP codes |
No requirement |
- |
|
6.4.2 |
Experimental-Result-Code AVP values |
No requirement |
- |
|
6.4.3 |
Command Code values |
No requirement |
- |
|
6.4.4 |
Application-ID value |
Supported |
- |
|
7 |
Special Requirements |
No requirement |
- |
|
7.1 |
Version Control |
Not supported |
- |
|
Annex A |
Change history |
No requirement |
- |
Table 5-2 lists the compliance information for Diameter User Data commands for Diameter Sh protocol.
Table 5-2 Diameter User Data Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
User-Data-Request (UDR) |
Supported |
- |
|
User-Data-Answer (UDA) |
Supported |
- |
Table 5-3 lists the compliance information for User-Data-Request AVPs.
Table 5-3 User-Data-Request AVPs
| Diameter AVP | Status | Notes |
|---|---|---|
|
Session-Id |
Supported |
- |
|
User-Identity |
Supported |
- |
|
-- Public-Identity |
Supported |
- |
|
Data-Reference |
Supported |
- |
|
Wildcarded-Public-Identity |
Not supported |
- |
|
Wildcarded-IMPU |
Not supported |
- |
|
Server-Name |
Not supported |
- |
|
Service-Indication |
Not supported |
- |
|
Identity-Set |
Not supported |
- |
|
Requested-Domain |
Not supported |
- |
|
Current-Location |
Not supported |
- |
|
DSAI-Tag |
Not supported |
- |
|
Session-Priority |
Not supported |
- |
|
User-Name |
Not supported |
- |
|
Requested-Nodes |
Not supported |
- |
|
Serving-Node-Indication |
Not supported |
- |
|
Pre-Paging-Supported |
Not supported |
- |
|
Local-Time-Zone-Indication |
Not supported |
- |
|
UDR-Flags |
Not supported |
- |
|
Call-Reference-Info |
Not supported |
- |
Diameter Gateway does not support Profile-Update-Request (PUR) and Profile-Update-Answer (PUA) commands.
Table 5-5 lists the compliance information for Diameter Subscribe Notifications commands.
Table 5-5 Diameter Subscribe Notifications Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
Subscribe-Notifications-Request (SNR) |
Supported |
- |
|
Subscribe-Notifications-Answer (SNA) |
Supported |
- |
Table 5-6 lists the compliance information for Subscribe-Notifications-Request (SNR) AVPs.
Table 5-6 Subscribe-Notifications-Request AVPs
| Diameter AVP | Status | Notes |
|---|---|---|
|
Session-Id |
Supported |
- |
|
User-Identity |
Supported |
- |
|
-- Public-Identity |
Supported |
- |
|
Data-Reference |
Supported |
- |
|
Subs-Req-Type |
Supported |
- |
|
Expiry-Time |
Supported |
- |
|
Send-Data-Indication |
Supported |
- |
|
Wildcarded-Public-Identity |
Not supported |
- |
|
Wildcarded-IMPU |
Not supported |
- |
|
Service-Indication |
Not supported |
- |
|
Server-Name |
Not supported |
- |
|
Identity-Set |
Not supported |
- |
|
DSAI-Tag |
Not supported |
- |
|
One-Time-Notification |
Not supported |
- |
|
User-Name |
Not supported |
- |
Table 5-7 lists the compliance information for Subscribe-Notifications-Answer (SNA) AVPs.
Table 5-8 lists the compliance information for Diameter Push Notification commands.
Table 5-8 Diameter Push Notification Commands
| Diameter Command | Status | Notes |
|---|---|---|
|
Push-Notification-Request (PNR) |
Supported |
- |
|
Push-Notification-Answer (PNA) |
Supported |
- |
Table 5-9 lists the compliance information for Push-Notification-Request AVPs.
Table 5-10 lists the compliance information for Push-Notification-Answer AVPs.