Description
The Session Border Controller (SBC) is a critical component in IP-based multimedia networks, particularly in the context of 3GPP's IP Multimedia Subsystem (IMS) and VoLTE architectures. It acts as a border element between different network domains, such as between the access network and the core network, or between different operator networks. The SBC is responsible for controlling the signaling and media streams that traverse these borders, ensuring security, policy enforcement, and interoperability.
Architecturally, the SBC sits at the edge of the IMS core network, typically interfacing with the P-CSCF (Proxy Call Session Control Function) on the core side and the access network (e.g., E-UTRAN, WLAN) on the other. It may also interconnect with other operators' networks via the NNI (Network-to-Network Interface). The SBC handles both signaling (SIP) and media (RTP/RTCP) planes. On the signaling side, it performs functions such as SIP message normalization, topology hiding, and protocol interworking. On the media side, it manages media relay, transcoding, and QoS marking.
Key functions of the SBC include security (e.g., preventing DoS attacks, enforcing access control lists, and encrypting signaling and media), policy enforcement (e.g., applying QoS policies, bandwidth management, and charging), and interoperability (e.g., handling differences in SIP implementations, codec negotiation, and NAT traversal). The SBC also plays a vital role in emergency services, lawful interception, and regulatory compliance.
In 3GPP specifications, the SBC is not always defined as a standalone entity but is often referenced in the context of the IMS architecture. For example, 3GPP TS 23.700 series provides study results on SBC-related topics, while TS 24.802 specifies the protocol procedures for the SBC in the context of the IMS. The SBC is typically deployed as a physical or virtual network function and can be integrated with other IMS elements.
The SBC has evolved with the advent of 5G and network slicing, where it may be deployed as a virtualized function to support flexible and scalable deployments. It also plays a role in interworking between 5G and legacy networks, ensuring seamless service continuity.
Purpose & Motivation
The SBC exists to solve the challenges of interconnecting IP-based multimedia networks across different domains and operators. Before the SBC, networks faced issues such as security vulnerabilities (e.g., SIP-based attacks), lack of policy control, and interoperability problems between different vendor implementations. The SBC provides a centralized point for enforcing security policies, managing media streams, and ensuring that sessions can be established and maintained across heterogeneous networks.
Historically, the need for SBCs arose with the migration from circuit-switched to packet-switched networks, where voice and video services began to be carried over IP. The IMS architecture, defined by 3GPP, introduced the SBC as a border element to handle the complexities of SIP signaling and media traversal across NATs and firewalls. The SBC also addresses regulatory requirements, such as lawful interception and emergency call handling.
In the context of 5G, the SBC continues to be relevant for VoNR (Voice over New Radio) and for interworking with legacy networks. It enables operators to enforce QoS, manage bandwidth, and provide a consistent user experience across different access technologies.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference SBC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 24.802 vc10 | II-NNI Traversal Scenario Determination | Rel-12 read |