* [ Acct-Application-Id ]

259

-

RFC 6733

* [ Auth-Application-Id ]

258

-

RFC 6733

[ Firmware-Revision ]

367

-

RFC 6733

1* { Host-IP-Address }

257

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

{ Product-Name }

269

-

RFC 6733

* [ Supported-Vendor-Id ]

265

-

RFC 6733

{ Vendor-Id }

266

-

RFC 6733

*[ Vendor-Specific- Application-Id ]

260

-

RFC 6733

*[ Auth-Application-Id ]

258

RFC 6733

[ Error-Message ]

281

-

RFC 6733

[ Failed-AVP ]

279

RFC 6733

[ Firmware-Revision ]

267

-

RFC 6733

1*{ Host-IP-Address }

257

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

{ Product-Name }

269

-

RFC 6733

{ Result-Code }

268

-

RFC 6733

*[ Supported-Vendor-Id ]

265

According to configuration, the SAPC sends the values assigned to other supported vendors different from the vendor device (Ericsson):

• 10415 (3GPP)

• 5535 (3GPP2)

RFC 6733

{ Vendor-Id }

266

The SAPC sets it to value 193 (Ericsson).

RFC 6733

*[ Vendor-Specific- Application-Id ]

260

According to configuration, the SAPC sends the following AVP values:

• Vendor-Id= 10415 (3GPP)

• Auth-Application-Id= 16777238 (3GPP Gx)

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

[ Origin-State-Id ]

278

-

RFC 6733

[ Error-Message ]

281

-

RFC 6733

[ Failed-AVP ]

279

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

[ Origin-State-Id ]

278

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

{ Disconnect-Cause }

273

-

RFC 6733

[ Error-Message ]

281

-

RFC 6733

[ Failed-AVP ]

279

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

{ Result-Code }

268

-

RFC 6733

Control

Related AVPs

IP-CAN Session Access Control

If the trigger is the reception of a CCR:

• To accept the request, the SAPC answers with a CCA with the Result-Code AVP indicating success.

• To reject the request, the SAPC answers with the Result-Code AVP indicating DIAMETER_AUTHORIZATION_ REJECTED (5003).

If the trigger is an internal reauthorization, and the session terminates, the SAPC sends a RAR containing Session-Release-Cause = UE_SUBSCRIPTION_REASON.

Service Access Control

Charging-Rule-Authorization AVP

Charging-Rule-Install AVP, including:

• Charging-Rule-Name AVP

• Charging-Rule-Base-Name AVP

Charging-Rule-Definition AVP (for preconfigured or dynamic services). The charging information is included depending on the Service Charging Control.

Bearer-Identifier AVP

Charging-Rule-Remove AVP, including:

• Charging-Rule-Name AVP

• Charging-Rule-Base-Name AVP

Related to ToD, and when the PCEF is the time controller:

• Revalidation-Time

• Rule-Activation-Time and Rule-Deactivation-Time AVPs included within the Charging-Rule-Definition AVP

• REVALIDATION_TIMEOUT value for Event-Trigger AVP

Bearer QoS Control

⁽¹⁾

QoS-Information AVP

Default-EPS-Bearer-QoS AVP

Subscriber Charging Control

Online AVP at CCA level

Offline AVP at CCA level

3GPP-Charging-Characteristics AVP

Charging-Information AVP

Service Charging Control

Charging-Rule-Install AVP, including:

• Service-Identifier AVP

• Rating-Group AVP

• Reporting-Level AVP

• Online AVP

• Offline AVP

• Metering-Method AVP

• AF-Charging-Identifier AVP

Usage Reporting

Usage-Monitoring-Information AVP

Content Filtering Control

Content-Filtering-Profile-Id AVP

< Session-Id >

263

-

RFC 6733

[ 3GPP-Charging-Characteristics ]

13

3GPP-Charging-Characteristics AVP is of type UTF8String and is defined according to 3GPP TS 29 061 (Reference [3]) and transformed into a Diameter AVP.

3GPP TS 29 061

[ 3GPP-MS-TimeZone ]

23

-

3GPP TS 29 061

[ 3GPP-SGSN-MCC-MNC ]

18

-

3GPP TS 29 061

[ 3GPP-SGSN-Address ]

6

-

3GPP TS 29 061

[ 3GPP-SGSN-IPv6-Address ]

15

-

3GPP TS 29 061

[ 3GPP-User-Location-Info ]

22

-

3GPP TS 29 061

0*2[ AN-GW-Address ]

1050

-

3GPP TS 29.212

[ AN-Trusted ]

1503

-

3GPP TS 29.273

*[ Application-Detection-Information ]⁽¹⁾

