Display control method and device for vehicle-mounted display interface

Abstract

This invention discloses a display control method and apparatus for an in-vehicle display interface, relating to the field of interface display technology. The method includes: in response to vehicle startup, starting a main operating system and identifying whether a function signal for a vehicle function has been acquired; in response to acquiring a function signal, displaying a first toolbar and a first function icon in the first toolbar on the in-vehicle display interface through a hardware abstraction layer and / or a secondary operating system; the first function icon corresponds to a vehicle function; in response to the main operating system completing startup, drawing a second toolbar and a second function icon in the second toolbar on the in-vehicle display interface through the main operating system's display service, and replacing the first toolbar and the first function icon in the first toolbar with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to a vehicle function. This implementation can provide vehicle functions to the user even before the main operating system has completed startup.

Description

Technical Field

[0001] This invention relates to the field of interface display technology, and in particular to a display control method and device for an in-vehicle display interface. Background Technology

[0002] With the development of automotive technology, more and more cars are equipped with in-vehicle display screens. These screens not only serve for vehicle control and information display, but are also an important component of in-vehicle infotainment systems.

[0003] In-vehicle infotainment systems typically run on an operating system. It generally takes about 10 to 25 seconds from vehicle ignition to the completion of the operating system's boot process. Only after the Android operating system has finished booting can the toolbar containing relevant function icons appear on the in-vehicle display screen, meaning that the system cannot meet the user's needs for using certain functions immediately after the car starts. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a display control method and device for an in-vehicle display interface, which can provide vehicle functions to users before the main operating system has been fully started.

[0005] To achieve the above objectives, according to one aspect of the present invention, a display control method for an in-vehicle display interface is provided, comprising:

[0006] In response to vehicle startup, the main operating system is launched to identify whether functional signals of the vehicle functions have been acquired;

[0007] In response to receiving the aforementioned functional signals, a first toolbar and a first function icon in the first toolbar are displayed on the vehicle display interface through a hardware abstraction layer and / or an auxiliary operating system; the first function icon corresponds to the aforementioned vehicle function.

[0008] In response to the completion of the main operating system startup, the display service of the main operating system is used to draw a second toolbar and a second function icon in the vehicle display interface, and the first toolbar and the first function icon in the first toolbar are replaced with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to the vehicle function.

[0009] Optionally, the above method further includes:

[0010] Before starting the main operating system, start a secondary operating system that is independent of the main operating system.

[0011] The first toolbar and the first function icons in the first toolbar are displayed on the in-vehicle display interface through the hardware abstraction layer and the auxiliary operating system, including:

[0012] Based on the toolbar drawing task created in advance in the aforementioned secondary operating system, the drawing data of the first toolbar is determined in the drawing library of the aforementioned secondary operating system.

[0013] Based on the above drawing data, the above auxiliary operating system is used to draw the above first toolbar and the first function icon in the above first toolbar;

[0014] The auxiliary operating system calls the display function of the hardware abstraction layer to display the first toolbar and the first function icon in the first toolbar on the in-vehicle display interface.

[0015] Optionally, a first toolbar and the first function icons in the first toolbar are displayed in the vehicle display interface through a hardware abstraction layer, including:

[0016] The drawing data of the first toolbar is determined from its own drawing library through the aforementioned hardware abstraction layer.

[0017] Based on the above drawing data, the first toolbar and the first function icon in the first toolbar are drawn through the hardware abstraction layer, and the first toolbar and the first function icon in the first toolbar are displayed in the vehicle display interface.

[0018] Optionally, displaying the first toolbar and the first function icons in the first toolbar on the vehicle display interface includes:

[0019] Obtain the functional and control data of the aforementioned vehicle functions;

[0020] In response to obtaining the functional data and control data of the aforementioned vehicle functions, a first toolbar and a first function icon displayed in a first state in the vehicle display interface are displayed.

[0021] In response to the failure to obtain the functional data and / or control data of the aforementioned vehicle functions, a first toolbar and a first function icon displayed in the first toolbar in a second state are displayed on the in-vehicle display interface through the hardware abstraction layer.

[0022] Optionally, the vehicle functions mentioned above include the vehicle functions corresponding to each second function icon in the second toolbar that was in the first state when the vehicle was powered off during the last ignition cycle, and the first state is a triggerable state.

[0023] Optionally, displaying the first toolbar and the first function icons in the first toolbar on the vehicle display interface includes:

[0024] Determine the number of the aforementioned vehicle functions that have received the aforementioned functional signals.

[0025] Based on the aforementioned quantity and the size of the first toolbar, the display position of each of the aforementioned first function icons in the first toolbar is determined, so that the aforementioned first toolbar and each of the aforementioned first function icons in the first toolbar are displayed in the vehicle display interface according to the aforementioned display position.

[0026] To achieve the above objectives, according to another aspect of the present invention, a display control device for an in-vehicle display interface is provided, comprising:

[0027] The startup module is used to respond to vehicle startup, start the main operating system, and identify whether the vehicle function signals have been acquired.

