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

Glossary term · Services

CSC

Communication Service Customer

Services →

CSC is the 3GPP management entity that purchases, consumes, and manages communication services from a network operator or service provider.

Introduced
Rel-5
Where
Management
Specifications
21 specs
Also in
Services, Security
CSC Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Communication Service Customer (CSC) is a functional role defined within the 3GPP management architecture, specifically in the context of the Management and Orchestration (MANO) framework and network slicing. It represents the organizational entity (which could be an enterprise, a vertical industry player, a virtual operator, or even another service provider) that has a commercial agreement with a Communication Service Provider (CSP) to consume one or more communication services. The CSC is not the end-user device but the administrative and business entity responsible for the service relationship.

Architecturally, the CSC interacts with the CSP's management systems through standardized reference points, primarily the Consumer-facing Service Interface (CnF). Through this interface, the CSC can request services, such as the creation of a network slice instance, modify service parameters, monitor service performance, and receive fault and performance reports. The CSC's domain includes its own management systems (CSC Management System) which may integrate with the CSP's Business Support Systems (BSS) and Operations Support Systems (OSS). This separation allows the CSP to expose a controlled set of management capabilities to the customer, enabling self-service and automation.

The role of the CSC is central to the network slicing paradigm defined from 3GPP Release 15 onwards. When a CSC (e.g., an automotive company) requires a dedicated network slice for connected car services, it submits a service request via the CnF. This request, containing the Network Slice Service Profile, triggers the CSP's orchestration systems to instantiate the necessary network functions across the RAN, transport, and core network to fulfill the service-level agreement (SLA). The CSC then receives continuous insight into the slice's performance, including key performance indicators (KPIs) like latency, throughput, and availability, allowing for proactive management of their application's quality of experience.

Key components in the CSC ecosystem include the CSC Management System, which formulates service requests and consumes service assurance data, and the Service Management Function (SMF) within the CSP's domain that handles these requests. The relationship is governed by a Service Level Agreement (SLA) that defines technical performance targets, business terms, and reporting obligations. The CSC concept enables a clear demarcation between the provider's network management responsibilities and the customer's service management responsibilities, which is essential for complex, SLA-driven 5G and beyond services.

Purpose & Motivation

The CSC concept was introduced to formalize and standardize the business-to-business (B2B) and customer-to-provider relationship in telecommunication services, particularly as networks evolved to support diverse vertical industries with 5G. Prior to its formal definition, service management interfaces were often proprietary, limiting automation and hindering the scalable onboarding of enterprise customers. The CSC model addresses the need for a standardized, automated, and programmable interface through which customers can directly interact with the provider's network capabilities.

Historically, enterprise services were provisioned through manual, ticket-based processes with limited customer visibility into network performance. The shift towards network virtualization, cloud-native principles, and network slicing demanded a more dynamic, API-driven approach. The CSC role, along with the CnF interface, was created to solve this by enabling zero-touch service management. It allows vertical customers (in manufacturing, healthcare, logistics, etc.) to order, configure, and monitor their dedicated network services (slices) on-demand, much like consuming cloud computing resources. This is a fundamental change from the traditional monolithic, one-size-fits-all network service model.

Furthermore, the CSC framework supports the monetization of 5G networks by providing the necessary management architecture for Network-as-a-Service (NaaS) business models. It allows Communication Service Providers to expose network capabilities as manageable, billable services with clear ownership and accountability boundaries. This empowers enterprises to innovate by integrating guaranteed network performance directly into their operational technology and applications, driving the digital transformation of industries.

What changed in its specifications

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

TS 23.280Rel-18 → Rel-19

Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.

Full comparison in TS 23.280 →
TS 25.223Rel-9 → Rel-10

Added MU-MIMO definition and modified scheduled E-HICH signature sequence allocation rules for MU-MIMO users.

Full comparison in TS 25.223 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 2 changes
  • Corrections to reference point CSC-16 TS 23.280CR0348
  • SIP interface corrections for reference points CSC-7, CSC-19, CSC-20 TS 23.280CR0349
Rel-20 1 change
  • Revised CSC-15: Incorporating Additional LMS and MC Service Server Interactions TS 23.280CR0671

Defining Specifications

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

SpecificationTitleRelease
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 25.223 vj00 UTRA Physical Layer TDD Spreading & Modulation Rel-19 read
TS 26.941 vk00 5GMS Network Slicing Study Rel-20 read
TS 28.530 vj00 Network Slicing Concepts & Requirements Rel-19 read
TS 28.531 vk10 5G Network Slice Provisioning Management Rel-20 read
TS 28.535 vj00 Closed Control Loop Assurance Management Rel-19 read
TS 28.536 vj20 Management services for communication service assurance Rel-19 read
TS 28.557 vj00 Management of Non-Public Networks (NPN) Rel-19 read
TS 28.805 vg10 Management of Communication Services in 5G Rel-16 read
TR 28.812 vh10 Study on Intent Driven Management Services Rel-17 read
TR 28.828 vi00 Charging Aspects for Non-Public Networks Rel-18 read
TR 28.836 vi00 Technical Report on Intent Driven Management Rel-18 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TR 32.847 vi00 Technical Report Rel-18 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.128 vj80 Lawful Interception Protocols and Procedures Rel-19 read
TS 33.179 vdc0 MCPTT Security Architecture and Procedures Rel-13 read
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.879 vd10 MCPTT Security Study Rel-13 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read