E4 AVPs
E4 (application id: 16777231)
The E4 interface is a component within the Resource and Admission Control Subsystem (RACS) architecture, used to facilitate the exchange of IP-connectivity session data between the Network Attachment Subsystem (NASS) and RACS. This exchange ensures efficient resource allocation and admission control for IP-based services.
E4 interafce workflow:
Session Initiation:
- The UE initiates a session and connects to the network through the Access Node.
- The Access Node communicates with the NASS over the Ra interface to authenticate the user and allocate an IP address.
Session Data Exchange:
- After authentication and IP address allocation, the NASS sends session data to the A-RACF via the e4 interface.
- This data includes details such as the user’s IP address, identity, and QoS requirements.
Resource and Admission Control:
- The A-RACF processes the session data received via the e4 interface to make resource and admission control decisions based on available network resources and the QoS requirements of the session.
- The A-RACF then communicates with the RCEF at the IP Edge over the Re interface to enforce these decisions.
Policy Enforcement:
- The RCEF enforces resource control policies as directed by the A-RACF.
- For additional policy decisions, the A-RACF interacts with the SPDF, which communicates with the Application Function (AF) over the Gq interface.
Session Management:
- Throughout the session, the e4 interface ensures ongoing communication between the NASS and A-RACF, managing any changes in session parameters.
For complete technical specification of E4 interface in Diameter protocol please refer to: [ETSI ES 283 034]
package com.mobius.software.telco.protocols.diameter.primitives.e4
Name |
AVP Code |
Data Type |
Vendor |
Access-Network-Type |
306 |
Grouped |
ETSI |
Provides information about the type of network port and the aggregation network used to connect user equipment (UE) to the network. It ensures that Diameter nodes are aware of the characteristics of the access environment, enabling efficient session handling, authorization, and network policy enforcement. The AVP structure is defined as follows: NAS-Port-Type: Identifies the specific port type used by the user equipment (UE) to connect to the access network. It reflects the physical or logical nature of the connection, such as wired Ethernet, wireless LAN, or xDSL. Aggregation-Network-Type: Specifies the type of aggregation network supporting the access port. |
|||
Address-Realm |
301 |
OctetString |
ETSI |
Represents an address realm in the form of a Fully Qualified Domain Name (FQDN). It is used to specify the network domain or administrative boundary within which Diameter nodes operate. |
|||
Aggregation-Network-Type |
307 |
Enumerated |
ETSI |
Defines the type of aggregation network used in the user's connection. It specifies the technology employed to aggregate traffic at the network edge or intermediate layers, aiding in identifying the network's capabilities and context. Values: UNKNOWN (0): The type of aggregation network is not specified or recognized. ATM (1): Asynchronous Transfer Mode (ATM) is used as the aggregation network technology. ETHERNET (2): Ethernet is employed for traffic aggregation. |
|||
Application-Class-ID |
312 |
UTF8String |
ETSI |
Identifies a class of applications that share the same Quality of Service (QoS) profile within the network. |
|||
Globally-Unique-Address |
300 |
Grouped |
ETSI |
Provides the capability to identify a network entity or device using a globally unique address. This AVP is crucial for routing, authentication, and addressing in various network scenarios, ensuring unambiguous identification of endpoints. It allows the specification of IP addresses (IPv4 or IPv6) and an associated address realm. The AVP structure is defined as follows: Frame-IP-Address: An IPv4 address identifying the entity. Frame-IPv6-Prefix: An IPv6 address or prefix. Address-Realm: The realm (e.g., FQDN) associated with the IP address. |
|||
Initial-Gate-Setting-Description |
303 |
Grouped |
ETSI |
Provides essential gate settings for traffic flow management in the network. It defines initial parameters such as filtering rules and bandwidth limitations for specific traffic directions, offering precise control over user traffic in the aggregation network. The AVP structure is defined as follows: NAS-Filter-Rule: Specifies one or more rules to filter traffic at the NAS level. Maximum-Allowed-Bandwidth-UL: Maximum uplink bandwidth in bits per second. Absence indicates no uplink limitation. Maximum-Allowed-Bandwidth-DL: Maximum downlink bandwidth in bits per second. Absence indicates no downlink limitation. |
|||
Initial-Gate-Setting-ID |
314 |
Unsigned32 |
ETSI |
Used to refer to a pre-configured set of initial gate settings for managing traffic flow and network behavior. Instead of defining detailed gate settings directly in the command, this AVP provides a pointer to a pre-defined configuration, simplifying the command structure and improving efficiency. This AVP must not be used simultaneously with the Initial-Gate-Setting-Description AVP in the same Diameter command, ensuring clarity and avoiding redundancy in gate-setting definitions. |
|||
IP-Connectivity-Status |
305 |
Enumerated |
ETSI |
Provides a status indicator of the current IP connectivity state for a user or network entity. This AVP is critical in scenarios where the IP connection's availability or loss must be conveyed to ensure proper handling of services and policies within the network. Values: 0: IP-CONNECTIVITY-ON: Indicates that IP connectivity is established and operational. 1: IP-CONNECTIVITY-LOST: Indicates that IP connectivity has been lost, which could require network-level corrective actions or alternative routing. |
|||
Maximum-Allowed-Bandwidth-DL |
309 |
Unsigned32 |
ETSI |
Specifies the maximum allowable bandwidth for downlink traffic associated with a particular traffic class. This AVP is integral in enforcing QoS policies, ensuring that network resources are appropriately allocated and that traffic flows adhere to predefined bandwidth constraints. The value is expressed in kilobits per second (kbits/s). |
|||
Maximum-Allowed-Bandwidth-UL |
308 |
Unsigned32 |
ETSI |
Specifies the maximum allowable bandwidth for uplink traffic associated with a specific traffic class. This AVP plays a crucial role in traffic management and QoS enforcement by setting an upper limit on the amount of bandwidth that can be utilized for transmitting data from the user device toward the network. The value is expressed in kilobits per second (kbits/s). |
|||
QoS-Profile-Description |
304 |
Grouped |
ETSI |
Defines a set of parameters that collectively describe a Quality of Service (QoS) profile. This AVP is used to specify the QoS requirements for a given traffic flow or set of flows in network environments such as mobile and fixed broadband networks. This AVP facilitates effective QoS management by enabling operators to define application-specific, media-specific, or traffic-specific QoS profiles. The flexibility in specifying parameters allows tailoring QoS settings to meet diverse use-case requirements. The AVP structure is defined as follows: Application-Class-ID: Specifies the class of applications that share the QoS profile. Absence indicates that the profile applies to any requestor. Media-Type: Indicates the type of media associated with the QoS profile (e.g., audio, video). Absence applies the profile to any media type. Reservation-Priority: Defines the priority for resource reservations, ensuring critical traffic is prioritized. Bandwidth Parameters:
Traffic-Profile: Identifies specific traffic profiles, adding another layer of granularity to the QoS description. |
|||
QoS-Profile-ID |
315 |
Unsigned32 |
ETSI |
Serves as a reference to a predefined set of Quality of Service (QoS) parameters. Rather than including detailed QoS definitions within the message, this AVP allows for referencing a pre-configured QoS profile stored in the network. This mechanism simplifies signaling and ensures consistent application of QoS policies across network nodes. |
|||
Transport-Class |
311 |
Unsigned32 |
ETSI |
Serves as a pointer to a specific class of transport services to be applied within the network. It uses an integer index to identify the appropriate transport behavior, such as forwarding or routing mechanisms. This abstraction enables flexible and efficient application of transport policies without the need for transmitting detailed parameters. |
Start innovating with Mobius
What's next? Let's talk!