Vehicle function control using sensor-based verification

A data processing system parses audio signals to generate and verify action data structures based on vehicle states, addressing inefficient bandwidth and computation issues by discarding invalid requests.

CN113335299BActive Publication Date: 2024-12-03GOOGLE LLC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110643583.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2017-10-03
Publication Date
2024-12-03
Estimated Expiration
2037-10-03

AI Technical Summary

Technical Problem

Excessive network transmission of network service data leads to inefficient bandwidth utilization and computational inefficiencies due to invalid requests, complicating data routing and response quality.

Method used

A data processing system that utilizes a natural language processor to parse audio signals, generates action data structures, and verifies vehicle states through sensor data to validate requests, discarding or disabling invalid requests to improve network efficiency and computational efficiency.

Benefits of technology

Reduces bandwidth utilization and processor load by preventing transmission of invalid requests, enhancing network and computational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113335299B_ABST
    Figure CN113335299B_ABST
Patent Text Reader

Abstract

The present disclosure relates to vehicle function control using sensor-based verification. The present disclosure generally relates to a data processing system for verifying vehicle functions in a voice-activated computer network environment. The data processing system can improve network efficiency by discarding invalid action data structures and requests before transmitting them over the network. The system can invalidate requests by comparing attributes of a vehicle state to attributes of a request state.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Description of the case

[0002] This application is a divisional application of Chinese invention patent application No. 201780091946.5, filed on October 3, 2017. Technical Field

[0003] The present invention relates to vehicle function control using sensor-based authentication. Background Art

[0004] Excessive network transmission of network service data between computing devices, based on packets or other means, may prevent computing devices from correctly processing network service data, completing operations related to network service data, or responding to network service data in a timely manner. Excessive network transmission of network service data may also complicate data routing or reduce response quality if the responding computing device reaches or exceeds its processing capacity, which may lead to inefficient bandwidth utilization. Part of the excessive network transmission may include transmission of requests that are invalid requests. Summary of the invention

[0005] According to aspects of the present disclosure, a system for verifying vehicle functions may include a data processing system. The system may include a natural language processor component executed by the data processing system. The natural language processor component may receive an input audio signal via an interface of the data processing system. The natural language processor component may parse the input audio signal to identify a request, a vehicle associated with the request, and a fulfillment interface associated with the request and the vehicle. The system may include a direct action application programming interface for generating a first action data structure based on the request. The system may include a verification engine for determining a vehicle state of a vehicle associated with the request based on a first sensor data set. The vehicle state may include a first plurality of attributes. The verification engine may determine the request state based on the request and a second sensor data set. The request state may include a second plurality of attributes. The verification engine may compare the second plurality of attributes of the request state with the first plurality of attributes of the vehicle state. The verification engine may send the first action data structure to the fulfillment interface to perform a function associated with the first action data structure based on one of the second plurality of attributes of the request state matching one of the first plurality of attributes of the vehicle state.

[0006] According to aspects of the present disclosure, a method for verifying vehicle functionality may include a natural language processor component executed by a data processing system and receiving an input audio signal via an interface of the data processing system. The method may include parsing the input audio signal by a natural language processor to identify a request, a vehicle associated with the request, and a fulfillment interface associated with the request and the vehicle. The method may include generating a first action data structure based on the request by a direct action application programming interface. The method may include determining a vehicle state of a vehicle associated with the request based on a first sensor data set by a verification engine. The vehicle state may include a first plurality of attributes. The method may include determining a request state by a verification engine based on the request and a second sensor data set. The request state includes a second plurality of attributes. The method may include comparing a second plurality of attributes of the request state with a first plurality of attributes of the vehicle state by the verification engine. The method may include sending a first action data structure to a fulfillment interface to perform a function associated with the first action data structure by verification and based on a match between one of the second plurality of attributes of the request state and one of the first plurality of attributes of the vehicle state.

[0007] In the following, these and other aspects and embodiments are discussed in detail. The foregoing information and the following detailed description include illustrative examples of the various aspects and embodiments, and provide an overview or framework for understanding the nature and character of the claimed aspects and embodiments. The accompanying drawings provide illustration and further understanding of the various aspects and embodiments, and are incorporated in and constitute a part of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The drawings are not intended to be drawn to scale. Like reference numbers and names in the various drawings indicate like elements. For clarity, not every component may be labeled in every drawing. In the drawings:

[0009] Figure 1 An example system for authenticating and controlling vehicle functions through sensor-based authentication is shown.

[0010] Figure 2 A top view of the vehicle is shown, and Figure 1 The interior of the vehicle shown in .

[0011] Figure 3 Shows the use of Figure 1 An example method for verifying vehicle functionality is shown in the example system.

[0012] Figure 4 is a block diagram of an example computer system. DETAILED DESCRIPTION

[0013] The following is a more detailed description of various concepts related to methods, apparatuses, and systems for multi-mode transmission of packet data in a computer network environment based on voice-activated data packets and their implementation. The various concepts introduced above and discussed in more detail below can be implemented in any of many ways.

[0014] The present disclosure is generally directed to a data processing system to verify requests within a packetized audio signal in a voice-activated computer network environment. The data processing system can improve the efficiency and effectiveness of the transmission of auditory data packets through one or more computer networks by, for example, discarding or otherwise disabling invalid requests (and their associated action data structures) before transmission through the network. The present solution can also improve computational efficiency by preventing the data processing system from performing further computational operations on action data structures that are invalid and should be discarded. By disabling the transmission of invalid requests, the system can reduce bandwidth utilization by not transmitting data packets carrying invalid action data structures on the network. Processing natural speech audio signals can be a computationally intensive task. By detecting requests that may be invalid, the system can enable the system to skip, temporarily skip, discard, or modify requests that may be invalid, thereby reducing computational waste.

[0015] The systems and methods described herein may include a data processing system that receives an audio input query, which may also be referred to as an audio input signal. The input audio signal may include a request to perform a function in a vehicle setting, such as opening a window or starting a car. The data processing system may identify the request from the input audio signal. The system may generate an action data structure based on the audio input query. The action data structure may include attributes indicating the requirements for fulfilling the request. The system may determine a vehicle state and attributes associated with the vehicle state. The system may compare and analyze the attributes of the action data structure with the attributes of the vehicle state to determine whether the request should be fulfilled. If the attributes of the vehicle state and the action data structure do not match, the system may disable or discard the action data structure (and the associated request), and prevent the fulfillment interface from fulfilling the request, thereby saving network bandwidth, reducing processor utilization, and saving power.

