Window scheduling method and device for vehicle-mounted terminals, vehicle-mounted terminals

By introducing a focus arbitration mechanism that considers window area, hierarchy, and priority, the problem of chaotic window display in in-vehicle applications has been solved, achieving refined control and improved security.

CN123067971APending Publication Date: 2026-11-10PATEO CONNECT (NANJING) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510593025.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In multitasking scenarios, the display of in-vehicle application windows may become chaotic, affecting the user experience. Existing technologies cannot finely control window display, leading to confusion.

Method used

A window scheduling method is introduced, taking into account window area, level and priority, and a focus arbitration mechanism is used to uniformly schedule window display, thereby achieving fine-grained control.

Benefits of technology

Reduce window display clutter, improve user experience, meet diverse needs, and ensure driving safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123067971A_ABST
    Figure CN123067971A_ABST
Patent Text Reader

Abstract

This application provides a window scheduling method and apparatus for an in-vehicle terminal, and an in-vehicle terminal; wherein, the method includes: responding to a first request sent by a first application, determining first information of the first window according to the first request; the first request is used to request the display of the first window; the first information includes a region identifier of a target display area, a window level, and a window priority; scheduling the window display of the target display area according to the first information and the current display status of the target display area.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to vehicle technology, including but not limited to window scheduling methods and devices for vehicle-mounted terminals, and vehicle-mounted terminals. Background Technology

[0002] With the rapid development of automotive intelligence and connectivity, the intelligent cockpit has become a core component of modern vehicles. As a key element of the intelligent cockpit, the display technology of in-vehicle application windows not only serves the function of information presentation but also deeply integrates interactive control, personalized services, and multimodal experiences, significantly improving driving safety and user experience.

[0003] However, in multitasking scenarios, the display of in-vehicle application windows may become cluttered, affecting the user experience. Summary of the Invention

[0004] In a first aspect, embodiments of this application provide a window scheduling method for an in-vehicle terminal. The method includes: responding to a first request sent by a first application, determining first information of the first window based on the first request; the first request is used to request the display of the first window; the first information includes a region identifier of a target display area, a window level, and a window priority; and scheduling the display of the window in the target display area based on the first information and the current display status of the target display area.

[0005] It is understood that, in this application embodiment, a window scheduling method for an in-vehicle terminal is provided. In this method, not only the window area and window level are considered when scheduling windows, but also the window priority. Different windows at the same window level may have different window priorities. Therefore, compared with only considering the window area and window level when scheduling windows, it is beneficial to schedule window display more intelligently, realize fine control over the display of in-vehicle application windows, thereby reducing the occurrence of window display chaos and improving user experience.

[0006] Secondly, embodiments of this application provide a window scheduling device for an in-vehicle terminal, the device comprising a first determining unit and a scheduling unit; wherein: the first determining unit is configured to respond to a first application sent by a first application, the first application being used to request the display of a first window; and, based on the first application, to determine first information of the first window; the first information including a region identifier of a target display area, a window level, and a window priority; the scheduling unit is configured to schedule the window display of the target display area based on the first information and the current display status of the target display area.

[0007] Thirdly, embodiments of this application provide an in-vehicle terminal, including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the method described in the first aspect.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor or an in-vehicle terminal, implements the method described in the first aspect.

[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program or instructions, which, when executed by a processor or vehicle terminal, implement the method described in the first aspect of this application.

[0010] Sixthly, embodiments of this application provide a computer program that causes a processor or vehicle terminal to perform the method described in the first aspect.

[0011] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0012] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0013] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0014] Figure 1 This is a schematic diagram of the architecture of an in-vehicle system applicable to the embodiments of this application;

[0015] Figure 2 A schematic diagram of the implementation process of the window scheduling method for the vehicle terminal provided in the embodiments of this application. Figure 1 ;

[0016] Figure 3 A schematic diagram illustrating a further implementation of step 202 provided in an embodiment of this application;

[0017] Figure 4 A schematic diagram illustrating a further implementation of step 302 provided in an embodiment of this application;

[0018] Figure 5 Example diagram of focal points in the same region provided in the embodiments of this application;

[0019] Figure 6 Example diagrams of focal points in different regions provided in embodiments of this application;

[0020] Figure 7 A schematic diagram of the implementation process of the window scheduling method for the vehicle terminal provided in the embodiments of this application. Figure 2 ;

[0021] Figure 8 The embodiments provided in this application are related to Figure 7 The corresponding timing diagram;

[0022] Figure 9 A schematic diagram of the window scheduling device for an in-vehicle terminal provided in an embodiment of this application;

[0023] Figure 10 This is a schematic diagram of the structure of the vehicle-mounted terminal provided in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.

[0025] 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.

[0026] In the following description, references to "some embodiments," "this embodiment," "this application embodiment," and examples, etc., describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subset of all possible embodiments and may be combined with each other without conflict.

[0027] The descriptions such as "first," "second," and "third" appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described. They do not indicate any order and do not represent a special limitation on the number of devices in the embodiments of this application. They cannot constitute any limitation on the embodiments of this application.

[0028] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies or terms of the embodiments of this application are described below. The following relevant technologies or terms are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.

