Vehicle programming using pseudonymous logging and commands
Using pseudonymous identifiers in vehicle data management systems addresses privacy and security issues by allowing secure, efficient predictive maintenance and command execution without associating vehicle data with personal information.
Patent Information
- Application Number
- JP2024523589
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-21
- Filing Date
- 2022-10-20
- Publication Date
- 2024-11-06
AI Technical Summary
Existing vehicle data management systems rely on Vehicle Identification Numbers (VINs) that associate vehicle data with personal information, leading to privacy vulnerabilities and security risks, as well as inefficiencies in data processing and maintenance operations.
Implementing pseudonymous identifiers generated by vehicles to facilitate data transmission and command processing without associating with personal information, allowing network services to manage and predict vehicle conditions while maintaining privacy.
Enhances privacy and security in vehicle data management, enabling efficient predictive maintenance and command execution without revealing personal information, and reducing the risk of data breaches.
Smart Images

Figure 2024540929000001_ABST
Abstract
Description
[Technical field]
[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application is a non-provisional application and claims priority to U.S. Provisional Patent Application No. 63 / 262,856, entitled “VEHICLE PROGNOSTICS UTILIZING PSUEDONYMOUS LOGGING AND DIRECTIVES,” filed October 21, 2021, which is incorporated by reference in its entirety and for all purposes. Summary of the Invention
[0002] In general, computing devices and communication networks can be utilized to exchange data and / or information. In a typical application, a computing device can request content from another computing device over a communication network. For example, a user at a personal computing device can utilize a browser application to request a content page (e.g., a network page, a web page, etc.) from a server computing device over a network (e.g., the Internet). In such an embodiment, the user computing device can be referred to as a client computing device, and the server computing device can be referred to as a content provider. In another embodiment, the user computing device can collect or generate information and provide the collected information to the server computing device for further processing or analysis.
[0003] In general, various vehicles, such as electric vehicles, combustion engine vehicles, hybrid vehicles, etc., can be configured to collect information about the vehicle. In some scenarios, a maintenance facility may want to access operating parameters, sensor values, or other vehicle information, such as to monitor or calculate vehicle performance characteristics. In other scenarios, a maintenance facility may want to contact one or more vehicle users or owners to request that an action be performed. [Brief description of the drawings]
[0004] The present disclosure is described herein with reference to drawings of several embodiments that are intended to illustrate but not limit the disclosure. It should be understood that the accompanying drawings, which are incorporated in and constitute a part of this specification, are for the purpose of illustrating the concepts disclosed herein and may not be to scale. [Figure 1] FIG. 1 is a block diagram of an example environment for providing vehicle communications with network services in accordance with one or more aspects of the present application.
[0005] [Diagram 2] FIG. 1 illustrates an environment corresponding to a vehicle, in accordance with one or more aspects of the present application.
[0006] [Figure 3A] FIG. 2 illustrates an exemplary architecture for implementing a management component, according to an aspect of the present application.
[0007] [Figure 3B] FIG. 1 illustrates an example architecture for implementing a vehicle data service in accordance with aspects of the present application.
[0008] [Figure 4] FIG. 1 is a block diagram of an exemplary environment for interaction of a network service with an individual vehicle to create a pseudonym, according to one embodiment.
[0009] [Diagram 5] FIG. 1 is a block diagram of an example environment for interaction of an individual vehicle with a network service for transmission of vehicle data based on one or more pseudonymous identifiers, according to one embodiment.
[0010] [Figure 6A] FIG. 1 is a block diagram of an example environment for interaction of individual vehicles with a network service for transmitting vehicle commands, according to one embodiment.
[0011] [Figure 6B] FIG. 1 is a block diagram of an example environment between a network service for processing vehicle data and individual vehicles and the subsequent transmission of vehicle commands with one or more pseudonymous identifiers.
[0012] [Figure 7] FIG. 1 is a block diagram of an exemplary environment for an alternative embodiment of interaction between a network service 120 and a computing device 130 for transmitting vehicle commands.
[0013] [Figure 8] 1 is a flow chart illustrating a routine for vehicle pseudonym management according to one or more embodiments disclosed herein.
[0014] [Figure 9] 4 is a flow chart illustrating a routine for vehicle data transmission according to one or more embodiments disclosed herein.
[0015] [Figure 10] 4 is a flow chart illustrating a routine for vehicle command request processing according to one or more embodiments disclosed herein.
[0016] [Figure 11] 4 is a flow chart illustrating a routine for vehicle command request processing according to one or more embodiments disclosed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] In general, one or more aspects of the present disclosure relate to configuration and management of actions taken by vehicles based on vehicle data. By way of example, aspects of the present application include management of data communications between individual vehicles and a network service provider. Illustratively, vehicle data can include, but is not limited to, vehicle operation information, vehicle parameters, sensor configuration information, sensor values, environmental information, and the like. In other examples, aspects of the present application correspond to management of actions or commands taken by a select subset of vehicles based on communications generated by the network service provider. Aspects of the present application also include vehicle data processing to make predictions of vehicle states, errors, or conditions, or to consider such conditions, errors, or conditions as part of vehicle maintenance or repair. Illustratively, a network service receives the vehicle data and performs vehicle predictions.
[0018] In general, access to vehicle information has generally been limited to applications where vehicle data and vehicles are associated with an identity unique to an individual or vehicle. For example, several services may track vehicle ownership, vehicle performance data, vehicle maintenance information, etc. according to a unique identifier as a vehicle identification number ("VIN") assigned to a vehicle at the time of manufacture. Traditionally, the VIN number of a vehicle is also associated with personal information of the registered owner. Thus, such implementations require a tight association of the VIN number to the vehicle so that the maintenance business receiving the vehicle data associated with the VIN can tightly associate all received operational and performance data with an individual user. Since the VIN is known to both the maintenance business and the vehicle and is further associated with the owner, utilizing the VIN number for vehicle data reporting and processing does not provide privacy protection. Such systems / approaches may be vulnerable to tampering or security breaches. Furthermore, when one or more vehicles need to be serviced, the maintenance business may need to identify information about the vehicles.
[0019] To address at least some of the above inefficiencies, a network service provider may utilize pseudonymous identifiers to facilitate management of data communications between selected vehicles and remote services. By way of example, the pseudonymous identifier may correspond to an at least semi-unique identifier generated by or configured on the vehicle. The pseudonymous (fake name, anonymous) generation / configuration is performed such that the network service provider does not associate additional identifiers, such as VINs, associated with the vehicle, vehicle owner, vehicle user, etc. In this regard, each pseudonymous identifier represents a logical generic identifier for an individual vehicle that may be transmitted and processed without association with vehicle identification or user identification information.
[0020] Vehicles may have network communication capabilities that allow them to establish bidirectional communication with a network service. Each vehicle generates / configures a pseudonymous identifier and registers with the network service. The vehicle may then collect and transmit vehicle data (e.g., performance metrics, operating conditions, sensor values, etc.) associated with the pseudonymous identifier. Meanwhile, the network service provider may receive vehicle data for multiple vehicles without the information necessary to be able to identify any particular source of the vehicle data (e.g., a particular VIN or other identifier) other than the pseudonymous identifier. The network service provider may then make the collected vehicle data available for processing, such as diagnostic processing, usage processing, etc. Illustratively, the network service may utilize machine learning or other data processing techniques to identify vehicles with particular attributes, such as those that may be considered likely to break down or require maintenance. For example, such attributes may include, but are not limited to, accumulation of use / wear / damage, rate of accumulation of use / wear / damage, malfunctions, failures, indications of malfunctions occurring, etc. Examples of machine learning or data processing techniques include, but are not limited to, neural networks, physics-based models, probability models and methods, statistical analysis models, etc.
[0021] In some embodiments, a user of a network service may wish to trigger some action to be performed by selected vehicles that meet a selection criteria corresponding to collected vehicle data. For example, a network service provider may receive an action request that attempts to trigger a service request or the execution of a diagnostic / correction process for vehicles that meet the selection criteria. In another example, a network service provider may receive an action request that attempts to provide a notification to a user / owner of a vehicle that meets the selection criteria. Because the collected data that meets the selection criteria is associated only with a pseudonymous identifier, the network service cannot directly send a communication to the target vehicle, such as via direct communication. Thus, the network service provider may publish a vehicle command that corresponds to a list of pseudonyms that are requested to perform some responsive action.
[0022] The individual vehicle is then configured to poll the published vehicle command list with the pseudonym and determine whether any of the listed pseudonyms match the individual vehicle's pseudonym. If there is a match, the vehicle can trigger the implementation of a response action. For example, the vehicle can generate a communication including additional information to the network service provider or requesting additional instructions. The additional information or transmission can omit the pseudonym identifier such that the network service provider cannot associate the matching pseudonym identifier with the additional transmission. The additional information can include vehicle VIN information or other identifiers that enable the maintenance entity to perform further processing to identify corrective actions or other maintenance in response to the identified selection criteria. The remaining vehicle VINs that have not performed corrective actions or other maintenance are notified or issued a response command. Additionally, the maintenance technician may be provided with a notification regarding the proposed corrective action. Additionally, the network service can interact with one or more computing devices, such as a mobile device, associated with the user of the vehicle to provide the notification, additional information, or other information.
[0023] In some embodiments, the network service by utilizing the vehicle data can perform vehicle predictions and provide them as instructions to the vehicle. Illustratively, the network service can process the vehicle data and predict that the vehicle is likely to experience mechanical problems. For example, if the vehicle data indicates that the vehicle's CAN communication has communication failures, the network service can predict that a MOSFET switch installed in the communication circuit is faulty. In another example, if the vehicle data indicates that the vehicle's electronic components are frequently failing, the network service can predict that the 12V battery installed in the vehicle needs to be replaced.
[0024] In some embodiments, the predictions can be performed by utilizing a machine learning component. The machine learning component can include various algorithms for performing the predictions and a training algorithm for training the machine learning component. For example, the training algorithm can monitor a log file of vehicle predictions and any vehicles that have performed corrective actions and retrain the prediction algorithm accordingly.
[0025] In some embodiments, the prediction can be performed by grouping the vehicles based on a criterion. Illustratively, the criterion can be based on the number of vehicles with the same or similar concerns, and these vehicles can be grouped together. For example, if the criterion is a number of vehicles, such as 100 vehicles, the network service can group these vehicles and perform the prediction. In some embodiments, the network service can monitor the vehicle data received from the group and perform the prediction. For example, if a group of vehicles indicates that the batteries of these vehicles are depleting faster than other vehicles not in the group, the network service can monitor each vehicle data received from this group of vehicles. If one or more of the vehicles in the group have a significant problem, the network service can perform the prediction and provide the results to users of the vehicles in the group, even if the number of vehicles in the group does not meet the criterion.
[0026] While various aspects are described according to exemplary embodiments and feature combinations, those skilled in the art will appreciate that the examples and feature combinations are exemplary in nature and should not be construed as limiting. More specifically, aspects of the present application may be applicable to various types of vehicle data or vehicle processes. However, those skilled in the art will appreciate that aspects of the present application are not necessarily limited in application to any particular type of vehicle data, data communications, or exemplary interactions between a vehicle, an owner / user, and a network service provider. Such interactions should not be construed as limiting.
[0027] 1 illustrates a block diagram of an example environment of a system 100 in which a plurality of vehicles communicate with a network service via a network connection. The system 100 may comprise a network connecting a set of vehicles 110, a network service 120, and a computing device 130. The components may correspond to software modules implemented or executed by one or more external computing devices, which may be separate, standalone external computing devices. Thus, the components of the network service 120 should be considered as logical representations of services and do not require a specific implementation in the one or more external computing devices.
[0028] As shown in FIG. 1, a network 150 can connect the devices and modules of the system. A network can connect any number of devices. In some embodiments, the vehicle 110, the network service 120, and the computing device 130 can communicate or exchange data (e.g., establishing one or more communication channels) over the network 150. In some embodiments, the network service 120 provides network-based services to the vehicle 110 and the computing device 130 over the network 150. The network service 120 refers to a large shared pool of network-accessible computing resources (e.g., computational, storage, or networking resources, applications, or services) that can implement the network-based services and can be virtualized or bare metal. The network service 120 can provide on-demand network access to a shared pool of configurable computing resources that can be programmatically provisioned and released in response to customer commands. These resources can be dynamically provisioned and reconfigured to match variable loads. Thus, the concept of "cloud computing" or "network-based computing" can be considered both the applications delivered as services over a network and the hardware and software in the network services that provide those services.
[0029] In some embodiments, network 150 may be a secure network, such as a local area network, that securely communicates with network service 120 over the Internet. Network 150 may include any wired network, wireless network, or combination thereof. For example, network 150 may be a personal area network, a local area network, a wide area network, a wireless broadcast network (e.g., for radio or television), a cable network, a satellite network, a cellular network, or a combination thereof. As a further example, network 150 may be a publicly accessible network of linked networks that may be operated by a variety of different parties, such as the Internet. In some embodiments, network 150 may be a private or semi-private network, such as a corporate or university intranet. Network 150 may include one or more wireless networks, such as, for example, a Global System for Mobile Communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Long Term Evolution (LTE) network, a 5G (fifth generation wireless communication), or any other type of wireless network. Network 150 may use protocols and components for communicating over the Internet or any of the other aforementioned types of networks. For example, protocols used by network 150 may include HyperText Transfer Protocol (HTTP), HTTP Secure (HTTPS), Message Queuing Telemetry Transport (MQTT), Constrained Application Protocol (CoAP), etc. Protocols and components for communicating over the Internet or any of the other aforementioned types of communication networks are well known to those of skill in the art and thus will not be described in greater detail herein.
[0030] In some embodiments, each individual vehicle 110 is connected to a computing device 130 and a network 160. In these embodiments, the network 160 includes any combination of wired and / or wireless networks, such as, for example, one or more direct communication channels, a local area network, a wide area network, a personal area network, and / or the Internet. In some embodiments, communication between the vehicle 110 and the computing device 130 may be performed via a short-range communication protocol, such as Bluetooth, Bluetooth low energy ("BLE"), and / or near field communication ("NFC"). In some embodiments, the network 160 may be utilized as a backup network for the network 150. For example, if communication between the vehicle 110 and the network service 120 is disconnected or interrupted, communication may be performed by utilizing the network between the computing device 130 and the network service 120. In some embodiments, vehicle data may be periodically synchronized by utilizing the network 160. In some embodiments, each computing device 130 may establish a network 160 with multiple vehicles 110.
[0031] In some embodiments, networks 150, 160 may include some or all of the same communication protocols, services, hardware, etc. Thus, while the description herein may describe communication between vehicle 110 and computing device 140 over network 160, and communication between vehicle 110, network service 120, third party service provider 130, and computing device 140 may occur over network 150, communication of the devices and / or network-based services is not limited in this manner. The various communication protocols described herein are merely examples, and the application is not limited thereto.
[0032] In some embodiments, computing device 130 (e.g., also referred to as a user device) may be any computing device, such as a desktop, laptop or tablet computer, a personal computer, a tablet computer, a wearable computer, a server, a personal digital assistant (PDA), a hybrid PDA / cell phone, a cell phone, a smart phone, a set-top box, a voice command device, a digital media player, etc. In some embodiments, computing device 130 may execute an application (e.g., a browser, a standalone application, etc.) that allows a user to access an interactive user interface as described herein, view images, analyses, aggregated data, etc. In various embodiments, a user of computing device 130 may interact with vehicle and / or network services through various devices. Such interaction may typically be accomplished through an interactive graphical user interface or voice commands, although such interaction may alternatively be accomplished through command line and / or other means.
[0033] Illustratively, the network service 120, as used in the aspects of the present application, may include a vehicle data service 122 that may provide functionality in response to data received from the vehicle 110 and / or the computing device 130. In some embodiments, the vehicle periodically transmits vehicle data to the vehicle data service 122 using a pseudonymous identifier associated with a particular vehicle. In these embodiments, the vehicle data service 122 may process the vehicle data received from the vehicle and provide the command. For example, the vehicle data service 122 receives vehicle data from multiple vehicles 110, each vehicle associated with one pseudonymous identifier. The vehicle data service 122 then processes the vehicle data and posts the command using the pseudonymous identifier for each command. The network service 120 may further include a vehicle data store 124 configured to store the processed data and / or the vehicle data received from the multiple data. In some embodiments, the vehicle data store 124 may include any computer-readable storage medium and / or device (or a collection of data storage media and / or devices). Examples of data stores include, but are not limited to, optical disks (e.g., CD-ROM, DVD-ROM), magnetic disks (e.g., hard disk, floppy disk), memory circuits (e.g., solid state drives, random access memory (RAM)), and the like. Another example of vehicle data store 124 is a hosted storage environment that includes a collection of physical data storage devices (commonly referred to as "cloud" storage) that may be remotely accessible and rapidly provisioned as needed. Network services are represented in a simplified logical form and do not reflect all of the physical software and hardware components that may be implemented to provide the functionality associated with the network services.
[0034] Each of the vehicles 110 may include communication capabilities, including hardware and software, that facilitate interaction over one of a number of communication media and protocols. More specifically, the vehicles include a number of sensors, components, and data stores for acquiring, generating, and maintaining vehicle data, including operational data. In some embodiments, the information provided by the components may include processed information, such as from a vision system, where a controller, logic unit, processor, etc. may utilize inputs from one or more camera sensors to provide an output (e.g., processing raw camera image data and generating an output corresponding to the processing of the raw camera image information) to generate additional information. The camera sensors may be sensor components associated with the vision system to determine vehicle operational conditions, environmental conditions, or other information. In other embodiments, the camera sensors may be separate from the sensor components, such as for non-camera sensor components or vehicles with multiple camera sensors. In yet another example, the control components may utilize additional information acquired from or otherwise associated with a positioning system, a calendar system, or a time-based system.
[0035] For illustrative purposes, FIG. 2 illustrates an environment corresponding to a vehicle 110, according to one or more aspects of the present application. Each vehicle illustratively includes a management component 210 operable to implement one or more aspects of the present application described herein. In one aspect, the management component 210 can generate or configure a pseudonymous identifier that is utilized to identify the vehicle by a network service. The pseudonymous identifier can correspond to any one of a variety of unique or semi-unique identifiers. The pseudonymous identifier can be based on an attribute of the vehicle, such as a representation of a particular hardware or software component. In another example, the pseudonymous identifier can be selected, such as by random selection, from a list of available pseudonymous identifiers. The pseudonymous identifier(s) can be generated or configured at the time of manufacture, at the time of release from the manufacturer, etc. For simplicity, one or more vehicles are depicted generally as a single component, but include some of the functionality described and illustrated in other vehicles.
[0036] The environment of the vehicle 110 may include sensors 212 that may provide input for the operation of the vehicle or collection of information, as described herein. The collection of sensors 212 may include one or more sensors or sensor-based systems included in the vehicle or accessible by the vehicle during operation. The sensors 212 may be integrated into the vehicle. Alternatively, the sensors 212 may be provided by an interface associated with the vehicle, such as a physical connection, a wireless connection, or a combination thereof.
[0037] In one aspect, the sensors 212 may include a vision system that provides input to the vehicle, such as detection of objects, attributes of detected objects (e.g., location, speed, acceleration), presence of environmental conditions (e.g., snow, rain, ice, fog, smoke), and the like. For example, the vehicle 110 may include multiple sensors 212 (including cameras, operational sensors, and the like), a managing component 210, and a data store 214. In this example, the sensors 212 may provide vehicle operating parameters to the managing component 210 in real-time or near real-time. The managing component 210 may provide data related to control of the vehicle, such as steering direction, acceleration, braking, and the like. The data store 214 may store information regarding the current vehicle operating environment. In some embodiments, the vehicle 110 may rely on such a vision system for defined vehicle operating functions, without assistance from, or in place of, other conventional detection systems.
[0038] In yet another aspect, the sensor 212 may further include one or more positioning systems that may obtain reference information from external sources that enable various levels of accuracy in determining the vehicle's positioning information. For example, the positioning system may include various hardware and software components for processing information from a GPS source, a wireless local area network (WLAN) access point information source, a Bluetooth information source, a radio frequency identification (RFID) source, and the like. In some embodiments, the positioning system may obtain a combination of information from multiple sources. Illustratively, the positioning system may obtain information from various input sources and determine the vehicle's positioning information, a particular altitude of the current location. In other embodiments, the positioning system may also determine driving-related operating parameters, such as driving direction, speed, acceleration, and the like. The positioning system may be configured as part of a vehicle for multiple purposes, including automated driving applications, driving augmentation, or user-assisted navigation, and the like. Illustratively, the positioning system may include processing components and data that facilitate identification of various vehicle parameters or processing information.
[0039] In yet another aspect, the sensors 212 may include one or more navigation systems for identifying navigation-related information. Illustratively, the navigation system may obtain positioning information from a positioning system and identify characteristics or information related to the identified location, such as elevation, road grade, etc. The navigation system may also identify proposed or intended lane positions on a multi-lane road based on directions that have been provided or assumed to the vehicle user. Similar to the positioning system, the navigation system may be configured as part of the vehicle for multiple purposes, including automated driving applications, driving augmentation or user-assisted navigation, etc.
[0040] The local resources further include one or more management components 210, which may be hosted on the vehicle 110 or on a computing device 130 accessible by the vehicle (e.g., a mobile computing device, etc.). The management component 210 may illustratively access input from various sensors 212, process the input data, and store the processed data. For purposes of this application, the management component 210 will be described with respect to one or more functions related to the illustrative aspects. For example, the management component 210 may generate or configure a pseudonymous identifier by associating it with vehicle data generated from the multiple sensors 212. The management component 210 may communicate with the computing device 130 and the network service 120 via communications 216.
[0041] The environment may further include various additional sensor components or sensing systems operable to provide information regarding various operational parameters for use according to one or more operating conditions. The environment may further include one or more control components for processing the output, such as transmitting the data via a communication output, generating the data in a memory, transmitting the output to other processing components, etc.
[0042] 3A, an exemplary architecture for implementing the management component 210 on the vehicle 110 is described. The management component 210 may be part of a component / system that can generate or configure pseudonymous identifiers and provide functionality associated with processing and managing vehicle data for further use by network services. The management component 210 may be further configured to identify commands generated from the network service and perform one or more corrective actions based on the commands.
[0043] The architecture of Figure 3A is exemplary in nature and should not be construed as requiring a particular hardware or software configuration for the managing component 210. The general architecture of the managing component 210 shown in Figure 3A includes an arrangement of computer hardware and software components that may be used to implement aspects of the present disclosure. As shown, the managing component 210 may include a processing unit 302, a network interface 308, a computer-readable media drive 306, and an input / output device interface 304, all of which may communicate with each other via a communication bus. The components of the managing component 210 may be physical hardware components that may include one or more circuits and software models.
[0044] The network interface 308 may provide connectivity to one or more networks or computing systems, such as networks 150, 160 of FIG. 1. Thus, the processing unit 302 may receive information and instructions from other computing systems or services over the network. The processing unit 302 also communicates with memory 310 and may further provide output information via an input / output device interface. In some embodiments, the management component 210 may include more (or fewer) components than those shown in FIG. 3A.
[0045] The memory 310 may include computer program instructions that the processing unit 302 executes to implement one or more embodiments. The memory 310 generally includes RAM, ROM, or other persistent or non-transitory memory. The memory 310 may store an operating system 314 that provides computer program instructions used by the processing unit 302 in the general management and operation of the management component 210. The memory 310 may further include computer program instructions and other information for implementing aspects of the present disclosure.
[0046] The memory 310 can include a pseudonymous identifier management component 316. The pseudonymous identifier management component 316 may be configured to generate or configure a pseudonymous identifier by associating with vehicle data. Each pseudonymous identifier represents a logical generic identifier of an individual vehicle that may be transmitted and processed without association with vehicle identification or user identification. The pseudonymous identifier may correspond to any one of a variety of unique or semi-unique identifiers. The pseudonymous identifier may be based on an attribute of the vehicle, such as a representation of a particular hardware or software component. In another example, the pseudonymous identifier may be selected from a list of available pseudonymous identifiers, such as by random selection. The generation or configuration of the pseudonymous identifier(s) may occur at the time of manufacture, at the time of release from the manufacturer, etc. The pseudonymous identifier may be associated with a cryptographic or other security mechanism to prevent modification or corruption of the pseudonymous identifier by a user or an external service.
[0047] In some embodiments, the pseudonymous identifier management component 316 processes the vehicle data by adding a pseudonymous identifier corresponding to the vehicle. For example, the pseudonymous identifier management component 316 can add a pseudonymous identifier for each segment of vehicle data or group of vehicle data. In one embodiment, the pseudonymous identifier is automatically added to the vehicle data when the vehicle transmits the vehicle data to the network service. In some embodiments, the pseudonymous identifier management component 316 can generate a new pseudonymous identifier associated with the vehicle. For example, a vehicle manufacturer, administrator, or owner can request that the pseudonymous identifier be replaced with a new identifier. For example, a vehicle owner can request that the pseudonymous identifier be reset if the existing pseudonymous identifier information is publicly released. In this example, the pseudonymous identifier management component 316 can generate a new identifier or receive a new identifier from the vehicle manufacturer (e.g., an authorized maintenance facility, technician, or administrator of the vehicle manufacturer). In these embodiments, the pseudonymous identifier management component 316 can keep track of the previous pseudonymous identifier by associating the previous identifier with the new pseudonymous identifier.
[0048] In some embodiments, the pseudonymous identifier management component 316 can identify any vehicle activity (e.g., maintenance activity) performed on the vehicle's VIN number. For example, if a vehicle has had its brake fluid changed and a brake fluid record is stored with the vehicle's VIN number, the pseudonymous identifier management component 316 can associate the brake fluid history with the vehicle's pseudonymous identifier. In this example, the pseudonymous identifier management component 316 can identify the vehicle activity based on a public record search of the vehicle's VIN. In some embodiments, the pseudonymous identifier management component 316 can associate the pseudonymous identifier with one or more vehicle service requests, history, or parts. For example, if a vehicle orders a new part, the pseudonymous identifier management component 316 can associate the new part with the vehicle's pseudonymous identifier. The type or number of vehicle activities or maintenance is not limited by this disclosure.
[0049] The memory 310 may further include a vehicle data management component 318. In some embodiments, the vehicle data management component 318 may collect vehicle data. The vehicle data may include, but is not limited to, vehicle performance metrics, operating conditions, sensor values, location information, and the like. As shown in FIG. 2, the vehicle includes multiple sensors, components, and data stores for acquiring, generating, and maintaining vehicle data, including operational data. The collection and processing of vehicle data may be based on programmed configuration data, based on manual input from a user, or in response to a request from a network service.
[0050] The memory 310 may further include a command identification component 320. The command identification component 320 may be configured to identify one or more commands issued by a network service. The command may include a command that needs to be executed by the vehicle in response thereto, such as a diagnostic, repair, or update process. In some embodiments, the command identification component 320 may collect and process published / posted vehicle commands. In some embodiments, the command identification component 320 may identify a command corresponding to a vehicle by attempting to match a specific pseudonymous identifier of the vehicle with any of the pseudonymous identifiers associated with the vehicle command. If the command identification component 320 does not match the specific pseudonymous identifier of the vehicle, the vehicle command may be ignored.
[0051] The memory 310 may further include a command processing component 322. The command processing component 322 may process published / posted vehicle commands associated with the vehicle's pseudonymous identifier. In some embodiments, processing the vehicle command may trigger some responsive action by the vehicle. In one aspect, the command may include a command to be executed by the vehicle in response thereto, such as a diagnostic, repair, or update process. One or more actions may be considered mandatory or optional. In another aspect, the vehicle command may include a request to trigger an action by the vehicle owner / user, such as generating a notification to schedule a service call. Additionally, the vehicle may also send confirmation, status, or notification upon request or if the vehicle is pre-configured to send confirmation, status, or notification information. In some embodiments, the command processing component 322 processes the command to classify the command based on priority, type of action required (e.g., mandatory, optional, emergency, etc.), and the like. The command processing component 322 may further provide one or more instructions or recommendations to the vehicle owner or driver based on the result of processing the command.
[0052] 3B, an exemplary architecture for implementing vehicle data service 122 on network service 120 will be described. Vehicle data service 122 may be part of a component / system capable of providing functionality associated with vehicle 110 and / or computing device 130. Vehicle data service 122 may be configured to periodically receive vehicle data and issue vehicle commands based on processing of the vehicle data. Vehicle data service 122 may be configured to post vehicle commands with a list of pseudonymous identifiers based on the results of processing of the vehicle data. Vehicle data service 122 may also be configured to perform vehicle predictions or characterizations based on processing of the vehicle data.
[0053] The architecture of Figure 3B is exemplary in nature and should not be construed as requiring a particular hardware or software configuration for the vehicle data service 122. The general architecture of the vehicle data service 122 shown in Figure 3B includes an arrangement of computer hardware and software components that may be used to implement aspects of the present disclosure. As shown, the vehicle data service 122 may include a processing unit 342, a network interface 348, a computer-readable media drive 346, and an input / output device interface 344, all of which may communicate with each other via a communication bus. The components of the vehicle data service 122 may be physical hardware components that may include one or more circuits and software models.
[0054] The network interface 348 may provide connectivity to one or more networks or computing systems, such as the networks 150, 160 of FIG. 1. Thus, the computing device 140 may receive information and instructions from other computing systems or services over the network. The vehicle data service 122 may also communicate with a memory 350 and further provide output information via an input / output device interface. In some embodiments, the vehicle data service 122 may include more (or fewer) components than those shown in FIG. 3B.
[0055] The memory 350 may include computer program instructions that the processing unit 342 executes to implement one or more embodiments. The memory 350 typically includes RAM, ROM, or other persistent or non-transitory memory. The memory 350 may store an operating system 352 that provides computer program instructions used by the processing unit 342 in the general management and operation of the vehicle data service 122.
[0056] The memory 350 can include a command identification component 354. The command identification component 354 can receive a request for issuance of a vehicle command in a pseudonym. Illustratively, the vehicle command corresponds to one or more actions and associated parameters that are triggered by the command identification component 354 upon receipt. In one aspect, the command can include a command to be performed by the vehicle in response thereto, such as a diagnostic, repair, or update process. The one or more actions may be considered mandatory or optional. In another aspect, the vehicle command can include a request to trigger an action by the vehicle owner / user, such as generating a notification to schedule a service call.
[0057] In some embodiments, the command identification component 354 processes the vehicle command request. In one aspect, the command identification component 354 can verify that the request for vehicle data is authorized, such as via an authentication or authorization mechanism. In another aspect, the received request may not explicitly identify the pseudonymous identifier of interest, but provides selection criteria (e.g., all vehicles with mileage greater than 100,000 miles). Thus, the command identification component 354 can query stored vehicle data to identify appropriate pseudonymous identifiers associated with the selection criteria. In yet another aspect, if the selection criteria results in a set of pseudonymous identifiers that does not exceed a size threshold, the network service can reject the request, request additional criteria, or include additional pseudonymous identifiers in the set. As previously discussed, having a set of pseudonymous identifiers that exceed one or more thresholds can mitigate potential network service failures, allowing an individual or third party to repeatedly match VINs or other identifying information to a particular pseudonymous identifier.
[0058] The memory 350 can further include a command posting component 356. The command posting component 356 can post a vehicle command request that identifies a set of pseudonymous identifiers requested to implement the command request. In some embodiments, the command posting component 356 need not actively send vehicle command requests to each vehicle, nor need it include processing mechanisms that specifically identify a contact mechanism (e.g., a network address) for each pseudonymous identifier. Rather, individual vehicles independently contact the network service for the published list of pseudonymous identifiers and vehicle commands.
[0059] In some embodiments, the command posting component 356 posts the vehicle command with the list of pseudonymous identifiers. Illustratively, individual vehicles need not be configured to send requests at the same time. The sending of requests can be randomized or performed over a range of times (e.g., any time throughout the day) so that the sending of requests can be spread out to reduce the network processing resource requirements by the network service. In one embodiment, the command posting component 356 can provide a set of published / posted vehicle commands and associated pseudonymous identifiers. This can include identifying a complete list of pseudonymous identifiers or some sorted / filtered subset of the pseudonymous identifiers. This approach requires that the vehicle can match the pseudonymous identifier against the list of pseudonymous identifiers. In another embodiment, the vehicle can send the pseudonymous identifier of interest and the command posting component 356 can then determine whether a match occurs. The network service can then respond with a notification or confirmation. This embodiment can minimize the amount of data sent between the network service and the vehicle and can also reduce the impact on the vehicle's processing resources to process the list and identify potential matches.
[0060] The memory 350 may further include a network request component 358. The network request component 358 may collect network performance information, such as network bandwidth, or by predefined rules in accessing vehicle data, such as a predefined two-way data communication protocol. In some embodiments, the network request component 358 may identify when to initiate communication with the vehicle. The timing of initiating communication may be the timing of a request for vehicle data from the vehicle. In some embodiments, the network request component 358 may monitor the network performance information to determine when to initiate a request for vehicle data, what vehicle data is being requested, and the like. For example, the network request component 358 may utilize the collected network performance information to determine when a vehicle data request may be initiated. In another example, the network request component 358 may utilize the network performance information to select or filter from various requested information, such as selecting higher priority information during (relative) network conditions of lower quality. In a further example, the network request component 358 may implement different data transmission timings or intervals in scenarios where the quality of network conditions may be more variable or may be considered degraded. By way of example, network performance information may include, but is not limited to, available bandwidth, latency measurements, transmission error rates, and the like.
[0061] In some embodiments, the network request component 358 can configure a secondary network communication path with the computing device 130 in response to detecting a network degradation. For example, the vehicle and the network service can initially communicate over the network 150. In this example, if the network request component 358 detects that the vehicle 110 has a lost or interrupted network connection, the network request component 358 can automatically connect to the computing device 130 associated with the vehicle 110.
[0062] In some embodiments, the network request component 358 can determine an initial communication path between the vehicle and a network service or between the computing device and a network service. For example, the network request component 358 can establish an initial communication path between one of the computing device and the vehicle based on a criterion. The criterion can be based on a timing of a response received at the network request component 358. For example, if the network request component 358 receives a response from the vehicle before the computing device, the network request component 358 can establish an initial communication path between the vehicle and the network service. The criterion can also be based on network performance monitoring results. For example, the network request component 358 can compare the network performance of a network connection with the vehicle and the computing device.
[0063] The memory 350 may further include a prediction component 360. The prediction component 360 may be configured to make predictions for the vehicles based on processing the vehicle data received from the plurality of vehicles 110. In some embodiments, the prediction component 360 processes the data for the individual vehicles and provides a prediction result. For example, if the individual vehicle data indicates that the vehicle has a greater number of wheel spins than other similar vehicles, the prediction component 360 may predict that the vehicle is likely to require tire rotation or tire replacement in a shorter period of time than other similar vehicles. In this example, the prediction result may be provided to the vehicle user (e.g., an owner, driver, manager, etc.) as a command associated with the pseudonymous identifier of the vehicle. In some embodiments, the prediction result may be a recommendation to the vehicle user. For example, if the battery of a particular vehicle is depleting more quickly than other similar vehicles and the vehicle data indicates that the vehicle's interior lights are frequently turned on at night, the prediction component 360 may provide a recommendation, such as checking the vehicle's interior lights before leaving the vehicle.
[0064] In some embodiments, the prediction component 360 can perform predictions based on criteria. The criteria can be the number of vehicles with similar or the same issues in the vehicle data. For example, the prediction component 360 can collect 100 vehicles with issues with components such as the 12V battery or battery system. In some embodiments, the prediction component 360 can prioritize the groups. Illustratively, the prediction component 360 can prioritize a group of vehicles with safety issues as a group with a higher priority than other groups of vehicles with issues with other features or components that may not be safety related. For example, a group of vehicles with issues with their braking systems may have a higher priority than another group of vehicles with issues with their HVAC systems or entertainment systems. Priority can also be based on the number of vehicles in the group. For example, a group containing 10,000 vehicles may have a higher priority than another group containing 100 vehicles. In one embodiment, the prediction component 360 can monitor vehicle data for the vehicles in the group. In this embodiment, if data for one or more vehicles indicates urgent corrective action, prediction component 360 can provide a prediction result to vehicle users even if the group does not meet the grouping criteria that triggers the prediction. For example, a set of vehicles can be grouped based on a common or related braking system, and if one of the vehicles in the group has a brake failure, prediction component 360 can provide a prediction result to the vehicles in the group (and all associated users) even if the group does not meet the grouping criteria. The number of vehicles in the grouping criteria and the criteria for prioritizing the groups are not limited in this application, and the number of vehicles and the prioritization criteria can be determined based on a particular application.
[0065] The memory 350 may further include a machine learning component 362. The machine learning component 362 may be configured to perform predictions for a plurality of vehicles. In some embodiments, the machine learning component 362 monitors vehicle data for a plurality of vehicles, such as vehicle data batches. The machine learning component 362 also reviews prediction result data, such as prediction batches. The machine learning component 362 may include various prediction models and training models. Illustratively, the prediction models may be trained by using the training models. For example, if a vehicle has an issue with a communication component of the vehicle that is repaired by replacing a MOSFET, the training model of the machine learning component 362 trains the prediction model such that a corrective action in the event that a particular vehicle communication fails is to diagnose the MOSFET in the vehicle communication circuit.
[0066] In some embodiments, several different types of algorithms may be used by the machine learning component 362 to generate the model. For example, some embodiments herein may use logistic regression models, decision trees, random forests, convolutional neural networks, deep networks, and the like. However, other models are possible, such as linear regression models, discrete choice models, or generalized linear models. The machine learning algorithms may be configured to adaptively develop and update the model over time based on new inputs received by the machine learning component 362. For example, the model may be periodically regenerated as new human physical characteristics or biometric information becomes available to help keep the model's predictions more accurate as information changes over time. The machine learning component 362 is described in more detail herein.
[0067] Some non-limiting examples of machine learning algorithms that can be used to generate and update parameter functions or predictive models include supervised and unsupervised machine learning algorithms, including regression algorithms (e.g., ordinary least squares regression, etc.), instance-based algorithms (e.g., learning vector quantization, etc.), decision tree algorithms (e.g., classification trees and regression trees, etc.), Bayesian algorithms (e.g., Naive Bayes, etc.), clustering algorithms (e.g., k-means clustering, etc.), association rule learning algorithms (e.g., Apriori algorithm, etc.), artificial neural network algorithms (e.g., perceptrons), deep learning algorithms (e.g., deep Boltzmann machines, etc.), dimensionality reduction algorithms (e.g., principal component analysis, etc.), ensemble algorithms (e.g., stacked generalization, etc.), and / or other machine learning algorithms.
[0068] These machine learning algorithms may include any type of machine learning algorithm, including hierarchical clustering algorithms and cluster analysis algorithms, such as k-means algorithms. In some cases, the implementation of the machine learning algorithm may include the use of artificial neural networks. Machine learning techniques may be used to analyze large amounts (such as terabytes or petabytes) of player interaction data to generate models.
[0069] 4, exemplary interactions between a network service and individual vehicles to create pseudonyms will now be described. Although a set of interactions is shown, the application is not limited to any particular number of vehicles interacting with the network service. Rather, in some embodiments, the number of interactions between individual vehicles and the network service will be relatively large, including thousands or more individual vehicles.
[0070] In (1), the vehicle 110 (e.g., management component 210) may generate or configure a pseudonymous identifier that is utilized by network service 120 to identify the vehicle 110. As discussed above, the pseudonymous identifier may correspond to any one of a variety of unique or semi-unique identifiers. The pseudonymous identifier may be based on an attribute of the vehicle 110, such as a representation of a particular hardware or software component. In another example, the pseudonymous identifier may be selected, such as by random selection, from a list of available pseudonymous identifiers. The generation or configuration of the pseudonymous identifier(s) may occur at the time of manufacture, at the time of release from the manufacturer, etc.
[0071] At (2), the vehicle 110 may store the pseudonymous identifier in local memory for use in communications. The pseudonymous identifier may be associated with a cryptographic or other security mechanism to prevent modification or corruption of the pseudonymous identifier by a user or an external service.
[0072] At (3), individual vehicles 110 can transmit pseudonym registrations with network services 120 (such as vehicle data services 122). This process illustrates the first instantiation of the transmission of pseudonym identifiers between vehicles 110 and network services 120. Although the transmissions are illustrated as being transmitted in parallel, vehicles 110 may be triggered to register with network services 120 at various times or in response to triggering criteria, such as delivery of the vehicle to a new owner. In some embodiments, the timing of the transmission of the pseudonym can be based on a seed value, such as a randomly generated number, such that the transmission of the pseudonym is not closely related to the timing of delivery of the vehicle or generation of the pseudonym.
[0073] At (4), network service 120 processes the registration data using the pseudonymous identifier. Illustratively, network service 120 may instantiate one or more records, data stores, etc. based solely on the transmitted pseudonymous identifier and without further association with other identifying information associated with the vehicle, such as a VIN or user identifier.
[0074] 5, an exemplary interaction between the network service 120 and individual vehicles 110 for the transmission of vehicle data based on one or more pseudonymous identifiers is described. As noted above, while a set of interactions is shown, the application is not limited to any particular number of vehicles 110 interacting with the network service. Rather, in some embodiments, the number of interactions between individual vehicles and the network service 120 will be relatively large, including thousands or more of individual vehicles 110.
[0075] At (1), vehicle 110 can collect vehicle data (e.g., via management component 210). As described above, the vehicle includes a number of sensors, components, and data stores for acquiring, generating, and maintaining vehicle data, including operational data. The collection and processing of vehicle data may be based on programmed configuration data, based on manual input from a user, or in response to a request from a network service (not shown).
[0076] At (2), the vehicle 110 may be associated with a previously stored pseudonymous identifier that is maintained in local memory. The pseudonymous identifier and vehicle data may be associated with a cryptographic or other security mechanism to prevent modification or corruption of the pseudonymous identifier by a user or an external service.
[0077] In (3), one or more of the vehicles 110 may synchronize vehicle data with the computing device 130. In some embodiments, the synchronization may be performed periodically or in real-time. In some embodiments, a portion of the data may be synchronized with the computing device 130. In these embodiments, the portion of the data may be defined or specified by a user, a vehicle manufacturer, a vehicle manager, etc. For example, the computing device 130 may obtain only synchronized vehicle data related to engine oil management data. In this example, the computing device 130 may transmit the engine oil management data directly to the network service 120 by associating the data with a pseudonymous identifier for the vehicle. In some embodiments, process (3) may be an optional process.
[0078] At (4), individual vehicles can transmit vehicle data to the network service using the generated pseudonymous identifier. Although shown as a single transmission, the collection and transmission of vehicle data using the associated pseudonymous identifier can correspond to multiple transmissions. These transmissions may be scheduled for each individual vehicle or for groups of vehicles. Additionally, while the transmissions are shown as being transmitted in parallel, the vehicles may be triggered to transmit vehicle data to the network service at various times or in response to trigger criteria such as an error, a particular sensor value, accumulation of a threshold amount of vehicle data, a change in a vehicle data value, etc. At (4), the network service processes the vehicle using the pseudonymous identifier. Illustratively, the network service can utilize an instantiated record, data store, etc. associated with a previously transmitted pseudonymous identifier without further association with other identifying information associated with the vehicle such as a VIN or user identifier. Thus, the network service can receive detailed information about the vehicle, including performance or operating parameters, even though it illustratively does not have the information necessary to identify the particular vehicle or vehicle owner providing (or associated with) the transmitted vehicle data.
[0079] In some embodiments, when a network connection between vehicle 110 and network service 120 is lost or interrupted, computing device 130 may send synchronized vehicle data to network service 120. For example, computing device 130 and vehicle 110 may periodically synchronize vehicle data by utilizing network 160, such as a short-range data communications network. In this example, computing device 130 may send vehicle data to network service 120 if vehicle 110 cannot connect to network 150.
[0080] 6A, an example interaction between network service 120 and individual vehicles 110 for the transmission of vehicle commands via one or more pseudonymous identifiers is described. As noted above, while a set of interactions is illustrated, the application is not limited to any particular number of vehicles 110 interacting with network service 120. Rather, in some embodiments, the number of interactions between individual vehicles 110 and network service 120 will be relatively large, including thousands or more individual vehicles.
[0081] In (1), network service 120 may pseudonymously process (or receive a request to process) the stored vehicle data. In one embodiment, network service 120 may analyze the collected performance data to identify one or more actions to be performed by vehicle 110 associated with the pseudonymous identifier. For example, network service 120 may perform a diagnostic process to identify potential hardware or software errors / faults indicated by the collected vehicle data. In another example, network service 120 may utilize processing techniques to facilitate grouping or organization of a set of vehicles 110 based on vehicle data such as operating parameters, vehicle attributes, operating area, usage characterization, etc. In some embodiments, processing of the stored vehicle data may be omitted or performed as a separate process and is not required herein.
[0082] In some embodiments, the network service 120 (prediction component 360) may make predictions for vehicles based on processing vehicle data received from multiple vehicles 110. In some embodiments, the prediction component 360 processes data for individual vehicles and provides prediction results. For example, if the individual vehicle data indicates that the vehicle has a greater number of wheel spins than other similar vehicles, the prediction component 360 may predict that the vehicle is likely to require tire rotation or tire replacement at a shorter interval than other similar vehicles. In this example, the prediction results may be provided to the vehicle user (e.g., owner, driver, manager, etc.) as instructions associated with the vehicle's pseudonymous identifier. In some embodiments, the prediction results may be recommendations to the vehicle user. For example, if a particular vehicle's battery system is deviating from nominally defined operating parameters (e.g., the battery is depleting more quickly than other similar vehicles) and the vehicle data indicates that the vehicle's interior lights are frequently turned on at night, the prediction component 360 may provide recommendations such as checking the vehicle's interior lights before leaving the vehicle.
[0083] In some embodiments, the prediction component 360 can perform predictions based on criteria. The criteria can be the number of vehicles with similar or the same issues in the vehicle data. For example, the prediction component 360 can collect 100 vehicles with issues with the 12V battery. In some embodiments, the prediction component 360 can prioritize the groups. Illustratively, the prediction component 360 can prioritize a group of vehicles with safety issues as a group with a higher priority than other groups of vehicles with issues with the vehicle's convenience features. In another example, a group of vehicles with issues with a detection system for semi-autonomous or autonomous driving may have a similar priority to a headlight system, but a higher priority than another group of vehicles with issues with tire rotation. The priority can also be based on the number of vehicles in the group. In one embodiment, the prediction component 360 can monitor vehicle data for the vehicles in the group. In this embodiment, if the data for one or more vehicles indicates urgent corrective action, the prediction component 360 can provide a prediction result to the vehicle user even if the group does not meet the grouping criteria that triggers the prediction. For example, if a group of vehicles are associated with a common or similar suspension system and one of the vehicles in the group has a suspension fault, the prediction component 360 may provide a prediction result to the entire group even though the group does not meet the grouping criteria. Similarly, if one vehicle in the same group has a data communication failure, the entire group may not receive a prediction result because the group does not meet the grouping criteria and the associated priority of the potential error is low. The number of vehicles in the grouping criteria and the criteria for prioritizing the groups are not limited in this application, and the number of vehicles and the prioritization criteria may be determined based on a particular application.
[0084] In some embodiments, the network service 120 (machine learning component 362) can perform predictions for multiple vehicles. In some embodiments, the machine learning component 362 monitors vehicle data for multiple vehicles, such as vehicle data batches. The machine learning component 362 also reviews prediction result data, such as prediction batches. The machine learning component 362 can include various prediction models and training models. Illustratively, the prediction models can be trained by using the training models. For example, if a vehicle has an issue with a communication component of the vehicle that is repaired by replacing a MOSFET, the training model of the machine learning component 362 trains the prediction model such that a corrective action in the event that a particular vehicle communication fails is to diagnose the MOSFET in the vehicle communication circuit.
[0085] At (2), the network service 120 receives a request for issuance of a vehicle command in a pseudonym. Illustratively, the vehicle command corresponds to one or more actions and associated parameters to be triggered by the vehicle upon receipt. In one aspect, the command may include a command to be performed by the vehicle in response thereto, such as a diagnostic, repair, or update process. The one or more actions may be considered mandatory or optional. In another aspect, the vehicle command may include a request to trigger an action by the vehicle owner / user, such as generating a notification to schedule a service call.
[0086] In yet another aspect, the vehicle command may include a request / command to transmit additional or supplemental vehicle data to network service 120 or a third party. For example, the vehicle command may include transmission of an identification of a particular vehicle (e.g., a VIN) and certain operational parameters that may be utilized for subsequent operation by network service 120. In such a response communication, the pseudonymous identifier may be omitted such that network service 120 is unable to associate the supplementally provided vehicle identifier with the pseudonymous identifier.
[0087] In a variation of the above, the vehicle order may include a list of specific vehicles that network service 120 is to track as a subset of the pseudonymous identifiers. Thus, the vehicle order may request the return of the pseudonymous identifiers in response to a matching VIN. In this regard, if the subset of pseudonymous identifiers is large enough, the maintenance service may not be able to definitively associate a particular VIN with a pseudonymous identifier.
[0088] At (3), network service 120 processes the vehicle command request. In one aspect, network service 120 can verify that the request for vehicle data is authorized, such as via an authentication or authorization mechanism. In another aspect, the received request may not explicitly identify the pseudonymous identifier of interest, but provides selection criteria (e.g., all vehicles with mileage greater than 100,000 miles). Thus, network service 120 can query stored vehicle data to identify appropriate pseudonymous identifiers associated with the selection criteria. In yet another aspect, if the selection criteria results in a set of pseudonymous identifiers that does not exceed a size threshold, network service 120 can reject the request, request additional criteria, or include additional pseudonymous identifiers in the set. As discussed above, having a set of pseudonymous identifiers that exceed one or more thresholds can mitigate the potential network service 120 allowing an individual or third party to repeatedly match a VIN or other identifying information to a particular pseudonymous identifier.
[0089] At (4), network service 120 can post a vehicle command request that identifies a set of pseudonymous identifiers that are requested to fulfill the command request. In this embodiment, network service 120 need not actively send vehicle command requests to each vehicle, nor need it include processing mechanisms that specifically identify a contact mechanism (e.g., a network address) for each pseudonymous identifier. Rather, individual vehicles independently contact network service 120 for the published list of pseudonymous identifiers and vehicle commands.
[0090] At (5), each vehicle 110 requests posted vehicle commands with the list of pseudonymous identifiers. Illustratively, each vehicle need not be configured to send requests at the same time. The sending of requests can be randomized or performed over a range of times (e.g., any time throughout the day) so that the sending of requests can be spread out to reduce the network processing resource requirements by network service 120. At (6), network service 120 can respond to each request individually. In one embodiment, network service 120 can provide a set of published / posted vehicle commands and associated pseudonymous identifiers. This can include identifying a complete list of pseudonymous identifiers or some sorted / filtered subset of the pseudonymous identifiers. This approach requires that vehicle 110 can match the pseudonymous identifier against the list of pseudonymous identifiers. In another embodiment, the vehicle can send the pseudonymous identifier of interest, and network service 120 can then determine whether a match occurs. Network service 120 can then respond with a notification or confirmation. This embodiment may minimize the amount of data transmitted between network service 120 and the vehicle and may also reduce the impact on the vehicle's processing resources for processing the list and identifying potential matches.
[0091] In (7), the vehicle 110 (e.g., via the management component 210) may collect and process a set of published / posted vehicle orders and associated pseudonymous identifiers. As described above, the vehicle processes the set of published / posted vehicle orders and associated pseudonymous identifiers by attempting to match the vehicle's particular pseudonymous identifier with any of the pseudonymous identifiers associated with the vehicle orders. If the vehicle does not match the vehicle's particular pseudonymous identifier, the vehicle order may be ignored. Alternatively, the vehicle may initiate or process the vehicle order for a subset of the vehicles that match the pseudonymous identifier. As described above, initiation of a vehicle order may trigger some responsive action by the vehicle, the maintenance business, and / or the user of the vehicle. In one aspect, the order may include a command to be executed by the vehicle in response thereto, such as a diagnostic, repair, or update process. One or more actions may be considered mandatory or optional. In another aspect, the vehicle order may include a request that triggers an action by the vehicle owner / user, such as generating a notification to schedule a maintenance call. Additionally, the vehicle may also transmit confirmation, status, or notification upon request or if the vehicle is pre-configured to transmit confirmation, status, or notification information. This may include generating an interface on the vehicle, a mobile device on the vehicle, etc. For example, the vehicle command may include information that allows for pre-population of a service request form, or descriptive information that allows for scheduling of a service request, etc.
[0092] At (8), vehicle 110 may initiate a vehicle command. In some embodiments, vehicle 110 processes the command to categorize the command based on priority, type of action required (e.g., mandatory, optional, emergency, etc.), etc. Vehicle 110 may further provide one or more instructions or recommendations to the vehicle owner or driver based on the result of processing the command.
[0093] Now, with reference to FIG. 6B, an exemplary interaction between the network service and individual vehicles for processing vehicle data with one or more pseudonymous identifiers and subsequent transmission of vehicle commands is described. At (1), in response to the command, one or more vehicles can provide supplemental vehicle data, which can include VIN data or other identification as described above. At (2), the network service processes the received supplemental data. The additional information can include vehicle VIN information or other identifiers that enable the maintenance facility to perform further processing to identify corrective actions or other maintenance in response to the identified selection criteria. For example, the maintenance facility can determine maintenance records, parts orders, previous fault / error reports, etc.
[0094] At (3), the maintenance organization may identify any remaining vehicle VINs (in the subset that responded to the vehicle command and have not performed a corrective action or other maintenance) and send a request for additional corrective action at (4) and (5). At (6), a response command is notified or issued to the receiving vehicles. Further, a maintenance technician may be provided with a notification regarding the proposed corrective action. For example, parts may be pre-ordered at a given maintenance organization. Thus, additional corrective or supplemental actions may be administered or provided to individual vehicles having common diagnostic attributes.
[0095] Referring now to FIG. 7, an exemplary interaction of an alternative embodiment between network service 120 and computing device 130 for the transmission of vehicle commands with one or more pseudonymous identifiers is described. As discussed above, while a set of interactions is shown, the present application is not limited to any particular number of vehicles 110 and computing devices 130 interacting with network service 120. Rather, in some embodiments, the number of interactions between individual vehicles 110 and network service 120 is relatively large, including thousands or more individual vehicles. The processes (1)-(4) described in FIG. 6A can be used in FIG. 7.
[0096] At (5), computing device 130 may request posted vehicle commands with the list of pseudonymous identifiers. Illustratively, computing device 130 need not be configured to send requests simultaneously. The sending of requests may be randomized or performed over a range of times (e.g., any time throughout the day) so that the sending of requests can be spread out to reduce the network processing resource requirements by network service 120. At (6), network service 120 may respond to each request individually. In one embodiment, network service 120 may provide a set of published / posted vehicle commands and associated pseudonymous identifiers. This may include identifying a complete list of pseudonymous identifiers or some sorted / filtered subset of the pseudonymous identifiers. This approach requires that vehicle 110 be able to match the pseudonymous identifier against the list of pseudonymous identifiers. In another embodiment, computing device 130 may send the pseudonymous identifier of interest, and network service 120 may then determine whether a match occurs. Network service 120 may then respond with a notification or confirmation. This embodiment may minimize the amount of data transmitted between network service 120 and computing device 130 and may also reduce the impact on the processing resources of computing device 130 for processing the list and identifying potential matches.
[0097] In (7), the computing device 130 may collect and process a set of published / posted vehicle orders and associated pseudonymous identifiers. As described above, the computing device 130 processes the set of published / posted vehicle orders and associated pseudonymous identifiers by attempting to match the vehicle's particular pseudonymous identifier with any of the pseudonymous identifiers associated with the vehicle order. If the computing device 130 does not match the vehicle's particular pseudonymous identifier, the vehicle order may be ignored. Alternatively, as shown in FIG. 7, the computing device 130 may initiate or process the vehicle order for a subset of the vehicles that match the pseudonymous identifier. As described above, initiation of a vehicle order may trigger some responsive action by the computing device 130. In one aspect, the order may include a command to be executed by the computing device 130 in response thereto, such as a diagnostic, repair, or update process. One or more actions may be considered mandatory or optional. In another aspect, the vehicle order may include a request that triggers an action by the vehicle owner / user, such as generating a notification to schedule a service call. Additionally, the vehicle may also transmit confirmation, status, or notification information upon request or if the vehicle is pre-configured to transmit confirmation, status, or notification information.
[0098] At (8), computing device 130 may initiate a vehicle command. In some embodiments, computing device 130 processes the command to classify the command based on priority, type of action required (e.g., mandatory, optional, emergency, etc.), etc. Computing device 130 may further provide one or more instructions or recommendations to the vehicle owner or driver based on the result of processing the command.
[0099] At (9), the computing device 130 may synchronize vehicle data, such as updated vehicle data, with the vehicle 110 based on processing the command.
[0100] In an alternative embodiment, both the vehicle 110 and the computing device 130 can respond to a command posted by the network service 120. In this embodiment, the network service 120 can establish an initial communication path between the vehicle and the network service based on a criterion. The criterion can be based on the timing of the response received at the network service 120 (e.g., the network request component 358). For example, if the network request component 358 receives a response from the vehicle before the computing device, the network request component 358 can establish an initial communication path between the vehicle and the network service. The criterion can also be based on network performance monitoring results. For example, the network request component 358 can compare the network performance of the network connection with the vehicle and the computing device.
[0101] 8, vehicle pseudonym management routine 800 will now be described. Routine 800 is illustratively implemented by management component 210 implemented in vehicle 110. The process illustrated in FIG. 8 is illustrative in nature and should not be construed as limiting.
[0102] At block 802, the vehicle 110 (e.g., management component 210) may generate or configure a pseudonymous identifier that is utilized by the network service 120 to identify the vehicle 110. As described above, the pseudonymous identifier may correspond to any one of a variety of unique or semi-unique identifiers. The pseudonymous identifier may be based on an attribute of the vehicle 110, such as a representation of a particular hardware or software component. In another example, the pseudonymous identifier may be selected from a list of available pseudonymous identifiers, such as by random selection. The generation or configuration of the pseudonymous identifier(s) may occur at the time of manufacture, at the time of release from the manufacturer, etc.
[0103] At block 804, the vehicle 110 may store the pseudonymous identifier in local memory for use in communications. The pseudonymous identifier may be associated with a cryptographic or other security mechanism to prevent modification or corruption of the pseudonymous identifier by a user or an external service.
[0104] At block 806, each vehicle 110 may transmit the generated pseudonym with a network service 120 (such as vehicle data service 122). This process illustrates a first instantiation of the transmission of a pseudonym identifier between the vehicle 110 and the network service 120. Although the transmissions are illustrated as being transmitted in parallel, the vehicle 110 may be triggered to register with the network service 120 at various times or in response to a triggering criterion, such as delivery of the vehicle to a new owner. In some embodiments, the timing of the transmission of the pseudonym may be based on a seed value, such as a randomly generated number, such that the transmission of the pseudonym is not closely related to the timing of delivery of the vehicle or generation of the pseudonym. At block 806, the routine 800 may end.
[0105] 9, the vehicle data transmission routine 900 will now be described. The routine 900 is illustratively implemented by the management component 210 implemented in the vehicle 110. The process illustrated in FIG. 9 is illustrative in nature and should not be construed as limiting.
[0106] At block 902, the vehicle 110 may collect vehicle data (e.g., via the management component 210). As described above, the vehicle includes a number of sensors, components, and data stores for acquiring, generating, and maintaining vehicle data, including operational data. The collection and processing of vehicle data may be based on programmed configuration data, based on manual input from a user, or in response to a request from a network service (not shown).
[0107] At block 904, the vehicle 110 may be associated with the previously stored pseudonymous identifier that is maintained in local memory. The pseudonymous identifier and vehicle data may be associated with cryptographic or other security mechanisms to prevent modification or corruption of the pseudonymous identifier by a user or an external service.
[0108] In some embodiments, one or more of the vehicles 110 may synchronize vehicle data with the computing device 130. In some embodiments, the synchronization may be performed periodically or in real time. In some embodiments, a portion of the data may be synchronized with the computing device 130. In these embodiments, the portion of the data may be defined or specified by a user, a vehicle manufacturer, a vehicle manager, etc. For example, the computing device 130 may only obtain synchronized vehicle data related to engine oil management data. In this example, the computing device 130 may transmit the engine oil management data directly to the network service 120 by associating the data with a pseudonymous identifier for the vehicle. In some embodiments, process (3) may be an optional process.
[0109] At block 904, each vehicle may transmit vehicle data to the network service using the generated pseudonymous identifier. Although shown as a single transmission, the collection and transmission of vehicle data using the associated pseudonymous identifier may correspond to multiple transmissions. These transmissions may be scheduled for each individual vehicle or for groups of vehicles. Additionally, while the transmissions are shown as being sent in parallel, the vehicles may be triggered to transmit vehicle data to the network service at various times or in response to trigger criteria such as an error, a particular sensor value, accumulation of a threshold amount of vehicle data, a change in a vehicle data value, etc.
[0110] In some embodiments, when a network connection between vehicle 110 and network service 120 is lost or interrupted, computing device 130 may send synchronized vehicle data to network service 120. For example, computing device 130 and vehicle 110 may periodically synchronize vehicle data by utilizing network 160, such as a short-range data communications network. In this example, computing device 130 may send vehicle data to network service 120 if vehicle 110 cannot connect to network 150. Routine 900 may end at block 906.
[0111] 10, a vehicle command request processing routine 1000 will now be described. The routine 1000 is illustratively implemented by a management component 210 implemented in the vehicle 110. The process illustrated in FIG. 10 is illustrative in nature and should not be construed as limiting.
[0112] At block 1002, each vehicle 110 requests a posted vehicle command using the list of pseudonymous identifiers. Illustratively, each vehicle need not be configured to send requests at the same time. The sending of requests may be randomized or performed over a range of times (e.g., any time throughout the day) such that the sending of requests may be distributed to reduce network processing resource requirements by network service 120.
[0113] At block 1004, the vehicle 110 may receive (e.g., via the management component 210) a set of published / posted vehicle orders and associated pseudonymous identifiers. At block 1006, the vehicle 110 processes the set of published / posted vehicle orders and associated pseudonymous identifiers by attempting to match the vehicle's particular pseudonymous identifier with any of the pseudonymous identifiers associated with the vehicle orders. If the vehicle does not match the vehicle's particular pseudonymous identifier, the routine 1000 may end at block 1010 and the vehicle order may be ignored. If the vehicle matches the vehicle's particular pseudonymous identifier, the routine continues to block 1008. In some embodiments, the vehicle 110 may initiate or process a vehicle order for a subset of the vehicles that match the pseudonymous identifier. In these embodiments, initiating a vehicle order may trigger some responsive action by the vehicle 110. In one aspect, the order may include a command to be executed by the vehicle in response, such as a diagnostic, repair, or update process. One or more actions may be considered mandatory or optional. In another aspect, the vehicle command may include a request to trigger an action by the vehicle owner / user, such as generating a notification to schedule a service call. Additionally, the vehicle may also send confirmation, status, or notification upon request or if the vehicle is pre-configured to send confirmation, status, or notification information.
[0114] At block 1008, vehicle 110 may initiate a vehicle command. In some embodiments, vehicle 110 processes the command to categorize the command based on priority, type of action required (e.g., mandatory, optional, emergency, etc.), etc. Vehicle 110 may further provide one or more instructions or recommendations to the vehicle owner or driver based on the result of processing the command.
[0115] 11, vehicle command request processing routine 1100 will now be described. Routine 1100 is illustratively performed by vehicle data service 122 implemented in network services 120. The process illustrated in FIG. 10 is illustrative in nature and should not be construed as limiting.
[0116] At block 1102, the network service 120 receives a request for issuance of a vehicle command in a pseudonym. Illustratively, the vehicle command corresponds to one or more actions and associated parameters to be triggered by the vehicle upon receipt. In one aspect, the command may include a command to be executed by the vehicle in response thereto, such as a diagnostic, repair, or update process. The one or more actions may be considered mandatory or optional. In another aspect, the vehicle command may include a request to trigger an action by the vehicle owner / user, such as generating a notification to schedule a service call.
[0117] In yet another aspect, the vehicle command may include a request / command to transmit additional or supplemental vehicle data to network service 120 or a third party. For example, the vehicle command may include transmission of an identification of a particular vehicle (e.g., a VIN) and certain operational parameters that may be utilized for subsequent operation by network service 120. In such a response communication, the pseudonymous identifier may be omitted such that network service 120 is unable to associate the supplementally provided vehicle identifier with the pseudonymous identifier.
[0118] In a variation of the above, the vehicle order may include a list of specific vehicles that network service 120 is to track as a subset of the pseudonymous identifiers. Thus, the vehicle order may request the return of the pseudonymous identifiers in response to a matching VIN. In this regard, if the subset of pseudonymous identifiers is large enough, the maintenance service may not be able to definitively associate a particular VIN with a pseudonymous identifier.
[0119] In some embodiments, network service 120 may pseudonymously process (or receive requests to process) the stored vehicle data. In one embodiment, network service 120 may analyze collected performance data to identify one or more actions to be performed by vehicle 110 associated with the pseudonymous identifier. For example, network service 120 may perform a diagnostic process to identify potential hardware or software errors / faults indicated by collected vehicle data. In another example, network service 120 may utilize processing techniques to facilitate grouping or organization of a set of vehicles 110 based on vehicle data such as operating parameters, vehicle attributes, operating area, usage characterization, etc. In some embodiments, processing of stored vehicle data may be omitted or performed as a separate process and is not required herein.
[0120] In block 1104, network service 120 processes the vehicle command request. In one aspect, network service 120 may verify that the request for vehicle data is authorized, such as via an authentication or authorization mechanism. In another aspect, the received request may not explicitly identify the pseudonymous identifier of interest, but may provide selection criteria (e.g., all vehicles with mileage greater than 100,000 miles). Thus, network service 120 may query stored vehicle data to identify appropriate pseudonymous identifiers associated with the selection criteria. In yet another aspect, if the selection criteria results in a set of pseudonymous identifiers that does not exceed a size threshold, network service 120 may reject the request, request additional criteria, or include additional pseudonymous identifiers in the set. As previously discussed, having a set of pseudonymous identifiers that exceed one or more thresholds may mitigate the potential network service 120 allowing an individual or third party to repeatedly match a VIN or other identifying information to a particular pseudonymous identifier.
[0121] In some embodiments, the network service 120 (prediction component 360) can make predictions for vehicles based on processing vehicle data received from multiple vehicles 110. In some embodiments, the prediction component 360 processes data for individual vehicles and provides prediction results. For example, if the individual vehicle data indicates that the vehicle has a greater number of wheel spins than other similar vehicles, the prediction component 360 can predict that the vehicle is likely to require tire rotation or tire replacement at a shorter interval than other similar vehicles. In this example, the prediction results can be provided to the vehicle user (e.g., owner, driver, manager, etc.) as instructions associated with the vehicle's pseudonymous identifier. In some embodiments, the prediction results can be recommendations to the vehicle user. For example, if the battery of a particular vehicle is depleting more quickly than other similar vehicles and the vehicle data indicates that the vehicle's interior lights are frequently turned on at night, the prediction component 360 can provide recommendations such as checking the vehicle's interior lights before leaving the vehicle.
[0122] In some embodiments, the prediction component 360 can perform predictions based on criteria. The criteria can be the number of vehicles with similar or the same issues in the vehicle data. For example, the prediction component 360 can collect 100 vehicles with issues with the 12V battery. In some embodiments, the prediction component 360 can prioritize the groups. Illustratively, the prediction component 360 can prioritize a group of vehicles with safety issues as a group with a higher priority than other groups of vehicles with issues with the vehicle's convenience features. For example, a group of vehicles with brake issues has a higher priority than other groups of vehicles with heater issues. Priority can also be based on the number of vehicles in the group. For example, a group containing 10,000 vehicles may have a higher priority than another group containing 100 vehicles. In one embodiment, the prediction component 360 can monitor vehicle data for vehicles in the group. In this embodiment, if the data for one or more vehicles indicates urgent corrective action, the prediction component 360 can provide a prediction result to the vehicle user even if the group does not meet the grouping criteria that triggers the prediction. For example, if a group of vehicles is related to braking and one of the vehicles in the group has a brake failure, the prediction component 360 can provide a prediction result to a user of a vehicle in the group even if the group does not meet the grouping criteria. The number of vehicles in the grouping criteria and the criteria for prioritizing the groups are not limited in this application and the number of vehicles and the prioritization criteria can be determined based on a particular application.
[0123] In some embodiments, the network service 120 (machine learning component 362) can perform predictions for multiple vehicles. In some embodiments, the machine learning component 362 monitors vehicle data for multiple vehicles, such as vehicle data batches. The machine learning component 362 also reviews prediction result data, such as prediction batches. The machine learning component 362 can include various prediction models and training models. Illustratively, the prediction models can be trained by using the training models. For example, if a vehicle has an issue with a communication component of the vehicle that is repaired by replacing a MOSFET, the training model of the machine learning component 362 trains the prediction model such that a corrective action in the event that a particular vehicle communication fails is to diagnose the MOSFET in the vehicle communication circuit.
[0124] At block 1106, network service 120 may respond to each request individually. In one embodiment, network service 120 may provide a set of published / posted vehicle orders and associated pseudonymous identifiers. This may include identifying the complete list of pseudonymous identifiers or some sorted / filtered subset of the pseudonymous identifiers. This approach requires that vehicle 110 be able to match the pseudonymous identifier against the list of pseudonymous identifiers.
[0125] At block 1108, network service 120 may receive the selected response to the posted pseudonym command request. In some embodiments, vehicle 110 may transmit the target pseudonym identifier, and network service 120 may then determine whether a match occurs. In some embodiments, network service 120 may then respond with a notification or confirmation. This embodiment may minimize the amount of data transmitted between network service 120 and the vehicle and may also reduce the impact on the vehicle's processing resources for processing the list to identify potential matches.
[0126] At block 1110, network service 120 may process the received selected responses to post a vehicle command request that identifies a set of pseudonymous identifiers requested to implement the command request. In this embodiment, network service 120 need not actively send vehicle command requests to each vehicle, nor need it include processing mechanisms that specifically identify a contact mechanism (e.g., a network address) for each pseudonymous identifier. Rather, individual vehicles independently contact network service 120 for the published list of pseudonymous identifiers and vehicle commands. Routine 1100 may end at block 1112.
[0127] Various embodiments of the present disclosure may be systems, methods, and / or computer program products at any possible level of technical detail integration. The computer program product may include one or more computer-readable storage media having computer-readable program instructions for causing a processor to perform aspects of the present disclosure.
[0128] For example, the functions described herein may be performed when and / or in response to software instructions being executed by one or more hardware processors and / or any other suitable computing devices. The software instructions and / or other executable code may be read from one or more computer-readable storage media.
[0129] A computer-readable storage medium may be a tangible device capable of holding and storing data and / or instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device (including any volatile and / or non-volatile electronic storage device), a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer-readable storage media includes portable computer diskettes, hard disks, solid state drives, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in grooves on which instructions are recorded, and any suitable combination of the above. A computer-readable storage medium as used herein should not be construed as a transitory signal per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over wires.
[0130] The computer readable program instructions described herein can be downloaded to the respective computing / processing device from a computer readable storage medium or via an external computer or storage device over a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer readable program instructions from the network and transfers the computer readable program instructions to a computer readable storage medium in the respective computing / processing device for storage.
[0131] Computer readable program instructions (also referred to as, for example, "code," "instructions," "modules," "applications," "software applications," etc.) for performing the operations of the present disclosure may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or procedural programming languages, such as object-oriented programming languages such as Java, C++, and the "C" programming language or similar programming languages. The computer readable program instructions may be invoked from other instructions or from themselves, and / or in response to detected actions or interrupts. Computer readable program instructions configured to execute on a computing device may be provided on a computer readable storage medium and / or as a digital download (which may be originally stored in a compressed or installable format that requires installation, decompression, or decryption before execution) that can then be stored in the computer readable storage medium. Such computer readable program instructions may be partially or completely stored in a memory device (e.g., a computer readable storage medium) of the computing device during execution, for execution by the computing device. The computer readable program instructions may execute entirely on the user's computer (e.g., the computing device on which it is running), partially on the user's computer, as a stand-alone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can execute computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry to perform aspects of the present disclosure.
[0132] Aspects of the present disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.
[0133] These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, and the instructions executing via the processor of the computer or other programmable data processing apparatus create means for performing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer readable program instructions may also be stored on a computer readable storage medium capable of directing a computer, programmable data processing apparatus, and / or other device to function in a particular manner, such that a computer readable storage medium having instructions stored thereon includes a product including instructions implementing aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.
[0134] The computer-readable program instructions may also be loaded onto a computer, other programmable device, or other device to cause the computer, other programmable device, or other device to execute a series of operational steps to generate a computer-implemented process such that the instructions executed on the computer, other programmable device, or other device perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer may load the instructions and / or modules into its dynamic memory and transmit the instructions over a telephone, cable, or optical line using a modem. A modem local to the server computing system may receive the data over the telephone / cable / optical line and place the data on a bus using a converter device including appropriate circuitry. The bus may carry the data to a memory from which a processor may retrieve and execute the instructions. The instructions received by the memory may optionally be stored on a storage device (e.g., a solid state drive) either before or after execution by the computer processor.
[0135] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or part of instructions that includes one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions described in the blocks may be performed out of the order described in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Furthermore, in some implementations, some blocks may be omitted. The methods and processes described herein are also not limited to any particular order, and the blocks or states associated therewith may be executed in other orders as appropriate.
[0136] It should also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by a dedicated hardware-based system that performs the specified functions or operations or executes a combination of dedicated hardware and computer instructions. For example, any of the processes, methods, algorithms, elements, blocks, applications, or other functions (or portions of functions) described in the preceding sections may be embodied in electronic hardware such as application specific processors (e.g., application specific integrated circuits (ASICs)), programmable processors (e.g., field programmable gate arrays (FPGAs)), application specific circuits, etc. (any of which may combine custom hardwired logic, logic circuits, ASICs, FPGAs, etc. with custom programming / execution of software instructions to accomplish the techniques), and / or may be fully or partially automated.
[0137] Any of the above-mentioned processors and / or devices incorporating any of the above-mentioned processors may be referred to herein as, for example, a "computer," a "computing device," a "computing device," a "hardware computing device," a "hardware processor," a "processing unit," and the like. The computing devices of the above embodiments may typically (but not necessarily) be controlled and / or coordinated by operating system software, such as Mac OS, iOS, Android, Chrome OS, Windows OS (e.g., Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server, etc.), Windows CE, Unix, Linux, SunOS, Solaris, Blackberry OS, VxWorks, or other suitable operating systems. In other embodiments, the computing device may be controlled by its own operating system. A conventional operating system controls and schedules computer processes for execution, performs memory management, provides file systems, networking, I / O services, and provides user interface functionality such as a graphical user interface ("GUI"), among other things.
[0138] As mentioned above, in various embodiments, some functions may be accessible by a user via a web-based viewer (such as a web browser) or other suitable software program. In such implementations, the user interface may be generated by a server computing system and transmitted to a user's web browser (e.g., running on the user's computing system). Alternatively, data necessary to generate the user interface (e.g., user interface data) may be provided by the server computing system to the browser, where the user interface may be generated (e.g., the user interface data may be executed by the browser accessing a web service and configured to render the user interface based on the user interface data). The user may then interact with the user interface via the web browser. The user interface of some implementations may be accessible via one or more dedicated software applications. In some embodiments, one or more of the computing devices and / or systems of the present disclosure may include a mobile computing device, and the user interface may be accessible via such a mobile computing device (e.g., a smartphone and / or tablet).
[0139] Many variations and modifications can be made to the above-described embodiments, and the elements should be understood as being among other acceptable examples. All such modifications and variations are intended to be included within the scope of the present disclosure. The above description details certain embodiments. However, no matter how detailed the above content is described, it will be understood that the systems and methods can be implemented in many ways. Also, as mentioned above, it should be noted that the use of a particular term in describing a particular feature or aspect of the systems and methods should not be interpreted as meaning that the term is redefined herein to be limited to include any particular characteristic of the feature or aspect of the systems and methods with which the term is associated.
[0140] In particular, conditional language such as "can," "could," "might," or "may," unless otherwise specified or understood otherwise within the context in which it is used, is intended to generally convey that certain embodiments include certain features, elements, and / or steps, but other embodiments may not. Thus, such conditional language does not generally imply that the features, elements, and / or steps are in any way required by one or more embodiments, or that one or more embodiments necessarily include logic for determining whether those features, elements, and / or steps should be included in or performed in any particular embodiment, with or without user input or prompting.
[0141] Conjunctions such as the phrase "at least one of X, Y, and Z," or "at least one of X, Y, or Z," should be understood in the context in which they are generally used to convey that an item, term, etc. can be either X, Y, or Z, or any combination thereof, unless otherwise noted. For example, the term "or" is used in an inclusive (not exclusive) sense, e.g., when used to connect a list of elements, the term "or" means one, some, or all of the elements in the list. Thus, such conjunctive words are not generally intended to imply that a particular embodiment requires at least one of X, at least one of Y, and at least one of Z, respectively, to be present.
[0142] The term "a" as used herein should be given an inclusive interpretation rather than an exclusive interpretation. For example, unless otherwise specified, the term "a" should not be understood to mean "exactly one" or "only one." Instead, the term "a" means "one or more" or "at least one," regardless of whether it is used in the claims or elsewhere in the specification, and regardless of the use of quantifiers such as "at least one," "one or more," or "plurality" in the claims or elsewhere in the specification.
[0143] The term "comprising" as used herein should be given an inclusive rather than an exclusive interpretation. For example, a general purpose computer with one or more processors should not be interpreted as excluding other computer components, but may include components such as memory, input / output devices, and / or network interfaces, among others.
[0144] While the above detailed description has illustrated, described and pointed out novel features in relation to various embodiments, it will be understood that various omissions, substitutions and changes can be made in the form and details of the illustrated devices or processes without departing from the spirit of the disclosure. As will be recognized, certain embodiments of the invention described herein may be embodied in a form that does not provide all of the features and benefits described herein, since some features may be used or practiced separately from other features. The scope of the particular inventions disclosed herein is indicated by the appended claims, rather than the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims
1. 1. A system for providing vehicle predictions, comprising: receiving vehicle data associated with the pseudonymous identifiers from a plurality of vehicles; storing the vehicle data in a vehicle data store; Analyzing the stored vehicle data for a prediction for the vehicle associated with the stored vehicle data; receiving a request to issue a vehicle command at a pseudonymous identifier corresponding to the prediction for the vehicle; Posting a vehicle command including a set of pseudonymous identifiers associated with said request.
23. A system comprising: one or more computing processors and memory for executing computer-executable instructions for implementing a vehicle data service, the system being configured to:
2. The prediction of the vehicle may include: grouping the vehicles based on criteria; monitoring vehicle data received from the vehicles in the group; performing the vehicle prediction for vehicles in the group; and generating a vehicle prediction result associated with the pseudonymous identifier.
3. The system of claim 2 , wherein the vehicle prediction is performed using a machine learning component, the machine learning component including at least a vehicle prediction algorithm and a training algorithm.
4. The system of claim 1 , wherein the vehicle command comprises a command to be executed by the vehicle in response to identifying the vehicle command associated with the vehicle, such as a diagnostic, repair, or update process.
5. The system of claim 1 , wherein the pseudonymous identifier corresponds to one of a variety of unique or semi-unique identifiers associated with each vehicle of the plurality of vehicles.
6. The system of claim 1 , wherein each vehicle of the plurality of vehicles includes a plurality of sensors, components, and data stores for acquiring, generating, and maintaining the vehicle data.
7. The system of claim 1 , wherein the posted vehicle command makes public the vehicle command and a set of associated pseudonymous identifiers.
8. Each vehicle of the plurality of vehicles is a management entity, each performing management of pseudonymous identifiers associated with individual vehicles; Performing vehicle data transmission to the vehicle data service; Request a vehicle command from the vehicle data service 10. The system of claim 1, further comprising one or more external computing devices associated with a processor and memory for executing computer-executable instructions for implementing a management component configured to:
9. 1. A system for providing vehicle predictions, comprising: accessing a vehicle data store implemented in a network service and configured to store vehicle data; analyzing the stored vehicle data for predictions for a plurality of vehicles associated with the stored vehicle data; receiving a request for issuance of a vehicle command at a pseudonymous identifier corresponding to the prediction for the plurality of vehicles; and posting a vehicle command including a set of pseudonym identifiers associated with the request.
10. The prediction of the vehicle may include: grouping the vehicles based on criteria; monitoring vehicle data received from the vehicles in the group; performing the vehicle prediction for vehicles in the group; and generating a vehicle prediction result associated with the pseudonymous identifier.
11. The system of claim 10 , wherein the vehicle prediction is performed using a machine learning component, the machine learning component including at least a vehicle prediction algorithm and a training algorithm.
12. The system of claim 9 , wherein the vehicle data is received from the plurality of vehicles, and the vehicle data is associated with a pseudonymous identifier.
13. The system of claim 9 , wherein the vehicle command comprises a command to be executed by the vehicle in response to identifying the vehicle command associated with the vehicle, such as a diagnostic, repair, or update process.
14. The system of claim 9 , wherein the pseudonymous identifier corresponds to one of a variety of unique or semi-unique identifiers associated with each vehicle of the plurality of vehicles.
15. The system of claim 9 , wherein each vehicle of the plurality of vehicles includes a plurality of sensors, components, and data stores for acquiring, generating, and maintaining the vehicle data.
16. The system of claim 9 , wherein the posted vehicle command makes public the vehicle command and a set of associated pseudonymous identifiers.
17. Each vehicle of the plurality of vehicles is a management entity, each performing management of pseudonymous identifiers associated with individual vehicles; Execute vehicle data transmission to the network service; A vehicle command is requested from the network service.
10. The system of claim 9, comprising one or more external computing devices associated with a processor and memory for executing computer-executable instructions for implementing a management component configured to:
18. 1. A computer-implemented method for providing a prediction for a vehicle, comprising: management of pseudonymous identifiers, each associated with an individual vehicle, performed by the vehicles; performing, by the vehicle, a vehicle data transmission to the vehicle data service; receiving vehicle data from a plurality of vehicles via a vehicle data service; storing, by the vehicle data service, the vehicle data in a vehicle data store; analyzing, by the vehicle data service, the stored vehicle data for a prediction for a vehicle associated with the stored vehicle data; receiving, by the vehicle data service, a request for issuance of a vehicle command according to the pseudonym identifier, the vehicle command being requested from one or more of the vehicles; and posting a vehicle command including a set of pseudonym identifiers associated with the request.
19. The prediction of the vehicle may include: grouping the vehicles based on criteria; monitoring vehicle data received from the vehicles in the group; performing the vehicle prediction for vehicles in the group; and generating a vehicle prediction result associated with the pseudonymous identifier.
20. 20. The computer-implemented method of claim 19, wherein the vehicle prediction is performed using a machine learning component, the machine learning component including at least a vehicle prediction algorithm and a training algorithm.
21. 20. The computer-implemented method of claim 18, wherein the vehicle command comprises a command to be executed by the vehicle in response to identifying the vehicle command associated with the vehicle, such as a diagnostic, repair, or update process.
