![](https://csdnimg.cn/release/download_crawler_static/75779492/bg11.jpg)
Your use is subject to the terms of the O-RAN Adopter License Agreement in Annex ZZZ 17
Copyright © 2021 by the O-RAN Alliance e.V.
NETCONF/YANG is used as the network element management protocol [3] and data modeling language [4]. Use of such a
standardized framework and common modeling language simplifies integration between O-DU and O-RU as well as operator
network integration (in terms of running service) in case of elements sharing a common set of capabilities. The framework
supports integration of products with differing capabilities enabled by well-defined published data models. NETCONF also
natively supports a hybrid architecture which enables multiple clients to subscribe and receive information originating at the
NETCONF server in the O-RU.
Based on the transport topology, various modes of network connectivity are possible between O-RU and O-DU and SMO.
The basic requirement for M-Plane is to have end to end IP connectivity between the O-RU and the elements managing it (O-
DU, SMO, or so called “O-RU Controllers”). The connectivity between the O-DU and SMO and its management plane are not
in scope of this specification. The O-RU shall support either IPv4 or IPv6 and optionally support dual stack (IPv4 and IPv6).
Note, in previous versions of this specification, only IPv4 was mandatory. In order to ensure backwards compatibility
with equipment supporting earlier versions of this specification, an operator and vendor can agree to use a common IP
version in the O-RU, O-DU and any other O-RU controllers.
2.1.4 M-Plane functional description
The M-Plane provides the following major functionalities to the O-RU. These features are implemented using the NETCONF
During startup, the O-RU acquires its network layer parameters either via static (pre-configured in the O-RU) or dynamically
via DHCP or DHCPv6. During this process the O-RU may acquire the IP address of the O-RU controller(s), in which case the
O-RU establishes the NETCONF connectivity using the “call home” feature. When the O-RU is operating in an environment
which include the O-RAN defined SMO, the O-RU may acquire the IP address of the event-collector(s), in which case the O-
RU performs a pnfRegistration which triggers the SMO to establish NETCONF connectivity using the information recovered
from the pnfRegistration procedure. The capability exchange is performed between the client and server as part of the initial
NETCONF Hello exchanges. Details of these steps are provided in chapter 3.
Note, the use of “start up” terminology in this specification is distinct from the “startup” capability used in a NETCONF
environment to indicate that a device supports separate running and startup configuration datastores. This specification makes
specific reference to configuration which is required to be stored in “reset persistent memory”. The O-RU shall use this stored
configuration as its “startup” configuration.
The M-Plane is responsible for software download, installation, validation and activation of new SW when requested by O-RU
Controller. The software download is triggered by NETCONF RPC procedures, and the actual software package download is
done using sFTP. In this version of the M-Plane specification, sFTP is the only defined file transfer protocol for software and
Configuration management covers various scenarios like Retrieve Resource State, Modify Resource State, Modify Parameters
and Retrieve Parameters. NETCONF get-config and edit-config RPCs shall be used for configuration parameter retrieval and
Performance management describes the measurements and counters used to collect data related to O-RU operations. The
purpose of Performance Management is optimizing the operation of the O-RU.
The measurement results are reported by two options:
1. YANG Notification: This option uses the stats definition of YANG model per measurement group. In this case, get
rpc and/or notification will be used (see Chapter 7 for more details).