Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Full ICE

Full Interactive Connectivity Establishment

Services →

Full ICE is the complete implementation of the Interactive Connectivity Establishment protocol used in 3GPP networks to enable NAT traversal for real-time communications.

Introduced
Rel-12
Where
Core Network › Evolved Packet Core
Specifications
6 specs
Full ICE Description Purpose What changed Neighbours Specifications

Description

Full ICE (Interactive Connectivity Establishment) is a term used in 3GPP specifications to denote the full implementation of the ICE protocol as defined by the IETF. ICE is a protocol for NAT (Network Address Translation) traversal, allowing two endpoints to establish a direct media path even when they are behind NATs or firewalls. In 3GPP networks, Full ICE is used in the context of IP Multimedia Subsystem (IMS) and other real-time communication services, such as VoLTE and VoWiFi. The term distinguishes the complete ICE implementation from other simplified or partial implementations that may be used in certain scenarios.

ICE works by gathering candidate transport addresses from each endpoint. These candidates include host addresses (local IP addresses), server-reflexive addresses (obtained via STUN servers), and relayed addresses (obtained via TURN servers). The endpoints exchange these candidates through a signaling protocol (e.g., SIP) and then perform connectivity checks to determine which candidate pairs can be used for communication. The checks involve sending STUN binding requests and responses, and the endpoints prioritize pairs based on their type and other criteria. The selected pair is then used for media transport.

Full ICE implies that the endpoint supports all aspects of the ICE protocol, including the gathering of all candidate types, the full connectivity check procedure, and the nomination and selection of candidate pairs. This is in contrast to partial implementations that might only support a subset of candidates or simplified procedures. In 3GPP, Full ICE is specified in documents such as TS 23.333, TS 23.334, TS 29.162, TS 29.163, TS 29.235, and TS 29.292, which cover IMS, MMTel, and other services.

The need for Full ICE arises from the prevalence of NATs in both fixed and mobile networks. Without ICE, establishing a direct media path between two endpoints behind NATs is often impossible, leading to failed calls or the need for media relay through a TURN server. While TURN relay is a fallback, it adds latency and consumes server resources. Full ICE maximizes the chance of establishing a direct path, improving quality of experience and reducing operational costs.

In 3GPP networks, Full ICE is typically implemented in the UE and in IMS core network elements such as the P-CSCF and IMS-ALG. The UE gathers candidates and performs connectivity checks, while the network may assist by providing STUN/TURN servers. The use of Full ICE is particularly important for VoLTE and VoWiFi, where seamless handover and high-quality voice are expected. The protocol has evolved from RFC 5245 to RFC 8445, which clarifies and updates the original specification. 3GPP specifications have been updated accordingly, with Rel-17 and later referencing RFC 8445.

Overall, Full ICE is a critical enabler for reliable real-time communications in 3GPP networks, ensuring that media can traverse NATs and firewalls efficiently and securely.

Purpose & Motivation

Full ICE exists to solve the problem of establishing direct media paths between endpoints that are behind NATs or firewalls. In the early days of VoIP, NAT traversal was a major challenge, often requiring media to be relayed through a central server, which added latency and cost. The IETF developed ICE as a standardized solution, and 3GPP adopted it for IMS-based services. Full ICE ensures that endpoints implement the complete protocol, maximizing the chances of a direct connection and providing a consistent user experience.

The motivation for Full ICE in 3GPP was to support VoLTE and other real-time services over mobile networks, where UEs are often behind operator NATs. By mandating Full ICE, 3GPP ensures interoperability and reliable NAT traversal across different vendors and network configurations. It also aligns with the IETF's evolution from RFC 5245 to RFC 8445, which improved the protocol's efficiency and clarity. Full ICE remains a cornerstone of 3GPP's real-time communication architecture, enabling high-quality voice and video over IP.

What changed in its specifications

The latest release-to-release comparison of specifications that define Full ICE. Each summary describes the whole specification, not only this term.

TS 23.333Rel-17 → Rel-18

EVS Codec Extension for Immersive Voice and Audio Services adds handling procedures and references for the IVAS speech codec.

Full comparison in TS 23.333 →
TS 23.334Rel-17 → Rel-18

Rel-18 adds IVAS codec handling clauses, references to IVAS specifications, a definition, and modifies EVS max-red parameter selection.

Full comparison in TS 23.334 →

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.

Rel-12 Initial

Initial definition introduced in 3GPP specifications: The full implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245. This established Full ICE as a requirement for NAT traversal in IMS-based services.

Definition carried over unchanged from Rel-12. Full ICE continued to be referenced in IMS and MMTel specifications.

Definition carried over unchanged. The concept remained stable as VoLTE and VoWiFi deployments expanded.

Definition carried over unchanged. Full ICE continued to be a key enabler for real-time communications in 5G networks.

Definition carried over unchanged. The protocol reference remained RFC 5245 during this release.

The definition was updated to reference IETF RFC 8445 instead of RFC 5245. This change reflects the IETF's revision of the ICE protocol, which obsoleted RFC 5245 and introduced clarifications and improvements. The core meaning of Full ICE remained the same: the full implementation of ICE.

Definition carried over unchanged from Rel-17, continuing to reference RFC 8445. Full ICE remained a requirement for NAT traversal in 3GPP services.

Definition carried over unchanged from Rel-18, with the reference to RFC 8445. The term continues to be used in the context of IMS and real-time communications.

Defining Specifications

3GPP specifications that define or reference Full ICE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.333 vj00 MRFC-MRFP Mp Interface Requirements Rel-19 read
TS 23.334 vj00 IMS-ALG to IMS-AGW Interface (Iq) Stage 2 Rel-19 read
TS 29.162 vj00 IMS-IP Network Interworking Rel-19 read
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19 read
TS 29.235 vj00 SIP-I CS Core Network Interworking Rel-19 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read