[0028] The first display module is configured to, in response to acquiring the aforementioned function signal, display a first toolbar and a first function icon in the first toolbar on the vehicle display interface through a hardware abstraction layer and / or an auxiliary operating system; the first function icon corresponds to the aforementioned vehicle function.

[0029] The second display module is used to, in response to the completion of the startup of the main operating system, draw a second toolbar and a second function icon in the vehicle display interface through the display service of the main operating system, and replace the first toolbar and the first function icon in the first toolbar with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to the vehicle function.

[0030] To achieve the above objectives, according to another aspect of the present invention, an electronic device for display control of an in-vehicle display interface is provided.

[0031] An electronic device for display control of an in-vehicle display interface according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the display control method of an in-vehicle display interface according to an embodiment of the present invention.

[0032] To achieve the above objectives, according to another aspect of the present invention, a computer-readable storage medium is provided.

[0033] An embodiment of the present invention provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a display control method for an in-vehicle display interface according to an embodiment of the present invention.

[0034] To achieve the above objectives, according to another aspect of the present invention, a computer program product is provided.

[0035] A computer program product according to an embodiment of the present invention includes a computer program that, when executed by a processor, implements a display control method for an in-vehicle display interface according to an embodiment of the present invention.

[0036] One embodiment of the above invention has the following advantages or beneficial effects: By identifying whether the function signals of the vehicle functions are obtained during the startup of the main operating system after the vehicle is started, and if the function signals can be obtained, the first toolbar and the first function icon in the first toolbar are displayed on the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system has finished starting, the second toolbar and the second function icon in the second toolbar are drawn and displayed on the vehicle display interface through the main operating system. The toolbar can be displayed on the vehicle display interface even if the main operating system has not finished starting after the vehicle is started, which can provide vehicle functions to users more quickly and meet the user's needs for using vehicle functions when the vehicle is just started.

[0037] By displaying the first toolbar and the first function icon in the first toolbar on the vehicle display interface through a hardware abstraction layer and / or a secondary operating system, the time for displaying the first toolbar on the vehicle display interface can be significantly reduced, thus improving the user's driving experience.

[0038] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0039] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0040] Figure 1 This is a flowchart illustrating a display control method for an in-vehicle display interface according to an embodiment of the present invention;

[0041] Figure 2 This is a flowchart illustrating the display of a first toolbar and a first function icon according to an embodiment of the present invention;

[0042] Figure 3 This is a flowchart illustrating the display of a first toolbar and a first function icon according to another embodiment of the present invention;

[0043] Figure 4 This is a flowchart illustrating a display control method for an in-vehicle display interface according to another embodiment of the present invention;

[0044] Figure 5 This is a schematic diagram of the display control framework for an in-vehicle display interface configured with an auxiliary operating system according to an embodiment of the present invention;

[0045] Figure 6This is a flowchart illustrating a display control method for an in-vehicle display interface according to another embodiment of the present invention;

[0046] Figure 7 This is a schematic diagram of the display control framework for an in-vehicle display interface without an auxiliary operating system according to an embodiment of the present invention;

[0047] Figure 8 This is a schematic diagram of the main modules of the display control device for an in-vehicle display interface according to an embodiment of the present invention;

[0048] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing the display control method of the vehicle display interface in the embodiments of the present invention. Detailed Implementation

[0049] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0050] It should be noted that, unless otherwise specified, the embodiments of the present invention and the technical features thereof can be combined with each other.

[0051] Figure 1 This is a schematic diagram illustrating the main steps of a display control method for an in-vehicle display interface according to an embodiment of the present invention. Figure 1 As shown, the display control method for the vehicle display interface in this embodiment of the invention mainly includes the following steps S101 to S103:

[0052] Step S101: In response to vehicle startup, start the main operating system and identify whether the function signal of the vehicle function has been obtained;

[0053] The in-vehicle operating system may include the main operating system, which is used to manage and control in-vehicle hardware and software resources. For example, the main operating system may be an Android operating system, but it is not limited to this.

[0054] Upon startup, it's necessary to determine if the vehicle's functional signals can be successfully acquired. If a signal is detected, it indicates that the corresponding vehicle function's hardware is functioning correctly, and the function meets the basic requirements for normal operation. If no signal is detected, it suggests a potential hardware problem preventing the function from functioning properly, and the function does not meet the basic requirements for normal operation. It's important to note that even if a signal is detected, not all vehicle functions will be usable until the main operating system has fully booted, due to incomplete hardware initialization and the absence of system services.

[0055] Step S102: In response to obtaining the above-mentioned function signal, the first toolbar and the first function icon in the first toolbar are displayed in the vehicle display interface through the Hardware Abstraction Layer (HAL) and / or the auxiliary operating system; the first function icon corresponds to the above-mentioned vehicle function.

[0056] A secondary operating system is a separate operating system from the primary operating system. The primary operating system typically has a complex functional architecture, providing comprehensive and rich services and supporting the execution of various applications. In contrast, the secondary operating system has a relatively smaller codebase and more streamlined functionality, primarily designed to meet specific and singular task requirements. The primary operating system has a longer boot time, while the secondary operating system can be a real-time operating system with a relatively shorter boot time. It should be noted that in-vehicle infotainment systems generally only have a primary operating system; the secondary operating system can be optionally configured based on requirements.