[0029] In the current smart cockpit environment, the display hierarchy of in-vehicle application windows mainly relies on the system's own hierarchical management mechanism. The display order of windows is simply determined by their hierarchy level; the higher the hierarchy, the closer the window is to the user, obscuring lower-level windows. The inventors of this application, through research and analysis of this hierarchical management mechanism, discovered that this mechanism cannot finely coordinate the display relationships between different areas or windows at the same hierarchy. For example, multiple windows in different areas of the central control screen (such as the driver's area and the passenger's area) may be displayed mutually exclusively or overlappingly, potentially causing window display chaos in multi-tasking scenarios and affecting the user experience. Current smart cockpit window management relies solely on hierarchy level to determine the window display order, resulting in a lack of flexible control methods to determine whether windows in the same area and at the same hierarchy should be displayed overlappingly or mutually exclusively. Furthermore, the system's own hierarchical management mechanism cannot set different display strategies for different areas.

[0030] Based on this, the display of windows is uniformly scheduled in the following embodiments, and the display behavior of windows can be finely controlled. Figure 1 This is a schematic diagram of the architecture of an in-vehicle system applicable to the embodiments of this application; as shown Figure 1 As shown, the architecture 100 of the vehicle system includes system components 101, window control module 102, and one or more applications (such as application one, application two, application three, application four, etc.); wherein, the window control module 102 includes a window focus management unit (WindowFocusManager), a window focus service unit (WindowFocusService), and a window focus control unit (WindowFocusControl).

[0031] In this embodiment, the unit division of the window control module 102 is not limited to... Figure 1 The division shown does not limit the specific functional units included in the window control module 102. In short, the window control module 102 is used to implement the window scheduling method of the vehicle terminal provided in the embodiments of this application.

[0032] It should be noted that, Figure 1 The system architecture shown runs on the in-vehicle terminal, meaning the window control module 102 runs on the in-vehicle terminal. In other embodiments, the window control module 102 may also run on a cloud server. This application does not limit the executing entity of the provided window scheduling method and apparatus for in-vehicle terminals; it can be either the in-vehicle terminal or a cloud server.

[0033] The following describes the window scheduling method and apparatus for vehicle-mounted terminals, as well as the vehicle-mounted terminal, provided in the embodiments of this application.

[0034] Figure 2 A schematic diagram of the implementation process of the window scheduling method for the vehicle terminal provided in the embodiments of this application. Figure 1 ;like Figure 2 As shown, the method may include the following steps 201 to 202:

[0035] Step 201: In response to a first request sent by the first application, determine first information of the first window based on the first request; wherein, the first request is used to request the display of the first window; the first information includes the region identifier of the target display area, the window level, and the window priority;

[0036] Step 202: Based on the first information and the current display status of the target display area, schedule the window display of the target display area.

[0037] It is understood that, in this application embodiment, a window scheduling method for an in-vehicle terminal is provided. In this method, not only the window area and window level are considered when scheduling windows, but also the window priority. Different windows at the same window level may have different window priorities. Therefore, compared with only considering the window area and window level when scheduling windows, it is beneficial to schedule window display more intelligently, realize fine control over the display of in-vehicle application windows, thereby reducing the occurrence of window display chaos and improving user experience.

[0038] The following sections will describe further optional implementation methods for each of the above steps, as well as related terms.

[0039] Step 201: In response to the first request sent by the first application, determine the first information of the first window according to the first request; the first request is used to request the display of the first window; the first information includes the region identifier of the target display area, the window level and the window priority; wherein, the target display area refers to the target area to be displayed in the first window.

[0040] It is understood that, in this embodiment, window priority can be interpreted as a further division of window levels within the same window hierarchy, and multiple windows within the same window hierarchy may have different priorities. In one implementation, the priorities of each window within the same window hierarchy can be predefined, for example, by predefining the mapping relationship between window identifiers and window priorities.

[0041] In some embodiments, different display areas have their own corresponding first mapping relationship tables, which record the mapping relationship between window identifiers and window priorities. Based on this, for embodiments in the first application that do not carry a window priority for the first window, further, in one possible implementation, the corresponding first mapping relationship table can be determined based on the region identifier of the target display area of ​​the first window. Of course, in other embodiments, different display areas can share a single first mapping relationship table.

[0042] It should also be noted that, in this embodiment, the first window can be understood as the application window or application interface of the first application. The first application is used to request the display of the first window, or it can be understood as the first application to request the display permission of the first window, or it can also be understood as a focus request (i.e., requesting the display permission of the window). In this embodiment, the information carried by the first application is not limited. In short, the first application carries information related to the first window, and based on the first application, the first information of the first window can be determined.

[0043] In some embodiments, the first application carries one or more of the following information:

[0044] The window identifier (i.e., window ID) of the first window;

[0045] The first window displays the region identifier (i.e., region ID) of the target display area.

[0046] The window hierarchy of the first window (i.e., the window hierarchy identifier);

[0047] The window priority of the first window (i.e., the window priority indicator).

[0048] It is understood that the above embodiments actually include multiple combinations:

[0049] In combination scheme 1, the first application carries a window identifier for a first window. Based on this, in one possible implementation, the window level corresponding to the window identifier of the first window can be determined according to a predefined mapping relationship between window identifiers and window levels. In one possible implementation, the window priority corresponding to the window identifier of the first window can be determined according to a predefined mapping relationship between window identifiers and window priorities. In one possible implementation, the target display area (i.e., the area identifier of the target display area) corresponding to the window identifier of the first window can be determined according to a predefined mapping relationship between window identifiers and display areas.

