Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

API exposing function location

API exposing function location

Services →

API exposing function location is the location information specifying where a service API is hosted, including civic address, GPS coordinates, or data center ID, for location-aware service discovery and selection in the 5G Service Based Architecture.

Introduced
Rel-17
Where
Services › IMS
Specifications
2 specs
API exposing function location Description Purpose What changed Neighbours Specifications

Description

The API exposing function (AEF) location is a concept introduced in 3GPP Release 17 within the Service Based Architecture (SBA) for 5G core networks. It is defined in TS 23.222 (Common API Framework for 3GPP Northbound APIs) and TS 29.222 (CAPIF API specification). The AEF is the entity that exposes service APIs to API invokers, and its location information is used to describe where the API is physically or logically hosted. This location can be expressed as a civic address, GPS coordinates, a data center identifier, or other forms of location data. The primary purpose is to enable location-aware service discovery and selection, allowing API invokers to choose an API instance that is geographically close or meets specific location requirements.

In the Common API Framework (CAPIF), the AEF registers with the CAPIF Core Function (CCF) and provides its location information as part of the service API description. The CCF stores this information and makes it available to API invokers during service discovery. When an API invoker queries for a service API, it can include location preferences or constraints, and the CCF can return a list of AEFs that match those criteria. This is particularly useful for latency-sensitive applications, where selecting a nearby AEF reduces round-trip time, or for regulatory reasons, where data must be processed within a certain jurisdiction.

The location information is also relevant for edge computing scenarios, where AEFs may be deployed at the network edge to serve local users. By knowing the location of the AEF, the network can route API requests efficiently and ensure that services are provided from the most appropriate location. The AEF location is an attribute in the service API description, which is a JSON object containing details such as API name, version, and endpoint. The location attribute is optional but recommended for scenarios where location matters.

From an architectural perspective, the AEF location is part of the CAPIF framework, which standardises API exposure across 3GPP and non-3GPP domains. CAPIF provides authentication, authorization, and discovery functions. The AEF location enhances discovery by adding a spatial dimension. It is also used in the context of network exposure function (NEF) and service capability exposure function (SCEF) for external API exposure, where the location of the exposure function can influence the choice of API endpoint.

In summary, the API exposing function location is a key enabler for location-aware API discovery and selection in 5G SBA. It allows service providers to deploy APIs in multiple locations and enables API invokers to select the most suitable instance based on proximity, latency, or regulatory requirements. This concept is particularly important for edge computing and low-latency services, aligning with the broader goals of 5G to provide flexible and efficient service delivery.

Purpose & Motivation

The API exposing function location was introduced to address the need for location-aware service discovery in the 5G Service Based Architecture. As networks become more distributed, with edge computing and multi-access edge computing (MEC), the physical location of API endpoints becomes relevant for latency, bandwidth, and regulatory compliance. Prior to Rel-17, CAPIF provided service discovery based on API name and version, but lacked location information. This limitation made it difficult for API invokers to select the nearest or most appropriate API instance. The introduction of AEF location solves this by allowing API invokers to specify location preferences and enabling the CAPIF Core Function to return AEFs that match those criteria. This is especially important for latency-sensitive applications like URLLC and for scenarios where data sovereignty laws require processing within specific regions. The concept also supports the evolution towards edge computing, where APIs are deployed closer to users.

What changed in its specifications

The latest release-to-release comparison of specifications that define API exposing function location. Each summary describes the whole specification, not only this term.

TS 23.222Rel-18 → Rel-19

Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.

Full comparison in TS 23.222 →
TS 29.222Rel-17 → Rel-18

Adds subscriber-aware northbound API access (OAuth grant types, API provider name, UE IP address types), SEAL Phase 3 (API status monitoring, protocol/data format support, CAPIF features), Edge Apps Phase 2 (8.2.4.1, ServiceKpis, AefProfile), and slice capability exposure expiration time.

Full comparison in TS 29.222 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-17 Initial

Initial definition introduced in TS 23.222 and TS 29.222, specifying that the API exposing function location includes information such as civic address, GPS coordinates, or data center ID. This enabled location-aware service discovery in CAPIF.

The definition text carried over unchanged, continuing to support location-aware API discovery as CAPIF evolved.

The definition remained unchanged, maintaining consistency for ongoing CAPIF enhancements.

The definition was unchanged, ensuring stable reference for future releases.

Defining Specifications

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

SpecificationTitleRelease
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 29.222 vk10 CAPIF Northbound API Protocol Rel-20 read