[0057] Since the main operating system has not yet fully started, in order to meet the user's demand for certain vehicle dry red energy, a first toolbar and the first function icon in the first toolbar can be displayed on the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. This allows the user to use the corresponding vehicle function by triggering the first function icon in the first toolbar when needed, without waiting for the main operating system to finish starting.

[0058] In step S103, in response to the completion of the startup of the main operating system, the second toolbar and the second function icon in the second toolbar are drawn in the vehicle display interface through the display service of the main operating system, and the first toolbar and the first function icon in the first toolbar are replaced with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to the vehicle function.

[0059] After the main operating system has started up, the display of the first toolbar and the first function icon in the first toolbar on the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system can be stopped. Instead, the display of the second toolbar and the second function icon in the second toolbar can be displayed on the vehicle display interface through the display service of the main operating system, so as to replace the first toolbar and the first function icon in the first toolbar.

[0060] The main operating system can provide more complete hardware resources and service support to support the normal use of vehicle functions.

[0061] The second function icon and the first function icon can be icons for the same vehicle function, and the second function icon and the first function icon can be in different states or the same state. Here, the state of the function icon can include multiple states, and different states can have different display attributes or trigger attributes.

[0062] In an optional embodiment, the method further includes: starting a secondary operating system independent of the main operating system before starting the main operating system.

[0063] In vehicles with a secondary operating system, the secondary operating system boots up before the primary operating system. Because the secondary operating system has a shorter boot time, it can quickly provide support.

[0064] Optionally, the secondary operating system may be FreeRT OS, but is not limited to it. FreeRT OS is a real-time operating system suitable for microcontrollers and microprocessors.

[0065] like Figure 2 As shown, the first toolbar and the first function icon in the first toolbar are displayed on the vehicle display interface through the hardware abstraction layer and the auxiliary operating system, including the following steps S201 to S203:

[0066] Step S201: Based on the toolbar drawing task created in advance in the auxiliary operating system, determine the drawing data of the first toolbar in the drawing library of the auxiliary operating system.

[0067] Step S202: Based on the above drawing data, draw the first toolbar and the first function icon in the first toolbar using the above auxiliary operating system.

[0068] Step S203: The auxiliary operating system calls the display function of the hardware abstraction layer to display the first toolbar and the first function icon in the first toolbar in the vehicle display interface.

[0069] After the vehicle starts, the secondary operating system is started first, following the chronological order. The secondary operating system pre-creates and stores toolbar drawing tasks. Based on these toolbar drawing tasks, the secondary operating system calls its own drawing library to determine the drawing data for the first toolbar. The drawing data for the first toolbar refers to the drawing data for the first toolbar and its first function icons, including the display position, size, text attributes, and display attributes of the first toolbar and the first function icons.

[0070] Based on the above drawing data, the secondary operating system can draw the first toolbar and the first function icon in the first toolbar. Specifically, based on the drawing data, the secondary operating system draws the first toolbar and the first function icon in the first toolbar using its own drawing library and stores them in the graphics cache.

[0071] After the secondary operating system has booted up, the primary operating system starts. The HAL layer, part of the primary operating system, is located between the primary operating system kernel and the hardware. During the primary operating system boot process, the HAL layer boots up first. After the HAL layer boots up, the secondary operating system calls the display functions of the HAL layer through an interface call to read the first toolbar and the first function icon stored in the graphics cache. The HAL layer communicates with the display controller of the screen, sending the first toolbar and the first function icon from the graphics cache to the display controller. This allows the toolbar to be displayed on the in-vehicle display interface even before the primary operating system has finished booting, meeting the user's needs for vehicle functions after vehicle startup without waiting for the primary operating system to complete.

[0072] In one optional embodiment, displaying a first toolbar and a first function icon in the first toolbar on the vehicle display interface via a hardware abstraction layer includes: determining drawing data of the first toolbar from its own drawing library via the hardware abstraction layer; drawing the first toolbar and the first function icon in the first toolbar via the hardware abstraction layer based on the drawing data, and displaying the first toolbar and the first function icon in the first toolbar on the vehicle display interface.

[0073] In the absence of a secondary operating system in the in-vehicle infotainment system, the first toolbar and its first function icons can be drawn directly through the HAL layer. Specifically, during the main operating system startup process, the HAL layer starts up first and then determines the drawing data for the first toolbar from its own drawing library. The drawing data for the first toolbar refers to the drawing data for the first toolbar and its first function icons, including their display position, size, and text attributes.

[0074] Based on the aforementioned drawing data, the HAL layer uses its own drawing library to draw the first toolbar and the first function icon within it, and stores them in the graphics cache. The HAL layer communicates with the display controller of the screen, sending the first toolbar and the first function icon stored in the graphics cache to the display controller. This allows the first toolbar and its first function icon to be displayed on the vehicle's in-vehicle display interface, enabling the toolbar to be displayed on the in-vehicle display interface even before the main operating system has fully booted up. This satisfies the user's need to use vehicle functions after the vehicle starts, without waiting for the main operating system to complete booting.

