Application display method and device for in-vehicle interface

Abstract

This application relates to an application display method and apparatus for an in-vehicle interface. The method includes: responding to user operations on various first applications in the in-vehicle interface, determining a usage category label corresponding to each first application; when the vehicle's driving speed is greater than a target driving speed, determining an operation feature corresponding to each first application based on the usage operation; determining a position allocation result of the display area of ​​each first application in the in-vehicle interface based on at least one of the operation features corresponding to each first application, the usage category label, and the vehicle's driving state; and adjusting the current position of the display area of ​​each first application in the in-vehicle interface based on the position allocation result. This application can reasonably allocate display areas for multiple applications on the in-vehicle interface, improving driving safety while reducing user manual intervention.

Description

Technical Field

[0001] This application relates to the field of computer technology, and specifically to an application display method and device for an in-vehicle interface. Background Technology

[0002] Currently, with the continuous improvement of vehicle intelligence and connectivity, the functions of in-vehicle infotainment systems are becoming increasingly rich, and the number of applications that need to run and be displayed simultaneously on the central control screen is also increasing. For example, navigation, music, vehicle settings, and video calls may all be active at the same time. Therefore, how to rationally allocate display positions for multiple applications on the in-vehicle screen to reduce manual user intervention and ensure driving safety is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, and computer-readable storage medium for displaying applications on an in-vehicle interface, which can reasonably allocate display positions for multiple applications on the in-vehicle interface, thereby improving driving safety while reducing manual intervention by the user.

[0004] This application provides an application display method for an in-vehicle interface, the method including: In response to the user's operation on each first application in the vehicle interface, determine the usage category label corresponding to each first application. The first application represents the application that is running in the vehicle interface. When the vehicle's speed is greater than the target speed, the operation characteristics corresponding to each first application are determined based on the usage operation. The operation characteristics include at least one of operation complexity, gaze duration, and operation frequency. Based on at least one of the operation characteristics, usage category tags, and vehicle driving status of each first application, determine the location allocation result of the display area of ​​each first application in the vehicle interface. Based on the location allocation results of the display area, adjust the current display area position of each first application in the vehicle interface.

[0005] Based on the aforementioned technical means, the usage category label is determined in response to the user's operation on the first application. When the vehicle speed is greater than the target speed, operation characteristics such as operation complexity, gaze duration, and operation frequency are further obtained. The display area position of each application in the in-vehicle interface is dynamically allocated by comprehensively considering at least one factor among operation characteristics, usage category label, and vehicle driving status. This allows the layout of the in-vehicle interface to adaptively adjust according to the driving scenario and the user's real-time interaction behavior. In this way, while ensuring driving safety and reducing the driver's cognitive load and gaze deviation time, it also takes into account the user's operational convenience and personalized usage habits for different applications, thereby improving the interactive safety and user experience during driving.

[0006] In some embodiments, the location allocation result of the display area of ​​each first application in the vehicle interface is determined based on at least one of the operation characteristics, usage category tags, and vehicle driving status corresponding to each first application, including: The security level of each first application is determined based on its operational complexity, gaze duration, and operation frequency. Based on at least one of the security level, usage category label, and vehicle driving status corresponding to each first application, the location allocation result of the display area of ​​each first application in the vehicle interface is determined.

[0007] Based on the aforementioned technical means, by quantifying the complexity of operation, gaze duration, and operation frequency into the safety level of the application, and then combining the use of category tags and driving status for location allocation, the in-vehicle interface layout can implement differentiated strategies for applications with different risk levels, achieving a balance between safety and usability, and effectively improving driving safety and interactive experience.

[0008] In some embodiments, the security level of each first application is determined based on its operational complexity, gaze duration, and operation frequency, including: Based on the complexity of the operation, the interaction levels of each first application are classified into three levels: high interaction level, medium interaction level, and low interaction level. The driving attention occupancy coefficient for each primary application is determined based on fixation duration and operation frequency; the driving attention occupancy coefficient is directly proportional to fixation duration and operation frequency. The interaction level and the driver attention occupancy coefficient are weighted and fused to obtain the comprehensive safety coefficient of each primary application; The security level of each primary application is determined based on the comprehensive security factor.

[0009] Based on the aforementioned technical means, by quantifying operational complexity into interaction level, merging gaze duration and operation frequency into driving attention occupancy coefficient, and then weighting and fusing the two to obtain a comprehensive safety coefficient, a comprehensive quantitative assessment of application safety is achieved from two orthogonal dimensions: inherent application risk and real-time attention consumption. This avoids misjudgment based on a single dimension, provides a precise decision-making basis for subsequent differentiated display area allocation, and effectively reduces the risk of driver distraction.

[0010] In some embodiments, the location allocation result of the display area of ​​each first application in the vehicle interface is determined based on at least one of the security level, usage category label, and vehicle driving status corresponding to each first application, including: For each first application, if the security level corresponding to the first application is greater than the preset security level and the vehicle is in driving mode, the location allocation result of the display area of ​​the first application in the vehicle interface is determined based on the usage category label and the preset mapping relationship. If the security level of the first application is less than or equal to the preset security level, and the vehicle is in driving mode, control the first application to be displayed on the vehicle interface as a status bar icon.

[0011] Based on the aforementioned technical means, by introducing a comparison and judgment mechanism between the security level and the preset security level, on the one hand, for applications with a security level greater than the preset security level, it indicates that they pose a relatively small threat to driving safety during high-speed driving. Therefore, they are allowed to be normally allocated display areas according to the usage category label and the preset mapping relationship, ensuring users' normal access needs for commonly used low-risk applications. On the other hand, for applications with a security level less than or equal to the preset security level, it indicates that they may pose a significant threat to driving safety during high-speed driving. In this case, they are forcibly controlled to be displayed as status bar icons, which not only preserves the user's ability to perceive that the application is running, but also effectively avoids accidental touches or prolonged staring operations of such high-risk applications by the driver at the physical interaction entry point.

[0012] In some embodiments, category labels include long-term viewing category, short-term viewing category, and short-term operation category. Based on the category labels and a preset mapping relationship, the location allocation result of the display area of ​​the first application in the vehicle interface is determined, including: If the usage category label of the first application is the long-term viewing category, the location allocation result of the first application is determined as the first display area; wherein, the first display area is a fixed area that is always displayed near the driver's side; If the usage category label of the first application is short-term viewing, the location allocation result of the first application is determined to be the second display area; wherein, the second display area is a temporary floating layer area close to the driver's side; If the usage category label of the first application is short-term operation category, the location allocation result of the first application is determined to be the third display area; wherein, the third display area is a fixed area for constant display near the passenger side.

[0013] Based on the aforementioned technical means, the differentiated and refined layout of the display area is achieved by using application category tags. This maximizes information acquisition efficiency and operational convenience while ensuring driving safety, achieving a balance between safety and user experience. Specifically, for applications that require long-term viewing, they are placed in a fixed, always-displayed area on the driver's side, allowing the driver to continuously obtain key information without frequently shifting their gaze, reducing the time their eyes are off the road. For applications that require short-term viewing, they are placed in a temporary floating area on the driver's side, satisfying the driver's need for quick information viewing while avoiding long-term occupation of fixed interface resources. The floating layer can also automatically collapse, further reducing visual interference. For applications that require short-term operation, they are placed in a fixed, always-displayed area on the passenger side, effectively guiding the passenger to assist in completing interactive operations, or forcing the driver to operate at relatively safe times, thereby significantly reducing the time the driver takes one hand off the wheel and the length of time their eyes are off the road while driving.

[0014] In some embodiments, based on the location allocation result of the display area, the current display area position of each first application in the vehicle interface is adjusted, including: If the position allocation results of the display area of ​​each first application in the vehicle interface are the same, the position of the current display area of ​​each first application in the vehicle interface is adjusted based on the position allocation results of the display area and the corresponding startup time of each first application.

[0015] Based on the aforementioned technical means, when multiple applications have the same position allocation in the display area of ​​the in-vehicle interface, the current display area position of each application in the in-vehicle interface can be automatically adjusted according to the startup time of each application. This avoids information overlap or display conflicts caused by multiple applications competing for the same area, and enables dynamic and orderly allocation of display resources according to a reasonable strategy, thereby improving the information presentation efficiency and driving safety of the in-vehicle interface in multi-tasking concurrent scenarios.

[0016] In some embodiments, based on the location allocation result of the display area and the startup time corresponding to each first application, the current display area position of each first application in the vehicle interface is adjusted, including: Based on the startup time of each first application, determine the second application with the latest startup time, and determine the display area of ​​the second application in the vehicle interface as the target display area; Based on a pre-set list of degraded display areas corresponding to usage category labels, the display area of ​​the third application (excluding the second application) in the vehicle interface is determined; the degraded display area list includes multiple degraded target display areas and the priority of each degraded target display area.

[0017] Based on the aforementioned technical means, when multiple applications compete for the same display area, the second application with the latest launch time (i.e., the most recently activated) is prioritized for allocation to that display area. Then, according to a pre-defined list of degraded display areas corresponding to usage category tags (such as long-term viewing, short-term viewing, short-term operation), other available display areas are allocated to the remaining third applications in order of priority. This conflict resolution mechanism respects the user's recent operational intentions (the most recent application receives the optimal area) while also achieving a reasonable and dynamic reallocation of display resources based on the safe interaction needs of each application. This minimizes visual clutter and operational interference when switching between multiple applications, while ensuring driving safety.

[0018] In some embodiments, determining the display area of ​​a third application (other than the second application) in the in-vehicle interface based on a pre-set list of degraded display areas corresponding to usage category labels includes: The application with the latest startup time and whose application identifier is not updated is identified from multiple third-party applications as the current application; Based on the list of degraded display areas corresponding to the usage category tag of the current application, determine whether there are any free display areas in the list of multiple degraded target display areas; If there are available display areas in multiple downgrade target display areas, the current application will be assigned to the highest priority available display area for display based on the priority of the available display areas, and the application identifier of the current application will be updated to "processed". If there is no free display area in multiple downgrade target display areas, the application identifier of the current application will be updated to the remaining application; Repeat the above steps until the application identifiers of all third-party applications are updated to processed or remaining applications.

[0019] Based on the aforementioned technical methods, by prioritizing the allocation of applications launched latest from the remaining unupdated applications, it ensures that applications launched later (usually those most recently followed by the user) receive higher downgrade allocation priority, meeting user expectations and improving the user experience. Fine-grained tracking of allocation status through application identifiers (not updated, processed, remaining applications) ensures the controllability and termination of the allocation process, avoiding infinite loops or duplicate allocations.

[0020] In some embodiments, the above method further includes: If the application identifier of the third application includes the identifiers of the remaining applications, the third applications are displayed sequentially in the second display area in the form of rotating floating layers according to the startup time order of the third applications corresponding to each remaining application identifier; or, the third applications corresponding to each remaining application identifier are displayed on the vehicle interface in the form of status bar icons.

[0021] Based on the aforementioned technical means, by providing rotating overlay displays for the remaining applications, multiple remaining applications can share temporary overlay resources, avoiding the information loss problem caused by a large number of applications being directly downgraded to status bar icons due to insufficient display area. Alternatively, by providing status bar icon displays for the remaining applications, the driver's active gaze time and operation frequency on the in-vehicle interface during high-speed driving are effectively reduced, thereby reducing the risk of driver distraction caused by viewing non-core application information.

[0022] In some embodiments, in response to a user's operation on various first applications in the in-vehicle interface, a usage category label corresponding to each first application is determined, including: Within the first duration, if the total duration of a user's gaze on the first application is greater than or equal to the first duration threshold and the duration interval between two gazes is less than or equal to the second duration threshold, then the usage category label of the first application is determined to be the long-term viewing category. If the user's single gaze duration on the first application is less than or equal to the third duration threshold and there is no gaze within the second duration, then the usage category label of the first application is determined to be the short-term viewing category. If the time interval between two user operations on the first application is greater than or equal to the fourth time threshold and the duration of a single operation is less than or equal to the fifth time threshold, then the usage category label of the first application is determined to be the short-term operation category.

