Multi-view display method, device, vehicle, medium and product

Abstract

Embodiments of the present application provide a multi-view display method, device, vehicle, medium and product. The method comprises: determining an instrument data display area and a status bar data display area according to a display mode of a vehicle screen; obtaining a first instrument view set and a first status bar view set; filtering out a second instrument view set and a display position of a target instrument view thereof, and a second status bar view set and a display position of a target status bar view thereof according to a preset view display strategy, the instrument data display area and the status bar data display area; determining whether there is an overlap according to the display positions of the target instrument view and the target status bar view; if there is an overlap, adjusting the target status bar view and the display position thereof in the second status bar view set according to a priority of the target status bar view until there is no overlap; and if there is no overlap, displaying according to the respective display positions. The method improves the comprehensiveness of important information display.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to a multi-view display method, device, vehicle, medium, and product. Background Technology

[0002] With the rapid development of intelligent vehicle technology, in-vehicle human-machine interaction systems are evolving from traditional single-function instrument panels to multi-screen integrated intelligent cockpits. Current mainstream multi-screen configurations typically include a first screen for the driver (such as an integrated instrument cluster and center console screen) and a second screen for the passenger (such as an infotainment screen), aiming to enhance information capacity through the expansion of physical screens. However, how to achieve coordinated interaction and efficient management of application views across multiple screens has become a pressing technical problem to be solved in the field of intelligent cockpit human-machine interaction.

[0003] To address the aforementioned requirements, the current approach primarily involves detecting whether multiple floating application views are arranged in a stacked manner on the vehicle's display screen. The applications loaded in these views are independent of the desktop applications on the first and second screens. When a stacked view is detected, the task priority of the current application for each view is retrieved from a preset application priority mapping table. Based on the priority, the display level of each view is determined, with higher priority views being displayed closer to the top layer.

[0004] However, existing technologies have a technical problem where important information cannot be fully displayed. Summary of the Invention

[0005] This application provides multi-view display methods, devices, vehicles, media, and products to achieve the technical effect of improving the comprehensiveness of important information display.

[0006] In a first aspect, embodiments of this application provide a multi-view display method, including:

[0007] Determine the instrument panel data display area and the status bar data display area based on the vehicle screen's display mode;

[0008] Obtain the first set of instrument view and the first set of status bar view to be displayed;

[0009] Based on the preset view display strategy, the instrument data display area, and the status bar data display area, the first instrument view set is filtered to determine the display position of the second instrument view set and the target instrument view it contains. Similarly, the first status bar view set is filtered to determine the display position of the second status bar view set and the target status bar view it contains.

[0010] Based on the display position of the target instrument view and the display position of the target status bar view, determine whether there are overlapping views;

[0011] If there are overlapping views, the target status bar views contained in the second status bar view set and their corresponding display positions are readjusted according to the priority of the target status bar view until there are no overlapping views.

[0012] If there is no view overlap, the target status bar view and the target instrument panel view are displayed on the vehicle screen according to their respective display positions.

[0013] In one possible implementation, the step of readjusting the target status bar views and their corresponding display positions contained in the second status bar view set according to the priority of the target status bar views includes:

[0014] Step a: Update the status bar data display area based on the display position of the target instrument view;

[0015] Step b: Filter the second status bar view set according to the priority of the target status bar view;

[0016] Step c: Based on the updated status bar data display area, determine the updated display position of the remaining target status bar views in the second status bar view set;

[0017] Step d: Determine whether the corresponding total display area is within the updated status bar data display area based on the remaining target status bar view;

[0018] If not, repeat steps b through d until the total display area of ​​the remaining target status bar view is within the updated status bar data display area.

[0019] In one possible implementation, filtering the second set of status bar views according to the priority of the target status bar view includes:

[0020] Remove the highest priority target status bar view from the second status bar view set.

[0021] In one possible implementation, filtering the second set of status bar views according to the priority of the target status bar view includes:

[0022] The target status bar view with the highest priority is determined from the second set of status bar views;

[0023] If the target status bar view with the highest priority is a very visible view, then the target status bar view with the highest priority is removed from the second status bar view set;

[0024] If the target status bar view with the highest priority is a constantly displayed view, then the non-displayed view with the highest priority is determined from the second set of status bar views.

[0025] Calculate the priority difference between the target status bar view with the highest priority and the non-display view with the highest priority;

[0026] If the priority difference is greater than the preset priority difference, then the target status bar view with the highest priority is removed from the second status bar view set;

[0027] If the priority difference is less than or equal to the preset priority difference, then the most prominent view with the highest priority is removed from the second status bar view set.

[0028] In one possible implementation, the preset view display strategy includes at least one of the following:

[0029] For the same instrument signal, remove the outdated initial instrument view from the first instrument view set;

[0030] Initial instrument views with a priority greater than a preset priority are filtered out from the first instrument view set;

[0031] During the filtering process of the first status bar view set, the initial status bar view with higher priority is filtered out before the initial status bar view with lower priority.

[0032] During the filtering process of the first status bar view set, the most prominent initial status bar view is filtered out because it is superior to the normally prominent initial status bar view.

[0033] The total display area of ​​the second status bar view set is limited to the area within the status bar data display area.

[0034] In one possible implementation, the display mode of the vehicle screen includes any one of single-screen display, dual-screen extended display, and full-screen splicing display.

[0035] Secondly, embodiments of this application provide a multi-view display device, including:

[0036] The first determining module is used to determine the instrument panel data display area and the status bar data display area according to the display mode of the vehicle screen;

[0037] The acquisition module is used to acquire the first set of instrument views and the first set of status bar views to be displayed;

[0038] The processing module is used to filter the first instrument view set according to the preset view display strategy, the instrument data display area and the status bar data display area, to determine the display position of the second instrument view set and the target instrument view contained therein, and to filter the first status bar view set to determine the display position of the second status bar view set and the target status bar view contained therein.

[0039] The second determining module is used to determine whether there are overlapping views based on the display position of the target instrument view and the display position of the target status bar view;

[0040] The adjustment module is used to readjust the target status bar views and their corresponding display positions contained in the second status bar view set according to the priority of the target status bar view if there are overlapping views, until there are no overlapping views.

