Software updates using client self-reporting and a hierarchical data structure

• US 10,042,626 B2
• Filed: 06/29/2015
• Issued: 08/07/2018
• Est. Priority Date: 06/29/2015
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Nekrestyanov, Igor, Ng, Thomas Van Chung, Perrett, Timothy M.
• Primary Examiner(s): Chowdhury, Ziaul A
• Application Number:
  US14/753,597
• Publication Number:
  US 20160378454A1
• Time in Patent Office: 1,135 Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A client device forwards data about itself to an update device. The client metadata may identify hardware components included in the client, software being executed by the client, or other information, such as a geographic location associated with the client device and/or account information for associated operator. The update device determines metadata regarding various software updates, such as data identifying different versions of available updates and logical rules for selecting among the versions. The update device selects specific update versions for the client device, and forwards data identifying the selected updates to the client device. The client device uses the identifying data to locate and obtain the identified updates. The client device may access the updates via a content delivery network that schedules delivery of the updates to the client device.

Claims

1. A method comprising:

receiving, by a processor associated with a first device, first data from a second device, wherein the first data identifies one or more attributes associated with the second device;

selecting, by the processor and based on the one or more attributes, a software update from a repository that includes a plurality of software updates, wherein the repository further includes a plurality of versions of the software update;

determining, by the processor, metadata associated with the plurality of versions of the software update, wherein the metadata identifies two or more versions of the software update of the plurality of versions of the software update that are marked as usable based on update attributes for identifying the two or more versions and logic rules for selecting usable versions of the plurality of versions of the software update, wherein the two or more versions of the software update includes a first version of the software update and a second version of the software update, wherein the first version of the software update is generated before the second version of the software update;

selecting, by the processor, a version of the two or more versions of the software update for the second device, wherein selecting the version for the second device includes;

performing a lookup in a table, wherein the table stores information about each version of each software update of the plurality of software updates in a plurality of metadata columns, wherein the plurality of metadata columns comprise an update identifier column, a version identifier column, a version time identifier column, a usability indicator column, a use logic column, and an other metadata column, wherein the other metadata column includes entries indicating whether a selected version of a software update must be installed with an additional software update without requiring subsequent use of the additional software update;

navigating an update hierarchy in the use logic column to determine whether the second device is specifically identified in the use logic column of a third version of the software update of the plurality of versions of the software update;

if the second device is specifically identified in the use logic column of the third version of the software update and complies with all other criteria in the plurality of metadata columns, selecting the third version of the software update as the selected version for use by the second device;

if the second device is not specifically identified in the use column of the third version of the software update, selecting a fourth version of the software update as the selected version for use by the second device, wherein the fourth version of the software update matches the second device at a root or hardware group level and complies with all the other criteria of the plurality of metadata columns;

determining, by the processor and based on the table, whether the additional software update is to be used by the second device when installing the selected version of the software update;

and

forwarding, by the processor, second data to the second device, wherein the second data identifies the selected version of the software update, wherein the second device uses the second data to obtain the selected version of the software update, and wherein the second data includes information identifying the additional software update when the additional software update is to be used by the second device when installing the third version of the software update or installing the fourth version of the software update.

2. The method of claim 1, further comprising:

forwarding a request to the second device for the one or more attributes, wherein the first data is received from the second device that generates the first data based on the forwarded request.

3. The method of claim 1, wherein the repository further includes a plurality of versions of the additional software update, and wherein the method further comprises:

determining metadata associated with the plurality of versions of the additional software update, wherein the metadata associated with the plurality of versions of the additional software update identifies two or more versions of the additional software update, of the plurality of versions of the additional software update, that are marked as usable;

selecting a version, of the two or more versions of the additional software update, that is compatible with the second device and the selected version of the software update; and

including, in the second data, information identifying the selected version of the additional software update.

4. The method of claim 1, wherein the metadata associated with the plurality of versions of the software update identify times when the plurality of versions of the software update were at least one of generated or added to the repository, and wherein the method further comprises:

identifying, based on the associated times, an oldest version of the plurality of versions of the software update; and

causing the oldest version of the software update to be removed from the repository.

5. The method of claim 1, wherein the second data includes a uniform resource locator that identifies a storage location associated with the selected version of the software update.

6. The method of claim 1, wherein the second device obtains the selected version of the software update via a content delivery network (CDN), and wherein the method further comprises:

identifying an attribute of the CDN, wherein the attribute includes at least one of a congestion level on the CDN, available bandwidth on the CDN, or transmission delays on the CDN; and

scheduling transmission of the selected version of the software update via the CDN to the second device based on the attribute of the CDN.

7. A first device comprising:

a memory configured to store instructions; and

a processor configured to execute one or more of the instructions to;

receive first data from a second device, wherein the first data identifies one or more attributes associated with the second device;

select, based on the one or more attributes, a software update from a repository that includes a plurality of software updates, wherein the repository further includes a plurality of versions of the software update;

determine metadata associated with the plurality of versions of the software update, wherein the metadata identifies two or more versions of the software update of the plurality of versions of the software update that are marked as usable based on update attributes for identifying the two or more versions and logic rules for selecting usable versions of the plurality of versions of the software update, wherein the two or more versions of the software update includes a first version of the software update and a second version of the software update, wherein the first version of the software update is generated before the second version of the software update;

select a version of the two or more versions of the software update for the second device, wherein the processor, when selecting the version for the second device, is further configured to;

perform a lookup in a table, wherein the table stores information about each version of each software update of the plurality of software updates in a plurality of metadata columns, wherein the plurality of metadata columns comprise an update identifier column, a version identifier column, a version time identifier column, a usability indicator column, a use logic column, and an other metadata column, wherein the other metadata column includes entries indicating whether a selected version of a software update must be installed with an additional software update without requiring subsequent use of the additional software update;

navigate an update hierarchy in the use logic column to determine whether the second device is specifically identified in the use logic column of a third version of the software update of the plurality of versions of the software update;

if the second device is specifically identified in the use logic column of the third version of the software update and complies with all other criteria in the plurality of metadata columns, select the third version of the software update as the selected version for use by the second device;

if the second device is not specifically identified in the use logic column of the third version of the software update, select a fourth version of the software update as the selected version for use by the second device, wherein the fourth version of the software update matches the second device at a root or hardware group level and complies with all the other criteria of the plurality of metadata columns;

determine, based on the table, whether the additional software update is to be used by the second device when installing the selected version of the software update; and

forward second data to the second device, wherein the second data identifies the selected version of the software update, wherein the second device uses the second data to obtain the selected version of the software update, and wherein the second data includes information identifying the additional software update when the additional software update is to be used by the second device when installing the third version of the software update or installing the fourth version of the software update.

8. The first device of claim 7, wherein the processor is further configured to execute one or more of the instructions to:

forward a request to the second device for the one or more attributes, wherein the first data is received from the second device that generates the first data based on the forwarded request.

9. The first device of claim 7, wherein the repository further includes a plurality of versions of the additional software update, and wherein the processor is further configured to execute one or more of the instructions to:

determine metadata associated with the plurality of versions of the additional software update, wherein the metadata associated with the plurality of versions of the additional software update identifies two or more versions of the additional software update, of the plurality of versions of the additional software update, that are marked as usable;

select a version, of the two or more versions of the additional software update, that is compatible with the second device and the selected version of the software update; and

include, in the second data, information identifying the selected version of the additional software update.

10. The first device of claim 7, wherein the metadata associated with the plurality of versions of the software update identify times when the plurality of versions of the software update were at least one of generated or added to the repository, and wherein the processor is further configured to execute one or more of the instructions to:

identify, based on the associated times, an oldest version of the plurality of versions of the software update; and

cause the oldest version of the software update to be removed from the repository.

11. The first device of claim 7, wherein the second data includes a uniform resource locator that identifies a storage location associated with the selected version of the software update.