[0023] Based on the aforementioned technical means, by setting multiple temporal threshold conditions such as gaze duration, gaze interval, operation interval, and single operation duration, the application's usage category label can be automatically and quantitatively identified from the user's natural interaction behavior, thereby avoiding classification bias caused by subjective judgment or simple statistics.

[0024] This application provides an application display device for an in-vehicle interface, the device comprising: The first determining unit is used to determine the usage category label corresponding to each first application in response to the user's operation on each first application in the vehicle interface. The first application represents the application that is running in the vehicle interface. The second determining unit is used to determine the operation characteristics corresponding to each first application based on the usage operation when the vehicle's driving speed is greater than the target driving speed. The operation characteristics include at least one of operation complexity, gaze duration, and operation frequency. The third determining unit is used to determine the position allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the operation characteristics, usage category labels and vehicle driving status corresponding to each first application. The adjustment unit is used to adjust the current display area position of each first application in the vehicle interface based on the display area position allocation result.

[0025] This application provides an electronic device, including a processor and a memory. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the steps in any of the above methods.

[0026] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in any of the above methods.

[0027] This application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps of any of the above methods. Attached Figure Description

[0028] Figure 1 A flowchart illustrating an application display method for an in-vehicle interface provided in an embodiment of this application; Figure 2 This application provides an illustration of an in-vehicle interface display. Figure 1 ; Figure 3 This application provides an illustration of an in-vehicle interface display. Figure 2 ; Figure 4 This application provides an illustration of an in-vehicle interface display. Figure 3 ; Figure 5 This is a schematic diagram of the overall process of an application display method for an in-vehicle interface provided in an embodiment of this application. Figure 6 This application provides a schematic diagram of the composition structure of an application display device for an in-vehicle interface. Figure 7 This is a schematic diagram of the hardware entity of an electronic device provided in an embodiment of this application.

[0029] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0030] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0031] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0032] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0033] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0034] In this embodiment, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0035] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0036] Currently, with the continuous improvement of vehicle intelligence and connectivity, the functions of in-vehicle infotainment systems are becoming increasingly rich, and the number of applications that need to run and be displayed simultaneously on the central control screen is also increasing. For example, applications such as navigation, music, vehicle settings, and video calls may be active at the same time.

[0037] In existing technologies, the following methods are commonly used for display layouts that are frequently used in in-vehicle screens: (1) Fixed split-screen mode: The screen is pre-divided into several fixed areas, and each application fills in the area in a preset order. For example, the left 1 / 3 area displays navigation, and the right 2 / 3 area displays a list of other applications.

[0038] (2) Manual adjustment mode: Users can adjust the size and position of each application window by dragging, scaling and other gesture operations.

[0039] (3) Single application full-screen mode: By default, only one application is displayed in full screen at a time, and the current interface is completely replaced when switching applications.

[0040] However, the relevant technical solutions have significant shortcomings. Fixed split-screen mode lacks flexibility, failing to dynamically allocate the optimal display area based on the application's actual usage characteristics (such as whether the user views it frequently or operates it occasionally), leading to inconvenient operation or excessively long eye-shifting distances. While manual adjustment mode is flexible, it requires complex manual operations by the driver while driving, posing significant safety hazards. A single full-screen mode cannot meet the user's need to monitor multiple information sources simultaneously (such as simultaneously focusing on navigation and music).

[0041] Therefore, how to reasonably allocate display positions for multiple applications on the in-vehicle screen to reduce user manual intervention and improve driving safety is an urgent problem to be solved.

[0042] Based on this, embodiments of this application provide an application display method for an in-vehicle interface. The method includes: responding to user operations on various first applications in the in-vehicle interface, determining a usage category label corresponding to each first application, wherein the first application represents an application that is running in the in-vehicle interface; when the vehicle's driving speed is greater than a target driving speed, determining operation features corresponding to each first application based on the usage operations, wherein the operation features include at least one of operation complexity, gaze duration, and operation frequency; determining a position allocation result of the display area of ​​each first application in the in-vehicle interface based on at least one of the operation features, usage category labels, and vehicle driving state; and adjusting the current position of the display area of ​​each first application in the in-vehicle interface based on the position allocation result of the display area. In this way, by responding to the user's operation on the first application to determine the usage category label, and when the vehicle speed is greater than the target speed, further operational characteristics such as operation complexity, gaze duration, and operation frequency are obtained, the display area position of each application in the in-vehicle interface is dynamically allocated by comprehensively considering at least one factor among the operational characteristics, usage category label, and vehicle driving status. This allows the layout of the in-vehicle interface to adaptively adjust according to the driving scenario and the user's real-time interaction behavior. Thus, while ensuring driving safety and reducing the driver's cognitive load and gaze deviation time, it also takes into account the user's operational convenience and personalized usage habits for different applications, thereby improving the interactive safety and user experience during driving.

[0043] The technical solutions in the embodiments of this application will now be clearly and completely described with reference to the accompanying drawings.

[0044] It should be noted that the in-vehicle interface application display method provided in the embodiments of this application can be executed by a display device, which can be an electronic device, a server, a terminal device, a smartwatch, etc. It can also be applied to vehicle cockpit systems equipped with a central touchscreen display.

[0045] Figure 1 This is a flowchart illustrating an application display method for an in-vehicle interface provided in an embodiment of this application, as shown below. Figure 1 As shown, it may include S101 to S103, wherein: S101, in response to the user's operation on each first application in the vehicle interface, determines the usage category label corresponding to each first application.

[0046] The first application refers to the application that is currently running on the vehicle's in-vehicle interface. In other words, the first application refers to the application that is currently running on the vehicle's in-vehicle interface (such as the central control display, instrument panel display, or head-up display system).

[0047] In the embodiments of this application, an application in the running state can be understood as an application that is started in response to a user's startup operation, so that the application is in the running state. The process of the application in the running state has been started and has not been destroyed. It currently resides in the system memory and can respond to user interaction or system events.

[0048] Here, "user actions" in the first application refer to the user's actions during human-computer interaction with various first applications. User actions include, but are not limited to: touch clicks, swipes and drags, text input, voice commands, gesture control, knob rotation, and button presses. User actions not only record the type of action but also the timestamp of the action, its duration, its coordinates on the screen, and the intervals between each step in the action sequence. User actions serve as the foundational data source for subsequently determining operation complexity, gaze duration, and operation frequency.

[0049] Here, category labels are identification information assigned to the first application after categorizing it according to its usage operations. For example, category labels include long-term viewing category, short-term viewing category, and short-term operation category.

[0050] Here, applications that require sustained driver attention refer to applications that can include navigation maps (where the driver must continuously look at the route), full-screen video playback, music lyrics information, and driver assistance information.

[0051] Applications that allow for short-term viewing of categories do not require continuous driver attention; they only require a quick, one-time access to information. This can include mileage and energy consumption information, tire pressure information, and weather information.

[0052] Applications with short-term operation categories have a low interaction frequency and are used to respond to changes in status or to start / stop simple tasks. These can include music control (play / switch / volume), air conditioning control (temperature / fan speed), vehicle control (seat / rearview mirror / lock), and telephone call control.

[0053] In some embodiments, if the number of applications in the running state is greater than a first quantity threshold, after receiving a user's usage operation on one or more first applications in the vehicle interface, the usage category label corresponding to each first application can be determined based on the user's usage operation on each first application in the vehicle interface; correspondingly, if the number of applications in the running state is less than or equal to the first quantity threshold, it is not necessary to determine the usage category label of the application, and the number of applications in the running state can be directly displayed in the corresponding area of ​​the vehicle interface.

[0054] It should be noted that the first quantity threshold can be customized according to the application scenario or user needs. For example, the first quantity threshold can be 2, but this application embodiment does not limit it.

[0055] Next, this application embodiment will describe in detail several implementation methods for determining the usage category label corresponding to each first application.

[0056] In one possible implementation, the above-mentioned "determining the usage category label corresponding to each first application in response to the user's operation on each first application in the vehicle interface" may include the following steps: S1011, within the first duration, if the total duration of the user's gaze on the first application is greater than or equal to the first duration threshold and the duration interval between two gazes is less than or equal to the second duration threshold, then the usage category label of the first application is determined to be the long-term viewing category.

[0057] In some embodiments, all user gaze events on the first application can be collected within a first duration. When the total duration of user gaze on the first application is greater than or equal to a first duration threshold, and the time interval between any two adjacent gaze events is less than or equal to a second duration threshold, the usage category label of the first application is determined to be a long-term viewing category.

[0058] For example, the first duration, the first duration threshold, and the second duration threshold can be customized according to the user or the scenario; the first duration can be 30 seconds; the first duration threshold can be 5 seconds; and the second duration threshold can be 10 seconds.

[0059] S1012, if the user's single gaze duration on the first application is less than or equal to the third duration threshold and there is no gaze within the second duration, then the usage category label of the target application is determined to be the short-term viewing category.

[0060] In some embodiments, single-gaze events of the user on the first application can be collected. When the duration of a single gaze on the first application is less than or equal to a third duration threshold, and no new gaze events are detected within a second preset duration after the end of the gaze, the usage category label of the first application is determined to be short-term viewing. The user only obtains key status information (such as time, signal strength) through a very brief glance, and then looks away, indicating that their attention to the application interface is low and no interaction is required.

[0061] For example, the third duration threshold can be customized according to the user or scenario; the third duration threshold can be 2 seconds.

[0062] S1013, if the time interval between two user operations on the first application is greater than or equal to the fourth time threshold and the duration of a single operation is less than or equal to the fifth time threshold, then the usage category label of the first application is determined to be a short-term operation type.

[0063] In some embodiments, continuous operation events of the user on the first application are collected. When the time interval between any two adjacent operations of the user on the first application is greater than or equal to a fourth duration threshold, and the duration of each single operation is less than or equal to a fifth duration threshold, the usage category label of the first application is determined to be a short-term operation category.

[0064] For example, the fourth duration threshold can be customized according to the user or scenario; the fourth duration threshold can be 2 minutes.

[0065] In this embodiment, by setting multiple temporal threshold conditions such as gaze duration, gaze interval, operation interval, and single operation duration, the usage category label of the first application can be automatically and quantitatively identified from the user's natural interaction behavior, thereby avoiding classification bias caused by subjective judgment or simple statistics. This fine-grained classification method based on eye movement and operation behavior can effectively distinguish whether the user is focusing on content for a long time (such as navigation), briefly glancing at information (such as the status bar), or making rapid click adjustments (such as changing songs). In driving scenarios, the classification results can provide a basis for subsequent safety scheduling.

[0066] In another possible implementation, an integral model with a decay factor can be constructed to calculate an "attention heat score" for each application in real time. Each time a user looks at an application, the score increases by a fixed weight and decays exponentially over time (e.g., a half-life of 0.5 seconds). User actions can receive additional, higher weights. At the end of the first duration, the shape of the score curve for each application is analyzed: if the curve maintains a consistently high and stable value, it is considered a long-term viewing type (the user continuously focuses on the content); if the curve shows only one isolated peak and then quickly returns to zero, it is a short-term viewing type (the user only glanced at it); if the curve exhibits dense, low-amplitude pulse-like oscillations (each action causes a short rise followed by rapid decay), it is a short-term action type (the user clicks quickly based on muscle memory, without prolonged viewing).

[0067] S102, when the vehicle's speed is greater than the target speed, determine the operation characteristics corresponding to each first application based on the usage operation.

[0068] In some embodiments, if it is determined that the vehicle's speed is greater than the target speed, it indicates that the vehicle's current speed is relatively fast. Furthermore, the operation characteristics corresponding to each first application can be determined based on the user's operation on each first application in the in-vehicle interface.

