Vehicle-mounted interface rendering method and device, electronic equipment, vehicle and program product

Abstract

The embodiment of the invention provides a vehicle-mounted interface rendering method and device, electronic equipment, a vehicle and a program product, and relates to the field of automobile intelligence. The method comprises the following steps: acquiring a node area rendering refresh rate of a node in the vehicle-mounted interface; positioning a node control area of a node in the vehicle-mounted interface; generating a node area frame skipping parameter according to the node area rendering refresh rate; and rendering the node control area based on the node area frame skipping parameter. According to the method and the device, different nodes can be supported to update by using differentiated refresh rates, so that the optimal refresh rate is allocated to each node on the interface according to actual requirements, key functions such as heartbeat detection can be maintained on the premise of not sacrificing rendering performance, and a powerful guarantee is provided for system stability and response speed.

Description

Technical Field

[0001] The present application relates to the field of vehicle intelligence, and particularly to a vehicle-mounted interface rendering method, device, electronic device, vehicle and program product. Background Art

[0002] During the rendering process of in-vehicle instruments or center consoles, even if the data on the interface has not changed, the system may still perform unnecessary rendering operations, thus consuming precious CPU and GPU resources. This usually stems from the system's sensitive mechanism for interface data changes. Even if the data has not actually changed, the system may misjudge that the data has been updated and trigger the rendering process. Such unnecessary rendering not only increases the burden on the system but may also affect the response speed and user experience of in-vehicle applications. Secondly, in order to reduce resource occupancy, developers may try to stop rendering when there is no data change in the application. However, this approach may interfere with the normal operation of key functions such as heartbeat detection in the application. Heartbeat detection is an important means to ensure the stable operation of the application, which relies on regularly sending data packets to the service to confirm the running state of the application. When rendering stops, the sending of heartbeat data packets may also be affected, resulting in the service being unable to accurately judge the running state of the application, which may trigger an incorrect restart mechanism. This will not only interrupt the normal use of users but may also pose a potential threat to the overall stability and security of the in-vehicle system. Summary of the Invention

[0003] The main purpose of the embodiments of the present application is to propose a vehicle-mounted interface rendering method, device, electronic device, vehicle and program product, aiming to reduce the resource occupancy of vehicle-mounted interface rendering.

[0004] In a first aspect, the present application provides a vehicle-mounted interface rendering method, and the method includes:

[0005] Obtain the node area rendering refresh rate of nodes in the vehicle-mounted interface;

[0006] Locate the node control area of nodes in the vehicle-mounted interface;

[0007] Generate a node area frame skipping parameter according to the node area rendering refresh rate;

[0008] Render the node control area based on the node area frame skipping parameter.

[0009] In a possible implementation manner, the step of rendering the node control area based on the node area frame skipping parameter specifically includes:

[0010] Control the node area frame skipping count to count;

[0011] When the frame skip count of the node area is equal to the frame skip parameter of the node area, render the node control area;

[0012] Among them, the frame skip count of the node area increases as the main rendering loop is executed.

[0013] In a possible implementation, before the step of controlling the frame skip count of the node area to count, it further includes:

[0014] Cache the current node rendering result of the node control area to obtain a node area rendering cache, and stop rendering the node control area.

[0015] In a possible implementation, the step of controlling the frame skip count of the node area to count specifically includes:

[0016] Reset the frame skip count of the node area, and control the frame skip count of the node area to count.

[0017] In a possible implementation, the step of when the frame skip count of the node area is equal to the frame skip parameter of the node area, rendering the node control area specifically includes:

[0018] When the frame skip count of the node area is equal to the frame skip parameter of the node area, reset the node area rendering cache, and render the node control area.

[0019] In a possible implementation, the step of generating the frame skip parameter of the node area according to the rendering refresh rate of the node area specifically includes:

[0020] Obtain the window rendering refresh rate of the vehicle-mounted interface;

[0021] Based on the window rendering refresh rate and the rendering refresh rate of the node area, calculate the frame skip parameter of the node area.

[0022] In a second aspect, the present application provides a vehicle-mounted interface rendering device, and the device includes:

[0023] An acquisition module, configured to acquire the rendering refresh rate of the node area of the node in the vehicle-mounted interface;

[0024] A positioning module, configured to position the node control area of the node in the vehicle-mounted interface;

