Device Decision to Download Software Update

Abstract

Various embodiments that pertain to device software is described. A decision can be made by a device on if the device should download an update for device software, such as a software patch. When the device decides that it should download the update, the device can download the appropriate update. In one example, the update can be downloaded by way of a patch portal that communicates with a patch database. The device can request the patch for the software and in response the device can be provided access to the patch by way of the patch portal.

What is claimed is: 
     
         1 . A processor that is communicatively coupled to a non-transitory computer-readable medium and that is configured to execute a command set stored by the non-transitory computer-readable medium to effectuate operation of a component set, the component set comprising:
 a decision component configured to decide if a download should occur for an update set to a software set on a device; and   a download component configured to cause the download to occur in response to the decision component deciding that the download should occur,   where the non-transitory computer-readable medium and the processor are resident upon the device.   
     
     
         2 . The processor of  claim 1 , the component set comprising:
 an assessment component configured to make an assessment of a quality of a network connection of the device; and   a determination component configured to make a determination if the network is of a sufficient quality in relation to a network connection quality threshold,   where if the determination is that the network is of the sufficient quality, then the decision component decides that download should occur,   where if the determination is that the network is not of the sufficient quality, then the decision component decides that download should not occur, and   where the assessment component and the determination component are resident upon the device.   
     
     
         3 . The processor of  claim 1 , the component set comprising:
 an assessment component configured to make an assessment of a task schedule of the device,   where the decision component decides if the download should occur based, at least in part, on a result of the assessment and   where the assessment component is resident upon the device.   
     
     
         4 . The processor of  claim 1 , the component set comprising:
 an interface component configured to receive a user update request; and   an authentication component configured to authenticate the user update request to produce an authentication result,   where the decision component decides that the download should occur in response to the authentication result indicating that the user update request is properly authenticated and   where the interface component and the authentication component are resident upon the device.   
     
     
         5 . The processor of  claim 1 , the component set comprising:
 an installation component configured to cause the installation of the update set upon the update set after the download is caused,   where the instillation component is resident upon the device.   
     
     
         6 . The processor of  claim 1 ,
 where the decision component is configured to decide an order of download for the update set and   where the download component is configured to cause the download to occur in accordance with the order of download.   
     
     
         7 . The processor of  claim 1 ,
 where the update set is a first update set,   where the download is a first download,   where the decision component is configured to decide if a second download should occur for a second update set to the software set on the device;   where the first update set is a patch update set, and   where the second update set is a metadata update set that indicates a useable portion of the patch update set to perform a patch.   
     
     
         8 . A system, comprising:
 a non-transitory computer-readable medium configured to retain a patch database that comprises a first patch for a first software module and a second patch for a second software module;   a reception component configured to receive a request for the first patch for the first software module from the device; and   an access component configured to allow access to the first patch for the first software module to the device in response to the request.   
     
     
         9 . The system of  claim 8 ,
 where in having access to the first patch the device downloads the first patch to itself,   where the device runs the first software module, and   where the device does not run the second software module.   
     
     
         10 . The system of  claim 8 ,
 where in having access to the first patch the device downloads the first patch to itself,   where the device runs the first software module,   where the device runs the second software module, and   where the access component is configured to allow access to the first patch without allowing access to the second patch.   
     
     
         11 . The system of  claim 8 ,
 where the request is a request for the first patch and the second patch,   where the device is configured to be allowed access to a common patch portion that is applicable for the first patch and the second patch, and   where the device downloads the common patch portion to itself after access is granted.   
     
     
         12 . The system of  claim 8 ,
 where the request is a first request,   where the device is a first device,   where the first request is received from the first device,   where the reception component is configured to receive a second request for the second patch for the second software module,   where the second request is received from a second device,   where the second device is different from the first device, and   where the access component is configured to allow access to the second patch for the second software module to the second device in response to the second request concurrently with allowing access to the first patch for the first software module to the first device in response to the first request.   
     
     
         13 . The system of  claim 8 ,
 where the request is a first request,   where the device is a first device,   where the first request is received from the first device,   where the reception component is configured to receive a second request for the first patch for the first software module,   where the second request is received from a second device,   where the second device is different from the first device, and   where the access component is configured to allow access to the first patch for the first software module to the second device in response to the second request concurrently with allowing access to the first patch for the first software module to the first device in response to the first request.   
     
     
         14 . A system, comprising:
 a non-transitory computer-readable medium configured to retain a software registry for a device, where the software registry lists a first software module of the device and a second software module of the device; and   an update component configured to manage an update for the first software module and the second software module through use of the software registry,   where the update component manages the update by downloading a first patch for the first software module and downloading a second patch for the second patch module and   where the non-transitory computer-readable medium and the update component are resident upon the device.   
     
     
         15 . The system of  claim 14 ,
 where the software registry lists a current device version of the first software module of the device and a current device version of the second software module of the device,   where the current device version of the first software module is compared against an available version of the first software module to determine if a first software module version mismatch exists,   where the update causes the current device version of the first software module to be replaced with the available version of the first software module when the first software module version mismatch exists,   where the current device version of the software module is compared against an available version of the second software module to determine if a second software module version mismatch exists, and   where the update causes the current device version of the second software module to be replaced with the available version of the second software module when the first software module version mismatch exists.   
     
     
         16 . The system of  claim 15 , comprising:
 a transmission component configured to communicate a metadata set to a management entity,   a reception component configured to receive a version list in response to the communication of the metadata set,   where the metadata set comprises metadata that pertains to the first software module and the second software module,   where the version list comprises metadata that indicates the available version of the first software module and the available version of the second software module, and   where the update component employs the version list to manage the update.   
     
     
         17 . The system of  claim 15 , comprising:
 a transmission component configured to communicate a metadata set to a management entity,   a reception component configured to receive an update file in response to the communication of the metadata set,   where the update file comprises the available version of the first software module when the first software module version mismatch exists,   where the update file comprises the available version of the second software module when the second software module version mismatch exists, and   where the update component employs the update file to manage the update.   
     
     
         18 . The system of  claim 14 , comprising:
 a decision component configured to make a decision on if the update should occur,   where the update component manages the update by causing the update to occur when the decision is that the update should occur.   
     
     
         19 . The system of  claim 18 ,
 where the decision is based, at least in part, on a network connection status of the device.   
     
     
         20 . The system of  claim 18 ,
 where the decision is based, at least in part, on an active performance function of the device.