The initial planning of radio parameters is typically done with specialized tools called Radio Planning Tools (RPTs). RPTs generate throughput and capacity estimations as well as predictions for coverage and interference maps. RPTs utilize site and antenna (equipment) information, as well as geographic data (e.g. terrain data, type of land usage, building data and road data). This data has to be entered into the tools.
In order to improve the initial network planning, planned site and antenna data are adjusted until the estimated system performance meets the requirements within the given deployment constraints.
Information about the sites and antennas is needed also by other applications, like SON applications or CM applications on NM level. For this reason it is beneficial if this data can be read via standardized interfaces.
In contrast to configuration information it is normally not possible to read this data from the network elements.
The only place where this data is available in many deployment scenarios is in the RPT. Though this data represents initial planning, site data and antenna data are not likely to be changed very often, so that there is a fair chance that the data stored by the RPT represents also the actual situation in the network.
For this reason it is beneficial to have a read access to site and antenna data stored by the RPT.
It is to be noted that this TS series is only about the read access to site and antenna data. It is not concerned with any other functionality the RPT might have, nor with how the read data is used, nor if the read data represents the actual information about the network or if the data is outdated. Reading of site and antenna data stored by the RPT is hence the only use case in scope.
The RPT is a kind of NMLS (see TS 32.101
The RPT offers a capability allowing read access to site and antenna data. The RPT is a Service Provider (SP) and the NM a Service Consumer (SC). The RPTA IRP specifies the information model exposed by the RPT, and the operations to access it.