[0041] The display module is used to display the target status bar view and the target instrument view on the vehicle screen according to their respective display positions if there is no view overlap.

[0042] In one possible implementation, the adjustment module is specifically used for:

[0043] Step a: Update the status bar data display area based on the display position of the target instrument view;

[0044] Step b: Filter the second status bar view set according to the priority of the target status bar view;

[0045] Step c: Based on the updated status bar data display area, determine the updated display position of the remaining target status bar views in the second status bar view set;

[0046] Step d: Determine whether the corresponding total display area is within the updated status bar data display area based on the remaining target status bar view;

[0047] If not, repeat steps b through d until the total display area of ​​the remaining target status bar view is within the updated status bar data display area.

[0048] In one possible implementation, the adjustment module is specifically used for:

[0049] Remove the highest priority target status bar view from the second status bar view set.

[0050] In one possible implementation, the adjustment module is specifically used for:

[0051] The target status bar view with the highest priority is determined from the second set of status bar views;

[0052] If the target status bar view with the highest priority is a very visible view, then the target status bar view with the highest priority is removed from the second status bar view set;

[0053] If the target status bar view with the highest priority is a constantly displayed view, then the non-displayed view with the highest priority is determined from the second set of status bar views.

[0054] Calculate the priority difference between the target status bar view with the highest priority and the non-display view with the highest priority;

[0055] If the priority difference is greater than the preset priority difference, then the target status bar view with the highest priority is removed from the second status bar view set;

[0056] If the priority difference is less than or equal to the preset priority difference, then the most prominent view with the highest priority is removed from the second status bar view set.

[0057] In one possible implementation, the preset view display strategy includes at least one of the following:

[0058] For the same instrument signal, remove the outdated initial instrument view from the first instrument view set;

[0059] Initial instrument views with a priority greater than a preset priority are filtered out from the first instrument view set;

[0060] During the filtering process of the first status bar view set, the initial status bar view with higher priority is filtered out before the initial status bar view with lower priority.

[0061] During the filtering process of the first status bar view set, the most prominent initial status bar view is filtered out because it is superior to the normally prominent initial status bar view.

[0062] The total display area of ​​the second status bar view set is limited to the area within the status bar data display area.

[0063] In one possible implementation, the display mode of the vehicle screen includes any one of single-screen display, dual-screen extended display, and full-screen splicing display.

[0064] Thirdly, embodiments of this application provide a vehicle, including: a vehicle body, a memory, and a processor;

[0065] The memory stores computer-executed instructions;

[0066] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0067] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0068] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0069] The multi-view display method, apparatus, vehicle, medium, and product provided in this application determine the instrument panel data display area and the status bar data display area based on the display mode of the vehicle screen. Then, a first set of instrument panel views and a first set of status bar views to be displayed are obtained. Based on a preset view display strategy, the instrument panel data display area, and the status bar data display area, the first set of instrument panel views is filtered to determine a second set of instrument panel views and the display positions of the target instrument panel views contained therein. Similarly, the first set of status bar views is filtered to determine the second set of status bar views and the display positions of the target status bar views contained therein. Then, based on the display positions of the target instrument panel views and the target status bar views, it is determined whether there are overlapping views. If overlapping views exist, the target status bar views contained in the second set of status bar views and their corresponding display positions are readjusted according to the priority of the target status bar views until no overlapping views exist. If no views overlap, they are displayed on the vehicle screen according to their respective display positions on the target status bar views and target instrument panel views. This technical solution enables the orderly coexistence of the instrument panel view and the status bar view within a limited screen space. While ensuring that the display position of the target instrument panel view is not affected, it solves the problem of overlapping and occlusion of multiple views by dynamically adjusting the target status bar view and its display position based on priority only in the second status bar view set. This avoids the shortcomings of existing technologies that rely solely on simple hierarchical coverage, which leads to mutual occlusion of important information. It significantly improves the collaborative display capability of multi-task information and driving safety in multi-screen display scenarios, and ensures the comprehensiveness of important information display. Attached Figure Description

[0070] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0071] Figure 1A schematic diagram of the architecture of the multi-view display system provided in this application;

[0072] Figure 2 Flowchart of the multi-view display method provided in this application Figure 1 ;

[0073] Figure 3 Flowchart of the multi-view display method provided in this application Figure 2 ;

[0074] Figure 4 Flowchart of the multi-view display method provided in this application Figure 3 ;

[0075] Figure 5 A schematic diagram of the structure of the multi-view display device provided in this application;

[0076] Figure 6 This is a structural diagram of the vehicle provided in this application.

[0077] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0078] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0079] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0080] In existing technologies, when multiple application views with high priority appear simultaneously, they are simply covered according to a fixed priority order. The highest priority view obscures other important views, and users cannot obtain information from multiple tasks at the same time. This results in important information being obscured from each other and the inability to achieve collaborative and orderly display of information from multiple tasks. Therefore, there is a technical problem that important information cannot be fully displayed.

[0081] Based on the aforementioned technical problems, the technical concept of this application is as follows: During the research of multi-view display solutions, the inventors discovered that existing technologies only overlay views according to priority after they appear. While this can highlight the highest priority view, the problem of mutual occlusion cannot be avoided when multiple high-priority views appear simultaneously. If multi-view coexistence can replace priority-based overlay display, that is, if a first set of instrument views and a first set of status bar views are pre-filtered according to a preset view display strategy, instrument data display area, and status bar data display area, and the target instrument views included in the second set of instrument views and the target status bar views included in the second set of status bar views are pre-assigned their respective display positions; then, it is determined whether the target instrument views and target status bar views overlap. If overlap exists, the target status bar views are repeatedly adjusted according to their priority until the overlap is eliminated. Finally, the target instrument views and target status bar views are displayed on the vehicle screen according to their final determined display positions, thus enabling the simultaneous display of multiple important pieces of information on the vehicle screen and improving the comprehensiveness of the display of important information.

