IP Library Granted Patent US 12,470,461
Granted Patent B2
US 12,470,461 · App. 18/338,546 · Granted Nov 11, 2025

Method and apparatus for configuring node

Inventors: Rui Chen (Dongguan, CN); Tushou Xie (Beijing, CN); Yin Jia (Dongguan, CN)
Assignee: Huawei Technologies Co., Ltd.
H04L41/0869H04L41/084
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 12,470,461
App. No.
18/338,546
Granted
Nov 11, 2025
Kind
B2
Abstract

In a method, after receiving a packet including first information, a server validates a configuration for a data node in a storage location identified by the first information. When the configuration for the data node fails to pass the validation, if the packet includes a first parameter, the server enables, based on the first parameter, a mode of outputting configuration information, and outputs recommended configuration information.

Claims (48)

1 . A method, applied to a server, the method comprising:

obtaining a first packet, wherein the first packet comprises first information and a first parameter, the first information identifies a storage location of a configuration for a first data node, and the first parameter identifies a mode of outputting configuration information to be enabled when a first preset condition is satisfied;

attempting to validate the configuration for the first data node based on the first information, to obtain a validation result; and

outputting, based on the first parameter, the configuration information when the validation result satisfies the first preset condition, comprising:

in response to the configuration for the first data node failing to pass validation, parsing a reason why the configuration fails to pass validation, and outputting configuration information comprising recommended configuration information, wherein the recommended configuration information is constructed based on error types indicated by the reason why the configuration fails to pass validation.

2 . The method according to claim 1 , wherein parsing the reason why the configuration fails to pass validation, and outputting the configuration information comprising the recommended configuration information comprises:

obtaining a first result based on a logical relationship between the first data node and a second data node comprised in a data structure to which the first data node belongs, wherein the first result comprises the reason why the configuration fails to pass the validation; and

outputting the configuration information based on the first result.

3 . The method according to claim 2 , wherein the configuration for the first data node comprises an instruction to delete the first data node, and the logical relationship comprises that the second data node references the first data node; and

wherein obtaining the first result based on the logical relationship between the first data node and the second data node comprised in the data structure to which the first data node belongs comprises:

when the second data node is created, obtaining, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the second data node lacks the first data node to be referenced.

4 . The method according to claim 3 , wherein the recommended configuration information comprises an instruction to delete the second data node.

5 . The method according to claim 2 , wherein the configuration for the first data node comprises an instruction to create the first data node, and the logical relationship comprises that the first data node references the second data node; and

wherein obtaining the first result based on the logical relationship between the first data node and the second data node comprised in the data structure to which the first data node belongs comprises:

when the second data node is not created, obtaining, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the first data node lacks the second data node to be referenced.

6 . The method according to claim 5 , wherein the recommended configuration information comprises an instruction to create the second data node.

7 . The method according to claim 2 , wherein the configuration for the first data node comprises an instruction to create the first data node, and the logical relationship comprises that the first data node and the second data node co-exist; and

wherein obtaining the first result based on the logical relationship between the first data node and the second data node comprised in the data structure to which the first data node belongs comprises:

when the second data node is not created, obtaining, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the second data node is missing.

8 . The method according to claim 7 , wherein the recommended configuration information comprises an instruction to create the second data node.

9 . The method according to claim 2 , wherein the configuration for the first data node comprises an instruction to configure a parameter value of the first data node as a first configuration parameter value, and the logical relationship comprises that the second data node is valid when the parameter value of the first data node satisfies a second preset condition; and

wherein obtaining the first result based on the logical relationship between the first data node and the second data node comprised in the data structure to which the first data node belongs comprises:

when the first configuration parameter value does not satisfy the second preset condition, obtaining, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the parameter value of the first data node does not satisfy the second preset condition.

10 . The method according to claim 9 , wherein the recommended configuration information comprises:

an instruction to configure the parameter value of the first data node to satisfy the second preset condition.

11 . An apparatus, comprising:

a memory storing instructions; and

at least one processor coupled to the memory and configured to execute the instructions, wherein the instructions comprise instructions to:

obtain a first packet, wherein the first packet comprises first information and a first parameter, the first information identifies a storage location of a configuration for a first data node, and the first parameter identifies a mode of outputting configuration information to be enabled when a first preset condition is satisfied;

attempt to validate the configuration for the first data node based on the first information, to obtain a validation result; and

output, based on the first parameter, the configuration information when the validation result satisfies the first preset condition, comprising:

in response to the configuration for the first data node failing to pass validation, parsing a reason why the configuration fails to pass validation, and outputting configuration information comprising recommended configuration information, wherein the recommended configuration information is constructed based on error types indicated by the reason why the configuration fails to pass validation.

12 . The apparatus according to claim 11 , wherein the instructions further comprise instructions to:

obtain a first result based on a logical relationship between the first data node and a second data node comprised in a data structure to which the first data node belongs, wherein the first result comprises a reason why the configuration fails to pass the validation; and