[0069] Here, operation features refer to the operational data generated during the user's operation of various first applications in the vehicle interface. For example, operation features may include at least one of operation complexity, gaze duration, and operation frequency.

[0070] Operational complexity refers to the comprehensive measure of the number of steps a user needs to take to complete a specific task within a first application (such as changing songs, entering a navigation destination, or answering a phone call). Operational complexity can be quantified from one or more of the following dimensions: Step Count: The number of steps a user takes from initiating interaction to completing the target operation, involving touch, clicks, swipes, or voice commands. More steps indicate greater visual search and hand movement on the interface, resulting in higher complexity. Interaction Level Depth: The depth of the application interface involved in the operation. For example, if a user needs to navigate to a three-level submenu to complete an operation, the interaction level depth is 3. The deeper the level, the heavier the visual search and memory burden on the user, leading to higher complexity. Input Type Complexity: Different input types consume different levels of cognitive resources. For example, voice input has a lower cognitive burden than text input (the user doesn't need to take their eyes off the screen), while text or gesture input requires higher cognitive engagement.

[0071] Gaze duration refers to the cumulative time a user's gaze remains on a specific display area of ​​the in-vehicle interface or a specific application interface during interaction with various primary applications. Gaze duration can be collected and statistically analyzed in real time using in-vehicle cameras, infrared gaze-tracking sensors, or image-processing-based eye-tracking modules.

[0072] Operation frequency refers to the average number of times a user triggers an operation event per unit of time when interacting with various applications. Operation frequency is used to measure the intensity of a user's use and the level of interaction with a particular application.

[0073] In some embodiments, the current driving speed of the vehicle can be obtained from the vehicle electronic control unit via the vehicle controller local area network bus or vehicle Ethernet, and the obtained current driving speed is compared with a preset target driving speed. When the vehicle speed is greater than the target driving speed, it is considered that the vehicle has entered a medium-to-high speed driving state, and the driving operation significantly increases the occupation of the driver's cognitive resources. It is necessary to determine the operation characteristics corresponding to the application, and determine the position allocation result of the display area of ​​each first application in the vehicle interface based on the operation characteristics, usage category labels, and vehicle driving state. When the vehicle speed is less than or equal to the target driving speed, it is considered that the vehicle is in a low-speed driving state or about to stop. At this time, the driver has relatively sufficient cognitive resources to process the interaction of the vehicle interface, and it is not necessary to determine the operation characteristics of the application. The position allocation result of the display area of ​​each first application in the vehicle interface can be determined only based on the application's usage category label and the vehicle driving state.

[0074] Next, this application will describe the method for determining the operational features corresponding to each first application.

[0075] Regarding the determination of operational complexity, one possible implementation is that the in-vehicle system can pre-store a baseline value for the operational complexity of each first application. This baseline value is pre-calibrated by the application developer or system integrator based on the application's interface hierarchy and typical operation flow. For example, the baseline operational complexity of a music playback application can be set to a low value because users typically only need to click once to switch songs; while the baseline complexity of destination input in a navigation application can be set to a high value because it requires multiple steps such as inputting text, selecting candidate addresses, and confirming routes.

[0076] In another possible implementation, the complexity of an operation can be calculated in real time based on the user's current operation sequence. Factors such as the number of operation steps from the start of the operation to the completion of the goal, the number of interface jump levels, and the input method can be comprehensively considered. Each factor is assigned a corresponding weight, and finally a comprehensive score that reflects the difficulty of the operation is obtained.

[0077] The duration of gaze can be determined through a driver monitoring system within the vehicle's cabin. This system typically includes one or more infrared cameras facing the driver's face, which, combined with eye-tracking algorithms, detect the driver's gaze direction in real time. When the system detects that the user's gaze is focused on the display area of ​​a specific application, it begins accumulating gaze duration from that moment. Gazing duration is a cumulative amount, continuously accumulating throughout the driving trip until the vehicle is powered off or the user closes the application.

[0078] Regarding the determination of operation frequency, in one possible implementation, within a preset statistical time window, the number of valid operations triggered by the user on each first application is counted, and the number of operations within this statistical period is used to characterize the operation frequency.

[0079] S103, determine the position allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the operation characteristics, usage category labels and vehicle driving status corresponding to each first application.

[0080] Here, the vehicle's driving status can include the vehicle being in motion, the vehicle being parked, or the vehicle being stationary.

[0081] Here, the location allocation result refers to the identification information or coordinate information of the display area that should be placed in the vehicle interface for each of the currently running first applications. The specific form of the location allocation result may include: the area number of the target display area corresponding to each first application, the sorting position of the application in its display area (such as the 1st position, the 2nd position), and the coordinate range of the application interface on the screen.

[0082] It should be noted that the location allocation of the display area of ​​each first application in the vehicle interface can be determined based on the operation characteristics corresponding to each first application; it can also be determined based on the usage category tags corresponding to each first application; it can also be determined based on the vehicle driving status corresponding to each first application; or it can be determined based on one or more of the operation characteristics, usage category tags, and vehicle driving status corresponding to each first application. This embodiment of the application does not limit the scope of this method.

[0083] Next, this application embodiment details the specific implementation method for determining the position allocation result of each first application in the display area of ​​the vehicle interface.

[0084] In one possible implementation, the above-mentioned "determining the location allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the operation characteristics, usage category labels and vehicle driving status corresponding to each first application" may include the following steps: S1031, determine the security level of each first application based on the operation complexity, gaze duration and operation frequency corresponding to each first application.

[0085] Among them, the security level is related to the application's operational complexity, gaze duration, and operation frequency.

[0086] In some embodiments, the security level of the first application can be determined based on the operational complexity of the first application. For example, the security level of the application is inversely proportional to the operational complexity of the application. That is, the higher the operational complexity of the application by the user, the lower the security level of the application.

[0087] In some embodiments, the security level can be determined based on the application's gaze duration. For example, the security level of an application is inversely proportional to the application's gaze duration; that is, the longer the user gazes at the application, the lower the application's security level.

[0088] In some embodiments, the security level can also be determined based on the frequency of application operation; for example, the security level of an application is inversely proportional to the frequency of application operation, that is, the higher the frequency of user operation of the application, the lower the security level of the application.

[0089] In some embodiments, the security level can also be determined based on the application's operational complexity, gaze duration, and operation frequency simultaneously, but this application does not limit this aspect.

[0090] In some embodiments, the complexity score, gaze duration score, and operation frequency score of each first application are obtained; a weighted sum is performed based on the complexity score, gaze duration score, and operation frequency score to obtain a comprehensive risk score for each first application; and a safety level is determined based on a preset score range into which the comprehensive risk score falls, wherein a higher comprehensive risk score corresponds to a lower safety level, and the safety level is used to indicate the degree of risk when the first application is operated during driving.

[0091] S1032, determine the location allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the security level, usage category label and vehicle driving status corresponding to each first application.

[0092] In one embodiment, at least one of the security level, usage category label, and vehicle driving status corresponding to each first application can be input into a pre-trained machine learning model to determine the position allocation result of each first application in the display area of ​​the vehicle interface.

[0093] In another embodiment, multiple first applications can be divided into applications with higher security levels and applications with lower security levels according to the relationship between the security level of each first application and the preset security level. For applications with higher security levels, the position allocation result of the display area of ​​the first application in the vehicle interface can be determined by using the preset position relationship; for applications with lower security levels, they can be displayed directly in the form of a status bar icon or a floating window.

[0094] In this embodiment, by quantifying operation complexity, gaze duration, and operation frequency into the application's security level, and then combining this with the use of category tags and driving status for location allocation, the in-vehicle interface layout can implement differentiated strategies for applications with different risk levels, achieving a balance between security and usability, and effectively improving driving safety and interactive experience.

[0095] In another possible implementation, at least one of the following can be input into a pre-trained machine learning model: the operation features of each first application, the usage category label, and the vehicle driving state. This will directly output the position allocation result of each first application in the display area of ​​the vehicle interface.

[0096] S104, based on the position allocation result of the display area, adjust the current display area position of each first application in the vehicle interface.

[0097] In some embodiments, after determining the position allocation results of each application's display area in the vehicle interface, it can be determined whether the position allocation results of each first application are the same, that is, whether there is a conflict in the position allocation results of each first application. If there is no conflict, the window management module or view management module of the vehicle system is called according to the target display area identifier or coordinate information corresponding to each first application contained in the position allocation results, and the interface window of each first application is moved to the target position. If there is a conflict, the current position of each first application's display area in the vehicle interface can be adjusted according to the position allocation results of the display area and the preset conflict strategy.

[0098] In this embodiment, a usage category label is determined in response to the user's operation on the first application. When the vehicle speed is greater than the target speed, operation features such as operation complexity, gaze duration, and operation frequency are further obtained. The display area position of each application in the vehicle interface is dynamically allocated by comprehensively considering at least one of the operation features, usage category label, and vehicle driving state. This allows the layout of the vehicle interface to be adaptively adjusted according to the driving scenario and the user's real-time interaction behavior. This ensures driving safety, reduces the driver's cognitive load and gaze deviation time, and takes into account the user's operational convenience and personalized usage habits for different applications, thereby improving the interactive safety and user experience during driving.

[0099] In some embodiments, the above-mentioned S1031 "determining the security level of each first application based on the operation complexity, gaze duration, and operation frequency corresponding to each first application" may further include the following steps: S10311, Based on the complexity of operation, the interaction levels of each first application are classified to obtain the interaction level.

[0100] The interaction levels are categorized into high, medium, and low interaction levels.

[0101] For high-interaction-level applications (requiring multi-level confirmation), when an application's operation is complex, users need to go through multiple steps to complete a task, typically involving information input, multi-level menu navigation, or requiring users to select and confirm among multiple options. Understandably, high-interaction-level applications significantly consume the driver's cognitive resources and operating time when used while driving, thus constituting a higher-risk application type.

[0102] For example, when setting a new destination in a navigation app, users need to perform the following steps in sequence: click the search box, enter the address text, select the target address from the candidate list, confirm route preferences (such as the fastest or shortest route), and finally click "Start Navigation" for final confirmation. The entire process involves multiple confirmation operations. Similarly, adjusting the vehicle's driving mode in a car system (switching from Standard to Sport mode) may require navigating to a deep sub-page of the settings menu, and after selecting the mode, a secondary confirmation dialog box must pop up to confirm the switch. These types of applications or functions are categorized as high-interaction-level.

[0103] For medium-level interaction (requiring single confirmation), when an application's operational complexity is at a medium level, users typically only need one or two steps to complete the main tasks, involving at most one confirmation operation. Understandably, while these operations require users to perform a click and involve brief eye contact, the short operation path and few confirmation steps limit their impact on driving distraction. For example, in a music playback app, switching tracks requires only one click of the "next song" button, without further confirmation; similarly, answering a call requires only one click of the answer button on the screen.

[0104] For low-interaction levels (no confirmation required), when an application's operation complexity is low, user actions typically do not require any form of confirmation. The action itself may be passively receiving information or an action executed automatically by the system. Understandably, such applications or functions consume almost no user resources or require significant confirmation, minimizing the negative impact on driving safety. For example, real-time driving information displayed on the dashboard (such as current speed, remaining range, tire pressure data, etc.) requires only passive observation from the user, without any active operation or confirmation. Similarly, voice prompts in navigation applications proactively output information to the user, which the user receives without confirmation. Furthermore, when a user controls the air conditioning temperature via voice commands, the system executes the command directly without requiring the user to manually click a confirmation button.

[0105] In some embodiments, after determining the operational complexity of the first application, the first application can be divided into three interaction levels based on the level of operational complexity. For example, operational complexity can be reflected by the number of operation steps. By collecting the operation steps of the application in a driving scenario, if the number of operation steps is greater than or equal to a first step threshold (e.g., 5 steps), the application is determined to be a high-interaction-level application; if the number of operation steps is greater than or equal to a second step threshold (e.g., 2 steps) and less than the first step threshold, the application is determined to be a medium-interaction-level application; and if the number of operation steps is less than the second step threshold, the application is determined to be a low-interaction-level application.

[0106] It should be noted that the first and second step thresholds of the interaction level can be preset by the system developers based on the application type and interaction characteristics.

[0107] In other embodiments, the classification of interaction levels can further refer to the depth of interface navigation, i.e. how deep a user needs to enter a submenu to complete the operation; the deeper the level, the higher the interaction level.

[0108] S10312, determine the driving attention occupancy coefficient for each first application based on gaze duration and operation frequency.

[0109] Among them, the driving attention occupancy coefficient is directly proportional to the duration of gaze, and the driving attention occupancy coefficient is directly proportional to the frequency of operation.

[0110] Here, the driving attention occupancy coefficient represents the total amount of attention resources a user transfers from driving tasks to using a specific application per unit of time. The higher the coefficient, the greater the driver's attention consumption by the application in the current driving scenario, and the greater the potential threat to driving safety.

[0111] In one possible implementation, gaze duration and operation frequency can be normalized separately and mapped to a uniform score range (e.g., between 0 and 1). Furthermore, the product between the normalized gaze duration value and the normalized operation frequency value can be calculated as the driving attention occupancy coefficient.

[0112] For example, suppose application A has a gaze duration normalized value of 0.8 (indicating a long gaze duration) and an operation frequency normalized value of 0.9 (indicating a high operation frequency). Then its driving attention occupancy coefficient is 0.8 multiplied by 0.9, which equals 0.72, indicating a high level of attention occupancy. On the other hand, application B has a gaze duration normalized value of 0.9 (long gaze duration) but an operation frequency normalized value of 0.1 (extremely low operation frequency, such as an application that continuously displays information but is rarely operated by the user). Then its driving attention occupancy coefficient is 0.9 multiplied by 0.1, which equals 0.09, indicating a low level of attention occupancy.

[0113] In another possible implementation, gaze duration and operation frequency can be normalized separately, mapping them to a uniform score range (e.g., between 0 and 1). Furthermore, the normalized values ​​for gaze duration and operation frequency can be assigned different weights and then summed. It should be noted that the specific values ​​of the weights can be adjusted according to the actual application scenario and safety priorities. For example, in high-speed driving scenarios, the weight of gaze duration can be increased because the risk of the gaze leaving the road is greater at high speeds.

[0114] S10313, the interaction level and the driving attention occupancy coefficient are weighted and fused to obtain the comprehensive safety coefficient of each first application.

[0115] In some embodiments, the interaction level can be quantified into a numerical form. For example, a low interaction level can be assigned a value of 1, a medium interaction level a value of 2, and a high interaction level a value of 3 (the higher the value, the higher the risk); then, this value is normalized to a score between 0 and 1. Further, the interaction level score and the driver attention occupancy coefficient can be weighted and fused according to a preset weighting coefficient to obtain a comprehensive safety coefficient for each first application. A higher comprehensive safety coefficient indicates a greater overall risk for the application in the current driving scenario, and it is more likely to be assigned to a location far from the driver's line of sight or with lower operational convenience in subsequent steps to reduce the risk of driver distraction.

[0116] For example, the weight corresponding to the interaction level can be set to 0.6, the weight corresponding to the driving attention occupancy coefficient can be set to 0.4, and the formula for calculating the comprehensive safety coefficient is: the interaction level quantification normalization value multiplied by 0.6 plus the driving attention occupancy coefficient multiplied by 0.4 to obtain the final comprehensive safety coefficient (the value range is between 0 and 1).

[0117] It should be noted that this weighting ratio can be adjusted according to actual needs. For example, in scenarios where more emphasis needs to be placed on the inherent operational complexity of the application (such as driver training mode or novice driver mode), the weight of the interaction level can be increased; in scenarios where more emphasis needs to be placed on the user's real-time behavior (such as personalized adaptive mode), the weight of the driving attention occupancy coefficient can be increased.

[0118] S10314, Determine the security level of each primary application based on the comprehensive security factor.

[0119] Here, security levels can include low security level, medium security level, and high security level.

[0120] In some embodiments, multiple coefficient ranges can be preset, each coefficient range can correspond to a security level, and the security level of the first application can be determined based on the coefficient range in which the comprehensive security coefficient is located.

[0121] For example, three coefficient ranges can be preset. When the overall safety coefficient is less than or equal to the first coefficient threshold (e.g., 0.3), the application's safety level is determined to be high. Applications with a high safety level have minimal negative impact on driving safety during driving, such as dashboard driving information displays and voice-activated applications, and can be kept in convenient locations on the in-vehicle interface. When the overall safety coefficient is greater than the first preset threshold and less than or equal to the second coefficient threshold (e.g., between 0.3 and 0.7), the application's safety level is determined to be medium. When the overall safety coefficient is greater than the second coefficient threshold (e.g., greater than 0.7), the application's safety level is determined to be low. Applications with a low safety level significantly distract the driver during driving and seriously affect driving safety. Examples include destination settings requiring text input and browsing social media feeds. These should be prioritized and moved to display areas away from the driver, and in extreme cases, the system may even suggest suspending or locking them.

[0122] It should be noted that the first and second coefficient thresholds (0.3 and 0.7) mentioned above are merely exemplary values ​​and can be flexibly adjusted in practical applications based on vehicle type, target users, or different driving scenarios (urban roads or highways). For example, in commercial or operational vehicles, to ensure a higher level of safety, the threshold for determining a high-risk level can be appropriately lowered, allowing more applications to be classified as high-risk and adopting a more conservative location allocation strategy. In other embodiments, the safety level can also be divided into more levels (such as five or ten levels) to achieve more refined location allocation control.

[0123] In this embodiment, by quantifying operational complexity into interaction level, fusing gaze duration and operation frequency into driving attention occupancy coefficient, and then weighting and fusing the two to obtain a comprehensive safety coefficient, a comprehensive quantitative assessment of application safety is achieved from two orthogonal dimensions: inherent application risk and real-time attention consumption. This avoids misjudgment based on a single dimension, provides a precise decision-making basis for subsequent differentiated display area allocation, and effectively reduces the risk of driver distraction.

[0124] In some embodiments, the above-mentioned S1032 "determining the position allocation result of the display area of ​​each first application in the vehicle interface according to at least one of the security level, usage category label and vehicle driving status corresponding to each first application" may further include the following steps: S10321, for each first application, if the security level corresponding to the first application is greater than the preset security level and the vehicle driving state is driving state, the position allocation result of the display area of ​​the first application in the vehicle interface is determined based on the usage category label and the preset mapping relationship.

[0125] Here, the preset safety level refers to a safety threshold pre-set for each application, used to determine whether the application is allowed to display its interface according to conventional rules during driving. For example, the safety level value can be an integer from 1 to 10, with higher values ​​indicating less interference with driving safety. The preset safety level can be preset by the system (e.g., preset safety level = 6) or dynamically adjusted according to the user's driving habits. As another example, the safety level can be divided into three levels: low safety level, medium safety level, and high safety level.

[0126] Here, the preset mapping relationship refers to the pre-established correspondence rules between application usage category tags and specific display areas in the in-vehicle interface. This mapping relationship is pre-stored in the in-vehicle system and is used to automatically assign applications with different usage category tags to the appropriate display areas.

[0127] In some embodiments, after determining that the vehicle is in a driving state and the driving speed is greater than the target driving speed, the security level of each application in the running state can be further determined. If the security level of an application is greater than the preset security level, it indicates that the application has a low operation frequency or low operation complexity during high-speed driving, or a short gaze duration, and will not pose a significant security threat to the user. Based on this, the display area of ​​each application in the vehicle interface can be determined according to the preset display rules, that is, based on the use of category labels and preset mapping relationships.

[0128] Next, this application embodiment will describe in detail the specific implementation method of determining the location allocation result of the display area of ​​the first application in the vehicle interface based on the use of category labels and preset mapping relationships.

[0129] In some embodiments, when the usage category label of the first application is a long-term viewing category, the location allocation result of the first application is determined as a first display area; wherein, the first display area is a fixed area that is always displayed near the driver's side; when the usage category label of the first application is a short-term viewing category, the location allocation result of the first application is determined as a second display area; wherein, the second display area is a temporary floating layer area that is near the driver's side; when the usage category label of the first application is a short-term operation category, the location allocation result of the first application is determined as a third display area; wherein, the third display area is a fixed area that is always displayed near the passenger's side.

[0130] Here, the primary display area refers to the fixed display area located on the left side of the in-vehicle display screen, close to the center of the driver's line of sight. This area is stable, allowing the driver to continuously access information without significantly shifting their gaze, making it suitable for content that requires prolonged or frequent viewing. This area is typically not covered by temporary notifications or pop-ups.

[0131] Here, the second display area refers to a temporary display area that dynamically appears on the in-vehicle display screen. It is usually located near the driver's side, but it disappears or collapses automatically after the user completes the interaction or after a preset time (such as 3-5 seconds). This area is suitable for information that is viewed briefly, avoiding occupying fixed interface space for a long time.

[0132] Here, the third display area refers to the fixed display area located on the right side of the in-vehicle display screen, closer to the passenger side. This area is significantly off-line from the driver's line of sight and is not suitable for frequent operation while driving. Therefore, it is used for short-term operation applications, which can be handled by the passenger.

[0133] In some embodiments, Figure 2 This application provides an illustration of an in-vehicle interface display. Figure 1 ,like Figure 2 As shown, the first display area is a fixed display area located on the left side of the vehicle display screen, close to the center of the driver's line of sight. It can be the 1 / 3 area closest to the driver's side, denoted as area 1 / 3. .

[0134] In some embodiments, Figure 3 This application provides an illustration of an in-vehicle interface display. Figure 2 ,like Figure 3 As shown, the third display area is a fixed display area on the right side of the vehicle's display screen, closer to the passenger side. It can be the second-to-last two-thirds of the area closest to the driver's side, denoted as area . .

[0135] In some embodiments, Figure 4 This application provides an illustration of an in-vehicle interface display. Figure 3 ,like Figure 4 As shown, the second display area is a temporary display area that dynamically appears on the in-vehicle display screen, usually located on the driver's side, and is denoted as area. .

[0136] In some embodiments, after determining the usage category label of a first application that is in operation, the display area corresponding to the application can be determined from a preset mapping relationship based on the usage category label.

[0137] In this embodiment, the use category tags of the first application enable a differentiated and refined layout of the display area, maximizing information acquisition efficiency and operational convenience while ensuring driving safety, achieving a balance between safety and user experience. Specifically, for applications with long-term viewing, they are placed in a fixed, always-displayed area on the driver's side, allowing the driver to continuously acquire key information without frequently shifting their gaze, reducing the time spent with their eyes off the road. For applications with short-term viewing, they are placed in a temporary floating area on the driver's side, satisfying the driver's need for quick information viewing while avoiding long-term occupation of fixed interface resources, and the floating layer can automatically collapse, further reducing visual interference. For applications with short-term operation, they are placed in a fixed, always-displayed area on the passenger side, effectively guiding the passenger to assist in completing interactive operations, or forcing the driver to operate at a relatively safe time, thereby significantly reducing the time the driver takes one hand off the wheel and the length of time their eyes are off the road while driving.

[0138] S10322, when the security level corresponding to the first application is less than or equal to the preset security level, and the vehicle is in driving mode, the control application is displayed on the vehicle interface as a status bar icon.

[0139] In some embodiments, after determining that the vehicle is in a driving state and the driving speed is greater than the target driving speed, the safety level of each first application in the running state can be further determined. If the safety level of the first application is less than or equal to the preset safety level, it indicates that the application has a high frequency of operation or high complexity of operation during high-speed driving, or a long duration of attention, which may pose a significant driving safety threat to the user. Based on this, applications with lower safety levels can be directly controlled to be displayed on the in-vehicle interface as status bar icons. In this way, in high-risk driving scenarios such as high-speed driving, applications with high safety risks can be forcibly hidden in the status bar, retaining only their most basic running status prompts. This avoids accidental touches or prolonged attention from the user in physical space, thereby effectively reducing the risk of distracted driving caused by operating the in-vehicle interface and significantly improving driving safety.

[0140] In some embodiments, when the vehicle is in a driving state and the driving speed is less than or equal to the target driving speed, indicating that the current driving speed of the vehicle is slow, the security level of each application can be disregarded, and the location allocation result of the display area of ​​the first application in the vehicle interface can be determined based on the use of category labels and preset mapping relationships.

[0141] In some embodiments, when the vehicle is in a parked driving state, the location allocation result of the display area of ​​the first application in the vehicle interface can be determined based on the use of category labels and preset mapping relationships, without considering the security level of each application.

[0142] In some embodiments, when the vehicle is in a parking state while driving, all automatic allocation policies can be paused, allowing users to manually adjust or temporarily hide non-safety-related applications to prioritize parking safety.

[0143] In this embodiment, by introducing a comparison mechanism between the security level and the preset security level, on the one hand, for applications with a security level greater than the preset security level, it indicates that they pose a relatively small threat to driving safety during high-speed driving. Therefore, the display area is allowed to be allocated normally according to the usage category label and the preset mapping relationship, ensuring the user's normal access needs for commonly used low-risk applications. On the other hand, for applications with a security level less than or equal to the preset security level, it indicates that they may pose a significant threat to driving safety during high-speed driving. In this case, they are forcibly controlled to be displayed as status bar icons, which not only preserves the user's ability to perceive that the application is running, but also effectively avoids the driver's accidental touch or prolonged staring operation of such high-risk applications during high-speed driving.

[0144] Understandably, after determining the display area for each application within the in-vehicle interface, conflict resolution is necessary when multiple applications are assigned to the same display area to ensure that each application can be correctly displayed in the target display area. The following embodiments of this application will detail the specific implementation of conflict resolution.

[0145] In some embodiments, the above-mentioned S104 "adjusting the current display area position of each first application in the vehicle interface based on the display area position allocation result" may further include the following steps: If the position allocation results of the display area of ​​each first application in the vehicle interface are the same, the position of the current display area of ​​each first application in the vehicle interface is adjusted based on the position allocation results of the display area and the corresponding startup time of each first application.

[0146] Here, the location allocation results are the same, which can be understood as the display area of ​​each first application in the vehicle interface being the target display area, where the target display area is any one of the first display area, the second display area, and the third display area.

[0147] Here, startup time refers to the moment when each first application is launched in the current driving cycle, or the moment when it switches from the background to the foreground.

[0148] In some embodiments, if the position allocation results of the display areas of each first application in the vehicle interface are the same, the startup time of each first application can be determined. Further, based on the position allocation results of the display areas, the startup time of each first application, and the conflict handling strategy, the current position of each first application in the display area of ​​the vehicle interface can be adjusted.

[0149] Here, the conflict resolution strategy refers to the preset rules used to determine which first application obtains display permissions for the same target display area when multiple first applications are assigned to it. For example, the conflict resolution strategy may include, but is not limited to: The first-come, first-served strategy prioritizes the target display area, with other applications waiting in queue according to their launch time or displayed in a collapsed form in other areas. The last-come, first-served strategy (preemptive strategy) prioritizes the target display area, with the original application being downgraded to a status bar icon or moved to another area. The dynamic priority strategy combines factors such as the application's security level, usage frequency, and user-defined priority to calculate a score, with the application with the highest score occupying the target display area.

[0150] In one possible implementation, after determining the position allocation results of each first application's display area in the vehicle interface, all running first applications are traversed to check if there are two or more first applications with the same position allocation result, i.e., assigned to the same target display area (i.e., both in the first display area, both in the second display area, or both in the third display area). If no conflict is detected, the display area of ​​the first application in the vehicle interface is determined according to a preset mapping relationship.

[0151] For example, let's illustrate this by having a driver sequentially open three applications with different usage characteristics while driving. Assume the vehicle is in motion, and the central control screen is initially off or on its home screen. The user then performs the following actions in sequence: 1. Opens the map navigation application (for route guidance); 2. Then opens the music player application (for playing media content); 3. Finally, opens the phone application (for dialing numbers).

[0152] The system detected that three primary applications (map navigation, music player, and phone) are currently active, with a total of ≥2. Therefore, the usage characteristics of each application are identified: Map navigation application: Users need to frequently and intermittently monitor route information over a period of time to maintain continuous awareness of the navigation status. Therefore, its main usage characteristic is identified as prolonged viewing. Music player application: Once opened, users typically do not need to perform any operations for a considerable period, only requiring minimal and infrequent interaction when switching songs or adjusting volume. Therefore, its main usage characteristic is identified as occasional operation. Phone application: Users only need to quickly scan the caller ID and decide to dial a number, a process that usually requires only a brief glance. Therefore, its main usage characteristic is identified as short-term viewing. Furthermore, the system obtains the current vehicle driving status. Assuming the initial speed is 30 km / h (urban road), and the high-speed correction threshold has not been triggered, the interface displays normally according to the above strategy. The system calls the preset display area division. Long-term viewing (map navigation → assigned to location ① (the 1 / 3 of the constantly displayed fixed area closest to the driver's side)). Occasional operation (music player → assigned to location ② (the 2 / 3 of the constantly displayed fixed area next to the driver's side)). Short-term viewing (phone → assigned to location ③ (the temporary floating area closest to the driver's side)). The three applications were assigned to three different display areas without any display conflict, and no conflict decision was required.

[0153] Furthermore, if the user does not make manual adjustments, the display effect of the central control screen is as follows: Position ① (1 / 3 area closer to the driver): The map navigation interface is always displayed, ensuring that the navigation information is always within the driver's optimal line of sight. Position ② (2 / 3 area further from the driver): The music playback interface is always displayed, allowing the user to operate it occasionally without affecting the main driving task. Position ③ (temporary floating layer): The telephone function is displayed floating above the navigation interface, clearly visible, and disappears after operation ends, without affecting the core functions.

[0154] In this way, when there are no conflicts, the driver doesn't need to manually operate any of the three applications; they automatically obtain the optimal display position. Navigation remains constantly visible to ensure driving safety, phone messages are clearly displayed for quick decision-making, and music controls are on the side without interfering with the main task. Simultaneously, through speed-linked operation, the system automatically retracts occasionally used applications at high speeds, reducing driving interference and further enhancing driving safety. Throughout the entire process, the driver's line-of-sight distance is minimized, and the operational complexity is zero.

[0155] In one possible implementation, after determining the location allocation of each first application's display area in the vehicle interface, all running first applications are traversed to check if two or more first applications have the same location allocation result, i.e., they are assigned to the same target display area (i.e., both in the first display area, both in the second display area, or both in the third display area). If a conflict is detected, all applications assigned to that target display area are extracted to form a conflict application set. For example, if applications A, B, and C are all assigned to the first display area, then these three applications constitute a conflict set. Further, the startup time of each conflicting application in the current driving cycle is obtained, and the display area of ​​each application in the vehicle interface is re-determined according to a preset conflict handling strategy. If the preset conflict handling strategy is a first-come, first-served strategy, the application with the earliest startup time retains its original target display area; the remaining applications are assigned to alternative display areas (such as the alternative area of ​​the second display area) in order of startup time, or collapsed as status bar icons, or coexist in the original area as tabs.

[0156] In another possible implementation, if the preset conflict handling strategy is the last-to-first strategy, the application that starts latest will preempt the original target display area; the application that originally occupied the area will be downgraded to a status bar icon or moved to another free display area.

[0157] In another possible implementation, if the preset conflict handling strategy is a dynamic priority strategy, each conflicting application can calculate a comprehensive priority score based on preset weight factors (startup time weight, security level weight, and usage frequency weight), and the application with the highest score will obtain the target display area; the remaining applications will be allocated to other areas or collapsed for display in descending order of their scores.

[0158] In this embodiment, when multiple applications have the same location allocation result, the actual display area of ​​each first application in the vehicle interface can be adjusted according to the startup time of each application and its corresponding conflict handling strategy. This avoids information overlap or display conflicts caused by multiple applications competing for the same area, and enables dynamic and orderly allocation of display resources according to a reasonable strategy, thereby improving the information presentation efficiency and driving safety of the vehicle interface in multi-task concurrent scenarios.

[0159] In some embodiments, the above-mentioned "adjusting the current display area position of each first application in the vehicle interface based on the display area allocation result and the startup time corresponding to each first application" may include the following steps: Based on the startup time of each first application, determine the second application with the latest startup time, and determine the display area of ​​the second application in the vehicle interface as the target display area; Based on a pre-set list of downgraded display areas corresponding to the usage category labels, determine the display area of ​​the second application (other than the first application) in the vehicle interface.

[0160] The list of degraded display areas includes multiple degraded target display areas and the priority of each degraded target display area.

[0161] Here, the second application refers to the application that takes priority in occupying the target display area when multiple first applications have the same location allocation result, selected according to preset rules. In this embodiment, the second application is the application with the latest start time in the conflicting application set.

[0162] Here, the third application refers to any application in the conflicting application set other than the second application. The third application needs to be reassigned to another display area instead of continuing to occupy the original target display area.

[0163] Here, the degraded display area list refers to a list of alternative display areas pre-configured for each category label, sorted by priority. When an application is unable to occupy its originally allocated target display area (e.g., it is preempted by the first application), the system attempts to allocate the application to the highest priority available display area in order of priority in this list.

[0164] It is understandable that the list of degraded display areas may differ for different applications using category tags. For example, if the target display area is a long-term viewing application (i.e., the first display area), the degraded display area list may include a first degraded target (a short-term operation application) and a second degraded target (a short-term viewing application); if the target display area is a short-term operation application (i.e., the third display area), the degraded display area list may include a first degraded target (a short-term viewing application) and a second degraded target (a long-term viewing application); if the target display area is a short-term viewing application (i.e., the second display area), the degraded display area list may include a first degraded target (status bar icon) and a second degraded target (rotating overlay).

[0165] In some embodiments, it is detected that two or more applications are assigned to the same target display area (any one of the first, second, or third display areas). The launch time of each application in the conflicting application set is obtained, and the application with the latest launch time is selected as the second application. That is, the second application is considered the application that most needs to be displayed immediately (e.g., an application the user just opened or switched to the foreground), and therefore its original target display area is retained. For each third application other than the second application, a corresponding degraded display area list can be obtained from a pre-stored configuration based on the application's usage category tag (long-term viewing type, short-term viewing type, or short-term operation type). According to the priority order in the degraded display area list, it is determined whether each degraded target display area is currently available (e.g., not occupied by other applications, or allowed to be shared). The first available degraded target display area is assigned to the third application. If all degraded target display areas are unavailable, the third application is collapsed into a status bar icon. Furthermore, the in-vehicle interface can be re-rendered according to the above allocation results.

[0166] In this embodiment, when multiple applications compete for the same target display area, the second application with the latest launch time (i.e., the most recently activated) is prioritized for allocation to that target display area. Then, based on a pre-defined list of degraded display areas corresponding to usage category tags (such as long-term viewing, short-term viewing, short-term operation), other available display areas are allocated to the remaining third applications in order of priority. This conflict resolution mechanism respects the user's recent operational intentions (the most recent application receives the optimal area) and also achieves a reasonable and dynamic reallocation of display resources according to the security interaction needs of each application. This minimizes visual clutter and operational interference when switching between multiple applications while ensuring driving safety.

[0167] In some embodiments, the above-mentioned "determining the display area of ​​a third application (other than the second application) in the vehicle interface based on a pre-set list of degraded display areas corresponding to usage category labels" may include the following steps: The application with the latest startup time and whose application identifier is not updated is identified from multiple third-party applications as the current application; Based on the list of degraded display areas corresponding to the usage category tag of the current application, determine whether there are any free display areas in the list of multiple degraded target display areas; If there are available display areas in multiple downgrade target display areas, the current application will be assigned to the highest priority available display area for display based on the priority of the available display areas, and the application identifier of the current application will be updated to "processed". If there is no free display area in multiple downgrade target display areas, the application identifier of the current application will be updated to the remaining application; Repeat the above steps until the application identifiers of all third-party applications are updated to processed or remaining applications.

[0168] Here, the application identifier refers to a temporary state marker assigned to each application, used to record the application's allocation status during conflict resolution.

[0169] For example, the application identifier may include, but is not limited to: not updated, i.e., the initial state, indicating that the application has not yet been assigned a degraded display area; processed, i.e., the application has been successfully assigned to a degraded display area; remaining application, i.e. the application cannot be assigned temporarily because all degraded target display areas are unavailable.

[0170] The idle display area refers to the area within the current display resources that is not occupied by any application. It can be understood that for the first display area, only a single application is allowed to remain active; if it is occupied, it is considered non-idle. For the second display area, which uses a rotating overlay mechanism, it can be considered as allowing multiple applications to share the space in a time-slice manner. For the third display area, only a single application is allowed to remain active; if it is occupied, it is considered non-idle. For the status bar icon, multiple applications are allowed to exist simultaneously as icons, therefore it is always considered idle.

[0171] In this embodiment of the application, the highest priority free display area can be understood as the first free demoted target display area that is traversed from front to back in the demoted display area list according to priority order.

[0172] In some embodiments, all third applications (i.e., applications other than the second application in the conflicting application set) are obtained, and the application identifier for each third application is initialized to "not updated". Then, a loop processing flow is entered, repeating the following steps until the application identifiers of all third applications are updated to "processed" or "remaining application". From all the third applications with the application identifier "not updated", the one with the latest start time is determined as the current application. Based on the current application's usage category tag (long-term viewing type, short-term viewing type, or short-term operation type), the corresponding degraded display area list is obtained from a preset configuration. The degraded target display areas in this list are sorted by priority from high to low; according to the order of priority from high to low, it is determined whether each degraded target display area is currently an idle display area.

[0173] If a free display area exists, the current application is assigned to the highest priority free display area and its application identifier is updated to "processed". Then, the loop continues to the next round to process the next "not updated" third application.

[0174] If no free display area exists, no degraded display area can be allocated to the current application temporarily. In this case, the application identifier of the current application is updated to "Remaining Application," and the loop continues to process the next "Not Updated" third application. After all "Not Updated" applications have been processed, a second or third round of attempts is made for applications identified as "Remaining Applications" (as the areas of already allocated applications are occupied, applications not allocated in this round may have the opportunity to be allocated in subsequent rounds because some display areas are released after other applications are allocated); then, the application identifiers of all third applications are checked. If the application identifiers of all third applications are "Processed" or "Remaining Applications," the loop terminates. If there are still applications identified as "Not Updated," the loop returns to continue to the next round.

[0175] For example, consider a user continuously opening multiple applications with the same usage characteristics. Assume the vehicle is on an urban expressway at a speed of 50 km / h (without triggering highway correction). The user first opens a map navigation application (for prolonged viewing); then opens an ADAS driving assistance visualization application (used to display lane keeping, obstacle detection, etc., also requiring continuous attention, identified as prolonged viewing); and finally opens a tire pressure monitoring application (used to display tire pressure data in real time, also requiring continuous attention, identified as prolonged viewing).

[0176] The system detected that three applications are currently active (≥2). Application usage characteristics are identified: Map navigation application (long-term viewing); ADAS driving assistance visualization application (users need to continuously monitor the vehicle's surroundings to maintain real-time awareness of safety status); Tire pressure monitoring application (users need to intermittently monitor tire pressure changes to prevent tire blowout risk); Current vehicle speed is 50km / h, below the 80km / h threshold, therefore no correction is triggered. All applications participate in allocation and display normally. According to the rules, all three applications with the "long-term viewing" characteristic are assigned to position ① (the 1 / 3 of the constantly displayed fixed area closest to the driver's side). The system handles conflicts according to the following hierarchy: First level: Tire pressure monitoring (last activated) wins the right to display in position ①. Second layer: Map navigation, as the loser, has its first downgrade target as location ②. Since location ② is currently free, map navigation is downgraded and assigned to location ②. ADAS visualization, as another loser, has its first downgrade target, location ②, already occupied. Therefore, it checks its second downgrade target, location ③. Since location ③ is currently free, ADAS visualization is downgraded and assigned to location ③. Third layer: All applications are already assigned, so there is no need to enter the third layer. The final display result is: Location ① displays tire pressure monitoring, Location ② displays map navigation, and Location ③ displays ADAS visualization.

[0177] Furthermore, if the driver prefers to see map navigation (e.g., when approaching an unfamiliar intersection), they can intervene by manually adjusting the settings: Method 1 (Swap): Drag the tire pressure monitoring app icon to the map navigation app icon position, and the system will swap the display rights of the two.

[0178] Method 2 (Specified): Click the map navigation application directly. The system will force it to be displayed in location ① and move the original application (tire pressure monitoring) to the temporary storage area or assign it to other locations according to the rules.

[0179] Furthermore, assuming the vehicle speed subsequently increases to 80 km / h and is not in intelligent assisted driving mode, the system detects that the speed exceeds the first preset threshold (80 km / h) and automatically triggers driving state correction: applications with "occasional operation" in location ② (the two-thirds area on the far side of the vehicle) are collapsed, but since there are no "occasional operation" applications in this area, map navigation is considered "long-term viewing" and therefore remains unchanged. Optionally, if the vehicle speed further increases to 100 km / h, all long-term viewing applications (such as navigation) can be optimized to a simplified mode, retaining only the most essential information.

[0180] Thus, when multiple equally important security applications need to be displayed simultaneously, this application automatically decides which application to display based on a "last application to open" rule, and rationally arranges other applications in unused areas through a demotion allocation mechanism, maximizing the utilization of screen space and avoiding display errors caused by interface conflicts. Simultaneously, a manual adjustment option is provided as a supplement, ensuring both the rationality of the default allocation and meeting the personalized needs of users. Furthermore, through vehicle speed-linked correction, this invention can automatically optimize the display at high speeds, further ensuring driving safety and achieving a unity of automation, flexibility, and safety.

[0181] In this embodiment, by prioritizing the allocation of applications from the remaining unupdated applications, the application with the latest launch time is selected, ensuring that applications launched later (usually those recently followed by the user) receive a higher priority for demotion allocation, which aligns with user expectations and improves the user experience. Fine-grained tracking of the allocation status using application identifiers (not updated, processed, remaining applications) ensures the controllability and termination of the allocation process, avoiding infinite loops or repeated allocations.

[0182] In some embodiments, the above method further includes: If the application identifier of the third application includes the identifiers of the remaining applications, the third applications are displayed sequentially in the second display area in the form of rotating floating layers according to the startup time order of the third applications corresponding to each remaining application identifier; or, the third applications corresponding to each remaining application identifier are displayed on the vehicle interface in the form of status bar icons.

[0183] Here, rotating overlays refer to the practice where, when the capacity of the second display area (the temporary overlay area near the driver's side) is limited, multiple short-term viewing applications are alternately displayed in the same overlay area according to a time-slice rotation or user interaction trigger. Rotating overlays can prevent a single application from occupying the temporary overlay area for a long time, while ensuring that multiple applications have the opportunity to be viewed by the user.

[0184] The status bar icon refers to the remaining application retaining basic status prompts (such as unread message badges, running status indicators, etc.). Users can open a temporary floating window by clicking the status bar icon to view or operate on it. The floating window will automatically collapse after the user completes the interaction or after a short pause.

[0185] In one possible implementation, a set of remaining applications can be obtained, that is, all applications identified as "remaining applications" are identified as third applications, forming a set of remaining applications; the remaining applications are sorted according to their startup time, for example, applications that were started later are listed first, and applications that were started earlier are listed last; the remaining applications can be displayed in rotation in the second display area according to a preset rotation time interval (e.g., 5 seconds), that is, the second display area is used as the carrier area of ​​the rotation overlay, and each remaining application is displayed in the second display area in the sorted order, and each application stays for a preset time interval before automatically switching to the next application.

[0186] In some embodiments, during the rotation of floating layer displays, users can also perform some interactive operations. For example, a user can click on the currently displayed floating layer area to lock the display of the application and pause the rotation until the user manually unlocks it. For another example, a user can manually switch to the next remaining application by swiping or clicking the rotation button. For yet another example, a user can turn off the floating layer display of a remaining application and remove it from the rotation queue.

[0187] It should be noted that the rotation time interval can be dynamically adjusted based on factors such as vehicle speed, the number of remaining applications, and user settings, but this application embodiment does not impose any limitations on this.

[0188] In another possible implementation, after obtaining the remaining application set, each remaining application can be collapsed into a status bar icon and uniformly displayed in the status bar area of ​​the vehicle interface. Users can click on the status bar icon to expand a temporary floating window for viewing or operation. The floating window will automatically collapse after the user completes the interaction or after a short pause.

[0189] In some embodiments, the status bar icons can be sorted and displayed according to the application's launch time or application name to facilitate quick user location. For example, the application with the latest launch time is displayed first.

[0190] In this embodiment of the application, by providing rotating floating layer display for the remaining applications, multiple remaining applications can be allowed to share temporary floating layer resources, avoiding the problem of information loss caused by a large number of applications being directly downgraded to status bar icons due to insufficient display area. Alternatively, by providing status bar icon display for the remaining applications, the driver's active gaze time and operation frequency on the in-vehicle interface during high-speed driving are effectively reduced, and the risk of driver distraction caused by viewing non-core application information is reduced.

[0191] In some embodiments, the method further includes: in response to a user's drag command on the vehicle interface, moving a third application from the current display area to another display area corresponding to the drag command; and swapping the display areas of the third application and the fourth application if the drag command indicates that the third application should be dragged to the display area of ​​the fourth application; and moving the third application to the free display area if the drag command indicates that the third application should be dragged to the free display area, and determining the application in the original display area of ​​the third application based on the usage category labels of the remaining applications.

[0192] Figure 5 This is a schematic diagram of the overall process of an application display method for an in-vehicle interface provided in an embodiment of this application, as shown below. Figure 5 As shown, it may include S501 to S511, wherein: S501, obtain the usage operations of each first application; S502, determine whether the number of first applications in the running state in the vehicle interface is greater than the first number threshold. If yes, proceed to S504; otherwise, proceed to step S503. S503 displays the application in full screen; S504, determine the usage category label for each first application based on usage operations; Among them, the category labels include long-term viewing type, short-term viewing type, and short-term operation type; S505, determine whether the driving speed is greater than the target driving speed. If yes, proceed to S506; otherwise, proceed to step S507. S506, determine whether the security level of the first application is greater than the preset security level. If yes, proceed to S507; otherwise, proceed to step S508. S507, based on the use of category labels and preset mapping relationships, determine the location allocation result of the display area of ​​the first application in the vehicle interface; S508, the control application is displayed in the vehicle interface as a status bar icon; S509, determine whether there is a conflict in the display area of ​​multiple first applications in the vehicle interface. If so, proceed to S510; otherwise, proceed to step S507. S510: Based on the startup time of each first application, determine the second application with the latest startup time, and determine the display area of ​​the second application in the vehicle interface as the target display area; S511, based on a pre-set list of downgraded display areas corresponding to the usage category labels, determines the display area of ​​the third application (other than the second application) in the vehicle interface.

[0193] The following describes the application of the vehicle interface display method provided in the embodiments of this application in a real-world scenario.

[0194] Based on the above-mentioned technical problems, this application provides a method for allocating the display layout of multiple application interfaces.

[0195] In some embodiments, the following steps may be included: (1) Determine the number of applications that are active in the current interface; the system first detects and determines the number of applications that are active in the current interface (e.g., opened and not closed).

[0196] If only one application is detected as active, the system automatically assigns that application to full-screen mode, and the process ends. If two or more applications are detected as active, the core allocation logic of this application is triggered, and the process proceeds to step 2 below.

[0197] (2) When the number of applications is greater than or equal to 2, the usage characteristics of each application are obtained; in this application, the usage characteristics of an application are defined based on the user's interaction behavior pattern with the application, and the usage characteristics include: viewing characteristics that require continuous or intermittent attention, and operation characteristics that require interaction; the usage characteristics are determined based on absolute thresholds, specifically including: Long-term viewing: Within a preset time window (e.g., 30 seconds), the total duration of a user's gaze at the application exceeds the first threshold (e.g., 5 seconds), and the interval between two gazes is less than the second threshold (e.g., 10 seconds). This type of application requires the driver to maintain continuous attention to keep aware of dynamic information, such as navigation maps and ADAS visualizations. (Note: The time threshold can be recalibrated after multiple experiments). Short-term viewing: The user's single gaze duration is less than the third threshold (e.g., 2 seconds), and there is no repeated gaze within the subsequent preset time; this type of application only needs to quickly obtain information once, such as tire pressure reading, current time, and remaining range; Occasional use: The average interval between two user actions (clicks, swipes, etc.) on the application is greater than the fourth threshold (e.g., 2 minutes). These applications have low interaction frequency and are typically used to respond to state changes or to start / stop simple tasks, such as music player control or air conditioner temperature adjustment. Continuous operation: refers to the need for frequent and continuous interaction by the user during a specific task (operation interval < fifth threshold, such as 5 seconds). In the in-vehicle application scenario of this application, for driving safety considerations, there are no applications with the characteristic of "continuous operation".

[0198] Each application is assigned only one primary usage characteristic, which is determined based on its most prominent behavioral pattern and does not change with minor fluctuations in statistical values. Unlike related technologies that use continuous priority values, the usage characteristics of this invention are discretely classified and remain stable once determined until the application undergoes major updates, thus avoiding frequent layout jumps caused by statistical fluctuations.

[0199] (3) (Driving Status Correction): After completing the application usage feature recognition, the system further obtains the current vehicle driving status, including real-time vehicle speed and driving mode (Sport / Comfort / Economy / Parking). The initial allocation results are corrected based on the driving status: Core principle: When driving at high speeds, reduce applications that require sustained attention or complex interactions, but retain or enhance the ease of short-term viewing.

[0200] 1. High-speed driving correction (vehicle speed > first preset threshold, such as 80km / h, and not in intelligent assisted driving mode): Applications with "occasional operation" characteristics (such as music control and air conditioning adjustment) will be automatically collapsed to reduce the incentive for users to perform unnecessary manual operations while driving at high speeds; applications with "short-term viewing" characteristics (such as tire pressure, time, and battery range) will remain temporarily displayed without being collapsed or simplified, ensuring that users can still quickly obtain key information; applications with "long-term viewing" characteristics (such as navigation and ADAS) will be displayed normally and will not be affected. 2. Low-speed driving correction (vehicle speed < second preset threshold, such as 30km / h): Restore the full display of the "Occasionally Used" app, allowing users more flexibility in their actions.

[0201] 3. Parking mode correction: When the vehicle is in parking assist mode (such as when the reversing camera is on), the system pauses all automatic allocation rules, allowing users to manually adjust or temporarily hide non-safety-related applications to prioritize parking safety.

[0202] Through the above-mentioned driving state correction, the allocation strategy of the present invention can dynamically adapt to different driving environments, further improving driving safety.

[0203] (4) After identifying the usage characteristics of each application, the system determines the display area and corresponding size ratio of each application on the screen according to the preset "interface allocation strategy"; among which, 4.1 Based on the driver's line-of-sight distance and ease of operation, this application pre-divides the in-vehicle screen into three fixed candidate areas: Location ①: The first always-displayed fixed area, located in the longitudinal section of the screen closest to the driver's side. This area is closest to the driver, offering optimal ease of eye movement and operation.

[0204] Location ②: The second constant display area, located in the two-thirds of the screen's longitudinal section closest to the driver's side. This area is slightly further from the driver, making operation relatively less convenient, but it provides a larger display area.

[0205] Location ③: Temporary floating layer area, also close to the driver's side, but floating above the current interface as a temporary floating layer. This floating layer can be automatically collapsed or manually collapsed by the user, and its appearance and hiding do not affect the always-visible layout of the aforementioned locations ① and ②.

[0206] 4.2 Prioritized allocation based on usage characteristics; The system prioritizes allocating applications to display areas that match their usage characteristics, based on the following core rules: Long-term viewing of features → Assign to location ① (the constantly displayed fixed area closest to the driver's side).

[0207] Briefly view the application of the feature → Assign to location ③ (temporary floating area near the driver's side).

[0208] Application of occasional operation features → Assigned to position ② (the constant display fixed area on the driver's side).

[0209] Application of continuous operation features → As mentioned before, there are no such applications in driving scenarios, so no allocation is involved.

[0210] This allocation rule ensures that information requiring the highest level of sustained attention (such as navigation) receives the best visual location, while low-frequency applications (such as music control) are placed in areas with lower ease of operation but larger areas.

[0211] 4.3 Conflict Decision and Degradation Assignment; When multiple applications are assigned to the same display area, it is determined to be a display conflict and handled according to the following three levels: First layer: Winner determination; For multiple applications assigned to the same display area, the system determines a winning application according to the "last opened first" rule, and the winning application obtains the display right of that display area. Specifically, the opening time of each application is compared, and the application with the latest opening time (i.e., the most recently opened) becomes the winner.

[0212] The second layer: demotion allocation; for failed applications that fail to obtain display rights in the same position conflict, the system attempts to allocate them to other free display areas in turn according to the preset demotion priority order.

[0213] In this embodiment, the specific order of degradation priority is shown in Table 1: Table 1

[0214] The specific execution logic of the degradation allocation is as follows: For each failed application, the system first checks whether its first degradation target is free; if it is free, it is allocated to that region; if it is already occupied, it continues to check the second degradation target; if it is still unavailable, it enters the third layer of processing.

[0215] The third layer: Remaining applications; if there are still applications that have not been assigned after the downgrade allocation (for example, when there are more than 4 applications that have been viewed for a long time at the same time), the remaining applications will be displayed in position ③ in a rotating overlay order according to the "last opened first" order, or only their status bar icons will be displayed. Users can expand the full interface by clicking the icons or overlays.

[0216] (5) User manual adjustment (optional step); In order to take into account the personalized preferences of different users, this application also provides an optional manual adjustment mechanism. Users can intervene and modify the allocation results automatically generated in (4) above in real time, specifically including: Designated location application: Users can force any specified application to be placed in any preset display location (location ①, ②, or ③) by dragging and dropping the application icon or other interactive methods.

[0217] Swap Fixed-Position Applications: For two applications that are already displayed in fixed positions (position ① and position ②), users can easily swap their display positions and corresponding window sizes by dragging or clicking.

[0218] Controlling Temporary Overlays: For applications displayed in the temporary overlay area (location ③), users can manually collapse (keeping only a label or icon) or expand them again through interactive methods such as swiping or clicking, so as to flexibly manage the screen space they occupy.

[0219] Through the above steps (1) to (5), this application achieves an adaptive and rational layout of the in-vehicle multi-application interface. This method not only minimizes the driver's eye movement and manual operation, thus improving driving safety, but also fully meets the user's personalized usage needs through optional manual adjustment functions.

[0220] Compared with related technologies, this application has the following advantages: Enhance driving safety: By automatically recognizing the "viewing" or "operating" characteristics of applications, applications that need to be viewed frequently are assigned to the area closest to the driver's seat, while applications that are operated occasionally are assigned to areas with lower operational convenience, minimizing the distance the driver's eyes need to shift and the complexity of operation during driving.

[0221] Optimize screen utilization: Adopt a layout that combines a fixed position for constant display with a temporary overlay. This ensures that applications that require continuous awareness, such as navigation, remain in the optimal area, while applications that are viewed for short periods can appear as overlays without disrupting the overall layout.

[0222] Reduce cognitive load: Through the "last app to open first" conflict decision mechanism, the application that the user is currently most concerned about is always automatically displayed in the optimal position, which meets the user's usage expectations and does not require manual intervention.

[0223] To cater to individual needs: Optional manual adjustment steps are provided, allowing users to fine-tune the automatic allocation while ensuring the reasonableness of the default allocation and satisfying the individual preferences of different users.

[0224] It does not rely on historical statistics: This application performs qualitative classification based on the behavioral pattern characteristics (viewing / operation) of the application, and even newly installed applications can be quickly assigned through preset rules.

[0225] Driving status linkage: This application combines real-time vehicle speed and driving mode to dynamically adjust the allocation strategy (such as automatically retracting occasional operations when driving at high speeds), which is different from general terminal solutions and fully considers the core constraint of driving safety.

[0226] Discrete stable mapping: This application adopts discrete feature classification instead of continuous priority sorting, which avoids frequent changes in interface layout caused by small fluctuations in statistical indicators such as usage time and frequency, and ensures visual stability during driving.

[0227] In some embodiments, the number of currently active applications is detected; if there is only one application, it is displayed in full screen; if there are two or more, the usage characteristics of each application are identified (long-term viewing, short-term viewing, occasional operation, etc.), and adjustments are made based on driving status (vehicle speed, driving mode); then, applications are assigned to preset areas (positions ①, ②, ③) based on usage characteristics; if multiple applications exist in the same area (conflict), conflict decision-making and demotion assignment are performed (the winning application is prioritized, the losing application is demoted to an empty area, and if still not assigned, it is displayed as a rotating overlay or status bar icon); finally, an optional manual adjustment step is provided. This method achieves adaptive and rational layout of multiple application interfaces.

[0228] In some embodiments, when multiple applications are assigned to the same display area, the winning application is first determined according to the "last opened application first" rule, and the winning application obtains the display right for that area. Subsequently, the system processes each failed application sequentially: checking if the target area is free according to a preset demotion priority order (e.g., position ① → position ② → position ③); if free, it is assigned to that area; if occupied, the system continues to check the next lower-level demotion target. After all failed applications have been processed, if there are still applications that have not been assigned, they are displayed in the form of a rotating overlay or status bar icon. This process ensures that all active applications have a reasonable display position, maximizing screen utilization.

[0229] Based on the above embodiments, this application also provides an application display device for an in-vehicle interface. Figure 6 As shown in Figure 6, a schematic diagram of the composition structure of an application display device for an in-vehicle interface provided in an embodiment of this application is provided. The application display device 600 for the in-vehicle interface includes a first determining unit 601, a second determining unit 602, a third determining unit 603, and an adjusting unit 604, wherein: The first determining unit 601 is used to determine the usage category label corresponding to each first application in response to the user's operation on each first application in the vehicle interface. The first application represents the application that is running in the vehicle interface. The second determining unit 602 is used to determine the operation features corresponding to each first application based on the usage operation when the vehicle's driving speed is greater than the target driving speed. The operation features include at least one of operation complexity, gaze duration and operation frequency. The third determining unit 603 is used to determine the position allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the operation characteristics, usage category labels and vehicle driving status corresponding to each first application. The adjustment unit 604 is used to adjust the current display area position of each first application in the vehicle interface based on the display area position allocation result.

[0230] In some embodiments of this application, the third determining unit 603 is specifically used to determine the security level of each first application based on the operation complexity, gaze duration and operation frequency corresponding to each first application; and to determine the position allocation result of the display area of ​​each first application in the vehicle interface based on at least one of the security level, usage category label and vehicle driving state corresponding to each first application.

[0231] In some embodiments of this application, the third determining unit 603 is specifically used to classify the interaction levels of each first application according to the complexity of operation to obtain an interaction level; the interaction level includes a high interaction level, a medium interaction level, and a low interaction level; determine the driving attention occupancy coefficient of each first application according to the gaze duration and the operation frequency; the driving attention occupancy coefficient is proportional to the gaze duration and the driving attention occupancy coefficient is proportional to the operation frequency; weight and fuse the interaction level and the driving attention occupancy coefficient to obtain a comprehensive safety coefficient of each first application; and determine the safety level of each first application according to the comprehensive safety coefficient.

[0232] In some embodiments of this application, the third determining unit 603 is specifically used to determine the position allocation result of the display area of ​​the first application in the vehicle interface based on the usage category label and the preset mapping relationship when the security level corresponding to the first application is greater than the preset security level and the vehicle driving state is driving state; and to control the first application to be displayed in the vehicle interface in the form of a status bar icon when the security level corresponding to the first application is less than or equal to the preset security level and the vehicle driving state is driving state.

[0233] In some embodiments of this application, the category labels used include long-term viewing category, short-term viewing category, and short-term operation category. The third determining unit 603 is specifically used to determine the location allocation result of the first application as a first display area when the usage category label of the first application is a long-term viewing category; wherein the first display area is a fixed area that is always displayed near the driver's side; when the usage category label of the first application is a short-term viewing category, the location allocation result of the first application is determined as a second display area; wherein the second display area is a temporary floating layer area that is near the driver's side; and when the usage category label of the first application is a short-term operation category, the location allocation result of the first application is determined as a third display area; wherein the third display area is a fixed area that is always displayed near the passenger's side.

[0234] In some embodiments of this application, the adjustment unit 604 is specifically used to adjust the current position of each first application in the display area of ​​the vehicle interface based on the position allocation result of the display area and the startup time of each first application when the position allocation result of each first application in the display area of ​​the vehicle interface is the same.

[0235] In some embodiments of this application, the adjustment unit 604 is specifically used to determine the second application with the latest startup time based on the startup time of each first application, and determine the display area of ​​the second application in the vehicle interface as the target display area; and determine the display area of ​​the third application other than the second application in the vehicle interface based on a pre-set list of downgraded display areas corresponding to the usage category tags; wherein, the list of downgraded display areas includes multiple downgraded target display areas and the priority corresponding to each downgraded target display area.

[0236] In some embodiments of this application, the adjustment unit 604 is specifically configured to determine, from multiple third applications, the application with the latest startup time and whose application identifier is not updated as the current application; determine, based on the degraded display area list corresponding to the usage category tag of the current application, whether there are any free display areas in the multiple degraded target display areas in the degraded display area list; if there are free display areas in the multiple degraded target display areas, then the current application is assigned to the highest priority free display area for display according to the priority of the free display areas, and the application identifier of the current application is updated to processed; if there are no free display areas in the multiple degraded target display areas, then the application identifier of the current application is updated to remaining application; the above steps are executed repeatedly until the application identifiers of all third applications are updated to processed or remaining application.

[0237] In some embodiments of this application, the above-mentioned vehicle interface application display device 600 further includes a display unit, which is used to display the third application in the second display area in the form of a rotating floating layer according to the startup time order of the third application corresponding to each remaining application identifier when the application identifier of the third application includes the remaining application identifier; or, to display the third application corresponding to each remaining application identifier in the form of a status bar icon on the vehicle interface.

[0238] In some embodiments of this application, the first determining unit 601 is specifically configured to: within a first duration, if the total duration of the user's gaze on the first application is greater than or equal to a first duration threshold and the duration interval between two gazes is less than or equal to a second duration threshold, then determine the usage category label of the first application as a long-term viewing category; if the duration of a single gaze on the first application is less than or equal to a third duration threshold and there is no gaze within the second duration, then determine the usage category label of the first application as a short-term viewing category; if the duration interval between two operations on the first application is greater than or equal to a fourth duration threshold and the duration of a single operation is less than or equal to a fifth duration threshold, then determine the usage category label of the first application as a short-term operation category.

[0239] It should be noted that, in the embodiments of this application, if the above method is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0240] Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, magnetic disks, or optical disks. Therefore, the embodiments of this application are not limited to any specific hardware and software combination.

[0241] This application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the above-described method.

[0242] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described method. The computer-readable storage medium can be transient or non-transient.

[0243] This application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof.

[0244] In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0245] It should be noted that, Figure 7 This is a hardware entity diagram of an electronic device provided in an embodiment of this application, such as... Figure 7 As shown, the hardware entity of the electronic device 700 includes: a processor 701, a communication interface 702, and a memory 703, wherein: The processor 701 typically controls the overall operation of the electronic device 700.

[0246] The communication interface 702 enables the electronic device 700 to communicate with other terminals or servers via a network.

[0247] The memory 703 is configured to store instructions and applications executable by the processor 701, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 701 and various modules in the electronic device 700. It can be implemented using flash memory or RAM. Data transfer between the processor 701, the communication interface 702, and the memory 703 can be performed via bus 704.

[0248] It should be noted that the descriptions of the storage medium and device embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0249] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0250] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

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

[0252] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0253] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0254] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory, magnetic disks, or optical disks.

[0255] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0256] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A method for displaying an in-vehicle interface, characterized in that, The method includes: In response to the user's operation on each first application in the vehicle interface, a usage category label corresponding to each first application is determined, and the first application represents the application that is running in the vehicle interface. When the vehicle's speed is greater than the target speed, based on the usage operation, the operation feature corresponding to each of the first applications is determined, and the operation feature includes at least one of operation complexity, gaze duration, and operation frequency. Based on at least one of the operation characteristics corresponding to each of the first applications, the usage category label, and the vehicle driving status, determine the position allocation result of the display area of ​​each of the first applications in the vehicle interface; Based on the position allocation result of the display area, the position of the current display area of ​​each of the first applications in the vehicle interface is adjusted.