[0016] Figure 1 An example system 100 is shown that utilizes sensor-based authentication to authenticate and control vehicle functions. The system 100 may include at least one data processing system 102 , one or more client devices 128 , and one or more vehicles 140 .

[0017] The data processing system 102 may include an interface 104. The data processing system 102 may include a natural language processor (NLP) component 106 to parse audio-based input. The data processing system 102 may include an interface management component 108 to detect and manage interfaces of other devices in the system 100. The data processing system 102 may include an audio signal generator component 110 to generate audio-based signals. The data processing system 102 may include a direct action application programming interface (API) 112. The data processing system 102 may include a response selector component 114 to select a response to an audio-based input signal. The data processing system 102 may include a verification engine 116 to verify the audio-based input received by the data processing system 102. The data processing system 102 may include a data repository 118, in which the data processing system 102 may store parameters 120, policies 122, response data 124, and templates 126. The client device 128 and the vehicle 140 may include and execute instances of components of the data processing system 102. In some implementations, client device 128 and vehicle 140 may each include and execute an instance of data processing system 102 .

[0018] The system 100 may also include one or more client devices 128. The client device 128 may include a sensor 130, a speaker 132, an interface 104, and a transducer 136. The client device 128 may execute an instance of the NLP component 106. The system 100 may also include one or more data providers 138. The system 100 may include one or more vehicles 140. The vehicle 140 may include a sensor 130, a speaker 132, an interface 104, and a transducer 136. The vehicle 140 may execute an instance of the NLP component 106. The components of the system 100 may communicate via a network 142. In some embodiments, one or more client devices 128 may be located within an instance of the vehicle 140. For example, the client device 128 may be a mobile phone of a driver driving the vehicle 140. In some embodiments, one or more client devices 128 may be remote from the vehicle 140. For example, the driver's mobile phone is remote from the vehicle 140 after the driver parks and leaves the vehicle 140 to go to work.

[0019] Network 142 may include a computer network such as the Internet, a local area network, a wide area network, a metropolitan area network or other local area network, an intranet, a satellite network, other computer networks such as voice or data mobile phone communication networks, and combinations thereof. Data processing system 102, client device 128, and vehicle 140 may use network 142 to access information resources such as web pages, websites, domain names, uniform resource locators, or data providers 138. For example, data processing system 102 may access data providers 138 via network 142 that provide weather data for a particular location, such as a location associated with vehicle 140.

[0020] The network 142 may include, for example, a point-to-point network, a broadcast network, a wide area network, a local area network, a telecommunications network, a data communications network, a computer network, an ATM (asynchronous transfer mode) network, a SONET (synchronous optical network) network, an SDH (synchronous digital hierarchy) network, a wireless network or a wired network and combinations thereof. The network 142 may include a wireless link, such as an infrared channel or a satellite band. The topology of the network 142 may include a bus, a star, or a ring network topology. The network 142 may include a mobile phone network using any one or more protocols for communicating between mobile devices, including an advanced mobile phone protocol (AMPS), time division multiple access (TDMA), code division multiple access (CDMA), a global system for mobile communications (GSM), a general packet radio service (GPRS), or a universal mobile telecommunications system (UMTS). Different types of data may be transmitted via different protocols, or the same type of data may be transmitted via different protocols.

[0021] Client device 128 and vehicle 140 may each include at least one logical device, such as a computing device with a processor, communicating with data processing system 102 via network 142. Client device 128 and vehicle 140 may include instances of any components described with respect to data processing system 102. Client device 128 and vehicle 140 may include instances of data processing system 102. Client device 128 may include a desktop computer, a laptop computer, a tablet computer, a personal digital assistant, a smart phone, a mobile device, a portable computer, a thin client computer, a virtual server, a speaker-based digital assistant, or other computing device. Vehicle 140 may include a manual or self-driving car, a truck, a bus, an industrial vehicle, a motorcycle, or other transportation machine. Vehicle 140 may include one or more processors that may execute instances of data processing system 102 or any of its components. The processor may be a component of a head unit of the vehicle.

[0022] The client device 128 and the vehicle 140 may include at least one sensor 130, at least one transducer 136, at least one audio driver, and at least one speaker 132. The sensor 130 may include a microphone or an audio input sensor. The sensor 130 may also include at least one of a GPS sensor, a proximity sensor, an ambient light sensor, a temperature sensor, a motion sensor, an accelerometer, or a gyroscope. The sensor may include an occupancy or weight sensor. The transducer 136 may convert the audio input into an electronic signal. The audio driver may include a script or program executed by one or more processors of the client device 128 or the vehicle 140 to control the speaker 132. The speaker 132 may render an audio signal by converting the electrical signal into an audible wave.

[0023] The client device 128 and the vehicle 140 may be associated with an end user who inputs a voice query as an input audio signal (via the sensor 130) into the client device 128 or the vehicle 140 and receives an audio output in the form of a computer-generated voice that may be provided from the data processing system 102. In response to the input audio signal, the client device 128 and the vehicle 140 may also receive an action data structure to perform a predetermined function or action. The interface 104 may receive data messages or provide data messages to the direct action API 112 of the data processing system 102 and enable communication between components of the system 100. The client device 128 and the vehicle 140 may also include a user interface that enables a user to interact with components of the system 100.

[0024] The data processing system 102 of the system may include at least one server having at least one processor. For example, the data processing system 102 may include a plurality of servers located in at least one data center or server farm. The data processing system 102 may determine a request and a trigger keyword associated with the request from an audio input signal. Based on the request and the trigger keyword, the data processing system 102 may generate or select response data. The response data may be audio-based or text-based. For example, the response data may include one or more audio files that provide audio output or sound waves when rendered. The data within the response data may also be referred to as content items. In addition to audio content, the response data may also include other content (e.g., text, video, or image content).

[0025] The data processing system 102 may include multiple logically grouped servers and facilitate distributed computing technology. The logical group of servers may be referred to as a data center, a server farm, or a machine farm. The servers may also be geographically dispersed. A data center or a machine farm may be managed as a single entity, or a machine farm may include multiple machine farms. The servers within each machine farm may be heterogeneous-one or more servers or machines may operate according to one or more operating system platforms. The data processing system 102 may include servers in a data center stored in one or more high-density rack systems and associated storage systems, such as those located in an enterprise data center. In this way, the data processing system 102 with integrated servers may improve the manageability of the system, data security, physical security of the system, and system performance by locating servers and high-performance storage systems on a localized high-performance network. The centralization of all or some of the data processing system 102 components, including servers and storage systems and coupling them with advanced system management tools, allows for more efficient use of server resources, thereby saving power and processing requirements and reducing bandwidth usage. Each component of data processing system 102 may include at least one processing unit, server, virtual server, circuit, engine, agent, device, or other logic device such as a programmable logic array configured to communicate with data repository 118 and other computing devices.

