Version

Accounting AVPs

package com.mobius.software.telco.protocols.diameter.primitives.accounting

These AVPs enable accounting and charging functionality across multiple Diameter interfaces (e.g., offline, online, IMS, SMS, location services, etc.). Rather than belonging to a single application interface (like Np, Gx, Gy, etc.), these AVPs form a common toolkit that different interfaces can use to manage usage reporting, rating, and cost calculation in telecom scenarios.

Name	AVP Code	Data Type	Vendor
Access-Network-Identifier	1000	Unsigned32	oneM2M
Identifies the access network associated with a specific request triggering an M2M (Machine-to-Machine) event record. The network in question is detected by the IN-CSE (Infrastructure Node - Common Services Entity), which recognizes the link from which a request originated or was sent to and maps it to a locally configured identifier. This AVP provides a way to track the access network involved in the transaction, facilitating proper billing, accounting, and event tracking.
Access-Network-Info-Change	4401	Grouped	3GPP
Used to convey information regarding changes in the access network information. This AVP is typically employed in scenarios where one or two SIP P-headers ("P-Access-Network-Info") have undergone changes, and it also captures the time when this change occurred. It is a grouped AVP that may include the following fields: Access-Network-Information: Contains multiple instances of network-related information, often related to SIP sessions. Cellular-Network-Information: Optional field that stores details about the cellular network involved. Change-Time: Specifies the exact time when the access network information change occurred.
Access-Network-Information	1263	OctetString	3GPP
Used to indicate an instance of the SIP P-header "P-Access-Network-Info", [RFC 7315]. This AVP carries information related to the access network used in the session, including various network identifiers depending on the type of network access (e.g., 3GPP, trusted or untrusted WLAN). In scenarios where multiple access-net-spec values are included in the SIP header, multiple instances of this AVP will be used, with each AVP containing one access-net-spec value. For GERAN access: The cgi-3gpp field contains the CGI. For UTRAN access: The utran-cell-id-3gpp field contains the LAI and CI, and the utran-sai-3gpp field contains the SAI. For E-UTRAN access: The utran-cell-id-3gpp field contains the TAI and ECGI. For NR access: The utran-cell-id-3gpp field contains the TAI and NCI. Trusted WLAN Access: Contains the BSSID in the i-wlan-node-id field, and the operator-specific-GI field may hold a Geographical Identifier. Untrusted WLAN Access: Includes the BSSID in the i-wlan-node-id field, along with the UE local IP address, ePDG IP Address, and source ports (TCP/UDP).
Access-Transfer-Information	2709	Grouped	3GPP
Used in IMS networks to provide essential information for service continuity during an access transfer. This grouped AVP contains multiple elements that describe the conditions and parameters of an access transfer, ensuring seamless handover and session continuity across different network access types. The AVP includes details about the type of access transfer, network information, and specific identifiers related to the session or user equipment. It plays a critical role in ensuring uninterrupted service for users switching between different access networks (e.g., cellular to WLAN) during an ongoing IMS session. The AVP structure is defined as follows: Access-Transfer-Type: Specifies the type of access transfer being performed. Access-Network-Information: Contains information about the network from which the transfer is initiated. Cellular-Network-Information: Provides details about the cellular network involved in the transfer. Inter-UE-Transfer: Describes whether an inter-UE transfer is involved. User-Equipment-Info: Provides information about the user equipment (UE) involved in the session. Instance-Id: Uniquely identifies the instance of the transfer. Related-IMS-Charging-Identifier: Contains the identifier related to IMS charging for the session. Related-IMS-Charging-Identifier-Node: Identifies the node responsible for IMS charging. Change-Time: Indicates the time the transfer event occurred.
Access-Transfer-Type	2710	Enumerated	3GPP
Indicates the type of access transfer that occurred for IMS service continuity. It defines the specific type of transfer that took place between packet-switched (PS) and circuit-switched (CS) domains or within the same domain. Enumerated values: 0: PS to CS Transfer 1: CS to PS Transfer 2: PS to PS Transfer 3: CS to CS Transfer
Account-Expiration	2309	Time	3GPP
Used to indicate the expiration date and time of day for a subscriber's account. This AVP provides essential information for account management, ensuring that services are properly terminated or renewed based on the specified expiration time.
Accumulated-Cost	2052	Grouped	3GPP
Used to represent the total cost accumulated for an ongoing session in a telecommunications network. This AVP helps in real-time monitoring and billing by providing a measure of the accumulated usage charges as they accrue. This AVP is essential in cases where tracking of costs in real time is required, such as in prepaid billing or quota management scenarios. The AVP structure is defined as follows: Value-Digits (Required): This field holds the primary numerical value of the accumulated cost. It is specified as a long integer, representing the integral part of the accumulated cost. For example, if the accumulated cost is represented in currency units, Value-Digits would contain the integer portion. Exponent (Optional): This field represents the magnitude or scale of the cost by denoting the decimal position, essentially functioning as the "power of ten" multiplier for Value-Digits. It enables precision by allowing representation of costs that require decimal places, for example, converting "123" in Value-Digits with an Exponent of "-2" to mean "1.23" currency units.
Adaptations	1217	Enumerated	3GPP
Indicates whether the content originator permits adaptations to the content during delivery. This AVP is typically used in multimedia service scenarios where the content may need to be adjusted (e.g., compressed or modified) depending on network conditions or device capabilities. Enumerated values: 0: Yes (Adaptations are allowed) 1: No (Adaptations are not allowed)
Additional-Content-Information	1207	Grouped	3GPP
Used to identify subsequent content types within a Multimedia Message (MM). It helps specify multiple parts of the content when multipart content is indicated by the Type-Number AVP or Additional-Type-Information AVP within the Content-Type AVP. This AVP allows for further details to be specified for each content item, including the content's type and size. The AVP structure is defined as follows: Type-Number: Identifies the type of the content. Additional-Type-Information: Provides additional information about the content type. Content-Size: Specifies the size of the content in bytes.
Additional-Exception-Reports	3936	Enumerated	3GPP
Specifies whether additional exception reports are permitted when the maximum reporting rate is reached. This AVP helps control the generation of extra reports in cases where exception thresholds are met. Enumerated values: 0: Not allowed (no additional reports should be generated) 1: Allowed (additional reports are permitted)
Additional-Type-Information	1205	UTF8String	3GPP
Used to provide any additional information about media types beyond the well-known or non-well-known media types. This AVP allows for further identification of media content in multimedia messaging scenarios.
Address-Data	897	UTF8String	3GPP
Provides address information formatted according to the type specified in the Address-Type AVP. This AVP carries the actual address data, such as an email, MSISDN, or IP address, in accordance with the MMS encapsulation standard.
Addressee-Type	1208	Enumerated	3GPP
Identifies how the recipient is addressed in the header of a multimedia message (MM). Enumerated values: 0 TO: Primary recipient 1 CC: Carbon copy recipient 2 BCC: Blind carbon copy recipient
Address-Type	899	Enumerated	3GPP
Specifies the type of address carried within the Address-Data AVP. Enumerated values: 0: Email address 1: MSISDN (Mobile Subscriber ISDN Number) 2: IPv4 address 3: IPv6 address 4: Numeric shortcode 5: Alphanumeric shortcode 6: Other address type 7: IMSI (International Mobile Subscriber Identity)
AF-Correlation-Information	1276	Grouped	3GPP
Used to carry the Application Function (AF) charging identifier, also known as the Inter-IMS Charging Identifier (ICID) for IMS, along with associated flow identifiers. These identifiers are generated by the AF and conveyed to the Policy and Charging Control (PCC) elements, such as the P-GW, over the Rx or Gx interfaces as specified in 3GPP [TS 29.214] and [TS 29.212]. This AVP is vital in scenarios where multiple AF sessions are conveyed over the same bearer and can help correlate these sessions with a particular charging identifier. The AF-Correlation-Information AVP is defined either per Rating Group or per Rating Group and Service Identifier when Service Identifier level reporting is applied. The AVP structure is defined as follows: AF-Charging-Identifier (Required): This field contains the unique identifier used to correlate the AF sessions within the IMS network. Represented as a byte buffer, it typically includes information such as ICID for IMS-based services. This identifier helps to uniquely link the session-related data for billing and policy control purposes across various network components. Flows (Optional, Multiple): A list of Flows AVPs, where each entry identifies a specific IP flow associated with the AF session. Each Flows AVP contains information about a data flow in the session, enabling granular control and reporting for each identified flow. This parameter is crucial in scenarios involving multiple flows per session, providing detailed tracking and management capabilities.
Alternate-Charged-Party-Address	1280	UTF8String	3GPP
Holds the address of an alternate charged party, which is determined by an Application Server (AS) at the initiation of an IMS session. This AVP specifies the address used for charging when an alternate party is responsible for session charges.
Announcement-Identifier	3905	Unsigned32	3GPP
Contains a code identifying an announcement that is to be played. This AVP allows the network to specify and control the playback of announcements during an IMS session.
Announcement-Information	3904	Grouped	3GPP
Provides the parameters necessary for an announcement service within a Diameter-based network. Each Announcement-Information AVP describes a single announcement to be played to a user, including the order, timing, and various settings related to playback. This AVP is used in services where announcements are delivered to users, allowing detailed control over the playback sequence and customization of each announcement. The AVP structure is defined as follows: Announcement-Identifier (Required): A unique identifier for the announcement. This ID is used to specify which announcement should be played to the user. Variable-Part (Optional, Multiple): A list of Variable-Part AVPs that define dynamic or variable content segments within the announcement. Each part has an order, type, and value that allow the announcement to include specific information based on contextual factors, enhancing the personalized experience for the user. Time-Indicator (Optional): Specifies a timing parameter, indicating when the announcement should be connected to the user relative to quota exhaustion or other thresholds. This timing control allows precise alignment of announcements with service conditions. Quota-Indicator (Optional): Defines whether the announcement is linked to a specific quota status, such as when nearing quota exhaustion. The QuotaIndicatorEnum specifies particular quota-related triggers for announcement playback. Announcement-Order (Optional): Specifies the sequence in which multiple announcements should be played. If multiple Announcement-Information AVPs are present in a message with the same timing, this field determines the playback order. Play-Alternative (Optional): Indicates if an alternative announcement should be played if the primary announcement is unavailable. The PlayAlternativeEnum allows specifying a fallback mechanism for announcement delivery. Privacy-Indicator (Optional): Controls privacy settings for the announcement, indicating if certain information within the announcement should be concealed. This setting is managed through PrivacyIndicatorEnum and applies when privacy considerations are required. Language (Optional): Defines the language for the announcement playback. This parameter is essential in multilingual environments where users receive announcements in their preferred or configured language.
Announcement-Order	3906	Unsigned32	IETF
Specifies the sequence in which multiple announcements should be connected for playback. When multiple Announcement-Information AVPs are included in a single message with the same timing indicator, the Announcement-Order AVP dictates the exact order in which these announcements will be presented to the user. This ordering ensures that announcements are played in the intended sequence, creating a coherent experience, particularly when a series of related messages need to be conveyed.
Announcing-PLMN-ID	4408	UTF8String	3GPP
Contains the identity of the Public Land Mobile Network (PLMN) that signaled the carrier frequency. This identity is used when the serving PLMN is different from both the Home PLMN (HPLMN) and Visited PLMN (VPLMN).
Announcing-UE-HPLMN-Identifier	3426	UTF8String	3GPP
Contains the identifier of the Home Public Land Mobile Network (HPLMN) for the announcing User Equipment (UE).
Announcing-UE-VPLMN-Identifier	3427	UTF8String	3GPP
Contains the identifier of the Visited Public Land Mobile Network (VPLMN) for the announcing User Equipment (UE).
AoC-Cost-Information	2053	Grouped	3GPP
Provides detailed cost information for Advice of Charge (AoC) services. It includes both accumulated costs and incremental costs, allowing for precise monitoring and billing of ongoing services. The AVP structure is defined as follows: Accumulated-Cost: This optional field represents the total cost accrued over the duration of the session or usage period, offering a cumulative cost overview. Incremental-Cost: This optional, repeatable field indicates incremental charges, allowing the specification of cost changes at various stages of the session. Multiple Incremental-Cost AVPs can be included to represent charges at different points in the service timeline. Currency-Code: This field specifies the currency used for the cost values, represented by the ISO 4217 numeric code. It ensures clarity in cost representation, especially in services spanning multiple regions or requiring specific currency designations.
AoC-Format	2310	Enumerated	3GPP
Specifies the format in which Advice of Charge (AoC) information is delivered to the User Equipment (UE). Enumerated values: 0 MONETARY: The AoC information is sent in a monetary format, presenting the cost in a currency-based structure (e.g., showing charges in dollars, euros, etc.). 1 NON_MONETARY: This format sends AoC information in units rather than currency. 2 CAI: Refers to the Charging Amount Information (CAI) format, which provides a detailed breakdown of charges in a standardized manner. This format is generally used for more complex billing structures, allowing the AoC information to include specific charge categories and structures.
AoC-Information	2054	Grouped	3GPP
Includes the necessary information for the Advice of Charge (AoC) service. It contains details such as cost information, tariff information, and subscription information. The AVP structure is defined as follows: AoC-Cost-Information: Provides accumulated and incremental cost data. Tariff-Information: Offers details about tariff information for the session. AoC-Subscription-Information: Holds subscription-related information.
AoC-Request-Type	2055	Enumerated	3GPP
Indicates the type of Advice of Charge (AoC) requested. Enumerated values: 0: AoC_NOT_REQUESTED – The AoC is not requested. 1: AoC_FULL – The full AoC information is requested. 2: AoC_COST_ONLY – Only cost-related information is requested. 3: AoC_TARIFF_ONLY – Only tariff-related information is requested.
AoC-Service	2311	Grouped	3GPP
Contains details related to the Advice of Charge (AoC) service type and whether the AoC service is obligatory. The AVP structure is defined as follows: AoC-Service-Obligatory-Type: Indicates if the AoC service is obligatory. AoC-Service-Type: Specifies the type of AoC service.
AoC-Service-Obligatory-Type	2312	Enumerated	3GPP
Indicates whether the Advice of Charge (AoC) information is binding or non-binding for the service. Enumerated values: 0: NON_BINDING – The AoC information is not binding. 1: BINDING – The AoC information is binding.
AoC-Service-Type	2313	Enumerated	3GPP
Defines the type of Advice of Charge (AoC) information that will be provided to the subscriber. Enumerated values: 0: NONE – No AoC service is provided. 1: AOC-S – AoC service during the session. 2: AOC-D – AoC service for delivery. 3: AOC-E – AoC service for event-based charging.
AoC-Subscription-Information	2314	Grouped	3GPP
Contains subscription and formatting parameters related to the Advice of Charge (AoC) service as provided by the Home Subscriber Server (HSS). The AVP structure is defined as follows: AoC-Service: Specifies the services associated with AoC. AoC-Format: Indicates the format of the AoC information. Preferred-AoC-Currency: Represents the preferred currency for AoC.
API-Content	1309	UTF8String	3GPP
Contains the message content, such as location or Monitoring Type, used in the T8 transaction for an API invocation request. This AVP may be used in scenarios where the specific content of an API call is included.
API-Direction	1310	Enumerated	3GPP
Specifies the direction of the API communication, either invocation or notification. Enumerated values: 0: Invocation – Indicates an API invocation. 1: Notification – Indicates an API notification.
API-Identifier	1311	OctetString	3GPP
Contains the identification of the northbound exposure API for each API invocation. This AVP uniquely identifies the API being invoked or notified in the transaction.
API-Invocation-Timestamp	1312	Time	3GPP
Records the exact timestamp when the API invocation request is submitted to the SCEF (Service Capability Exposure Function) from the SCS/AS (Service Capability Server/Application Server). This AVP is useful for tracking the timing of API requests in network operations.
API-Network-Service-Node	1315	Enumerated	3GPP
Identifies the network element that triggers an API notification. Enumerated values: 0: MME (Mobility Management Entity) 1: SGSN (Serving GPRS Support Node) 2: HSS (Home Subscriber Server) 3: PCRF (Policy and Charging Rules Function) 4: PFDF (Policy Decision Function and Policy Decision Filter) 5: BMSC (Broadcast Multicast Service Center) 6: CSCF (Call Session Control Function) 7: RCAF (Radio Core Access Function)
API-Result-Code	1313	Unsigned32	3GPP
Indicates the result of an API invocation. This AVP can hold status codes that provide information about the success or failure of an API request.
API-Size	1314	Unsigned64	3GPP
Represents the size of the API payload in bytes. This AVP helps track the volume of data being transmitted or processed as part of the API invocation.
APN-Rate-Control	3933	Grouped	3GPP
Specify the rate control parameters applicable for data packet transfers within a specific Access Point Name (APN) in both uplink and downlink directions. This AVP is especially relevant in managing data traffic flows, ensuring optimized network resource utilization, and controlling bandwidth usage for particular APNs. The AVP structure is defined as follows: APN-Rate-Control-Uplink: Specifies the rate control limits and configurations applied to data transfers from the user device to the network (uplink direction). APN-Rate-Control-Downlink: Specifies the rate control limits for data transfers from the network to the user device (downlink direction), thereby controlling download bandwidth and managing incoming data flow.
APN-Rate-Control-Downlink	3934	Grouped	3GPP
Contains rate control parameters specifically applicable to data transfers in the downlink direction for the designated APN. This AVP helps manage the maximum rate and message size allowed for downlink traffic. The AVP structure is defined as follows: Rate-Control-Time-Unit: Defines the time unit for rate control. Rate-Control-Max-Rate: Specifies the maximum rate allowed for downlink data transfers. Rate-Control-Max-Message-Size: Defines the maximum size of data messages allowed in downlink traffic.
APN-Rate-Control-Uplink	3935	Grouped	3GPP
Holds the rate control parameters applicable to data transfers in the uplink direction for the designated APN. The AVP structure is defined as follows: Additional-Exception-Reports: Indicates whether additional exception reports are allowed when the maximum rate is reached. Rate-Control-Time-Unit: Defines the time unit for rate control. Rate-Control-Max-Rate: Specifies the maximum rate allowed for uplink data transfers.
Application-Entity-ID	1001	UTF8String	oneM2M
Represents the identity of an M2M (Machine-to-Machine) Application Entity (AE) when applicable. This AVP is essential for identifying the specific AE involved in a transaction or session, and its format is specified according to M2M standards.
Application-Provided-Called-Party-Address	837	UTF8String	3GPP
Contains the called party number, such as a SIP URI or an E.164 number, as determined by the application server. It is used when the application server is responsible for selecting or determining the called party's address.
Application-Server	836	UTF8String	3GPP
Holds the SIP URL(s) of the application server(s) that were addressed during a session. This AVP is crucial for tracking the application servers involved in a session and provides a reference for identifying the specific application server that was used.
Application-Server-Information	850	Grouped	3GPP
Contains details about the application servers visited through the ISC interface. The AVP structure is defined as follows: Application-Server: Holds the SIP URL(s) of the application server(s) involved. Application-Provided-Called-Party-Address: Contains the called party number(s) as provided by the application server. Status-AS-Code: Contains the status code related to the application server.
Application-Specific-Data	3458	OctetString	3GPP
Contains a block of data provided by the application on the User Equipment (UE). The content of this block is specific to the application and may vary depending on the particular use case of the application in the network.
Applic-ID	1218	UTF8String	3GPP
Holds the identification of the destination application that the underlying MMS (Multimedia Messaging Service) abstract message was addressed to. This AVP is crucial for routing the message to the appropriate application service.
Associated-Party-Address	2035	UTF8String	3GPP
Used in the context of MMTel (Multimedia Telephony) supplementary services. It holds the address of the user involved in the supplementary service, such as the "forwarding party" in call diversion (CDIV), the "transferor" in explicit call transfer (ECT), the "Pilot Identity" in Flexible Alerting (FA), or the "Initiator party" in three-party calling (3PTY). The address is typically a SIP URI or Tel URI.
Associated-URI	856	UTF8String	3GPP
Holds a non-barred public user identity, such as a SIP URI or Tel URI, that is associated with the registered public user identity. This identity is obtained from the P-Associated-URI header in the 200 OK SIP response to a REGISTER request. If the P-Associated-URI header contains multiple public user identities, this AVP may appear multiple times, each representing one identity.
Authorised-QoS	849	UTF8String	3GPP
Represents the authorized Quality of Service (QoS) level, as defined in [TS 23.207] and [TS 29.207], which is applied through the Go reference point. Although defined, this AVP is not actively used in implementations.
Aux-Applic-Info	1219	UTF8String	3GPP
Contains additional application-specific control information relevant to the implementation. This AVP allows applications to include supplementary details necessary for custom operations or features.
Base-Time-Interval	1265	Unsigned32	3GPP
Specifies the duration, in seconds, of the base time interval used for controlling time quota consumption.
Basic-Service-Code	3411	Grouped	3GPP
Used to represent essential service information associated with a voice call service in telecommunications. It allows the identification of the service type—either a Bearer-Service or a Teleservice—being used during a voice session. The AVP structure is defined as follows: Bearer-Service: Represents a type of bearer service associated with the voice call, which refers to a transport service that provides the data connection, typically at a specific quality of service (QoS) level. The inclusion of Bearer-Service AVP specifies that the session is associated with a particular bearer service type. Teleservice: Identifies a teleservice associated with the call, representing specific telecommunication services such as voice, SMS, or other multimedia communication services directly utilized by the end-user.
Bearer-Capability	3412	OctetString	3GPP
Provides information about the type of bearer service or connectivity capability used in a session. Defined as an OctetString, this AVP contains coded information following the specifications in [TS 29.078] that indicates the characteristics of the bearer channel, such as data rate, transfer capabilities, and quality of service requirements.
Bearer-Service	854	OctetString	3GPP
Indicates the bearer service utilized for the Public Switched Telephone Network (PSTN) segment of an IMS session or a voice call service. It identifies the specific bearer used to facilitate the service’s connectivity requirements.
BSSID	2716	UTF8String	3GPP
Contains the Basic Service Set Identifier (BSSID) of the access point associated with the User Equipment (UE) within a WLAN Access Network. The BSSID format is defined by IEEE Std [802.11-2012], providing a unique identifier for the access point that the UE is connected to in a wireless environment.
Called-Asserted-Identity	1250	UTF8String	3GPP
Contains the final address of the asserted called party, such as a SIP URI or E.164 number. This address is retrieved from the P-Asserted-Identity SIP header in 2xx responses to a SIP request (either dialog-initiating or standalone transaction). If both SIP URI and Tel URI are included in the P-Asserted-Identity header, multiple instances of this AVP may appear. It is mandatory if the P-Asserted-Identity SIP header is available in the response.
Called-Identity	3916	UTF8String	3GPP
Holds the address (e.g., SIP URI, E.164) of the called party after a change in the session, typically due to a SIP UPDATE or SIP RE-INVITE request. It is used to track changes in the called party identity throughout the session.
Called-Identity-Change	3917	Grouped	3GPP
Used to capture information about a change in the called party's identity, such as in cases where call redirection or forwarding has occurred. This AVP includes the updated identity (address) of the terminating party and a timestamp of when the change was made. It facilitates accurate tracking and billing in cases of redirected calls, ensuring the session reflects the final called destination. The AVP structure is defined as follows: Called-Identity: Specifies the new identity address of the called party after the change. Change-Time: Records the exact time the called identity was updated, allowing precise event correlation and billing based on session changes.
Called-Party-Address	832	UTF8String	3GPP
Specifies the address (SIP URI, Tel URI, or URN) of the party to whom the call is directed. In IMS charging scenarios, it holds the Public User ID or Public Service ID from the Request-URI of an outgoing request. It is used for various SIP transactions, including registrations and subscriptions, with the AVP containing the address relevant to the context of the SIP request. For VCS charging, it holds the destination address after proxy processing.
Calling-Party-Address	831	UTF8String	3GPP
Identifies the party initiating a SIP transaction (Public User Identity or Public Service Identity) for IMS charging. The address (SIP URI or Tel URI) is retrieved from the P-Asserted-Identity header of a non-REGISTER SIP request. If the P-Asserted-Identity contains both a SIP URI and a Tel URI, multiple AVPs may appear. In cases where no P-Asserted-Identity is known, it defaults to "unknown." In VCS charging, it identifies the initiating party of a voice call and is derived from the circuit-switched Calling Party Number.
Carrier-Select-Routing-Information	2023	UTF8String	3GPP
Holds routing information regarding carrier selection as determined by the S-CSCF or AS. This information is derived from the SIP Requested URI header and indicates the carrier selected during the session.
Cause-Code	861	Integer32	3GPP
Identifies the specific cause of a session termination or transaction result within an IMS (IP Multimedia Subsystem) network, encapsulating both success and failure scenarios. The AVP is used in messages such as Accounting-Request (ACR) for "Stop" and "Event" notifications, and Credit-Control-Request (CCR) messages for "Terminate" and "Event." This AVP helps to capture the session's outcome, including SIP (Session Initiation Protocol) responses, and maps them to a numerical code for tracking. Parameters: Successful Cause Codes: 0: Normal end of session – Used in ACR[Stop] to indicate a standard session release, initiated by the user or network (triggered by a SIP BYE after SIP ACK). -1: Successful transaction – Signifies a successful SIP transaction (e.g., SIP REGISTER) that received a 200 Final Response. -2: End of SUBSCRIBE dialog – Indicates a successful end of a SIP SUBSCRIBE transaction. -2xx: 2xx Final Response (except 200) – Specifies transaction end due to a 2xx Final Response as per RFC 3261. -3xx: 3xx Redirection – Implies transaction termination from receiving/initiating a 3xx response. -3: End of REGISTER dialog – Shows the closure of a SIP REGISTER dialog (e.g., due to an expiration). Failure Cause Codes: 1: Unspecified error – Denotes an unknown termination reason for the SIP transaction. 4xx: 4xx Request failure – Transaction failure due to receiving a 4xx error response (client error). 5xx: 5xx Server failure – Indicates termination from receiving a 5xx server error. 6xx: 6xx Global failure – Marks a global failure response as the cause of termination. 2: Unsuccessful session setup – Session setup failed, for example, due to Timer H expiration or lack of ACK receipt. 3: Internal error – Termination triggered by an internal processing error within the IMS node.
Cellular-Network-Information	3924	OctetString	3GPP
Contains information related to the cellular network, represented as an instance of the SIP header "Cellular-Network-Info". This AVP is utilized to relay cellular network-specific data within the SIP context for Diameter protocol interactions.
CG-Address	846	Address	3GPP
Holds the IP address of the Charging Gateway (CG) associated with the session. It is primarily used to identify the charging gateway endpoint in billing and charging scenarios, enabling accurate record association for accounting purposes.
Change-Condition	2037	Integer32	3GPP
Indicates specific changes in charging conditions that trigger various actions within a session, such as the generation of an Accounting-Request, the closure of a volume counts container for an IP-CAN bearer, or the ending of a service data container or ProSe communication data container. Each change condition is identified by a distinct integer value, and the AVP is used primarily in billing, accounting, and charging scenarios to communicate the reason for closing or adjusting session records. Values: 0 Normal Release: Used for IP-CAN session termination, bearer release, or service flow termination. 1 Abnormal Release: Indicates an abnormal session or connection release. 2 QoS Change: Signifies a change in Quality of Service. 3 Volume Limit: Triggered when a volume threshold is reached. 4 Time Limit: Triggered by a time threshold being reached. 5 Serving Node Change: Indicates a change in the serving node. 6 Serving Node PLMN Change: Indicates a change in the serving node’s Public Land Mobile Network (PLMN). 7 User Location Change: Triggered by a change in the user’s geographical location. 8 RAT Change: Radio Access Technology change detected. 9 UE TimeZone Change: Indicates a change in the user’s device time zone. 10 Tariff Time Change: Triggered by a change in tariff timing. 11 Service Idled Out: Indicates service idling. 12 Service-Specific Unit Limit: Service-specific unit threshold reached. 13 Max Number of Changes in Charging Conditions: Limit for charging condition changes reached. 14 CGI-SAI Change: Change in Cell Global Identity or Service Area Identity. 15 RAI Change: Change in Routing Area Identity. 16 ECGI Change: Evolved Cell Global Identity change detected. 17 TAI Change: Tracking Area Identity change. 18 Service Data Volume Limit: Limit reached for service data volume. 19 Service Data Time Limit: Limit reached for service data time. 20 Management Intervention: External management intervention. 21 Service Stop: Service has stopped. 22 User CSG Information Change: Closed Subscriber Group info update. 23 S-GW Change: Change in Serving Gateway. 24 Change of UE Presence in Presence Reporting Area: UE presence change in specified reporting area. 25-30 ProSe Charging Only: Values specific to Proximity Services (e.g., 25 for proximity alert). 31 Removal of Access: Access removal. 32 Unavailability of Access: Access is unavailable. 33 Access Change of Service Data Flow: Service data flow access altered. 34 Indirect Change Condition: Indirect triggering condition. 35 Maximum Number of NIDD Submissions: NIDD submissions limit. 36 Change in UP to UE: User plane change to UE. 37 Serving PLMN Rate Control Change: PLMN rate control change. 38 APN Rate Control Change: Access Point Name rate control adjustment. 39-43 NIDD Specific Conditions: Conditions related to Non-IP Data Delivery, like timeouts. 44 MO Exception Data Counter: MO exception data count reached. 45 Change of 3GPP PS Data Off Status: Data off status change. 46 VoLTE Bearer Normal Release: Normal release of VoLTE bearer. 47 VoLTE Bearer Abnormal Release: Abnormal release of VoLTE bearer.
Change-Time	2038	Time	3GPP
Holds a timestamp in UTC format, representing different events based on the charging context: EPC Charging: Time when volume counts for the IP-CAN bearer or service data container are closed due to charging condition changes. IMS Charging: Time of access transfer. MMTel Charging: Time when a conference participant's action (e.g., joining, creating) triggers an Accounting Request. ProSe Charging: Time when volume counts for the ProSe group communication container are closed due to charging condition changes.
Charged-Party	857	UTF8String	3GPP
Holds the address (Public User ID, SIP URI, Tel URI, etc.) of the party responsible for charges. For Monitoring Event charging, it specifies the entity for which accounting and charging functions are performed by the 3GPP network elements.
Charging-Characteristics-Selection-Mode	2066	Enumerated	3GPP
Identifies the specific type of charge associated with a Rate-Element. It helps categorize the reason for charges applied during a session, allowing differentiation between usage-based and event-specific charges. This AVP supports multiple charging scenarios, particularly for billing and accounting in Diameter-based networks. Enumerated values: 0 UNKNOWN: The charge type is not specified or unknown. 1 USAGE: The charge corresponds to standard usage, such as data or voice usage. 2 COMMUNICATION-ATTEMPT-CHARGE: The charge is applied for an attempt to initiate communication, regardless of success. 3 SETUP-CHARGE: This is a setup charge, generally a one-time fee for initiating a session or service. 4 ADD-ON-CHARGE: An additional charge applied for extra features or services beyond the primary usage.
Charging-Per-IP-CAN-Session-Indicator	4400	Enumerated	3GPP
Specifies whether charging on a per IP-CAN session basis is active for offline charging. This AVP is particularly relevant for managing offline charging sessions in complex network environments, where charging can either be tracked across the entire IP-CAN session or at specific service levels. If this AVP is not included, it is assumed that charging per IP-CAN session is inactive. Enumerated values: 0 Inactive: Charging per IP-CAN session is inactive; charging does not track the entire session but may be based on individual events or transactions. 1 Active: Charging per IP-CAN session is active, tracking and billing the user based on the entirety of the IP-CAN session.
Civic-Address-Information	1305	OctetString	3GPP
Holds the Civic Address of the Access Point to which the User Equipment (UE) is connected, whether under a trusted or untrusted WLAN.
Class-Identifier	1214	Enumerated	3GPP
Classifies the type or category of data associated with a service or transaction. It specifies how the data is used or interpreted, particularly for content classification and billing purposes. Enumerated values: 0 (Personal): Indicates data or content intended for personal use by the end user, typically not for public sharing. 1 (Advertisement): Marks content as promotional or commercial in nature, which may be used to manage and bill ad-related data separately. 2 (Informational): Identifies data as informational, such as notifications or updates, and not intended for direct commercial gain. 3 (Auto): Used for automated or system-generated data, possibly for backend or operational purposes.
Client-Address	2018	Address	3GPP
Provides the address of the messaging node to which the Online Charging System (OCS) is connected. It identifies the specific client node involved in the charging process.
CN-Operator-Selection-Entity	3421	Enumerated	3GPP
Indicates the entity responsible for selecting the Serving Core Network in network-sharing scenarios. Enumerated values: 0: The Serving Network was selected by the UE. 1: The Serving Network was selected by the network.
Content-Class	1220	Enumerated	3GPP
Categorizes multimedia messages (MM) based on their content type and quality. It enables classification of content for Multimedia Messaging Services (MMS), allowing network systems to determine the type and quality of multimedia content being transmitted. The AVP can help in applying policies, charging, or prioritization based on content complexity or richness. Enumerated values: 0 (text): Plain text-only messages. 1 (image-basic): Basic image content, often of lower resolution. 2 (image-rich): Richer, higher-quality images, potentially in larger file sizes. 3 (video-basic): Basic video content, generally low-resolution or shorter in duration. 4 (video-rich): Higher quality or high-resolution video content. 5 (megapixel): Very high-quality images, typically larger than 1 megapixel. 6 (content-basic): Basic multimedia content, possibly combining images, text, and basic video. 7 (content-rich): Rich multimedia content that may include high-quality images, complex graphics, and high-definition video.
Content-Disposition	828	UTF8String	3GPP
Determines how the message body, or individual parts of it in the case of multipart messages, should be processed by the User Agent Client (UAC) or User Agent Server (UAS) in SIP communications. This AVP extends MIME Content-Disposition handling, enabling specialized control over multimedia message content within SIP messages, as defined in [RFC3261]. Several SIP-specific disposition-types are available for Content-Disposition, each indicating a particular handling approach for the message body: session: The body part represents a session, such as one used for a call setup or pre-call media. This type is commonly associated with application/sdp content. render: Indicates that the body part should be displayed or otherwise presented to the user. This value is used instead of "inline" to emphasize standalone rendering of the content, separate from the overall message presentation. icon: The content contains an image that serves as an iconic representation of the caller or callee, suitable for informational display by the user agent throughout a dialog. alert: This type designates content, such as an audio clip, that is meant to alert the user to an incoming request. It might be rendered as a ringtone, for example, following the receipt of a 180 Ringing response. In cases where the Content-Disposition header is omitted, the handling defaults based on content type. For example, bodies of type application/sdp are assumed to have a "session" disposition, while others are treated as "render." Handling Parameters: optional: The content may be ignored if not recognized. required (default): Indicates that the content must be processed. If the handling parameter is missing, this value is assumed by default.
Content-Length	827	Unsigned32	3GPP
Indicates the size, in octets, of the message body transmitted in a SIP message. This AVP adheres to the standards specified in [RFC3261], section 20.14, where the Content-Length header is crucial for determining the precise length of the message body to be read and processed by the recipient. This value does not include the CRLF (Carriage Return Line Feed) that separates the message headers from the body. It represents only the message-body size itself. For protocols that stream data, like TCP, the Content-Length field is mandatory to define the exact end of the message body. Valid Range: Any value greater than or equal to zero. Zero value: Indicates the absence of a message body. Non-zero value: Represents the exact size in octets of the message body content. Compact form: The Content-Length AVP may use the shorthand form “l”. Example Values: Content-Length: 349 l: 173
Content-Size	1206	Unsigned32	3GPP
Specifies the size, in bytes, of the content of a specific type. It provides information on the amount of data associated with the specified content type in a message.
Content-Type	826	UTF8String	3GPP
Specifies the media type of the message body in a SIP message, as outlined in [RFC3261], section 20.15. This AVP is mandatory when the message body is not empty, ensuring that the recipient correctly interprets the type of data received. If the body is empty and a Content-Type header is provided, it signifies that the message body for the specified media type has zero length (e.g., an empty audio file). The Content-Type AVP supports various media types, including common formats like application/sdp for session descriptions and text/html for HTML content. This AVP also permits parameters like character encoding, for instance, charset=ISO-8859-4 for text-based data. Compact form: In shorthand, the Content-Type AVP can be represented as “c”. Example Values: Content-Type: application/sdp c: text/html; charset=ISO-8859-4
Control-Memory-Size	1002	Unsigned32	oneM2M
Represents the storage memory (in bytes) used for storing control-related information associated with an M2M event record. This excludes data storage linked to container-related operations.
Coverage-Info	3459	Grouped	3GPP
Provides details about the coverage status of the UE, indicating whether it is served by E-UTRAN. It also includes the timestamp when the coverage status last changed and may list location changes (such as ECGI changes) with their associated timestamps.
Coverage-Status	3428	Enumerated	3GPP
Indicates whether the UE is in or out of E-UTRAN coverage. Enumerated values: 0: Out of coverage 1: In coverage
CP-CIoT-EPS-Optimisation-Indicator	3930	Enumerated	3GPP
Specifies whether the Control Plane CIoT (Cellular Internet of Things) EPS (Evolved Packet System) optimization is active for data transfer between the Packet Data Network (PDN) connection and the User Equipment (UE). This AVP is crucial in IoT scenarios, where data efficiency and reduced overhead are often prioritized, allowing for lightweight data transfers over the control plane rather than the user plane. This optimization can enhance battery life and reduce signaling traffic for IoT devices. Enumerated values: 0: Not Apply. 1: Apply.
CPDT-Information	3927	Grouped	3GPP
Contains specific information elements related to CP (Control Plane) data transfer services. This AVP is utilized in scenarios where additional control plane data service parameters need to be communicated, particularly for the NIDD (Non-IP Data Delivery) service provided through the SCEF (Service Capability Exposure Function) and for nodes handling control plane optimizations. The AVP structure is defined as follows: External-Identifier: Uniquely identifies an external entity associated with the control plane data service. SCEF-ID: Specifies the identifier of the SCEF responsible for facilitating control plane communication for non-IP data transfer. Serving Node Identity: Identifies the serving node involved in the control plane data transfer, ensuring accurate routing and service continuity. SGW-Change: An enumeration indicating whether a change in the Serving Gateway (SGW) has occurred. This is relevant for network architecture updates and mobility scenarios within the PDN connection. NIDD-submission: Contains details on the NIDD submission state or requirements, providing additional context on data transmission settings specific to non-IP data handling.
CSG-Access-Mode	2317	Enumerated	3GPP
Indicates how users are allowed to access a Closed Subscriber Group (CSG) cell. The CSG cell is a small subset of a mobile network that allows access only to specific users. Enumerated values:: Closed Mode (0): Only authorized members of the CSG can access the network through this cell. Hybrid Mode (1): Both CSG members and non-members can access the cell, but non-members may have limited service options. This AVP is important for operators managing differentiated access rights in specific parts of their network, particularly in private LTE/5G networks.
CSG-Membership-Indication	2318	Enumerated	3GPP
Informs the network whether a user (UE) is a member of a particular CSG (Closed Subscriber Group) when accessing the network in hybrid mode. This AVP is essential in determining the user's privileges or restrictions in the hybrid CSG environment. Values: Not CSG Member (0): The user is not a member and may have restricted access. CSG Member (1): The user is part of the group and has full access to the services within the CSG cell.
CUG-Information	2304	OctetString	3GPP
Carries the Closed User Group (CUG) membership data. CUGs are used to restrict mobile communication within a specified group of users (like a company or organization). The AVP typically contains a unique "CUG Interlock Code," which allows network systems to verify whether a user belongs to a particular CUG. This AVP plays a key role in supplementary services such as MMTel (Multimedia Telephony) by ensuring calls and services are correctly routed and billed according to the user’s membership in a CUG.
Current-Number-Members	1003	Unsigned32	oneM2M
Used in group-based communication scenarios, particularly in IoT and M2M networks. It provides the current count of members in a group, which can fluctuate based on the responses to queries sent to group members. This AVP is particularly important in applications where devices or users communicate as part of a larger group, and understanding how many members are actively participating is critical for operations, resource allocation, or billing.
Current-Tariff	2056	Grouped	3GPP
Encapsulates information on the active tariff applied for service usage. This AVP is crucial in cost calculation, providing a structured formula to compute charges based on usage. The calculation is influenced by associated Used-Service-Unit values, and the result is expressed in a specified currency. The AVP structure is defined as follows: Currency-Code: Represents the currency in which the cost is calculated, following the standard ISO 4217 numeric code. Scale-Factor: A multiplier applied to the computed sum of rate elements, scaling the cost proportionally to service or pricing requirements. Rate-Element: A list of Rate-Element AVPs, where each element contributes to the overall cost formula. Multiple rate elements are summed, then scaled by the Scale-Factor to determine the final tariff amount.
Data-Coding-Scheme	2001	Integer32	3GPP
The Data-Coding-Scheme AVP is used to specify the encoding format of the message content. In the context of Short Message Service (SMS), the specific data coding schemes follow the rules defined in 3GPP [TS 23.040], [TS 23.038], which outlines how messages are encoded for different languages, alphabets, or specific application purposes. For example, the coding scheme can specify if the message uses a 7-bit GSM encoding or a Unicode format. This AVP ensures proper interpretation of the message content across network nodes.
Data-Memory-Size	1004	Unsigned32	oneM2M
Represents the storage memory size, in bytes, used to store data associated with M2M (Machine-to-Machine) operations, specifically related to container storage. In M2M systems, data containers may hold various pieces of information, such as sensor readings or other types of machine-generated data, and this AVP defines the amount of memory reserved for these data containers. This is crucial for resource management in M2M networks where memory is allocated dynamically based on the size of incoming data.
Deferred-Location-Event-Type	1230	UTF8String	3GPP
Provides information about location-related events that occur at a deferred time. In scenarios where the network needs to report location information of a user or device, but not in real-time, this AVP is used to identify the type of event that triggered the location request (e.g., device movement, service access). The deferred nature of this AVP allows the network to collect and report location data based on pre-set conditions, optimizing resource use and reducing the need for constant real-time monitoring.
Delivery-Report-Requested	1216	Enumerated	3GPP
Indicates whether the originator of a message has requested a delivery report. A delivery report provides confirmation that the message has been successfully delivered to its intended recipient. Enumerated values: 0 (No): No delivery report was requested. 1 (Yes): A delivery report was requested.
Destination-Interface	2002	Grouped	3GPP
Provides the interface-related information where the message is to be delivered. This AVP is essential for routing messages to the correct interface on a network node. The AVP structure is defined as follows: Interface-Id: Identifies the specific interface. Interface-Text: A textual description of the interface. Interface-Port: The port number used by the interface. Interface-Type: Specifies the type of interface, such as SIP or Diameter. This AVP is crucial in ensuring that messages are routed correctly to their intended destination within a network.
Diagnostics	2039	Integer32	3GPP
Provides detailed information about the cause of an event or failure in a PCN (Packet Core Network) node. This AVP complements the Change-Condition AVP and is used in offline charging scenarios. It provides network operators with insight into issues that might occur during charging, enabling detailed troubleshooting and accurate reporting.
Discoveree-UE-HPLMN-Identifier	4402	UTF8String	3GPP
Contains the Home Public Land Mobile Network (HPLMN) identifier of the user equipment (UE) that is being discovered. This AVP helps in identifying the home network of the UE during discovery procedures. The HPLMN identifier is essential for routing and processing network requests related to UE discovery in multi-network environments.
Discoveree-UE-VPLMN-Identifier	4403	UTF8String	3GPP
Contains the Visited Public Land Mobile Network (VPLMN) identifier of the user equipment (UE) that is being discovered. It helps identify the network that the UE is currently visiting, which is crucial for handling roaming and network discovery requests.
Discoverer-UE-HPLMN-Identifier	4404	UTF8String	3GPP
Contains the Home Public Land Mobile Network (HPLMN) identifier of the user equipment (UE) initiating the discovery. This AVP plays a key role in identifying the home network of the UE that is making a discovery request, ensuring proper routing and handling of network requests.
Discoverer-UE-VPLMN-Identifier	4405	UTF8String	3GPP
Contains the Visited Public Land Mobile Network (VPLMN) identifier of the user equipment (UE) initiating the discovery. This AVP is important for identifying the network that the UE is visiting when it initiates a discovery request, enabling efficient handling of roaming and network interactions.
Domain-Name	1200	UTF8String	3GPP
Contains a fully qualified domain name (FQDN) as specified by the Diameter protocol. This AVP is used for identifying domains within a network, often in scenarios involving routing or addressing information. The FQDN is an essential part of DNS lookups and is used to map human-readable domain names to IP addresses. This AVP helps to ensure that requests are routed to the correct domain within networked services.
DRM-Content	1221	Enumerated	3GPP
Indicates whether the multimedia message (MM) contains DRM (Digital Rights Management) protected content. DRM technologies are used to protect digital content from unauthorized use or distribution. Values: 0 (No): The content is not DRM-protected. 1 (Yes): The content is DRM-protected.
Dynamic-Address-Flag	2051	Enumerated	3GPP
Specifies whether a Packet Data Protocol (PDP) context or PDN address is statically or dynamically allocated. This AVP is crucial in defining how network addresses are assigned in mobile or IP-based networks. Enumerated values: 0 (Static): The address is statically assigned. 1 (Dynamic): The address is dynamically allocated.
Dynamic-Address-Flag-Extension	2068	Enumerated	3GPP
Extends the Dynamic-Address-Flag AVP by indicating whether the IPv4 address associated with a PDN type of IPv4v6 is dynamically allocated. This AVP clarifies how the IPv4 component of a dual-stack PDN connection is handled. Values: 0 (Static): The IPv4 address is statically allocated. 1 (Dynamic): The IPv4 address is dynamically allocated.
Early-Media-Description	1272	Grouped	3GPP
Encapsulates details of an early media session, including session and media parameters, and timestamps relevant to media components that have been activated prior to the final response in a SIP session establishment. This AVP allows tracking of media components' status as they change following SDP signaling in early SIP dialogs (e.g., before receiving a final response to an initial SIP INVITE). The AVP structure is defined as follows: SDP-TimeStamps: Contains timestamps that indicate when specific SDP media components were set to active, allowing for time-based tracking of early media activation. SDP-Media-Component: A list of SDP-Media-Component AVPs, each describing individual media streams involved in the session, such as audio or video streams, with their specific parameters. SDP-Session-Description: A list of SDP (Session Description Protocol) strings describing the session’s attributes. These strings provide additional metadata about the session, aligning with the SDP protocol specifications. The Early-Media-Description AVP facilitates the identification and management of active and inactive media states based on SDP attributes. Media marked with "a=inactive" or assigned zero bandwidth is considered inactive, while media marked with direction attributes like "a=recvonly", "a=sendonly", or "a=sendrecv" is considered active.
Enhanced-Diagnostics	3901	Grouped	3GPP
Provides detailed diagnostic information for session releases, enhancing the Change-Condition AVP by offering additional causes for session termination from PCN nodes in offline charging contexts. As a Grouped AVP, it allows multiple release causes to be provided for a comprehensive diagnostic view. The AVP structure is defined as follows: RAN-NAS-Release-Cause: Represents the specific cause for release as detected by the Radio Access Network (RAN) or NAS (Non-Access Stratum) layers. Multiple RAN-NAS-Release-Cause values can be included, allowing a nuanced representation of potential release causes associated with a single session.
Envelope	1266	Grouped	3GPP
Provides information on a specific time envelope for usage reporting, encapsulating the start and optional end times of the envelope along with volume data or service-specific units, if applicable. This AVP is instrumental in tracking and reporting usage within specified time frames and is particularly useful for services that require precise tracking of data usage, as outlined in clauses 6.5.6 and 6.5.7 of the 3GPP [TS32.299]. The AVP structure is defined as follows: Envelope-Start-Time: Mandatory. This field captures the exact time when the envelope begins. If the envelope starts before the current reporting interval, this field still reflects the actual start time of the envelope. Envelope-End-Time: Optional. Represents the time when the envelope ends. If an envelope has not concluded at the time of reporting, this field is omitted. CC-Total-Octets: Optional. Indicates the total data volume in octets from the start of the envelope. CC-Input-Octets: Optional. Specifies the volume of incoming data in octets within the envelope. CC-Output-Octets: Optional. Specifies the volume of outgoing data in octets within the envelope. CC-Service-Specific-Units: Optional. Contains the count of service-specific units if they were requested in the related Envelope-Reporting AVP. For cases where the envelope is closed retroactively, the client is expected to include this Envelope AVP in the next usage report. When multiple Envelope AVPs are provided, they should be listed in chronological order.
Envelope-End-Time	1267	Time	3GPP
Used to indicate the time when a time-based envelope ends. It marks the completion of a usage period for which data is being tracked, such as the end of a session or time interval for reporting purposes. If an envelope is still active, this AVP may not be present, but it is included when the envelope has definitively ended.
Envelope-Reporting	1268	Enumerated	3GPP
Dictates how the client reports time-based usage envelopes in cases where a quota is consumed in envelopes. Enumerated values: 0: DO_NOT_REPORT_ENVELOPES – No reporting of individual envelopes. 1: REPORT_ENVELOPES – Report only the envelope's start and end times. 2: REPORT_ENVELOPES_WITH_VOLUME – Report envelope times and volume of data consumed. 3: REPORT_ENVELOPES_WITH_EVENTS – Report envelope times and specific events that occurred. 4: REPORT_ENVELOPES_WITH_VOLUME_AND_EVENTS – Report envelope times, data volume, and events. This AVP is typically used in Credit-Control-Answer (CCA) messages to instruct the client on how to report usage envelopes for online or offline charging scenarios.
Envelope-Start-Time	1269	Time	3GPP
Used to indicate the start time of a time envelope. It records the exact time at which a packet of user data initiated the time-based usage report. This AVP is critical in tracking the duration of time-based usage periods, such as when charging or usage monitoring is based on time intervals.
EPDG-Address	3425	Address	3GPP
Holds the IP address of the ePDG (Evolved Packet Data Gateway) node. The ePDG is used in scenarios where a mobile device connects to the mobile core network over an untrusted non-3GPP access network, such as Wi-Fi. This AVP ensures that the ePDG node is identified for proper routing and management of the session.
Event	825	UTF8String	3GPP
Contains the content of the "Event" header, typically used in SIP signaling. This AVP is part of the information conveyed during event-based communication sessions and may hold details about the type of event (e.g., call initiation, message delivery) as specified in the SIP protocol.
Event-Charging-TimeStamp	1258	Time	3GPP
Records the exact time when an event occurred, specifically when event-based charging applies. It is used in conjunction with the CC-Service-Specific-Units AVP to track the timestamp of a chargeable event in real-time or offline charging scenarios. This AVP ensures accurate billing by capturing when the event took place, allowing for precise charge calculation and auditing.
Event-Type	823	Grouped	3GPP
Provides detailed information about the type of event or telecommunication service being charged. This AVP is used in Accounting and Credit-Control messages to indicate the nature of the event or service that generated the message. The AVP structure is defined as follows: SIP-Method: The SIP method associated with the event (e.g., INVITE, REGISTER). Event: The type of event as defined in the SIP header. Expires: Time-to-live (TTL) or expiration time of the event if applicable, as in SIP registration or subscription events.
Expires	888	Unsigned32	3GPP
Holds the expiration time for a session or event, typically used in SIP signaling. This value indicates the duration for which the session or event remains valid, as specified in the "Expires" header in the SIP message. It is particularly useful in scenarios like SIP registration, where a user's registration expires after a certain period, or in subscription-based events.
Exposure-Function-API-Information	1316	Grouped	3GPP
Facilitates the transfer of additional information specific to the Exposure Function API. This AVP encapsulates various elements necessary for API operations, including support features, content, direction, invocation details, and network element identifiers. Each component provides information on the characteristics, execution, and results of API interactions within a network. The AVP structure is defined as follows: Supported-Features: Optional. Represents a list of features supported by the API function, allowing compatibility checks and feature-specific handling within the network. API-Content: Optional. Contains the main content payload for the API, detailing the information exchanged during API interaction. API-Direction: Optional. Indicates the direction of API interaction, such as "request" or "response," which helps identify the API call flow. API-Identifier: Optional. Provides a unique identifier for the API, represented as a ByteBuf. This identifier is essential for tracking and managing API transactions. API-Invocation-Timestamp: Optional. Records the timestamp of the API invocation, providing a chronological marker for each API call. API-Network-Service-Node: Optional. Specifies the network service node responsible for handling the API request, described as an enumerated type (APINetworkServiceNodeEnum). API-Result-Code: Optional. Indicates the outcome of the API execution, represented by a result code. This field allows easy identification of successful or error responses. API-Size: Optional. Denotes the size of the API message payload, useful for managing data transfer and resource allocation. Network-Element: Optional but not defined in the provided specification. This may refer to a network component involved in the API processing. As it is unspecified, further documentation would be required. SCEF-Address: Optional. Contains the IP address of the SCEF (Service Capability Exposure Function), represented as an InetAddress. This address is crucial for routing API messages in networks supporting SCEF functionalities. SCS-AS-Address: Optional. Holds the address of the SCS-AS (Service Capability Server/Application Server), enabling API calls to be directed to the correct application server. TLTRI: Optional. A unique identifier for transactional linkage between API calls, helping in tracking and managing API requests related to long-term data retention and interchange.
External-ID	1005	UTF8String	oneM2M
Contains the external ID used for communication in machine-to-machine (M2M) or Internet of Things (IoT) networks, where applicable. This AVP follows the format specified for the M2M-Ext-ID, typically used in addressing scenarios where unique identifiers are required for communication over Mcn (Machine Communication Network). It allows for external identification of devices or entities in M2M systems, supporting efficient and scalable addressing in large networks.
FE-Identifier-List	4413	UTF8String	3GPP
Represents a list of Function Elements (FE) identifiers, as defined in [TS24.229]. These identifiers pertain to IMS network elements responsible for generating charging information. The AVP facilitates the exchange of this information via SIP signaling, helping to ensure accurate and detailed tracking of IMS network element activity for charging and accounting purposes.
File-Repair-Supported	1224	Enumerated	3GPP
Specifies whether the Multimedia Broadcast Multicast Service (MBMS) user service supports point-to-point file repair. File repair ensures that corrupted or missing data in broadcasted or multicast files can be corrected. Enumerated values: 1: SUPPORTED, indicating that file repair is available. 2: NOT_SUPPORTED, indicating that file repair is not available.
Forwarding-Pending	3415	Enumerated	3GPP
Indicates whether a call is about to be forwarded to another number. It helps manage voice call forwarding scenarios by signaling if forwarding is expected. Enumerated values: 0: Forwarding not pending, meaning the call is not expected to be forwarded. 1: Forwarding pending, meaning the call is expected to be forwarded to a different number.
From-Address	2708	UTF8String	3GPP
Holds information from the SIP "From" header field. This AVP contains the address (e.g., SIP URI) that identifies the initiator of the SIP request. The "From" address in SIP messages typically includes details about the user or entity making the request, and this AVP captures that data for further processing in Diameter-based systems. It is crucial for identifying the originator in signaling and session establishment scenarios.
GGSN-Address	847	Address	3GPP
Contains the IP address of the Gateway GPRS Support Node (GGSN), Packet Data Network Gateway (P-GW), or Session Management Function (SMF) that generated the GPRS, EPC, or 5GS Charging ID. This AVP is essential for identifying the network element responsible for handling user data sessions and plays a critical role in charging and accounting procedures across 3G, 4G, and 5G networks. The GGSN/P-GW/SMF address is used to link charging data records to the appropriate network node for accurate billing.
Group-Name	1006	UTF8String	oneM2M
Identifies the group associated with a particular request, specifically in machine-to-machine (M2M) or Internet of Things (IoT) communication contexts. It is included when the Information Node (IN) initiates a fanning operation, which involves sending requests to multiple endpoints simultaneously. The AVP captures the group name, allowing for efficient handling and tracking of operations performed on multiple entities as part of a group. This AVP corresponds to the "groupName" attribute, enabling group-based operations in M2M systems.
Hosting-CSE-ID	1007	UTF8String	oneM2M
Identifies the Hosting Common Service Entity (CSE) in machine-to-machine (M2M) or IoT communications when the receiving node is not the host of the request. The Hosting-CSE-ID is crucial for routing and managing M2M traffic, as it indicates which CSE is responsible for handling the request. The format of the CSE-ID is specified in the relevant M2M protocol standard and is used to ensure proper communication between nodes in a distributed M2M network.
IMS-Application-Reference-Identifier	2601	UTF8String	3GPP
Contains the IMS Application Reference Identifier (IARI), which is used to identify specific IMS applications. It is extracted from the SIP request and corresponds to applications defined within IMS services. This AVP is essential for routing and processing SIP-based communication services within IMS, allowing the network to apply application-specific logic based on the IARI as defined in 3GPP [TS24.229].
IMS-Charging-Identifier	841	UTF8String	3GPP
Contains the IMS Charging Identifier (ICID), which is generated by an IMS node to uniquely identify a charging session within the network. The ICID is used for billing and accounting purposes, ensuring that each session's usage is accurately recorded and billed. It plays a vital role in managing charging information for SIP sessions and other IMS-related transactions.
IMS-Communication-Service-Identifier	1281	UTF8String	3GPP
Holds the IMS Communication Service Identifier (ICSI), which identifies the specific IMS communication service being used. It is extracted from the P-Asserted-Service header of a SIP request and is used to route and apply service-specific logic for various communication services within the IMS architecture. This AVP is critical for distinguishing between different IMS services and applying appropriate policies and charging.
IMS-Emergency-Indicator	2322	Enumerated	3GPP
Indicates whether an IMS session or registration is identified as an emergency session. This AVP helps distinguish between regular and emergency sessions or registrations, which is critical in prioritizing emergency communication and routing within the IMS network. Enumerated values: 0 Non Emergency: Indicates that the IMS session or registration is a standard session and does not carry emergency designation. 1 Emergency: Marks the session or registration as an IMS emergency, which could trigger special handling, such as priority routing and resource allocation, to ensure that emergency calls are processed with high reliability and speed. If this AVP is absent, the session or registration is treated as non-emergency by default.
IMS-Information	876	Grouped	3GPP
Designed to encapsulate additional service-specific details for an IMS session. Its purpose is to convey various attributes associated with the IMS service and its interactions within the IMS network. These details include session characteristics, roles, parties involved, routing information, timestamps, and other specific service parameters, making it a comprehensive AVP for managing and tracking IMS sessions. The AVP structure is defined as follows: Event-Type: Specifies the type of event occurring in the IMS session. Role-Of-Node: Indicates the node’s role in the IMS session (e.g., originating or terminating). Node-Functionality: Describes the functional role of the node (mandatory). User-Session-Id: Unique identifier for the user session. Outgoing-Session-Id: Identifier for the outgoing session leg. Session-Priority: Defines the priority level of the session. Calling-Party-Address: List of addresses for the calling party. Called-Party-Address: Address of the called party. Called-Asserted-Identity: List of asserted identities for the called party. Called-Identity-Change: AVP providing information on any change in the terminating identity. Number-Portability-Routing-Information: Number portability information for routing purposes. Carrier-Select-Routing-Information: Carrier selection information for routing. Alternate-Charged-Party-Address: Address for an alternate charged party. Requested-Party-Address: List of addresses for requested parties in the session. Associated-URI: List of associated URIs in the session. Time-Stamps: AVP containing timestamps related to session events. Application-Server-Information: List of application server information involved in the session. Inter-Operator-Identifier: Identifiers for inter-operator interactions. Transit-IOI-List: List of transit IOIs for routing purposes. IMS-Charging-Identifier: Unique identifier for IMS session charging. SDP-Session-Description: List of SDP session descriptions. SDP-Media-Component: List of SDP media components associated with the session. Served-Party-IP-Address: IP address of the served party. Server-Capabilities: Capabilities of the server handling the session. Trunk-Group-ID: Identifier for trunk groups. Bearer-Service: Service information related to the bearer. Service-Id: Identifier for the service. Service-Specific-Info: List of service-specific information AVPs. Message-Body: List of message bodies within the IMS session. Cause-Code: Code describing the cause of session termination or interruption. Reason-Header: List of reason headers indicating reasons for session state. Access-Network-Information: Information about the access network. Cellular-Network-Information: Network-specific information for cellular networks. Early-Media-Description: Early media description elements. IMS-Communication-Service-Identifier: Identifier for IMS communication services. IMS-Application-Reference-Identifier: Application-specific identifier for the IMS session. Online-Charging-Flag: Flag indicating online charging presence. Real-Time-Tariff-Information: Real-time tariff information for the session. Account-Expiration: Expiration date of the account. Initial-IMS-Charging-Identifier: Initial charging identifier for the IMS session. NNI-Information: Information for network-to-network interfaces. From-Address: Source address for the session. IMS-Emergency-Indicator: Flag indicating if the session is an emergency. IMS-Visited-Network-Identifier: Identifier for the visited network in the IMS session. Access-Network-Info-Change: List of changes to access network information. Access-Transfer-Information: List of access transfer information AVPs. Related-IMS-Charging-Identifier: Identifier for a related IMS charging instance. Related-IMS-Charging-Identifier-Node: Node information related to the IMS charging instance. Route-Header-Received: Received route header information. Route-Header-Transmitted: Transmitted route header information. Instance-Id: Instance ID for the IMS session. TAD-Identifier: Identifier for TAD (Traffic Activity Data). FE-Identifier-List: List of functional element identifiers.
IMSI-Unauthenticated-Flag	2308	Enumerated	3GPP
Indicates whether the served IMSI (International Mobile Subscriber Identity) is authenticated or not. This AVP is particularly relevant when emergency bearer services are provided, where the user’s IMSI may not be authenticated. Enumerated values: 0 (Authenticated): The IMSI has been authenticated. 1 (Unauthenticated): The IMSI has not been authenticated, often associated with emergency bearer services. If this AVP is not present, it implies that the served IMSI is authenticated.
IMS-Visited-Network-Identifier	2713	UTF8String	3GPP
Holds the content of the SIP P-header "P-Visited-Network-ID," formatted as a UTF8 string, as specified in 3GPP [TS24.229]. This AVP provides critical information about the network location of the P-CSCF (Proxy Call Session Control Function) and is used in IMS roaming scenarios. It supports both local breakout and home-routed architectures for voice over IMS: Local Breakout: For this architecture, the IMS-Visited-Network-Identifier AVP contains a pre-provisioned identifier string representing the network of the P-CSCF within the home network. This helps to establish a context for the local breakout network while maintaining the user's home network as a reference. Home Routed Traffic: In this scenario, the AVP string identifies the visited network of the User Equipment (UE) and signals that the P-CSCF is in the home network, helping to distinguish where the session is managed in home-routed IMS setups.
Incoming-Trunk-Group-ID	852	UTF8String	3GPP
Identifies the incoming PSTN (Public Switched Telephone Network) leg in the session. It is used to distinguish the incoming trunk group for call routing and charging purposes, especially when multiple trunk groups are involved in the session.
Incremental-Cost	2062	Grouped	3GPP
Holds the incremental cost of an ongoing session since the last Advice of Charge (AoC) interaction. This AVP is particularly useful in real-time charging scenarios where cost updates are provided during a session. The AVP structure is defined as follows: Value-Digits: (Required) The digits representing the incremental cost. Exponent: (Optional) The exponent used to scale the value digits. If the Exponent AVP is not provided, the client assumes an exponent value of zero.
Initial-IMS-Charging-Identifier	2321	UTF8String	3GPP
Holds the Initial IMS Charging Identifier (ICID) generated by an IMS node for the initial SIP session created for IMS service continuity. This identifier is crucial for tracking and managing charging information across different IMS sessions, particularly during service continuity events.
Instance-Id	3402	UTF8String	3GPP
Contains a unique URN (Uniform Resource Name) generated by the device, which identifies the specific device among all other devices. This Instance-Id is carried in the Contact header of a SIP request associated with the served user. It is crucial for identifying the device in network operations that involve SIP communication.
Interface-Id	2003	UTF8String	3GPP
Holds the interface identification information provided by the messaging node (either the originator or destination of the message). This AVP is used to uniquely identify an interface related to a specific charging event or communication session within the network.
Interface-Port	2004	UTF8String	3GPP
Contains the port identification or details about the transport layer port used by the application associated with a charging event. This information is critical for understanding the network and transport layer characteristics of the communication for charging and logging purposes.
Interface-Text	2005	UTF8String	3GPP
Consolidates information about the application or interface related to a charging event. This AVP provides additional textual information that may be necessary for billing, diagnostics, or logging, offering context about the application responsible for generating the traffic.
Interface-Type	2006	Enumerated	3GPP
Contains information about the type of interface or the nature of the transaction taking place in the messaging node that triggered the charging event. Enumerated values: 0 (Unknown): The interface type is unknown. 1 (MOBILE_ORIGINATING): The event originated from a mobile device. 2 (MOBILE_TERMINATING): The event terminated at a mobile device. 3 (APPLICATION_ORIGINATING): The event was originated by an application. 4 (APPLICATION_TERMINATION): The event terminated at an application.
Inter-Operator-Identifier	838	Grouped	3GPP
Identifies network neighbors involved in a communication session, specifying both originating and terminating operators as exchanged via SIP signaling. It is defined in [RFC7315]. The AVP structure is defined as follows: Originating-IOI: Identifies the operator from which the session originated. Terminating-IOI: Identifies the operator where the session terminates.
Inter-UE-Transfer	3902	Enumerated	3GPP
Indicates whether the type of transfer is intra-UE (within the same user equipment) or inter-UE (between different user equipment). If this AVP is not present, the default assumption is that the transfer is intra-UE. Enumerated values: 0 Intra-UE transfer: The transfer occurs within the same user equipment. 1 Inter-UE transfer: The transfer occurs between different user equipment.
IP-Realm-Default-Indication	2603	Enumerated	3GPP
Indicates whether the IP realm used for the SDP (Session Description Protocol) media component is the default IP realm. This information is essential in media communication sessions. Enumerated values: 0 Default IP Realm Not Used: The default IP realm is not used. 1 Default IP Realm Used: The default IP realm is used.
ISUP-Cause	3416	Grouped	3GPP
Provides information about the reason for the release of a voice call service in circuit-switched (CS) networks. It is used primarily in IMS (IP Multimedia Subsystem) charging scenarios. The AVP structure is defined as follows: ISUP-Cause-Location: Identifies the network location where the event that caused the call release occurred. ISUP-Cause-Value: Holds the ISUP (ISDN User Part) cause code for the call release. ISUP-Cause-Diagnostics: Contains diagnostic information related to the call release.
ISUP-Cause-Diagnostics	3422	OctetString	3GPP
Holds the diagnostic field related to the release of a voice call service. In IMS charging scenarios, it contains the diagnostics for circuit-switched (CS) calls. The diagnostics provide further details about the reasons for the call release, complementing the ISUP cause code. The specific values are defined in [TS29.078].
ISUP-Cause-Location	3423	Unsigned32	3GPP
Identifies the network location where the event that triggered the call release occurred. It is typically used in conjunction with the ISUP-Cause AVP to provide a full context of the release scenario. The supported values are defined in [TS29.078], and they help pinpoint whether the issue occurred in the user network, transit network, or another network location.
ISUP-Cause-Value	3424	Unsigned32	3GPP
Identifies the reason a voice call service is released. In the context of IMS charging, this AVP indicates the cause for the release of a circuit-switched (CS) call. The specific values are defined in [TS29.078]. It is used to convey detailed information about the call release event, such as network errors, user actions, or system conditions leading to the termination of the call.
Language	3914	UTF8String	3GPP
Specifies the language of an announcement that should be played. It contains a language code in accordance with [RFC3066], enabling applications to select appropriate language resources, such as voice prompts or announcements, for a given user or session.
Layer-2-Group-ID	3429	OctetString	3GPP
Carries the identifier of a ProSe (Proximity-based Services) communication group, which uniquely represents a specific ProSe Direct Communication session. Known as the "ProSe Layer-2 Group ID" in [TS23.303], it is included in CDRs (Charging Data Records) for each participant in the communication group. This AVP enables efficient tracking and billing for one-to-many ProSe Direct Communication sessions, typically used in public safety and group communication scenarios.
LCS-APN	1231	UTF8String	3GPP
Holds the Access Point Name (APN) of the Location-based Services (LCS) Client. This AVP identifies the APN through which the LCS Client accesses location-based services. In cases where a device or application requires location services, this APN serves as a reference point to route location requests, making it a key element for location-based services within mobile networks.
LCS-Client-Dialed-By-MS	1233	UTF8String	3GPP
Contains the number of the LCS (Location Services) Client dialed by the User Equipment (UE). This AVP is primarily used when a user initiates a location request by dialing a specific number associated with an LCS Client, allowing the network to track and route location-based queries initiated directly by the user.
LCS-Client-External-ID	1234	UTF8String	3GPP
Identifies the external Location Services (LCS) client, which is an entity outside the mobile network that interacts with the network's location-based services. This identifier allows external systems or applications to be recognized when requesting location data for specific use cases, such as tracking, emergency response, or location-based advertising. The ID format follows network-specific standards for identifying external clients.
LCS-Client-ID	1232	Grouped	3GPP
Contains essential details about the Location Services (LCS) client involved in a location-based request. This information includes various attributes identifying and characterizing the client. The AVP's structure allows for multiple identifiers, such as type, external ID, name, and associated APN. By consolidating this information, the AVP enables the network to differentiate between LCS clients, identify specific applications, and manage client requests for location services. The AVP structure is defined as follows: LCS-Client-Type: Indicates the client type (e.g., emergency services). LCS-Client-External-ID: Uniquely identifies external LCS clients. LCS-Client-Dialed-By-MS: Holds the dialed number when user-initiated. LCS-Client-Name: Specifies the client's display name. LCS-APN: Identifies the APN associated with the LCS client. LCS-Requestor-ID: Represents the identity of the user or system making the request.
LCS-Client-Name	1235	Grouped	3GPP
Provides detailed information about the name of the LCS client, which is often displayed to users during location-based interactions. The AVP structure is defined as follows: LCS-Data-Coding-Scheme: Specifies the character encoding for the name. LCS-Name-String: Contains the actual name of the LCS client, encoded based on the data-coding scheme. LCS-Format-Indicator: Describes the name's format, which could vary by client type or network specifications. These components ensure that the client name is properly represented, displayed, and managed across different network and user environments, maintaining clarity and consistency.
LCS-Client-Type	1241	Enumerated	3GPP
Identifies the type of services requested by a Location Services (LCS) client, enabling the network to categorize requests based on the service needs. Enumerated values: 0 EMERGENCY_SERVICES: Indicates requests related to emergency services, enabling immediate response for public safety. 1 VALUE_ADDED_SERVICES: For commercial or personalized location-based services. 2 PLMN_OPERATOR_SERVICES: Services provided directly by the operator within their Public Land Mobile Network (PLMN). 3 LAWFUL_INTERCEPT_SERVICES: Location services for lawful interception purposes, supporting authorized monitoring.
LCS-Data-Coding-Scheme	1236	UTF8String	3GPP
Specifies the encoding format, alphabet, and language used in location-based services communication, ensuring that any textual data adheres to specific linguistic or regional standards. This AVP facilitates accurate display and processing of language-dependent information, particularly for names, addresses, and other user-facing data.
LCS-Format-Indicator	1237	Enumerated	3GPP
Defines the format type for the LCS client's name. This indicator informs the system how the client's identity is represented. Enumerated values: 0 LOGICAL_NAME: A descriptive, logical name for the client. 1 EMAIL_ADDRESS: Identifies the client using an email address. 2 MSISDN: The Mobile Station International Subscriber Directory Number, used in telecommunications. 3 URL: A web URL identifying the client. 4 SIP_URL: A SIP (Session Initiation Protocol) URL for clients connected via SIP services.
LCS-Information	878	Grouped	3GPP
Aggregates specific details about the LCS service interaction, facilitating the inclusion of various client-related and location-specific data. This grouped AVP allows for the transmission of detailed LCS session data. The AVP structure is defined as follows: LCS-Client-ID: Identifies the LCS client requesting location information. Location-Type: Specifies the nature of the location request (e.g., immediate or periodic). Location-Estimate: Contains an approximate or precise estimate of the client's location. Positioning-Data: Holds additional positioning information, often network or technology-specific. 3GPP-IMSI: The IMSI (International Mobile Subscriber Identity) for identifying the user. MSISDN: The phone number (Mobile Station ISDN) associated with the client’s mobile subscription.
LCS-Name-String	1238	UTF8String	3GPP
Represents the name of the LCS Client in a human-readable format. This AVP serves as the identifier of the client, providing a clear label that can be displayed in service records or used within system logs to track specific client requests.
LCS-Requestor-ID	1239	Grouped	3GPP
Holds the identification information for the requestor of an LCS service. This AVP allows systems to identify the requestor associated with a particular LCS request, which is critical for tracking, auditing, and authorizing access to location data. The AVP structure is defined as follows: LCS-Data-Coding-Scheme: Specifies the encoding format, facilitating correct interpretation of language and character set in the requestor's name or ID. LCS-Requestor-ID-String: The actual identifier for the requestor, such as an MSISDN or a logical name.
LCS-Requestor-ID-String	1240	UTF8String	3GPP
Contains a unique identifier for the requestor, which may take forms such as an MSISDN (Mobile Station International Subscriber Directory Number) or a logical name. This AVP provides a standardized reference for identifying the party requesting location-based services, aiding in client tracking and service delivery.
Local-GW-Inserted-Indication	2604	Enumerated	3GPP
Indicates whether a local Gateway (GW), such as a Transit Gateway (TrGW) or IMS Access Gateway (IMS-AGW), has been inserted for the SDP media component. This AVP helps in determining the configuration of the session, specifically if local GW resources are being utilized for media relay. Enumerated values: 0 Local GW Not Inserted: Indicates that no local GW is in place for the session. 1 Local GW Inserted: Confirms that a local GW is in use, which may affect media handling, routing, or quality.
Local-Sequence-Number	2063	Unsigned32	3GPP
Holds a sequence number associated with the service data container, incremented by one for each container closed. This AVP enables the tracking of service data containers in sequential order, ensuring proper organization and processing of service events within the session.
Location-Estimate	1242	OctetString	3GPP
Provides an estimated geographic location of a mobile station (MS), including universal coordinates and the accuracy of the estimate. This AVP is structured according to the geographical area description specified in [TS23.032] and allows precise location tracking of a mobile user within defined accuracy limits.
Location-Estimate-Type	1243	Enumerated	3GPP
Specifies the type of location estimate being provided. Enumerated values: 0 CURRENT_LOCATION: Request for the current location of the MS. 1 CURRENT_LAST_KNOWN_LOCATION: Last known location of the MS. 2 INITIAL_LOCATION: Initial location at the start of the session. 3 ACTIVATE_DEFERRED_LOCATION: Activate deferred location updates. 4 CANCEL_DEFERRED_LOCATION: Cancel deferred location requests.
Location-Info	3460	Grouped	3GPP
Contains detailed information on a user’s current location, including Enhanced Cell Global Identity (ECGI) and a timestamp for when the location was changed. The AVP structure is defined as follows: 3GPP-User-Location-Info: Information about the user's current location in the network. Change-Time: Timestamp indicating when the location was last updated.
Location-Type	1244	Grouped	3GPP
Used to specify the type of location estimate requested by the LCS client. The AVP structure is defined as follows: Location-Estimate-Type: Indicates the type of location estimate desired (e.g., current location, initial location). Deferred-Location-Event-Type: Specifies an event type if deferred location estimation is requested.
Logical-Access-ID	13019	OctetString	ETSI
Holds either a Circuit-ID, as defined in [RFC3046], or a technology-independent identifier, allowing identification of a logical access point within the network. In cases like xDSL/ATM, the Logical Access ID may include VP (Virtual Path) and VC (Virtual Channel) information, which helps specify the exact channel carrying the traffic.
Low-Balance-Indication	2020	Enumerated	3GPP
Alerts if a subscriber’s account balance has fallen below a specified threshold. This indicator helps notify users of the need to top up their balance. Enumerated values: 0 NOT-APPLICABLE: No low balance indication. 1 YES: Balance is low, requiring attention.
Low-Priority-Indicator	2602	Enumerated	3GPP
Signifies whether a PDN connection has a low priority, particularly useful in Machine-Type Communications (MTC) where lower priority levels may be sufficient. Enumerated values: 0 NO: The connection does not have low priority. 1 YES: The connection is marked as low priority.
M2M-Event-Record-Timestamp	1010	Time	oneM2M
Records the exact time when an M2M event occurred. This AVP helps maintain accurate logs for events related to M2M transactions, aiding in precise tracking and monitoring of interactions within the M2M infrastructure.
M2M-Information	1011	Grouped	oneM2M
Enables the transmission of specific service information elements essential for OneM2M-specific charging. This AVP plays a crucial role in managing and billing Machine-to-Machine (M2M) communication services. It consolidates various parameters that provide context about the M2M session and communication specifics. The AVP structure is defined as follows: Application-Entity-ID: Identifies the application entity involved in the M2M session, crucial for tracking and billing purposes. External-ID: A unique external identifier used to differentiate the M2M entities. Receiver and Originator: Define the source and destination of the communication, detailing the direction of the message flow. Hosting-CSE-ID and Target-ID: Identifiers for the hosting Common Services Entity (CSE) and the target M2M resource, respectively. Protocol-Type and Request-Operation: Specify the protocol and the operation requested in the M2M communication. Request-Headers-Size, Request-Body-Size, Response-Headers-Size, Response-Body-Size: Define the size of the headers and body for both requests and responses, contributing to detailed data usage records. Response-Status-Code: Enumerates the status of the response, useful for error handling and diagnostics. Rating-Group: Specifies the rating group for categorizing the charging based on the M2M activity. M2M-Event-Record-Timestamp: Records the timestamp for the event, essential for chronological tracking. Control-Memory-Size and Data-Memory-Size: Capture the memory allocations, providing insight into resource utilization. Access-Network-Identifier: Identifies the network through which the M2M data was transmitted. Occupancy: Specifies the usage density or occupancy level for M2M communication within a given timeframe. Group-Name, Maximum-Number-Members, Current-Number-Members, Subgroup-Name: Group-related information, particularly useful for M2M sessions involving multiple entities. Node-Id: Uniquely identifies the node handling the M2M session, helping in pinpointing the specific machine resource.
Maximum-Number-Members	1009	Unsigned32	oneM2M
Defines the upper limit on the number of members allowed in a group during the Create and Update operations. This AVP supports group management within M2M communications, helping to enforce constraints on group size as defined by the "maxNrOfMembers" attribute.
MBMS-Charged-Party	2323	Enumerated	3GPP
Identifies the party responsible for the charges in the generated CDR. Enumerated values: 0: Content Provider – The content provider bears the charges. 1: Subscriber – The subscriber is responsible for the charges.
MBMS-GW-Address	2307	Address	3GPP
Holds the IP address of the MBMS Gateway (GW) responsible for generating the MBMS Charging ID. This AVP is used when the MBMS Gateway operates as a standalone entity, providing a critical address for identifying the charging entity within the MBMS infrastructure.
MBMS-Information	880	Grouped	3GPP
Provides essential service-specific data related to Multimedia Broadcast Multicast Service (MBMS) within the Diameter protocol. It is used to specify details about the MBMS session, user service type, and network requirements, among other properties. The AVP structure is defined as follows: TMGI: Temporary Mobile Group Identity, which uniquely identifies the MBMS service session. MBMS-Service-Type: Defines the type of MBMS service, represented by an enumerated value. MBMS-User-Service-Type: Specifies the user service type for MBMS, allowing for further classification within MBMS services. File-Repair-Supported: Indicates if file repair is supported in the MBMS service. Required-MBMS-Bearer-Capabilities: Specifies any necessary bearer capabilities for MBMS. MBMS-2G-3G-Indicator: Enum that indicates compatibility with 2G or 3G network standards. RAI: Routing Area Identity, providing additional network location information. MBMS-Service-Area: Lists the geographical or service area where MBMS is accessible. MBMS-Session-Identity: A unique identifier for the session within MBMS. CN-IP-Multicast-Distribution: Enum specifying multicast distribution properties in the core network IP. MBMS-GW-Address: IP address of the MBMS Gateway. MBMS-Charged-Party: Identifies the entity responsible for charges in the MBMS service. MSISDN: Lists of MSISDNs (Mobile Station International Subscriber Directory Numbers) for the MBMS users. MBMS-Data-Transfer-Start: Timestamp for the start of MBMS data transfer. MBMS-Data-Transfer-Stop: Timestamp for the stop of MBMS data transfer.
MBMS-User-Service-Type	1225	Enumerated	3GPP
Description: Specifies the type of MBMS (Multimedia Broadcast Multicast Service) user service being delivered. Enumerated values: 1 DOWNLOAD: The service type is download. 2 STREAMING: The service type is streaming.
Media-Initiator-Flag	882	Enumerated	3GPP
Indicates which party requested the session modification in IMS charging. Enumerated values: 0 called party: Modification initiated by the called party. 1 calling party: Modification initiated by the calling party. 2 unknown: Initiator of the modification is unknown.
Media-Initiator-Party	1288	UTF8String	3GPP
Contains the address (SIP URI or Tel URI) of the party (Public User ID or Public Service ID) who initiates a media action, such as adding/removing or connecting/disconnecting the media. Primarily used for PoC (Push-to-talk over Cellular) charging.
Message-Body	889	Grouped	3GPP
Holds information about message bodies, excluding those with Content-Type = "application-sdp". The AVP structure is defined as follows: Content-Type (Mandatory): Specifies the media type of the message body. Content-Length (Mandatory): Specifies the length of the message body. Content-Disposition (Optional): Provides handling instructions for the content. Originator (Optional): Enum indicating the originator of the message.
Message-Class	1213	Grouped	3GPP
Contains class information for the message. The AVP structure is defined as follows: Class-Identifier (Optional): An enumerated identifier for the message class. Token-Text (Optional): A string providing additional token information related to the message class.
Message-ID	1210	UTF8String	3GPP
Holds the unique identification of the message being charged.
Message-Size	1212	Unsigned32	3GPP
Represents the total size in bytes of the message. For MMS, it is the total size in bytes calculated as per [TS23.140]. For SMS, it is the total size in octets, including any user data headers.
Message-Type	1211	Enumerated	3GPP
Specifies the type of message according to MMS transactions. Enumerated values: 1 m-send-req: MMS Send Request 2 m-send-conf: MMS Send Confirmation 3 m-notification-ind: MMS Notification Indication 4 m-notifyresp-ind: MMS Notify Response Indication 5 m-retrieve-conf: MMS Retrieve Confirmation 6 m-acknowledge-ind: MMS Acknowledge Indication 7 m-delivery-ind: MMS Delivery Indication 8 m-read-rec-ind: MMS Read Report Indication 9 m-read-orig-ind: MMS Read Original Indication 10 m-forward-req: MMS Forward Request 11 m-forward-conf: MMS Forward Confirmation 12 m-mbox-store-conf: MMS Mailbox Store Confirmation 13 m-mbox-view-conf: MMS Mailbox View Confirmation 14 m-mbox-upload-conf: MMS Mailbox Upload Confirmation 15 m-mbox-delete-conf: MMS Mailbox Delete Confirmation
MMBox-Storage-Requested	1248	Enumerated	3GPP
Specifies whether an MMBox (Multimedia Message Box) storage request has been made by the originating MMS (Multimedia Messaging Service) User Agent. This AVP indicates the user's request to store multimedia messages, which may include images, videos, or text, in the designated MMBox storage. This request can impact message storage and retrieval within MMS infrastructure, as well as associated billing and data management. Enumerated values: 0 (No): No storage request was made. The originating MMS User Agent has not requested the storage of the multimedia message in an MMBox. 1 (Yes): Storage was requested. The originating MMS User Agent has requested that the multimedia message be stored in an MMBox.
MM-Content-Type	1203	Grouped	3GPP
Represents the overall content type of the MM, including details of its contents. The AVP structure is defined as follows: Type-Number: An enumerated type indicating the type of content. Additional-Type-Information (Optional): Additional information about the content type. Content-Size (Optional): The total content size. Additional-Content-Information (Optional, Repeated): A list of extra details related to the content.
MMS-Information	877	Grouped	3GPP
Provides details about MMS services, containing various service-specific information. The AVP structure is defined as follows: Originator-Address: Origin address for the MMS. Recipient-Address (Repeated): List of addresses for MMS recipients. Submission-Time: Time when the MMS was submitted. MM-Content-Type: Type and details of the MMS content. Priority: Indicates priority of the MMS. Message-ID: Unique identifier for the message. Message-Type: Type of message being transmitted. Message-Size: Total size of the message. Message-Class: Class of the message. Delivery-Report-Requested: Whether a delivery report was requested. Read-Reply-Report-Requested: Indicates if a read-reply report was requested. MMBox-Storage-Requested: Whether storage was requested for MMBox. Applic-ID: Application identifier. Reply-Applic-ID: Identifier for reply applications. Aux-Applic-Info: Auxiliary application information. Content-Class: Class of content. DRM-Content: Digital rights management content indicator. Adaptations: Any adaptations applied. VASP-Id: Identifier for VASP (Value-Added Service Provider). VAS-Id: Identifier for VAS (Value-Added Service).
MMTel-Information	2030	Grouped	3GPP
Allows the transmission of additional MMTel service-specific information, including supplementary services invoked during MMTel service. The AVP structure is defined as follows: Supplementary-Service (Repeated): Contains MMTel supplementary service details.
MMTel-SService-Type	2031	Enumerated	3GPP
Specifies the type of supplementary service within the Multimedia Telephony (MMTel) environment. Each enumerated value represents a specific MMTel supplementary service type, which can impact user call handling, call identification, and other telephony features. These services are commonly used in IP Multimedia Subsystem (IMS) networks to enhance voice and video communication by adding supplementary functionalities. Enumerated values: 0: Originating Identification Presentation (OIP) - Displays the calling party’s identity to the recipient. 1: Originating Identification Restriction (OIR) - Restricts the display of the calling party’s identity. 2: Terminating Identification Presentation (TIP) - Displays the receiving party’s identity to the caller. 3: Terminating Identification Restriction (TIR) - Restricts the display of the receiving party’s identity. 4: Communication HOLD (HOLD) - Enables users to put a communication session on hold. 5: Communications Barring (CB) - Restricts specific outgoing or incoming communications. 6: Communication Diversion (CDIV) - Diverts incoming calls to another designated endpoint. 8: Communication Waiting (CW) - Alerts users to an incoming call when they are already engaged in another call. 9: Message Waiting Indication (MWI) - Notifies users of a waiting message, typically for voicemail. 10: Conference (CONF) - Allows multiple parties to join a communication session. 11: Flexible Alerting (FA) - Provides flexibility in alerting methods and tones. 12: Completion of Communication to Busy Subscriber (CCBS) - Allows call completion when the busy user becomes available. 13: Completion of Communications on No Reply (CCNR) - Allows call completion when the initially unavailable user becomes available. 14: Malicious Communication Identification (MCID) - Identifies and flags malicious communications. 15: Customized Alerting Tone (CAT) - Enables a custom alerting tone. 16: Closed User Group (CUG) - Limits communication within a specific group of users. 17: Personal Network Management (PNM) - Provides management options within a personal network. 18: Customized Ringing Signal (CRS) - Enables a custom ringing signal. 19: Advice of Charge (AoC) - Provides cost information for a service session. 20: Explicit Communication Transfer (ECT) - Allows the explicit transfer of a communication session. Values ≥ 1024 are reserved for network- or manufacturer-specific variants of supplementary services, allowing for additional customization based on network or device manufacturer requirements.
Monitored-PLMN-Identifier	3430	UTF8String	3GPP
Contains the Monitored PLMN ID, which corresponds to the Announcing UE VPLMN Identifier when roaming and the Announcing UE HPLMN Identifier when not roaming, as defined in [TS23.303].
Monitoring-Event-Configuration-Activity	3919	Enumerated	3GPP
Specifies the action associated with configuring a monitoring event, which subsequently influences event-based charging. It defines specific activities that can trigger the monitoring event, affecting how these events are tracked, reported, and billed. This AVP is crucial for managing and billing monitoring events within a network. Enumerated values: 0: Create - Initiates the configuration of a new monitoring event. This action marks the beginning of monitoring a specific event type within the network. 1: Transfer - Transfers the configuration or ownership of the monitoring event to another entity, facilitating continuity of event tracking across nodes or sessions. 2: Update - Modifies the existing configuration of the monitoring event. Updates may involve changes in monitored parameters or criteria. 3: Delete - Removes the monitoring event configuration, terminating the tracking and any related charging of the event.
Monitoring-Event-Functionality	3922	Enumerated	3GPP
Specifies the type of functionality related to a monitoring event that is subject to charging. This AVP is used to differentiate between the configuration and reporting aspects of monitoring events, enabling precise billing based on the specific function performed within the monitoring framework. Enumerated values: 0: Configuration - Refers to the initial setup or modification of a monitoring event's parameters. When this functionality is selected, charging is associated with the act of configuring or reconfiguring the monitoring event criteria, such as setting thresholds or defining event conditions. 1: Reporting - Involves the collection and transmission of data based on monitoring events. When this functionality is specified, it indicates that the charging applies to the reporting process, including the sending of reports to designated entities when the monitored conditions meet predefined criteria.
Monitoring-Event-Report-Data	3920	Grouped	3GPP
Provides detailed information related to a monitoring event, enabling the transmission of multiple specific information elements for effective monitoring in network environments. This AVP supports tracking, managing, and configuring various aspects of the monitoring event, covering everything from the type and configuration of the event to reachability, accuracy, and reporting details. The AVP structure is defined as follows: Monitoring-Event-Functionality: Specifies the functionality of the monitoring event (e.g., configuration or reporting), defining the event’s purpose. Event-Timestamp: Records the timestamp of the monitoring event, providing a chronological reference for tracking. Monitoring-Event-Configuration-Activity: Indicates the configuration activity (e.g., create, transfer, update, or delete) that triggers the monitoring event. SCEF-Reference-ID: Identifies the reference ID for the Service Capability Exposure Function (SCEF), used to associate this monitoring event with a specific SCEF instance. SCEF-ID: Specifies the identifier for the SCEF managing the monitoring event. Monitoring-Type: Defines the type of monitoring (e.g., UE reachability or location change) for this event. Maximum-Number-of-Reports: Limits the maximum number of reports generated for this monitoring event, controlling the reporting frequency. Monitoring-Duration: Specifies the duration for which the monitoring event is active. Charged-Party: Identifies the entity responsible for charges related to the monitoring event. Maximum-Detection-Time: Sets the maximum detection time allowed for the monitoring event, after which the event may be concluded or refreshed. UE-Reachability-Configuration: Configures the UE reachability monitoring details, such as detection intervals. MONTE-Location-Type: Specifies the location type for monitoring (e.g., cell or area-based monitoring). Accuracy: Indicates the desired accuracy level for location-based monitoring. Number-Of-UE-Per-Location-Configuration: Lists the number of UEs per location configuration, supporting group-based monitoring. Monitoring-Event-Report: Contains event-specific reports generated from the monitoring activity, providing insights on the monitoring status and results.
Monitoring-Event-Report-Number	3923	Unsigned32	3GPP
Represents the sequential number of the report being sent for the specified Monitoring Event request from this node.
Monitoring-UE-HPLMN-Identifier	3431	UTF8String	3GPP
Identifies the HPLMN (Home Public Land Mobile Network) of the monitored UE.
Monitoring-UE-Identifier	3432	UTF8String	3GPP
Identifies the initiating party in a monitor/match report, often the IMSI of the UE being monitored.
MSC-Address	3417	E.164 Address (OctetString)	3GPP
Contains the MSC (Mobile Switching Center) address in an international E.164 format, encoded as a TBCD string.
MTC-IWF-Address	3406	Address	3GPP
Holds the address of the MTC-IWF (Machine Type Communication Interworking Function) for MTC, as defined in [TS29.337].
Neighbour-Node-Address	2705	Address	3GPP
Contains the control plane IP address of a neighboring network contact point for handling service requests in interconnection and roaming scenarios.
Network-Call-Reference-Number	3418	OctetString	3GPP
Contains a unique reference number generated by the GMSC/MSC for identifying a specific voice call service, in combination with the MSC's identity.
Next-Tariff	2057	Grouped	3GPP
Holds tariff information for cost calculation based on the Used-Service-Unit AVP. The calculated cost is provided in the Currency-Code AVP, with the sum of the rating elements multiplied by the Scale-Factor AVP.
NIDD-Submission	3928	Grouped	3GPP
Used to report details of the Non-IP Data Delivery (NIDD) submission in the context of Control Plane (CP) data transfer. This AVP provides key metrics and timestamps related to the NIDD submission process, allowing operators to monitor and account for data usage in IoT/M2M communications. The AVP structure is defined as follows: Submission-Timestamp: Records the exact time the NIDD submission was made, providing a timestamp for tracking submission events. Event-Timestamp: Specifies the timestamp of the related monitoring event, indicating when the event associated with the submission took place. Accounting-Input-Octets: Reports the total number of input octets sent to the network during this submission, providing an account of incoming data volume. Accounting-Output-Octets: Reports the total number of output octets received from the network, measuring the outgoing data volume. Change-Condition: Indicates the change condition that triggered this submission, such as QoS change or other predefined triggers, as defined in the Change-Condition AVP.
NNI-Information	2703	Grouped	3GPP
Contains information about the Network-to-Network Interface (NNI) used for interconnection and roaming, including session direction, NNI type, relationship mode, and the address of the neighboring node. The AVP structure is defined as follows: Session-Direction: Specifies the direction of the session. NNI-Type: Defines the type of NNI (e.g., non-roaming, roaming without loopback, roaming with loopback). Relationship-Mode: Indicates the operational mode of the relationship. Neighbour-Node-Address: Contains the IP address of the neighboring network contact point.
NNI-Type	2704	Enumerated	3GPP
Identifies the type of Network-to-Network Interface (NNI) used in a session. It distinguishes between different types of NNI configurations, especially in the context of roaming, enabling network operators to track and manage traffic based on the NNI setup. This AVP provides insight into whether the session involves roaming and if loopback routing is applied. Enumerated values: 0 - non-roaming: Indicates that the session does not involve roaming; the network connection is within the home network. 1 - roaming without loopback: Specifies that the session is a roaming session, but no loopback routing is used. This configuration generally means that traffic is not routed back to the home network. 2 - roaming with loopback: Denotes a roaming session where loopback routing is applied. In this configuration, traffic is routed back to the home network, often for compliance or regulatory purposes.
Node-Functionality	862	Enumerated	3GPP
Identifies the functionality or role of a node in the network. This can represent various nodes such as S-CSCF, P-CSCF, I-CSCF, and others with specific functionalities. Enumerated values: 0 - S-CSCF (Serving-Call Session Control Function) 1 - P-CSCF (Proxy-Call Session Control Function) 2 - I-CSCF (Interrogating-Call Session Control Function) 3 - MRFC (Media Resource Function Controller) 4 - MGCF (Media Gateway Control Function) 5 - BGCF (Breakout Gateway Control Function) 6 - AS (Application Server) 7 - IBCF (Interconnection Border Control Function) 8 - S-GW (Serving Gateway) 9 - P-GW (Packet Gateway) 10 - HSGW (Home Subscriber Gateway) 11 - E-CSCF (Emergency Call Session Control Function) 12 - MME (Mobility Management Entity) 13 - TRF (Traffic Routing Function) 14 - TF (Traffic Function) 15 - ATCF (Access Transfer Control Function) 16 - Proxy Function 17 - ePDG (Evolved Packet Data Gateway) 18 - TDF (Traffic Detection Function) 19 - TWAG (Trusted Wireless Access Gateway) 20 - SCEF (Service Capability Exposure Function) 21 - IWK-SCEF (Interworking SCEF)
Node-Id	2064	UTF8String	3GPP
Contains an optional, operator-configurable identifier string for the node.
Nr-Cgi	1325	UTF8String	3GPP
Includes the NR Global Cell Identity, formatted according to clause 19.6A of [TS23.003]. It provides a unique identifier for a cell in NR (New Radio) networks.
Number-Of-Diversions	2034	Unsigned32	3GPP
S AVP specifies the total number of diversions related to a Call Diversion (CDIV) service. It includes all types of diversions.
Number-Of-Messages-Sent	2019	Unsigned32	3GPP
Indicates the number of SMS messages sent by the IMS application. In cases of concatenated short messages, this AVP contains the total SMS count, specifically for SMS offline charging.
Number-Of-Participants	885	Unsigned32	3GPP
Represents the count of invited parties in a multi-party session for services like PoC, conference, and SIMPLE IM. For interim or update charging messages, it reflects the number of participants currently in the session.
Number-Of-Received-Talk-Bursts	1282	Unsigned32	3GPP
Represents the count of received talk bursts, commonly used in communication sessions like push-to-talk (PTT) services.
Number-Of-Talk-Bursts	1283	Unsigned32	3GPP
Holds the count of talk bursts sent during a session, typically in communication applications like push-to-talk (PTT).
Number-Portability-Routing-Information	2024	UTF8String	3GPP
Contains routing information based on a number portability lookup (e.g., ENUM/DNS). It may be included in the SIP Requested URI header, allowing IMS nodes to report this information.
Occupancy	1012	Unsigned32	oneM2M
Represents the total size (in bytes) of data containers generated by a set of Application Entities (AEs) identified by the M2M Service Subscription Identifier.
OC-OLR	623	Grouped	IETF
Provides overload control information for a Diameter node. It allows Diameter peers to communicate load and congestion levels, helping to manage traffic effectively and maintain service quality. This AVP is particularly useful in scenarios where network elements may be experiencing high traffic loads and need to inform other network entities of the reduced capacity to prevent overloading. The AVP structure is defined as follows: OC-Sequence-Number: A unique identifier for the overload report sequence. It helps peers track and apply the correct sequence of overload control actions. OC-Report-Type: Indicates the type of report. The OCReportTypeEnum defines possible values, such as "Host" or "Realm", specifying the scope of the overload control (e.g., for a specific host or an entire realm). OC-Reduction-Percentage (optional): Specifies the percentage by which traffic should be reduced to mitigate overload. This value indicates the recommended reduction level for incoming traffic based on current load conditions. OC-Validity-Duration (optional): Defines the duration, in seconds, for which the overload report remains valid. After this time, the overload control report should be considered outdated, and peers may stop applying the reduction percentage. 3GPP-OC-Specific-Reduction (optional, repeatable): Specifies additional reduction information that may be unique to 3GPP networks. Each entry contains specific reduction percentages for various services, facilitating granular control over traffic for particular 3GPP applications.
Offline-Charging	1278	Grouped	3GPP
Manages offline charging settings and parameters. The AVP structure is defined as follows: Quota-Consumption-Time: Specifies quota time consumption. Time-Quota-Mechanism: Manages time-based quotas. Envelope-Reporting: Enables or disables envelope reporting. Multiple-Services-Credit-Control: Can contain multiple service credit controls, with specific configurations for rating groups and quotas.
OneM2MOriginator	1008	UTF8String	OneM2M
Identifies the initiating entity (i.e., the originator or "from" party) in an M2M (Machine-to-Machine) communication request. It holds the identifier of the oneM2M entity initiating the request, such as an Application Entity (AE) or a Common Services Entity (CSE), as specified in the oneM2M standard. This identifier facilitates routing and addressing in M2M communications. Format and Syntax: The value of this AVP follows the format specified in oneM2M clause 6.2.3, using M2M Identifiers that are protocol-independent. The syntax aligns with the Absolute or SP-Relative Identifier structure. The CSE-ID or AE-ID is used to uniquely identify each oneM2M entity, either by a full (absolute) identifier or a service-provider relative identifier. CSE-ID Format: Absolute CSE-ID: //M2M-SP-ID/SP-relative-CSE-ID Example: //myoperator.com/cse1 SP-Relative CSE-ID: /SP-relative-CSE-ID Example: /cse1 AE-ID Format: Absolute AE-ID: //M2M-SP-ID/SP-relative-CSE-ID/C-AE-ID-Stem or //M2M-SP-ID/S-AE-ID-Stem Example: //myoperator.com/cse2/C3532ea3 SP-Relative AE-ID: /SP-relative-CSE-ID/C-AE-ID-Stem or /S-AE-ID-Stem Example: /cse2/C3532ea3 Examples: //myoperator.com/S563423: An absolute AE-ID assigned by an M2M Service Provider. /cse2/C3532ea3: An SP-relative AE-ID assigned by the Registrar CSE.
OnlineChargingFlag	2303	Enumerated	3GPP
Indicates whether the Online Charging Request was initiated based on the provided ECF address from the SIP P-header "P-Charging-Function-Addresses." Enumerated values: 0: ECF address not provided 1: ECF address provided
Originating-IOI	839	UTF8String	3GPP
Contains the Inter Operator Identifier (IOI) for the originating network, generated by the IMS Network Element responsible for populating this parameter in SIP requests. This IOI reflects the network identifier and varies depending on the type of SIP request and the originating/terminating network's role. Types of IOI: Type 1 IOI: Represents the IOI of either the visited network (where the P-CSCF is located) or the home network (where the S-CSCF is located) for specific SIP request scenarios involving roaming and local breakout. Type 2 IOI: Indicates the IOI of the home network of the originating user, with specific behaviors for redirections, roaming with local breakout, and sessions initiated from the PSTN. Type 3 IOI: Refers to the IOI of the home or service provider network for SIP request forwarding and handling involving Application Servers (AS). For further details, refer to [TS32.240] and [TS24.229].
Originator	864	Enumerated	3GPP
Specifies the originating party of the message body. Enumerated values: 0: Calling Party 1: Called Party
Originator-Address	886	Grouped	3GPP
Identifies the originator of a message. The AVP structure is defined as follows: Address-Type: Specifies the type of address (e.g., IPv4, IPv6, or other custom types). Address-Data: Contains the actual address data. Address-Domain: Specifies the domain information of the address.
Originator-Interface	2009	Grouped	3GPP
Provides information on the interface where the message originated. The AVP structure is defined as follows: Interface-Id: A unique identifier for the interface. Interface-Text: Descriptive text about the interface. Interface-Port: Port information associated with the interface. Interface-Type: Specifies the type of interface, allowing categorization based on interface functionality.
Originator-Received-Address	2027	Grouped	3GPP
Captures the originator's original, unmodified address information as it was received, prior to any manipulation. It is useful for correlating address data with information generated by other nodes in the message flow. The AVP structure is defined as follows: Address-Type: The type of address (e.g., IPv4, IPv6). Address-Data: The actual address information. Address-Domain: The domain of the address.
Originator-SCCP-Address	2008	Address	3GPP
Represents the "SCCP calling address" utilized by the messaging node when a message is received. It usually points to the MSC or SGSN/Serving Node serving the UE at message submission. The address can be either a Point Code (ISPC) or a Global Title (often an E.164 number). The address type is set to value 8 (E.164), with UTF-8 encoding for the address information.
Outgoing-Session-Id	2320	UTF8String	3GPP
Holds the outgoing session identifier for an Application Server (AS) functioning as a Back-to-Back User Agent (B2BUA). For SIP sessions, it contains the SIP Call ID of the outgoing session leg, as specified in [RFC3261].
Outgoing-Trunk-Group-ID	853	UTF8String	3GPP
Used to identify the outgoing PSTN (Public Switched Telephone Network) leg in a telecommunication session.
Participant-Access-Priority	1259	Enumerated	3GPP
This AVP defines the priority level for participants in a Push-to-Talk over Cellular (PoC) session, indicating the urgency of a user's access request. It is used to manage user access in scenarios where participants may join or initiate PoC sessions with different priority levels. Enumerated values: 1 (Pre-emptive priority): The highest priority level. Requests with this priority will revoke other current requests unless those are also pre-emptive. 2 (High priority): Lower than pre-emptive but above normal. 3 (Normal priority): The standard priority level, below high. 4 (Low priority): The lowest priority level.
Participant-Action-Type	2049	Enumerated	3GPP
Captures the type of action taken by a participant in a conference session, relevant to billing and participant activity tracking. Enumerated values: 0 (CREATE_CONF): Initiate a new conference. 1 (JOIN_CONF): Join an existing conference. 2 (INVITE_INTO_CONF): Invite another participant into the conference. 3 (QUIT_CONF): Exit from the conference.
Participant-Group	1260	Grouped	3GPP
Aggregates detailed information about a participant in a PoC session, including the participant's address, access priority, and participation type. The AVP structure is defined as follows: Called-Party-Address: The address of the called party, which may include SIP URI, Tel URI, or MSISDN. Participant-Access-Priority: The priority level assigned to the participant, as defined in Participant-Access-Priority. User-Participating-Type: Indicates the role or type of user participation within the session (e.g., caller, responder).
Participants-Involved	887	UTF8String	3GPP
Contains a list of addresses representing the participants involved in a Push-to-Talk over Cellular (PoC) session. The addresses can be specified in various formats, including Public User ID, SIP URI, Tel URI, or MSISDN. The Participants-Involved AVP is typically used for logging or billing purposes to maintain records of the parties present in a PoC session.
PC3-Control-Protocol-Cause	3434	Integer32	3GPP
Identifies the reason why a DISCOVERY_REQUEST or MATCH_REPORT message from a User Equipment (UE) was rejected by the ProSe (Proximity Services) function. The PC3-Control-Protocol-Cause value is specified as part of the PC3 control protocol, defined in [TS24.334]. The integer value represents specific rejection reasons, which might include protocol errors, policy violations, or network restrictions that prevent successful message processing.
PC3-EPC-Control-Protocol-Cause	3435	Integer32	3GPP
Similar in purpose to PC3-Control-Protocol-Cause but is used specifically for proximity-related messages within the Evolved Packet Core (EPC). It indicates the reason for rejection when a proximity request from a UE is denied by the ProSe function. This AVP is also part of the PC3 EPC control protocol, as defined in [TS24.334], and provides insights into the reasons for proximity request failures, such as authorization issues or unsupported proximity scenarios.
PC5-Radio-Technology	1300	Enumerated	3GPP
Specifies the radio technology that the User Equipment (UE) used for ProSe (Proximity Services) Direct Discovery on the PC5 interface. It helps identify the specific radio access method used for ProSe. Enumerated values: 0: EUTRA (Evolved UMTS Terrestrial Radio Access, LTE) 1: WLAN (Wireless Local Area Network) 2: Both EUTRA and WLAN
PDN-Connection-Charging-ID	2050	Unsigned32	3GPP
Contains the charging identifier for identifying different records related to the same Packet Data Network (PDN) connection. It helps uniquely identify a PDN connection in association with the P-GW (Packet Gateway) address for charging purposes. It includes the Charging ID of the first IP-CAN bearer activated and is coded similarly to the 3GPP-Charging-Id as specified in [TS29.061].
PDP-Address	1227	Address	3GPP
Holds the IP address associated with a PDP context (or PDN connection) of an IP CAN bearer session. This AVP specifies the IP address used by the user device during a PDP connection session. For IPv6 addresses, the PDP-Address-Prefix-Length AVP may specify the address prefix length.
PDP-Address-Prefix-Length	2606	Unsigned32	3GPP
Provides the prefix length of an IPv6 PDP-Address. The default prefix length is assumed to be 64 bits if this AVP is omitted, as required for an IPv6 PDP-Address.
PDP-Context-Type	1247	Enumerated	3GPP
Indicates the type of a PDP context, specifying whether it is a primary or secondary context. It is typically included only in the initial Credit-Control-Request (CCR) message. Enumerated values: 0: Primary 1: Secondary
Physical-Access-ID	313	UTF8String	ETSI
Identifies the physical access point to which the user equipment is connected. It includes a port identifier along with the access node’s identity where the port resides, allowing for precise localization of the connection point within the network infrastructure. The Vendor-Id in CER is set to ETSI (13019).
Play-Alternative	3913	Enumerated	3GPP
Specifies the intended recipient of an announcement in a telecommunication session. It identifies whether the announcement should be directed to the served party (the user initiating the session) or the remote party (the recipient of the session). Enumerated values: 0 - Served Party: The announcement is directed toward the served party. This typically refers to the user initiating or managing the session. 1 - Remote Party: The announcement is intended for the remote party, who is the recipient of the session.
PoC-Change-Condition	1261	Enumerated	3GPP
Specifies the reason for the closure of a current PoC (Push-to-Talk over Cellular) container and the initiation of a new container. This AVP is essential for managing PoC sessions and ensuring proper charging and resource management during service changes. Enumerated values: 0 - ServiceChange: Indicates a service-level change that necessitates closing the current container and opening a new one. 1 - VolumeLimit: Triggered when a predefined data volume threshold for the container is reached. 2 - TimeLimit: Indicates that the container has reached its maximum allowed duration. 3 - NumberofTalkBurstLimit: Triggered when the maximum number of talk bursts within the container has been exceeded. 4 - NumberofActiveParticipants: Indicates a change in the number of active participants in the PoC session that requires container modification. 5 - TariffTime: Triggered due to a tariff time change, which may affect session charging and resource allocation.
PoC-Change-Time	1262	Time	3GPP
Provides a timestamp indicating when a container or Call Detail Record (CDR) is closed in a PoC session, marking the moment of change in session state or billing.
PoC-Controlling-Address	858	UTF8String	3GPP
Identifies the PoC server responsible for controlling the associated Push-to-Talk over Cellular (PoC) session. It is essential for determining the controlling entity within the PoC network infrastructure.
PoC-Event-Type	2025	Enumerated	3GPP
Specifies the type of event in a Push-to-Talk over Cellular (PoC) context that is unrelated to the actual PoC session. It allows for categorization of specific events for proper handling in charging and service scenarios. Enumerated values: 0 - Normal: Refers to standard PoC events that do not fall into any specialized category. 1 - Instant Personal Alert Event: Represents a PoC-specific event where a user sends an instant alert to notify another user about an intended communication. 2 - PoC Group Advertisement Event: Indicates a group-related event where information or advertisements are communicated within a PoC group. 3 - Early Session Setting-Up Event: Identifies events related to the preparation and setup of a PoC session before the actual session starts. 4 - PoC Talk Burst: Refers to the transmission of talk bursts within a PoC environment, typically indicating user speech during a session.
PoC-Group-Name	859	UTF8String	3GPP
Specifies the name of a group for a PoC session, such as a pre-arranged or chat group. It allows identification of group sessions and is useful in both PoC and OMA SIMPLE IM applications for group-based charging and session management.
PoC-Information	879	Grouped	3GPP
Enables the inclusion of additional PoC-specific service information. It is essential for conveying session details, such as server roles, session types, user roles, participant information, and various session identifiers. The AVP structure is defined as follows: PoC-Server-Role: Defines the role of the PoC server (e.g., controlling or participating server). PoC-Session-Type: Specifies the type of PoC session, such as group or one-to-one session. PoC-User-Role: Indicates the role of the user within the PoC session. PoC-Session-Initiation-Type: Shows the type of initiation (e.g., ad-hoc or pre-arranged). PoC-Event-Type: Indicates specific events within the PoC session, like normal, group advertisement, or talk burst. Number-Of-Participants: The count of users currently involved in the session. Participants-Involved: A list of participants' identifiers (kept for backward compatibility with versions before 3GPP Release 7). Participant-Group: Contains detailed participant information, including address and access priority. Talk-Burst-Exchange: Represents the exchange data for talk bursts within the session. PoC-Controlling-Address: Identifies the PoC server performing the controlling function. PoC-Group-Name: Identifies the group involved in the session, relevant for group-based sessions. PoC-Session-Id: The unique session identifier for tracking purposes. Charged-Party: Specifies the party responsible for charging in the session.
PoC-Server-Role	883	Enumerated	3GPP
Identifies the functional role of a Push-to-Talk over Cellular (PoC) server within a PoC network. The AVP enables the differentiation of PoC server responsibilities, ensuring that signaling and media traffic are appropriately directed and managed. Enumerated values: 0 - Participating PoC Server: Represents a PoC server that facilitates the participation of users in the PoC session. This server acts as a bridge between the users and the controlling PoC server, managing communication for one or more users. 1 - Controlling PoC Server: Identifies the central server responsible for managing the overall PoC session. This server handles the session control, including talk burst arbitration and participant permissions. 2 - Interworking Function: Denotes a server that provides interworking capabilities between the PoC system and other communication systems or networks. 3 - Interworking Selection Function: Specifies a server that selects the appropriate interworking function to ensure compatibility and communication between PoC and other systems.
PoC-Session-Id	1229	UTF8String	3GPP
A unique identifier for each end-to-end PoC session, aiding in correlating charging information. It’s derived from the "Contact" header in SIP messages from the controlling PoC function. Note: It may not be available in initial charging interactions.
PoC-Session-Initiation-Type	1277	Enumerated	3GPP
Identifies the mode in which a Push-to-Talk over Cellular (PoC) session is initiated. It specifies whether the session is pre-established before user interaction or set up dynamically upon user request. Enumerated values: 0 - Pre-established: Indicates that the PoC session is set up in advance and remains ready for use. This mode minimizes session initiation delays by pre-configuring the session, ensuring faster call setup. Suitable for scenarios with high availability requirements. 1 - On-demand: Specifies that the PoC session is dynamically established upon a user’s request or trigger. This mode optimizes resource usage by avoiding unnecessary pre-established sessions, making it ideal for environments with variable traffic patterns.
PoC-Session-Type	884	Enumerated	3GPP
Specifies the type of Push-to-Talk over Cellular (PoC) session. This AVP is used to differentiate between various PoC communication scenarios, ensuring proper signaling and charging mechanisms are applied based on the session type. Enumerated values: 0 - 1-to-1 PoC Session: Indicates a session between two individual PoC users. This type of session facilitates private, direct communication, similar to a one-on-one call. 1 - Chat PoC Group Session: Refers to a spontaneous PoC group session where participants engage in informal or unstructured group communication. Often used for impromptu team discussions or social chats. 2 - Pre-arranged PoC Group Session: Represents a group session that has been scheduled or configured in advance. This type of session is often used for recurring or planned communication within predefined groups, such as regular team meetings. 3 - Ad-hoc PoC Group Session: Denotes a group session created dynamically, often involving participants who are not part of a pre-arranged group. This type supports flexible group communication for on-the-spot collaborations.
PoC-User-Role	1252	Grouped	3GPP
Specifies the roles and associated information of a PoC (Push-to-Talk over Cellular) user participating in a PoC session. This AVP enables the PoC server to manage user roles effectively, applying session policies and ensuring seamless communication. The AVP structure is defined as follows: PoC-User-Role-IDs: Provides a unique identifier for the role(s) assigned to the PoC user. PoC-User-Role-Info-Units: Specifies detailed information about the role type associated with the user. Values: 1 - Moderator: A user with elevated privileges, such as managing session settings or controlling participants. 2 - Dispatcher: A user responsible for coordinating communication among participants. 3 - Session-Owner: The initiator or owner of the session with complete control over its lifecycle. 4 - Session-Participant: A standard participant in the session with no special privileges.
PoC-User-Role-IDs	1253	UTF8String	3GPP
Identifies the PoC user role, linking the user’s functional identity within the session.
PoC-User-Role-Info-Units	1254	Enumerated	3GPP
Defines the specific role type of a PoC (Push-to-Talk over Cellular) user within a PoC session. It facilitates session control and management by explicitly identifying the user's functional role, which is crucial for role-based access, policy enforcement, and resource allocation. Enumerated values: 1 - Moderator: Represents a user with elevated privileges who can manage the session settings, participants, and overall communication flow. Example: In a corporate group call, the moderator controls who speaks and ensures adherence to meeting protocols. 2 - Dispatcher: Denotes a user responsible for coordinating the communication among participants. Example: A dispatcher assigns speaking turns or routes information during an emergency response scenario. 3 - Session-Owner: Refers to the user who initiated or owns the session and has full control over its lifecycle. Example: A session owner starts a group communication session and invites participants. 4 - Session-Participant: Represents a standard participant in the PoC session without any special privileges. Example: A participant in a team meeting who can contribute to discussions but cannot manage session settings.
Positioning-Data	1245	UTF8String	3GPP
Contains data on each positioning method used to estimate the location, including whether attempts were successful or not.
Preferred-AoC-Currency	2315	Unsigned32	3GPP
Specifies the preferred currency code for the Advice of Charge (AoC) function, represented by numeric values per the ISO 4217 standard (referenced in [RFC4006]). This AVP allows users to receive AoC information in their preferred currency.
Priority	1209	Enumerated	3GPP
Indicates the relative importance of a message, facilitating priority handling in service delivery and charging. It is primarily used in contexts such as SMS charging or communication services, where the delivery or processing order of messages is influenced by their importance level. For SMS charging, the value "Low" is not applicable. Enumerated values: 0 - Low: Indicates the least priority level. Messages with this priority are processed or delivered after higher-priority messages. Note: Not applicable for SMS charging. 1 - Normal: Represents the standard priority level for most messages. 2 - High: Denotes an elevated priority level. Messages with this priority are given precedence over others in processing and delivery.
Privacy-Indicator	3915	Enumerated	3GPP
Specifies whether an announcement within a session is considered private and should only be accessible to the designated party. This AVP ensures compliance with privacy requirements and provides a mechanism to restrict access to sensitive or confidential announcements. Enumerated values: 0 - NOT_PRIVATE: Indicates that the announcement is not considered private and may be accessed or played to multiple parties as necessary. 1 - PRIVATE: Denotes that the announcement is private and must only be played to the intended party.
ProSe-3rd-Party-Application-ID	3440	UTF8String	3GPP
Carries a globally unique identifier for a specific third-party application within the Proximity Services (ProSe) framework, used to identify applications at the upper layers of ProSe (referred to as "Application Identity" in [TS24.334]).
ProSe-Direct-Communication-Reception-Data-Container	3461	Grouped	3GPP
Facilitates the transmission of container data specific to Proximity Services (ProSe) Charging, capturing the volume count associated with receiving data within a ProSe group communication. It reports various parameters linked to changes in the charging condition. The AVP structure is defined as follows: Local-Sequence-Number: Identifies the sequence number of this record. Coverage-Status: Indicates whether the user equipment (UE) is under coverage. 3GPP-User-Location-Info: Provides location information related to the user. Accounting-Input-Octets: Captures the input volume (in octets). Change-Time: The timestamp of the latest change in charging condition. Change-Condition: Specifies the reason for charging condition change. Visited-PLMN-Id: Identifies the PLMN (Public Land Mobile Network) visited by the UE. Usage-Information-Report-Sequence-Number: Sequence number for usage report. Radio-Resources-Indicator: Indicates the radio resources utilized. Radio-Frequency: Frequency information for ProSe communications.
ProSe-Direct-Communication-Transmission-Data-Container	3441	Grouped	3GPP
Similar to the Reception Data Container, this AVP reports transmission-related ProSe Charging information for volume count changes within a ProSe group communication. It includes parameters to track usage, location, and resource utilization. The AVP structure is defined as follows: Local-Sequence-Number: Sequence number for tracking. Coverage-Status: Status of network coverage for the UE. 3GPP-User-Location-Info: Indicates the location data for the UE. Accounting-Output-Octets: Captures the output volume (in octets). Change-Time: Indicates the time when a charging condition change occurred. Change-Condition: Specifies the condition prompting a change. Visited-PLMN-Id: Identifies the PLMN currently visited by the UE. Usage-Information-Report-Sequence-Number: Report sequence number. Radio-Resources-Indicator: Resource indicator for radio utilization. Radio-Frequency: Specifies the frequency used for ProSe transmissions.
ProSe-Direct-Discovery-Model	3442	Enumerated	3GPP
Identifies the model of direct discovery utilized by a User Equipment (UE) in a Proximity Services (ProSe) environment. This AVP, defined in 3GPP [TS23.303], specifies how the discovery of nearby devices or services is conducted, facilitating efficient communication in scenarios such as device-to-device interactions. Enumerated values: 0 - Model A: Direct discovery where the UE directly broadcasts discovery information. The discovery process is device-centric, with minimal network involvement. 1 - Model B: Direct discovery where the network assists in managing and controlling the discovery process. The discovery information is exchanged via the network to ensure enhanced control and coordination.
ProSe-Event-Type	3443	Enumerated	3GPP
Specifies the type of Proximity Services (ProSe) charging events that occur in proximity-based communication scenarios. It defines the charging-relevant actions taken by devices or networks during the discovery or interaction processes in a ProSe-enabled system. Enumerated values: 0 - Announcing: Represents an event where a device broadcasts its presence or service availability to nearby devices. 1 - Monitoring: Refers to an event where a device or network monitors the broadcast or discovery activity of other devices. 2 - Match Report: An event triggered when a match is detected between the announcing device and a monitoring device based on predefined criteria (e.g., service or user profile).
ProSe-Functionality	3445	Enumerated	3GPP
Specifies the type of Proximity Services (ProSe) functionality being requested by a User Equipment (UE). ProSe functionalities enable direct or network-assisted discovery and communication in ProSe-enabled environments, particularly useful in public safety and IoT applications. Enumerated values: 0 - Direct Discovery: The UE requests the ability to discover other ProSe-enabled devices directly without relying on the Evolved Packet Core (EPC). 1 - EPC-Level Discovery: The UE requests network-assisted discovery through the EPC, enabling a centralized mechanism for identifying nearby devices or services. 2 - Direct Communication: The UE requests the ability to communicate directly with another device, bypassing the network for data exchange.
ProSe-Function-IP-Address	3444	Address	3GPP
Holds the IP address of the ProSe Function, essential for network operations involving direct communication and service discovery for ProSe.
ProSe-Function-PLMN-Identifier	3457	UTF8String	3GPP
Contains the identifier of the Public Land Mobile Network (PLMN) where the ProSe Function resides. It’s used to uniquely identify the network in which the ProSe Function is deployed, enabling proper network context and routing.
ProSe-Group-IP-Multicast-Address	3446	Address	3GPP
Holds the IP multicast address used for ProSe direct communication within a group. It enables devices to communicate within a specific ProSe group over multicast, facilitating efficient group communication as specified in ProSe standards.
ProSe-Information	3447	Grouped	3GPP
Holds comprehensive information specific to Proximity Services (ProSe). It encompasses various sub-AVPs used for transmitting detailed ProSe-related data for applications such as direct communication, discovery, and group management. It includes identifiers, control parameters, timestamps, and specific communication details required for effective ProSe functionality in a telecom environment. The AVP structure is defined as follows: Supported-Features: List of supported features relevant to the ProSe context. Announcing-UE-HPLMN-Identifier / VPLMN-Identifier: Identifies the home/visited PLMN of the announcing UE. Monitoring-UE-HPLMN-Identifier / VPLMN-Identifier: Identifies the home/visited PLMN of the monitoring UE. Monitored-HPLMN-Identifier: Home PLMN identifier for the UE being monitored. Role-Of-ProSe-Function: Specifies the function of the ProSe, such as direct discovery or communication. ProSe-App-Id: Identifies the ProSe application. ProSe-3rd-Party-Application-ID: Unique identifier for any associated third-party application. Application-Specific-Data: Byte data for application-specific details. ProSe-Event-Type: Type of ProSe event (e.g., announcing, monitoring). ProSe-Direct-Discovery-Model: Indicates the discovery model in use. ProSe-Function-IP-Address: IP address of the ProSe function. ProSe-Function-ID: Identifier for the ProSe function. ProSe-Validity-Timer: Timer indicating the duration of ProSe session validity. ProSe-Role-Of-UE: Role of the User Equipment in the ProSe context. ProSe-Request-Timestamp: Timestamp marking the request time. PC3-Control-Protocol-Cause: Cause indicator for PC3 protocol control. ProSe-Group-IP-Multicast-Address: IP multicast address for group communication. Coverage-Info, Radio-Parameter-Set-Info, Transmitter-Info: Various parameters and information related to ProSe coverage, radio settings, and transmitter specifics. ProSe-Direct-Communication-Transmission/Reception-Data-Container: Containers for detailed transmission and reception data. ProSe-Target-Layer-2-ID / Relay-IP-address / Target-IP-Address: Network layer details related to the ProSe targets, relays, and endpoints.
ProSe-Range-Class	3448	Enumerated	3GPP
Specifies a proximity range class for ProSe requests, providing distance ranges in meters. Enumerated values: 0: Reserved 1: 50 meters 2: 100 meters 3: 200 meters 4: 500 meters 5: 1000 meters 6-255: Unused
ProSe-Reason-For-Cancellation	3449	Enumerated	3GPP
Specifies the reason for the cancellation of an EPC-level discovery request in a Proximity Services (ProSe) environment. It is used to identify the cause for terminating a discovery process, which helps in diagnostics and charging differentiation. Enumerated values: 0 - Proximity Alert Sent: The discovery process was terminated because the proximity alert has already been sent to the relevant entities. 1 - Time Expired with No Renewal: The discovery process was canceled due to the expiration of the allocated time for the request, and no renewal was initiated. 2 - Requestor Cancellation: The discovery request was explicitly canceled by the requesting entity.
ProSe-Request-Timestamp	3450	Time	3GPP
Captures the timestamp when a ProSe request is received from the UE, enabling precise tracking and synchronization
ProSe-Role-Of-UE	3451	Enumerated	3GPP
Specifies the role of a User Equipment (UE) in Proximity Services (ProSe) interactions. This AVP is essential for defining the functional behavior of the UE within a ProSe-enabled network, facilitating efficient proximity-based communication. Enumerated values: 0 - Announcing UE: The UE is responsible for broadcasting its presence or availability to nearby devices. 1 - Monitoring UE: The UE is actively listening for announcements from other devices to discover nearby UEs or services. 2 - Requestor UE: The UE initiates a specific ProSe request, such as discovery or communication, towards a targeted UE or service. 3 - Requested UE: The UE is the target of a specific ProSe request, such as being discovered or receiving a communication initiation.
ProSe-Source-IP-Address	3452	Address	3GPP
Holds the IP address used by the UE as the source address for performing ProSe direct communication, as referenced in [TS23.303].
ProSe-Target-Layer-2-ID	4410	OctetString	3GPP
Used to carry a unique Layer 2 identifier for a User Equipment (UE) involved in Proximity Services (ProSe) direct communication. This AVP ensures that a specific UE is uniquely identifiable within a one-to-one ProSe Direct Communication session, allowing the network and participating UEs to correctly associate the ProSe communication session with the appropriate peer device. Provides a unique Layer 2 identifier to precisely recognize a target UE within the ProSe framework.
ProSe-UE-ID	3453	OctetString	3GPP
A unique link layer identifier assigned by the EPS (Evolved Packet System) representing the UE in the context of ProSe Direct Communication. Referred to as "ProSe UE ID" in [TS23.303].
ProSe-UE-to-Network-Relay-UE-ID	4409	OctetString	3GPP
Holds a link layer identifier representing the ProSe UE-to-Network relay UE for ProSe Direct Communication via UE-to-Network Relay.
Protocol-Type	1013	Enumerated	oneM2M
Specifies the protocol being used for a request in an M2M (Machine-to-Machine) communication scenario. It provides a standardized mechanism to identify the communication protocol, ensuring interoperability between different systems in OneM2M architectures. Values: 0 HTTP: Hypertext Transfer Protocol. 1 CoAP: Constrained Application Protocol. 2 MQTT: Message Queuing Telemetry Transport. 3-99: Reserved for OneM2M-defined protocol types. 100-199: Reserved for operator/vendor-specific types.
Proximity-Alert-Indication	3454	Enumerated	3GPP
Specifies whether a proximity alert was sent prior to the cancellation of a proximity request. This AVP ensures clarity in Proximity Services (ProSe) communication by identifying the status of alert notifications. Values: 0 Alert: Proximity alert sent. 1 No Alert: Proximity alert not sent.
Proximity-Alert-Timestamp	3455	Time	3GPP
Holds the timestamp indicating when the proximity alert was sent, used to confirm that two UEs are in proximity.
Proximity-Cancellation-Timestamp	3456	Time	3GPP
Represents the timestamp when the proximity request cancellation was requested.
PS-Append-Free-Format-Data	867	Enumerated	3GPP
Indicates how the PS-Free-Format-Data should be handled in the online charging session. Values: 0 - Append: The P-GW appends new data to the existing PS free format data for the session. 1 - Overwrite: (Default) The P-GW overwrites the existing PS free format data for the session if present.
PSCell-Info	1324	Grouped	3GPP
Provides information on the primary or Secondary Cell Group (SCG). The AVP structure is defined as follows: Nr-Cgi: Contains the NR Global Cell Identity, as specified in clause 19.6A of [TS23.003].
PS-Free-Format-Data	866	OctetString	3GPP
Holds session-specific data related to the online charging session.
PS-Furnish-Charging-Information	865	Grouped	3GPP
Adds specific information for online charging sessions that needs to be included in Charging Data Records (CDRs) when online and offline charging are active simultaneously. The AVP structure is defined as follows: 3GPP-Charging-Id: Identifier for charging. PS-Free-Format-Data: Contains online charging session data. PS-Append-Free-Format-Data: Defines whether the PS-Free-Format-Data should be appended or overwrite existing data in the session.
PS-Information	874	Grouped	3GPP
Allows for the transmission of comprehensive PS (Packet-Switched) service-specific information elements. It provides various fields to collect data related to network nodes, charging, quality of service, user equipment, and session details, ensuring effective management and control of PS sessions. The AVP structure is defined as follows: Supported-Features (Multiple): Lists supported features for the session. 3GPP-Charging-Id: Unique identifier for 3GPP charging. PDN-Connection-Charging-ID: Identifies records belonging to the same PDN connection. Node-Id: Identifier of the serving node. 3GPP-PDP-Type: Type of PDP (Packet Data Protocol). PDP-Address (Multiple): PDP session IP addresses. PDP-Address-Prefix-Length: Prefix length for IPv6 PDP addresses. Dynamic-Address-Flag: Indicates dynamic or static IP addressing. Dynamic-Address-Flag-Extension: Extended dynamic address flag. QoS-Information: Contains quality of service details. SGSN-Address (Multiple): IP addresses for Serving GPRS Support Nodes. GGSN-Address (Multiple): IP addresses for Gateway GPRS Support Nodes. TDF-IP-Address (Multiple): Trusted Data Function IP addresses. SGW-Address (Multiple): Serving Gateway IP addresses. ePDG-Address (Multiple): ePDG (Evolved Packet Data Gateway) addresses. TWAG-Address (Multiple): TWAN (Trusted WLAN Access Gateway) addresses. CG-Address: Charging Gateway address. Serving-Node-Type: Type of the serving node (e.g., SGSN, GGSN). SGW-Change: Indicates if the Serving Gateway has changed. 3GPP-IMSI-MCC-MNC: IMSI, MCC, and MNC identifier for 3GPP. IMSI-Unauthenticated-Flag: Indicates if IMSI is unauthenticated. 3GPP-GGSN-MCC-MNC: MCC and MNC for the GGSN. 3GPP-NSAPI: Network Service Access Point Identifier. Called-Station-Id: Identifier for the called station. 3GPP-Session-Stop-Indicator: Indicator for session termination. 3GPP-Selection-Mode: Selection mode for 3GPP. 3GPP-Charging-Characteristics: Charging characteristics for the session. Charging-Characteristics-Selection-Mode: Defines selection mode for charging characteristics. 3GPP-SGSN-MCC-MNC: MCC and MNC for SGSN. 3GPP-MS-TimeZone: Mobile station's time zone. Charging-Rule-Base-Name: Name for charging rule base. ADC-Rule-Base-Name: Rule base name for ADC. 3GPP-User-Location-Info: Provides location information. User-Location-Info-Time: Timestamp for location information. User-CSG-Information: Information on the user’s Closed Subscriber Group. Presence-Reporting-Area-Information (Multiple): Presence reporting area details. 3GPP2-BSID: BSID for 3GPP2. TWAN-User-Location-Info: Location info for Trusted WLAN. UWAN-User-Location-Info: Location info for Untrusted WLAN. 3GPP-RAT-Type: Radio Access Technology type. PS-Furnish-Charging-Information: Adds online charging session-specific information. PDP-Context-Type: Type of PDP context. Offline-Charging: Indicates if offline charging is supported. Traffic-Data-Volumes (Multiple): Data volumes for traffic analysis. Service-Data-Container (Multiple): Containers for service-specific data. User-Equipment-Info: Information about user equipment. Terminal-Information: Details about the user terminal. Start-Time: Session start timestamp. Stop-Time: Session stop timestamp. Change-Condition: Condition for data change. Diagnostics: Diagnostics information. Low-Priority-Indicator: Low priority indicator for the session. NBIFOM-Mode: NB-IoT support mode. NBIFOM-Support: Indicates if NBIFOM support is available. MME-Number-for-MT-SMS: MME number for MT-SMS. MME-Name: Name of the MME. MME-Realm: Realm for the MME. Logical-Access-ID: Logical identifier for network access. Physical-Access-ID: Physical access point ID. Fixed-User-Location-Info: Fixed user location information. CN-Operator-Selection-Entity: Entity for CN operator selection. Enhanced-Diagnostics: Enhanced diagnostic information. SGi-PtP-Tunnelling-Method: SGi point-to-point tunneling method. CP-CIoT-EPS-Optimisation-Indicator: Indicator for Control Plane CIoT EPS optimization. UNI-PDU-CP-Only-Flag: Flag for UNI PDU CP only. Serving-PLMN-Rate-Control: Rate control for Serving PLMN. APN-Rate-Control: Rate control for Access Point Name. Charging-Per-IP-CAN-Session-Indicator: Indicator for charging per IP-CAN session. RRC-Cause-Counter: Counter for RRC cause occurrences. 3GPP-PS-Data-Off-Status: Status of PS Data Off feature. SCS-AS-Address: SCS/AS address for service. Unused-Quota-Timer: Timer for unused quota. RAN-Secondary-RAT-Usage-Report (Multiple): Reports on secondary RAT usage. PSCell-Info: Information on Primary or Secondary Cell Group (SCG).
Quota-Consumption-Time	881	Unsigned32	3GPP
Represents an idle traffic threshold time in seconds. Used within the Multiple-Services-Credit-Control AVP when a time quota is applied. This AVP helps monitor traffic activity during a session, ensuring that if the user is idle beyond the specified threshold, the quota consumption can be adjusted accordingly.
Quota-Holding-Time	871	Unsigned32	3GPP
Specifies the time (in seconds) to hold the quota when traffic ceases. The quota holding timer starts when consumption stops, marking the quota as expired if no traffic is detected within the defined period. It applies to both time and volume quotas and can be configured with a default value if not present in the CCA command.
Quota-Indicator	3912	Enumerated	3GPP
Indicates whether the granted quota should be used during announcement setup and playback. This AVP provides an option to either use or exclude the granted quota based on specific session requirements. Values: 0 (QUOTA_IS_NOT_USED_DURING_PLAYBACK): Excludes quota usage during playback. 1 (QUOTA_IS_USED_DURING_PLAYBACK): Includes quota usage during playback.
Radio-Frequency	3462	OctetString	3GPP
Identifies the radio frequency used for ProSe (Proximity-based Services) direct communication. The value format aligns with the ARFCN-ValueEUTRA-r9 ASN.1 data type defined in [TS36.331], which ensures compatibility with the standards for cellular frequency bands used in direct communication scenarios.
Radio-Parameter-Set-Info	3463	Grouped	3GPP
Provides information about a radio parameter set configured in the UE (User Equipment) for direct communication. This AVP contains the radio parameters for setting up the communication environment and includes a timestamp of when the configuration became active, which can be critical for session tracking and configuration management. The AVP structure is defined as follows: Radio-Parameter-Set-Values: Contains the set values used for configuration. Change-Time: A timestamp indicating when this parameter set became active.
Radio-Parameter-Set-Values	3464	OctetString	3GPP
Holds the specific configuration values for the radio parameters used by the UE for direct communication. The value format follows the SL-Preconfiguration-r12 ASN.1 data type, as described in [TS36.331], ensuring it is compatible with predefined standards for direct communication setups.
Radio-Resources-Indicator	3465	Enumerated	3GPP
Used to specify the type of radio resources employed for ProSe (Proximity Services) direct communication. This AVP identifies whether operator-provided or pre-configured radio resources were utilized during the communication session. Values: 1: Operator-provided radio resources 2: Configured radio resources
RAN-End-Timestamp	1301	Time	3GPP
Holds the UTC timestamp marking the end of the reported usage period within the volume container. This AVP enables accurate tracking of data usage over time, helping with billing and resource allocation.
RAN-Secondary-RAT-Usage-Report	1302	Grouped	3GPP
Contains the volume count for uplink and downlink data as reported by the Radio Access Network (RAN) for the secondary Radio Access Technology (RAT) associated with the bearer. This AVP includes timestamps and volume information, providing essential metrics for accurate data tracking and billing in multi-RAT environments. The AVP structure is defined as follows: Secondary-RAT-Type: Identifies the type of secondary RAT. RAN-Start-Timestamp: The timestamp marking the start of the reported usage period. RAN-End-Timestamp: The timestamp marking the end of the reported usage period. Accounting-Input-Octets: Count of octets received (uplink). Accounting-Output-Octets: Count of octets transmitted (downlink). 3GPP-Charging-Id: The charging identifier for IP-CAN bearer when session-based charging is active.
RAN-Start-Timestamp	1303	Time	3GPP
Stores the UTC timestamp marking the beginning of the reported usage period in the volume container.
Rate-Control-Max-Message-Size	3937	Unsigned32	3GPP
Holds the maximum data Protocol Data Unit (PDU) size in octets. This AVP is used for controlling data message sizes, ensuring that PDUs transmitted do not exceed a specified limit.
Rate-Control-Max-Rate	3938	Unsigned32	3GPP
Specifies the maximum number of data PDUs that can be transmitted per unit of time (as defined by the Rate-Control-Time-Unit AVP).
Rate-Control-Time-Unit	3939	Enumerated	3GPP
Used to specify the time unit for controlling the rate of data transmissions, such as data PDUs (Protocol Data Units). It enables the application of restrictions on data transmission over specified time periods, or it may indicate that no restrictions are applied. Values: 0 Unrestricted: No restrictions on the number of data PDUs 1 Minute: Rate control is applied per minute 2 Hour: Rate control is applied per hour 3 Day: Rate control is applied per day 4 Week: Rate control is applied per week
Rate-Element	2058	Grouped	3GPP
Defines a simple rate element that describes the charge rate based on one dimension, such as CC-Unit-Type. This AVP can represent units like time, volume, or money, and may include other charging elements like Unit-Cost and Unit-Value. The AVP structure is defined as follows: CC-Unit-Type (required): Specifies the unit type for the charge, such as TIME or MONEY. Charge-Reason-Code (optional): The reason code for the charge. Unit-Value (optional): Represents the value of the unit. Unit-Cost (optional): Specifies the cost per unit. Unit-Quota-Threshold (optional): Sets a threshold for quota consumption.
Read-Reply-Report-Requested	1222	Enumerated	3GPP
Indicates whether a read reply report is requested by the originator’s MMS User Agent. This AVP is often used in messaging services to provide read confirmation. Values: 0: No (report not requested) 1: Yes (report requested)
Real-Time-Tariff-Information	2305	Grouped	3GPP
Contains real-time tariff details received through SIP signaling, as specified in [TS29.658]. This AVP allows users to access tariff data instantaneously, such as cost per unit time or volume, often in XML format for flexibility. The AVP structure is defined as follows: Tariff-Information (optional): Holds structured tariff data, such as rate per unit. Tariff-XML (optional): XML-based representation of the tariff information, allowing detailed tariff structures to be described dynamically.
Reason-Header	3401	UTF8String	3GPP
Contains the content of the Reason header found in SIP BYE and CANCEL messages. It allows for multiple entries, enabling support for multiple Reason headers within a single SIP message.
Received-Talk-Burst-Time	1284	Unsigned32	3GPP
Represents the total duration of received talk bursts in a session, measured in seconds. It is useful for tracking the length of talk segments received in push-to-talk (PTT) or similar communication services.
Received-Talk-Burst-Volume	1285	Unsigned32	3GPP
Records the total volume of received talk bursts in bytes, allowing for monitoring and billing based on data volume received during a communication session.
Receiver	1014	UTF8String	oneM2M
Identifies the recipient of a Machine-to-Machine (M2M) request, typically an M2M node. The format follows M2M specifications for receiver identification, enabling accurate message routing to the intended M2M recipient.
Recipient-Address	1201	Grouped	3GPP
Holds the recipient details for a message, combining several components for thorough recipient identification. The AVP structure is defined as follows: Address-Type: Specifies the type of address. Address-Data: Contains the actual address data. Address-Domain: Identifies the address domain. Addressee-Type: Specifies the role or type of the addressee.
Recipient-Info	2026	Grouped	3GPP
Groups all information about a specific recipient of a message, supporting charging scenarios where a message may have multiple recipients. The AVP structure is defined as follows: Destination-Interface: Identifies the interface destination for message routing. Recipient-Address: Holds the recipient’s address details (can appear multiple times). Recipient-Received-Address: Specifies an address where the recipient received the message. Recipient-SCCP-Address: Contains the SCCP (Signaling Connection Control Part) address for the recipient, useful in SMS and telephony. SM-Protocol-ID: Provides the protocol identifier for short message (SM) delivery, specifically for Mobile Terminated (MT) SMS.
Recipient-Received-Address	2028	Grouped	3GPP
Captures the original address of the message recipient, as received before any alterations by intermediate nodes. It ensures that the unmodified address details are preserved, allowing for consistent correlation of recipient information across different stages in the message processing flow. The AVP structure is defined as follows: Address-Type: Specifies the type of the address. Address-Data: Holds the address details. Address-Domain: Specifies the domain of the address.
Recipient-SCCP-Address	2010	Address	3GPP
Provides the SCCP (Signaling Connection Control Part) called address for message delivery. Typically, this address belongs to the MSC, SGSN, or another serving node that facilitates message delivery to the user equipment (UE). The Recipient-SCCP-Address is an E.164 Global Title with an optional Point Code (ISPC), encoded in UTF-8. This address plays a key role in SMS and other signaling-based message routing within telecommunications.
Refund-Information	2022	OctetString	3GPP
Provides details relevant to the Online Charging System (OCS) for handling refunds. This AVP, if previously received in a Credit-Control-Answer (CCA) message, should be used in a Credit-Control-Request (CCR) during a refund scenario. It ensures that refund information is accurately carried over across interactions, supporting seamless refund processing within the charging system.
Related-Change-Condition-Information	3925	Grouped	3GPP
Used to convey details about a change condition that occurred on an alternate access within a multi-access PDN (Packet Data Network) connection. This AVP indicates how an indirect change in condition of one access can affect the other, providing context for why certain behaviors or status changes are observed on the current access. The AVP structure is defined as follows: SGSN-Address: The Serving GPRS Support Node (SGSN) address involved in the change. Change-Condition: A list indicating the specific conditions that triggered the change. 3GPP-User-Location-Info: The location information based on 3GPP standards. 3GPP2-BSID: Represents the 3GPP2 Base Station Identifier, giving additional location context. UWAN-User-Location-Info: Location information for Ultra-Wide Area Network users. Presence-Reporting-Area-Status: Indicates the presence reporting area status, which defines user access area status changes. User-CSG-Information: Closed Subscriber Group (CSG) information of the user, relevant for identifying specific network group data. 3GPP-RAT-Type: Radio Access Technology (RAT) type information, identifying the access technology used (e.g., LTE, UMTS).
Related-IMS-Charging-Identifier	2711	UTF8String	3GPP
Contains the Related IMS Charging Identifier (ICID) generated by either the Enhanced MSC Server or the P-CSCF during an SRVCC (Single Radio Voice Call Continuity) access transfer for a target access leg. It uniquely identifies the charging context related to an IMS session that has been transferred across access types.
Related-IMS-Charging-Identifier-Node	2712	Address	3GPP
Specifies the network node (such as an Enhanced MSC Server or the P-CSCF) that generated the Related IMS Charging Identifier (ICID). It is used to identify the origin node associated with the charging session, which is crucial for SRVCC transfer scenarios where the continuity of the charging session across network nodes is required.
Related-Trigger	3926	Grouped	3GPP
Holds information about trigger types for another access point within a multi-access PDN connection, particularly when there is an indirect change condition. This AVP is included if the Trigger AVP specifies an "indirect change condition" type, which allows it to facilitate the coordination of charging across multiple access types within a single PDN session. The AVP structure is defined as follows: Trigger-Type: (Multiple entries) Enumerates the types of triggers, with each representing a specific condition or event that influences the charging behavior across the connected accesses.
Relationship-Mode	2706	Enumerated	3GPP
Defines the trust relationship between the serving functional entity and a neighboring functional entity (e.g., a contact point in a neighboring network). It determines whether the entities are considered to belong to the same trust domain. Values: 0 Trusted: Part of the same trust domain 1 Non-trusted: Outside the trust domain
Relay-IP-address	4411	Address	3GPP
Specifies the IP address of a relay used in ProSe (Proximity-based Services) Direct Communication, specifically for a UE-to-Network relay. It provides the IP information needed for routing and connection in scenarios where the UE directly communicates through a relay node.
Remaining-Balance	2021	Grouped	3GPP
Provides details about the remaining balance in a subscriber's account. It can be useful for both online and offline charging contexts, offering insight into the current balance available for services. The AVP structure is defined as follows: Unit-Value: Specifies the amount remaining in the user's account, based on the unit type. Currency-Code: Indicates the currency in which the balance is represented.
Reply-Applic-ID	1223	UTF8String	3GPP
Identifies the "reply path" application responsible for receiving delivery reports, read-reply reports, or reply multimedia messages (MMs). It allows applications to address and handle message replies efficiently.
Reply-Path-Requested	2011	Enumerated	3GPP
Determines whether the Reply Path is set in a message, allowing for a reverse message route to be specified. This AVP indicates whether the reply path for a message is explicitly requested. Values: 0: No Reply Path Set 1: Reply Path Set
Reporting-Reason	872	Enumerated	3GPP
Specifies the reason for reporting quota usage. It can apply to one quota type or multiple quota types and may occur in either the Multiple-Services-Credit-Control AVP or Used-Service-Units AVP. Values: 0: THRESHOLD - Usage reporting due to reaching a specified threshold. 1: QHT - Reporting because the quota holding time was reached. 2: FINAL - Reporting due to service termination. 3: QUOTA_EXHAUSTED - Reporting due to quota exhaustion. 4: VALIDITY_TIME - Reporting due to credit authorization expiry. 5: OTHER_QUOTA_TYPE - Reporting triggered by another quota condition in multi-dimensional quota. 6: RATING_CONDITION_CHANGE - Reporting due to change in rating conditions (e.g., QoS, RAT). 7: FORCED_REAUTHORISATION - Reporting due to server-initiated reauthorization. 8: POOL_EXHAUSTED - Reporting due to pool exhaustion, where granted units are insufficient for a rating group. 9: UNUSED_QUOTA_TIMER - Reporting due to unused quota timer expiry.
Request-Body-Size	1015	Unsigned32	oneM2M
Represents the size of the request body in bytes. It is used to indicate the payload size in an M2M (Machine-to-Machine) communication, helping to monitor data consumption and ensure compliance with message size limitations.
Requested-Party-Address	1251	UTF8String	3GPP
Contains the address (SIP URI, Tel URI, or URN) of the originally addressed party in a SIP transaction or IMS/VCS (Voice Call Session) call. In IMS, it represents the address initially targeted in the request. For VCS, it identifies the call destination before Proxy Function processing.
Requested-PLMN-Identifier	3436	UTF8String	3GPP
Contains the Public Land Mobile Network (PLMN) identifier of a user targeted in a proximity request. It assists in identifying the PLMN associated with a specific user, especially in proximity service contexts.
Request-Headers-Size	1016	Unsigned32	oneM2M
Represents the size of the control information header in bytes. It provides insight into the overhead data in a request, helping to track and manage header information size for M2M requests effectively.
Request-Operation	1017	Enumerated	oneM2M
Identifies the specific type of operation being requested in a Diameter message. This AVP supports operation-based communication in Machine-to-Machine (M2M) systems, aligning with the operation types. Values: 1 Create: Indicates a request to create a new resource. 2 Retrieve: Indicates a request to retrieve an existing resource. 3 Update: Indicates a request to update an existing resource. 4 Delete: Indicates a request to delete an existing resource. 5 Notify: Indicates a request to send notifications about resource changes.
Requestor-PLMN-Identifier	3437	UTF8String	3GPP
Holds the PLMN identifier of the user who initiates a proximity request. This AVP allows the system to identify the originating Public Land Mobile Network (PLMN) of the requestor, helping to track and manage requests based on the initiating network.
Response-Body-Size	1018	Unsigned32	oneM2M
Represents the number of bytes in the body of a response message. This AVP is used to specify the size of the response payload in M2M interactions, facilitating data management by tracking the volume of data in responses.
Response-Headers-Size	1019	Unsigned32	oneM2M
Represents the number of bytes in the control information header of a response. This AVP is used to specify the size of the headers in the response message, enabling efficient data handling and transport size management for M2M communications.
Response-Status-Code	1020	Enumerated	oneM2M
Identifies the status of a request in the context of the OneM2M protocol. This AVP provides detailed feedback on the success or failure of an operation through a numeric code and its corresponding description. The RSC AVP categorizes responses into several classes such as Informational, Successful, Error, and System Error responses, each with a specific range of numeric codes. Values: Informational Response Class 1000: ACCEPTED Successful Response Class 2000: OK 2001: CREATED 2002: DELETED 2004: UPDATED Originator Error Response Class 4000: BAD_REQUEST 4004: NOT_FOUND 4005: OPERATION_NOT_ALLOWED 4008: REQUEST_TIMEOUT 4101: SUBSCRIPTION_CREATOR_HAS_NO_PRIVILEGE 4102: CONTENTS_UNACCEPTABLE 4103: ORIGINATOR_HAS_NO_PRIVILEGE 4104: GROUP_REQUEST_IDENTIFIER_EXISTS 4105: CONFLICT 4106: ORIGINATOR_HAS_NOT_REGISTERED 4107: SECURITY_ASSOCIATION_REQUIRED 4108: INVALID_CHILD_RESOURCE_TYPE 4109: NO_MEMBERS 4110: GROUP_MEMBER_TYPE_INCONSISTENT Receiver Error Response Class 5000: INTERNAL_SERVER_ERROR 5001: NOT_IMPLEMENTED 5103: TARGET_NOT_REACHABLE 5105: RECEIVER_HAS_NO_PRIVILEGE 5106: ALREADY_EXISTS 5203: TARGET_NOT_SUBSCRIBABLE 5204: SUBSCRIPTION_VERIFICATION_INITIATION_FAILED 5205: SUBSCRIPTION_HOST_HAS_NO_PRIVILEGE 5206: NON_BLOCKING_REQUEST_NOT_SUPPORTED 5207: NOT_ACCEPTABLE 5209: GROUP_MEMBERS_NOT_RESPONDED Network System Error Response Class 6003: EXTERNAL_OBJECT_NOT_REACHABLE 6005: EXTERNAL_OBJECT_NOT_FOUND 6010: MAX_NUMBER_OF_MEMBER_EXCEEDED 6020: MGMT_SESSION_CANNOT_BE_ESTABLISHED 6021: MGMT_SESSION_ESTABLISHMENT_TIMEOUT 6022: INVALID_CMDTYPE 6023: INVALID_ARGUMENTS 6024: INSUFFICIENT_ARGUMENTS 6025: MGMT_CONVERSION_ERROR 6026: MGMT_CANCELLATION_FAILED 6028: ALREADY_COMPLETE 6029: MGMT_COMMAND_NOT_CANCELLABLE
Role-Of-Node	829	Enumerated	3GPP
Specifies the role that the IMS or VCS node assumes during communication. Helps in identifying the functional role of a node within a session, especially in IMS and VCS environments. Values: 0 ORIGINATING_ROLE: Node serves the calling party. 1 TERMINATING_ROLE: Node serves the called party. 2 FORWARDING_ROLE: Node serves the forwarding party.
Role-Of-ProSe-Function	3438	Enumerated	3GPP
Identifies which PLMN contains the ProSe Function. Important for proximity services (ProSe) to ensure functions are assigned according to network locations, enhancing control over local and roaming users in ProSe scenarios. Values: 0 HPLMN: Home PLMN. 1 VPLMN: Visited PLMN. 2 Local PLMN: Local PLMN.
Route-Header-Received	3403	UTF8String	3GPP
Contains the information from the topmost route header in a received initial SIP INVITE or non-session-related SIP MESSAGE request. Used in SIP signaling to retain route information from incoming requests, crucial for tracking and routing in IMS networks.
Route-Header-Transmitted	3404	UTF8String	3GPP
Stores the route header information representing the destination for a transmitted initial SIP INVITE or non-session-related SIP MESSAGE request. Ensures that outgoing SIP requests have proper routing headers, maintaining the destination path as defined by the session policies.
Scale-Factor	2059	Grouped	3GPP
Represents a multiplication factor in a similar format to the Unit-Value AVP. Primarily used in charging or credit-control applications to adjust values based on the multiplication factor, such as when calculating costs. The AVP structure is defined as follows: Value-Digits: Specifies the main value for the scale factor. Exponent: Optional field that defines the exponent for scaling.
SCEF-Address	1317	Address	3GPP
Contains the IP address of the Service Capability Exposure Function (SCEF), which facilitates secure exposure of service capabilities and network resources. This AVP is important in Machine-Type Communication (MTC) and IoT applications, where it allows core network functions to securely communicate with external application servers.
SCS-Address	3941	Address	3GPP
Stores the IP address of the Service Capability Server/Application Server (SCS/AS). This server is integral in providing services to user equipment in IoT and M2M contexts. Used within network functions to route information and service requests to the correct application server in IoT and M2M communication scenarios, enabling connectivity between devices and network services.
SCS-AS-Address	3940	Grouped	3GPP
Holds the address information of the Service Capability Server/Application Server (SCS/AS). This AVP aggregates information necessary for routing and addressing the SCS/AS. Primarily used in Machine-Type Communication (MTC) and IoT setups where addressing and routing details are essential for the communication between network functions and application servers. The AVP structure is defined as follows: SCS-Realm: Represents the realm of the SCS/AS, providing the routing scope. SCS-Address: Specifies the IP address of the SCS/AS.
SCS-Realm	3942	DiameterIdentity	3GPP
Represents the Diameter realm identity for the Service Capability Server/Application Server (SCS/AS). This identity provides a logical separation and routing scope within Diameter. It is used to specify the realm in which the SCS/AS operates, helping to facilitate accurate routing in IoT and M2M communication scenarios.
SDP-Answer-Timestamp	1275	Time	3GPP
Stores the timestamp, in UTC format, indicating when the response to the Session Description Protocol (SDP) offer was received. Relevant in multimedia and IP-based communication applications, especially within IMS and SIP contexts, where SDP is used to initiate media sessions.
SDP-Media-Component	843	Grouped	3GPP
Contains detailed information about the media components used in an IP Multimedia Subsystem (IMS) session, including media type, codec details, and session-specific attributes. This AVP is crucial for tracking the specifics of media components in IMS sessions, such as audio or video streams, and their related configurations. The AVP structure is defined as follows: SDP-Media-Name: Specifies the name of the media component (e.g., audio, video). SDP-Media-Description: A list describing the specifics of the media component, like codec type or bitrate. Local-GW-Inserted-Indication: Indicates if a local gateway was inserted for the media session. IP-Realm-Default-Indication: Specifies if the IP realm is default, used for routing purposes in IMS. Transcoder-Inserted-Indication: Identifies if a transcoder is required for the media stream. Media-Initiator-Flag: Defines whether the media initiator flag is active, indicating session setup initiation. Media-Initiator-Party: Specifies the party initiating the media, such as "caller" or "callee." 3GPP-Charging-Id: The charging identifier for 3GPP networks; exclusive with Access-Network-Charging-Identifier-Value. Access-Network-Charging-Identifier-Value: Used for non-3GPP networks, such as Wi-Fi; mutually exclusive with 3GPP-Charging-Id. SDP-Type: Defines the type of SDP, distinguishing between initial offers, answers, or updates within the SDP negotiation. Either 3GPP-Charging-Id or Access-Network-Charging-Identifier-Value should be present, depending on whether the IP-CAN is 3GPP-defined (e.g., GPRS) or non-3GPP-defined (e.g., Wi-Fi).
SDP-Media-Description	845	UTF8String	3GPP
Holds content of various SDP lines (i=, c=, b=, k=, a=, etc.) for specifying attributes in the media description of a session. This AVP aligns with the SDP-Media-Name to provide context about the media (e.g., codec information, bandwidth).
SDP-Media-Name	844	UTF8String	3GPP
Holds the content of the "m=" line within a Session Description Protocol (SDP) media description. This AVP encapsulates critical details about media streams in SDP, as defined in [RFC4566]. The "m=" line in SDP describes media type, transport protocol, port, and media format, which are essential for establishing multimedia communication sessions.
SDP-Offer-Timestamp	1274	Time	3GPP
Captures the UTC time when an SDP offer was made. This AVP provides timing context in the offer-answer exchange, particularly useful in call setup and media negotiations in IMS.
SDP-Session-Description	842	UTF8String	3GPP
Encapsulates content from the Session Description Protocol (SDP) session description lines, such as i=, c=, b=, k=, a=, and other similar fields, as defined in [RFC4566]. These fields collectively describe the session's media parameters, transport information, and attributes.
SDP-TimeStamps	1273	Grouped	3GPP
Provides timestamps associated with the Session Description Protocol (SDP) negotiation process. It specifically records the times when the SDP offer and SDP answer were generated, which is crucial for session tracking, synchronization, and troubleshooting in multimedia communication systems. The AVP structure is defined as follows: SDP-Offer-Timestamp: Description: Indicates the time when the SDP offer was created and sent. SDP-Answer-Timestamp: Indicates the time when the SDP answer was created and received in response to the SDP offer.
SDP-Type	2036	Enumerated	3GPP
Specifies whether the SDP media component represents an offer or an answer, aiding in identifying the role of SDP messages in media negotiation and session establishment. Values: 0 SDP Offer: Represents the initial SDP message proposing a media session. 1 SDP Answer: Represents the response SDP message accepting or modifying the offer.
Secondary-RAT-Type	1304	OctetString	3GPP
Indicates the Secondary Radio Access Technology (RAT) type as provided by the RAN. Used for cases involving secondary RAT types, such as 5G NR, to ensure seamless network interoperability and traffic management.
Served-Party-IP-Address	848	Address	3GPP
Holds the IP address of the calling or called party, depending on which party the P-CSCF serves. Essential for session routing and call processing in IMS, provided exclusively by the P-CSCF.
Service-Data-Container	2040	Grouped	3GPP
Facilitates the transmission of service-specific data for flow-based or application-based charging. It identifies changes in charging conditions and reports metrics such as volume counts (uplink and downlink), elapsed time, or event counts for service data flows. The AVP structure is defined as follows: AF-Correlation-Information: Application Function correlation info. Charging-Rule-Base-Name: Charging rule base name for the flow or service. Accounting-Input-Octets: Uplink volume in octets. Accounting-Output-Octets: Downlink volume in octets. Local-Sequence-Number: Local sequence number for tracking. QoS-Information: Quality of Service (QoS) parameters. Rating-Group: Identifies the rating group for the flow. Change-Time: Timestamp of the last change in conditions. Service-Identifier: Identifies the service associated with this container. Service-Specific-Info: Additional service-specific details. ADC-Rule-Base-Name: ADC rule base name for application detection. SGSN-Address: SGSN IP address associated with the flow. Time-First-Usage: First usage timestamp. Time-Last-Usage: Last usage timestamp. Time-Usage: Total time duration of usage. Change-Condition: Indicates conditions that triggered a change. 3GPP-User-Location-Info: 3GPP user location information. 3GPP2-BSID: 3GPP2 base station identifier. UWAN-User-Location-Info: User location in an untrusted WLAN. TWAN-User-Location-Info: User location in a trusted WLAN. Sponsor-Identity: Identifies the sponsor of the session. Application-Service-Provider-Identity: Service provider identity for the application. Presence-Reporting-Area-Information: Presence reporting details. Presence-Reporting-Area-Status: Status of the presence reporting area. User-CSG-Information: Closed Subscriber Group (CSG) information. 3GPP-RAT-Type: Radio Access Technology type. Related-Change-Condition-Information: Related change condition details. Serving-PLMN-Rate-Control: Rate control information for the serving PLMN. APN-Rate-Control: Rate control information for the APN. 3GPP-PS-Data-Off-Status: Status of data-off feature in the 3GPP network. Traffic-Steering-Policy-Identifier-DL: Identifier for downlink traffic steering policies. Traffic-Steering-Policy-Identifier-UL: Identifier for uplink traffic steering policies. VoLTE-Information: VoLTE-specific service details.
Service-ID	855	UTF8String	3GPP
Identifies the service being hosted or facilitated by the MRFC, such as a specific conference or AoC service. For conferencing services, this AVP holds the Conference ID, ensuring that participants and service instances are appropriately identified. The AVP plays a critical role in services where tracking distinct identifiers is necessary to facilitate accurate charging, resource allocation, or service continuity.
Service-Information	873	Grouped	3GPP
Aggregates various service-specific information elements in one container, facilitating the inclusion of additional 3GPP service data as needed for specific applications. This allows for extensive information about different telecommunications services and protocols. The AVP structure is defined as follows: Subscription-Id: Identifies the subscriber for billing and management purposes. AoC-Information: Details Advice of Charge information for services with cost-related updates. PS-Information: Represents Packet-Switched service data, relevant to mobile data sessions. IMS-Information: Contains data specific to the IP Multimedia Subsystem (IMS). MMS-Information: Provides information related to Multimedia Messaging Services. LCS-Information: Delivers data on Location Services for user positioning. PoC-Information: Contains Push-to-talk over Cellular information. MBMS-Information: Represents Multimedia Broadcast Multicast Services details. SMS-Information: Stores information for Short Message Service, such as message data and routing. VCS-Information: Data related to Voice Call Continuity services. MMTel-Information: Contains Multimedia Telephony service details. ProSe-Information: Provides Proximity Services data, supporting device-to-device communication. Service-Generic-Information: A generic container for service data not covered by specific AVPs. IM-Information: Stores Instant Messaging information. DCD-Information: Data for Device Connection Data, specific to device connectivity. M2M-Information: Provides Machine-to-Machine communication details. CPDT-Information: Contains data for Charging Data Triggered applications.
Service-Mode	2032	Enumerated	3GPP
Specifies the operational mode for various MMTel supplementary services such as Communication Diversion (CDIV), Communication Barring (CB), and Explicit Call Transfer (ECT). It defines the specific behavior or configuration of these services, enabling precise control over telecommunication service features. Values: 0: Communication Forwarding Unconditional (CFU) 1: Communication Forwarding Busy (CFB) 2: Communication Forwarding No Reply (CFNR) 3: Communication Forwarding on Not Logged-In (CFNL) 4: Communication Deflection (CD) 5: Communication Forwarding on Subscriber Not Reachable (CFNRc) 6: Incoming Call Barring (ICB) 7: Outgoing Call Barring (OCB) 8: Anonymous Communication Rejection (ACR) 9: Blind Transfer 10: Consultative Transfer 11: Three-Party Call (3PTY) 12: Advice of Charge - S (AoC-S) 13: Advice of Charge - D (AoC-D) 14: Advice of Charge - E (AoC-E) ≥ 1024: Reserved for specific Network/Manufacturer supplementary service variants
Service-Specific-Data	863	UTF8String	3GPP
Holds a UTF-8 encoded string value that specifies data relevant to a particular service. This data could represent metadata, configuration settings, or any service-related information essential for the application server or network element handling the service.
Service-Specific-Info	1249	Grouped	3GPP
Used to contain service-specific data within the Diameter protocol. This AVP is generally populated by an Application Server (AS) in the case of IMS (IP Multimedia Subsystem) charging, by a PCEF (Policy and Charging Enforcement Function) for PS (Packet-Switched) domain charging with predefined PCC (Policy and Charging Control) rules, or by a Proxy for VCS (Voice Call Continuity) charging scenarios. The AVP structure is defined as follows: Service-Specific-Data: Holds specific data related to the service, which may vary depending on the application. This parameter allows service-specific information to be transmitted within Diameter messages. Service-Specific-Type: An identifier for the type of service-specific data in Service-Specific-Data. This helps in interpreting the content of the data, ensuring accurate handling and processing by various network components.
Service-Specific-Type	1257	Unsigned32	3GPP
Unsigned integer that specifies the type of service-specific data provided in the Service-Specific-Data AVP. This AVP functions as a classifier, allowing network elements to identify and process the service-specific data correctly. It is especially relevant for systems where multiple types of services and corresponding data are handled concurrently, ensuring the correct application of policies and charging based on the service type.
Serving-Node-Identity	3929	DiameterIdentity	3GPP
Identifies the specific Serving Node involved in a particular transaction or report. For example, in the SCEF (Service Capability Exposure Function), this AVP might hold the identifier of the MME (Mobility Management Entity) serving the user equipment. This AVP is critical in scenarios where the network element generating a report needs to provide details about which Serving Node managed the session, aiding in troubleshooting, analytics, and accurate billing.
Serving-Node-Type	2047	Enumerated	3GPP
Specifies the type of Serving Node involved in a particular session or transaction. This AVP helps differentiate between various nodes in the network infrastructure, which may each play a unique role in managing the user’s session or traffic. This AVP is particularly valuable for charging, reporting, and session management purposes, as it enables accurate identification of the network node type. Values: 0: SGSN (Serving GPRS Support Node) 1: PMIPSGW (Proxy Mobile IPv6 Serving Gateway) 2: GTPSGW (GTP Serving Gateway) 3: ePDG (Evolved Packet Data Gateway) 4: hSGW (Home Serving Gateway) 5: MME (Mobility Management Entity) 6: TWAN (Trusted Wireless Access Network)
Session-Direction	2707	Enumerated	3GPP
Defines the direction of a session request in the control plane, particularly relevant for NNI (Network-to-Network Interface) usage in interconnection and roaming scenarios. This AVP can indicate whether the session is an inbound or outbound request, facilitating control and routing decisions for network elements involved in roaming or interconnection. Knowing the session direction helps operators manage and monitor service flows and associated charges accurately. Values: 0: Inbound – Indicates an inbound service request from an external network. 1: Outbound – Indicates an outbound service request to an external network.
SGi-PtP-Tunnelling-Method	3931	Enumerated	3GPP
Specifies the tunneling method used for SGi Point-to-Point (PtP) connections over non-IP PDN (Packet Data Network) types. This AVP determines if the PtP connection is based on UDP/IP or another protocol. Such identification is essential in cases where non-IP PDN connections require special handling or configuration in the network, enabling efficient routing and processing based on the tunneling method. Values: 0: UDP_IP_based – Indicates that the tunneling is based on UDP over IP. 1: Others – Indicates an alternative tunneling method is in use, which may vary by network configuration or vendor implementation.
SGSN-Address	1228	Address	3GPP
Contains the IP address of the Serving GPRS Support Node (SGSN) or an equivalent serving node used during a data report. This AVP is critical for identifying the node involved in processing or reporting specific network data, enabling accurate association of records with the correct network elements. This IP address can represent nodes like the Serving Gateway (S-GW), Access Gateway (AGW), evolved Packet Data Gateway (ePDG), Trusted Wireless Access Gateway (TWAG), and the Mobility Management Entity (MME). Proper identification of these elements supports seamless data tracking, billing, and session management within complex network structures.
SGW-Address	2067	Address	3GPP
Holds the IP address of the Serving Gateway (SGW) Node involved in a specific transaction or data session. The SGW acts as a pivotal point in the network, directing user traffic and handling data connections between the user equipment and the network. By including this AVP, the Diameter protocol can accurately pinpoint the SGW in charge of a session, facilitating proper session management, charging, and reporting. This AVP is especially important for tracking and managing SGW usage and events in IP-based networks.
SGW-Change	2065	Enumerated	3GPP
Indicates whether an Accounting Request (ACR) command has been initiated due to a change in the serving node. This change may result from node transitions such as a shift from one Serving Gateway (SGW) to another, or similar changes involving other network nodes like the ePDG (evolved Packet Data Gateway), TWAG (Trusted Wireless Access Gateway), or HSGW (Home Serving Gateway). This AVP is particularly relevant when tracking session continuity and charging across network node transitions. Values: 0: ACR_Start_NOT_due_to_SGW_Change – Indicates that the session has started without a change in the SGW. 1: ACR_Start_due_to_SGW_Change – Indicates that the session has started specifically due to an SGW change.
SIP-Method	824	UTF8String	3GPP
Specifies the name of the SIP (Session Initiation Protocol) method that has triggered the sending of an Accounting Request (ACR) to the Charging Data Function (CDF) or a Credit Control Request (CCR) to the Online Charging Function (OCF). This AVP is essential for identifying the specific SIP command in play, such as "INVITE" or "UPDATE," allowing the network to handle and account for different types of SIP-based session events accurately. The identification of SIP methods supports session control, billing, and data tracking, particularly in real-time communication scenarios.
SIP-Request-Timestamp	834	Time	3GPP
Records the precise time of a SIP request, such as an "INVITE" or "UPDATE" request, in Coordinated Universal Time (UTC) format. This AVP is essential for tracking when a SIP request was issued, which is crucial in scenarios requiring precise timing for billing, troubleshooting, or compliance purposes. By marking the exact moment of the SIP request, this AVP aids in accurate event sequencing and latency measurement in SIP signaling.
SIP-Request-Timestamp-Fraction	2301	Unsigned32	3GPP
Provides a finer level of detail to the SIP request timestamp by storing the millisecond fraction of the SIP-Request-Timestamp. This AVP enables high-precision time tracking, which is critical in high-performance networks and scenarios where every millisecond of latency or delay impacts service quality or billing accuracy. This AVP works in conjunction with the SIP-Request-Timestamp to ensure that timestamps are not limited to whole seconds, allowing for microsecond-level event tracking.
SIP-Response-Timestamp	835	Time	3GPP
Captures the UTC time of a response to a SIP request, such as a "200 OK" response. This timestamp is vital for evaluating response times and latency within SIP signaling flows, as it marks when the system processed and replied to a SIP request. This AVP is particularly important in monitoring and optimizing the responsiveness of SIP-based applications, as well as for billing and compliance purposes where response times must be logged precisely.
SIP-Response-Timestamp-Fraction	2302	Unsigned32	3GPP
Stores the milliseconds fraction of the SIP-Response-Timestamp. It enhances the precision of the SIP-Response-Timestamp by accounting for sub-second intervals, thereby allowing for accurate measurement of response times down to milliseconds. This AVP is valuable for performance monitoring, as it enables network administrators to track delays accurately, even for short-lived SIP transactions, and provides granular detail for troubleshooting, optimizing response times, and ensuring the timely delivery of SIP responses.
SM-Device-Trigger-Indicator	3407	Enumerated	3GPP
Specifies whether a Short Message (SMS) is related to a Device Trigger event and, if so, indicates the type of action requested. Device Trigger events are specific SMS messages designed to initiate or manage remote actions on a device. This AVP supports various Device Trigger operations, such as requests, replacements, and recalls of device triggers. Values: 0 (Not DeviceTrigger): Indicates the SMS is not related to any Device Trigger. 1 (Device Trigger request): Initiates a new Device Trigger request to the target device. 2 (Device Trigger replace): Replaces an existing Device Trigger with new trigger data. 3 (Device Trigger recall): Withdraws a previously sent Device Trigger.
SM-Device-Trigger-Information	3405	Grouped	3GPP
Contains detailed information for device-triggered SMS events. This AVP is utilized in scenarios where specific device trigger settings are required within a Short Message (SMS). The data in this AVP supports the delivery and configuration of device triggers, including details such as node address, reference numbers, and priority levels. The AVP structure is defined as follows: MTC-IWF-Address: IP address of the MTC Interworking Function responsible for the device trigger. Reference-Number: Unique identifier for the trigger event, allowing differentiation among triggers. Serving-Node: Identifies the serving node managing the trigger process, e.g., SMS Gateway or specific SMS server. Validity-Time: Specifies the expiration time for the trigger action, ensuring timeliness. Priority-Indication: Enum indicating the priority level for processing the trigger, which can affect delivery time. Application-Port-Identifier: Port number associated with the application requiring the trigger, assisting in route-specific handling.
SM-Discharge-Time	2012	Time	3GPP
Records the exact time associated with an SMS delivery or status event, particularly for scenarios where the SMS report (such as a Status-Report) is billed. This AVP allows the recording of the time an SMS is delivered, returned, or another event that modifies the Short Message’s status. When paired with the SM-Status AVP, this AVP offers a clear, timestamped record of delivery events, ensuring the accuracy of billing or reporting processes. The SM-Discharge-Time must be accurately encoded, aligning with SMS-specific time encoding standards.
SM-Message-Type	2007	Enumerated	3GPP
Specifies the type of SMS message that initiated a charging interaction. This AVP categorizes SMS messages to ensure accurate charging and reporting in SMS-based communication scenarios. Values: 0 (SUBMISSION): Indicates an SMS submission by the user. 1 (DELIVERY_REPORT): Refers to a delivery report generated by the SMS network. 2 (SM Service Request): Represents an SMS service request initiated for a specific service. 3 (T4 Device Trigger): Indicates a Device Trigger in a T4 network context. 4 (SM Device Trigger): Denotes a Device Trigger in an SMS-specific context. 5 (MO-SMS T4 submission): Indicates a Mobile-Originated SMS submission in a T4 environment.
SM-Protocol-ID	2013	OctetString	3GPP
Identifies the specific protocol used for a Short Message (SM) in SMS-based communications. This AVP supports encoding the protocol or application layer details for SMS services, ensuring the accurate handling and routing of messages based on the underlying protocol. This AVP may include values that represent protocol specifics such as SMS over GSM, SMS over CDMA, or any proprietary protocols, providing flexibility in handling diverse SMS transport formats.
SMSC-Address	2017	Address	3GPP
Carries the address of the Short Message Service Center (SMSC) responsible for processing and routing SMS messages. This AVP provides critical addressing information to network elements involved in SMS transmission, ensuring messages reach the correct SMSC for delivery. The SMSC address typically follows the standard address format (e.g., IP or E.164 format), facilitating SMS routing in both inter-network and intra-network messaging scenarios.
SM-Sequence-Number	3408	Unsigned32	3GPP
Used to identify the sequence number of a Short Message (SM) within a concatenated message sequence in SMS Offline Charging scenarios. This AVP enables the charging system to track each segment of a concatenated SMS, ensuring that individual parts are processed in the correct order. In concatenated SMS scenarios, each message part is assigned a unique sequence number, which helps reconstruct the complete message on the receiving side and supports accurate billing for the entire message.
SM-Service-Type	2029	Enumerated	3GPP
Specifies the type of Short Message (SM) service that triggered the charging interaction, supporting various value-added SMS services (VAS4SMS) as defined in [TS22.142]. This AVP allows differentiation of SMS service types for billing and service-specific processing. Values: 0 (VAS4SMS Short Message content processing): Processing of message content for value-added services. 1 (VAS4SMS Short Message forwarding): Forwarding of the SMS to another destination. 2 (VAS4SMS Short Message Forwarding multiple subscriptions): Forwarding SMS to multiple subscribers. 3 (VAS4SMS Short Message filtering): Filtering messages based on content or sender. 4 (VAS4SMS Short Message receipt): Receipt acknowledgment for the SMS. 5 (VAS4SMS Short Message Network Storage): Storing the SMS within the network for later retrieval. 6 (VAS4SMS Short Message to multiple destinations): Sending the SMS to multiple recipients. 7 (VAS4SMS Short Message Virtual Private Network (VPN)): SMS service within a VPN context. 8 (VAS4SMS Short Message Auto Reply): Automated reply to the received SMS. 9 (VAS4SMS Short Message Personal Signature): Appending a personal signature to the SMS. 10 (VAS4SMS Short Message Deferred Delivery): Scheduled or delayed delivery of the SMS. 11-99: Reserved for 3GPP-defined SM services. 100-199: Reserved for vendor-specific SM services. This AVP must be present when the SM-Message-Type AVP has a value of 2 (SM Service Request), enabling the system to charge based on the specific SMS service provided.
SMS-Information	2000	Grouped	3GPP
Designed to encapsulate detailed SMS-related service-specific information, such as originator, recipient, protocol details, and other associated metadata for billing and analysis in charging applications. This AVP supports a variety of attributes to thoroughly document each aspect of an SMS interaction within the Diameter protocol, often for billing and charging scenarios. The AVP structure is defined as follows: SMS-Node: Identifies the SMS node involved in the transaction (e.g., SMSC). Client-Address: Specifies the IP address of the client involved in the SMS transaction. Originator-SCCP-Address: Holds the SCCP (Signaling Connection Control Part) address of the SMS originator. SMSC-Address: Represents the address of the SMSC (Short Message Service Center) that processed the SMS. Data-Coding-Scheme: Specifies the data encoding scheme used for the SMS content, aiding in interpreting message content. SM-Discharge-Time: Indicates the time of message discharge or delivery in UTC format. SM-Message-Type: Defines the type of SMS message, such as submission, delivery report, or device trigger. Originator-Interface: Provides interface-specific details about the message originator. SM-Protocol-ID: Indicates the protocol ID used for the message, which specifies the nature of the SMS service. Reply-Path-Requested: Boolean value indicating if the reply path is requested for the SMS. SM-Status: Encodes the status of the SMS, such as delivered, pending, or failed. SM-User-Data-Header: Contains the User Data Header (UDH) if used in the SMS message, often for concatenated or formatted messages. Number-Of-Messages-Sent: Tracks the number of SMS messages sent, useful for reporting and billing. SM-Sequence-Number: Defines the sequence number for concatenated messages, allowing correct reconstruction of multi-part SMS messages. Recipient-Info: A grouped list that includes information about the SMS recipients. Originator-Received-Address: Specifies the address the originator received the message from, in cases involving forwarding. SM-Service-Type: Details the specific type of SMS service that triggered the transaction (e.g., auto-reply, forwarding). SMS-Result: Indicates the result of the SMS transaction, useful for error handling or success confirmation. SM-Device-Trigger-Indicator: Specifies whether the SMS includes a device trigger and defines the requested action. SM-Device-Trigger-Information: Grouped AVP holding information specific to device-triggered SMS messages, such as the MTC-IWF address and serving node. MTC-IWF-Address: IP address of the MTC Inter-Working Function. Application-Port-Identifier: Identifies the application port involved in the SMS transaction. External-Identifier: Optional identifier for external reference or tracking within the SMS service.
SMS-Node	2016	Enumerated	3GPP
Identifies the functional role of the SMS node in the context of a charging event. This AVP helps classify the node's role, which can influence charging and routing decisions. Values: 0 (SMS Router): Acts solely as an SMS router within the network. 1 (IP-SM-GW): Acts as an IP Short Message Gateway, facilitating SMS over IP-based networks. 2 (SMS Router and IP-SM-GW): Acts both as an SMS Router and an IP-SM-GW, performing dual functions. 3 (SMS-SC): Serves as the SMS Service Center (SMSC), handling message storage and forwarding.
SMS-Result	3409	Unsigned32	3GPP
Records the outcome of an attempt to submit or deliver a Short Message (SM). This result can indicate success, failure, or any intermediary state that may require further processing. It is useful for tracking SMS transaction statuses within charging and billing records and may include result codes to specify the success or error state of the transaction.
SM-Status	2014	OctetString (1 byte)	3GPP
Provides status information about the Short Message (SM) delivery, typically as a 1-octet (1 byte) code. This status indicates whether the message was delivered, pending, or encountered any issues during transmission. The encoding of the status byte allows for quick reference in monitoring or troubleshooting SMS delivery outcomes.
SM-User-Data-Header	2015	OctetString	3GPP
Contains any user data header (UDH) extracted from the user data portion of a Short Message (SM). Encoded as an OctetString, this AVP follows the encoding standards in [TS23.040]. The UDH can be used to add additional information to the message, such as concatenated message sequence indicators or multimedia identifiers, without affecting the main message content. Any padding bits are excluded from the header, ensuring efficient data handling.
Start-of-Charging	3419	Time	3GPP
Denotes the starting point for charging in a call or session, expressed in UTC time format. Depending on the configuration, it may indicate the time the call setup was initiated or the time the call was answered. This AVP is crucial in accurately calculating session or call durations for billing and charging purposes. It provides the time origin against which usage or events will be measured.
Start-Time	2041	Time	3GPP
Captures the UTC time at the beginning of a user session, either at the Serving Gateway (S-GW)/Packet Gateway (P-GW) for data sessions or the Mobile Switching Center (MSC) for voice calls. This AVP is fundamental in session management and charging calculations, as it marks the start of resource usage, enabling accurate tracking of session duration.
Status-AS-Code	2702	Enumerated	3GPP
Indicates an abnormal response code returned by an Application Server (AS) when it does not respond normally to a Serving Call Session Control Function (S-CSCF) request. The values include error classes such as 4xx and 5xx SIP response codes, as well as a timeout. When the AS responds with a normal response (e.g., SIP 200 OK), this AVP is not included in the Application-Server-Information AVP. Values: 0: 4xx — Client error response 1: 5xx — Server error response 2: Timeout — Response time exceeded
Stop-Time	2042	Time	3GPP
Holds the termination time in UTC for a user session or voice call. For data sessions, this AVP represents the time a session ends at the Serving Gateway (S-GW) or Packet Gateway (P-GW). In voice call scenarios, it marks the call’s end time at the Mobile Switching Center (MSC). This AVP is critical for billing and tracking session duration, ensuring accurate resource utilization measurements.
Subgroup-Name	1021	UTF8String	oneM2M
Identifies the subgroup associated with a request, especially in scenarios involving a fanning operation initiated by an Intelligent Network (IN). This AVP’s value aligns with the "groupName" attribute for a subgroup as detailed in [Table 7.4.14.1-137] of the relevant standards, ensuring consistency in identifying and managing subgroup members in multi-party requests or operations.
Submission-Time	1202	Time	3GPP
Records the exact UTC time at which a message, such as an SMS or data session request, was initially submitted. This timestamp plays a crucial role in tracking message flow, coordinating time-sensitive actions, and supporting billing records for transactional events within networked systems.
Subscriber-Role	2033	Enumerated	3GPP
Identifies the role of a subscriber in the context of MMTel supplementary services, particularly in mobile multimedia telecommunications (MMTel) interactions. Values: 0: Originating — Indicates the subscriber initiated the service or communication. 1: Terminating — Indicates the subscriber is the receiving or ending party. Although specified here, it is noted that this AVP is not currently in active use.
Supplementary-Service	2048	Grouped	3GPP
Contains detailed data related to a specific MMTel (Multimedia Telephony) supplementary service. This grouped AVP organizes various parameters critical for managing and billing supplementary services, providing insights into both the type and the configuration of the service. The AVP structure is defined as follows: MMTel-SService-Type: Defines the type of MMTel service provided. Service-Mode: Indicates the mode of service, such as forwarding or barring. Number-Of-Diversions: Tracks how many times the call or service has been diverted. Associated-Party-Address: The address of the associated party, typically for diversions or forwarded communications. Service-ID: Identifies the particular service instance. Change-Time: The time of any service-related changes. Number-Of-Participants: Specifies the count of users or entities involved in the session. Participant-Action-Type: Defines the action taken by a participant, such as joining or leaving a call. CUG-Information: Contains Closed User Group data if applicable. AoC-Information: Advice of Charge details, providing charging instructions for supplementary services.
TAD-Identifier	2717	Enumerated	3GPP
Specifies the type of access network to be used for session termination, distinguishing between Circuit-Switched (CS) and Packet-Switched (PS) networks. This AVP assists in directing termination operations based on the type of access network, optimizing the handling of multimedia sessions. Values: 0: CS - (Circuit-Switched) 1: PS - (Packet-Switched)
Talk-Burst-Exchange	1255	Grouped	3GPP
Contains charging data related to talk burst exchanges in a Push-to-Talk over Cellular (PoC) session. This grouped AVP collects metrics and timestamps that represent the volume, timing, and participant details of talk bursts, offering granular insight into the PoC session’s usage. The AVP structure is defined as follows: PoC-Change-Time: (Mandatory) Records the exact UTC time of a PoC session change. Number-Of-Talk-Bursts: Indicates the count of talk bursts initiated by the participant. Talk-Burst-Volume: Total volume of data (in bytes) transmitted during talk bursts. Talk-Burst-Time: Cumulative time spent on outgoing talk bursts. Number-Of-Received-Talk-Bursts: Specifies the count of talk bursts received. Received-Talk-Burst-Volume: Volume of data (in bytes) for received talk bursts. Received-Talk-Burst-Time: Time spent on listening to incoming talk bursts. Number-Of-Participants: Indicates the number of participants in the PoC session. PoC-Change-Condition: Describes the condition leading to a session change, e.g., session initiation or participant change.
Talk-Burst-Time	1286	Unsigned32	3GPP
Represents the total duration, in seconds, of all talk bursts transmitted by a participant in a Push-to-Talk over Cellular (PoC) session. This AVP is integral to tracking the active talk time within a session, providing data for both usage monitoring and billing purposes. By aggregating the talk burst times, this AVP offers insight into user interaction patterns in real-time communication.
Talk-Burst-Volume	1287	Unsigned32	3GPP
Holds the total volume, in bytes, of data transmitted through talk bursts during a PoC session. It measures the outgoing data payload of a user’s talk bursts, which is essential for monitoring data usage and facilitating accurate billing. This AVP is used alongside other session metrics to analyze communication traffic and resource utilization.
Target-ID	1022	UTF8String	oneM2M
Used to specify the target URL or resource identifier for a Machine-to-Machine (M2M) request. This AVP can either hold a URL, which points to the specific resource in an M2M network, or a resource identifier formatted according to the standards outlined in the protocol’s clause [6.3.4].
Target-IP-Address	4412	Address	3GPP
Used in ProSe (Proximity Services) Direct one-to-one communication scenarios. It holds the IP address that serves as the destination for direct communication between devices. This AVP facilitates peer-to-peer communication by specifying the intended IP address of the recipient in a ProSe interaction.
Tariff-Information	2060	Grouped	3GPP
Contains detailed information about the active tariff associated with a specific service, either defined by the local provider or a third-party provider. It provides the current tariff details, the scheduled tariff switch time, and the upcoming tariff, if applicable. This AVP is essential for real-time billing adjustments and for informing users of changes in service costs during a session. Additionally, it supports complex scenarios where tariffs may chain across intermediate operators, each potentially defining their own tariff structure. The AVP structure is defined as follows: Current-Tariff: Contains details of the active tariff for the service, including parameters like base rate and usage charges. Tariff-Time-Change: Indicates the scheduled time at which a new tariff will come into effect. Next-Tariff: Contains details of the upcoming tariff that will replace the current one after the tariff switch time.
Tariff-XML	2306	UTF8String	3GPP
Carries tariff and add-on charge information as an XML-encoded string, used primarily within SIP transactions to convey detailed pricing structures, usage policies, or additional charges. This XML body aligns with [TS29.658] and allows the exchange of dynamic billing data between network elements, supporting real-time charging updates and service adjustments. The XML format provides a structured way to represent complex tariff data, which is essential for billing transparency and customization in telecom networks.
Teleservice	3413	OctetString	3GPP
Specifies the teleservice associated with a voice call, indicating the type of service, such as voice or messaging, requested by the subscriber. This AVP enables accurate service identification within the charging and billing systems, allowing network operators to distinguish and bill for specific teleservices utilized by users.
Terminating-IOI	840	UTF8String	3GPP
Holds the Inter Operator Identifier (IOI) for the terminating network, as assigned by the IMS Network Element during a SIP response. This identifier is critical for routing and billing purposes, distinguishing between the network of the serving user, the home network, and other involved parties. It defines specific "Type 1," "Type 2," and "Type 3" IOIs, which cover different scenarios of session redirection, roaming, and service provider interactions. Each IOI type helps clarify which network or operator is handling the SIP request or response, ensuring correct inter-operator routing, billing, and service accountability.
3GPP2-BSID	Defined in Tgpp2AvpCodes.BSID	OctetString	3GPP
Identifies the Base Station Identifier (BSID) where the User Equipment (UE) is currently located. This BSID typically includes location-specific details such as the Cell-ID, System Identifier (SID), or Network Identifier (NID), depending on the cellular network's configuration. By pinpointing the UE's current base station, this AVP supports accurate location reporting for network management, billing, and service provision.
Multiple-Services-Credit-Control	456	Grouped	IETF
Designed for use in Diameter credit control applications to manage and control credit for multiple services simultaneously. This AVP contains additional charging and control parameters unique to 3GPP networks, enabling granular management of services provided to users. The AVP structure is defined as follows: Granted-Service-Unit: Specifies the units (e.g., time, volume) allowed for service consumption. Requested-Service-Unit: Represents the units requested by the client application. Used-Service-Unit: A collection of records detailing the units that have already been consumed. Service-Identifier: Identifies the specific service(s) for which credit is being managed. Rating-Group: An identifier used to group services for rating and charging purposes. G-S-U-Pool-Reference: References a pool of granted service units for shared quota usage. Validity-Time: Specifies the validity duration for the granted units. Result-Code: Indicates the outcome of the credit control request (e.g., success or failure). Final-Unit-Indication: Indicates the final unit behavior once the granted service units are exhausted. Time-Quota-Threshold: Defines a threshold for time-based quota usage. Volume-Quota-Threshold: Sets a threshold for volume-based quota usage. Unit-Quota-Threshold: Establishes a threshold for generic unit-based quotas. Quota-Holding-Time: Specifies how long the quota is retained after service termination. Quota-Consumption-Time: Defines the time taken to consume the quota. Reporting-Reason: Lists reasons for generating interim reports. Trigger: Specifies conditions that trigger quota usage reporting. PS-Furnish-Charging-Information: Provides packet-switched charging-related information. Refund-Information: Contains details about refunds for unused units. AF-Correlation-Information: Correlates application-specific data with the credit control process. Envelope: A structure used for envelope reporting in real-time monitoring. Envelope-Reporting: Indicates the type of envelope reporting mechanism. Time-Quota-Mechanism: Defines the mechanism for enforcing time-based quotas. Service-Specific-Info: Contains additional service-specific details if required. QoS-Information: Defines Quality of Service parameters for the service. Announcement-Information: Provides data for announcements during service delivery. 3GPP-RAT-Type: Specifies the radio access technology type in use. Related-Trigger: Provides conditions for related service events to trigger additional reporting.
3GPP-OC-Rating-Group	1321	Unsigned32	3GPP
Holds the charging key, as defined in [TS23.203], that is used to apply overload control restrictions to specific rating groups. This AVP identifies which groups are impacted by the overload control measures, enabling targeted restriction to manage network load during congestion or heavy usage periods.
3GPP-OC-Request-Type	1322	Enumerated	3GPP
Specifies the type of credit control request to which overload control is applied. Defined by [RFC4006], it enables selective restriction of specific request types in response to network overload. Values: 1: INITIAL_REQUEST - Applies overload control to initial requests. 2: UPDATE_REQUEST - Restricts update requests during congestion. 3: TERMINATION_REQUEST - Limits termination requests under overload. 4: EVENT_REQUEST - Applies restrictions to one-time event requests.
3GPP-OC-Specific-Reduction	1320	Grouped	3GPP
Provides specific reduction directives for overload control, targeting particular rating groups, request types, or both, with a defined reduction percentage. This grouped AVP structure allows for fine-tuned control of overload measures across selected service requests. The AVP structure is defined as follows: 3GPP-OC-Rating-Group: Specifies rating groups impacted by overload. 3GPP-OC-Request-Type: Indicates which request types are restricted. OC-Reduction-Percentage: Defines the percentage reduction applied, facilitating controlled load management.
3GPP-PS-Data-Off-Status	4406	Enumerated	3GPP
Represents the data-off status of the User Equipment (UE) in 3GPP packet-switched (PS) data services. This AVP indicates whether the data-off status is active or inactive, controlling the UE’s access to PS services for managing data consumption. Values: 0: Active – Data-off is enabled, restricting PS data usage. 1: Inactive – Data-off is disabled, allowing PS data usage.
Time-First-Reception	3466	Time	3GPP
Holds the UTC timestamp of the first IP packet received in a session. This AVP provides critical information for session management and billing by recording when data reception began. Used in monitoring and diagnostics, it enables tracking of the session's initial inbound data activity.
Time-First-Transmission	3467	Time	3GPP
Contains the UTC timestamp of the first IP packet transmitted in a session. This AVP is useful for network analysis and billing, as it logs when outbound data transmission started, complementing the Time-First-Reception AVP for a comprehensive record of session activity.
Time-First-Usage	2043	Time	3GPP
Records the UTC timestamp of the first IP packet associated with the current service data container. It marks the beginning of data transmission within a specific service or session, providing a reference point for session timing and billing. This AVP is essential for tracking initial service usage and monitoring session activity.
Time-Indicator	3911	Unsigned32	3GPP
Specifies when an announcement should be connected in relation to the granted quota for a session. The value represents the time, in seconds, before the quota is fully exhausted. A value of zero triggers the announcement exactly when the quota ends, while a higher value provides an early notification. If this AVP is absent, the announcement plays before the IMS session resumes, ensuring users are notified of nearing quota limits for uninterrupted service management.
Time-Last-Usage	2044	Time	3GPP
Stores the UTC timestamp of the last IP packet sent within the current service data container. This AVP is used to mark the end of data transmission in a service or session, facilitating accurate usage tracking and supporting billing. It complements the Time-First-Usage AVP by providing a complete timeline of the session’s data activity.
Time-Quota-Mechanism	1270	Grouped	3GPP
Specifies the quota mechanism for managing time-based services. This AVP is included in the Multiple-Services-Credit-Control AVP when granting a time quota. The AVP structure is defined as follows: Time-Quota-Type: Determines the method of time quota application, whether as discrete periods (e.g., fixed intervals) or continuous time. Base-Time-Interval: Sets the fundamental time interval for quota application, allowing the Online Charging System (OCS) to control how time is allocated and consumed within a session.
Time-Quota-Threshold	868	Unsigned32	3GPP
Represents a threshold in seconds. When a client's remaining time quota falls below this threshold, it triggers a re-authorization request to the server. While the re-authorization is pending, the client allows service continuation until the original quota depletes. This mechanism ensures seamless service delivery during quota renewal processes and avoids abrupt session terminations.
Time-Quota-Type	1271	Enumerated	3GPP
Defines the method of time quota consumption for a specific Rating Group. Values: 0 (DISCRETE_TIME_PERIOD): Applies quota in fixed, discrete intervals, suitable for session-based services. 1 (CONTINUOUS_TIME_PERIOD): Applies quota continuously, ideal for ongoing or streaming services that consume time without interruption.
Time-Stamps	833	Grouped	3GPP
Records timestamps for SIP requests and responses, providing precise tracking of SIP transaction times. This AVP is useful in scenarios requiring detailed timing information, such as billing or performance monitoring. The AVP structure is defined as follows: SIP-Request-Timestamp: The exact UTC timestamp of when the SIP request was initiated. SIP-Response-Timestamp: The UTC timestamp of when the SIP response was received. SIP-Request-Timestamp-Fraction: Additional millisecond-level precision for the request timestamp. SIP-Response-Timestamp-Fraction: Additional millisecond-level precision for the response timestamp.
Time-Usage	2045	Unsigned32	3GPP
Records the actual time used within a service data container's reporting interval. Measured in seconds, this AVP is essential for accurate billing or quota tracking, allowing service providers to account for usage in a given interval accurately.
TLTRI	1318	Unsigned32	3GPP
The TLTRI (T8 Long Term Transaction Reference ID) provides an identifier for long-term transactions facilitated over the T8 interface between the SCEF (Service Capability Exposure Function) and the SCS/AS (Service Capability Server/Application Server). It is applicable in cases such as NIDD (Non-IP Data Delivery) configuration, group message requests, or monitoring event configuration, where long-duration transactions are required. This AVP helps in uniquely tracking these extended transactions, supporting ongoing session management and accountability.
Token-Text	1215	UTF8String	3GPP
Provides additional information that extends the Message-Class AVP. It is used to store supplementary data in a UTF-8 encoded string, allowing for flexible and descriptive text extensions that may enhance message handling or classification. This AVP may include information pertinent to classification, routing, or additional message context, facilitating finer-grained control and improved information delivery in relevant applications.
Traffic-Data-Volumes	2046	Grouped	3GPP
Designed to encapsulate details about IP-CAN bearer activity, particularly when a change in charging conditions occurs for the bearer. It facilitates reporting on data volumes for both uplink and downlink directions and includes additional IP-CAN-specific information, such as location, charging identifiers, and quality of service (QoS) metrics. The AVP structure is defined as follows: QoS-Information: Represents the quality of service attributes for the IP-CAN bearer. Accounting-Input-Octets: Records the volume of data transmitted in the downlink direction. Accounting-Output-Octets: Records the volume of data transmitted in the uplink direction. Change-condition: Indicates the specific condition that triggered the change in charging. Change-Time: The time at which the change condition occurred. 3GPP-User-Location-Info: Contains user location details within a 3GPP network context. UWAN-User-Location-Info: Captures location information within a UWAN (unlicensed wireless access network). 3GPP-Charging-Id: Identifies the IP-CAN bearer for charging purposes in 3GPP-based sessions. Presence-Reporting-Area-Status: Indicates the presence status within a defined reporting area. Presence-Reporting-Area-Information: A list containing information about defined presence-reporting areas. User-CSG-Information: Contains information about the user’s closed subscriber group (CSG). 3GPP-RAT-Type: Represents the type of radio access technology in use. Access-Availability-Change-Reason: Specifies the reason for a change in access availability. Related-Change-Condition-Information: Additional context related to the change condition. Diagnostics: Contains diagnostic information to help identify issues. Enhanced-Diagnostics: Provides more detailed diagnostic data for troubleshooting. CP-CIoT-EPS-Optimisation-Indicator: Indicates if CP-CIoT EPS optimizations are in use. Serving-PLMN-Rate-Control: Controls rate limits for the serving PLMN. APN-Rate-Control: Specifies rate control settings for the APN in use.
Transcoder-Inserted-Indication	2605	Enumerated	3GPP
Specifies whether a transcoder has been added to the media session for SDP (Session Description Protocol) media components. The AVP provides insight into the media path modifications applied to accommodate compatibility between differing codecs or to manage bandwidth. Values: 0: Transcoder Not Inserted 1: Transcoder Inserted
Transit-IOI-List	2701	UTF8String	3GPP
Holds a list of Inter-Operator Identifiers (IOIs) for the transit networks encountered during a SIP transaction. These identifiers, generated by IMS (IP Multimedia Subsystem) network elements, are arranged chronologically, where the first entry corresponds to the SIP request. In cases where only the SIP response is known, the SIP request entry is listed as "unknown." This AVP enables accurate tracking of the transit network path in inter-operator scenarios.
Transmitter-Info	3468	Grouped	3GPP
Provides details about a detected transmitter in direct communication scenarios. The AVP structure is defined as follows: ProSe-Source-IP-Address: The IP address of the detected ProSe (Proximity-based Services) transmitter. ProSe-UE-ID: The unique identifier for the transmitting UE (User Equipment) in ProSe communications.
Trigger	1264	Grouped	3GPP
Provides a mechanism for identifying events that prompt specific actions within the Diameter protocol, particularly within Credit Control and Accounting (CCA) and Credit Control Requests (CCR). It serves two main functions: In a CCA (Credit-Control-Answer) message, the presence of the Trigger AVP without any Trigger-Type AVPs allows the Online Charging System (OCS) to disable all event triggers. In a CCR (Credit-Control-Request) message, the Trigger AVP is included to specify the types of events that have triggered the request. Each trigger event is identified by Trigger-Type AVPs, which list the conditions or events responsible for generating the request.
Trigger-Type	870	Enumerated	3GPP
Defines specific events that can prompt a re-authorization request for a quota. This AVP allows a Credit-Control client to only request quota re-authorization for defined trigger events, ensuring efficient quota management by reacting to significant network changes or conditions. Depending on the event type, it can be included in both Credit-Control Answer (CCA) and Credit-Control Request (CCR) messages to manage service quality and usage based on evolving session conditions. Values: CHANGE_IN_SGSN_IP_ADDRESS (1): Indicates that a change in the Serving GPRS Support Node (SGSN) IP address prompts the Credit-Control client to request a re-authorization, reflecting network handoffs or relocations. CHANGE_IN_QOS (2): Triggers re-authorization when the user’s negotiated Quality of Service (QoS) changes, such as altering data transfer rates or service reliability. This ensures billing accuracy aligned with service quality changes. CHANGE_IN_LOCATION (3): Initiates re-authorization if the user’s geographical location changes, addressing location-based pricing or service limitations. CHANGE_IN_RAT (4): Used when the Radio Access Technology (RAT) type changes, such as a switch from LTE to 5G. This ensures the quota matches the new network’s capabilities. CHANGE_IN_UE_TIMEZONE (5): Re-authorization is requested if the user’s device changes time zones, which could impact time-sensitive services or billing practices. CHANGEINQOS_TRAFFIC_CLASS (10) to CHANGEINQOS_GUARANTEED_BIT_RATE_FOR_DOWNLINK (23): These reflect various specific QoS attributes, such as traffic class, delay, throughput, and error rates. Each enumerated value signals changes to specific parameters, prompting re-authorization to maintain alignment between allocated quotas and altered service demands. CHANGEINQOS_APN_AGGREGATE_MAXIMUM_BIT_RATE (24): Re-authorization is triggered when there’s a modification in the maximum bit rate for the APN, important for adjusting quotas based on allowed data transfer rates. CHANGEINLOCATION_MCC (30) to CHANGEINLOCATION_ECGI (36): Location-related triggers based on Mobile Country Code (MCC), Mobile Network Code (MNC), and other location identifiers like Tracking Area Code (TAC) or Cell ID. This captures any notable geographical shifts impacting service terms or restrictions. CHANGE_IN_MEDIA_COMPOSITION (40): Occurs if the media composition (such as audio or video parameters) in a SIP session changes, ensuring service adjustments for modified multimedia sessions. CHANGE_IN_PARTICIPANTS_NMB (50) and CHANGE_IN_THRSHLD_OF_PARTICIPANTS_NMB (51): Relevant for multi-participant sessions where changes in participant numbers affect resource allocation, necessitating quota updates. CHANGE_IN_USER_PARTICIPATING_TYPE (52): Signals re-authorization when the user’s participation role within a session changes, addressing adjustments for different user interaction types in conferencing. CHANGE_IN_SERVICE_CONDITION (60): General trigger for any changes in the rating conditions tied to a service, often service-specific, and configurable by the operator. CHANGE_IN_SERVING_NODE (61): Requests re-authorization if the user’s serving node changes, reflecting updates due to network re-routing. CHANGE_IN_ACCESS_FOR_A_SERVICE_DATA_FLOW (62): Occurs when the access path for a service data flow changes, essential in multi-access scenarios where charging depends on access type. CHANGE_IN_USER_CSG_INFORMATION (70) to CHANGE_IN_HYBRID_UNSUBSCRIBED_USER_CSG_INFORMATION (72): Triggers based on the user’s access to a Closed Subscriber Group (CSG) cell, reflecting entry or exit from subscribed or hybrid cells. CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA (73): Re-authorization based on the user’s movement in or out of presence-reporting areas, such as designated coverage zones or buildings. CHANGE_IN_SERVING_PLMN_RATE_CONTROL (74) and CHANGE_IN_APN_RATE_CONTROL (75): Activated by changes in rate control for Public Land Mobile Network (PLMN) or APN, ensuring that quotas are adjusted according to new rate-limiting measures. CHANGE_IN_3GPP_PS_DATA_OFF (76): Reflects a change in the packet-switched (PS) data off status, such as disabling mobile data, prompting quota adjustments for accurate tracking.
Trunk-Group-ID	851	Grouped	3GPP
Used to identify the Public Switched Telephone Network (PSTN) trunk group for both incoming and outgoing calls. The AVP structure is defined as follows: Incoming-Trunk-Group-ID: A sub-AVP that holds the identifier for the incoming PSTN trunk group. This identifier specifies the trunk group from which the call originated in the PSTN network. Outgoing-Trunk-Group-ID: A sub-AVP that holds the identifier for the outgoing PSTN trunk group. This identifies the trunk group to which the call is directed in the PSTN network. The inclusion of these identifiers helps in call routing and management across PSTN networks, ensuring that calls are tracked from entry to exit points, thus enabling effective billing, monitoring, and quality assurance.
TWAG-Address	3903	Address	3GPP
Holds the IP address of the Trusted WLAN Access Gateway (TWAG) node. The TWAG serves as an interface between WLAN networks and mobile core networks, allowing devices connected over Wi-Fi to access mobile services with authentication and authorization from the mobile network.
TWAN-User-Location-Info	2714	Grouped	3GPP
Provides information about the User Equipment (UE) location within a Trusted WLAN Access Network (TWAN). This AVP is essential for tracking the precise location of a UE connected over a trusted WLAN, providing multiple identifiers and location details to facilitate network management and service delivery. The AVP structure is defined as follows: SSID (Service Set Identifier): The mandatory SSID of the connected WLAN network, identifying the specific wireless network in which the UE is connected. BSSID (Basic Service Set Identifier): The optional BSSID, which is a unique MAC address for the access point that the UE is connected to, offering more granular identification of the access point. Civic-Address-Information: An optional AVP that contains detailed civic location information, such as street address, city, and country, encoded as a ByteBuf, to provide precise geographical location details for the UE. WLAN-Operator-Id: This optional identifier specifies the WLAN operator’s identity, enabling service providers to distinguish between different WLAN networks when providing services to users in diverse operator environments. Logical-Access-ID: An optional identifier that provides a logical access identifier for the TWAN, encoded as a ByteBuf, further defining the specific access point within the network.
Type-Number	1204	Enumerated	3GPP
Identifies the well-known media types associated with a specific Diameter message. The values for this AVP are sourced from the Open Mobile Naming Authority (OMNA) WSP Content Type Numbers, which provide standardized identifiers for various media types. These enumerated values allow applications to interpret the type of media involved in the communication, which can include types like text, image, audio, and video.
UNI-PDU-CP-Only-Flag	3932	Enumerated	3GPP
Specifies the type of PDU (Packet Data Unit) connection for a given PDN (Packet Data Network) session when Control Plane (CP) CIoT EPS (Cellular Internet of Things Evolved Packet System) Optimization is enabled. It determines if only the control plane is used for data transfer or if both user and control planes are available. Values: Value 0 (UNI-PDU-both-UP-CP): This setting indicates that both user plane (UP) and control plane (CP) can be used for the PDU transfer, allowing either S1-U or S11-U interfaces from the S-GW (Serving Gateway). Value 1 (UNI-PDU-CP-Only): This value specifies that only the control plane (CP) is utilized for data transfer, meaning only the S11-U interface is used from the S-GW. The absence of this AVP implies that both user and control planes are available for PDU transfer. This setting is particularly relevant in IoT deployments where optimizing for control plane-only connections reduces complexity and overhead.
Unit-Cost	2061	Grouped	3GPP
Specifies the cost associated with a single unit of service, typically expressed in terms of a monetary value. It has a similar structure to the Unit-Value AVP, containing both Value-Digits and an optional Exponent to represent large or small values precisely. The AVP structure is defined as follows: Value-Digits: A mandatory parameter representing the significant digits of the cost. For instance, if the cost is $0.10, Value-Digits would be set to 10. Exponent: An optional parameter that works with Value-Digits to adjust the cost by orders of magnitude. It indicates the position of the decimal point. For example, if Value-Digits is 10 and Exponent is -2, the final value represents $0.10.
Unit-Quota-Threshold	1226	Unsigned32	3GPP
Specifies a threshold value in service-specific units, often used for re-authorization when granted service units are near depletion. It is commonly included within the Multiple-Services-Credit-Control AVP and the Rate-Element AVP. In Multiple-Services-Credit-Control AVP context: If this AVP appears alongside a Granted-Service-Units AVP containing a CC-Service-Specific-Units AVP, it indicates a service-specific quota. When the available units fall below this threshold, the Credit-Control client initiates a re-authorization request to refresh the quota. Service continues during the re-authorization up to the original quota amount. In Rate-Element AVP context: The Unit-Quota-Threshold denotes the usage level at which a new rating element within a tariff takes effect, switching the applicable rate once the threshold for a particular service is met.
Unused-Quota-Timer	4407	Unsigned32	3GPP
Represents the duration, in seconds, without any quota being granted or consumed within a session. It applies specifically to rating groups in the context of the Gy session, typically associated with online charging. This timer helps manage session resources by indicating inactivity within the allocated quota. If the timer surpasses a certain threshold, the system may trigger resource re-evaluation or session termination for efficiency and billing accuracy, ensuring that unused resources do not remain allocated indefinitely.
Usage-Information-Report-Sequence-Number	3439	Integer32	3GPP
Provides a sequential identifier for usage information reports. It is instrumental in tracking and organizing the sequence of reports generated within a container. By assigning each report a unique sequence number, this AVP ensures that usage information is accurately processed in the intended order, preventing data overlap or sequence confusion. This AVP is typically used in scenarios where multiple usage reports are generated and need to be consistently ordered for reliable processing.
User-CSG-Information	2319	Grouped	3GPP
Contains essential information about a user's Closed Subscriber Group (CSG) settings, primarily applicable within CSG cell access environments. It is particularly relevant in GPRS and EPC contexts as defined in [TS29.060] and [TS29.274]. The AVP structure is defined as follows: CSG-Id (mandatory): Represents the unique identifier for the CSG within the Public Land Mobile Network (PLMN). It identifies the specific CSG cell the user is associated with. CSG-Access-Mode (mandatory): Defines the mode of access for the CSG, indicating whether the access is open, closed, or hybrid. This determines whether users outside the CSG can access the network services provided within the CSG. CSG-Membership-Indication (optional): Specifies if the user is a member of the CSG, especially useful for hybrid access scenarios. When set, it provides an indication of the user's membership status, enabling different treatment based on whether the user is a CSG member.
User-Participating-Type	1279	Enumerated	3GPP
Indicates the type of user participation within a Push-to-Talk over Cellular (PoC) session. It is a component of the Participants-Group AVP, which tracks the involvement type of different users in the session. Values: 0 (Normal): Indicates a standard user participating in the PoC session. 1 (NW PoC Box): Refers to the Network PoC Box, typically representing a network-side control box within the PoC session. 2 (UE PoC Box): Denotes a User Equipment (UE) PoC Box, which can manage the user’s interaction within the session.
User-Session-Id	830	UTF8String	3GPP
Contains a unique session identifier for the user, which is especially relevant in SIP-based sessions. In the context of a SIP session, this AVP holds the SIP Call ID, as specified in [RFC3261]. For scenarios where the Application Server (AS) functions as a Back-to-Back User Agent (B2BUA), this AVP covers the incoming Session-ID leg, ensuring session continuity and tracking across network components.
UWAN-User-Location-Info	3918	Grouped	3GPP
Provides detailed information about the User Equipment (UE) location within an Untrusted Wireless Access Network (UWAN). This AVP is essential for enabling accurate tracking and management of UE sessions within non-secure wireless environments, especially where Network Address Translation (NAT) is present. The AVP structure is defined as follows: UE-Local-IP-Address (Required): Specifies the IP address of the UE within the UWAN. This is mandatory for identifying the device in the network. UDP-Source-Port (Optional): Indicates the UDP source port if NAT is detected, facilitating proper routing of UDP-based traffic within the network. SSID (Optional): Specifies the Service Set Identifier (SSID) of the WLAN to which the UE is connected. This is helpful for location-based services and network management. BSSID (Optional): Denotes the Basic Service Set Identifier (BSSID), identifying the specific access point within the network. TCP-Source-Port (Optional): Provides the TCP source port number if NAT is detected, enabling the network to route TCP-based connections accurately. Civic-Address-Information (Optional): Contains location information formatted as per civic address standards, aiding in geographic positioning and location-based services. WLAN-Operator-Id (Optional): Identifies the WLAN operator managing the untrusted network, enabling service differentiation and operator-specific handling. Logical-Access-ID (Optional): Represents the logical identifier for the access point in the UWAN, facilitating device management within large networks.
Variable-Part	3907	Grouped	3GPP
Used to specify a customizable component within an announcement. This AVP enables announcements to dynamically incorporate variable elements based on specific parameters, such as order, type, and value, allowing a tailored playback experience. The AVP structure is defined as follows: Variable-Part-Order (Optional): Defines the playback order of this variable within the announcement sequence. This ensures that each part plays back in the intended sequence. Variable-Part-Type (Mandatory): Specifies the data type of the variable part. This type determines how the value should be interpreted and displayed. Recognized types include: 0: Integer 1: Number 2: Time 3: Date 4: Currency 5-127: Reserved for future standardization 128-255: Reserved for operator-defined types Variable-Part-Value (Mandatory): Holds the actual value of the variable, allowing it to be rendered during playback based on the specified type.
Variable-Part-Order	3908	Unsigned32	3GPP
Determines the order in which a variable part will be played within an announcement sequence. This AVP is crucial for maintaining the intended flow of dynamic parts in multi-part announcements, ensuring each variable plays at its designated time.
Variable-Part-Type	3909	Unsigned32	3GPP
Identifies the data type for a variable component in an announcement, dictating how its value should be interpreted. Types include: 0: Integer 1: Number 2: Time 3: Date 4: Currency 5-127: Reserved for future standardization 128-255: Reserved for operator-defined types
Variable-Part-Value	3910	UTF8String	3GPP
Contains the value of the variable component to be announced, based on the type defined by the associated Variable-Part-Type AVP. The format of the content within Variable-Part-Value varies depending on the type, as detailed below: Integer: A string of digits (up to 10), which should be announced as a single number. Number: A string of digits (up to 24), which should be announced as individual digits. Time: A string formatted as HHMM, representing the hour and minute, which will be used to convey time information. Date: A string formatted as YYYYMMDD, representing the year, month, and day, for date-related announcements. Currency: A string formatted as AAAAAABB, where AAAAAA represents the integral part and BB represents the decimal part of the currency value.
VCS-Information	3410	Grouped	3GPP
Provides additional service-specific information for Voice Call Services (VCS) within the telecommunications network. It is of type Grouped, meaning it contains a series of AVPs that together provide a detailed dataset. The AVP structure is defined as follows: Bearer-Capability: Contains the bearer capability information for the call, indicating the type and quality of service requested. Network-Call-Reference-Number: Provides a unique reference number for the call within the network, enabling tracking and correlation of call-related records. MSC-Address: Specifies the address of the Mobile Switching Center (MSC) managing the call, often formatted as a network element identifier. Basic-Service-Code: Identifies the type of basic service (such as voice or data) associated with the call. ISUP-Location-Number: Contains the location number in ISUP format, used for routing and location identification within the network. VLR-Number: Refers to the Visitor Location Register (VLR) number, providing information on the location register responsible for the user during the call. Forwarding-Pending: Indicates whether call forwarding is pending, with enumerated values showing the status (e.g., pending, not pending). ISUP-Cause: Specifies the ISUP cause code, representing the reason for call release or redirection within ISUP signaling. Start-Time: Marks the beginning of the call or session in UTC format, helping in billing and call tracking. Start-of-Charging: Indicates the time when charging begins for the call, potentially aligning with call initiation or answer time. Stop-Time: Records the end time of the call or session in UTC, critical for accurate billing and service duration tracking. PS-Free-Format-Data: Contains additional free-format data specific to Packet Switched (PS) services, enabling transmission of service-specific data as needed.
VLR-Number	3420	OctetString	3GPP
Holds the E.164 address of the Visitor Location Register (VLR) currently serving the user. Encoded in Telephony Binary Coded Decimal (TBCD) format, this address is used to uniquely identify the VLR within the mobile network. It does not include any prefixes indicating the nature of address or numbering plan, containing only the TBCD-encoded digits. This AVP provides essential information for call routing, mobility management, and user location services within the mobile network.
VoLTE-Information	1323	Grouped	3GPP
Aggregates information about the caller and callee within a Voice over LTE (VoLTE) session. The AVP structure is defined as follows: Calling-Party-Address: Specifies the address of the calling party. This is typically the E.164 formatted number of the VoLTE caller. Callee-Information: Provides additional details about the callee, encapsulated in the CalleeInformation AVP. This AVP may include various identifiers and routing details specific to the VoLTE session.
Volume-Quota-Threshold	869	Unsigned32	3GPP
Specifies a volume threshold value in octets, triggering re-authorization for volume-based quotas. When included in the Multiple-Services-Credit-Control AVP (MSCC AVP), this AVP typically accompanies the Granted-Service-Units AVP, which may contain volume-related AVPs, such as CC-Total-Octets, CC-Input-Octets, or CC-Output-Octets. When the credit-control client detects that the remaining quota falls below the threshold specified by the Volume-Quota-Threshold AVP, it initiates a re-authorization request to the credit-control server. During this re-authorization process, service is allowed to continue until the initial granted volume quota is fully used, ensuring a seamless experience for the end-user.
WLAN-Operator-Id	1306	Grouped	3GPP
Identifies the trusted or untrusted WLAN operator. It includes information about the Public Land Mobile Network (PLMN) ID and the name of the WLAN operator. The AVP structure is defined as follows: WLAN-PLMN-Id: Identifies the PLMN associated with the WLAN. WLAN-Operator-Name: Specifies the name of the WLAN operator.
WLAN-Operator-Name	1307	UTF8String	3GPP
Specifies the name of the WLAN operator, either trusted or untrusted, and is represented as a UTF-8 encoded string. This name is used to help identify and authenticate the WLAN operator in network access and roaming scenarios, allowing network elements to distinguish between operators when applying access control and service-specific policies. The operator name format is specified in subclause 19.8 of 3GPP [TS23.003].
WLAN-PLMN-Id	1308	UTF8String	3GPP
Holds the Public Land Mobile Network (PLMN) Identity associated with a WLAN operator, whether trusted or untrusted. Represented as a UTF-8 encoded string, this AVP uniquely identifies the operator’s network, supporting secure access and authentication for WLAN-connected devices. By providing the PLMN Identity, this AVP helps differentiate between various WLAN operators and enables network elements to apply appropriate policies and access controls based on operator identity.

Accounting AVPs

Accounting AVPs

Start innovating with Mobius

What's next? Let's talk!

As a company you'll get:

Accounting AVPs

Accounting AVPs

Start innovating with Mobius

What's next? Let's talk!

Log in

Forgot password

As a company you'll get: