Description
Single-Cell Point-to-Multipoint (SC-PTM) is a transmission mode and feature set within the LTE Radio Access Network that enables the network (specifically the eNodeB) to deliver the same content to multiple User Equipments (UEs) simultaneously using shared radio resources within the coverage area of a single cell. It is a complementary technology to MBMS (Multimedia Broadcast Multicast Service) based on MBSFN (Multicast-Broadcast Single Frequency Network), but it operates without the need for time-synchronized transmission across multiple cells. The SC-PTM architecture introduces new logical channels and procedures in the LTE stack to manage multicast sessions. The two key logical channels are the Single Cell Multicast Control Channel (SC-MCCH) and the Single Cell Multicast Transport Channel (SC-MTCH). The SC-MCCH carries control information, such as the configuration, scheduling, and modification details for available SC-PTM services. The SC-MTCH carries the actual user data for the multicast service.
The operation of SC-PTM involves several steps. First, the network broadcasts system information that indicates the availability of SC-PTM and provides the configuration for the SC-MCCH, including its scheduling and a modification period. UEs interested in multicast services (identified by a Temporary Mobile Group Identity - TMGI) monitor the SC-MCCH to discover which services are available and how to receive them. When a UE decides to join a service, it extracts the scheduling information and the associated Group RNTI (G-RNTI) for that service's SC-MTCH. The eNodeB then transmits the multicast data on the Physical Downlink Shared Channel (PDSCH) at the scheduled times. The eNodeB uses the G-RNTI to scramble the corresponding PDCCH messages that point to the PDSCH resources, allowing all UEs subscribed to that G-RNTI to decode the data. A separate fixed RNTI, the SC-N-RNTI (Single Cell Notification RNTI), is used on the PDCCH to notify UEs of changes to the SC-MCCH information, enabling efficient power saving.
SC-PTM is integrated into the broader LTE protocol architecture. At the Radio Resource Control (RRC) layer, UEs can be in RRC_IDLE or RRC_CONNECTED state while receiving SC-PTM. The service itself is initiated and managed by the core network, often via the MBMS Gateway (MBMS-GW) and the Broadcast Multicast Service Center (BM-SC), but the data path for SC-PTM bypasses the MCE (Multi-cell/multicast Coordination Entity) used for MBSFN. The eNodeB receives the multicast IP packets from the core network and handles all radio resource scheduling and transmission for its cell independently. This single-cell autonomy is a defining characteristic. For reliability, SC-PTM does not use MAC-layer HARQ retransmissions due to its point-to-multipoint nature. Instead, reliability can be provided at the application layer using forward error correction (FEC) or through RLC unacknowledged mode transmissions with potential repetition. The feature is designed to be lightweight, making it suitable for services that are localized, sporadic, or do not justify the complexity and overhead of establishing an MBSFN area.
Purpose & Motivation
SC-PTM was developed to address the need for a flexible, efficient, and deployable multicast solution for LTE that complements the existing MBSFN-based MBMS. MBSFN is excellent for high-quality, synchronized video broadcast over a wide area (like mobile TV) but requires precise synchronization among all eNodeBs in the MBSFN area, careful network planning, and is less agile for dynamic or localized services. Many emerging use cases, such as public safety group communications (Mission Critical Push-To-Talk), software updates for IoT devices, or targeted advertising in a specific location, do not require wide-area synchronization and benefit from a simpler, cell-centric approach.
The primary problem SC-PTM solves is the inefficiency of using multiple unicast bearers (Dedicated Traffic Channels - DTCH) to deliver the same content to many users in one cell. Unicast replication wastes downlink radio resources and eNodeB processing power. SC-PTM allows a single transmission of a data packet over the air to be received by an entire group, dramatically improving spectral efficiency for group communication scenarios. This is particularly important for network capacity and for serving large numbers of low-cost, battery-constrained MTC devices.
Introduced in 3GPP Release 13 as part of the enhancements for Machine-Type Communication (eMTC) and Critical Communications, SC-PTM filled a crucial gap in the LTE service portfolio. It provided a standardized, optimized method for point-to-multipoint delivery that operators could deploy rapidly, often with only software upgrades to existing eNodeBs, without the need for the extensive backhaul synchronization and coordination required for MBSFN. Its creation was motivated by concrete demands from vertical industries like public safety and utilities, which needed reliable group communication for their operational workflows.
Key Features
- Enables multicast/broadcast data transmission within a single LTE cell without MBSFN synchronization.
- Utilizes dedicated logical channels: SC-MCCH for control and SC-MTCH for user data.
- Employs group identifiers (G-RNTI) for scheduling and a fixed SC-N-RNTI for change notifications.
- Supports UEs in both RRC_IDLE and RRC_CONNECTED states for service reception.
- Improves spectral efficiency versus unicast replication for group services.
- Designed for low overhead, suitable for sporadic, localized, or IoT-oriented multicast traffic.
Evolution Across Releases
Initial introduction for LTE. Defined the overall SC-PTM architecture, including SC-MCCH and SC-MTCH logical channels, SC-N-RNTI notification procedure, and integration with MBMS core network for service announcement. Targeted eMTC, public safety, and efficient software update distribution.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.741 | 3GPP TS 23.741 |
| TS 23.780 | 3GPP TS 23.780 |
| TS 23.795 | 3GPP TS 23.795 |
| TS 25.446 | 3GPP TS 25.446 |
| TS 26.989 | 3GPP TS 26.989 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.306 | 3GPP TR 36.306 |
| TS 36.321 | 3GPP TR 36.321 |
| TS 36.443 | 3GPP TR 36.443 |
| TS 36.444 | 3GPP TR 36.444 |
| TS 36.890 | 3GPP TR 36.890 |
| TS 37.985 | 3GPP TR 37.985 |
| TS 38.913 | 3GPP TR 38.913 |