AEF

Additional Elementary Functions

Services →
Introduced in Rel-5 Also in: Security

AEF is the set of supplementary service capabilities and functional components defined in 3GPP standards that extend beyond basic telephony to enable enhanced communication features, service personalization, and network intelligence.

Category
Services
Introduced
Rel-5
Where
Services › IMS
Also touches
1 segments
Specifications
13 specs
AEF Description Purpose Detected Changes Specifications

Description

Additional Elementary Functions (AEF) represent a comprehensive set of supplementary service capabilities and functional building blocks defined within the 3GPP architecture. These functions operate as modular components that extend the basic call processing and session management capabilities of mobile networks, enabling sophisticated service delivery mechanisms. AEF encompasses various functional entities that can be deployed, configured, and combined to create complex service logic, supporting everything from basic supplementary services like call forwarding and barring to advanced multimedia communication features.

Architecturally, AEF components are typically implemented within the Core Network domain, often integrated with service control functions or application servers. These functions interact with basic call state models and session management entities through standardized interfaces and protocols. The AEF framework defines precise behavioral models, state machines, and interaction patterns that ensure consistent service execution across different network implementations and operator deployments. This standardization is crucial for interoperability and consistent user experience in multi-vendor, multi-operator environments.

Key technical aspects of AEF include their modular design, which allows operators to selectively deploy functions based on service requirements and market demands. Each AEF component follows well-defined triggering mechanisms, typically based on specific events in call/session processing or user interactions. The functions implement standardized algorithms for service logic execution, conflict resolution when multiple services interact, and fallback procedures for error conditions. This structured approach ensures predictable behavior and facilitates testing and validation of complex service combinations.

In practical network implementations, AEF components work in conjunction with subscriber databases, policy control functions, and charging systems to deliver personalized services. They process service requests, apply business logic, modify session parameters, and generate appropriate charging records. The AEF framework also includes mechanisms for service provisioning, activation/deactivation, and status reporting, enabling flexible service management. These functions form the technical foundation for the rich ecosystem of value-added services that differentiate modern mobile networks from basic connectivity platforms.

Purpose & Motivation

The creation of Additional Elementary Functions (AEF) within 3GPP standards addressed the growing need for standardized, interoperable supplementary services in mobile networks. Prior to their formal definition, operators implemented proprietary service platforms that created interoperability challenges, limited service portability, and increased complexity for multi-vendor network deployments. The AEF framework provided a standardized approach to service implementation that enabled consistent user experience across different networks and devices.

AEF solved critical problems in service deployment and management by establishing clear functional boundaries, standardized interfaces, and predictable behavior models. This allowed operators to deploy complex service portfolios with confidence in their reliability and interoperability. The framework also facilitated the development of third-party service applications by providing well-defined hooks and integration points within the network architecture.

Historically, AEF emerged as part of 3GPP's broader effort to create a comprehensive service architecture that could support the transition from basic voice services to rich multimedia communications. By defining these elementary functions as building blocks, 3GPP enabled the gradual evolution of service capabilities while maintaining backward compatibility and network stability. This approach proved particularly valuable as networks evolved through multiple generations, allowing service innovation without requiring complete network overhauls.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (24 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-5, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the AEF (Additional Elementary Functions) saw corrections to its operations related to obtaining security information and revoking API invokers. Furthermore, its resource model was corrected and missing functions were added within the CAPIF_Security_API. These updates refined the AEF's procedures and its interface for security management.

  • Correct resource model and add missing functions in CAPIF_Security_API TS 29.222CR0072
  • Correct AEF operations related to obtaining security info or revoking API invokers TS 29.222CR0085
Rel-16 4 changes

In Release 16, the new developments for the Additional Elementary Functions (AEF) primarily involved enhanced procedures for operating within third-party trust domains and establishing formal interactions between API exposing functions. Furthermore, the release introduced specific architectural requirements and procedures for the registration of API provider domain functions. These updates provided a more structured framework for AEF interoperability and security in multi-domain API environments.

  • Architectural requirements for registration of API provider domain functions TS 23.222CR0052
  • Procedures for registration of API provider domain functions TS 23.222CR0053
  • Updates to AEF procedures for 3rd party trust domain TS 23.222CR0054
  • Interactions between API exposing functions TS 23.222CR0048
Rel-17 5 changes

In Release 17, the enhancements for the Additional Elementary Functions (AEF) primarily focused on location support and service discovery. Specifically, the release introduced support for AEF location and defined the related API invoker interface for edge applications. These updates included formalizing the `preferred-aef-loc` query parameter for the CAPIF_Discover_Service_API to enable service discovery based on AEF location.

  • Support AEF location and API invoker interface for edge application TS 23.222CR0078
  • AEF location support TS 29.222CR0215
  • Corrections for incomplete functions of ECS and EDGE-6 TS 23.558CR0096
  • Solve EN in ACR Correction to the supported functions of EDGE-9 TS 23.558CR0104
  • CAPIF_Discover_Service_API: formatting of preferred-aef-loc query parameter TS 29.222CR0232
Rel-18 5 changes

In Release 18, the Additional Elementary Functions (AEF) enhancements focused on improving discovery mechanisms within the CAPIF architecture. The new capabilities allow for discovering a proper AEF with owner and IP information, as well as enabling this discovery in interconnection scenarios. These updates address architectural requirements for Standalone Non-Public Networks (SNA) and ensure the EEC's supporting functions are complete.

  • Additional CAPIF architectural requirements for SNA TS 23.222CR0090
  • Discover a proper AEF with owner information TS 23.222CR0094
  • Discover proper AEF in interconnection TS 23.222CR0098
  • Discover proper AEF with IP information TS 23.222CR0103
  • Updating missing EEC’s supporting functions TS 23.558CR0267
Rel-19 8 changes

In Release 19, the new developments for the Additional Elementary Functions (AEF) primarily involved enhancements and clarifications within the CAPIF framework. This included introducing support for AEF instantiation, providing an enhanced description of AEF capabilities, and making additional corrections to CAPIF API definitions such as the CAPIF_Open_Discover_Service_API. The release also addressed specific AEF type corrections and elaborated on the responsibilities of CAPIF API provider domain functions.

  • Additional CAPIF Interconnection-related requirements TS 23.222CR0231
  • Additional RNAA-related requirements TS 23.222CR0232
  • Proposal for AEF instantiation support in CAPIF TS 23.222CR0261
  • Responsibilities of CAPIF API provider domain functions TS 23.222CR0152
  • 23.222 CAPIF_ph3 Correction on AEF type TS 23.222CR0266
  • Enhanced AEF Capabilities Description TS 23.222CR0267

+ 2 more changes

Explore further

Broader topics and technologies where AEF plays a role.

Defining Specifications

3GPP specifications that define or reference AEF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.222 vj80 Common API Framework for 3GPP Northbound APIs Rel-19
TS 23.558 vk00 Architecture for Edge Applications Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15
TR 23.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19
TS 29.222 vj40 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-19
TS 29.549 vj40 SEAL API Specification for Vertical Applications Rel-19
TS 29.558 vj40 Enabling Edge Applications Rel-19
TS 33.122 vj20 Security Architecture for CAPIF Rel-19
TR 33.884 vi01 Technical Report Rel-18