[0050] In combination scheme 2, the first application carries a window identifier and a window hierarchy of the first window. In one possible implementation, the window priority corresponding to the window identifier of the first window can be determined based on a predefined mapping relationship between window identifiers and window priorities. In another possible implementation, the region identifier of the target display area corresponding to the window identifier of the first window can be determined based on a predefined mapping relationship between window identifiers and display areas.

[0051] In combination scheme 3, the first application carries a window identifier of the first window, a region identifier of the target display area to be displayed in the first window, and a window hierarchy of the first window; in one possible implementation, the window priority corresponding to the window identifier of the first window can be determined based on a predefined mapping relationship between window identifiers and window priorities.

[0052] In combination scheme 4, the first application carries the window identifier of the first window, the region identifier of the target display area to be displayed in the first window, the window hierarchy of the first window, and the window priority of the first window. Therefore, the first information can be obtained by parsing the first application.

[0053] Step 202: Based on the first information and the current display status of the target display area, schedule the window display of the target display area.

[0054] It is understood that the current display status of the target display area may be that a window is currently displayed, or it may be idle with no window displayed. In some embodiments, the current display status of the target display area can be obtained based on the area identifier of the target display area. The following describes further embodiments for scheduling the window display of the target display area according to different display statuses.

[0055] In some embodiments, such as Figure 3 As shown, step 202 may further include the following steps 301 to 302:

[0056] Step 301: If the current display status of the target display area is a second window displaying a second application, determine the window level of the second window;

[0057] Step 302: Based on the relationship between the window hierarchy of the first window and the window hierarchy of the second window, and the window priority of the first window, schedule the display window of the target display area.

[0058] It is understandable that, in the above Figure 3In the illustrated embodiment, when scheduling the display windows of the target display area, the system considers not only the window hierarchy relationship between the first window and the second window, but also at least the window priority of the first window. This facilitates more intelligent scheduling of window display and enables refined management of window display in the target display area.

[0059] In practical applications, the window hierarchy of the first window may be the same as or different from that of the second window. The following describes a further implementation of step 302 for the case where the window hierarchy is the same.

[0060] In some embodiments, such as Figure 4 As shown, step 302 may further include the following steps 401 and 402:

[0061] Step 401: If the window level of the first window is the same as the window level of the second window, determine the window priority of the second window;

[0062] Step 402: Based on the relationship between the window priority of the first window and the window priority of the second window, schedule the display windows of the target display area.

[0063] It is understood that in this embodiment of the application, windows at the same window level compete for display rights according to priority, thereby achieving more refined management of window display, avoiding window display chaos in multi-tasking scenarios, and thus improving user experience.

[0064] It is understandable that for two windows with the same window hierarchy, their window priorities may be the same or different. Regarding the case where the first window and the second window have the same window hierarchy, the following describes further embodiments of the display window scheduling for the target display area, specifically further implementations of step 402, for three scenarios: the first window has a higher window priority than the second window, the first window has the same window priority as the second window, and the first window has a lower window priority than the second window.

[0065] In some embodiments, step 402, which involves scheduling the display window of the target display area based on the relationship between the window priority of the first window and the window priority of the second window, may further include: sending a first notification to the second application when the window priority of the first window is higher than that of the second window; wherein the first notification is used to notify the second application to forcibly close the second window.

[0066] In some embodiments, the second application receives and responds to the first notification, closes the second window, and thus no longer displays it in the target display area; after closing the second window, the second application returns the execution result for the first notification to the sender of the first notification.

[0067] Furthermore, in some embodiments, the method further includes: in response to a first execution result returned by the second application in response to the first notification, if the first execution result indicates that the window has been closed, sending a display notification to the first application; wherein the display notification is used to notify the first application to display the window.

[0068] In some embodiments, the first application receives and responds to the display notification, and displays the first window in the target display area.

[0069] It is understood that this embodiment, combined with the above embodiments, achieves more refined window display scheduling when the first window and the second window have the same window layer. Even if the two windows have the same window layer, because the window priority of the first window is higher than that of the second window, the currently displayed second window is forced to close, and the first window is displayed first; thus, fine-grained management of the display of multiple windows at the same window layer is achieved.

[0070] For example, in one user scenario, suppose the incoming call window of the phone app has a higher window priority than the navigation window of the navigation app, and the window hierarchy of the incoming call window is the same as that of the navigation window. When the navigation window is currently displayed in the driver's area (i.e., the user is using the navigation app), if there is an incoming call, the incoming call window of the phone app should be displayed immediately and occupy the entire driver's area, while the navigation app window should be automatically hidden.

[0071] In some other embodiments, step 402, which involves scheduling the display window of the target display area based on the relationship between the window priority of the first window and the window priority of the second window, may further include: sending a second notification to the second application when the window priority of the first window is the same as the window priority of the second window; wherein the second notification is used to notify the second application to determine whether to close the second window based on user needs.

[0072] In some embodiments, the second application receives and responds to the second notification, and decides whether to close the second window based on the user's needs. After the second window is closed, the second application returns a second execution result for the second notification to the sender of the first notification.

