ICMP

Internet Control Message Protocol

Protocol →
Introduced in R99 Also in: Core Network

ICMP is a network-layer protocol used for diagnostic and error reporting in IP networks, enabling devices to communicate network status and supporting utilities like ping and traceroute.

Category
Protocol
Introduced
R99
Where
Services › Codecs
Also touches
1 segments
Specifications
9 specs
ICMP Description Purpose Related Classification Detected Changes Specifications

Description

The Internet Control Message Protocol (ICMP) is a supporting protocol within the Internet Protocol (IP) suite, operating at the network layer (Layer 3). It is primarily used by network devices, such as routers and hosts, to send error messages and operational information indicating, for example, that a requested service is not available or that a host or router could not be reached. ICMP messages are encapsulated within IP packets, but unlike TCP or UDP, it is not used for end-user data transmission. Common ICMP message types include Echo Request and Echo Reply (used by the ping command), Destination Unreachable, Time Exceeded (used by traceroute), and Redirect. In 3GPP networks, ICMP is relevant for IP-based communication between User Equipment (UE) and external networks, as well as within the core network for operations and maintenance. The protocol is stateless, meaning each message is processed independently, and it includes a checksum for error detection. While ICMP is fundamental for IP network functionality, 3GPP specifications often reference it in the context of interworking with external IP networks (e.g., the Internet) and for testing connectivity, but the core 3GPP protocols themselves (like GTP or Diameter) handle most control-plane signaling internally.

Purpose & Motivation

ICMP was created to provide a mechanism for IP network devices to communicate control and error information. In the early development of the Internet, the IP protocol was designed for best-effort datagram delivery without inherent mechanisms to report delivery failures or network congestion. ICMP solves this by allowing routers and destination hosts to send feedback to the source about problems encountered during packet processing, such as unreachable hosts, fragmentation needs, or routing redirects. This capability is crucial for network diagnostics, allowing administrators to identify connectivity issues, measure round-trip times, and trace network paths. In the context of 3GPP, while the mobile core network (e.g., GPRS, EPS, 5GC) uses its own set of protocols for mobility and session management, ICMP remains vital when UEs communicate with external IP networks. It ensures that IP-based applications running over 3GPP access can leverage standard Internet diagnostic tools, maintaining interoperability with the global Internet.

Classification

Part ofIP

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 5 changes

In Release 15, the changes relevant to ICMP functions were not defined within the provided grounding context, which focuses on GPRS enhancements, access stratum definitions, and bearer services. The listed Change Requests for this release, such as those concerning the GGSN control plane and user plane addresses or the 3GPP-GPRS-Negotiated-QoS-Profile AVP, pertain to core network signaling and QoS parameter updates rather than modifications to the Internet Control Message Protocol itself. Therefore, based exclusively on the given material, no new ICMP-specific introductions in Release 15 can be detailed.

  • Updates to 3GPP-GPRS-Negotiated-QoS-Profile AVP TS 29.061CR0505
  • Rate control for MO exception data TS 29.061CR0498
  • Correction to 3GPP-GPRS-Negotiated-QoS-Profile AVP TS 29.061CR0509
  • Alternative GGSN addresses for control Plane and user traffic TS 29.060CR1061
  • GGSN control plane and user plane addresses TS 29.060CR1062
Rel-17 3 changes

In Release 17, the updates to the ICMP function specifically introduced support for L2TP within both the RADIUS and Diameter message flows, as indicated by the CR titles. Furthermore, enhancements were made to provide Alternative GGSN Addresses for both Control Plane and User Traffic Information Elements. These changes provided additional flexibility and support for specific tunneling and addressing scenarios within the core network protocols.

  • Updates to support L2TP in RADIUS message flow TS 29.061CR0537
  • Updates to support L2TP in Diameter message flow TS 29.061CR0538
  • Alternative GGSN Addresses for Control Plane and User Traffic IEs TS 29.060CR1071
Rel-19 2 changes

In Release 19, the updates for the ICMP function involved upgrading to a new change control version and updating the mapping of Sh messages to HSS SBI services. These changes refined the standardized application interface and the associated application protocols used for service capability access.

  • Updating the Mapping of Sh messages to HSS SBI services TS 23.228CR1702
  • Upgrade to change control version TS 33.749

Explore further

Broader topics and technologies where ICMP plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TR 23.976 vj00 Push Service Requirements Analysis Rel-19
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19