Description
Supplementary Services (SS) represent a comprehensive portfolio of value-added telephony features defined in 3GPP standards that operate in conjunction with the basic telecommunication service, which is primarily the establishment and maintenance of a two-party voice call. They are a cornerstone of traditional circuit-switched (CS) mobile networks like GSM and UMTS, and their principles and many specific services have been carried forward into the IP Multimedia Subsystem (IMS) for VoLTE and VoNR. SS modify, supplement, or restrict the basic call in some way to provide users with greater control, privacy, and functionality.
Architecturally, in classic GSM/UMTS CS networks, Supplementary Services are managed by the Home Location Register (HLR) and executed by the Mobile Switching Center (MSC) or Visitor Location Register (VLR). The HLR stores the subscriber's SS subscription data, including which services are allowed and their specific parameters (e.g., the forward-to number for Call Forwarding Unconditional). When a subscriber registers with a network, this data is transmitted to the VLR serving that subscriber. The MSC/VLR then applies the logic for these services during call setup and in-call phases. Signaling for SS activation, deactivation, and interrogation uses the Mobile Application Part (MAP) protocol between HLR and VLR, and DTMF tones or unstructured Supplementary Service Data (USSD) codes are often used for subscriber interaction.
In the IMS domain for VoLTE/VoNR, Supplementary Services are implemented using SIP (Session Initiation Protocol) methods and event packages, aligning with the IP-based nature of IMS. The service logic often resides in an Application Server (AS) within the IMS core. For example, a Call Forwarding service in IMS would be handled by a SIP AS that intercepts INVITE requests, checks the subscriber's forwarding rules, and potentially redirects the call. The traditional CS-style SS are mapped to equivalent IMS communication services, ensuring feature parity and smooth migration for subscribers. The management of SS settings in IMS can be done via Ut interface (using XCAP protocol) allowing a user to configure services via a web portal.
The operation of a specific Supplementary Service involves a well-defined state model and procedures. Taking Call Waiting as an example: when a subscriber (User B) is engaged in an active call and a new incoming call arrives, the MSC (or IMS AS) determines that Call Waiting is active for User B. Instead of rejecting the new call with a busy signal, the MSC/AS applies call waiting tone to the existing connection and sends a notification (e.g., a SIP re-INVITE with alert-info header) to User B's UE. The UE then provides an indication to the user, who can choose to place the first call on hold and answer the second one, invoking the Call Hold supplementary service. This demonstrates how multiple SS can interact to create a complex user experience. Another critical category is Call Barring, which includes services like Barring of All Outgoing Calls (BAOC) or Barring of Incoming Calls When Roaming (BIC-Roam), which are crucial for security and cost control, especially in roaming scenarios.
Purpose & Motivation
Supplementary Services were created to transform the mobile phone from a simple wireless voice pipe into a sophisticated personal communications tool, matching and eventually surpassing the feature set of the fixed-line telephone network (PSTN/ISDN). The basic telecommunication service only provides connection establishment and voice transmission. SS add the intelligence and user control necessary for practical daily use, such as managing multiple calls, protecting privacy, and customizing call handling based on time or caller identity.
Historically, the development of SS in GSM (starting from Phase 1 and greatly expanded in Phase 2) was driven by the need for standardization across different operators and countries to enable seamless roaming and interoperability. Without standardized SS, a feature like Call Forwarding might work in a subscriber's home network but fail when roaming, leading to a fragmented user experience. The 3GPP specifications provided a common set of features, protocols, and interfaces, ensuring that a service like Calling Line Identification Presentation (CLIP) would work consistently regardless of the visited network.
Furthermore, SS became a significant source of revenue and differentiation for operators. They could offer tiered service packages, charging extra for advanced features like multi-party conferencing or explicit call transfer. They also provided essential tools for subscribers: Call Barring services allowed parents to control children's phone usage or businesses to manage employee calling privileges. Call Forwarding enabled "follow-me" functionality. As networks evolved to IMS and VoIP, it was imperative to preserve this rich set of features to ensure user acceptance of new technology. Therefore, a major design goal for IMS was to support equivalent or enhanced Supplementary Services, solving the problem of feature regression when migrating from CS voice to VoLTE/VoNR, thereby protecting both the user experience and the operator's service revenue.
Key Features
- A standardized set of advanced call features including Call Forwarding (Unconditional, Busy, No Reply), Call Barring (outgoing, incoming, when roaming), Call Waiting, Call Hold
- Calling Line Identification Presentation (CLIP) and Restriction (CLIR) for caller ID management
- Multi-Party Communication (Conferencing) service to establish calls with more than two parties
- Explicit Call Transfer (ECT) allowing a user to transfer an established call to a third party
- Closed User Group (CUG) enabling creation of private calling groups within a network
- Implemented in both circuit-switched core (MSC/HLR) and IMS (SIP Application Servers) with defined interworking
Evolution Across Releases
Introduced a comprehensive set of Supplementary Services for the GSM/UMTS circuit-switched domain as part of the 3GPP standardization. Defined the core architecture with HLR storing subscription data and MSC/VLR executing services. Included fundamental services like Call Forwarding, Call Barring, Call Waiting/Hold, Calling Line Identification, and Multi-Party Communication.
Began the work on mapping and supporting Supplementary Services in the new IP Multimedia Subsystem (IMS) architecture. Defined initial IMS service requirements and the use of SIP for implementing SS features, laying the groundwork for VoLTE.
Enhanced IMS-based Supplementary Services, specifying more detailed SIP procedures for services like Call Hold, Call Waiting, and Conferencing. Introduced the Ut interface using XCAP protocol for user-managed service configuration (e.g., setting call forwarding rules via a web interface).
Continued refinement of IMS Supplementary Services, including work on service interworking between CS and IMS domains (e.g., for subscribers roaming between networks). Improved support for number portability interactions with SS.
Solidified IMS-based Supplementary Services as a core part of the VoLTE profile. Defined the IMS Communication Service Identifier (ICSI) and IMS Application Reference Identifier (IARI) to identify specific SS applications. Ensured alignment with EPS/SAE architecture.
Enhanced support for emergency calls in conjunction with Supplementary Services (e.g., ensuring barring services do not apply to emergency calls). Further defined service continuity aspects for SS during SRVCC handovers.
Introduced Rich Communication Services (RCS) which builds upon IMS and incorporates enhanced messaging and call features that extend traditional Supplementary Services (e.g., enriched call with content sharing).
Focused on service centralization and continuity, ensuring Supplementary Services work seamlessly across access technologies (CS, LTE, WiFi) via the IMS SCC architecture. Refined the management and provisioning interfaces.
Enhanced support for Supplementary Services in machine-type communication (MTC) and for enterprise communications. Worked on optimizations for battery-efficient signaling related to SS management.
Further integration of Supplementary Services with VoLTE and ViLTE (Video over LTE) profiles. Specified detailed test cases and performance requirements for IMS-based SS to ensure interoperability.
Extended Supplementary Services concepts to support Mission Critical Push-to-Talk (MCPTT) and other critical communications services over LTE, defining group call and dynamic group management features.
Defined the support and evolution of Supplementary Services for the 5G System and VoNR. Ensured that IMS-based SS work over the 5G Core network, including interactions with network slicing for service-specific slices.
Enhanced 5G IMS Supplementary Services with a focus on integration with new 5G capabilities like network exposure. Worked on advanced calling services for vertical industries as part of 5G phase 2.
Continued evolution for 5G-Advanced, including Supplementary Services for Non-Public Networks (NPN) and industrial IoT scenarios. Explored AI/ML-based enhancements for intelligent call handling features.
Ongoing work within 5G-Advanced on further enriching communication services, potentially integrating traditional SS with immersive media calls and extended reality (XR) applications.
Maintenance and potential introduction of new service features for the evolving 5G and beyond 5G communication landscape, ensuring Supplementary Services remain relevant and powerful.
Future-looking evolution, likely focusing on the integration of communication services with AI-driven networks, advanced privacy features, and support for novel use cases in the 6G exploration timeframe.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.110 | 3GPP TS 23.110 |
| TS 24.167 | 3GPP TS 24.167 |
| TS 24.424 | 3GPP TS 24.424 |
| TS 24.623 | 3GPP TS 24.623 |
| TS 25.171 | 3GPP TS 25.171 |
| TS 25.172 | 3GPP TS 25.172 |
| TS 25.173 | 3GPP TS 25.173 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 26.130 | 3GPP TS 26.130 |
| TS 26.131 | 3GPP TS 26.131 |
| TS 26.132 | 3GPP TS 26.132 |
| TS 26.253 | 3GPP TS 26.253 |
| TS 26.260 | 3GPP TS 26.260 |
| TS 28.309 | 3GPP TS 28.309 |
| TS 28.518 | 3GPP TS 28.518 |
| TS 28.541 | 3GPP TS 28.541 |
| TS 28.606 | 3GPP TS 28.606 |
| TS 28.616 | 3GPP TS 28.616 |
| TS 28.622 | 3GPP TS 28.622 |
| TS 28.623 | 3GPP TS 28.623 |
| TS 28.626 | 3GPP TS 28.626 |
| TS 28.629 | 3GPP TS 28.629 |
| TS 28.653 | 3GPP TS 28.653 |
| TS 28.656 | 3GPP TS 28.656 |
| TS 28.659 | 3GPP TS 28.659 |
| TS 28.662 | 3GPP TS 28.662 |
| TS 28.663 | 3GPP TS 28.663 |
| TS 28.669 | 3GPP TS 28.669 |
| TS 28.673 | 3GPP TS 28.673 |
| TS 28.676 | 3GPP TS 28.676 |
| TS 28.706 | 3GPP TS 28.706 |
| TS 28.709 | 3GPP TS 28.709 |
| TS 28.733 | 3GPP TS 28.733 |
| TS 28.736 | 3GPP TS 28.736 |
| TS 29.007 | 3GPP TS 29.007 |
| TS 29.332 | 3GPP TS 29.332 |
| TS 29.412 | 3GPP TS 29.412 |
| TS 29.424 | 3GPP TS 29.424 |
| TS 31.111 | 3GPP TR 31.111 |
| TS 31.121 | 3GPP TR 31.121 |
| TS 31.829 | 3GPP TR 31.829 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.103 | 3GPP TR 32.103 |
| TS 32.111 | 3GPP TR 32.111 |
| TS 32.150 | 3GPP TR 32.150 |
| TS 32.153 | 3GPP TR 32.153 |
| TS 32.154 | 3GPP TR 32.154 |
| TS 32.300 | 3GPP TR 32.300 |
| TS 32.302 | 3GPP TR 32.302 |
| TS 32.303 | 3GPP TR 32.303 |
| TS 32.306 | 3GPP TR 32.306 |
| TS 32.307 | 3GPP TR 32.307 |
| TS 32.311 | 3GPP TR 32.311 |
| TS 32.312 | 3GPP TR 32.312 |
| TS 32.313 | 3GPP TR 32.313 |
| TS 32.316 | 3GPP TR 32.316 |
| TS 32.317 | 3GPP TR 32.317 |
| TS 32.323 | 3GPP TR 32.323 |
| TS 32.326 | 3GPP TR 32.326 |
| TS 32.343 | 3GPP TR 32.343 |
| TS 32.346 | 3GPP TR 32.346 |
| TS 32.347 | 3GPP TR 32.347 |
| TS 32.353 | 3GPP TR 32.353 |
| TS 32.356 | 3GPP TR 32.356 |
| TS 32.363 | 3GPP TR 32.363 |
| TS 32.366 | 3GPP TR 32.366 |
| TS 32.367 | 3GPP TR 32.367 |
| TS 32.373 | 3GPP TR 32.373 |
| TS 32.376 | 3GPP TR 32.376 |
| TS 32.393 | 3GPP TR 32.393 |
| TS 32.396 | 3GPP TR 32.396 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.413 | 3GPP TR 32.413 |
| TS 32.416 | 3GPP TR 32.416 |
| TS 32.417 | 3GPP TR 32.417 |
| TS 32.443 | 3GPP TR 32.443 |
| TS 32.446 | 3GPP TR 32.446 |
| TS 32.506 | 3GPP TR 32.506 |
| TS 32.507 | 3GPP TR 32.507 |
| TS 32.523 | 3GPP TR 32.523 |
| TS 32.526 | 3GPP TR 32.526 |
| TS 32.602 | 3GPP TR 32.602 |
| TS 32.603 | 3GPP TR 32.603 |
| TS 32.606 | 3GPP TR 32.606 |
| TS 32.607 | 3GPP TR 32.607 |
| TS 32.613 | 3GPP TR 32.613 |
| TS 32.616 | 3GPP TR 32.616 |
| TS 32.617 | 3GPP TR 32.617 |
| TS 32.622 | 3GPP TR 32.622 |
| TS 32.623 | 3GPP TR 32.623 |
| TS 32.626 | 3GPP TR 32.626 |
| TS 32.643 | 3GPP TR 32.643 |
| TS 32.646 | 3GPP TR 32.646 |
| TS 32.652 | 3GPP TR 32.652 |
| TS 32.653 | 3GPP TR 32.653 |
| TS 32.656 | 3GPP TR 32.656 |
| TS 32.662 | 3GPP TR 32.662 |
| TS 32.663 | 3GPP TR 32.663 |
| TS 32.666 | 3GPP TR 32.666 |
| TS 32.667 | 3GPP TR 32.667 |
| TS 32.673 | 3GPP TR 32.673 |
| TS 32.676 | 3GPP TR 32.676 |
| TS 32.713 | 3GPP TR 32.713 |
| TS 32.716 | 3GPP TR 32.716 |
| TS 32.722 | 3GPP TR 32.722 |
| TS 32.723 | 3GPP TR 32.723 |
| TS 32.726 | 3GPP TR 32.726 |
| TS 32.733 | 3GPP TR 32.733 |
| TS 32.736 | 3GPP TR 32.736 |
| TS 32.743 | 3GPP TR 32.743 |
| TS 32.746 | 3GPP TR 32.746 |
| TS 32.753 | 3GPP TR 32.753 |
| TS 32.756 | 3GPP TR 32.756 |
| TS 32.763 | 3GPP TR 32.763 |
| TS 32.766 | 3GPP TR 32.766 |
| TS 32.773 | 3GPP TR 32.773 |
| TS 32.776 | 3GPP TR 32.776 |
| TS 32.783 | 3GPP TR 32.783 |
| TS 32.786 | 3GPP TR 32.786 |
| TS 32.792 | 3GPP TR 32.792 |
| TS 32.796 | 3GPP TR 32.796 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.818 | 3GPP TR 32.818 |
| TS 32.824 | 3GPP TR 32.824 |
| TS 32.832 | 3GPP TR 32.832 |
| TS 32.866 | 3GPP TR 32.866 |
| TS 32.880 | 3GPP TR 32.880 |
| TS 34.109 | 3GPP TR 34.109 |
| TS 34.114 | 3GPP TR 34.114 |
| TS 34.229 | 3GPP TR 34.229 |
| TS 36.171 | 3GPP TR 36.171 |
| TS 36.509 | 3GPP TR 36.509 |
| TS 36.579 | 3GPP TR 36.579 |
| TS 37.171 | 3GPP TR 37.171 |
| TS 37.355 | 3GPP TR 37.355 |
| TS 37.544 | 3GPP TR 37.544 |
| TS 37.571 | 3GPP TR 37.571 |
| TS 37.579 | 3GPP TR 37.579 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 37.910 | 3GPP TR 37.910 |
| TS 37.911 | 3GPP TR 37.911 |
| TS 37.976 | 3GPP TR 37.976 |
| TS 37.977 | 3GPP TR 37.977 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.104 | 3GPP TR 38.104 |
| TS 38.151 | 3GPP TR 38.151 |
| TS 38.161 | 3GPP TR 38.161 |
| TS 38.171 | 3GPP TR 38.171 |
| TS 38.212 | 3GPP TR 38.212 |
| TS 38.214 | 3GPP TR 38.214 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.321 | 3GPP TR 38.321 |
| TS 38.508 | 3GPP TR 38.508 |
| TS 38.509 | 3GPP TR 38.509 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.551 | 3GPP TR 38.551 |
| TS 38.561 | 3GPP TR 38.561 |
| TS 38.741 | 3GPP TR 38.741 |
| TS 38.761 | 3GPP TR 38.761 |
| TS 38.762 | 3GPP TR 38.762 |
| TS 38.810 | 3GPP TR 38.810 |
| TS 38.817 | 3GPP TR 38.817 |
| TS 38.834 | 3GPP TR 38.834 |
| TS 38.852 | 3GPP TR 38.852 |
| TS 38.853 | 3GPP TR 38.853 |
| TS 38.863 | 3GPP TR 38.863 |
| TS 38.870 | 3GPP TR 38.870 |
| TS 38.873 | 3GPP TR 38.873 |
| TS 38.884 | 3GPP TR 38.884 |
| TS 41.033 | 3GPP TR 41.033 |
| TS 43.901 | 3GPP TR 43.901 |
| TS 51.010 | 3GPP TR 51.010 |
| TS 52.402 | 3GPP TR 52.402 |