[0075] In one alternative embodiment, such as Figure 3 As shown, the above-mentioned display of the first toolbar and the first function icon in the vehicle display interface includes the following steps S301 to S303:

[0076] Step S301: Obtain the functional data and control data of the aforementioned vehicle functions;

[0077] Step S302: In response to obtaining the functional data and control data of the above-mentioned vehicle functions, a first toolbar and a first function icon displayed in the first toolbar in a first state are displayed in the vehicle display interface.

[0078] In step S303, in response to the failure to obtain the functional data and / or control data of the aforementioned vehicle functions, a first toolbar and a first function icon displayed in the first toolbar in a second state are displayed in the vehicle display interface through the hardware abstraction layer.

[0079] If a vehicle function signal is detected, it indicates that the corresponding vehicle function has the basic conditions for normal operation. However, since the main operating system has not fully started, the functional data and control data that support the normal operation of the vehicle function may still not be available. Therefore, even if all the vehicle functions corresponding to the first function icons in the first toolbar have the basic conditions for use, not all vehicle functions are in a usable state.

[0080] Vehicle functions that need to be usable before the main operating system has finished booting are pre-configured. To distinguish between vehicle functions that can be used before the main operating system has finished booting and those that cannot be used before the main operating system has finished booting, the HAL layer and / or the secondary operating system can draw function icons for different states.

[0081] Specifically, for vehicle functions that need to be usable before the main operating system has finished booting, it is necessary to acquire functional data and control data that are sufficient for the normal operation of the vehicle function. The functional data can be obtained from the corresponding hardware of the vehicle function via the electronic control unit integrated with the driver assistance system, while the control data can be obtained from the device in the main operating system used to control the vehicle function. When the functional data and control data of the vehicle function are acquired, a first function icon for a first state can be drawn; when the functional data and / or control data of the vehicle function are not acquired, a first function icon for a second state can be drawn.

[0082] Furthermore, the aforementioned vehicle functions include the vehicle functions corresponding to each second function icon in the second toolbar that was in the first state when the vehicle was powered off during the last ignition cycle, and the first state is a triggerable state.

[0083] During the previous ignition cycle, the state of each second function icon in the second toolbar can be recorded when the vehicle is powered off. The second function icon in the first state is identified, and the vehicle function corresponding to the second function icon in the first state is used as the vehicle function that needs to be identified to determine whether the function signal can be obtained when the vehicle is started this time.

[0084] For vehicle functions that have acquired functional and control data, the first function icon can be depicted as the first state, which is the triggerable state. For vehicle functions that have not acquired functional and / or control data, the first function icon can be depicted as the second state, which is the non-triggerable state. To distinguish between the triggerable and non-triggerable first function icons, different display attributes, such as color and outline, can be set.

[0085] Specifically, when drawing the first toolbar and the first function icons in the first toolbar through the HAL layer and the auxiliary operating system, for vehicle functions that can normally obtain function signals, the auxiliary operating system can further obtain the corresponding function data and control data. Based on the pre-stored toolbar drawing task, the auxiliary operating system calls its own drawing library to determine the drawing data of the first toolbar, draws the first toolbar, and for vehicle functions that can obtain function data and control data, draws the first function icons displayed in the first toolbar in a triggerable state; for vehicle functions that cannot obtain function data and / or control data, draws the first function icons displayed in the first toolbar in a non-triggerable state. The drawn first toolbar and the first function icons in the first toolbar are stored in the graphics buffer, and then the first toolbar in the graphics buffer and the first function icons in the first toolbar are displayed on the vehicle display interface through the HAL layer.

[0086] When drawing the first toolbar and its first function icons using the HAL layer, for vehicle functions that can normally obtain function signals, the HAL layer can further obtain the corresponding function data and control data. The HAL layer determines the drawing data for the first toolbar from its own drawing library, draws the first toolbar, and for vehicle functions that can obtain function and control data, draws the first function icons displayed in the first toolbar in a triggerable state; for vehicle functions that cannot obtain function and / or control data, draws the first function icons displayed in the first toolbar in a non-triggerable state. The drawn first toolbar and its first function icons are stored in a graphics buffer, and then the HAL layer displays the first toolbar in the graphics buffer and its first function icons in the vehicle display interface.

[0087] Furthermore, after the main operating system has booted up, it can generally obtain all the functional and control data of the vehicle's functions. It then uses its own drawing library to draw the second toolbar and the second function icons displayed in the second toolbar in a triggerable state, storing these in the graphics cache. The main operating system can communicate with the display controller, sending the second toolbar and the second function icons stored in the graphics cache to the display controller. This allows the second toolbar and its second function icons to be displayed on the vehicle's in-vehicle display interface, replacing the first toolbar and its first function icons currently displayed on the in-vehicle display interface.