[0073] Furthermore, in some embodiments, the method further includes: sending a display notification to the first application in response to a second execution result returned by the second application in response to a second notification; wherein the display notification is used to notify the first application to display a window. In some embodiments, the first application receives and responds to the display notification, and displays the first window in the target display area.

[0074] In other embodiments, the second application receives and responds to the second notification, and decides whether to close the second window based on the user's own needs; if it decides not to close the second window, the second application returns a third execution result for the second notification to the sender of the first notification.

[0075] Furthermore, in some embodiments, the method further includes: in response to a third execution result returned by the second application in response to the second notification, waiting to receive the second execution result, and / or sending a fourth notification to the first application; wherein the fourth notification is used to notify the first application to wait for a display notification before displaying the window.

[0076] It is understood that this embodiment, combined with the above embodiments, achieves more refined window display scheduling when the first window and the second window have the same window hierarchy. If the window priority of the first window is also the same as that of the second window, the second application decides whether to close the second window based on user needs. This design is based on the consideration that, for first and second windows with the same window priority, forcibly closing the second window when requesting to display the first window may not meet the user's actual needs. For example, the second application or its second window is strongly related to the user. Even if the first application requests a first window with the same priority as the second window, the second window may still be expected to be displayed under certain circumstances due to user characteristics. For example, the target display area currently displays an incoming call notification window (an example of the second window), and the user neither wants to answer the call nor hang up or close the window. At the same time, the first application requests the display of the first window (such as a volume control window). Forcibly closing the incoming call notification window in this situation would not meet the user's needs. Therefore, in this embodiment of the application, for two windows at the same window level and with the same window priority, the second application decides whether to close the second window based on the user's needs;

[0077] Furthermore, the decision to close the second window can be based on its relevance to the user. Relevance can be determined by whether user interaction with the window interface is required. For example, if a call notification window requires user interaction (answering or hanging up), then the call notification window has a high relevance to the user (strong relevance), and in this case, the call notification window cannot be closed, i.e., the second window cannot be closed. Conversely, if a music application window is playing music from its playlist automatically without user intervention, its relevance to the user is low, and the music application window can be closed to allow background playback, i.e., the second window can be closed. In this embodiment, the second application receives and responds to the second notification, and the second application decides whether to close the second window based on its relevance to the user.

[0078] After the second application closes its second window, the first application opens its first window and displays it on the target display area; thus, more refined management of the display of multiple windows at the same window level is achieved.

[0079] In some other embodiments, for step 402, scheduling the display window of the target display area according to the relationship between the window priority of the first window and the window priority of the second window includes: if the window priority of the first window is lower than the window priority of the second window, after waiting for the second window to close, sending a display notification to the first application; wherein the display notification is used to notify the first application to display the window.

[0080] In some embodiments, the first application receives and responds to the display notification, and displays the first window in the target display area.

[0081] It is understood that in the above embodiments, more refined window display scheduling is achieved when the first window and the second window have the same window level. Since the two windows are at the same window level, if the window priority of the first window is lower than that of the second window, the first application is notified to display the first window in the target display area after the second window is closed, thereby achieving fine-grained management of the display of multiple windows at the same window level.

[0082] It is understood that the above embodiments describe a window display scheduling mechanism when a first application requests display permission for a first window, provided that a second window is currently displayed in the target display area. Additionally, there is another scenario where no window is displayed in the target display area when the first application requests display permission for the first window. In this case, in some embodiments, the method further includes: sending a display notification to the first application when the current display status of the target display area is that no window is displayed; wherein the display notification is used to notify the first application to display the window.

[0083] In some embodiments, the first application receives and responds to the display notification, and displays the first window in the target display area.

[0084] To save on window scheduling overhead for the vehicle-mounted terminal, in some embodiments, step 202, scheduling the window display of the target display area based on the first information and the current display status of the target display area, includes: performing information verification based on the first application; and, if the verification passes, scheduling the window display of the target display area based on the first information and the current display status of the target display area. In other words, step 202 is only executed when the information verification of the first application passes.

[0085] Furthermore, in some embodiments, the information verification according to the first application includes: determining the size of the first window according to the first application; and performing information verification according to the size of the first window.

[0086] In other embodiments, the method further includes: sending a third notification to the first application if the verification fails; wherein the third notification is used to notify the first application that the first application has failed.

[0087] In some embodiments, the first application receives and responds to the third notification without opening and displaying the first window.

[0088] The following examples illustrate possible implementation schemes of the window scheduling method for the vehicle terminal described in one or more of the above embodiments.

[0089] As analyzed earlier, current smart cockpit window management relies on the system's own hierarchical mechanism, determining the window display order solely based on the hierarchy. This results in a lack of flexible control mechanisms to determine whether windows should be displayed overlappingly or mutually exclusively in the same area and at the same hierarchy. Furthermore, the system's hierarchical mechanism cannot set different display strategies for different areas.

[0090] Based on this, in this embodiment of the application, a regional window focus arbitration mechanism is introduced to achieve unified window scheduling and to finely control window display behavior. (1) Within the same region, the focus arbitration mechanism can determine whether the window is mutually exclusive or delayed in display based on the focus status of the target display region; (2) For different regions, different display strategies can be customized.

[0091] It's important to note that window focus can also be understood as the window's display permission. An application that wants to display a window can request window focus by sending a focus request (the first request mentioned earlier), which is essentially requesting the window's display permission. The focus state can be understood as the situation where the window is requested to be displayed in the target display area, i.e., the situation of the first request.

