Human-computer interaction method and system, touch module, controller, vehicle and medium

Abstract

The invention relates to the technical field of vehicle control, particularly provides a man-machine interaction method and system, a touch module, a controller, a vehicle and a medium, and aims to solve the problem of improving interaction experience. The method provided by the invention comprises the steps that a touch module receives an application scene which is sent by a cockpit domain controller and is associated with information presentation equipment, wherein the application scene is an application scene which is associated with the information presentation equipment and corresponds to a currently active application program; the touch module identifies a gesture event of a user in a touch area in the touch module in the application scene, and sends the gesture event to the cabin domain controller, so that the cabin domain controller obtains a control operation matched with the gesture event in the application scene, and an operation result of the control operation is presented on the information presentation equipment. By means of the method, function multiplexing can be conducted on the same gesture event, the number of control functions can be remarkably increased in a limited space based on the multiple gesture events, and the control functions of the gesture events can be conveniently updated.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle control, and specifically relates to a human-computer interaction method, system, touch control module, controller, vehicle and medium. Background Art

[0002] Currently, the conventional human-computer interaction method for vehicles mainly sets multiple physical buttons in the vehicle, and each physical button is respectively used to trigger different functions. The user clicks the corresponding physical button according to the function to be used, such as playing music, adjusting the music volume, etc.

[0003] However, due to the limited space inside the vehicle, the number of physical buttons is usually not large. At the same time, since each physical button can only trigger a fixed function, the functions of the physical buttons are single and cannot be reused, nor can the functions of the physical buttons be updated. Therefore, this method can no longer meet the intelligent and personalized interaction requirements for vehicles, and reduces the user experience of driving the vehicle.

[0004] Correspondingly, a new technical solution is needed in this field to solve the above problems. Summary of the Invention

[0005] In order to overcome the above defects, the present application is proposed to provide a human-computer interaction method, system, touch control module, controller, vehicle and medium that can meet the intelligent and personalized interaction requirements for vehicles and improve the interaction experience.

[0006] In a first aspect, a human-computer interaction method for a vehicle is provided. The method is applied to a touch control module disposed in a vehicle cockpit domain, and a cockpit domain controller and an information presentation device are also disposed in the cockpit domain. The method includes:

[0007] The touch control module receives an application scenario associated with the information presentation device sent by the cockpit domain controller;

[0008] In the application scenario, the touch control module identifies a gesture event of a user's gesture operation in a touch area of the touch control module, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains a control operation matching the gesture event in the application scenario, and presents an operation result of the control operation on the information presentation device;

[0009] Wherein, the application scenario associated with the information presentation device is an application scenario corresponding to an application program associated with the information presentation device and currently active.

[0010] In a technical solution of the above human-computer interaction method, the gesture event at least includes a gesture type, and the method further includes:

[0011] In the described application scenario, the touch control module acquires a vibration pattern that matches the gesture type in the gesture event, and controls the touch area to vibrate according to the vibration pattern.

[0012] In a technical solution of the above human-computer interaction method, the touch control module includes a plurality of touch areas, and a plurality of information presentation devices are provided in the cockpit domain. The plurality of touch areas correspond to the plurality of information presentation devices one by one;

[0013] The touch control module receives the application scenario associated with the information presentation device sent by the cockpit domain controller, including:

[0014] Receiving respectively the application scenario associated with the information presentation device corresponding to each touch area sent by the cockpit domain controller.

[0015] In a technical solution of the above human-computer interaction method, one of the plurality of touch areas is set as the first touch area, and the remaining touch areas are set as the second touch areas;

[0016] The method further includes:

[0017] When the first touch area has the control authority over one of the second touch areas, the first touch area replaces the second touch area and controls the first application program that is associated with the information presentation device corresponding to the second touch area and is currently active.

[0018] In a technical solution of the above human-computer interaction method, the control authority of the second touch area includes an independent control authority. The method further includes:

[0019] When the first touch area has the independent control authority, the first touch area replaces the second touch area and controls the first application program, and

[0020] The first touch area pauses controlling the second application program that is associated with the information presentation device corresponding to the first touch area itself and is currently active.

[0021] In a technical solution of the above human-computer interaction method, the control authority of the second touch area includes a combined control authority. The method further includes:

[0022] When the first touch area has the combined control authority, the first touch area replaces the second touch area and controls the first application program, and

[0023] The first touch area simultaneously controls the second application program that is associated with the information presentation device corresponding to the first touch area itself and is currently active.

[0024] In a technical solution of the above human-computer interaction method, the first touch area replaces the second touch area to control a first application program that is associated with an information presentation device corresponding to the second touch area and is currently active, including:

[0025] Regarding the information presentation device corresponding to the second touch area as the target device;

[0026] Receiving an application scenario associated with the target device sent by the cockpit domain controller;

[0027] In the application scenario, identifying a gesture event of a user's gesture operation in the first touch area, and sending the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains a control operation matching the gesture event in the application scenario and presents an operation result of the control operation on the target device.

[0028] In a second aspect, a human-computer interaction method for a vehicle is provided. The method is applied to a cockpit domain controller provided in a vehicle cockpit domain. The cockpit domain is also provided with a touch module and an information presentation device. The method includes:

[0029] The cockpit domain controller sends an application scenario associated with the information presentation device to the touch module, so that the touch module identifies a gesture event of a user's gesture operation in a touch area in the touch module in the application scenario and sends the gesture event to the cockpit domain controller;

[0030] The cockpit domain controller obtains a control operation matching the gesture event in the application scenario and presents an operation result of the control operation on the information presentation device;

[0031] Wherein, the application scenario associated with the information presentation device is an application scenario corresponding to an application program that is associated with the information presentation device and is currently active.

[0032] In a technical solution of the above human-computer interaction method, the method further includes:

[0033] After the currently active application program is no longer in an active state, the cockpit domain controller determines whether another application program that was in an active state was interrupted before the currently active application program was in an active state;

[0034] If so, re-determine an application scenario associated with the information presentation device according to the other application program, and send the application scenario to the touch area.

[0035] In a technical solution of the above human-computer interaction method, the touch control module includes a plurality of touch control areas, and the cockpit domain is provided with a plurality of information presentation devices, and the plurality of touch control areas correspond to the plurality of information presentation devices one by one;

[0036] The method further includes: the cockpit domain controller sends the application scenarios associated with each of the information presentation devices to the touch control module respectively.

[0037] In a technical solution of the above human-computer interaction method, one of the plurality of touch control areas is set as the first touch control area, and the remaining touch control areas are set as the second touch control areas;

[0038] The method further includes:

[0039] The cockpit domain controller, in response to a detected trigger event, assigns a control permission of one of the second touch control areas to the first touch control area, so that when the first touch control area has the control permission, it can replace the second touch control area and control the currently active first application program associated with the information presentation device corresponding to the second touch control area.

[0040] In a technical solution of the above human-computer interaction method, the assigning a control permission of one of the second touch control areas to the first touch control area includes:

[0041] Assigning a separate control permission of the second touch control area to the first touch control area, so that when the first touch control area has the separate control permission, it can replace the second touch control area and control the first application program, and pause the control of the currently active second application program associated with the information presentation device corresponding to the first touch control area itself.

[0042] In a technical solution of the above human-computer interaction method, after assigning the separate control permission of the second touch control area to the first touch control area, the method further includes:

[0043] The cockpit domain controller controls the information presentation device corresponding to the first touch control area to present the first application program.

[0044] In a technical solution of the above human-computer interaction method, the assigning a control permission of one of the second touch control areas to the first touch control area further includes:

[0045] Assigning a combined control permission of the second touch control area to the first touch control area, so that when the first touch control area has the combined control permission, it can replace the second touch control area and control the first application program, and simultaneously control the currently active second application program associated with the information presentation device corresponding to the first touch control area itself.

[0046] In one technical solution of the above human-machine interaction method, the first touch area replaces the second touch area to control the first application that is associated with the information presentation device corresponding to the second touch area and is currently active, including:

[0047] The touch control module uses the information presentation device corresponding to the second touch area as the target device and receives the application scenario associated with the target device sent by the cockpit domain controller;