[0088] During the entire cycle from the main operating system startup to shutdown, if the functional data and / or control data of the vehicle function cannot be obtained, it indicates that the vehicle function cannot be used normally. The corresponding secondary function icon can be redrawn, thus switching the secondary function icon from a triggerable state to a non-triggerable state. Upon shutdown, confirm that each secondary function icon in the secondary toolbar is in a triggerable state, as these are the vehicle functions whose function signals need to be identified and verified upon the next vehicle startup.

[0089] In one optional embodiment, the above-mentioned display of the first toolbar and the first function icons in the first toolbar in the vehicle display interface includes: determining the number of vehicle functions that have received the function signals; and determining the display position of each of the first function icons in the first toolbar based on the number and the size of the first toolbar, so as to display the first toolbar and each of the first function icons in the first toolbar in the vehicle display interface according to the display position.

[0090] Since the vehicle functions that need to be identified to receive function signals may be different each time the vehicle starts, and the vehicle functions that can receive function signals may also be different each time, while the size of the first toolbar is generally fixed, in order to improve the neatness of the arrangement of the first function icons in the first toolbar and present a better visual experience to the user, the number of vehicle functions that have received function signals can be determined. Based on the above number and the size of the first toolbar, the first function icons of the above vehicle functions that can receive function signals are evenly distributed in the first toolbar, the display position of each first function icon in the first toolbar is determined, and then the first toolbar and each first function icon in the first toolbar are drawn according to the display position.

[0091] In one optional embodiment, after the first toolbar and the first function icons in the first toolbar are displayed on the in-vehicle display interface, the HAL layer and / or the auxiliary operating system can receive a user's trigger command for any of the first function icons in the first state. Based on the trigger command, the HAL layer and / or the auxiliary operating system can determine the relevant information of the vehicle function based on the function data and control data of the vehicle function corresponding to the first function icon and display it on the in-vehicle display interface.

[0092] As an example, when the first toolbar is drawn through the HAL layer and the auxiliary operating system, when a user triggers a function icon for the reversing image, the auxiliary operating system can obtain control data from the main operating system's video control device via the video control device of the HAL layer, send the control data to the vehicle's rear camera via the electronic control unit integrated with the driving assistance system, and obtain reversing image data from the vehicle's rear camera via the electronic control unit integrated with the driving assistance system, thereby displaying the reversing image data on the in-vehicle display interface.

[0093] As another example, when the first toolbar is drawn through the HAL layer, when a user triggers a function icon for the reversing image, the HAL layer can obtain control data from the video control device of the main operating system, send the control data to the vehicle's rear camera via the electronic control unit integrated with the driver assistance system, and obtain reversing image data from the vehicle's rear camera via the electronic control unit integrated with the driver assistance system, thereby displaying the reversing image data on the in-vehicle display interface.

[0094] According to the display control method of the vehicle display interface of the present invention, after the vehicle is started, during the startup of the main operating system, it is identified whether the function signal of the vehicle function is obtained. If the function signal can be obtained, a first toolbar and a first function icon in the first toolbar are displayed in the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system has finished starting, a second toolbar and a second function icon in the second toolbar are drawn and displayed in the vehicle display interface through the main operating system. This method can display the toolbar in the vehicle display interface even after the vehicle has started, even if the main operating system has not finished starting. This can provide vehicle functions to users more quickly and meet the user's needs for using vehicle functions when the vehicle is just started.

[0095] The following describes a specific embodiment of the display control method for an in-vehicle display interface.

[0096] Assuming the main operating system is Android OS and the secondary operating system is FreeRT OS, the default vehicle function that needs to be usable before the main operating system finishes booting is the reversing camera. Figure 4 and Figure 5 As shown, the display control method for the vehicle display interface in this embodiment of the invention includes the following steps S401 to S408:

[0097] Step S401: Following the chronological order, after the vehicle is started, the auxiliary operating system FreeRT OS is started first, followed by the main operating system Android OS. FreeRT OS then identifies whether the vehicle's functional signals can be obtained.

[0098] The vehicle functions include the vehicle functions corresponding to each of the second function icons in the second toolbar that were in the first state when the vehicle was powered off during the last ignition cycle. The first state is a triggerable state.

[0099] In step S402, in response to acquiring the above-mentioned function signal, the number of the above-mentioned vehicle functions that have received the above-mentioned function signal can be determined by FreeRT OS, and based on the above-mentioned number and the size of the first toolbar, the display position of each of the above-mentioned first function icons in the first toolbar is determined.

[0100] Step S403: For the vehicle function that needs to be used normally before the main operating system is fully started—the reversing camera—FreeRT OS can obtain its function data and control data.

[0101] like Figure 5 As shown, solid lines represent the flow of functional data, and dashed lines represent the flow of control data. FreeRT OS can obtain the functional data of the reversing image from the rear camera device through the electronic control unit that integrates the driving assistance system, and obtain the control data of the reversing image from the video control device in the main operating system through the video control device of the HAL layer.

