Detecting Online Charging

The OC-Charging-Result AVP in a CDR indicates whether online (Diameter Ro) charging was used for a session. This may be used to determine if further action is needed when processing CDRs offline.

  • An OC-Charging-Result value of -1 means that online charging was not used for the session.

  • Otherwise the value is set to the Diameter Result-Code AVP value.

Populated AVPs in the Multiple-Services-Credit-Control AVP

The Multiple-Services-Credit-Control AVP is of type grouped, and is defined in RFC 4006. Section 7.1.4 of 3GPP TS 32.299 defines it with additional 3GPP specific parameters and states some IETF parameters are not used in the 3GPP.

AVP Name Specification reference Included in CDR Included in CCR Comments

Requested-Service-Unit

IETF RFC 4006

No

Yes

Used in the CCR. The CDR represents this information in the OC-Session-Counter AVP

Used-Service-Unit

IETF RFC 4006 and 3GPP TS 32.299

No

Yes

Used in the CCR according to Populated AVPs in the Used-Service-Unit AVP. The CDR represents this information in the OC-Session-Counter AVP

Service-Identifier

IETF RFC 4006

No

No

Sentinel uses the Rating-Group AVP in preference to the Service-Identifier

Rating-Group

IETF RFC 4006 and 3GPP TS 32.299 v8.13.0 section 7.1.5

No

Yes

This AVP is set according to Session Counters and the ratingGroup session state field.

Reporting-Reason

3GPP TS 32.299 v8.13.0 section 7.2.136

No

Yes

Trigger

3GPP TS 32.299 v8.13.0 section 7.2.175

No

No

PS-Furnish-Charging-Information

3GPP TS 32.299 v8.13.0 section 7.2.123

No

No

Refund-Information

3GPP TS 32.299 v8.13.0 section 7.2.132

No

No

AF-Correlation-Information

3GPP TS 32.299 v8.13.0 section 7.2.11

No

No

Envelope

3GPP TS 32.299 v8.13.0 section 7.2.41

No

No

Envelope-Reporting

3GPP TS 32.299 v8.13.0 section 7.2.43

No

No

Time-Quota-Mechanism

3GPP TS 32.299 v8.13.0 section 7.2.170

No

No

Service-Specific-Info

3GPP TS 32.299 v8.13.0 section 7.2.151

No

No

QoS-Information

3GPP TS 29.212

No

No

The BNF grammer for this AVP in 32.299 v8.13.0 is as follows:

<Multiple-Services-Credit-Control> ::=	   < AVP Header: 456 >

    [ Granted-Service-Unit ]   // not used in CCR
    [ Requested-Service-Unit ]
  * [ Used-Service-Unit ]
    [ Tariff-Change-Usage ]    // not used in 3GPP
  * [ Service-Identifier ]
    [ Rating-Group ]
  * [ G-S-U-Pool-Reference ]   // not used in CCR
    [ Validity-Time ]          // not used in CCR
    [ Result-Code ]            // not used in CCR
    [ Final-Unit-Indication ]  // not used in CCR
    [ Time-Quota-Threshold ]   // not used in CCR
    [ Volume-Quota-Threshold ] // not used in CCR
    [ Unit-Quota-Threshold ]   // not used in CCR
    [ Quota-Holding-Time ]     // not used in CCR
    [ Quota-Consumption-Time ] // not used in CCR
  * [ Reporting-Reason ]
    [ Trigger ]
    [ PS-Furnish-Charging-Information ]
    [ Refund-Information ]
  * [ AF-Correlation-Information]
  * [ Envelope ]
    [ Envelope-Reporting ]
    [ Time-Quota-Mechanism ]
  * [ Service-Specific-Info ]
    [ QoS-Information ]
  * [ AVP ]                    // not used in 3GPP

Populated AVPs in the Used-Service-Unit AVP

The Used-Service-Unit AVP is defined in IETF RFC 4006, and then its BNF is modified slightly in 3GPP TS 32.299 section 7.1.9.

AVP Name Specification reference Included in CDR Included in CCR Comments

Reporting-Reason

3GPP TS 32.299 v8.13.0 section 7.2.136

No

No

Tariff-Change-Usage

IETF RFC 4006

No

No

CC-Time

IETF RFC 4006

No

Yes

Used by default as the unit type for SIP Sessions

CC-Money

IETF RFC 4006

No

Not typically

Not used out-of-the-box for Sentinel SIP

CC-Total-Octets