[0092] The window focus strategy definition is described below:

[0093] 1. Windows at the same window level and in the same target display area are displayed in order based on the window priority of the current area, and whether they overlap or exclude each other is determined based on the window focus request information (i.e., the first information).

[0094] For example, Application 1 requests focus with priority 1 in area A, and after successful request, Application 1's window is displayed in area A. When Application 1's window is displayed in area A, Application 2 requests focus with priority 1 in area A (i.e., Application 1 and Application 2 have the same window priority for requesting display permission in the same area). At this time, Application 1's window will receive a permanent focus release callback (i.e., an example of the second notification). Application 1 determines whether to release and close the window based on user needs. If the focus is not released (i.e., the window is not closed), Application 2 will receive a focus callback (i.e., an example of the display notification) when Application 1's window disappears. Based on the received callback, Application 2's window is displayed in area A. At this time, Application 3 also requests focus with priority 2 in area A (where priority 2 is higher than priority 1). Application 2 will then receive a forced focus release callback (an example of the first notification) and close its window. If Application 3 also requests focus with priority 1, and Application 2 does not release focus, Application 2 will still receive a permanent focus release callback (an example of the second notification) and determine whether to release and close the window based on user needs. If Application 2 does not release the window, when Application 2 closes its window, Application 3 will receive a focus acquisition callback (an example of the display notification).

[0095] For example, if Application 1 requests focus with priority 2 in area A and displays its window in area A after successful request, and Application 2 requests focus with priority 1 in area A while Application 1's window is displayed, Application 2's focus request will be delayed. Application 2 will only gain focus (i.e., gain display permission) after Application 1's window is closed. Similarly, if Application 3 requests focus with priority 1 in area A after Application 2's focus request, the focus request will still be delayed. Application 3 will only gain focus after both Application 1's and Application 2's windows are closed. Finally, if Application 3 requests focus with priority 2 in area A while Application 1's window is displayed, Application 1's window will receive a permanent focus release callback (an example of the second notification). Application 1 will then determine whether to release and close the window based on user needs. When application 1's window is displayed in area A, if application 3 requests focus in area A with a priority of 3 (where priority 3 is higher than priority 2), application 1 will receive a forced focus release callback (i.e., an example of the first notification) and close the window.

[0096] It should be noted that when Application 1 requests focus with priority 1 in area A, it can be understood as Application 1 requesting the display permission of a window with priority 1 in area A. Similarly, when Application 2 requests focus with priority 1 in area A, it can also be understood as Application 2 requesting the display permission of a window with priority 1 in area A. Area A can be understood as the display area of ​​the in-vehicle terminal. In short, when an application requests focus with priority N (such as N being 1, 2, or 3) in a certain area, it can be understood as the application requesting the display permission of a window with priority N in that area (i.e., a certain display area of ​​the in-vehicle terminal, or the target display area).

[0097] Second, windows in different areas at the same level determine their display order based on the priority of the current area window, and determine whether they overlap or exclude each other based on the window focus request information. Different areas are not affected.

[0098] For example, if Application 1 requests a focus with priority 1 in area A, and Application 2 requests a focus with priority 2 in area B, then the two areas will not be affected.

[0099] Third, windows at different levels in the same area are displayed in a specific order based on their level, and whether they overlap or exclude each other is determined by the window focus request information (i.e., the first information).

[0100] For example, Application 1 requests window focus in area A with a level of 1 and a priority of 3, and the request is successful, displaying Application 1's window in area A. While Application 1's window is displayed in area A, if Application 2 requests window focus in area A with a level of 2 and a priority of 1 (where level 2 is higher than level 1), Application 1's window will receive a permanent focus release callback (an example of the second notification). Application 1 then determines whether to release the focus and close the window based on user needs. If Application 1 does not release the focus (i.e., does not close the window), Application 2 will receive a focus callback (an example of the display notification) when Application 1's window disappears. The priority of the focus callback is based on window level -> window priority -> window request time. Level 2 is higher than level 1. It can be understood that requesting focus is essentially requesting permission to display the window.

[0101] In summary, the judgment strategy is: window area > window hierarchy > window priority. It should be noted that the priority mentioned in this application can also be understood as window priority.

[0102] It is understandable that in the above scheme:

[0103] (1) Introduce a focus arbitration mechanism to unify the management of window focus.

[0104] Windows at the same level compete for focus (i.e., compete for display rights in the same area) based on priority, with higher-priority windows gaining focus (i.e. gaining display rights first).

[0105] (2) Supports permanent focus release (i.e., whether to release focus and close the window based on user needs) and forced focus release (i.e., forced focus release and close the window) to ensure that critical windows are displayed in a timely manner.

[0106] (3) Provide a focus callback mechanism, through which the application adjusts its behavior based on the information received (such as the first notification, the second notification, or the display notification).

[0107] Figure 5 Example diagram of the same area focus provided in the embodiments of this application; such as Figure 5 As shown, application one requests focus to display window A, and application two (starting after application one) requests focus to display window B. Both window A and window B are windows with a window level of 2 and a window priority of 1. For example, both windows are windows of a video application.