[0025] A generation module, configured to generate a frame skip parameter of the node area according to the rendering refresh rate of the node area;

[0026] A frame skip module, configured to render the node control area based on the frame skip parameter of the node area.

[0027] In a third aspect, the present application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the vehicle-mounted interface rendering method as described in the above first aspect or any possible implementation manner of the first aspect.

[0028] In a fourth aspect, the present application provides a vehicle, which includes the vehicle-mounted interface rendering device described in the above second aspect or the electronic device described in the above third aspect.

[0029] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the vehicle-mounted interface rendering method as described in the above first aspect or any possible implementation manner of the first aspect when executed by a processor.

[0030] The vehicle-mounted interface rendering method, device, electronic device, vehicle, and program product proposed by the present application perform separate rendering control on the node control area corresponding to a node through a node control method, so that some functions that rely on each rendering trigger, such as heartbeat detection, can be normally deployed and used without affecting the overall rendering frame rate of the entire window. Moreover, during the process of node rendering, a node area frame skipping parameter is introduced to control the node rendering in the form of frame skipping, thereby ensuring the rendering frame rate control of the node control area. Description of the Drawings

[0031] Figure 1 It is a schematic flowchart of a vehicle-mounted interface rendering method provided by an embodiment of the present application;

[0032] Figure 2 For the present application Figure 1 It is a flowchart of step S104 in the present application;

[0033] Figure 3 It is a schematic diagram of an application display window of a vehicle-mounted interface rendering method provided by an embodiment of the present application;

[0034] Figure 4 It is a schematic flowchart of frame skipping rendering of a vehicle-mounted interface rendering method provided by an embodiment of the present application;

[0035] Figure 5 It is a schematic structural diagram of a vehicle-mounted interface rendering device provided by an embodiment of the present application;

[0036] Figure 6 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed Embodiments

[0037] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] It should be noted that although functional module division is performed in the device schematic diagram and the logical sequence is shown in the flowchart, in some cases, the steps shown or described may be executed in a different module division in the device or a different sequence in the flowchart. Terms such as "first" and "second" in the description, claims and the above-mentioned drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0039] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0040] First, several terms involved in the present application are analyzed:

[0041] Rendering: Rendering is a complex and delicate process. It involves various elements in the interface, including text, images, buttons, icons, etc. According to preset styles (such as fonts, colors, borders, etc.), layout rules (such as the arrangement and position of elements), and other relevant parameters, it is calculated and drawn through a professional rendering engine. In this process, the rendering engine will parse the interface description file, load the necessary resources, and calculate the final appearance of each interface element according to the style rules and themes. At the same time, it will also calculate the specific position and size of each element according to the layout rules and screen size. Finally, these elements will be drawn onto the screen in sequence and a complete image frame will be generated through synthesis technology and output to the display for the user to view. Interface rendering technology is widely used in user interface design, game development, mobile application development, and graphic design, providing rich, intuitive, and easy-to-operate interface display methods for these fields.

[0042] Caching: Caching is a mechanism widely used in computer systems or applications. It temporarily stores data frequently accessed by users or the system in memory to reduce the time and resource consumption required to read these data from slower storage media (such as hard disks or networks) during subsequent accesses. This mechanism embeds hardware or software components in memory to automatically store a certain amount of recently or most frequently accessed data. When these data are requested again, they can be quickly obtained from the cache, thus greatly improving the speed and efficiency of data access.

[0043] Currently, during the performance optimization of in-vehicle instrument or central control applications, it is usually necessary to support low-frame-rate rendering or stop rendering of the page when there is no data change in the screen to reduce the resource occupancy of the system's CPU and GPU. In applications made with Kanzi, a configuration word with ApplicationIdleState set to 1 is usually added to the application configuration file to achieve the stop rendering of the application when there is no data change. However, the operation of updating data in SetProperty in Kanzi will also trigger the operation of parameter change when setting the same data for a parameter, thus waking up the Kanzi Engine to execute the rendering task. When making an application with Kanzi, using SetProperty to update data is an unavoidable operation. If we want to avoid triggering this situation, we need to replace it with bindings with greater function limitations or compare the data before and after the SetProperty trigger to determine whether data needs to be updated. This optimization method usually requires a large amount of manpower to modify and maintain. In application development, for example, the instrument display App usually needs to develop an application heartbeat detection function to determine whether the program is in a normal running state. The specific method is to send a data packet to the relevant service before each frame rendering of the application. The service depends on whether it can receive the data packet every period of time to determine whether the application is in a running state and whether the application is stuck. Under this requirement premise, since the solution of adding a configuration word with ApplicationIdleState set to 1 in the application configuration file will cause the rendering thread to stop when stopping rendering, the logic of sending a data packet to the relevant service before each frame rendering of the application will not be able to be executed. Since the relevant service has not received the heartbeat data packet from the application program for a long time, this will cause the service to misjudge that the application is in a serious stuck state and restart the application.