IETF RFC 4006

No

Not typically

Not used out-of-the-box for Sentinel SIP

CC-Input-Octets

IETF RFC 4006

No

Not typically

Not used out-of-the-box for Sentinel SIP

CC-Output-Octets

IETF RFC 4006

No

Not typically

Not used out-of-the-box for Sentinel SIP

The 3GPP definition (in v8.13.0) is

<Used-Service-Unit> ::=	   < AVP Header: 446 >
    [ Reporting-Reason ]
    [ Tariff-Change-Usage ]
    [ CC-Time ]
    [ CC-Money ]    // not used in 3GPP
    [ CC-Total-Octets ]
    [ CC-Input-Octets ]
    [ CC-Output-Octets ]
    [ CC-Service-Specific-Units ]
   *[ Event-Charging-TimeStamp ]
   *[ AVP ]        // not used in 3GPP

Populated AVPs in the Service-Information AVP

The Service-Information AVP is defined in 3GPP TS 32.299 v8.13.0. It is a grouped AVP. This table lists the AVPs grouped within Service-Information and how the product populates them.

AVP Name Specification reference Included in CDR Included in CCR Comments

SMS-Information

32.299 v8.13.0 section 7.2.162

Yes

Yes

Refer to Populated AVPs in the SMS-Information AVP

MMTel-Information

32.299 v8.13.0 section 7.2.88A

Yes

Yes

The Sentinel VoLTE product populates this AVP

Subscription-Id

IETF RFC 4006

Yes

No

3GPP TS 32.299 v8.13.0 states that it should be set on the Rf interface, not the Ro interface (see section 7.2.149)

AoC-Information

32.299 v8.13.0 section 7.2.12B

No

No

Sentinel does not implement the advice of charge service out-of-the-box

PS-Information

32.299 v8.13.0 section 7.2.124

No

No

PS-Information AVP contains EPC layer information and as such is not populated by a SIP-AS.

WLAN-Information

32.299 v8.13.0 section 7.2.185

No

No

WLAN-Information AVP contains information not accessible to a SIP-AS

IMS-Information

32.299 v8.13.0 section 7.2.58

Yes

Yes

See the IMS-Information table for further details

MMS-Information

32.299 v8.13.0 section 7.2.88

No

No

Sentinel does not implement any MMS node roles out-of-the-box

LCS-Information

32.299 v8.13.0 section 7.2.69

No

No

PoC-Information

32.299 v8.13.0 section 7.2.111

No

No

Sentinel does not implement the PoC service out-of-the-box

MBMS-Information

32.299 v8.13.0 section 7.2.77

No

No

Sentinel does not implement the MBMS service out-of-the-box

Service-Generic-Information

OMA-DDS-Charging_Data

No

No

IM-Information

OMA-DDS-Charging_Data

No

No

Sentinel does not implement IM services out-of-the-box

DCD-Information

OMA-DDS-Charging_Data

No

No

The BNF for the AVP is defined in section 7.2.149. It is as follows:

Service-Information :: = 	< AVP Header: 873>

  * [ Subscription-Id ]
    [ AoC-Information ]
    [ PS-Information ]
    [ WLAN-Information ]
    [ IMS-Information ]
    [ MMS-Information ]
    [ LCS-Information ]
    [ PoC-Information ]
    [ MBMS-Information ]
    [ SMS-Information ]
    [ MMTel-Information ]
    [ Service-Generic-Information ]
    [ IM-Information ]
    [ DCD-Information ]

Populated AVPs in the SMS-Information AVP

The SMS-Information AVP is a grouped AVP. It is defined in 32.299 v8.13.0 section 7.2.162.

AVP Name Specification reference Included in CDR Included in CCR Comments

SMS-Node

32.299 v8.13.0 section 7.2.163

No

Yes

IP_SM_GW(1)

Client-Address

32.299 v8.13.0 section 7.2.28

No

Yes

Configured IPSMGW GT address

Data-Coding-Scheme

32.299 v8.13.0 section 7.2.34

No

Yes

The dataCodingSheme portion of the MT_ForwardSM’s SMS-DELIVER TPDU

SM-User-Data-Header

32.299 v8.13.0 section 7.2.161

No

Yes

The userDataHeader portion of the MT_ForwardSM’s SMS-DELIVER TPDU

SM-Status

32.299 v8.13.0 section 7.2.160

No

Yes

The single octet TP-Status field of the MT_ForwardSM’s SMS-STATUS-REPORT TPDU