2. The method according to claim 1, characterized in that, The step of determining the position allocation result of the display area of ​​each of the first applications in the vehicle interface based on at least one of the operation characteristics corresponding to each of the first applications, the usage category label, and the vehicle driving state includes: The security level of each first application is determined based on the operation complexity, gaze duration, and operation frequency corresponding to each first application. Based on at least one of the security level corresponding to each of the first applications, the usage category label, and the vehicle driving status, the location allocation result of the display area of ​​each of the first applications in the vehicle interface is determined.

3. The method according to claim 2, characterized in that, The step of determining the security level of each first application based on the operation complexity, gaze duration, and operation frequency corresponding to each first application includes: Based on the operational complexity, the interaction levels of each of the first applications are classified to obtain an interaction level; the interaction level includes high interaction level, medium interaction level and low interaction level. Based on the gaze duration and the operation frequency, a driving attention occupancy coefficient for each of the first applications is determined; the driving attention occupancy coefficient is proportional to the gaze duration and the operation frequency. The interaction level and the driving attention occupancy coefficient are weighted and fused to obtain the comprehensive safety coefficient of each of the first applications; The security level of each of the first applications is determined based on the comprehensive security coefficient.

4. The method according to claim 2, characterized in that, The step of determining the location allocation result of the display area of ​​each of the first applications in the vehicle interface based on at least one of the security level corresponding to each of the first applications, the usage category label, and the vehicle driving status includes: For each of the first applications, if the security level corresponding to the first application is greater than the preset security level and the vehicle driving state is in a driving state, the location allocation result of the display area of ​​the first application in the vehicle interface is determined based on the usage category label and the preset mapping relationship. When the security level corresponding to the first application is less than or equal to the preset security level, and the vehicle is in driving mode, the first application is controlled to be displayed on the vehicle interface as a status bar icon.

