Network Control Protocol

Description

The Network Control Protocol (NCP) is a control plane protocol defined in early 3GPP releases, primarily for managing packet data protocol (PDP) contexts in GPRS and UMTS networks. It operates between the mobile station (MS) and the serving GPRS support node (SGSN) to establish, modify, and deactivate PDP contexts, which are essential for IP data sessions. The protocol handles signaling for session management, including negotiation of quality of service (QoS) parameters, assignment of IP addresses, and management of network resources. It is a key component of the GPRS session management (SM) layer, working in conjunction with mobility management (MM) to provide seamless data connectivity.

Architecturally, NCP is part of the protocol stack in the control plane, specifically within the session management sublayer. It uses the underlying signaling connections provided by the radio resource control (RRC) and other lower-layer protocols. The protocol defines specific message types for activation, deactivation, and modification of PDP contexts, each containing information elements that convey parameters like the requested QoS profile, access point name (APN), and protocol configuration options. These messages are exchanged during procedures such as PDP context activation, where the MS requests a data session, and the network responds with assigned resources and addresses.

In operation, when a user initiates a data session, the MS sends an Activate PDP Context Request message via NCP to the SGSN. This message includes the desired APN and QoS parameters. The SGSN then interacts with the gateway GPRS support node (GGSN) to establish a GTP tunnel and allocate an IP address. Upon successful resource allocation, the SGSN sends an Activate PDP Context Accept message back to the MS, confirming the session parameters. NCP also handles modifications, such as QoS renegotiation during a session, and deactivation when the session ends. Its role is critical for efficient resource management and ensuring that data sessions meet the required service levels.

Key components of NCP include its message set, state machines for session management, and integration with other network elements like the GGSN and HLR. The protocol supports various PDP types, including IPv4 and IPv6, and interacts with authentication and charging functions. Although later releases evolved session management mechanisms, NCP laid the groundwork for control plane signaling in packet-switched networks, influencing subsequent protocols like the EPS session management (ESM) in LTE and 5G. Its design emphasizes reliability and flexibility, enabling early mobile data services.

Purpose & Motivation

NCP was created to provide a standardized method for managing packet data sessions in 2.5G and 3G networks, specifically GPRS and UMTS. Prior to its introduction, circuit-switched networks dominated, lacking efficient mechanisms for dynamic IP session management. NCP solved the problem of establishing and controlling packet-switched connections, enabling mobile internet access by defining clear procedures for session setup, modification, and teardown. It addressed the need for QoS negotiation, allowing networks to allocate resources based on service requirements, which was crucial for differentiating between services like web browsing and video streaming.

The historical context stems from the transition to packet-switched data in the late 1990s, as mobile operators sought to offer data services beyond voice. NCP facilitated this by integrating with existing mobility management and providing a control protocol that could handle the complexities of IP-based sessions. It solved limitations of earlier approaches, which were often proprietary or lacked support for dynamic session management, by offering a standardized, interoperable solution. This enabled widespread deployment of mobile data services, paving the way for later advancements in LTE and 5G.

Motivations for NCP included the need for efficient network resource utilization, support for multiple PDP types, and seamless mobility. By defining a protocol specifically for session control, 3GPP ensured that networks could scale to handle growing data traffic while maintaining service quality. NCP's role in early mobile data ecosystems was foundational, influencing subsequent protocols and contributing to the evolution of mobile broadband.

Key Features

• Manages PDP context activation, modification, and deactivation
• Negotiates QoS parameters for data sessions
• Supports multiple PDP types including IPv4 and IPv6
• Integrates with mobility management for seamless handovers
• Defines standardized message sets for control plane signaling
• Facilitates interaction between MS, SGSN, and GGSN

Evolution Across Releases

Defining Specifications