Charging Session

Business Object (WS)

Definition

A charging session (such as phone calls or video streaming) is considered as a succession of simple events which are split into quotas of customer service to be charged and occurring during a limited period.

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	Data Types
Version	0
Application Area	IS-CC

Business Context and Use

Related Operations

You can use the following operations to perform actions on charging sessions.

• Find charging sessions Cancel charging sessions

Related Process Components

• Business Processing: Charging Session Management

Features

Life Cycle

A charging session can be created and modified during the execution of the charging process (start, update, and stop operations) :

When the charging session has expired, or when the multiservice session is stopped, the charging session will be removed from the system using the cleanup mechanism. The cleanup mechanism applies the default resolution of the charging session.

Structure

A charging session contains the following informations:

• A unique external session identifier
• The reservation identifier, which is unique for the multiservice charging session
• The identifier of the subscriber account
• The identifier of the charging contract
• An SAP CC access, which is made up of a customer service identifier (SID) and a user service identifier (USID) related to the end customer (in case of multiservice, this identifier is the same for all the services)
• A consumption date, which is combined with the above access to retrieve the adequate subscription or provider contract item
• An expiration date, which represents the date by which the session will expired
• The time to live, which is the duration in milliseconds of the session
• The property name, which represents the balance to inverse for calculating the maximum usage quota to reserve
• A currency, which represents the amount accumulated during a session
• The default resolution of the session (confirmed or cancelled)
• The reservation item, whixh is used to start the reservation of the session
• The list of impacts for persistent counters, which are provisioned by the current contract
• The list of impacts for persistent counters, which are provisioned by the parent contract if the current contract is a linked contract
• The list of impacts for persistent counters, which are provisioned inside prepaid balances in the current subscriber account.
• The list of impacts for persistent counters, which are provisioned by allowances defined within the current contract.
• The list of impacts for persistent counters, which are provisioned by allowances defined by the parent of the current (linked) contract.
• The list of impacts for distributed counters, which are provisioned by shared allowances debited within the session.
• The list of the transient counters, which have been created by the current contract at reservation time.
• The list of the transient counters, which have been created by allowances visited at reservation time
• A list of all the charged items, which are generated during the session

Integration

There is no specific integration information.

Constraints and Integrity Conditions

There is no specific constraint.

Notes on SAP CC Implementation

You must have installed and configured the SAP CC Core Server system.

Configuration

Consult the SAP CC Configuration and Implementation Guide to know the necessary configuration or Customizing of the SAP CC system.

Before implementing SAP Convergent Charging in your SAP system landscape, you must configure the systems and the data (master data, business data).