[0026] The data processing system 102 may include a data repository 118. The data repository 118 may include one or more local or distributed databases, and may include a database management system. The data repository 118 may include a computer data storage or memory, and may store one or more parameters 120, one or more policies 122, response data 124, and templates 126, among others. The parameters 120, policies 122, and templates 126 may include information such as rules for a voice-based session between the client device 128, the data processing system 102, and the vehicle 140. The response data 124 may include content items for audio output or associated metadata, as well as input audio messages that may be part of one or more communication sessions with the client device 128.

[0027] An application, script, program, or other component associated with the data processing system 102 may be installed at the client device 128 or vehicle 140. The application may enable the client device 128 or vehicle 140 to communicate input audio signals (and other data) to the interface 104 of the data processing system 102. The application may enable the client device 128 and vehicle 140 to drive components of the client device 128 and vehicle 140 to render output audio signals.

[0028] The NLP component 106 of the data processing system can receive an input audio signal. The data processing system 102 can receive the input audio signal from the client device 128 or the vehicle 140. The first device can execute the NLP component 106, and the NLP component 106 can receive the input audio signal from the second device. For example, the vehicle 140 can execute the NLP component 106 and can receive the input audio signal from the client device 128.

[0029] The NLP component 106 can convert the input audio signal into recognized text by comparing the input audio signal to a stored set of representative audio waveforms and selecting the closest match. Representative waveforms can be generated across a large set of input audio signals. Once the input audio signal is converted into recognized text, the NLP component 106 can match the text to words associated with the action or output audio signal, for example, via a learning phase.

[0030] The NLP component 106 can identify at least one request or at least one trigger or hot keyword corresponding to the request from the input audio signal. The request can indicate the intent or subject of the input audio signal. The trigger keyword can indicate the type of action that may be taken. For example, the NLP component 106 can parse the input audio signal to identify at least one request to open a car window or skip to the next audio file in a music playlist. The trigger keyword may include at least one word, phrase, root or partial word, or derivative that indicates the action to be taken. For example, the trigger keyword "go" or "ok" or "hey."

[0031] The response selector component 114 can retrieve information from the data repository 118, which can be stored as part of the response data 124. The response selector component 114 can query the data repository 118 to select or otherwise identify a response phrase or content item from the response data 124, for example.

[0032] The audio signal generator component 130 may generate or otherwise obtain an output signal including a content item. The data processing system 102 may execute the audio signal generator component 110 to generate or create an output signal corresponding to a content item or request. For example, once the request is fulfilled, the signal generator component 110 may generate an audio output signal including the phrase "The action was completed".

[0033] The interface 104 may be a data interface or a network interface that enables the components of the system 100 to communicate with each other. The interface 104 of the data processing system 102 may provide or send one or more data packets including an action data structure, an audio signal, or other data to the client device 128 or the vehicle 140 via the network 142. For example, the data processing system 102 may provide an output signal from the data repository 118 or the audio signal generator component 110 to the client device 128. The data processing system 102 may also instruct the client device 128 or the vehicle 140 to perform the function indicated in the action data structure via data packet transmission. The output signal may be obtained or generated from the data processing system 102 (or other computing device), or the output signal may be transformed into one or more data packets (or other communication protocols), or the output signal may be transmitted from the data processing system 102 (or other computing device) to the client device 128 or the vehicle 140 as one or more data packets (or other communication protocols).

[0034] The direct action API 112 of the data processing system 102 can generate an action data structure based on, for example, a request. The action data structure can include data or instructions for performing a specified action to satisfy the request. In some implementations, the action data structure can be a data structure in JSON format or a data structure in XML format.

[0035] Depending on the action specified in the request, the direct action API 112 can execute code or a dialog script that identifies the parameters required to fulfill the request. An action data structure can be generated in response to the request. The action data structure can be included in a message sent to or received by a client device 128 or a vehicle 140. Based on the request parsed by the NLP component 106, the direct action API 112 can determine which of the client device 128 or the vehicle 140 the message should be sent to. For example, if the input audio signal includes "open a window", the NLP component 106 can identify the action word "open a window". The direct action API 112 can package the request into an action data structure for transmission to the vehicle 140. The action indication API 112 can access the vehicle ID from the response data 124 to determine which vehicle is associated with the user who generated the request. Once received, the vehicle 140 can process the action data structure and open the window of the car.

[0036] The action data structure may include information for completing the request. For example, the action data structure may be a data structure in XML or JSON format that includes attributes used to complete or otherwise fulfill the request. Attributes may include the location of the vehicle 140, the location of the client device 128, the authorization level of the user associated with the client device 128, a vehicle identifier, an interface identifier, a vehicle state, or a request state. In some embodiments, the request state includes one or more attributes that should be satisfied before fulfilling the action. For example, with the request "Ok, change the song", the request state may have the attribute {Requester: [Authorization, Passenger]}, indicating that the request should be an explicitly authorized user or passenger in the vehicle.

[0037] The direct action API 112 may retrieve the template 126 from the repository 118 to determine which fields or attributes to include in the action data structure. The direct action API 112 may determine the necessary parameters and may package the information into the action data structure. The direct action API 112 may retrieve content from the repository 118 to obtain information about the attributes of the data structure.

[0038] The direct action API 112 may populate fields with data from an input audio signal. The direct action API 112 may also populate fields with data from a data provider 138, a client device 128, or a vehicle 140. In some embodiments, the direct action API 112 may prompt a user to provide additional information when filling in fields. The templates 126 may be standardized for different types of actions, such as playing a media file through a vehicle's head unit, responding to a message, and performing a function within the vehicle. In some embodiments, an action data structure may be initially generated by a direct action API 112 executed by a remote data processing system 102. The remote data processing system 102 may send the action data structure to the data processing system 102 of the vehicle 140, which may add fields and attributes to the action data structure.

[0039] For example, the direct action API 112 can obtain the response data 124 (or parameters 120 or policies 122) from the data repository 118, and the data received from the client user 128 with the end user's permission to determine the location, time, user account, and logic or other information for booking a car from the car sharing service. The response data 124 (or parameters 120 or policies 122) can be included in the action data structure. When the content included in the action data structure includes end user data for authentication, the data can be passed through a hash function before being stored in the data repository 118.