[0082] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0083] For example, the multi-view display method provided in this application can be applied to a multi-view display system. Figure 1 This is a schematic diagram of the architecture of the multi-view display system provided in this application. Figure 1 As shown, the multi-view display system includes: a data layer, a business capability layer, a capability layer, a view control layer, and a user interface (UI) view layer.

[0084] The data layer stores and defines the data involved in the multi-view display method. This data includes instrument data, priority data, status bar content beans, and other data. Specifically, instrument data contains the information that the instrument view needs to display, such as vehicle speed, battery level, and ADAS alarm status; priority data defines the priority of each view; status bar content beans define the data model of the status bar view, such as name, location, whether it is always visible, and priority; other data includes data generated during method execution and data reserved for future use.

[0085] The business capability layer supports expansion based on different business needs, isolates different channels, provides reusable business capabilities to external applications, and has the ability to interact with external modules. It includes a desktop mode manager, a meter communication module, a priority manager, and a status bar data control library. Specifically, the desktop mode manager communicates with the desktop application to obtain or issue desktop mode switching commands and reports the corresponding values ​​to the view control layer. For example, desktop modes include 1X, 3X, and 6X, used to determine the display size of the view. The meter communication module communicates with the meter service to obtain meter light signals and assembles the data for the view control layer. It should be understood that the meter service is an external module, and external modules also include the desktop. The priority manager manages the priority of each view and reports the priority information to the view control layer. The status bar data control library provides reusable status bar view controls.

[0086] The capability layer provides commonly used, non-business-related basic capabilities that can be reused in other applications, including Gaussian blur capability, data storage capability, and update capability. For example, the update capability can be specifically implemented as a version upgrade capability.

[0087] The view control layer is responsible for retrieving relevant data from the business capability layer and the capability layer based on business needs, processing the data according to a preset view display strategy, and feeding the final result back to the view layer. It also controls the display and hiding of the view. This approach decouples data, business logic, and view presentation, ensuring the accuracy and flexibility of the view display. The view control layer includes a view layer display form controller, a status bar view and dashboard view overlap manager, and a status bar view and dashboard view display strategy manager. Specifically, the view layer display form controller determines the view's display size based on the desktop layout; the status bar view and dashboard view overlap manager determines whether there is overlap between the status bar view and the dashboard view; and the status bar view and dashboard view display strategy manager configures the view display strategy.

[0088] For example, the preset view display strategy includes at least one of the following:

[0089] 1. When views overlap, prioritize hiding views with lower priority;

[0090] 2. For the same display area, when a new view signal or status change is received, the later reported view will overwrite the previously displayed view;

[0091] 3. When a view needs to be hidden, the non-displayable view is hidden before the always-displayable view; the display priority of the instrument view is higher than that of the status bar view, that is, in the event of a conflict, the display of the instrument view is guaranteed first.

[0092] 4. When the content of the instrument view exceeds its preset minimum display area, the boundary of the instrument display area is expanded to fully display the content of the instrument view;

[0093] 5. When the instrument view content is zoomed out, the status bar views that were not displayed in the status bar display area will be displayed one by one in order of priority from high to low.

[0094] The UI view layer is primarily responsible for displaying or hiding the corresponding views based on the data uploaded from the view control layer, and for distributing user actions to the view control layer for business processing. The view layer is managed using view layers, including the dashboard area and the status bar area. The dashboard area further includes the actual dashboard area and the mini status bar area. The actual dashboard area displays the dashboard data, the mini status bar area is the portion of the status bar data display area that can be encroached upon by the dashboard view, and the status bar area is the portion of the status bar data display area that cannot be encroached upon by the dashboard view.

[0095] In practical applications, the multi-view display system adopts a modular + Model-View-ViewModel (MVVM) architecture to isolate data, business logic, basic capabilities, repository (REPO), and view layer.

[0096] It should be understood that while introducing the multi-view display method below, we will further explain the actual processing procedures of each part of the above multi-view display system, which will not be repeated here.

[0097] Figure 2 Flowchart of the multi-view display method provided in this application Figure 1 ,like Figure 2 As shown, the method includes:

[0098] S21. Determine the instrument panel data display area and the status bar data display area according to the vehicle screen display mode.

[0099] Among them, vehicle screens refer to physical display screens installed in the vehicle cabin. The number of such physical display screens can be one, two, or more.

[0100] For example, the physical display screen can be an instrument panel screen, a central control screen, or a passenger entertainment screen.

[0101] Furthermore, the vehicle screen's display modes include any one of single-screen display, dual-screen extended display, or full-screen splicing display.

[0102] Taking a vehicle screen as an example of two physical displays, single-screen display means using only one of the physical displays, dual-screen extended display means treating the two physical displays as two independent display areas, and full-screen splicing display (also known as integrated screen display) means treating the two physical displays as a continuous logical canvas.

[0103] The instrument data display area refers to the area used to display the target instrument view. In practical applications, it is usually located on the left side of the vehicle screen so that the driver can easily view it.

[0104] For example, the instrument panel data display area can be used to display Advanced Driver Assistance Systems (ADAS) warning views, vehicle status views, and speed limit reminder views, etc.

[0105] Similarly, the status bar data display area is the area used to display the target status bar view, and in practical applications, it is usually located on the right side of the vehicle screen.

[0106] For example, the status bar data display area can be used to display a system signal strength view, a Bluetooth connection status view, and an unread message notification view, etc.

[0107] In practical applications, different display modes are pre-configured with corresponding instrument data display areas and status bar data display areas. For example, in full-screen splicing display, the right 50% width of the entire logical canvas can be designated as the status bar data display area, and the left 50% width as the instrument data display area; in single-screen display, the right 30% width of the entire logical canvas is designated as the status bar data display area, and the left 70% width as the instrument data display area.

[0108] It should be understood that, under different display modes, the specific location and size of the instrument display area and the status bar display area on the vehicle screen can be pre-configured according to the actual situation, and this application embodiment does not impose specific restrictions on this.

[0109] S22. Obtain the first set of instrument view to be displayed and the first set of status bar view.

[0110] The first instrument view set refers to the set of all initial instrument views requested to be displayed in the instrument data display area. Each initial instrument view corresponds to a specific business function or vehicle status information, and is usually dynamically generated and reported by the instrument communication module or business capability layer.

