Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Diameter Messages in TDF Subscriber Sessions Overview

 

This topic contains the following sections that describe the RADIUS messages that are exchanged between the Diameter peers, which are configured on the routers that function as the Services Control Gateway over Gx interfaces. Diameter peers communicate over a reliable TCP transport layer connection by exchanging Diameter messages that convey status, requests, and acknowledgements by means of standard Diameter attribute-value pairs (AVPs) and application-specific AVPs. Each Diameter network element can be associated with one or more functions and consists of a prioritized list of peers.

Table 1 describes the attributes that are present and contained in the Credit Control Request-Initiate (CCR-I) messages.

Table 1: AVPs in Credit Control Request-Initiate (CCR-I) Messages

AVP-Name

Presence (Session triggered by Acct-Req from GGSN/PGW)

Presence (Session triggered by UE Packet triggered)

Presence (Session triggered by Acct-Req from BNG)

Condition

Derived From

Auth-Application-id

Mandatory

Mandatory

Mandatory

Gx (16777238)

The 3GPP Gx Application-Id. It is set by the TDF.

Session-Id

Mandatory

Mandatory

Mandatory

Identifies the session

Set by the TDF.

Origin-realm

Mandatory

Mandatory

Mandatory

Configuration.

Origin-Host

Mandatory

Mandatory

Mandatory

Configuration.

Origin-State-id

Mandatory

Mandatory

Mandatory

This field contains the state associated to the TDF

TDF generated Number; Incremented on every restart.

Destination-realm

Mandatory

Mandatory

Mandatory

Configuration

TDF-Information

This AVP needs to be included if it is configured.

This AVP needs to be included if it is configured.

This AVP needs to be included if it is configured.

TDF identity. It contains:

  • – TDF-Destination-Realm

  • TDF-Destination-Host

  • TDF-IP-Address

TDF identity. It is configurable on the TDF.

CC-Request-Type

Mandatory

Mandatory

Mandatory

INITIAL_REQUEST.

Set by the TDF.

CC-Request-Number

Mandatory

Mandatory

Mandatory

Can Start with 0.

Generated by the TDF and incremented for each CCR

Subscription-Id

Mandatory

Not present

Not present

More than one AVPs of this type can be included to report more than one Subscription-Id i.e. IMSI and MSISDN.

IMSI/MSISDN received in the RADIUS Accounting-Request message.

Username

Not present

Not present

Conditional

Specifies the username for a fixed device. For a subscriber managed by AAA, the value is the subscriber’s login name. For a static interface, the value is the interface name, which is used as the subscriber’s login name.

The username from the User-Name AVP in Accounting-Request Start message. APN/VRF for wireline APN from Accounting-Request or from configuration.

Called-Station-Id

Mandatory

Conditional (If configured on TDF for incoming VRFs)

Conditional (If configured on TDF for incoming VRFs)

APN/VRF for wireline.

APN from Accounting-Request or from configuration.

Framed-IP-Address

Conditional

Mandatory

Conditional

Note: It needs to be possible for the TDF to create 2 sessions for the same IMSI, in case both IPv4 and IPv6 flows arrive on TDF from the same UE.

Received in the Accounting-Request message or the source IP address of the data packet.

Framed-IPv6-Prefix

Conditional

Mandatory

Conditional

In UE data packet triggered case the initial CCR-I will contain source IP address with /64 prefix. Correct prefix is received from PCRF in CCA-I.

Received in the Accounting-Request message.

IP-CAN-Type

Not present

Not present

Not present

Event-Report-Indication

Conditional

Conditional

Conditional

Based on configuration on TDF

Table 2 describes the attributes that are present and contained in the Credit Control Request-Terminate (CCR-T) messages.

Table 2: AVPs in Credit Control Request-Terminate (CCR-T) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Sent by TDF.

Session-Id

Mandatory

Identifier of the session.

Sent by TDF.

Origin-realm

Mandatory

Configuration

Origin-Host

Mandatory

Configuration

Origin-State-id

Mandatory

