Systems and methods for reliable software update in a network of moving things including, for example, autonomous vehicles
US-2018052681-A1 · Feb 22, 2018 · US
US11537383B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11537383-B2 |
| Application number | US-202017069600-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 13, 2020 |
| Priority date | Oct 13, 2020 |
| Publication date | Dec 27, 2022 |
| Grant date | Dec 27, 2022 |
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.
Systems, methods, and computer-readable media are disclosed for a systems and methods for improved smart infrastructure data transfer. An example method may involve identifying that a software update is available for a smart infrastructure system. The example method may also involve determining, by a processor of the smart infrastructure system and using a signal strength between a first vehicle and the smart infrastructure system, that the first vehicle is within a threshold range of the smart infrastructure system. The example method may also involve establishing, by the smart infrastructure system, a first ad-hoc peer-to-peer communication link with the first vehicle. The example method may also involve sending, to the vehicle, a request for the software update. The example method may also involve receiving, from the vehicle, at least a first portion of the software update that is transferred using the first ad-hoc peer-to-peer communication link.
Opening claim text (preview).
What which is claimed is: 1. A method comprising: identifying that a software update is available for a smart infrastructure system located relative to a fixed location; determining, by a processor of the smart infrastructure system and using a signal strength between a first vehicle and the smart infrastructure system, that the first vehicle is within a threshold range of the fixed location of the smart infrastructure system; establishing, by the smart infrastructure system, a first ad-hoc peer-to-peer communication link with the first vehicle based on a calculation of a length of time that the first vehicle will remain in communication range of the smart infrastructure system and a calculation of an amount of the software update that can be transferred during the calculated length of time; sending, to the first vehicle, a request for the software update; and receiving, by the smart infrastructure system and from the first vehicle, at least a first portion of the software update that is transferred using the first ad-hoc peer-to-peer communication link. 2. The method of claim 1 , further comprising: determining that a second vehicle is within the threshold range of the smart infrastructure system; establishing a second ad-hoc peer-to-peer communication link with the second vehicle; sending, to the second vehicle, a second request for a second portion of the software update; and receiving, from the second vehicle, the second portion of the software update. 3. The method of claim 1 , further comprising: identifying that a second software update is available for the smart infrastructure system; determining, by the processor of the smart infrastructure system and using a signal strength between a first mobile entity and the smart infrastructure system, that the first mobile entity is within a mobile threshold range of the smart infrastructure system, wherein the first mobile entity is different than the first vehicle; establishing a first mobile ad-hoc peer-to-peer communication link with the first mobile entity; sending, to the first mobile entity, a mobile request for the software update; and receiving, from the first mobile entity, at least a first portion of the software update that is transferred using the first mobile ad-hoc peer-to-peer communication link. 4. The method of claim 1 , wherein sending, to the first vehicle, the request for at least the first portion of the software update is further based on a determination that the smart infrastructure system is not connected to a network. 5. The method of claim 1 , wherein the first portion of the software update is received by a first device included within the smart infrastructure system, wherein the first device comprises at least one of a camera, a light, a sign, and a road sensor, and wherein the method further comprises: sending, by the first device, the first portion of the software update to a second device included within the smart infrastructure system. 6. The method of claim 5 , further comprising: establishing an ad-hoc peer-to-peer communication link between the first device and a third device included within a second smart infrastructure system; and sending, by the first device or the second device, the first portion of the software update to the third device, wherein the smart infrastructure system is different than the second smart infrastructure system. 7. The method of claim 1 , further comprising: determining that the first vehicle is stopped within the threshold range of the smart infrastructure system. 8. The method of claim 1 , wherein establishing an ad-hoc peer-to-peer communication link with the first vehicle is based on a determination that the first vehicle will remain within a communication range of the smart infrastructure system for a longer period of a time than a second vehicle. 9. The method of claim 1 , further comprising: ending the first ad-hoc peer-to-peer communication link with the first vehicle after receiving the first portion of the software update. 10. A system comprising: a processor; and a memory storing computer-executable instructions, that when executed by the processor, cause the processor to: identify that a software update is available for a smart infrastructure system; determine, using a signal strength between a first vehicle and the smart infrastructure system, that the first vehicle is within a threshold distance to a fixed location of the smart infrastructure system; establish a first ad-hoc peer-to-peer communication link with the first vehicle based on a calculation of a length of time that the first vehicle will remain in communication range of the smart infrastructure system, and a calculation of an amount of the software update that can be transferred during the calculated length of time; send, to the first vehicle, a request for the software update; and receive, by the smart infrastructure system and from the first vehicle, at least a first portion of the software update that is transferred using the first ad-hoc peer-to-peer communication link. 11. The system of claim 10 , wherein the computer-executable instructions further cause the processor to: ending the first ad-hoc peer-to-peer communication link with the first vehicle after receiving the first portion of the software update. 12. The system of claim 10 , wherein the computer-executable instructions further cause the processor to: determine that a second vehicle is within a geographical region defined by the threshold distance of the smart infrastructure system; establish a second ad-hoc peer-to-peer communication link with the second vehicle; send, to the second vehicle, a second request for a second portion of the software update; and receive, from the second vehicle, the second portion of the software update. 13. The system of claim 10 , wherein the computer-executable instructions further cause the processor to: identify that a second software update is available for the smart infrastructure system; determine, by the processor of the smart infrastructure system and using a mobile signal strength between a first mobile entity and the smart infrastructure system, that the first mobile entity is within a mobile threshold range of the smart infrastructure system, wherein the first mobile entity is different than the first vehicle; establish a first mobile ad-hoc peer-to-peer communication link with the first mobile entity; send, to the first mobile entity, a request for the software update; and receive, from the first mobile entity, at least a first portion of the software update that is transferred using the first ad-hoc peer-to-peer communication link. 14. The system of claim 10 , wherein sending, to the first vehicle, the request for at least the first portion of the software update is further based on a determination that the smart infrastructure system is not connected to a network. 15. The system of claim 10 , wherein the first portion of the software update is received by a first device included within the smart infrastructure system, wherein the first device comprises at least one of a light and a sign, and wherein the computer-executable instructions further cause the processor to: send, by the first device, the first portion of the software update to a second device included within the smart infrastructure system. 16. The system of claim 15 , wherein the computer-executable instructions further cause the processor to: establish an ad-hoc peer-to-peer communication link between the first device and a third device included within a second smart infrastructure sys
Updates (security arrangements therefor G06F21/57) · CPC title
specially adapted for the location of the user terminal · CPC title
Peer-to-peer [P2P] networks · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Systems supporting electrical power generation, transmission or distribution · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.