[0048] In the application scenario, the touch control module recognizes the gesture event of the user's gesture operation in the first touch area, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains the control operation matching the gesture event in the application scenario, and presents the operation result of the control operation on the target device.

[0049] In one technical solution of the above human-machine interaction method, the method further includes:

[0050] The cockpit domain controller determines whether a trigger event is detected in the following manner:

[0051] If the gesture type of the user's gesture operation recognized in the first touch area is a preset type, it is determined that the trigger event is detected;

[0052] Or,

[0053] If a preset trigger operation is detected through the information presentation device corresponding to the first touch area, it is determined that the trigger event is detected;

[0054] Or,

[0055] If a preset voice message is detected, it is determined that the trigger event is detected.

[0056] In a third aspect, a touch control module is provided. The touch control module is arranged in the vehicle cockpit domain. The cockpit domain is also provided with a cockpit domain controller and an information presentation device. The touch control module is communicatively connected to the cockpit domain controller;

[0057] The touch control module includes:

[0058] A touch area;

[0059] At least one processor;

[0060] And a memory communicatively connected to the at least one processor;

[0061] Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, it implements the human-machine interaction method for vehicles provided in the foregoing first aspect.

[0062] In one technical solution of the above touch control module, the touch control module includes a strip-shaped touch control area, the strip-shaped touch control area is divided into a plurality of touch control areas, and the touch control areas are arranged in sequence along the same direction on the strip-shaped touch control area.

[0063] In a fourth aspect, a cockpit domain controller is provided. The cockpit domain controller is disposed in the vehicle cockpit domain. The cockpit domain is further provided with a touch control module and an information presentation device. The cockpit domain controller is communicatively connected to the touch control module;

[0064] The cockpit domain controller includes:

[0065] At least one processor;

[0066] And a memory communicatively connected to the at least one processor;

[0067] Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the human-computer interaction method for a vehicle provided in the foregoing second aspect is implemented.

[0068] In a fifth aspect, a human-computer interaction system for a vehicle is provided. An information presentation device is disposed in the cockpit domain of the vehicle. The system includes:

[0069] A touch control module and a cockpit domain controller disposed in the cockpit domain;

[0070] Wherein,

[0071] The touch control module is the touch control module provided in the foregoing third aspect;

[0072] The cockpit domain controller is the cockpit domain controller provided in the foregoing fourth aspect.

[0073] In a sixth aspect, a vehicle is provided. An information presentation device is disposed in the cockpit domain of the vehicle. The vehicle further includes the human-computer interaction system for a vehicle provided in the foregoing fifth aspect.

[0074] In a seventh aspect, a computer-readable storage medium is provided, in which a plurality of program codes are stored, and the program codes are adapted to be loaded and run by a processor to execute the human-computer interaction method for a vehicle provided in the foregoing first aspect or second aspect.

[0075] Solution 1. A human-computer interaction method for a vehicle, characterized in that the method is applied to a touch control module disposed in a vehicle cockpit domain, and the cockpit domain is further provided with a cockpit domain controller and an information presentation device. The method includes:

[0076] The touch control module receives an application scenario associated with the information presentation device sent by the cockpit domain controller;

[0077] In the application scenario, the touch control module identifies a gesture event of a user's gesture operation in the touch control area of the touch control module, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains a control operation matching the gesture event in the application scenario, and presents an operation result of the control operation on the information presentation device;

[0078] Wherein, the application scenario associated with the information presentation device is an application scenario corresponding to an application program associated with and currently active on the information presentation device.

[0079] Solution 2. The method according to Solution 1, characterized in that the gesture event at least includes a gesture type, and the method further includes:

[0080] In the application scenario, the touch control module obtains a vibration mode matching the gesture type in the gesture event, and controls the touch control area to vibrate according to the vibration mode.

[0081] Solution 3. The method according to Solution 1, characterized in that the touch control module includes a plurality of touch control areas, and the cockpit domain is provided with a plurality of information presentation devices, and the plurality of touch control areas correspond to the plurality of information presentation devices one by one;

[0082] The touch control module receives the application scenario associated with the information presentation device sent by the cockpit domain controller, including:

[0083] Receiving the application scenarios associated with the information presentation devices corresponding to each touch control area sent by the cockpit domain controller respectively.

[0084] Solution 4. The method according to Solution 3, characterized in that one of the plurality of touch control areas is set as the first touch control area, and the remaining touch control areas are set as the second touch control areas;

[0085] The method further includes:

[0086] When the first touch control area has the control authority over one of the second touch control areas, the first touch control area replaces the second touch control area to control the first application program associated with and currently active on the information presentation device corresponding to the second touch control area.

[0087] Solution 5. The method according to Solution 4, characterized in that the control authority of the second touch control area includes an independent control authority, and the method further includes:

[0088] When the first touch control area has the independent control authority, the first touch control area replaces the second touch control area to control the first application program, and

[0089] The first touch area pauses controlling the currently active second application program associated with the information presentation device corresponding to the first touch area itself.

[0090] Solution 6. The method according to Solution 4, characterized in that the control authority of the second touch area includes a combined control authority, and the method further includes:

[0091] When the first touch area has the combined control authority, the first touch area replaces the second touch area to control the first application program, and

[0092] The first touch area simultaneously controls the currently active second application program associated with the information presentation device corresponding to the first touch area itself.

[0093] Solution 7. The method according to any one of Solutions 4 to 6, characterized in that the first touch area replaces the second touch area to control the currently active first application program associated with the information presentation device corresponding to the second touch area, including:

[0094] Regarding the information presentation device corresponding to the second touch area as the target device;

[0095] Receiving the application scenario associated with the target device sent by the cockpit domain controller;

[0096] In the application scenario, identifying the gesture event of the user's gesture operation in the first touch area, and sending the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains the control operation matching the gesture event in the application scenario and presents the operation result of the control operation on the target device.

[0097] Solution 8. A human-machine interaction method for a vehicle, characterized in that the method is applied to a cockpit domain controller provided in a vehicle cockpit domain, and a touch module and an information presentation device are further provided in the cockpit domain, and the method includes:

[0098] The cockpit domain controller sends the application scenario associated with the information presentation device to the touch module, so that the touch module identifies the gesture event of the user's gesture operation in the touch area in the touch module in the application scenario and sends the gesture event to the cockpit domain controller;

[0099] The cockpit domain controller obtains the control operation matching the gesture event in the application scenario and presents the operation result of the control operation on the information presentation device;

[0100] Among them, the application scenario associated with the information presentation device is the application scenario corresponding to the currently active application program associated with the information presentation device.

[0101] Solution 9. The method according to Solution 8, characterized in that the method further comprises:

[0102] After the current active application program is no longer in the active state, the cockpit domain controller determines whether other application programs that are in the active state were interrupted before the current active application program was in the active state;

[0103] If so, re-determine the application scenario associated with the information presentation device according to the other application program, and send the application scenario to the touch area.

[0104] Solution 10. The method according to Solution 8, characterized in that the touch control module comprises a plurality of touch areas, the cockpit domain is provided with a plurality of information presentation devices, and the plurality of touch areas correspond to the plurality of information presentation devices one by one;

[0105] The method further comprises: the cockpit domain controller respectively sends the application scenario associated with each information presentation device to the touch control module.

[0106] Solution 11. The method according to Solution 10, characterized in that one of the plurality of touch areas is set as the first touch area, and the remaining touch areas are set as the second touch areas;

[0107] The method further comprises:

[0108] In response to the detected trigger event, the cockpit domain controller assigns the control authority of one of the second touch areas to the first touch area, so that when the first touch area has the control authority, it can replace the second touch area and control the currently active first application program associated with the information presentation device corresponding to the second touch area.

[0109] Solution 12. The method according to Solution 11, characterized in that the assigning the control authority of one of the second touch areas to the first touch area comprises:

[0110] Assign the separate control authority of the second touch area to the first touch area, so that when the first touch area has the separate control authority, it can replace the second touch area and control the first application program, and pause the control of the currently active second application program associated with the information presentation device corresponding to the first touch area itself.

[0111] Solution 13. The method according to Solution 11, characterized in that, after assigning the separate control authority of the second touch area to the first touch area, the method further includes:

[0112] The cockpit domain controller controls the information presentation device corresponding to the first touch area to present the first application.

[0113] Solution 14. The method according to Solution 11, characterized in that, the assignment of the control authority of one of the second touch areas to the first touch area further includes:

[0114] Assigning the combined control authority of the second touch area to the first touch area, so that when the first touch area has the combined control authority, it can replace the second touch area to control the first application, and at the same time control the second application that is associated with the information presentation device corresponding to the first touch area itself and is currently active.

[0115] Solution 15. The method according to any one of Solutions 11 to 14, characterized in that, when the first touch area replaces the second touch area to control the first application that is associated with the information presentation device corresponding to the second touch area and is currently active, it includes:

[0116] The touch module takes the information presentation device corresponding to the second touch area as the target device and receives the application scenario sent by the cockpit domain controller and associated with the target device;

[0117] In the application scenario, the touch module identifies the gesture event of the user's gesture operation on the first touch area, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains the control operation matching the gesture event in the application scenario and presents the operation result of the control operation on the target device.

[0118] Solution 16. The method according to Solution 11, characterized in that, the method further includes:

[0119] The cockpit domain controller determines whether a trigger event is detected in the following ways:

[0120] If the gesture type of the user's gesture operation on the first touch area is identified as a preset type, it is determined that the trigger event is detected;

[0121] Or, if a preset trigger operation is detected through the information presentation device corresponding to the first touch area, it is determined that the trigger event is detected;

[0122] Or, if a preset voice message is detected, it is determined that the trigger event is detected.

[0123] Solution 17. A touch control module, characterized in that the touch control module is arranged in the vehicle cockpit domain, and a cockpit domain controller and an information presentation device are also arranged in the cockpit domain, and the touch control module is communicatively connected with the cockpit domain controller;

[0124] The touch control module includes:

[0125] A touch area;

[0126] At least one processor;

[0127] And a memory communicatively connected with the at least one processor;

[0128] Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the human-machine interaction method for a vehicle described in any one of Solutions 1 to 7 is implemented.

[0129] Solution 18. The touch control module according to Solution 17, characterized in that the touch control module includes a strip-shaped touch area, and the strip-shaped touch area is divided into a plurality of touch areas, and the touch areas are arranged in sequence along the same direction on the strip-shaped touch area.

[0130] Solution 19. A cockpit domain controller, characterized in that the cockpit domain controller is arranged in the vehicle cockpit domain, and a touch control module and an information presentation device are also arranged in the cockpit domain, and the cockpit domain controller is communicatively connected with the touch control module;

[0131] The cockpit domain controller includes:

[0132] At least one processor;

[0133] And a memory communicatively connected with the at least one processor;

[0134] Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the human-machine interaction method for a vehicle described in any one of Solutions 8 to 16 is implemented.

[0135] Solution 20. A human-machine interaction system for a vehicle, characterized in that an information presentation device is arranged in the cockpit domain of the vehicle, and the system includes:

[0136] A touch control module and a cockpit domain controller arranged in the cockpit domain;

[0137] Wherein,

[0138] The touch control module is the touch control module described in Solution 17 or 18;

[0139] The cockpit domain controller is the cockpit domain controller described in Solution 19.

[0140] Solution 21. A vehicle, characterized in that an information presentation device is provided in the cockpit domain of the vehicle, and the vehicle further includes the human-machine interaction system for vehicles described in Solution 20.

[0141] Solution 22. A computer-readable storage medium storing multiple program codes, characterized in that the program codes are adapted to be loaded and run by a processor to execute the human-machine interaction method for vehicles described in any one of Solutions 1 to 16.

[0142] One or more of the above technical solutions of the present application have at least one or more of the following beneficial effects:

[0143] In a technical solution of implementing the human-machine interaction method for vehicles provided by the present application, the method can be applied to a touch module provided in the cockpit domain of a vehicle, and a cockpit domain controller and an information presentation device are further provided in the cockpit domain. The method includes: the touch module receives an application scenario associated with the information presentation device sent by the cockpit domain controller, and the application scenario is an application scenario corresponding to the currently active application program associated with the information presentation device; the touch module, in the application scenario, recognizes a gesture event of a user's gesture operation in the touch area of the touch module, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains, in the application scenario, a control operation matching the gesture event, and presents an operation result of the control operation on the information presentation device.

[0144] Based on the above implementation, the touch module and the cockpit domain controller control the currently active application program based on the application scenario, and it can be determined that different application scenarios may be obtained according to different application programs. In this way, even if the same gesture event is sampled in multiple different application scenarios, different function controls for different application programs can be accurately and reliably completed, realizing the function reuse of the same gesture event; multiple different gesture events can be recognized through one touch area, and one gesture event can realize the reuse of multiple functions. Therefore, based on multiple different gesture events, the number of control functions can be significantly increased without occupying too much space in the vehicle; when wanting to update the control function of a gesture event, the control operation matching the gesture event can be changed, and the operation is simple and convenient, with high flexibility.

[0145] In another technical solution of the human-machine interaction method for vehicles provided in this application, this method can be applied to a cockpit domain controller disposed in a vehicle cockpit domain. A touch module and an information presentation device are also disposed in the cockpit domain. The method includes: the cockpit domain controller sends an application scenario associated with the information presentation device to the touch module, so that the touch module can identify a gesture event of a user's gesture operation in a touch area of the touch module under the application scenario, and send the gesture event to the cockpit domain controller; the cockpit domain controller obtains a control operation matching the gesture event under the application scenario, and presents an operation result of the control operation on the information presentation device; wherein, the application scenario is an application scenario associated with the information presentation device and corresponding to the currently active application program. The above implementation is similar to the foregoing implementation, and can also achieve function reuse of the same gesture event, increase the number of control functions without occupying too much vehicle interior space, and can update control functions simply and conveniently. BRIEF DESCRIPTION OF THE DRAWINGS

[0146] With reference to the accompanying drawings, the disclosure of this application will become more readily understood. It is easy for those skilled in the art to understand that: these drawings are only for illustrative purposes and are not intended to limit the protection scope of this application. Among them:

[0147] Figure 1 is a schematic flowchart of the main steps of a human-machine interaction method for vehicles according to an embodiment of this application;

[0148] Figure 2 is a schematic flowchart of the process of human-machine interaction in a multimedia scenario according to an embodiment of this application;

[0149] Figure 3 is a schematic flowchart of the process of human-machine interaction in a navigation scenario according to an embodiment of this application;

[0150] Figure 4 is a schematic flowchart of the process of human-machine interaction in an incoming call scenario according to an embodiment of this application;

[0151] Figure 5 is a schematic diagram of multiple touch areas according to an embodiment of this application;

[0152] Figure 6 is a schematic flowchart of the main steps of a human-machine interaction method for vehicles according to another embodiment of this application;

[0153] Figure 7 is a schematic flowchart of the main steps of a human-machine interaction method for vehicles according to still another embodiment of this application;

[0154] Figure 8It is a schematic diagram of the main connection structure between the memory and the processor in a touch control module according to an embodiment of the present application;

[0155] Figure 9 It is a schematic diagram of the main connection structure between the memory and the processor in a cockpit domain controller according to an embodiment of the present application.

[0156] List of reference numerals:

[0157] 11: Memory; 12: Processor; 21: Memory; 22: Processor. Detailed implementation manners

[0158] The following describes some implementation manners of the present application with reference to the accompanying drawings. Those skilled in the art should understand that these implementation manners are only used to explain the technical principle of the present application and are not intended to limit the protection scope of the present application.

[0159] In the description of the present application, the "processor" may include hardware, software, or a combination of both. The processor may be a central processing unit, a microprocessor, an image processor, a digital signal processor, or any other suitable processor. The processor has data and / or signal processing functions. The processor may be implemented in software, in hardware, or in a combination of both. The computer-readable storage medium includes any suitable medium that can store program code, such as magnetic disks, hard disks, optical discs, flash memories, read-only memories, random access memories, and so on.

