Charging Data

The following sections provide a reference to WebLogic Network Gatekeeper charging data:

Charging data format

The CDR data is stored in the MySQL database in the following format:

Field	Format
transaction_id	bigint
session_id	bigint
service_name	varchar
user_id	varchar
start_of_usage	bigint
connect_time	bigint
end_of_usage	bigint
duration_of_usage	bigint
amount_of_usage	bigint
originating_party	varchar
destination_party	varchar
transaction_part_number	int
completion_status	int
additional_info	blob
revenue_share_percentage	float
charging_info	varchar
party_to_charge	varchar
service_provider	varchar
slee_instance	varchar

All services that produce charging data do not use all fields. See the section below on details of which fields that are relevant for the different services.

All times given, except duration of usage, are relative to the UNIX era, that is number of milliseconds since midnight, January 1, 1970, Greenwich Mean Time, GMT.

Duration of usage is given in seconds.

Charging

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (Charging) that has created the CDR.
user_id	The application that used the service capability module.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed
additional_info (in XML format)	Possible data: <merchant_id> </merchant_id> The merchant ID, for instance the ID of the organisation or company that provided the content. <account_id> </account_id> The account the charging operation is performed on. <user_id> </user_id> The ID of the user that used the service. <method_name> </method_name> Provides the type of charging performed.
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

Call

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (Call control) that has created the CDR.
user_id	The application that used the service capability module.
start_of_usage	The date and time the service capability module started to use services in the telecom network.
connect_time	The date and time the destination party responded.
end_of_usage	The date and time the service capability module stopped to use services in the telecom network.
duration_of_usage	The total time the service capability module used the network services. Value is 0 (zero) if no answer or route fail.
originating_party	The address of the originating party.
destination_party	The address of the destination party.
transaction_part_ number	Always equal to 1.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

Messaging

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (Messaging) that has created the CDR.
user_id	The application that used the service capability module.
start_of_usage	The date and time the service capability module started to use services in the telecom network.
amount_of_usage	Always equal to 1.
originating_party	The address of the originating party.
destination_party	The address of the destination party.
transaction_part_ number	Always equal to 1.
completion_status	Indicates the completion status of the transaction. Outgoing message: 0 - failed 1 - completed 2 - partial (indicates that SEND_RESULT=OK, another CDR with status completed or failed will be created after DEVLIVERY_ACK has been recieved) Incomig message: 0 - failed 1 - completed 2 - partial (indicates that the message has been successfully stored in the database, but there is no listener registered) 3 - completed but notfication failed (indicates that the message has been successfully stored in the database, but the notification towards the application failed)
additional_info (in XML format)	Possible data: <method> </method> The type of operation performed [ DELIVERY_ACK \| SEND_RESULT \| MESS_ARRIVED ] Possible data if method=DELIVERY_ACK: <sendListSize> </sendListSize> - no. of addresses in send list. <byteSize> </byteSize> - size of message in bytes. <mbox></mbox> - mailbox address <msg_type></msg_type> SMS or MMS Possible data if method=SEND_RESULT: <sendListSize> </sendListSize> - no. of addresses in send list. Possible data if method=MESS_ARRIVED: <byteSize> </byteSize> - size of message in bytes. <msg_type></msg_type> SMS or MMS
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

Subscriber profile

Field Name	Description
transaction_id	A unique ID for the transaction.
service_name	The service capability module (Subscriber profile) that has created the CDR.
user_id	The application that used the service capability module.
start_of_usage	The date and time the service capability module started to use services in the telecom network.
amount_of_usage	The used amount. Used when charging is not time dependent. For example, flat rate services.
destination_party	The address of the destination party. That is, the subscriber the profile belongs to.
transaction_part_ number	Always equal to 1.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed 3 - completed but callback to application failed
additional_info (in XML format)	Possible data: <op> </op> Provides the type of subscriber profile operation performed [get \| set]
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

User interaction

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (User interaction) that has created the CDR.
user_id	The application that used the service capability module.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed 3 - completed but callback to application failed
additional_info (in XML format)	Possible data: <method name> </method name> The type of operation performed [ abortActionErr \| abortActionRes \| deleteMessageErr \| deleteMessageRes \| recordMessageErr \| recordMessageRes \| sendInfoAndCollectErr \| sendInfoAndCollectRes \| sendInfoErr \| sendInfoRes \| userInteractionFaultDetected ] <assignmentID> </assignmentID> Provides the assignment ID. <infoID> </infoID> Provides the announcement's infoID. Used for call based UI only. <serviceCode> </serviceCode> Provides the service code used to identify the application. Used for network initiated UI requests (UI notification) or sendInfoAndCollect responses. <resourceType> </resourceType> Provides the plug-in type [ SMS \| USSD \| GUI ].
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

User location

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (User location) that has created the CDR.
user_id	The application that used the service capability module.
start_of_usage	The date and time the service capability module started to use services in the telecom network.
amount_of_usage	Always equal to 1.
destination_party	The address of the destination party.
transaction_part_ number	Always equal to 1.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed 3 - completed but callback to application failed
additional_info (in XML format)	Possible data: <location_type> </location_type> The type of operation performed [ standard \| extended \| periodic ] <cause> </cause> Provides an indication on the possible cause in case of an unsuccesful status request.
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.

User status

Field Name	Description
transaction_id	A unique ID for the transaction.
session_id	An ID used to connect related transactions.
service_name	The service capability module (User status) that has created the CDR.
user_id	The application that used the service capability module.
start_of_usage	The date and time the service capability module started to use resources in the telecom network.
amount_of_usage	The used amount. Used when charging is not time dependent. For example, flat rate services.
destination_party	The address of the destination party.
transaction_part_ number	Always equal to 1.
completion_status	Indicates the completion status of the transaction. 0 - failed 1 - completed 3 - completed but callback to application failed
additional_info (in XML format)	Possible data: <cause> </cause> Provides an indication on the possible cause in case of an unsuccesful status request.
charging_info	Service code added by the application or by the policy service. Can also be used to provide the actual price.
party_to_charge	The ID of the party that initiated the request that resulted in the transaction.
service_provider	The ID of the service provider that hosts the application.
slee_instance	The SLEE instance hosting the service capability module that generated the CDR.