[0040] The data processing system 102 (or its hardware, processor or memory components) may include, interface communication, or otherwise communicate with a verification engine 116. The verification engine 116 may verify or otherwise determine whether the actions and functions associated with the action data structure should be performed or implemented. When the verification passes, the verification engine 116 may cause the request to be fulfilled. The verification engine 116 may determine whether the requester has the right to perform the action, whether it is safe to perform the action, or whether other functions should be performed in place of the requested function or action.

[0041] For example, in response to receiving the input audio signal “Ok, open the trunk”, the verification engine 116 may determine not to open the trunk because the vehicle 140 is traveling along a road and it would be unsafe to open the trunk. In another example, in response to receiving the input audio signal “Ok, next song”, the verification engine 116 may determine that the user has permission to change songs and skip to the next song. The verification engine 116 may be executed by the client device 128, the vehicle 140, or a component thereof. For example, when the vehicle 140 is connected to the network 142, the vehicle 140 may execute a local instance of the verification engine 116. In some embodiments, when the verification engine 116 has a connection to the network 142, the vehicle 140 may offload computing work to the remote verification engine 116, and when the vehicle 140 does not have a connection to the network 142, the request is processed by the local instance of the verification engine 116.

[0042] The verification engine 116 can verify the action based on data from external sensor data, such as data received from a data provider 138, a sensor 130 of a client device 128, and a sensor 130 of a vehicle 140. The verification engine 116 can also verify the action based on the administrative rights of the user generating the input audio signal. The verification engine 116 can verify the action based on the vehicle state of the vehicle 140.

[0043] The verification engine 116 can determine the vehicle state of the vehicle 140 based on a set of sensor data. The vehicle state can indicate the current state of the vehicle 140 to fulfill the request. The vehicle state can indicate whether the vehicle 140 is driving, parking or idling. The vehicle state can indicate the speed of the vehicle 140. The verification engine 116 can use a combination of sensor data to determine the vehicle state. The combination of sensor data can be used to distinguish different states that may have similar conditions. For example, different states of stopping at a red light, stopping in a parking lot, stopping in traffic, and parking in a parking lot may have some similar conditions (e.g., a speed of 0mph), but different functions may be authorized in each different state. For example, when the vehicle 140 is parked in a parking lot, it may be safe to open the trunk, but when the vehicle 140 is stopped at a red light, it is unsafe to open the trunk. The vehicle state can include multiple sub-states, such as a motion state, an external environment state, an internal environment state, and a device state.

[0044] The motion substate may include attributes such as current and average speed, current and average acceleration, driving mode state, and gear state. The external environment substate may include attributes such as external weather conditions (e.g., raining, sunny, or snowing), external temperature, external weather condition forecast, and external temperature forecast. The internal environment substate may include attributes such as internal temperature and internal zone temperature. The equipment substate may include attributes such as HVAC state (e.g., air conditioning on, air conditioning off, heating, etc.), window state, lock state, trunk state, door ajar state, sunroof state, heated seat state, heated steering wheel state, headlight state, and interior light state.

[0045] The verification engine 116 can determine the vehicle state based on a set of sensor data, which can include sensor data from sensors 130 of the client device, sensor data from sensors 130 of the vehicle, data from data providers 138, or any combination thereof. Some of the attributes within the vehicle state can be determined from a single sensor (e.g., a door ajar state), and other attributes can be determined from a combination of sensor signals (e.g., a motion state can be determined from a combination of speed data and gear data).

[0046] The sensor data from the client device 128 may include location data determined by cellular tower triangulation or a GPS receiver in the client device 128, speed data determined by integrating location data, acceleration data, account data, authorization data, or any combination thereof. The sensor data may include data from one or more data providers 138. The data provider 138 may be an Internet-based data repository. The data provider 138 may make its data available through, for example, an API. The data provider 138 may provide weather data, location data, event data, location review data, forecast data, or any combination thereof to the verification engine 116.

[0047] The verification engine 116 can determine the request state based on the request parsed from the input audio file. The verification engine 116 can determine the request state based on the second sensor data set. The data in the first sensor data set and the second sensor data set can be received as data in an update data signal, a vector, a data array, a scalar value, or other format. The request state can include multiple attributes, under which the requested action can be performed or these attributes are required to fulfill the request. The request state can be a component of the action data structure or derived from the action data structure. For example, the request "OK, open the trunk" may include a request state with an attribute indicating that the trunk can be opened only when it is in a parked state and when the driver or authorized passenger requests it. For example, the request state can be {motion state: parked, requester: authorized passenger}.

[0048] The second sensor data set used to determine the request status may include sensor data from the first sensor data set that the verification engine 116 uses to determine the vehicle status. The second data set may also include the location of the client device 128 (or a user associated therewith) within the vehicle 140.

[0049] The verification engine 116 can compare the request state with the vehicle state to determine whether the action of the action data structure should be executed, implemented or further processed. For example, the vehicle state can indicate that the vehicle 140 is parked in a parking lot, the windows are closed and the external condition is raining (e.g., {motion state: parking, windows: closed, external condition: raining}). For example, when the input audio signal is "OK, open the windows", the verification engine 116 can determine that the request state of the request requires that the request comes from an authorized user, the driving attribute can be driving or parking, and the weather attribute must be a non-rainy day (e.g., {requester: authorization, movement state: [driving, parking], external condition: [sunny, cloudy, cloudy]}). Comparing the vehicle state with the request state, the verification engine 116 can determine that the external condition attribute of the vehicle state does not match (or is not an element of) the external condition attribute of the request state. Because the state does not match, the verification engine 116 can determine that the request should not be fulfilled because it is raining outside the vehicle 140 and the window should not be opened when it rains.

[0050] For example, when the verification engine 116 determines that the function should not be performed, the verification engine 116 can generate a request for confirmation, which is presented to the user via the interface 104 of the client device 128 or the vehicle 140. The confirmation request can ask the user whether the user wants to override the verification engine's decision not to perform the request. When the verification engine 116 determines that the function should not be performed, the verification engine 116 can propose to modify the action data structure. Continuing with the above example, the verification engine 116 can generate an audio-based prompt asking the user whether to deploy the sunroof.