[0044] Therefore, the existing in-vehicle interface rendering method faces the problem of high resource occupancy, with a high burden on the in-vehicle system, which affects the response speed and user experience of in-vehicle applications.

[0045] Based on the above problems, this application performs separate rendering control on the node control area corresponding to the node through the method of node control, so that some functions that rely on each rendering trigger, such as heartbeat detection, can be normally deployed and used without affecting the overall rendering frame rate of the entire window. Moreover, during the process of node rendering, a node area frame skipping parameter is introduced, and the control of node rendering is achieved in the form of frame skipping, so as to ensure separate rendering frame rate control for the node control area.

[0046] More specifically, the present application enables the optimization of the application's CPU and GPU by controlling the application to have low frames or static frames while supporting heartbeat detection (without affecting the rendering thread); moreover, the application is optimized in the case where ApplicationIdleState cannot be used for optimization (a large number of SetProperty are used in the application for function production and other solutions cannot be used for replacement).

[0047] The in-vehicle interface rendering method provided by the embodiments of the present application can be applied to a terminal, can also be applied to a server side, or can also be software running on the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, an in-vehicle terminal, etc.; the server side can be configured as an independent physical server, can also be configured as a server cluster or a distributed system composed of multiple physical servers, or can also be configured as a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application implementing the in-vehicle interface rendering method, etc., but is not limited to the above forms.

[0048] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet-type devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, small computers, large computers, distributed computing environments including any of the above systems or devices, and so on. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in a distributed computing environment where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0049] It should be noted that in each specific embodiment of the present application, when it comes to relevant processing based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first. Moreover, the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiments of the present application need to obtain the user's sensitive personal information, the user's separate permission or separate consent will be obtained through methods such as pop-up windows or redirecting to a confirmation page. After clearly obtaining the user's separate permission or separate consent, the necessary user-related data for the normal operation of the embodiments of the present application will be obtained.

[0050] Figure 1 It is a schematic flowchart of a vehicle-mounted interface rendering method provided by an embodiment of the present application. Figure 1 The method in it may include but is not limited to steps S101 to S104.

[0051] S101. Obtain the node area rendering refresh rate of the nodes in the vehicle-mounted interface;

[0052] S102. Locate the node control area of the nodes in the vehicle-mounted interface;

[0053] S103. Generate node area frame skipping parameters according to the node area rendering refresh rate;

[0054] S104. Render the node control area based on the node area frame skipping parameters.

[0055] Specifically, the system first obtains the node area rendering refresh rate of each node in the in-vehicle interface. The node area rendering refresh rate refers to the number of times a specific node control area is re-rendered per unit time, which determines the speed of the screen update in that area. For different nodes, their node area rendering refresh rates may vary, depending on the type, importance of the node, and the user's interaction requirements. Immediately afterwards, the system locates each node control area, which is the specific position and range occupied by the node on the interface. After obtaining the node area rendering refresh rate of the node, the system generates the frame skipping parameters for the node area based on the node area rendering refresh rate of the node. The node area frame skipping parameters are used to guide the system on how to optimize the rendering process according to the node area rendering refresh rate of the node. By reasonably setting the frame skipping of the node area, the system can reduce unnecessary rendering times while ensuring the smoothness of the screen, thereby reducing the resource consumption of the system. Finally, the system uses the generated frame skipping of the node area to render the node control area. During the rendering process, the system decides when to render and what to render according to the frame skipping of the node area. In this way, the system can utilize resources more efficiently while ensuring the response speed and smoothness of the user interface. The in-vehicle interface rendering method provided by the embodiments of the present application optimizes the in-vehicle interface rendering process through steps such as obtaining the node area rendering refresh rate of the node, locating the node control area, generating the node area frame skipping parameters, and rendering based on the node area frame skipping parameters. This method can not only improve the rendering efficiency, reduce resource consumption, but also enhance the response speed and smoothness of the user interface, bringing a better interaction experience to users.

