Description
Super-Charger (SC), as defined in 3GPP specifications such as TS 23.116, is a network-based service optimization feature. It operates as an enhancement within the mobile core network, specifically interacting with the Policy and Charging Control (PCC) architecture and often involving a Traffic Detection Function (TDF). The core concept of SC is to identify specific types of user data traffic—primarily web (HTTP/HTTPS) and video streaming traffic—and apply optimizations to improve the quality of experience (QoE) and the efficiency of network resource utilization. It is not a standalone network node but a set of capabilities that can be integrated into existing network elements or deployed as a dedicated service.
Architecturally, SC functionality typically involves several key components. A Traffic Detection Function (TDF) is crucial for deep packet inspection (DPI) to identify SC-eligible traffic flows based on application type, destination, or content. The TDF communicates with the Policy and Charging Rules Function (PCRF) via the Sd reference point. Based on the traffic detection report and operator-defined policies, the PCRF can then install new rules in the Policy and Charging Enforcement Function (PCEF), which resides in the Gateway (e.g., PGW/UPF). These rules govern how the identified traffic is handled. The actual optimization might be performed by the PCEF itself, a dedicated optimization node (like a transparent proxy or cache), or through steering traffic to a Service Capability Exposure Function (SCEF)/Network Exposure Function (NEF) for third-party application server interaction.
How SC works involves a dynamic policy cycle. When a user starts a data session, the PCEF requests rules from the PCRF. If SC is enabled, the PCRF may activate traffic detection for that session. As packets flow through the gateway, the TDF (which could be collocated with the PCEF) inspects them. Upon detecting traffic matching a Super-Charger policy (e.g., video from a specific provider), the TDF informs the PCRF. The PCRF then decides on an action, such as applying a dedicated bearer with guaranteed bit rate (GBR) for that video flow, instructing the PCEF to apply header compression, or redirecting the flow through a content optimization engine that might perform caching, transcoding, or compression. This entire process happens dynamically and per-flow, allowing for granular service differentiation.
The role of SC in the network is to bridge the gap between simple best-effort internet access and sophisticated application-aware networking. It allows mobile network operators to actively manage and enhance popular data services. By prioritizing, shaping, or optimizing specific traffic, SC can reduce video buffering, speed up web page loads, and decrease overall latency. This leads to higher customer satisfaction. From a network perspective, SC can improve spectral efficiency by reducing the volume of redundant data (through caching) and ensuring critical traffic gets the resources it needs, thereby smoothing traffic peaks and improving overall network capacity and performance for all users.
Purpose & Motivation
Super-Charger was created to address the challenges posed by the explosive growth of internet traffic, particularly bandwidth-intensive and latency-sensitive applications like video streaming and web browsing, on mobile networks. The classic best-effort IP model in mobile cores was insufficient to guarantee a good quality of experience for these services, leading to user frustration with buffering and slow loads. SC's purpose is to solve this by enabling the network to intelligently identify and optimize specific traffic flows, thereby accelerating service delivery and making more efficient use of limited radio and transport resources.
The historical context for SC lies in the evolution from simple voice-centric networks to complex data-centric service platforms. As 3G and 4G (LTE) deployed, operators sought ways to monetize data services beyond simple volume charging. They needed tools to differentiate their offerings—for example, providing a 'premium video' service tier. SC provided the technical framework to do this. It addressed the limitations of previous, more static approaches to QoS, which often relied on Access Point Name (APN) or static IP address filtering, by introducing dynamic, application-aware policy control. This allowed for real-time reaction to user activity.
Furthermore, SC was motivated by the need for network efficiency. Transmitting the same popular video content to thousands of users independently wastes backhaul and radio resources. By integrating caching and compression capabilities, SC aims to reduce redundant data transmission. It also allows operators to manage traffic peaks more effectively by ensuring high-priority services remain stable during congestion. In essence, SC exists to transform the mobile network from a passive bit-pipe into an active, service-aware platform that can enhance performance, create new service tiers, and improve the economic efficiency of data service delivery.
Key Features
- Application-aware traffic detection via Deep Packet Inspection (DPI)
- Dynamic policy enforcement integrated with PCC architecture
- Capability to trigger dedicated bearers for optimized traffic flows
- Support for content optimization techniques (e.g., caching, compression)
- Quality of Experience (QoE) monitoring and reporting
- Enables service differentiation and tiered data offerings
Evolution Across Releases
The concept of service optimization and enhanced data services began to take shape. While not formally named 'Super-Charger' at this stage, R99 introduced fundamental packet-switched core network elements (SGSN, GGSN) and basic QoS mechanisms. This release laid the groundwork for identifying and treating different data flows separately, which is a core principle later refined and formalized into the Super-Charger feature set in subsequent releases.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.944 | 3GPP TS 22.944 |
| TS 22.950 | 3GPP TS 22.950 |
| TS 22.978 | 3GPP TS 22.978 |
| TS 23.016 | 3GPP TS 23.016 |
| TS 23.039 | 3GPP TS 23.039 |
| TS 23.237 | 3GPP TS 23.237 |
| TS 23.875 | 3GPP TS 23.875 |
| TS 23.889 | 3GPP TS 23.889 |
| TS 24.216 | 3GPP TS 24.216 |
| TS 24.237 | 3GPP TS 24.237 |
| TS 24.337 | 3GPP TS 24.337 |
| TS 25.141 | 3GPP TS 25.141 |
| TS 25.142 | 3GPP TS 25.142 |
| TS 25.707 | 3GPP TS 25.707 |
| TS 28.667 | 3GPP TS 28.667 |
| TS 28.668 | 3GPP TS 28.668 |
| TS 28.820 | 3GPP TS 28.820 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.408 | 3GPP TR 32.408 |
| TS 32.501 | 3GPP TR 32.501 |
| TS 32.505 | 3GPP TR 32.505 |
| TS 32.506 | 3GPP TR 32.506 |
| TS 32.507 | 3GPP TR 32.507 |
| TS 33.838 | 3GPP TR 33.838 |
| TS 36.141 | 3GPP TR 36.141 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 37.145 | 3GPP TR 37.145 |
| TS 37.802 | 3GPP TR 37.802 |
| TS 37.900 | 3GPP TR 37.900 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.113 | 3GPP TR 38.113 |
| TS 38.175 | 3GPP TR 38.175 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.741 | 3GPP TR 38.741 |
| TS 38.863 | 3GPP TR 38.863 |