Memory device with secure boot updates and self recovery
US-2024406008-A1 · Dec 5, 2024 · US
US9400644B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9400644-B2 |
| Application number | US-201514836954-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 26, 2015 |
| Priority date | Sep 30, 2009 |
| Publication date | Jul 26, 2016 |
| Grant date | Jul 26, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Software receives a message from a client device requesting an update check for an app deployed on the client device. The message includes a version number for the app. The software determines that a count of messages requesting an update check for the app exceeds a specified number. The software obtains an executable for the app from an app database, using the received version number. The software generates a dependency analysis by scanning the executable. The dependency analysis includes a version number for at least one dependent code module. The software determines that the app is updatable by comparing the version number in the dependency analysis with a version number for source code for the dependent code module. The software creates an updated app using newer source code for the dependent code module, using a developer specification as to compilation type, and transmits the updated app to the client device.
Opening claim text (preview).
What is claimed is: 1. A method, comprising operations of: receiving a message from a client device requesting an update check for an app deployed on the client device, wherein the message includes a version number for the app; determining that a count of messages requesting an update check for the app exceeds a specified number; obtaining an executable for the app from an app database, using the received version number; generating a dependency analysis by scanning the executable to determine a dependency graph topology for code modules in the app, wherein the dependency analysis includes a version number for at least one dependent code module; obtaining a compatibility specification for a current version of the app and updated module versions stored in the code database; determining that the app is updatable by comparing the version number in the dependency analysis with a version number for source code for the dependent code module; creating an updated app using newer source code for the dependent code module, using the obtained compatibility specification and a developer specification as to compilation type; and transmitting the updated app to the client device, wherein each operation of the method is performed by one or more processors. 2. The method of claim 1 , wherein the version number for the source code is stored in a code database. 3. The method of claim 1 , wherein a dependency-walker utility is used to determine the dependency graph topology. 4. The method of claim 1 , wherein the app allows a user of the client device to play a multi-player online game. 5. The method of claim 1 , wherein the app includes a call to an application programming interface (API) for a social-networking service. 6. The method of claim 5 , wherein the call obtains user profile data. 7. The method of claim 5 , wherein the call modifies a news feed. 8. The method of claim 1 , wherein the compilation type is ahead-of-runtime. 9. The method of claim 1 , wherein the compilation type is on-the-fly. 10. One or more computer-readable media that are non-transitory and that store instructions, which when executed by a processor, perform the following operations: receive a message from a client device requesting an update check for an app deployed on the client device, wherein the message includes a version number for the app; determine that a count of messages requesting an update check for the app exceeds a specified number; obtain an executable for the app from an app database, using the received version number; generate a dependency analysis by scanning the executable to determine a dependency graph topology for code modules in the app, wherein the dependency analysis includes a version number for at least one dependent code module; obtain a compatibility specification for a current version of the app and updated module versions stored in the code database; determine that the app is updatable by comparing the version number in the dependency analysis with a version number for source code for the dependent code module; create an updated app using newer source code for the dependent code module, using the obtained compatibility specification; and transmit the updated app to the client device. 11. The computer-readable media of claim 10 , wherein the version number for the source code is stored in a code database. 12. The computer-readable media of claim 10 , wherein a dependency-walker utility is used to determine the dependency graph topology. 13. The computer-readable media of claim 10 , wherein the app allows a user of the client device to play a multi-player online game. 14. The computer-readable media of claim 10 , wherein the app includes a call to an application programming interface (API) for a social-networking service. 15. The computer-readable media of claim 14 , wherein the call obtains user profile data. 16. The computer-readable media of claim 14 , wherein the call modifies a news feed. 17. The computer-readable media of claim 10 , wherein the compilation type is ahead-of-runtime. 18. The computer-readable media of claim 10 , wherein the compilation type is on-the-fly. 19. A method, comprising operations of: receiving a message from a client device requesting an update check for an app deployed on the client device, wherein the message includes a version number for the app and wherein the app allows a user of the client device to play a multi-player online game; determining that a count of messages requesting an update check for the app exceeds a specified number; obtaining an executable for the app from an app database, using the received version number; generating a dependency analysis by scanning the executable to determine a dependency graph topology for code modules in the app, wherein the dependency analysis includes a version number for at least one dependent code module; obtaining a compatibility specification for a current version of the app and updated module versions stored in the code database; determining that the app is updatable by comparing the version number in the dependency analysis with a version number for source code for the dependent code module, wherein the version number for the source code is stored in a code database; creating an updated app using newer source code for the dependent code module, using the obtained compatibility specification; and transmitting the updated app to the client device, wherein each operation of the method is performed by one or more processors. 20. The method of claim 19 , wherein the app includes a call to an application programming interface (API) for a social-networking service.
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Checking; Contextual analysis · CPC title
Indexing; Web crawling techniques · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.