Communication Service Customer

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.

Key Features

• Represents the administrative entity consuming services via a commercial agreement
• Interacts with the provider's management system via the standardized Consumer-facing Service Interface (CnF)
• Central role in requesting, modifying, and terminating network slice instances
• Receives service assurance data, performance reports, and fault notifications
• Enables customer self-service and automation for service lifecycle management
• Fundamental for implementing SLA-driven B2B and Network-as-a-Service models

Evolution Across Releases

Defining Specifications