A multi-system fusion interface display method and intelligent cockpit system

Abstract

The application provides a multi-system fusion interface display method and an intelligent cockpit system. The multi-system fusion interface display method comprises the following steps: configuring a logical display space consistent with the resolution of a physical display device; defining a content display area by setting the layout margin of a root view container based on the logical display space; rendering all application contents of a second system in the content display area; wherein, by controlling the value of the layout margin, a split-screen state or a full-screen state is formed; in the split-screen state, the unoccupied area in the logical display space is mapped as a composite area for use by a first system. The application solves the technical problem that, due to the static fixed screen partition in the prior art, the second operating system and its applications cannot be dynamically switched to the full-screen mode, thereby limiting the flexibility of user experience.

Description

Technical Field

[0001] This application relates to the field of intelligent cockpit system technology, and more specifically, to a multi-system fusion interface display method and an intelligent cockpit system. Background Technology

[0002] In the field of embedded systems such as smart cockpits and smart terminals, a hybrid architecture with multiple operating systems has become the mainstream technical approach in order to simultaneously ensure functional safety and a rich application ecosystem. In embedded devices such as smart cockpits, the physical display screen is typically divided into two fixed areas and statically assigned to two different operating systems.

[0003] However, the existing technical solution has the following problems: because the existing technical solution uses static and fixed screen partitions, the second operating system and its applications cannot dynamically switch to full-screen mode, which limits the flexibility of user experience. Summary of the Invention

[0004] The technical problem solved by this application is that the existing technical solutions use static and fixed screen partitions, which prevents the second operating system and its applications from dynamically switching to full-screen mode, thus limiting the flexibility of the user experience.

[0005] To address the aforementioned issues, this application provides a method for displaying a multi-system integrated interface, comprising: configuring a logical display space consistent with the resolution of the physical display device; defining a content display area based on the logical display space by setting the layout margins of the root view container; rendering all application content of the second system within the content display area; wherein, by controlling the value of the layout margins, a split-screen state or a full-screen state is formed; in the split-screen state, the unoccupied area in the logical display space is mapped as a composite area for use by the first system.

[0006] Compared with the existing technology, the technical effects achieved by adopting this technical solution are as follows: This application realizes the dynamic switching of the display mode of the second system. Users can freely switch between split-screen and full-screen modes according to their needs. While maintaining the display of key information of the first system, it provides a variable display area for the second system, solving the problem of interface rigidity caused by traditional fixed split-screen.

[0007] In one example of this application, a split-screen state or a full-screen state is formed by controlling the value of the layout margin, including: when the value of the layout margin is set to a non-zero value, a split-screen state is formed, wherein the content display area is the remaining area in the logical display space after deducting the area occupied by the layout margin; when the value of the layout margin is set to a zero value, a full-screen state is formed, wherein the content display area extends to the entire logical display space.

[0008] Compared with the existing technology, the technical effects achieved by adopting this technical solution are as follows: This application solves the problem of inflexible display mode switching caused by static screen partitioning, enabling the second system to switch freely between split-screen and full-screen modes according to user needs, while maintaining display compatibility with other systems. This solution improves system response speed and reduces resource consumption by replacing hardware reconfiguration with software parameter adjustment.

[0009] In one example of this application, in split-screen mode, an unoccupied area in the logical display space is mapped to a composite area for use by the first system, including: a blank area in the logical display space formed by layout margins is mapped to a composite area on the physical display device; the graphical interface content of the first system is rendered within the composite area; wherein the position and size of the composite area are determined by the width of the layout margins.

[0010] Compared with the prior art, the technical effects achieved by adopting this technical solution are as follows: This application solves the problem that static split screen causes the first system to be unable to dynamically use the unoccupied display area, realizes the dynamic adaptation of the composite area and the split screen state, and when the second system adjusts the split screen ratio, the display area of ​​the first system can automatically match the change of the layout margin, avoiding the waste of physical display resources. In addition, by binding the mapping relationship of the composite area with the layout margin parameter, the accuracy and stability of the dual system interface overlay display are ensured.