output the configuration information based on the first result.

13 . The apparatus according to claim 12 , wherein the configuration for the first data node comprises an instruction to delete the first data node, and the logical relationship comprises that the second data node references the first data node; and the instructions further include instructions to:

when the second data node is created, obtain, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the second data node lacks the first data node to be referenced.

14 . The apparatus according to claim 13 , wherein the recommended configuration information comprises an instruction to delete the second data node.

15 . The apparatus according to claim 12 , wherein the configuration for the first data node comprises creating the first data node, and the logical relationship comprises that the first data node references the second data node; and the instructions further include instructions to:

when the second data node is not created, obtain, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the first data node lacks the second data node to be referenced.

16 . The apparatus according to claim 15 , wherein the recommended configuration information comprises an instruction to create the second data node.

17 . The apparatus according to claim 12 , wherein the configuration for the first data node comprises creating the first data node, and the logical relationship comprises that the first data node and the second data node co-exist; and the instructions further include instructions to:

when the second data node is not created, obtain, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the second data node is missing.

18 . The apparatus according to claim 17 , wherein the recommended configuration information comprises an instruction to create the second data node.

19 . The apparatus according to claim 12 , wherein the configuration for the first data node comprises an instruction to configure a parameter value of the first data node as a first configuration parameter value, and the logical relationship comprises that the second data node is valid when the parameter value of the first data node satisfies a second preset condition; and the instructions further include instructions to:

when the first configuration parameter value does not satisfy the second preset condition, obtain, based on the logical relationship, the reason why the configuration fails to pass the validation, wherein the reason why the configuration fails to pass the validation comprises that the parameter value of the first data node does not satisfy the second preset condition.

20 . The apparatus according to claim 19 , wherein the recommended configuration information comprises:

an instruction to configure the parameter value of the first data node to satisfy the second preset condition.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 31, 2023
From: CHEN, RUI; XIE, TUSHOU; JIA, YIN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 064763/0563 →
Priority Claims (2)
CN 202011531306.1 · Dec 22, 2020 · national
CN 202110185554.3 · Feb 10, 2021 · national
Continuity (2)
Continuation PCTCN2021118847 · Sep 16, 2021
Related Publication 20230336410A1 · Oct 19, 2023
References Cited (35)
US 7376719B1 · Shafer · 2008 [cited by examiner]
US 8024440B2 · Jibbe · 2011 [cited by examiner]
US 8250184B2 · Poyhonen · 2012 [cited by examiner]
US 8291506B2 · Shafer · 2012 [cited by examiner]
US 8504660B2 · DeCusatis · 2013 [cited by examiner]
US 8595332B2 · Ding · 2013 [cited by examiner]
US 8713522B2 · Blakeley · 2014 [cited by examiner]
US 9426030B1 · Anerousis · 2016 [cited by examiner]
US 9529772B1 · Shankaran · 2016 [cited by examiner]
US 9578126B1 · Kirti · 2017 [cited by examiner]
US 10057124B2 · Affoneh · 2018 [cited by examiner]
US 10397051B1 · Featonby · 2019 [cited by examiner]
US 10749759B2 · Clark · 2020 [cited by examiner]
US 11044148B2 · Patterson · 2021 [cited by examiner]
US 11082293B2 · Clark · 2021 [cited by examiner]
US 11088913B2 · Washenko · 2021 [cited by examiner]
US 11418397B1 · Engi · 2022 [cited by examiner]
US 11513982B2 · Martin · 2022 [cited by examiner]
US 11528191B1 · Ficara · 2022 [cited by examiner]
US 11586611B2 · Srinivasan · 2023 [cited by examiner]
US 11765154B2 · Eichen · 2023 [cited by examiner]
US 11915014B2 · Deka · 2024 [cited by examiner]
US 20050027858A1 · Sloth · 2005 [cited by examiner]
US 20060015591A1 · Datla · 2006 [cited by examiner]
US 20170054601A1 · Affoneh · 2017 [cited by examiner]
US 20170171024A1 · Anerousis · 2017 [cited by examiner]
US 20170195187A1 · Bennett · 2017 [cited by examiner]
US 20170317884A1 · Ackerman · 2017 [cited by examiner]
US 20180034805A1 · Eichen · 2018 [cited by examiner]
US 20190342296A1 · Anandam · 2019 [cited by examiner]
US 20200336374A1 · Clark · 2020 [cited by examiner]
US 20210014283A1 · Soroush · 2021 [cited by examiner]
US 20230336410A1 · Chen · 2023 [cited by examiner]
US 20240251041A1 · Chai · 2024 [cited by examiner]
Enns R et al: “Network Configuration Protocol (NETCONF); rfc6241.txt”, Network Configuration Protocol (NETCONF); rfc6241.txt, Internet Engineering Task Force, IETF; Standard, Internet Society (ISOC) 4, Rue Des Falaises … [cited by applicant]