Virtual keyboard display method, controller and vehicle

Abstract

The application provides a virtual keyboard display method, a controller and a vehicle, and relates to the technical field of intelligent cockpits. The method comprises the following steps: when a keyboard display instruction is acquired, acquiring running data of the vehicle; obtaining a running risk level of the vehicle according to the running data; determining a keyboard display strategy based on the running risk level; wherein the keyboard display strategy comprises a function area of a virtual keyboard to be displayed, and the number of the function area is negatively correlated with the running risk level; and generating and displaying the virtual keyboard according to the keyboard display strategy. According to the application, the function area of the virtual keyboard to be displayed is determined based on the running risk level of the vehicle and the principle that the number of the function area is negatively correlated with the running risk level, the function of the virtual keyboard is dynamically adjusted according to the running risk of the vehicle, the driving distraction risk is reduced while the input availability of the virtual keyboard is ensured, and finally the balance between driving safety and interaction efficiency is achieved.

Description

Technical Field

[0001] This application relates to the field of smart cockpit technology, and in particular to a virtual keyboard display method, controller and vehicle. Background Technology

[0002] With the development of smart cockpit technology, the convenience of in-vehicle human-machine interaction is constantly improving. As a core input component for in-vehicle interaction, the vehicle virtual keyboard is usually displayed on in-vehicle display devices such as the central control screen, covering in-vehicle input needs in scenarios such as navigation, multimedia, vehicle settings, and communication, effectively improving the flexibility and efficiency of human-machine interaction.

[0003] In related technologies, virtual keyboards are typically presented in the form of a full keyboard, such as using the full-key layout of mobile phones and tablets. However, this presentation method forces drivers to divert their attention to perform precise touch operations on the virtual keyboard, leading to an imbalance between driving safety and interaction efficiency, and increasing driving safety risks. Summary of the Invention

[0004] This application provides a virtual keyboard display method, controller, and vehicle to solve the technical problem in the related art where the presentation of virtual keyboards forces drivers to distract themselves from precise touch operations, thus leading to an imbalance between driving safety and interaction efficiency.

[0005] In a first aspect, embodiments of this application provide a virtual keyboard display method, including: Upon receiving a keyboard display command, acquire the vehicle's operating data; Based on the operational data, the operational risk level of the vehicle is obtained; Based on the operational risk level, a keyboard display strategy is determined; wherein, the keyboard display strategy includes the functional areas of the virtual keyboard to be displayed, and the number of functional areas is negatively correlated with the operational risk level; The virtual keyboard is generated and displayed according to the keyboard display strategy.

[0006] In this embodiment of the application, when a virtual keyboard needs to be displayed, i.e., when a user has a need to use a virtual keyboard, the vehicle's operational risk level is first accurately determined based on the vehicle's operating data. This determines the level of driver attention required and provides a valid basis for accurately determining the functional configuration of the virtual keyboard to be displayed. Then, based on the vehicle's operational risk level, a corresponding keyboard display strategy is matched, i.e., the functional areas of the virtual keyboard to be displayed are determined. The number of functional areas is negatively correlated with the operational risk level. Subsequently, according to the above keyboard display strategy, a virtual keyboard is generated and displayed for the user to perform in-vehicle human-machine interaction. In this way, by determining the functional areas of the virtual keyboard to be displayed based on the vehicle's operational risk level and the principle that the number of functional areas is negatively correlated with the operational risk level, it is possible to simplify the functions of the virtual keyboard in scenarios with high vehicle operational risk and high demands on driver attention, thereby reducing driver touch operations and distraction and improving driving safety. In scenarios with low vehicle operational risk and low demands on driver attention, more functions of the virtual keyboard are retained, thereby improving the input usability of the virtual keyboard while ensuring safety. This achieves dynamic adjustment of the virtual keyboard's functions according to the vehicle's operational risk, reducing the risk of driver distraction while ensuring the usability of virtual keyboard input, and ultimately achieving a balance between driving safety and interaction efficiency.

[0007] In one possible implementation, the operational data includes the vehicle's speed, position, operating status, and gear. The step of obtaining the vehicle's operational risk level based on the operational data includes: The driving task type of the vehicle is determined based on at least one of the vehicle's speed, position, operating status, and gear position. Based on the driving task type, the operational risk level of the vehicle is obtained.

[0008] In this embodiment, by relying on operational data that can characterize the actual state of the vehicle, the current driving task type can be accurately identified, providing effective support for the accurate and reasonable determination of the subsequent operational risk level. At the same time, the introduction of driving task type as an intermediate layer upgrades the determination of operational risk level to a scenario-based comprehensive determination, effectively avoiding the one-sided problem that can easily occur when determining the operational risk level directly from a single piece of operational data.

[0009] In one possible implementation, determining the driving task type of the vehicle based on at least one of the vehicle's speed, position, operating status, and gear position includes: If the vehicle speed exceeds a first preset speed threshold within a preset time period, then the driving task type is determined to be a high-speed cruise task; or, If the operating state is a frequent start-stop state, then the driving task type is determined to be a congested driving task; or, If the location is less than a preset distance threshold from a preset location, then the driving task type is determined to be a navigation guidance task; the navigation guidance task includes turning, as well as entering and exiting ramps; or, If the operating state is automatic parking and the vehicle speed is less than a second preset speed threshold, then the driving task type is determined to be an automatic parking task; or, If the gear is in the parking position, then the driving task type is determined to be a parking task.

[0010] Here, based on the core characteristics of different driving task types, different operational data such as vehicle speed, position, working status, and gear are selected as the basis for judgment, which is adapted to the actual working conditions of each driving task type. Furthermore, multiple operational data combinations can be used for judgment, thereby accurately determining the driving task type of the vehicle and providing an effective basis for obtaining the vehicle's operational risk level in the future.

[0011] In one possible implementation, obtaining the vehicle's operational risk level based on the driving task type includes: If the vehicle has multiple driving task types, the operational risk level corresponding to each driving task type is determined based on the pre-stored correspondence between the vehicle's operational risk level and the driving task type. Based on the operational risk level corresponding to each driving task type, the highest operational risk level is obtained, and the highest operational risk level is taken as the operational risk level of the vehicle.

