Vehicle-User Interaction System and Interaction Method

Abstract

The present invention provides a vehicle-user interaction system and method. The system includes: an editor configured to receive user input and edit a rule script based on the user input, the rule script including rules having trigger conditions defined by the user and vehicle operations when the trigger conditions are satisfied; a parser configured to obtain the rule script and create a monitoring element list and a function element list based on the rule script, the monitoring element list including sensor elements that directly or indirectly represent the trigger conditions for monitoring, and the function element list including function elements corresponding to the vehicle operations for execution; and an actuator configured to monitor sensor detection information corresponding to the sensor elements and, when sensor detection information indicating that the trigger conditions are satisfied is monitored, execute the corresponding function elements to implement the rules defined by the user.

Description

Technical Field

[0001] The present invention relates to a vehicle-user interaction system and a vehicle-user interaction method. The present invention also relates to a corresponding machine-readable storage medium. Background Art

[0002] In the field of automotive technology, in addition to the two major aspects of safety and comfort that have been studied extensively, more and more attention is being paid to the user experience. To improve the user experience, the current main research involves human-machine interaction technology. Existing human-machine interaction technology can achieve basic interaction functions between people and vehicles. For example, vehicle users can obtain vehicle status information and road condition information through an in-vehicle human-machine interaction system and set functions such as cruise control, hands-free phone, air conditioning, and audio. On this basis, it is expected that the vehicle can provide customized services and functions for users. Summary of the Invention

[0003] In view of this, the present invention aims to provide a solution for vehicle-user interaction that can provide user-defined services on a vehicle.

[0004] According to one aspect of the present invention, there is provided a vehicle-user interaction system, comprising: an editor configured to receive user input and edit a rule script based on the user input, the rule script including rules having trigger conditions defined by the user and vehicle operations when the trigger conditions are met; a parser configured to obtain the rule script and create a monitoring element list and a function element list based on the rule script, the monitoring element list including sensor elements for monitoring that directly and / or indirectly represent the trigger conditions, and the function element list including function elements for execution corresponding to the vehicle operations; and an actuator configured to monitor sensor detection information corresponding to the sensor elements and, when sensor detection information indicating that the trigger conditions are met is monitored, execute the corresponding function elements to implement the user-defined rules.

[0005] According to another aspect of the present invention, there is provided a vehicle-user interaction method. Optionally, this method is executed by the system as described above. The method includes: receiving a user input at an electronic device and / or the vehicle's infotainment system, and editing a rule script based on the user input, which includes rules having trigger conditions defined by the user and vehicle operations when the trigger conditions are met; obtaining the rule script at the infotainment system, and creating a monitoring element list and a function element list based on the rule script, where the monitoring element list includes sensor elements that directly or indirectly represent the trigger conditions for monitoring, and the function element list includes function elements corresponding to the vehicle operations for execution; and monitoring, at the infotainment system, sensor detection information corresponding to the sensor elements, and when sensor detection information indicating that the trigger conditions are met is monitored, executing the corresponding function elements to implement the rules defined by the user.

[0006] According to yet another aspect of the present invention, there is provided a machine-readable storage medium storing executable instructions that, when executed, cause a processor to execute the method as described above.

[0007] The above gives a brief summary of the main aspects of the present invention for a basic understanding of these aspects. This summary is not intended to describe the key or important elements of all aspects, nor to limit the scope of any or all aspects. This summary presents some implementations of these aspects in a simplified form as a prelude to the detailed description to be given later. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The technical solutions of the present invention will become clearer from the following detailed description in conjunction with the accompanying drawings. It can be understood that these drawings are only for illustrative purposes and are not intended to limit the protection scope of the present invention.

[0009] Figure 1 is a schematic diagram of a vehicle-user interaction system according to an embodiment of the present invention.

[0010] Figures 2A - 2C are respectively schematic block diagrams of implementations of an editor, a parser, and an executor of the vehicle-user interaction system.

[0011] Figure 3 is a flowchart of an editing process of a rule script according to an embodiment of the present invention.

[0012] Figure 4 is a flowchart of a parsing and execution process of a rule script according to an embodiment of the present invention.