This field contains the state associated to the TDF.

TDF generated Number; Incremented on every restart.

Destination-Host

Mandatory

  

Destination-Realm

Mandatory

  

CC-Request-Type

Mandatory

TERMINATION_REQUEST

Sent by TDF.

CC-Request-Number

Mandatory

 

Generated by the TDF and incremented for each CCR.

Subscription-Id

Mandatory

More than one AVPs of this type can be included to report more than one.

Subscription-Id i.e. IMSI and MSISDN.

 

Framed-IP-Address

Conditional

If the UE is allocated IPv4 Address.

 

Framed-IPv6-Prefix

Conditional

If the UE is allocated IPv6 Prefix

 

Termination-Cause

   

Called-Station-Id

Mandatory

APN

APN from Accounting-Start.

PDN-Connection-ID

Mandatory

  

Usage-Monitoring-Information

Conditional

Contains the usage monitoring threshold associated to a usage monitoring Key. One instance per usage monitoring key is required

Only present if PCRF provisions PCC rules with usage monitoring information (volume cap). The PCC rule will contain the Usage-monitoring-key within the PCC charging-rule definition

UM keys will be associated either to PCC rules but not both simultaneously.

Routing-Rule-Install

   

Routing-Rule-Remove

   

Table 3 Table describes the attributes that are present and contained in the Credit Control Request-Update (CCR-U) messages.

Table 3: AVPs in Credit Control Request-Update (CCR-U) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Sent by TDF.

Session-Id

Mandatory

Identifier of the session.

Sent by TDF.

Origin-realm

Mandatory

Configuration

Origin-Host

Mandatory

Configuration

Origin-State-id

Mandatory

This field contains the state associated to the TDF.

TDF generated Number; Incremented on every restart.

Destination-Host

Mandatory

  

CC-Request-Type

Mandatory

UPDATE_REQUEST.

Sent by TDF.

CC-Request-Number

Mandatory

Can Start with 0.

Generated by the TDF and incremented for each CCR.

Termination-Cause

   

Event-Report-Indication

 

Contains the data corresponding to the Event Triggers that the TDF subscribes (for example, event triggers from the PCEF or BBERF) Contains only the Event-Trigger AVP when sent from TDF to PCRF.

Optional. If present, it contains the data (for example, ULI, RAT type), which the TDF may include in report to OCS.

Charging-Rule-Report

   

ADC-Rule-Report

   

Application-Detection-Information

 

When a ADC rule is active, and the PCRF has a subscriber to the Application-Start and Application-Stop event-triggers; This AVP is included in case a user flow matches the criteria defined in the ADC rule.

 

TDF-Application-Identifier

 

Identifier of the AppID identified by TDF.

 

TDF-Application-Instance-Identifier

 

Progressive number of this AppID being identified by TDF (to correlate AppStart and AppStop).

 

Flow-Information

 

When the Event-Trigger indicates APPLICATION_Start, the Flow-Information AVP for the detected application (if deducible) is included. It contains Flow-Description and Flow-Direction AVPs

 

Event-Trigger

 

Indicates that the corresponding event has occurred at the gateway. Only the following values are supported:

  • OUT_OF_CREDIT (15)

  • REALLOCATION_OF_CREDIT (16)

  • REVALIDATION_TIMEOUT (17)

  • CHARGING_CORRELATION_EXCHANGE (28)

  • USAGE_REPORT (33)

  • NO_EVENT_TRIGGERS (14)

  • APPLICATION_Start (39)

  • APPLICATION_Stop (40)

 

Usage-Monitoring-Information

   

Table 1 describes the attributes that are present and contained in the Credit Control Answer-Initiate (CCA-I) messages.

Table 4: AVPs in Credit Control Answer-Initiate (CCR-I) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Session-Id

Mandatory

Identifier of the session.

Same as the value sent by TDF.

Origin-realm

Mandatory

Origin-Host

Mandatory

Origin-State-id

Mandatory

This field contains the state associated to the PCRF.

PCRF generated Number; Incremented on every restart.

Result-Code

