Huawei Diameter Credit-Control AVPs
Huawei Diameter Credit-Control (application id: –)
The Huawei Diameter Credit-Control (DCC) interface is a specialized application protocol derived from the general Diameter protocol. It is designed to handle real-time credit control for a variety of user services, such as network access, SIP-based communication, and other real-time services that require immediate billing verification. The DCC interface ensures that services are only provided to users who have sufficient credit, thereby safeguarding service providers against revenue loss.
The Huawei DCC interface operates between two key components in the network architecture:
- Charging and Billing Platform (CBP): This is the DCC server responsible for processing charging requests. It applies charging rules, calculates costs, and determines whether the user's account has sufficient credit to proceed with the requested service.
- Online Charging Gateway (OCG) or Other Real-Time Charging Network Elements (NEs): These act as DCC clients. They initiate charging requests when a user attempts to access a service that requires real-time billing verification.
Interface workflow:
The interaction between the CBP and OCG/NEs through the DCC interface follows a structured process:
- Service Request Initiation: A user initiates a service that requires real-time credit control, such as a voice call, data session, or any other billable event.
- Charging Request: The OCG or another NE sends a charging request to the CBP via the DCC interface. This request includes details about the service being accessed, such as the type of service, the anticipated duration or data usage, and the current status of the user's account balance.
- Credit Authorization: Upon receiving the charging request, the CBP applies predefined charging rules to evaluate the request. It checks the user’s account balance to determine if sufficient funds are available to cover the cost of the service. If the account balance is adequate, the CBP reserves the necessary amount of credit.
- Authorization Response: The CBP sends a response back to the OCG or NE. If the service is authorized, the response indicates that the reserved credit is approved, allowing the service to be delivered to the user. If the account balance is insufficient, the response will deny the service request, and the user will be informed accordingly.
- Service Delivery: If the service is authorized, the OCG or NE proceeds to deliver the requested service to the user. The CBP continues to monitor the usage, ensuring that the service remains within the authorized credit limit. If the user consumes the authorized credit before the service ends, the CBP may initiate a subsequent charging request to extend the service, depending on the configuration.
- Final Accounting: After the service is delivered, or if the session is terminated early, the CBP finalizes the billing by deducting the actual cost of the service from the user’s account. Any unused reserved credit is released back to the user’s account.
- Purpose and Advantages
The primary purpose of the Huawei DCC interface is to provide a reliable, scalable solution for managing real-time credit control across various services. By ensuring that services are only provided when sufficient credit is available, it helps prevent revenue leakage for service providers. The Huawei DCC interface also supports complex billing scenarios, including prepaid and postpaid models, and can be easily integrated with existing charging systems to offer flexible and efficient account management.
package com.mobius.software.telco.protocols.diameter.primitives.creditcontrol.huawei
Name |
AVP Code |
Data Type |
Vendor |
ABM-Operation-Type |
30336 |
Unsigned32 |
Huawei |
Вefines the operation type for Account Balance Management (ABM) in Huawei's implementation of the Diameter protocol. This AVP allows the client or server to indicate the specific action being performed on the account, such as expenses, recharges, or locking-related operations. Values: The AVP uses enumerated values within the range [0, 999): 0: Forward operation (e.g., expense or recharge). 1: Reversal operation (e.g., expense or recharge reversal). 2: Submission operation (used only for locking). 3: Locking rollback operation. |
|||
Access-Front-End-Id |
30356 |
UTF8String |
Huawei |
Used to represent a Huawei-specific identifier for the access front-end. It provides a UTF-8 encoded string value that uniquely identifies the access front-end associated with a session or operation. |
|||
Access-Method |
20340 |
Unsigned32 |
Huawei |
Used in Huawei-specific implementations to define the method used for recharge and balance query processes. Depending on the process, it provides the method of access, such as IVR, USSD, or SMS. Values: For Recharge and Balance Query Processes: 1: IVR 2: USSD 3: SMS For UVC-Controlled Recharge Processes: 0: IVR 1: USSD 2: SMS |
|||
Access-Module |
30349 |
Integer32 |
Huawei |
Used in Huawei's recharge UVC scheme to specify the network element (NE) or system that initiates a recharge request. It categorizes the source of the recharge request by assigning specific values to different initiating entities. Values: 0: OCG (Huawei OM or SCP invokes the interface.) 1: OCG (Huawei IPCC invokes the interface.) 2: 3rd party payment gateway (A third-party system invokes the WebService of the AR for recharge.) 3: CRM (Huawei CRM invokes the interface.) 4: CBS AR GUI (Recharge request initiated from Huawei Billing Care AR GUI.) 5: Reserved for future extensions. |
|||
Access-Network-Type |
20804 |
Unsigned32 |
Huawei |
Specifies the type of network access used in a Huawei environment. This AVP helps categorize the network through which a user is accessing services. Values: 100: PSTN (Public Switched Telephone Network) 101: PBX (Private Branch Exchange) 102: PHS (Personal Handyphone System) 200: GSM (Global System for Mobile Communications) 201: GPRS (General Packet Radio Service) 202: EDGE (Enhanced Data Rates for GSM Evolution) 300: CDMA (Code Division Multiple Access) 301: CDMA 450 400: WCDMA (Wideband Code Division Multiple Access) 500: TD-SCDMA (Time Division-Synchronous Code Division Multiple Access) 600: IP/IMS (Internet Protocol/IP Multimedia Subsystem) 601: WIFI (Wireless Fidelity) 602: WIMAX (Worldwide Interoperability for Microwave Access) Other values may be introduced for future network types. |
|||
Account-Balance-Change |
20351 |
Integer64 |
Huawei |
Represents the change in the user's account balance. This AVP is used to specify the monetary adjustment (increase or decrease) applied to the account during transactions, such as recharges, deductions, or refunds. |
|||
Account-Balance-Change |
30348 |
Integer64 |
Huawei |
Used to represent modifications to the user's account balance. It specifies a monetary adjustment (increase or decrease) in the account during a transaction. This AVP plays a similar role to its counterpart with code 20351, but it is defined under a different scope or context in Huawei-specific Diameter applications. |
|||
Account-Change-Info |
20349 |
Grouped |
Huawei |
Used to provide detailed information about changes in an account's balance and related attributes. It serves as a container for various sub-AVPs that collectively describe the specifics of a balance adjustment, such as the type of account, balance changes, and associated dates. The AVP structure is defined as follows: AccountID: A unique identifier for the account. Account-Type: Specifies the type of account being affected (e.g., prepaid or postpaid). Current-Account-Balance: Indicates the balance in the account after the change. Account-Balance-Change: Represents the change in the account balance (positive for additions, negative for deductions). AccountDate: Provides the date and time associated with the account operation. Account-Date-Change: Indicates a change to the account's associated date, if any. Measure-Type: Specifies the type of measure associated with the balance change (e.g., monetary or data units). |
|||
Account-Class |
30330 |
Unsigned32 |
Huawei |
Identifies the type of account involved in a transaction or service request. This AVP provides a classification to distinguish between different account functionalities, such as charging accounts or transaction accounts. Values: 0: Charging account - Indicates that the account is used for standard charging purposes. 1: Transaction account - Specifies that the account is used for transactional operations. |
|||
Account-Code |
30347 |
UTF8String |
Huawei |
Represents a unique identifier or code associated with a specific account. While its exact usage and format are not explicitly defined in the provided documentation, it is typically used in contexts such as billing, transaction tracking, or account-specific operations. |
|||
Account-Date |
20359 |
OctetString |
Huawei |
Used to represent the validity date of an account in Huawei's Diameter-based applications. The format and interpretation of the date value are application-specific and typically follow Huawei's implementation standards. |
|||
Account-Date-Change |
20352 |
Unsigned32 |
Huawei |
Specifies the change in the validity period of an account. This AVP is used to adjust the validity duration by a specified number of seconds. |
|||
AccountID |
20357 |
OctetString |
Huawei |
Specifies the unique identifier of an account as recorded in the Customer Relationship Management (CRM) system. This identifier is critical for account-related operations such as balance management, validation, and updates. |
|||
AccountInfo |
20356 |
Grouped |
|
Provides detailed account information relevant to specific events such as recharge operations, calls, or billing. It includes information about the account state before and after the operation, along with associated monetary details. A maximum of 20 groups of AccountInfo can be transmitted in a single message. The AVP structure is defined as follows: Account-Id: Identifies the account uniquely within the system. Account-Type: Specifies the type of the account (e.g., primary or secondary). CC-Money: Indicates monetary balance details. CC-Credit: Represents the credit information of the account. Account-Date: Captures the account's validity or last update date. LifeCycle-State: Denotes the lifecycle state of the account, such as active, inactive, or suspended. |
|||
Account-Query-Method |
20346 |
Unsigned32 |
|
Specifies the method or criteria used to query account-related information. It provides flexibility to fetch specific account details, balances, or package-related data based on the query type. This AVP supports various predefined query types, catering to both prepaid and postpaid subscriber accounts. The AVP supports the following query methods: 1: Query information about all accounts. 2: Query information about the core balance account: Prepaid accounts: Type 2000. Postpaid accounts: Type 3000. 3: Query information about residual traffic. 4: Query information about the subscriber's points account. 5: Reserved. 7: Query information about the main account and all subaccounts. 8: Query information about the main account and its validity period. 9: Query information about the main account and bonus account books. 13: Query EasyNet package information. 14: Query SMS Bundle package information. 15: Query effective and expiration times of the CTU service. 16: Query remaining service usage of the CTU service under the Fair Usage Policy (FUP). 18: Query balance information about all account books, summarized by account book type, with the longest validity period. 22: CHG returns information and validity periods of all account books via AVP, while bonus account books are sent via SMS. Specific account books can be excluded. 26: Query accumulator information via USSD. |
|||
Account-Type |
20372 |
Unsigned32 |
|
Specifies the type of account, enabling differentiation between prepaid, postpaid, or hybrid account types in the system. This AVP is critical in scenarios involving balance updates, recharge operations, or account-specific queries. If a recharge is performed and no account type is specified for a hybrid subscriber, the recharge amount defaults to being credited to the prepaid account. |
|||
Activation-Date |
30820 |
OctetString |
|
Provides the date when a specific service or account was activated. It is an essential AVP for tracking the initiation time of subscriptions, services, or related features. The value is encoded as an OctetString and must comply with the defined length range. |
|||
Active-Currency-Code |
20894 |
Unsigned32 |
|
Specifies the currently active currency code used for billing, account management, or other financial operations. It is encoded as an Unsigned32 value, typically representing a currency in a numeric format (e.g., [ISO4217] numeric codes). |
|||
Active-Day |
20367 |
Unsigned32 |
|
Specifies the number of active days added to a user’s account as a result of a recharge operation. It represents the duration (in days) for which a service or account remains active following a recharge. |
|||
Active-Flag |
20978 |
Integer32 |
|
Indicates whether activation should occur during a pure authentication process. This AVP defines a binary decision with the following options: 0: Activation is not performed during authentication. 1: Activation is performed during authentication. |
|||
Active-Method |
20738 |
Unsigned32 |
|
Indicates the channel through which a subscriber activates their personal account for the first time. The Online Charging Gateway (OCG) communicates this channel information to the Convergent Billing Point (CBP) during the account activation process. Predefined Channel Values: 1: IVR (Interactive Voice Response) 2: USSD (Unstructured Supplementary Service Data) 3: SMS (Short Message Service) 4: OCS (Online Charging System) 5: WebService Interface 6: GPRS (General Packet Radio Service) Extensions: Carriers may define and implement additional channels as needed. |
|||
Active-Period |
20733 |
OctetString |
|
Indicates the end date of the validity period for a subscriber's account. This date is specified in days, with the expiration time being 23:59:59 on the specified day. |
|||
Additional-Calling-Party-Number |
20312 |
UTF8String |
|
Used to represent an additional calling number associated with a session or operation. This number is typically supplementary to the primary calling party number and can provide additional context for call processing or billing. |
|||
Additional-Info |
20371 |
UTF8String |
|
Designed to carry supplementary information within Diameter messages. This AVP is primarily intended for logging and recording purposes, specifically for writing Call Detail Records (CDRs). It allows service providers to include optional, descriptive, or contextual data that may not directly affect session processing. |
|||
Additional-Info |
20665 |
UTF8String |
|
Provides supplementary information in the context of the RTBP-Information AVP group within Diameter messages. It is primarily used during the Call Detail Record (CDR) writing process to store optional or contextual data that does not directly affect session processing or Diameter protocol operations. |
|||
Address-Of-Restricted-Indicator |
21121 |
Unsigned32 |
|
Specifies whether the Calling Line Identification Restriction (CLIR) is enabled or disabled for a session. CLIR determines whether the caller's number is displayed to the called party. |
|||
Adjust-Roaming-Type |
21010 |
Integer32 |
|
Used to indicate whether the roaming type should be adjusted to "no-roaming" for calls made near a network boundary. This functionality is particularly useful in managing billing or routing for calls that might otherwise be incorrectly categorized due to proximity to a roaming zone. Values: 0: Do not adjust the roaming type to "no-roaming." 1: Adjust the roaming type to "no-roaming." |
|||
Alert-Level |
20499 |
Unsigned32 |
|
Used to specify the type of low-balance notification in Huawei's Diameter protocol implementation. The value of this AVP categorizes the alert based on the level of the threshold triggering the notification. The numeric prefix in the value indicates the scope of the threshold. Threshold Levels: 1xx: Subscriber-level threshold. 2xx: System-level threshold. |
|||
Amount-Before-Recharge |
20914 |
Unsigned32 |
|
Used to indicate the subscriber's main account balance before a recharge operation. This AVP is returned by the EVC (Electronic Voucher Card) recharge interface as part of the recharge response process. |
|||
Announcement-Data |
20931 |
Grouped |
|
Provides information about an announcement group. This AVP is typically used to define or reference specific announcements within a telecommunications system, such as call waiting messages, recharge prompts, or service-related announcements. The AVP structure is defined as follows: Announcement-Order: Indicates the order in which announcements should be played. Announcement-Id: Uniquely identifies an announcement within the group. Announcement-Parameter: Specifies additional parameters related to the announcement. |
|||
Apply-Time |
30332 |
OctetString |
|
Specifies the time when an operation or event should be applied. Although the specific context is not described in the provided documentation, it is likely used in scenarios such as scheduling updates, applying configurations, or triggering specific actions at a designated time. |
|||
ATM-Recharge-Source-Type |
20799 |
Unsigned32 |
|
Differentiates between the recharge menu and payment menu in ATM-based payment systems. This AVP is used to specify the context of a transaction initiated via an ATM system. Options: 0: Recharge – Indicates a balance top-up transaction. 1: Payment – Indicates a payment transaction, such as bill payment or settlement. |
|||
Auth-Action |
30803 |
UTF8String |
|
Used to define instructions for authentication results. It conveys a two-digit command string that specifies subsequent actions after an authentication operation. Each digit in the string holds a distinct meaning: First Digit (Service Logic Handling): 0: CONTINUE – Continue the service logic. 1: BREAK – Terminate the service logic unconditionally. 2: Access Service/Management Component – Terminate service logic and directly connect to the service/management component. 3: Reroute – Terminate service logic and reroute the call to another number. Second Digit (Message Display Handling): 0: No Prompt – Do not display any message. 1: Display Message – Display a message to the user. The message can contain details about the authentication result or other contextual information. |
|||
Auth-Information |
30800 |
Grouped |
|
Used to encapsulate internal authentication results returned by the Online Charging System (OCS). This AVP enables communication of detailed authentication outcomes and instructions for charging or service processing. For Huawei systems, the group information can trigger specific actions based on authentication results. For interconnection with third-party devices, the inclusion of this AVP is subject to agreement during interconnection processes. The AVP structure is defined as follows: Auth-Result-Code: Indicates the result code of the authentication process. Auth-User-State: Describes the state of the authenticated user. Auth-Action: Specifies actions to be taken based on authentication results. Auth-Voice-ID: Contains a voice-related identifier used in specific service scenarios. Auth-Message-ID: Contains a message identifier for user notifications or service interactions. Auth-Sub-Service-Key: Identifies a sub-service key for handling service-specific authentication details. |
|||
Auth-Message-ID |
30805 |
Unsigned32 |
|
Specifies the identifier of the short message to be sent by the system when a message display is required. This AVP is relevant when the second digit of the Auth-Action AVP indicates 1 (i.e., the user needs to see a message). When the second digit of Auth-Action equals 1, this AVP provides the ID of the message to display. |
|||
Auth-Reroute-Number |
21190 |
OctetString |
|
Provides the reroute number to be used when specific rerouting actions are required. This AVP is applicable when the first digit of the Auth-Action AVP is set to 3, which indicates that the service logic should release and reroute the call to a new number. When the first digit of Auth-Action equals 3, the Auth-Reroute-Number specifies the new destination to reroute the call. |
|||
Auth-Result-Code |
30801 |
Unsigned32 |
|
Represents the result of an authentication process. This AVP is used to indicate the outcome of the authentication and authorization for a subscriber's access to a service. It provides a code that reflects the result of validating the subscriber state, service scenario, and other service-specific information. |
|||
Auth-Sub-Brand-Type |
30910 |
Unsigned32 |
|
Indicates the primary offering type or sub-brand type associated with a service or subscriber. This AVP is used to define specific branding or service-level classifications within the operator's ecosystem. Supported Values: 1: HappyZone - Represents a specific service offering or brand type under the primary operator's umbrella. |
|||
Auth-Sub-Service-Key |
30806 |
UTF8String |
|
Specifies the function ID of a service component. It is used when the first digit of the Auth-Action AVP indicates a value of 2, which corresponds to releasing the service logic and connecting it to a specific service component. This AVP provides a mechanism to identify and route calls or sessions to a particular service component after releasing the primary service logic. |
|||
Auth-User-State |
30802 |
UTF8String |
|
Provides detailed information about the current life cycle and management state of a subscriber. The AVP value is structured as a seven-digit code in the format CCMMMMM, where: Digits 1-2 (CC): Represent the life cycle status of the subscriber (prepaid or postpaid). Digits 3-7 (MMMMM): Represent specific management states for the subscriber. Life Cycle States: Prepaid and Postpaid Subscriber Status (Digit 1 or 2): 0: Idle 1: Active 2: Barred 3: Suspended 4: Pool Management States: Specific Indicators (Digits 3-7): Digit 3: Indicates if the subscriber has reported their SIM as missing. 0: No, 1: Yes Digit 4: Indicates if the subscriber is suspended upon their request. 0: No, 1: Yes Digit 5: Indicates if the subscriber is suspended but their number is reserved. 0: No, 1: Yes Digit 6: Indicates if the subscriber is blocked. 0: No, 1: Yes Digit 7: Indicates if the subscriber is added to the blacklist. 0: No, 1: Yes |
|||
Auth-Voice-ID |
30804 |
Unsigned32 |
|
Specifies the ID of the voice message that the system should play. This AVP is used in scenarios where a message is displayed to the subscriber, as indicated by the second digit of the Auth-Action AVP being 1. |
|||
Balance-Category |
60003 |
Integer32 |
|
Specifies the type of balance account associated with a subscriber. This AVP helps classify different types of balances within the subscriber’s account. Values: 0: Balance Account - Represents the standard balance account for payment or recharge transactions. Allowed Payment-Type Values: 0 or 1. 1: Credit Account - Represents a credit account where charges are deducted on a postpaid basis. Allowed Payment-Type Values: 1 only. 2: Free Resource Account - Represents a pool of free resources (e.g., bonus data, minutes, or SMS). Allowed Payment-Type Values: Can be left blank. |
|||
Balance-Date |
60007 |
Time |
|
Indicates the validity period of a balance account. This AVP helps manage the lifecycle of balance accounts by specifying their expiration or end date. The value is expressed in seconds since January 1, 1900, 00:00 UTC. |
|||
Balance-ID |
60004 |
Integer64 |
|
Uniquely identifies a balance instance within the system. The interpretation of this AVP depends on the value of the associated Balance-Category AVP. When Balance-Category = 0: Represents the ID of a balance account instance. When Balance-Category = 1: Represents the ID of a credit account instance. When Balance-Category = 2: Represents the ID of a free resource account instance. |
|||
Balance-Info |
60001 |
Grouped |
|
Provides detailed information about queried account balances. It supports up to 20 groups of records, covering the main fund, bonus amounts, and free resources. This AVP is critical for managing and querying financial information in telecom systems. The AVP structure is defined as follows: Payment-Type: Indicates the payment type, e.g., prepaid or postpaid. Balance-Category: Specifies the type of balance, such as main account, credit, or free resources. Balance-ID: Uniquely identifies the balance instance. Balance-Type: Indicates the type of the balance instance. Current-Balance: Represents the current balance amount. Balance-Date: Indicates the validity period of the balance. Measure-Type: Defines the unit of measurement for the balance (e.g., currency, time, or data volume). Currency-Code: Identifies the currency for monetary balances. Related-Object-Type: Indicates the type of related object (e.g., service type or resource type). Related-Object-ID: Uniquely identifies the related object. Unpaid-Fee: Represents any unpaid fee associated with the account. |
|||
Balance-Type |
30326 |
Integer64 |
|
Used to define the type of balance associated with a subscriber account or service. This AVP provides flexibility in categorizing and managing balances in telecom environments. |
|||
Balance-Type |
60005 |
Integer32 |
|
Used to indicate the specific type of balance based on the Balance-Category AVP. This AVP allows the differentiation of balances across categories such as monetary funds, credits, or free resources. Behavior by Balance-Category Balance-Category: 0 (Monetary Funds) 2000: Prepaid main funds bill type. 3000: Postpaid main funds bill type. Balance-Category: 1 (Credit) - Indicates a type of credit balance. Balance-Category: 2 (Free Resource) - Indicates a type of free resource. |
|||
Bank-Channel-Distribution-Code |
20793 |
OctetString |
|
Used to identify the distribution code associated with a specific bank channel. It enables tracking and differentiation of transactions across multiple banking channels, facilitating detailed reporting and processing. |
|||
Bank-Code |
20974 |
OctetString |
|
Used to represent a specific code associated with a bank. This AVP serves as an identifier for banks in financial or transactional contexts, facilitating accurate routing, processing, and reporting of banking-related operations. |
|||
Bearer-Capability |
20313 |
OctetString |
|
Specifies the service type supported in the circuit-switched domain. This AVP identifies various services such as video calls, fax services, and data services that are carried over the bearer. |
|||
Bearer-Protocol-Type |
20522 |
Unsigned32 |
|
Specifies the network access type. This AVP is used to identify the protocol or technology used for network access during communication. Values: 01: WAP/IP 10: HTTP/TCP/IP 20: SMTP 30: RTSP 40: FTP 100: ADSL/LAN 101: Dial-Up/ISDN 102: WiFi 200: GPRS/UMTS 300: CDMA 400: WiMAX 500: TD-SCDMA Others: To be extended |
|||
Bearer-Type |
20519 |
Unsigned32 |
|
Represents the type of bearer used for a session. The bearer type typically indicates the nature of the connection or service being utilized for the communication session. |
|||
Bear-Service |
20641 |
UTF8String |
|
Specifies the service type being carried over the bearer. This AVP is often used to identify specific services for billing, authentication, or service-level policy enforcement. Values: 1: SMSC (Short Message Service Center) 2: AAA (Authentication, Authorization, and Accounting) 3: BREW (Binary Runtime Environment for Wireless) Additional values may be defined or extended based on network requirements. |
|||
Brand |
30815 |
Unsigned32 |
|
Represents the identity of a brand. This AVP is used to distinguish between different brands or sub-brands managed within the same network, typically for segmentation, branding-specific policies, or differentiated user experience. |
|||
Call-Begin-Time |
30365 |
UTF8String |
|
Specifies the start time of a call. The value is represented in a detailed timestamp format, accurate to 0.1 seconds. Format: YYYYMMDDHHMMSSd Where: YYYY = Year MM = Month DD = Day HH = Hour (24-hour format) MM = Minutes SS = Seconds d = Tenths of a second |
|||
Called-CellID-Or-SAI |
20306 |
UTF8String |
|
Provides information about the Cell ID or Service Area Identifier (SAI) that the called party is currently visiting. This data is primarily used for call tracking and location-based services. |
|||
Called-IMEI |
20308 |
UTF8String |
|
Contains the International Mobile Station Equipment Identity (IMEI) number of the device used by the called party. This AVP is typically used for device identification in call management and analytics. |
|||
Called-LAI |
20307 |
UTF8String |
|
Represents the Location Area Identifier (LAI) where the called party is located. The LAI is a globally unique identifier used to specify a location area within a mobile network. This information is essential for mobility management and network operations. |
|||
Called-Location-Number |
21173 |
OctetString |
|
Contains the location number associated with a called party, as used in the Initial Detection Point (IDP) procedures. This value typically represents routing or location-specific information related to the called party's service. |
|||
Called-Location-Number-Nature |
21174 |
Unsigned32 |
|
Specifies the nature or format of the called location number. It provides context about how the number should be interpreted within the network. Values: 0: Spare (reserved for future use) 1: Subscriber number (within a national service) 2: Unknown number (within a national service) 3: National number 4: International number |
|||
Called-Msc-Address |
21172 |
OctetString |
|
Represents the address of the Mobile Switching Center (MSC) associated with the called party. The address typically includes routing information used in mobile networks for call delivery. |
|||
Called-Party-Address |
20337 |
UTF8String |
|
Indicates the phone number of the party being called. This AVP can report various number formats depending on the use case and the originating system (e.g., SSP or OCG). The number dialed by the subscriber, reported by the Service Switching Point (SSP). In call forwarding scenarios, this AVP contains the forwarding number. |
|||
Called-Party-Address-Nature |
21163 |
Unsigned32 |
|
Specifies the nature of the address of the called number. It defines the type of number format or the address attributes for the called party. Values: 0: Spare 1: Subscriber number (national service) 2: Unknown number (national service) 3: National number 4: International number 5: Number specified by a network (national service) |
|||
Called-Party-BCDNumber |
21164 |
OctetString |
|
Represents the called party's number encoded in Binary Coded Decimal (BCD) format. This format is commonly used in telecommunications systems to encode telephone numbers efficiently for signaling purposes. |
|||
Called-Party-BCDNumber-Nature |
21165 |
Unsigned32 |
|
Defines the nature or classification of a called party's number when represented in Binary Coded Decimal (BCD) format. This classification ensures that the system properly interprets and processes the number for routing, billing, and service delivery. Values: 2: Unknown number (in a national service). 3: National number. 4: International number. 5: Number specified by a network (in a national service). 6: Dedicated short number. |
|||
Called-Party-NP |
20385 |
UTF8String |
|
Specifies the Number Portability (NP) prefix of a called party's number during the calling process. The NP prefix is used to identify whether the number has been ported and to which network it currently belongs. |
|||
Called-Service |
20420 |
Unsigned32 |
|
Identifies the specific service requested or invoked during the call session. This AVP helps distinguish between different service types or actions tied to the called number. |
|||
Called-Short-Number |
20338 |
UTF8String |
|
Represents the VPN short number dialed by the calling party to reach the called party within a Virtual Private Network (VPN). It facilitates routing and handling of calls within VPNs by providing the compact number representation of the called party. |
|||
Called-Vlr-Number |
20305 |
UTF8String |
|
Identifies the Visitor Location Register (VLR) code associated with the geographic area where the called party is currently located. This AVP plays a critical role in mobile network scenarios where tracking and routing calls rely on the VLR information of the subscriber. |
|||
Call-Forward-Indicator |
20387 |
Unsigned32 |
|
Specifies whether the called number is forwarded to another number. It plays a crucial role in call routing and management, particularly in multi-stage call forwarding scenarios. Values: 0: No forwarding - Indicates that the call is not being forwarded. 1: Forwarding - Indicates that the call is forwarded to another number. |
|||
Calling-CellID-Or-SAI |
20303 |
UTF8String |
|
Identifies the Cell ID or Service Area Identifier (SAI) where the calling party is currently located. This information is typically used in mobility management and call routing scenarios to enhance service quality and ensure proper resource allocation. |
|||
Calling-IMEI |
20309 |
UTF8String |
|
Contains the International Mobile Equipment Identity (IMEI) of the device initiating the call. The IMEI is a unique identifier assigned to mobile devices, typically used to distinguish devices on a network, enable device-specific policies, and assist in fraud prevention. |
|||
Calling-LAI |
20304 |
UTF8String |
|
Provides the Location Area Identifier (LAI) for the area in which the calling party is currently located. The LAI uniquely identifies a location area within a mobile network, assisting in subscriber mobility management, call routing, and billing. |
|||
Calling-Location-Number |
21170 |
OctetString |
|
Represents the Location Number for the originating party. This AVP is part of the location management process and helps identify the number associated with the location from where the call was initiated. |
|||
Calling-Location-Number-Nature |
21171 |
Unsigned32 |
|
Specifies the attribute type of the calling party's location number. It categorizes the nature of the location number, providing additional context for how the number should be interpreted or handled within the network. Values: 0: Spare 1: Subscriber number (used in a national service). 2: Unknown number (used in a national service). 3: National number. 4: International number. |
|||
Calling-MSC-Address |
21169 |
OctetString |
|
Provides the Mobile Switching Center (MSC) address of the calling party. This address identifies the originating MSC that processed the call, allowing the receiving system to handle the call routing and processing efficiently. |
|||
Calling-Party-Address |
20336 |
UTF8String |
|
Specifies the calling number of a subscriber, which is typically used in call routing and identification. This AVP ensures accurate representation of the calling party in various call-processing scenarios. Supported Formats: International Calls: International Prefix + Country Code + Area Number + PSTN National Calls: Area Number + PSTN Mobile Virtual Network Operator (MVNO) Calls: Country Code (CC) + Mobile Subscriber Integrated Services Digital Network (MSISDN) The Country Code (CC) corresponds to the location of the Online Charging Gateway (OCG) system. |
|||
Calling-Party-Address-Nature |
21162 |
Unsigned32 |
|
Defines the nature or type of the calling party's address. This AVP helps in identifying the context or format of the calling number, which is crucial for routing and call-handling decisions. The AVP uses predefined integer values to represent the address nature: 0: Spare (reserved for future use). 1: Subscriber number (used within national services). 2: Unknown number (used within national services). 3: National number (used for domestic calls). 4: International number (used for global calls). 5: Number specified by the network (used within national services). |
|||
Calling-Party-NP |
20384 |
UTF8String |
|
Represents the Number Portability (NP) prefix of the calling party's number in the called process. It indicates whether a phone number has been ported and provides associated prefix information for accurate routing and billing. |
|||
Calling-Partys-Category |
20301 |
Unsigned32 |
|
Identifies the type or category of the calling party in a telecommunication session. This can include distinctions such as carrier, public telephone, or regular users, enabling operators to classify and handle calls appropriately based on the calling party’s category. The exact definitions of categories are operator-specific, but typical examples include: 0: Carrier 1: Public telephone 2: Common user 3: Emergency service |
|||
Calling-Service |
20411 |
Unsigned32 |
|
Identifies the specific service or application used by the calling party in a Diameter session. It allows for tracking and differentiation of services originating from the calling party, aiding in service-specific processing, billing, and policy enforcement. While specific service definitions depend on operator configurations, examples could include: 1: Voice service 2: Video service 3: Data service 4: SMS service |
|||
Calling-VLR-Number |
20302 |
UTF8String |
|
Identifies the Visitor Location Register (VLR) code of the area where the calling party is located during a session. This AVP is crucial for mobility management and location-based services, ensuring accurate identification of the caller's geographic region. |
|||
Call-Reference-Number |
20321 |
UTF8String |
|
Filled by the Mobile Switching Center (MSC) to uniquely identify a specific call or session within the network. This AVP acts as a session or transaction identifier, allowing efficient call tracking and troubleshooting. |
|||
Call-Type |
20807 |
Unsigned32 |
|
Specifies the type of call based on its context within a network. This classification is essential for proper call handling, billing, and management within VPN and non-VPN environments. Values: 0: On-net call - Call between subscribers within the same VPN network. 1: Off-net call - Call between a VPN subscriber and a non-VPN subscriber. 2: Cross-net call - Call between subscribers in different VPN networks. 3: Common call (reserved) - Call between subscribers not associated with any VPN network. 4: Off-net number group call - Call where the caller is a VPN subscriber and the recipient is a non-VPN subscriber in a corporate-defined group. 5: Attendant call - Call initiated or answered by a VPN attendant. 6: Charge-free call (reserved) - Free-of-charge call. 7: Closed group call - Call between subscribers from Closed User Group (CUG) in the same VPN network. 8: Super-group call - Call involving at least one subscriber from a higher-level VPN network (e.g., headquarter and branch). 9: Cell-based charge (reserved) - Call billed based on cell ID. 10: AIP attendant call (reserved) - Call initiated or answered by an Advanced IP (AIP) attendant. 11: Off-net number group call at group member level - Similar to type 4 but defined at the corporate member level. |
|||
Card-Batch |
20364 |
OctetString |
|
Identifies the batch number of a voucher card. This information is used in telecommunications systems to track and manage voucher card details, often in prepaid services or other credit-control applications. |
|||
Card-Brand-ID |
22121 |
OctetString |
|
Identifies the brand associated with a voucher card. This AVP is used in telecommunications systems to specify and distinguish between different voucher brands or carriers. It is essential in systems that manage multiple voucher providers or types. |
|||
Card-Cur-Distributor-ID |
21120 |
UTF8String |
|
Specifies the identifier of the distributor responsible for managing or issuing a particular voucher card. This AVP is used in telecommunications systems to associate a voucher with its distributor, enabling proper tracking, validation, and management of distribution channels. |
|||
Card-Money |
20378 |
Integer64 |
|
Specifies the monetary face value of a voucher card. It is typically used in telecommunications systems for recharge and billing purposes, allowing systems to correctly credit the voucher's worth to the appropriate account. |
|||
Card-Number |
20342 |
OctetString |
|
Identifies the unique number associated with a voucher card. This number is typically used in telecommunications systems to process voucher-related operations, such as recharges or validation of card authenticity. |
|||
Card-Sp-ID |
20389 |
Unsigned32 |
|
Identifies the Service Provider (SP) ID associated with a voucher card. This AVP is typically used to link the voucher card to a specific service provider, ensuring proper allocation and tracking within telecommunications systems. |
|||
Card-Type |
20365 |
Unsigned32 |
|
Specifies the type of a voucher card. This AVP is used to categorize and identify the purpose or characteristics of a voucher card within a system, such as prepaid, promotional, or specialized card types. |
|||
Category-ID |
20639 |
UTF8String |
|
Represents the service category identifier. This AVP is used to define or classify a service into a specific category for better management, routing, or reporting purposes. |
|||
CC-Credit |
473 |
Grouped |
|
Represents the credit available in a user’s account. It provides information about the credit in terms of units and optionally includes the associated currency code. The AVP structure is defined as follows: Currency-Code: specifying the currency in which the credit is measured. |
|||
CDR-Begin-Time |
20632 |
Integer32 |
|
Indicates the start time of service access in the form of a timestamp. This AVP is used for generating Call Detail Records (CDRs), capturing the initiation time of a specific service or session. The time is represented in the format: YYYYMMDD24hhmiss Where: YYYY: Year (4 digits) MM: Month (2 digits, 01-12) DD: Day (2 digits, 01-31) 24hh: Hour in 24-hour format (2 digits, 00-23) mi: Minutes (2 digits, 00-59) ss: Seconds (2 digits, 00-59) |
|||
CDR-Charge-Mode |
20626 |
Integer32 |
|
Specifies the charging mode applied for a particular service or session. It defines how a user is billed for the service, using a predefined set of modes. This AVP is primarily used in billing systems and Call Detail Records (CDRs) to document the applied charging method. Values: -1: Not Applicable (NA) 0: Monthly charge 1: Charging by occurrences 2: Charging by items 3: Charging by pages 4: Charging by volume 5: Charging by duration 6: Fixed fee 7: Free 8: Fixed fee by seconds 9: Fixed fee by occurrences 10: Fixed fee by days 11: Fixed fee by volume 12: Fixed fee by items 13: Fixed monthly fee |
|||
CDR-Duration |
20628 |
Integer32 |
|
Specifies the duration of service access for a particular session or event. The value is represented in seconds and provides a precise measurement of the time span for which the service was accessed. This AVP is commonly used in billing systems and Call Detail Records (CDRs) for duration-based charging or analytics. |
|||
CDR-End-Time |
20633 |
Integer32 |
|
Specifies the end time of a service access session. The value is encoded in the format YYYYMMDD24hhmiss, representing the date and time up to seconds. This AVP is crucial for billing, analytics, and call/session tracking, often used in combination with the CDR-Begin-Time AVP to calculate session duration. |
|||
CDR-Pkg-Product-Id |
20636 |
UTF8String |
|
Represents the identifier of a package or node-level product used within a billing or service context. This AVP is crucial for differentiating between multiple product packages or nodes associated with a particular session or service in a Call Detail Record (CDR). |
|||
CDR-Pkg-Service-Id |
20635 |
UTF8String |
|
Specifies the identifier of a package or node-level service within the context of a Call Detail Record (CDR). It uniquely identifies a service associated with a package or node, facilitating tracking and differentiation of specific services availed by a subscriber. |
|||
CDR-PkgSp-Id |
20634 |
UTF8String |
|
Identifies the service provider (SP) or entity responsible for the package or node within the context of a Call Detail Record (CDR). This AVP provides a unique identifier for the SP, enabling effective tracking and management of services or packages offered by different providers. |
|||
CDR-Product-ID |
20625 |
UTF8String |
|
Used to identify the product associated with a Call Detail Record (CDR). It provides a unique identifier for the product, enabling accurate tracking, management, and analysis of product usage and performance. |
|||
CDR-Qos |
20528 |
UTF8String |
|
Specifies the Quality of Service (QoS) profile applied by the Gateway GPRS Support Node (GGSN) in a mobile data network. It provides information about the QoS parameters associated with a session or service, enabling accurate tracking and management of network resource allocation and service performance. |
|||
CDR-Service-Name |
20638 |
UTF8String |
|
Records the name of the service associated with a session or transaction in Call Detail Records (CDRs). This AVP provides a human-readable identifier for the service, aiding in billing, analytics, and troubleshooting. |
|||
CDR-Service-Type |
20631 |
Integer32 |
|
Specifies the type of service associated with a session or transaction in Call Detail Records (CDRs). It categorizes the service into predefined types, enabling precise identification and usage tracking. Values: 0: WAP 1: KJava 2: SMS 3: MMS 4: Mail 5: LBS (Location-Based Services) 6: Stream Media 7: IMPS (Instant Messaging and Presence Services) 8: UM (Unified Messaging) 9: WapPush 11: CRBT (Caller Ring Back Tone) 12: General 13: MC (Messaging Center) 14: PIM (Personal Information Manager) 15: VMB (Voice Mailbox) 16: CMB (Content Management Box) 17: PaymentGW (Payment Gateway) 18: Storage 20: Service Package |
|||
CDR-SP-Name |
20637 |
UTF8String |
|
Specifies the name of the service provider associated with a session or transaction, as recorded in Call Detail Records (CDRs). This information helps identify the entity responsible for providing the service, offering insights into service usage across providers. |
|||
CDR-Times |
20627 |
Integer32 |
|
Specifies the session timeout interval for a service in seconds. If the value is not provided or set to null, a default timeout interval is assumed. This AVP helps define the duration after which a session will automatically timeout if no further activity is detected. |
|||
CDR-Type |
20630 |
Integer32 |
|
Used to specify the type of Call Detail Record (CDR) being generated or referenced. While the exact enumeration values and their corresponding meanings are not provided in the AVP description, this AVP is typically used in systems that generate, store, or process CDRs for billing, reporting, or auditing purposes. |
|||
CDR-Volume |
20629 |
Integer32 |
|
Represents the volume of traffic or data generated during the service session being recorded. The traffic is measured in bytes, providing detailed insights into the volume consumed for billing, monitoring, or analytical purposes. |
|||
Change-Type |
30325 |
Unsigned32 |
|
Identifies the type of operation performed on an account. It indicates whether the operation involves a deduction or a recharge of the account balance. Values: 0: Deduct 1: Recharge |
|||
Channel-ID |
22347 |
UTF8String |
|
Specifies the recharge channel type. It is derived from the RechargeChannelID parameter of the WebService interface, identifying the method or source through which a recharge is performed. |
|||
Charge-Confirm-Flag |
20347 |
Enumerated |
|
Used to indicate the confirmation status of a recharge operation. It provides the system with a binary flag that dictates whether the recharge should be confirmed or canceled. Values: 0: Confirm the recharge 1: Cancel the recharge |
|||
Charge-Flow-Type |
20339 |
Unsigned32 |
|
Defines the type of charging flow in mobile communication scenarios. It categorizes the direction or purpose of the data or call flow for charging purposes. Values: 0: Mobile Originating Flow 1: Mobile Terminating Flow 3: Mobile Forwarding Flow |
|||
Charge-Mode |
20610 |
Integer32 |
|
Specifies the method used for charging a session or service. It defines the type of resource consumption (e.g., duration, volume, or frequency) to be measured for billing purposes. Values: 0: Charging by Times 1: Charging by Volume 2: Charging by Duration |
|||
Charge-Money |
20344 |
Grouped |
|
Grouped AVP used to specify details of a recharge operation. It includes the value being recharged, any new balance resulting from the recharge, and the validity period or active days associated with the recharge. The AVP structure is defined as follows: Money-Value: Indicates the monetary value of the recharge. New-Money: Specifies the new balance after recharge. Active-Day: Defines the validity period in days. |
|||
Charge-Number |
20326 |
OctetString |
|
Specifies the number associated with a charging operation. This AVP is commonly used to indicate the subscriber or account number that is being charged for a service or transaction. |
|||
Charge-Number-Nature |
30051 |
Integer32 |
|
Specifies the attribute of the charged party number. It is used to indicate the context or category of the charged number, which may be required for billing analysis or charge processing. This AVP is commonly utilized in charging scenarios where the nature of the charged number affects the billing logic. |
|||
Charge-Party-Type |
20731 |
Unsigned32 |
|
Specifies the type of party being charged for a given service or transaction. This AVP helps in determining the billing approach based on the nature of the charged entity, such as prepaid, postpaid, hybrid, or promotional balances. |
|||
Charging-ID |
20527 |
UTF8String |
|
Specifies a unique identifier for a charge transaction. This identifier is used to correlate charging data across systems and services, ensuring accurate billing and transaction tracking. |
|||
Clearing-House-Id |
20798 |
OctetString |
|
Specifies an identifier for the clearing house involved in processing a transaction. Clearing houses act as intermediaries in billing and settlement processes, ensuring proper reconciliation of charges and payments. |
|||
Client-IP |
20510 |
IPAddress |
|
Identifies the IP address of the client involved in a Diameter transaction. This AVP is typically used for tracking, security, and audit purposes. It ensures that the system can accurately identify and associate client-specific activities with their respective IP addresses. |
|||
Community-Information |
21204 |
Grouped |
|
Used to define community-specific information related to calling and called parties. It encapsulates details such as number types, group numbers, VPN-specific flags, and additional screening and display parameters. The AVP structure is defined as follows: S-Caller-Number-Type / S-Called-Number-Type: Specifies the type of number used by the caller/called party. S-Caller-VPN-Phone-Flags / S-Called-VPN-Phone-Flags: Includes flags specific to VPN phone configurations. S-Caller-PBX-Display-Number / S-Called-PBX-Display-Number: Indicates the PBX display number for caller/called party. S-Caller-Hunting-Main-Number / S-Called-Hunting-Main-Number: Represents the main number used in hunting scenarios for caller/called party. S-Caller-Group-Number / S-Called-Group-Number: Identifies the group number associated with the caller/called party. S-Caller-Top-Group-Number / S-Called-Top-Group-Number: Refers to the top-level group number in hierarchical groups. S-Caller-Short-Number: A short number associated with the caller. S-Called-Long-Number: Represents a long-form number for the called party. Member-Screen-Class: Classifies the screening rules for the member. Screen-Zone-ID: Identifies the screening zone. |
|||
Connect-Called-Number |
20373 |
UTF8String |
|
Represents the number dialed by the user to establish a connection. In cases where an IP prefix is preset, this AVP includes both the IP prefix and the dialed number. |
|||
Consumer-Account-Id |
30359 |
Unsigned32 |
|
Used to represent an account identifier associated with a consumer. Although the description is not provided in detail, this AVP typically serves to uniquely identify a user's account within a system for various Diameter-based applications. |
|||
Content-ID |
20640 |
UTF8String |
|
Identifies specific content in a Diameter message. It is typically used in content-related operations to reference a particular piece of content in a transaction, such as downloadable media, subscription-based services, or application-specific data. |
|||
Content-ID (Binary) |
20508 |
OctetString |
|
Used to identify content using a binary format. It is often applied in contexts where binary encoding is preferred for efficiency or when the identifier contains non-textual data. |
|||
Cost-Type |
20392 |
Unsigned32 |
|
Specifies the type of service fee associated with a particular transaction or session. This AVP is useful in scenarios where fees need to be categorized, such as local fees, roaming fees, or charges related to e-commerce services. |
|||
Credit-Type |
30344 |
Unsigned64 |
|
Used to represent specific credit-related values in Diameter messages. This AVP is essential for handling credit management within prepaid or postpaid services. Although the description lacks specific details, its large range and type suggest use cases where high precision and extended ranges are required, such as financial transactions or extensive credit management. |
|||
Credit-Use-Notification |
21176 |
Grouped |
|
Designed to notify the system about credit usage. This AVP is particularly useful for scenarios involving real-time credit management in telecommunications, where credit usage needs to be monitored and accounted for efficiently. The AVP structure is defined as follows: PPS-Account-Notify: Details notifications specific to prepaid systems POS-Account-Notify: Details notifications specific to point-of-sale accounts |
|||
Cum-Id |
20854 |
OctetString |
|
Serves as a unique identifier for the consumption accumulator of a subscriber. This AVP is primarily used in scenarios where tracking and managing consumption metrics for subscribers is essential, such as in prepaid or postpaid billing systems in telecommunications. |
|||
Cum-Info |
20853 |
Grouped |
|
Provides accumulated consumption information for a subscriber. It encapsulates data related to subscriber consumption metrics, allowing up to 13 records to be saved within its structure. The AVP structure is defined as follows: Cum-Money: Represents the amount of money consumed by the subscriber. CumId: Unique identifier for the consumption accumulator. |
|||
Cum-Money |
20855 |
Grouped |
|
Represents the accumulated consumption amount for a subscriber. It is a grouped AVP designed to encapsulate detailed usage metrics, particularly in monetary terms. This AVP includes a mandatory CumUnit-Value sub-AVP to define the unit and value of accumulated consumption. The AVP structure is defined as follows: CumUnit-Value: Represents the unit and value of accumulated consumption. |
|||
Cumulate-Type |
30338 |
Integer64 |
|
Represents a cumulative metric associated with subscriber usage or other Diameter-related calculations, such as accumulated data consumption or call durations. |
|||
Cum-Unit-Value |
20856 |
Grouped |
|
Encapsulates accumulated usage or resource consumption data. It provides a structured way to represent and transfer cumulative metrics using subordinate AVPs. Specifically, this AVP contains the CumValue-Digits AVP, which holds the numerical value of the accumulated amount. The AVP structure is defined as follows: CumValue-Digits: specifies the accumulated value. |
|||
Cum-Value-Digits |
20857 |
Integer64 |
|
Used to represent the integer part of an accumulated consumption amount. It is part of grouped AVPs, such as Cum-Unit-Value, that report cumulative metrics for subscribers or services. |
|||
Current-Account-Balance |
20350 |
Integer64 |
|
Represents the current monetary or resource balance of a subscriber's account. It is primarily used in charging and billing applications to track and manage real-time account balances in telecom systems. This AVP is a component of Account-Change-Info AVP. |
|||
Current-Account-Balance |
30322 |
Integer64 |
|
Indicates the current balance of a subscriber's account, expressed as a signed 64-bit integer. This implementation is distinct from other Current-Account-Balance AVP (20350). This AVP is a component of Account-Change-Info AVP. |
|||
Current-Balance |
60006 |
Integer64 |
|
Provides the current balance of an account. For postpaid subscribers, the value represents the unsettled balance, excluding the settled amounts. It is commonly used in real-time charging systems to manage financial transactions and account states for both prepaid and postpaid users. |
|||
Cycle-End-Time |
30342 |
OctetString |
|
Represents the end time of a billing or charging cycle. It can be used to define the termination point of an accounting cycle, such as monthly billing periods, subscription terms, or predefined time limits for a specific service or usage plan. |
|||
Cycle-Start-Time |
30341 |
OctetString |
|
Specifies the start time of a billing or charging cycle. |
|||
DCS (Data Coding Scheme) |
20436 |
Unsigned32 |
|
Indicates the type of encoding used for a message reported by the SMPP+ protocol. It helps to identify the character set and data encoding format applied to a message, ensuring proper interpretation and delivery across communication networks. The value is typically an Unsigned32 integer that corresponds to specific encoding schemes defined by the messaging standards. The DCS AVP typically follows the standard SMPP Data Coding Scheme values, which include: 0: SMSC Default Alphabet 4: 8-bit Binary Encoding 8: UCS2 (16-bit Unicode) Encoding 245: Reserved for SMPP+ Custom Encoding |
|||
Dealer-Code |
20791 |
OctetString |
|
Identifies a specific dealer associated with certain operational or business transactions within the system. This code differentiates dealers and ensures that they can only interact with designated MVNOs (Mobile Virtual Network Operators), providing a controlled and secure operational environment. |
|||
Dest-Addr |
20407 |
UTF8String |
|
Represents the destination address or number of the message or transaction receiver. This AVP is typically used in scenarios where a specific recipient's information needs to be included in a Diameter message, enabling targeted communication or service delivery. |
|||
Dest-IMSI |
20435 |
UTF8String |
|
Indicates the IMSI (International Mobile Subscriber Identity) of the called number as reported in an SMPP+ message. |
|||
Disable-Period |
20735 |
OctetString |
|
Used to represent the disable stop date in a Diameter-based credit control context. |
|||
Diversion-Count |
20822 |
Unsigned32 |
|
Represents the total count of diversions or call forwards in a Diameter-based credit control scenario. |
|||
Diversion-Reason |
20821 |
Enumerated |
|
Indicates the specific reason for a call being forwarded. It helps define the context or trigger for call forwarding behavior. Values: 0: UNKNOWN 1: Call Forwarding Unconditional (CFU) 2: Call Forwarding Busy (CFB) 3: Call Forwarding No Reply (CFNR) 4: Call Forwarding Offline (CFNL) 5: Call Forwarding Deflection Alerting Response 6: Call Forwarding Deflection Immediate Response 7: Call Forwarding on User Not Reachable (CFNRC) 8-14: Call Forwarding (CF) to Mailbox, differentiated by condition 15: Call Forwarding by Time (CFTB) 16: Call Forwarding by Subscriber (CFSB) 17: Call Forwarding Do Not Disturb (DND) to Mailbox 18: Call Forwarding No Reply in Call Wait (CW) 19: Call Forwarding Selective (CFS) 20: Anonymous Call Rejection (ACR) to Mailbox 100-103: Caller/Called Call Transfer, including Call Wait scenarios 104: Call Forwarding Private Branch Exchange Queued 105: Call Forwarding Synchronous Ring 255: Call Forwarding Butt Call Others: Reserved for future use. |
|||
Dst |
20618 |
UTF8String |
|
Used in Diameter-based credit control scenarios to indicate the number of the sender. |
|||
Error-Type |
20744 |
Unsigned32 |
|
Used to represent a recharge error code credit control scenarios. |
|||
Etopup-Session-ID |
20740 |
UTF8String |
|
Used to uniquely identify an E-topup transaction in Diameter-based credit control scenarios. This AVP ensures proper tracking and reconciliation of recharge sessions. Facilitates accurate account synchronization when the Unified Voucher Center (UVC) is directly connected to the Charging and Billing Platform (CBP) for recharge operations. |
|||
Event-Type |
22004 |
UTF8String |
|
Used to represent the type or category of an event, supporting Huawei-specific use cases that involve custom event types for billing, analytics, or monitoring purposes. |
|||
Ex-Parameter-1 |
30312 |
UTF8String |
|
Ex-Parameter-2 |
30313 |
UTF8String |
|
Ex-Parameter-3 |
30314 |
UTF8String |
|
Ex-Parameter-4 |
30315 |
UTF8String |
|
Ex-Parameter-5 |
30316 |
UTF8String |
|
Ex-Parameter-6 |
30317 |
UTF8String |
|
Ex-Parameter-7 |
30318 |
UTF8String |
|
Ex-Parameter-8 |
30319 |
UTF8String |
|
Ex-Parameter-9 |
30320 |
UTF8String |
|
Ex-Parameter-10 |
30321 |
UTF8String |
|
Used to transmit common attribute fields in the recharge Unified Voucher Center (UVC) scheme. It serves as part of a sequence of AVPs (ExParameter1 through ExParameter10) to support extended key-value pair attributes when their combined length exceeds the limit of earlier AVPs. |
|||
Expire-Time |
30333 |
OctetString |
|
Used to represent a timestamp or duration indicating when a particular session, service, or resource allocation is set to expire. |
|||
Ex-Trans-Type |
21400 |
UTF8String |
|
Used to specify the recharge channel when the WebService interface is utilized for voucher recharge operations. |
|||
Fav-Area-Flag |
20917 |
Unsigned32 |
|
Used to indicate whether a subscriber is currently located in a predefined "favorite area." Values: 0: The subscriber is not in a favorite area. 1: The subscriber is in a favorite area. |
|||
Fav-Cell-Id-Flag |
20361 |
Enumerated |
|
Used to indicate whether a subscriber is located within a preferential cell or zone, such as a HomeZone or SpecialZone. Values: 0: Not in any preferential cell. 1: In the system-level preferential cell. 2: In the user-level preferential cell. 3: In both the user-level HomeZone and the system-level SpecialZone. |
|||
FeeAddress |
20408 |
UTF8String |
|
Used to represent the number of the sender responsible for charging in credit control scenarios. |
|||
Fee-Fixed |
20413 |
Unsigned32 |
|
Used to indicate the charge rate for each short message in a monthly SMS package with a limited number of included short messages. When the number of short messages exceeds the predefined limit, additional messages are charged individually. |
|||
Fee-Flag |
20409 |
Unsigned32 |
|
Used to indicate the charging flag, defining which entity is responsible for the charges in a Diameter-based credit control scenario. Values: 0: Charge in the original mode (processed as an exception). 1: Charge the calling number. 2: Charge the called number. 3: Charge the charging number. |
|||
Fee-Msg-Num |
20411 |
Unsigned32 |
|
Used to indicate the number of messages included in a charging context within Diameter-based credit control systems. This AVP supports billing scenarios where charges are calculated based on the quantity of messages. |
|||
Fee-Single |
20412 |
Unsigned32 |
|
Used to indicate the charge rate for a single short message. This AVP applies to scenarios where service providers (SPs) charge subscribers on a per-message basis. |
|||
Fee-Type |
20410 |
Unsigned32 |
|
Used to indicate the charging type for SMS services. It provides flexibility in defining the billing model, supporting various subscription and pay-per-use options. This AVP is integral to Huawei systems for implementing advanced charging strategies for SMS services. Values: 0: Charge by default mode. 1: Charge by item (pay-per-use). 2: Charge by month (with authentication and fee deduction). 3: Charge by month (with authentication but no fee deduction). 4: Charge upper limit amount based on the number of SMSs. 5: Charge by month with a limited number of SMSs (with authentication and fee deduction). 6: Charge by month with a limited number of SMSs (with authentication but no fee deduction). |
|||
Fix-Rent-Fee |
21108 |
Unsigned32 |
|
Used to represent a management fee or a fixed rental fee. This AVP is primarily employed in scenarios where a consistent fee is applied periodically for service management or subscription purposes. |
|||
Fraud-Times |
20390 |
Unsigned32 |
|
Used to indicate the number of incorrect password attempts made with a voucher card. |
|||
Function-Flag |
20770 |
UTF8String |
|
Used to convey charging-related flags and additional reserved data in Diameter Credit-Control-Request (CCR) and Credit-Control-Answer (CCA) messages. |
|||
Grace-Period |
20734 |
OctetString |
|
Used to indicate the suspend stop date for a service or account. |
|||
HandleOver-Toolbox-Flag |
21011 |
Integer32 |
|
Used to indicate whether a transaction or process should be handed over to the Toolbox system. Values: 0: No, do not hand over to the Toolbox system. 1: Yes, hand over to the Toolbox system. |
|||
I-Brand-ID |
21198 |
Integer32 |
|
Used to represent the brand ID associated with a subscriber. |
|||
IDD-Originate-Number |
21119 |
OctetString |
|
Used to report the calling number in Diameter-based scenarios. |
|||
I-First-Call-Flag |
30050 |
UTF8String |
|
Used to indicate whether a given call is the subscriber's first call. This AVP helps in scenarios where the system behavior or charging policy is influenced by whether the call is the first interaction of its kind. Values: 0: Yes, this is the first call. - the Resource Broker (RB) updates the attribute and returns it to the Operations and Maintenance (OM) system. 1: No, this is not the first call. - by default, the RB sets this value to 1 and does not update it for subsequent calls. |
|||
I-Language-Type |
21194 |
Integer32 |
|
Used to indicate the language preference of a subscriber. |
|||
IMS-Information |
876 |
Grouped |
|
Used to encapsulate detailed information related to the IP Multimedia Subsystem (IMS). The AVP structure is defined as follows: Event-Type: Specifies the type of event related to the IMS session. Message-Body: Contains the body of the message related to the IMS session. Role-of-Node: Identifies the role of the node in the IMS session (e.g., originating or terminating). User-Session-Id: Represents the user session identifier. Calling-Party-Address: Specifies the address of the calling party. Called-Party-Address: Specifies the address of the called party. Time-Stamps: Contains time-related information for the session. Inter-Operator-Identifier: Provides identifiers for inter-operator communication. IMS-Charging-Identifier: Specifies the charging identifier for IMS sessions. SDP-Session-Description (optional, multiple): Contains session description protocol details. SDP-Media-Component (optional, multiple): Specifies media components within the SDP. SDP-Media-Identifier: Identifies media components within the session. Diversion-Reason: Indicates the reason for call diversion. Requested-Party-Address: Specifies the address of the requested party. UUS-Data: Contains user-to-user signaling data. Cause: Provides cause codes for session-related events. Service-ID: Identifies the service being used. Service-Specific-Data: Includes data specific to the service. |
|||
INAPCS1-Tariff-Class |
30383 |
UTF8String |
|
Used to represent the tariff class in the INAP CS1 (Intelligent Network Application Protocol Capability Set 1) context. |
|||
IN-Information |
20300 |
Grouped |
|
Used to carry comprehensive intelligent network (IN) information in Huawei Diameter systems. The AVP structure is defined as follows: Active-Flag: Indicates whether the session or subscriber is active. Calling-VLR-Number: Provides the Visitor Location Register (VLR) number of the calling party. Calling-MSC-Address: Specifies the Mobile Switching Center (MSC) address for the calling party. Calling-CellID-Or-SAI: Identifies the calling cell or Service Area Identifier (SAI). Access-Method: Specifies the method of access used for the session. Auth-Information: Contains authentication data for the session. BalanceInfo (Multiple): Provides details about the account balance. Calling-Party-Address: Specifies the address of the calling party. Called-Party-Address: Specifies the address of the called party. Called-Short-Number: Includes a short number for the called party. Specific-Output: Specifies session-specific output data. Calling-Partys-Category: Categorizes the calling party. Calling-Party-Address-Nature: Indicates the nature of the calling party’s address. Called-Party-Address-Nature: Indicates the nature of the called party’s address. Calling-LAI: Provides the Location Area Identifier (LAI) for the calling party. Called-VLR-Number: Specifies the VLR number of the called party. Called-CellID-Or-SAI: Identifies the called cell or SAI. Called-IMEI: Includes the International Mobile Equipment Identity (IMEI) of the called party. Calling-IMEI: Includes the IMEI of the calling party. Additional-Calling-Party-Number: Provides an additional number for the calling party. Redirecting-Party-ID: Identifies the redirecting party. Redirection-Reason: Specifies the reason for call redirection. MSCAddress: Contains the address of the MSC. Time-Zone: Indicates the time zone of the session. Access-Network-Type: Specifies the type of access network. Service-Key: Includes the key for the specific service being used. Call-Forward-Indicator: Indicates whether the call has been forwarded. UE-IMSI: Contains the International Mobile Subscriber Identity (IMSI) of the user equipment. Original-Called-Party-ID: Specifies the originally called party’s identifier. Call-Reference-Number: Provides a reference number for the call. Route-Prefix: Includes the routing prefix for the session. SSP-Time: Indicates the Service Switching Point (SSP) time. Charge-Flow-Type: Specifies the type of charging flow. Bearer-Capability: Provides bearer capabilities for the session. Calling-Location-Number-Nature: Indicates the nature of the calling location number. Called-Party-BCDNumber-Nature: Specifies the nature of the called party’s Binary Coded Decimal (BCD) number. Called-Location-Number: Includes the location number of the called party. Called-Location-Number-Nature: Indicates the nature of the called location number. Original-Called-Party-ID-Nature: Specifies the nature of the originally called party ID. Reroute-Called-Number: Provides the rerouted called number. FunctionFlag: Indicates flags related to session functionality. VPNCall-Auth-Flag: Specifies whether the call is authenticated for a Virtual Private Network (VPN). PersonalPayNotifyMode: Includes notification mode for personal payment scenarios. UserPassWd: Contains the user’s password for authentication. IDD-Originate-Number: Specifies the originating number for international dialing. Address-Of-Restricted-Indicator: Indicates whether the address is restricted. Connect-Called-Number: Specifies the connected called number. Calling-Location-Number: Includes the calling location number. Called-Msc-Address: Specifies the MSC address for the called party. Redirecting-Party-ID-Nature: Indicates the nature of the redirecting party ID. Real-Called-Number: Provides the real called number. Called-Party-BCDNumber: Includes the called party’s BCD number. Original-Redirecting-Party-ID: Specifies the ID of the originally redirecting party. New-SSP-Time: Indicates a new SSP time for the session. INAPCS1-Tariff-Class: Includes tariff class information for INAP CS1. Called-LAI: Provides the LAI for the called party. KeepVoiceFlag: Indicates whether voice services are kept active. Service-Parameter-Info (Multiple): Includes additional service parameters. Alert-Level: Specifies the alert level for the session. GracePeriod: Indicates the grace period for session activities. DisablePeriod: Specifies the disable period for services. Call-Type: Indicates the type of call. VPNNotifyFlag: Includes notification flags for VPN scenarios. FavAreaFlag: Indicates whether the session is in a favorite area. SameCUGNotFreeNotifyFlag: Specifies notification flags for Closed User Group (CUG) scenarios. PersonalPayCostValue: Includes cost values for personal payments. ActiveCurrencyCode: Specifies the active currency code. SuspendReason: Provides the reason for service suspension. ChargePartyType: Specifies the type of charging party. Credit-Use-Notification: Includes credit use notifications. User-Basic-Info: Provides basic user information. Community-Information: Includes community-related details. Subscriber-Pay-Type: Specifies the type of payment for the subscriber. ActivePeriod: Indicates the active period for the session. Announcement-Data: Provides data for announcements. Notice-Information (Multiple): Includes notification-related information. ShareCallPercent: Specifies the percentage for call sharing scenarios. Service-Free-Indicator: Indicates whether the service is free. HandleOver-Toolbox-Flag: Indicates whether the session is handled over to a toolbox system. Call-Begin-Time: Specifies the start time of the call. Adjust-Roaming-Type: Includes roaming type adjustments. Total-Cost-Flag: Indicates whether total cost tracking is enabled. Release-Reason: Specifies the reason for call release. AccountInfo: Provides account-related information. Called-Party-NP: Includes Number Portability details for the called party. Calling-Party-NP: Includes Number Portability details for the calling party. FavCellIdFlag: Indicates whether the session is in a favorite cell. Recharge-Information: Provides information about recharge actions. ActiveMethod: Specifies the active method for the session. OperatorID: Includes the operator identifier. Account-Query-Method: Specifies the method for account querying. Account-Type: Indicates the type of account. CC-Money: Provides monetary charging details. Fix-Rent-Fee: Includes fixed rental fees. Next-Bill-DateTime: Specifies the date and time for the next billing event. Amount-Before-Recharge: Indicates the amount before recharge. RchgExtActKey: Includes recharge extension action keys. Account-Change-Info: Provides details about account changes. CumInfo: Contains cumulative information for the session. ParentLimitValue: Specifies parent limit values. AdditionalInfo: Provides additional session information. ChargeConfirmFlag: Indicates flags related to charge confirmation. MainProductID: Specifies the main product ID associated with the session. IVRLang: Indicates the IVR language preference. SMSLang: Specifies the SMS language preference. PayType: Includes payment type details. Brand: Specifies the brand associated with the session. ActivationDate: Indicates the activation date for services. ManagementState: Provides the management state of the session. State: Specifies the state of the session or subscriber. PPSBalance: Provides prepaid balance information. POSBalance: Provides postpaid balance information. |
|||
I-Saas-Tenant-ID |
30049 |
Integer32 |
|
Used to indicate the tenant ID in a Software as a Service (SaaS) scenario. |
|||
I-SMS-Language-Type |
21195 |
Integer32 |
|
Used to indicate the SMS language preference of a subscriber. |
|||
I-Sub-COSID |
21191 |
Integer32 |
|
Represents the primary offering or Class of Service (COS) identifier for a subscriber. This AVP is used to associate subscribers with a specific service package or class. |
|||
I-Tenant-ID |
21193 |
Integer32 |
|
Indicates the unique tenant ID to which a subscriber belongs. It supports multi-tenant environments, enabling tenant-specific service provisioning and management. |
|||
I-User-Type |
21192 |
Integer32 |
|
Indicates the type of subscriber. This AVP is used to classify subscribers based on their billing and payment method. Values: 1: Prepaid subscriber 2: Postpaid subscriber 3: Hybrid subscriber |
|||
IVR-Lang |
30811 |
Unsigned32 |
|
Represents the preferred language for Interactive Voice Response (IVR) services. |
|||
Keep-Voice-Flag |
30017 |
Unsigned32 |
|
Indicates whether the calling party is actively connected in the call. |
|||
Lifecycle-State |
20772 |
Unsigned32 |
|
Indicates the life cycle state of a prepaid subscriber. It provides information about the subscriber's account status, enabling effective subscriber management. Values: 1: Idle – The subscriber account is inactive but not barred or suspended. 2: Active – The subscriber account is active and operational. 3: Barred – The subscriber is barred from services due to specific conditions (e.g., fraud or policy violations). 4: Suspended – The subscriber account is temporarily suspended, possibly for non-payment. 5: Pool – The subscriber account is in a pool of inactive accounts awaiting reactivation or other operations. |
|||
Main-Product-ID |
30816 |
Unsigned32 |
|
Identifies the primary product associated with a subscriber. Values: 1: One Card 2: Two Card |
|||
Main-Product-Key |
20794 |
Integer32 |
|
Represents a brand identifier for the subscriber’s main product. It is used to associate subscribers with specific branding, such as Blue, xPay, or Sukses. |
|||
Management-State |
30823 |
UTF8String |
|
Provides the subscriber's management status. |
|||
Measure-Type |
20353 |
Integer32 |
|
Specifies the type of measurement associated with a balance or resource in a subscriber's account. When Balance-Type AVP is 0 or 1, the value of Measure-Type is fixed to 4. When Balance-Type AVP is 2, it indicates a Measure-Type. Values: 1: Time 2: Bytes 3: Items 4: Money 5: Times 6: Pages |
|||
Member-Screen-Class |
30406 |
UTF8String |
|
Indicates the screening class of a member. This AVP is used to define specific categories or classifications for members based on screening rules. |
|||
Merchant-ID |
22008 |
UTF8String |
|
Used to identify a merchant in various service contexts. It supports systems that involve transactions, purchases, or other interactions requiring merchant identification. |
|||
Message-Content-1 |
20396 |
UTF8String |
|
Message-Content-2 |
20397 |
UTF8String |
|
Message-Content-3 |
20398 |
UTF8String |
|
Message-Content-4 |
20399 |
UTF8String |
|
Message-Content-5 |
20700 |
UTF8String |
|
Message-Content-6 |
20701 |
UTF8String |
|
Used to transmit parts of a message payload, allowing for multi-part messaging functionality. Each AVP contains up to 140 English characters, with a total length of up to 256 bytes for UTF8 encoding. When a message exceeds 140 characters, it is split across multiple AVPs, such as Message-Content-1 and Message-Content-2, with each AVP carrying a portion of the message content. |
|||
Message-Count |
20395 |
Unsigned32 |
|
Indicates the number of message parts sent as part of a notification. This AVP is used in conjunction with Message-Content-X AVPs to manage multi-part message transmission. |
|||
Message-PID |
20414 |
Unsigned32 |
|
Represents the Protocol Identifier (PID) of a message, which defines the type or nature of the message content, such as sound or image. |
|||
MO-MSC-Addr |
20404 |
UTF8String |
|
Represents the Mobile Switching Center (MSC) address in the roaming area of the message sender. |
|||
Money-Value |
20328 |
Integer64 |
|
Indicates the monetary value associated with a transaction or service. |
|||
MSC-Address |
20322 |
UTF8String |
|
Represents the address of the Mobile Switching Center (MSC). |
|||
Msg-Send-Result |
20803 |
Enumerated |
|
Indicates the result of a message transmission. It is used to notify whether a message was sent successfully or if it failed. Values: 0: The message failed to send. 1: The message was sent successfully. |
|||
Msg-Seq |
20802 |
UTF8String |
|
Represents the message sequence number. |
|||
M-Stat |
20620 |
Integer32 |
|
Indicates the status of service processing. It is used to report whether a service operation was successful or encountered a failure. Values: 0: Success 1: Failure |
|||
MT-MSC-Addr |
20405 |
UTF8String |
|
Represents the Mobile Switching Center (MSC) address associated with the roaming area of the message receiver. |
|||
Need-Cnfm |
20606 |
Integer32 |
|
Indicates whether the associated information requires confirmation. Possible values in a CCR (Credit-Control Request) message: 0: Information does not need confirmation. 1: Information needs confirmation. -1: Default value; the Online Charging System (OCS) determines whether confirmation is required. Corresponding values in a CCA (Credit-Control Answer) message depend on the value in the CCR and the OCS configuration: 0: No confirmation required. 1: Confirmation required. |
|||
New-Active-Stop |
20745 |
UTF8String |
|
Indicates the validity period of a subscriber's account before a recharge. |
|||
New-Card-Money |
22994 |
Integer64 |
|
Represents the monetary value of a voucher card. |
|||
New-Money |
22995 |
Integer64 |
|
Specifies the amount of money involved in a transaction. |
|||
New-SSP-Time |
22992 |
Time |
|
Represents the specific time when SSP (Service Switching Point) reporting occurs. This AVP is used for timing and synchronization of SSP reports, typically in contexts where precise timestamping is necessary for network operations or billing. |
|||
New-User-State |
20748 |
UTF8String |
|
Provides information about the user state of a subscriber before a recharge. |
|||
Next-Bill-Date |
21186 |
OctetString |
|
Specifies the start date of the next billing cycle for a subscriber. |
|||
Next-Bill-DateTime |
21109 |
OctetString |
|
Provides the exact date and time of the next monthly settlement. The value is represented in a precise format (YYYYMMDDHHMMSS). |
|||
Node-Id |
2064 |
UTF8String |
10415 (3GPP) |
Contains an optional, operator-configurable identifier string for the node. |
|||
Notice-Information |
20394 |
Grouped |
2011 (Huawei) |
Used to deliver Short Message (SM) notification information assembled by the Online Charging System (OCS). The OCS is responsible for preparing the SM notification, ensuring it is complete and in the correct order, so that third-party systems, such as Value-added Service Control Points (VSCPs), can forward it directly to the SMSC without further processing. The AVP structure is defined as follows: MessageCount: Indicates the number of messages in the notification. MessageContent1 to MessageContent6: Content of the message in the notification (from 1 to 6). ReceiveMessageAddr: The recipient address for the message notification. |
|||
Notify-Mode |
20431 |
Integer32 |
|
Specifies the notification mode used by the Short Message Service Center (SMSC) for sending charging notifications to the Online Charging Gateway (OCG). The notification mode dictates the conditions under which notifications are sent, enabling flexibility based on the success or failure of message delivery. Values: 1: The SMSC sends a charging notification to the OCG regardless of delivery success. 2: The SMSC sends a charging notification to the OCG only if the Short Message (SM) fails to be delivered. 3: The SMSC sends a charging notification to the OCG only if the SM is successfully delivered. 4: The SMSC does not send a charging notification to the OCG regardless of delivery success. |
|||
Old-Active-Stop |
20746 |
UTF8String |
|
Indicates the validity period of a subscriber after a recharge has been completed. This value helps track the active status duration for a subscriber following a recharge operation. |
|||
Old-User-State |
20747 |
UTF8String |
|
Specifies the state of a subscriber after a recharge has been applied. This AVP helps identify the post-recharge status of a user in the system. |
|||
Operation-Description |
30327 |
UTF8String |
|
Provides a textual description of an operation. It allows log details of the operation being executed within a Diameter transaction. |
|||
Operation-Result |
20430 |
Integer32 |
|
Indicates the outcome of a specific operation within a Diameter session or transaction. It conveys whether the operation was successful, failed, or resulted in another defined state. Values: 0: Success 1: Failure Other values may define specific failure states or informational results. |
|||
Operator-ID |
20739 |
UTF8String |
|
Identifies the operator responsible for initiating a specific request. It is typically used in scenarios such as manual recharge and transaction logging. The operator's ID is recorded in Call Detail Records (CDRs) for auditing and tracking purposes. In balance transfer operations, this AVP can be utilized to record the transaction sequence number generated by the Online Charging Gateway (OCG). |
|||
Orig-IMSI |
20434 |
UTF8String |
|
Indicates the International Mobile Subscriber Identity (IMSI) of the calling party. It is specifically used in scenarios involving Short Message Peer-to-Peer (SMPP+) messages. This AVP is critical when implementing number portability schemes based on Fake-IMSI, ensuring accurate identification and routing of the calling subscriber's message. |
|||
Original-Called-Party-Id |
20310 |
UTF8String |
|
Represents the originally dialed number in a call forwarding scenario. This AVP helps trace the call routing back to the initial intended recipient before any forwarding actions occurred. Number Formats Supported: Mobile:
PSTN (Public Switched Telephone Network):
This AVP excludes any IP prefixes, making it applicable for GSM/UMTS/LTE voice and SMS traffic. |
|||
Original-Called-Party-Id-Nature |
21166 |
Unsigned32 |
|
Specifies the type or "nature" of the original called number, aiding in routing decisions and billing classifications. Values: 0: Spare 1: Subscriber number (National service) 2: Unknown number (National service) 3: National number 4: International number |
|||
Original-Credit |
30343 |
Integer64 |
|
Represent the initial credit amount associated with a particular session or transaction in monetary terms. |
|||
Original-Group |
20416 |
Unsigned32 |
|
Used to represent the identifier of a group to which the user or session originally belongs. |
|||
Original-Message-ID |
20421 |
Unsigned32 |
|
Used to identify the ID of a previously transmitted message. This AVP is typically used in message retransmission, correlation, or tracking scenarios, where the system needs to reference a specific message. |
|||
Original-Party-Number |
20792 |
OctetString |
|
Used to represent the identifier of the original party in a communication session. It may include details such as the phone number, IMSI, or other identifiers of the party that initiated or is being referenced in the session. |
|||
Original-Redirecting-Party-Id |
20668 |
UTF8String |
|
Represents the original "forwarded-to" number in scenarios where calls or messages are redirected. This AVP is typically reported by the SSP (Service Switching Point) to retain information about the redirection chain or initial forwarding target. |
|||
P2PSMS-Information |
20400 |
Grouped |
|
Containing detailed information about point-to-point short message (SMS) operations. It includes metadata and processing attributes for SMS transactions, providing a structured way to encapsulate and transmit SMS-related details. The AVP structure is defined as follows: Sms-Type: Indicates the type of SMS (e.g., normal, flash). SMSC-Address: Represents the address of the Short Message Service Center (SMSC). SM-Id: Unique identifier for the SMS. SM-Length: Length of the SMS content in characters or bytes. MO-MSC-Addr: Address of the MSC in the originating region for the SMS. MT-MSC-Addr: Address of the MSC in the terminating region for the SMS. Source-Address: Address of the message sender. Dest-Address: Address of the message recipient. Fee-Flag: Indicates the charging flag (e.g., who pays for the SMS). Fee-Type: Represents the charging type (e.g., per message, per byte). Message-PID: Protocol identifier for the message, indicating the type of content (e.g., text, image). Status-Report-Request: Indicates whether a delivery status report is requested for the SMS. Orig-IMSI: IMSI of the originating subscriber. Dest-IMSI: IMSI of the destination subscriber. Calling-IMEI: IMEI of the calling party’s device. Called-IMEI: IMEI of the called party’s device. Send-Result: Outcome of the SMS delivery (e.g., success, failure). Data-Coding-Scheme (DCS): Coding scheme used for the SMS content (e.g., GSM 7-bit, UCS2). V-MCC-MNC-Addr: Represents the visited network's MCC (Mobile Country Code) and MNC (Mobile Network Code). Original-Called-Party-Id: Original recipient's number before forwarding. Notify-Mode: Notification mode for delivery status (e.g., notify on success/failure). Operation-Result: Indicates the result of an operation related to the SMS (e.g., success, error). |
|||
Parent-Limit-Value |
21220 |
Integer64 |
|
Specifies the payment limit set by a parent card subscriber for a special child card subscriber during the balance query process. If multiple payment limits exist, only one is returned. If no payment limit exists, the value is set to 0. |
|||
Payment-Type |
60002 |
Integer32 |
|
Indicates whether a subscriber is using a prepaid or postpaid billing model. Values: 0: Prepaid 1: Postpaid |
|||
Pay-Type |
30813 |
Unsigned32 |
|
Specifies the payment method used by the subscriber. |
|||
Personal-Pay-Cost-Value |
30016 |
Integer64 |
|
Indicates the amount of an individual's payment. |
|||
Personal-Pay-Notify-Mode |
30015 |
UTF8String |
|
Specifies how the system notifies a subscriber about their individual payment mode. Notifications can occur before or after a call, and the AVP encodes different modes of notification for various scenarios. The first digit and second digit represent the following: First Digit: Pre-call notification (via IVR): 0: No notification 1: Notify only once 2: Notify every time Second Digit: Post-call notification (via USSD): 0: No notification 1: Notify only once 2: Notify every time Other digits: Reserved for future use. |
|||
POS-Account-Notify |
21182 |
Grouped |
|
Provides grouped information about the subscriber's Point of Sale (POS) account status and notifications. It includes details such as notification mode, used credit, maximum allowed credit, and the next billing date. The AVP structure is defined as follows: POS-Notify-Mode: Specifies the notification mode for POS-related updates. Possible values are implementation-specific. POS-Used-Credit: Indicates the amount of credit already used by the subscriber at the POS. POS-Max-Credit: Specifies the maximum credit limit available to the subscriber at the POS. Next-Bill-Date: Indicates the start date of the next billing cycle. The date is encoded as a string. |
|||
POS-Balance |
30822 |
Integer64 |
|
Represents the current balance of a post-paid subscriber's account. |
|||
POS-Max-Credit |
21185 |
Integer64 |
|
Specifies the maximum allowable credit for a subscriber's account in a post-paid billing system. |
|||
POS-Notify-Mode |
21183 |
Integer32 |
|
Defines the notification preferences for post-paid account credit usage. It specifies the conditions under which a subscriber or system will receive notifications related to credit consumption. Options: 1: Notification is sent when a certain predefined credit threshold is used. 2: Notification is sent when the available credit is fully utilized. |
|||
POS-Used-Credit |
21184 |
Integer64 |
|
Indicates the total amount of credit that has been consumed by a subscriber in a post-paid billing account. |
|||
PPS-Account-Notify |
21177 |
Grouped |
|
Provides details about the status of a pre-paid subscriber's account. It is a grouped AVP that encapsulates multiple related AVPs to deliver comprehensive account notification information. The AVP structure is defined as follows: PPS-Notify-Mode: Specifies the mode of notification regarding the account status or credit usage. PPS-Used-Credit: Indicates the amount of credit already used by the subscriber. PPS-Max-Credit: Specifies the maximum allowable credit for the subscriber. Validity-Date-2: Indicates the expiration date of the subscriber’s account or credit validity. |
|||
PPS-Balance |
30821 |
Integer64 |
|
Represents the current balance of a pre-paid subscriber's account. |
|||
PPS-Max-Credit |
21180 |
Integer64 |
|
Specifies the maximum allowable credit limit for a pre-paid subscriber's account. |
|||
PPS-Notify-Mode |
21178 |
Integer32 |
|
Indicates the notification preferences for pre-paid subscribers. It specifies the conditions under which a notification should be triggered regarding the subscriber's account status. Options: 1: Notify when a certain amount of credit is used. 2: Notify when the entire credit balance is used up. |
|||
PPS-Used-Credit |
21179 |
Integer64 |
|
Provides the amount of credit that has already been consumed from a pre-paid subscriber's balance. |
|||
Premium-SMS-Flag |
30127 |
Enumerated |
|
Indicates whether a sent SMS qualifies as a premium service. Premium SMS messages often incur higher charges and are associated with value-added services. Values: 1: the system identifies the SMS as a premium message and applies the appropriate charge. 0: the message is treated as a standard SMS with regular rates. |
|||
Provisition-ID |
20681 |
UTF8String |
|
Utilized in content-based charging services to uniquely identify the provision associated with a service or content being charged. |
|||
Provisition-Type |
20682 |
Unsigned32 |
|
Specifies the type of content or service associated with a provision in content-based charging. Values: 151: Full Track Online Play 152: Full Track Download 153: Color Ring 154: Ring Tone Download 155: Game Download 156: Application Download 157: Application Online Play 158: Video Online Play 159: Video Download 160: Theme Download 161: Audio Download 162: Picture Download 163: Text Download 164: Widget Download |
|||
PS-Information |
874 |
Grouped |
|
Provides detailed information about packet-switched (PS) services, primarily used for volume-based charging and QoS management. The AVP structure is defined as follows: 3GPP-Charging-Id: Identifies the charging session for PS services. 3GPP-PDP-Type: Specifies the PDP (Packet Data Protocol) type (e.g., IPv4, IPv6). PDP-Address: Address associated with the PDP context. QoS: Quality of Service parameters. SGSN-Address: Address of the Serving GPRS Support Node. GGSN-Address: Address of the Gateway GPRS Support Node. CG-Address: Charging Gateway address. 3GPP-IMSI-MCC-MNC: Mobile Country Code and Mobile Network Code associated with the IMSI. 3GPP-GGSN-MCC-MNC: MCC and MNC of the GGSN. 3GPP-NSAPI: Network Service Access Point Identifier. 3GPP-Session-Stop-Indicator: Indicates whether the session is stopped. 3GPP-Selection-Mode: Mode of selection for the PDP context. 3GPP-Charging-Characteristics: Charging characteristics for the session. 3GPP-SGSN-MCC-MNC: MCC and MNC of the SGSN. 3GPP-MS-TimeZone: Time zone of the mobile station. 3GPP-CAMEL-Charging-Info: CAMEL-related charging information. Charging-Rule-Base-Name: Name of the charging rule base applied. 3GPP-User-Location-Info: Location information of the user. 3GPP-RAT-Type: Radio Access Technology type (e.g., LTE, UMTS). PS-Furnish-Charging-Information: Charging information specific to PS services. PDP-Context-Type: Type of PDP context. SP-Id: Service provider identifier. Service-Id: Unique identifier for the service. Service-Type: Type of service being provided. Content-Id: Identifier for the content being accessed. BearerType: Type of bearer service. StartTime: Start time of the PS session. StopTime: Stop time of the PS session. BearerProtocolType: Protocol type for the bearer. ChargingID: Identifier used for billing and session tracking. ServiceLevel: Level of service provided. Message-Id: Unique identifier for the message. |
|||
Purpose-Id |
30357 |
UTF8String |
|
Used to identify the specific purpose or intent associated with a session, transaction, or request. |
|||
Query-End-Time |
20742 |
Time |
|
Specifies the endpoint of a time range for querying recharge logs. |
|||
Query-Start-Time |
20741 |
Time |
|
Defines the beginning of a time range for querying recharge logs. |
|||
Rchg-Ext-Act-Key |
20812 |
Unsigned32 |
|
Used to indicate an extended recharge action that can be executed by an external system. For example, it might specify actions such as switching the subscriber's sub-brand. |
|||
Real-Called-Number |
20327 |
UTF8String |
|
Represents the actual, fully-translated telephone number that was called. If a user dials a short or abbreviated number (e.g., a shortcode), this AVP captures the corresponding full-length number used for routing the call. |
|||
Receive-Message-Addr |
20732 |
UTF8String |
|
Specifies the destination address of a short message (SM) receiving party. While this AVP is typically not used (defaulting to NULL), it may be employed in scenarios requiring explicit definition of the destination address. |
|||
Recharge-Card-Type |
20790 |
Enumerated |
|
Identifies the type of recharge card used in a transaction. This information helps distinguish between various dealer or card types and is integral to billing, processing, and reporting systems. Values: 2: Airtime Card 3: Network Card |
|||
Recharge-Information |
20341 |
Grouped |
|
Provides comprehensive details about a recharge transaction. It is a grouped AVP that includes various sub-AVPs related to the recharge process, such as card number, charge number, money values, and additional parameters for tracking and processing the recharge. The AVP structure is defined as follows: Charge-Number: The number associated with the charge (typically the phone number or account number receiving the recharge). Card-Number: The number of the card being used for the recharge. Card-Batch: A batch identifier for cards. Card-Type: The type of card (e.g., prepaid, postpaid). Card-Money: The value of the card. Charge-Money: The monetary amount being charged. CardSpID: The ID of the service provider associated with the card. CardBrandID: The ID of the card brand. CardCurDistributorID: The ID of the card's current distributor. FraudTimes: The number of fraudulent attempts. SerialNo: The serial number of the card or transaction. UniformSerialNo: The uniform serial number for identification. Recharge-Method: The method used to perform the recharge (e.g., USSD, IVR, etc.). Etopup-SessionID: An identifier for the e-topup session. Account-Type: The type of account receiving the recharge (e.g., prepaid, postpaid). New-Card-Money: The value of the new card. Ex-Trans-Type: The type of external transaction, if applicable. ChannelID: The channel used for the transaction (e.g., web, mobile app). ExParameters (1-10): Optional additional parameters for further details on the transaction. AccessModule: The module used to access the recharge system. |
|||
Recharge-Method |
20343 |
Enumerated |
|
The Recharge-Method AVP specifies the method used for the recharge process. The AVP indicates the type of recharge operation, including various methods such as voucher recharges, first-time activation, and loan-based recharges. Values: 0: First activation (Normal first activation rather than the first activation by recharge card or cash). 1: Voucher recharge through IVR from another phone. 2: Voucher recharge through IVR from the self phone. 3: Voucher recharge through SMS from another phone. 4: Voucher recharge through SMS from the self phone. 5: Voucher recharge through USSD from another phone. 6: Voucher recharge through USSD from the self phone. 7: Voucher recharge by operator/external system (manual recharge). 8: First activation by recharge card. 9: First activation in cash. 10: Loan by USSD. 11: Loan by IVR. 999: EVC Recharge (Electronic Voucher Collection). 9999: Query recharge record. Other (>1000): Extended by external systems (custom recharge methods). |
|||
Recipient-Amount |
20538 |
Unsigned32 |
|
Indicates the number of email boxes that receive the mail. This value is used to calculate the total cost after a rating process is completed. If the value is greater than 1: Multiply the unit price by the Recipient-Amount to calculate the total cost. If the value is 1 or less: The parameter is not used for calculation. |
|||
Recipient-Type |
30809 |
Enumerated |
|
Defines the recipient type of the received number. Values: 0: MM1 (Mobile) 1: MM3 (E-mail) 5: MM4 (Other operator's destination) 4: MM7 (VAS or short code) |
|||
Redirecting-Party-Id |
20316 |
UTF8String |
|
Indicates the redirection party number. This is used to specify the number of the party responsible for redirecting a call. The number format is as follows: International prefix + Country code + MSISDN (Mobile Station International Subscriber Directory Number) International prefix + Country code + Area number + PSTN (Public Switched Telephone Network). |
|||
Redirecting-Party-Id-Nature |
21167 |
Unsigned32 |
|
Used to describe the nature or type of the Redirecting-Party-Id. Specifically, it categorizes the party that is responsible for redirection in a telecom system. |
|||
Redirection-Reason |
20363 |
Unsigned32 |
|
Indicates the reason for a call redirection in a telecom system. The values differ between networks, such as CDMA and GSM, but the AVP is used to provide a reason for the redirection, which can affect call routing, billing, or service behavior. Possible Values (CDMA Network): 0: Unconditional (No conditions for redirection) 1: User Busy (The user is currently busy) 2: No Reply (The user did not answer) 3: Mobile Subscriber Not Reachable (The subscriber cannot be reached) 4: Others (Other reasons for redirection) Possible Values (GSM Network): 1: User Busy (The user is busy on another call) 2: No Reply (The user did not answer within the time frame) 3: Unconditional (Redirection is applied without conditions) 4: Others (Other reasons for redirection) 6: Mobile Subscriber Not Reachable (The subscriber is out of range) |
|||
Related-Object-ID |
60009 |
Integer64 |
|
Used to represent an ID associated with an object in the system. The specific meaning of this ID depends on the value of the Related-Object-Type AVP: 1: Offering ID (For associated offers) 2: Global Plan ID (For global plans) |
|||
Related-Object-Type |
60008 |
Integer32 |
|
Used to indicate the type of object that is associated with a balance instance in the telecom system. Values: 0: Not Involved (The object is not associated with any balance instance) 1: Offering (The object is an offering, such as a product or service package) 2: Global Plan (The object is part of a global plan, such as an international plan or subscription) |
|||
Release-Reason |
20780 |
Integer32 |
|
Specifies the cause for the release of a call. This can help determine the reason for disconnecting a session, which is crucial for accounting and troubleshooting. Values: 0: Unknown (The release reason is not specified) 1: OVER_MAXIMUM_CALL_DURATION (The call exceeded the maximum allowed duration) 2: The calling or called party hangs up (The call was ended by one of the parties) 3: The CCA message is returned (The call duration is reduced due to account changes but not released) 4: The account balance is used up (The account has no remaining balance to continue the call) 5: Session rerouted (After the session is released in one direction, a new session is initiated) |
|||
Reroute-Called-Number |
21168 |
OctetString |
|
Stores the number that the call is rerouted to, which is essential in scenarios where a call is redirected during its processing. |
|||
RN-Prefix |
30808 |
UTF8String |
|
Specifies the routing prefix for a received number. If the received number is for a number portability subscriber, the RN-Prefix field is populated by the MMSC (Mobile Message Service Center) to identify the routing prefix. |
|||
Route-Prefix |
20354 |
OctetString |
|
Holds the international route prefix used to transfer routing information for a special number. |
|||
RTBP-Information |
20600 |
Grouped |
|
Contains a group of data related to the one-off deduction in a Real-Time Billing Protocol (RTBP) system. The AVP structure is defined as follows: sp-id: Service provider ID service-id: Service ID for the charge CategoryID: Category identifier for the service ContentID: Content ID associated with the service CDRProductID: CDR (Call Detail Record) product ID CDRChargeMode: Mode of charging in CDR CDRTimes: Number of times a service is used CDRDuration: Duration of the service in seconds CDRVolume: Volume of data or usage CDRType: Type of charge (e.g., one-off, recurring) CDRServiceType: Type of service being billed CDRBeginTime: Start time of the service CDREndTime: End time of the service CDRPkgSpId: Service provider ID for the package CDRPkgServiceId: Service ID for the package CDRPkgProductId: Product ID for the package CDRSPName: Name of the service provider CDRServiceName: Name of the service being billed TransactionID: Transaction ID associated with the charge |
|||
Same-CUG-Not-Free-Notify-Flag |
30020 |
Integer32 |
|
Indicates whether a notification should be sent to both the calling and called parties to inform them that a call will incur charges when they are in the same Closed User Group (CUG) during a mobile-originated (MO) process. Values: 0: No notification is sent regarding charges. 1: A notification is sent to inform both parties that the call is chargeable, even though they belong to the same CUG. |
|||
S-Called-Group-Number |
21213 |
OctetString |
|
Used in the Mobile-Originated (MO), Mobile-Terminated (MT), or Mobile-Forwarded (MF) processes to identify the group code to which the called party belongs, in cases where the called party is part of a group of subscribers. If the called party is not a member of such a group, this AVP is left empty. |
|||
S-Called-Hunting-Main-Number |
21219 |
OctetString |
|
Used in the MO, MT, or MF processes to indicate the hunting access number of the called party. This number allows the system to reach the main number of the hunting list associated with the called party. If the called party is not part of a group (i.e., not a group subscriber), this AVP remains empty. |
|||
S-Called-Long-Number |
21207 |
OctetString |
|
Used in the MO, MT, or MF processes to represent the full, long-format number of the called party, typically in the MSISDN (Mobile Station International Subscriber Directory Number) format. This AVP is particularly useful when a called party is not part of a group subscriber, or when short number translation has not been performed, providing the original long-form number instead of a potentially abbreviated short number. |
|||
S-Called-Number-Type |
21216 |
OctetString |
|
Used in the MO, MT, or MF processes to indicate the type of subscriber when the called party is a group subscriber. This AVP helps identify whether the called party is a PBX (Private Branch Exchange) user or a non-PBX user within a group calling scenario. Values: 0: Non-PBX user 2: PBX user |
|||
S-Called-PBX-Display-Number |
21218 |
OctetString |
|
Used in the MO, MT, or MF processes to indicate the number displayed to the called party when the call is routed through a PBX (Private Branch Exchange) switchboard number. If the called party is not part of a group subscriber setup, this AVP will remain empty. |
|||
S-Called-Top-Group-Number |
21214 |
OctetString |
|
Used in the MO, MT, or MF processes when the called party is part of a group subscriber. This AVP indicates the top-level group code to which the called party belongs. It is helpful in scenarios where group-based call routing or group-level service management is involved. If the called party is not in a group, this AVP remains empty. |
|||
S-Called-VPN-Phone-Flags |
21217 |
OctetString |
|
Provides specific information about the called party in the MO, MT, or MF processes. If the called party is not part of a group subscriber, this AVP is left empty. The AVP contains a series of digits, each representing a different aspect of the called party's characteristics or call conditions. First digit: On-net or super group call display mode
Second digit: Always set to 0 Third digit: Always set to 0 Fourth digit: Always set to 0 Fifth digit: User type
Sixth digit: Always set to 0 Seventh digit: Whether the user has joined a hunting list
Eighth digit: Always set to 0 Ninth digit: IVR notification mode for individual payment
Tenth digit: USSD notification mode for individual payment
All other digits: Set to 0 |
|||
S-Caller-Group-Number |
21205 |
OctetString |
|
Used in the MO, MT, or MF processes to indicate the group code to which the calling party belongs. This AVP is only applicable when the calling party is a group subscriber. If the calling party is not part of a group, this AVP will be left empty. |
|||
S-Caller-Hunting-Main-Number |
21212 |
OctetString |
|
Used during the MO, MT, or MF processes to indicate the main hunting access number of the calling party. This is the number that can be dialed to access the calling party's hunting list. If the calling party is not a group subscriber, this AVP will be left empty. |
|||
S-Caller-Number-Type |
21209 |
OctetString |
|
Used to indicate the group subscriber type of the calling party when the calling party is a group subscriber in the MO, MT, or MF processes. This AVP is used to specify the type of user within the group, and it can take the following values: 0: Non-PBX user 2: PBX user |
|||
S-Caller-PBX-Display-Number |
21211 |
OctetString |
|
Used in the MO, MT, or MF processes to specify the number displayed to the called party when the calling number is a PBX switchboard number. If the calling party is not a group subscriber, this AVP will be left empty. |
|||
S-Caller-Short-Number |
21208 |
OctetString |
|
Indicates the short number of the calling party when the caller is a group subscriber involved in Mobile Originated (MO), Mobile Terminated (MT), or Mobile Forwarded (MF) processes. |
|||
S-Caller-Top-Group-Number |
21206 |
OctetString |
|
Indicates the code of the top-level group to which the calling party belongs. It is specifically relevant when the calling party is a group subscriber involved in Mobile Originated (MO), Mobile Terminated (MT), or Mobile Forwarded (MF) processes. |
|||
S-Caller-VPN-Phone-Flags |
21210 |
OctetString |
|
Conveys detailed flags related to the calling party's VPN phone settings during Mobile Originated (MO), Mobile Terminated (MT), or Mobile Forwarded (MF) processes. AVP encodes multiple flags within its octet string. Each digit in the string represents a specific attribute: First Digit: On-net or Super Group Call Display Mode
Second to Fourth Digits: Reserved for Future Use
Fifth Digit: User Type
Sixth Digit: Reserved for Future Use
Seventh Digit: Hunting List Participation
Eighth to Ninth Digits: Reserved for Future Use
Tenth Digit: IVR Notification Mode for Individual Payment
Eleventh Digit: USSD Notification Mode for Individual Payment
Remaining Digits: Reserved for Future Use
|
|||
Screen-Zone-ID |
30407 |
Integer32 |
|
Conveys zone information pertinent to the call screen list, facilitating the management and processing of call screening based on geographical or logical zones within the network. |
|||
SDP-Media-Identifier |
20820 |
Enumerated |
|
Serves to identify the type of multimedia service associated with a session, enabling accurate handling and processing of various service types within the network. Values: 0: VoiceCall 1: VideoCall 2: Fax |
|||
Send-Result |
20418 |
Unsigned32 |
|
Communicates whether the short message was successfully delivered or if it encountered a rollback scenario during the Mobile Originated (MO), Mobile Terminated (MT), or Mobile Forwarded (MF) processes. Values: 0: Indicates the short message has been delivered. 1: Indicates the short message has been rolled back. |
|||
Serial-No |
20391 |
UTF8String |
|
Used to indicate the serial number of a voucher card. |
|||
Service-Free-Indicator |
20388 |
Unsigned32 |
|
Serves as a flag to indicate whether a particular service is offered for free or is subject to charges. It plays a crucial role in billing, service provisioning, and policy enforcement by clearly distinguishing between free and paid services. Values: 0: Not free 1: Free |
|||
Service-Id |
20602 |
UTF8String |
|
Uniquely identifies a value-added service (VAS) by its service ID, enabling precise service recognition, provisioning, and management within the network. It is primarily utilized in the RTBP (Routing and Traffic Billing Process) to associate specific services with user sessions and billing records. |
|||
Service-Id |
20506 |
OctetString |
|
Uniquely identifies a service by its service ID, facilitating accurate service recognition, provisioning, and management within the network. It is primarily employed in GPRS (General Packet Radio Service) and MMS (Multimedia Messaging Service) processes to associate specific services with user sessions and billing records. |
|||
Service-Information |
873 |
Grouped |
|
Used to represent detailed information about specific service types. It allows for the transmission of service-related details in a structured and extensible format. The AVP structure is defined as follows: PS-Information: Information related to Packet-Switched services. IN-Information: Data for Intelligent Network services. P2PSMS-Information: Details specific to Peer-to-Peer Short Message Services. MDSP-Information: Metadata for Media Delivery and Streaming Protocols. IMS-Information: Information regarding IP Multimedia Subsystem (IMS) services. LCS-Information: Data for Location-based Services (LCS). PoC-Information: Push-to-Talk over Cellular (PoC) service information. Conference-Information: Details related to conferencing services. Message-Information: Messaging-specific service data. MMS-Information: Multimedia Messaging Service (MMS) details. MBMS-Information: Information for Multimedia Broadcast and Multicast Services (MBMS). SMS-Information: Information for Short Message Services (SMS). VCS-Information: Voice Call Service information. MMTel-Information: Data for Multimedia Telephony (MMTel) services. ProSe-Information: Proximity Services (ProSe) information. ServiceGeneric-Information: General service-related data for unclassified services. IM-Information: Instant Messaging service information. DCD-Information: Data for Dynamic Content Delivery services. M2M-Information: Information for Machine-to-Machine (M2M) communication. CPDT-Information: Charging and Policy Decision support data. |
|||
Service-Key |
20806 |
Unsigned32 |
|
Serves to specify the value of a service key, which identifies the type of intelligent service being triggered. For instance, it can be used by Voice over Broadband (VoBB) users to invoke specific intelligent services. Ordinary Services: If the value of this AVP is null (not set), it indicates that the associated service is an ordinary service rather than an intelligent one. Intelligent Services: When a value is present, the AVP specifies the type of intelligent service that should be applied, allowing network elements to tailor their handling of the session or transaction based on the specified service key. |
|||
Service-Level |
20531 |
Unsigned32 |
|
Indicates the level or tier of a service, allowing the network to differentiate between services of varying priorities, qualities, or importance. |
|||
Service-Parameter-Info |
20920 |
Grouped |
|
Encapsulates specific service parameters and their values, enabling the transmission of detailed service-related information within the Diameter protocol. This AVP is crucial for managing and configuring services by associating parameter types with their corresponding values. The AVP structure is defined as follows: Service-Parameter-Type: Specifies the type of the parameter, such as Tenant ID or SubcosId for the non-charged party. Service-Parameter-Value (Vendor-Specific): Defines the value corresponding to the parameter type. |
|||
Service-Parameter-Type |
20921 |
Unsigned32 |
|
Specifies the type of service parameter being transmitted in the Service-Parameter-Info AVP. It is used to identify the nature of the parameter, such as tenant-related information for a non-charged party. Values: 1: Tenant ID of the non-charged party 2: SubcosId of the non-charged party |
|||
Service-Parameter-Value |
20922 |
Integer64 |
|
Specifies the value of a service parameter identified by the Service-Parameter-Type AVP. |
|||
Service-Seq-No |
30350 |
UTF8String |
|
Used to define a service sequence number. |
|||
Service-Time-Out |
30360 |
Integer64 |
|
Indicates the session timeout value in seconds. |
|||
Service-Transaction-ID |
30335 |
UTF8String |
|
Provides a unique identifier for a service transaction. |
|||
Service-Type |
20507 |
Enumerated |
|
Specifies the type of service associated with a particular session or transaction, enabling network elements to identify, manage, and apply policies tailored to specific services. You can extend the Service-Type to include more service types by adding additional constants. This is a part of PS-Information AVP. |
|||
Service-Type (Integer) |
20608 |
Integer32 |
|
Indicates the type of service being utilized. It’s a part of RTBP-Information AVP. Values: 0: WAP 1: KJava 2: SMS 3: MMS 4: Mail 5: LBS (Location-Based Services) 6: Stream Media 7: IMPS (Instant Messaging and Presence Service) 8: UM (Unified Messaging) 9: WAP Push 11: CRBT (Caller Ring Back Tone) 12: General 13: MC (Multimedia Conference) 14: PIM (Personal Information Management) 15: VMB (Voice Mail Box) 16: CMB (Content Mail Box) 17: Payment Gateway 18: Storage 20: Service Package 21: Bank 22: E-Voucher 23: Msg+ |
|||
SGSN-IP |
20671 |
OctetString (represented as DiameterAddress) |
|
Specifies the IP address of the Serving GPRS Support Node (SGSN). |
|||
Share-Call-Percent |
30023 |
Integer32 |
|
Indicates the percentage of call fees entrusted to the called party under the Share Call function. A value of 100 signifies that the called party is responsible for paying all the fees, while other values indicate partial sharing of the costs. |
|||
SM-Id |
20402 |
UTF8String |
|
Used to uniquely identify a short message. It plays a critical role in the SMS refund process, where the Online Charging System (OCS) utilizes this identifier to determine the subscriber eligible for a refund. The generating party guarantees the uniqueness of the SM-Id, ensuring reliable tracking and management of short messages. |
|||
SM-Length |
20403 |
Unsigned32 |
|
Specifies the length of a short message. |
|||
SMSC-Address |
20401 |
UTF8String |
|
Specifies the address of the Short Message Service Center (SMSC). The SMSC is responsible for the storage and delivery of short messages in telecommunications networks. |
|||
SMS-Information |
2000 |
Grouped |
10415 (3GPP) |
Encapsulates details about an SMS, such as sender/recipient addresses, message type, status, and other metadata. The AVP structure is defined as follows: SMS-Node: Identifies the SMS node involved. Client-Address: IP address of the client. Originating-SCCP-Address: SCCP address of the originator. Recipient-SCCP-Address: SCCP address of the recipient. SMSC-Address: Address of the SMS Center. SM-Data-Coding-Scheme: Coding scheme used for the message. SM-Destination-Interface: Information about the destination interface. SM-Discharge-Time: Timestamp when the SMS was discharged. SM-Message-Text: The text of the SMS. SM-Message-Type: The type of the SMS message (e.g., MO/MT). SM-Originator-Interface: Information about the originator interface. SM-Protocol-ID: Protocol identifier for the message. SM-Reply-Path-Requested: Indicates if the reply path is requested. SM-Status: Status of the SMS (e.g., delivered, failed). SM-User-Data-Header: User data header for the message. User-Session-Id: Unique session identifier for the user. |
|||
SMS-Lang |
30812 |
Unsigned32 |
|
Represents the SMS language type. |
|||
SMS-Language-Type |
20795 |
Integer32 |
|
Specifies the language type of an SMS. Values: 1: Malay 2: English 3: Mandarin |
|||
Sms-Type |
20715 |
Unsigned32 |
|
Used to indicate the type of a Short Message (SM). It allows the network to distinguish between different types of SMS, such as inter-network (between different operators) and intra-network (within the same operator) messages. |
|||
Source-Addr |
20406 |
UTF8String |
|
Specifies the sender's address or phone number for an SMS. |
|||
Specific-Output |
20708 |
Unsigned32 |
Huawei |
Specifies the preference identifier of a Visited Public Mobile Network (VPMN) enterprise. |
|||
SP-Id |
20601 |
UTF8String |
|
Specifies the Service Provider (SP) code. |
|||
SP-Id (Binary) |
20504 |
OctetString |
|
Specifies the service provider's ID in a binary format. This AVP is primarily used in GPRS-related processes to identify the service provider associated with a session or transaction. It provides an alternative representation of the service provider ID compared to the UTF8String-based SP-Id AVP. |
|||
Src |
20617 |
UTF8String |
|
Specifies the sender's number or address in a message. |
|||
SSPNO |
20927 |
Unsigned32 |
|
Used to indicate the reported SSPNO (Service Switching Point Number). |
|||
SSP-Time |
20386 |
Time |
|
Indicates the time of SSP (Service Switching Point) reporting. |
|||
Start-Time |
20520 |
UTF8String |
|
Used to specify the start time of an event or session. |
|||
State |
30814 |
Unsigned32 |
|
Indicates the lifecycle status of a session or entity. |
|||
Status-Report-Request |
20415 |
Unsigned32 |
|
Indicates whether an SMS status report is required. It provides control over the SMS status report function, including enabling or disabling the feature and handling specific conditions related to status reporting failures. Values: 0: No SMS status report is required. 1: SMS status report is required. 2: Enable the SMS status report function. If the SMC fails to send an SMS status report, only the fee for sending the SMS status report is refunded. |
|||
Stop-Time |
20521 |
UTF8String |
|
Used to specify the stop time of an event or session. |
|||
Subscriber-Pay-Type |
20355 |
Unsigned32 |
|
Indicates the payment type of a subscriber. |
|||
Subscriber Type |
20797 |
Integer32 |
|
Specifies the type of a subscriber. It provides information about the subscriber's card configuration, such as whether they use a single SIM card or dual SIM cards. Values: 1: One Card 2: Two Card |
|||
Sum-Balance-Info |
30324 |
Grouped |
|
Contains aggregated balance-related information. |
|||
Suspend-Reason |
20895 |
Unsigned32 |
|
Used to specify the reason for suspending a session or subscriber service. |
|||
Tenant-ID |
21009 |
OctetString |
|
Specifies the identifier of a tenant in a multi-tenant environment. |
|||
Time-Zone |
20324 |
Unsigned32 |
|
Indicates the time zone associated with a user. |
|||
Total-Cost-Flag |
20375 |
Unsigned32 |
|
Indicates whether the total cost of a call or session should be returned. It provides a mechanism for enabling or disabling the return of cost-related information, ensuring compatibility with the standard Cost-Information AVP group. Values: 0: Do not return the consumption result. 1: Return the total cost information. |
|||
Total-Gift-Amount |
20703 |
Integer32 |
|
Specifies the total amount rewarded to a subscriber in the smallest currency unit (e.g., cents). This AVP is commonly used in contexts involving loyalty programs, promotional campaigns, or rewards, aligning with the definitions in the CCA{Termination} message. |
|||
Trade-Time |
20712 |
OctetString |
|
Specifies the recharge request time. This AVP is used in Huawei-specific Diameter applications, particularly in contexts involving recharge or transaction requests, aligning with the definition and value used in the CCR{Initial} message. |
|||
Transaction-ID |
20643 |
UTF8String |
|
Specifies an event ID generated by a third-party system. |
|||
Transaction-ID (20796) |
20796 |
UTF8String |
|
Specifies a unique transaction identifier. This AVP is aligned with the Transaction-ID used in the CCR{Initial} message. |
|||
Transaction-ID (Binary) |
20501 |
OctetString |
|
Specifies a transaction identifier generated by the application system. This AVP is primarily used in GPRS processes to identify and manage transactions. |
|||
Transaction-Operation-Status |
30323 |
Unsigned32 |
|
Used to indicate the status of a transaction's operation. This AVP enables the tracking and reporting of operational outcomes, providing essential feedback to involved systems and entities. Values: 0: for success 1: for failure 2: for pending |
|||
U-Billed-Fee |
30022 |
Integer32 |
|
Specifies the unbilled amount for a service or transaction. |
|||
UE-IMSI |
20318 |
UTF8String |
|
Specifies the International Mobile Subscriber Identity (IMSI) of a user. |
|||
Uniform-Serial-No |
20786 |
UTF8String |
|
Specifies a uniform sequence number associated with a transaction. For manual recharges initiated by an external business system, this AVP provides the external system's sequence number. For card recharges initiated by subscribers through self-service, the value is null. |
|||
Unit-Type |
30346 |
Unsigned32 |
|
Specifies the type of units being used or tracked within a session or transaction. |
|||
Unpaid-Fee |
60010 |
Integer64 |
|
Specifies the amount of unpaid fees associated with a subscriber. This AVP is only applicable when the Balance-Type AVP is set to 3000, providing critical data for financial tracking and billing purposes. |
|||
User-Basic-Info |
21196 |
Grouped |
|
Encapsulates basic subscriber information. This AVP allows the Online Charging Gateway (OCG) to retrieve subscriber details from the Charging and Billing Platform (CBP), bypassing the Service Data Unit (SDU). The AVP structure is defined as follows: I-Sub-COSID: Indicates the class of service ID for the subscriber. I-User-Type: Identifies the user's category (e.g., individual, corporate). I-Tenant-ID: Specifies the tenant ID associated with the subscriber. I-Language-Type: Indicates the preferred language of the subscriber. I-SMS-Language-Type: Specifies the language type for SMS communication. I-Brand-ID: Represents the brand ID associated with the subscriber. I-Saas-Tenant-ID: Specifies the SaaS tenant ID. I-First-Call-Flag: Indicates whether this is the subscriber's first call. |
|||
User-Passwd |
20362 |
UTF8String |
|
Indicate the authentication results for specific call control services. Each digit in the value corresponds to a predefined service, where: 1: indicates successful authentication 0: indicates failed authentication This AVP allows flexible and granular representation of authentication results for multiple services, such as Ring Back Tone (RBT) or Background Music (BGM). |
|||
Validity-Date2 |
21181 |
OctetString |
|
Specifies the validity period for a prepaid user. |
|||
V-MCC-MNC-Addr |
30924 |
Unsigned32 |
|
Used to represent the Mobile Country Code (MCC) and Mobile Network Code (MNC) address for a virtual network. |
|||
VPN-Call-Auth-Flag |
20941 |
OctetString |
|
Used to report permission control strings for groups and individuals in the Virtual Private Network (VPN) feature. |
|||
VPN-Notify-Flag |
20940 |
UTF8String |
|
Used to indicate whether a VPN subscriber is notified that their individual account is being used to pay fees. The first digit in the VPN-Notify-Flag AVP specifies the notification setting: 0: No notification 1: Notification enabled Other values: Reserved for future use |
Start innovating with Mobius
What's next? Let's talk!