[0013] Figures 5A - 5D is a schematic diagram of implementations of some sub-interfaces of an editing interface.

[0014] Figure 6 It is a flowchart of a vehicle-user interaction method according to an embodiment of the present invention. Detailed implementation manners

[0015] Embodiments of the present invention mainly relate to a solution for vehicle-user interaction, which is based on an in-vehicle infotainment system of the Android operating system. According to the vehicle-user interaction system and interaction method of the embodiments of the present invention, a user can design custom rules on a mobile phone, a web page, and / or an in-vehicle unit, and then synchronize the rules to the in-vehicle unit of AAOS (Android Automotive Operation System) and execute the rules on the vehicle. In this way, the vehicle can provide the user with customized functions and services.

[0016] According to the technical solution of the embodiments of the present invention, on the one hand, a visual programming platform is provided for the user to set custom rules, and on the other hand, the content and scope of the user's custom rules are restricted. Specifically, the settings that the user can input into the visual programming platform are restricted based on considering vehicle safety factors. In this way, while ensuring vehicle safety, the vehicle can provide user-customized services, and to a certain extent, an advanced technology of defining an automobile from the perspective of user experience is realized.

[0017] Next, the specific implementation manners of the present invention will be described with reference to the accompanying drawings.

[0018] Figure 1 FIG. schematically shows a vehicle-user interaction system 100 according to an embodiment of the present invention, which mainly includes an editor 10, a memory 20, a parser 30, and an executor 40.

[0019] The editor 10 can be set in an electronic device and / or in the in-vehicle infotainment system of the vehicle. The electronic device can use the Android operating system or the IOS operating system (see Figure 1 10A, 10B, 10C in). The editor 10 can be implemented as one or more editors, which are respectively set in one or more of an Android mobile phone, an Apple mobile phone, a laptop computer, and a desktop computer. For example, the editor 10 is implemented as software (APP) in a mobile phone, a laptop computer, or a desktop computer. In this way, the user can design custom rules at one or more of a mobile phone, a web page, and an in-vehicle unit.

[0020] It should be noted that the electronic device refers to an electronic device that is not a component of the vehicle. The physical location of the electronic device is not limited. The electronic device can be located inside the vehicle (for example, the user carries a smart phone in the vehicle), or can be located outside the vehicle (for example, the user carries a smart phone outside the vehicle).

[0021] Editor 10 is configured to receive user input and edit the user input into a rule script, which includes rules defined by the user. The rules include a trigger condition set by the user and a vehicle operation in the case where the trigger condition is satisfied. The trigger condition may include the external environment or the vehicle state. The vehicle operation may include operations and functions that can be implemented inside the vehicle. For example, a rule defined by the user may be "if the external environment temperature is higher than 26 degrees Celsius, then close the windows and turn on the air conditioner".

[0022] It should be noted that regarding the user-designed rules, on the one hand, it satisfies user customization, and on the other hand, it is also restricted, that is, the user is not allowed to design rules arbitrarily, which is for the consideration of vehicle safety. This will be specifically introduced below.

[0023] The memory 20 is provided in the vehicle's infotainment system for storing the edited rule script. The rule script edited in the editor 10 can be transmitted to the memory 20 by means of wired and / or wireless communication. In one embodiment, the rule script is transmitted to the memory 20 by near-field communication. In another embodiment, the rule script is first uploaded to the cloud server and then transmitted from the cloud server to the memory 20.

[0024] The parser 30 is also provided in the vehicle's infotainment system. The parser 30 is configured to obtain the rule script from the memory 20 and create a monitoring element list and a function element list based on the obtained rule script. The monitoring element list includes sensor elements that directly and / or indirectly represent the trigger condition for monitoring. The function element list includes function elements corresponding to the vehicle operation for execution.

[0025] The actuator 40 is also provided in the vehicle's infotainment system. The actuator 40 is configured to monitor the sensor detection information corresponding to the sensor element (for example, if the trigger condition includes a setting regarding the environmental temperature, the corresponding sensor detection information includes environmental temperature detection information and / or sensor detection information that can calculate the environmental temperature). The actuator 40 is also configured to execute the corresponding function element to implement the rule defined by the user when it is determined based on the sensor detection information that the monitored trigger condition set by the user is satisfied.