[0056] More specifically, in the generation of nodes, the present application uses Node2D in the Kanzi Engine as the base class, adds the function of implementing the control area rendering refresh rate to make a Kanzi plug-in, which is used to implement node control for areas with different refresh rates. In the entire window rendering, each 2D node can be used as a separate area for rendering control. As Figure 3 shown, when the maximum refresh rate set by the application is 60 frames, and this plug-in is used to layout the area and set the refresh rate. When area 1 is set to 30 frames, the number of times area 1 is redrawn per second is only 30 times, which is 30 frames less than the entire application display window. When the area is set to 20 frames, the performance consumption of area 2 for redrawing per second is only 1 / 3 of the original. When area 3 is set to 15 frames, the performance consumption of area 3 for redrawing per second is only 1 / 4 of the original. This method only acts on the control of a single node in rendering control and does not affect the rendering frame rate of the entire display window, enabling some functions that rely on each rendering trigger, such as heartbeat detection, to be normally deployed and used.

[0057] Please refer to Figure 2, in some embodiments, step S104 may include but is not limited to steps S1041 to S1042:

[0058] S1041. Control the node area skip frame count to count;

[0059] S1042. When the node area skip frame count is equal to the node area skip frame parameter, render the node control area;

[0060] Wherein, the node area skip frame count increases as the main rendering loop is executed.

[0061] In this embodiment, in order to track the number of rendered frames that have been skipped, the node area skip frame count is used to record the number of frames that have passed since the last rendering of a specific node control area. This counter increases every time the main rendering loop is executed. When the node area skip frame count reaches the preset node area skip frame parameter, the system triggers the rendering of the node control area. For example, if the node area skip frame parameter is set to 5, then the node control area will be rendered every 6 frames. After rendering is completed, the node area skip frame count is usually reset to 0 or starts counting again to prepare for the next rendering.

[0062] More specifically, the Kanzi Engine provides a setCacheResult control property that supports node caching and a control property resetCacheResult for resetting node caching. When initializing the plugin node, set the value of the setCacheResult property to true so that the node does not perform rendering operations by default. Subsequently, control the execution timing of resetCacheResult to control node rendering and cache refreshing. In this application, the skip frame method is used to control node rendering and cache refreshing. For example, if the skip frame is set to 0, then the node will be rendered every frame, that is, the refresh rate is kept consistent with the overall application. When set to 1, the node will retain the cache updated by the previous frame rendering for the next frame to use. Repeating this way, the refresh rate of half of the overall application can be used to refresh all the content within the node. When set to n, it means rendering and caching once every n + 1 frames. Refer to Figure 4, in the main program rendering loop, each loop traverses and calls the renderOverride function of each child node. Therefore, in the main program rendering, each time the renderOverride function of this plugin node is executed, the custom frame skip counter parameter FrameCount used to determine whether to render and reset the cache will be incremented by 1. When a certain call to renderOverride determines that the number of frame skips of FrameCount is equal to the set FrameStep parameter, the node will reset the counter FrameCount and set to perform a rendering and cache reset once. By looping the above operations, the rendering frame rate control of the data in the node can be achieved. Regarding the increment of the count of FrameCount, the above operations can also be encapsulated into a function, and this function can be submitted as a task to the rendering stage of the main loop queue for callback, and the running state of the main rendering thread can also be obtained.

[0063] Before step S1041 in some embodiments, it further includes:

[0064] Cache the current node rendering result of the node control area to obtain the node area rendering cache, and stop rendering the node control area.

[0065] Specifically, in the rendering process of the in-vehicle interface, when the cumulative frame skip count of the node area reaches the preset node area frame skip parameter, the system will trigger a specific rendering event, that is, re-render the node control area. By adopting the node area rendering cache, the system can significantly improve the rendering efficiency while ensuring the normal progress of interface updates. Since the cached rendering result already contains the latest visual representation of the node control area, it can be directly presented to the user without repeating the time-consuming rendering calculations. In this way, not only the burden on the CPU and GPU is reduced, but also the response speed of the interface is accelerated, and the overall user experience is improved. When the system uses the rendering cache, it will simultaneously monitor the data changes in the node control area. Once it detects a change in data or status, the system will immediately update the cache and re-render the node control area to ensure the accuracy and consistency of the interface content. Therefore, the use of the node area rendering cache not only optimizes the rendering performance but also ensures the real-time and accuracy of interface updates.