[0011] In one example of this application, rendering of all application content of the second system within the content display area includes: modifying the layout parameters of the root view container through a system service and setting margin values; the root view container triggering a re-layout of the entire view hierarchy based on the set margin values; and all interface components in the view hierarchy automatically adjusting their display position and size based on the new layout boundaries and being rendered within the content display area.

[0012] Compared with existing technologies, the technical effects achieved by this solution are as follows: This application solves the problem of interface element overflow or misalignment when dynamically switching display modes, ensuring that the application content of the second system can be fully displayed and conform to visual logic in both split-screen and full-screen modes. The layout adjustment process of interface components is entirely driven by the underlying system, without the need for additional adaptation at the application layer, significantly improving the display stability in multi-system integration scenarios.

[0013] In one example of this application, configuring a logical display space with the same resolution as the physical display device includes: configuring a virtual display device for the second system through a virtualization layer; the logical resolution of the virtual display device is the same as the resolution of the physical display device; wherein the second system establishes a logical display space based on the virtual display device.

[0014] Compared with existing technologies, the technical effects achieved by this solution are as follows: This application achieves seamless adaptation between the second system's display space and the physical device, ensuring that the screen ratio remains correct during the switching between split-screen and full-screen states, and avoiding display distortion or black borders caused by resolution differences. Simultaneously, the fixed resolution design of the virtual display device allows interface layout calculations to be independent of physical hardware parameters, providing a stable operating environment for dynamically adjusting the content display area.

[0015] In one instance of this application, the logical resolution of the virtual display device remains fixed during system operation; the switching between split-screen and full-screen states is achieved by adjusting the values ​​of the layout margins.

[0016] Compared with the prior art, the technical effects achieved by adopting this technical solution are as follows: This application solves the problem of inflexible display mode switching caused by static screen partitioning, enabling the second system to dynamically switch between split-screen and full-screen states, and there is no need to trigger resolution reconfiguration during the switching process, which not only improves the smoothness of user experience, but also avoids the system stability risk caused by frequent modification of display parameters.

[0017] In one instance of this application, the second system is an Android system; the root view container is a decorative view in the Android system window manager; the layout margins are implemented by modifying the layout parameters of the decorative view.

[0018] Compared with existing technologies, the technical effects achieved by this technical solution are as follows: This application realizes seamless switching control of the display area of ​​the Android system. Without affecting the normal operation of the application, the switching between split-screen and full-screen states is global and instantaneous through the adjustment of system-level view container parameters, effectively solving the problem of rigid display mode caused by traditional static split-screen.

[0019] In one example of this application, the layout margin is the left margin, the content display area is the right area of ​​the logical display space excluding the left margin area, and the composite area is located on the left side of the physical display device.

[0020] Compared with existing technologies, the technical effects achieved by this solution are as follows: This application enables the dynamic switching of the second system's display area between split-screen and full-screen modes, solving the problem of insufficient interactive flexibility caused by static screen partitioning. By limiting the margin direction to the left, the complexity of layout adjustment is simplified, while ensuring a clear positional correspondence between the display areas of the two systems in split-screen mode, thus improving the interactive experience of multi-system interface integration.

[0021] On the other hand, this application also provides an intelligent cockpit system, including a multi-system fusion interface display method as described in any of the above examples. The intelligent cockpit system includes: a physical display device; a first system; and a second system. The second system is configured to perform the following operations: configure a logical display space with a resolution consistent with that of the physical display device; define a content display area based on the logical display space by setting the layout margin of the root view container; constrain all application content of the second system within the content display area for rendering; and switch between split-screen and full-screen states by controlling the value of the layout margin. In the split-screen state, unoccupied areas in the logical display space are mapped as composite areas for use by the first system.

[0022] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: it can achieve the technical effects corresponding to any of the above examples, which will not be elaborated here.

[0023] By adopting the technical solution of this application, the following technical effects can be achieved:

[0024] (1) This application breaks through the technical limitations of traditional fixed split-screen, and realizes flexible switching between split-screen and full-screen modes of the second system by dynamically adjusting the layout margins at the software level. This method can achieve dynamic control of the display area by only modifying the layout parameters of the root view container while keeping the resolution of the virtual display device constant;

[0025] (2) The system ensures that all interface elements can be fully adapted in different display states by triggering automatic rearrangement of the view hierarchy, without requiring any modifications to the application layer;

[0026] (3) This technical solution effectively utilizes physical display resources, avoids the performance overhead and display abnormalities caused by resolution reconfiguration in traditional solutions, and provides an optimized display solution for converged scenarios such as smart cockpits. Attached Figure Description

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

[0028] Figure 1 This is a schematic diagram of a multi-system integrated interface display method provided in this application. Detailed Implementation

[0029] The technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. The components of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following drawings indicate similar items; therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0030] In existing technologies, when using a multi-operating system hybrid architecture in embedded systems such as smart cockpits and smart terminals, the physical display screen is typically divided into two fixed areas and statically allocated to different operating systems. This static screen splitting method prevents the second operating system and its applications from dynamically switching to full-screen mode, limiting the user's display needs in different scenarios. For example, in a smart cockpit scenario, when a user needs to view navigation information in full screen, existing technologies cannot achieve flexible switching of display modes.

[0031] To address these issues, researchers discovered that the core problem with fixed partitioning lies in the lack of decoupling between the physical division and logical control of the display area. After studying the display system architecture, they found that virtualization technology could be used to create a logical display space independent of the physical device. Further analysis of the view rendering mechanism revealed that the layout margin parameters of the root view container can dynamically control the display area. Based on this, a technical concept was developed: by dynamically adjusting the layout margin parameters of the logical display space, variable control of the content display area can be achieved, and blank areas can be remapped to composite display areas from other systems.

[0032] Therefore, this application provides a method for displaying a multi-system integrated interface, including: configuring a logical display space with the same resolution as the physical display device; defining a content display area based on the logical display space by setting the layout margin of the root view container; rendering all application content of the second system within the content display area; wherein, by controlling the value of the layout margin, a split-screen state or a full-screen state is formed; in the split-screen state, the unoccupied area in the logical display space is mapped as a composite area for use by the first system.

[0033] Furthermore, a multi-system integrated interface display method specifically addresses the fusion display of interfaces between different systems in a smart cockpit scenario. First, a logical display space with the same resolution as the physical display device is configured. This logical display space provides a complete display environment for the second system, with its size perfectly matching the physical screen, ensuring that the second system and its applications always perceive a full-screen display environment. Based on the logical display space, the content display area is defined by setting the layout margins of the root view container.

[0034] Furthermore, the root view container is the top-level container in the second system's graphical interface that carries all application content. By adjusting its layout margins, the actual display position and range of the second system's content can be dynamically controlled without changing the virtual display device configuration.

[0035] Furthermore, all application content of the second system is constrained to the content display area for rendering. Due to the layout margin settings, all application content of the second system will automatically adapt to the new layout boundaries and be restricted to display within the specified sub-area.

[0036] Furthermore, by controlling the layout margin values, split-screen or full-screen modes can be created. When the layout margin is non-zero, split-screen mode is created; when the layout margin is zero, full-screen mode is created.

[0037] Furthermore, in split-screen mode, unoccupied areas in the logical display space are mapped to composite areas for use by the first system.

[0038] In one embodiment, the left margin is set to 30% of the screen width, at which point the content display area automatically adjusts to the 70% width area on the right. All application interfaces of the second system, under the control of the layout engine, automatically adjust their size and are rendered entirely within the right-side area. The blank area on the left is mapped to an independent layer through the graphics compositor, used by the first system to render key information such as dashboards. When the user triggers full-screen mode, the layout margins are reset to zero, the content display area expands to the entire logical display space, the second system's application interface automatically fills the full screen, and the compositor area of ​​the first system disappears.

