API-Based Charging

SCEF supports API-based charging for the following events that operate across the T8 reference point:

• NIDD Events
• Monitoring Events
• Device Triggering Events
• Enhanced coverage Restriction Events.

In addition, charging is implemented based on offline event-based charging mechanism. The network reports the resource usage by the particular user by forwarding the CDR (Charging Data Record) to the billing domain. Refer to CDR Field Properties for CDR field information.

API-Based Charging for Invocation Events

SCS/AS sends the T8 request (Nidd/Monitor/Device Trigger/ECR) to DSR APIGW, which is part of SCEF. DSR APIGW forwards the incoming T8 request to the serving SCEF-MP. The SCEF-MP acts on the message and sends back a response message to DSR APIGW. DSR then APIGW generates a CDR with available data and writes into a file in binary format. The response is then forwarded to SCS/AS.

Figure 2-27 API-Based Charging for Invocation Events

API-Based Charging for Notification Events

SCEF-MP receives a notification message from MME/HSS if SCEF is subscribed for certain events. SCEF-MP sends the notification request (Nidd/Monitor/Device Trigger) to DSR APIGW. DSR APIGW generates a CDR with available data and writes into a file in binary format. Then request is then forwarded to SCS/AS and SCS/AS response is forwarded to the SCES-MP using DSR APIGW.

Figure 2-28 API-Based Charging for Notification Events