[0066] In step S1041 of some embodiments, it specifically includes:

[0067] Reset the node area frame skip count and control the counting of the node area frame skip count.

[0068] Specifically, in the rendering optimization strategy of the in-vehicle interface, resetting the frame skipping count is a crucial step. Its purpose is to ensure that at the beginning of each rendering cycle, or when a significant change occurs in the detected node control area, the frame skipping count can restart from a known and definite initial state (such as 0 or other preset values). Such a design helps to eliminate rendering errors or interface inconsistency problems that may be caused by the residual state of the frame skipping count in the previous rendering cycle or event. By resetting the frame skipping count at the beginning of each cycle or event, the system can ensure the correct execution of the frame skipping logic, thereby making accurate judgments based on the current rendering requirements and conditions. At a fixed point in the rendering main loop, such as the beginning of the loop, or when changes occur in the content, style, or data of the node control area, the system will immediately trigger the reset operation of the frame skipping count. This ensures that the frame skipping count can always be synchronized with the current rendering state, providing a reliable basis for subsequent rendering decisions. Generally speaking, resetting the frame skipping count is a key link in the rendering optimization of the in-vehicle interface, which helps to improve the accuracy and consistency of the rendering logic, thereby providing users with a smoother and more stable interface experience.

[0069] In step S1042 of some embodiments, it specifically includes:

[0070] When the frame skipping count of the node area is equal to the frame skipping parameter of the node area, reset the rendering cache of the node area and render the node control area.

[0071] Specifically, the purpose of resetting the rendering cache is to ensure that before rendering the node control area, the content in the cache is up-to-date or has been cleared, so as to avoid using outdated or invalid rendering results. When the frame skipping count of the node area is equal to the frame skipping parameter of the node area, the system will clear or overwrite the existing rendering cache. Set the cache to an empty state or a default state, ready to receive new rendering results. Render the node control area according to the current state and data. Since the rendering cache has been reset, this step will generate new rendering results and store them in the cache. The rendering process usually involves calculating the visual representation of the node control area and drawing it on the screen. This may include drawing elements such as shapes, texts, images, etc., and applying effects such as colors, shadows, animations, etc.

[0072] In step S103 of some embodiments, it specifically includes:

[0073] Obtain the window rendering refresh rate of the in-vehicle interface;

[0074] Calculate the frame skipping parameter of the node area based on the window rendering refresh rate and the rendering refresh rate of the node area.

[0075] Specifically, during the rendering of the node control area, since the frame skipping method is used for the rendering of the node control area, it is necessary to calculate the frame skipping parameters of the node area. When calculating the frame skipping parameters of the node area, the following formula needs to be used for calculation:

[0076]

[0077] Among them, FrameStep is the frame skipping parameter of the node area, TotalFrame is the window rendering refresh rate, and NodeFrame is the node area rendering refresh rate.

[0078] Calculate the number of frames to be skipped in the node control area through the ratio of the window rendering refresh rate and the node area rendering refresh rate, so as to realize the rendering control of the node control area.

[0079] Figure 5 FIG. is a schematic structural diagram of a vehicle-mounted interface rendering device provided by an embodiment of the present application. The vehicle-mounted interface rendering device 500 includes:

[0080] An acquisition module 501, configured to acquire the node area rendering refresh rate of a node in the vehicle-mounted interface;

[0081] A positioning module 502, configured to position the node control area of a node in the vehicle-mounted interface;

[0082] A generation module 503, configured to generate a node area frame skipping parameter according to the node area rendering refresh rate;

[0083] A frame skipping module 504, configured to render the node control area based on the node area frame skipping parameter.

[0084] The specific implementation manner of this vehicle-mounted interface rendering device is basically the same as the specific embodiment of the above vehicle-mounted interface rendering method, and will not be repeated here.

[0085] An embodiment of the present application further provides an electronic device. The electronic device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the above vehicle-mounted interface rendering method is implemented. This electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.

[0086] Please refer to Figure 6 , Figure 6 which schematically shows the hardware structure of an electronic device in another embodiment. The electronic device includes:

[0087] The processor 601 can be implemented in the form of a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0088] The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM), etc. The memory 602 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 602 and are called by the processor 601 to execute the vehicle-mounted interface rendering method of the embodiments of the present application;