[0108] Figure 5 The execution order shown is that application one is opened first, followed by application two. After receiving the open command, application one first sends... Figure 1The window control module 102 (also known as the arbitrator) requests focus (the request information includes window information, such as window identifier, the ID of the area to be displayed, the window hierarchy ID, and the window priority ID). After the request is successful, window A is displayed. Later, application 2 receives an open command. At this time, application 2 first requests focus from the arbitrator. The arbitrator responds to the request by notifying application 1, which has already registered focus (for example, the information carried in the notification includes: the window hierarchy and window priority of window B). After receiving the notification, application 1 may close the window directly (another possibility is that if application 1's window is in progress, it will not close the window immediately, but will close it after it is completed). After application 1 closes the window, it feeds back to the arbitrator through a callback. The arbitrator then notifies application 2 to display the window based on this notification.

[0109] In one possible implementation, the window display rules are as follows: for windows at the same level and with the same priority, the window that requests focus later can overwrite the currently displayed window; for windows at the same level but with different priorities, the higher-priority window, regardless of whether it requested focus first or later, must be displayed first.

[0110] In one possible implementation, the arbitrator defines the window display rules and acts as a communicator, notifying each application of the current focus state. The application is the executor; for example, whether to close the current window or whether to display the window is implemented by the application.

[0111] Figure 6 Examples of focal points for different regions provided in embodiments of this application; such as Figure 6 As shown, Application 1 requests to display window A in region 1, and Application 2 requests to display window B in region 2. Therefore, the focus request of Application 2 does not affect the display of window A of Application 1 in region 1. Different regions have their own corresponding display strategies, and different regions have their own corresponding first mapping relationship tables. Different first mapping relationship tables may have different priorities for the same window.

[0112] Figure 7 A schematic diagram of the implementation process of the window scheduling method for the vehicle terminal provided in the embodiments of this application. Figure 2 ; Figure 8 The embodiments provided in this application are related to Figure 7 The corresponding timing diagram, therefore here for Figure 8 I will not go into details further;

[0113] Combination Figure 1 The system architecture shown is as follows: Figure 7 As shown, the method includes the following steps 701 to 714:

[0114] Step 701: The App requests focus from WindowFocusManager, that is, the App sends the first request to WindowFocusManager;

[0115] Step 702: Add a focus change callback to WindowFocusManager so that the App is notified when the focus changes;

[0116] Step 703: WindowFocusManager matches and obtains basic information; wherein, the basic information includes the window priority, window length, window width, and window identifier;

[0117] Step 704: WindowFocusManager creates a binder; in this way, WindowFocusManager can notify the App whether the focus request was successful, failed, or delayed based on the created binder.

[0118] Step 705: WindowFocusService registers focus;

[0119] Step 706: WindowFocusService performs information verification; if the verification passes, proceed to step 707; otherwise, notify the App of the focus request failure via binder.

[0120] Step 707: WindowFocusControl registers focus;

[0121] Step 708: WindowFocusControl determines whether the binder is alive; if so, proceed to step 709; otherwise, release the focus and notify the App of the focus request failure via the binder.

[0122] Step 709: WindowFocusControl stores focus requests in a queue;

[0123] Step 710: WindowFocusControl determines the window region; if the region where the focus is requested is the same as the region of the window where the focus was previously requested, then proceed to step 711; otherwise, return to step 709.

[0124] Step 711: WindowFocusControl performs a window hierarchy check; if the window hierarchy of the current focus request is higher than that of the previous focus request window, proceed to step 712; if the window hierarchy of the current focus request is the same as that of the previous focus request window, proceed to step 713.

[0125] In step 712, WindowFocusControl inserts the focus request after the vertex stack, and asynchronously acquires focus when the vertex focus is released; and returns the focus request with a delay via binder.

[0126] Step 713: WindowFocusControl performs a window priority determination; if the priority of the window applying for focus is lower than the priority of the window applying for focus previously, proceed to step 712; if the priority of the window applying for focus is higher than the priority of the window applying for focus previously, proceed to step 714.

[0127] Step 714: WindowFocusControl notifies other focus objects in the queue that "focus has been lost" and notifies the requester that it has obtained focus, such as by returning focus via binder if the request was successful.

[0128] It is understandable that the above solution has the following advantages:

[0129] 1. Fine-grained control: Enables fine-grained control over window display, avoiding cluttered window displays and improving user experience.

[0130] 2. Flexibility: Supports different display strategies for different regions to meet diverse needs.

[0131] 3. Intelligent: Intelligently schedule window display based on factors such as window area, level, and priority.

[0132] 4. Stability: Regionalized window management and focus arbitration mechanism improve system stability.

[0133] 5. Safety: Ensure that critical information windows are displayed in a timely manner to guarantee driving safety.

[0134] The following describes the user scenarios in which the above solutions may be applicable.

[0135] Scene 1:

[0136] Driver's area:

[0137] Applications: Phone, navigation, music;

[0138] Strategy: Mutually exclusive display, delayed display. Priority: Phone > Navigation > Music;

[0139] Scenario Description: When a user is using a navigation app, if a call comes in, the phone app window should immediately appear and occupy the entire driver's side area, while the navigation app window should automatically hide. After the call ends, the navigation app window can be restored to its original display based on the focus type. If the user opens a music app while using the navigation or phone app, the music app will not appear immediately until the navigation or phone app is closed.

[0140] Passenger area:

[0141] Applications: Video, Games, Music;

[0142] Strategy: Overlay display, priority: games > videos > music;

[0143] Scenario Description: When a user is watching a video, if a game application is opened, the game application window will be overlaid on the video window. When the user exits the game application, the video window will continue playing. If the user opens a music application while watching a video or playing a game, the music application window will be overlaid on the video or game window, but the video or game will continue to run in the background.

[0144] Scenario 2: Dashboard area:

[0145] Applications: ADAS warnings, vehicle information, navigation maps;

[0146] Strategy: Mutually exclusive display, priority: ADAS warnings > vehicle information > navigation map;

[0147] Scenario Description: When the ADAS system issues an emergency warning, the warning information should be immediately displayed on the instrument panel, overwriting other information such as vehicle information or a simplified navigation map. Once the warning is lifted, the instrument panel should revert to displaying the previous vehicle information or navigation map.

[0148] Scenario 3: HUD area:

[0149] Applications: Navigation guidance, ADAS warnings, incoming call reminders;

[0150] Strategy: Overlay display, priority: ADAS warnings > incoming call reminders > navigation guidance;

[0151] Scenario Description: When the ADAS system issues a warning, the warning information should be immediately displayed on the HUD, overriding other information such as navigation guidance or incoming call alerts. Once the warning is cleared, the HUD should resume displaying the previous navigation guidance or incoming call alert. If there is an incoming call, the call alert will override the navigation guidance, but will not override the ADAS warning.

[0152] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps; or steps from different embodiments may be combined into a new technical solution.

[0153] Based on the same inventive concept as the foregoing embodiments, this application provides a window scheduling device for an in-vehicle terminal. This device can be applied to an in-vehicle terminal or to a cloud server, and this application does not limit it.

[0154] Figure 9 This is a schematic diagram of the window scheduling device for the vehicle-mounted terminal provided in the embodiments of this application; as shown below. Figure 9 As shown, the window scheduling device 900 of the vehicle terminal includes a first determining unit 901 and a scheduling unit 902; wherein:

[0155] The first determining unit 901 is configured to respond to a first request sent by a first application and determine first information of the first window based on the first request; wherein the first request is used to request the display of the first window; the first information includes the region identifier of the target display area, the window level, and the window priority;

[0156] The scheduling unit 902 is configured to schedule the window display of the target display area based on the first information and the current display status of the target display area.

[0157] In some embodiments, scheduling the window display of the target display area according to the first information and the current display status of the target display area includes: when the current display status of the target display area is a second window displaying a second application, determining the window level of the second window; and scheduling the display windows of the target display area according to the relationship between the window level of the first window and the window level of the second window and the window priority of the first window.

[0158] Furthermore, in some embodiments, scheduling the display windows of the target display area based on the relationship between the window levels of the first window and the second window and the window priority of the first window includes: determining the window priority of the second window when the window levels of the first window and the second window are the same; and scheduling the display windows of the target display area based on the relationship between the window priorities of the first window and the second window.

[0159] Furthermore, in some embodiments, scheduling the display window of the target display area according to the relationship between the window priority of the first window and the window priority of the second window includes: sending a first notification to the second application when the window priority of the first window is higher than the window priority of the second window; wherein the first notification is used to notify the second application to forcibly close the second window.

[0160] Furthermore, in some other embodiments, scheduling the display window of the target display area according to the relationship between the window priority of the first window and the window priority of the second window includes: sending a second notification to the second application when the window priority of the first window and the window priority of the second window are the same; wherein the second notification is used to notify the second application to determine whether to close the second window according to user needs.

[0161] In some embodiments, such as Figure 9 As shown, the window scheduling device 900 of the vehicle terminal further includes a sending unit 903; wherein, the sending unit 903 is configured to send a display notification to the first application in response to a first execution result returned by the second application in response to a first notification or a second notification, wherein, if the first execution result indicates that the window has been closed; wherein, the display notification is used to notify the first application to display the window.

[0162] Furthermore, in some other embodiments, scheduling the display window of the target display area according to the relationship between the window priority of the first window and the window priority of the second window includes: when the window priority of the first window is lower than the window priority of the second window, after waiting for the second window to close, sending a display notification to the first application; wherein the display notification is used to notify the first application to display the window.

[0163] In some embodiments, scheduling the window display of the target display area based on the first information and the current display status of the target display area includes: performing information verification based on the first application, and if the verification passes, scheduling the window display of the target display area based on the first information and the current display status of the target display area.

[0164] Furthermore, in some embodiments, the information verification according to the first application includes: determining the size of the first window according to the first application; and performing information verification according to the size of the first window.

[0165] In some embodiments, such as Figure 9 As shown, the window scheduling device 900 of the vehicle terminal also includes a sending unit 903; wherein, the sending unit 903 is configured to send a third notification to the first application if the verification fails; wherein, the third notification is used to notify the first application that the first application has failed.

[0166] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0167] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware, as software functional units, or a combination of software and hardware.

