IP Library Granted Patent US 12,192,383
Granted Patent B2
US 12,192,383 · App. 18/318,230 · Granted Jan 7, 2025

Method and system for establishing trust for a cybersecurity posture of a V2X entity

Inventors: Stephen John Barrett (Haywards Heath, GB); Nicholas James Russell (Newbury, GB); John Octavius Goyo (Acton, CA)
Assignee: BlackBerry Limited
H04L9/3268G06F21/64H04L9/3213H04L63/1425
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,192,383
App. No.
18/318,230
Granted
Jan 7, 2025
Kind
B2
Abstract

A method at an Intelligent Transportation System (ITS) Transmitting Entity, the method including: generating an ITS message; augmenting the ITS message with an Integrity Report generated by an integrity detection function at the ITS Transmitting Entity to create an augmented ITS message; signing the augmented ITS message with an Authorization Certificate or Ticket, the Authorization Certificate or Ticket including an assurance indication from an Audit Certificate Authority for the integrity detection function; and sending the signed, augmented ITS message to an ITS Receiving Entity.

Claims (36)

1. A method at an Intelligent Transportation System (ITS) Receiving Entity, the method comprising:

receiving an ITS message at the ITS Receiving Entity from an ITS Transmitting Entity;

determining whether the ITS message comprises an Integrity Report regarding a cybersecurity posture of the ITS Transmitting Entity, the Integrity Report comprising an integrity check of the ITS Transmitting Entity generated by an integrity detection function checking the cybersecurity posture at the ITS Transmitting Entity;

when the ITS message comprises the Integrity Report, determining whether the Integrity report indicates anomalies in the cybersecurity posture of the ITS Transmitting Entity exist; and

based on the ITS message not containing the Integrity Report or the Integrity Report indicating anomalies, performing a mitigating action at the ITS Receiving Entity.

2. The method of claim 1 , wherein the ITS message is signed with an Authorization Certificate or Ticket, the Authorization Certificate or Ticket including an assurance indication from an Audit Certificate Authority for the integrity detection function at the ITS Transmitting Entity.

3. The method of claim 2 , wherein the assurance indication from the Audit Certificate Authority is within a field of the Authorization Certificate or Ticket.

4. The method of claim 1 , wherein the Integrity Report is Boolean indicating whether an anomaly was detected.

5. The method of claim 1 , wherein the Integrity Report includes a level of an anomaly detected.

6. The method of claim 5 , wherein the mitigating action includes a degree of reaction based on the level of the anomaly detected.

7. The method of claim 1 , further comprising:

when the ITS message contains the Integrity Report and provides no indicating of anomalies, performing an action with no mitigation.

8. The method of claim 1 , wherein an action associated with the ITS message comprises applying brakes of a vehicle with a first force, and wherein the mitigating action comprises at least one of: applying brakes with a second force, the second force being less than the first force; pre-charging a braking system; or not applying brakes until corroborating evidence is received.

9. An Intelligent Transportation System (ITS) Receiving Entity,

the ITS Receiving Entity comprising:

a processor;

a memory; and

a communications subsystem,

wherein the memory storing instructions when executed by the processor cause the ITS Receiving Entity to:

receive an ITS message at the ITS Receiving Entity from an ITS Transmitting Entity using the communications subsystem;

determine whether the ITS message comprises an Integrity Report regarding a cybersecurity posture of the ITS Transmitting Entity, the Integrity Report comprising an integrity check of the ITS Transmitting Entity generated by an integrity detection function checking the cybersecurity posture at the ITS Transmitting Entity;

when the ITS message comprises the Integrity Report, determine whether the Integrity report indicates anomalies in the cybersecurity posture of the ITS Transmitting Entity exist; and

based on the ITS message not containing the Integrity Report or the Integrity Report indicating anomalies, perform a mitigating action at the ITS Receiving Entity.

10. The ITS Receiving Entity of claim 9 , wherein the ITS message is signed with an Authorization Certificate or Ticket, the Authorization Certificate or Ticket including an assurance indication from an Audit Certificate Authority for the integrity detection function at the ITS Transmitting Entity.

11. The ITS Receiving Entity of claim 10 , wherein the assurance indication from the Audit Certificate Authority is within a field of the Authorization Certificate or Ticket.

12. The ITS Receiving Entity of claim 9 , wherein the Integrity Report is Boolean indicating whether an anomaly was detected.

13. The ITS Receiving Entity of claim 9 , wherein the Integrity Report includes a level of an anomaly detected.

14. The ITS Receiving Entity of claim 13 , wherein the mitigating action includes a degree of reaction based on the level of the anomaly detected.

15. The ITS Receiving Entity of claim 9 , wherein the ITS Receiving Entity is further configured to:

when the ITS message contains the Integrity Report and provides no indicating of anomalies, perform an action with no mitigation.