[0111] For example, when the advanced driver assistance system detects a forward collision risk, the instrument communication module generates an ADAS warning view and adds it to the first instrument view set; when the navigation system issues a steering command, it generates a navigation guidance view and adds it to the first instrument view set; when the vehicle battery level is below a threshold, the vehicle status monitoring module generates a low battery warning view and adds it to the first instrument view set.

[0112] It should be understood that the ADAS warning view, navigation guidance view, and low battery warning view mentioned above are all initial instrument panel views.

[0113] The first status bar view set refers to the set of initial status bar views that are displayed in the status bar data display area for all requests. Each initial status bar view corresponds to a system status icon, notification prompt, or temporary interactive feedback, which is usually dynamically generated and reported by various business modules (such as Bluetooth service, network service, message notification service, etc.).

[0114] For example, when a Bluetooth device successfully connects, the Bluetooth service generates a Bluetooth connection status view and adds it to the first status bar view set; when the network signal strength changes, a corresponding system signal strength view is generated and added to the first status bar view set; when a new instant message is received, an unread message notification view is generated and added to the first status bar view set.

[0115] It should be understood that the Bluetooth connection status view, system signal strength view, and unread message notification view mentioned above are all initial status bar views.

[0116] In practical applications, based on Figure 1 The view control layer continuously listens for view requests from the instrument communication module and various business modules (such as Bluetooth service, network service, message notification service, etc.). Whenever a new instrument view request is generated, the corresponding initial instrument view is added to the first instrument view set; whenever a new status bar view request is generated, the initial status bar view is added to the first status bar view set.

[0117] The first instrument cluster view set and the first status bar view set are dynamically changing, updating in real time as new view requests arrive or old view requests are withdrawn. For example, for a period after the vehicle is started, the first instrument cluster view set may include ADAS warning views, navigation guidance views, and low battery warning views, while the first status bar view set may include Bluetooth connection status views, system signal strength views, and unread message notification views. The view control layer continuously monitors these changes to ensure that the acquired first instrument cluster view set and first status bar view set always reflect the latest display requirements.

[0118] S23. Based on the preset view display strategy, instrument data display area and status bar data display area, filter the first instrument view set to determine the display position of the second instrument view set and the target instrument view it contains, and filter the first status bar view set to determine the display position of the second status bar view set and the target status bar view it contains.

[0119] The preset view display strategy refers to a predefined set of rules used to determine which views should be displayed and which should be hidden or delayed in display. These rules can be formulated from multiple dimensions based on actual business needs, such as priority, view type, time order, content importance, and whether it is a frequently displayed view.

[0120] based on Figure 1 Priorities are preset and dynamically updated by the priority manager based on the view's business attributes. For example, status bar views related to driving safety alarms may be given the highest priority; core system status views may be given medium priority; and ordinary application push notifications may be given lower priority.

[0121] It should be understood that the smaller the priority value, the higher the importance and priority.

[0122] "Constantly displayed" refers to the view type that is continuously displayed on the vehicle screen. Constantly displayed views are usually related to core system status or basic functions and need to be continuously presented to the user for a long time. "Partially displayed" refers to the view type that appears temporarily in specific scenarios and disappears automatically after the conditions are met. Partially displayed views correspond to temporary notifications, brief prompts, or interactive feedback. Their display is time-sensitive and can be prioritized for hiding when space is insufficient.

[0123] For example, the system signal strength view and the Bluetooth connection status view are both always-visible views. These views occupy a fixed position in the status bar data display area for a long time, providing continuous information feedback to the user. The unread message notification view and the voice assistant wake-up status view are both never-visible views. These views are removed from the status bar data display area after the triggering conditions disappear or after the user views them.

[0124] exist Figure 1 Based on this, preset view display strategies can be stored in the view display strategy manager.

[0125] In practical applications, the preset view display strategy includes at least one of the following:

[0126] 1. For the same instrument signal, remove the non-latest initial instrument view from the first instrument view set;

[0127] In practical applications, based on Figure 1Each view request sent by the instrument communication module carries a signal identifier and a timestamp. The view control layer groups the initial instrument views in the first instrument view set according to the signal identifier, with the same signal identifier corresponding to the same instrument signal. For each group of initial instrument views with the same signal identifier, the view control layer identifies the latest view based on the timestamp and removes the remaining non-latest initial instrument views in the group from the first instrument view set.

[0128] For example, when an advanced driver assistance system detects a collision risk, it sends a mild warning view, followed by an emergency warning view when the risk escalates. Both views carry the same signal identifier but different timestamps. Only the later-sent emergency warning view is retained, while the previous mild warning view is removed from the first set of instrument panel views, ensuring that the displayed content always reflects the latest risk level.

[0129] By employing the above methods, the repeated or incorrect presentation of multiple historical versions of the same signal in the display area is avoided, ensuring the real-time performance and accuracy of the instrument information display.

[0130] 2. Filter out initial instrument views with a priority higher than the preset priority from the first instrument view set;

[0131] It should be understood that the preset priority can be pre-set based on empirical or experimental values, and this application embodiment does not impose specific restrictions on this.

[0132] 3. During the filtering process of the first set of status bar views, the initial status bar views with higher priority are filtered out before the initial status bar views with lower priority.

[0133] In practical applications, the view display strategy manager first associates a priority with each initial status bar view in the first status bar view set, and then sorts these initial status bar views in descending order of priority. When the display area controller reports insufficient space, the view display strategy manager selects the initial status bar views with the highest priority in the sorted order for elimination. After eliminating each initial status bar view, it re-evaluates whether the remaining space meets the display requirements, until the remaining initial status bar views can be fully accommodated. This method ensures that views with lower priority are retained.

[0134] 4. During the filtering process of the first status bar view set, the most prominent initial status bar view is filtered out because it is superior to the normally prominent initial status bar view.