[0012] In this embodiment, by utilizing the pre-stored correspondence between vehicle operational risk levels and driving task types, the corresponding operational risk level can be directly matched after the driving task type is determined, adapting to the real-time requirements of in-vehicle human-machine interaction. Furthermore, when a vehicle triggers multiple driving task types simultaneously, the highest operational risk level is taken as the final level, achieving a risk safety net, preventing risk omissions, and maximizing driving safety.

[0013] In one possible implementation, determining the keyboard display strategy based on the operational risk level includes: Based on the operational risk level, rules for reducing the pre-stored complete virtual keyboard are determined; wherein, the reduction rules include reducing the functional areas of the complete virtual keyboard, and the number of functional areas to be reduced is positively correlated with the operational risk level; The keyboard display strategy is obtained based on the reduction rules.

[0014] In this embodiment, based on the principle that the number of functional areas to be removed is positively correlated with the level of operational risk, the operational risk level of the vehicle is used as the basis for determining the rules for removing the complete virtual keyboard. This links the keyboard display strategy with the actual operational risk of the vehicle, abandons the fixed presentation of the complete keyboard, and enables the virtual keyboard to dynamically adjust its functions according to the operational risk of the vehicle, thereby achieving a balance between driving safety and interaction efficiency.

[0015] In one possible implementation, the operational risk level includes a high-risk level, a medium-risk level, and a low-risk level; The rules for reducing the number of pre-stored complete virtual keyboards based on the operational risk level include: If the operational risk level is high risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area are deleted. If the operational risk level is medium risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area, letter key area, number area, basic symbol area and basic function control area are deleted. If the operational risk level is low risk, then the deletion rule is determined as follows: the functional area of ​​the complete virtual keyboard will not be deleted.

[0016] Here, based on the principle that the number of functional areas to be removed is positively correlated with the level of operational risk, the functions of the complete virtual keyboard are removed in a step-by-step manner. At medium to high operational risk, the core functional areas are retained without affecting basic human-computer interaction. This achieves the interaction logic of less interaction at high operational risk, moderate interaction at medium operational risk, and more / full interaction at low operational risk, thus balancing driving safety and interaction efficiency.

[0017] In one possible implementation, the keyboard display strategy also includes the size of the virtual keyboard to be displayed; Before obtaining the keyboard display strategy based on the reduction rules, the method further includes: Based on the operational risk level, the size of the virtual keyboard to be displayed is determined; wherein, the size of the virtual keyboard to be displayed is positively correlated with the operational risk level; The step of obtaining the keyboard display strategy based on the deletion rules includes: Based on the reduction rules and the size of the virtual keyboard to be displayed, the keyboard display strategy is obtained.

[0018] Here, based on the principle that the size of the virtual keyboard to be displayed is positively correlated with the level of operational risk, the size of the virtual keyboard is set so that under medium and high risk levels, the visual proportion of the virtual keyboard is higher and more eye-catching, so that the driver can quickly identify it without deliberately focusing, reducing visual search and dwell time.

[0019] In one possible implementation, determining the size of the virtual keyboard to be displayed based on the operational risk level includes: If the operational risk level is low risk, then the size of each key in the virtual keyboard to be displayed is determined to be the size of the corresponding key in the complete virtual keyboard; If the operational risk level is medium risk, then the size of each key in the virtual keyboard to be displayed is determined to be a preset multiple of the size of the corresponding key in the complete virtual keyboard.

[0020] In this embodiment, when the vehicle's operational risk level is medium risk, the size of each keyboard in the virtual keyboard to be displayed is enlarged so that the driver can quickly identify them without having to focus, thereby ensuring the driver's ease of operation of the virtual keyboard.

[0021] Secondly, embodiments of this application provide a virtual keyboard display device, comprising: The acquisition module is used to acquire vehicle operating data when a keyboard display command is received.

[0022] The module is used to obtain the operational risk level of the vehicle based on the operational data.

[0023] The determination module is used to determine a keyboard display strategy based on the operational risk level; wherein the keyboard display strategy includes functional areas of the virtual keyboard to be displayed, and the number of functional areas is negatively correlated with the operational risk level.

[0024] The display module is used to generate and display the virtual keyboard according to the keyboard display strategy.

[0025] Thirdly, embodiments of this application provide a controller, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the virtual keyboard display method as described in any of the first aspects.

[0026] Fourthly, embodiments of this application provide a vehicle including the controller described in the third aspect.

[0027] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the virtual keyboard display method as described in any of the first aspects.

[0028] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here.

[0029] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application; Figure 2 This is a flowchart illustrating a virtual keyboard display method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating a virtual keyboard display method provided in another embodiment of this application; Figure 4 This is a schematic diagram of the structure of a virtual keyboard display device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the controller provided in one embodiment of this application. Detailed Implementation

[0032] The present application will be described more clearly below with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the function of the present application, but do not limit the present application in any way. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application. These all fall within the protection scope of the present application.

[0033] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0034] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0035] In the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0036] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0037] Furthermore, the term "multiple" mentioned in the embodiments of this application should be interpreted as two or more.

[0038] As a core input component for in-vehicle interaction, the virtual keyboard is typically displayed on in-vehicle displays such as the central control screen. It adapts to various in-vehicle input needs, including navigation, multimedia, vehicle settings, and communication. For example, users can input driving destinations or song titles using the virtual keyboard. The virtual keyboard often adopts the full-button layout of mobile phones and tablets, providing users with in-vehicle input interaction services in a complete keyboard format.

[0039] The aforementioned virtual keyboard with full physical buttons ensures effective input availability, but requires precise touch operation from the driver, which can distract the driver's attention. In scenarios requiring high driver focus, if the driver devotes too much attention to operating the virtual keyboard, it will increase driving safety risks, create an imbalance between driving safety and interaction efficiency, and even lead to accidents.