16. The ITS Receiving Entity of claim 9 , wherein an action associated with the ITS message comprises applying brakes of a vehicle, and wherein the mitigating action comprises at least one of: applying brakes of a vehicle with a first force, and wherein the mitigating action comprises at least one of: applying brakes with a second force, the second force being less than the first force; pre-charging a braking system; or not applying brakes until corroborating evidence is received.

17. A non-transitory computer readable medium for storing instruction code which, when executed by a processor of an Intelligent Transportation System (ITS) Receiving Entity cause the ITS Receiving Entity to:

receive an ITS message at the ITS Receiving Entity from an ITS Transmitting Entity;

determine whether the ITS message comprises an Integrity Report regarding a cybersecurity posture of the ITS Transmitting Entity, the Integrity Report comprising an integrity check of the ITS Transmitting Entity generated by an integrity detection function checking the cybersecurity posture at the ITS Transmitting Entity;

when the ITS message comprises the Integrity Report, determine whether the Integrity report indicates anomalies in the cybersecurity posture of the ITS Transmitting Entity exist; and

based on the ITS message not containing the Integrity Report or the Integrity Report indicating anomalies, perform a mitigating action at the ITS Receiving Entity.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2023
From: RUSSELL, NICHOLAS JAMES; BARRETT, STEPHEN JOHN
To: BLACKBERRY UK LIMITED
Reel/Frame 063655/0692 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2023
From: GOYO, JOHN OCTAVIUS
To: BLACKBERRY LIMITED
Reel/Frame 063655/0839 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2023
From: BLACKBERRY UK LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 063656/0930 →
Continuity (2)
Continuation 16861991 · Apr 29, 2020
Related Publication 20230291578A1 · Sep 14, 2023
References Cited (32)
US 9805601B1 · Fields · 2017 [cited by applicant]
US 20130117558A1 · Metke · 2013 [cited by applicant]
US 20150019067A1 · Chakravarty · 2015 [cited by applicant]
US 20160373473A1 · Truong · 2016 [cited by applicant]
US 20170244565A1 · Bronk · 2017 [cited by examiner]
US 20180109538A1 · Kumar et al. · 2018 [cited by applicant]
US 20180288069A1 · Burchard · 2018 [cited by applicant]
US 20180295147A1 · Haga · 2018 [cited by examiner]
US 20180322785A1 · Jerichow · 2018 [cited by applicant]
US 20190297499A1 · Hawkes · 2019 [cited by applicant]
US 20190312738A1 · Barrett et al. · 2019 [cited by applicant]
US 20190312896A1 · Petit · 2019 [cited by applicant]
US 20190379683A1 · Overby · 2019 [cited by applicant]
US 20200025575A1 · Weissman · 2020 [cited by applicant]
US 20200045552A1 · Kim · 2020 [cited by applicant]
US 20200051434A1 · Sasaki · 2020 [cited by examiner]
US 20200205006A1 · Denis · 2020 [cited by examiner]
US 20200211368A1 · Ueno · 2020 [cited by applicant]
US 20200226274A1 · Juliato · 2020 [cited by applicant]
US 20210227356A1 · Hwang · 2021 [cited by applicant]
US 20210281986A1 · Zhu · 2021 [cited by applicant]
WO 2016048177A1 · 2016 [cited by applicant]
European Patent Office, Extended European Search Report (EESR) for Application No. 21796127.5, dated Sep. 19, 2023. [cited by applicant]
IEEE 1609.2, “EEE Standard for WAVE—Security Services for Applications and Management Messages—Consolidated Draft of IEEE 1609.2-2016 with Amendments Specified in 1609.2a / D8 and 1609.2b / D3” Dec. 2016. [cited by applicant]
ETSI Technical Specification (TS) 103 097 “TS; Security; Security header and certificate formats” v1.3.1, Oct. 2017. [cited by applicant]
ETSI Technical Specification (TS) 102 941 “ITS; Security; Trust and Privacy Management”, v1.2.1, May 2018. [cited by applicant]
ETSI Technical Specification (TS) 102 904 “Intelligent Transport Systems (ITS) Security, ITS Communications Security Architecture and Security Management”, v. 1.2.1, Nov. 2016. [cited by applicant]
ETSI Technical Specification (TS) 102 940 “Intelligent Transport Systems (ITS); Security; ITS communications security architecture and security management” v1.3.1, Apr. 2019. [cited by applicant]
Car2Car Communication Consortium, “Protection profile V2X Hardware security module”, Aug. 2018. [cited by applicant]
IETF Network Endpoint Assessment, “Request for Comment (RFC) 5209 Network Endpoint Assessment (NEA): Overview and Requirements” Jun. 2008. [cited by applicant]
Preserve, “PREparing SEcuRe VEhicle-to-X Communication Systems Deliverable 5.4”, Jan. 31, 2016. [cited by applicant]
Canadian Intellectual Property Office (CIPO): Office Action for Application No. 3,171,847, dated Aug. 27, 2024, 4 pages. [cited by applicant]