Human-machine interaction method, device, equipment, medium and program product for cockpit display screen
Patent Information
- Application Number
- CN202610608538.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-04-30
- Publication Date
- 2026-10-13
AI Technical Summary
[0004]由于操作步骤较多,导致在中控屏的显示桌面上,添加程序卡片的方式不够灵活,操作较为繁琐
在本申请中,将第一桌面的第一布局切换为第二布局,第二布局包括第一区域和第二区域,第一区域用于显示n个应用程序的程序卡片,第二区域用于显示m个应用程序的图标;控制第一应用程序的第一程序卡片和第一应用程序的第一图标联动,在不离开第一桌面的情况下,能够通过响应于针对第一图标的触发操作,自动添加或删除第一应用程序的程序卡片,减少用户的额外操作,解决由于多级人机交互导致的操作繁琐,效率低下的问题,提升系统各个功能区域间的相关性,提升操作效率及易用性,降低功能操作的失败率。
Smart Images

Figure CN122902901A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of human-computer interaction, and in particular to a human-computer interaction method, apparatus, device, medium, and program product for a cockpit display screen. Background Technology
[0002] Among the various in-vehicle devices in a car, the central control screen occupies an important position, enabling diverse operations on the vehicle.
[0003] When operating the central control screen, users can add program cards to the screen's display desktop by long-pressing any program card displayed on the desktop to enter edit mode. A list of program cards that can be added will appear, or an add button will be displayed. Clicking the button will take you to the program card library, where you can click the program card you want to add.
[0004] The numerous steps involved make adding program cards on the central control screen's desktop inflexible and cumbersome. Summary of the Invention
[0005] This application provides a human-computer interaction method, apparatus, device, medium, and program product for a cockpit display screen, the technical solution of which includes at least: According to one aspect of the embodiments of this application, a human-computer interaction method for a cockpit display screen is provided, the method comprising: Display a first layout of a first desktop, the first layout including a first area and multiple controls, the multiple controls including a first control; in response to a first trigger operation on the first control, switch the first layout to a second layout, the second layout including a first area and a second area, the first area for displaying program cards of n applications, the second area for displaying icons of m applications; control the linkage between the first program card and the first icon of the first application; Wherein, the program cards of n applications include the first program card; and / or, the icons of m applications include the first icon, where n and m are both positive integers.
[0006] In some optional designs, in response to a first trigger operation on the first control, the first layout is switched to the second layout, including: In response to a first trigger operation on the first control, the first area is shifted upwards and the second area is displayed below the first area; or, the first area is shifted downwards and the second area is displayed above the first area.
[0007] In some optional designs, in response to a first trigger operation on the first control, the size of the application cards of n applications in the first area is proportionally reduced from a first size to a second size that does not overlap with the second area.
[0008] In some optional designs, in response to a first trigger operation on the first control, q application components, where q is a positive integer, are displayed above the first area.
[0009] In some optional designs, the second layout is switched to the first layout in response to a second trigger action on the first control.
[0010] In some optional designs, in response to a second trigger action on the first control, the second area is switched to a canceled display state.
[0011] In some optional designs, the program cards of n applications in the second layout are sized to a second size, and in response to a second trigger operation on the first control, the size of the program cards of the n applications in the first area is restored from the second size to the first size.
[0012] In some optional designs, the second layout also displays components of q applications, and in response to a second trigger action on the first control, the display of the components of q applications is canceled.
[0013] In some optional designs, in response to a first trigger operation on the first control, a second control is displayed on the program card of at least one of the n application program cards in the first region.
[0014] In some optional designs, the display state of the first icon of the first application is changed when the display state of the first application card changes, and / or, in response to a triggering operation on a second control on the first application card.
[0015] In some optional designs, the first application card and the first icon of the first application are linked, including: When the display state of the first application card of the first application changes, and / or, in response to a triggering operation on the second control on the first application card, the display state of the first icon of the first application is changed.
[0016] In some optional designs, the display state of the first application card of the first application is changed when the display state of the first icon of the first application changes, and / or, in response to a triggering operation on the first icon.
[0017] In some optional designs, in response to a triggering operation on a second control on the first application card, the display state of the first icon of the first application is changed, including: In response to a third trigger operation on the second control, the first application card of the first application is switched from a currently displayed state to a canceled display state, and the display state of the first icon is switched from a first state to a second state; The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0018] In some optional designs, when the running state of the first application meets the first triggering condition, the first program card of the first application is switched from the currently displayed state to the canceled display state, and the display state of the first icon is switched from the first state to the second state. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0019] In some alternative designs, in response to a fourth trigger operation on the first icon, the display state of the first icon is switched from a first state to a second state, and the first application card of the first application is switched from a currently displayed state to a canceled display state; and / or, In response to a fifth trigger operation on the first icon, the display state of the first icon is switched from the second state to the first state, and the first application card of the first application is restored from the canceled display state to the displayed state.
[0020] In some optional designs, when the running state of the first application meets the second trigger condition, the display state of the first icon is switched from the first state to the second state, and the first application card of the first application is switched from the currently displayed state to the canceled display state; or, When the running state of the first application meets the third triggering condition, the display state of the first icon is switched from the second state to the first state, and the first program card of the first application is switched from the canceled display state to the displaying state. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0021] In some optional designs, in response to a third trigger operation on the first program card, the size of the first program card in the display state is proportionally reduced until the first program card is in the undisplayed state, and the display state of the first icon is switched from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0022] In some optional designs, if the current working state does not support the first application card being displayed, the size of the first application card being displayed is proportionally reduced until the first application card of the first application is de-displayed, and the display state of the first icon is switched from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0023] In some optional designs, in response to a fourth trigger operation on the first icon, the display state of the first icon is switched from a first state to a second state; and the size of the first application card in the currently displayed state is proportionally reduced until the first application card is in the undisplayed state; The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0024] In some optional designs, in response to a fifth trigger action on the first icon, the display state of the first icon is switched from the second state to the first state, and the first application card is added to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0025] In some optional designs, if the current working state does not support the display state of the first icon as the first state, the display state of the first icon is switched from the first state to the second state, and the size of the first program card that is currently being displayed is proportionally reduced until the first program card is in the undisplayed state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0026] In some optional designs, if the current working state does not support the display state of the first icon being in the second state, the display state of the first icon will be switched from the second state to the first state, and the first program card will be added to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0027] In some optional designs, icons of all or some applications in the system are displayed in the second area, based on usage frequency or a system preset order.
[0028] In some optional designs, when the first program card is in the canceled display state, the second program card adjacent to the first program card moves to the original position of the first program card; The original location of the second program card is on the first desktop or on a second desktop adjacent to the first desktop.
[0029] According to another aspect of the embodiments of this application, a display device is provided, the display device comprising the following modules: The display module is used to display the first layout of the first desktop. The first layout includes a first area and multiple controls, among which the first control is included. The control module is used to switch the first layout to the second layout in response to a first trigger operation on the first control. The second layout includes a first area and a second area. The first area is used to display the program cards of n applications, and the second area is used to display the icons of m applications. The control module is also used to control the linkage between the first application card and the first icon of the first application. Wherein, the program cards of n applications include the first program card; and / or, the icons of m applications include the first icon, where n and m are both positive integers.
[0030] In some optional designs, the control module is also used to switch the first layout to a second layout in response to a first trigger operation on the first control, including: In response to a first trigger operation on the first control, the first area is shifted upwards and the second area is displayed below the first area; or, the first area is shifted downwards and the second area is displayed above the first area.
[0031] In some optional designs, the control module is also used to, in response to a first trigger operation on the first control, scale down the program card size of n applications in the first area from a first size to a second size that does not overlap with the second area.
[0032] In some optional designs, the control module is also used to display q application components above the first area in response to a first trigger operation on the first control, where q is a positive integer.
[0033] In some optional designs, the control module is also used to switch the second layout to the first layout in response to a second trigger operation on the first control.
[0034] In some optional designs, the control module is also used to switch the second area to a canceled display state in response to a second trigger operation on the first control.
[0035] In some optional designs, the program cards of n applications in the second layout are sized to a second size, and the control module is also used to restore the size of the program cards of n applications in the first area from the second size to the first size in response to a second trigger operation on the first control.
[0036] In some optional designs, the second layout also displays components of q applications, a control module, and is also used to cancel the display of the components of q applications in response to a second trigger operation on the first control.
[0037] In some optional designs, the control module is also used to display a second control on the program card of at least one of the n application program cards in the first region in response to a first trigger operation on the first control.
[0038] In some optional designs, the control module is also used to change the display state of the first icon of the first application when the display state of the first application card of the first application changes, and / or, in response to a triggering operation on a second control on the first application card.
[0039] In some optional designs, the control module is also used to change the display state of the first program card of the first application when the display state of the first icon of the first application changes, and / or, in response to a trigger operation on the first icon.
[0040] In some optional designs, the control module is also used to switch the first application card of the first application from a display state to a cancel display state in response to a third trigger operation on the second control, and to switch the display state of the first icon from a first state to a second state. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0041] In some optional designs, the control module is also used to switch the first program card of the first application from the displaying state to the canceled display state, and to switch the display state of the first icon from the first state to the second state, when the running state of the first application meets the first triggering condition. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0042] In some optional designs, the control module is also configured to, in response to a fourth trigger operation on the first icon, switch the display state of the first icon from a first state to a second state, and switch the first application card of the first application from a currently displayed state to a canceled display state. And / or, The control module is also configured to respond to a fifth trigger operation on the first icon by switching the display state of the first icon from the second state to the first state, and restoring the first application card of the first application from the canceled display state to the currently displayed state.
[0043] In some optional designs, the control module is further configured to, when the running state of the first application meets the second trigger condition, switch the display state of the first icon from the first state to the second state, and switch the first application card of the first application from the currently displayed state to the canceled display state; or, The control module is also used to switch the display state of the first icon from the second state to the first state and switch the first program card of the first application from the canceled display state to the displaying state when the running state of the first application meets the third triggering condition. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0044] In some optional designs, the control module is also used to respond to a third trigger operation on the first program card by proportionally reducing the size of the first program card in the display state until the first program card is in the canceled display state, and switching the display state of the first icon from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0045] In some optional designs, the control module is also used to proportionally reduce the size of the first program card in the display state until the first program card of the first application is de-displayed, and to switch the display state of the first icon from the first state to the second state when the current working state does not support the first program card of the first application being in the display state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0046] In some optional designs, the control module is also configured to, in response to a fourth trigger operation on the first icon, switch the display state of the first icon from a first state to a second state; and proportionally reduce the size of the first program card in the currently displayed state until the first program card is in the undisplayed state; The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0047] In some optional designs, the control module is also used to switch the display state of the first icon from the second state to the first state in response to a fifth trigger operation on the first icon, and to add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0048] In some optional designs, the control module is also used to switch the display state of the first icon from the first state to the second state when the current working state does not support the display state of the first icon being in the first state, and to proportionally reduce the size of the first program card in the currently displayed state until the first program card is in the undisplayed state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0049] In some optional designs, the control module is also used to switch the display state of the first icon from the second state to the first state when the current working state does not support the display state of the first icon being the second state, and to add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0050] In some optional designs, the display module is also used to display icons of all or some applications in the system within a second area, based on usage frequency or a system preset order.
[0051] In some optional designs, the control module is also used to move a second program card adjacent to the first program card to the original position of the first program card when the first program card is in the canceled display state; The original location of the second program card is on the first desktop or on a second desktop adjacent to the first desktop.
[0052] According to another aspect of the embodiments of this application, a computer device is provided, the computer device comprising: A processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement human-machine interaction methods for cockpit displays as described above.
[0053] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores at least one program that is loaded and executed by a processor to implement the human-computer interaction method for a cockpit display screen as described in the various aspects above.
[0054] According to another aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuitry and / or program instructions, which, when the chip is run on a computer device, are used to implement the human-computer interaction methods for cockpit displays described in the above aspects.
[0055] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium, a processor retrieving the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to implement the human-computer interaction method for a cockpit display screen as described in the various aspects above.
[0056] The technical solutions provided in this application embodiment may include the following beneficial effects: In this application, the first layout of the first desktop is switched to a second layout. The second layout includes a first area and a second area. The first area is used to display program cards of n applications, and the second area is used to display icons of m applications. The first program card and the first icon of the first application are linked together. Without leaving the first desktop, the program card of the first application can be automatically added or deleted in response to the trigger operation of the first icon. This reduces the user's extra operations, solves the problem of cumbersome operation and low efficiency caused by multi-level human-computer interaction, improves the correlation between various functional areas of the system, improves operation efficiency and ease of use, and reduces the failure rate of functional operations. Attached Figure Description
[0057] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.
[0058] Figure 1 A schematic diagram of an in-vehicle display screen provided in an exemplary embodiment of this application is shown; Figure 2 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 3This illustration shows a schematic diagram of performing a first trigger operation on a first control according to an exemplary embodiment of this application; Figure 4 This illustration shows a schematic diagram of deleting a first program card in response to a trigger operation on a first icon, according to an exemplary embodiment of this application. Figure 5 This illustration shows a schematic diagram of changing the display state of a first icon in response to a trigger operation on a first program card, according to an exemplary embodiment of this application. Figure 6 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 7 This illustration shows a schematic diagram of a first desktop in an editable state, provided by an exemplary embodiment of this application. Figure 8 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 9 This illustration shows a schematic diagram of performing a second trigger operation on a first control according to an exemplary embodiment of this application; Figure 10 This illustration shows a schematic diagram of a first desktop exiting an editable state, provided in an exemplary embodiment of this application. Figure 11 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 12 This illustration shows a schematic diagram of performing a third trigger operation on a first program card according to an exemplary embodiment of this application; Figure 13 This illustration shows a schematic diagram of a first program card that gradually shrinks according to an exemplary embodiment of this application; Figure 14 This illustration shows a schematic diagram of a first program card in a canceled display state according to an exemplary embodiment of this application; Figure 15 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 16 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 17 This illustration shows a schematic diagram of performing a fourth triggering operation on a first icon according to an exemplary embodiment of this application; Figure 18 This illustration shows a schematic diagram of performing a fifth trigger operation on a first icon according to an exemplary embodiment of this application; Figure 19This illustration shows a schematic diagram of adding a first program card according to an exemplary embodiment of this application; Figure 20 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 21 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown; Figure 22 This invention illustrates a block diagram of a human-machine interaction device for an in-vehicle display screen provided in an exemplary embodiment of this application; Figure 23 This illustration shows a structural schematic diagram of a human-computer interaction device for an in-vehicle display screen provided in an exemplary embodiment of this application. Detailed Implementation
[0059] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0060] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0061] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."
[0062] Figure 1 This diagram illustrates the architecture of an in-vehicle display screen 100 provided in an exemplary embodiment of this application. The display content of the in-vehicle display screen 100 includes: a first program card 110, a second program card 120, and a third program card 130.
[0063] The first program card 110 is associated with a first application, which includes a navigation program, a music program, a vehicle control program, a communication program, or any other application that supports operation in an in-vehicle environment, and this application does not limit this to any particular application. The first program card 110 dynamically displays the real-time content of the first application and / or provides access to the operation / function of the first application. For example, when the first application is a navigation program, the first program card 110 displays one or more pieces of information such as the current route, the next turn prompt, and the estimated arrival time in real time, and / or integrates access to one or more operations / functions such as start navigation, end navigation, and mute; when the first application is a music program, the first program card 110 displays one or more pieces of information such as the currently playing song and the album cover, and / or provides access to one or more operations / functions such as play, pause, and skip tracks.
[0064] The second program card 120 is associated with the second application. The third program card 130 is associated with the third application. The second and / or third applications include any application that supports operation in the in-vehicle environment, and its specific type may be the same as or different from the first application. Taking the second program card 120 as an example, the second program card 120 dynamically displays the content of the second application and / or provides entry points for one or more operations / functions associated with the second application. For example, the second program card 120 is associated with the air conditioning control program, displaying one or more pieces of information, including in-vehicle temperature and fan speed mode, in real time, and / or supporting entry points for one or more operations / functions, including temperature adjustment and mode switching. This application does not limit this.
[0065] Optionally, Figure 1 The diagram shows an example of a basic architecture including a first program card 110, a second program card 120, and a third program card 130. In actual deployment, at least two program cards can be displayed simultaneously on the vehicle display screen 100, and program cards can be deleted, added, or moved.
[0066] Optionally, the first program card 110, the second program card 120, and the third program card 130 may be arranged vertically, or the first program card 110, the second program card 120, the third program card 130 and the program cards of other applications may be arranged in a grid. This application does not limit this arrangement.
[0067] In some embodiments, the first program card 110 may be one or more, and the second program card 120 and / or the third program card 130 may also be one or more, which is not limited in this application.
[0068] In some embodiments, the in-vehicle display screen 100 is mounted on the dashboard in the center of the cockpit, in the area to the right of the steering wheel and between the driver and passenger seats. Optionally, the in-vehicle display screen 100 can also be mounted behind the steering wheel to display vehicle status, navigation information, and driver assistance information to the driver; and / or the in-vehicle display screen 100 can also be mounted directly in front of the passenger seat, on the back of the front seats, behind the center armrest, or tilted down in the roof to provide passengers with audio-visual entertainment, independent navigation, games, and vehicle environmental control functions; and / or the in-vehicle display screen 100 can also be mounted via a robotic arm or sliding rail, allowing its height and angle to be adjusted within a certain range to adapt to different driver seating positions or usage scenarios. This application does not limit this.
[0069] Optionally, the vehicle display 100 is not limited to a single physical screen; it may be composed of multiple physical screens seamlessly spliced together to form a continuous, wide display area. The first program card 110, the second program card 120, and the third program card 130 are arranged and interact with each other across multiple physical screens on their continuous display area, and their layout logic is consistent with the embodiment on a single screen.
[0070] In some embodiments, the in-vehicle display screen 100 is operated using various auxiliary methods, including touch, voice control, and shortcut keys. Optionally, the display content of the in-vehicle display screen 100 includes one or more of icons, application cards, and controls. In response to a click on an icon, the user enters the operation page of the application associated with the icon; in response to a click on a control on the operation page, the user adjusts the relevant parameters of the in-vehicle component associated with the control; in response to a long press on an icon, the application card enters an editable state, thereby enabling the user to move, add, and delete application cards.
[0071] In some embodiments, the vehicle display 100 is connected to the vehicle control system via other vehicle displays or other terminals in the vehicle via an internal vehicle communication bus (such as an Ethernet vehicle bus or a Controller Area Network (CAN) bus); the first program card 110, the second program card 120, the third program card 130 and the program cards of other applications in the vehicle display 100 are implemented through the corresponding service function modules in the screen interface.
[0072] First, a brief introduction to one or more terms used in the embodiments of this application: Screens: In the field of intelligent vehicles, screens include one or more of the following: central control screen, passenger entertainment screen, rear entertainment screen, sliding screen, magic control screen, and central touch screen. The central control screen, as a crucial hub for cockpit interaction, is typically located in the center of the dashboard. It offers comprehensive functionality, enabling navigation planning, multimedia playback, air conditioning adjustment, and seat settings, and some models also support vehicle-to-everything (V2X) connectivity and app downloads. The passenger entertainment screen serves as both a basic control function and can interact with other screens. The front passenger entertainment screen is a dedicated screen designed for the front passenger, allowing for independent video playback, content browsing, or game playing, avoiding interference with the driver. It also supports various functions, including smartphone screen mirroring, enhancing the front passenger experience. Rear entertainment screens are typically installed in the rear seat headrests or roof, are usually large, and offer one or more functions such as playing high-definition videos, connecting gaming devices, and mobile office capabilities. Some also support adjusting rear air conditioning and / or seats. The sliding screen is a movable interactive screen that allows for position adjustment by sliding it across different areas of the vehicle and / or angle adjustment. The smart control screen is a small interactive screen that integrates multiple convenient control functions, allowing users to control cabin functions from any location within the vehicle. The central touchscreen integrates specific vehicle control functions, centrally managing various detailed operations. As a supplement to the central control screen, it clarifies function categories and reduces the operational layers of a single screen.
[0073] Desktop: The desktop is the default interactive interface displayed after the screen starts up. It is a visual operation center that integrates function entry points, information display and personalized settings, and a bridge connecting the user and screen functions.
[0074] The desktop includes one or more of the following: 3D car model control desktop, card-style desktop, immersive entertainment desktop, minimalist wallpaper desktop, interactive desktop, and quick control desktop. The 3D car model control desktop uses a 3D car model as its visual element; the model can rotate and dynamically displays the status of vehicle components. It integrates various vehicle control functions, including seat adjustment, air conditioning control, and window operation, replacing complex text menus with intuitive visuals to reduce the difficulty of vehicle control. The card-style desktop uses a segmented program card layout, with each program card corresponding to an independent function. Program cards include one or more types, such as navigation program cards, music program cards, air conditioning program cards, and entertainment program cards. Some card-style desktops support adding, deleting, and moving one or more program cards, making them easy to use and adaptable to different user habits, flexibly matching functional needs in different scenarios. The immersive entertainment desktop uses high-definition wallpapers or animated... Based on a static background, it integrates various entertainment functions including video playback, games, music, and screen mirroring, minimizing complex operation elements and enhancing the comfort and enjoyment of the ride. The simple wallpaper desktop mainly uses static or dynamic wallpapers, retaining a few function entries and supporting custom wallpaper changes to reduce interface clutter and meet the personalized aesthetic needs of drivers and passengers. The interactive desktop supports cross-screen content flow, breaking the functional limitations of a single screen, realizing multi-screen information sharing and collaborative control, adapting to the usage needs of different positions in the car, making interaction more flexible and smooth, and enhancing the overall intelligent experience of the cabin. The quick control desktop integrates high-frequency quick functions, with the interface mainly featuring large icons and simple buttons, some of which support voice linkage control, centralizing scattered control functions and shortening the operation path.
[0075] Icons: Icons are small, visual identifiers on the desktop that represent applications. They are typically presented as simple graphics (with a minimal text name) and serve as quick access points to launch applications. They are small in size, have fixed styles or support customization, and are associated with the launch command of the corresponding application. Icons allow users to intuitively distinguish between different applications, and by clicking an icon, they can quickly launch the application without having to search through complex menus, simplifying the operation path.
[0076] Application Cards: Application cards are visual interactive modules associated with a specified application. Application cards include one or more of the following characteristics: • Dynamically display real-time information for a specified application; • Integrates one or more entry points for operations / functions, enabling multiple functions without launching the full interface of the application; • At least one of the following: size, position, and display format can be flexibly adjusted by the user or system.
[0077] Unlike icons, which serve only as static launch points, application cards carry dynamic content for a single application and / or continuously update application data or information (such as navigation routes, music playback progress, and message notifications). Application cards also differ from feature-aggregated folders, which manage multiple application entry points; application cards do not collect or manage other applications or cards. Application cards are interactive cards or controls used to display real-time information about the application and implement all or part of the application's functions. They have real-time information preview capabilities and can be dynamically adjusted in real time.
[0078] Optionally, on an in-vehicle display, the application card may appear as a navigation preview, music playback controls, or an air conditioning settings panel; in the virtual space of virtual reality (VR) or augmented reality (AR) glasses, the application card may appear as a floating, spatially positioned 3D information panel; on a head-up display (HUD), it can be integrated with the real field of view, displaying key navigation or safety prompts as a transparent layer. The application card can be presented and interacted with as a unified information module across device forms (such as in-vehicle screens, VR or AR spaces, and HUDs).
[0079] Each application card is associated with an application, and the visual presentation of the application card includes at least one of the following: an information display area for continuously updating and displaying data or information from the associated application, an interactive operation area for integrating one or more functions for the application, and an identification area for displaying the application name or icon.
[0080] Secondly, the relevant content involved in this application will be introduced.
[0081] In related technologies, when operating the central control screen, users can add program cards to the display desktop by long-pressing any program card on the display desktop to enter the edit state and display a list of program cards that can be added; or an add button can be displayed, and clicking the button can jump to the program card library and click the program card that you want to add.
[0082] When deleting an application card on the central control screen's display desktop, users need to long-press the application card to enter edit mode. A red delete button or delete icon will appear on the application card. Click the icon to delete.
[0083] To address the issue of cumbersome operation steps in related technologies, this application adopts a method of continuously switching between display desktop and desktop editing state, which improves the correlation between various functional areas of the system, enhances operational efficiency and ease of use, and reduces the failure rate of functional operations.
[0084] Figure 2A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown. The method is performed by a display device and includes: Step 210: Display the first layout of the first desktop, which includes a first area and multiple controls, including the first control among the multiple controls.
[0085] The first desktop is a desktop with program cards on the screen of the in-vehicle display device, also known as a card-style desktop.
[0086] The first desktop can be deployed on one or more of various in-vehicle screens, including the central control screen, passenger entertainment screen, rear entertainment screen, sliding screen, magic control screen, and central touch screen.
[0087] On in-vehicle display screens, a card-based desktop is a main screen interface or system default user interface adapted to in-vehicle driving scenarios, using application cards as the primary interaction module. The card-based desktop transforms individual in-vehicle applications or functions into independent visual application cards, presented on the screen through a segmented layout. It supports customizing the position, combination, and addition / removal of application cards, directly displaying dynamic information about the corresponding functions of the application, and providing entry points for one or more operations / functions within the application card. For example, switching tracks in a music application card or viewing the remaining trip in a navigation application card can be done without entering the full application interface, thereby improving the convenience of operation and the intuitiveness of information acquisition during driving, and meeting the safety interaction needs while driving.
[0088] For example, such as Figure 3 As shown, the first control 30 is located in the lower left corner of the first desktop and is used to enable the first desktop to enter an editable state and / or change the layout of the first desktop.
[0089] In some embodiments, the upper area of the first desktop is a vehicle status information bar, which displays the current system time status information, allowing users to quickly obtain the vehicle's operating parameters.
[0090] In some embodiments, the lower area of the first desktop is an application shortcut bar containing app thumbnails of multiple applications. The layout of this area is fixed, and the apps displayed below are not necessarily related to the application cards of the applications currently displayed on the first desktop. The content displayed does not change with desktop switching. That is, during the process of switching from the first desktop to the second desktop, the third desktop, or other desktops, the app thumbnails in this shortcut bar remain fixed and do not change with the switching process. Users can quickly launch the corresponding application by clicking the thumbnail without having to go into the application list to find it.
[0091] For example, such as Figure 3As shown, the first layout is displayed. At this time, the first layout only has a first area and multiple controls. The first area includes program cards of n applications, and the multiple controls include the first control.
[0092] Step 220: In response to the first trigger operation on the first control, switch the first layout to the second layout. The second layout includes a first area and a second area. The first area is used to display the program cards of n applications, and the second area is used to display the icons of m applications.
[0093] In some embodiments, when the first desktop is in the second layout, the first desktop is in an editable state. The editable state of the first desktop is a state in which program cards of n applications switch between a currently displayed state and a canceled display state, and / or a state in which icons of m applications switch between a first state and a second state. It can also be understood as a state in which a delete button appears in the upper right corner of the program cards of n applications in the first area, and at the same time, a first identifier appears in the upper right corner of the icons of n applications in the second area.
[0094] like Figure 4 As shown, the first desktop includes a first area 410 and a second area 420. The first area 410 is located above or below the second area 420. The first area 410 is used to display program cards of n applications, and the second area 420 is used to display icons of m applications. The types of the n applications and the m applications may overlap or not overlap.
[0095] The types of the n and / or m applications include: navigation and positioning applications, which meet the route guidance needs while driving; audio-visual entertainment applications, which provide users with auditory and visual entertainment; vehicle control and diagnostic applications, which directly connect to vehicle hardware to monitor vehicle conditions and ensure normal vehicle operation; interconnection and interaction applications, which break down device barriers and enable the vehicle to interact with other devices and scenarios, including mobile phone-vehicle interconnection programs and / or vehicle-home interconnection programs; system tools and personalization applications, which provide download and management of various applications, optimize the vehicle user experience, and / or enable personalized customization; and communication and collaboration applications, which support voice-controlled calling functions and / or synchronize mobile phone contacts and call logs for seamless integration.
[0096] In some embodiments, the second area is used to display icons of m applications, including: displaying icons of all or some applications in the system in the second area according to user usage frequency or system preset order.
[0097] Optionally, in the second area, icons corresponding to one or more program cards on the first desktop are displayed according to the user's usage frequency or a system preset order. For example, there are three desktops, each displaying three program cards, and nine icons corresponding to these nine program cards are displayed in the second area.
[0098] Optionally, the icon order can be preset based on driving operation convenience. Alternatively, the icon order can be preset by taking into account the driver's operating posture and touch range, and / or by following the relevance of functions and the logic of usage scenarios.
[0099] In some embodiments, the order of icons and the content displayed are not fixed, but dynamically adapted based on the user's usage scenario and operating habits.
[0100] Step 230: Control the linkage between the first application card and the first icon of the first application.
[0101] Wherein, the program cards of n applications include the first program card; and / or, the icons of m applications include the first icon, where n and m are both positive integers.
[0102] In some embodiments, the first program card is displayed in the first area, and the first icon is displayed in the second area, or is folded under the second area.
[0103] The linkage between the first program card and the first icon refers to the synchronized response between them in terms of function, information, and operation, achieving interoperability and information sharing to meet the safety and convenience requirements of in-vehicle scenarios. The linkage includes bidirectional synchronization of operations; when an operation is performed on the first program card or the first icon, a corresponding response will appear on the other side; and real-time synchronized display of information, where the first program card will synchronize the dynamic information of the application associated with its corresponding first icon in real time, allowing users to intuitively access content without entering the application.
[0104] In this application, the linkage between the first program card and the first icon includes changing the display state of the first program card or performing an operation on the first program card, and the display state of the first icon performing a corresponding response feedback, and / or changing the display state of the first icon or performing an operation on the first icon, and the display state of the first program card performing a corresponding response feedback.
[0105] In this application, the display state of the first program card includes a displaying state and a canceled display state, and the display state of the first icon includes a first state and a second state.
[0106] The states are as follows: the first program card is displayed on the first desktop; the state of being canceled is that the first program card is not displayed on the first desktop; the first state includes the first icon displaying the first identifier; and the second state includes the first icon not displaying the first identifier.
[0107] Optionally, the first identifier is a checkmark displayed in the upper right corner of the first icon. This application does not limit the implementation of the first identifier, as long as it supports distinguishing the two states of the first icon.
[0108] In some embodiments, such as Figure 4 As shown, the operation performed on the first icon "Application 4" includes a click operation. The click operation can be implemented as follows: after the user touches the first icon "Application 4" on the screen with their finger and immediately releases it, in response to the click operation on the first icon "Application 4", the display state of the first icon "Application 4" is changed, and according to the display state of the first icon "Application 4", the corresponding operation is performed on the first program card "Program Card 4".
[0109] For example, when a user touches the first icon "App 4" on the screen and immediately releases their finger, in response to the click operation on the first icon "App 4", the check mark in the upper right corner of the first icon "App 4" disappears, and the first application card "Application Card 4" is deleted.
[0110] Optionally, if the in-vehicle display supports floating touch, the click operation can also be implemented as follows: the user does not touch the screen, but points to the location of the first icon "Application 4" on the screen with their finger. When the first icon "Application 4" on the screen appears as a selected icon, the user slightly shakes their finger to change the display state of the first icon "Application 4". Based on the display state of the first icon "Application 4", the user performs the corresponding operation on the first program card "Program Card 4".
[0111] For example, when the in-vehicle display supports floating touch, the user can point to the location of the first icon "Application 4" on the screen without touching it. When the first icon "Application 4" appears with a selection mark, the user can slightly shake their finger, and the check mark in the upper right corner of the first icon "Application 4" will disappear, thus deleting the first program card "Program Card 4".
[0112] There are no restrictions on how users touch the screen or how they point at it.
[0113] In some embodiments, such as Figure 5As shown, the operations performed on the first program card "program card 4" include a click operation. The click operation can be implemented as follows: after the user touches a designated position on the first program card "program card 4" on the screen with their finger, they immediately release their finger. In response to the click operation on the first program card "program card 4", the display state of the first program card "program card 4" is changed, and according to the display state of the first program card, the corresponding operation is performed on the first icon.
[0114] For example, when a user touches the delete button on the first application card "Application Card 4" and immediately releases their finger, the first application card "Application Card 4" is deleted in response to the click operation on the first application card "Application Card 4", and the check mark in the upper right corner of the first icon "Application 4" disappears.
[0115] The method of deleting the first program card "Program Card 4" is not limited.
[0116] Optionally, if the in-vehicle display supports floating touch, the click operation can also be implemented as follows: the user does not touch the screen, but points to a designated location on the first program card on the screen with their finger. When a selection mark appears at the designated location on the first program card, the user slightly shakes their finger to change the display state of the first program card. Based on the display state of the first program card, the user performs the corresponding operation on the first icon. There are no restrictions on the way the user touches the screen or the way the user points to the screen.
[0117] For example, when the in-vehicle display supports floating touch, the user does not touch the screen. The user points to the delete key on the first program card with their finger. When the delete key on the first program card is selected, the user shakes their finger slightly to delete the first program card "Program Card 4". The check mark in the upper right corner of the first icon "Application 4" disappears.
[0118] In summary, the first layout of the first desktop is switched to a second layout, which includes a first area and a second area. The first area displays program cards for n applications, and the second area displays icons for m applications. The system controls the linkage between the first program card and the first icon of the first application. Without leaving the first desktop, program cards of the first application can be automatically added or deleted in response to trigger operations on the first icon. This reduces the user's extra operations, solves the problem of cumbersome and inefficient operation caused by multi-level human-computer interaction, improves the correlation between various functional areas of the system, enhances operational efficiency and ease of use, and reduces the failure rate of functional operations.
[0119] 1. In response to a first trigger operation on the first control, switch the first layout of the first desktop to the second layout.
[0120] Figure 6 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown.
[0121] In some embodiments, for step 220: such as Figure 6 As shown, in response to a first trigger operation on the first control, switching the first layout to the second layout includes: Step 221: In response to a first trigger operation on the first control, shift the first region upward and display the second region below the first region; or shift the first region downward and display the second region above the first region.
[0122] In some embodiments, in response to a first trigger operation on a first control, the size of the application cards of n applications in the first region is proportionally reduced from a first size to a second size that does not overlap with the second region.
[0123] In some embodiments, in response to a first trigger operation on a first control, q application components, where q is a positive integer, are displayed above a first area.
[0124] like Figure 7 As shown, in response to a first trigger operation on the first control, the layout of the first desktop is changed by shifting the first area upwards and simultaneously reducing the size of the application cards of n applications in the first area to display the second area 420. The application cards of m applications are displayed in the second area. For example, the second area 420 can be expanded to display all applications in the system that support displaying application cards on the first desktop, and q application widgets are displayed above the application cards of the n applications.
[0125] 2. In response to a second trigger operation on the first control, switch the second layout of the first desktop to the first layout.
[0126] In some embodiments, such as Figure 8 As shown, in response to a second trigger operation on the first control, switching the second layout to the first layout includes: Step 240: In response to the second trigger operation on the first control, switch the second layout to the first layout.
[0127] In some embodiments, in response to a second triggering operation on a first control, the second layout is switched to the first layout.
[0128] In some embodiments, in response to a second trigger operation on the first control, the second area is switched to a de-display state.
[0129] In some embodiments, the size of the application cards of n applications in the second layout is a second size, and in response to a second trigger operation on the first control, the size of the application cards of the n applications in the first area is restored from the second size to the first size.
[0130] In some embodiments, the second layout also displays q application components, and in response to a second trigger operation on the first control, the display of the q application components is canceled.
[0131] For example, such as Figure 9 As shown, in response to a second click operation on the first control, such as Figure 10 As shown, the second area is switched from being displayed to being undisplayed, the size of n application cards is restored from the second size to the first size, and the widgets of q applications are undisplayed.
[0132] For step 230: it includes one or more of the following steps: • In response to a trigger operation on the first program card, change the display state of the first icon.
[0133] • When the display state of the first program card changes, change the display state of the first icon.
[0134] • In response to a trigger action on the first icon, change the display state of the first program card.
[0135] • When the display state of the first icon changes, change the display state of the first program card.
[0136] The following describes an exemplary embodiment of the human-computer interaction method for the cockpit display screen described above.
[0137] In some embodiments, when the display state of the first application card of the first application changes, and / or, in response to a triggering operation on a second control on the first application card, the display state of the first icon of the first application is changed.
[0138] In some embodiments, when the display state of the first icon of the first application changes, and / or, in response to a trigger operation on the first icon, the display state of the first application card of the first application is changed.
[0139] 3. In response to a trigger operation on the second control on the first program card, change the display state of the first icon.
[0140] In some embodiments, switching the first layout to the second layout in response to a first trigger operation on the first control further includes: displaying the second control on the application card of at least one of the application cards of n applications in the first region in response to the first trigger operation on the first control.
[0141] Figure 11 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown.
[0142] In some embodiments, such as Figure 11 As shown, in response to a trigger operation on a second control on a first application card, changing the display state of a first icon of the first application includes: Step 231: In response to a third trigger operation on the second control, switch the first application card of the first application from the currently displayed state to the undisplayed state, and switch the display state of the first icon from the first state to the second state.
[0143] The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0144] In this application, as Figure 12 As shown, the third triggering operation includes a third click operation. The third click operation can be implemented as follows: the user touches a designated location on the first application card "Application Card 4" on the screen and immediately releases their finger. For example, the user touches the delete button in the upper right corner of the first application card "Application Card 4" and immediately releases their finger. In response to the click operation on the first application card, the first application card is deleted, and the display state of the first icon "Application 4" is changed accordingly. For example, the check mark in the upper right corner of the first icon "Application 4" is deleted.
[0145] Optionally, if the in-vehicle display supports floating touch, the third click operation can also be implemented as follows: the user does not touch the screen, but points to a specific location on the first program card "Program Card 4" on the screen with their finger. For example, the user points to the delete key on the first program card "Program Card 4". When the delete key on the first program card "Program Card 4" shows a selection mark, the user slightly shakes their finger to delete the first program card, which changes the display state of the first icon accordingly. For example, the check mark in the upper right corner of the first icon is deleted.
[0146] There are no restrictions on how users touch the screen or how they point at it.
[0147] In some embodiments, in response to a third trigger operation on a second control on a first application card, switching the first application card of the first application from a currently displayed state to a de-displayed state, and switching the display state of the first icon from a first state to a second state, includes: In response to a third click operation on the second control on the first program card, the size of the first program card in the display state is proportionally reduced until the first program card is de-displayed, and the display state of the first icon is switched from the first state to the second state.
[0148] The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0149] like Figure 13 As shown, in response to a click operation on a specified location of the first program card "Program Card 4", the first program card "Program Card 4" is deleted, and the size of the first program card "Program Card 4" is reduced proportionally, such as... Figure 14 As shown, this continues until the first program card "Program Card 4" completely disappears. The specified location of the first program card "Program Card 4" includes the location of the delete key on the first program card "Program Card 4". For example, the delete key on the first program card "Program Card 4" is located in the upper right corner of the first program card.
[0150] For example, a third trigger operation for a first program card includes a first swipe operation for the first program card.
[0151] The first swipe operation includes swiping the first program card up or down, with the swipe distance meeting a first threshold, deleting the first program card, and putting the first program card in a canceled display state. This application does not limit the implementation method of the third trigger operation.
[0152] 4. When the display state of the first program card changes, change the display state of the first icon.
[0153] Figure 15 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown.
[0154] In some embodiments, when the display state of the first application card of the first application changes, changing the display state of the first icon of the first application includes: Step 232: When the running state of the first application meets the first triggering condition, switch the first program card of the first application from the currently displayed state to the canceled display state, and switch the display state of the first icon from the first state to the second state.
[0155] The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0156] In some embodiments, when the running state of the first application meets a first triggering condition, switching the first application card of the first application from a currently displayed state to a canceled display state, and switching the display state of the first icon from a first state to a second state, includes: If the current working state does not support the first application card of the first application being displayed, the size of the first application card in the display state will be reduced proportionally until the first application card of the first application is de-displayed, and the display state of the first icon will be switched from the first state to the second state.
[0157] The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0158] For example, such as Figure 13 and Figure 14 As shown, when the first application card "Application Card 4" is not displayed in the current working state, the size of the first application card "Application Card 4" is proportionally reduced until the first application card "Application Card 4" is de-displayed, and the display state of the first icon "Application 4" is switched from the first state to the second state.
[0159] The first state includes a checkmark displayed in the upper right corner of the first icon, and the second state includes no checkmark displayed in the upper right corner of the first icon.
[0160] In some embodiments, the first triggering condition includes at least one of the following: the first application ends video playback; the first application exits navigation mode; the first application ends real-time call; the state change of the first application from running in the foreground to running in the background meets a preset condition.
[0161] In some embodiments, the first triggering condition includes the first application ending video playback. That is, when the system detects that the first application has switched from video playback state to non-video playback state, it determines that the first application card does not need to be displayed on the first desktop. Keeping the first application card displayed on the first desktop may cause space redundancy.
[0162] In some embodiments, the first triggering condition includes the first application ending a real-time call. That is, when the first application (such as a communication application) ends a voice or video call or the voice or video call is hung up, the system determines that it is not necessary to view communication-related information or perform communication-related operations at any time, and the first application card does not need to be displayed on the first desktop.
[0163] In some embodiments, the first triggering condition includes a state change where the first application switches from running in the foreground to running in the background, which satisfies a preset condition. This preset condition includes, but is not limited to, at least one of the following: the user actively switches to another application, or the current application does not require a high-priority task to be continuously displayed in the foreground.
[0164] In this application, the first icon has different first and second states to distinguish whether the first application corresponding to the first icon is displayed on the first desktop. When the first application card is not displayed on the first desktop, the first icon is in the first state; when the first application card is displayed on the first desktop, the first icon is in the second state.
[0165] This application does not limit the specific implementation of distinguishing between the first state and the second state. For example, the first icon being in the first state includes the display of a first identifier in the upper right corner of the first icon, and the first icon being in the second state includes the first icon not displaying the first identifier in the upper right corner of the first icon. The first identifier is a checkmark displayed in the upper right corner of the first icon.
[0166] In embodiments of “3. In response to a trigger operation on a second control on a first program card, change the display state of the first icon.” and / or “4. When the display state of the first program card changes, change the display state of the first icon.”, when the first program card is in a de-display state, the second program card adjacent to the first program card moves to the original position of the first program card.
[0167] The original location of the second program card is on the first desktop or on a second desktop adjacent to the first desktop.
[0168] 5. In response to a trigger operation on the first icon, change the display state of the first program card.
[0169] Figure 16 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown.
[0170] In some embodiments, in response to a trigger operation on a first icon, changing the display state of a first application card of a first application includes: Step 233: Determine whether the first icon is in the first state.
[0171] If the first icon is in the first state, proceed to step 234; if the first icon is not in the first state, proceed to step 235. Step 234: In response to the fourth trigger operation on the first icon, switch the display state of the first icon from the first state to the second state, and switch the first application card of the first application from the currently displayed state to the canceled display state; Step 235: In response to the fifth trigger operation on the first icon, switch the display state of the first icon from the second state to the first state, and restore the first application card of the first application from the canceled display state to the displayed state.
[0172] In some embodiments, in response to a fourth trigger operation on the first icon, switching the display state of the first icon from a first state to a second state, and switching the first application card of the first application from a currently displayed state to a canceled display state, includes: In response to a fourth click on the first icon, such as Figure 13 As shown, the display state of the first icon is switched from the first state to the second state; and the size of the first program card in the currently displayed state is proportionally reduced until the first program card is in the undisplayed state; The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0173] For example, such as Figure 17 As shown, in response to the fourth trigger operation for the first icon "Application 4", the display state of the first icon "Application 4" is switched from the first state to the second state, and the size of the first application card "Application Card 4" which is currently being displayed is proportionally reduced until the first application card "Application Card 4" of the first application is in the undisplayed state.
[0174] The first state includes a checkmark displayed in the upper right corner of the first icon, and the second state includes no checkmark displayed in the upper right corner of the first icon.
[0175] In some embodiments, in response to a fifth trigger operation on the first icon, switching the display state of the first icon from a second state to a first state, and restoring the first application card of the first application from a canceled display state to a currently displayed state, includes: In response to the fifth click on the first icon, the display state of the first icon is switched from the second state to the first state, and the first application card is added to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0176] For example, such as Figure 18 As shown, in response to the fifth triggered action for the first icon "Application 4", as Figure 19 As shown, the display state of the first icon "Application 4" is switched from the second state to the first state, and the first program card "Program Card 4", which is currently being displayed, is added to the far right of the first desktop.
[0177] The first state includes a checkmark displayed in the upper right corner of the first icon, and the second state includes no checkmark displayed in the upper right corner of the first icon.
[0178] In some embodiments, the fourth triggering operation includes a fourth click operation, and the fourth triggering operation includes a fifth click operation.
[0179] The fourth click operation can be implemented as follows: after the user touches the first icon on the screen in the first state with their finger and immediately releases their finger, in response to the click operation on the first icon in the first state, the display state of the first icon is switched from the first state to the second state, and the first program card of the first application corresponding to the first icon is deleted on the first area of the first desktop. Optionally, the fourth click operation can also be implemented as follows: without touching the screen, the user points to the location of the first icon in the first state on the screen with their finger. When the first icon in the first state on the screen appears as a selected icon, the user slightly shakes their finger to switch the display state of the first icon from the first state to the second state, and deletes the first program card of the first application corresponding to the first icon on the first area of the first desktop. There are no restrictions on the way the user touches the screen or the way the user points to the screen.
[0180] The fifth click operation can be implemented as follows: after the user touches the first icon on the screen in the second state with their finger and immediately releases their finger, in response to the click operation on the first icon in the second state, the display state of the first icon is switched from the second state to the first state, and the first program card of the first application corresponding to the first icon is added to the first area on the first desktop. Optionally, the fifth click operation can also be implemented as follows: without touching the screen, the user points to the location of the first icon in the second state on the screen with their finger. When the first icon in the second state on the screen appears as a selected icon, the user slightly shakes their finger to switch the display state of the first icon from the second state to the first state, and adds the first application card of the first application corresponding to the first icon to the first area on the first desktop. There are no restrictions on the way the user touches the screen or the way the user points to the screen.
[0181] This application does not limit the specific implementation method of adding the first program card. For example, in response to the fifth click operation of the first icon, the first program card slides out from top to bottom or from bottom to top, or the size of the first program card gradually increases and is displayed in the first area of the first desktop.
[0182] 6. The display state of the first icon changes, thus changing the display state of the first program card.
[0183] Figure 20 A flowchart illustrating a human-computer interaction method for a cockpit display screen provided in an exemplary embodiment of this application is shown.
[0184] In some embodiments, when the display state of the first icon of the first application changes, changing the display state of the first application card of the first application includes: Step 233: Determine whether the first icon is in the first state.
[0185] If the first icon is in the first state, proceed to step 236; if the first icon is not in the first state, proceed to step 237.
[0186] Step 236: If the running state of the first application meets the second triggering condition, switch the display state of the first icon from the first state to the second state, and switch the first application card of the first application from the currently displayed state to the canceled display state; or, Step 237: When the running state of the first application meets the third triggering condition, switch the display state of the first icon from the second state to the first state, and switch the first program card of the first application from the canceled display state to the displaying state.
[0187] The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0188] In some embodiments, when the running state of the first application meets the second triggering condition, switching the display state of the first icon from the first state to the second state, and switching the first application card of the first application from the currently displayed state to the canceled display state, includes: If the current working state does not support the first icon to be displayed in the first state, switch the display state of the first icon from the first state to the second state, and proportionally reduce the size of the first program card that is currently being displayed until the first program card is in the undisplayed state.
[0189] The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0190] For example, if the current working state does not support the display state of the first icon being in the first state, the display state of the first icon "Application 4" is switched from the first state to the second state, and the size of the first application card "Application Card 4" which is currently being displayed is proportionally reduced until the first application card "Application Card 4" of the first application is in the undisplayed state.
[0191] The first state includes a checkmark displayed in the upper right corner of the first icon, and the second state includes no checkmark displayed in the upper right corner of the first icon.
[0192] In some embodiments, the second triggering condition includes at least one of the following: the first application ends video playback; the first application exits navigation mode; the first application ends real-time call; the state change of the first application from running in the foreground to running in the background meets a preset condition.
[0193] In some embodiments, the second triggering condition includes the first application ending video playback. That is, when the system detects that the first application has switched from video playback state to non-video playback state, it determines that the first application card does not need to be displayed on the first desktop. Keeping the first application card displayed on the first desktop may cause space redundancy.
[0194] In some embodiments, the second triggering condition includes the first application ending a real-time call. That is, when the first application (such as a communication application) ends a voice or video call or the voice or video call is hung up, the system determines that it is not necessary to view communication-related information or perform communication-related operations at any time, and the first application card does not need to be displayed on the first desktop.
[0195] In some embodiments, the second triggering condition includes a state change where the first application switches from running in the foreground to running in the background, which satisfies a preset condition. This preset condition includes, but is not limited to, at least one of the following: the user actively switches to another application, or the current application does not require a high-priority task to be continuously displayed in the foreground.
[0196] When the display state of the first icon changes, the display state of the first program card will automatically change, which can reduce visual interference, reduce driving safety risks, automatically delete invalid and low-frequency program cards, reduce redundant information on the screen, make important function program cards stand out, release system resources, improve the smoothness of vehicle system operation, and improve interaction efficiency.
[0197] In some embodiments, when the running state of the first application meets a third triggering condition, switching the display state of the first icon from the second state to the first state, and switching the first application card of the first application from the canceled display state to the currently displayed state, includes: If the current working state does not support the display state of the first icon being in the second state, switch the display state of the first icon from the second state to the first state, and add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0198] For example, if the current working state does not support the display state of the first icon being in the second state, the display state of the first icon "Application 4" is switched from the second state to the first state, and the first program card "Program Card 4" which is currently being displayed is added to the far right of the first desktop.
[0199] The first state includes a checkmark displayed in the upper right corner of the first icon, and the second state includes no checkmark displayed in the upper right corner of the first icon.
[0200] In some embodiments, the third triggering condition includes the first application playing a video. That is, when the system detects that the first application has switched from a non-video playback state to a video playback state, it determines that the first application card needs to be added to the first desktop so that video-related information and / or the first application operation entry can be quickly found later.
[0201] In some embodiments, the third triggering condition includes the first application entering navigation mode. That is, when the first application switches from route planning and location search to real-time navigation guidance mode, the system determines that the first application card needs to be added to the first desktop so that the route display, intersection magnification map and traffic information, and / or the first application operation entry can be quickly found later.
[0202] In some embodiments, the third triggering condition includes the first application receiving a real-time call request. That is, when the first application (such as a communication application) receives a call request for a voice or video call, the system determines that the first application card needs to be added to the first desktop so that the caller's information can be quickly found later, and / or the first application's operation entry point.
[0203] In some embodiments, the third triggering condition includes a state change where the first application switches from running in the background to running in the foreground that meets a preset condition. This preset condition includes, but is not limited to, at least one of the following: the application is activated by an important notification; the application is launched directly by the user via an icon or other shortcut; or the task being performed in the background by the application has a high priority and requires foreground monitoring.
[0204] In this application, in response to a trigger operation on the first icon, the display state of the first program card is changed. During driving, without leaving the first desktop, the first program card can be added to the first desktop simply by performing a fifth trigger operation on the first icon or changing the display state of the first icon. This shortens the operation time, avoids reduced efficiency due to hidden multi-level menus, reduces driving safety risks, reduces system response pressure, and minimizes the impact of lag.
[0205] In this application, any one of the following can be implemented individually as an embodiment of a human-computer interaction method for a cockpit display screen; or, the above embodiments can be combined to jointly implement an embodiment of a human-computer interaction method for a cockpit display screen.
[0206] In this application, all names of modes, areas, interfaces, and related prompts are examples. This application uses the desktops of various screens in a vehicle cabin as examples for illustration. The application scenarios of this application are not limited to the field of intelligent vehicles.
[0207] In summary, the first layout of the first desktop is switched to a second layout, which includes a first area and a second area. The first area displays program cards for n applications, and the second area displays icons for m applications. The system controls the linkage between the first program card and the first icon of the first application. Without leaving the first desktop, program cards of the first application can be automatically added or deleted in response to trigger operations on the first icon. This reduces the user's extra operations, solves the problem of cumbersome and inefficient operation caused by multi-level human-computer interaction, improves the correlation between various functional areas of the system, enhances operational efficiency and ease of use, and reduces the failure rate of functional operations.
[0208] Figure 21 A flowchart illustrating a human-computer interaction method for a cockpit display screen according to an exemplary embodiment of this application is shown. The steps of the method are as follows: Step 1: Display the first layout of the first desktop. The first layout includes a first area and multiple controls, including the first control.
[0209] In some embodiments, the first control is located in the lower left corner of the first desktop and is used to enable entry into the editable state of the first desktop and / or change the layout of the first desktop.
[0210] In some embodiments, the editable state of the first desktop is a state in which program cards of n applications switch between a currently displayed state and a canceled display state, and / or a state in which icons of m applications switch between a first state and a second state. It can also be understood as a state in which a delete button appears in the upper right corner of the program cards of n applications in the first area, and at the same time, a first identifier appears in the upper right corner of the icons of n applications in the second area.
[0211] Step 2: In response to the first trigger operation on the first control, switch the first layout to the second layout.
[0212] In some embodiments, such as Figure 3 As shown, the first desktop is displayed. At this time, the first desktop only has a first area and multiple controls. The first area includes application cards for n applications, and the multiple controls include the first control. Figure 3 As shown, in response to a first click operation on the first control, the layout of the first desktop is changed by shifting the first area upwards and simultaneously reducing the size of the application cards of n applications in the first area to display a second area. In the second area, application cards of m applications are displayed. For example, the second area can be expanded to display all applications in the system that support displaying application cards on the first desktop, and widgets of q applications are displayed above the application cards of the n applications.
[0213] For a detailed description of the first trigger operation, please refer to "1. In response to the first trigger operation on the first control, switch the first layout of the first desktop to the second layout." It will not be repeated here.
[0214] Step 3: Determine whether to execute the third trigger operation on the second control on the first program card.
[0215] If a third trigger operation is performed on the second control on the first program card, proceed to step 4; if no third trigger operation is performed on the first program card, proceed to step 5.
[0216] For a detailed description of the third trigger operation, please refer to "3. In response to the trigger operation of the second control on the first program card, change the display state of the first icon." It will not be repeated here.
[0217] Step 4: Switch the first application card of the first application from the currently displayed state to the undisplayed state, and switch the display state of the first icon from the first state to the second state.
[0218] For details regarding the switching of the first application card from the currently displayed state to the undisplayed state, and the switching of the display state of the first icon from the first state to the second state, please refer to "3. In response to a trigger operation on the second control on the first application card, change the display state of the first icon." These details will not be repeated here.
[0219] Step 5: Determine whether the first program card meets the first trigger condition.
[0220] If the first program card meets the first trigger condition, proceed to step 4; if the first program card does not meet the first trigger condition, proceed to step 6.
[0221] For a detailed description of the first triggering condition, please refer to "4. When the display state of the first program card changes, change the display state of the first icon." It will not be repeated here.
[0222] Step 6: Determine if the first icon is in the first state.
[0223] If the first icon is in the first state, proceed to step 7; if the first icon is not in the first state, proceed to step 8.
[0224] In this application, when the first icon is not in the first state, it is in the second state. The first state and the second state of the first icon are different, used to distinguish whether the first application corresponding to the first icon is displayed on the first desktop. When the first application's first application card is not displayed on the first desktop, the first icon is in the first state; when the first application's first application card is displayed on the first desktop, the first icon is in the second state.
[0225] This application does not limit the specific implementation of distinguishing between the first state and the second state. For example, the first icon being in the first state includes the display of a first identifier in the upper right corner of the first icon, and the first icon being in the second state includes the first icon not displaying the first identifier in the upper right corner of the first icon. The first identifier is a checkmark mark existing within a square frame displayed in the upper right corner of the first icon.
[0226] Step 7: Determine whether to execute the fourth trigger operation on the first icon.
[0227] If the fourth trigger operation is performed on the first icon, proceed to step 4; if the fourth trigger operation is not performed on the first icon, proceed to step 9.
[0228] For a detailed description of performing the fourth trigger operation on the first icon of the first application, please refer to "5. In response to the trigger operation on the first icon, change the display state of the first application card." It will not be repeated here.
[0229] Step 8: Determine whether to execute the fifth trigger operation on the first icon.
[0230] If the fifth trigger operation is performed on the first icon, proceed to step 11; if the fifth trigger operation is not performed on the first icon, proceed to step 12.
[0231] For a detailed description of performing the fifth trigger operation on the first icon of the first application, please refer to "5. In response to the trigger operation on the first icon, change the display state of the first application card." It will not be repeated here.
[0232] Step 9: Determine if the first icon meets the second trigger condition.
[0233] If the second triggering condition is met, proceed to step 4; if the second triggering condition is not met, proceed to step 10.
[0234] For a detailed description of the second triggering condition, please refer to "6. The display state of the first icon changes, thus changing the display state of the first program card." It will not be repeated here.
[0235] Step 10: In response to the second trigger operation on the first control, switch the second layout to the first layout.
[0236] For a detailed description of the second trigger operation, please refer to "2. In response to the second trigger operation on the first control, switch the second layout of the first desktop to the first layout." It will not be repeated here.
[0237] Step 11: Switch the display state of the first icon from the second state to the first state, and switch the first application card of the first application from the canceled display state to the currently displayed state.
[0238] Step 12: Determine whether the first icon meets the third trigger condition.
[0239] If the first icon of the first application meets the third trigger condition, proceed to step 11; if the first icon of the first application does not meet the third trigger condition, proceed to step 10.
[0240] For a detailed description of the fifth trigger condition, please refer to "6. The display state of the first icon changes, thus changing the display state of the first program card." It will not be repeated here.
[0241] In the above flowchart, the numbers in each step are used to uniquely identify and reference each step, and do not represent any time order, logical sequence or importance level. For example, the judgment steps of steps 3, 5 and 6 can be performed simultaneously, and the judgment steps of steps 8 and 12 can be performed simultaneously. There is no sequential relationship between the judgment steps, and this application embodiment does not impose any restrictions on this.
[0242] Figure 22 A block diagram of a human-machine interface device 2200 for a cockpit display screen provided in an exemplary embodiment of this application is shown. The in-vehicle display device 2200 includes a display module 2210 and a control module 2220.
[0243] Display module 2210 is used to display a first layout of a first desktop. The first layout includes a first area and multiple controls, among which the first control is included.
[0244] The first desktop is a desktop with program cards on the screen of the in-vehicle display device, also known as a card-style desktop. The screen of the in-vehicle display device includes one or more screen carriers such as the central control screen, passenger entertainment screen, rear entertainment screen, sliding screen, magic control screen, and central touch screen.
[0245] On in-vehicle display screens, a card-based desktop is a main screen interface or system default user interface adapted to in-vehicle driving scenarios, using application cards as the primary interaction module. The card-based desktop transforms individual in-vehicle applications or functions into independent visual application cards, presented on the screen through a segmented layout. It supports customizing the position, combination, and addition / removal of application cards, directly displaying dynamic information about the corresponding functions of the application, and providing entry points for one or more operations / functions within the application card. For example, switching tracks in a music application card or viewing the remaining trip in a navigation application card can be done without entering the full application interface, thereby improving the convenience of operation and the intuitiveness of information acquisition during driving, and meeting the safety interaction needs while driving.
[0246] The control module 2220 is also configured to switch the first layout to a second layout in response to a first trigger operation on the first control. The second layout includes a first area and a second area, wherein the first area is used to display program cards of n applications and the second area is used to display icons of m applications.
[0247] In some embodiments, when the first desktop is in the second layout, the first desktop is in an editable state. The editable state of the first desktop is a state in which program cards of n applications switch between a currently displayed state and a canceled display state, and / or a state in which icons of m applications switch between a first state and a second state. It can also be understood as a state in which a delete button appears in the upper right corner of the program cards of n applications in the first area, and at the same time, a first identifier appears in the upper right corner of the icons of n applications in the second area.
[0248] like Figure 4 As shown, the first desktop includes a first area 410 and a second area 420. The first area 410 is located above or below the second area 420. The first area 410 is used to display program cards of n applications, and the second area 420 is used to display icons of m applications. The n applications and the m applications may or may not overlap.
[0249] The types of the n and / or m applications include: navigation and positioning applications, which meet the route guidance needs while driving; audio-visual entertainment applications, which provide users with auditory and visual entertainment; vehicle control and diagnostic applications, which directly connect to vehicle hardware to monitor vehicle conditions and ensure normal vehicle operation; interconnection and interaction applications, which break down device barriers and enable the vehicle to interact with other devices and scenarios, including mobile phone-vehicle interconnection programs and / or vehicle-home interconnection programs; system tools and personalization applications, which provide download and management of various applications, optimize the vehicle user experience, and / or enable personalized customization; and communication and collaboration applications, which support voice-controlled calling functions and / or synchronize mobile phone contacts and call logs for seamless integration.
[0250] In some embodiments, the second area is used to display icons of m applications, including: displaying icons of all or some applications in the system in the second area according to user usage frequency or system preset order.
[0251] Optionally, in the second area, icons corresponding to one or more program cards on the first desktop are displayed according to the user's usage frequency or a system preset order. For example, there are three desktops, each displaying three program cards, and nine icons corresponding to these nine program cards are displayed in the second area.
[0252] Optionally, the icon order can be preset based on driving operation convenience. Alternatively, the icon order can be preset by taking into account the driver's operating posture and touch range, and / or by following the relevance of functions and the logic of usage scenarios.
[0253] The control module 2220 is used to control the linkage between the first program card and the first icon of the first application.
[0254] Wherein, the application cards of n applications include a first application card; and / or, the icons of m applications include a first icon, where n and m are both positive integers. In some embodiments, the first application card is in a first area, and the first icon is in the display area of a second area, or is folded under the second area.
[0255] The linkage between the first program card and the first icon refers to the synchronized response between them in terms of function, information, and operation, achieving interoperability and information sharing to meet the safety and convenience requirements of in-vehicle scenarios. The linkage includes bidirectional synchronization of operations; when an operation is performed on the first program card or the first icon, a corresponding response will appear on the other side; and real-time synchronized display of information, where the first program card will synchronize the dynamic information of the application associated with its corresponding first icon in real time, allowing users to intuitively access content without entering the application.
[0256] In this application, the linkage between the first program card and the first icon mainly includes changing the display state of the first program card or performing an operation on the first program card, and the display state of the first icon performing a corresponding response feedback, and / or changing the display state of the first icon or performing an operation on the first icon, and the display state of the first program card performing a corresponding response feedback.
[0257] In this application, the display state of the first program card includes a displaying state and a canceled display state, and the display state of the first icon includes a first state and a second state.
[0258] The states are as follows: the first program card is displayed on the first desktop; the state of being canceled is that the first program card is not displayed on the first desktop; the first state includes the first icon displaying the first identifier; and the second state includes the first icon not displaying the first identifier.
[0259] Optionally, the first identifier is a checkmark displayed in the upper right corner of the first icon. This application does not limit the implementation of the first identifier, as long as it supports distinguishing the two states of the first icon.
[0260] In some embodiments, such as Figure 4 As shown, the operation performed on the first icon "Application 4" includes a click operation. The click operation can be implemented as follows: after the user touches the first icon "Application 4" on the screen with their finger and immediately releases it, in response to the click operation on the first icon "Application 4", the display state of the first icon "Application 4" is changed, and according to the display state of the first icon "Application 4", the corresponding operation is performed on the first program card "Program Card 4".
[0261] For example, when a user touches the first icon "App 4" on the screen and immediately releases their finger, in response to the click operation on the first icon "App 4", the check mark in the upper right corner of the first icon "App 4" disappears, and the first application card "Application Card 4" is deleted.
[0262] In some embodiments, such as Figure 5 As shown, the operations performed on the first program card "program card 4" include a click operation. The click operation can be implemented as follows: the user touches a designated position on the first program card "program card 4" on the screen and immediately releases his / her finger. For example, the user touches the delete key on the first program card "program card 4" and immediately releases his / her finger. In response to the click operation on the first program card "program card 4", the display state of the first program card "program card 4" is changed, and the corresponding operation is performed on the first icon according to the display state of the first program card.
[0263] For example, when a user touches the delete button on the first application card "Application Card 4" and immediately releases their finger, the first application card "Application Card 4" is deleted in response to the click operation on the first application card "Application Card 4", and the check mark in the upper right corner of the first icon "Application 4" disappears.
[0264] Optionally, if the in-vehicle display supports floating touch, the click operation can also be implemented as follows: the user does not touch the screen, but points to a designated location on the first program card on the screen with their finger. When a selection mark appears at the designated location on the first program card, the user slightly shakes their finger to change the display state of the first program card. Based on the display state of the first program card, the user performs the corresponding operation on the first icon. There are no restrictions on the way the user touches the screen or the way the user points to the screen.
[0265] For example, when the in-vehicle display supports floating touch, the user does not touch the screen. The user points to the delete key on the first program card with their finger. When the delete key on the first program card is selected, the user shakes their finger slightly to delete the first program card "Program Card 4". The check mark in the upper right corner of the first icon "Application 4" disappears.
[0266] In some optional designs, the control module is also used to switch the first layout to a second layout in response to a first trigger operation on the first control, including: In response to a first trigger operation on the first control, the first area is shifted upwards and the second area is displayed below the first area; or, the first area is shifted downwards and the second area is displayed above the first area.
[0267] In some optional designs, the control module is also used to, in response to a first trigger operation on the first control, scale down the program card size of n applications in the first area from a first size to a second size that does not overlap with the second area.
[0268] In some optional designs, the control module is also used to display q application components above the first area in response to a first trigger operation on the first control, where q is a positive integer.
[0269] In some embodiments, the control module 2220 is further configured to switch the second layout to the first layout in response to a second trigger operation on the first control.
[0270] In some embodiments, the control module 2220 is further configured to switch the second area to a canceled display state in response to a second trigger operation on the first control.
[0271] In some embodiments, the size of the application cards of n applications in the second layout is a second size, and the control module 2220 is further configured to restore the size of the application cards of n applications in the first area from the second size to the first size in response to a second trigger operation on the first control.
[0272] In some embodiments, the second layout also displays components of q applications, and the control module 2220 is further configured to cancel the display of components of q applications in response to a second trigger operation on the first control.
[0273] In some embodiments, the control module 2220 is further configured to display a second control on the program card of at least one of the program cards of n applications in the first region in response to a first trigger operation on the first control.
[0274] In some embodiments, the control module 2220 is further configured to change the display state of the first icon of the first application when the display state of the first application card of the first application changes, and / or, in response to a triggering operation on the second control on the first application card.
[0275] In some embodiments, the control module 2220 is further configured to change the display state of the first program card of the first application when the display state of the first icon of the first application changes, and / or, in response to a triggering operation on the first icon.
[0276] In some embodiments, the control module 2220 is further configured to, in response to a third trigger operation on the second control, switch the first application card of the first application from a displaying state to a canceled display state, and switch the display state of the first icon from a first state to a second state. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0277] In some embodiments, the control module 2220 is further configured to, when the running state of the first application meets the first triggering condition, switch the first program card of the first application from the displaying state to the canceled display state, and switch the display state of the first icon from the first state to the second state. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0278] In some embodiments, the control module 2220 is further configured to, in response to a fourth trigger operation on the first icon, switch the display state of the first icon from a first state to a second state, and switch the first application card of the first application from a currently displayed state to a canceled display state. And / or, The control module 2220 is also configured to, in response to a fifth trigger operation on the first icon, switch the display state of the first icon from a second state to a first state, and restore the first application card of the first application from a canceled display state to a currently displayed state.
[0279] In some embodiments, the control module 2220 is further configured to, when the running state of the first application meets the second triggering condition, switch the display state of the first icon from the first state to the second state, and switch the first application card of the first application from the currently displayed state to the canceled display state; or, The control module 2220 is also used to switch the display state of the first icon from the second state to the first state and switch the first program card of the first application from the canceled display state to the displaying state when the running state of the first application meets the third triggering condition. The first state indicates that the first program card is in the display state, and the second state indicates that the first program card is in the cancel display state.
[0280] In some embodiments, the control module 2220 is further configured to, in response to a third click operation on the first program card, proportionally reduce the size of the first program card in the display state until the first program card is in the canceled display state, and switch the display state of the first icon from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0281] In some embodiments, the control module 2220 is further configured to, when the current working state does not support the first program card of the first application being displayed, proportionally reduce the size of the first program card in the display state until the first program card of the first application is in the undisplayed state, and switch the display state of the first icon from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0282] In some embodiments, the control module 2220 is further configured to, in response to a fourth click operation on the first icon, switch the display state of the first icon from a first state to a second state; and proportionally reduce the size of the first program card in the currently displayed state until the first program card is in the undisplayed state; The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0283] In some embodiments, the control module 2220 is further configured to, in response to a fifth click operation on the first icon, switch the display state of the first icon from a second state to a first state, and add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0284] In some embodiments, the control module 2220 is further configured to switch the display state of the first icon from the first state to the second state when the current working state does not support the display state of the first icon being the first state, and to proportionally reduce the size of the first program card in the display state until the first program card is in the canceled display state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0285] In some embodiments, the control module 2220 is further configured to switch the display state of the first icon from the second state to the first state when the current working state does not support the display state of the first icon being the second state, and to add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
[0286] In some embodiments, the display module 2210 is further configured to display icons of all or some applications in the system within a second area according to usage frequency or a system preset order.
[0287] In some embodiments, the control module 2220 is further configured to move a second program card adjacent to the first program card to the original position of the first program card when the first program card is in a canceled display state; In this embodiment, the original position of the second program card is located on the first desktop or on a second desktop adjacent to the first desktop. In some embodiments, the relevant content of the specific cockpit display screen human-computer interaction method refers to the following in the above method-side embodiments: "1. In response to a first trigger operation on the first control, switch the first layout of the first desktop to the second layout." and / or, "2. In response to a second trigger operation on the first control, switch the second layout of the first desktop to the first layout." and / or, "3. In response to a trigger operation on the second control on the first program card, change the display state of the first icon." and / or, "4. When the display state of the first program card changes, change the display state of the first icon." and / or, "5. In response to a trigger operation on the first icon, change the display state of the first program card." and / or, "6. When the display state of the first icon changes, change the display state of the first program card." and / or, Figures 2 to 20 The content in [the document / article].
[0288] In summary, the first layout of the first desktop is switched to a second layout, which includes a first area and a second area. The first area displays program cards for n applications, and the second area displays icons for m applications. The system controls the linkage between the first program card and the first icon of the first application. Without leaving the first desktop, program cards of the first application can be automatically added or deleted in response to trigger operations on the first icon. This reduces the user's extra operations, solves the problem of cumbersome and inefficient operation caused by multi-level human-computer interaction, improves the correlation between various functional areas of the system, enhances operational efficiency and ease of use, and reduces the failure rate of functional operations.
[0289] It should be noted that the specific limitations of the human-machine interaction device embodiments of the above-mentioned in-vehicle display screen can be found in the limitations of the human-machine interaction method for the cockpit display screen above, and will not be repeated here. Each module of the above-mentioned device can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in the processor of the computer device in hardware form or independent of the processor, or it can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.
[0290] Figure 23This illustration shows a schematic diagram of a human-machine interface device (HMI) for a cockpit display screen provided in an exemplary embodiment of this application. The HMI 2300 for the display screen can be used to execute the method steps described in the above embodiments. The HMI 2300 for the display screen includes: a processor 2301, an input / output device 2302, a memory 2303, and a touchscreen 2304.
[0291] The processor 2301 includes one or more processing cores. The processor 2301 executes various functional applications and information processing by running software programs and modules.
[0292] The memory 2303 can be connected to the processor 2301 and the input / output device 2302.
[0293] The memory 2303 can be used to store a computer program executed by the processor, and the processor 2301 is used to execute the computer program to implement the various steps in the above method embodiments.
[0294] Furthermore, the memory 2303 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.
[0295] For details not described in this embodiment, please refer to the method-side embodiment above, which will not be repeated here.
[0296] This application also provides a computer-readable storage medium storing a computer program for execution by a processor to implement the human-computer interaction method of the cockpit display screen executed by the aforementioned computer device. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).
[0297] This application also provides a chip, which includes programmable logic circuits and / or program instructions, and when the chip is running, it is used to implement the human-computer interaction method of the cockpit display screen described above.
[0298] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. The processor reads and executes the computer program from the computer-readable storage medium to implement the human-computer interaction method of the cockpit display screen described above.
[0299] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0300] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.
[0301] In some embodiments of this application, "predefined" can be achieved by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including sensing signal receiving nodes and sensing signal transmitting nodes). This application does not limit the illustrative implementation method. For example, "predefined" can refer to what is defined in the protocol.
[0302] In some embodiments of this application, "protocol" may refer to standard protocols in the field of communications, such as LTE protocol, NR protocol and related protocols applied to future communication systems, and this application does not limit it.
[0303] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0304] In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.
[0305] Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.
[0306] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.
[0307] The above are merely exemplary embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application shall be included within the protection scope of this application.
Claims
1. A human-computer interaction method for a cockpit display screen, characterized in that, The method includes: A first layout of a first desktop is displayed, the first layout including a first area and multiple controls, the multiple controls including a first control; In response to a first trigger operation on the first control, the first layout is switched to a second layout, the second layout including a first area and a second area, the first area being used to display program cards of n applications, and the second area being used to display icons of m applications; the first program card of the first application and the first icon of the first application are linked together. Wherein, the program cards of the n applications include the first program card; and / or, the icons of the m applications include the first icon, where n and m are both positive integers.
2. The method according to claim 1, characterized in that, The step of switching the first layout to the second layout in response to a first trigger operation on the first control includes: In response to a first trigger operation on the first control, the first area is shifted upwards and the second area is displayed below the first area; or, the first area is shifted downwards and the second area is displayed above the first area.
3. The method according to claim 1 or 2, characterized in that, The method further includes: In response to a first trigger operation on the first control, the size of the application cards of the n applications in the first region is proportionally reduced from a first size to a second size that does not overlap with the second region.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: in response to a first trigger operation on the first control, displaying q application components above the first area, where q is a positive integer.
5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: In response to a second trigger operation on the first control, the second layout is switched to the first layout.
6. The method according to claim 5, characterized in that, The step of switching the second layout to the first layout in response to a second trigger operation on the first control includes: In response to the second trigger operation on the first control, the second area is switched to a canceled display state.
7. The method according to claim 5 or 6, characterized in that, The program cards of the n applications are sized to the second size in the second layout; the method further includes: In response to the second trigger operation for the first control, the size of the application cards of the n applications in the first region is restored from the second size to the first size.
8. The method according to any one of claims 5 to 7, characterized in that, The second layout also displays q application components; the method further includes: In response to the second trigger operation on the first control, the display of components of the q applications is cancelled.
9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: In response to the first trigger operation for the first control, a second control is displayed on the application card of at least one of the n applications in the first region.
10. The method according to any one of claims 1 to 9, characterized in that, The linkage between the first application card and the first icon of the first application includes: When the display state of the first application card of the first application changes, and / or, in response to a triggering operation on the second control on the first application card, the display state of the first icon of the first application is changed.
11. The method according to any one of claims 1 to 9, characterized in that, The linkage between the first application card and the first icon of the first application includes: When the display state of the first icon of the first application changes, and / or, in response to a triggering operation on the first icon, the display state of the first program card of the first application is changed.
12. The method according to claim 10, characterized in that, The step of changing the display state of the first icon of the first application in response to a trigger operation on the second control on the first application card includes: In response to a third trigger operation on the second control, the first application card of the first application is switched from being displayed to being canceled, and the display state of the first icon is switched from a first state to a second state; Wherein, the first state is used to indicate that the first program card is in the displaying state, and the second state is used to indicate that the first program card is in the canceled display state.
13. The method according to claim 10, characterized in that, The step of changing the display state of the first icon of the first application when the display state of the first application card of the first application changes includes: When the running state of the first application meets the first triggering condition, the first program card of the first application is switched from the displaying state to the canceled display state, and the display state of the first icon is switched from the first state to the second state. Wherein, the first state is used to indicate that the first program card is in the displaying state, and the second state is used to indicate that the first program card is in the canceled display state.
14. The method according to claim 11, characterized in that, The step of changing the display state of the first application card of the first application in response to a trigger operation on the first icon includes: In response to a fourth trigger operation on the first icon, the display state of the first icon is switched from a first state to a second state, and the first application card of the first application is switched from a currently displayed state to a canceled display state. And / or, In response to a fifth trigger operation on the first icon, the display state of the first icon is switched from the second state to the first state, and the first application card of the first application is restored from the canceled display state to the currently displayed state.
15. The method according to claim 11, characterized in that, The step of changing the display state of the first application card when the display state of the first icon of the first application changes includes: When the running state of the first application meets the second triggering condition, the display state of the first icon is switched from the first state to the second state, and the first application card of the first application is switched from the currently displayed state to the canceled display state; or, When the running state of the first application meets the third triggering condition, the display state of the first icon is switched from the second state to the first state, and the first program card of the first application is switched from the canceled display state to the displaying state. Wherein, the first state is used to indicate that the first program card is in the display state, and the second state is used to indicate that the first program card is in the cancel display state.
16. The method according to claim 12, characterized in that, The response to the third trigger operation on the second control, switching the first application card of the first application from a currently displayed state to a canceled display state, and switching the display state of the first icon from a first state to a second state, includes: In response to a third click operation on the first program card, the size of the first program card in the display state is proportionally reduced until the first program card is in the undisplayed state, and the display state of the first icon is switched from the first state to the second state; The first state includes the first icon displaying a first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
17. The method according to claim 13, characterized in that, When the running state of the first application meets the first trigger condition, switching the first application card of the first application from the currently displayed state to the canceled display state, and switching the display state of the first icon from the first state to the second state, includes: If the current working state does not support the first application card of the first application being displayed, the size of the first application card that is being displayed will be reduced proportionally until the first application card of the first application is de-displayed, and the display state of the first icon will be switched from the first state to the second state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
18. The method according to claim 14, characterized in that, The step of responding to a fourth trigger operation on the first icon by switching the display state of the first icon from a first state to a second state, and switching the first application card of the first application from a currently displayed state to a canceled display state, includes: In response to a fourth click operation on the first icon, the display state of the first icon is switched from a first state to a second state; and the size of the first program card in the currently displayed state is proportionally reduced until the first program card is in the undisplayed state; The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
19. The method according to claim 14, characterized in that, The step of responding to a fifth trigger operation on the first icon by switching the display state of the first icon from a second state to a first state, and restoring the first application card of the first application from the canceled display state to the currently displayed state, includes: In response to a fifth click on the first icon, the display state of the first icon is switched from the second state to the first state, and the first application card is added to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
20. The method according to claim 15, characterized in that, When the running state of the first application meets the second triggering condition, the display state of the first icon is switched from the first state to the second state, and the first application card of the first application is switched from the currently displayed state to the canceled display state, including: If the current working state does not support the first icon to be displayed in the first state, the display state of the first icon is switched from the first state to the second state, and the size of the first program card that is currently being displayed is proportionally reduced until the first program card is in the undisplayed state. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
21. The method according to claim 15, characterized in that, When the running state of the first application meets the third triggering condition, switching the display state of the first icon from the second state to the first state, and switching the first program card of the first application from the canceled display state to the currently displayed state, includes: If the current working state does not support the display state of the first icon being in the second state, switch the display state of the first icon from the second state to the first state, and add the first program card to the far right of the first desktop. The first state includes the first icon displaying the first identifier in the upper right corner, and the second state includes the first icon not displaying the first identifier in the upper right corner.
22. The method according to any one of claims 1 to 21, characterized in that, The second area is used to display icons for m applications, including: Within the second area, icons of all or some applications in the system are displayed according to usage frequency or a system preset order.
23. The method according to any one of claims 10 to 21, characterized in that, The method further includes: When the first program card is in the canceled display state, the second program card adjacent to the first program card moves to the original position of the first program card; The original location of the second program card is located on the first desktop or on a second desktop adjacent to the first desktop.
24. A human-computer interaction device for a display screen, characterized in that, The apparatus includes modules for implementing the method as described in any one of claims 1 to 23.
25. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the human-computer interaction method for a cockpit display screen as described in any one of claims 1 to 23.
26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is loaded and executed by a processor to implement the human-computer interaction method for a cockpit display screen as described in any one of claims 1 to 23.
27. A computer program product, characterized in that, The computer program product stores a computer program that is loaded and executed by a processor to implement the human-computer interaction method for a cockpit display screen as described in any one of claims 1 to 23.