[0089] The input / output interface 603 is used to implement information input and output;

[0090] The communication interface 604 is used to implement communication interaction between this device and other devices, and can implement communication through a wired method (such as USB, network cable, etc.) or through a wireless method (such as a mobile network, WIFI, Bluetooth, etc.);

[0091] The bus 605 transmits information between the various components of the device (such as the processor 601, the memory 602, the input / output interface 603, and the communication interface 604);

[0092] Among them, the processor 601, the memory 602, the input / output interface 603, and the communication interface 604 achieve communication connections with each other inside the device through the bus 605.

[0093] The embodiments of the present application also provide a vehicle, and the vehicle includes the above-mentioned vehicle-mounted interface rendering device or the above-mentioned electronic device.

[0094] The embodiments of the present application also provide a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the above-mentioned vehicle-mounted interface rendering method.

[0095] The embodiments described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided in the embodiments of the present application. Those skilled in the art know that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0096] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than those shown in the figures, or combine certain steps, or different steps.

[0097] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0098] Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations.

[0099] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0100] It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or its similar expression means any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (one) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0101] In several embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the above division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be in electrical, mechanical or other forms.

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

[0103] In addition, in each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0104] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in each embodiment of the present application. And the aforementioned storage medium includes: various media that can store programs such as USB flash drives, mobile hard disks, read-only memories (ROM for short), random access memories (RAM for short), magnetic disks, or optical discs.

[0105] The preferred embodiments of the embodiments of the present application have been described above with reference to the accompanying drawings. However, this does not limit the scope of the rights of the embodiments of the present application. Any modifications, equivalent replacements, and improvements made by those skilled in the art without departing from the scope and essence of the embodiments of the present application shall be within the scope of the rights of the embodiments of the present application.

Claims

1. A vehicle interface rendering method, characterized in that: The method comprises: Obtaining a node area rendering refresh rate of a node in the vehicle interface; Locating a node control area of ​​a node in the vehicle-mounted interface; Generate a node area frame skipping parameter according to the node area rendering refresh rate; The node control area is rendered based on the frame skipping parameters of the node area.

2. The vehicle-mounted interface rendering method according to claim 1, characterized in that: The step of rendering the node control area based on the frame skipping parameter of the node area specifically includes: Control the frame skipping count of the node area to count; When the frame skipping count of the node area is equal to the frame skipping parameter of the node area, rendering the node control area; The node region frame skip count increases as the main rendering loop is executed.

3. The vehicle-mounted interface rendering method according to claim 2, characterized in that: Before the step of counting the frame skipping count of the control node area, the method further includes: The current node rendering result of the node control area is cached to obtain a node area rendering cache, and the rendering of the node control area is stopped.

4. The vehicle-mounted interface rendering method according to claim 2, characterized in that: The step of controlling the frame skipping count of the node area specifically includes: The node area frame skipping count is reset, and the node area frame skipping count is controlled to count.

5. The vehicle-mounted interface rendering method according to claim 2, characterized in that: The step of rendering the node control area when the node area frame skip count is equal to the node area frame skip parameter specifically includes: When the node area frame skip count is equal to the node area frame skip parameter, the node area rendering cache is reset and the node control area is rendered.

6. The vehicle-mounted interface rendering method according to claim 1, characterized in that: The step of generating a node area frame skipping parameter according to the node area rendering refresh rate specifically includes: Obtaining the window rendering refresh rate of the vehicle-mounted interface; A node area frame skipping parameter is calculated based on the window rendering refresh rate and the node area rendering refresh rate.

7. A vehicle-mounted interface rendering device, characterized in that: The device comprises: An acquisition module, used to acquire a node area rendering refresh rate of a node in the vehicle-mounted interface; A positioning module, used to locate the node control area of ​​the node in the vehicle interface; A generating module, used for generating a node area frame skipping parameter according to the node area rendering refresh rate; A frame skipping module is used to render the node control area based on the frame skipping parameters of the node area.

8. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the in-vehicle interface rendering method according to any one of claims 1 to 6 when executing the computer program.

9. A vehicle, characterized in that: The vehicle includes the in-vehicle interface rendering device as described in claim 7 or the electronic device as described in claim 8.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the vehicle-mounted interface rendering method described in any one of claims 1 to 6 is implemented.

Images