Abstract: A vehicle data management system and data jurisdiction system manage vehicle data between multiple jurisdictions and enables a set of jurisdiction rules involving rules of various jurisdictions to be applied consistently. The vehicle data jurisdiction system can detect changes in jurisdiction of a vehicle based on various pieces of received vehicle information and applies appropriate jurisdiction rules from a set of jurisdiction rules. Various jurisdictions may have conflicting jurisdiction rules and, in such circumstances, the data jurisdiction system resolves potential conflicts between the rules using a jurisdiction rules resolution workflow. Based on the resolution of the conflict, the data jurisdiction system can migrate data of the vehicle to one or more other jurisdictions, or otherwise implement the correct rules determined by resolving the conflict.

Abstract: A vehicle signal relay system enables a relay agent in a first zone of a vehicle to send sensor signals having a first link-layer communication protocol to a software application deployed on a compute unit in another zone of the vehicle that is connected using another link-layer communication protocol. The vehicle signal relay system allows the software application to identify target relay agents with access to needed sensor signals. The vehicle signal relay system may further enable one way or mutual attestation. The vehicle signal relay system may also allow filters to be applied to the subscribed vehicle sensor signals, and may allow the software application to determine a communication protocol to be used between the software application and the relay agent.

Abstract: A vehicle data management system and data jurisdiction system manage vehicle data between multiple jurisdictions and enables a set of jurisdiction rules involving rules of various jurisdictions to be applied consistently. The vehicle data jurisdiction system can detect changes in jurisdiction of a vehicle based on various pieces of received vehicle information and applies appropriate jurisdiction rules from a set of jurisdiction rules. Various jurisdictions may have conflicting jurisdiction rules and, in such circumstances, the data jurisdiction system resolves potential conflicts between the rules using a jurisdiction rules resolution workflow. Based on the resolution of the conflict, the data jurisdiction system can migrate data of the vehicle to one or more other jurisdictions, or otherwise implement the correct rules determined by resolving the conflict.

Abstract: Systems and methods are disclosed for implementing a vehicle shadow service that includes a vehicle and/or vehicle shadow update mechanism. A vehicle shadow management sub-system of the vehicle shadow service includes or interfaces with an interface configured to receive vehicle state change requests. Received requests are stored in an update queue for a vehicle shadow and a validation processor determines whether the received state change requests are valid before sending a given state change request to a vehicle corresponding to the vehicle shadow. In some embodiments, state change requests may be invalidated due to being rendered moot by subsequently received requests, changes in state of the vehicle, expiration, etc. The corresponding vehicle shadow is then updated when a data stream from the vehicle indicates that the requested state change has in fact been implemented at the vehicle.

Abstract: A vehicle signal relay system enables a relay agent in a first zone of a vehicle to send sensor signals having a first link-layer communication protocol to a software application deployed on a compute unit in another zone of the vehicle that is connected using another link-layer communication protocol. The vehicle signal relay system allows the software application to identify target relay agents with access to needed sensor signals. The vehicle signal relay system may further enable one way or mutual attestation. The vehicle signal relay system may also allow filters to be applied to the subscribed vehicle sensor signals, and may allow the software application to determine a communication protocol to be used between the software application and the relay agent.

Abstract: A vehicle software test environment management system provides a virtual vehicle environment that includes virtual electronic control units (vECUs) having a virtual bus connectivity configuration used to simulate respective ones of electronic control units (ECUs) of a real-world vehicle. The vehicle software test environment management system determines respective instance types of one or more virtual compute instances to be used to implement the vECUs based on respective configuration of respective ones of the ECUs and further determines respective machine images to emulate respective software environments of the respective ones of the ECUs. The vehicle software test environment management system may also deploy a vehicle software application to be certified on one or more of the vECUs and test the deployed vehicle software application using recorded signals of one or more ECUs of the real-world vehicle.