1098

The SAPC supports the following AVPs:

• {TDF-Application-Identifier}

• [TDF-Application-Instance-Identifier]

• *[Flow-Information]

3GPP TS 29.212

{ Auth-Application-Id }

258

-

3GPP TS 29.212

[ Bearer-Identifier ]

1020

-

3GPP TS 29.212

[ Bearer-Operation ]

1021

-

3GPP TS 29.212

[ Bearer-Usage ]

1000

-

3GPP TS 29.212

[ Called-Station-Id ]

30

-

See RFC 4005

{ CC-Request-Number }

415

-

RFC 4006

{ CC-Request-Type }

416

-

RFC 4006

*[ Charging-Rule-Report ]

1018

See Section 6.3

3GPP TS 29.212

[ Default-EPS-Bearer-QoS ]

1049

See Section 6.5

3GPP TS 29.212

{ Destination-Realm }

283

-

RFC 6733

[ Destination-Host ]

293

-

RFC 6733

*[ Event-Trigger ]

1006

The SAPC supports the following values:

• SGSN_CHANGE (0)

• QoS_CHANGE(1)

• RAT_CHANGE (2)

• PLMN_CHANGE (4)

• IP-CAN_CHANGE (7).

• RAI_CHANGE (12)

• USER_LOCATION_CHANGE (13)

• OUT_OF_CREDIT (15)

• REALLOCATION_OF_CREDIT (16)

• REVALIDATION_TIMEOUT (17)

• DEFAULT_EPS_BEARER_QOS_CHANGE (20)

• AN_GW_CHANGE (21)

• SUCCESSFUL_RESOURCE_ALLOCATION (22)

• UE_TIME_ZONE_CHANGE (25)

• TAI_CHANGE (26)

• ECGI_CHANGE (27)

• APN-AMBR_MODIFICATION_FAILURE (29)

• USAGE_REPORT (33)

• DEFAULT-EPS-BEARER-QOS_MODIFICATION_FAILURE (34)

• APPLICATION_START (39).

• APPLICATION_STOP (40).

• ACCESS_NETWORK_INFO_REPORT (45).

• CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT (48).

3GPP TS 29.212

[ Framed-IP-Address ]⁽²⁾

⁽³⁾

8

The SAPC identifies the subscriber IP-CAN session using Framed-IP-Address AVP together with Called-Station-Id AVP and Subscription-Id AVP.

RFC 4005

[ Framed-IPv6-Prefix ]

⁽²⁾

⁽³⁾

97

The SAPC identifies the subscriber IP-CAN session using Framed-IPv6-Prefix AVP together with Called-Station-Id AVP and Subscription-Id AVP.

RFC 4005

[ IP-CAN-Type ]

1027

The SAPC supports the following values:

• 3GPP-GPRS (0)

• DOCSIS (1)

• xDSL (2)

• WiMAX (3)

• 3GPP2 (4)

• 3GPP-EPS (5)

• Non-3GPP-EPS (6)

• FBA (7)

3GPP TS 29.212

[ Network-Request-Support ]

1024

-

3GPP TS 29.212

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

[ Origin-State-Id ]

278

-

RFC 6733

[ Presence-Reporting-Area-Information ]

2822

See Section 6.7

3GPP TS 29.212

[ QoS-Information ]

1016

See Section 6.4.

3GPP TS 29.212

[ QoS-Negotiation ]

1029

-

3GPP TS 29.212

[ QoS-Upgrade ]

1030

-

3GPP TS 29.212

[ RAI ]

909

-

3GPP TS 29 061

[ RAT-Type ]

1032

-

3GPP TS 29.212

*[ Subscription-Id ]

443

If the SAPC receives several instances of this AVP, it uses:

• The value contained in Subscription-Id-Data of the first Subscription-Id AVP received

• Or the value contained in Subscription-Id-Data corresponding to the Subscription-Id-Type set in a configurable parameter in the SAPC.

For IP-CAN sessions restricted to IMS emergency services, Subscription-Id AVP is optional in the CCR INITIAL message. If Subscription-Id AVP is not received, the CCR INITIAL message must include the IMEISV within the User-Equipment-Info AVP.

RFC 4006

*[ Supported-Features ]

628

See Section 6.1.

TS 29.229

[ TWAN-Identifier ]

29

-

3GPP TS 29 061

[ TDF-Information ]

1087

See Section 6.8.

3GPP TS 29.212

[ TCP-Source-Port ]

2843

-

3GPP TS 29.212

[ UDP-Source-Port ]

2806

-

3GPP TS 29.212

[ UE-Local-IP-Address ]

2805

-

3GPP TS 29.212