[0039] In one example of this application, a split-screen state or a full-screen state is formed by controlling the value of the layout margin, including: when the value of the layout margin is set to a non-zero value, a split-screen state is formed, wherein the content display area is the remaining area in the logical display space after deducting the area occupied by the layout margin; when the value of the layout margin is set to a zero value, a full-screen state is formed, wherein the content display area extends to the entire logical display space.

[0040] Specifically, the switching between split-screen and full-screen modes is achieved by precisely controlling the layout margin values. When the layout margin value is set to a non-zero value, a split-screen mode is formed, and the content display area is the remaining area in the logical display space after deducting the area occupied by the layout margins. This design ensures that in split-screen mode, the content of the second system is precisely constrained within the specified area, while leaving accurate display space for the first system.

[0041] Furthermore, when the layout margin is set to zero, a full-screen state is achieved, expanding the content display area to the entire logical display space. This switching process does not require reconfiguring the virtual display device's resolution; it can be achieved solely through software-level parameter adjustments, ensuring smooth and real-time switching. Moreover, the process is completed through software-level parameter adjustments, eliminating the need for hardware configuration modifications or system restarts.

[0042] In one example of this application, in split-screen mode, an unoccupied area in the logical display space is mapped to a composite area for use by the first system, including: a blank area in the logical display space formed by layout margins is mapped to a composite area on the physical display device; the graphical interface content of the first system is rendered within the composite area; wherein the position and size of the composite area are determined by the width of the layout margins.

[0043] Specifically, in split-screen mode, the blank areas in the logical display space created by layout margins are precisely mapped to the composite areas on the physical display device. This mapping process ensures that the coordinate correspondence between the virtual display space and the physical display device is accurate.

[0044] Furthermore, the graphical interface content of the first system is rendered within this composite area, achieving seamless integration with the interface of the second system. The position and size of the composite area are determined by the width of the layout margins. This design allows the display area of ​​the first system to dynamically adjust with changes in the layout margins, achieving a true dynamic split-screen effect.

[0045] Specifically, when the second system enters split-screen mode, the left margin of the root view container is set to a non-zero value, for example, 30% of the width of the physical display device. At this time, a blank area is formed on the left side of the logical display space. This blank area is mapped to the left side of the physical display device through the display mapping interface of the virtualization layer, forming a composite area for use by the first system. The graphical interface content of the first system is output to this composite area through an independent rendering channel, for example, through the GPU's layer overlay function to achieve parallel display with the content of the second system. When the layout margin value is dynamically adjusted, for example through a user-triggered split-screen ratio adjustment operation, the width and position of the composite area are updated in real time. For example, when the margin is adjusted from 30% to 20%, the width of the composite area is simultaneously reduced to 20% of the width of the physical display device.

[0046] In one example of this application, rendering of all application content of the second system within the content display area includes: modifying the layout parameters of the root view container through a system service and setting margin values; the root view container triggering a re-layout of the entire view hierarchy based on the set margin values; and all interface components in the view hierarchy automatically adjusting their display position and size based on the new layout boundaries and being rendered within the content display area.

[0047] Specifically, the implementation of confining all application content of the second system to the content display area for rendering includes: modifying the layout parameters of the root view container and setting the margin values ​​through system services. This operation is completed at the system service level, ensuring the globality and authority of the adjustment.

[0048] Furthermore, the root view container triggers a complete re-layout of the entire view hierarchy based on the set margin values. This chain reaction ensures that all UI elements, from the root container to the bottommost view components, respond to layout changes.

[0049] Furthermore, all UI components in the view hierarchy automatically adjust their display position and size based on the new layout boundaries and are rendered within the content display area. This adaptive process is entirely driven by the system's underlying layer, requiring no modifications or adaptations from the application layer, thus ensuring application compatibility.

[0050] In one example of this application, configuring a logical display space with the same resolution as the physical display device includes: configuring a virtual display device for the second system through a virtualization layer; the logical resolution of the virtual display device is the same as the resolution of the physical display device; wherein the second system establishes a logical display space based on the virtual display device.