Abstract: A system comprising one or more computing devices implements a vehicle software deployment management system. The vehicle software deployment management system enables clients to send signed serialized data chunks of a vehicle software application and a deployment plan for the software application to vehicles using a protocol agnostic transmission format. The vehicle software deployment management system may generate a deployment plan that may be processed by an in-vehicle application deployment planner/orchestrator of the vehicle to deploy the particular vehicle software application. The vehicle software deployment management system may send the vehicle software application using containers to be used by ECU agents of various ECUs of the vehicle. Furthermore, the vehicle software deployment management system may utilize received vehicle information to dynamically generate one or more updated vehicle deployment plans to send to respective vehicles.

Abstract: A system comprising one or more computing devices implements a vehicle application deployment planner. The vehicle application deployment planner may utilize received vehicle information to dynamically generate one or more vehicle deployment plans to send to respective vehicles. The deployment plans may also be dynamically updated based on newly received vehicle information. The application deployment planner may generate updated deployment plans for already deployed applications in response to chances in vehicle conditions as indicated in the received vehicle information. In some embodiments, the deployment plan may be processed by an in-vehicle application deployment planner/orchestrator of the vehicle to deploy the particular vehicle software application.

Abstract: Systems and methods are disclosed for implementing a vehicle shadow service configured to construct and maintain up-to-date vehicle shadows using asynchronously received disaggregated vehicle data. For example, different sensors of a vehicle may provide sensor data into a data stream at different times in a disaggregated manner. A vehicle shadow may be constructed using partial sensor data from a sub-set of sensors of the vehicle, and may be updated or augmented using asynchronously received sensor data from other sensors of the vehicle.

Abstract: A vehicle data streaming service provides a curated catalog of vehicle attributes and allows a vehicle data stream source to register to the vehicle data streaming system and associate its data stream to a vehicle attribute of the attribute catalog. The vehicle data streaming service also allows vehicle data stream destinations to subscribe to the vehicle attribute in the vehicle catalog, receives streamed vehicle data from the data stream source, and sends streamed vehicle data conforming to registration requirements to the data stream destinations. Additionally, the vehicle data streaming service may allow management of the vehicle attribute catalog and may further manage the registration one or more sources and the subscriptions of one or more destinations.

Abstract: Systems and methods are disclosed for implementing a vehicle shadow service that includes a vehicle and/or vehicle shadow update mechanism. A vehicle shadow management sub-system of the vehicle shadow service includes or interfaces with an interface configured to receive vehicle state change requests. Received requests are stored in an update queue for a vehicle shadow and a validation processor determines whether the received state change requests are valid before sending a given state change request to a vehicle corresponding to the vehicle shadow. In some embodiments, state change requests may be invalidated due to being rendered moot by subsequently received requests, changes in state of the vehicle, expiration, etc. The corresponding vehicle shadow is then updated when a data stream from the vehicle indicates that the requested state change has in fact been implemented at the vehicle.

Abstract: Systems and methods are disclosed for implementing perspective-based vehicle shadows. A user of a vehicle shadow service can specify different vehicle shadows for a given vehicle, wherein the different vehicle shadows comprise at least partially different sets of sensor data received from the vehicle and represent the vehicle from different perspectives. For example, a first vehicle shadow may represent the vehicle from the perspective of a first vehicle system, such as the tires, and another vehicle shadow may represent the same vehicle from the perspective of a second vehicle system, such as the engine. Streaming data is provided to the vehicle shadow service and is mapped to the respective perspective-based vehicle shadows, based on user defined configurations for the respective perspective-based vehicle shadows.

Abstract: A vehicle data management system and data jurisdiction system manage vehicle data between multiple jurisdictions and enables a set of jurisdiction rules involving rules of various jurisdictions to be applied consistently. The vehicle data jurisdiction system can detect changes in jurisdiction of a vehicle based on various pieces of received vehicle information and applies appropriate jurisdiction rules from a set of jurisdiction rules. Various jurisdictions may have conflicting jurisdiction rules and, in such circumstances, the data jurisdiction system resolves potential conflicts between the rules using a jurisdiction rules resolution workflow. Based on the resolution of the conflict, the data jurisdiction system can migrate data of the vehicle to one or more other jurisdictions, or otherwise implement the correct rules determined by resolving the conflict.