[0160] For any relevant user personal information that may be involved in the embodiments of the present application, it is all processed in strict accordance with the requirements of laws and regulations, following the principles of legality, legitimacy, and necessity, based on reasonable purposes of business scenarios, for the personal information actively provided by the user during the use of the product / service or generated due to the use of the product / service, as well as the personal information obtained with the user's authorization.

[0161] The user personal information processed by the present application will vary depending on the specific product / service scenario, and it is necessary to be subject to the specific scenario of the user's use of the product / service. It may involve the user's account information, device information, driving information, vehicle information, or other relevant information. The present application will treat the user's personal information and its processing with a high degree of diligence.

[0162] The present application attaches great importance to the security of user personal information and has taken security protection measures that meet industry standards and are reasonable and feasible to protect the user's information and prevent personal information from being accessed, publicly disclosed, used, modified, damaged, or lost without authorization.

[0163] First, some terms involved in the present application are explained here.

[0164] An information presentation device, which may include a display device and / or a voice device. The display device may be a device with an information display function such as a screen, a dashboard, etc., or a device that simultaneously has an information display function and a voice interaction function; the voice device includes but is not limited to a microphone.

[0165] An application (APP), which can be presented on the information presentation device. Among them, the presented content includes but is not limited to information such as the screen and voice of the application. Taking the music player app as an example, on the information presentation device, the user interface (UI) of the music player app can be displayed, and the music information of the music player app can be output, etc.

[0166] In the embodiments of the present application, the applications that can be presented on the information presentation device can be set in advance. This setting can also be understood as associating the information presentation device with the applications. In some embodiments, if there are multiple information presentation devices, the applications that can be presented on each information presentation device are set respectively, that is, the applications are associated with each information presentation device respectively. It should be noted that different information presentation devices can be associated with different applications, but they can also be associated with the same application. For example, the information presentation devices include a vehicle center console screen and a co-pilot screen, and both of these devices can be associated with the music player app.

[0167] An active application can be understood as an application that is running. In some embodiments, when there are multiple running applications, the currently active application can be the application with the highest response level, or the application that is running in the foreground. For example, music is being played through the music player app, and the music player app is a running application. If there is only this one running application at this time, then the currently active application is the music player app. If the user selects to run the music player app in the background and opens the navigation app, and the navigation app starts running, then there are two running applications at this time. However, since the navigation app is running in the foreground and has a higher response level than the music player app, the currently active application is the navigation app. Further, if a call comes in at this time and the incoming call app starts running, then there are three running applications at this time. However, since the response level of the incoming call app is higher than the other two apps, the currently active application is the incoming call app.

[0168] An application scenario, which can be used to describe the scenario in which the user is located when the application is running. This scenario can be determined according to the function of the application. Taking the music player app as an example, according to its function, it can be determined that the user is in a multimedia scenario when the music player app is running.

[0169] In the embodiments of the present application, multiple different application scenarios can be preset in advance, and one or more different application programs can be associated with each application scenario according to the functions of each application program. Through this associated setting, the application scenario associated with each application scenario can be accurately obtained, that is, the application scenario corresponding to each application program.

[0170] Next, an embodiment of a human-machine interaction method for a vehicle will be described.

[0171] First, in combination with the attached Figure 1 , an embodiment of a human-machine interaction method implemented by a touch control module and a cockpit domain controller provided in a vehicle cockpit domain as the execution main body will be described.

[0172] In an embodiment according to the present application, in addition to the touch control module and the cockpit domain controller (Cockpit Domain Functional, CDF) in the vehicle cockpit domain, an information presentation device is also provided. In addition, the touch control module may include a touch area where the user can perform gesture operations such as clicking and swiping. In some embodiments, there may be multiple touch control modules.

[0173] Referring to the attached Figure 1 , the human-machine interaction method for a vehicle according to the embodiments of the present application may include the following steps S101 to step S106.

[0174] Step S101: The cockpit domain controller obtains the currently active application program associated with the information presentation device.

[0175] Step S102: The cockpit domain controller determines the application scenario corresponding to the above application program and sends the application scenario to the touch control module. Among them, this application scenario can also be understood as the application scenario associated with the information presentation device.

[0176] In this embodiment, multiple different application scenarios can be preset in advance, and one or more different application programs can be associated with each application scenario according to the functions of each application program. After obtaining the application program, the application scenario associated with this application program can be obtained according to the association relationship between the application scenario and the application program.

[0177] For example, the application programs include a music player app, a video player app, a call app, and a navigation app. The preset application scenarios may include a multimedia scenario, a call scenario, and a navigation scenario. Among them, the multimedia scenario is associated with the music player app and the video player app, and the call scenario and the navigation scenario are associated with the call app and the navigation app respectively.

[0178] Step S103: The touch control module receives the application scenario sent by the cockpit domain controller.

[0179] Step S104: In the above application scenario, the touch control module identifies a gesture event of a user's gesture operation in the touch area of the touch control module, and sends the gesture event to the cockpit domain controller.

[0180] The gesture event includes, but is not limited to, information such as the gesture type and the coordinates of the gesture operation in the touch area.

[0181] In some embodiments, after receiving the application scenario, the touch control module can switch the application scenario associated with itself to this application scenario. Since this application scenario is also the application scenario associated with the information presentation device, through scenario switching, the application scenarios associated with the touch control module and the information presentation device can be kept consistent.

[0182] Each application program has different functions. For an application program with complex functions, relatively many gesture events may be preset, and different function controls are performed on the application program through each gesture event respectively; correspondingly, for an application program with simple functions, relatively few gesture events may be preset, and different function controls are performed on the application program through each gesture event respectively. Based on this, it can be determined that for each application scenario, if the application program associated with it requires more gesture events, then this application scenario also requires more gesture events, and vice versa. Therefore, in this embodiment, the gesture events that can be detected by the touch control module can be preset according to the gesture events required by each application scenario. For an application scenario with few gesture events, after the touch control module detects the user's gesture operation, as long as a small number of gesture events are compared, the user's gesture event can be accurately identified, greatly reducing the processing pressure or computing power consumption of the touch control module.

[0183] Step S105: The cockpit domain controller obtains the control operation that matches the gesture event in the above application scenario.

[0184] In this embodiment, the one-to-one mapping relationship between different gesture events and different control operations can be preset for each application scenario. The cockpit domain controller can obtain the mapping relationship corresponding to the current application scenario of the information presentation device, and then match the gesture event sent by the touch control module based on the mapping relationship to obtain the corresponding control operation.

[0185] Step S106: The cockpit domain controller presents the operation result of the control operation on the information presentation device. For example, if the application program is a video playback app and the control operation is to fast forward 15 seconds, then the video playback app can be controlled to fast forward the currently playing video by 15 seconds.

[0186] Based on the method described in the above steps S101 to S106, the same gesture event (such as swiping) can be adopted in different application scenarios to perform different function controls on different application programs, realizing the function reuse of the same gesture event. Further, a touch control module can recognize multiple different gesture events, and the same gesture event can also realize function reuse. Therefore, this method can also significantly increase the number of control functions without occupying too much space in the vehicle. In addition, when wanting to update the control function of a gesture event, the control operation matching the gesture event can be changed, which is simple, convenient, and has high flexibility.

[0187] The following takes Figure 2 the multimedia scenario shown as an example to briefly describe the human-machine interaction process according to the above embodiment. Specifically, the user starts the music player app on the vehicle's center console screen to play music. At the same time, the cockpit domain controller detects that the application program presented synchronously and currently active on the vehicle's center console screen is the music player app, determines that the application scenario currently associated with the vehicle's center console screen is the multimedia scenario, and sends the multimedia scenario to the touch control module. Subsequently, the touch control module switches its associated application scenario to the multimedia scenario. The user quickly swipes to the right in the touch area, and the touch control module recognizes that the gesture event is a right swipe gesture and reports the right swipe gesture event to the cockpit domain controller. The cockpit domain controller obtains that the control operation matching the right swipe gesture in the multimedia scenario is to switch to the next piece of music, and controls the music player app to switch to the next piece of music.