*[ Usage-Monitoring-Information ]

1067

-

3GPP TS 29.212

[ User-Equipment-Info ]

458

-

RFC 4006

[ User-Location-Info-Time ]

2812

3GPP TS 29.212

< Session-Id >

263

-

RFC 6733

{ Auth-Application-Id }

258

-

3GPP TS 29.212

[ Bearer-Control-Mode ]

1023

For CCA Initial, the SAPC sets its value to:

• UE_ONLY (0) if Network-Request-Support AVP received with value Network Request Not Supported, or if the Network-Request-Support AVP was not received.

• UE_NW (2) if Network-Request-Support AVP was received in CCR with value Network Request Supported

For CCA updates, the SAPC include this AVP only if Network-Request-Support AVP was received in the CCR, and sets its value to:

• UE_ONLY (0) if Network-Request-Support AVP received with value Network Request Not Supported.

• UE_NW (2) if Network-Request-Support AVP was received in CCR with value Network Request Supported.

3GPP TS 29.212

{ CC-Request-Number }

415

The SAPC includes the same value as received in the CCR.

3GPP TS 29.212

{ CC-Request-Type }

416

The SAPC includes the same value as received in the CCR.

3GPP TS 29.212

[ Charging-Information ]

618

-

TS 29.229

*[ Charging-Rule-Install ]

1001

See Section 6.2.

3GPP TS 29.212

*[ Charging-Rule-Remove ]

1002

-

3GPP TS 29.212

[ Default-EPS-Bearer-QoS ]

1049

See Section 6.5.

3GPP TS 29.212

*[ Event-Trigger ]

1006

The SAPC includes this AVP in the CCA Initial and CCA Update messages.

The SAPC provides a new complete list of applicable event triggers for adding new event triggers or removing provisioned event triggers. If the SAPC does not include the Event-Trigger AVP in the CCA message, the previously provisioned event triggers are still applicable. If the SAPC includes the value NO_EVENT_TRIGGERS (14) in the CCA message, the previously provisioned event triggers are removed.

See eventTriggers.

3GPP TS 29.212

[ Experimental-Result ]

297

-

RFC 6733

[ Failed-AVP ]

279

-

RFC 6733

[ Offline ]

1008

-

3GPP TS 29.212

[ Online ]

1009

-

3GPP TS 29.212

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

[ Presence-Reporting-Area-Information ]

2822

See Section 6.7

3GPP TS 29.212

[ Origin-State-Id ]

278

The SAPC increments its value in standalone mode after restart.

In geographical redundancy, the SAPC does not increment its value unless both peers are down. This MUST never happen, as the SAPC does a transparent switch-over (the Diameter peer always sees an operative SAPC, the one in active state).

RFC 6733

[ QoS-Information ]

1016

See Section 6.4.

3GPP TS 29.212

[ Result-Code ]

268

-

RFC 6733

[ Revalidation-Time ]

1042

-

3GPP TS 29.212

*[ Supported-Features ]

628

-

TS 29.229

*[ Usage-Monitoring-Information ]

1067

See Section 6.6.

3GPP TS 29.212

< Session-Id >

263

-

RFC 6733

{ Auth-Application-Id }

258

-

3GPP TS 29.212

*[ Charging-Rule-Install ]

1001

See Section 6.2.

3GPP TS 29.212

*[ Charging-Rule-Remove ]

1002

-

3GPP TS 29.212

[ Default-EPS-Bearer-QoS ]

1049

See Section 6.5.

3GPP TS 29.212

*[ Event-Trigger ]

1006

The SAPC provides a new complete list of applicable event triggers for adding new event triggers or removing provisioned event triggers. If the SAPC does not include the Event-Trigger AVP in the RAR message, the previously provisioned event triggers are still applicable. If the SAPC includes the value NO_EVENT_TRIGGERS (14) in the RAR message, the previously provisioned event triggers are removed.

See eventTriggers.

3GPP TS 29.212

{ Destination-Host }

293

-

RFC 6733

{ Destination-Realm }

283

-

RFC 6733

{ Origin-Host }

264

-

RFC 6733

{ Origin-Realm }

296

-

RFC 6733

[ Origin-State-Id ]

278

The SAPC increments its value in standalone mode after restart.

In geographical redundancy, the SAPC does not increment its value unless both peers are down. This MUST never happen, as the SAPC does a transparent switch-over (the Diameter peer always sees an operative SAPC, the one in active state).

RFC 6733

[ QoS-Information ]

1016

See Section 6.4.

3GPP TS 29.212

{ Re-Auth-Request-Type }

285

The SAPC supports the following values:

• AUTHORIZE_ONLY (0)

RFC 6733

