IP Library Granted Patent US 8,478,797
Granted Patent B2
US 8,478,797 · App. 13/485,482 · Granted Jul 2, 2013

Atomic deletion of database data categories

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 8,478,797
App. No.
13/485,482
Granted
Jul 2, 2013
Kind
B2
Abstract

A device maintains, in a database, a plurality of data items, each data item of the plurality of data items being associated with a respective category. The device associates, in the database, a first counter value with each data item, the first counter value indicating a number of times the respective category has been deleted from the database at a time when the data item was stored in the database. The device associates, in the database or another database, a second counter value with the respective category, the second counter value indicating a current value for a number of times the respective category has been deleted from the database. The device selectively deletes, from the database, one or more data items of the plurality of data items from the database based on the first counter values and the second counter value.

Claims (79)

1. A method comprising:

receiving, by a device, a query for a data item;

retrieving, by the device, an item deletion count associated with the data item;

determining, by the device, a category associated with the data item;

retrieving, by the device, a category deletion count associated with the determined category;

comparing, by the device, the retrieved item deletion count and the retrieved category deletion count;

determining, by the device, whether the retrieved item deletion count is greater than or less than the retrieved category deletion count;

retrieving, by the device and when the retrieved item deletion count is greater than the retrieved category deletion count, the data item for collection; and

hiding, by the device and when the retrieved item deletion count is less than the retrieved category deletion count, the data item from collection.

2. The method of claim 1 , where, when determining the category associated with the data item, the method further comprises:

determining the category associated with the data item by extracting data related to the data item, or

determining the category associated with the data item by calculating a function of the data item.

3. The method of claim 1 , where, when determining the category associated with the data item, the method further comprises:

determining the category based on a publish request received from another device, the publish request including:

a publisher identifier that identifies the other device.

4. The method of claim 3 , further comprising:

using the publisher identifier as the category.

5. The method of claim 1 , further comprising:

determining whether the retrieved item deletion count is equal to the retrieved category deletion count; and

retrieving, when the retrieved item deletion count is equal to the retrieved category deletion count, the data item.

6. The method of claim 1 , where, when hiding the data item, the method further comprises:

marking the data item as non-retrievable.

7. A device comprising:

a processor to:

receive a query for a data item;

retrieve an item deletion count associated with the data item;

determine a category associated with the data item;

retrieve a category deletion count associated with the determined category;

compare the retrieved item deletion count and the retrieved category deletion count;

determine whether the retrieved item deletion count is greater than or less than the retrieved category deletion count;

retrieve, when the retrieved item deletion count is greater than the retrieved category deletion count, the data item for collection; and

hide, when the retrieved item deletion count is less than the retrieved category deletion count, the data item from collection.

8. The device of claim 7 , where, when determining the category associated with the data item, the processor is further to:

determine the category associated with the data item by extracting data related to the data item, or

determine the category associated with the data item by calculating a function of the data item.

9. The device of claim 7 , where, when determining the category associated with the data item, the processor is further to:

determine the category based on a publish request received from another device, the publish request including:

a publisher identifier that identifies the other device.

10. The device of claim 9 , where the processor is further to:

use the publisher identifier as the category.

11. The device of claim 7 , where the processor is further to:

determine whether the retrieved item deletion count is equal to the retrieved category deletion count; and

retrieve, when the retrieved item deletion count is equal to the retrieved category deletion count, the data item for collection.

12. The device of claim 9 , where, when hiding the data item, the processor is further to:

mark the data item as non-retrievable.

13. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions which, when executed by at least one processor, cause the at least one processor to:

receive a query for a data item;

retrieve an item deletion count associated with the data item;

determine a category associated with the data item;

retrieve a category deletion count associated with the determined category;

compare the retrieved item deletion count and the retrieved category deletion count;

determine whether the retrieved item deletion count is greater than or less than the retrieved category deletion count;

retrieve, when the retrieved item deletion count is greater than the retrieved category deletion count, the data item for collection; and

hide, when the retrieved item deletion count is less than the retrieved category deletion count, the data item from collection.

14. The non-transitory computer-readable medium of claim 13 , where the one or more instructions to determine the category associated with the data item further include:

one or more instructions which, when executed by the at least one processor, cause the at least one processor to:

determine the category associated with the data item by extracting data related to the data item, or

determine the category associated with the data item by calculating a function of the data item.

15. The non-transitory computer-readable medium of claim 13 , where the one or more instructions to determine the category associated with the data item further include:

one or more instructions which, when executed by the at least one processor, cause the at least one processor to:

extract the category based on a publish request received from another device, the publish request including:

a publisher identifier that identifies the other device.

16. The non-transitory computer-readable medium of claim 15 , where the instructions further comprise:

one or more instructions which, when executed by the at least one processor, cause the at least one processor to:

use the publisher identifier as the category.

17. The non-transitory computer-readable medium of claim 13 , where the instructions further comprise:

one or more instructions which, when executed by the at least one processor, cause the at least one processor to:

determine whether the retrieved item deletion count is equal to the retrieved category deletion count; and

retrieve, when the retrieved item deletion count is equal to the retrieved category deletion count, the data item for collection.

18. The non-transitory computer-readable medium of claim 13 , where the one or more instructions to hide the data item further include:

one or more instructions which, when executed by the at least one processor, cause the at least one processor to:

mark the data item as non-retrievable.

19. The method of claim 1 , further comprising:

providing the retrieved item to another device,

the other device transmitting the query.

20. The device of claim 7 , where the processor is further to:

provide the retrieved item to another device,

the other device transmitting the query.

Assignments (15)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: PULSE SECURE LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0027 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 054665/0873 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0386 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; INVANTI, INC.; MOBILEIRON, INC.; INVANTI US LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 054665/0873 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 053638-0220 Recorded Dec 1, 2020
From: KKR LOAN ADMINISTRATION SERVICES LLC
To: PULSE SECURE, LLC
Reel/Frame 054559/0368 →
SECURITY INTEREST Recorded Aug 29, 2020
From: PULSE SECURE, LLC
To: KKR LOAN ADMINISTRATION SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 053638/0220 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 042380/0859 Recorded Aug 29, 2020
From: CERBERUS BUSINESS FINANCE, LLC, AS AGENT
To: PULSE SECURE, LLC
Reel/Frame 053638/0259 →
RELEASE OF SECURITY INTEREST Recorded Jul 21, 2020
From: JUNIPER NETWORKS, INC.
To: PULSE SECURE, LLC; SMOBILE SYSTEMS, INC.
Reel/Frame 053271/0307 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL 037338, FRAME 0408 Recorded May 1, 2017
From: US BANK NATIONAL ASSOCIATION
To: PULSE SECURE, LLC
Reel/Frame 042381/0568 →
GRANT OF SECURITY INTEREST PATENTS Recorded May 1, 2017
From: PULSE SECURE, LLC
To: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT
Reel/Frame 042380/0859 →
SECURITY INTEREST Recorded Dec 21, 2015
From: PULSE SECURE, LLC
To: U.S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 037338/0408 →
SECURITY INTEREST Recorded Dec 30, 2014
From: PULSE SECURE, LLC; SMOBILE SYSTEMS, INC.
To: JUNIPER NETWORKS, INC.
Reel/Frame 034713/0950 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 24, 2014
From: JUNIPER NETWORKS, INC.
To: PULSE SECURE, LLC
Reel/Frame 034045/0717 →