[0135] In practical applications, the view display strategy manager first identifies the type attribute of each initial status bar view in the first status bar view set, dividing them into two categories: frequently displayed views and infrequently displayed views. When the display area controller reports insufficient space, the view display strategy manager prioritizes selecting objects to be removed from the infrequently displayed views. If space is still insufficient after removing all infrequently displayed views, then the view with the highest priority from the frequently displayed views is considered for removal. This approach ensures the display stability of the frequently displayed views and prevents the core system status from being frequently hidden due to temporary notifications.

[0136] 5. Limit the total display area of ​​the second status bar view collection to the area within the status bar data display area.

[0137] It should be understood that when the preset view display strategy includes both 3 and 4 above, when determining the initial status bar views to be removed from the first status bar view set, a strategy of prioritizing type over priority can be adopted, or a strategy of combining type and priority can be adopted. The specific implementation is as follows:

[0138] Following a type-first-priority strategy, when the display area controller reports insufficient space in the status bar display area, the view display strategy manager prioritizes culling from the non-displayable view subset. Within this subset, the view display strategy manager culls the highest-priority non-displayable views in descending order of priority value, reassessing the remaining space after each culling to ensure sufficient display space. If, after culling all non-displayable views, the space is still insufficient to accommodate all frequently displayed views, the view display strategy manager then enters the frequently displayed view subset, similarly culling the highest-priority frequently displayed views in descending order of priority value, until the remaining views can be fully accommodated.

[0139] For the type and priority fusion decision, the initial status bar view with the highest priority is determined from the current first status bar view set as the first candidate view, and the type of the first candidate view is identified. If the first candidate view is a non-displayable view, it is directly removed from the first status bar view set as a priority elimination object. If the first candidate view is a frequently displayed view, the non-displayable view with the highest priority is determined from the remaining views in the current first status bar view set excluding the first candidate view as the second candidate view. The priority difference between the first candidate view and the second candidate view is calculated. If the priority difference is greater than a preset priority difference threshold, it indicates that the priority of the frequently displayed view is lower than that of the available non-displayable views, and the first candidate view (frequently displayed view) is removed from the first status bar view set. If the priority difference is less than or equal to the preset priority difference threshold, it indicates that the difference between the frequently displayed view and the non-displayable view with the highest priority is not significant. In this case, the type priority principle is still followed, and the second candidate view (non-displayable view) is removed from the first status bar view set. After each view is eliminated, the remaining space is re-evaluated to see if it meets the display requirements. If it is still insufficient, repeat the above process, determine the view with the highest priority in the updated first status bar view set again, and perform a combined judgment based on the difference between type and priority, until the remaining views can be fully accommodated.

[0140] Furthermore, the preset view display strategy can be specifically as follows: all ADAS warning views have the highest priority and must be displayed; navigation guidance views can be compressed but cannot be hidden when space is insufficient; and ordinary vehicle status views are preferentially filtered out when they conflict with other high-priority views.

[0141] The second instrument view set refers to the set of instrument views that, after filtering, are determined to be displayed within the instrument data display area. The second instrument view set is a subset of the first instrument view set. Similarly, the second status bar view set refers to the set of status bar views that, after filtering, are determined to be displayed within the status bar data display area. The second status bar view set is a subset of the first status bar view set.

[0142] For example, after priority sorting, only the ADAS alarm view and navigation guidance view are retained in the first instrument view set to form the second instrument view set; only the system signal strength view and Bluetooth connection status view are retained in the first status bar view set, and the unread message notification view with higher priority is temporarily removed to form the second status bar view set.

[0143] Here, the target instrument panel view refers to each specific instrument panel view in the second set of instrument panel views. Each target instrument panel view corresponds to a specific piece of vehicle information, such as a specific ADAS warning icon, a navigation turn arrow, or a low battery warning symbol. Similarly, the target status bar view refers to each specific status bar view in the second set of status bar views, such as a specific signal strength icon, a Bluetooth icon, or a message notification icon.

[0144] The display position refers to the specific screen coordinate area assigned to the target instrument view and the target status bar view, which typically includes the starting horizontal coordinate, the starting vertical coordinate, and the width and height of the view.

[0145] It should be understood that in practical applications, the total display area of ​​the second instrument view set can exceed the instrument data display area to ensure that all important instrument information can be displayed.

[0146] In practical applications, based on Figure 1 The view display strategy manager determines the importance of each initial instrument view in the first instrument view set according to the preset view display strategy, and sorts them in descending order of importance. For example, for views with the same priority, frequently displayed views are more important than infrequently displayed views. Then, the display area controller retrieves the views in sequence according to the above order and attempts to allocate display positions for them within the corresponding display areas.

[0147] Specifically, taking the first set of status bar views as an example, the display area controller attempts to allocate a display position for each initial status bar view within the status bar data display area after sorting. Initial status bar views that are successfully allocated positions constitute the second set of status bar views, and their corresponding display positions are recorded. If insufficient space is encountered during the allocation process, operations such as compressing view sizes or culling can be performed until all initial status bar views have been processed or there is no remaining space within the status bar data display area.

[0148] Specifically, taking the first set of instrument views as an example, the display area controller attempts to allocate a display position for each initial instrument view within the instrument data display area after sorting. The initial instrument views that are successfully allocated positions constitute the second set of instrument views, and their corresponding display positions are recorded. If insufficient space is encountered during the allocation process, the status bar data display area can be used.

[0149] Furthermore, the display area controller can employ a dynamic layout algorithm to place larger views in the center of the area and arrange smaller views around it; it can also arrange views in preset orders such as right to left, left to right, top to bottom, and bottom to top.

[0150] S24. Determine whether there are overlapping views based on the display position of the target instrument view and the display position of the target status bar view.

[0151] Here, overlap refers to the intersection of the display areas of two or more views in the screen coordinate system. Since it has been ensured in S23 that there is no overlap between target instrument views and target status bar views, the overlap here specifically refers to the existence of a common pixel between the display position of any target instrument view and the display position of any target status bar view.

[0152] For example, if the bottom boundary of a target instrument view intersects or overlaps with the top boundary of a target status bar view, it is determined that there is an overlap.

[0153] Optionally, the overlap can be determined based on the standard rectangle intersection algorithm, that is, by comparing whether the boundaries of the two rectangles intersect, or it can be determined based on other existing judgment algorithms. This application embodiment does not impose specific limitations on this.