[ Revalidation-Time ]

1042

-

3GPP TS 29.212

[ Session-Release-Cause ]

1045

The SAPC supports the following values:

• UE_SUBSCRIPTION_REASON (1)

3GPP TS 29.212

*[ Usage-Monitoring-Information ]

1067

See Section 6.6.

3GPP TS 29.212

0*2[ AN-GW-Address ]

1050

-

3GPP TS 29.212

[ AN-Trusted ]

1503

-

3GPP TS 29.273

[ Experimental-Result ]

297

The SAPC supports the following value within Experimental-Result-Code AVP:

• DIAMETER_PENDING_TRANSACTION (4144)

3GPP TS 29.212

[ IP-CAN-Type ]

1027

See Table 8.

3GPP TS 29.212

[ NetLoc-Access-Support ]

2824

It is present when NetLoc is requested by the AF, but the IP-CAN session does not support NetLoc.

3GPP TS 29.212

[ RAT-Type ]

1032

-

3GPP TS 29.212

[ Result-Code ]

268

The SAPC supports the following values:

• DIAMETER_SUCCESS (2001)

• DIAMETER_OUT_OF_SPACE (4002)

• DIAMETER_UNKNOWN_SESSION_ID (5002)

• DIAMETER_USER_UNKNOWN (5030)

RFC 6733

PRA

If the SAPC receives bit 23 = 1 in CCR command and the PRA function is enabled, the SAPC answers CCA including bit 23 = 1.

Pending Transaction

If the SAPC receives bit 16 = 1 in CCR command, it answers CCA including bit 16 = 1.

NetLoc-Untrusted-WLAN

If the SAPC receives bit 30 = 1 in CCR command and the NetLoc function is enabled, the SAPC answers CCA including bit 30 = 1. It requires that the SAPC also receives bit 10 = 1.

NetLoc

If the SAPC receives bit 10 = 1 in CCR command and the NetLoc function is enabled, the SAPC answers CCA including bit 10 = 1.

ADC

If the SAPC receives bit 6 = 1 in CCR command and the ADC Rule function is enabled, the SAPC answers CCA including bit 6 = 1.

ProvAFsignalFlow

If the SAPC receives bit 2 = 1 in CCR command and the dynamic policy control function is enabled, the SAPC answers CCA including bit 2 = 1.

Gx Rel10 onwards

If the SAPC receives from the PCEF in CCR command:

Supported-Features
   { Vendor-Id = 10415 }
   { Feature-List-ID = 1 }
   { Feature-List
        bit 0 = x (any value)
        bit 1 = x (any value)
        bit 3 = 1
        rest of bits = x (any value)}

the SAPC answers CCA including:

Supported-Features
   { Vendor-Id = 10415 }
   { Feature-List-ID = 1 }
   { Feature-List
        bit 0 = x (same value than received in CCR)
        bit 1 = x (same value than received in CCR)
        bit 3 = 1
        rest of bits = 0 }

Gx Rel9

If the SAPC receives from the PCEF in CCR command:

Supported-Features
   { Vendor-Id = 10415 }
   { Feature-List-ID = 1 }
   { Feature-List
        bit 0 = x (any value)
        bit 1 = 1
        bit 3 = 0
        rest of bits = x (any value)}

the SAPC answers CCA including:

Supported-Features
   { Vendor-Id = 10415 }
   { Feature-List-ID = 1 }
   { Feature-List
        bit 0 = x (same value than received in CCR)
        bit 1 = 1
        bit 3 = 0
        rest of bits = 0 }

Gx Rel8

If the SAPC receives from the PCEF in CCR command:

Supported-Features
   { Vendor-Id = 10415 }
   { Feature-List-ID = 1 }
   { Feature-List
        bit 0 = 1
        bit 1 = 0
        bit 3 = 0
        rest of bits = x (any value)}

the SAPC answers CCA with Result-Code AVP set to DIAMETER_INVALID_AVP_VALUE, and including Supported-Features AVP inside Failed-AVP AVP.

Gx Rel7

If the SAPC receives from a PCEF a Gx message without Supported-Features AVP, the SAPC responds with Result-Code AVP set to DIAMETER_MISSING_AVP, including Supported-Features AVP inside Failed-AVP AVP.

Extended-BW-NR

If the SAPC receives bit 7 = 1 in CCR command and the extended bit rates over Gx function is licensed, the SAPC answers CCA including bit 7 = 1.

[ Bearer-Identifier ]

1020

The SAPC includes Bearer-Identifier AVP only for UE_ONLY bearer control mode, and if it was received from the PCEF.

3GPP TS 29.212

*[ Charging-Rule-Base-Name ]

1004

