IP Library Granted Patent US 8,150,961
Granted Patent B1
US 8,150,961 · App. 11/289,130 · Granted Apr 3, 2012

Systems and methods for updating distributed network inventory services

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,150,961
App. No.
11/289,130
Granted
Apr 3, 2012
Kind
B1
Abstract

Systems and methods for updating distributed network inventory services are disclosed. A network or a portion thereof is scanned to identify at least one computing asset within the scanned portion. A scan file is compiled based on the information obtained. A first inventory service is updated based on the scan file. A second inventory service is identified. The scan file is transmitted to the second inventory service, and the second inventory service is updated based on the scan file. In one embodiment, the inventory services are selectively updated based on specific types of data, such as hardware or software inventory data, within the scan file. In addition, a specialized database management system may be used to enable data gathering techniques specific to inventory data.

Claims (38)

1. A method for updating distributed inventory services that enumerate computing assets within a computer network, comprising:

scanning a first portion of a network to inventory computing assets within the first portion of the network;

compiling a first inventory scan file that reflects at least one computing asset within the first portion of the network, wherein after an initial scan, the first inventory scan file includes only incremental data about changes in the software or hardware configuration of the computing assets since a last scan was performed;

updating a first inventory service running on a first server based on the first inventory scan file;

identifying an address of a second server running a second inventory service, the first and second server each managing one or more computing assets;

transmitting the first inventory scan file to the second server;

receiving, by the first server, a second inventory scan file from the second server, the second inventory scan file being compiled to reflect a second computing asset within a second portion of the network, wherein the second inventory scan file includes only incremental data about changes in the software or hardware configuration of the second computing asset since a last scan was performed; and

updating the first inventory service on the first server based on the second inventory scan file, wherein the first and second servers have selective updating to store specific data types from the first and second scan files, wherein a first data type is stored on the first server and a second data type is stored on the second server, wherein the first server receives the second data type from either the first scan file or the second scan file but does not store the second data type, and wherein the second server receives the first data type from either the first scan file or the second scan file but does not store the first data type, wherein at least one of the first and second inventory services comprises a database management system created specifically for inventory services to enable specialized inventory data gathering, wherein the specialized inventory data gathering technique comprises a breadcrumb feature that identifies which server is associated with a particular computing asset, and further comprises a hashing function that groups computing assets according to the server which is associated with each asset.

2. The method of claim 1 , wherein the first inventory service comprises a first type of data.

3. The method of claim 2 , wherein the first type of data comprises an inventory of software computing assets.

4. The method of claim 2 , wherein the first type of data comprises an inventory of hardware computing assets.

5. The method of claim 2 , wherein the second inventory service comprises a second type of data.

6. The method of claim 5 , further comprising limiting access to the second inventory service.

7. The method of claim 1 , wherein the first server is associated with a first set of computing assets, and the second server is associated with a second set of computing assets.

8. A system for updating distributed inventory services that enumerate computing assets within a computer network, comprising:

a first and a second server in electronic communication with each other, wherein the servers comprise a computer-readable medium that is part of the servers or is in electronic communication with the servers, the computer-readable medium comprising instructions for updating a first inventory service running on the first server and a second inventory service running on the second server, the instructions being executable to:

scan a first portion of a network to inventory computing assets within the first portion of the network;

compile a first inventory scan file that reflects at least one computing asset within the first portion of the network, wherein after an initial scan, the first inventory scan file includes only incremental data about changes in the software or hardware configuration of the computing asset since a last scan was performed;

update the first inventory service running on the first server based on the first inventory scan file;

identify an address of the second server, the first and second server each managing one or more computing assets;

transmit the first inventory scan file to the second server;

receiving, by the first server, a second inventory scan file from the second server, the second inventory scan file being compiled to reflect a second computing asset within a second portion of the network, wherein the second inventory scan file includes only incremental data about changes in the software or hardware configuration of the second computing asset since a last scan was performed; and

updating the first inventory service on the first server based on the second inventory scan file, wherein the first and second servers have selective updating to store specific data types from the first and second scan files, wherein a first data type is stored on the first server and a second data type is stored on the second server, wherein the first server receives the second data type from either the first scan file or the second scan file but does not store the second data type, and wherein the second server receives the first data type from either the first scan file or the second scan file but does not store the first data type, wherein at least one of the first and second inventory services comprises a database management system created specifically for inventory services to enable specialized inventory data gathering, wherein the specialized inventory data gathering technique comprises a breadcrumb feature that identifies which server is associated with a particular computing asset, and further comprises a hashing function that groups computing assets according to the server which is associated with each asset.

