GIP

Generic IP access

Core Network
Introduced in Rel-8
A standardized mechanism in the IP Multimedia Subsystem (IMS) that allows user equipment to obtain IP connectivity for IMS services via any IP-capable access network, such as WLAN or fixed broadband. It decouples IMS service delivery from the underlying 3GPP packet-switched domain.

Description

Generic IP access (GIP) is a concept and architectural principle within the 3GPP IP Multimedia Subsystem (IMS) defined in specifications such as TS 26.114 (Multimedia telephony; Media handling and interaction). It refers to the capability of IMS to provide multimedia services over any IP-based access network, not exclusively over the 3GPP-defined Packet-Switched (PS) domains like GPRS, UMTS, or LTE. The core idea is that the IMS core network (comprising CSCFs, HSS, etc.) is access-agnostic; it provides services as long as the User Equipment (UE) has an IP connection that can reach the IMS network, regardless of how that IP connection is established. This could be via a 3GPP mobile network, a Wi-Fi network (as defined in IMS over WLAN), a fixed broadband connection, or even other wireless technologies.

Architecturally, GIP is enabled by the IMS's design, which uses SIP (Session Initiation Protocol) over IP as its core signaling protocol. The P-CSCF (Proxy-Call Session Control Function) is the entry point to the IMS and can be discovered by the UE via DHCP or other mechanisms specific to the access network. For a UE using generic IP access (e.g., a laptop on a home Wi-Fi network), it must first obtain a local IP address from the access network (e.g., via DHCP). It then performs P-CSCF discovery, which for non-3GPP access may involve using a Fully Qualified Domain Name (FQDN) configured in the device or provided by the access network. Once the P-CSCF is contacted, standard IMS registration and session establishment procedures (using SIP REGISTER and INVITE) proceed over this generic IP transport. The media for the service (voice, video) is also carried over IP via RTP/RTCP, routed through the IMS media functions as needed.

Key components that interact in a GIP scenario include the UE's IMS client, the access network's IP infrastructure (router, DHCP server), the P-CSCF, and the IMS core. Security is a critical aspect; when using untrusted non-3GPP access (like public Wi-Fi), the UE must establish an IPsec security association with the IMS network, typically terminated at a Security Gateway (SEG) or the P-CSCF itself, as per IMS specifications for untrusted access. The role of GIP is fundamental to the convergence vision of IMS, allowing it to be the common service delivery platform for fixed-mobile convergence (FMC), enabling services like Voice over Wi-Fi (VoWiFi) and seamless service continuity as users move between different types of IP networks. It abstracts the access layer, allowing service logic to be applied uniformly.

Purpose & Motivation

Generic IP access was conceived to break the tight coupling between advanced multimedia services and the 3GPP mobile radio access network. Before IMS and GIP, value-added services were often siloed within specific access technologies (e.g., circuit-switched voice on GSM, packet data on GPRS). The goal of IMS was to create a single, reusable service layer for real-time multimedia. GIP was the architectural answer to the question: "How can we deliver these IMS services if the user is not connected via a 3GPP network?" It solved the problem of access independence, which was crucial for fixed-mobile convergence and for leveraging the ubiquity of IP networks like residential broadband and public Wi-Fi.

The historical context is the mid-2000s push towards All-IP networks and the competition from over-the-top (OTT) VoIP services that could run on any internet connection. 3GPP needed a strategy to make its standardized telephony and messaging services competitive by also being available on any network. GIP, standardized starting in Rel-8 as part of the mature IMS architecture, addressed the limitation of earlier attempts that were access-specific. It allowed operators to deploy IMS once and offer services across their mobile, fixed, and Wi-Fi footprints, creating a unified user experience. This was a key motivator for operators to invest in IMS, as it future-proofed their service platform against access technology evolution and enabled new business models like offering home-zone calling over broadband.

Key Features

  • Enables IMS service access over any IP network (3GPP and non-3GPP)
  • Utilizes standard IETF protocols (SIP, RTP, IPsec) over the generic IP transport
  • Requires access-specific procedures for IP address allocation and P-CSCF discovery
  • Supports security mechanisms for both trusted and untrusted access networks
  • Fundamental for Fixed-Mobile Convergence (FMC) and IMS over Wi-Fi
  • Access-agnostic service logic in the IMS core (CSCF, HSS, AS)

Evolution Across Releases

Rel-8 Initial

Formally defined as a core principle of the IMS architecture, enabling access independence. Specifications detailed the procedures for IMS registration and session control over generic IP connectivity, including P-CSCF discovery mechanisms for non-3GPP access and the requisite security framework (e.g., IMS Authentication and Key Agreement adapted for IP access).

Defining Specifications

SpecificationTitle
TS 26.114 3GPP TS 26.114