12. The first device of claim 7, wherein the second device obtains the selected version of the software update via a content delivery network (CDN), and wherein the processor is further configured to execute one or more of the instructions to:

identify an attribute of the CDN, wherein the attribute includes at least one of a congestion level on the CDN, available bandwidth on the CDN, or transmission delays on the CDN; and

schedule transmission of the selected version of the software update via the CDN to the second device based on the attribute of the CDN.

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

a plurality of computer-executable instructions stored thereon, which, when executed by a processor associated with a first device, cause the processor to;

receive first data from a second device, wherein the first data identifies one or more attributes associated with the second device;

select, based on the one or more attributes, a software update from a repository that includes a plurality of software updates, wherein the repository further includes a plurality of versions of the software update;

determine metadata associated with the plurality of versions of the software update, wherein the metadata identifies two or more versions of the software update of the plurality of versions of the software update that are marked as usable based on update attributes for identifying the two or more versions and logic rules for selecting usable versions of the plurality of versions of the software update, wherein the two or more versions of the software update includes a first version of the software update and a second version of the software update, wherein the first version of the software update is generated before the second version of the software update;

select a version of the two or more versions of the software update for the second device, wherein processor, when selecting the version for the second device, is further configured to;

perform a lookup in a table, wherein the table stores information about each version of each software update of the plurality of software updates in a plurality of metadata columns, wherein the plurality of metadata columns comprise an update identifier column, a version identifier column, a version time identifier column, a usability indicator column, a use logic column, and an other metadata column, wherein the other metadata column includes entries indicating whether a selected version of a software update must be installed with an additional software update without requiring subsequent use of the additional software update;

navigate an update hierarchy in the use logic column to determine whether the second device is specifically identified in the use logic column of a third version of the software update of the plurality of versions of the software update;

if the second device is specifically identified in the use logic column of the third version of the software update and complies with all other criteria in the plurality of metadata columns, select the third version of the software update as the selected version for use by the second device;

if the second device is not specifically identified in the use logic column of the third version of the software update, select a fourth version of the software update as the selected version for use by the second device, wherein the fourth version of the software update matches the second device at a root or hardware group level and complies with all the other criteria of the plurality of metadata columns;

determine, based on the table, whether the additional software update is to be used by the second device when installing the selected version of the software update;

and

forward second data to the second device, wherein the second data identifies the selected version of the software update, wherein the second device uses the second data to obtain the selected version of the software update, and wherein the second data includes information identifying the additional software update when the additional software update is to be used by the second device when installing the third version of the software update or installing the fourth version of the software update.

14. The non-transitory computer-readable medium of claim 13, wherein the repository further includes a plurality of versions of the additional software update, and wherein the plurality of computer-executable instructions further cause the processor to:

determine metadata associated with the plurality of versions of the additional software update, wherein the metadata associated with the plurality of versions of the additional software update identifies two or more versions of the additional software update, of the plurality of versions of the additional software update, that are marked as usable;

select a version, of the two or more versions of the additional software update, that is compatible with the second device and the selected version of the software update; and

include, in the second data, information identifying the selected version of the additional software update.

15. The non-transitory computer-readable medium of claim 13, wherein the metadata associated with the plurality of versions of the software update identify times when the plurality of versions of the software update were at least one of generated or added to the repository, and wherein the plurality of computer-executable instructions further cause the processor to:

identify, based on the associated times, an oldest version of the plurality of versions of the software update; and

cause the oldest version of the software update to be removed from the repository.

16. The non-transitory computer-readable medium of claim 13, wherein the second data includes a uniform resource locator that identifies a storage location associated with the selected version of the software update.

17. The non-transitory computer-readable medium of claim 13, wherein the second device obtains the selected version of the software update via a content delivery network (CDN), and wherein the plurality of computer-executable instructions further cause the processor to:

identify an attribute of the CDN, wherein the attribute includes at least one of a congestion level on the CDN, available bandwidth on the CDN, or transmission delays on the CDN; and

schedule transmission of the selected version of the software update via the CDN to the second device based on the attribute of the CDN.