[0040] Based on the aforementioned problems, the inventors considered that since operating a virtual keyboard with multiple characters and a dense layout can distract the driver excessively, and the driver's attention requirements vary significantly depending on the vehicle's operating state, simplifying the virtual keyboard's functionality to retain only its basic functions in scenarios with high driver attention requirements would reduce driver touch operations, preventing excessive distraction from operating the virtual keyboard, thus improving driving safety while ensuring the basic usability of the virtual keyboard's input. Conversely, retaining the full functionality of the virtual keyboard in scenarios with low driver attention requirements would improve input usability without compromising safety. This achieves a dynamic adjustment of the virtual keyboard's functionality according to the level of driver attention required, thereby achieving a balance between driving safety and interaction efficiency.

[0041] The inventors continued their thinking, realizing that the level of driver attention required can be determined based on the vehicle's operational risks. Higher operational risks naturally require higher driver attention, and vice versa. Therefore, the operational risks of a vehicle can be determined based on its operational data, thus revealing the level of driver attention required.

[0042] In other words, in the embodiments of this application, when a virtual keyboard needs to be displayed, that is, when a user has a need to use a virtual keyboard, the vehicle's operational risk level is first accurately obtained based on the vehicle's operating data, which corresponds to determining the level of driver attention required. This provides a valid basis for accurately determining the functional configuration of the virtual keyboard to be displayed. Then, based on the vehicle's operational risk level, a corresponding keyboard display strategy is matched, that is, the functional areas of the virtual keyboard to be displayed are determined, and the number of functional areas is negatively correlated with the operational risk level. Subsequently, according to the above keyboard display strategy, a virtual keyboard is generated and displayed for the user to perform in-vehicle human-machine interaction.

[0043] In this way, by determining the functional areas of the virtual keyboard to be displayed based on the vehicle's operational risk level and the principle that the number of functional areas is negatively correlated with the operational risk level, it is possible to simplify the functions of the virtual keyboard in scenarios with high vehicle operational risk and high demands on driver attention, thereby reducing driver touch operations and distraction and improving driving safety. In scenarios with low vehicle operational risk and low demands on driver attention, more functions of the virtual keyboard are retained, thereby improving the input usability of the virtual keyboard while ensuring safety. This achieves dynamic adjustment of the virtual keyboard's functions according to the vehicle's operational risk, reducing the risk of driver distraction while ensuring the usability of virtual keyboard input, and ultimately achieving a balance between driving safety and interaction efficiency.

[0044] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0045] First refer to Figure 1 , Figure 1 The illustration shows an application scenario diagram provided according to the embodiments of this application. The equipment involved in the application scenario may include: controller, vehicle display terminal such as central control screen, etc.

[0046] When the controller receives a keyboard display command, it acquires the vehicle's operating data, then determines the vehicle's operating risk level based on the operating risk level, and determines the keyboard display strategy for the functional area of ​​the virtual keyboard to be displayed. After that, the virtual keyboard is generated and displayed on the central control screen according to the keyboard display strategy, so that the virtual keyboard has the corresponding functions.

[0047] Optionally, the aforementioned controller can be an in-vehicle controller, an external controller, or a combination of both. It is a hardware device with data storage, processing, and analysis functions. Taking an in-vehicle controller as an example, it can be an Electronic Control Unit (ECU), etc.

[0048] For example, this application scenario may also include speed sensors, in-vehicle navigation systems, etc., to collect relevant vehicle data, so that the controller can obtain the vehicle's operating data based on the aforementioned relevant data, and thus determine the vehicle's operating risk level, etc.

[0049] The following is combined with Figure 1 Application scenarios, refer to Figures 2-3 This application describes a virtual keyboard display method provided according to exemplary embodiments. It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way. Rather, the embodiments of this application can be applied to any applicable scenario.

[0050] refer to Figure 2 , Figure 2 This is a flowchart illustrating a virtual keyboard display method provided in an embodiment of this application. Figure 2 As shown, the method in the embodiments of this application may include: Step 201: When a keyboard display command is received, acquire the vehicle's operating data.

[0051] In real-world scenarios, when users need to use the virtual keyboard, they can issue voice commands, or touch the relevant buttons or input boxes displayed on the central control screen. In other words, keyboard display commands can be voice commands, such as opening the virtual keyboard, or touch commands such as clicking the virtual keyboard activation button on the central control screen, or touch commands such as clicking the relevant input boxes displayed on the central control screen.

[0052] Step 202: Based on the operational data, obtain the vehicle's operational risk level.

[0053] Here, vehicle operation data can include vehicle speed, location, and operating status. Operating status refers to the vehicle's driving and operational conditions, such as automatic parking status. Operational risk levels can be categorized as high-risk, medium-risk, and low-risk. High-risk levels correspond to high driver attention requirements, low-risk levels to low driver attention requirements, and medium-risk levels to driver attention requirements between high and low.

[0054] Based on vehicle operating data, the vehicle's operational risk level can be determined. For example, when the vehicle speed exceeds a certain value, the window for responding to sudden road conditions is significantly shortened due to the excessive speed, and the vehicle's braking distance increases significantly. In this case, the vehicle's operational risk level is considered high-risk, and the driver needs to maintain a high level of attention to quickly assess road conditions and operate the vehicle precisely. When the vehicle's position indicates that it is turning or about to turn, the operational risk level is considered medium-risk because the vehicle needs to adjust its direction during a turn, and blind spots may exist in the turning section. The driver needs to concentrate. When the vehicle is in automatic parking mode, the parking system takes over and completes automatic parking. The driving range is limited, and there is no complex traffic flow. In this scenario, the vehicle's operational risk level is considered low-risk. The driver does not need to manually operate the vehicle and only needs to focus on the parking process.

[0055] It should be noted that the above operational data may determine multiple operational risk levels for a vehicle. In this case, for the purpose of prioritizing driving safety, the highest operational risk level will be used as the final operational risk level for the vehicle.