[0188] After a period of time, the user closes the music player app on the vehicle's center console screen and starts the video player app. The cockpit domain controller detects that the application program presented synchronously and currently active on the vehicle's center console screen is the video player app, determines that the application scenario currently associated with the vehicle's center console screen is the multimedia scenario, and sends the multimedia scenario to the touch control module. Subsequently, the touch control module switches its associated application scenario to the multimedia scenario. The user quickly swipes to the right in the touch area, and the touch control module recognizes that the gesture event is a right swipe gesture and reports the right swipe gesture event to the cockpit domain controller. The cockpit domain controller obtains that the control operation matching the right swipe gesture in the multimedia scenario is to fast forward the video by 15 seconds, and controls the video player app to fast forward the currently playing video by 15 seconds. It should be noted that since the previous application scenario of the touch control module is also the multimedia scenario, after receiving that the application scenario sent by the cockpit domain controller is still the multimedia scenario, the touch control module can not perform the scenario switching action and still control the video player app based on the multimedia scenario.

[0189] The above is a brief description of the human-machine interaction process in the multimedia scenario.

[0190] The following further describes the human-machine interaction method for vehicles according to the embodiments of the present application.

[0191] In some embodiments, the touch control module can also obtain a vibration pattern matching the gesture type in the gesture event in the application scenario and control the touch area to vibrate according to the vibration pattern. The touch area can be provided with a vibration device, and the touch area can control the vibration device to vibrate according to the vibration pattern. In this embodiment, it can be preset which gesture type has a matching vibration pattern in each application scenario, and the one-to-one mapping relationship between different gesture types and different vibration patterns can be set. The touch control module can obtain the mapping relationship corresponding to the current application scenario, and then match the gesture type based on the mapping relationship to obtain the corresponding vibration pattern.

[0192] In this embodiment, the touch control module directly matches the vibration pattern and then vibrates according to the vibration pattern. Compared with the cockpit domain controller obtaining the vibration pattern matching the gesture type and then feeding back the vibration pattern to the touch control module, and the touch control module vibrating according to the received vibration pattern, in this embodiment, the touch control module can vibrate within a very short time after recognizing the gesture type, greatly improving the response speed of vibration and thus improving the user's interactive experience.

[0193] The following takes Figure 3 the navigation scenario shown as an example to briefly describe the human-computer interaction process according to the above embodiment. Specifically, the user searches for the destination of the vehicle's travel by voice search. The cockpit domain controller controls the vehicle's central control screen to start the navigation app, searches and displays the destination result list through the navigation app. At the same time, the cockpit domain controller detects that the application program that is synchronously presented and currently active on the vehicle's central control screen is the navigation app, and determines that the application scenario currently associated with the vehicle's central control screen is the navigation scenario (or Figure 3 the HMI control scenario shown), sends the navigation scenario to the touch control module, and sets or pre-sets the vibration pattern ( Figure 3 the vibration trigger spacing in) of the continuous sliding gesture of the touch control module in this scenario. Subsequently, the touch control module switches its associated application scenario to the navigation scenario. The user quickly swipes right on the touch area, and the touch control module recognizes that the gesture event is a right swipe gesture and reports the right swipe gesture event to the cockpit domain controller. The cockpit domain controller obtains that the control operation matching the right swipe gesture in the navigation scenario is to switch to the next / right one selected in the list, and controls the navigation app to switch the destination display result list to select the next / right one destination in the list.

[0194] After a period of time, the user continuously swipes right in the touch area. The touch module recognizes that the gesture event is a continuous right swipe, reports the gesture event and the touch movement coordinates as a gesture event to the cockpit domain controller, and vibrates once after the movement distance is met. The cockpit domain controller obtains that the control operation matching the above gesture event in the navigation scenario is to move the list focus in the moving direction corresponding to the right swipe. At the same time, the moving distance can be obtained according to the touch movement coordinates. Subsequently, the navigation app is controlled to move the focus of the destination display result list by the above distance in the above moving direction.

[0195] The above is a simple description of the human-machine interaction process in the navigation scenario.

[0196] Next, the human-machine interaction method for vehicles according to the embodiments of the present application will be further described.

[0197] In some embodiments, after the currently active application is no longer in the active state, the cockpit domain controller can also determine whether other applications that are in the active state have been interrupted before the currently active application is in the active state; if so, re-determine the application scenario associated with the information presentation device according to the above other applications, and send the application scenario to the touch module. Through this embodiment, after the currently active application is no longer in the active state, the application that was interrupted before can be restored in time, without the user having to start the interrupted application again, further improving the user's interaction experience.

[0198] Next, taking Figure 4 the incoming call scenario shown as an example, the human-machine interaction process according to the above embodiment will be simply described. Specifically, the vehicle center control screen is starting the music player app to play music. At a certain moment, the user's mobile phone receives a call. The cockpit domain controller controls the vehicle center control screen to interrupt the music player app and start the incoming call app, and displays the incoming call interface on the vehicle center control screen. The cockpit domain controller obtains that the application scenario associated with the vehicle center control screen is the incoming call scenario, sends the incoming call scenario to the touch module, and sets or pre-sets the vibration mode of the swipe gesture in this scenario ( Figure 4 the vibration trigger distance level in). Subsequently, the touch module switches its associated application scenario to the incoming call scenario. The user swipes left / right in the touch area. The touch module recognizes that the gesture event is a left / right swipe and reports the left / right swipe gesture event to the cockpit domain controller. The cockpit domain controller obtains that the control operation matching the left / right swipe type in the incoming call scenario is to answer / reject the incoming call, and controls the incoming call app to answer / reject the incoming call.

[0199] After the call ends, the incoming call app closes, and the music player app restarts. The application scenario associated with the vehicle's center control screen is the multimedia scenario. The cockpit domain controller sends the multimedia scenario to the touch module so that the touch module can switch the application scenario associated with itself to the multimedia scenario.

[0200] The above is a simple description of the human-machine interaction process in the incoming call scenario.

[0201] Next, the human-machine interaction method for vehicles according to the embodiments of the present application will be further described.

[0202] In the human-machine interaction method for vehicles according to the embodiments of the present application, the touch module may include multiple touch areas, and the cockpit domain may also be provided with multiple information presentation devices, and the multiple touch areas correspond to the multiple information presentation devices one by one.

[0203] Refer to the appendix Figure 5 In some embodiments, the touch module may include three touch areas 1, 2, and 3 arranged in sequence. The information presentation devices corresponding to the touch areas 1, 2, and 3 are the driver's screen, the center control screen, and the co-pilot screen in the vehicle cockpit domain respectively. Below, in combination with Tables 1-3, the application programs associated with the driver's screen, the center control screen, and the co-pilot screen, as well as information such as the application scenarios corresponding to each application program, will be briefly described.

[0204] I. Driver's Screen Table 1

[0205] As shown in Table 1, the application scenarios associated with the driver's screen may include screen cards and mode switching. Taking the screen card as an example, in the application scenario of the screen card, the application program associated with and currently active on the driver's screen may be card switching. The functions of card switching include switching to the previous card, switching to the next card, and confirming the switch. Among them, taking switching to the previous card as an example, the gesture type for executing the function of switching to the previous card is a light swipe / slide upward.

[0206] Below, the cards and modes in Table 1 will be briefly described. A card refers to an application component, through which users can use the application program more intuitively. For example, the card may include a weather card, etc. A mode refers to the operating mode of the screen. For example, the mode may include a standard mode, a night mode, etc. Under different modes, the display parameters such as the brightness and color temperature of the screen are also different.

[0207] II. Center Control Screen Table 2

[0208] As shown in Table 2, the application scenarios associated with the central control screen can include multimedia, communication, selection list, and global. Taking multimedia as an example, in the multimedia application scenario, the applications associated with and currently active on the central control screen can be music and video. Taking music as an example, the functions of music include pause / play, play previous, play next, favorite, and drag progress bar. Among them, taking pause / play as an example, the gesture type for performing the pause / play function can be a single click, and this gesture type has a vibration mode, which is normal vibration twice.

[0209] III. Co-pilot Screen Table 3

[0210] As shown in Table 3, the application scenarios associated with the co-pilot screen can include screen cards and mode switching. Taking screen cards as an example, in the screen card application scenario, the applications associated with and currently active on the co-pilot screen can be card switching. The functions of card switching include switching to the previous card, switching to the next card, and confirming the switch. Among them, taking switching to the previous card as an example, the gesture type for performing the function of switching to the previous card is a light swipe / slide upward.