-

3GPP TS 29.212

*[ Charging-Rule-Definition ]

1003

The Charging-Rule-Install AVP can contain several Charging-Rule-Definition AVPs that define PCC rules for service data flows that use IPv4, IPv6 or both.

The flows for a PCC rule are sent in one or several Flow-Information AVPs inside the same Charging-Rule-Definition AVP, according to the PCC rule information configured in the SAPC.

For PCC rules derived from AF, the SAPC includes several Charging-Rule-Definition AVPs (one per media subcomponent) inside a Charging-Rule-Install AVP.

See Section 6.2.1.

3GPP TS 29.212

*[ Charging-Rule-Name ]

1005

-

3GPP TS 29.212

[ Resource-Allocation- Notification ]

1063

The SAPC supports the following values:

• ENABLE_NOTIFICATION (0)

3GPP TS 29.212

[ Rule-Activation-Time ]

1043

-

3GPP TS 29.212

[ Rule-Deactivation-Time ]

1044

-

3GPP TS 29.212

[ AF-Charging-Identifier ]

505

-

3GPP TS 29.214

[ AF-Signalling-Protocol ]

529

-

3GPP TS 29.214

{ Charging-Rule-Name }

1005

-

3GPP TS 29.212

*[ Flow-Information ]

1058

The SAPC sends the following AVPs:

• [Flow-Description]

• [Flow-Direction]

3GPP TS 29.212

[ Flow-Status ]

511

The SAPC sets it to ENABLED for preconfigured PCC rules.

The SAPC sends the value received from Rx interface for dynamic PCC rules.

3GPP TS 29.214

*[ Flows ]

510

-

3GPP TS 29.214

[ Metering-Method ]

1007

It is configured in the SAPC at service level.

3GPP TS 29.212

[ Mute-Notification ]⁽¹⁾

2809

-

3GPP TS 29.212

[ Offline ]

1008

It is set in the SAPC at service level.

3GPP TS 29.212

[ Online ]

1009

It is set in the SAPC at service level.

3GPP TS 29.212

[ Precedence ]

1010

See Section 6.2.1.2.

3GPP TS 29.212

[ QoS-Information ]

1016

It can be set in the SAPC at service level or derived from AF information.

3GPP TS 29.212

[ Rating-Group ]

432

It is set in the SAPC at service level.

RFC 4006

[ Redirect-Information ]

1085

The SAPC sends the following AVPs:

[Redirect-Support]

[Redirect-Address-Type]

[Redirect-Server-Address]

3GPP TS 29.212

*[ Required-Access-Info ]

536

The SAPC sets this AVP only when the AF requests the SAPC to report Access Network Information.

3GPP TS 29.214

[ Reporting-Level ]

1011

The SAPC supports the following values:

• SERVICE_IDENTIFIER_LEVEL (0)

• RATING_GROUP_LEVEL (1)

It is configured in the SAPC at service level.

3GPP TS 29.212

[ Service-Identifier ]

439

It is configured in the SAPC at service level.

RFC 4006

[ TDF-Application-Identifier ]⁽²⁾

1088

-

3GPP TS 29.212

bit 7

bit 6

bit 5

bit 4

bit 3

bit 2

bit 1

bit 0

Configurable for preconfigured PCC rules

Dynamic part

[ Bearer-Identifier ]

1020

-

3GPP TS 29.212

*[ Charging-Rule-Base-Name ]

1004

-

3GPP TS 29.212

*[ Charging-Rule-Name ]

1005

-

3GPP TS 29.212

[ PCC-Rule-Status ]

1019

The SAPC supports the following values:

• ACTIVE (0)

• INACTIVE (1)

3GPP TS 29.212

[ Rule-Failure-Code ]

1031

The SAPC supports the following values:

• UNKNOWN_RULE_NAME (1)

• RATING_GROUP_ERROR (2)

• SERVICE_IDENTIFIER_ERROR (3)

• GWPCEF_MALFUNCTION (4)

• RESOURCES_LIMITATION (5)

• MAX_NR_BEARERS_REACHED (6)

• UNKNOWN_BEARER_ID (7)

• MISSING_BEARER_ID (8)

• MISSING_FLOW_INFORMATION (9)

• RESOURCE_ALLOCATION_FAILURE (10)

• UNSUCCESSFUL_QOS_VALIDATION (11)

• INCORRECT_FLOW_INFORMATION (12)

• PS_TO_CS_HANDOVER (13) ⁽¹⁾

• TDF_APPLICATION_IDENTIFIER_ERROR (14)

• NO_BEARER_BOUND (15)

• MISSING_REDIRECT_SERVER_ADDRESS (18)

