10 UTRAN O&M Requirements

25.4013GPPRelease 17TSUTRAN overall description

10.1 O&M of Node B

The O&M of Node B is separated in two parts: the O&M linked to the actual implementation of Node B, denoted as Implementation Specific O&M, and the O&M which impacts on the traffic carrying resources in Node B controlled from the RNC, denoted logical O&M. The RNS architecture with the O&M interfaces is shown in figure 9.

Figure 9: RNS architecture with O&M interfaces

NOTE 1: The concept of an interface from the RNC to the management system is shown for clarity only. It’s definition is outside the scope of 3GPP-TSG-RAN-WG3.

NOTE 2: The presentation of the O&M functions within the management system is shown for clarity only. Their actual implementation is outside the scope of 3GPP-TSG-RAN-WG3.

NOTE 3: The standardisation of the Implementation Specific O&M is outside the scope of 3GPP-TSG-RAN-WG3. The 3GPP-TSG-RAN-WG3 should only address the bearer for the Implementation Specific O&M.

NOTE 4: The figure shows only logical connections and does not intend to mandate any physical interfaces.

NOTE 5: The Iuant interface to the control unit of the RET antennas or TMAs is specified in the series of Technical Specifications 25.460 [24], 25.461 [25], 25.462 [26] and 25.466 [32]. An Implementation Specific O&M function is needed for the RET antennas or TMAs control to translate the control signalling from the Node B Element Manager into the control commands of the Iuant interface specified in TS 25.460 [24].

10.1.1 Implementation Specific O&M

The Implementation Specific O&M functions are heavily dependent on the implementation of Node B, both for its hardware components and for the management of the software components. It needs therefore to be implementation dependent, and be performed between Node B and the management system.

One solution for the transport of Implementation Specific O&M is to route from Node B to the management system via the RNC. In this case, the Implementation Specific O&M interface and Iub interface share the same physical bearer, and TS 25.442 [4] specifies the routing function and the transport bearer for this scenario. The deployment of the routing across the RNC in the UTRAN is optional. Where signalling between co-located equipment and its management system is required, this may be carried over the same bearer as Implementation Specific O&M.

10.1.2 Logical O&M

Logical O&M is the signalling associated with the control of logical resources (channels, cells,…) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP.

10.2 O&M of RNC

10.2.1 O&M requirements

The O&M of an RNC shall, if supported, configure the UTRAN with reporting criteria for the Traffic Volume for RAN Sharing function. The O&M may configure the UTRAN to collect and report volume reports on a per cell basis.