[0211] The meanings of cards and modes in Table 3 are the same as those of cards and modes in Table 1.

[0212] The following further describes the human-computer interaction method in the case of the above-mentioned multiple touch areas and multiple information presentation devices.

[0213] In some embodiments, the cockpit domain controller can send the application scenarios associated with each information presentation device to the touch control module respectively.

[0214] Based on this embodiment, it is possible to accurately control through the touch areas corresponding to each information presentation device respectively, improving the reliability and accuracy of interaction control in the case of multiple touch areas and multiple information presentation devices.

[0215] In some embodiments, one touch area among the multiple touch areas can be set as the first touch area, and the remaining touch areas can be set as the second touch areas. Then, a control permission of a second touch area can be assigned to the first touch area, so that the first touch area can replace this second touch area for touch control. Specifically, the cockpit domain controller can, in response to a detected trigger event, assign a control permission of a second touch area to the first touch area; when the first touch area has a control permission of a second touch area, the first touch area replaces this second touch area to control the first application associated with and currently active on the information presentation device corresponding to the second touch area.

[0216] Based on this embodiment, when an abnormality occurs in the second touch area or when it is inconvenient for a user near the second touch area to perform gesture operations, etc., the first touch area can be used to control the information presentation device corresponding to the second touch area, further improving the user's interaction experience. It should be noted that those skilled in the art can flexibly set which touch area is the first touch area according to actual needs, and this embodiment does not limit this.

[0217] The following further describes the above embodiment of allocating control permissions.

[0218] In some embodiments, the cockpit domain controller can, in response to a detected trigger event, allocate a separate control permission for a second touch area to the first touch area. When the first touch area has this separate control permission for the second touch area, the first touch area can replace this second touch area to control the currently active first application associated with the information presentation device corresponding to the second touch area, and the first touch area pauses controlling the currently active second application associated with the information presentation device corresponding to the first touch area itself. Based on this embodiment, when the application scenarios associated with the information presentation devices corresponding to the first touch area and the replaced second touch area are different, the first touch area can be made to temporarily pause controlling the currently active application associated with the information presentation device corresponding to itself, so as to avoid accidentally controlling the currently active application associated with the information presentation device corresponding to itself while controlling the information presentation device corresponding to the second touch area.

[0219] In addition, after allocating a separate control permission for a second touch area to the first touch area, the cockpit domain controller can also control the information presentation device corresponding to the first touch area to synchronously present the above-mentioned currently active first application. Generally speaking, the user using the first touch area is usually near the information presentation device corresponding to the first touch area. And this embodiment controls the information presentation device corresponding to the first touch area to present the presentation screen of the information presentation device corresponding to the replaced second touch area, which will be more conducive to the user of the first touch area to control. For example, the information presentation device corresponding to the replaced second touch area is a screen located in the co-pilot of the vehicle, and the information presentation device corresponding to the first touch area is the central control screen in the front row of the vehicle. When the driver wants to control the screen in the co-pilot of the vehicle, based on the above embodiment, the central control screen can be made to present the picture of the screen in the co-pilot of the vehicle. The driver can control the screen in the co-pilot of the vehicle through the first touch area and the content displayed on the central control screen.

[0220] In some embodiments, the cockpit domain controller may also allocate the combined control authority of a second touch area to the first touch area in response to a detected trigger event. When the first touch area has the combined control authority of a second touch area, the first touch area may replace this second touch area to control the first application that is currently active and associated with the information presentation device corresponding to the second touch area, and at the same time, the first touch area controls the second application that is currently active and associated with the information presentation device corresponding to the first touch area itself. Based on this embodiment, when the application scenarios of the information presentation devices corresponding to the first touch area and the replaced second touch area are the same, the applications that are currently active and associated with these information presentation devices can be controlled simultaneously, realizing the synchronous control of multiple information presentation devices through one touch area. For example, the volume output by the information presentation devices corresponding to both of them can be adjusted simultaneously.

[0221] The method for the first touch area to replace the second touch area to control the first application that is currently active and associated with the information presentation device corresponding to the second touch area in the above-mentioned embodiments of individual and combined control authorities will be described below. Specifically, the touch module may use the information presentation device corresponding to the second touch area as the target device and receive the application scenario associated with the target device sent by the cockpit domain controller. In the above application scenario, the touch module identifies the gesture event of the user's gesture operation in the first touch area and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains the control operation that matches the gesture event in the application scenario and presents the operation result of the control operation on the target device.

[0222] The method for the cockpit domain controller to detect the trigger event will be described below. Specifically, if the gesture type of the user's gesture operation in the first touch area is identified as the preset type, it is determined that the trigger event is detected; or, if a preset trigger operation is detected through the information presentation device corresponding to the first touch area, it is determined that the trigger event is detected; or, if a preset voice message is detected, it is determined that the trigger event is detected. Based on this embodiment, when the user wants to allocate the control authority of the second touch area to the first touch area, it can be allocated in multiple different ways such as gestures, voice, and device operations, improving the convenience and flexibility of authority allocation.

[0223] It should be noted that those skilled in the art can flexibly set the preset type of the above gesture type, the above preset trigger operation, and the above preset voice message according to actual needs, and this embodiment does not make specific limitations. For example, the preset type of the gesture type can be double-click, the preset trigger operation can be to click a preset control on the information presentation device, and the preset voice message can be to allocate the individual control authority of touch area 2 to touch area 1.

[0224] The above is a description of an embodiment of a human-machine interaction method implemented with a touch control module and a cockpit domain controller as the execution entities together.

[0225] Next, in conjunction with the attached Figure 6 , an embodiment of a human-machine interaction method implemented with the touch control module alone as the execution entity will be described.

[0226] In an embodiment according to the present application, an information presentation device is also provided in the vehicle cockpit domain. In addition, the touch control module includes a touch area.

[0227] Referring to the attached Figure 6 , the human-machine interaction method for a vehicle according to an embodiment of the present application may include the following steps S201 to step S202.

[0228] Step S201: The touch control module receives an application scenario associated with the information presentation device sent by the cockpit domain controller.

[0229] The application scenario is an application scenario corresponding to the currently active application program associated with the information presentation device.

[0230] Step S202: In the application scenario, the touch control module identifies a gesture event of a user's gesture operation in the touch area of the touch control module, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains a control operation matching the gesture event in the application scenario, and presents the operation result of the control operation on the information presentation device.

[0231] Based on the method described in the above steps S201 to step S202, in cooperation with the cockpit domain controller, the touch control module can implement human-machine interaction. In addition, based on this method, the same gesture event (such as swiping) can be used in different application scenarios to perform different function controls on different application programs, realizing the function reuse of the same gesture event. Further, a touch control module can identify multiple different gesture events, and the same gesture event can also realize function reuse. Therefore, this method can also significantly increase the number of control functions without occupying too much space in the vehicle. In addition, when wanting to update the control function of the gesture event, the control operation matching the gesture event can be changed, and the operation is simple and convenient, with high flexibility.

[0232] In some embodiments, the touch control module can also obtain a vibration mode matching the gesture type in the gesture event in the above application scenario, and control the touch area to vibrate according to the vibration mode.

[0233] Further, in the human-machine interaction method for a vehicle according to an embodiment of the present application, the touch control module may include multiple touch control areas, and the cockpit domain may also be provided with multiple information presentation devices, and the multiple touch control areas correspond to the multiple information presentation devices one by one.

[0234] The human-machine interaction method in this case will be further described below.

[0235] In some embodiments, when the touch control module receives the application scenario associated with the information presentation device sent by the cockpit domain controller (step S201), it respectively receives the application scenarios associated with the information presentation devices corresponding to each touch control area sent by the cockpit domain controller.

[0236] In some embodiments, one of the multiple touch control areas can be set as the first touch control area, and the remaining touch control areas can be set as the second touch control areas. Then, a control permission of a second touch control area is assigned to the first touch control area, so that the first touch control area can perform touch operations on behalf of this second touch control area. Specifically, in this embodiment, when the first touch control area has the control permission of a second touch control area, the first touch control area can replace this second touch control area and control the first application program that is associated with the information presentation device corresponding to the second touch control area and is currently active.