3GPP TS 29.212

[ Allocation-Retention-Priority ]

1034

-

3GPP TS 29.212

[ APN-Aggregate-Max-Bitrate-DL ]

1040

-

3GPP TS 29.212

[ APN-Aggregate-Max-Bitrate-UL ]

1041

-

3GPP TS 29.212

[ Bearer-Identifier ]

1020

The SAPC includes Bearer-Identifier AVP, if it was received from the PCEF in the CCR messages.

3GPP TS 29.212

[ Extended-APN-AMBR-DL ]

2848

The SAPC includes Extended-APN-AMBR-DL AVP instead of APN-Aggregate-Max-Bitrate-DL if the bandwidth value sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.212

[ Extended-APN-AMBR-UL ]

2849

The SAPC includes Extended-APN-AMBR-UL AVP instead of APN-Aggregate-Max-Bitrate-UL if the bandwidth value to be sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.212

[ Extended-GBR-DL ]

2850

The SAPC includes Extended-GBR-DL AVP instead of Guaranteed-Bitrate-DL if the bandwidth value sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.212

[ Extended-GBR-UL ]

2851

The SAPC includes Extended-GBR-UL AVP instead of Guaranteed-Bitrate-UL if the bandwidth value sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.212

[ Extended-Max-Requested-BW-DL ]

554

The SAPC includes Extended-Max-Requested-BW-DL AVP instead of Max-Requested-Bandwidth-DL if the bandwidth value sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.214

[ Extended-Max-Requested-BW-UL ]

555

The SAPC includes Extended-Max-Requested-BW-UL AVP instead of Max-Requested-Bandwidth-UL if the bandwidth value sent to the PCEF is higher than 2³²-1 bps.

3GPP TS 29.214

[ Guaranteed-Bitrate-DL ]

1025

-

3GPP TS 29.212

[ Guaranteed-Bitrate-UL ]

1026

-

3GPP TS 29.212

[ Max-Requested-Bandwidth-DL ]

515

-

3GPP TS 29.214

[ Max-Requested-Bandwidth-UL ]

516

-

3GPP TS 29.214

{ QoS-Class-Identifier }

1028

-

3GPP TS 29.212

[ Allocation-Retention-Priority ]

1034

The SAPC supports the following AVPs:

• {Priority-Level}

• [Pre-emption-Capability]

• [Pre-emption-Vulnerability]

3GPP TS 29.212

[ QoS-Class-Identifier ]

1028

-

3GPP TS 29.212

[ Monitoring-Key ]

1066

-

3GPP TS 29.212

[ Used-Service-Unit ]

446

The SAPC supports the following AVPs:

• [CC-Input-Octets]

• [CC-Output-Octets]

• [CC-Total-Octets]

RFC 4006

[ Granted-Service-Unit ]

431

The SAPC supports the following AVPs:

• [CC-Input-Octets]

• [CC-Output-Octets]

• [CC-Total-Octets]

RFC 4006

[ Monitoring-Key ]

1066

-

3GPP TS 29.212

[ Usage-Monitoring-Level ]

1068

The SAPC supports the following values:

• SESSION_LEVEL (0)

• PCC_RULE_LEVEL (1)

3GPP TS 29.212

[ Usage-Monitoring-Report ]

1069

The SAPC supports the following values:

• USAGE_MONITORING_REPORT_REQUIRED (0)

3GPP TS 29.212

[ Usage-Monitoring-Support ]

1070

The SAPC supports the following values:

• USAGE_MONITORING_DISABLED (0)

3GPP TS 29.212

[ Presence-Reporting-Area-Identifier ]

2821

Only valid for CCR-Update and CCA-Initial message.

3GPP TS 29.212

[ Presence-Reporting-Area-Status ]

2823

Only valid for CCR-Update message.

The SAPC supports the following values:

• In Area (0)

• Out of Area (1)

3GPP TS 29.212

[ Presence-Reporting-Area-Elements-List ]

2820

Only valid for CCA-Initial message.

3GPP TS 29.212

[ TDF-Destination-Host ]⁽¹⁾

1089

Only valid with the TDF-Destination-Realm AVP.

3GPP TS 29.212

[ TDF-Destination-Realm ]⁽²⁾

1090

Only valid with the TDF-Destination-Host AVP.

3GPP TS 29.212

[ TDF-IP-Address ]

1091

The address type can be IPv4 or IPv6.

3GPP TS 29.212

[ 3GPP-Charging-Characteristics ]

13

3GPP-Charging-Characteristics AVP is of type UTF8String and is defined according to 3GPP TS 29 061 (Reference [3]) and transformed into a Diameter AVP.

3GPP TS 29 061

