IP Library Granted Patent US 12,585,513
Granted Patent B2
US 12,585,513 · App. 17/870,474 · Granted Mar 24, 2026

Data management method, apparatus, and device, computer-readable storage medium, and system

Inventors: Zitao Wang (Nanjing, CN); Ye Niu (Beijing, CN); Ran Tao (Shenzhen, CN); Qin Wu (Nanjing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
G06F9/547G06F16/215H04L41/00
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,585,513
App. No.
17/870,474
Granted
Mar 24, 2026
Kind
B2
Abstract

A data management method, apparatus, device, a computer-readable storage medium, and system are provided. The method is applied to a first network device, the first network device determines target invalid data existing in a second network device, the first network device obtains a first RPC, and the first RPC carries information about target invalid data that needs to be deleted. Then, the first network device sends the first RPC to the second network device, where the first RPC is used to indicate the second network device to delete the target invalid data. In this application, residual data is automatically identified, and the residual data is cleared, to automatically delete the residual data in batches, thereby saving device resources and improving an operation and maintenance management effect.

Claims (72)

1 . A method comprising:

determining, by a first network device, target invalid data in a second network device,

wherein the determining the target invalid data in the second network device comprises:

sending, by the first network device, a second remote procedure call (RPC) or a third RPC to the second network device;

obtaining, by the first network device, a first RPC, wherein the first RPC carries information about the target invalid data that needs to be deleted; and

sending, by the first network device, the first RPC to the second network device, wherein the first RPC indicates the second network device to delete the target invalid data.

2 . The method according to claim 1 , wherein the second RPC indicates the second network device to perform data difference comparison, and wherein the determining, by the first network device, the target invalid data in the second network device further comprises:

receiving, by the first network device, a data difference comparison result returned by the second network device; and

determining, by the first network device, based on the data difference comparison result, the target invalid data in the second network device.

3 . The method according to claim 2 , wherein before the sending, by the first network device, the second RPC to the second network device, the method further comprises:

receiving, by the first network device, a basic event notification sent by the second network device, wherein the basic event notification indicates that invalid data exists in the second network device; and

determining, by the first network device, based on the basic event notification, that the invalid data exists in the second network device; and

triggering the sending of the second RPC to the second network device.

4 . The method according to claim 1 , wherein the third RPC indicates to the second network device to return first data, and wherein the determining, by the first network device, the target invalid data in the second network device further comprises:

receiving, by the first network device, the first data returned by the second network device; and

determining, by the first network device, in response to determining that second data referenced by the first data does not exist, that the first data is the target invalid data in the second network device.

5 . The method according to claim 1 , wherein the third RPC indicates the second network device to return first data, and wherein the determining, by the first network device, the target invalid data in the second network device further comprises:

receiving, by the first network device, an error identifier returned by the second network device, wherein the error identifier indicates that second data referenced by the first data has been deleted; and

determining, by the first network device, based on the error identifier, the first data as the target invalid data in the second network device.

6 . The method according to claim 1 , wherein before the determining, by the first network device, the target invalid data in the second network device, the method further comprises:

establishing, by the first network device, a network configuration session with the second network device; and

receiving, by the first network device based on the network configuration session, information indicating a residual network configuration data clearing capability that is sent by the second network device and that is supported by the second network device.

7 . The method according to claim 1 , wherein the first RPC is a new RPC, wherein an input parameter of the new RPC comprises the information about the target invalid data that needs to be deleted; or

the first RPC is an extended RPC obtained by extending an existing RPC, wherein the extended RPC carries the information about the target invalid data that needs to be deleted.

8 . The method according to claim 1 , wherein after the sending, by the first network device, the first RPC to the second network device, the method further comprises:

reading, by the first network device, the target invalid data in the second network device; and

verifying, based on reading the target invalid data, whether the target invalid data is cleared.

9 . An apparatus, wherein the apparatus comprises:

at least one processor;

at least one non-transitory computer-readable storage medium storing a program to be executed by the at least one processor, the program including instructions to cause the apparatus to perform operations including:

determining target invalid data in a second network device,

wherein the determining the target invalid data in the second network device comprises:

sending a second remote procedure call (RPC) or a third RPC to the second network device; and

obtaining a first RPC, wherein the first RPC carries information about target invalid data that needs to be deleted; and

sending the first RPC to the second network device, wherein the first RPC indicates to the second network device to delete the target invalid data.

10 . The apparatus according to claim 9 , wherein the second RPC indicates the second network device to perform data difference comparison, and wherein the determining the target invalid data further comprises:

receiving a data difference comparison result returned by the second network device; and

determining, based on the data difference comparison result, the target invalid data in the second network device.

11 . The apparatus according to claim 10 , wherein before the sending the second RPC to the second network device, the operations further comprise:

receiving a basic event notification sent by the second network device, wherein the basic event notification indicates that invalid data exists in the second network device;

determining, based on the basic event notification, that the invalid data exists in the second network device; and

triggering the sending of the second RPC to the second network device.

12 . The apparatus according to claim 9 , wherein the third RPC indicates to the second network device to return first data, and wherein the determining the target invalid data in the second network device further comprises:

receiving the first data returned by the second network device; and

determining, in response to determining that second data referenced by the first data does not exist, that the first data is the target invalid data in the second network device.

13 . The apparatus according to claim 9 , wherein the third RPC indicates the second network device to return first data, and wherein the determining the target invalid data in the second network device further comprises:

receiving an error identifier returned by the second network device, wherein the error identifier indicates that second data referenced by the first data has been deleted; and

determining, based on the error identifier, the first data as the target invalid data in the second network device.

14 . The apparatus according to claim 9 , wherein before the determining the target invalid data in the second network device, the operations further comprise:

establishing a network configuration session with the second network device; and

receiving, based on the network configuration session, information indicating a residual network configuration data clearing capability that is sent by the second network device and that is supported by the second network device.

15 . The apparatus according to claim 9 , wherein the first RPC is a new RPC, wherein an input parameter of the new RPC comprises the information about the target invalid data that needs to be deleted; or

the first RPC is an extended RPC obtained by extending an existing RPC, wherein the extended RPC carries the information about the target invalid data that needs to be deleted.

16 . The apparatus according to claim 9 , wherein after the sending the first RPC to the second network device, the operations further comprise:

reading the target invalid data in the second network device; and

verifying, based on a result of reading the target invalid data, whether the target invalid data is cleared.

17 . A non-transitory computer-readable storage medium storing a program to be executed by a first network device, the program including instructions to cause the first network device to perform operations including:

determining target invalid data in a second network device,

wherein the determining the target invalid data in the second network device comprises:

sending a second remote procedure call (RPC) or a third RPC to the second network device;

obtaining a first RPC, wherein the first RPC carries information about the target invalid data that needs to be deleted; and

sending the first RPC to the second network device, wherein the first RPC indicates to the second network device to delete the target invalid data.

18 . The non-transitory computer-readable storage medium according to claim 17 , wherein the second RPC indicates the second network device to perform data difference comparison, and wherein the determining the target invalid data further comprises:

receiving a data difference comparison result returned by the second network device; and

determining based on the data difference comparison result, the target invalid data in the second network device.

19 . The non-transitory computer-readable storage medium according to claim 17 , wherein before the sending the second RPC to the second network device, the operations further comprise:

receiving a basic event notification sent by the second network device, wherein the basic event notification indicates that invalid data exists in the second network device;

determining based on the basic event notification, that the invalid data exists in the second network device; and

triggering the sending of the second RPC to the second network device.

20 . The non-transitory computer-readable storage medium according to claim 17 , wherein the third RPC indicates to the second network device to return first data, and wherein the determining the target invalid data in the second network device further comprises:

receiving the first data returned by the second network device; and

determining in response to determining that second data referenced by the first data does not exist, that the first data is the target invalid data in the second network device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 10, 2025
From: WANG, ZITAO; NIU, YE; TAO, RAN; WU, QIN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 073180/0870 →
Priority Claims (1)
CN 202010075689.X · Jan 22, 2020 · national
Continuity (2)
Continuation PCTCN2020119583 · Sep 30, 2020
Related Publication 20220358003A1 · Nov 10, 2022
References Cited (14)
US 8335171B1 · Purkayastha · 2012 [cited by examiner]
US 9094299B1 · Rao D.S · 2015 [cited by examiner]
US 10977223B2 · Ellis · 2021 [cited by examiner]
US 11075793B2 · Luo · 2021 [cited by examiner]
US 11397717B2 · Baker · 2022 [cited by examiner]
US 20070073792A1 · Nichols et al. · 2007 [cited by applicant]
US 20140365621A1 · Vieira · 2014 [cited by applicant]
CN 110391949A · 2019 [cited by applicant]
Clemm, A. et al., “Comparison of NMDA datastores draft-ietf-netmod-nmda-diff-03,” Network Working Group, Internet-Draft, Intended status: Standards Track, Expires: May 7, 2020, Nov. 4, 2019, 17 pages. [cited by applicant]
Bjorklund, M et al., “YANG—A Data Modeling Language for the Network Configuration Protocol (NETCONF),” Internet Engineering Task Force (IETF), Request for Comments: 6020, Category: Standards Track, ISSN: 2070-1721, Tail… [cited by applicant]
Bjorklund, M. et al., “The YANG 1.1 Data Modeling Language,” Internet Engineering Task Force (IETF), Request for Comments: 7950, Category: Standards Track, ISSN: 2070-1721, Tail-f Systems, Aug. 2016, 217 pages. [cited by applicant]
Clemm, A. et al., “Comparison of NMDA Datastores draft-ietf-netmod-nmda-diff-01,” Network Working Group, Internet Draft, Intended Status: Standards Track, Expires: Nov. 24, 2019, YumaWorks, May 23, 2019, 15 pages. [cited by applicant]
Enns, R. et al., “NETCONF Configuration Protocol,” Network Working Group, Request for Comments: 4741, Category: Standards Track, Juniper Networks, Dec. 2006, 95 pages. [cited by applicant]
Wu, Q. et al., “NMDA Base Notification for Intent Based Configuration Update draft-wu-netmod-base-notification-nmda-03,” NETWOD Working Group, Internet-Draft, Intended Status: Standards Track, Expires: Dec. 31, 2019, Hu… [cited by applicant]