[0237] The above embodiments will be further described below.

[0238] In some embodiments, when the first touch control area has the separate control permission of a second touch control area, the first touch control area can replace this second touch control area and control the above-mentioned first application program, and the first touch control area suspends the control of the second application program that is associated with the information presentation device corresponding to the first touch control area itself and is currently active.

[0239] In some embodiments, when the first touch control area has the combined control permission of a second touch control area, the first touch control area can replace this second touch control area and control the above-mentioned first application program, and the first touch control area simultaneously controls the above-mentioned second application program.

[0240] In the above embodiments of the separate and combined control permissions, the method by which the first touch control area replaces the second touch control area and controls the above-mentioned first application program is the same as the related method in the human-machine interaction method in which the touch control module and the cockpit domain controller jointly serve as the execution entities, and will not be elaborated here.

[0241] It should be noted that in this embodiment, the functions of the cockpit domain controller are the same as those of the cockpit domain controller in the aforementioned human-machine interaction method in which the touch control module and the cockpit domain controller jointly serve as the execution entities, and will not be elaborated here. In addition, the technical effects of the touch control module and the cockpit domain controller in different embodiments in this embodiment are also the same as those in the aforementioned human-machine interaction method in which the touch control module and the cockpit domain controller jointly serve as the execution entities, and will not be elaborated either.

[0242] The above is the description of the embodiment of the human-machine interaction method implemented by the touch control module alone as the execution entity.

[0243] Next, Figure 7 in conjunction with the appended

[0244] In an embodiment according to the present application, an information presentation device is also provided in the vehicle cockpit domain. In addition, the touch control module includes a touch area.

[0245] Referring to the appended Figure 7 drawings, the human-machine interaction method for a vehicle according to an embodiment of the present application may include the following steps S301 to step S305.

[0246] Step S301: The cockpit domain controller obtains the currently active application program associated with the information presentation device.

[0247] Step S302: The cockpit domain controller determines the application scenario corresponding to the above application program, and sends the application scenario to the touch control module, so that the touch control module can identify the gesture event of the user's gesture operation in the touch area of the touch control module in this application scenario, and send the gesture event to the cockpit domain controller. Among them, this application scenario can also be understood as the application scenario associated with the information presentation device.

[0248] Step S303: The cockpit domain controller receives the gesture event sent by the touch control module.

[0249] Step S304: The cockpit domain controller obtains the control operation that matches the gesture event in the above application scenario.

[0250] Step S305: The cockpit domain controller presents the operation result of the control operation on the information presentation device.

[0251] Based on the method described in the above steps S301 to S305, in cooperation with the touch control module, the human-machine interaction can be realized by the cockpit domain controller. In addition, based on this method, the same gesture event (such as swiping) can be used in different application scenarios to perform different function controls on different application programs, realizing the function reuse of the same gesture event. Further, a touch area can recognize multiple different gesture events, and the same gesture event can also realize function reuse. Therefore, this method can also significantly increase the number of control functions without occupying too much space in the vehicle. In addition, when wanting to update the control function of the gesture event, the control operation matching the gesture event can be changed, which is simple and convenient to operate and has high flexibility.

[0252] The following further describes the human-machine interaction method for vehicles according to the embodiments of the present application.

[0253] In some embodiments, after the currently active application program is no longer in the active state, the cockpit domain controller determines whether other application programs that are in the active state are interrupted before the currently active application program is in the active state; if so, the application scenario associated with the information presentation device is re-determined according to the above other application programs, and the application scenario is sent to the touch control module.

[0254] Specifically, in the case of multiple running application programs, the currently active application program can be the application program with the highest response level, or the application program running in the foreground. For example, music is being played through the music player app, and the music player app is the running application program. If there is only this one running application program at this time, then the currently active application program (in the active state) is the music player app. If the user selects to run the music player app in the background and opens the navigation app, and the navigation app starts running, then there are two running application programs at this time. However, since the navigation app is running in the foreground and has a higher response level than the music player app, the currently active application program (in the active state) is the navigation app. Further, if a call comes in at this time and the incoming call app starts running, then there are three running application programs at this time. However, since the response level of the incoming call app is higher than the other two apps, the currently active application program (in the active state) is the incoming call app.

[0255] In the above example, when the currently active application program (phone call) is in the active state, other application programs that are in the active state (navigation app) are interrupted. At this time, if the currently active application program (phone call) is no longer in the active state (the call ends), then the currently active application program is re-determined as other application programs (navigation app), and the application scenario associated with the information presentation device is re-determined according to the above other application programs.

[0256] Further, in the human-machine interaction method for a vehicle according to an embodiment of the present application, the touch control module may include multiple touch control areas, and the cockpit domain may also be provided with multiple information presentation devices, and the multiple touch control areas correspond to the multiple information presentation devices one by one.

[0257] The human-machine interaction method in this case will be further described below.

[0258] In some embodiments, the cockpit domain controller may send the application scenarios associated with each information presentation device to the touch control module respectively.

[0259] In some embodiments, one of the multiple touch control areas may be set as the first touch control area, and the remaining touch control areas may be set as the second touch control areas. Then, a control permission of a second touch control area is assigned to the first touch control area, so that the first touch control area can perform touch control instead of this second touch control area. Specifically, in this embodiment, the cockpit domain controller may, in response to a detected trigger event, assign the control permission of this second touch control area to the first touch control area, so that when the first touch control area has the control permission, it can replace this second touch control area and control the first application program that is currently active and associated with the information presentation device corresponding to the second touch control area.

[0260] The above embodiments will be further described below.

[0261] In some embodiments, the cockpit domain controller may, in response to a detected trigger event, assign a separate control permission of a second touch control area to the first touch control area, so that when the first touch control area has the separate control permission, it can replace this second touch control area and control the above first application program, and pause the control of the second application program that is currently active and associated with the information presentation device corresponding to the first touch control area itself.

[0262] In some embodiments, after the cockpit domain controller assigns a separate control permission of a second touch control area to the first touch control area, it may also control the information presentation device corresponding to the first touch control area to synchronously present the above first application program.

[0263] In some embodiments, the cockpit domain controller may, in response to a detected trigger event, assign a combined control permission of a second touch control area to the first touch control area, so that when the first touch control area has the combined control permission, it can replace this second touch control area and control the above first application program, and simultaneously control the above second application program.

[0264] In the above implementation manners of separate and combined control authorities, the method of using the first touch area to control the first application program instead of the second touch area is the same as the relevant method in the above-mentioned human-machine interaction method with the touch module and the cockpit domain controller jointly as the execution entities, and will not be elaborated here. In addition, the method for the cockpit domain controller to detect trigger events is the same as the relevant method in the human-machine interaction method with the touch module and the cockpit domain controller jointly as the execution entities, and will not be elaborated here.

[0265] It should be noted that the function of the touch module in this embodiment is the same as that of the touch module in the above-mentioned human-machine interaction method with the touch module and the cockpit domain controller jointly as the execution entities, and will not be elaborated here. In addition, the technical effects of the touch module and the cockpit domain controller in different implementation manners in this embodiment are also the same as those in the above-mentioned human-machine interaction method with the touch module and the cockpit domain controller jointly as the execution entities, and will not be elaborated here either.

[0266] The above is the description of the embodiment of the human-machine interaction method implemented with the cockpit domain controller alone as the execution entity.

[0267] It should be pointed out that although the above steps are described in a specific order, those skilled in the art can understand that in order to achieve the effects of this application, different steps do not necessarily have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders. These adjusted solutions are equivalent technical solutions to the technical solutions described in this application, and thus will also fall within the protection scope of this application.

[0268] Those skilled in the art can understand that all or part of the processes in the method for implementing the above-mentioned embodiment of this application can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable storage medium can include: any entity or device, medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory, random access memory, electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals.

[0269] Another aspect of the present application further provides a touch control module.

