Service domain charging systems and methods
Various mechanisms are disclosed for a service domain charging system that can interact with underlying networks. A service domain charging architecture is defined with several logical functions. Service-based charging types may be and applied to existing event, session, online, and offline charging mechanisms. Service domain charging messages may be exchanged over the X, Y, Z reference points. An E reference point may be used for interfacing with a service domain billing system, and a B reference point may be used between a service domain billing system and underlying network's billing system.
1. In a service layer of a communication network, a method comprising:
configuring a charging policy at the service layer, the charging policy being defined as a rule with associated attributes that instructs the service layer how to create a charging data record (CDR) for a service that the service layer performs on behalf of a requestor, where the service includes a sequence of multiple operations performed by the service layer based on plural inputs received from the requestor,
the attributes including a rule status attribute indicating if the rule is active, and a chargeable event identifier,
the charging policy being stored in a resource configurable using Create, Retrieve, Update, Delete (CRUD) operations;
using the charging policy to determine chargeable events within the service layer of the communication network;
triggering an online or offline charging event based on the determined chargeable events;
wherein the charging policy includes a configuration with attributes including eventID, event type, event start, event end, and data size and
wherein the configuration is used to create a charging event.
2. The method of claim 1 wherein the charging policy is received from an application.
3. The method of claim 1 , wherein the chargeable event identifier identifies a chargeable event object with additional attributes defining an event in the service layer of the communication network.
4. The method of claim 1 , wherein the attributes include an originator identifier identifying the charging party, and a receiver ID indicating the charged party.
5. The method of claim 1 , wherein the resource is addressable with a uniform resource indicator (URI).
6. The method of claim 1 , wherein the charging policy defines service based charging.
7. The method of claim 1 , wherein the service domain charging management function offers configurable charging services to applications.
8. The method of claim 1 , wherein the configuration is used to perform a credit check and make a determination about providing a service.
9. The method of claim 1 , wherein the charging policy concerns online charging.
10. The method of claim 1 , wherein the charging policy includes an eventID attribute that identifies the event.
11. The method of claim 1 , wherein the charging policy includes an eventType attribute that indicates the type of the event.
12. The method of claim 11 , wherein the charging policy includes an operationType attribute that defines the type of the operation to be collected.
13. The method of claim 1 , wherein the charging policy includes a chargingCredit attribute defines the avowed credit for online charging, and the charging policy includes a chargingType attribute that indicates whether the charging rule applies for ONLINE or OFFLINE charging.
14. The method of claim 1 , wherein the charging policy is configured at the service domain charging management function at the service layer.
15. The method of claim 1 , wherein the configuring and using steps are performed at the infrastructure node.
16. The method of claim 1 , wherein the multiple operations depend on an outcome of a preceding operation.
17. The method of claim 1 , wherein the online charging event produces one or more of a credit check, credit reservation and record update.
18. The method of claim 1 , wherein the offline charging event produces a charging record.