IP Library Granted Patent US 12,395,816
Granted Patent B2
US 12,395,816 · App. 18/680,181 · Granted Aug 19, 2025

Method and system for vehicle location tracking using V2X communication

Inventors: Michaela Vanderveen (Tracy, CA); Nicholas James Russell (Newbury, GB)
Assignee: Malikie Innovations Limited
H04W4/029H04W4/06H04W4/40H04W12/03H04W12/80
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,395,816
App. No.
18/680,181
Granted
Aug 19, 2025
Kind
B2
Abstract

A method at a network element within a Vehicle to Everything (V2X) Communications Domain, the method including receiving a tracking request at the network element for a target vehicle, the tracking request including identifying information for the target vehicle; creating a target vehicle list based on the tracking request; distributing the target vehicle list to at least one V2X endpoint; receiving at least one sighting report from the at least one V2X endpoint; and forwarding the at least one sighting report to a second network element.

Claims (31)

1. A method for controlling a target vehicle, comprising:

receiving, at the target vehicle, a target vehicle list from a Vehicle to Everything (V2X) Communications Domain;

determining, at the target vehicle, whether the target vehicle list includes identifying information of the target vehicle; and

taking one or more actions, at the target vehicle, in response to determining that the target vehicle list includes identifying information of the target vehicle.

2. The method of claim 1 , wherein the one or more actions include sending additional information associated with the target vehicle.

3. The method of claim 2 , wherein the additional information is sent via a different domain than the Vehicle to Everything (V2X) Communications Domain from which the target vehicle list was received.

4. The method of claim 1 , wherein the one or more actions include enabling or disabling systems or modes of the target vehicle or taking physical action by the target vehicle.

5. The method of claim 1 , wherein the target vehicle list is based on a tracking request from a law enforcement monitoring facility for target vehicles.

6. The method of claim 1 , wherein the target vehicle list includes linkage values or hashed values of certificates issued to the target vehicle.

7. The method of claim 1 , wherein the target vehicle list is encrypted, and wherein the target vehicle and a roadside unit have decryption keys.

8. A vehicle for being controlled as a target vehicle, comprising:

a memory storing instructions;

one or more processors, upon execution of the instructions, configured to:

receive, at the vehicle, a target vehicle list from a Vehicle to Everything (V2X) Communications Domain;

determine, at the vehicle, whether the target vehicle list includes identifying information of the vehicle; and

take one or more actions, at the vehicle, in response to determining that the target vehicle list includes identifying information of the vehicle, which is a target vehicle.

9. The vehicle of claim 8 , wherein the one or more actions include the one or more processors further configured to send additional information associated with the vehicle.

10. The vehicle of claim 9 , wherein the additional information is sent via a different domain than the Vehicle to Everything (V2X) Communications Domain from which the target vehicle list was received.

11. The vehicle of claim 8 , wherein the one or more actions include the one or more processors further configured to enable or disable certain systems or modes of the vehicle or to take physical action by the vehicle.

12. The vehicle of claim 8 , wherein the target vehicle list is based on a tracking request from a law enforcement monitoring facility for target vehicles.

13. The vehicle of claim 8 , wherein the target vehicle list includes linkage values or hashed values of certificates issued to the vehicle.

14. The vehicle of claim 8 , wherein the target vehicle list is encrypted, and wherein the vehicle and a roadside unit have decryption keys.

15. A non-transitory computer readable medium for storing instruction code, which, when executed by one or more processor of a vehicle cause the vehicle to:

receive, at the vehicle, a target vehicle list from a Vehicle to Everything (V2X) Communications Domain;

determine, at the vehicle, whether the target vehicle list includes identifying information of the vehicle; and

take one or more actions, at the vehicle, in response to determining that the target vehicle list includes identifying information of the vehicle, which is a target vehicle.

16. The non-transitory computer readable medium of claim 15 , wherein the one or more actions include the one or more processors further configured to cause the vehicle to send additional information associated with the vehicle.

17. The non-transitory computer readable medium of claim 16 , wherein the additional information is sent via a different domain than the Vehicle to Everything (V2X) Communications Domain from which the target vehicle list was received.

18. The non-transitory computer readable medium of claim 15 , wherein the one or more actions include the one or more processors further configured to cause the vehicle to enable or disable certain systems or modes of the vehicle or to take physical action by the vehicle.