SM-Discharge-Time

32.299 v8.13.0 section 7.2.157

No

Yes

The TP-Discharge-Time field of the MT_ForwardSM’s SMS-STATUS-REPORT TPDU

Originator-Interface

32.299 v8.13.0 section 7.2.97

No

Yes

Refer to Populated AVPs in the Originator-Interface AVP

It has the following ABNF grammar:

SMS-Information :: =   < AVP Header: 2000>
    [ SMS-Node ]
    [ Client-Address ]
    [ Originator-SCCP-Address ]
    [ SMSC-Address]
    [ Data-Coding-Scheme ]
    [ SM-Discharge-Time ]
    [ SM-Message-Type ]
    [ Originator-Interface ]
    [ SM-Protocol-ID ]
    [ Reply-Path-Requested ]
    [ SM-Status ]
    [ SM-User-Data-Header ]
    [ Number-Of-Messages-Sent ]
  * [ Recipient-Info ]
    [ Originator-Received-Address ]
    [ SM-Service-Type ]

Populated AVPs in the Originator-Interface AVP

The Originator-Interface AVP is a grouped AVP. It is defined in 3GPP TS 32.299 v8.13.0 section 7.2.97.

AVP Name Specification reference Included in CDR Included in CCR Comments

Interface-Id

32.299 v8.13.0 section 7.2.52

Yes

Yes

"SCCP Address=<SMSC SCCP Address>"

Interface-Port

32.299 v8.13.0 section 7.2.53

No

Yes

"SSN=<SMSC SCCP Address SSN>"

Interface-Text

32.299 v8.13.0 section 7.2.54

No

Yes

"IP-SM-GW/GSM MAP"

Interface-Type

32.299 v8.13.0 section 7.2.55

No

Yes