[0168] It should be noted that, in the embodiments of this application, if the above-described methods 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 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 computer software product is stored in a storage medium and includes several instructions to cause the vehicle terminal to execute all or part of the methods described in 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 (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0169] This application provides a vehicle-mounted terminal.

[0170] Figure 10 This is a schematic diagram of the structure of the vehicle-mounted terminal provided in the embodiments of this application; as shown below. Figure 10 As shown, the vehicle terminal 100 includes a memory 1001 and a processor 1002. The memory 1001 stores a computer program that can run on the processor 1002. When the processor 1002 executes the program, it implements the steps in the method provided in the above embodiments.

[0171] It should be noted that the memory 1001 is configured to store instructions and applications executable by the processor 1002, 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 1002 and the various modules in the vehicle terminal 100. It can be implemented by flash memory or random access memory (RAM).

[0172] This application also provides a computer-readable storage medium for storing computer programs.

[0173] Optionally, the computer-readable storage medium can be applied to the vehicle terminal in the embodiments of this application, and the computer program causes the processor or vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0174] This application also provides a computer program product, including computer program instructions.

[0175] Optionally, the computer program product can be applied to the vehicle terminal in the embodiments of this application, and the computer program instructions cause the processor or vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0176] This application also provides a computer program.

[0177] Optionally, the computer program can be applied to the vehicle terminal in the embodiments of this application. When the computer program runs on the processor or the vehicle terminal, it causes the processor or the vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0178] It should be noted that the descriptions of the vehicle-mounted terminal, storage medium, computer program product, and computer program embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the vehicle-mounted terminal, storage medium, computer program product, and computer program embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0179] It should be understood that the phrases "one embodiment," "an embodiment," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment," "in one embodiment," or "in some embodiments" appearing throughout the specification do 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-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. The descriptions of the various embodiments above tend to emphasize the differences between the various embodiments; their similarities or commonalities can be referred to mutually, and for the sake of brevity, they will not be repeated here.

