# US 8,150,961 B1 · Systems and methods for updating distributed network inventory services

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,150,961 B1
- Document ID: US8150961B1
- Status: Granted
- Kind: B1
- Application number: 11/289,130
- Filed: 2005-11-29
- Granted: 2012-04-03
- Earliest claimed: 2005-11-29
- Assignees: Crimson Corporation
- Inventors: Mark Bird; Scot Swan
- Web page: https://patentgrep.com/patent/US8150961B1

## CPC

- G06Q 10/087: Inventory or stock management, e.g. order filling, procurement or balancing against orders
- G06Q 10/08744: {by distributed inventory management}
- G06Q 10/0877: {by inventory control or reporting using inventory tracking or counting}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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

### Claim 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.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 2)

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

### Claim 4 (depends on 2)

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

### Claim 5 (depends on 2)

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

### Claim 6 (depends on 5)

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

### Claim 7 (depends on 1)

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.

### Claim 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.

### Claim 9 (depends on 8)

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

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 10)

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

### Claim 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.

### Claim 13 (depends on 12)

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

### Claim 14 (depends on 13)

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

### Claim 15 (depends on 14)

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

### Claim 16 (depends on 12)

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.