[0056] Step 203: Determine the keyboard display strategy based on the operational risk level; wherein, the keyboard display strategy includes the functional areas of the virtual keyboard to be displayed, and the number of functional areas is negatively correlated with the operational risk level.

[0057] For example, a complete virtual keyboard typically follows the full-key layout of mobile phones, tablets, etc. The functional areas may include letter key areas, pinyin key areas, handwriting areas, input switching areas, as well as voice input prompt areas, number areas, basic symbol areas, symbol switching areas, complete symbol areas, basic function control areas, function switching areas, complete function control areas, emoji areas, emoji switching areas, etc. For details, please refer to the soft keyboards of mobile phones and tablets, which will not be elaborated here.

[0058] The keyboard layout includes: a letter key area with 26 English letters, a Chinese / English toggle key, and a case toggle key; a pinyin key area with 9 pinyin combination keys, a Chinese / English toggle key, and a case toggle key; a voice input prompt area to indicate that voice input is now active; a number area with 10 number keys; a basic symbol area with commonly used symbol keys such as comma, period, question mark, and exclamation mark, and a complete symbol area with commonly used symbol keys as well as special symbol keys such as parentheses and quotation marks; a basic function control area with commonly used function keys such as delete, space, and confirm, and a complete function control area with commonly used function keys as well as special function keys such as shortcut key; and an emoji area with multiple emoji keys.

[0059] The input switching area, symbol switching area, function switching area, and emoji switching area are actually shortcut keys. These keys allow you to switch to the corresponding function area with a single click. For example, a typical virtual keyboard display includes an input area such as the letter keys, a basic symbol area, a basic function control area, and the aforementioned shortcut keys. Using the input switching area, you can choose to switch to the pinyin key area or the handwriting area. Other shortcut keys function similarly and will not be described in detail here.

[0060] It should be noted that the functional areas included in the complete virtual keyboard described above are only examples. In reality, the functional areas and corresponding functions included in a complete virtual keyboard can be flexibly configured according to actual usage scenarios and needs, and are not limited to the functional areas and corresponding functions shown above.

[0061] In this embodiment, after determining the vehicle's operational risk level, to achieve a balance between driving safety and interaction efficiency, a keyboard display strategy is determined based on the principle that the number of functional areas is negatively correlated with the operational risk level. That is, the higher the operational risk level, the fewer functional areas of the virtual keyboard to be displayed in the determined keyboard display strategy. This reduces the driver's touch operation on the virtual keyboard when the vehicle's operational risk level is high, avoids the driver being distracted too much by operating the virtual keyboard, and improves driving safety. When the vehicle's operational risk level is low, more functions of the virtual keyboard are retained, which can improve the input usability of the virtual keyboard without affecting safety.

[0062] In some embodiments, a corresponding keyboard display strategy can be determined based on the vehicle's operational risk level and the preset correspondence between the keyboard display strategy and the operational risk level. The preset correspondence between the keyboard display strategy and the operational risk level is set based on the principle that the number of functional areas is negatively correlated with the operational risk level.

[0063] For example, when the risk level is high, the corresponding keyboard display strategy can be to include only the voice input prompt area. In other words, the virtual keyboard only supports user voice input and disables other functional areas that require user touch operation. By appropriately reducing interaction efficiency, driving safety can be ensured to the greatest extent.

[0064] Here, the controller generates and displays a virtual keyboard while activating the voice input function. The virtual keyboard supports user voice input, and the voice input prompt area of ​​the virtual keyboard is only used to prompt the user that voice input is available at this time, without requiring the user to manually touch the screen.

[0065] When the risk level is medium, the corresponding keyboard display strategy can be to include only the letter key area, number area, and basic function control area. In other words, the virtual keyboard only retains basic functions and only supports simple touch operations by the user, while disabling the handwriting area, shortcut switching keys, full symbol area and other functional areas that require more user attention.

[0066] When the risk level is low, the corresponding keyboard display strategy can include all functional areas, meaning the virtual keyboard retains full functionality, improving the input usability of the virtual keyboard without compromising security.

[0067] It should be noted that, under high and medium operational risk levels, the keyboard display strategy includes a small number of virtual keyboard function areas to be displayed, but these areas are sufficient to meet the basic usage requirements of in-vehicle human-machine interaction.

[0068] Step 204: Generate and display a virtual keyboard according to the keyboard display strategy.

[0069] After determining the keyboard display strategy, a corresponding virtual keyboard is generated and displayed on the central control screen based on the keyboard display strategy. At the same time, corresponding functional attributes are configured for each functional area included in the virtual keyboard, so that the virtual keyboard has corresponding functions, thereby enabling users to realize in-vehicle human-machine interaction based on the virtual keyboard.

[0070] The virtual keyboard display method provided in this application embodiment, when a virtual keyboard needs to be displayed, i.e., when a user has a need to use a virtual keyboard, firstly, accurately obtains the vehicle's operational risk level based on the vehicle's operating data, which corresponds to determining the level of driver attention required. This provides a valid basis for accurately determining the functional configuration of the virtual keyboard to be displayed. Then, based on the vehicle's operational risk level, a corresponding keyboard display strategy is matched, i.e., the functional areas of the virtual keyboard to be displayed are determined, and the number of functional areas is negatively correlated with the operational risk level. Subsequently, according to the above keyboard display strategy, a virtual keyboard is generated and displayed for the user to perform in-vehicle human-machine interaction. In this way, by determining the functional areas of the virtual keyboard to be displayed based on the vehicle's operational risk level and the principle that the number of functional areas is negatively correlated with the operational risk level, it is possible to simplify the functions of the virtual keyboard in scenarios with high vehicle operational risk and high demands on driver attention, thereby reducing driver touch operations and distraction and improving driving safety. In scenarios with low vehicle operational risk and low demands on driver attention, more functions of the virtual keyboard are retained, thereby improving the input usability of the virtual keyboard while ensuring safety. This achieves dynamic adjustment of the virtual keyboard's functions according to the vehicle's operational risk, reducing the risk of driver distraction while ensuring the usability of virtual keyboard input, and ultimately achieving a balance between driving safety and interaction efficiency.