[0026] In one embodiment, the editor 10, the parser 30, and the actuator 40 may be respectively implemented as a software, or may be combined together to form a software. In this embodiment, the editor 10, the parser 30, and the actuator 40 may all be provided in the vehicle, or may all be provided in the above-mentioned electronic device.

[0027] In one embodiment, the editor 10 is provided in the information entertainment system of an electronic device and / or a vehicle, the parser 30 is provided in the information entertainment system of the vehicle, and the actuator 40 is provided in the information entertainment system of the vehicle.

[0028] In one embodiment, the information entertainment system of the vehicle adopts the Android automotive operating system, that is, Android Automotive Operation System (AAOS).

[0029] Figures 2A - 2C Feasible implementation manners of the editor 10, the parser 30, and the actuator 40 of the vehicle-user interaction system 100 are schematically shown respectively.

[0030] See Figure 2A , the editor 10 can be implemented to include a database 11, an editing interface 12, and an editing module 13.

[0031] The database 11 is used to store interface elements. The interface elements can include interface elements that will be presented and can receive user input, and can also include interface elements such as borders, colors, numerical values, etc.

[0032] The editing interface 12 can include a first sub-interface 121, a second sub-interface 122, a third sub-interface 123, and a fourth sub-interface 124. Each sub-interface will be specifically introduced below.

[0033] The editing interface 12 can include one or more of touch-sensitive interface elements, non-touch-sensitive interface elements, and voice-controlled interface elements.

[0034] In the embodiment of the touch-sensitive interface element, the touch-sensitive interface element can understand finger contact, finger tap gesture, finger swipe gesture, stylus movement, or a combination thereof, etc.

[0035] In the embodiment of the non-touch-sensitive interface element, the non-touch-sensitive interface element (for example, an icon or a button) receives an input signal from another input device (for example, a mouse or a keyboard). For example, at an icon on the editing interface 12, a mouse click is received to select the icon.

[0036] In the embodiment of the voice-controlled interface element, the user can read out the interface elements presented on the interface he / she sees, so that the interface elements that can be seen by the vehicle occupants can be controlled by voice.

[0037] The editing module 13 edits the user input into a rule script according to a predetermined algorithm and format. The rule script in the predetermined format is used for storage and transmission.

[0038] SeeFigure 2B , the parser 30 can be implemented to include an acquisition module 31, a parsing module 32, and a management module 33. The acquisition module 31 is used to acquire a rule script from the memory 20. The parsing module 32 is used to convert the acquired rule script into an expression that can run on the AAOS and inject the expression into the management module 33. The management module 33 is used to create a list of monitoring elements and a list of function elements according to the expression.

[0039] See Figure 2C , the actuator 40 can be implemented to include a monitoring module 41 and a triggering module 42. The monitoring elements included in the list of monitoring elements created in the management module 32 are registered in the monitoring module 41 so that the monitoring module 41 monitors the corresponding sensor detection information. When the monitoring module 41 determines that the triggering condition is satisfied based on the sensor detection information, it triggers the management module 33 to make a response. Then, the triggering module 42 calls the corresponding vehicle function, thereby executing the user-defined rule.

[0040] It can be understood that the editor 10, the parser 30, and the actuator 40 and their components can be implemented in a way that combines hardware, software, or software and hardware. For the part implemented by hardware, it can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic units designed to execute their functions, or a combination thereof. For the part implemented by software, it can be realized by means of microcode, program code, or code segments, and they can also be stored in a machine-readable storage medium such as a storage component.

[0041] It can be understood that the naming of the editor 10, the parser 30, and the actuator 40 and their components should be understood as a logical (functional) description and should not be understood as a limitation on the physical form or setting method.

[0042] Figure 3 Shows an editing process 300 of a script rule according to an embodiment of the present invention. The editing process 300 can be implemented by the editor 10.

[0043] Before executing the editing process 300, an initialization process (not shown) can be executed. For example, in the initialization process, an APP for editing a rule script is started.

