Version

Ericsson SCAPv2 AVPs

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:

  • 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.

Interface workflow:

  • 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.
  • 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.
  • 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.
  • 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.

package com.mobius.software.telco.protocols.diameter.primitives.creditcontrol.ericsson;

Name

AVP Code

Data Type

Vendor

Account-Location

1073

Unsigned32

Ericsson

Represents the logical identity of an account location in an Ericsson Diameter-based credit control system. It is used to identify where an account is logically located within the network infrastructure.

If the location is unknown to the serving element, this AVP must be excluded from the request.

The Account-Location AVP is categorized as:

Static: The value does not change dynamically during the session.

Cached: The value is stored and reused for future requests.

Other-Party-Id

1075

Grouped

Ericsson

Identifies an additional party involved in a session without being charged for it. This AVP complements the Subscription-Id by providing additional details about the other party in the session.

This could represent:

  • Calling party

  • Called party

  • Redirecting party

  • Sender or receiver (depending on the service)

The AVP structure is defined as follows:

Other-Party-Id-Type (Mandatory, Enumerated): Defines the type of the other party (e.g., calling party, called party, sender, receiver).

Other-Party-Id-Data (Mandatory, UTF8String): Contains the actual identifier of the other party (e.g., phone number, username).

Other-Party-Id-Nature (Optional, Enumerated): Defines the nature of the identifier (e.g., international, national, local).

The Other-Party-Id AVP is categorized as:

  • Static: Its value does not change dynamically during the session.

  • Cached: The value can be stored and reused.

The serving element is not allowed to use the additional AVPs (*[AVP]), as they are reserved for internal service use.

Other-Party-Id-Data

1077

UTF8String

Ericsson

Contains the E.164 number (or other identifier) of the other party involved in a session.

This AVP is used in conjunction with:

Other-Party-Id-Type AVP (1076) – Defines the type of the other party (e.g., calling party, called party, sender, receiver).

Other-Party-Id-Nature AVP (1078) – Defines the nature of the identifier (e.g., international, national, local).

Other-Party-Id-Nature

1076

Enumerated

Ericsson

Specifies the nature of the address stored in the Other-Party-Id-Data AVP (1077). It defines whether the other party's number is an international number, national number, or unknown.

Used in conjunction with:

Other-Party-Id-Data (1077) – Contains the actual identifier (e.g., E.164 phone number).

Other-Party-Id-Type (1075) – Defines what type of party is being identified (e.g., calling party, called party).

If omitted, the default value is INTERNATIONAL (1) when the Other-Party-Id-Type AVP is set to END_USER_E164 (0).

Enumerated Values:

0: UNKNOWN: Address nature is unknown.

1: INTERNATIONAL (Default): The number is an E.164 international number (default value if AVP is omitted).

2: NATIONAL: The number is a national (significant) number, meaning it is formatted for use within a specific country.

Other-Party-Id-Type

1078

Enumerated

Ericsson

Used to define the format/type of identifier carried within the Other-Party-Id (1075). Specifies how the identifier should be interpreted (e.g., E.164 number, IMSI, SIP URI, NAI).

Used alongside:

Other-Party-Id-Data (1077) – Holds the actual identifier (e.g., phone number, IMSI, SIP URI).

Other-Party-Id-Nature (1076) – Defines the nature of the address (e.g., international, national).

Only END_USER_E164 (0) is supported in the SCAPv2 service context.

Enumerated Values:

0: END_USER_E164: The identifier is in E.164 phone number format (e.g., "+15551234567"). Other-Party-Id-Nature AVP (1076) must be used to specify whether it's an international or national number.

1: END_USER_IMSI: The identifier is an International Mobile Subscriber Identity (IMSI) used for mobile network subscriber identification.

2: END_USER_SIP_URI: The identifier is a SIP URI (Session Initiation Protocol Uniform Resource Identifier), used in VoIP/IMS communications (e.g., "sip:user@example.com").

3: END_USER_NAI: The identifier is a Network Access Identifier (NAI), typically used in authentication and roaming scenarios.

Result-Code-Extension

N/A

Unsigned32

Ericsson

Used to extend the standard Diameter Result-Code AVP. It provides additional error codes or customized result information beyond the standard Result-Code AVP (268).

Service-Provider-Id

1081

UTF8String

Ericsson

Used to identify a service provider in Diameter-based credit control and charging applications. The identifier format is operator-specific, meaning its structure and interpretation depend on the specific Ericsson system implementation.

The AVP is in this service context defined as ‘static’ and ‘cached’, meaning the value is predefined and stored in the system for quick access.

Subscription-Id-Location

1074

UTF8String

Ericsson

Defines the geographical location of a user identified by the Subscription-Id AVP. The value is encoded as a UTF8String and follows the E.164 numbering plan (ITU-T E.164 standard).

The AVP is in this service context defined as ‘static’ and ‘cached’, meaning the location is predefined and stored for efficient retrieval.

Used in Ericsson DAAC/SCAPv2-based systems, particularly when Mobile Number Portability (MNP) functions are required for terminating traffic.

The Subscription-Id-Location includes the following components:

Country Code (CC): Mandatory

National Destination Code (NDC): Recommended

Local Subscriber Number (LSP): Optional

Traffic-Case

1082

Unsigned32

Ericsson

Specifies the type of traffic scenario for which a charged event is being processed in an Ericsson-based Diameter Credit-Control system.

Used to classify different types of charging scenarios.

The AVP is in this service context defined as ‘static’ and ‘cached’ – meaning its value is predefined and does not change dynamically.

Values:

0 – 19: Reserved for future use

20: Originating Service Charging (For events where the user is the caller/sender)

21: Terminating Service Charging (For events where the user is the receiver)

22 – MAXRANGE: Reserved for future use (MAXRANGE represents the maximum defined unit range)

 

Start innovating with Mobius

What's next? Let's talk!

Mobius Software

As a company you'll get:

  • Get started quickly

  • Support any business model

  • Join millions of businesses

Questions? websupport@mobius.com