[0071] Furthermore, this application also considers determining the operational risk level based on the type of driving task of the vehicle, in order to obtain the vehicle's operational risk more accurately. Additionally, it also considers determining the keyboard display strategy based on deletion rules, in order to more accurately determine the functional areas of the virtual keyboard to be displayed.

[0072] Figure 3 This is a flowchart illustrating a virtual keyboard display method provided in another embodiment of this application. Figure 3 As shown, the method in the embodiments of this application may include: Step 301: When a keyboard display command is received, obtain the vehicle's speed, position, operating status, and gear.

[0073] For example, the keyboard display command can be a voice command issued by the user, such as opening the virtual keyboard, or a touch operation command for the user to click the virtual keyboard on the central control screen, or a touch operation command for the user to click the relevant input box displayed on the central control screen.

[0074] Step 302: Determine the driving task type of the vehicle based on at least one of the vehicle's speed, position, working status, and gear, and obtain the vehicle's operational risk level based on the driving task type.

[0075] Among these, "location" indicates the vehicle's current location, which can be obtained through the in-vehicle navigation system. "Operating status" indicates the vehicle's driving and operating conditions, such as automatic parking. "Driving task type" can include highway cruising, traffic jam driving, navigation guidance, automatic parking, and parking tasks.

[0076] In this embodiment, by relying on operational data that can characterize the actual state of the vehicle, the current driving task type of the vehicle can be accurately identified, providing effective support for the accurate and reasonable determination of the subsequent operational risk level. At the same time, the introduction of driving task type as an intermediate layer upgrades the determination of operational risk level to a scenario-based comprehensive determination, effectively avoiding the one-sided problem that can easily occur when determining the operational risk level directly from a single piece of operational data.

[0077] In some embodiments, determining the type of driving task for a vehicle may include: If the vehicle speed exceeds a first preset speed threshold within a preset time period, the driving task type is determined to be a high-speed cruise task, or... If the operating status is frequent start-stop, then the driving task type is determined to be a traffic jam driving task, or... If the location is less than a preset distance threshold from a preset location, then the driving task type is determined to be a navigation guidance task; navigation guidance tasks include turning, as well as merging and exiting ramp tasks, or... If the operating status is automatic parking and the vehicle speed is less than the second preset speed threshold, then the driving task type is determined to be an automatic parking task, or... If the gear is in the parking position, then the driving task type is determined to be a parking task.

[0078] For example, the first preset speed threshold can be 40 km / h, and the preset time period is a historical time period, which can be 1 minute or 30 seconds before the current moment. If the vehicle speed is greater than 40 km / h within the preset time period, it is considered that the vehicle speed is continuously too high, and the driving task type is determined to be a high-speed cruise task. Here, the first preset speed threshold and the preset time period can be set according to the actual scenario and needs.

[0079] If the vehicle's operating state is one of frequent starts and stops, the driving task type is determined to be a congested driving task. For example, if the vehicle's speed changes from 0 to a value greater than a third preset speed threshold within a first time period, and this happens repeatedly a preset number of times, then the vehicle's operating state is considered to be one of frequent starts and stops. The first time period is a historical time period, such as the two minutes preceding the current moment. The third preset speed threshold can be determined based on the average vehicle speed during congested driving scenarios, for example, it could be 5 km / h.

[0080] When an in-vehicle navigation system provides navigation, it obtains the vehicle's navigation path and location. If the vehicle's location is less than a preset distance threshold (e.g., intersections, ramp entrances, ramp exits on the navigation path), it can be assumed the vehicle will turn or enter / exit a ramp, thus classifying the driving task as a navigation guidance task. The preset distance can be set according to the actual scenario and needs, such as 500 meters or 100 meters.

[0081] If the vehicle is in automatic parking mode and its speed is less than a second preset speed threshold, the driving task type is determined to be an automatic parking task. The second preset speed threshold can be determined based on the average speed of different vehicles during automatic parking. If the vehicle is in park, the driving task type is determined to be a parking task.

[0082] In addition, if the vehicle speed is less than the first preset speed threshold within a preset time period, it is considered that the vehicle speed is continuously low, and the driving task type is determined to be an urban driving task.

[0083] It should be noted that the classification and determination of driving task types are not limited to the examples above. In practical applications, different driving task types and determination methods can be obtained based on the real-world scenarios and requirements.

[0084] In this embodiment, different operational data such as vehicle speed, position, working status, and gear are selected as the basis for judgment based on the core characteristics of different driving task types. This adapts to the actual working conditions of each driving task type and allows for the use of multiple operational data combinations for judgment. This enables accurate determination of the vehicle's driving task type and provides a valid basis for obtaining the vehicle's operational risk level.

[0085] In some embodiments, when the vehicle's operational risk level is obtained based on the driving task type, the vehicle's operational risk level can be determined according to the pre-stored correspondence between the vehicle's operational risk level and the driving task type.

[0086] For high-speed cruising missions, due to the excessive speed, the window for responding to sudden road conditions is significantly shortened, and the vehicle's braking distance is significantly increased. Therefore, the vehicle's operational risk level is considered high. For congested driving missions, the vehicle is in a densely populated traffic environment, requiring the driver to frequently perform braking, starting, and following maneuvers. The probability of sudden traffic conflicts such as following too closely or cutting in is high. Therefore, the vehicle's operational risk level is considered medium. For navigation guidance missions, the vehicle needs to adjust its trajectory at key nodes along the navigation path, increasing the potential risks of road traffic. Therefore, the vehicle's operational risk level is considered medium.

[0087] For automated parking tasks, the vehicle is automatically parked by the parking system, the driving range is limited, and there is no complex traffic flow. Therefore, the vehicle's operational risk level is considered low. For parking tasks, the vehicle is stationary and has no interaction with surrounding road traffic or the traffic environment. Therefore, the vehicle's operational risk level is considered low. For urban driving tasks, the vehicle speed is consistently low, but there are many traffic interference factors, posing potential risks such as scrapes and unavoidable collisions. Therefore, the vehicle's operational risk level is considered medium.

