Description
Radio Planning Tool Access (RPTA) specifies the standardized mechanisms for interoperability between a Radio Planning Tool (RPT) and external systems, primarily the Network Management System (NMS), as defined in 3GPP TS 28.667 and TS 28.668. RPTA is not a tool itself but defines the access framework, including reference points, data models, and procedures. Architecturally, it establishes an interface (often based on web services/APIs) through which the RPT can pull necessary input data from the NMS and push its planning results back. Key data retrieved via RPTA includes live or historical network performance measurements (PM data), configuration management (CM) data of existing network elements, fault management (FM) data, and inventory information. This live data feed allows the RPT to perform realistic 'what-if' analysis and optimization based on the actual network state rather than just theoretical models. Conversely, the RPT can upload its output, such as a list of recommended new cell sites, antenna parameter changes, or frequency plans, to the NMS. The NMS can then use these recommendations to generate network configuration scripts or work orders for implementation. The RPTA framework ensures data consistency, security (authentication and authorization), and semantic understanding between the planning tool and the management system, which may be from different vendors. It is a critical enabler for closed-loop automation in network lifecycle management.
Purpose & Motivation
RPTA was created to solve the problem of data silos and manual, error-prone data transfer between network planning and network operations domains. Historically, planning teams used standalone tools with static inputs, while operations teams managed the live network via the NMS. Reconciling planning assumptions with ground truth was difficult. RPTA bridges this gap by providing a standardized, automated data pipeline. Its primary purpose is to improve the accuracy and relevance of network planning by basing it on real operational data (e.g., actual traffic hotspots, measured interference). Furthermore, it streamlines the deployment process by allowing planning outputs to be directly ingested by the NMS for automated configuration, reducing the time from design to implementation. The specification in Release 12 was motivated by the industry drive towards more integrated and automated network management, a key aspect of 3GPP's Self-Organizing Networks (SON) vision, where planning, deployment, optimization, and healing are closely coupled processes.
Key Features
- Standardized interface for RPT-NMS interoperability
- Secure data exchange protocols and authentication mechanisms
- Information model for planning-relevant PM, CM, FM, and inventory data
- Support for both data query (pull) and result upload (push) operations
- Enables model tuning and calibration using live network measurements
- Facilitates automated provisioning based on planning recommendations
Evolution Across Releases
RPTA was initially standardized alongside the RPT framework in Release 12. The initial specification defined the reference point (e.g., Rp) between the RPT and the NMS, the basic service operations for data exchange, and the core information objects needed to support radio network planning activities, laying the foundation for integrated planning and operations.
Defining Specifications
| Specification | Title |
|---|---|
| TS 28.667 | 3GPP TS 28.667 |
| TS 28.668 | 3GPP TS 28.668 |