Construction of vehicle shadows using decomposed streaming data
By asynchronously receiving and processing decomposing data flows and building and updating vehicle shadows, the problem of low vehicle data update efficiency in remote data storage systems is solved, and efficient and flexible data management and access are achieved.
Patent Information
- Application Number
- CN202380032154.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-31
- Filing Date
- 2023-03-23
- Publication Date
- 2024-11-22
AI Technical Summary
The existing remote data storage system has low flexibility and operational efficiency when processing vehicle data, especially because users are only interested in a subset of vehicle data and the vehicle status update frequency is different, resulting in low data update efficiency.
By asynchronously receiving and processing decomposed data streams from vehicles, asynchronously streaming data is provided to construct and update vehicle shadows, allowing vehicle shadows from different perspectives, and organizing data based on graphics or tree structures, achieving efficient storage and management of vehicle data .
It realizes the latest state of vehicle data under low network overhead, adapts to different data update frequencies, provides flexible data access and management, and meets the needs of different user perspectives.
Smart Images

Figure CN119013665A_ABST
Abstract
Description
Background Art
[0001] In recent years, the adoption of technologies such as distributed cloud computing and the increase in digitization of various industries have made data an important part of the modern global economy. For vehicles, remote data storage systems (such as cloud-based computing systems) can store vehicle data. Such systems typically receive a snapshot of vehicle data generated at the vehicle and submit the snapshot to the remote data storage system via a network. However, such systems may be inflexible and / or inefficient in operation. For example, some users may only be interested in a subset of vehicle data rather than a complete list of vehicle data contained in a snapshot. In addition, such systems may lack a process for updating vehicle status, and / or require data updates for different elements of the vehicle shadow to be updated at the same rate based on the snapshot frequency, even though the underlying vehicle data may have different data update frequencies. BRIEF DESCRIPTION OF THE DRAWINGS
[0002] Figure 1 A vehicle shadow storage system is shown, which may be a subsystem of a vehicle shadow service. According to some embodiments, the vehicle shadow storage system is configured to maintain multiple vehicle shadows representing different perspectives of the same vehicle.
[0003] Figure 2 A tree-based structure of nodes that can be used to organize vehicle shadows is shown according to some embodiments.
[0004] Figure 3 A node-based graph structure is shown that can be used to organize vehicle shadows according to some embodiments.
[0005] Figure 4 An example vehicle shadow service is shown, which includes a vehicle shadow storage subsystem, which includes a vehicle shadow model builder, which can be used to build a vehicle shadow model to be stored in the vehicle shadow storage subsystem. Figure 4 Also shown is a vehicle shadow management subsystem according to some embodiments that enables state changes to be queued, sent to the vehicle, reflected in updated vehicle shadows, and / or invalidated along with other components if necessary.
[0006] Figure 5 is a flow chart illustrating an example process for generating and maintaining perspective-based vehicle shadows for a vehicle, according to some embodiments.
[0007] Figure 6is a flowchart illustrating a process for enabling a user of a vehicle shadow service to select different sensor configurations to include sensor data in perspective-based vehicle shadows representing different perspectives of the same vehicle, according to some embodiments.
[0008] Figure 7 is a flow chart illustrating a process for responding to query target data included in a vehicle shadow, according to some embodiments.
[0009] Figure 8 Additional details of the vehicle shadow management subsystem are shown, where the vehicle shadow management subsystem includes an update queue, an invalidation handler, and a vehicle shadow update API. If a subsequent event (such as a vehicle state change or expiration) causes a pending request to be invalidated, the invalidation handler invalidates the request in the queue. In addition, according to some embodiments, the vehicle shadow is updated only based on sensor data from the vehicle, so that the invalidation request is not reflected in the state of the vehicle shadow.
[0010] Fig. 9A / Fig. 9B State change requests are shown being received sequentially according to some embodiments, wherein a subsequently received state change request renders a pending state change request invalid.
[0011] Fig. 10A / Fig. 10B Pending state change requests are shown being invalidated based on a changed state of a vehicle indicated in streaming data received from the vehicle according to some embodiments.
[0012] Fig.11A / Fig. 11B Pending state change requests are shown being invalidated based on an amount of time that has passed (e.g., expiration of the request) in accordance with some embodiments.
[0013] Fig.12 A data jurisdiction system that determines a vehicle jurisdiction change is shown. The data jurisdiction system determines one or more actions to be taken in response to the vehicle jurisdiction change based on a jurisdiction rule set. Additionally, according to some embodiments, the data jurisdiction system resolves conflicts between jurisdiction rules of different jurisdictions, and if applicable, the data management system migrates the vehicle's data (such as a vehicle shadow) to one or more other jurisdictions in accordance with the resolved conflicting jurisdiction rules.
[0014] Fig.13 A process for managing state change requests for a vehicle received by a vehicle shadow service is shown according to some embodiments.
[0015] Fig.14A process for providing a user interface for managing pending requests stored in a queue of a vehicle shadow management system is shown according to some embodiments.
[0016] Fig.15 A process for updating an authority jurisdiction for a vehicle shadow and invalidating a state change request at a replaced vehicle shadow is shown according to some embodiments.
[0017] Fig.16 A process for generating a vehicle shadow model according to some embodiments is shown.
[0018] Fig.17 A process for maintaining vehicle shadows up to date is shown according to some embodiments.
[0019] Fig.18 Example mappings between streaming data elements and pattern attributes, and mappings between pattern attributes and nodes of a vehicle shadow, are shown according to some embodiments.
[0020] Fig.19 An example mapping is shown in which there are no entries in the target path with a cardinality greater than 1 according to some embodiments.
[0021] Fig. 20 An alternative example mapping is shown in accordance with some embodiments, where at least some of the entries in the target path have a cardinality greater than 1.
[0022] Fig.21 A process for generating a map of vehicle shadows and updating the vehicle shadows using decomposed sensor data received asynchronously from a data stream is shown according to some embodiments.
[0023] Fig. 22 Additional details are shown regarding how mapping of vehicle shadows is generated according to some embodiments.
[0024] Fig.23 Shown is a block diagram illustrating an example computer system that implements some or all of the techniques described herein, according to some embodiments.
[0025] Although embodiments are described herein with several embodiments and illustrative drawings as examples, those skilled in the art will recognize that embodiments are not limited to the described embodiments or drawings. It should be understood that the drawings and their detailed descriptions are not intended to limit the embodiments to the disclosed specific forms, but on the contrary, it is intended to cover all modifications, equivalents and alternatives falling within the spirit and scope as defined by the accompanying claims. The titles used herein are only for organizational purposes and are not intended to limit the scope of the specification or claims. As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning possible) rather than a mandatory sense (i.e., meaning must). Similarly, the word "include, including and includes" means including but not limited to this. DETAILED DESCRIPTION
[0026] The systems and methods described herein include techniques for implementing a vehicle shadow service. In some embodiments, the vehicle shadow service is configured to asynchronously receive decomposed sensor data in one or more data streams from the vehicle and / or other data sources related to the vehicle (such as a service department, etc.). Asynchronous streaming data may include data generated at different rates. For example, engine information may be generated at a higher rate (e.g., more frequently) than tire pressure data. By decomposing and asynchronously receiving and processing data from various data sources related to the vehicle, the vehicle shadow service can provide a vehicle shadow that is kept up to date and requires less network overhead than other methods. For example, in a design where a snapshot of the vehicle is generated at the vehicle and the snapshot is sent to a remote service to be presented as a representation of the vehicle state, the snapshot may not be generated at a sufficient frequency to capture vehicle data updated at a high rate, or if generated at a sufficiently high frequency, the snapshot may need to send redundant data signals, and thus inefficiently use system and network resources. For example, if tire pressure is updated once a minute and engine data is updated at a rate of once per second, a snapshot needs to be generated at a rate of 1 snapshot per second (in order to match the engine data frequency), but the tire pressure of the same measurement that is redundantly transmitted in 60 snapshots will be included. Conversely, if snapshots were sent at a rate of once per minute, the engine data would have much less fidelity by averaging 60 measurements into a single signal data point. However, a vehicle shadow service that allows for receiving and processing asynchronously decomposed data enables processing of engine data at a first rate (e.g., once per second) (without redundantly sending lower frequency data signals) and processing tire pressure data at a second rate (e.g., once per minute).
[0027] In addition, in some embodiments, a vehicle shadow may be constructed using partial data signals from heterogeneous sources. For example, some vehicle data may be provided to the vehicle shadow from the vehicle itself (e.g., via a subset of the vehicle's sensors), and other vehicle information about the vehicle may be provided from other sources (such as other vehicles observing the vehicle, a maintenance department that repairs the vehicle, etc.). In some embodiments, the vehicle shadow service may verify data from heterogeneous sources (wherein the heterogeneous sources may include heterogeneous sources located on the vehicle and / or additional heterogeneous sources outside the vehicle) before applying the vehicle data to the vehicle shadow of the vehicle. For example, the vehicle shadow service may verify whether the received data is correctly linked to the vehicle, such as by verifying the vehicle identification number (VIN) included in the received vehicle data. In addition, in some embodiments, when a new vehicle data fragment is received at the vehicle shadow service, the vehicle shadow is partially constructed (and / or partially updated). For example, this can be contrasted with buffering vehicle data and waiting to construct or update the vehicle shadow until all (or substantially all) vehicle data has been stored in the buffer within a given update interval. For example, the vehicle shadow may be partially updated with new engine data without updating the tire pressure data of the vehicle shadow.
[0028] In some embodiments, data streams from vehicles are registered to be provided to a given vehicle shadow. Data streams can be parsed into data elements corresponding to the vehicle's sensors, and each data stream of a given sensor can be mapped to one or more attributes of a pattern. In some embodiments, the pattern can be an intermediate representation that can map data streams to nodes of a vehicle shadow. In addition, the pattern may represent a large block of streaming data being processed. For example, the attributes of the pattern to which the streaming data elements corresponding to a given sensor of a vehicle are mapped can also be mapped to one or more nodes of the vehicle shadow. This can allow data from multiple sensors to be mapped to a single node of the vehicle shadow and / or one or more transformations to be applied to a single data element corresponding to a single sensor and / or application of transformations that take multiple data elements from multiple sensors as input to generate outputs included in the nodes of the vehicle shadow.
[0029] In some embodiments, the vehicle shadow mapping may allow for two or more cardinalities. For example, the tire pressure may be mapped to the right front tire using two different paths (e.g., cardinalities greater than one) to the target node of the vehicle shadow. For example, the tire pressure of the right front tire may be mapped using a first path (such as front, then right) or a second path (such as right, then front).
[0030] In addition, in some embodiments, various model types may be used to construct the structure of the vehicle shadow. For example, in some embodiments, a tree structure may be used, where vehicle components are organized based on a tree, and the leaves of the tree include nodes that are updated with streaming data. In other embodiments, a graph structure may be used, where streaming data is used to update the nodes of the graph, and the edges between the nodes of the graph represent the relationships between the nodes as represented in the actual vehicle. For example, an edge between a wheel and an axle may represent that the wheel is connected to the axle in an actual vehicle.
[0031] In some embodiments, the vehicle shadow service may provide a user interface that enables users of the vehicle shadow service to define customized "perspective-based vehicle shadows". For example, users of the vehicle shadow service may include engineers working at a vehicle manufacturer. The first team of engineers responsible for designing the engine may care about engine information, but are less interested in tire information. In addition, the second team of engineers responsible for designing tires may care about tire information, but are less interested in engine information. In some embodiments, the first team of engineers and the second team of engineers may be "users" of the vehicle shadow service. The first team of engineers may select a configuration for the first vehicle shadow from the perspective of the engine. The first vehicle shadow may include nodes representing engine information, but may omit other types of information about the vehicle included in the streaming data received from the vehicle. Similarly, the second team of engineers may select a different configuration for the second vehicle shadow from the perspective of the tire. The second vehicle shadow may include nodes representing tire information, but may omit other types of information about the vehicle included in the streaming data received from the vehicle, such as engine information. In this way, each team can build a lightweight and manageable vehicle shadow that includes vehicle information relevant to the purpose of configuring the corresponding perspective-based vehicle shadow without carrying a large amount of unnecessary vehicle data that is not relevant to the purpose of configuring the corresponding perspective-based vehicle shadow.
[0032] In some embodiments, multiple instances of the same vehicle shadow may be created or may be selected. For example, in some embodiments, a tree structure instance type may be used for a vehicle shadow, and / or alternatively, a graph-based instance type may be used for the same vehicle shadow. Tree structures may be less expensive to store and maintain, but may lack the relationship information available in a graph structure. Similarly, a graph structure may provide more insight into the relationships between nodes, but may be more expensive to store and maintain. Therefore, different users may select different instance types for their vehicle shadows based on how the vehicle shadows will be used. For example, for vehicle shadows that include a large number of data points, a tree structure may be easier to manage than a graph structure. However, for more focused perspective-based vehicle shadows, a graph structure may be a better choice.
[0033] In some embodiments, a graphical user interface may be used with either instance type, such as a graphical query language (GraphQL) interface. The GraphQL interface may traverse the branches of a tree to locate data items targeted by a query in a vehicle shadow formatted using a tree structure. For vehicle shadows formatted using a graph structure, the query engine may traverse the nodes of the graph to locate data items targeted by a query. In a tree structure vehicle shadow instance type, there may be multiple pointers to the same piece of information (e.g., a node).
[0034] In some embodiments, an agent or software development kit is uploaded to a vehicle computing device, such as an electronic control unit (ECU), and the agent or SDK can enable vehicle state changes to be propagated from the vehicle shadow service to the vehicle itself.
[0035] In some embodiments, the vehicle shadow service includes an application programming interface for receiving state change requests for vehicle shadows and, by extension, for vehicles. The received vehicle state change request can be stored in an update queue and sent to the vehicle to be applied. The vehicle shadow state can be updated based on the received sensor data included in the streaming data received from the vehicle. Since the vehicle shadow is updated based on the actual sensed state of the vehicle as reflected in the streaming data, the vehicle shadow is not updated when the state change request is pending and stored in the update queue. In addition, for example, if the vehicle state changes so that the request is no longer valid, the request expires, or the request received subsequently causes the previously received request to become meaningless, the state change request in the update queue may be invalidated. Since the same vehicle may have multiple vehicle shadows, a centralized system (e.g., a vehicle shadow management subsystem) manages the updates provided to each vehicle shadow.
[0036] In addition to multiple vehicle shadows at different perspectives, there may also be multiple vehicle shadows in different data jurisdictions. Therefore, the vehicle shadow management subsystem can interface with the data jurisdiction service to determine which data jurisdiction is the authoritative data jurisdiction for the vehicle.
[0037] In some embodiments, the vehicle may include a "message received" sensor that acknowledges receipt of a state change request sent to the vehicle. The output of the "message received" sensor may be included in the sensor data of the data stream provided to the vehicle shadow service.
[0038] Figure 1 A vehicle shadow storage system 402 is shown, which may be a subsystem of the vehicle shadow service 400. Figure 4According to some embodiments, the vehicle shadow storage system 402 is configured to maintain multiple vehicle shadows representing different perspectives of the same vehicle.
[0039] In some embodiments, the vehicle data stream subsystem 112 receives disaggregated vehicle data from multiple heterogeneous sources, such as vehicle information received from the manufacturer 102, sales information 104, service information 106, and vehicle information received from various sensors of the vehicle, such as vehicle sensor groups 1 to N (e.g., 108 to 110). A vehicle shadow model builder (such as vehicle shadow model builder 116 or 124) reads a catalog of available vehicle information included in the ingested data stream. For example, the manufacturing information 102 or the sales information 104 may indicate which sensors are included in the vehicle and may be used to generate a catalog accessed by the vehicle shadow builder 116 or 124. A user (such as user A or user B) may select a set of sensors to be included in a corresponding perspective-based vehicle shadow (such as vehicle shadow A (120) or vehicle shadow B (128)). In some embodiments, different sets of sensor data may be selected for different vehicle shadows in the perspective-based vehicle shadow. For example, at least some of the sensors included in vehicle shadow A (120) may be different from at least some of the sensors included in vehicle shadow B (128). Furthermore, each perspective-based vehicle shadow may include more or fewer sensors than other corresponding perspective-based vehicle shadows.
[0040] A vehicle shadow builder (such as vehicle shadow builder 118 or 126) uses the streaming data ingested by the vehicle data stream subsystem 112 to build and maintain perspective-based vehicle shadows (e.g., vehicle shadow A (120) and vehicle shadow B (128)). In some embodiments, vehicle shadow builder 118 or 126 may use a vehicle shadow builder such as Figures 16 to 22 Mapping for further discussion.
[0041] In some embodiments, user A or user B may specify operational characteristics for vehicle shadow A (120) and vehicle shadow B (128). For example, access control rules or access control lists (ACLs) may be specified that restrict access to vehicle shadows via access boundaries 114 or access boundaries 122. In some embodiments, users may specify other operational characteristics, such as replication rules for relocating a given vehicle shadow between data jurisdictions, encryption rules for defining the type of sensor data to be encrypted included in a given vehicle shadow. In some embodiments, the access control list may restrict access to the entire vehicle shadow or only to one or more nodes of the vehicle shadow. Likewise, the entire vehicle shadow or only one or more nodes may have their data encrypted.
[0042] In some embodiments, the operating characteristics may be specified by a user and may include query interface rules for defining a query language to be used to query vehicle shadows.
[0043] In some embodiments, user A and user B can use a user interface provided by the vehicle shadow service (such as Figure 4 422) to specify the configuration to be used for the corresponding vehicle shadow. In some embodiments, the user interface may include a command line interface, a graphical user interface, a web-based user interface, an application programming interface, or other suitable interface. In some embodiments, the same or different user interfaces may be used to configure vehicle shadows and query vehicle shadows.
[0044] In some embodiments, user A and user B may have different accounts in the vehicle shadow storage system 402 , where user A's account boundaries are defined via access boundaries 114 , and user B's account boundaries are defined via access boundaries 122 .
[0045] Figure 2 A tree-based structure of nodes that can be used to organize vehicle shadows is shown according to some embodiments.
[0046] In some embodiments, a vehicle shadow (such as vehicle shadow A (120) or vehicle shadow B (128)) may include nodes representing vehicle data that is kept up to date. The nodes may be organized using a tree structure. For example, in Figure 2 , the tree-based vehicle shadow 200 includes leaf nodes 202, 204, 206, 208, 210, and 212. The tree structure organizes the leaf nodes, but the higher-level nodes and branches of the tree do not include vehicle data. For example, leaf node 202 includes vehicle information and can be reached via a branch from "vehicle". In addition, leaf node 204 includes vehicle information and can be reached via a sub-branch of "vehicle" connected to "mechanical" and further branched down to leaf node 204. Alternatively, leaf node 204 can be reached via a sub-branch from "vehicle" to "mechanical" to "engine component". Therefore, there may be multiple taxonomies linked to the same leaf node, where the leaf node maps to attributes that are updated using streaming data, such as a given sensor for a vehicle. As another example, leaf node 208 includes timing belt information, and leaf node 210 includes cylinder information. These leaf nodes can be reached through a branch of "engine component", which is a branch of "mechanical", and "mechanical" is a branch of "vehicle". In addition, leaf nodes 206 and 212 include vehicle information for axles and wheels, respectively. They can be reached through the corresponding branches of "rotating equipment" on "vehicle". It should be noted that Figure 2A simplified example is shown. In some embodiments, the tree-based structure for vehicle shadows may include more or fewer nodes and more or fewer branch levels, etc. However, the tree-based structure simplifies storage because leaf nodes can point to data objects, such as can be stored in a key-value database, and higher-level branches are not linked to the key-value database. Therefore, in response to a query, the tree-based structure can be traversed to locate the target node, and the vehicle information of the target node can be retrieved from the database at the location indicated by the pointer of the leaf node. In some embodiments, multiple tree structures can be used to map to the same data object in the database. For example, in the case where vehicle shadow A (120) and vehicle shadow B (128) include some of the same nodes, these nodes may be linked to the same database entry. For example, if the vehicle shadow focused on the tire includes a "vehicle speed" node, and the vehicle shadow focused on the tire includes a "vehicle speed" node, then both trees may have separate "vehicle speed" leaf nodes that map to the same attributes in the pattern, which, as an example, can be stored in the database as a single data object.
[0047] Figure 3 A node-based graph structure is shown that can be used to organize vehicle shadows according to some embodiments.
[0048] As an alternative to a tree-based structure, in some embodiments, the same vehicle shadow service may additionally or alternatively provide a graph-based vehicle shadow instance type, where vehicle information is linked to nodes of the graph connected via edges representing relationships between the nodes. For example, the graph-based vehicle shadow 300 includes a vehicle 308, which is linked to engine information 304 and axle information 310. The engine information 304 is also linked to cylinder data 302 and timing belt information 306, where the engine information 304 shares an edge with engine part information 316, which also shares an edge with engine information 322 of vehicle 320. Similarly, the timing belt information 306 shares an edge with the timing belt part information 314, which in turn shares an edge with the timing belt information 318, which in turn shares an edge with the engine 322 of vehicle 320. The engine information 322 also shares an edge with the cylinder information 326 (of vehicle 320). Looking back at axle information 320 of vehicle 308, the axle information shares an edge with wheel information 312, where part information of the tire of the wheel is shown in 328. Looking at axle information 324 of vehicle 324, wheel information 332 shares an edge with axle information 324 and also shares an edge with tire part information 330.
[0049] As can be seen, a graph-based vehicle shadow (such as graph-based vehicle shadow 300) includes more inter-component relationship information than a tree-based structure, but is also more complex. In addition, a graph-based structure enables part property nodes to be associated with component data nodes. For example, engine information 304 showing engine temperature and mileage can share edges (and therefore relationships) with engine part information 316 indicating engine part number, engine type (e.g., electric or gas), engine size (e.g., 2.0L, etc.). Similarly, a graph-based structure allows multiple component data nodes to be associated with a common part property node. For example, both engine information 304 and engine information 322 are associated with engine part properties 316.
[0050] Figure 4 An example vehicle shadow service is shown, which includes a vehicle shadow storage subsystem, which includes a vehicle shadow model builder, which can be used to build a vehicle shadow model to be stored in the vehicle shadow storage subsystem. Figure 4 Also shown is a vehicle shadow management subsystem according to some embodiments that enables state changes to be queued, sent to the vehicle, reflected in updated vehicle shadows, and / or invalidated along with other components if necessary.
[0051] The vehicle shadow service 400 includes a vehicle shadow storage subsystem 402, wherein the vehicle shadow storage subsystem 402 includes a vehicle shadow model builder 404, which can be interfaced with a vehicle shadow pattern repository 410, a vehicle shadow model repository 412, and a transformation / validation rule repository 414. The vehicle shadow model builder 404 can use a user-selected or defined model stored in the vehicle model repository 412 to build a vehicle shadow. In addition, the vehicle shadow model builder 404 can use user-defined patterns and / or user-defined transformation rules, which can be stored in the vehicle shadow pattern repository 410 and the transformation / validation rule repository 414, respectively. In some embodiments, the vehicle shadow model can include a user's selection of sensors whose streaming data is to be included in the vehicle shadow. For example, from Figure 1User A may define a model focused on the engine, and user B may define a model focused on the tires. In some embodiments, the patterns, transformation rules, and selection of attributes to include in the vehicle shadow may be separated into separate entities, such as patterns, transformation rules, and models, or they may be collapsed into a single "model" entity that defines what streaming data components to include in the vehicle shadow, what patterns to use to map the vehicle shadow, and what transformation rules to apply to the mapped data in the vehicle shadow.
[0052] In addition, the vehicle shadow service 400 includes a vehicle shadow management subsystem 416 that enables state changes to be queued, sent to the vehicle, and / or invalidated (if necessary). In addition, the vehicle shadow service 400 includes a vehicle shadow API 418 and an interface with a data jurisdiction system 420, which can interface with a data jurisdiction system, such as Fig.12 In addition, the vehicle shadow service 400 includes a vehicle shadow user interface 422, which can enable a user (such as Figure 1 Users A and B described in are able to select the configuration of their respective vehicle shadows and / or query the data included in their respective vehicle shadows.
[0053] In some embodiments, a vehicle supplier or other third party may implement a vehicle status interface 430, such as a web-based application, which is configured to provide a vehicle consumer 424 with an interface for viewing and interacting with the vehicle shade. The vehicle consumer 424, the vehicle shade designer 426, and / or the vehicle shade user 428 (such as Figure 1 The user A and B described in the above can submit a vehicle state change request via the vehicle state interface 430, and the vehicle state interface 430 can make an API call to the vehicle shadow API 418 to submit the vehicle state change request to the vehicle shadow management subsystem 416. In addition, the vehicle shadow designer 426 and the vehicle shadow user 428 can directly make an API call to the vehicle shadow API 418 via the network 434. Figures 8 to 15 The process of receiving a vehicle state change request, queuing a vehicle state change request, submitting a vehicle state change request, or invalidating a vehicle state change request is further described in detail. Figures 16 to 22 The vehicle shadow model builder is described in further detail.
[0054] The vehicle shadow service 400 also includes a vehicle data stream subsystem 404 (which may be similar to Figure 1 ), a vehicle shadow builder / updater 406 (which may be similar to Figure 1The vehicle shadow builder 116 described in the specification and the vehicle shadow repository 408, which can store vehicle shadows, such as Figure 1 . In addition, the vehicle shadow repository 408 can manage and enforce operational characteristics of the vehicle shadow, such as access boundaries 114, 122. Other operational characteristics managed or enforced by the vehicle shadow repository 408 may include access control lists of nodes of the vehicle shadow (or the entire vehicle shadow), encryption of vehicle information of the vehicle shadow, etc. In some embodiments, the user interface configuration of a given vehicle shadow may be stored as metadata with the vehicle shadow stored in the vehicle shadow repository 408, and may be used by the vehicle shadow user interface 422 to configure the user interface so that the vehicle shadow user 428 can access the vehicle shadow or the data included in the vehicle shadow. In some embodiments, networks 432, 434, and 436 may be the same or different networks. For example, in some embodiments, the vehicle shadow designer 426 and the vehicle shadow user 428 may be connected to the vehicle shadow service 400 via a public network (such as the Internet), or may be connected via a private network connection (such as a direct connection between a customer and a service provider network hosting the vehicle shadow service 400). Additionally, network 432 or 434 may be a public network or a private network, and in some embodiments, network 436 may be a public network (such as the Internet) or a private network (such as a network operated by a vehicle manufacturer to connect the vehicle to external services).
[0055] Figure 5 is a flow chart illustrating an example process for generating and maintaining perspective-based vehicle shadows for a vehicle, according to some embodiments.
[0056] At box 502, the vehicle shadow service receives streaming data from a vehicle or other source. At box 504, a first vehicle shadow (e.g., a first perspective-based vehicle shadow) of a vehicle is generated, wherein the first vehicle shadow includes data of a first sensor subset whose sensor data is included in the streaming data. At box 506, a different perspective-based vehicle shadow (e.g., a second vehicle shadow) including at least some sensors different (or less / more) from the first vehicle shadow is generated. At box 508, the first vehicle shadow is maintained up to date using streaming data, and at the same time at box 510, the second vehicle shadow is maintained up to date using streaming data. It should be noted that in some embodiments, different sensors included in different vehicle shadows in the vehicle shadow may generate sensor measurements at different frequencies. In some embodiments, the first vehicle shadow and the second vehicle shadow can be updated when new sensor data is received, regardless of the rate at which the sensor data is generated by the sensor and received by the vehicle shadow service.
[0057] At block 512 , the vehicle shadow service provides a user interface that allows a user to access the latest vehicle shadows (eg, from any angle).
[0058] Figure 6 is a flowchart illustrating a process for enabling a user of a vehicle shadow service to select different sensor configurations to include sensor data in perspective-based vehicle shadows representing different perspectives of the same vehicle, according to some embodiments.
[0059] At box 602, the vehicle shadow service provides a user interface for configuring multiple vehicle shadows to be constructed to represent different perspectives of the vehicle. At boxes 604 and 606, a first user selection and a second user selection are received to include a first sensor set and a second sensor set in a first vehicle shadow and a second (or Nth) vehicle shadow. In addition, at boxes 608 and 610, corresponding user-selected sets of operating characteristics to be applied to the first vehicle shadow and the second (or Nth) vehicle shadow are received. Then, at boxes 612 and 614, corresponding models and associated patterns are constructed for the first vehicle shadow and the second vehicle shadow. The models and / or patterns can then be used to generate and maintain the first vehicle shadow and the second vehicle shadow, such as Figure 5 As described in blocks 504, 506, 508 and 510 of .
[0060] Figure 7 is a flow chart illustrating a process for responding to query target data included in a vehicle shadow, according to some embodiments.
[0061] At box 702, the vehicle shadow service receives query target data included in the vehicle shadow. In some embodiments, the query can be formatted as a graph QL query (regardless of whether the vehicle shadow uses a tree-based instance type or a graph-based instance type). For example, if it is a tree-based instance type, the branches of the tree are traversed at box 704 to locate the leaves that map to the attributes of the pattern, where the pattern maps elements of the data stream to the attributes. The target data can then be read from the leaves. Alternatively, if it is a graph-based instance type, at box 706, the graph structure is traversed to locate the nodes that map to the attributes of the pattern, where the pattern maps elements of the data stream to the attributes. The target data can then be read from the nodes of the graph.
[0062] At block 708 , a response to the query received at 702 is provided using data read from leaves or nodes of the graph.
[0063] Figure 8Additional details of the vehicle shadow management subsystem are shown, where the vehicle shadow management subsystem includes an update queue, an invalidation handler, and a vehicle shadow update API. If a subsequent event (such as a vehicle state change or expiration) causes a pending request to be invalidated, the invalidation handler invalidates the request in the queue. In addition, according to some embodiments, the vehicle shadow is updated only based on sensor data from the vehicle, so that the invalidation request is not reflected in the state of the vehicle shadow.
[0064] In some embodiments, the vehicle shadow management subsystem 416 (such as also in Figure 4 802 . In addition, the vehicle shadow management subsystem 416 includes an update queue 806 of a vehicle 802 represented by a vehicle shadow 804. In addition, the vehicle shadow management subsystem 416 includes a vehicle shadow API 418 (or interacts with it), which receives a state change request for the vehicle 802. The state change request received via the API 418 is added to the update queue 806. When in the update queue, the invalidation processor 808 checks the vehicle shadow 808 to determine whether a change in the vehicle state has been indicated in the received streaming data, wherein the change in the vehicle state causes the state change request to be invalid. If so, the pending state change request is invalidated in the update queue 806 and is not sent to the vehicle 802. If the state change request is valid, it is sent as a vehicle action to be executed at the vehicle 802. Once the vehicle action is performed and the vehicle action is indicated in the streaming data received from the vehicle at the vehicle shadow 804 (e.g., in an updated vehicle state), the vehicle shadow 804 is updated to show the new state of the vehicle 802 when the vehicle action is performed. In some embodiments, a pending state change request may be invalidated based on a subsequently received state change request or the expiration of the state change request.
[0065] Additionally, in some embodiments, the API 418 may provide information about the current status of the vehicle shade 804 to a user (such as a vehicle customer, a vehicle shade user, and / or a vehicle shade designer).
[0066] Fig. 9A / Fig. 9B State change requests are shown being received sequentially according to some embodiments, wherein a subsequently received state change request renders a pending state change request invalid.
[0067] For example, a first state change request 902 may be received at API 418 at time 1, where the first state change request is to increase the cabin temperature control. Additionally, a state change request 904 may be received at API 418 at time 2, where the second state change request is to turn off the cabin temperature control. In some embodiments, the second request 904 may be received while the first request 902 is still stored in update queue 806. Since turning off the cabin temperature control renders the request to increase the cabin temperature control meaningless, invalidation processor 808 may invalidate first request 902 and send only second request 904 to vehicle 802, as shown in FIG. Fig. 9B shown.
[0068] Fig. 10A / Fig. 10B Pending state change requests are shown being invalidated based on a changed state of a vehicle indicated in streaming data received from the vehicle according to some embodiments.
[0069] As another example, a state change request 1002 may be received at API 418. However, while state change request 1002 is still stored in update queue 806, streaming data 1004 may indicate that vehicle 802 has changed from a stopped state to a moving state. Invalidation handler 808 may check vehicle shadow 804 to attempt to validate state change request 1002, and may determine (e.g., based on the current state of vehicle 802 as indicated in vehicle shadow 804) that the state change request 1002 has changed from a stopped state to a moving state. Fig. 10B As shown) state change request 1002 is invalid.
[0070] Fig.11A / Fig. 11B Pending state change requests are shown being invalidated based on an amount of time that has passed (e.g., expiration of the request) in accordance with some embodiments.
[0071] As yet another example, a state change request 1102 may be received via API 418 at time 1. The state change request may be a request to start vehicle 802. However, after a threshold amount of time has passed (where the threshold (D, e.g., delay) corresponds to an expiration time of the state change request 1102), the vehicle state information 1104 may not be received due to a loss of connection with vehicle 802. In response to the state change request expiring, invalidation processor 808 may invalidate state change request 1102, e.g., Fig. 11B shown.
[0072] Fig.12A vehicle data management system and a data jurisdiction system are shown, and the data jurisdiction system determines changes in vehicle jurisdictions according to jurisdiction rules, resolves conflicts between jurisdiction rules (if necessary), and retains, deletes, or migrates vehicle data to one or more other jurisdictions. Various vehicle data management systems 1210a, 1210b, and 1210c can be located in two or more jurisdictions, such as jurisdiction A 1202a, jurisdiction B 1202b, and jurisdiction C 1202c. Various jurisdictions can be geographic regions or territories in which the authority to affect vehicle data management is exercised. In some embodiments, the jurisdiction can be based on countries representing different sovereign political entities, such as the United States. In other embodiments, the jurisdiction can be based on states or places that subdivide countries into separate jurisdictions, such as California and San Francisco. The jurisdiction can also be composed of multiple countries or states, or it can be composed of various territories of any number and / or combination, such as the European Union. In some embodiments, there may be jurisdictions with overlapping authority to affect the management of vehicle data.
[0073] The vehicle data management systems 1210a, 1210b, and 1210c may be composed of the following: corresponding vehicle data streaming systems 1220a, 1220b, and 1220c (which may be Figure 1 The vehicle data stream subsystem 112 shown or Figure 4 The vehicle data flow subsystem 404 shown), data jurisdiction systems 1224a, 1224b and 1224c, and vehicle migration systems 1240a, 1240b and 1240c. Fig.12 The respective vehicle data management systems 1210a, 1210b, and 1210c are described as being comprised of respective components, but the respective systems including the vehicle data management systems may be outside of and independent of the vehicle data management systems 1210a, 1210b, and 1210c. In some embodiments, a vehicle shadow service (such as vehicle shadow service 400) may be included in a given vehicle data management system in the vehicle data management system, such as included in the vehicle data management systems 1210a, 1210b, and 1210c.
[0074] In some embodiments, the vehicle 1250 can generate one or more vehicle information streams 1206 to send to the vehicle data streaming system 1220a. The vehicle 1250 can send a vehicle information stream 1206 containing data such as video frames, images, radar amplitudes, temperature data, engine speed, and other information about the vehicle 1250. The vehicle information 1206 may include global positioning system (GPS) information determined using cellular, wireless passive, satellite, and other types of GPS systems. In some embodiments, the geographic location of the vehicle 1250 can be determined in various ways. For example, in some embodiments, GPS can be used or a global navigation satellite system (GNSS) can be used. In some embodiments, the vehicle can use local sensors and / or algorithms to determine its location, such as using computer vision, light detection and ranging (LIDAR), vehicle odometers, etc.
[0075] although Fig.12 Only the vehicle 1250 and the vehicle service center 1260 are described as generating vehicle information 1206, but any number of data sources within or outside the jurisdiction may contribute to sending the vehicle information 1206 to the vehicle data streaming system 1220a. In various embodiments, the vehicle data streaming system 1220a may be a device or system for managing the creation, storage, retrieval, and processing of large-scale vehicle data streams. The vehicle data streaming system 1220a may be designed to handle hundreds or even thousands of concurrent data producers and data consumers. The term "data stream" as used herein refers to a sequence of vehicle data records that may be generated by one or more data producers (e.g., vehicle 1250, vehicle service center 1260) and accessed by one or more data consumers.
[0076] Once the vehicle data streaming system 1220a receives the vehicle information 1206, it can use the vehicle information 1206 to detect a jurisdiction change event. In some embodiments, the detection of a jurisdiction change for the vehicle 1250 can be performed by the data jurisdiction system 1224a instead of the vehicle data streaming system 1220a. The jurisdiction change event can be inferred or derived based on a single clear indication of a vehicle jurisdiction change, such as a registration information change from the vehicle service center 1260. In some embodiments, a jurisdiction change event can be detected based on multiple vehicle information signals, such as GPS signals, vehicle service information, vehicle location history, etc. In addition, a jurisdiction change event can be detected or inferred based on one or more machine learning models trained using the past history of the vehicle information 1206 and the jurisdiction rules 128a.
[0077] The detected jurisdiction change event is then sent or requested by the data jurisdiction system 1224a, and the data jurisdiction system 1224a applies the jurisdiction rule set 1228a to initiate vehicle data migration 1270a, 1270b, 1270c, respectively. Although in some embodiments, the application of the jurisdiction rule set may result in the continued retention of vehicle data or the deletion of vehicle data (whether migrated or not). The data jurisdiction system 1224a may include a workflow engine 1230a and a jurisdiction rule engine 1226a. The jurisdiction rule engine 1226a can access the jurisdiction rule set 1228a, and can utilize the jurisdiction rules 1228a to determine whether one or more portions of the vehicle data stored for the vehicle 1250 are to be deleted, moved, or retained in a particular jurisdiction. The jurisdiction rule set 1228a may include various data storage / transfer requirements for one or more jurisdictions. Jurisdiction rules 1228a may include rules based on jurisdiction change events (e.g., a jurisdiction change from Jurisdiction A to Jurisdiction B causes data to be migrated to Jurisdiction B), based on data type (e.g., migration of vehicle user identification data, vehicle location data, vehicle camera data is allowed), based on jurisdiction (e.g., migration of data to Jurisdiction B is prohibited), or any combination thereof. For example, one jurisdiction rule may require that GPS vehicle data be migrated to Jurisdiction B 1202b upon detection of a jurisdiction change trigger event to Jurisdiction B 1202b. Jurisdiction rules 1228a, 1228b, and 1228c may be added, removed, or modified, and may be synchronized between multiple jurisdictions.
[0078] Once the jurisdiction rules applied to the vehicle data are determined, the workflow engine 1230a creates routing rules and / or migration jobs for the data migration system 1240a. The data migration system 1240a receives a migration notification from the data jurisdiction management system 1230a, which identifies one or more parts of the vehicle data to be moved. The migration of vehicle data may involve the vehicle migration systems 1240a, 1240b and 1240c of the corresponding jurisdictions 1202a, 1202b and 1202c. In some embodiments, the data migration system 1240a can transmit vehicle data in batches. The jurisdiction rule engine 1226a can determine whether one or more parts of the data of the vehicle 1250 should be deleted, moved or retained based on the jurisdiction rule set 1228a. The data migration system 1240a moves one or more parts of the vehicle data stored in the jurisdiction A 1202a to the jurisdiction B 1202b based on the received migration notification. In some embodiments, the workflow engine 1230a communicates with other data jurisdiction systems where data related to the associated VIN is stored. The workflow engine 1230a can coordinate applicable rules and priorities associated with the corresponding vehicle data to determine a migration strategy to be implemented in all affected jurisdictions.
[0079] In some embodiments, the jurisdiction rule engine 1228a can determine that there is a jurisdiction conflict between one or more rules in the jurisdiction rule set 1228a that has been selected for application. The jurisdiction rule engine 1226a can initiate a jurisdiction conflict resolution workflow to resolve the conflict. The workflow engine 1230a can use a predetermined priority sorting scheme to resolve the conflict between the jurisdiction rules 1228a. In some embodiments, manual resolution may be required in the conflict resolution workflow, where the conflict is presented to the user via a user interface and a user decision is received. Based on the user decision, the workflow engine 1230a can resolve the conflict.
[0080] Fig.13 A process for managing state change requests for a vehicle received by a vehicle shadow service is shown according to some embodiments.
[0081] At block 1302, the vehicle shadow service receives streaming data from one or more sensors of the vehicle. At block 1304, the vehicle shadow service maintains an up-to-date vehicle shadow for the vehicle based on the received streaming data.
[0082] At box 1306, the vehicle shadow service receives one or more state change requests to be applied to the vehicle shadow and / or the vehicle via the API of the vehicle shadow service. At box 1308, the vehicle shadow service places one or more requests in an update queue to apply the update to the vehicle, wherein the state of the vehicle shadow is updated only in response to a confirmation received in the vehicle sensor data that the one or more state changes have been applied to the vehicle. At box 1310, the vehicle shadow service updates the vehicle shadow in response to receiving an indication in the streaming data received from one or more sensors of the vehicle indicating that a given requested state change has been performed at the vehicle. Alternatively, at box 1312, the vehicle shadow service invalidates a given state change request stored in the update queue in response to receiving an indication in the streaming data received from one or more sensors of the vehicle indicating that the state of the vehicle has changed and invalidates the given request. Alternatively, the state change request can be invalidated based on a subsequently received state change request due to expiration, or invalidated in response to a specific request (e.g., received via an API) that invalidates the state change request. At box 1314, the vehicle shadow service avoids updating the vehicle shadow based on the invalid request (e.g., no matter what was requested (and subsequently invalidated), the vehicle shadow is updated based on what is reflected in the received sensor data in the data stream).
[0083] Fig.14 A process for providing a user interface for managing pending requests stored in a queue of a vehicle shadow management system is shown according to some embodiments.
[0084] At block 1402, the vehicle shadow service provides a user interface (such as an API or other interface) for providing a state change request and invalidating a previously submitted state change request. At block 1404, the vehicle shadow service receives an indication via the user interface that the state change request stored in the update queue is to be invalidated. For example, Fig.15 As further described, the jurisdiction of the vehicle may have changed such that the previous vehicle shadow is no longer authoritative and all pending state change requests associated with the replaced vehicle shadow should be invalidated. At block 1406, the vehicle shadow service invalidates the state change requests stored in the update queue as indicated in the invalidate request. The vehicle shadow service also avoids sending invalid state change requests to the vehicle and also avoids updating the vehicle shadow based on the invalid state change request.
[0085] Fig.15 A process for updating an authority jurisdiction for a vehicle shadow and invalidating a state change request at a replaced vehicle shadow is shown according to some embodiments.
[0086] At block 1502, the vehicle shadow service receives (and / or Fig.12 The data jurisdiction service determines an indication that the authoritative jurisdiction of the vehicle represented by the vehicle shadow has changed from the first jurisdiction to the second jurisdiction. In response, at box 1504, the vehicle shadow service designates the vehicle shadow in the second jurisdiction as the authoritative vehicle shadow for the vehicle. Additionally, at box 1506, the vehicle shadow service removes the authoritative vehicle shadow designation from the vehicle shadow for the vehicle stored in the first jurisdiction. In some embodiments, various other rules may be applied to resolve the data jurisdiction service's determination of which jurisdiction is authoritative.
[0087] At box 1508, the vehicle shadow service invalidates the state change requests that are still waiting to be processed at the replaced vehicle shadow. For example, the state change requests for the vehicle shadow in the first jurisdiction stored in the update queue may be invalidated. In addition, the state change requests subsequently received at the vehicle shadow in the first jurisdiction may be invalidated and / or rerouted to the vehicle shadow in the second jurisdiction. In some embodiments, the vehicle shadow service can maintain a centralized vehicle shadow management system for multiple jurisdictions so that all state change requests are routed to the centralized vehicle shadow management subsystem. Alternatively, separate vehicle shadow management subsystems can be maintained in different jurisdictions, and the data jurisdiction service can be used to determine the authoritative jurisdiction, as described above.
[0088] Fig.16 A process for generating a vehicle shadow model according to some embodiments is shown.
[0089] In some embodiments, a vehicle shadow model builder (such as Figure 1 The vehicle shadow model builder 126 and Figure 4 The modeling phases performed by the vehicle shadow model builder 414 shown may include a model creation phase 1604 , a schema and format registration phase 1606 , and a data mapping phase 1606 .
[0090] For example, the modeling phase 1602 may be used to define a vehicle shadow model, map data sources to schemas (for supported formats), and map attributes from schemas to models. The vehicle shadow service may provide a user interface for modeling a vehicle shadow, defining entities and their properties, relationships between them, and cardinality associated with relationships. The mapping of data sources to schemas may contain data source metadata that will allow the vehicle shadow service to identify schemas for validating and parsing incoming data. The mapping of schemas to shadows may define source attributes of identifiers of root entities (such as vehicle VIN) in the vehicle shadow of the schema, sources of data attributes in the schema, optional transformations of attributes (which may include creating new attributes whose values may be fixed or derived), and target paths of attributes to the vehicle shadow structure. If there are vehicle shadow entities with cardinality greater than 1 in the target path, an identifier attribute needs to be defined in the mapping to distinguish instances. For example, when there are two or more target paths to a given attribute (such as, for example, front left tire or left front tire), the cardinality is greater than one.
[0091] Fig.17 A process for maintaining vehicle shadows up to date is shown according to some embodiments.
[0092] The operation phase 1702 includes a streaming data ingestion phase 1704 , a validation phase 1706 of the ingested streaming data, and a vehicle shadow construction phase 1706 .
[0093] In operation phase 1702, data processing is activated. The vehicle shadow service ingests data from various sources based on the defined mapping of data sources to schemas. The vehicle shadow service also validates the data to ensure compliance with the schema. After successful validation, the vehicle shadow is incrementally built based on the mapping of schemas to shadows that have been defined. The vehicle shadow service finds the appropriate entity based on the mapping to update its value, and if the entity cannot be found, the vehicle shadow service will use the available identifiers and data attributes to build all missing entities in the target path of the mapping.
[0094] Fig.18 Example mappings between streaming data elements and pattern attributes, and mappings between pattern attributes and nodes of a vehicle shadow, are shown according to some embodiments.
[0095] For example, streaming data 1802 including data sources from sensors 1 to N is mapped to a schema 1804, wherein data corresponding to different sensors in sensors 1 to N are mapped to attributes 1 to N of schema 1804. In addition, validation rules 1808 are applied to the ingested data ingested from the streaming data 1802 to ensure compliance with schema 1804. Attributes 1 to N of schema 1804 are then mapped to nodes of a vehicle shadow, such as nodes 1 to N of vehicle shadow 1806. In some embodiments, more than one sensor may be mapped to an attribute. For example, sensors 1 and 2 are mapped to attribute 1. In addition, in some embodiments, multiple attributes may be mapped to the same node of a vehicle shadow. For example, both attributes 2 and N are mapped to node 3. In addition, in some embodiments, a given attribute may be mapped to more than one node. For example, attribute 1 is mapped to both nodes 1 and N. In addition, attribute 2 is mapped to nodes 2 and 3. In some embodiments, transformation rules 1810 may be applied to an attribute to transform an attribute value into a value to be included in a node of a vehicle shadow.
[0096] It should be noted that in some embodiments, the nodes of the vehicle shadow 1806 may be leaf nodes of a tree structure of the tree-based vehicle shadow 200, such as Figure 2 In addition, in some embodiments, the nodes of the vehicle shadow 1806 can be nodes of a graph structure, such as Figure 3 A graphics-based vehicle shadow 300 is shown.
[0097] Fig.19 An example mapping is shown in which there are no entries in the target path with a cardinality greater than 1 according to some embodiments.
[0098] In the example of "Schema to Shadow Mapping A" 1908, the "VIN" attribute of schema 1906 can be used as an identifier for the root entity, which is the "vin" property in the "vehicle 1910" of the vehicle shadow. The "timing_belt_last_inspection1914" attribute is stored as epoch milliseconds, so it needs to be transformed to a date. The transformed attribute has a target path from the "vehicle 1910" entity to the "engine 1912" entity to the "timing belt 1914" entity to the "last_inspection" property. There are no entities in the target path with a cardinality greater than 1, so the mapping is complete.
[0099] Fig. 20 An alternative example mapping is shown in accordance with some embodiments, where at least some of the entries in the target path have a cardinality greater than 1.
[0100] In the example of "Mapping of patterns to shadows B1 2020", the "VIN" attribute is used as an identifier of the root entity, which is the "vin" property in the "vehicle 1902" element of the vehicle shadow. The first item in the "tire_pressure" array attribute of pattern 2018 can be selected. The data attribute has a target path from the "vehicle 1902" entity to the "axle 1906" entity, to the "wheel 1912" entity, to the "pressure" property. The "axle 1906" and "wheel 1912" entities in the target path have a cardinality greater than 1, so a new attribute with a fixed value of "front" is needed (in addition to VIN) to uniquely identify the "axle 1906" entity by the "position" property, a new attribute with a fixed value of "left" is needed to uniquely identify the "wheel 1912" entity by the "position" property, and the mapping is completed.
[0101] In the example of "Mapping B2 2022 of patterns to shadows", "VIN" is used as the identifier of the root entity, which is the "vin" property in the "vehicle 1902" element of the vehicle shadow. The second item in the "tire_pressure" array attribute of pattern 2018 is selected. The data attribute has a target path from the "vehicle 1902" entity to the "axle 1906" entity, to the "wheel 1912" entity, to the "pressure" property. The "axle 1906" and "wheel 1912" entities in the target path have a cardinality greater than 1, so a new attribute with a fixed value of "front" is needed (in addition to VIN) to uniquely identify the "axle 1906" entity by the "position" property, a new attribute with a fixed value of "right" is needed to uniquely identify the "wheel" entity by the "position" property, and the mapping is completed.
[0102] It should be noted that graph-based instance types Fig.19 and Fig. 20 The mapping shown in can be used with any of the other graph-based vehicle shading as described herein. As already mentioned, in some embodiments a tree structure may be used as an alternative, where the cardinality of each leaf is 1.
[0103] Fig.21 A process for generating a map of vehicle shadows and updating the vehicle shadows using decomposed sensor data received asynchronously from a data stream is shown according to some embodiments.
[0104] At box 2102, the vehicle shadow service receives a user-defined or selected model of a vehicle shadow to be used for a vehicle. At box 2104, the vehicle shadow service generates a mapping of sensor data elements included in streaming data received from the vehicle to one or more nodes of the vehicle shadow based on the model. At box 2106, the vehicle shadow service asynchronously receives decomposed sensor data included in ingested streaming data received from the vehicle. At box 2108, the vehicle shadow service maintains an updated version of the vehicle shadow based on the asynchronously received decomposed sensor data, wherein the updated version of the vehicle shadow reflects a current state of the vehicle.
[0105] Fig. 22 Additional details are shown regarding how mapping of vehicle shadows is generated according to some embodiments.
[0106] In some embodiments, to generate the mapping, the vehicle shadow service maps data included in the streaming data corresponding to the corresponding sensors of the vehicle to attributes of the schema at block 2202. In addition, at block 2204, the vehicle shadow service maps the attributes of the schema to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received or selected model.
[0107] Example Computer System
[0108] Fig.23 An exemplary computer system 2300 is shown that can be used to implement the vehicle shadow service and its various components, as described above with reference to Figures 1 to 22 In various embodiments, computer system 2300 may be any of a variety of types of devices, including, but not limited to, a personal computer system, a desktop computer, a laptop computer, a notebook computer, a tablet computer, a palmtop computer, or a netbook computer, a handheld computer, a workstation, a network computer, a mobile device, a consumer device, an application server, a storage device, a peripheral device (such as a switch, a modem, a router), or generally any type of computing or electronic device.
[0109] As described herein, various embodiments of program instructions for generating and updating vehicle shadows and / or statuses of corresponding vehicles and migrating vehicle data to one or more other jurisdictions may be executed in one or more computer systems 2300, which may interact with various other devices. It should be noted that, according to various embodiments, the above description of Figures 1 to 22 Any component, action, or functionality described may be configured as Fig.23The computer system 2300 of the present invention is implemented on one or more computers of the computer system 2300. In the illustrated embodiment, the computer system 2300 includes one or more processors 2310 coupled to the system memory 2320 via an input / output (I / O) interface 2330. The computer system 2300 also includes a network interface 2340 coupled to the I / O interface 2330, and one or more input / output devices 2350, such as a cursor control device 2360, a keyboard 2370, and a display 2380. In some cases, it is contemplated that a single instance of the computer system 2300 can be used to implement the embodiment, while in other embodiments, a plurality of such computer systems or a plurality of nodes that make up the computer system 2300 can be configured to host different parts or instances of the program instructions as described above for various embodiments. For example, in one embodiment, some elements of the program instructions can be implemented via one or more nodes of the computer system 2300, which are different from those nodes that implement other elements.
[0110] In some embodiments, computer system 2300 can be implemented as a system on chip (SoC). For example, in some embodiments, processor 2310, memory 2320, I / O interface 2330 (e.g., fabric), etc. can be implemented in a single SoC including multiple components integrated into a single chip. For example, a SoC can include multiple CPU cores, a multi-core GPU, a multi-core neural engine, caches, one or more memories, etc. integrated into a single chip. In some embodiments, a SoC implementation can implement a reduced instruction set computing (RISC) architecture or any other suitable architecture.
[0111] System memory 2320 can be configured to store compressed or decompressed program instructions 2322 and / or sensor data that can be accessed by processor 2310. In various embodiments, system memory 2320 can be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), non-volatile / flash memory, or any other type of memory. In the illustrated embodiment, program instructions 2322 can be configured to implement any of the functionality described above. In some embodiments, program instructions and / or data can be received, sent, or stored on different types of computer accessible media or on similar media separate from system memory 2320 or computer system 2300.
[0112] In one embodiment, the I / O interface 2330 can be configured to coordinate I / O traffic between the processor 2310, the system memory 2320, and any peripheral devices in the device (including the network interface 2340 or other peripheral interfaces, such as the input / output device 2350). In some embodiments, the I / O interface 2330 can perform any necessary protocols, timing, or other data transformations that convert data signals from one component (e.g., the system memory 2320) into a format suitable for use by another component (e.g., the processor 2310). In some embodiments, for example, the I / O interface 2330 may include support for devices attached through various types of peripheral buses (such as, variants of the peripheral component interconnect (PCI) bus standard or the universal serial bus (USB) standard). In some embodiments, the functionality of the I / O interface 2330 can be split into two or more separate components, such as, for example, a north bridge and a south bridge. In addition, in some embodiments, some or all of the functionality of the I / O interface 2330 (such as an interface to the system memory 2320) can be directly incorporated into the processor 2310.
[0113] The network interface 2340 can be configured to allow data to be exchanged between the computer system 2300 and other devices (e.g., carriers or proxy devices) attached to the network 2385 or between nodes of the computer system 2300. In various embodiments, the network 2385 can include one or more networks, including but not limited to a local area network (LAN) (e.g., an Ethernet or an enterprise network), a wide area network (WAN) (e.g., the Internet), a wireless data network, some other electronic data network, or some combination thereof. In various embodiments, the network interface 2340 can support communication via a wired or wireless general data network, such as any suitable type of Ethernet; via a telecommunications / telephone network, such as an analog voice network or a digital fiber optic communication network; via a storage area network, such as a Fiber Channel SAN, or via any other suitable type of network and / or protocol.
[0114] In some embodiments, input / output devices 2350 may include one or more display terminals, keyboards, keypads, touch pads, scanning devices, voice or optical recognition devices, or any other device suitable for inputting or accessing data through one or more computer systems 2300. Multiple input / output devices 2350 may be present in computer system 2300, or may be distributed across various nodes of computer system 2300. In some embodiments, similar input / output devices may be separate from computer system 2300 and may interact with one or more nodes of computer system 2300 through a wired or wireless connection (such as through network interface 2340).
[0115] like Fig.23 As shown, memory 2320 may include program instructions 2322, which may be executable by a processor to implement any of the above elements or actions. In one embodiment, the program instructions may implement the above method. In other embodiments, different elements and data may be included.
[0116] Computer system 2300 may also be connected to other devices not shown, or may alternatively operate as a standalone system. In addition, in some embodiments, the functionality provided by the components shown may be combined in a few components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the components shown may not be provided and / or other additional functionality may be used.
[0117] It should also be understood by those skilled in the art that, although various items are shown as being stored in memory or stored on a storage device when being used, these items or parts thereof can be transmitted between memory and other storage devices for the purpose of memory management and data integrity. Alternatively, in other embodiments, some or all of the software components can be executed in a memory on another device and communicate with the computer system shown via inter-computer communication. Some or all of the system components or data structures can also be stored (for example, as instructions or structured data) on a computer-accessible medium or portable article for reading by a suitable driver (various examples of which are described above). In some embodiments, instructions stored on a computer-accessible medium separated from the computer system 2300 can be transmitted to the computer system 2300 via a transmission medium or signal (such as an electrical signal, an electromagnetic signal, or a digital signal), transmitted via a communication medium (such as a network and / or a wireless link). Various embodiments can also include receiving, sending, or storing instructions and / or data implemented according to the foregoing description on a computer-accessible medium. Generally speaking, computer accessible media may include non-transitory computer readable storage media or memory media, such as magnetic or optical media, for example, disks or DVD / CD-ROMs, volatile or non-volatile media, such as RAM (e.g., SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc. In some embodiments, computer accessible media may include transmission media or signals, such as electrical signals, electromagnetic signals, or digital signals, transmitted via a communication medium such as a network and / or wireless link.
[0118] In different embodiments, the methods described herein can be implemented by software, hardware or a combination thereof. In addition, the order of the frames of the method can be changed, and various elements such as addition, reordering, combination, omission, modification, etc. can be added. Various modifications and changes can be made, which are obvious to those skilled in the art who benefit from the present disclosure. The various embodiments described herein are used for illustration rather than limitation. Many changes, modifications, additions and improvements are possible. Therefore, multiple instances can be provided as single instances for the components described herein. The boundaries between various components, operations and data repositories are arbitrary to some extent, and specific operations are shown in the context of a specific illustrative configuration. The allocation of other functionalities is foreseeable and can fall within the scope of the appended claims. Finally, the structure and functionality presented as discrete components in the exemplary configuration can be implemented as a combined structure or component. These and other changes, modifications, additions and improvements can fall within the scope of the embodiments defined by the appended claims.
[0119] Embodiments of the present disclosure may be described in terms of the following:
[0120] Clause 1. A system comprising:
[0121] One or more computing devices configured to implement a model builder for a vehicle shadow of a vehicle, the model builder configured to:
[0122] receiving a model to be used for the vehicle shadow; and
[0123] generating, based on the received model and associated schema, a mapping of corresponding sensor data elements included in the streaming data provided by the vehicle to one or more nodes of the vehicle shadow; and
[0124] One or more computing devices, the one or more computing devices being configured to implement a data storage system for the vehicle shadow, the data storage system being configured to:
[0125] receiving the streaming data from the vehicle, wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously; and
[0126] An updated version of the vehicle shadow is maintained, wherein the updated version of the vehicle shadow is updated based on the streaming data to reflect a current state of the vehicle.
[0127] Clause 2. The system of clause 1, wherein to generate the mapping, the model builder is further configured to:
[0128] mapping data included in the streaming data corresponding to a corresponding sensor of the vehicle to attributes of the pattern corresponding to the corresponding sensor; and
[0129] The attributes of the pattern are mapped to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received model.
[0130] Clause 3. The system of clause 1 or clause 2, wherein the schema further defines one or more transformations to be applied to streaming data of one or more sensors mapped to one or more attributes of the schema.
[0131] Clause 4. A system as described in Clause 3, wherein for at least one attribute of the pattern, streaming data from two or more sensors are mapped to the at least one attribute, wherein a transformation is applied to the streaming data from the two or more sensors to generate an attribute value for the at least one attribute.
[0132] Clause 5. The system of any one of clauses 1 to 4, wherein data in the data stream of at least one sensor of the plurality of sensors of the vehicle is mapped to two or more attributes of the schema.
[0133] Clause 6. The system of any one of clauses 1 to 5, wherein the data storage system of the vehicle shadow is further configured to:
[0134] verifying that the received streaming data conforms to the said schema,
[0135] Wherein the updated version of the vehicle shadow is updated using the verified data conforming to the pattern.
[0136] Clause 7. A method comprising:
[0137] receiving streaming data from the vehicle, wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously; and
[0138] An updated version of a vehicle shadow of the vehicle is maintained, wherein the updated version of the vehicle shadow is updated based on the asynchronously received decomposed data stream of the streaming data to reflect a current state of the vehicle.
[0139] Clause 8. The method of clause 7, further comprising:
[0140] receiving a model and associated mode to be used for the vehicle shadow; and
[0141] Based on the received model and the associated schema, a mapping of corresponding sensor data elements included in the streaming data to one or more nodes of the vehicle shadow is generated.
[0142] Clause 9. The method of clause 8, wherein generating the mapping comprises:
[0143] mapping data included in the streaming data corresponding to a corresponding sensor of the vehicle to attributes of the pattern corresponding to the corresponding sensor; and
[0144] The attributes of the pattern are mapped to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received model.
[0145] Clause 10. The method as described in Clause 8 or Clause 9, further comprising:
[0146] A user interface for a vehicle shadow service is provided, wherein the model is received from a user of the vehicle shadow service via the user interface.
[0147] Clause 11. The method of clause 10, wherein the mode is:
[0148] received from the user via the user interface; or
[0149] Provided by the vehicle shadow service based on the model received from the user via the user interface.
[0150] Clause 12. A method as described in any of clauses 7 to 11, wherein the vehicle shadows are organized according to a tree structure, wherein leaves of the tree structure correspond to nodes of the vehicle shadows and map to attributes of the pattern of the vehicle shadows.
[0151] Clause 13. A method as described in any one of clauses 7 to 11, wherein the vehicle shadows are organized according to a graph structure, wherein the nodes of the graph of the vehicle shadows are mapped to attributes of the pattern of the vehicle shadows, and wherein the edges between the nodes of the graph indicate relationships between the attributes of the vehicle shadows.
[0152] Clause 14. The method according to any one of clauses 7 to 13, further comprising:
[0153] receiving a first model of a first vehicle shadow to be used to represent a first view of the vehicle;
[0154] receiving a second model of a second vehicle shadow to be used to represent a second view of the vehicle;
[0155] generating, based on the received first model, a first mapping of corresponding sensor data elements included in the streaming data to one or more nodes of the first vehicle shadow; and
[0156] generating, based on the received second model, a second mapping of at least some other corresponding sensor data elements included in the streaming data to one or more nodes of the second vehicle shadow,
[0157] Wherein maintaining the updated version of the vehicle shadow includes maintaining updated versions of the first vehicle shadow and the second vehicle shadow of the vehicle.
[0158] Clause 15. One or more non-transitory computer-readable storage media storing program instructions that, when executed on or across one or more processors, cause the one or more processors to:
[0159] receiving a model to be used for vehicle shadows;
[0160] generating, based on the received model and associated schema, a mapping of corresponding sensor data elements included in the streaming data provided by the vehicle to one or more nodes of the vehicle shadow; and
[0161] An updated version of the vehicle shadow is maintained, wherein the updated version of the vehicle shadow is updated based on the streaming data to reflect a current state of the vehicle.
[0162] Clause 16. The one or more non-transitory computer-readable storage media of Clause 15, wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously.
[0163] Clause 17. One or more non-transitory computer-readable storage media as described in Clause 15 or Clause 16, wherein to generate the mapping, when the program instructions are executed on or across the one or more processors, the program instructions further cause the one or more processors to:
[0164] mapping sensor identifiers included in the streaming data and corresponding to respective sensors of the vehicle to attributes of the pattern corresponding to the respective sensors; and
[0165] The attributes of the pattern are mapped to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received model.
[0166] Clause 18. One or more non-transitory computer-readable storage media as described in any of Clauses 15 to 17, wherein when the program instructions are executed on or across the one or more processors, the program instructions further cause the one or more processors to:
[0167] A user interface for a vehicle shadow service is provided, wherein the model is received from a user of the vehicle shadow service via the user interface.
[0168] Clause 19. One or more non-transitory computer-readable storage media as described in any of clauses 15 to 18, wherein the vehicle shadows are organized according to a tree structure, wherein leaves of the tree structure correspond to nodes of the vehicle shadows and are mapped to attributes of the pattern of the vehicle shadows.
[0169] Clause 20. One or more non-transitory computer-readable storage media as described in any of clauses 15 to 18, wherein the vehicle shadows are organized according to a graph structure, wherein the nodes of the graph of the vehicle shadows are mapped to attributes of the pattern of the vehicle shadows, and wherein the edges between the nodes indicate relationships between the attributes of the vehicle shadows.
[0170] Clause 21. A system comprising:
[0171] One or more computing devices, the one or more computing devices being configured to:
[0172] receiving streaming data from a vehicle;
[0173] generating a first vehicle shadow representation of the vehicle, the first vehicle shadow representation comprising a subset of data included in the streaming data and associated with a first view of the vehicle; and
[0174] A second vehicle shadow representation of the vehicle is generated, the second vehicle shadow representation comprising at least a partially different subset of the data included in the streaming data and associated with a second view of the vehicle.
[0175] Clause 22. The system of clause 21, wherein the one or more computing devices are further configured to:
[0176] A user interface is provided, the user interface being configured to receive:
[0177] a first user selection of a first sensor data set from a first sensor set of the vehicle to be included in the first vehicle shadow representation representing the first view of the vehicle; and
[0178] a second user selection of a second sensor data set from a second sensor set of the vehicle to be included in the second vehicle shadow representation representing the second view of the vehicle, wherein the first sensor set and the second sensor set include at least some different sensors of the vehicle; and
[0179] Based on the received first and second user selections, a first data model for the first vehicle shadow representation and a second data model for the second vehicle shadow representation are generated.
[0180] Clause 23. The system of clause 22, wherein at least one of the first data model or the second data model for a given vehicle shadow representation in the first vehicle shadow representation or the second vehicle shadow representation comprises a tree structure,
[0181] The leaves of the tree structure are mapped to data streams from sensors of the vehicle corresponding to the first sensor set or the second sensor set whose sensor data is selected to be included in the first vehicle shadow or the second vehicle shadow.
[0182] Clause 24. The system of clause 22, wherein at least one of the first data model or the second data model for a given vehicle shadow representation in the first vehicle shadow representation or the second vehicle shadow representation comprises a graph structure,
[0183] Wherein the nodes of the graph structure are mapped to data streams from sensors of the vehicle corresponding to the first sensor set or the second sensor set whose sensor data is selected to be included in the first vehicle shadow or the second vehicle shadow, and wherein the edges between the nodes indicate relationships between the selected sensors.
[0184] Clause 25. The system of any one of clauses 22 to 24, wherein the user interface is further configured to receive:
[0185] User selection of one or more operating characteristics of the first vehicle shade or the second vehicle shade, wherein the supported operating characteristics to select from include one or more of the following:
[0186] an access control list defining access rights to one or more types of sensor data included in the first vehicle shadow or the second vehicle shadow;
[0187] A replication rule, the replication rule being used to replicate the first vehicle shadow or the second vehicle shadow stored in a first data jurisdiction to one or more other data jurisdictions;
[0188] an encryption rule defining a type of sensor data included in the first vehicle shadow or the second vehicle shadow to be encrypted; or
[0189] A query interface rule defines a query language to be used to query the first vehicle shadow or the second vehicle shadow.
[0190] Clause 26. A method comprising:
[0191] receiving, at a vehicle shade service, a user-selected configuration of a vehicle shade for the vehicle;
[0192] receiving, at the vehicle shadow service, streaming data from the vehicle;
[0193] The vehicle shadow of the vehicle is generated via the vehicle shadow service, wherein the vehicle shadow includes a subset of data included in the streaming data according to the configuration selected by the user.
[0194] Clause 27. The method of Clause 26, further comprising:
[0195] receiving, at the vehicle shade service, a second user-selected configuration of a second vehicle shade for the vehicle; and
[0196] The second vehicle shadow of the vehicle is generated via the vehicle shadow service, wherein the second vehicle shadow includes at least a partially different subset of the data included in the streaming data according to the second user-selected configuration of the second vehicle shadow.
[0197] Clause 28. The method of Clause 27, further comprising:
[0198] A user interface for the vehicle shade service is provided, wherein the user-selected configuration for the vehicle shade and the second user-selected configuration for the second vehicle shade are submitted to the vehicle shade service by a first user and a second user, respectively, via the user interface of the vehicle shade service.
[0199] Clause 29. The method of Clause 28, further comprising:
[0200] receiving information from the vehicle or a manufacturer of the vehicle indicating a sensor type of a sensor included in the vehicle,
[0201] Wherein the user interface includes a list of the sensors of the vehicle selectable into a given user-selected configuration for a given vehicle shade of the vehicle.
[0202] Clause 30. The method of any one of clauses 26 to 29, wherein a tree structured data model is used for the vehicle shadow,
[0203] Wherein leaves of the tree structure are mapped to data streams from sensors corresponding to the subset of data in the streaming data selected to be included in the vehicle shadow.
[0204] Clause 31. A method as described in any one of clauses 26 to 29, wherein a graphical structure data model is used for the vehicle shadow,
[0205] Wherein the nodes of the graph structure are mapped to data streams from sensors corresponding to a subset of sensor data in the streaming data selected to be included in the vehicle shadow, and wherein the edges between the nodes indicate relationships between the sensors.
[0206] Clause 32. The method according to any one of clauses 26 to 31, further comprising:
[0207] Receiving a user selection of one or more operating characteristics of the vehicle shade, wherein the selectable supported operating characteristics include one or more of the following:
[0208] an access control list defining access permissions to one or more types of sensor data included in the vehicle shadow;
[0209] a replication rule for replicating the vehicle shadow from a first data jurisdiction to one or more other data jurisdictions;
[0210] encryption rules defining the type of sensor data included in the vehicle shadow to be encrypted; or
[0211] A query interface rule defines a query language to be used to query the vehicle shadow.
[0212] Clause 33. The method of clause 32 further comprising:
[0213] receiving a query formatted according to a graphical query language, wherein the query is directed to data included in the data subset of the streaming data included in the vehicle shadow; and
[0214] The query is responded to based on data stored in the vehicle shadow.
[0215] Clause 34. The method of clause 32, wherein responding to the query comprises:
[0216] Data of the vehicle shadow targeted by the query is identified via traversing one or more branches of the tree structure of the vehicle shadow.
[0217] Clause 35. The method of clause 32, wherein responding to the query comprises:
[0218] Data of the vehicle shadow targeted by the query is identified via traversing one or more nodes of a graph structure of the vehicle shadow.
[0219] Clause 36. One or more non-transitory computer-readable storage media storing program instructions that, when executed on or across one or more processors, cause the one or more processors to:
[0220] receiving streaming data from a vehicle;
[0221] A vehicle shadow of the vehicle is generated, wherein the vehicle shadow includes a subset of data included in the streaming data according to a user-selected configuration of the vehicle shadow.
[0222] Clause 37. One or more non-transitory computer-readable storage media as described in Clause 36, wherein when the program instructions are executed on or across the one or more processors, the program instructions further cause the one or more processors to:
[0223] A second vehicle shadow of the vehicle is generated, wherein the second vehicle shadow includes at least a partially different subset of the data included in the streaming data according to a second user-selected configuration of the second vehicle shadow.
[0224] Clause 38. One or more non-transitory computer-readable storage media as described in Clause 37, wherein when the program instructions are executed on or across the one or more processors, the program instructions further cause the one or more processors to:
[0225] A user interface is provided, the user interface being configured to receive:
[0226] the user-selected configuration of the vehicle shadow, wherein the user-selected configuration indicates a first sensor data set to be included in the vehicle shadow representing a first view of the vehicle; and
[0227] the second user-selected configuration of the second vehicle shadow, wherein the second user-selected configuration indicates a second sensor data set to be included in the second vehicle shadow representing a second view of the vehicle, wherein the first sensor data set and the second sensor data set include at least some different sensor data; and
[0228] A first data model for the vehicle shadow and a second data model for the second vehicle shadow are generated based on the received first user-selected configuration and the second user-selected configuration.
[0229] Clause 39. The one or more non-transitory computer-readable storage media of any one of clauses 36 to 38, wherein a tree structured data model is used for the vehicle shadow,
[0230] Wherein leaves of the tree structure are mapped to data streams from sensors of the vehicle corresponding to the subset of data included in the streaming data that has been selected to be included in the vehicle shadow.
[0231] Clause 40. The one or more non-transitory computer-readable storage media of any one of clauses 36 to 38, wherein a tree structured data model is used for the first vehicle shadow,
[0232] wherein nodes of the graph structure are mapped to data streams from sensors of the vehicle corresponding to the subset of sensor data included in the streaming data that has been selected to be included in the vehicle shadow,
[0233] The edges between the nodes indicate the relationships between the sensors.
[0234] Clause 41. A system comprising:
[0235] One or more computing devices configured to implement a vehicle shadow service, the vehicle shadow service configured to:
[0236] receiving streaming data from one or more sensors of the vehicle; and
[0237] maintaining a vehicle shadow for the vehicle, wherein data values of the vehicle shadow correspond to data included in the streaming data received from the vehicle; and
[0238] One or more computing devices, the one or more computing devices configured to implement a vehicle shadow management system for the vehicle shadow service, the vehicle shadow management system configured to:
[0239] receiving, via an application programming interface (API), one or more state change requests for the vehicle and the vehicle shadow;
[0240] storing one or more received state change requests in an update queue;
[0241] providing the vehicle with a next valid state change request from the update queue to perform the requested state change indicated in the next valid state change request; and
[0242] The vehicle shadow is updated in response to receiving an indication in the streaming data received from the one or more sensors of the vehicle indicating that a requested change of state has been performed at the vehicle.
[0243] Clause 42. The system of clause 41, wherein the vehicle shadow management system is further configured to:
[0244] Prior to providing the given state change request to the vehicle, the given state change request stored in the update queue is invalidated.
[0245] Clause 43. The system of clause 42, wherein the given state change request is overruled in response to receiving an indication in the streaming data indicating that one or more conditions of the vehicle have changed such that the given state change request is rendered invalid.
[0246] Clause 44. The system of Clause 42, wherein the given state change request is invalidated in response to receiving a subsequent state change request that invalidates the given state change request.
[0247] Clause 45. The system of any one of clauses 41 to 44, wherein the one or more computing devices configured to implement the vehicle shadow management system are further configured to:
[0248] providing, via a user interface, a list of state change requests included in the update queue;
[0249] receiving, via the user interface, an indication that one or more of the state change requests included in the update queue are to be invalidated; and
[0250] Prior to sending the one or more state change requests to the vehicle, the one or more state change requests in the update queue are invalidated.
[0251] Clause 46. A method comprising:
[0252] receiving, via an application programming interface (API), one or more state change requests for a vehicle or a vehicle shadow of the vehicle;
[0253] storing one or more received state change requests in an update queue;
[0254] providing one or more next valid state change requests from the update queue to the vehicle to perform the requested state change indicated in the one or more next valid state change requests; and
[0255] The vehicle shadow of the vehicle is updated in response to receiving an indication in streaming data received from one or more sensors of the vehicle indicating that a requested change of state has been performed at the vehicle.
[0256] Clause 47. The method of Clause 46, further comprising:
[0257] Prior to providing the given state change request to the vehicle, the given state change request stored in the update queue is invalidated.
[0258] Clause 48. The method of clause 47, further comprising:
[0259] receiving the streaming data from the one or more sensors of the vehicle, wherein the streaming data includes an indication that one or more conditions of the vehicle have changed such that the given state change request is rendered invalid,
[0260] wherein the given state change request is overridden in response to the indication in the streaming data that the one or more conditions of the vehicle have changed.
[0261] Clause 49. The method of Clause 47, further comprising:
[0262] receiving a subsequent state change request that invalidates the given state change request,
[0263] wherein the given state change request is invalidated in response to processing the subsequent state change request causing the given state change request to be invalidated.
[0264] Clause 50. A method as described in Clause 47, wherein the given state change request is invalidated in response to the given state change request expiring, wherein the given state change request expires after a threshold amount of time has passed since the given state change request was created, received or stored.
[0265] Clause 51. The method of any one of clauses 46 to 50, wherein a plurality of vehicle shadows are stored for the vehicle in a plurality of jurisdictions, and wherein one of the plurality of vehicle shadows stored in an authoritative jurisdiction serves as an authoritative vehicle shadow for the vehicle.
[0266] Clause 52. The method of clause 51, wherein a state change request for the vehicle received at a vehicle shadow of the vehicle in a non-authoritative jurisdiction is rendered invalid.
[0267] Clause 53. The method of any one of clauses 46 to 52, further comprising:
[0268] determining that the jurisdiction of authority for the vehicle changes from a first jurisdiction to a second jurisdiction;
[0269] designating a vehicle shadow of the vehicle in the second jurisdiction as the authoritative vehicle shadow; and
[0270] The designation as an authoritative vehicle shadow is removed from the vehicle shadow stored for the vehicle in the first jurisdiction.
[0271] Clause 54. The method of clause 53, further comprising:
[0272] After determining a change in authority jurisdiction, a change of state request stored at or received at the vehicle shadow in the first jurisdiction is invalidated.
[0273] Clause 55. The method of any one of clauses 46 to 54, further comprising:
[0274] An indication is received in the streaming data from the state change request message sensor of the vehicle confirming that the vehicle has received the one or more next valid state change requests provided to the vehicle.
[0275] Clause 56. The method of any one of clauses 46 to 55, wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously.
[0276] Clause 57. One or more non-transitory computer-readable storage media storing program instructions that, when executed on or across one or more processors, cause the one or more processors to:
[0277] receiving, via an application programming interface (API), one or more state change requests for a vehicle or a vehicle shadow of the vehicle;
[0278] storing one or more received state change requests in an update queue;
[0279] providing one or more next valid state change requests from the update queue to the vehicle to perform the requested state change indicated in the one or more next valid state change requests; and
[0280] The vehicle shadow of the vehicle is updated in response to receiving an indication in streaming data received from one or more sensors of the vehicle indicating that a requested change of state has been performed at the vehicle.
[0281] Clause 58. One or more non-transitory computer-readable storage media as described in Clause 57, wherein when the program instructions are executed on or across the one or more processors, the program instructions further cause the one or more processors to:
[0282] Prior to providing the given state change request to the vehicle, the given state change request stored in the update queue is invalidated.
[0283] Clause 59. The one or more non-transitory computer-readable storage media of Clause 58, wherein the given state change request is overridden in response to an indication in the received streaming data that the one or more conditions of the vehicle have changed.
[0284] Clause 60. The one or more non-transitory computer-readable storage media of Clause 58, wherein the given state change request is invalidated in response to processing a subsequent state change request that causes the given state change request to be invalidated.
Claims
1. A system comprising: One or more computing devices configured to implement a model builder for a vehicle shadow of a vehicle, the model builder configured to: receiving a model to be used for the vehicle shadow; and generating, based on the received model and the associated schema, a mapping of corresponding sensor data elements included in the streaming data provided by the vehicle to one or more nodes of the vehicle shadow; as well as One or more computing devices, the one or more computing devices being configured to implement a data storage system for the vehicle shadow, the data storage system being configured to: receiving the streaming data from the vehicle; and An updated version of the vehicle shadow is maintained, wherein the updated version of the vehicle shadow is updated based on the streaming data to reflect a current state of the vehicle. 2 . The system of claim 1 , wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously.
3. The system of claim 1 or claim 2, wherein to generate the mapping, the model builder is further configured to: mapping data included in the streaming data corresponding to a corresponding sensor of the vehicle to attributes of the pattern corresponding to the corresponding sensor; and The attributes of the pattern are mapped to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received model.
4. The system of any one of claims 1 to 3, wherein the schema further defines one or more transformations to be applied to streaming data of one or more sensors mapped to one or more attributes of the schema.
5. The system of claim 4, wherein for at least one attribute of the pattern, streaming data from two or more sensors are mapped to the at least one attribute, wherein a transformation is applied to the streaming data from the two or more sensors to generate an attribute value for the at least one attribute.
6. The system of any one of claims 1 to 5, wherein data in the data stream of at least one sensor of the plurality of sensors of the vehicle is mapped to two or more attributes of the schema.
7. The system of any one of claims 1 to 6, wherein the data storage system of the vehicle shadow is further configured to: verifying that the received streaming data conforms to the said schema, Wherein the updated version of the vehicle shadow is updated using the verified data conforming to the pattern.
8. A method comprising: receiving streaming data from the vehicle, wherein the streaming data comprises decomposed data streams from a plurality of sensors of the vehicle, and wherein the decomposed data streams are received asynchronously; as well as An updated version of a vehicle shadow of the vehicle is maintained, wherein the updated version of the vehicle shadow is updated based on the asynchronously received decomposed data stream of the streaming data to reflect a current state of the vehicle.
9. The method of claim 8, further comprising: receiving a model and an associated mode to be used for the vehicle shadow; as well as Based on the received model and the associated schema, a mapping of corresponding sensor data elements included in the streaming data to one or more nodes of the vehicle shadow is generated.
10. The method of claim 9, wherein said generating said mapping comprises: mapping data included in the streaming data corresponding to a corresponding sensor of the vehicle to attributes of the pattern corresponding to the corresponding sensor; as well as The attributes of the pattern are mapped to nodes of the vehicle shadow, wherein the nodes of the vehicle shadow are organized based on the received model.
11. The method of claim 9 or claim 10, further comprising: A user interface for a vehicle shadow service is provided, wherein the model is received from a user of the vehicle shadow service via the user interface.
12. The method of claim 11, wherein the mode is: received from the user via the user interface; or Provided by the vehicle shadow service based on the model received from the user via the user interface.
13. The method of any one of claims 8 to 12, wherein the vehicle shadows are organized according to a tree structure, wherein leaves of the tree structure correspond to nodes of the vehicle shadows and map to attributes of the patterns of the vehicle shadows.
14. A method as described in any one of claims 8 to 12, wherein the vehicle shadows are organized according to a graph structure, wherein the nodes of the graph of the vehicle shadows are mapped to attributes of the pattern of the vehicle shadows, and wherein the edges between the nodes of the graph indicate relationships between the attributes of the vehicle shadows.
15. The method according to any one of claims 8 to 14, further comprising: receiving a first model of a first vehicle shadow to be used to represent a first view of the vehicle; receiving a second model of a second vehicle shadow to be used to represent a second view of the vehicle; generating, based on the received first model, a first mapping of corresponding sensor data elements included in the streaming data to one or more nodes of the first vehicle shadow; as well as generating, based on the received second model, a second mapping of at least some other corresponding sensor data elements included in the streaming data to one or more nodes of the second vehicle shadow, Wherein maintaining the updated version of the vehicle shadow includes maintaining updated versions of the first vehicle shadow and the second vehicle shadow of the vehicle.