5. The method according to claim 4, characterized in that, The usage category tags include long-term viewing categories, short-term viewing categories, and short-term operation categories. The determination of the location allocation result of the display area of ​​the first application in the vehicle interface based on the usage category tags and a preset mapping relationship includes: If the usage category label of the first application is the long-term viewing category, the location allocation result of the first application is determined to be the first display area; wherein, the first display area is a fixed area that is always displayed near the driver's side; If the usage category label of the first application is the short-term viewing category, the location allocation result of the first application is determined to be the second display area; wherein, the second display area is a temporary floating layer area close to the driver's side; If the usage category label of the first application is the short-term operation category, the location allocation result of the first application is determined to be the third display area; wherein, the third display area is a fixed display area near the passenger side.

6. The method according to any one of claims 1 to 5, characterized in that, The step of adjusting the position of the current display area of ​​each of the first applications in the vehicle interface based on the position allocation result of the display area includes: If the position allocation results of the display areas of each of the first applications in the vehicle interface are the same, the position of the current display area of ​​each of the first applications in the vehicle interface is adjusted based on the position allocation results of the display areas and the startup time of each of the first applications.

7. The method according to claim 6, characterized in that, The step of adjusting the current display area position of each of the first applications in the vehicle interface based on the location allocation result of the display area and the startup time of each of the first applications includes: Based on the startup time of each of the first applications, the second application with the latest startup time is determined, and the display area of ​​the second application in the vehicle interface is determined as the target display area. Based on a pre-set list of degraded display areas corresponding to the usage category labels, the display area of ​​a third application (other than the second application) in the vehicle interface is determined; wherein, the list of degraded display areas includes multiple degraded target display areas and a priority corresponding to each degraded target display area.