[0044] After the initialization process, it enters box 302. In box 302, a first sub-interface 121 is presented. See Figure 5A, the first sub-interface 121 includes a status element window 121, which contains one or more status elements. These status elements can be implemented by means of the visual programming components encapsulated by AAOS. The status element window 1211 can contain multiple status elements. Each status element can receive user input. For example, the user clicks on a status element to select it.

[0045] Each status element represents a type of status. In one embodiment, the status element can include one or more of the following: time, location, alarm clock, email, ambient temperature, cabin temperature, calendar, phone call, instant messaging message notification, IoT (smart home, wearable device, road facilities, etc.), vehicle information (gear, speed, acceleration / deceleration, fuel consumption, remaining mileage, rain sensor, brightness sensor, seat pressure sensor, warning information, etc.).

[0046] In block 304, a first user input is received through the first sub-interface 121 so that the user can select a status element. For example, the user can touch a status element on the first sub-interface to select it; or, the user can read a status element on the first sub-interface to select it.

[0047] In block 306, in response to the user selecting a status element, a second sub-interface 122 is presented. See Figure 5B , the second sub-interface 122 includes a condition setting window 1221. The condition setting window 1221 can include interface elements for the user to set trigger conditions. For example, the interface element J for setting the judgment condition and the interface element T for setting the threshold. The judgment condition can include: greater than, equal to, less than, greater than or equal to, less than or equal to, contains, and does not contain. The symbols of these judgment conditions can be presented in the drop-down menu of the interface element, and the user sets the judgment condition by selecting a judgment condition symbol from the drop-down menu. The threshold can be a numerical value corresponding to the selected status. For example, the threshold for the temperature status can be a numerical value in the range of 10 - 30 °C.

[0048] In block 308, a second user input is received so that the user can set the trigger condition. The user can respectively output custom settings at the judgment condition interface element J and the threshold setting interface element T to complete the setting of the departure condition. For example, for the temperature status, enter "≥" at the judgment condition interface element J and enter "26 °C" at the threshold interface element T.

[0049] In addition, the second sub-interface 122 can also include an "OK" button. After the "OK" button receives the user input, it indicates that the user has completed the setting of the departure condition to trigger subsequent operations.

[0050] In block 310, in response to receiving user input at the "OK" button, the third sub-interface 123 is presented. Refer to Figure 5C , the third sub-interface 123 includes an operation element window 1231. The operation element window 1231 contains one or more operation elements. These operation elements can be implemented by means of the visualization programming components encapsulated by AAOS. Each operation element can receive user input. For example, a user clicks on an operation element to select it.

[0051] Each operation element represents a type of vehicle operation / function. In one embodiment, the operation element can include one or more of the following: in-vehicle / out-of-vehicle lighting, air conditioning, door locks, window locks, window control, rearview mirrors, seat positions, center console screen themes, instrument themes, navigation, IoT control, multimedia, vehicle function control (e.g., automatic start / stop, automatic parking, lane centering, etc.).

[0052] In block 312, a third user input is received through the third sub-interface 123 for the user to select an operation element. For example, the user can touch an operation element on the third sub-interface to select it; or, the user can read out an operation element on the third sub-interface to select it.

[0053] In block 314, in response to the user selecting a function element, the fourth sub-interface 124 is presented. Refer to Figure 5D , the fourth sub-interface 124 includes an operation setting window 1241. Refer to Figure 5D , the operation setting window 1241 can include interface elements A-C for the user to set vehicle operations.

[0054] In block 316, a fourth user input is received through the fourth sub-interface for the user to set vehicle operations. The user can respectively input custom settings at the vehicle operation interface elements A-C. For example, for the trigger condition "if the ambient temperature is greater than 26°C", "close the window", "air conditioning temperature", and "22°C" can be respectively input at the vehicle operation interface elements A-C.

[0055] In addition, a "OK" button can also be included on the fourth sub-interface. After the "OK" button receives user input, it indicates that the user has completed the vehicle operation settings and triggers subsequent operations.

