* [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]

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

[Result-Code]

268

-

RFC 6733

*[Supported-Vendor-Id]

265

The SAPC sends the values assigned to other supported vendors, different than the vendor device (Ericsson):

• 10415 (3GPP)

• 13019 (ETSI). Supported for Rel10 onwards

RFC 6733

Vendor-Id

266

The SAPC sets it to value 193 (Ericsson).

RFC 6733

*[Vendor-Specific-Application-Id]

260

The SAPC sends the following AVP values:

• Vendor-Id= 10415 (3GPP)

• Auth-Application-Id= 16777236 (3GPP Rx)

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

<Session-Id>

263

-

RFC 6733

[AF-Application-Identifier]

504

-

3GPP TS 29.214

[AF-Charging-Identifier]

505

-

3GPP TS 29.214

{Auth-Application-Id}

258

-

3GPP TS 29.214

[Called-Station-Id]

30

-

See RFC 4005

[Destination-Host]

293

-

RFC 6733

{Destination-Realm}

283

-

RFC 6733

[Framed-IP-Address]⁽¹⁾

8

-

RFC 4005

[Framed-IPv6-Prefix]⁽¹⁾

97

-

RFC 4005

[IP-Domain-Id]

537

-

3GPP TS 29.214

*[Media-Component-Description]

518

See Section 5.2.

3GPP TS 29.214

{Origin-Host}

264

-

RFC 6733

{Origin-Realm}

296

-

RFC 6733

[Origin-State-Id]

278

-

RFC 6733

*[Required-Access-Info]

536

-

3GPP TS 29.214

[Reservation-Priority]

458

-

ETSI TS 183.017

[Rx-Request-Type]

533

The SAPC supports the following values:

• INITIAL_REQUEST (0)

• UPDATE_REQUEST (1)

• PCSCF_RESTORATION (2)⁽²⁾

3GPP TS 29.214

[Service-Info-Status]

527

-

3GPP TS 29.214

[Service-URN]

525

-

3GPP TS 29.214

*[Specific-Action]

513

The SAPC supports the following values:

• INDICATION_OF_RELEASE_OF_BEARER (4)

• INDICATION_OF_SUCCESSFUL_RESOURCES_ALLOCATION (8)

• INDICATION_OF_FAILED_RESOURCES_ALLOCATION (9)

• ACCESS_NETWORK_INFO_REPORT (12)

3GPP TS 29.214

[SIP-Forking-Indication]

523

The SAPC uses the default value SINGLE_DIALOGUE (0), when this AVP is omitted.

3GPP TS 29.214

