Handling DU state information and recovery using NETCONF operational data
In general, the current subject matter relates to storing persistent data using Network Configuration Protocol (NETCONF) operational data. In some implementations, storing persistent data using NETCONF operational data can include receiving, at a NETCONF server from at least one microservice of a distributed unit (DU), state information for the at least one microservice, storing, in persistent storage of the NETCONF server, the received state information, fetching, by the at least one microservice from the NETCONF server, the stored state information, and recovering the DU to operational state based on the fetching.
1 . An apparatus, comprising:
at least one processor; and
at least one non-transitory storage media storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
receiving, at a Network Configuration Protocol (NETCONF) server from at least one microservice of a distributed unit (DU), state information for the at least one microservice,
storing, in persistent storage of the NETCONF server, the received state information,
fetching, by the at least one microservice from the NETCONF server, the received state information stored in the persistent storage of the NETCONF server; and
recovering the DU to operational state based on the fetching,
wherein the state information includes at least one of cell state information and baseband state information, wherein the cell state information specifies time synchronization information, and wherein the baseband state information specifies baseband sector and carrier signaling information, and
wherein the received state information is received on a per-microservice basis,
wherein the operations further comprise:
receiving, at the NETCONF server from the at least one microservice, at least one update to the state information for the at least one microservice, and
storing, in persistent storage of the NETCONF server, the received updated state information, and
wherein the at least one microservice fetches the state information most recently received by the NETCONF server for the purpose of recovering the DU to the operational state after a restart or a reboot.
2 . The apparatus of claim 1 , wherein the at least one microservice fetches the state information following a restart or a reboot of the DU for the purpose of recovering the DU to the operational state.
3 . The apparatus of claim 1 , wherein the NETCONF server receives the state information via an application programming interface (API) layer.
4 . The apparatus of claim 1 , wherein the operations further comprise storing, in non-persistent storage of the DU, the state information for the at least one microservice.
5 . The apparatus of claim 1 , wherein the state information further includes centralized unit control plane (CU-CP) connection information.
6 . The apparatus of claim 1 , wherein a base station includes the NETCONF server and the DU; and the base station includes a gNodeB or an eNodeB.
7 . The apparatus of claim 1 , wherein a wireless communication system base station includes the at least one processor and the at least one non-transitory storage media.
8 . At least one non-transitory storage media storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:
receiving, at a Network Configuration Protocol (NETCONF) server from at least one microservice of a distributed unit (DU), state information for the at least one microservice;
storing, in persistent storage of the NETCONF server, the received state information;
fetching, by the at least one microservice from the NETCONF server, the received state information stored in the persistent storage of the NETCONF server; and
recovering the DU to operational state based on the fetching,
wherein the state information includes at least one of cell state information and baseband state information, wherein the cell state information specifies time synchronization information, and wherein the baseband state information specifies baseband sector and carrier signaling information, and
wherein the received state information is received on a per-microservice basis,
wherein the operations further comprise:
receiving, at the NETCONF server from the at least one microservice, at least one update to the state information for the at least one microservice, and
storing, in persistent storage of the NETCONF server, the received updated state information, and
wherein the at least one microservice fetches the state information most recently received by the NETCONF server for the purpose of recovering the DU to the operational state after a restart or a reboot.
9 . The at least one non-transitory storage media of claim 8 , wherein the at least one microservice fetches the state information following a restart or a reboot of the DU for the purpose of recovering the DU to the operational state.
10 . The at least one non-transitory storage media of claim 8 , wherein the NETCONF server receives the state information via an application programming interface (API) layer.
11 . The at least one non-transitory storage media of claim 8 , wherein the operations further comprise storing, in non-persistent storage of the DU, the state information for the at least one microservice.
12 . The at least one non-transitory storage media of claim 8 , wherein the state information further includes centralized unit control plane (CU-CP) connection information.
13 . A computer-implemented method, comprising:
receiving, at a Network Configuration Protocol (NETCONF) server from at least one microservice of a distributed unit (DU), state information for the at least one microservice;
storing, in persistent storage of the NETCONF server, the received state information;
fetching, by the at least one microservice from the NETCONF server, the received state information stored in the persistent storage of the NETCONF server; and
recovering the DU to operational state based on the fetching,
wherein the state information includes at least one of cell state information and baseband state information, wherein the cell state information specifies time synchronization information, and wherein the baseband state information specifies baseband sector and carrier signaling information, and
wherein the received state information is received on a per-microservice basis,
wherein the method further comprises:
receiving, at the NETCONF server from the at least one microservice, at least one update to the state information for the at least one microservice, and
storing, in persistent storage of the NETCONF server, the received updated state information, and
wherein the at least one microservice fetches the state information most recently received by the NETCONF server for the purpose of recovering the DU to the operational state after a restart or a reboot.
14 . The method of claim 13 , wherein the at least one microservice fetches the state information following a restart or a reboot of the DU for the purpose of recovering the DU to the operational state.
15 . The method of claim 13 , wherein the NETCONF server receives the state information via an application programming interface (API) layer.
16 . The method of claim 13 , further comprising storing, in non-persistent storage of the DU, the state information for the at least one microservice.
17 . The method of claim 13 , wherein the state information further includes centralized unit control plane (CU-CP) connection information.