[ Gx-Capability-List ]

1060

Gx-Capability-List AVP is of type Unsigned32. It can be included in the CCR initial for the IP-CAN session by the PCEF indicating the Ericsson offered proprietary capabilities.

This negotiated Gx capability list is applicable for the lifetime of the IP-CAN session (and it is ignored if received again).

If this negotiation is not present, the SAPC works in standard 3GPP Gx mode.

Each bit, numbered 0-31 starting from the least significant bit, is used to indicate a separate function. The least significant bit is designated as bit 0.

See Section 8.2

[ Rule-Space-Suggestion ]

290

Rule-Space-Suggestion AVP is of type OctetString. It can be included in the initial CCR.

[ Rule-Space-Decision ]

291

Rule-Space-Decision AVP is of type OctetString and can be included in initial CCR/CCA.

If the Rule-Space-Decision AVP is received in the CCR, the SAPC does not change it, and does not include Rule-Space-Decision AVP in the CCA.

[ 3GPP-Charging-Characteristics ]

13

The SAPC returns this AVP in CCA (2 octets value), if configured in the SAPC at subscriber level and the capability Charging characteristics retrieval is negotiated.

3GPP TS 29 061

[ Charging-Rule-Authorization ]

1055

The SAPC can add this AVP inside Charging-Rule-Install AVP.

See Section 8.1.

[ Content-Filtering-Profile-Id ]

1138

The Content-Filtering-Profile-Id AVP is of type Unsigned 32. It is used to select a local content filtering profile identifier in the Ericsson PCEF. The SAPC uses the special value 0xFFFFFFFF to indicate to the PCEF to remove the previously downloaded value.

The SAPC includes it in CCA Initial message, if provisioned in the SAPC at subscriber level and the capability Content Filtering is negotiated.

The SAPC includes it in CCA Update, only if its value is different than the value previously sent.

[ Customer-Id ]

1146

It contains the customer identifier of the PDP context (used for HTTP Header Enrichment) and is primarily intended to replace the MSISDN as the user identity sent out to applications on the Internet. This AVP is an Ericsson proprietary addition, but it is not negotiated in the Gx-Capability-List. It is only sent in CCA initial, if configured in the SAPC at subscriber level. It contains an ASCII value of variable length, between 1-25 octets, and cannot include special characters.

[ Gx-Capability-List ]

1060

-

See Section 8.2.

[ Rule-Space-Decision ]

291

If the Rule-Space-Suggestion AVP is included in the CCR, this indicates to the SAPC can override this suggestion by including the Rule-Space-Decision AVP in the CCA initial.

[ Charging-Rule-Authorization ]

1055

The SAPC can add this AVP inside Charging-Rule-Install AVP.

See Section 8.1.

[ Content-Filtering-Profile-Id ]

1138

See avp-ContentFilter.

The SAPC only includes it in RAR message, if there is a change compared to the value that sent to the PCEF in a previous CCA or RAR message.

AUTHORIZED

0

DENIED_CALENDAR_TIME

1

DENIED_ROAMING

2

DENIED_QUALITY_OF_SERVICE

3

DENIED_BLACKLISTED

4

DENIED_TERMINAL

5

DENIED_OPERATOR_REASON_ONE

6

DENIED_OPERATOR_REASON_TWO

7

DENIED_OPERATOR_REASON_THREE

8

DENIED_OPERATOR_REASON_FOUR

9

DENIED_OPERATOR_REASON_FIVE

10

DENIED_UNKNOWN_REASON

11

DENIED_USAGE_CONTROL

12

0

Enhanced service authorization control

If set, use of non-authorization codes is possible

1

Not used

-

2

Not used

-

3

Rule Space negotiation

Rule Space negotiation is possible.

4

Charging Characteristics retrieval

If set, the SAPC is able to retrieve the Charging Characteristics specified for the subscriber and return it to the PCEF.

5

Not used

Set to 0

6

Not used

Set to 0

7

Not used

Set to 0

8

Not used

Set to 0

9

Not used

Set to 0

10-11

Reserved for future use

Set to 0.

12

Support of Content Filtering Profile Id

Set to 1 if Content Filtering Profile Id is supported.

13

Reserved for future use

Set to 0.

14

-

Not used for backward compatibility reasons

15

Reserved for future use

Reserved bits are set to zero for forward compatibility reasons

16

One-Time-Redirect

If set, One-Time-Redirect is enabled.

17-31

Reserved for future use

Reserved bits are set to zero for forward compatibility reasons

DIAMETER_SUCCESS

2001

A request is successfully completed.

DIAMETER_COMMAND_UNSUPPORTED

3001

