NGSI

Next Generation Service Interfaces

Interface →
Introduced in Rel-15

NGSI is a set of standardized northbound APIs that enable external applications to discover, request, and interact with 3GPP network capabilities and data for service exposure.

Category
Interface
Introduced
Rel-15
Where
Services › IMS
Specifications
2 specs
NGSI Description Purpose Related Classification Detected Changes Specifications

Description

Next Generation Service Interfaces (NGSI) are a cornerstone of 3GPP's service-based architecture (SBA), defined primarily for the 5G Core Network (5GC). They represent the standardized Application Programming Interfaces (APIs) that network functions (NFs) use to communicate with each other internally (southbound) and, more importantly, that expose network capabilities and information to authorized external application functions (AFs) northbound. These interfaces are based on HTTP/2 and JSON, utilizing RESTful principles or asynchronous notifications, making them web-friendly and easily consumable by third-party developers. The specifications, such as TS 23.222 and TS 23.722, detail the procedures, data models, and security mechanisms for these interactions.

Architecturally, NGSI operates through a key network function called the Network Exposure Function (NEF). The NEF acts as a secure gateway and policy enforcement point between the 3GPP network and external AFs. When an application needs to access network data (e.g., user location, network status) or request a specific network behavior (e.g., influence traffic routing, configure QoS), it does not communicate directly with core NFs like the PCF or SMF. Instead, it sends API requests to the NEF. The NEF authenticates and authorizes the request, translates the external API call into internal 3GPP signaling (using service-based interfaces like Npcf or Nsmf), and then returns the response back to the AF. This abstraction layer protects the core network and provides a consistent, versioned API regardless of internal network changes.

How NGSI works involves several key procedures. For capability exposure, an AF can subscribe to specific events (e.g., UE reachability status change) and receive notifications when they occur. For service parameter provisioning, an AF can provide expected service parameters to the network, which the policy framework (PCF) can use to make appropriate QoS decisions. The interfaces support both request-response and subscribe-notify paradigms. Key NGSI APIs include Nnef (for external AFs to interact with the NEF) and the internal SBI APIs like Nnrf (NF discovery), Npcf (policy control), and Nudm (unified data management). By providing these standardized interfaces, NGSI enables use cases like edge computing coordination, enhanced quality of experience for applications, and IoT device management.

Purpose & Motivation

NGSI was created to solve the critical problem of 'walled garden' networks where valuable network capabilities and data were inaccessible to third-party service providers. In pre-5G networks, exposing network functions was often done through proprietary, non-standardized gateways, limiting innovation, slowing down service deployment, and creating security risks. The rise of vertical industry applications (e.g., automotive, Industry 4.0, augmented reality) demanded direct, programmable access to network intelligence like location, bandwidth on demand, and latency guarantees.

The motivation for NGSI stems from the need to transition from a monolithic network offering only connectivity to an open platform enabling 'network as a service.' Previous approaches lacked a unified, secure, and scalable exposure mechanism. NGSI, built upon the cloud-native principle of APIs, directly addresses this. It allows mobile network operators to monetize their network assets by offering them as programmable services via open APIs. This fosters an ecosystem where application developers can create services that are deeply integrated with and optimized by the underlying network.

Furthermore, NGSI is essential for fulfilling 5G's promise of supporting diverse vertical industries. An automotive company, for example, can use NGSI APIs to request ultra-reliable low-latency communication (URLLC) slices for its connected vehicles or to obtain real-time vehicular location data for traffic management. Without a standardized exposure framework like NGSI, each vertical would require costly, custom integration projects. NGSI provides the common, reusable, and secure interface layer that makes such integrations efficient and scalable, enabling new revenue streams and innovative services.

Classification

Part ofAPI
Related approachesCAPIF

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 5 changes