[0088] The pre-stored correspondence between vehicle operational risk levels and driving task types includes: high-risk level for highway cruising tasks, medium-risk level for congested driving tasks, navigation guidance tasks, and city driving tasks, and low-risk level for automatic parking tasks and parking tasks. Based on the vehicle's driving task type and the above correspondence, the vehicle's operational risk level can be accurately determined.

[0089] In some embodiments, when there are multiple driving task types for a vehicle, the operational risk level corresponding to each driving task type is determined based on the pre-stored correspondence between the vehicle's operational risk level and the driving task type. Based on the operational risk level corresponding to each driving task type, the highest operational risk level is obtained and used as the vehicle's operational risk level.

[0090] When there are multiple identified driving task types, the highest operational risk level is used as the final operational risk level of the vehicle to prioritize driving safety.

[0091] In this embodiment, by utilizing the pre-stored correspondence between vehicle operational risk levels and driving task types, the corresponding operational risk level can be directly matched after the driving task type is determined, thus meeting the real-time requirements of in-vehicle human-machine interaction. Furthermore, when a vehicle triggers multiple driving task types simultaneously, the highest operational risk level is taken as the final level, ensuring a safety net against potential risks and maximizing driving safety.

[0092] Step 303: Based on the operational risk level, determine the rules for reducing the pre-stored complete virtual keyboard, and obtain the keyboard display strategy according to the reduction rules.

[0093] The reduction rules include the removal of functional areas from the complete virtual keyboard; the number of functional areas removed is positively correlated with the operational risk level. The keyboard display strategy includes the functional areas of the virtual keyboard to be displayed; the number of functional areas is negatively correlated with the operational risk level.

[0094] This embodiment uses a reduction rule to reduce the functionality of the complete virtual keyboard, resulting in a keyboard display strategy that includes the functional areas of the virtual keyboard to be displayed. Furthermore, the higher the vehicle's operational risk level, the more functional areas of the complete virtual keyboard are reduced in the determined reduction rule, thus reducing the number of functional areas of the virtual keyboard to be displayed. Therefore, when the vehicle's operational risk level is high, the fewer functional areas of the virtual keyboard reduce the driver's touch operations on the virtual keyboard, avoiding excessive driver attention and improving driving safety. When the vehicle's operational risk level is low, more functions of the virtual keyboard are retained, improving input usability without compromising safety. This achieves a balance between driving safety and interaction efficiency.

[0095] In addition, it should be noted that the removal of functional areas of the complete virtual keyboard in the removal rules refers to the removal of non-core functional areas that do not affect the basic use of the virtual keyboard, while retaining core functional areas that can meet the basic usage requirements of in-vehicle human-machine interaction.

[0096] In this embodiment, based on the principle that the number of functional areas to be removed is positively correlated with the level of operational risk, the operational risk level of the vehicle is used as the basis for determining the rules for removing the complete virtual keyboard. This links the keyboard display strategy with the actual operational risk of the vehicle, abandons the fixed presentation of the complete keyboard, and enables the virtual keyboard to dynamically adjust its function according to the operational risk of the vehicle, thereby achieving a balance between driving safety and interaction efficiency.

[0097] In some embodiments, determining the rules for reducing the size of a pre-stored complete virtual keyboard may include: B1. If the operational risk level is high, the deletion rule is as follows: all functional areas of the complete virtual keyboard, except for the voice input prompt area, will be deleted.

[0098] B2. If the operational risk level is medium risk, the deletion rule is as follows: all functional areas of the complete virtual keyboard, except for the voice input prompt area, letter key area, number area, basic symbol area, and basic function control area, shall be deleted.

[0099] B3. If the risk level is low, the deletion rule is: do not delete the functional area of ​​the complete virtual keyboard.

[0100] As mentioned above, the pre-stored complete virtual keyboard usually adopts the full button layout of mobile phones, tablets, etc. The functional areas can include letter key areas, pinyin key areas, handwriting areas, input switching areas, as well as voice input prompt areas, number areas, basic symbol areas, symbol switching areas, complete symbol areas, basic function control areas, function switching areas, complete function control areas, emoji areas, emoji switching areas, etc.

[0101] When the vehicle's operational risk level is high, all functional areas of the virtual keyboard, except for the voice input prompt area, are removed. The keyboard display strategy then only includes the voice input prompt area. This way, the virtual keyboard only supports user voice input, disabling other functional areas that require user touch operation. By appropriately reducing interaction efficiency, driving safety is ensured to the greatest extent possible. In this situation, users can still input short voice messages such as their driving destination.

[0102] When the risk level is medium, all functional areas of the virtual keyboard except for the core function areas will be removed. The keyboard display strategy will then only include the core function areas: voice input prompts, letter keys, numbers, basic symbols, and basic function controls. Only simple touch operations will be supported, while handwriting input, shortcut keys, and the full symbol area—functions that require more user attention—will be disabled. This allows users to input short text such as contacts, driving destinations, and short addresses. Of course, the removal rules are not limited to the above settings and can be configured according to actual scenarios and needs.

[0103] When the operational risk level is low, the full virtual keyboard's functional area is not removed. In this case, the keyboard display strategy includes all functional areas of the full virtual keyboard, thereby improving the input usability of the virtual keyboard without compromising security. This allows users to edit messages and input long text.

[0104] In this embodiment, based on the principle that the number of functional areas to be removed is positively correlated with the level of operational risk, the functions of the complete virtual keyboard are removed in a step-by-step manner. At medium to high operational risk, the core functional areas are retained without affecting basic human-computer interaction. This achieves the interaction logic of less interaction at high operational risk, moderate interaction at medium operational risk, and more / full interaction at low operational risk, thus balancing driving safety and interaction efficiency.

[0105] The keyboard display strategy may also include the size of the virtual keyboard to be displayed. In some embodiments, before obtaining the keyboard display strategy according to the reduction rules, the size of the virtual keyboard to be displayed may be determined based on the operational risk level, wherein the size of the virtual keyboard to be displayed is positively correlated with the operational risk level. Accordingly, when obtaining the keyboard display strategy according to the reduction rules, the keyboard display strategy can be obtained based on the reduction rules and the size of the virtual keyboard to be displayed.