[0056] It can be understood that the user interacts with the interface elements on the first sub-interface and is navigated to the second sub-interface, then interacts with the interface elements on the second sub-interface and is navigated to the third sub-interface, then interacts with the interface elements on the third sub-interface and is navigated to the fourth sub-interface.

[0057] It is understandable that the interface elements presented on each sub-interface and their presentation methods can be personalized arranged and can be flexibly adjusted. For example, they can be hidden, added, deleted, or have their positions, colors, or sizes changed.

[0058] In block 318, the editing module 13 edits the user input into a rule script.

[0059] In one embodiment, the editing module uses an algorithm designed based on the principle of regular expressions to transform the custom rules input by the user on the interface into a rule script.

[0060] This algorithm can include the following three basic parts: Expression, MetaCharacter, and Normal Character, where:

[0061] An expression is composed of meta characters, custom characters, and expressions. Expressions support nesting and recursion.

[0062] Meta characters include operators and factors.

[0063] Operators include: IF, ELSE, AND, OR, NOT. Factors include: Visual programming components encapsulated based on AAOS. Each component can include: Status, Action, and Preset.

[0064] Custom characters are characters input by the user or other defined expression names.

[0065] In this embodiment, the editing module 13 edits the script rule into a format that conforms to a predetermined format. For example, it converts the script rule into text information of a predetermined format. This text information of the predetermined format is used for the transmission and storage of the rule.

[0066] The rule script of this predetermined format includes three parts, namely, a first part and a second part that are aligned in length and a third part with a variable length. The lengths of the first part and the second part are both 32 bits. The length of the third part "data" is variable, and its length information can be recorded in the "packet length". The value range of the length of the "data" part is 0 - 65535 (65535 = 2^16 – 1).

[0067] The first part sequentially includes an 8-bit header, an 8-bit editor version, an 8-bit AAOS version, and an 8-bit identification part.

[0068] The second part sequentially includes a 16-bit data packet and a 16-bit reserved part.

[0069] The third part includes a data part with variable length.

[0070] For clarity, the definitions of the above-mentioned predetermined format (format definition) are exemplarily shown in the following table. The meanings of (4), (8), (12), and (16) in the following table are the number of bits occupied by the field in the computer.

[0071] Expression text format definition

[0072]

[0073] "Data" part format definition

[0074]

[0075] Expression start symbol

[0076] 0x0 Data Length (12) Reserved Bit (16)

[0077] Expression end symbol

[0078] 0xF Data Length (12) Reserved Bit (16)

[0079] Operator

[0080] 0x1 Data Length (12) Operator Type (16)

[0081] Enumeration definition of "operator type":

[0082] Expression name

[0083]

[0084] Preprocessing

[0085]

[0086] Condition definition

[0087]

[0088] Enumeration definition of "judgment condition":

[0089]

[0090] Action definition

[0091]

[0092] Figure 4Shows the parsing and execution process 400 of a rule script according to an embodiment of the present invention. This process 400 can be implemented by a parser 30 and an executor 40.

[0093] After the editing process 300 is executed, a rule script in a predetermined format can be stored in the memory 20, and the parser 30 is notified of a script update to trigger the process 400.

[0094] See Figure 4 , in block 402, the acquisition module 31 acquires a rule script in a predetermined format from the memory 20.

[0095] In block 404, the parsing module 32 translates the rule script into an expression that can run on the AAOS.

[0096] In block 406, the management module 33 creates a list of monitoring elements and a list of function elements based on the expression. The list of monitoring elements contains sensor elements that directly or indirectly express user-defined trigger conditions for monitoring. The list of function elements contains function elements corresponding to user-defined vehicle operations for execution.

[0097] In block 408, the management module 33 injects the monitoring elements into the monitoring module 41.

[0098] In block 410, the monitoring module 41 monitors the sensor detection information.

[0099] In block 412, the monitoring module 41 determines whether the user-defined trigger condition is satisfied based on the sensor detection information.

[0100] When it is determined that the user-defined trigger condition is not satisfied, return to block 410 to continue monitoring the sensor detection information.

