Enhanced NETCONF access control model (NACM) operations and granular controls for shared data node management
Systems and methods for handling and/or managing permissions data nodes across multiple NETCONF clients by generating or obtaining, by a NETCONF client, a first identifier, wherein the first identifier uniquely identifies the NETCONF client, establishing a first NETCONF session between a NETCONF server and the NETCONF client, wherein the NETCONF server comprises a first O-RU, wherein the NETCONF client comprises a first O-DU, delivering, from the NETCONF client to the NETCONF server, a first request during a NETCONF session handshake comprising the first identifier, delivering, from the NETCONF client to the NETCONF server, a first edit configuration request or payload, wherein the first edit configuration request or payload comprises the first identifier.
1 . A method comprising:
generating or obtaining a first identifier, wherein the first identifier uniquely identifies a network configuration protocol (NETCONF) client;
establishing a first NETCONF session between a NETCONF server and the NETCONF client;
transmitting a first request to the NETCONF server, during a NETCONF session handshake, wherein the first request comprises the first identifier; and
transmitting a first edit configuration communication to the NETCONF server, wherein the first edit configuration communication comprises the first identifier.
2 . The method of claim 1 , further comprising:
creating one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associating the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
3 . The method of claim 2 , wherein first identifier is stored outside of the one or more data nodes or data node instances.
4 . The method of claim 2 , further comprising:
associating, with the first NETCONF session, the first identifier as metadata.
5 . The method of claim 1 , further comprising:
updating one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associating the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
6 . The method of claim 1 , further comprising:
rejecting the first edit configuration communication in response to determining that the one or more data nodes or data instances is associated with a second identifier different from the first identifier.
7 . The method of claim 1 , further comprising:
setting one or more peer permissions to access the first edit configuration communication.
8 . A system comprising:
a non-transitory computer readable medium storing instructions thereon; and
a processor connected to the non-transitory computer readable medium, wherein the instructions, when executed by the processor, cause the system to:
generate or obtain a first identifier, wherein the first identifier uniquely identifies a network configuration protocol (NETCONF) client;
establish a first NETCONF session between a NETCONF server and the NETCONF client;
transmit, by a transmitter, a first request to the NETCONF server, during a NETCONF session handshake, wherein the first request comprises the first identifier; and
transmit, by the transmitter, a first edit configuration communication to the NETCONF server, wherein the first edit configuration communication comprises the first identifier.
9 . The system of claim 8 , wherein the system is configured to:
create one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associate the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
10 . The system of claim 9 , wherein first identifier is stored outside of the one or more data nodes or data node instances.
11 . The system of claim 9 , wherein the instructions, when executed by the processor, further cause the system to:
associate, with the first NETCONF session, the first identifier as metadata.
12 . The system of claim 8 , wherein the system is configured to:
update one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associate the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
13 . The system of claim 8 , wherein the instructions, when executed by the processor, further cause the system to:
reject the first edit configuration communication in response to a determination that the one or more data nodes or data instances is associated with a second identifier different from the first identifier.
14 . The system of claim 8 , wherein the instructions, when executed by the processor, further cause the system to:
set one or more peer permissions to access the first edit configuration communication.
15 . A non-transitory computer readable medium storing instructions that when executed cause one or more processors cause a system to:
generate or obtaining a first identifier, wherein the first identifier uniquely identifies a network configuration protocol (NETCONF) client;
establish a first NETCONF session between a NETCONF server and the NETCONF client;
transmit, by a transmitter, a first request to the NETCONF server, during a NETCONF session handshake, wherein the first request comprises the first identifier; and
transmit, by the transmitter, a first edit configuration communication to the NETCONF server, wherein the first edit configuration communication comprises the first identifier.
16 . The non-transitory computer readable medium of claim 15 , wherein the instructions when executed by the one or more processors cause the system to:
create one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associate the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
17 . The non-transitory computer readable medium of claim 16 , wherein first identifier is stored outside of the one or more data nodes or data node instances.
18 . The non-transitory computer readable medium of claim 16 , the instructions when executed by the one or more processors cause the system to:
associate, with the first NETCONF session, the first identifier as metadata.
19 . The non-transitory computer readable medium of claim 15 , wherein the instructions when executed by the one or more processors cause the system to:
update one or more data nodes or data node instances in response to receiving the first edit configuration communication; and
associate the one or more data nodes or data instances with the first identifier in response to receiving the first edit configuration communication.
20 . The non-transitory computer readable medium of claim 15 , the instructions when executed by the one or more processors cause the system to:
reject the first edit configuration communication in response to determining that the one or more data nodes or data instances is associated with a second identifier different from the first identifier.