Mandatory

Outcome of CCR.

Success/Failure.

Experimental-Result

Mandatory

Vendor assigned result of the operation.

Vendor assigned result.

CC-Request-Type

Mandatory

INITIAL_REQUEST.

The corresponding CCR-type.

CC-Request-Number

Mandatory

Same as received in CCR.

The corresponding CCR

Event-Trigger Charging-

Conditional

PCRF uses this AVP to subscribe to specific event triggers. Typical values are - NO_EVENT_TRIGGERS (14) APPLICATION_Start (39) APPLICATION_Stop (40) REVALIDATION_TIMEOUT (41) .

Triggers.

Rule-Install

Conditional

If new PCC rules need to be installed/activated or existing PCC rules need to be modified.

PCC Rules.

Qos-Information

Conditional

Indicates the authorized QoS for the session. This AVP may be used within PCC rule (to indicate MBR of a specific Application ID identified by a PCC rule). This AVP is never used at command level in TDF.

Online

Conditional

Default charging method for online. Provided by PCRF in CCA-I only if there is flows identified by PCC rule to be online charged.

Default charging method.

Charging-information

Optional

Contains the address of the primary and secondary charging server.

Provided by PCRF, if charging for application flows identified by PCC rules has to be performed. Same conditions as for ‘Online’. Not present if charging need not be performed by TDF.

Revalidation-Time

Conditional

Provided by PCRF and includes the Time at which TDF will have to reauthorize the PCC rules, Used for Time of Day controls on PCC rules.

Only if PCRF provisions PCC rules with ToD controls, this AVP will be present.

Usage-Monitoring-Information

Conditional

Contains the usage monitoring threshold associated to a usage monitoring key. One instance per usage monitoring key is required.

Only present if PCRF provisions PCC rules with usage monitoring information (volume cap). The PCC rule will contain the Usage-monitoring-key within the PCC charging-rule definition. For Release 14.1X55, UM keys will be associated either to PCC rules but not both simultaneously.

Event-Report-Indication

Optional

Contains the data corresponding to the Event Triggers that the TDF subscribes (for example, event triggers from the PCEF or Bearer Binding and Event Reporting Function [BBERF]).

Optional. If present, it contains the data (for example, ULI, RAT type), which the TDF may include in report to OCS.

Table 5 describes the attributes that are present and contained in the Credit Control Answer-Terminate (CCA-T) messages.

Table 5: AVPs in Credit Control Answer-Terminate (CCA-T) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Session-Id

Mandatory

Identifier of the session.

Same as the value sent by TDF.

Origin-realm

Mandatory

Origin-Host

Mandatory

Origin-State-id

Mandatory

This field contains the state associated to the PCRF.

PCRF generated Number; Incremented on every restart.

Result-Code

Mandatory

Outcome of CCR.

Success/Failure.

Experimental-Result

Mandatory

Vendor assigned result of the operation.

Vendor assigned result.

CC-Request-Type

Mandatory

TERMINATION_REQUEST.

The corresponding CCR-type.

CC-Request-Number

Mandatory

Same as received in CCR.

The corresponding CCR

Table 6 describes the attributes that are present and contained in the Credit Control Answer-Update (CCA-U) messages.

Table 6: AVPs in Credit Control Answer-Update (CCA-U) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Session-Id

Mandatory

Identifier of the session.

Same as the value sent by TDF.

Origin-realm

Mandatory

Origin-Host

Mandatory

Origin-State-id

Mandatory

This field contains the state associated to the PCRF.

PCRF generated Number; Incremented on every restart.

Result-Code

Mandatory

Outcome of CCR.

Success/Failure.

Experimental-Result

Mandatory

Vendor assigned result of the operation.

Vendor assigned result.

CC-Request-Type

Mandatory

UPDATE_REQUEST.

The corresponding CCR-type.

CC-Request-Number

Mandatory

Same as received in CCR.

The corresponding CCR

Event-Trigger

Conditional

If the PCRF wants to be reported of any event triggers at PCEF.

Triggers

