Security certificate management and misbehavior vehicle reporting in vehicle-to-everything (V2X) communication
US-11445362-B2 · Sep 13, 2022 · US
US12197903B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12197903-B2 |
| Application number | US-202017437313-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 6, 2020 |
| Priority date | Mar 8, 2019 |
| Publication date | Jan 14, 2025 |
| Grant date | Jan 14, 2025 |
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.
The present disclosure relates to a verification controller for a vehicle, configured to receive data being sent over a data bus within the vehicle, detect software update data being sent to a control unit within the vehicle over the data bus, determine from the software update data a first security characteristic associated with an authentic version of the software update, generate a second security characteristic in dependence on the received software update data, determine if the second security characteristic is consistent with the first security characteristic, and output a first control signal for the control unit, the first control signal enabling installation of the software update on the control unit in dependence on the second security characteristic being consistent with the first security characteristic.
Opening claim text (preview).
The invention claimed is: 1. A verification controller, embedded within a vehicle and comprising at least one processor that, when executed, the verification controller is configured to: verify authenticity of received software for installation on at least one of a plurality of control units within the vehicle, the plurality of control units being separate to the verification module; detect software update data on a data bus of the vehicle, the software update data comprising update software being sent to any of the plurality of control units within the vehicle over a data bus, the control unit being separate to the verification controller that is used for checking the authenticity of the received software, and upon detection of software update data comprising update software being sent to at least one of the plurality of vehicle control units: determine from the detected software update data a first security characteristic associated with an authentic version of the software; generate a second security characteristic in dependence on the received software update data; determine if the second security characteristic is consistent with the first security characteristic; and output a first control signal for the at least one of the plurality of vehicle control units, the first control signal enabling installation of the received software on the at least one of the plurality of vehicle control units in dependence on the second security characteristic being consistent with the first security characteristic. 2. The verification controller of claim 1 , wherein the at least one electronic processor has an electrical input for receiving data being sent over the data bus; and wherein the verification controller comprises at least one memory device electrically coupled to the at least one electronic processor and having instructions stored therein; and wherein the at least one electronic processor is configured to access the at least one memory device and execute the instructions thereon so as to: detect software update data comprising update software being sent to any of the plurality of vehicle control units within the vehicle over the data bus; determine from the software update data a first security characteristic associated with an authentic version of the software; generate a second security characteristic in dependence on the received software update data; determine if the second security characteristic is consistent with the first security characteristic; and output a first control signal for the at least one of the plurality of vehicle control units, the first control signal enabling installation of the software on the at least one of the plurality of vehicle control units in dependence on the second security characteristic being consistent with the first security characteristic. 3. The verification controller of claim 1 , wherein the verification controller is configured to receive data being sent over a plurality of data buses within the vehicle, each data bus having at least one of the plurality of vehicle control units operatively connected there to. 4. The verification controller of claim 1 , wherein the verification controller is comprised at a gateway control module. 5. The verification controller of claim 1 , wherein the verification controller is arranged to output an alert signal in dependence on the second security characteristic being inconsistent with the first security characteristic. 6. The verification controller of claim 1 , wherein the verification controller is configured to output a second control signal preventing installation of the software on the at least one of the plurality of vehicle control units in dependence on the second security characteristic being inconsistent with the first security characteristic. 7. The verification controller of claim 1 , wherein the verification controller is arranged to output the first control signal in dependence on receipt of a request from the at least one of the plurality of vehicle control units. 8. A vehicle comprising the verification controller of claim 1 . 9. The verification controller of claim 1 , wherein at least one of the first security characteristic and the second security characteristic is one of a cryptograph hash or message authentication code (MAC). 10. The verification controller of claim 9 , wherein the authentic version of the software and the at least one security characteristic are encrypted using cryptographic protocols. 11. A method for verifying the authenticity of received software for installation on a control unit within a vehicle, using a verification module embedded within the vehicle, the method comprising: verifying authenticity of received software for installation on at least one of a plurality of control units within the vehicle, the plurality of control units being separate to the verification module; detecting, using the verification module, software update data on a data bus of the vehicle, the software update data comprising update software being sent to any of the plurality of vehicle control units within the vehicle the control unit being separate to the verification controller that is used for checking the authenticity of the received software, and upon detection of software update data comprising update software being sent to at least one of the plurality of vehicle control units: determining, using the verification module, from the detected software update data a first security characteristic associated with an authentic version of the software; generating, using the verification module, a second security characteristic in dependence on the received software update data; determining, using the verification module, if the second security characteristic is consistent with the first security characteristic; and outputting, from the verification module, a first control signal for the at least one of the plurality of vehicle control units, the first control signal enabling installation of the software on the at least one of the plurality of vehicle control units in dependence on the second security characteristic being consistent with the first security characteristic. 12. A vehicle having stored therein computer software that, when executed, is arranged to perform the method of claim 11 . 13. A non-transitory, computer-readable storage medium storing instructions thereon that, when executed by one or more electronic processors, causes the one or more electronic processors to carry out the method of claim 11 . 14. The method of claim 11 , wherein at least one of the first security characteristic and the second security characteristic is one of a cryptograph hash or message authentication code (MAC). 15. The method of claim 14 , wherein the authentic version of the software and the at least one security characteristic are encrypted using cryptographic protocols. 16. A verification controller for a vehicle, embedded within a vehicle and comprising at least one processor that, when executed, the verification controller is configured to: detect software update data on a data bus of the vehicle, the software update data comprising update software being sent to a control unit within the vehicle, the control unit being separate to the verification controller that is used for checking the authenticity of the update software; determine from the detected software update data a first security characteristic associated with an authentic version of the software; generate a second security characteristic in dependence on the received software update data; determine if the second security c
Test or assess software · CPC title
Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities · CPC title
for transmission of signals between vehicle parts or subsystems · CPC title
related to technical updates when adding new parts or software · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.