9. The system of claim 8 , wherein the first inventory service comprises a first type of data.

10. The system of claim 9 , wherein the second inventory service comprises a second type of data.

11. The system of claim 10 , wherein the instructions are further executable to limit access to the second inventory service.

12. A non-transitory computer-readable medium comprising executable instructions for updating distributed inventory services that enumerate computing assets within a computer network, the instructions being executable to:

scan a first portion of a network to inventory computing assets within the first portion of the network;

compile a first inventory scan file that reflects at least one computing asset within the first portion of the network, wherein after an initial scan, the first inventory scan file includes only incremental data about changes in the software or hardware configuration of the computing asset since a last scan was performed;

update a first inventory service running on a first server based on the first inventory scan file;

identify an address of a second server running a second inventory service;

transmit the first inventory scan file to the second server, the first and second server each managing one or more computing assets;

receive, by the first server, a second inventory scan file from the second server, the second inventory scan file being compiled to reflect a second computing asset within a second portion of the network, wherein the second inventory scan file includes only incremental data about changes in the software or hardware configuration of the second computing asset since a last scan was performed; and

update the first inventory service on the first server based on the second inventory scan file, wherein the first and second servers have selective updating to store specific data types from the first and second scan files, wherein a first data type is stored on the first server and a second data type is stored on the second server, wherein the first server receives the second data type from either the first scan file or the second scan file but does not store the second data type, wherein the second server receives the first data type from either the first scan file or the second scan file but does not store the first data type, wherein at least one of the first and second inventory services comprises a database management system created specifically for inventory services to enable specialized inventory data gathering, wherein the specialized inventory data gathering technique comprises a breadcrumb feature that identifies which server is associated with a particular computing asset, and further comprises a hashing function that groups computing assets according to the server which is associated with each asset.

13. The non-transitory computer-readable medium of claim 12 , wherein the first inventory service comprises a first type of data.

14. The non-transitory computer-readable medium of claim 13 , wherein the second inventory service comprises a second type of data.

15. The non-transitory computer-readable medium of claim 14 , the instructions are further executable to limit access to the second inventory service.

16. The non-transitory computer-readable medium of claim 12 , wherein at least one of the first and second inventory services comprises a database management system created specifically for inventory services to enable specialized inventory data gathering.

Assignments (19)
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 - 41052/0762 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: CRIMSON CORPORATION
Reel/Frame 054560/0857 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 41459/0387 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: CRIMSON CORPORATION
Reel/Frame 054637/0161 →
MERGER Recorded Apr 19, 2018
From: CRIMSON CORPORATION
To: IVANTI, INC.
Reel/Frame 045983/0075 →
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 40182/0345 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 041463/0581 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 40183/0506 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 041463/0457 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jan 20, 2017
From: CRIMSON CORPORATION
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 041052/0762 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 20, 2017
From: CRIMSON CORPORATION
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 041459/0387 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Sep 29, 2016
From: CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 040183/0506 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Sep 29, 2016
From: CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 040182/0345 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT R/F 031029/0849 Recorded Sep 28, 2016
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 040171/0307 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT R/F 032333/0637 Recorded Sep 28, 2016
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 040171/0037 →
SECURITY AGREEMENT Recorded Feb 25, 2014
From: LANDESK SOFTWARE, INC.; CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 032333/0637 →
SECURITY AGREEMENT Recorded Aug 16, 2013
From: LANDESK GROUP, INC.; LANDSLIDE HOLDINGS, INC.; CRIMSON ACQUISITION CORP.; LANDESKSOFTWARE, INC.; CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 031029/0849 →
RELEASE OF SECURITY INTEREST Recorded Aug 12, 2013
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
To: CRIMSON CORPORATION
Reel/Frame 030993/0644 →
PATENT SECURITY AGREEMENT Recorded Jul 26, 2012
From: CRIMSON CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
Reel/Frame 028643/0847 →
RELEASE OF SECURITY INTEREST Recorded Jun 20, 2012
From: WELLS FARGO CAPITAL FINANCE, LLC
To: LANDESK GROUP, INC.; LANDSLIDE HOLDINGS, INC.; LANDESK SOFTWARE, INC.; CRIMSON ACQUISITION CORP.; CRIMSON CORPORATION
Reel/Frame 028413/0913 →