[0180] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three kinds of 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.

[0181] 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.

[0182] 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 embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or modules can be electrical, mechanical, or other forms.

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

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

[0185] 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 (ROM), magnetic disks, or optical disks.

[0186] 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 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 computer software product is stored in a storage medium and includes several instructions to cause the vehicle terminal to execute all or part of the methods described in 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.

[0187] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0188] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0189] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0190] The above description is merely an embodiment 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. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A window scheduling method for an in-vehicle terminal, characterized in that, The method includes: In response to a first request sent by a first application, the first request being used to request the display of a first window; According to the first application, the first information of the first window is determined; the first information includes the region identifier of the target display area, the window level, and the window priority. Based on the first information and the current display status of the target display area, schedule the window display of the target display area.

2. The method according to claim 1, characterized in that, The step of scheduling the window display of the target display area based on the first information and the current display status of the target display area includes: If the current display state of the target display area is a second window displaying a second application, determine the window level of the second window; Based on the relationship between the window hierarchy of the first window and the window hierarchy of the second window, as well as the window priority of the first window, the display windows of the target display area are scheduled.

3. The method according to claim 2, characterized in that, The step of scheduling the display windows of the target display area based on the relationship between the window hierarchy of the first window and the window hierarchy of the second window, and the window priority of the first window, includes: If the window level of the first window is the same as the window level of the second window, determine the window priority of the second window; Based on the relationship between the window priorities of the first window and the second window, the display windows of the target display area are scheduled.

4. The method according to claim 3, characterized in that, The step of scheduling the display windows of the target display area according to the relationship between the window priorities of the first window and the second window includes: If the window priority of the first window is higher than that of the second window, a first notification is sent to the second application; wherein the first notification is used to notify the second application to forcibly close the second window.

5. The method according to claim 3, characterized in that, The step of scheduling the display windows of the target display area according to the relationship between the window priorities of the first window and the second window includes: If the window priority of the first window is the same as that of the second window, a second notification is sent to the second application; wherein the second notification is used to notify the second application to determine whether to close the second window according to the user's needs.

6. The method according to claim 4 or 5, characterized in that, The method further includes: In response to a first execution result returned by the second application in response to a first notification or a second notification, if the first execution result indicates that the window has been closed, a display notification is sent to the first application; wherein the display notification is used to notify the first application to display the window.

7. The method according to claim 3, characterized in that, The step of scheduling the display windows of the target display area according to the relationship between the window priorities of the first window and the second window includes: If the window priority of the first window is lower than that of the second window, a display notification is sent to the first application after the second window is closed; wherein, the display notification is used to notify the first application to display the window.

8. The method according to any one of claims 1-7, characterized in that, The step of scheduling the window display of the target display area based on the first information and the current display status of the target display area includes: Information verification is performed based on the first application. If the verification passes, the window display of the target display area is scheduled according to the first information and the current display status of the target display area.

9. The method according to claim 8, characterized in that, The information verification according to the first application includes: According to the first application, the size of the first window is determined; information verification is performed based on the size of the first window.

10. The method according to claim 8, characterized in that, The method further includes: If the verification fails, a third notification is sent to the first application; wherein the third notification is used to notify the first application that the first application has failed.

11. A window scheduling device for a vehicle-mounted terminal, characterized in that, The device includes: The first determining unit is configured to respond to a first request sent by a first application and determine first information of a first window based on the first request; wherein the first request is used to request the display of the first window; the first information includes the region identifier of the target display area, the window level, and the window priority; The scheduling unit is configured to schedule the window display of the target display area based on the first information and the current display status of the target display area.

12. A vehicle-mounted terminal, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the method of any one of claims 1-10.

13. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor or vehicle terminal, they implement the method of any one of claims 1-10.