MOBILE_TERMINATING(2)`

It has the following ABNF grammar:

Originator-Interface: =   < AVP Header: 2009>
    [ Interface-Id ]
    [ Interface-Text ]
    [ Interface-Port ]
    [ Interface-Type ]

Populated AVPs in the IMS-Information AVP

The IMS-Information AVP is defined in 3GPP TS 32.299 v8.13.0. It is a grouped AVP. This table lists the AVPs grouped within IMS-Information and how the product populates them.

AVP Name Specification reference Included in CDR Included in CCR Comments

Event-Type

32.299 v8.13.0 section 7.2.47

Yes

Yes

Role-Of-Node

32.299 v8.13.0 section 7.2.138

Yes

Yes

Sessions with sescase of orig and orig_cdiv are in ORIGINATING_ROLE

Node-Functionality

32.299 v8.13.0 section 7.2.89

Yes

Yes

Set to value 6 as AS

User-Session-Id

32.299 v8.13.0 section 7.2.181

Yes

Yes

Set to the Call-Id for the initial request

Session-Priority

29.229

Yes

Yes

Set to value 2

Calling-Party-Address

32.299 v8.13.0 section 7.2.23

Yes

Yes

Called-Party-Address

32.299 v8.13.0 section 7.2.22

Yes

Yes

Called-Asserted-Identity

32.299 v8.13.0 section 7.2.21

Yes

Yes

Number-Portability-Routing-Information

32.299 v8.13.0 section 7.2.92A

No

No

Carrier-Select-Routing-Information

32.299 v8.13.0 section 7.2.23A

No

No

Alternate-Charged-Party-Address

32.299 v8.13.0 section 7.2.12

No

No

Requested-Party-Address

32.299 v8.13.0 section 7.2.137

Yes

Yes

This field is only included if different from the Called-Party-Address

Associated-URI

32.299 v8.13.0 section 7.2.16

No

No

Application-Server-Information

32.299 v8.13.0 section 7.2.15

No

No

Inter-Operator-Identifier

32.299 v8.13.0 section 7.2.60

Yes

Yes

IMS-Charging-Identifier

32.299 v8.13.0 section 7.2.56

Yes

Yes

SDP-Session-Description

32.299 v8.13.0 section 7.2.144

Yes

Yes

SDP-Media-Component

32.299 v8.13.0 section 7.2.140

Yes

Yes

Served-Party-IP-Address

32.299 v8.13.0 section 7.2.146

No

No

Server-Capabilities

29.229

No

No

Trunk-Group-ID

32.299 v8.13.0 section 7.2.177

No

No

Bearer-Service

32.299 v8.13.0 section 7.2.20

No

No

Service-Id

32.299 v8.13.0 section 7.2.147

No

No

Service-Specific-Info

32.299 v8.13.0 section 7.2.151

No

No

Message-Body

32.299 v8.13.0 section 7.2.81

No

No

Cause-Code

32.299 v8.13.0 section 7.2.24

Yes

Yes

Access-Network-Information

32.299 v8.13.0 section 7.2.2

Yes

Yes

The first value in the SIP P-Access-Network-Info header is included as the value for this AVP

Early-Media-Description

32.299 v8.13.0 section 7.2.40

Yes

Yes

The most recent Early Media offer/answer is included

IMS-Communication-Service-Identifier

32.299 v8.13.0 section 7.2.57

Yes

Yes

The BNF syntax for the IMS-Information AVP according to 3GPP TS 32.299 v8.13.0 is as follows

IMS-Information :: = 	  < AVP Header: 876>
    [ Event-Type ]
    [ Role-Of-Node ]
    { Node-Functionality }
    [ User-Session-ID ]
    [ Session-Priority ]
  * [ Calling-Party-Address ]
    [ Called-Party-Address ]
  * [ Called-Asserted-Identity ]
    [ Number-Portability-Routing-Information ]
    [ Carrier-Select-Routing-Information ]
    [ Alternate-Charged-Party-Address ]
    [ Requested-Party-Address ]
  * [ Associated-URI ]
    [ Time-Stamps ]
  * [ Application-Server-Information ]
  * [ Inter-Operator-Identifier ]
    [ IMS-Charging-Identifier ]
  * [ SDP-Session-Description ]
  * [ SDP-Media-Component ]
    [ Served-Party-IP-Address ]
    [ Server-Capabilities ]
    [ Trunk-Group-ID ]
    [ Bearer-Service ]
    [ Service-Id ]
  * [ Service-Specific-Info ]
  * [ Message-Body ]
    [ Cause-Code ]
    [ Access-Network-Information ]
  * [ Early-Media-Description]
    [ IMS-Communication-Service-Identifier ]

Additional populated AVPs

This table lists additional standard AVPs that appear at the top level of a CDR or CCR instead of their standard place in a grouped AVP.

AVP Name Specification reference Included in CDR Included in CCR Comments

PDP-Address

32.299 v8.13.0 section 7.2.105

No

Yes

Destination IPCAN address of SIP message

Populated OpenCloud AVPs

The population of OpenCloud AVPs is described here. The definition of OpenCloud AVPs is provided in Sentinel AVP definitions.

AVP Name Specification reference Included in CDR Included in CCR Comments

OC-Sentinel-Selection-Key

OC-Sentinel-Selection-Key

Yes

No

n/a

OC-Sentinel-Selection-Key

OC-Sentinel-Selection-Key AVP

Yes

No

n/a

OC-Play-Announcement-Id

OC-Play-Announcement-Id

Yes

No

n/a

OC-Call-Type

OC-Call-Type

Yes

No

Role-Of-Node AVP has similar meaning on the Ro interface

OC-Service-Type

OC-Service-Type

Yes

No

n/a

OC-Charging-Result

OC-Charging-Result

Yes

No

OC-OCS-Session-Id

OC-OCS-Session-Id

Yes

No

This is the session ID in Ro

OC-OCS-Session-Termination-Cause

OC-OCS-Session-Termination-Cause

Yes

No

OC-Sentinel-Error

OC-Sentinel-Error

Yes

No

OC-Charging-Instance

OC-Charging-Instance

Yes

No

OC-Event-Id

OC-Event-Id

Yes

No

OC-Call-Id

OC-Call-Id

Yes

No

The Ro Session Id optional part includes the SIP Call ID

OC-End-Session-Cause

OC-End-Session-Cause

Yes

No

OC-SM-Message-Type

OC-SM-Message-Type

Yes

Yes

n/a

OC-Plan-Id

OC-Plan-Id

Yes

No

n/a

OC-Submit-Report-Type

OC-Submit-Report-Type

Yes

No

n/a

OC-Correlated-Id

OC-Correlated-Id

Yes

No

n/a

OC-MT-PS-Delivery-Result

OC-MT-PS-Delivery-Result

Yes

No

n/a

OC-MT-CS-Delivery-Result

OC-MT-CS-Delivery-Result

Yes

No

n/a

OC-IMPU

OC-IMPU

Yes

No

n/a
Previous page Next page
Sentinel IP-SM-GW Version 2.5.1