[0051] Figure 2 A top view of a vehicle 140 is shown, and the interior of the vehicle 140 is shown. The interior of the vehicle 140 may include a plurality of seats 200. Each seat 200 may include one or more sensors 130. The sensors 130 may be weight or occupancy sensors. The interior of the vehicle 140 may include a plurality of speakers 132. The vehicle 140 may also include a head unit 202, which may execute one or more components described with respect to the data processing system 102 or the vehicle 140. For example, with the user's consent, the speaker 132 may generate sub-audio tones 204. The sub-audio tones 204 may be tones rendered by the speaker 132 that are not within a normal frequency range detectable by the user. The system 100 may use audible tones in place of the sub-audio tones 204. The head unit 202 may include all components of a data processing system within the vehicle 140. For example, the head unit 202 may include a data processing system 102 configured as a digital audio assistant application.

[0052] The verification engine 116 can determine the relative position of the client device 128 within the vehicle 140. The location of the client device 128 can be incorporated into one or more attributes of the request state or the vehicle state. The location or position of the client device 128 is a relative location and can include different levels of resolution. For example, the relative location can be an area associated with one of the seats 200 (e.g., client device 128(1) is associated with passenger seat 200), an area associated with a different zone (e.g., client devices 128(1) and 128(2) are in the front zone, and no client device 128 is in the rear zone).

[0053] The relative position of the client device 128 within the vehicle 140 may be determined using the sub-audible tones 204. The relative position of the client device 128 within the vehicle 140 may also be determined based on sensor data from the sensor 130. The relative position of the client device 128 within the vehicle 140 may be determined based on a combination of the sub-audible tones and the sensor data from the sensor 130.

[0054] The verification engine 116 can determine the relative location of the client device 128 by determining the time difference between transmitting the sub-audio tone 204 and receiving the sub-audio tone 204 by the client device 128. For example, the host unit 202 can cause one of the speakers 132 to generate the sub-audio tone 204. The speaker 132 can generate the sub-audio tone 204 at the first time. The client device 128 that is relatively closer to the speaker 132 generating the sub-audio tone 204 will receive the sub-audio tone 204 before the client device 128 that is relatively farther from the speaker 132 generating the sub-audio tone 204. For example, if Figure 2 As shown, client device 128(1) will receive sub-audio tones 204 before client device 128(2).

[0055] Once the client device 128 receives or otherwise detects the sub-audio tone 204, the client device 128 may generate a receipt notification, which the client device 128 sends to the head unit 202 or the data processing system 102. The receipt notification may indicate a second time that the speaker 132 received the sub-audio tone 204. The receipt notification may be sent to the data processing system 102 via a cellular network, a WiFi network local to the vehicle 140, or via Bluetooth. The verification engine 116 may determine the length of time between the generation of the sub-audio tone 204 and the time when the client device 128 received the sub-audio tone 204 (e.g., the time difference between the first time and the second time in the above example). Different speakers 132 may generate different sub-audio tones 204 at different times so that the data processing system 102 can triangulate the location of the client device 128 within the vehicle 140.

[0056] The verification engine 116 can determine the location of the client device 128 based on data from the sensor 130. The sensor 130 can be a weight sensor that can determine whether the seat 200 is occupied. For example, when the sensor 130 records a weight greater than a predetermined threshold, the verification engine 116 can determine that the seat 200 is occupied. In some embodiments, the verification engine 116 can use the sub-audio tone 204 to determine that the client device 128 is near one of the seats 200. The verification engine 116 can confirm that the user is associated with the client device 128 based on the sensor data that the sensor 130 of the determined seat 200 is detecting weight. The sensor data can be used to prevent the user from accessing functions that are only available to certain zones or users. For example, text messaging can be disabled on the client device 128 associated with the driver, but enabled for the client devices 128 associated with the passengers in the other seats 200 of the vehicle 140. If the driver intends to lean over and move his client device 128 into the area of ​​the passenger seat 200, based on the sub-audio tone 204, the verification engine 116 can determine that the client device 128 is associated with the passenger seat 200 and the request to use the text messaging program should be allowed to be generated. The verification engine 116 can receive the 0 lb weight data from the sensor 130 in the passenger seat 200 and determine that the user is not actually in the passenger seat 200, and may block the driver's client device 128 from accessing the text messaging function. In some embodiments, the verification engine 116 can update the relative position of the client device 128 in the vehicle 140 only after detecting the door of the vehicle 140 is opened and closed.

[0057] Figure 3 An example method 300 for verifying vehicle functionality is shown. The method 300 may include receiving an audio signal (block 302). The method 300 may include parsing the audio signal (block 304). The method 300 may include generating an action data structure (block 306). The method 300 may include determining a vehicle state (block 308). The method 300 may include determining a request state (block 310). The method 300 may include sending an action data structure (block 312).

[0058] Method 300 may include receiving an input audio signal (box 302). A data processing system may receive the input audio signal. For example, an NLP component executed by the data processing system may receive the input audio signal. The data processing system (and the NLP component) may be a component of a client device, a vehicle or otherwise executed by a client device, a vehicle, or may be an independent device. A sensor such as a microphone on the client device or vehicle may detect the input audio signal, and then the corresponding client device or vehicle may send the input audio signal to the data processing system. For example, an application executed on a client device may detect that a user says "Ok, open the sunroof". The detected speech may be encoded as an input audio signal and then transmitted to the NLP component of the data processing system or vehicle.

[0059] The method 300 may include parsing the input audio signal (block 304). The NLP component may parse the input audio signal to identify a request in the input audio signal. The NLP component may identify a vehicle associated with the request. The NLP component may identify a fulfillment interface associated with the request and the vehicle. The fulfillment interface may be an interface of one of the client device or the vehicle that will execute the action data structure to fulfill the request of the input audio signal.

[0060] In the above example, the request may be to open the sunroof. In this example, the fulfillment interface may be an interface for a vehicle that includes a sunroof. In some embodiments, the vehicle may be explicitly specified in the input audio signal. For example, a user may specify a nickname for his vehicle (e.g., a user may name his red Toyota Camry "red car"). When explicitly stated, the input audio signal may be "OK, open the sunroof of my red car". In some embodiments, the data processing system may determine which vehicles associated with the user account may perform the action. For example, the user's red car may include a sunroof, while the user's blue car may not. Upon receiving the input audio signal "Ok, open the sunroof.", the data processing system may automatically select the user's red car. In some embodiments, the data processing system may require the user to confirm the vehicle.

[0061] Method 300 may include generating an action data structure (box 306). The direct action API may generate a data structure that can be transmitted and processed by a client device or vehicle to fulfill a request for an input audio signal. For example, continuing the above example, the direct action API may generate a first action data structure for opening the sunroof of a user's car. The direct action API may generate the action data structure using a template retrieved from a data repository of a data processing system. The action data structure may include fields for fulfilling the request. For example, for a request to open the sunroof, the action data structure may include a field (or attribute) for a vehicle ID to which the action data structure should be sent if the action data structure is granted.