[0101] When it is determined that the user-defined trigger condition is satisfied, enter block 414. In block 414, the management module 33 makes a trigger response.

[0102] In block 416, the trigger module 42 calls the system function in response to the trigger response of the management module, thereby executing the user-defined rule.

[0103] For clarity, take "monitoring temperature and performing window closing and air conditioner turning on" as an example to illustrate the process of blocks 412 - 416. In this embodiment, the monitoring module 41 determines whether the ambient temperature meets the user-defined "if the ambient temperature is greater than or equal to 26 degrees Celsius" based on the ambient temperature detected by the sensor. When it is determined that the ambient temperature is lower than 26 degrees Celsius, the ambient temperature is continuously monitored. When it is determined that the ambient temperature is greater than 26 degrees Celsius, the management module 33 triggers a response. Then, the triggering module 42, in response to the triggering response of the management module, calls the system functions of "closing the vehicle window and turning on the air conditioner", thereby implementing the user-defined rule.

[0104] Figure 6 Fig. 600 shows a vehicle-user interaction method according to an embodiment of the present invention, which mainly includes an editing process 610, a parsing process 620, and an execution process 630. This method 600 can be executed by means of the above system 100, so the above related descriptions also apply here.

[0105] In the editing process 610, at the information entertainment system of the electronic device and / or the vehicle, user input is received and a rule script is edited based on the user input, which includes user-defined rules. The rules include user-defined triggering conditions and vehicle operations when the triggering conditions are met.

[0106] In the parsing process 620, at the information entertainment system, the rule script is obtained, and a monitoring element list and a function element list are created based on the rule script. The monitoring element list includes sensor elements that directly or indirectly represent the triggering conditions for monitoring, and the function element list includes function elements corresponding to the vehicle operations for execution.

[0107] In the execution process 630, at the information entertainment system, the sensor detection information corresponding to the sensor elements is monitored, and when the sensor detection information indicating that the triggering conditions are met is monitored, the corresponding function elements are executed to implement the user-defined rules.

[0108] The present invention also provides a machine-readable storage medium that stores executable instructions, and when the instructions are executed, the processor executes the above method 600.

[0109] It can be understood that all the above-described modules can be implemented in various ways. These modules can be implemented as hardware, software, or a combination thereof. In addition, any of these modules can be further functionally divided into sub-modules or combined together.

[0110] It will be appreciated that a processor may be implemented using electronic hardware, computer software, or any combination thereof. Whether the processor is implemented as hardware or software will depend upon the particular application and the overall design constraints imposed on the system. As an example, a processor, any part of the processor, or any combination of the processors given in the present invention may be implemented as a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gate logic, discrete hardware circuits, and other suitable processing components configured to perform the various functions described in the present disclosure. The functions of the processor, any part of the processor, or any combination of the processors given in the present invention may be implemented as software executed by a microprocessor, a microcontroller, a DSP, or other suitable platform.

[0111] It will be appreciated that software should be broadly construed as representing instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, running threads, processes, functions, and the like. Software may reside on a computer-readable medium. The computer-readable medium may include, for example, a memory, which may be, for example, a magnetic storage device (such as, a hard disk, a floppy disk, a magnetic strip), an optical disk, a smart card, a flash memory device, a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, or a removable disk. Although the memory is shown as being separate from the processor in several aspects of the present invention, the memory may also be located inside the processor (such as, a cache or a register).

[0112] Although some embodiments have been described above, these embodiments are presented by way of example only and are not intended to limit the scope of the present invention. The appended claims and their equivalents are intended to cover all modifications, substitutions, and alterations made within the scope and spirit of the present invention.

Claims