8. The method according to claim 7, characterized in that, The step of determining the display area of ​​a third application (other than the second application) in the vehicle interface based on a pre-set list of downgraded display areas corresponding to the usage category label includes: From among the multiple third applications, the application with the latest startup time and whose application identifier is not updated is determined as the current application; Based on the list of degraded display areas corresponding to the usage category tag of the current application, determine whether there are any free display areas in the list of multiple degraded target display areas; If there are idle display areas in multiple downgraded target display areas, the current application is assigned to the idle display area with the highest priority according to the priority of the idle display areas, and the application identifier of the current application is updated to "processed". If none of the multiple downgraded target display areas have free display areas, then the application identifier of the current application will be updated to the remaining application; Repeat the above steps until the application identifiers of all third-party applications are updated to processed or remaining applications.

9. The method according to claim 8, characterized in that, The method further includes: If the application identifier of the third application includes the remaining application identifier, the third application is displayed sequentially in the second display area in the form of a rotating floating layer according to the startup time order of the third application corresponding to each remaining application identifier; or, the third application corresponding to each remaining application identifier is displayed on the vehicle interface in the form of a status bar icon.

10. The method according to any one of claims 1 to 5, characterized in that, The step of responding to user operations on various first applications in the in-vehicle interface and determining the usage category tag corresponding to each first application includes: If, within a first duration, the total duration of a user's gaze on the first application is greater than or equal to a first duration threshold and the duration interval between two gazes is less than or equal to a second duration threshold, then the usage category label of the first application is determined to be a long-term viewing category. If the user's single gaze duration on the first application is less than or equal to the third duration threshold and there is no gaze within the second duration, then the usage category label of the first application is determined to be the short-term viewing category. If the time interval between two user operations on the first application is greater than or equal to the fourth time threshold and the duration of a single operation is less than or equal to the fifth time threshold, then the usage category label of the first application is determined to be a short-term operation category.

11. An application display device for an in-vehicle interface, characterized in that, The device includes: The first determining unit is used to determine the usage category label corresponding to each first application in response to the user's operation on each first application in the vehicle interface. The first application represents the application that is running in the vehicle interface. The second determining unit is used to determine, based on the usage operation, an operation feature corresponding to each of the first applications when the vehicle's driving speed is greater than the target driving speed. The operation feature includes at least one of operation complexity, gaze duration, and operation frequency. The third determining unit is used to determine the position allocation result of the display area of ​​each of the first applications in the vehicle interface based on at least one of the operation characteristics corresponding to each of the first applications, the usage category label and the vehicle driving state. An adjustment unit is used to adjust the current position of the display area of ​​each of the first applications in the vehicle interface based on the position allocation result of the display area.

Images