[0106] For medium-risk levels, where drivers need to focus more on driving, to further reduce the need for excessive driver attention to operate the virtual keyboard, the size of the virtual keyboard to be displayed is set to a larger size. Specifically, the size of each key on the virtual keyboard to be displayed is set to a larger size so that the driver can clearly see each key without having to spend too much attention identifying them. At the same time, since the virtual keyboard to be displayed at this time includes a small functional area, even if the size of each key is enlarged, it will not take up too much space on the central control screen.

[0107] For low-risk levels, drivers can focus more attention on operating the virtual keyboard. Since the virtual keyboard to be displayed retains a complete functional area and has a relatively large number of buttons, the size of the virtual keyboard to be displayed can be set to be relatively small. Specifically, the size of each button can be set to be relatively small to avoid taking up too much space on the central control screen.

[0108] For high-risk levels, the virtual keyboard to be displayed should only include the voice input prompt area. The voice input prompt area can be set to a large size to make it easier for drivers to intuitively and quickly identify the area.

[0109] In this embodiment, based on the principle that the size of the virtual keyboard to be displayed is positively correlated with the level of operational risk, the size of the virtual keyboard is set so that under medium and high risk levels, the visual proportion of the virtual keyboard is higher and more eye-catching, so that the driver can quickly identify it without deliberately focusing, reducing visual search and dwell time.

[0110] Optionally, when determining the size of the virtual keyboard to be displayed, if the operational risk level is low, the size of each key in the virtual keyboard to be displayed is determined to be the size of the corresponding key in the complete virtual keyboard; if the operational risk level is medium, the size of each key in the virtual keyboard to be displayed is determined to be a preset multiple of the size of the corresponding key in the complete virtual keyboard. The preset multiple is greater than 1.

[0111] In this embodiment, when the vehicle's operational risk level is medium risk, the size of each keyboard in the virtual keyboard to be displayed is enlarged so that the driver can quickly identify them without having to focus, thereby ensuring the driver's ease of operation of the virtual keyboard.

[0112] Step 304: Generate and display a virtual keyboard according to the keyboard display strategy.

[0113] After determining the keyboard display strategy, based on the functional areas and corresponding sizes of the virtual keyboard to be displayed included in the keyboard display strategy, the corresponding virtual keyboard is generated and displayed on the central control screen. At the same time, the corresponding functional attributes are configured for each functional area included in the virtual keyboard, so that the virtual keyboard has the corresponding functions, thereby enabling users to realize in-vehicle human-machine interaction based on the virtual keyboard.

[0114] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0115] Figure 4 This is a schematic diagram of the structure of a virtual keyboard display device provided in an embodiment of this application. Figure 4 As shown, the virtual keyboard display device provided in this embodiment may include: an acquisition module 401, a obtaining module 402, a determining module 403, and a display module 404.

[0116] The acquisition module 401 is used to acquire vehicle operating data when a keyboard display command is received.

[0117] The module 402 is used to obtain the operational risk level of the vehicle based on the operational data.

[0118] The determination module 403 is used to determine a keyboard display strategy based on the operational risk level; wherein the keyboard display strategy includes the functional areas of the virtual keyboard to be displayed, and the number of functional areas is negatively correlated with the operational risk level.

[0119] Display module 404 is used to generate and display the virtual keyboard according to the keyboard display strategy.

[0120] In one possible implementation, the operating data includes the vehicle's speed, position, operating status, and gear; the obtaining module 402 is further used for: The driving task type of the vehicle is determined based on at least one of the vehicle's speed, position, operating status, and gear position. Based on the driving task type, the operational risk level of the vehicle is obtained.

[0121] In one possible implementation, module 402 is also used for: If the vehicle speed exceeds a first preset speed threshold within a preset time period, then the driving task type is determined to be a high-speed cruise task; or, If the operating state is a frequent start-stop state, then the driving task type is determined to be a congested driving task; or, If the location is less than a preset distance threshold from a preset location, then the driving task type is determined to be a navigation guidance task; the navigation guidance task includes turning, as well as entering and exiting ramps; or, If the operating state is automatic parking and the vehicle speed is less than a second preset speed threshold, then the driving task type is determined to be an automatic parking task; or, If the gear is in the parking position, then the driving task type is determined to be a parking task.

[0122] In one possible implementation, module 402 is also used for: If the vehicle has multiple driving task types, the operational risk level corresponding to each driving task type is determined based on the pre-stored correspondence between the vehicle's operational risk level and the driving task type. Based on the operational risk level corresponding to each driving task type, the highest operational risk level is obtained, and the highest operational risk level is taken as the operational risk level of the vehicle.

[0123] In one possible implementation, the determining module 403 is further used for: Based on the operational risk level, rules for reducing the pre-stored complete virtual keyboard are determined; wherein, the reduction rules include reducing the functional areas of the complete virtual keyboard, and the number of functional areas to be reduced is positively correlated with the operational risk level; The keyboard display strategy is obtained based on the reduction rules.

[0124] In one possible implementation, the operational risk level includes a high-risk level, a medium-risk level, and a low-risk level; the determining module 403 is further configured to: If the operational risk level is high risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area are deleted. If the operational risk level is medium risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area, letter key area, number area, basic symbol area and basic function control area are deleted. If the operational risk level is low risk, then the deletion rule is determined as follows: the functional area of ​​the complete virtual keyboard will not be deleted.

[0125] In one possible implementation, the keyboard display strategy further includes the size of the virtual keyboard to be displayed; the determining module 403 is also used to: Based on the operational risk level, the size of the virtual keyboard to be displayed is determined; wherein, the size of the virtual keyboard to be displayed is positively correlated with the operational risk level; The step of obtaining the keyboard display strategy based on the deletion rules includes: Based on the reduction rules and the size of the virtual keyboard to be displayed, the keyboard display strategy is obtained.