19. The non-transitory computer readable medium of claim 15 , wherein the target vehicle list is based on a tracking request from a law enforcement monitoring facility for target vehicles.

20. The non-transitory computer readable medium of claim 15 , wherein the target vehicle list includes linkage values or hashed values of certificates issued to the vehicle.

Continuity (4)
Continuation 18177997 · Mar 3, 2023
Continuation 17358482 · Jun 25, 2021
Continuation 16403138 · May 3, 2019
Related Publication 20240323651A1 · Sep 26, 2024
References Cited (60)
US 10089869B1 · Makled · 2018 [cited by examiner]
US 10187766B2 · Lee et al. · 2019 [cited by applicant]
US 10270899B1 · Merjanian et al. · 2019 [cited by applicant]
US 10410516B1 · Anderson et al. · 2019 [cited by applicant]
US 11076262B2 · Vanderveen et al. · 2021 [cited by applicant]
US 11632654B2 · Vanderveen et al. · 2023 [cited by applicant]
US 12010589B2 · Vanderveen et al. · 2024 [cited by applicant]
US 20120116640A1 · Oh · 2012 [cited by examiner]
US 20160358031A1 · Miller · 2016 [cited by examiner]
US 20160363935A1 · Shuster et al. · 2016 [cited by applicant]
US 20190051142A1 · Wiles · 2019 [cited by applicant]
US 20190075447A1 · Lee et al. · 2019 [cited by applicant]
US 20190089547A1 · Simplicio, Jr. et al. · 2019 [cited by applicant]
US 20190245705A1 · Kumar et al. · 2019 [cited by applicant]
US 20190379548A1 · Barrett et al. · 2019 [cited by applicant]
US 20200023797A1 · Volos · 2020 [cited by examiner]
US 20200100048A1 · Wu · 2020 [cited by examiner]
US 20200106624A1 · Russell et al. · 2020 [cited by applicant]
US 20200280842A1 · Liu · 2020 [cited by examiner]
US 20200342753A1 · Arndt · 2020 [cited by examiner]
CN 102598643A · 2012 [cited by applicant]
3GPP TS 23.285 V16.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for V2X Services; Release 16; Mar. 2019; 37 pages. [cited by applicant]
3GPP TS 33.106 V15.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Lawful Interception Requirements; Release 15; Jun. 2018; 22 pages. [cited by applicant]
3GPP TS 33.107 V15.5.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Lawful Interception Architecture and Functions; Release 15; Mar. 2019; 386 pages. [cited by applicant]
3GPP TS 33.108 V15.4.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Handover Interface for Lawful Interception (LI); Release 15; Mar. 2019; 367 pages. [cited by applicant]
3GPP TS 33.126 V15.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security; Lawful Interception Requirements; Release 15; Dec. 2018; 18 pages. [cited by applicant]
3GPP TS 33.127 V15.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security; Lawful Interception (LI) Architecture and Functions; Release 15; Mar. 2019; 55 pages. [cited by applicant]
3GPP TS 33.128 V15.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security; Protocol and Procedures for Lawful Interception (LI); Stage 3; Release 15; Mar. 2019; 63 p… [cited by applicant]
IEEE Standards Association; “IEEE Standard for Wireless Access in Vehicular Environments—Security Services for Applications and Management Messages”; IEEE Std 1609.2-2016; Mar. 1, 2016; 241 pages. [cited by applicant]
IEEE Standards Association; “IEEE Standard for Wireless Access in Vehicular Environments (WAVE)—Networking Services”; IEEE Std 1609.3-2016; Jan. 2016; 160 pages. [cited by applicant]
IEEE Computer Society; “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications—Amendment 6: Wireless Access in Vehicular Environments”; IEEE Std 802.11p—2010; Jul. 15, 2010; 51 pages. [cited by applicant]
Camp LLC Vehicle Safety Communications 5 (VSC5); “Security Credential Management System Proof-of-Concept Implementation: EE Requirements and Specifications Supporting SCMS Software Release 1.2.2”; Nov. 15, 2016; 599 pag… [cited by applicant]
European Commission; Result of C-ITS Platform Phase II—Certificate Policy for Deployment and Operation of European Cooperative Intelligent Transport Systems (C-ITS); Release 1.1; Jun. 2018; 81 pages. [cited by applicant]
European Commission; Result of C-ITS Platform Phase II—Security Policy and Governance Framework for Deployment and Operation of European Cooperative Intelligent Transport Systems (C-ITS); Release 1; Dec. 2017; 36 pages. [cited by applicant]
ETSI EN 302 637-2 V1.3.1; “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service”; Sep. 2014; 44 pages. [cited by applicant]
ETSI EN 302 637-3 V1.2.1; “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service”; Sep. 2014; 73 pages. [cited by applicant]
ETSI EN 302 665 V1.1.1; “Intelligent Transport Systems (ITS); Communications Architecture”; Sep. 2010; 44 pages. [cited by applicant]
ETSI TS 101 331 V1.3.1; “Lawful Interception (LI); Requirements of Law Enforcement Agencies”; Oct. 2009; 30 pages. [cited by applicant]
ETSI TS 102 940 V1.3.1; “Intelligent Transport Systems (ITS); Security; ITS Communications Security Architecture and Security Management”; Apr. 2018; 42 pages. [cited by applicant]
ETSI TS 102 941 V1.2.1; “Intelligent Transport Systems (ITS); Security; Trust and Privacy Management”; May 2018; 71 pages. [cited by applicant]
Santesson, S., et al.; “X.509 Internet Public Key Infrastructure Online Certificate Status Protocol—OCSP”; RFC 6960; Jun. 2013; 41 pages. [cited by applicant]
International Telecommunication Union; “Technical Aspects of Lawful Interception: ITU-T Technology Watch Report #6”; May 2008; 12 pages. [cited by applicant]
International Telecommunication Union; “Series X: Data Networks, Open System Communications and Security—Information Technology—Open Systems Interconnection—The Directory: Public-Key and Attribute Certificate Frameworks… [cited by applicant]
Qualcomm, Incorporated.; “eCall Whitepaper”; Version 1.5; Mar. 2009; 14 pages. [cited by applicant]
Office Action dated Sep. 19, 2019; U.S. Appl. No. 16/403,138, filed May 3, 2019; 34 pages. [cited by applicant]
Office Action dated Mar. 2, 2020; U.S. Appl. No. 16/403,138, filed May 3, 2019; 32 pages. [cited by applicant]
Final Office Action dated Aug. 18, 2020; U.S. Appl. No. 16/403,138, filed May 3, 2019; 34 pages. [cited by applicant]
Advisory Action dated Dec. 23, 2020; U.S. Appl. No. 16/403,138, filed May 3, 2019; 5 pages. [cited by applicant]
Notice of Allowance dated Mar. 26, 2021; U.S. Appl. No. 16/403,138, filed May 3, 2019; 14 pages. [cited by applicant]
Office Action dated May 20, 2022; U.S. Appl. No. 17/358,482, filed Jun. 25, 2021; 27 pages. [cited by applicant]
Final Office Action dated Sep. 9, 2022; U.S. Appl. No. 17/358,482, filed Jun. 25, 2021; 25 pages. [cited by applicant]
Advisory Action dated Nov. 14, 2022; U.S. Appl. No. 17/358,482, filed Jun. 25, 2021; 4 pages. [cited by applicant]
Notice of Allowance dated Dec. 20, 2022; U.S. Appl. No. 17/358,482, filed Jun. 25, 2021; 16 pages. [cited by applicant]
PCT International Search Report & Written Opinion of the International Searching Authority; PCT/US2020/030720; May 27, 2020; 13 pages. [cited by applicant]
European Extended Search Report; Application No. 20803012.2; Sep. 9, 2022; 8 pages. [cited by applicant]
Canadian Office Action; Application No. 3,135,403; Oct. 19, 2023; 3 pages. [cited by applicant]
Chinese Office Action; Application No. 202080033177.5; Jun. 29, 2023; 17 pages. [cited by applicant]
European Examination Report; Application No. 20803012.2; Mar. 13, 2024; 6 pages. [cited by applicant]
Office Action dated Sep. 22, 2023; U.S. Appl. No. 18/177,997, filed Mar. 3, 2023; 40 pages. [cited by applicant]
Notice of Allowance dated Feb. 6, 2024; U.S. Appl. No. 18/177,997, filed Mar. 3, 2023; 13 pages. [cited by applicant]