[0154] In practical applications, based on Figure 1 This can be achieved by performing geometric calculations using the display area controller. The display area controller obtains the display positions of all target instrument views and all target status bar views, and then compares the rectangular areas of each pair of target instrument views and target status bar views one by one. The display area controller can use a double loop traversal method, performing intersection checks on each target instrument view with each target status bar view in turn. If any pair of target instrument views and target status bar views intersect, then overlapping views are determined; otherwise, overlapping views are determined.

[0155] S25. If there are overlapping views, then according to the priority of the target status bar view, readjust the target status bar views contained in the second status bar view set and their corresponding display positions until there are no overlapping views.

[0156] In practical applications, the entire adjustment process can lock the display position of all target instrument views, ensuring that the target instrument views remain unchanged throughout the adjustment process. Since the total display area of ​​the second set of instrument views may exceed the instrument data display area, encroaching on part of the status bar data display area, the available space in the status bar data display area is updated before adjustment, and the adjustment operation is then performed based on the updated available space.

[0157] The adjustment methods include removing target status bar views with higher priority from the second status bar view set, or changing the display size of the target status bar views and thus changing their corresponding display positions, so that the display positions of all target status bar views after adjustment no longer overlap with the display positions of all target instrument views.

[0158] For example, the adjustment methods include:

[0159] 1. Remove one or more target status bar views with the highest priority. In this approach, for example, since the overlap is due to insufficient space caused by too many target status bar views in the second status bar view set, removing the highest priority target status bar views can free up space.

[0160] 2. Adjust the display size of the target status bar view in the second status bar view set.

[0161] For example, the display size of the status bar views for the highest priority targets can be reduced from 40 pixels × 40 pixels to 20 pixels × 20 pixels.

[0162] It should be understood that the specific implementation process and principles of this step will be explained later. Figure 3 The embodiments shown are described in detail here, and will not be repeated here.

[0163] S26. If there is no view overlap, the target status bar view and the target instrument view will be displayed on the vehicle screen according to their respective display positions.

[0164] based on Figure 1 The view control layer packages and sends each target instrument view in the second instrument view set and its corresponding display position, as well as each target status bar view in the second status bar view set and its corresponding display position, to the UI view layer. Based on the above information, the UI view layer calls the underlying graphics rendering interface to draw the corresponding view content at the specified coordinates on the vehicle screen.

[0165] The multi-view display method provided in this application first determines the instrument panel data display area and the status bar data display area based on the vehicle screen's display mode. Then, it acquires a first set of instrument panel views and a first set of status bar views to be displayed. Based on a preset view display strategy, the instrument panel data display area, and the status bar data display area, it filters the first set of instrument panel views to determine a second set of instrument panel views and the display positions of the target instrument panel views contained within it. Similarly, it filters the first set of status bar views to determine the second set of status bar views and the display positions of the target status bar views contained within it. Next, based on the display positions of the target instrument panel views and the target status bar views, it determines whether there are overlapping views. If overlapping views exist, the target status bar views contained in the second set of status bar views and their corresponding display positions are readjusted according to their priority until no overlapping views exist. If no views overlap, the target status bar views and target instrument panel views are displayed on the vehicle screen according to their respective display positions. This technical solution enables the orderly coexistence of the instrument panel view and the status bar view within a limited screen space. While ensuring that the display position of the target instrument panel view is not affected, it solves the problem of overlapping and occlusion of multiple views by dynamically adjusting the target status bar view and its display position based on priority only in the second status bar view set. This avoids the shortcomings of existing technologies that rely solely on simple hierarchical coverage, which leads to mutual occlusion of important information. It significantly improves the collaborative display capability of multi-task information and driving safety in multi-screen display scenarios, and ensures the comprehensiveness of important information display.

[0166] Figure 3 Flowchart of the multi-view display method provided in this application Figure 2 ,like Figure 3 As shown, S15 includes:

[0167] Step a: Update the status bar data display area based on the display position of the target instrument view.

[0168] In one possible implementation, the display positions of all target instrument views are first locked to ensure they remain fixed during subsequent adjustments. Then, the display area controller obtains the display positions of all target instrument views and calculates the total display area they occupy. Afterward, the boundaries of the status bar data display area are recalculated so that the updated status bar data display area does not overlap with the display positions of any of the target instrument views.

[0169] Step b: Filter the second status bar view set according to the priority of the target status bar view.

[0170] In one possible implementation, the target status bar view with the highest priority is removed from the second status bar view set.

[0171] In this implementation, the least important target status bar view is removed first, which can quickly respond to situations where space is insufficient, reduce system computing overhead, and improve adjustment efficiency.

[0172] In another possible implementation, the target status bar view with the highest priority is determined from the second status bar view set. If the target status bar view with the highest priority is a non-displayable view, it is removed from the second status bar view set. If the target status bar view with the highest priority is a always-displayable view, the non-displayable view with the highest priority is determined from the second status bar view set. Then, the priority difference between the target status bar view with the highest priority and the non-displayable view with the highest priority is calculated. If the priority difference is greater than a preset priority difference, the target status bar view with the highest priority is removed from the second status bar view set. If the priority difference is less than or equal to the preset priority difference, the non-displayable view with the highest priority is removed from the second status bar view set.

[0173] It should be understood that the preset priority difference can be preset based on empirical or experimental values, and this application embodiment does not impose specific restrictions on this.

[0174] This implementation ensures the overall display stability of the always-on view while preventing the always-on view with extremely low priority from unreasonably crowding out the non-always-on view with higher priority, thus achieving more refined control over the content displayed in the status bar and a better balance in space utilization.

[0175] Step c: Based on the updated status bar data display area, determine the updated display position of the remaining target status bar views in the second status bar view set.

[0176] The remaining target status bar view refers to the target status bar view that is retained after S32 filtering.

[0177] based on Figure 1 The display area controller retrieves the updated status bar data display area, the remaining target status bar views, and their corresponding display sizes. Based on preset layout strategies, such as right-to-left, left-to-right, evenly spaced, or prioritizing placement (higher priority views are placed in more prominent positions), it assigns display positions to each remaining target status bar view in turn.