1. A vehicle-user interaction system, comprising: An editor configured to receive user input and edit a rule script based on the user input, the rule script including rules having trigger conditions defined by the user and vehicle operations when the trigger conditions are satisfied; a parser configured to obtain the rule script and create a list of monitoring elements and a list of functional elements based on the rule script, the list of monitoring elements including sensor elements that directly and / or indirectly represent the trigger conditions for monitoring, and the list of functional elements including functional elements corresponding to the vehicle operations for execution; and an actuator configured to monitor sensor detection information corresponding to the sensor elements and execute the corresponding functional elements to implement the user-defined rules when sensor detection information indicating that the trigger conditions are satisfied is monitored. Wherein, the system further includes an editing module configured to edit the user input into a rule script according to regular rules and a predetermined format. Wherein, the rule script format of the predetermined format includes a first part and a second part that are aligned in length and a third part with a variable length, and wherein the first part sequentially includes an 8-bit header, an 8-bit editor version, an 8-bit AAOS version, and an 8-bit identification part; the second part sequentially includes a 16-bit data packet and a 16-bit reserved part; the third part includes a data part with a variable length.

2. The vehicle-user interaction system according to claim 1, wherein, The editor includes an editing interface, which includes a first sub-interface, a second sub-interface, a third sub-interface, and a fourth sub-interface presented in sequence. Wherein, the first sub-interface includes a status element window, which includes one or more status elements implemented by means of visualization programming components encapsulated by the Android Automotive Operation System (AAOS); the second sub-interface includes a condition setting window, which includes interface elements for the user to set trigger conditions; the third sub-interface includes an operation element window, which includes one or more operation elements implemented by means of visualization programming components encapsulated by the AAOS; the fourth sub-interface includes an operation setting window, which includes interface elements for the user to set vehicle operations.

3. The vehicle-user interaction system according to claim 2, wherein, Receiving user input includes: receiving a first user input on the first sub-interface for the user to select a status element; receiving a second user input on the second sub-interface for the user to set a trigger condition, wherein the trigger condition set by the user is defined as the setting of a judgment condition and / or the setting of a threshold; receiving a third user input on the third sub-interface for the user to select a functional element; and receiving a fourth user input on the fourth sub-interface for the user to set a vehicle operation.

4. The vehicle-user interaction system according to claim 1, wherein, The vehicle-user interaction system further includes a memory disposed in the vehicle, and the rule script edited in the editor is transmitted to the memory by means of wired and / or wireless communication, and the parser obtains the rule script from the memory.

5. The vehicle-user interaction system according to claim 1, wherein, The editor is provided in an electronic device and / or a vehicle, the parser is provided in the vehicle, and the actuator is provided in the vehicle; or the editor, the parser, and the actuator are all provided in an in-vehicle infotainment system; or the editor, the parser, and the actuator are all provided in an electronic device.

6. The vehicle-user interaction system according to claim 5, wherein, The in-vehicle infotainment system uses AAOS as its operating system.

7. The vehicle-user interaction system according to claim 1, wherein, The editor includes one or more editors, and the one or more editors are provided in one or more of an in-vehicle infotainment system of a vehicle and a user's mobile phone, laptop, and desktop computer, so that custom rules can be edited through one or more of an APP, a web page, and a vehicle head unit.

8. A vehicle-user interaction method, executed by the system according to any one of claims 1-7, the method comprising: At an electronic device and / or an in-vehicle infotainment system of a vehicle, user input is received and a rule script is edited based on the user input, which includes a rule having a trigger condition defined by the user and a vehicle operation when the trigger condition is met; at the in-vehicle infotainment system, the rule script is obtained, and a monitoring element list and a function element list are created based on the rule script, the monitoring element list includes sensor elements that directly or indirectly represent the trigger condition for monitoring, and the function element list includes function elements corresponding to the vehicle operation for execution; and at the in-vehicle infotainment system, sensor detection information corresponding to the sensor elements is monitored, and when sensor detection information indicating that the trigger condition is met is monitored, the corresponding function element is executed to implement the user-defined rule, wherein the system further includes an editing module configured to edit the user input into a rule script according to regular rules and a predetermined format; wherein the rule script format of the predetermined format includes a first part and a second part that are aligned in length and a third part with a variable length, and wherein the first part sequentially includes an 8-bit header, an 8-bit editor version, an 8-bit AAOS version, and an 8-bit identification part; the second part sequentially includes a 16-bit data packet and a 16-bit reserved part; and the third part includes a data part with a variable length.

9. A machine-readable storage medium storing executable instructions that, when executed, cause a processor to perform the method according to claim 8.

Images