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

Glossary term · Interface

Application Interface

Application Interface

Interface →

Application Interface is a standardized interface used by applications or clients to access service capability features, abstracting network capabilities so third-party and operator applications can invoke services without deep network knowledge.

Introduced
R99
Where
Services
Specifications
3 specs
Application Interface Description Purpose What changed Neighbours Specifications

Description

The Application Interface is a long-standing 3GPP concept, introduced in R99 and documented in TS 21.905 (Vocabulary for 3GPP Specifications), TS 22.121 (Service aspects; The Virtual Home Environment) and TS 22.127 (Service aspects; Stage 1 Service Requirement for the Open Services Access). It defines a standardized interface through which applications or clients access service capability features exposed by the network. In essence, it is the contract between an application layer and the underlying service capability layer, allowing applications to invoke network services in a controlled, standardized manner.

Architecturally, the Application Interface sits between the application domain (which may include operator-hosted applications, third-party applications, or client applications on the UE) and the service capability features provided by the network. These service capability features include, for example, call control, location, messaging, and presence capabilities. By standardizing the interface, 3GPP ensures that applications can be ported across different networks and vendors, and that network operators can expose capabilities in a consistent way. The interface abstracts the complexity of the underlying network protocols and procedures, presenting a simplified, service-oriented view to the application.

The concept is closely tied to the Virtual Home Environment (VHE) and Open Service Access (OSA) work in 3GPP. The VHE aims to provide a consistent service environment for users roaming across networks, and the Application Interface is a key enabler, allowing applications to access service capabilities regardless of the visited network. OSA/Parlay defined APIs that map to the Application Interface, enabling third-party developers to build applications on top of network capabilities. The Application Interface thus forms part of the broader service exposure architecture that later evolved into concepts such as the Service Capability Exposure Function (SCEF) and the Network Exposure Function (NEF) in later releases.

In terms of operation, an application invokes the Application Interface to request a service capability feature. The interface defines the operations, parameters, and data types for these interactions. The network side authenticates and authorizes the application, then executes the requested capability and returns the result. The interface may be realized using various technologies (for example, APIs, CORBA, web services, or RESTful interfaces), depending on the specific service capability and the release. The standardization ensures interoperability and reduces the integration effort for application developers.

The definition of the Application Interface has been remarkably stable. In R99, it was defined as a 'standardised Interface used by applications to access service capability features.' In Rel-4, the wording changed to 'Standardised Interface used by application/clients to access service capability features,' explicitly adding 'clients' to the scope. This change reflects the recognition that not only server-side applications but also client-side applications (for example, on the UE) may access service capability features through the interface. From Rel-5 through Rel-19, the definition carried over unchanged, indicating that the fundamental concept has remained consistent even as the underlying technologies and service exposure mechanisms evolved. The Application Interface remains a foundational concept for service exposure in 3GPP networks.

Purpose & Motivation

The Application Interface exists to provide a standardized, stable contract between applications and the network's service capability features. Without such an interface, each application would need to integrate directly with proprietary network interfaces, leading to fragmentation, high development costs, and limited portability. The Application Interface abstracts the network complexity, allowing application developers to focus on application logic while the interface handles the invocation of network capabilities.

Historically, the concept emerged in R99 in the context of the Virtual Home Environment and Open Service Access. Operators wanted to expose network capabilities (such as call control, location, and messaging) to third-party developers and internal application teams in a controlled manner. The Application Interface provided the standardized access point, enabling a vibrant ecosystem of applications that could run across different networks and vendors. This was a precursor to modern API exposure frameworks.

The Rel-4 change, which added 'clients' to the definition, addressed the growing importance of client-side applications. As UEs became more capable, applications running on the device needed to access service capability features as well. By explicitly including clients, the standard clarified that the Application Interface is not limited to server-side applications but encompasses any application or client that needs to invoke network capabilities. This broadened scope helped drive adoption and ensured that the interface could support the full range of application architectures.

What changed in its specifications

The latest release-to-release comparison of specifications that define Application Interface. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 22.127Rel-7 → Rel-8

Topology hiding, policy management, service subscription, API accounting, identity management, and content management are the main additions in OSA Rel-8.

Full comparison in TS 22.127 →

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.

R99 Initial

Initial definition: 'standardised Interface used by applications to access service capability features.' Established the concept as part of the Virtual Home Environment and Open Service Access work.

Wording changed to 'Standardised Interface used by application/clients to access service capability features.' The explicit addition of 'clients' broadened the scope to include client-side applications, not just server-side applications.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TS 22.127 v900 Open Service Access (OSA) Stage 1 Requirements Rel-9 read