[0051] Specifically, the implementation of configuring a logical display space with the same resolution as the physical display device includes configuring a virtual display device for the second system through a virtualization layer.

[0052] Furthermore, the logical resolution of the virtual display device remains consistent with the resolution of the physical display device. This key design ensures that the second system always perceives the complete physical screen space, laying the foundation for the realization of full-screen functionality.

[0053] Furthermore, the second system establishes a logical display space based on this virtual display device. As a core concept of the graphics subsystem within the second system, the logical display space represents the display environment in which the system performs graphics compositing and rendering.

[0054] Specifically, in scenarios where the physical display device and the operating system's display space are mismatched, a virtual display device with a fixed resolution is created for the second system through a virtualization layer. The logical resolution of this virtual display device is strictly set to be the same as the actual resolution of the physical display device; for example, when the physical device resolution is 1920×720, the logical resolution of the virtual device is also configured to 1920×720. When the second system initializes the display module, it establishes a logical display space based on this virtual display device, and all layout calculations for interface elements are completed within this virtual space. Because the virtual display space and the physical device's resolution are completely consistent, the graphic data output by the second system can be directly adapted to the physical screen without scaling or cropping. When it is necessary to switch display areas, the position and size of the content display area in the logical space can be dynamically controlled by adjusting the layout margin parameters of the root view container while maintaining the virtual display space resolution.

[0055] In one instance of this application, the logical resolution of the virtual display device remains fixed during system operation; the switching between split-screen and full-screen states is achieved by adjusting the values ​​of the layout margins.

[0056] Specifically, the logical resolution of the virtual display device remains fixed during system operation. This characteristic is the fundamental difference between this solution and traditional dynamic resolution adjustment solutions, avoiding the performance overhead and stability risks caused by resolution reconfiguration.

[0057] Furthermore, switching between split-screen and full-screen modes is achieved by adjusting the layout margins. This purely software-based switching mechanism offers advantages such as fast response time, low resource consumption, and simple implementation, making it particularly suitable for in-vehicle environments with high real-time requirements.

[0058] Furthermore, the logical display space and the physical display device adopt a strict 1:1 pixel mapping relationship, and the layout margin value is set to the pixel level to ensure that the boundaries of the content display area and the composite area are precisely aligned. The position and size of the composite area are precisely controlled by the layout margin width to eliminate image overlap or gaps.

[0059] Specifically, during system operation, the logical resolution of the virtual display device remains consistent with the resolution of the physical display device and does not change dynamically. When switching from split-screen to full-screen mode, the layout margins are set to zero. At this time, the layout boundary of the root view container expands to the entire logical display space, and the application content of the second system automatically fills the entire logical display space. When reverting from full-screen to split-screen mode, the layout margins are reset to non-zero values. The root view container triggers a rearrangement of the view hierarchy based on the new margin values, constraining the application content within the reduced content display area. Therefore, switching display modes can be completed simply by adjusting the upper-level layout parameters, avoiding interface adaptation issues caused by dynamic resolution adjustments.

[0060] In one instance of this application, the second system is an Android system; the root view container is a decorative view in the Android system window manager; the layout margins are implemented by modifying the layout parameters of the decorative view.

[0061] Preferably, the first system is Linux and the second system is Android. Android has a rich application ecosystem and a mature graphics framework, making it a common choice for scenarios such as smart cockpits.

[0062] Furthermore, the root view container is the DecorView in the Android system window manager. DecorView is the root container for all views in an Android window, and manipulating it can affect the layout of the entire window. Layout margins are achieved by modifying the layout parameters of the DecorView.

[0063] In one example of this application, the layout margin is the left margin, the content display area is the right area of ​​the logical display space excluding the left margin area, and the composite area is located on the left side of the physical display device.

[0064] In one application scenario, the layout margin is the left margin, and the content display area is the right side of the logical display space excluding the left margin area. The composite area corresponds to the left side of the physical display device. This left-right partitioned layout conforms to the design habits of most in-vehicle interfaces, with the left side typically used to display key information such as vehicle status and navigation, and the right side used to run entertainment applications.