[0178] Step d: Determine whether the corresponding total display area is within the updated status bar data display area based on the remaining target status bar view.

[0179] If so, output the display position of each remaining target status bar view.

[0180] If not, repeat steps b through d until the total display area of ​​the remaining target status bar view is within the updated status bar data display area.

[0181] In the above embodiments, iterative filtering and position reassignment ensure that the total display area of ​​the remaining target status bar views is within the updated status bar data display area, thereby ensuring that there are no overlapping views and further improving the stability and reliability of multi-view display.

[0182] Figure 4 Flowchart of the multi-view display method provided in this application Figure 3 ,like Figure 4 As shown, the multi-view display methods include:

[0183] S401, Vehicle system starts.

[0184] S402, SystemUI starts.

[0185] SystemUI is a system-level application in Android that provides the system's user interface, used to display the status bar view and dashboard view.

[0186] S403, Desktop Startup.

[0187] S404. Determine the display mode of the vehicle screen.

[0188] S405. Determine the desktop layout.

[0189] S406. Based on the desktop layout, determine the instrument data display area, the status bar data display area, and the display size of each view.

[0190] Next, execute S407-S409 for the dashboard view; execute S410-S414 for the status bar.

[0191] S407. Perform a self-test on the instrument and obtain the self-test data.

[0192] Self-test refers to the process by which the instrument system performs a self-test of its own hardware and software functions when it starts up. This is used to confirm whether the instrument display function is working properly and to obtain self-test result data.

[0193] For example, the self-test may include checking whether the speedometer pointer responds normally, whether all indicator lights can be lit, and whether there are dead pixels on the display screen. The self-test data generated after the self-test is completed will be used as the initial input for the instrument view.

[0194] S408. Obtain the status of the registration light based on the instrument service.

[0195] The registration light status refers to the real-time status signals of various vehicle indicator lights obtained from the instrument cluster service, such as the on / off status information of turn signals, high beam headlights, low beam headlights, hazard lights, and seat belt reminder lights. These statuses are dynamically updated by the instrument cluster service based on the actual vehicle operating conditions and reported to the view control layer, serving as one of the important signals that the instrument cluster view needs to display.

[0196] S409. Based on the display size of each view and the instrument data display area, determine the second instrument view set and the display position of the target instrument views it contains. Then, execute S415.

[0197] S410, default status bar, then execute S412.

[0198] The default status bar refers to the initial blank area.

[0199] S411, Registration Priority.

[0200] S412. Register view items and coordinates according to the priority of business modules.

[0201] The registered coordinates refer to the predetermined display position parameters assigned to each status bar view, typically including the starting horizontal coordinate, the starting vertical coordinate, and the view's width and height. It should be understood that these coordinates represent an ideal display position pre-configured based on business needs and user experience design.

[0202] S413. Perform non / normal visual inspection.

[0203] The non / normal display check refers to determining whether the status bar view is a very prominent view or a normally prominent view.

[0204] S414. Determine the display position of the second status bar view set and the target status bar view contained therein, based on the display size of each view and the status bar data display area.

[0205] S415. Determine whether there is an overlapping view between the target instrument view and the target status bar view.

[0206] If it does not exist, execute S416; if it exists, execute S417.

[0207] S416, Notify UI view layer to refresh.

[0208] S417. Remove the highest priority target status bar view from the second status bar view set.

[0209] S418. Update the status bar data display area according to the display position of the target instrument view, and then execute S414.

[0210] As demonstrated by the multi-view display method in the above embodiments, this solution effectively improves the comprehensiveness of important information displayed on the vehicle screen, avoiding information omissions caused by overlapping views. By introducing modularity and a layered MVVM architecture, the data layer, business capability layer, capability layer, view control layer, and UI view layer are decoupled, significantly improving the reusability of each functional module. The built-in display strategy manager and region overlap manager in the view control layer work together to cover various complex display scenarios and have good scene adaptability. At the same time, the layered architecture design makes the system highly scalable, flexibly adapting to the status bar display requirements of various Android systems, reducing the maintenance and porting costs of functional modules, effectively improving the interactive experience of the smart cockpit, and enhancing the product's market competitiveness.

[0211] Figure 5 A schematic diagram of the structure of the multi-view display device provided in this application is shown below. Figure 5 As shown, the multi-view display device 50 provided in this embodiment includes:

[0212] The first determining module 501 is used to determine the instrument display data area and the status bar display data area according to the display mode of the vehicle screen.

[0213] The acquisition module 502 is used to acquire the first set of instrument views to be displayed and the first set of status bar views.

[0214] The processing module 503 is used to filter the first instrument view set according to the preset view display strategy, the instrument data display area and the status bar data display area, to determine the display position of the second instrument view set and the target instrument view contained therein, and to filter the first status bar view set to determine the display position of the second status bar view set and the target status bar view contained therein.

[0215] The second determining module 504 is used to determine whether there are overlapping views based on the display position of the target instrument view and the display position of the target status bar view.

[0216] The adjustment module 505 is used to readjust the target status bar views and their corresponding display positions contained in the second status bar view set according to the priority of the target status bar view if there are overlapping views, until there are no overlapping views.

[0217] The display module 506 is used to display the target status bar view and the target instrument view on the vehicle screen according to their respective display positions if there is no view overlap.

[0218] In one possible implementation, the adjustment module 505 is specifically used for:

[0219] Step a: Update the status bar data display area based on the display position of the target instrument view.

[0220] Step b: Filter the second status bar view set according to the priority of the target status bar view.

[0221] Step c: Based on the updated status bar data display area, determine the updated display position of the remaining target status bar views in the second status bar view set.

[0222] Step d: Determine whether the corresponding total display area is within the updated status bar data display area based on the remaining target status bar view.

[0223] If not, repeat steps b through d until the total display area of ​​the remaining target status bar view is within the updated status bar data display area.

[0224] In one possible implementation, the adjustment module 505 is specifically used for:

[0225] Remove the highest priority target status bar view from the second status bar view set.

[0226] In one possible implementation, the adjustment module 505 is specifically used for:

[0227] Identify the target status bar view with the highest priority from the second set of status bar views.

[0228] If the target status bar view with the highest priority is a very visible view, then the target status bar view with the highest priority is removed from the second status bar view set.

[0229] If the target status bar view with the highest priority is a constantly displayed view, then the non-displayed view with the highest priority is determined from the second set of status bar views.

[0230] Calculate the priority difference between the highest priority target status bar view and the highest priority non-visible view.

[0231] If the priority difference is greater than the preset priority difference, the target status bar view with the highest priority will be removed from the second status bar view set.

[0232] If the priority difference is less than or equal to the preset priority difference, the most prominent view with the highest priority will be removed from the second status bar view set.

[0233] In one possible implementation, the preset view display strategy includes at least one of the following:

[0234] For the same instrument signal, remove the latest initial instrument view from the first instrument view set.

[0235] Initial instrument views with a priority greater than the preset priority are filtered out from the first instrument view set.

[0236] During the filtering process of the first set of status bar views, the initial status bar views with higher priority are filtered out before the initial status bar views with lower priority.

[0237] During the filtering process of the first set of status bar views, the most prominent initial status bar views are filtered out, while the most commonly displayed initial status bar views are filtered out.

[0238] The total display area of ​​the second status bar view set is limited to the area within the status bar data display area.

[0239] In one possible implementation, the vehicle screen's display mode includes any one of single-screen display, dual-screen extended display, or full-screen splicing display.

[0240] The multi-view display device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0241] Figure 6 This is a structural diagram of the vehicle provided in this application. Figure 6 As shown, the vehicle 60 provided in this embodiment includes: a vehicle body 601, at least one processor 602, and a memory 603. Optionally, the vehicle 60 also includes a communication component 604. The processor 602, memory 603, and communication component 604 are connected via a bus 605.

[0242] In a specific implementation, at least one processor 602 executes computer execution instructions stored in memory 603, causing at least one processor 602 to perform the above-described method.

[0243] The specific implementation process of processor 602 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0244] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0245] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0246] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0247] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0248] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0249] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0250] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0251] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

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

[0253] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0254] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, 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 steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0255] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0256] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A multi-view display method, characterized in that, include: Determine the instrument panel data display area and the status bar data display area based on the vehicle screen's display mode; Obtain the first set of instrument view and the first set of status bar view to be displayed; Based on the preset view display strategy, the instrument data display area, and the status bar data display area, the first instrument view set is filtered to determine the display position of the second instrument view set and the target instrument view it contains. Similarly, the first status bar view set is filtered to determine the display position of the second status bar view set and the target status bar view it contains. Based on the display position of the target instrument view and the display position of the target status bar view, determine whether there are overlapping views; If there are overlapping views, the target status bar views contained in the second status bar view set and their corresponding display positions are readjusted according to the priority of the target status bar view until there are no overlapping views. If there is no view overlap, the target status bar view and the target instrument panel view are displayed on the vehicle screen according to their respective display positions.

2. The method according to claim 1, characterized in that, The step of readjusting the target status bar views and their corresponding display positions in the second status bar view set according to the priority of the target status bar views includes: Step a: Update the status bar data display area based on the display position of the target instrument view; Step b: Filter the second status bar view set according to the priority of the target status bar view; Step c: Based on the updated status bar data display area, determine the updated display position of the remaining target status bar views in the second status bar view set; Step d: Determine whether the corresponding total display area is within the updated status bar data display area based on the remaining target status bar view; If not, repeat steps b through d until the total display area of ​​the remaining target status bar view is within the updated status bar data display area.

3. The method according to claim 2, characterized in that, The step of filtering the second status bar view set according to the priority of the target status bar view includes: Remove the highest priority target status bar view from the second status bar view set.

4. The method according to claim 2, characterized in that, The step of filtering the second status bar view set according to the priority of the target status bar view includes: The target status bar view with the highest priority is determined from the second set of status bar views; If the target status bar view with the highest priority is a very visible view, then the target status bar view with the highest priority is removed from the second status bar view set; If the target status bar view with the highest priority is a constantly displayed view, then the non-displayed view with the highest priority is determined from the second set of status bar views. Calculate the priority difference between the target status bar view with the highest priority and the non-display view with the highest priority; If the priority difference is greater than the preset priority difference, then the target status bar view with the highest priority is removed from the second status bar view set; If the priority difference is less than or equal to the preset priority difference, then the most prominent view with the highest priority is removed from the second status bar view set.

5. The method according to any one of claims 1-4, characterized in that, The preset view display strategy includes at least one of the following: For the same instrument signal, remove the outdated initial instrument view from the first instrument view set; Initial instrument views with a priority greater than a preset priority are filtered out from the first instrument view set; During the filtering process of the first status bar view set, the initial status bar view with higher priority is filtered out before the initial status bar view with lower priority. During the filtering process of the first status bar view set, the most prominent initial status bar view is filtered out because it is superior to the normally prominent initial status bar view. The total display area of ​​the second status bar view set is limited to the area within the status bar data display area.

6. The method according to any one of claims 1-4, characterized in that, The display modes of the vehicle screen include any one of single-screen display, dual-screen extended display, and full-screen splicing display.

7. A multi-view display device, characterized in that, include: The first determining module is used to determine the instrument panel data display area and the status bar data display area according to the display mode of the vehicle screen; The acquisition module is used to acquire the first set of instrument views and the first set of status bar views to be displayed; The processing module is used to filter the first instrument view set according to the preset view display strategy, the instrument data display area and the status bar data display area, to determine the display position of the second instrument view set and the target instrument view contained therein, and to filter the first status bar view set to determine the display position of the second status bar view set and the target status bar view contained therein. The second determining module is used to determine whether there are overlapping views based on the display position of the target instrument view and the display position of the target status bar view; The adjustment module is used to readjust the target status bar views and their corresponding display positions contained in the second status bar view set according to the priority of the target status bar view if there are overlapping views, until there are no overlapping views. The display module is used to display the target status bar view and the target instrument view on the vehicle screen according to their respective display positions if there is no view overlap.

8. A vehicle, characterized in that, include: Vehicle body, memory, and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images