Event-Report-Indication

Conditional

Contains the data corresponding to the Event Triggers that the TDF subscribes (for example, event triggers from the PCEF or BBERF)

Optional. If present, it contains the data (for example, ULI, RAT type), which the TDF may include in report to OCS.

Charging-Rule-Remove

Conditional

  

Charging-Rule-Install

Conditional

If new PCC rules need to be installed/activated or existing PCC rules need to be modified.

PCC rules

Online

Conditional

Default charging method

Default charging method

Charging-information

 

Contains the address of the primary and secondary charging server.

Provided by PCRF, if charging for application flows identified by PCC rules has to be performed. Same conditions as for ‘Online’.

Revalidation-Time

Conditional

Provided by PCRF and includes the Time at which TDF will have to reauthorize the PCC rules, Used for Time of Day controls on PCC rules.

Only if PCRF provisions PCC rules with ToD controls, this AVP will be present.

Usage-Monitoring-Information

Conditional

Contains the usage monitoring threshold associated to a usage monitoring key. One instance per usage monitoring key is required.

Only present if PCRF provisions PCC rules with usage monitoring information (volume cap). The PCC rule rule will contain the Usage-monitoring-key within the PCC charging-rule definition.

UM keys will be associated either to PCC rules rules but not both simultaneously.

Error-Message

Error-Reporting-Host

Table 7 describes the attributes that are present and contained in the Re-Authorization Request (RAR) messages.

Table 7: AVPs in Re-Authorization Request (RAR) Messages

AVP-Name

Presence

Condition

Derived From

Auth-Application-id

Mandatory

Gx (16777238).

Session-Id

Mandatory

Identifier of the session.

Same as the value sent by TDF.

Origin-realm

Mandatory

Origin-Host

Mandatory

Destination-Realm

Mandatory

Destination-Host

Mandatory

Origin-State-id

Mandatory

This field contains the state associated to the PCRF.

PCRF generated Number; Incremented on every restart.

Re-Auth-Request-Type

Mandatory

  

Session-Release-Cause

Conditional

  

Event-Trigger

Conditional

If the PCRF wants to be reported of any event triggers at PCEF.

Triggers

Event-Report-Indication

Conditional

Contains the data corresponding to the Event Triggers that the TDF subscribes (for example, event triggers from the PCEF or BBERF)

Optional. If present, it contains the data (for example, ULI, RAT type), which the TDF may include in report to OCS.

Service-Chaining-Information

Conditional

Charging-Rule-Remove

Conditional

  

Charging-Rule-Install

Conditional

If new PCC rules need to be installed/activated or existing PCC rules need to be modified.

PCC rules

Revalidation-Time

Conditional

Provided by PCRF and includes the Time at which TDF will have to reauthorize the PCC rules, Used for Time of Day controls on PCC rules.

Only if PCRF provisions PCC rules with ToD controls, this AVP will be present.

Usage-Monitoring-Information

Conditional

Contains the usage monitoring threshold associated to a usage monitoring key. One instance per usage monitoring key is required.

Only present if PCRF provisions PCC rules with usage monitoring information (volume cap). The PCC rule will contain the Usage-monitoring-key within the PCC charging-rule definition.

UM keys will be associated either to PCC rules but not both simultaneously.

Table 8 describes the attributes that are present and contained in the Re-Authorization Answer (RAA) messages.

Table 8: AVPs in Re-Authorization Answer (RAA) Messages

AVP-Name

Presence

Condition

Derived From

Session-Id

Mandatory

Identifier of the session.

Same as the value sent by TDF.

Origin-realm

Mandatory

Origin-Host

Mandatory

Origin-State-id

Mandatory

This field contains the state associated to the TDF.

TDF generated Number; Incremented on every restart.

Destination-Realm

Mandatory

Destination-Host

Mandatory

Result-Code

Mandatory

  

Experimental-Result

Mandatory

Vendor assigned result of the operation.

Vendor assigned result.

Charging-Rule-Report

Conditional

  

ADC-Rule-Report

Conditional