[0065] Specifically, when the left margin is set to a non-zero value, the view layout engine constrains all application interface components of the second system to the right area of ​​the logical display space for rendering. Simultaneously, the blank area formed by the left margin is mapped to the left composite area of ​​the physical display screen for use by the first system. When switching to full-screen mode, the left margin value is adjusted to zero. At this time, the content display area of ​​the second system expands to the entire logical display space, covering the entire area of ​​the physical display screen. By limiting the margin adjustment direction to the left, the layout complexity caused by simultaneously operating multiple margin parameters is avoided, while ensuring that the display areas of the two systems form an intuitive left-right arrangement on the physical screen in split-screen mode.

[0066] On the other hand, this application also provides an intelligent cockpit system, including: a physical display device; a first system; and a second system; wherein the second system is configured to perform the following operations: configuring a logical display space with a resolution consistent with the physical display device; defining a content display area based on the logical display space by setting the layout margin of the root view container; rendering all application content of the second system within the content display area; and switching between split-screen and full-screen states by controlling the value of the layout margin; wherein, in the split-screen state, the unoccupied area in the logical display space is mapped as a composite area for use by the first system.

[0067] The second system is configured to perform the following operations: configure a logical display space consistent with the resolution of the physical display device; define the content display area by setting the layout margin of the root view container based on the logical display space; constrain all application content of the second system within the content display area for rendering; and switch between split-screen and full-screen states by controlling the value of the layout margin.

[0068] Furthermore, in split-screen mode, unoccupied areas in the logical display space are mapped as composite areas for use by the first system. This system-level implementation ensures the stability and reliability of multi-system fusion display.

[0069] Specifically, during the system initialization phase, the second system establishes a logical display space with the same resolution as the physical display device through a virtualization layer, providing a unified display benchmark for the integration of multiple system interfaces. The layout margin parameters of the root view container are dynamically adjusted. When the margin is set to a non-zero value, the content display area is constrained to a local area within the logical display space, forming a split-screen state; when the margin is zero, the content display area expands to the entire logical display space, switching to a full-screen state. In the split-screen state, the blank area created by the layout margin is mapped to the composite area on the physical screen. The graphical interface content of the first system is rendered to this area through the compositor, achieving seamless splicing of the two system interfaces. The view hierarchy triggers a global re-layout after the margin adjustment, ensuring that all application interface components automatically adapt to the new display boundaries.

[0070] This invention provides a method and system for displaying a multi-system integrated interface, which will be described below using a smart cockpit scenario as an example.

[0071] In intelligent cockpit systems, Linux is typically used as the primary operating system, responsible for safety-critical functions such as vehicle control and instrument display; Android is used as the secondary operating system, providing a rich ecosystem of entertainment applications. The two systems coexist on the same hardware platform through virtualization technology.

[0072] When the system starts, a virtualization layer configures a virtual display device for the Android system with the exact same resolution as the physical display device. For example, for a 1920x720 physical screen, a virtual display device with the same resolution is configured for Android. The Android system establishes its logical display space based on this virtual display device and considers itself to have complete screen space.

[0073] When the system needs to enter blended display mode, the left margin of the DecorView of the currently active window is dynamically set through a system service in the Android framework layer. For example, setting the left margin to 640 pixels reserves the left display area for Linux systems.

[0074] After setting the left margin, DecorView triggers a complete layout overhaul of the entire view hierarchy. All child views automatically adjust their position and size based on the new layout boundaries. Ultimately, all Android application content is constrained to a 1280-pixel area on the right for rendering.

[0075] The Weston compositor in the Linux system uses the full-screen graphics buffer output by Android as the background layer, and composites the display of Linux's own UI components, such as the navigation bar and vehicle status information, on a blank area of ​​640 pixels on the left.