[0062] Method 300 may include determining a vehicle state (block 308). The vehicle state may include a plurality of attributes. The attributes may identify the current state of the vehicle. The vehicle state may include a plurality of sub-states, such as a motion state, an external environment state, an internal environment state, and a device state. The motion sub-state may include attributes such as current and average speed, current and average acceleration, a driving mode state, and a gear state. The external environment sub-state may include attributes such as external weather conditions (e.g., raining, sunny, or snowing), external temperature, external weather condition forecast, and external temperature forecast. The internal environment sub-state may include attributes such as internal temperature and internal zone temperature. The device sub-state may include attributes such as HVAC state (e.g., air conditioning on, air conditioning off, heating, etc.), window state, lock state, trunk state, door ajar state, sunroof state, heated seat state, heated steering wheel state, and light state. The verification engine may determine the vehicle state using sensor data generated by the vehicle, the client device, or obtained from a data provider. In some embodiments, a verification engine executed at one location may determine the vehicle state and transmit the vehicle state to a second verification engine. For example, a verification engine executing at the vehicle may determine all or a portion of the vehicle state and then transmit the vehicle state to a verification engine executing at a remote data processing system.

[0063] Method 300 may include determining a request state (block 310). The request state may include a plurality of attributes. The attributes of the request state may indicate one or more conditions that should be fulfilled or satisfied before completing an action associated with an action data structure. The attributes (and request state) may be components of the action data structure or derived from the action data structure. For example, an action data structure for a request to open a sunroof may include a field indicating under which external environmental conditions the sunroof should be opened. The verification engine may incorporate the external environmental conditions into the attributes of the request state. The request state may include user attributes. The user attributes may include a location or authorization status of a client device associated with a user. The location may be a location within a vehicle or a geographic location (e.g., the client device is located in the user's office).

[0064] The verification engine may use sub-audio tones to determine the user's location in the vehicle. For example, the verification engine may cause one or more speakers within the vehicle to produce sub-audio tones. The verification engine may determine the relative location of the client device in the vehicle by determining the delay between when the sub-audio tone is played at the speaker and when the client device detects the sub-audio tone. The relative location of the user (and client device) in the vehicle may be determined based on weight or occupancy sensor readings placed in a vehicle seat.

[0065] Method 300 may send an action data structure (block 312). The action data structure may be sent to a fulfillment interface configured to perform a function associated with the action data structure. In some embodiments, the action data structure is sent to the fulfillment interface only when one or more attributes of the request state match one or more attributes of the vehicle state. For example, the confirmation engine may compare the attributes of the request state indicating the requirement to perform the function with the attributes of the vehicle state. For example, a request to open the sunroof may have an external environment attribute requirement {external environment: [sunny, cloudy, cloudy]}. Among other attributes, the vehicle state may include {external environment: raining}. In this example, the verification engine may determine that the request state attribute is not an element of the vehicle state attribute, and the sunroof should not be opened because it is raining at the vehicle location. When the verification engine determines that there is a mismatch between the request state attribute and the vehicle state attribute, the verification engine may modify the action data structure. For example, in response to determining that the sunroof should not be opened due to rain, the verification engine may modify the action data structure to turn on the HVAC of the vehicle. The verification engine may generate a prompt asking the user whether he or she wishes to modify the action data structure. For example, the data processing system may generate a prompt "I did not open the sunroof because it is raining. Would you like me to turn on the AC instead?"

[0066] The verification engine may determine that there is a mismatch between the request state attribute and the vehicle state attribute. The data processing system may generate a notification notifying the user that the request has not been completed. The notification may include a reason why the request was not completed. In some embodiments, if the verification engine does not find a match, the verification engine discards the action data structure and does not transmit the action data structure to the fulfillment interface.

[0067] For example, when the verification engine determines that there is a match between the request state attribute and the vehicle state attribute, the verification engine can transmit the action data structure to the fulfillment interface to perform the function associated with the action data structure. For example, to open the sunroof, the action data structure can be sent to the head unit of the vehicle, which can execute the application to control the motor, which controls the position of the sunroof. In some embodiments, the data processing system can send a confirmation that the function has been completed. For example, a text-based or audio-based output signal can be sent to the client device to indicate that the sunroof is opened.

[0068] Figure 4 4 is a block diagram of an example computer system 400. The computer system or computing device 400 may include or be used to implement the system 100 or its components, such as the data processing system 102. The computing system 400 includes a bus 405 or other communication component for transmitting information and a processor 410 or processing circuit coupled to the bus 405 to process information. The computing system 400 may also include one or more processors 410 or processing circuits coupled to the bus to process information. The computing system 400 also includes a main memory 415, such as a random access memory (RAM) or other dynamic storage device, which is coupled to the bus 405 to store information, and instructions to be executed by the processor 410. The main memory 415 may be or include the data repository 118. The main memory 415 may also be used to store location information, temporary variables, or other intermediate information during the execution of instructions by the processor 410. The computing system 400 may further include a read-only memory (ROM) 420 or other static storage device, which is coupled to the bus 405 to store static information and instructions for the processor 410. A storage device 425, such as a solid-state device, magnetic disk, or optical disk, may be coupled to bus 405 for persistent storage of information and instructions. Storage device 425 may include or be a part of data repository 118.

[0069] The computing system 400 may be coupled to a display 435 such as a liquid crystal display or an active matrix display via the bus 405 for displaying information to a user. An input device 430 such as a keyboard including alphanumeric and other keys may be coupled to the bus 405 for communicating information and command selections to the processor 410. The input device 430 may include a touch screen display 435. The input device 430 may also include a cursor control such as a mouse, trackball, or cursor direction keys for communicating direction information and command selections to the processor 410 and for controlling cursor movement on the display 435. For example, the display 435 may be a Figure 1 Part of data processing system 102, client computing device 128, or other component.

[0070] The processes, systems, and methods described herein can be implemented by the computing system 400 in response to the processor 410 executing an arrangement of instructions contained in the main memory 415. Such instructions can be read into the main memory 415 from another computer-readable medium such as the storage device 425. The arrangement of executing the instructions contained in the main memory 415 causes the computing system 400 to perform the exemplary processes described herein. One or more processors in a multi-processing arrangement can also be used to execute the instructions contained in the main memory 415. Hard-wired circuits can be used in place of software instructions or in combination with software instructions in conjunction with the systems and methods described herein. The systems and methods described herein are not limited to any specific combination of hardware circuitry and software.

[0071] although Figure 4 An example computing system has been described in the specification, but the subject matter including the operations described in this specification may be implemented in other types of digital electronic circuitry, or in computer software, firmware, or hardware including the structures disclosed in this specification and their structural equivalents, or in a combination of one or more of them.

[0072] For the situation that the system discussed in this article collects personal information about the user or can utilize personal information, the user can be provided with the opportunity to control whether the program or feature can collect personal information (e.g., information about the user's social network, social actions or activities, the user's preferences or the user's location) or control whether or how to receive content that may be more relevant to the user from a content server or other data processing system. In addition, some data can be anonymized in one or more ways before storage or use, so as to remove personally identifiable information when generating parameters. For example, the identity of the user can be anonymized so that the user's personally identifiable information cannot be determined, or the geographic location of the user who obtains the location information can be summarized (e.g., to the city, zip code or state level) so that the specific location of the user cannot be determined. Therefore, the user can control how the content server collects and uses information about him or her.

[0073] The subject matter and operations described in this specification may be implemented in digital electronic circuits, or in computer software, firmware or hardware including the structures disclosed in this specification and their structural equivalents or a combination of one or more thereof. The subject matter described in this specification may be implemented as one or more computer programs, such as one or more circuits of computer program instructions encoded on one or more computer storage media, for execution by a data processing device or for controlling the operation of a data processing device. Alternatively or additionally, program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical or electromagnetic signals, which are generated to encode information for transmission to a suitable receiver device for execution by a data processing device. A computer storage medium may be or may be included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or one or more combinations thereof. Although a computer storage medium is not a propagation signal, a computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagation signal. A computer storage medium may also be or may be included in one or more separate components or media (e.g., multiple CDs, disks or other storage devices). The operations described in this specification may be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.

[0074] The terms "data processing system," "computing device," "component," or "data processing apparatus" encompass various apparatuses, devices, and machines for processing data, including, for example, a programmable processor, a computer, a system on a chip, or multiple systems on a chip, or a combination of the foregoing. The apparatus may include dedicated logic circuits, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment may implement a variety of different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures. The components of system 100 may include or share one or more data processing apparatuses, systems, computing devices, or processors.

[0075] A computer program (also referred to as a program, software, software application, application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for a computing environment. A computer program may correspond to a file in a file system. A computer program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program, or in multiple coordinated files (e.g., files that store one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one computer or on multiple computers located at one site or distributed over multiple sites and interconnected by a communications network.

[0076] The processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs (e.g., components of data processing system 102) to perform actions by operating on input data and generating output. The processes and logic flows may also be performed by, and the apparatus may also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). Suitable devices for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated into, special purpose logic circuitry.

[0077] The subject matter described herein can be implemented in a computing system that includes a back-end component (e.g., as a data server) or includes a middleware component (e.g., an application server) or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification), or a combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), inter-networks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0078] A computing system such as system 100 or system 400 may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network (e.g., network 142). The relationship of the client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. In some embodiments, the server sends data (e.g., data packets representing content items) to a client device (e.g., in order to display data to a user interacting with the client device or to receive user input from it). Data generated at the client device (e.g., a result of a user interaction) may be received from the client device at the server (e.g., received by the data processing system 102 from the client computing device 128 or the vehicle 140).

