US 12,217,323 B2
Vehicle data jurisdiction management
Roland Mesde, Cupertino, CA (US); Alex Bessonov, San Jose, CA (US); Kyle Daniel Halbach, Berlin (DE); Nitin Giri, Bothell, WA (US); Edwin Ricardo Mendez Rodriguez, Seattle, WA (US); and Matthew Jonathan Narksusook, Auburn, WA (US)
Assigned to Amazon Technologies, Inc., Seattle, WA (US)
Filed by Amazon Technologies, Inc., Seattle, WA (US)
Filed on Mar. 31, 2022, as Appl. No. 17/710,551.
Prior Publication US 2023/0316445 A1, Oct. 5, 2023
Int. Cl. G06Q 50/26 (2024.01); B60W 50/04 (2006.01); G06F 16/23 (2019.01); H04W 4/021 (2018.01); H04W 12/64 (2021.01)
CPC G06Q 50/265 (2013.01) [B60W 50/045 (2013.01); G06F 16/2365 (2019.01); H04W 4/021 (2013.01); H04W 12/64 (2021.01)] 20 Claims
OG exemplary drawing
 
1. A system, comprising:
one or more computing devices configured to implement a data jurisdiction management system configured to:
detect, based on received vehicle information, a jurisdiction change event for a vehicle, wherein vehicle data for the vehicle is stored in a first jurisdiction;
determine, using the data jurisdiction management system, whether a conflict exists between a jurisdiction rule of the first jurisdiction and a jurisdiction rule of a second jurisdiction;
determine, based on the determination of whether the conflict exists, and based on a set of jurisdiction rules comprising the jurisdiction rule of the first jurisdiction and the jurisdiction rule of the second jurisdiction, one or more portions of the vehicle data stored for the vehicle to be deleted, moved, or retained, wherein the set of jurisdiction rules are based on data storage requirements for the vehicle; and
cause the one or more portions of the vehicle data stored in the first jurisdiction to be deleted from the first jurisdiction, moved to the second jurisdiction, or retained in the first jurisdiction based on the determination.