[0076] When a user needs to display an Android application in full screen, the Android application sends a full-screen request to the Linux system through a pre-defined communication channel. The Linux system hides its UI components, while the Android service adjusts the left margin of the DecorView to zero. The Android content immediately expands to fill the entire screen, achieving full-screen display.

[0077] When exiting fullscreen mode, the opposite operation is performed: Android notifies Linux to restore the display of UI components, while restoring the left margin setting of DecorView, and the system seamlessly returns to blended display mode.

[0078] For secondary screen display scenarios, in addition to setting the left margin, you can also set the corresponding margin on the right side to reserve display space for the status bar of the Linux system and prevent Android content from being obscured.

[0079] like Figure 1 As shown, the specific process of this application is as follows:

[0080] S1. Configure a logical display space for the second system that matches the resolution of the physical display device;

[0081] S2. Set the layout margins of the root view container based on the logical display space, and define the content display area and composition area according to the layout margins;

[0082] S3. Constrain all application content of the second system within the content display area;

[0083] S4. The first system performs interface rendering in the compositing area;

[0084] S5. Switch between split-screen and full-screen modes by controlling the layout margin values.

[0085] While this application discloses the above information, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of this application; therefore, the scope of protection of this application shall be determined by the scope defined in the claims.

Claims

1. A method for displaying a multi-system integrated interface, characterized in that, include: Configure a logical display space that matches the resolution of the physical display device; Based on the logical display space, the content display area is defined by setting the layout margins of the root view container; The entire application content of the second system is constrained to the content display area for rendering; In this process, by controlling the value of the layout margins, a split-screen state or a full-screen state can be formed. In the split-screen state, the unoccupied area in the logical display space is mapped to a composite area for use by the first system; The step of confining all application content of the second system to the content display area for rendering includes: Modify the layout parameters of the root view container and set the margin values ​​through system services; The root view container triggers a re-layout of the entire view hierarchy based on the set margin values; All interface components in the view hierarchy automatically adjust their display position and size based on the new layout boundaries and are rendered within the content display area. The logical display space configured to match the resolution of the physical display device includes: Configure virtual display devices for the second system through a virtualization layer; The logical resolution of the virtual display device is the same as the resolution of the physical display device; The second system establishes the logical display space based on the virtual display device; The second system is the Android system; The root view container is the decorative view in the Android system window manager; The layout margins are achieved by modifying the layout parameters of the decorative view.

2. The multi-system fusion interface display method according to claim 1, characterized in that, The process of controlling the layout margin values ​​to form a split-screen or full-screen state includes: When the value of the layout margin is set to a non-zero value, the split-screen state is formed, wherein the content display area is the remaining area in the logical display space after removing the area occupied by the layout margin. When the layout margin is set to zero, the full-screen state is formed, wherein the content display area is expanded to the entire logical display space.

3. The multi-system fusion interface display method according to claim 1, characterized in that, In the split-screen state, the unoccupied area in the logical display space is mapped as a composite area for use by the first system, including: The blank areas formed by the layout margins in the logical display space are mapped to the composite areas on the physical display device. The graphical interface content of the first system is rendered within the composite area; The position and size of the composite region are determined by the width of the layout margin.

4. The multi-system fusion interface display method according to claim 1, characterized in that, The logical resolution of the virtual display device remains constant during system operation.

5. The multi-system fusion interface display method according to claim 1, characterized in that, The layout margin is the left margin, the content display area is the right area of ​​the logical display space excluding the left margin area, and the composite area is located on the left side of the physical display device.

6. An intelligent cockpit system, applicable to the multi-system fusion interface display method as described in any one of claims 1-5, characterized in that, The intelligent cockpit system includes: Physical display devices; First system; Second system; The second system is configured to perform the following operations: Configure a logical display space that matches the resolution of the physical display device; Based on the logical display space, the content display area is defined by setting the layout margins of the root view container; The entire application content of the second system is constrained to the content display area for rendering; And by controlling the value of the layout margin, the system switches between the split-screen state and the full-screen state; In the split-screen state, the unoccupied area in the logical display space is mapped to the composite area for use by the first system.

Images