Nta AVPs
Nta (application id: 16777358)
The Nta interface facilitates communication between the Policy and Charging Rules Function (PCRF) and the Service Capability Exposure Function (SCEF). The Nta interface is specifically designed for configuring event monitoring for a group of User Equipment (UEs) and reporting those events.
Nta interface workflow
Event Configuration Request:
- The process begins when the SCEF receives a request from an SCS/AS to monitor specific events, such as location changes, for a group of UEs.
- The SCEF sends an Event-Configuration-Request (ECR) command to the PCRF. This request includes various Attribute-Value Pairs (AVPs), such as Monitoring-Type, External-Group-Identifier, and others that specify the details of the monitoring configuration.
Event Configuration Answer:
- Upon receiving the ECR, the PCRF retrieves the necessary UE identities and checks for any active IP-CAN sessions related to those UEs.
- The PCRF responds with an Event-Configuration-Answer (ECA) command, which indicates whether the event monitoring configuration was successfully applied. If successful, the PCRF proceeds to monitor the specified events based on the configuration.
Event Reporting:
- When an event that matches the configured monitoring parameters occurs, the PCRF generates a report and sends it to the SCEF using the Nta interface.
- The SCEF then forwards this event report to the requesting SCS/AS, completing the monitoring and reporting cycle.
For complete technical specification of Nta interface in Diameter protocol please refer to: [3GPP TS 29.154]
package com.mobius.software.telco.protocols.diameter.primitives.nta
|
Name |
AVP Code |
Data Type |
Vendor |
|
Event-Configuration |
4211 |
Grouped |
3GPP |
|
Defines the monitoring event configuration provided by the Service Capability Exposure Function (SCEF). It specifies the monitoring type, associated location information configuration, and references required for event reporting. The AVP structure is defined as follows: Extended-SCEF-Reference-ID (Unsigned32): Unique identifier assigned by the SCEF for reference purposes. SCEF-ID (UTF8String): Identifies the SCEF node handling the event configuration. Monitoring-Type (Enumerated): Specifies the type of monitoring (e.g., Location Reporting, Reachability). Location-Information-Configuration (Grouped): Contains details for location monitoring configuration, if required. |
|||
|
Event-Configuration-State |
4212 |
Unsigned32 (Bitmask) |
3GPP |
|
The Event-Configuration-State AVP is an Unsigned32 AVP used to represent a bitmask that provides the state of event configuration. It indicates whether the report for the UE group is final or whether additional reports are pending. Bitmask Definition: 0 Final Report Set: Indicates this is the final report for the UE group. Not Set: Indicates more reports are pending. |
|||
|
Event-Configuration-Status |
4213 |
Grouped |
3GPP |
|
Used to convey the status of a monitoring event configuration. It provides information about the state of the configuration and the extended SCEF reference ID, ensuring proper tracking and identification of monitoring events. The AVP structure is defined as follows: Event-Configuration-State (Unsigned32): Indicates the state of the configuration using a bitmask. Extended-SCEF-Reference-ID (Unsigned32): A globally unique identifier used to correlate monitoring events. Allows for future extensions with additional attributes. |
|||
|
Event-Reporting-Results |
4214 |
Unsigned32 |
3GPP |
|
Conveys status information about event reporting results for a UE group. It specifically indicates whether the report is final or if additional reports are pending. Bitmask Definitions: 0 Final Report Set: Indicates this is the final report for the UE group. Not Set: Reports pending. |
|||
|
Event-Reports |
4215 |
Grouped |
3GPP |
|
Used to aggregate event reports for a UE group in Diameter protocol-based communications. It provides detailed reporting results, reference IDs, and optional access network reports related to the monitoring sessions managed by the SCEF (Service Capability Exposure Function). The AVP structure is defined as follows: Event-Reporting-Results (4214, Unsigned32, Mandatory): Tracks status of event reporting (e.g., final or pending reports). Extended-SCEF-Reference-ID (4210, Unsigned32, Mandatory): Uniquely identifies the SCEF session associated with the reports. Access-Network-Reports (4216, Grouped, Optional): Provides access network-specific details and events for additional monitoring insights. |
|||
|
Extended-SCEF-Reference-ID |
4216 |
Unsigned64 |
3GPP |
|
Used to contain a unique identifier assigned by the SCEF (Service Capability Exposure Function). This identifier is used to correlate and track sessions or events related to monitoring configurations and reporting results between the SCEF and other Diameter-based nodes. |
|||
Start innovating with Mobius
What's next? Let's talk!