Ericsson SCAPv2 (application id: –)

The SCAPv2 (Service Charging Application Protocol version 2) interface is a part of Ericsson's Diameter-based service architecture, designed to facilitate real-time charging and cost control for services provided to users. It is specifically used in conjunction with the Diameter Credit Control (DCC) protocol, which handles the real-time accounting of service usage, ensuring that users have sufficient credit before a service is delivered.

The primary purpose of SCAPv2 is to define the framework and context for charging services within the DAAC/SCAPv2 Service. It specifies how charging interactions should occur between the application servers (providing the services) and the charging system (responsible for credit control). The interface uses a service context, which is a set of defined parameters that dictate how the DAAC Service should operate for a specific application. This includes service identification, interface parameters, charging models, and the configuration of the DAAC Service.
Key Elements of SCAPv2 Interface:

• Service Context Identification: The SCAPv2 service context is uniquely identified by the Service-Context-Id AVP (Attribute-Value Pair) in Diameter messages. This AVP contains a value that specifies which service context is being used, for example, SCAP_V.2.0@ericsson.com.
• Service Identification: Each service within the SCAPv2 context is identified using the Service-Identifier AVP. This AVP is crucial for distinguishing between different services that might be charged under the same service context. The service identifier needs to be configured both on the serving element (the application server) and within the service context to ensure proper charging.
• Over Usage: SCAPv2 includes mechanisms to prevent over-usage, ensuring that the serving element (application server) does not report more used units than the granted amount. This is critical to avoid scenarios where the user's account is charged for more than the available credit, potentially leading to service interruptions.

Ericsson SCAPv2 interface workflow:

1. Initialization:
   • When a service is requested by the user, the application server communicates with the charging system via the SCAPv2 interface.
   • The Service-Context-Id AVP is set to identify the charging framework, and the Service-Identifier AVP specifies the particular service being charged.
2. Credit Control:
   • The charging system checks the user’s account balance and determines if there is sufficient credit for the requested service.
   • If the credit is available, the service is authorized, and the application server is allowed to proceed with the service delivery.
3. Usage Reporting:
   • As the user consumes the service, the application server reports the used units back to the charging system.
   • The system tracks the usage in real-time, ensuring that it does not exceed the granted credit. If the usage approaches the credit limit, the system can request additional credit or terminate the service to prevent over-usage.
4. Service Termination:
   • Once the service is completed or if the user’s credit is exhausted, the service is terminated. The final usage data is sent to the charging system for account deduction.