[0079] Although operations are depicted in the drawings in a particular order, they need not be performed in the particular order shown or in sequential order, and not all operations shown need be performed. The actions described herein may be performed in a different order.

[0080] The separation of various system components need not require separation in all embodiments, and the described program components may be included in a single hardware or software product. For example, the NLP component 106 and the verification engine 116 may be a single component, application or program, or a logical device having one or more processing circuits, or part of one or more servers of the data processing system 102.

[0081] Now that some exemplary embodiments have been described, it is apparent that the foregoing is exemplary and not restrictive, having been presented by way of example. In particular, although many of the examples presented herein relate to specific combinations of method actions or system elements, these actions and those elements may be combined in other ways to achieve the same goals. The actions, elements, and features discussed in conjunction with one embodiment are not intended to be excluded from similar roles in other embodiments.

[0082] The words and terms used herein are for descriptive purposes and should not be considered limiting. The use of "including," "comprising," "having," "containing," "involving," "characterized by," "characterized by," and variations thereof are meant to encompass the items listed thereafter, their equivalents and additional items, and alternative embodiments consisting of the items listed thereafter. In one embodiment, the systems and methods described herein include one, more than one of each combination, or all of the described elements, actions, or components.

[0083] Any reference to the embodiments, elements or actions of the systems and methods herein mentioned in the singular may also encompass embodiments including a plurality of these elements, and any reference to any embodiments, elements or actions herein in the plural may also encompass embodiments including only one element. Reference in the singular or plural form is not intended to limit the currently disclosed systems or methods, their components, actions or elements to a single or multiple configurations. Reference to any action or element based on any information, action or element may include an embodiment where the action or element is based at least in part on any information, action or element.

[0084] Any embodiment disclosed herein may be combined with any other embodiment or example, and references to "an embodiment," "some embodiments," "an embodiment," etc. are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment or example. These terms as used herein do not necessarily all refer to the same embodiment. Any embodiment may include or be exclusively combined with any other embodiment in any manner consistent with the aspects and embodiments disclosed herein.

[0085] References to "or" may be interpreted as inclusive, such that any term described using "or" may indicate a single, more than one, and any of the described terms. References to at least one of "A" and "B" may include only "A," only "B," and both "A" and "B." Such references used in conjunction with "includes" or other open terms may include additional items.

[0086] Where technical features in the drawings, detailed description or any claims are followed by reference numerals, the reference numerals have been included to increase the intelligibility of the drawings, detailed description and claims. Therefore, neither the reference numerals nor their absence will have any limiting effect on the scope of any claim element.

[0087] The systems and methods described herein may be implemented in other specific forms without departing from their characteristics. The foregoing embodiments are exemplary rather than limiting of the described systems and methods. Therefore, the scope of the systems and methods described herein is indicated by the appended claims rather than the preceding description, and changes within the meaning and range of equivalents of the claims are hereby encompassed.

Claims