A request contains a Command-Code that the SAPC does not recognize or support.

DIAMETER_TOO_BUSY

3004

A request is received when the SAPC is overloaded.

DIAMETER_APPLICATION_UNSUPPORTED

3007

A request is received for an unsupported application.

DIAMETER_INVALID_HDR_BITS

3008

A request is received with a Diameter header whose bits are set to an invalid combination or to a value that is inconsistent with the Command-Code definition.

DIAMETER_INVALID_AVP_BITS

3009

A request is received with an AVP whose flag bits are set to an unrecognized value or are inconsistent with the AVPs definition.

DIAMETER_UNKNOWN_PEER

3010

A CER message is received from an unknown peer.

DIAMETER_OUT_OF_SPACE

4002

A Diameter node received the request but was unable to commit it to stable storage due to a temporary lack of space.

ELECTION_LOST

4003

The peer has determined that it has lost the election process and has therefore disconnected the transport connection.

DIAMETER_AVP_UNSUPPORTED

5001

A request is received with an AVP that is not recognized or supported (not included in the SAPC Diameter dictionary) and was marked with the Mandatory bit.

A Diameter message with this error must contain a Failed-AVP AVP containing the AVPs that caused the failure.

DIAMETER_UNKNOWN_SESSION_ID

5002

Returned if the session does not exist for the UE IP address at session modification/termination.

DIAMETER_INVALID_AVP_VALUE

5004

A request is received with an AVP with an invalid value in its data portion.

A Diameter message with this error must contain a Failed-AVP AVP containing the AVPs that caused the failure.

DIAMETER_MISSING_AVP

5005

When a request is received including an AVP that is not required to process that request, that AVP is ignored and the request is processed as usual. On the contrary, when a request does not include an AVP that is required to process such request, the SAPC returns a response including Result-Code DIAMETER_MISSING_AVP and the Failed-AVP AVP.

DIAMETER_CONTRADICTING_AVPS

5007

A request is received with AVPs that are contradicted each other.

A Diameter message with this error must contain a Failed-AVP AVP containing the AVPs that caused the failure.

DIAMETER_AVP_NOT_ALLOWED

5008

A request is received with an AVP that must not be present.

A Diameter message with this error must contain a Failed-AVP AVP with a copy of the offending AVP.

DIAMETER_AVP_OCCURS_TOO_MANY_TIMES

5009

A request is received with an AVP that appears more often than permitted in the message definition.

A Diameter message with this error must contain a Failed-AVP AVP with a copy of the first instance of the offending AVP that exceeded the maximum number of occurrences.

DIAMETER_NO_COMMON_APPLICATION

5010

A CER message is received and there are no common applications supported between the SAPC and the peer.

DIAMETER_UNSUPPORTED_VERSION

5011

A request is received with an unsupported version number.

DIAMETER_UNABLE_TO_COMPLY

5012

This error is returned when the SAPC receives a request and detects an internal error which does not allow to continue processing a request.

DIAMATER_INVALID_BIT_IN_HEADER

5013

A request is received with an unrecognized bit in the Diameter header is set to one.

DIAMETER_INVALID_AVP_LENGTH

5014

A request is received containing an AVP with an invalid length.

A Diameter message with this error must contain a Failed-AVP AVP containing the offending AVP.

DIAMETER_INVALID_MESSAGE_LENGTH

5015

A request is received with an invalid message length.

DIAMETER_INVALID_AVP_BIT_COMBO

5016

A request is received with an AVP which is not allowed to have the received value in the AVP Flags field.

A Diameter message with this error must contain a Failed-AVP AVP containing the offending AVP.

DIAMETER_NO_COMMON_SECURITY

5017

This error is returned when a CER message is received, and there are no common security mechanisms supported between the peers.

A CEA MUST be returned with the Result-Code AVP set to DIAMETER_NO_COMMON_SECURITY.

DIAMETER_AUTHORIZATION_REJECTED

5003

A request is received for which the subscriber could not be authorized, owing to IP-CAN Session Access Control.

DIAMETER_USER_UNKNOWN

5030

This error is returned when the subscriber specified in the Subscription-Id AVP is not known in the SAPC at session activation or modification

DIAMETER_PENDING_TRANSACTION

4144

Received if the PCEF cannot determine that Gx RAR message can be safely handled without creating a state mismatch.

DIAMETER_ERROR_INITIAL_PARAMETERS

5140

This error is returned when the SAPC receives a CCR INITIAL for an emergency IP-CAN session establishment where:

• The Subscription-Id AVP is missing and unauthenticated emergency services are not allowed

• Unauthenticated emergency services are allowed, but both Subscription-Id and User-Equipment-Info AVPs are missing