This chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 4.0 Application-driven Quality of Service (QoS)/Diameter communication service and how the interfaces and protocols comply to standards.
This section describes the standards compliance for the communication services for Parlay X 4.0 Application-Driven QoS.
The Parlay X 4.0 interface complies with ETSI ES 202 504-17 Open Service Access (OSA); Parlay X Web Services; Part 17:Application-driven Quality of Service (QoS); Parlay X 3.
See Table 1-11, "Quality of Service Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.
Table 15-1 Statement of Compliance, Parlay X 4.0 Application-Driven QoS
| Method | Compliant | Comment |
|---|---|---|
|
Interface: ApplicationQoS |
NA |
NA |
|
applyQoSFeature |
Yes |
This method sets temporary QoS feature profiles, but does not apply a default QoS feature profile. See the discussion on Parlay X 4.0 Quality of Service/Diameter in Services Gatekeeper System Administrator's Guide for more information. |
|
modifyQoSFeature |
Yes |
NA |
|
removeQoSFeature |
Yes |
NA |
|
getQoSStatus |
Yes |
NA |
|
getQoSHistory |
Yes |
NA |
|
Interface: ApplicationQoSNotificationManager |
NA |
NA |
|
startQoSNotification |
Yes |
NA |
|
stopQoSNotification |
Yes |
NA |
|
Interface: ApplicationQoSNotification |
NA |
NA |
|
notifyQoSEvent |
Yes |
NA |
Services Gatekeeper complies with a subset of the 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC); Reference points (Release 13) 3GPP TS 29.212 V13.5.0 (2016-03).
Table 15-2 lists the Diameter Gx AVPs Supported by Services Gatekeeper.
Table 15-2 Supported Diameter GX AVPs and Messages
| Diameter Gx AVP | Diameter Gx Message | Notes |
|---|---|---|
|
endUserOpaqueId |
AAR |
Added to request message from UE to PCRF, and then PECF. |
|
requiredAccessInfo |
AAR |
Added to request message from UE to PCRF, and then PECF. |
|
FramedPort |
AAR |
Added to request message from UE to PCRF, and then PECF. |
|
msTimeZone |
AAA |
Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE. |
|
userLocationInfo |
AAA |
Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE. |
|
apnAMBRUL |
AAA |
Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE. |
|
apnAMBRDL |
AAA |
Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE. |
The Parlay X 4.0 Application-Driven QoS/Diameter communication service complies with the Policy and Charging Control over Rx reference point 3GPP TS 29.214 specification. See Table 1-11, "Quality of Service Communication Service Specifications" for the name and version of the supported specification and a link to its location.
Services Gatekeeper acts as a Diameter server for quality of service, and uses your Policy Control and Charging Rules Function (PCRF) as the diameter client.
Table 15-1 lists the Rx commands supported by Policy Controller.
Table 15-3 Supported Rx Messages
| Command | Status | Link to List of Supported AVPs |
|---|---|---|
|
AA-Request (AAR) |
Supported |
|
|
AA-Answer (AAA) |
Supported |
|
|
Re-Auth-Request (RAR) |
Supported |
|
|
Re-Auth-Answer (RAA) |
Supported |
|
|
Session-Termination-Request (STR) |
Supported |
|
|
Session-Termination-Answer (STA) |
Supported |
|
|
Abort-Session-Request (ASR) |
Supported |
|
|
Abort-Session-Answer (ASA) |
Supported |
Table 15-4 lists the supported Diameter Rx AA-Request (AAR) AVPs.
| AVP | Status |
|---|---|
|
Auth-Application-Id |
Supported |
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
AF-Application-Identifier |
Supported |
|
---- Media-Component-Description |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Media-Sub-Component |
Supported |
|
---- ---- AF-Application-Identifier |
Supported |
|
---- ---- Media-Type |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- ---- RS-Bandwidth |
Supported |
|
---- ---- RR-Bandwidth |
Supported |
|
---- ---- Codec-Data |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Media-Sub-Component |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Flow-Description |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Flow-Usage |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- AF-Signalling-Protocol |
Supported |
|
---- AF-Application-Identifier |
Supported |
|
---- Media-Type |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Flow-Status |
Supported |
|
---- Reservation-Priority |
Supported |
|
---- RS-Bandwidth |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- RR-Bandwidth |
Supported |
|
---- Codec-Data |
Supported |
|
Service-Info-Status |
Supported |
|
AF-Charging-Identifier |
Supported |
|
SIP-Forking-Indication |
Supported |
|
Specific-Action |
Supported |
|
Subscription-Id |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Type |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Data |
Supported Reused from RFC 4006 |
|
Supported-Features |
Supported Reused from 3GPP TS 29.229 |
|
---- Vendor-Id |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List-ID |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List |
Supported Reused from 3GPP TS 29.229 |
|
Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
Framed-IP-Address |
Supported Reused from RFC 4005 |
|
Framed-IPv6-Prefix |
Supported Reused from RFC 4005 |
|
Called-Station-Id |
Supported Reused from RFC 4005 |
|
Service-URN |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 15-5 lists the supported Diameter Rx AA-Answer (AAA) AVPs.
| AVP | Status |
|---|---|
|
Auth-Application-Id |
Supported |
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Experiment-Result |
Supported |
|
Access-Network-Charging-Identifier |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Flows |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Access-Network-Charging-Address |
Supported |
|
Acceptable-Service-Info |
Supported |
|
---- Media-Component-Description |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Media-Sub-Component |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Flow-Description |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Flow-Usage |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- AF-Signalling-Protocol |
Supported |
|
---- ---- AF-Application-Identifier |
Supported |
|
---- ---- Media-Type |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- ---- RS-Bandwidth |
Supported |
|
---- ---- RR-Bandwidth |
Supported |
|
---- ---- Codec-Data |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
IP-CAN-Type |
Supported Reused from 3GPP TS 29.212 |
|
RAT-Type |
Supported Reused from 3GPP TS 29.212 |
|
Supported-Features |
Supported Reused from 3GPP TS 29.229 |
|
---- Vendor-Id |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List-ID |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List |
Supported Reused from 3GPP TS 29.229 |
|
Class |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
---- AVP |
Supported |
|
Origin-State-Id |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
Table 15-6 lists the supported Diameter Rx Re-Auth-Request (RAR) AVPs.
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
Auth-Application-Id |
Supported |
|
Specific-Action |
Supported |
|
Access-Network-Charging-Identifier |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Flows |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Access-Network-Charging-Address |
Supported |
|
Flows |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Flow-Number |
Supported |
|
---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Subscription-Id |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Type |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Data |
Supported Reused from RFC 4006 |
|
Abort-Cause |
Supported |
|
IP-CAN-Type |
Supported Reused from 3GPP TS 29.212 |
|
RAT-Type |
Supported Reused from 3GPP TS 29.212 |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 15-7 lists the supported Diameter Rx Re-Auth-Answer (RAA) AVPs.
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Experimental-Result |
Supported |
|
---- Vendor-Id |
Supported |
|
---- Experimental-Result-Code |
Supported |
|
Media-Component-Description |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Media-Sub-Component |
Supported |
|
---- AF-Application-Identifier |
Supported |
|
---- Media-Type |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Flow-Status |
Supported |
|
---- Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- RS-Bandwidth |
Supported |
|
---- RR-Bandwidth |
Supported |
|
---- Codec-Data |
Supported |
|
Service-URN |
Supported |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Failed-AVP |
Supported |
|
---- AVP |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
Table 15-8 lists the supported Diameter Rx Session-Termination-Request (STR) AVPs.
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Auth-Application-Id |
Supported |
|
Termination-Cause |
Supported |
|
Destination-Host |
Supported |
|
Class |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 15-9 lists the supported Diameter Rx Session-Termination-Answer (STA) AVPs.
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
Table 15-10 lists the supported Diameter Rx Abort-Session-Request (ASR) AVPs.
Table 15-10 Supported ASR AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
Auth-Application-Id |
Supported |
|
Abort-Cause |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
|
Route-Record |
Supported |
Table 15-11 lists the supported Diameter Rx Abort-Session-Answer (ASA) AVPs.
Table 15-11 Supported ASA AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Origin-State-Id |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
This section lists the Diameter Rx AVPs that Services Gatekeeper supports that are not included in the Policy and Charging Control over Rx reference point 3GPP TS 29.214 specification.
Table 15-12 lists the non-standard Diameter Rx AAR AVPs supported by Services Gatekeeper.
Table 15-12 Supported Non-Standard Diameter Rx AAR AVPs
| Name | Code | Vendor ID | Type | Attribute Flag | Notes |
|---|---|---|---|---|---|
|
FramedPort |
4001 |
21274 |
Integer32 |
Ox80 |
The source port of the UE request received by AME. Often this is a NAT assigned port. |
|
requiredAccessInfo |
536 |
10415 |
Integer32 |
0xc0 |
Used for the required access info for different access types such as USER_LOCATION or MS_TIMEZONE. |
Table 15-13 lists the non-standard Diameter Rx AAA AVPs supported by Services Gatekeeper.
Table 15-13 Supported Non-Standard Diameter Rx AAA AVPs
| Name | Code | Vendor ID | Type | Attribute Flag | Notes |
|---|---|---|---|---|---|
|
MsTimeZone |
23 |
10415 |
Byte |
0xc0 |
Contain the hexadecimal representation of the 3GPP-MS-TimeZone defined in 3GPP TS 29.061. |
|
userLocationInfo |
22 |
10415 |
Byte |
0xc0 |
Contain the hexadecimal representation of the 3GPP-User-Location-Info IE as defined in 3GPP TS 29.274. |
|
endUserOpaqueId |
4000 |
21274 |
Byte |
0x80 |
Uniquely identifies a user. |
|
apnAMBRUL |
1041 |
10415 |
Unsigned32 |
0x80 |
Specifies the APN (Access point Name) Aggregate Maximum Bit Rate for Uplink. |
|
apnAMBRDL |
1040 |
10415 |
Unsigned32 |
0x80 |
Specifies the APN (Access point Name) Aggregate Maximum Bit Rate for Downlink. |