*S[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.

RFC 4006

*[Supported-Features]

628

See Section 5.1.

3GPP TS 29.229

<Session-Id>

263

-

RFC 6733

{Auth-Application-Id}

258

-

3GPP TS 29.214

[Experimental-Result-Code]

298

See Table 17

3GPP TS 29.214

[Failed-AVP]

279

-

RFC 6733

[Netloc-Access-Support]

2824

The SAPC sends it when the AF requested Netloc, but the PCEF does not support Netloc.

3GPP TS 29.212

{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 SAPC peers are down. This MUST never happen, as the SAPC does a transparent switch-over (the Diameter peer always sees an operative node, the one in active state).

RFC 6733

[Result-Code]

268

-

RFC 6733

*[Supported-Features]

628

See Section 5.1.

3GPP TS 29.229

<Session-Id>

263

-

RFC 6733

[3GPP-MS-TimeZone]

23

The SAPC sends this AVP if the AF requested NetLoc, and if the SAPC received this AVP from the PCEF

3GPP TS 29.061

[3GPP-SGSN-MCC-MNC]

18

note-Netloc

3GPP TS 29.061

[3GPP-User-Location-Info]

22

note-Netloc

3GPP TS 29.061

[Abort-Cause]

500

The SAPC supports the following values:

• BEARER_RELEASED (0)

• PS_TO_CS_HANDOVER (3).

3GPP TS 29.214

{Auth-Application-Id}

258

-

3GPP TS 29.214

{Destination-Host}

293

-

RFC 6733

{Destination-Realm}

283

-

RFC 6733

*[Flows]

510

The SAPC supports the following AVPs:

• { Media-Component-Number }

• *[ Flow-Number ]

3GPP TS 29.214

[Netloc-Access-Support]

2824

The SAPC sends it when the AF requested Netloc, but the IP-CAN session does not support Netloc.

3GPP TS 29.212

{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 node, the one in active state).

RFC 6733

*{Specific-Action}

513

Besides the values listed in *[Specific-Action] in Table 7, the SAPC supports the following values:

• INDICATION_OF_ACCESS_NETWORK_INFO_REPORTING_FAILURE (14)

3GPP TS 29.214

[User-Location-Info-Time]

2812

note-Netloc

3GPP TS 29.212

<Session-Id>

263

-

RFC 6733

[Abort-Cause]

500

The SAPC supports the following values:

• BEARER_RELEASED (0)

• PS_TO_CS_HANDOVER (3).

3GPP TS 29.214

{Auth-Application-Id}

258

-

3GPP TS 29.214

{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 node, the one in active state).

RFC 6733

<Session-Id>

263

-

RFC 6733

*[Required-Access-Info]

536

⁽¹⁾

3GPP TS 29.214

<Session-Id>

263

-

RFC 6733

[3GPP-MS-TimeZone]

23

⁽¹⁾

3GPP TS 29.061

[3GPP-SGSN-MCC-MNC]

18

⁽¹⁾

3GPP TS 29.061

[3GPP-User-Location-Info]

22

⁽¹⁾

3GPP TS 29.061

[Failed-AVP]

279

-

RFC 6733

[Netloc-Access-Support]

2824

The SAPC sends it when the AF requested Netloc, but the PCEF or the IP-CAN session do not support Netloc.

3GPP TS 29.212

{Origin-Host}

264

-

RFC 6733

{Origin-Realm}

296

-

RFC 6733

[Origin-State-Id]

278

-

RFC 6733

[Result-Code]

268

-

RFC 6733

[User-Location-Info-Time]

2812

⁽¹⁾

3GPP TS 29.212

Netloc

If the SAPC receives bit 5 = 1 in AAR command and the Netloc function is enabled, the SAPC answers AAA including bit 5= 1.

Rx Rel10

If the SAPC receives from the AF in AAR command:

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

the SAPC answers AAA including:

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

Rx Rel9

If the SAPC receives from the AF in AAR command:

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

the SAPC answers AAA including:

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

Rx Rel8

If the SAPC receives from the AF in AAR command:

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

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

Rx Rel7

If the SAPC receives from the AF an AAR command without Supported-Features AVP, the SAPC responds AAA with Result-Code AVP set to DIAMETER_MISSING_AVP, including Supported-Features AVP inside Failed-AVP AVP.

[AF-Application-Identifier]

504

-

3GPP TS 29.214

[Flow-Status ]

511

Flow status information provided within the Media-Sub-Component AVP takes precedence over the value provided by this AVP.

3GPP TS 29.214

[Max-Requested-Bandwidth-DL]

515

Downlink bandwidth information provided within the Media-Sub-Component AVP takes precedence over the value provided by this AVP.

3GPP TS 29.214

[Max-Requested-Bandwidth-UL]

516

Uplink bandwidth information provided within the Media-Sub-Component AVP takes precedence over the value provided by this AVP.

3GPP TS 29.214

{Media-Component-Number}

518

-

3GPP TS 29.214

*[Media-Sub-Component]

519

The SAPC supports the following AVPs within it:

• { Flow-Number }

• 0*2[ Flow-Description ]

• [ Flow-Usage ]

•  [ Flow-Status ]

• [ Max-Requested-Bandwidth-UL ]

• [ Max-Requested-Bandwidth-DL ]

3GPP TS 29.214

[Media-Type]

520

-

3GPP TS 29.214

[Reservation-Priority]

458

-

ETSI TS 183.017

[RS-Bandwidth]

521

-

3GPP TS 29.214

[RR-Bandwidth]

522

-

3GPP TS 29.214

DIAMETER_SUCCESS

2001

A request is successfully completed.

DIAMETER_COMMAND_UNSUPPORTED

3001

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

DIAMETER_TOO_BUSY

3004

A session establishment 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 one or more 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 one or more 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 one or more 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.

REQUESTED_SERVICE_NOT_AUTHORIZED

5063

The SAPC rejects new or modified service information because the requested service, as described by the service information provided by the AF, is not consistent with either the related subscription information or operator defined policy rules.

IP-CAN_SESSION_NOT_AVAILABLE

5065

The SAPC rejects a new Rx session setup when it fails to perform session binding within the session information received from the AF to a unique existing IP-CAN session.

UNAUTHORIZED_NON_EMERGENCY_SESSION

5066

The SAPC rejects a new Rx session setup that binds to an emergency IP-CAN session and the Service-URN AVP is missing or does not contain a top-level service type of "sos"