[0102] Step S404: Based on the toolbar drawing task created in FreeRT OS in advance, determine the drawing data of the first toolbar in the drawing library of FreeRT OS.

[0103] Step S405: Based on the above drawing data and the above display position, draw the above first toolbar and the first function icon in the above first toolbar using the drawing library of FreeRT OS itself, and store them in the graphics cache area;

[0104] Specifically, the first function icon of the reversing camera that has acquired functional and control data is depicted as the first state, which is the triggerable state; the first function icons of other vehicle functions that have not acquired functional and control data are depicted as the second state, which is the non-triggerable state.

[0105] In step S406, FreeRT OS calls the display function of the HAL layer via the interface to read the first toolbar and the first function icon stored in the graphics buffer. Through communication between the HAL layer and the display controller, the first toolbar and the first function icon stored in the graphics buffer are sent to the display controller, thereby displaying the first toolbar and the first function icon in the first toolbar on the vehicle display interface of the display screen.

[0106] Step S407: When the user triggers the first function icon of the reversing image, FreeRT OS can obtain control data from the video control device of the main operating system through the video control device of the HAL layer, send the control data to the rear camera of the vehicle through the electronic control unit integrated with the driving assistance system, and obtain the reversing image data from the rear camera of the vehicle through the electronic control unit integrated with the driving assistance system, thereby displaying the reversing image data on the in-vehicle display interface.

[0107] In step S408, as all apps in the Android OS start up and the Android OS completes startup, the Android OS obtains the function data and control data of all vehicle functions. Then, the Android OS uses its own drawing library to draw the second toolbar and the second function icon displayed in the second toolbar in the second state. The main operating system's display service displays the second toolbar and the second function icon in the second toolbar on the vehicle display interface to replace the first toolbar and the first function icon in the first toolbar.

[0108] According to the display control method of the vehicle display interface of the present invention, after the vehicle is started, during the startup of the main operating system, it is identified whether the function signal of the vehicle function is obtained. If the function signal can be obtained, a first toolbar and a first function icon in the first toolbar are displayed in the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system has finished starting, a second toolbar and a second function icon in the second toolbar are drawn and displayed in the vehicle display interface through the main operating system. This method can display the toolbar in the vehicle display interface even after the vehicle has started, even if the main operating system has not finished starting. This can provide vehicle functions to users more quickly and meet the user's needs for using vehicle functions when the vehicle is just started.

[0109] The following describes a display control method for an in-vehicle display interface through specific embodiments.

[0110] like Figure 6 and Figure 7As shown, the display control method for the vehicle display interface in this embodiment of the invention includes the following steps S601 to S608:

[0111] Step S601: In chronological order, after the vehicle starts, the HAL layer in the main operating system Android OS starts first, and the function signals of the vehicle function are obtained by checking whether the HAL layer can be used.

[0112] The vehicle functions include the vehicle functions corresponding to each of the second function icons in the second toolbar that were in the first state when the vehicle was powered off during the last ignition cycle. The first state is a triggerable state.

[0113] In step S602, in response to obtaining the above-mentioned function signal, the number of the above-mentioned vehicle functions that have received the above-mentioned function signal can be determined by the HAL layer, and based on the above-mentioned number and the size of the first toolbar, the display position of each of the above-mentioned first function icons in the first toolbar is determined.

[0114] Step S603: For the vehicle function that needs to be used normally before the main operating system is fully started—the reversing camera—its function data and control data can be obtained through the HAL layer.

[0115] like Figure 7 As shown, solid lines represent the flow of functional data, and dashed lines represent the flow of control data. The HAL layer can obtain functional data of the reversing image from the rear camera device and control data of the reversing image from the video control device in the main operating system via the electronic control unit that integrates the driving assistance system.

[0116] Step S604: Determine the drawing data of the first toolbar from the drawing library of the HAL layer itself;

[0117] Step S605: Based on the above drawing data and the above display position, draw the above first toolbar and the first function icon in the above first toolbar through the drawing library of the HAL layer itself, and store them in the graphics cache area.

[0118] Specifically, the first function icon of the reversing camera that has acquired functional and control data is depicted as the first state, which is the triggerable state; the first function icons of other vehicle functions that have not acquired functional and control data are depicted as the second state, which is the non-triggerable state.

[0119] Step S606: Communicate with the display controller of the display screen through the HAL layer, and send the first toolbar stored in the graphics cache and the first function icon in the first toolbar to the display controller, so as to display the first toolbar and the first function icon in the first toolbar in the vehicle display interface of the display screen.

[0120] Step S607: When the user triggers the first function icon of the reversing image, the HAL layer can obtain control data from the video control device of the main operating system, send the control data to the rear camera device of the vehicle via the electronic control unit integrated with the driving assistance system, and obtain the reversing image data from the rear camera device of the vehicle via the electronic control unit integrated with the driving assistance system, thereby displaying the reversing image data on the vehicle display interface.