[0270] In an embodiment of a touch control module according to the present application, the touch control module is disposed in the vehicle cockpit domain, and a cockpit domain controller and an information presentation device are also disposed in the cockpit domain. The touch control module is communicatively connected to the cockpit domain controller. The touch control module may include a touch area, at least one processor, and a memory communicatively connected to the at least one processor. A computer program is stored in the memory, and when the computer program is executed by the at least one processor, the method described in the method embodiment with the touch control module as the execution subject is implemented. Refer to the appendix Figure 8 , Figure 8 In which, it is exemplarily shown that the memory 11 and the processor 12 are communicatively connected through a bus.

[0271] In some embodiments, the touch control module includes a strip-shaped touch area, and the strip-shaped touch area is divided into a plurality of touch areas, and each touch area is arranged in sequence in the same direction on the strip-shaped touch area. As Figure 5 shown, the touch control module includes a strip-shaped touch area, and the strip-shaped touch area is divided into three touch areas 1, 2, and 3, and these three touch areas are arranged in sequence in the same direction on the strip-shaped touch area. Among them, each touch area is a rectangular touch area.

[0272] The strip-shaped touch area has the advantage of regular boundaries, based on which it is convenient to divide the touch areas. At the same time, each touch area is a rectangular touch area, which also has the advantage of regular boundaries, so that the range of gesture operations can be clearly defined, which is beneficial to accurately detecting the coordinates of gesture operations, and then identifying accurate gesture events.

[0273] Another aspect of the present application further provides a cockpit domain controller.

[0274] In an embodiment of a cockpit domain controller according to the present application, the cockpit domain controller is disposed in the vehicle cockpit domain, and a touch control module and an information presentation device are also disposed in the cockpit domain. The cockpit domain controller is communicatively connected to the touch control module, and the touch control module includes a touch area. The cockpit domain controller may include at least one processor and a memory communicatively connected to the at least one processor. A computer program is stored in the memory, and when the computer program is executed by the at least one processor, the method described in the method embodiment with the cockpit domain controller as the execution subject is implemented. Refer to the appendix Figure 9 , Figure 9 In which, it is exemplarily shown that the memory 21 and the processor 22 are communicatively connected through a bus.

[0275] Another aspect of the present application further provides a human-machine interaction system for a vehicle.

[0276] In an embodiment of a human-machine interaction system for a vehicle according to the present application, an information presentation device is provided in the cockpit domain of the vehicle. Meanwhile, the system may include the touch control module described in the above touch control module embodiment, and the cockpit domain controller described in the cockpit domain controller.

[0277] Another aspect of the present application also provides a vehicle.

[0278] In an embodiment of a vehicle according to the present application, an information presentation device is provided in the cockpit domain of the vehicle. The vehicle also includes the human-machine interaction system for a vehicle described in the above system embodiment. In this embodiment, the vehicle may be an autonomous vehicle, a driverless vehicle, or other types of vehicles. In addition, classified by the type of power source, the vehicle in this embodiment may be a fuel vehicle, an electric vehicle, a hybrid vehicle with electric power and fuel, or a vehicle using other new energy sources, etc.

[0279] Another aspect of the present application also provides a computer-readable storage medium.

[0280] In an embodiment of a computer-readable storage medium according to the present application, the computer-readable storage medium may be configured to store a program for executing the method described in the above method embodiment with the touch control module as the execution subject. This program can be loaded and run by a processor to implement the above method. For the sake of convenience of description, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present application. The computer-readable storage medium may be a storage device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiments of the present application is a non-transitory computer-readable storage medium.

[0281] Another aspect of the present application also provides a computer-readable storage medium.

[0282] In an embodiment of a computer-readable storage medium according to the present application, the computer-readable storage medium may be configured to store a program for executing the method described in the above method embodiment with the cockpit domain controller as the execution subject. This program can be loaded and run by a processor to implement the above method. For the sake of convenience of description, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present application. The computer-readable storage medium may be a storage device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiments of the present application is a non-transitory computer-readable storage medium.

[0283] So far, the technical solution of the present application has been described in conjunction with an embodiment shown in the accompanying drawings. However, those skilled in the art can easily understand that the protection scope of the present application is obviously not limited to these specific embodiments. Without departing from the principle of the present application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present application.

Claims

1. A human-machine interaction method for a vehicle, characterized in that, The method is applied to a touch module disposed in a vehicle cockpit domain, and a cockpit domain controller and an information presentation device are also disposed in the cockpit domain. The method includes: The touch module receives an application scenario associated with the information presentation device sent by the cockpit domain controller; Under the application scenario, the touch module recognizes a gesture event of a user's gesture operation in a touch area of the touch module, and sends the gesture event to the cockpit domain controller, so that the cockpit domain controller obtains a control operation matching the gesture event under the application scenario, and presents an operation result of the control operation on the information presentation device; Wherein, The application scenario associated with the information presentation device is an application scenario corresponding to an application program associated with the information presentation device and currently active.

2. The method according to claim 1, characterized in that, The gesture event includes at least a gesture type, and the method further includes: Under the application scenario, the touch module obtains a vibration mode matching the gesture type in the gesture event, and controls the touch area to vibrate according to the vibration mode.

3. The method according to claim 1, characterized in that, The touch module includes a plurality of touch areas, and a plurality of information presentation devices are disposed in the cockpit domain, and the plurality of touch areas correspond to the plurality of information presentation devices one by one; The touch module receives the application scenario associated with the information presentation device sent by the cockpit domain controller, including: Receiving respectively the application scenarios associated with the information presentation devices corresponding to each touch area sent by the cockpit domain controller.

4. The method according to claim 3, characterized in that, One touch area among the plurality of touch areas is set as a first touch area, and the remaining touch areas are set as second touch areas; The method further includes: When the first touch area has the control authority over one of the second touch areas, the first touch area replaces the second touch area to control a first application program associated with the information presentation device corresponding to the second touch area and currently active.

5. The method according to claim 4, characterized in that, The control authority of the second touch area includes a separate control authority, and the method further includes: When the first touch area has the separate control authority, the first touch area replaces the second touch area to control the first application program, and The first touch area suspends controlling a second application program associated with the information presentation device corresponding to the first touch area itself and currently active.

6. The method according to claim 4, characterized in that, The control authority of the second touch area includes a combined control authority, and the method further includes: When the first touch area has the combined control authority, the first touch area replaces the second touch area to control the first application program, and The first touch area simultaneously controls a second application program associated with the information presentation device corresponding to the first touch area itself and currently active.

7. The method according to any one of claims 4 to 6, characterized in that, The first touch area replaces the second touch area to control the first application program associated with the information presentation device corresponding to the second touch area and currently active, including: Regarding the information presentation device corresponding to the second touch area as a target device; Receiving the application scenario associated with the target device sent by the cockpit domain controller; In the described application scenario, gesture events of a user's gesture operations in the first touch area are recognized and sent to the cockpit domain controller, so that the cockpit domain controller obtains control operations matching the gesture events in the application scenario and presents the operation results of the control operations on the target device.

8. A human-machine interaction method for a vehicle, characterized in that, The method is applied to a cockpit domain controller provided in a vehicle cockpit domain. The cockpit domain is also provided with a touch module and an information presentation device. The method includes: The cockpit domain controller sends an application scenario associated with the information presentation device to the touch module, so that the touch module can recognize gesture events of a user's gesture operations in the touch area of the touch module in the application scenario and send the gesture events to the cockpit domain controller; The cockpit domain controller obtains control operations matching the gesture events in the application scenario and presents the operation results of the control operations on the information presentation device; Wherein, The application scenario associated with the information presentation device is the application scenario corresponding to the currently active application associated with the information presentation device.

9. The method according to claim 8, characterized in that, The method further includes: After the currently active application is no longer in the active state, the cockpit domain controller determines whether other applications that were in the active state were interrupted before the currently active application was in the active state; If so, re-determine the application scenario associated with the information presentation device according to the other applications and send the application scenario to the touch area.

10. According to the method of claim 8, wherein The touch module includes a plurality of touch areas, and the cockpit domain is provided with a plurality of information presentation devices. The plurality of touch areas correspond to the plurality of information presentation devices one by one; The method further includes: The cockpit domain controller sends the application scenarios associated with each information presentation device to the touch module respectively.

Images