DSMIP

Dual Stack Mobile IP

Mobility
Introduced in Rel-8
DSMIP is a mobility management protocol that enables seamless handover for IPv4 and IPv6 dual-stack devices in 3GPP networks. It extends Mobile IP to support both IP versions simultaneously, allowing devices to maintain connectivity while moving across networks. It is crucial for transitioning to IPv6 and ensuring backward compatibility in evolving mobile infrastructures.

Description

Dual Stack Mobile IP (DSMIP) is a network-based mobility protocol standardized by 3GPP and IETF, designed to support devices that operate with both IPv4 and IPv6 addresses. It is an extension of Mobile IPv6 (MIPv6) and Mobile IPv4, enabling a UE (User Equipment) to maintain ongoing sessions while moving between different access networks, regardless of the IP version used. The architecture involves key entities: the Mobile Node (MN, i.e., the UE), the Home Agent (HA), and possibly a Foreign Agent (FA) in IPv4 contexts. DSMIP works by allowing the MN to have two care-of addresses—one for IPv4 and one for IPv6—registered with the HA. The HA then tunnels packets to the MN's current location, handling the encapsulation and decapsulation for both IP families. This dual-stack approach ensures that the MN can communicate with correspondents using either IPv4 or IPv6, with mobility transparent to upper-layer applications.

In operation, when a DSMIP-enabled UE attaches to a network, it obtains local IP addresses (care-of addresses) via mechanisms like DHCPv4 or IPv6 stateless address autoconfiguration. It then sends binding updates to its Home Agent, which maintains a binding cache associating the MN's home address(es) with its current care-of addresses. For IPv6 traffic, the HA uses IPv6-in-IPv6 tunneling; for IPv4 traffic, it uses IPv4-in-IPv4 or IPv4-in-IPv6 tunneling depending on the scenario. DSMIP also supports route optimization to reduce latency by allowing direct communication between the MN and correspondents after initial signaling. The protocol is specified in 3GPP documents like TS 33.107 and TS 33.108, focusing on security aspects and integration with 3GPP authentication frameworks.

DSMIP's role in 3GPP networks is to facilitate seamless mobility across heterogeneous access technologies (e.g., between LTE and Wi-Fi) while supporting the coexistence of IPv4 and IPv6. It integrates with 3GPP's Evolved Packet Core (EPC) through interfaces like S2a and S2b for trusted and untrusted non-3GPP access. Key components include the DSMIP client on the UE, the HA in the home network, and AAA servers for authentication. The protocol handles handovers by updating bindings during movement, minimizing packet loss and session disruption. Its importance grew with the transition to IPv6, as it allows operators to deploy IPv6 networks while maintaining legacy IPv4 services, ensuring continuity for dual-stack devices in mobile environments.

Purpose & Motivation

DSMIP was created to address the challenges of IP mobility in dual-stack environments, where networks and devices support both IPv4 and IPv6. As IPv6 adoption increased, there was a need for mobility solutions that could handle both protocols seamlessly, without requiring separate mechanisms for each IP version. Prior approaches like MIPv4 and MIPv6 operated independently, leading to complexity and inefficiency for dual-stack devices. DSMIP solves this by unifying mobility management, enabling devices to roam across networks while maintaining sessions over either IP family.

Historically, DSMIP was introduced in 3GPP Release 8 as part of the System Architecture Evolution (SAE) and Evolved Packet Core (EPC), motivated by the impending exhaustion of IPv4 addresses and the transition to IPv6. It allowed mobile operators to deploy IPv6-capable networks while ensuring backward compatibility with existing IPv4 infrastructure and devices. The protocol filled a gap by providing a standardized way to support mobility for dual-stack UEs, particularly for non-3GPP access integration (e.g., Wi-Fi offload) where IP version heterogeneity is common.

By implementing DSMIP, 3GPP aimed to facilitate smooth migration to IPv6, reduce operational costs, and enhance user experience with uninterrupted connectivity. It addresses limitations of earlier Mobile IP versions by simplifying binding management and reducing signaling overhead for dual-stack operations. This enabled features like network-based mobility management (PMIP) in conjunction with DSMIP, supporting scalable deployments in LTE and beyond. Ultimately, DSMIP played a key role in ensuring that mobility services could evolve alongside IP networking trends, supporting the long-term growth of mobile data.

Key Features

  • Supports simultaneous mobility management for IPv4 and IPv6 via dual care-of address registration
  • Integrates with 3GPP EPC for seamless handover across 3GPP and non-3GPP access networks
  • Utilizes tunneling mechanisms (e.g., IPv6-in-IPv6, IPv4-in-IPv4) for packet forwarding between Home Agent and Mobile Node
  • Includes route optimization to reduce latency by enabling direct correspondent communication
  • Incorporates security features like IPsec and 3GPP authentication for binding updates
  • Facilitates backward compatibility and smooth transition from IPv4 to IPv6 in mobile networks

Evolution Across Releases

Rel-8 Initial

Initial introduction in 3GPP as part of SAE/EPC, specified in TS 33.107 and TS 33.108. Defined DSMIP to enable dual-stack mobility for UEs, integrating with Mobile IP extensions and providing mechanisms for IPv4 and IPv6 handover support in evolving packet core architectures.

Defining Specifications

SpecificationTitle
TS 33.107 3GPP TR 33.107
TS 33.108 3GPP TR 33.108