Why 5G needs NETCONF system (2)

Due to the complex configuration of traditional CLI and SNM and the lack of support for transaction mechanism, the NETCONF network management protocol is enabled in the 5G system, allowing NMS (network management system) to issue, modify and delete the configuration of network devices connected to routers, eNodeB, gNodeB, DU, CU or RU. The working principle, structure and service session are as follows;

I. Working principle The NETCONF system contains at least one NMS that manages all network devices, as shown in the figure below. The NETCONF architecture contains two roles: client and server

II. System structure characteristics NETCONF contains at least one NMS that manages all network devices, including:

2.1 The client provides the following functions

• Use NETCONF to manage network devices.
• Send RPC requests to the NETCONF server to query or modify one or more parameter values.
• According to the alarms and events sent by the NETCONF server of the managed device, understand the status of the managed device.

2.2 When the server receives a request from the client, it will parse the request and send a reply to the client. When a managed device experiences a fault or other type of event, the NETCONF server reports the alarm or event to the client through a notification mechanism, allowing the client to understand the status of the managed device.

III. NETCONF Session: As shown in the figure below, the client and server communicate using the RPC mechanism. Communication is allowed only after a secure connection-oriented session is established between them. The client sends an RPC request to the server, which processes the request and returns a response to the client. The NETCONF client and server communicate using the RPC mechanism. Communication is allowed only after a secure connection-oriented session is established. The session establishment and termination process is as follows:

• The client establishes an SSH connection with the server and, after completing authentication and authorization, establishes a NETCONF session with the server.
• The client and server exchange Hello messages to negotiate capabilities.
• The client sends one or more RPC requests to the server. Some example requests are listed below:
•  Modify and commit the configuration;
•  Query configuration data or status;
•  Perform maintenance operations on the device;
•  The client terminates the NETCONF session;
•  The SSH connection terminates.