Memory device with secure boot updates and self recovery
US-2024406008-A1 · Dec 5, 2024 · US
US9298649B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9298649-B2 |
| Application number | US-201414291294-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 30, 2014 |
| Priority date | May 30, 2014 |
| Publication date | Mar 29, 2016 |
| Grant date | Mar 29, 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.
A system includes a processor configured to detect that a vehicle module update has been performed. The processor is further configured to create an identifier associated with a module that indicates an updated status and for each module having an identifier indicating an updated status associated therewith, requesting subscription to a topic, corresponding to the updated module, and specific to an individual vehicle, from a remote server.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a processor configured to: detect that a vehicle module update has been performed; create an identifier associated with a module that indicates an updated status; and for each module having an identifier indicating an updated status associated therewith, requesting subscription to a topic, corresponding to the updated module, and specific to an individual vehicle, from a remote server. 2. The system of claim 1 , wherein the module is a software module. 3. The system of claim 1 , wherein the module is a firmware module. 4. The system of claim 1 , wherein the topic is identified by the same name as the identifier. 5. The system of claim 1 , wherein the processor is further configured to receive confirmation from the remote server that the subscription request was successful. 6. The system of claim 1 , wherein the identifier comprises a previous identifier name identifying a previous module version, having indicia appended thereto indicating the updated status. 7. A system comprising: a processor configured to: receive a request from a vehicle computer to subscribe to a topic associated with an updated vehicle module; determine that the topic does not already exist for the specific requesting vehicle; and based on receipt of the request and the determination that the topic does not exist, create a vehicle-specific topic corresponding to the updated module. 8. The system of claim 7 , wherein the vehicle module is a software module. 9. The system of claim 7 , wherein the vehicle module is a firmware module. 10. The system of claim 7 , wherein the topic is named based on an identifier associated with the updated module. 11. The system of claim 10 , wherein the identifier comprises a previous identifier name identifying a previous module version, having indicia appended thereto indicating the updated status. 12. The system of claim 7 , wherein the topic identifies a current module version for a specific vehicle. 13. The system of claim 12 , wherein the topic name identifies the current module version. 14. A computer-implemented method comprising: receiving a request from a vehicle computer to subscribe to a topic associated with an updated vehicle module; determining, via a computer, that the topic does not already exist for the specific requesting vehicle; and based on receipt of the request and the determination that the topic does not exist, creating a vehicle-specific topic corresponding to the updated module. 15. The method of claim 14 , wherein the vehicle module is a software module. 16. The method of claim 14 , wherein the vehicle module is a firmware module. 17. The method of claim 16 , wherein the topic is named based on an identifier associated with the updated module. 18. The method of claim 17 , wherein the identifier comprises a previous identifier name identifying a previous module version, having indicia appended thereto indicating the updated status. 19. The method of claim 14 , wherein the topic identifies a current module version for a specific vehicle. 20. The method of claim 19 , wherein the topic name identifies the current module version.
Updates (security arrangements therefor G06F21/57) · CPC title
Handling requests for interconnection or transfer · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
electric {constitutive elements} · CPC title
Push-based network services · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.