IP Library Granted Patent US 12671628
Granted Patent B2
US 12671628 · App. 18/754,954 · Granted Jun 30, 2026

Configuration management method and apparatus, device, system, storage medium, and program product

Inventors: Chong Feng (Shenzhen, CN); Qiufang Ma (Nanjing, CN); Bo Wu (Nanjing, CN); Qin Wu (Nanjing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L41/0853G06F11/1464H04L41/0859G06F2201/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12671628
App. No.
18/754,954
Granted
Jun 30, 2026
Kind
B2
Abstract

In a configuration management process, a configuration commission request sent by a client to a server includes an identifier of a specified data source. The server, even if configuration data in a candidate configuration datastore comes from a plurality of data sources, does not commit all configuration data that comes from data sources other than the specified data source in the plurality of data sources to a running configuration datastore. That is, some configuration data that is not expected to be committed is not forced to be committed when configuration data from a data source needs to be committed.

Claims (47)

1 . A method comprising:

receiving, from a first client, a Network Configuration Protocol (NETCONF) configuration commission request comprising a first identifier of a first data source;

committing, to a running configuration datastore based on the first identifier, first configuration data that is from the first data source and that is in a candidate configuration datastore, wherein the candidate configuration datastore comprises a plurality of configuration data from a plurality of data sources, and wherein the plurality of data sources comprises the first data source;

receiving, from the first client, a NETCONF configuration update cancellation request comprising a second identifier of a second data source; and

rolling back, based on the second identifier, second configuration data that is from the second data source and that is in the candidate configuration datastore to be consistent with third configuration data that is from the second data source and that is in the running configuration datastore.

2 . The method of claim 1 , further comprising:

receiving, from the first client, a NETCONF configuration update request comprising a third identifier of a third data source and comprising third configuration data;

updating, in a target configuration datastore, the third configuration data based on the third identifier; and

recording, in the target configuration datastore, a correspondence between the first data source and the third configuration data.

3 . The method of claim 1 , further comprising:

receiving, from the first client, a NETCONF commission cancellation request comprising a third identifier of a third data source; and

canceling, based on the third identifier, a commit operation on third configuration data that is from the third data source and that is in the running configuration datastore.

4 . The method of claim 1 , further comprising:

receiving, from the first client, a NETCONF configuration copying request comprising a third identifier of a source configuration datastore, a fourth identifier of a third data source, and a fifth identifier of a target storage object; and

copying, to the target storage object based on the third identifier, the fourth identifier, and the fifth identifier, third configuration data that is from the third data source and that is in the source configuration datastore.

5 . The method of claim 4 , wherein the target storage object comprises a target configuration datastore or a target file.

6 . The method of claim 1 , further comprising:

receiving, from the first client, a NETCONF backup creation request comprising a third identifier of a third data source; and

backing up, based on the third identifier, third configuration data that is from the third data source and that is in a source configuration datastore to generate backup configuration data.

7 . An apparatus comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to cause the apparatus to:

receive, from a first client, a Network Configuration Protocol (NETCONF) configuration commission request comprising a first identifier of a first data source;

commit, to a running configuration datastore based on the first identifier, first configuration data that is from the first data source and that is in a candidate configuration datastore, wherein the candidate configuration datastore comprises a plurality of configuration data from a plurality of data sources, and wherein the plurality of data sources comprises the first data source;

receive, from the first client, a NETCONF configuration update cancellation request comprising a second identifier of a second data source; and

roll back, based on the second identifier, second configuration data that is from the second data source and that is in the candidate configuration datastore to be consistent with third configuration data that is from the second data source and that is in the running configuration datastore.

8 . The apparatus of claim 7 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to:

receive, from the first client, a NETCONF configuration update request comprising a third identifier of a third data source and comprising third configuration data;

update, in a target configuration datastore, the third configuration data based on the third identifier; and

record, in the target configuration datastore, a correspondence between the first data source and the third configuration data.

9 . The apparatus of claim 7 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to:

receive, from the first client, a NETCONF commission cancellation request comprising a third identifier of a third data source; and

cancel, based on the third identifier, a commit operation on third configuration data that is from the third data source and that is in the running configuration datastore.

10 . The apparatus of claim 7 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to:

receive, from the first client, a NETCONF configuration copying request comprising a third identifier of a source configuration datastore, a fourth identifier of a third data source, and a fifth identifier of a target storage object; and

copy, to the target storage object based on the third identifier, the fourth identifier, and the fifth identifier, third configuration data that is from the third data source and that is in the source configuration datastore.

11 . The apparatus of claim 10 , wherein the target storage object comprises a target configuration datastore or a target file.

12 . An apparatus comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to cause the apparatus to:

send, to a server, a network configuration protocol (NETCONF) configuration commission request comprising a first identifier of a first data source, wherein the NETCONF configuration commission request indicates to the server to commit, based on the first identifier, first configuration data that is from the first data source and that is in a candidate configuration datastore to a running configuration datastore, wherein the candidate configuration datastore comprises a plurality of configuration data from a plurality of data sources, and wherein the plurality of data sources comprises the first data source; and

send, to the server, a NETCONF configuration update cancellation request comprising a second identifier of a second data source, wherein the NETCONF configuration update cancellation request indicates to the server to roll back, based on the second identifier, second configuration data that is from the second data source and that is in the candidate configuration datastore to be consistent with third configuration data that is from the second data source and that is in the running configuration datastore.

13 . The apparatus of claim 12 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to send, to the server, a NETCONF configuration update request comprising a third identifier of a third data source and comprising third configuration data; and wherein the NETCONF configuration update request indicates to the server to update the third configuration data in a first target configuration datastore based on the third identifier, and to record, in the first target configuration datastore, a correspondence between the first data source and the third configuration data.

14 . The apparatus of claim 12 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to send, to the server, a NETCONF commission cancellation request comprising a third identifier of a third data source, wherein the NETCONF commission cancellation request indicates to the server to cancel, based on the third identifier, a commit operation on third configuration data that is from the third data source and that is in the running configuration datastore.

15 . The apparatus of claim 12 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to send, to the server, a NETCONF configuration copying request comprising a third identifier of a source configuration datastore, a fourth identifier of a third data source, and a fifth identifier of a target storage object, wherein the NETCONF configuration copying request indicates to the server to copy, to the target storage object based on the third identifier, the fourth identifier, and the fifth identifier, third configuration data that is from the third data source and that is in the source configuration datastore.

16 . The apparatus of claim 15 , wherein the target storage object comprises a target configuration datastore or a target file.

17 . The apparatus of claim 12 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to send, to the server, a NETCONF backup creation request comprising a third identifier of a third data source, wherein the NETCONF backup creation request indicates to the server to back up, based on the third identifier, third configuration data that is from the third data source and that is in a source configuration datastore to generate backup configuration data.