Technical Data
| Software Component Version |
Convergent Charging 3.0
|
| Namespace |
http://provisioning.ws.highdeal.com/ |
| Application Area |
IS-CC |
Business Context and Use
A charging contract is a long-term agreement between a service provider and a customer based on specific terms that have been negotiated
beforehand which defines how and how much the customer shall be charged:
- To have access to goods or services
- To consume these goods or services
In order to access to goods or services, the customer shall be charged:
- Once during time : these are one-off prices
- Recurrently: these are recurring prices
In order to consume goods or services, the customer shall be charged:
- Once per consumption
- Recurrently, for all consumption made in a given time period
The charging contract also defines what modifications in the customer basic charging definition are applied when accessing and consuming
goods or services. The modification in the customer basic charging definition can be:
- Price redefinition
- Price discount or surcharge
- Charging redefinition
- Condition redefinition for price computation and charging
The modifications may depend on the customer context and the way the customer consumes the goods and services. The modifications can
impact:
-
The customer charging definition only:
- The price to access and/or consume more goods and/or services is reduced
- The price to access and/or consume more goods and/or services is increased
- For the same price, more goods and/or services can be consumed
- For the same price, less goods and/or services can be consumed
-
The customer economic environment, such as :
- An extra charge, which is a remuneration, i.e. the payment of commission to another entity of the economic environment, such
as another
customer
- A split charge, which is a sponsorship, i.e. the splitting of the payment between the customer and another entity of the
economic
environment, such as another customer.
A charging contract also defines how a customer shall technically access to good and services thanks to the definition of user service identifiers, and which accounts shall be charged for this consumption, thanks to account assignments. These accounts are the one defined in the related subscriber account.
Related Operations
You can use the following operations to perform actions on existing subscriber account.
Features
A charging contract is defined by:
- Its identifier of the charging contract, unique in Convergent Charging (mandatory)
- Its related subscriber account identifier (mandatory)
- Some additional information (optional)
- Some items that are activations of a defined charge plan or refill plan
A charging contract contains at most one item that activates a refill plan and at least one item that activates a charge plan. A charging contract item is defined by:
- A charge plan class or a refill plan class identifier (mandatory)
- An identifier which is unique within the charging contract (mandatory)
- An external identifier which is not unique within the charging contract (optional)
- A set of validity periods, defined by:
- A start date: the validity start date of the considered period
- An end date: the validity end date of the considered period
- A set of parameters: each parameter defined in charge plan class or refill plan class can be redefined in charging contract item.
- A set of shared counter: each counter defined in charge plan class or refill plan class can be shared. The sharing can be influenced by the definition of the namespace. Name and namespace identifiers of a shared counter define a unique counter of the charging contract.
- A set of account: each account assignment defined in charge plan class or refill plan class must be assigned by one account defined in subscriber account.
- A set of user service identifiers: each user technical identifier defined in charge plan class or refill plan class can be assigned by one or several user service identifier. A user service identifier is a technical key that uniquely pinpoints the user inside the customer service. For example an e-mail address, a phone number, the IMSI or the MSISDN.
The validity periods are not necessary subsequent.
Prerequisites
There is no prerequisite.
Integration
There is no specific integration information.
Constraints and Integrity Conditions
There is no specific constraint.
|
SAP DOCUMENTATION