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

Glossary term · Services

Service Capability Feature

Service Capability Feature

Services →

Service Capability Feature is a standardized function exposed by service capabilities through an open API, enabling applications to access network services.

Introduced
R99
Where
Services
Specifications
5 specs
Service Capability Feature Description Purpose What changed Neighbours Specifications

Description

A Service Capability Feature (SCF) is a fundamental concept in the 3GPP service architecture, representing a specific piece of functionality offered by service capabilities that is accessible via a standardized application interface. SCFs are the atomic units that, when combined, form complete services. They abstract the underlying network complexity and expose it to application developers through open APIs, enabling the creation of value-added services without deep knowledge of the telecom infrastructure.

In the 3GPP architecture, service capabilities are provided by various network elements, such as the Service Capability Server (SCS) or the Service Capability Exposure Function (SCEF). Each SCF corresponds to a distinct capability, such as location reporting, messaging, call control, or session management. These features are defined in specifications like TS 22.105 (Services and service capabilities) and TS 22.121 (Service aspects; The Virtual Home Environment), ensuring interoperability and consistent behavior across different networks and vendors.

SCFs are exposed through standardized APIs, often based on RESTful principles in modern releases (e.g., via the Service Capability Exposure Function in 5G). This allows third-party application providers to integrate telecom services into their applications seamlessly. For example, an SCF for location could enable a weather app to automatically adjust forecasts based on the user's current cell, or an SCF for messaging could allow an enterprise application to send SMS notifications.

The concept of SCFs is closely tied to the Virtual Home Environment (VHE) and the Open Service Access (OSA) initiative, which aimed to provide a consistent service environment across network boundaries. In later releases, the Service Capability Exposure Function (SCEF) in 4G and the Network Exposure Function (NEF) in 5G have become the primary enablers for exposing SCFs to external applications, following the principles of Service Capability Interaction Managers (SCIM) and API gateways.

SCFs are essential for fostering innovation and enabling operators to monetize their network assets beyond basic connectivity. They allow rapid service creation, reduce time-to-market for new applications, and ensure that services can be ported across different access technologies and network generations. As networks evolve towards 5G and beyond, SCFs continue to play a critical role in the service layer, supporting diverse use cases from IoT to mission-critical communications.

Purpose & Motivation

Service Capability Features exist to bridge the gap between complex telecom network functionalities and application developers. Before SCFs, accessing network services required deep protocol knowledge and proprietary integrations, which hindered innovation and limited service creation to operators and their close partners. SCFs provide a standardized, open interface that abstracts network complexity, enabling third parties to leverage telecom capabilities easily.

The primary motivation for SCFs was the need for a consistent service environment across different networks and generations, as envisioned by the Virtual Home Environment (VHE). This allows users to access their personalized services anywhere, regardless of the underlying network. SCFs also address the fragmentation of service delivery by defining reusable building blocks that can be combined in various ways to create new services, promoting interoperability and reducing development costs.

Furthermore, SCFs enable operators to expose their network capabilities as APIs, creating new revenue streams and fostering an ecosystem of applications. They are foundational to the concept of the programmable network, where services can be dynamically composed and adapted to user needs. As networks move towards 5G and network slicing, SCFs become even more critical for enabling tailored services for different vertical industries.

What changed in its specifications

The latest release-to-release comparison of specifications that define Service Capability Feature. 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.105Rel-7 → Rel-8

Rel-8 added Service-Level Interworking for Messaging Services, enabling SMS interworking with other messaging services over IP-CAN subject to operator policy and verification.

Full comparison in TS 22.105 →

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 introduced: 'functionality offered by service capabilities that are accessible via the standardised application interface.' This established the concept of SCFs as the fundamental units of service composition in the 3GPP service architecture.

Wording changed to: 'Functionality offered by service capabilities that are accessible via the standardised application interfaceServices: Services are made up of different service capability features.' This added an explicit statement that services are composed of SCFs, clarifying their role as building blocks.

Wording changed back to the original: 'functionality offered by service capabilities that are accessible via the standardised application interface.' The explicit composition statement was removed, possibly to avoid redundancy or to align with other definitions.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5, with only minor formatting differences (capitalization).

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Definition carried over unchanged from Rel-5.

Defining Specifications

3GPP specifications that define or reference Service Capability Feature, 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.105 vj00 Telecommunication Services Framework 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
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read