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

Glossary term · QoS

Communication service availability

Communication Service Availability

QoS →

Communication service availability is a percentage measure of the time an end-to-end communication service is delivered according to an agreed QoS, divided by the time it is expected to be delivered.

Introduced
Rel-15
Where
Services
Specifications
7 specs
Communication service availability Description Purpose What changed Neighbours Detected Changes Specifications

Description

Communication Service Availability (CSA) is a quantitative reliability metric defined in 3GPP service requirements specifications (notably TS 22.104 and TS 22.261) to express how dependable an end-to-end communication service is over a defined area and observation period. It is expressed as a percentage and is computed as the amount of time the end-to-end communication service is delivered according to an agreed QoS, divided by the amount of time the system is expected to deliver the end-to-end service according to the specification. In other words, it captures the fraction of the intended service time during which the service actually meets its contracted quality, rather than merely being 'up'.

The metric is end-to-end by design. It spans the entire delivery chain: the device or application endpoint, the radio access network, the transport network, the core network, and any application servers or external networks involved. This is important because a service can fail to meet its QoS at any point in the chain, and CSA deliberately does not attribute availability to a single domain. It is therefore used as a service-level objective (SLO) that must be decomposed into per-domain budgets (RAN, transport, core, application) during network design and slice planning.

CSA is closely related to, but distinct from, other dependability metrics. Communication Service Reliability describes the probability that the service is delivered correctly over a period, while CSA focuses on the proportion of time QoS is met. Latency, jitter, and survival time are complementary attributes: survival time defines how long a communication service may continue without an update before it is considered to have failed, which directly influences how CSA is evaluated for cyclic traffic such as industrial control.

In practice, CSA is used in vertical domains such as factory automation, power distribution, and railway signalling, where TS 22.104 defines use cases with target availability values (for example, 99.9999% for certain closed-loop control applications). Network operators use these targets to dimension redundancy (dual connectivity, redundant paths, N3/N6 redundancy), to design 5G system enablers such as redundant transmission with dual connectivity (TS 23.501), and to define slice SLAs. Monitoring and assurance functions in management specifications (e.g., TS 28.554 KPIs) operationalize CSA so that it can be measured and reported.

Because CSA is defined in service requirements rather than protocol specifications, it is technology-agnostic and applies across 4G, 5G, and future systems. Its precise wording has been refined over releases to remove ambiguity, most notably in Rel-20 where the reference to 'an agreed QoS' was replaced by 'a specified QoS' and the area qualifier was removed, aligning the definition more closely with how the metric is specified and measured in practice.

Purpose & Motivation

Communication Service Availability exists to give vertical industries and operators a single, end-to-end, quantitative way to specify and verify how dependable a communication service must be. Earlier QoS frameworks focused on instantaneous performance attributes (throughput, latency, error rate) but did not express the temporal proportion of time those attributes are actually met across the whole delivery chain. For industrial control, where a missed cycle can halt production, a percentage-of-time availability target is far more meaningful than a peak performance figure.

The concept was motivated by the 5G verticals work in Rel-15, where 3GPP studied factory automation, process automation, and smart grid requirements in TS 22.104 and TS 22.261. Those studies needed a metric that could be contracted in an SLA, decomposed into per-domain budgets, and monitored. CSA filled that gap and became the anchor for reliability-related normative work, including redundant transmission and survival time.

Its continued refinement, such as the Rel-20 wording change from 'agreed QoS' to 'specified QoS', reflects the maturation from a descriptive requirement into a measurable, specification-grounded KPI used in slice assurance and network management.

What changed in its specifications

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

TS 22.104Rel-18 → Rel-19

Rel-19 adds an industrial edge computing clause covering production systems and mobile robot edge control. It also tightens 5G clock synchronisation budgets to 700 ns.

Full comparison in TS 22.104 →
TS 22.261Rel-18 → Rel-19

Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.

Full comparison in TS 22.261 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 1 change
  • Updating the definition of communication service availability TS 22.263CR0014
Rel-18 1 change
  • Quality improvement - updating the definition of communication service availability TS 22.261CR530

Defining Specifications

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

SpecificationTitleRelease
TS 22.104 vj20 Service requirements for cyber-physical control applications Rel-19 read
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read
TS 22.263 vj00 5G Professional Video/Audio/Imaging Requirements Rel-19 read
TS 22.289 vj01 Railway Communication for 5G Systems Rel-19 read
TR 22.804 vg30 5G Automation in Vertical Domains Study Rel-16 read
TR 22.826 vh20 Study on 5G for Critical Medical Applications Rel-17 read
TR 22.874 vi20 Technical Report Rel-18 read