[0121] In step S608, as all apps in the Android OS start up and the Android OS completes startup, the Android OS obtains the function data and control data of all vehicle functions. Then, the Android OS uses its own drawing library to draw the second toolbar and the second function icon displayed in the second toolbar in the second state. The second toolbar and the second function icon in the second toolbar are displayed on the vehicle display interface through the display service of the main operating system to replace the first toolbar and the first function icon in the first toolbar.

[0122] According to the display control method of the vehicle display interface of the present invention, after the vehicle is started, during the startup of the main operating system, it is identified whether the function signal of the vehicle function is obtained. If the function signal can be obtained, a first toolbar and a first function icon in the first toolbar are displayed in the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system has finished starting, a second toolbar and a second function icon in the second toolbar are drawn and displayed in the vehicle display interface through the main operating system. This method can display the toolbar in the vehicle display interface even after the vehicle has started, even if the main operating system has not finished starting. This can provide vehicle functions to users more quickly and meet the user's needs for using vehicle functions when the vehicle is just started.

[0123] Figure 8 This is a schematic diagram of the main modules of the display control device for an in-vehicle display interface according to an embodiment of the present invention. Figure 8As shown, the display control device 800 for the vehicle display interface of this embodiment includes: a startup module 801, used to start the main operating system in response to vehicle startup and identify whether a function signal of a vehicle function has been obtained; a first display module 802, used to display a first toolbar and a first function icon in the first toolbar in the vehicle display interface through a hardware abstraction layer and / or an auxiliary operating system in response to obtaining the function signal; the first function icon corresponds to the vehicle function; and a second display module 803, used to draw a second toolbar and a second function icon in the second toolbar in the vehicle display interface through the display service of the main operating system in response to the completion of startup of the main operating system, and replace the first toolbar and the first function icon in the first toolbar with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to the vehicle function.

[0124] In an optional embodiment of the present invention, the startup module 801 is further configured to: start an auxiliary operating system independent of the main operating system before starting the main operating system.

[0125] The first display module 802 is further configured to: determine the drawing data of the first toolbar in the drawing library of the auxiliary operating system based on the toolbar drawing task created in advance in the auxiliary operating system; draw the first toolbar and the first function icon in the first toolbar through the auxiliary operating system based on the drawing data; and call the display function of the hardware abstraction layer through the auxiliary operating system to display the first toolbar and the first function icon in the first toolbar in the vehicle display interface.

[0126] In an optional embodiment of the present invention, the first display module 802 is further configured to: determine the drawing data of the first toolbar from its own drawing library through the hardware abstraction layer; draw the first toolbar and the first function icon in the first toolbar through the hardware abstraction layer based on the drawing data, and display the first toolbar and the first function icon in the first toolbar in the vehicle display interface.

[0127] In an optional embodiment of the present invention, the first display module 802 is further configured to: acquire the functional data and control data of the vehicle function; in response to acquiring the functional data and control data of the vehicle function, display a first toolbar and a first function icon displayed in the first toolbar in a first state on the vehicle display interface; in response to not acquiring the functional data and / or control data of the vehicle function, display the first toolbar and the first function icon displayed in the first toolbar in a second state on the vehicle display interface through a hardware abstraction layer.

[0128] In an optional embodiment of the present invention, the vehicle function includes the vehicle function corresponding to each second function icon in the second toolbar that was in the first state when the engine was powered off during the last ignition cycle, and the first state is a triggerable state.

[0129] In an optional embodiment of the present invention, the first display module 802 is further configured to: determine the number of vehicle functions that have received the function signal; and, based on the number and the size of the first toolbar, determine the display position of each of the first function icons in the first toolbar, so as to display the first toolbar and each of the first function icons in the first toolbar in the vehicle display interface according to the display position.

[0130] According to the vehicle display interface display control device of the present invention, after the vehicle is started, during the startup of the main operating system, it identifies whether a function signal of the vehicle function is obtained. If a function signal can be obtained, a first toolbar and a first function icon in the first toolbar are displayed on the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system has finished starting, a second toolbar and a second function icon in the second toolbar are drawn and displayed on the vehicle display interface through the main operating system. This allows the toolbar to be displayed on the vehicle display interface even after the main operating system has not finished starting, providing vehicle functions to the user more quickly and meeting the user's needs for using vehicle functions when the vehicle is first started.

[0131] The following is for reference. Figure 9 It shows a schematic diagram of the structure of a computer system 900 suitable for implementing the display control method of the vehicle display interface in the embodiments of the present invention. Figure 9 The computer system 900 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0132] like Figure 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 902 or programs loaded from storage section 908 into random access memory (RAM) 903. The RAM 903 also stores various programs and data required for the operation of the computer system 900. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0133] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 910 as needed so that computer programs read from it can be installed into storage section 908 as needed.

[0134] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs the functions defined above in the system of this invention.

[0135] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0136] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0137] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a startup module, a first display module, and a second display module. The names of these modules do not necessarily limit the module itself; for example, a startup module can also be described as "a module that, in response to vehicle startup, starts the main operating system and identifies whether a functional signal for a vehicle function has been acquired."

