Description
Plug and Connect is a management procedure introduced in 3GPP Release 19, specified in TS 28.314 and TS 32.501. It defines how a network element (NE), such as an eNodeB or gNodeB, acquires basic connectivity information after it is powered up and connected to its Element Manager (EM) system in a multi-vendor environment. This procedure is a key component of the broader Multi-Vendor Plug and Play (MV PnP) framework, which aims to simplify the deployment and integration of network elements from different vendors into a mobile network.
The Plug and Connect procedure addresses the initial phase of NE deployment, where the NE has no pre-configured parameters and needs to discover and connect to its management system. Upon power-up, the NE typically has only a default configuration, such as a pre-provisioned IP address or a DHCP client that can obtain an IP address. The NE then uses discovery mechanisms to locate its EM system. This may involve DNS queries, DHCP options, or broadcast/multicast discovery protocols. Once the EM system is discovered, the NE establishes a connection, often using NETCONF or other management protocols, and authenticates itself. The EM system then provides the NE with basic connectivity information, such as the IP address of the core network, security credentials, and other parameters necessary for the NE to become operational.
The procedure is designed to be vendor-agnostic, allowing NEs from different vendors to interoperate with a multi-vendor EM system. This is achieved through standardized data models and protocols, such as those defined in 3GPP TS 28.314, which specifies the management services and procedures for plug-and-connect. TS 32.501 provides the overall management architecture and requirements for plug-and-play.
In a multi-vendor environment, the Plug and Connect procedure must handle the heterogeneity of NEs and EMs. It ensures that the NE can be authenticated and authorized by the EM system, and that the necessary configuration data is exchanged securely. The procedure also includes error handling and fallback mechanisms, such as retrying discovery or using alternative management endpoints.
The Plug and Connect procedure is part of the larger Multi-Vendor Plug and Play (MV PnP) initiative, which aims to reduce the operational effort and cost of integrating new NEs into a network. By automating the initial configuration, it minimizes manual intervention and reduces the risk of human error. It also enables faster deployment of new sites, which is critical for 5G network rollouts.
In Release 20, the definition was revised to generalize the NE to any network element (not just eNodeB) and to refer to the management system rather than EM system. This reflects the evolution towards a more generic and cloud-native management framework, where the management system may be a Service Management and Orchestration (SMO) framework or a Network Management System (NMS) that manages multiple NEs.
Overall, Plug and Connect is a foundational procedure for automated network element onboarding, enabling efficient and scalable deployment of multi-vendor networks.
Purpose & Motivation
The Plug and Connect procedure was created to solve the problem of manual configuration and integration of network elements in multi-vendor environments. Traditionally, when a new base station was deployed, engineers had to manually configure its connectivity parameters, which was time-consuming, error-prone, and required specialized knowledge of each vendor's equipment. As networks evolved to include multiple vendors, the complexity increased, leading to higher operational costs and longer deployment times.
The Multi-Vendor Plug and Play (MV PnP) initiative, of which Plug and Connect is a part, was motivated by the need to automate the onboarding process. The goal was to allow a network element to be simply powered on and connected to the network, after which it would automatically discover and connect to its management system, obtain the necessary configuration, and become operational. This reduces the need for manual intervention, speeds up deployment, and lowers costs.
Plug and Connect specifically addresses the initial connectivity phase. It provides a standardized way for NEs to obtain basic connectivity information, such as IP addresses and security credentials, from the management system. This is essential for the NE to establish a management connection and proceed with further configuration. The procedure is designed to work across different vendors, ensuring interoperability and reducing the integration burden.
The introduction of Plug and Connect in Release 19 aligns with the industry trend towards automation and zero-touch provisioning in 5G networks. It enables operators to deploy network elements more rapidly and efficiently, which is crucial for meeting the demands of 5G services. The revision in Release 20 to generalize the definition reflects the ongoing evolution towards more flexible and cloud-native management architectures.
What changed in its specifications
The latest release-to-release comparison of specifications that define Plug and Connect. Each summary describes the whole specification, not only this term.
Management of IAB nodes, including IP configuration, location notifications, and connectivity requirements.
Full comparison in TS 28.314 →Rel-12 added eNB Plug and Play/Connect procedures, network connection scenarios, certificate acquisition details, and related terms and abbreviations.
Full comparison in TS 32.501 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced: 'The procedure by which an eNodeB gets basic connectivity information after it is powered up and gets connected to its EM system in a multi-vendor environment. Multi-vendor Plug and Connect is part of the Multi-Vendor Plug and Play.' This focused on eNodeB and EM system, establishing the procedure for multi-vendor environments.
The definition was revised to generalize the network element from eNodeB to any NE and the management system from EM system to management system. The new wording is: 'The procedure by which a NE gets basic connectivity information after it is powered up and gets connected to its management system.' This reflects a broader applicability to various network elements and modern management architectures.
Defining Specifications
3GPP specifications that define or reference Plug and Connect, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.314 vk10 | Plug and Connect Concepts and Requirements | Rel-20 read |
| TS 32.501 vj00 | Self-Configuration of Network Elements Concepts | Rel-19 read |