This chapter describes how to manage and configure the Oracle Communications Services Gatekeeper call detail record (CDR)-to-Diameter service for offline charging.
Oracle Communications Services Gatekeeper forwards CDR charging events to a Diameter Rf server for offline charging. Services Gatekeeper offline charging uses the Charging management; Diameter charging; 3GPP TS 32.299 V8.4.0 (2008-09) (Release 8), Diameter Credit-Control Application; RFC 4006 here:
http://www.ietf.org/rfc/rfc4006.txt
You can also use the Parlay X 3.0 Payment/Diameter communication service to establish direct billing. For details see "Parlay X 3.0 Payment/Diameter" in Services Gatekeeper Communication Service Reference Guide.
The CdrToDiameter service forwards charging events to a Diameter server using the Diameter Rf interface. This allows for easy integration with charging systems that support Diameter Rf offline charging. When enabling this service, Oracle Communications Elastic Charging Engine or the Oracle Communications Billing and Revenue Management products, with Oracle Communications Network Mediation, can be used out-of-the-box with Services Gatekeeper.
Any traffic request processed through Services Gatekeeper that generates a CDR also generates a corresponding Diameter Rf request. The Diameter server can the be used for any billing, charging, and reporting for these requests. See "CDR to AVP mapping" for information about how CDRs are mapped to Diameter attribute-value pairs (AVPs).
The CdrToDiameter service is not deployed by default. It is deployed as a regular JEE module using WebLogic Server deployment tools. For information on how to deploy the service, see "Java EE 6 Deployment Implementation" in Oracle Fusion Middleware Understanding Oracle WebLogic Server.
The service is packaged in cdr_to_diameter-single.ear and cdr_to_diameter.ear in Gatekeeper_home/applications.
Use cdr_to_diameter.ear in clustered installations, and cdr_to_diameter-single.ear in single server domains.
The service is a cluster singleton, so it will execute only on one server at any given time. In case of server failure, this service is transferred to another server. The management part is distributed to all servers in the cluster, so it can be managed from any server in the cluster.
To configure the behavior of the CdrToDiameter service, in the managed object CdrToDiameter:
Specify these fields:
OriginHost
OriginPort
DestinationHost
DestinationPort
DestinationRealm
PeerRetryDelay
RequestTimeout
WatchdogTimeout
Use the connect method to connect to the Diameter server.
The CdrToDiameter service can be explicitly connected to the Diameter server. It does not connect to the server by default. The service has a connection status that will be preserved after service redeployment and server restart.
Use these methods in CDRDiameterMBean:
connect
disconnect
Use Enabled (r) to check the current connection status.
Use connect after any changes to the configuration attributes. Changes does not take affect until this operation is invoked.
The CDRs that are generated are mapped to Diameter attribute-value pairs, AVPs, as shown in Table 24-1. Both standard and custom AVPs are used. When custom are used it is indicated in the table.
Table 24-1 CDR to Diameter AVP Mappings
| AVP | Source | Description |
|---|---|---|
|
Session-Id |
Auto generated. |
Operation session identifier. Specification: RFC 3588 Example: nt1.ocsg.oracle.com;1214342798;0 |
|
Origin-Host |
Configurable, using the OriginHost field to CDRDiameterMBean |
Realm of the Services Gatekeeper domain. Addressed with the domain address of the corresponding public URI. Specification: RFC 3588 Example: nt1.ocsg.oracle.com |
|
Origin-Realm |
Auto generated. |
Ream of the Services Gatekeeper domain. Addressed with the domain address of the corresponding public URI. Specification: RFC 3588 Example: oracle.com |
|
Destination-Realm |
Configurable using the DestinationRealm field in CDRDiameterMBean |
Realm of the operator domain. Addressed with the domain address of the corresponding public URI. Specification: RFC 3588 Example: oracle.com |
|
Accounting-Record-Type |
Value of CDR name-value pair: CallInfo |
Defines the transfer type. Value is EVENT_RECORD for event based charging. Value is START_RECORD, INTERIM_RECORD, or STOP_RECORD for session based charging. If value of CallInfo is START, transfer type is EVENT_RECORD or START_RECORD. If value of CallInfo is STOP, transfer type is STOP_RECORD. EVENT_RECORD has numeric value 1. START_RECORD has numeric value 2. INTERIM_RECORD has numeric value 3. STOP_RECORD has numeric value 4. Specification: RFC 3588 Example: 1 |
|
Accounting-Record-Number |
Auto generated. |
Sequence number of the Diameter message sent from the CdrToDiameter service. Specification: RFC 3588 Example: 42 |
|
Acct-Application-Id |
Static. Value is always 3. |
Value is always 3, which corresponds to the application ID of the Diameter Accounting Application (off-line charging). Specification: RFC 3588 |
|
User-Name |
Value of CDR name-value pair: ServiceProviderId |
The service provider ID associated with the request that triggered the CDR. Specification: RFC 3588 Example: service_provider_1 |
|
Event-Timestamp |
CDR attribute in name-value pair: Timestamp |
Time the event happened. Given in seconds since the year 1900. Specification: RFC 3588 |
|
Calling-Party-Address |
Value of CDR name-value pair: destinationParty |
Custom AVP. Depending on which communication service that triggered the CDR, different application-provided parameters are used. Specification: 3GPP 32.299 Example: tel:7878 |
|
Called-Party-Address |
Value of CDR name-value pair: originatingParty |
Custom AVP. Depending on which communication service that triggered the CDR, different application-provided parameters are used. Specification: 3GPP 32.299 Example: tel:7878 |
|
Service-Indication |
Value of CDR name-value pair: ServiceName |
Custom AVP. The name of the service the request triggered. Specification: 3GPP 29.329 Example: MultimediaMessaging |
|
Message-Size |
Calculated from message payload. Relevant for Parlay X 2.1 Short Messaging and Multimedia Messaging. |
Custom AVP. For MM, it holds the total size in bytes of the MM calculated according to TS 23.140 For SM, it holds the total size in octets of the SM including any user data header. Specification: 3GPP 32.299 Example: 345 |
|
OCSG-Charge-Description |
Parameter ChargingDescription in any Parlay X operation that includes this parameter. |
Custom AVP. Application-provided description text to be used for information and billing text. Specification: none Example: Delivery of weather report. |
|
Currency-Code |
Parameter ChargingCurrency in any Parlay X operation that includes this parameter. |
Custom AVP. Currency code mapped according to ISO 4217. Specification: RFC 4006 Example: If the currency is U.S dollars, the value is 840 |
|
Unit-Value.Exponent |
Parameter ChargingAmount in any Parlay X operation that includes this parameter. |
Custom AVP. The exponent value to be applied for the Value-Digit AVP within the Unit-Value AVP. Specification: RFC 4006 Example: -2 |
|
Unit-Value.Value-Digits |
Parameter ChargingAmount in any Parlay X operation that includes this parameter. |
Custom AVP. The value to be applied for the Value-Digit AVP within the Unit-Value AVP. Contains the significant digits of the number scaled to an integer. Specification: RFC 4006 Example: 4062 |
|
Service-Context-Id |
Parameter ChargingCode in any Parlay X operation that includes this parameter. |
Custom AVP. Code that references a contract under which the charge is applied. Specification: RFC 4006 Example: premium |