In Release 15, the Common API Framework (CAPIF) was introduced as the new NGSI function, providing a standardized framework for the registration, discovery, and secure management of service APIs. It established common architecture requirements and procedures applicable to any service APIs used by northbound entities, independent of the underlying 3GPP access network. The framework was defined to work with both EPS and 5GS and could be hosted within a PLMN, SNPN, or by a third party.

  • Corrections for CAPIF-1e and CAPIF-2e TS 23.222CR0002
  • Configuration items for CAPIF TS 23.222CR0007
  • Update to CAPIF relationship with 3GPP EPS and 5GS TS 23.222CR0008
  • CAPIF utilization by service APIs TS 23.222CR0010
  • Editorial correction of TS 23.222 (CAPIF stage2) TS 23.222CR0019
Rel-16 11 changes

In Release 16, the key new feature for the NGSI function was the formal specification of CAPIF interconnection, enabling service API discovery and invocation across different trust domains, including third-party domains. This introduced new architectural requirements and procedures for API publishing, discovery, and event handling specifically for interconnected CAPIF provider domains. The release also defined mechanisms for sharing provider domain information and representing the architecture via interfaces to support this interconnection.

  • CAPIF interconnection requirements TS 23.222CR0018
  • Integrated CAPIF with 3GPP EPS and 5GS network exposure TS 23.222CR0021
  • Functional architecture for CAPIF interconnection TS 23.222CR0033
  • API publish and API discover for CAPIF interconnection TS 23.222CR0035
  • Service API discover for CAPIF interconnection TS 23.222CR0051
  • Updates to CAPIF events procedures for 3rd party trust domain TS 23.222CR0057

+ 5 more changes

Rel-17 2 changes

In Release 17, the enhancements for the Next Generation Service Interfaces (NGSI) function within the Common API Framework (CAPIF) focused on clarifying the interactions of service-based interfaces within CAPIF and providing corrections for CAPIF interconnection information elements. These updates refined the framework's mechanisms for API discovery, publication, and secure invocation between API invokers and providers, as applied to both EPS and 5GS.

  • Clarification of Service-based interfaces interaction within CAPIF TS 23.222CR0079
  • Correction for CAPIF interconnection IEs TS 23.222CR0075
Rel-18 13 changes

In Release 18, the enhancements for the Next Generation Service Interfaces (NGSI) function, realized through the Common API Framework (CAPIF), focused on extending its applicability and refining its architecture. Key additions included explicit support for Standalone Non-Public Networks (SNPN) as a CAPIF provider domain and architectural alignment for Roaming and Network Slice Authentication and Authorization (RNAA) scenarios. The release also introduced updates for service onboarding procedures, business relationship models for Service-based Network Architecture (SNA), and extensibility mechanisms as requested by external industry groups.

  • Additional CAPIF architectural requirements for SNA TS 23.222CR0090
  • CAPIF business relationship updates for SNA TS 23.222CR0091
  • CAPIF functional model updates for SNA TS 23.222CR0092
  • CAPIF extensibility as requested by ETSI ISG MEC TS 23.222CR0096
  • Solve CAPIF extensibility EN TS 23.222CR0099
  • Support CAPIF in SNPN TS 23.222CR0109

+ 7 more changes

Rel-19 23 changes

In Release 19, the NGSI function, through the Common API Framework (CAPIF), introduced significant enhancements for interconnection between different CAPIF provider domains. Key additions include new procedures for service API retrieval, update, and unpublish specifically for interconnection, along with enhanced mechanisms for API invoker authorization and security information exchange. The release also formalized support for AEF (API Exposing Function) instantiation and refined the roles and business relationships for interconnected API providers.

  • CAPIF interconnection TS 23.222CR0201
  • Update to API invoker Roles in CAPIF TS 23.222CR0202
  • Additional CAPIF Interconnection-related requirements TS 23.222CR0231
  • Solving ENs on CAPIF interconnection TS 23.222CR0248
  • Correction on Revocation on CAPIF interconnection TS 23.222CR0255
  • Proposal for AEF instantiation support in CAPIF TS 23.222CR0261

+ 17 more changes

Explore further

Broader topics and technologies where NGSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.222 vj80 Common API Framework for 3GPP Northbound APIs Rel-19
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15