[0138] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to: in response to vehicle startup, start a main operating system and identify whether a function signal for a vehicle function has been obtained; in response to obtaining the function signal, display a first toolbar and a first function icon in the first toolbar on an in-vehicle display interface through a hardware abstraction layer and / or a secondary operating system; the first function icon corresponds to the vehicle function; in response to the main operating system completing startup, draw a second toolbar and a second function icon in the second toolbar on the in-vehicle display interface through the display service of the main operating system, and replace the first toolbar and the first function icon in the first toolbar with the second toolbar and the second function icon in the second toolbar; the second function icon corresponds to the vehicle function.

[0139] According to the technical solution of the present invention, after the vehicle is started, during the process of starting the main operating system, it is identified whether the function signal of the vehicle function is obtained. If the function signal can be obtained, the first toolbar and the first function icon in the first toolbar are displayed on the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system. After the main operating system is started, the second toolbar and the second function icon in the second toolbar are drawn and displayed on the vehicle display interface through the main operating system. The toolbar can be displayed on the vehicle display interface even after the vehicle is started, even if the main operating system has not been started. This can provide vehicle functions to users more quickly and meet the user's needs for using vehicle functions when the vehicle is just started.

[0140] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A display control method for an in-vehicle display interface, characterized in that, include: In response to vehicle startup, the main operating system is launched to identify whether functional signals of the vehicle functions have been acquired; In response to acquiring the function signal, the first toolbar and the first function icon in the first toolbar are displayed in the vehicle display interface through the hardware abstraction layer and / or the auxiliary operating system; The first function icon corresponds to the vehicle function; In response to the completion of the main operating system startup, the display service of the main operating system is used to draw the second toolbar and the second function icon in the second toolbar on the vehicle display interface, and the first toolbar and the first function icon in the first toolbar are replaced with the second toolbar and the second function icon in the second toolbar. The second function icon corresponds to the vehicle function.

2. The display control method for the vehicle-mounted display interface according to claim 1, characterized in that, The method further includes: Before starting the main operating system, start a secondary operating system that is independent of the main operating system; The first toolbar and its first function icons are displayed on the in-vehicle display interface through a hardware abstraction layer and a secondary operating system, including: Based on the toolbar drawing task created in advance in the secondary operating system, the drawing data of the first toolbar is determined in the drawing library of the secondary operating system. Based on the drawing data, the first toolbar and the first function icon in the first toolbar are drawn by the auxiliary operating system. The auxiliary operating system calls the display function of the hardware abstraction layer to display the first toolbar and the first function icon in the first toolbar on the vehicle display interface.

3. The display control method for the vehicle-mounted display interface according to claim 1, characterized in that, Displaying a first toolbar and its first function icons on the in-vehicle display interface via a hardware abstraction layer includes: The drawing data of the first toolbar is determined from its own drawing library through the hardware abstraction layer; Based on the drawing data, the first toolbar and the first function icon in the first toolbar are drawn through the hardware abstraction layer, and the first toolbar and the first function icon in the first toolbar are displayed in the vehicle display interface.

4. The display control method for an in-vehicle display interface according to any one of claims 1-3, characterized in that, The step of displaying a first toolbar and a first function icon in the first toolbar on the vehicle display interface includes: Acquire the functional data and control data of the vehicle functions; In response to obtaining the functional data and control data of the vehicle functions, a first toolbar and a first function icon displayed in the first toolbar in a first state are displayed in the vehicle display interface; In response to the failure to acquire the functional data and / or control data of the vehicle function, a first toolbar and a first function icon displayed in the first toolbar in a second state are displayed in the vehicle display interface through the hardware abstraction layer.

5. The display control method for the vehicle-mounted display interface according to claim 4, characterized in that, The vehicle functions include the vehicle functions corresponding to each second function icon in the second toolbar that was in the first state when the vehicle was powered off during the last ignition cycle, and the first state is a triggerable state.

6. The display control method for an in-vehicle display interface according to claim 1, characterized in that, The step of displaying a first toolbar and a first function icon in the first toolbar on the vehicle display interface includes: Determine the number of vehicle functions that have received the function signal; Based on the quantity and the size of the first toolbar, the display position of each first function icon in the first toolbar is determined, so that the first toolbar and each first function icon in the first toolbar are displayed in the vehicle display interface according to the display position.

7. A display control device for an in-vehicle display interface, characterized in that, include: The startup module is used to respond to vehicle startup, start the main operating system, and identify whether the vehicle function signals have been acquired. The first display module is configured to, in response to acquiring the function signal, display a first toolbar and a first function icon in the first toolbar in the vehicle display interface through a hardware abstraction layer and / or an auxiliary operating system. The first function icon corresponds to the vehicle function; The second display module is used to, in response to the completion of the startup of the main operating system, draw a second toolbar and a second function icon in the second toolbar in the vehicle display interface through the display service of the main operating system, and replace the first toolbar and the first function icon in the first toolbar with the second toolbar and the second function icon in the second toolbar. The second function icon corresponds to the vehicle function.

8. An electronic device for display control of an in-vehicle display interface, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.

9. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-6.

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

Images