Description
In 3GPP management specifications (notably TS 28.535 and TS 28.805), 'Communication Services' refers to a subset of 3GPP-defined services that are relevant to a particular management or orchestration context. The definition is deliberately open: it points to examples such as 5G LAN and URLLC, which are described in the service requirements in TS 22.261. The term therefore acts as a scoping device rather than a single protocol feature — it identifies which of the many services a 5G system can provide are being managed, exposed, or assured in a given procedure.
The concept sits in the management layer. TS 28.535 addresses management and orchestration aspects of 5G communication services, including how services are modelled, how their performance is assured, and how they relate to network slices and network slice subnets. TS 28.805 covers management of 5G communication services more broadly. In these specifications, a communication service is the externally visible offering that a network operator or service provider delivers to a consumer (an enterprise, a vertical, or another operator), and it is realized by one or more network slices or slice subnets underneath.
Architecturally, communication services are modelled as managed entities with associated requirements (QoS, availability, coverage, capacity) and with relationships to the underlying network resources. Management services expose operations to create, modify, monitor, and delete communication services, and to report performance and fault information against them. This layering — communication service on top, slice/slice subnet in the middle, network functions and resources at the bottom — allows assurance to be performed at the service level without exposing internal network details to the consumer.
The term is intentionally broader than 'network slice'. A single communication service may be supported by multiple slices, and a slice may support multiple communication services. Examples such as 5G LAN (localized industrial networking with group-based communication) and URLLC (ultra-reliable low-latency communication) illustrate the range: one is a connectivity service with specific topology semantics, the other is a performance class. Both are 3GPP-defined services that can be offered, managed, and assured as communication services.
Because the definition is a pointer to TS 22.261 rather than an exhaustive list, the set of communication services evolves as new service requirements are added in each release. This keeps the management specifications stable while allowing the catalogue of services to grow with vertical requirements.
Purpose & Motivation
Communication Services as a defined term exists to give management and orchestration specifications a stable, technology-neutral way to refer to the services a 5G system offers to consumers. Before this term was formalized, management work referred to slices and network functions directly, which blurred the boundary between what the customer buys and how it is implemented. By defining communication services as a subset of 3GPP-defined services, the specifications can describe assurance, exposure, and lifecycle management at the service level.
The term was introduced in Rel-16, when 5G management and orchestration work matured and operators needed to manage end-to-end services (not just network elements) across multi-vendor and multi-domain environments. It supports the separation of concerns between the service layer, where SLAs and KPIs such as communication service availability are defined, and the resource layer, where slices and network functions are configured.
By anchoring the definition to TS 22.261, 3GPP ensures that the management view stays aligned with the service requirements view, so that a service promised in requirements can be managed and assured using the same vocabulary.
What changed in its specifications
The latest release-to-release comparison of specifications that define Communication services. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 28.535: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 28.535 →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.
Defining Specifications
3GPP specifications that define or reference Communication services, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.535 vj00 | Closed Control Loop Assurance Management | Rel-19 read |
| TS 28.805 vg10 | Management of Communication Services in 5G | Rel-16 read |