1. A method implemented by one or more processors, comprising: identifying a request to perform a vehicle function based on processing the received user input; generating, based on the request to perform the vehicle function, an action data structure, the action data structure including an action associated with the request to perform the vehicle function; determining a vehicle state of the vehicle associated with the request to perform the vehicle function based on: first sensor data associated with the vehicle, wherein the vehicle state includes a plurality of first attributes; determining a request status associated with the request to perform the vehicle function based on second sensor data associated with the vehicle, wherein the request status includes a plurality of second attributes; comparing the plurality of second attributes of the request state to the plurality of first attributes of the vehicle state; and In response to determining that one or more of the second plurality of attributes of the request state does not match one or more of the first plurality of attributes of the vehicle state: modifying the action data structure to generate a substitute action data structure, the substitute action data structure including a substitute action identified based on the request to perform the vehicle function; and The alternative actions included in the alternative action data structure are caused to be provided for presentation to the user providing the user input via a user's client device or a head unit of the vehicle.

2. The method according to claim 1, wherein: The plurality of first attributes of the vehicle state include at least external environment attributes, and wherein the plurality of second attributes of the request state include at least external environment requirements.

3. The method according to claim 2, wherein: Determining that one or more of the plurality of second attributes of the request state do not match one or more of the plurality of first attributes of the vehicle state includes determining that the external environment attributes of the plurality of first attributes of the vehicle state do not satisfy the external environment requirements of the plurality of second attributes of the request state.

4. The method according to claim 3, wherein: The action associated with the request to perform the vehicle function includes an open a window action, and wherein the alternative action identified based on the request to perform the vehicle function is a turn on air conditioning action.

5. The method according to claim 1, wherein: Causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user comprises: A prompt is generated to solicit whether the user wants to perform the alternative action included in the alternative action data structure instead of the action included in the action data structure.

6. The method according to claim 5, further comprising: After causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user: identifying, based on processing further received user input, a user confirmation to perform said alternative action included in said alternative action data structure; as well as In response to identifying the user confirmation to perform the alternative action: The alternative action included in the alternative action data structure is caused to be performed by the vehicle.

7. The method according to claim 5, further comprising: After causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user: identifying, based on processing the received further user input, a further request to overturn the modified action data structure; and In response to identifying the further request to override the alternative action: The action included in the action data structure is caused to be performed by the vehicle.

8. A method implemented by one or more processors, comprising: identifying a request to perform a vehicle function based on processing the received user input; generating, based on the request to perform the vehicle function, an action data structure, the action data structure including an action associated with the request to perform the vehicle function; determining a vehicle state of the vehicle associated with the request to perform the vehicle function based on: first sensor data associated with the vehicle, wherein the vehicle state includes a plurality of first attributes; determining a request status associated with the request to perform the vehicle function based on second sensor data associated with the vehicle, wherein the request status includes a plurality of second attributes; comparing the plurality of second attributes of the request state to the plurality of first attributes of the vehicle state; and In response to determining that one or more of the second plurality of attributes of the request state does not match one or more of the first plurality of attributes of the vehicle state: discarding the action data structure; generating a notification indicating that the action included in the action data structure was not performed; and causing the notification to be provided for presentation to the user who provided the user input via a client device of the user or a head unit of the vehicle, Wherein, the multiple second attributes of the request state include at least a driving mode condition requirement, and wherein determining that one or more of the multiple second attributes of the request state do not match one or more of the multiple first attributes of the vehicle state includes determining that the driving mode of the vehicle does not match the driving mode condition requirement for changing the device state of one or more devices of the vehicle.

9. The method according to claim 8, wherein: The action associated with the request to perform the vehicle function includes changing a device state of one or more devices of the vehicle.

10. The method according to claim 9, wherein: The plurality of first attributes of the vehicle status include at least the device status of one or more of the devices of the vehicle, and wherein the plurality of second attributes of the request status include at least an authorization level requirement.

11. The method according to claim 10, wherein: Determining that one or more of the plurality of second attributes of the request state do not match one or more of the plurality of first attributes of the vehicle state includes determining that an authorization level of the user providing the request does not match an authorization level requirement for changing the device state of one or more of the devices of the vehicle.

12. A system, comprising: at least one processor; as well as at least one memory storing instructions that, when executed, cause the at least one processor to: identifying a request to perform a vehicle function based on processing the received user input; generating, based on the request to perform the vehicle function, an action data structure, the action data structure including an action associated with the request to perform the vehicle function; determining a vehicle state of the vehicle associated with the request to perform the vehicle function based on: first sensor data associated with the vehicle, wherein the vehicle state includes a plurality of first attributes; determining a request status associated with the request to perform the vehicle function based on second sensor data associated with the vehicle, wherein the request status includes a plurality of second attributes; comparing the plurality of second attributes of the request state to the plurality of first attributes of the vehicle state; and In response to determining that one or more of the second plurality of attributes of the request state does not match one or more of the first plurality of attributes of the vehicle state: modifying the action data structure to generate a substitute action data structure, the substitute action data structure including a substitute action identified based on the request to perform the vehicle function; and The alternative actions included in the alternative action data structure are caused to be provided for presentation to the user providing the user input via a user's client device or a head unit of the vehicle.

13. The system according to claim 12, wherein: The plurality of first attributes of the vehicle state include at least external environment attributes, and wherein the plurality of second attributes of the request state include at least external environment requirements.

14. The system according to claim 13, wherein: The instructions for determining that one or more of the multiple second attributes of the request state do not match one or more of the multiple first attributes of the vehicle state include instructions for determining that the external environment attributes among the multiple first attributes of the vehicle state do not meet the external environment requirements among the multiple second attributes of the request state.

15. The system of claim 14, wherein: The action associated with the request to perform the vehicle function includes an open a window action, and wherein the alternative action identified based on the request to perform the vehicle function is a turn on air conditioning action.

16. The system of claim 12, wherein: The instructions for causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user include instructions for: A prompt is generated to solicit whether the user wants to perform the alternative action included in the alternative action data structure instead of the action included in the action data structure.

17. The system of claim 16, wherein: The instructions further cause the at least one processor to: After causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user: identifying, based on processing further received user input, a user confirmation to perform said alternative action included in said alternative action data structure; as well as In response to identifying the user confirmation to perform the alternative action: The alternative action included in the alternative action data structure is caused to be performed by the vehicle.

18. The system of claim 16, wherein: The instructions further cause the at least one processor to: After causing the alternative actions included in the alternative actions data structure to be provided for presentation to the user: identifying, based on processing the received further user input, a further request to overturn the modified action data structure; and In response to identifying the further request to override the alternative action: The action included in the action data structure is caused to be performed by the vehicle.

Citation Information

Patent Citations

  • Vehicular voice operation apparatus

    JP2017087950A

  • Control for an Electronic Multi-Function Apparatus

    US20180022359A1