[0126] In one possible implementation, the determining module 403 is further used for: If the operational risk level is low risk, then the size of each key in the virtual keyboard to be displayed is determined to be the size of the corresponding key in the complete virtual keyboard; If the operational risk level is medium risk, then the size of each key in the virtual keyboard to be displayed is determined to be a preset multiple of the size of the corresponding key in the complete virtual keyboard.

[0127] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0128] Figure 5 This is a schematic diagram of the controller provided in one embodiment of this application. Figure 5 As shown, the controller 500 of this embodiment includes a processor 510 and a memory 520, wherein the memory 520 stores a computer program 521 that can run on the processor 510. When the processor 510 executes the computer program 521, it implements the steps in any of the above method embodiments, for example... Figure 2 Steps 201 to 204 are shown. Alternatively, when processor 510 executes computer program 521, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 4 The functions of modules 401 to 404 are shown.

[0129] For example, computer program 521 may be divided into one or more modules / units, one or more of which are stored in memory 520 and executed by processor 510 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of computer program 521 in controller 500.

[0130] Those skilled in the art will understand that Figure 5 This is merely an example of a controller and does not constitute a limitation on the controller. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, buses, etc.

[0131] The processor 510 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0132] The memory 520 can be an internal storage unit of the controller, such as the controller's hard drive or memory, or an external storage device of the controller, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. The memory 520 can also include both internal and external storage units. The memory 520 is used to store computer programs and other programs and data required by the controller. The memory 520 can also be used to temporarily store data that has been output or will be output.

[0133] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0134] An embodiment of this application also provides a vehicle including the aforementioned controller.

[0135] An embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described virtual keyboard display method.

[0136] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0137] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0138] In the embodiments provided in this application, it should be understood that the disclosed devices / controllers and methods can be implemented in other ways. For example, the device / controller embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0139] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0140] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0141] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0142] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for displaying a virtual keyboard, characterized in that, include: Upon receiving a keyboard display command, acquire the vehicle's operating data; Based on the operational data, the operational risk level of the vehicle is obtained; Based on the operational risk level, a keyboard display strategy is determined; wherein, the keyboard display strategy includes the functional areas of the virtual keyboard to be displayed, and the number of functional areas is negatively correlated with the operational risk level; The virtual keyboard is generated and displayed according to the keyboard display strategy.

2. The virtual keyboard display method according to claim 1, characterized in that, The step of obtaining the vehicle's operational risk level based on the operational data includes: The driving task type of the vehicle is determined based on at least one of the vehicle's speed, position, operating status, and gear position. Based on the driving task type, the operational risk level of the vehicle is obtained.

3. The virtual keyboard display method according to claim 2, characterized in that, Determining the driving task type of the vehicle based on at least one of the vehicle's speed, position, operating status, and gear position includes: If the vehicle speed exceeds a first preset speed threshold within a preset time period, then the driving task type is determined to be a high-speed cruise task; or, If the operating state is a frequent start-stop state, then the driving task type is determined to be a congested driving task; or, If the location is less than a preset distance threshold from a preset location, then the driving task type is determined to be a navigation guidance task; the navigation guidance task includes turning, as well as entering and exiting ramps; or, If the operating state is automatic parking and the vehicle speed is less than a second preset speed threshold, then the driving task type is determined to be an automatic parking task; or, If the gear is in the parking position, then the driving task type is determined to be a parking task.

4. The virtual keyboard display method according to claim 2, characterized in that, The method of determining the vehicle's operational risk level based on the driving task type includes: If the vehicle has multiple driving task types, the operational risk level corresponding to each driving task type is determined based on the pre-stored correspondence between the vehicle's operational risk level and the driving task type. Based on the operational risk level corresponding to each driving task type, the highest operational risk level is obtained, and the highest operational risk level is taken as the operational risk level of the vehicle.

5. The virtual keyboard display method according to any one of claims 1 to 4, characterized in that, The process of determining the keyboard display strategy based on the operational risk level includes: Based on the operational risk level, rules for reducing the pre-stored complete virtual keyboard are determined; wherein, the reduction rules include reducing the functional areas of the complete virtual keyboard, and the number of functional areas to be reduced is positively correlated with the operational risk level; The keyboard display strategy is obtained based on the reduction rules.

6. The virtual keyboard display method according to claim 5, characterized in that, The operational risk levels include high risk, medium risk, and low risk. The rules for reducing the number of pre-stored complete virtual keyboards based on the operational risk level include: If the operational risk level is high risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area are deleted. If the operational risk level is medium risk, then the deletion rule is determined as follows: all functional areas of the complete virtual keyboard except for the voice input prompt area, letter key area, number area, basic symbol area and basic function control area are deleted. If the operational risk level is low risk, then the deletion rule is determined as follows: the functional area of ​​the complete virtual keyboard will not be deleted.

7. The virtual keyboard display method according to claim 6, characterized in that, The keyboard display strategy also includes the size of the virtual keyboard to be displayed; Before obtaining the keyboard display strategy based on the reduction rules, the method further includes: Based on the operational risk level, the size of the virtual keyboard to be displayed is determined; wherein, the size of the virtual keyboard to be displayed is positively correlated with the operational risk level; The step of obtaining the keyboard display strategy based on the deletion rules includes: Based on the reduction rules and the size of the virtual keyboard to be displayed, the keyboard display strategy is obtained.

8. The virtual keyboard display method according to claim 7, characterized in that, Determining the size of the virtual keyboard to be displayed based on the operational risk level includes: If the operational risk level is low risk, then the size of each key in the virtual keyboard to be displayed is determined to be the size of the corresponding key in the complete virtual keyboard; If the operational risk level is medium risk, then the size of each key in the virtual keyboard to be displayed is determined to be a preset multiple of the size of the corresponding key in the complete virtual keyboard.

9. A controller comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the virtual keyboard display method as described in any one of claims 1 to 8.

10. A vehicle, characterized in that, Includes the controller as described in claim 9.

Images