Correspondent Host

Description

In the context of 3GPP and IETF standards for IP mobility, a Correspondent Host (CH) is defined as the communication peer of a Mobile Node (MN). It is any host (e.g., a server, another user device) with which the MN is exchanging IP packets. The CH is typically assumed to be a standard IP host without specific mobility support capabilities, meaning it operates using conventional IP routing mechanisms. The primary architectural role of the CH is as the destination or source of data traffic in sessions involving a mobile user. The network's mobility management protocols, such as Mobile IP (MIP) and its variants, are designed to ensure that packets are correctly routed between the MN (which may change its point of network attachment) and the CH, despite the CH's lack of inherent awareness of the MN's mobility.

The operation of a CH is passive from a mobility signaling perspective. In basic Mobile IPv4 (MIPv4) and Mobile IPv6 (MIPv6), the CH sends packets to the MN's home address (HoA). These packets are intercepted by the Home Agent (HA) in the MN's home network and tunneled to the MN's current Care-of Address (CoA). Return traffic from the MN may be sent directly to the CH (using route optimization) or reverse-tunneled via the HA. The CH itself does not participate in binding updates or mobility signaling; it simply sends and receives IP packets to/from the MN's IP address as per standard IP semantics. This design keeps the CH simple and decouples mobility support from correspondent nodes.

Key components in the interaction with a CH include the Mobile Node's Home Agent and, in optimized scenarios, a Correspondent Node (CN) function. While 'Correspondent Host' and 'Correspondent Node' are often used synonymously, some contexts distinguish them: a Correspondent Node may imply a node that is mobility-aware and can participate in route optimization signaling (like in MIPv6 Route Optimization), whereas a CH might be considered a more general, possibly mobility-unaware, peer. The CH's IP address serves as a stable session anchor point from the perspective of the MN's application layer.

In 3GPP architectures, especially for IP Multimedia Subsystem (IMS) and Packet Data Networks, the concept of the CH is crucial for understanding end-to-end service delivery. While 3GPP networks manage mobility at the link layer (e.g., handovers) and often use network-based mobility management protocols like Proxy Mobile IP (PMIP) or GPRS Tunneling Protocol (GTP), the IP session endpoint visible to the User Equipment (UE) is a CH somewhere on the Internet or a service network. The 3GPP core network's role is to provide uninterrupted IP connectivity between the UE and its various CHs, ensuring that ongoing sessions (like VoIP calls or video streams) are maintained seamlessly as the user moves.

Purpose & Motivation

The concept of the Correspondent Host exists to formally model the peer entity in mobile communications within IP networking frameworks. Before standardized IP mobility protocols, a host's IP address was tied to its physical network location. If a host moved, existing TCP/IP sessions with correspondent hosts would break because packets could no longer be routed correctly. The development of Mobile IP introduced the separation of identification (home address) and location (care-of address), creating a need to define the other party in the communication—the CH—which continues to use the stable home address.

Its creation was motivated by the need to analyze, specify, and implement mobility solutions without requiring upgrades or changes to every possible communication peer on the Internet. By defining the CH as a potentially mobility-unaware entity, protocol designers could confine mobility complexity to the mobile node and its home network (agents). This approach ensured the practical deployability of mobility solutions, as the vast installed base of Internet hosts did not need modification. The CH represents the 'rest of the Internet' in mobility scenarios.

The concept addresses the fundamental limitation of traditional IP routing, which is topologically based. It provides a clear reference point for specifying how packets should be redirected (via tunneling) and how routing optimizations can be implemented (e.g., informing the CH of the mobile's current location). In 3GPP contexts, it helps delineate responsibilities between the mobile network operator's domain (managing mobility for the UE) and the external IP world (containing the CHs), which is essential for charging, policy control, and security boundary definitions.