Rendering control method and system, storage medium and vehicle-mounted terminal

Abstract

The invention provides a rendering control method and system, a storage medium and a vehicle-mounted terminal. The rendering control method comprises the steps that configuration information of an upper-layer application is acquired, and a rendering engine is confirmed according to the configuration information; then realizing an interface based on a rendering engine and returning to an upper-layer application; and further obtaining a target resource based on the upper-layer application, sending the target resource to the rendering engine, and finally rendering the target resource through the rendering engine. By providing the interface, the independence between the development of the upper-layer application and the rendering engine is ensured, and the coupling degree between the development and the rendering engine is reduced; due to decoupling of the upper-layer application and the rendering engine, developers can focus on logic and function implementation of the application, so that the development efficiency of the view end is improved, and the overall development period is shortened.

Description

Technical Field

[0001] The present application relates to the field of vehicle-mounted auxiliary technology, and in particular to a rendering control method, system, storage medium and vehicle-mounted terminal. Background Art

[0002] Currently, most of the common frameworks for interface application development on the market use the MVC framework, where M (Model) refers to model, V (View) refers to view, and C (Controller) refers to controller. The purpose of using MVC is to separate the implementation code of M and V, so that the same program can use different forms of expression.

[0003] In other words, when developing an application, the code can be abstracted into three parts: one part for control, one part for logic processing, and one part for interface display. Based on this, when a different interface style is needed, while keeping the control end and logic processing end unchanged, the code related to the interface end can be directly modified, or the entire display interface program can be directly replaced without changing the code related to the internal business logic, so as to achieve different display effects with the same function.

[0004] In the software under the entire MVC framework, based on business needs, the later control end and the logic processing end are relatively stable, with high code reusability, and are generally rarely modified. On the contrary, the code and display style of the view end are relatively large. There may be different display style interfaces required for the same rendering engine, or different rendering engines need to be replaced for interface development. From the development timeline of the entire application, the time taken for the modification of the view end may be equivalent to the development time of the entire application during the entire application development process. Therefore, improving the development efficiency of the view end will become a bottleneck.

[0005] In view of the above problems, the bottleneck of low development efficiency caused by switching rendering engines can be attributed to the strong coupling between the upper-layer application on the view side and the rendering engine. Summary of the invention

[0006] In order to solve the above technical problems, the present application provides a rendering control method, system, storage medium and vehicle-mounted terminal that can reduce the coupling between upper-level applications and rendering engines, thereby improving the development efficiency of the view end.

[0007] Specifically, the present application provides a rendering control method, wherein the current view end is configured with multiple rendering engines, and the rendering control method comprises the following steps:

[0008] Obtain configuration information of the upper layer application, and confirm the rendering engine according to the configuration information.

[0009] An interface is implemented based on the rendering engine and returned to the upper layer application.

[0010] A target resource is acquired based on the upper layer application, and the target resource is sent to the rendering engine.

[0011] And, rendering the target resource through the rendering engine.

[0012] In the above technical solution, by providing an interface, the independence between the development of the upper-level application and the rendering engine is ensured, and the coupling between the two is reduced, which means that the upper-level application can easily switch between different rendering engines without modifying the business logic code; due to the decoupling of the upper-level application and the rendering engine, developers can focus more on the logic and function implementation of the application without having to worry about the specific implementation of the interface display, thereby improving the development efficiency of the view end and shortening the overall development cycle.

[0013] Furthermore, the configuration information at least includes a view interface, environment variables and a configuration file; the confirmation rendering engine includes:

[0014] The configuration information is parsed to evaluate the priority of each rendering engine according to the parsing result.

[0015] A highest priority rendering engine is selected based on the priority.

[0016] In the above technical solution, by comprehensively considering various configuration information, the system can flexibly select the best rendering engine according to the actual application scenario and needs. This means that in different environments or conditions, it can automatically adapt to the most suitable rendering engine to ensure efficient rendering of resources.

[0017] Furthermore, the implementation of the interface based on the rendering engine and returning it to the upper layer application includes:

[0018] Respond to the interface call request of the upper layer application, and determine whether the interface corresponding to the interface call request exists.

[0019] When the interface corresponding to the interface call request exists, the interface is called, and the function of the interface is implemented based on the rendering engine, and the implementation result is returned to the upper application.

[0020] In the above technical solution, by checking whether the interface exists before calling, system crashes or exceptions caused by calling non-existent or incorrect interfaces are avoided. This greatly improves the robustness of the system and the reliability of interface calls, ensuring that upper-level applications can interact smoothly with the rendering engine.

[0021] In addition, some simple and easy-to-understand interfaces are defined for upper-level application developers, so that when switching engines, upper-level application developers do not need to redevelop, or can complete the development of upper-level applications with minor changes; at the same time, the interface functions need to be implemented by the underlying rendering engine. If not implemented, there will be functional omissions, and then the corresponding functions on the view side will be applied.

[0022] Furthermore, after determining whether the interface corresponding to the interface call request exists, the method further includes:

[0023] When the interface corresponding to the interface call request does not exist, an error message is returned to the upper layer application.

[0024] In the above technical solution, when the interface does not exist or the call fails, the system can immediately detect and take corresponding actions, which helps to quickly locate and solve the problem and reduce the overall troubleshooting time of the system.

[0025] In addition, the interface calling mechanism further decouples the dependency between the upper-layer application and the rendering engine. The upper-layer application only needs to care about the interface calling and does not need to understand the specific implementation details of the rendering engine.

[0026] Further, the acquiring of target resources based on upper layer applications includes:

[0027] An initial resource is received from an upper layer application, and resource parsing is performed on the initial resource based on the rendering engine to extract feature resources.

[0028] The characteristic resources are reorganized based on the rendering engine to obtain target resources; wherein the resource reorganization at least includes resource conversion and resource alignment.

[0029] In the above technical solution, by parsing the initial resources, the system can extract key feature resources and improve resource utilization; through resource conversion and resource alignment, the format of each resource is unified, and it is ensured that each resource can be aligned to the same timeline or spatial position during the rendering process, thereby reducing repeated calculations during the rendering process and further improving rendering efficiency.

[0030] Based on the same concept, the present application also provides a rendering control system, the system comprising:

[0031] The confirmation module is used to obtain the configuration information of the upper layer application and confirm the rendering engine according to the configuration information.

[0032] An interface implementation module is used to implement an interface based on the rendering engine and return it to the upper layer application.

[0033] The resource processing module is used to obtain the target resource based on the upper layer application and send the target resource to the rendering engine.

[0034] And a rendering module, used for rendering the target resource through the rendering engine.

[0035] In the above technical solution, an interface is provided so that the upper-level application does not need to rely on specific rendering engine details, thereby reducing the coupling between the upper-level application and the rendering engine, and further allowing developers to focus more on the logic and functional implementation of the application, thereby improving the development efficiency of the view end.

[0036] Furthermore, the interface implementation module includes:

[0037] An interface calling unit is used to respond to the interface calling request of the upper layer application and determine whether the interface corresponding to the interface calling request exists. When the interface corresponding to the interface calling request exists, the interface is called, and the function of the interface is implemented based on the rendering engine, and the implementation result is returned to the upper layer application.

[0038] The error handling unit is used to return error information to the upper layer application when the interface corresponding to the interface call request does not exist.

[0039] In the above technical solution, judging whether the interface exists avoids system errors or crashes caused by calling non-existent interfaces, improves the robustness of the system, and ensures the stable operation of upper-layer applications; timely feedback of errors is given when the interface does not exist, helping developers to quickly locate and solve problems.

[0040] Furthermore, the resource processing module includes:

[0041] The resource parsing unit is used to receive the initial resource from the upper layer application and perform resource parsing on the initial resource based on the rendering engine to extract feature resources.

[0042] A resource reorganization unit is used to reorganize the feature resources based on the rendering engine to obtain target resources.

[0043] A sending unit is used to send the target resource to the rendering engine.

[0044] In the above technical solution, the resource parsing unit can process a variety of initial resource formats, enhancing the system's adaptability to different types of resources and meeting diverse application needs; the resource reorganization unit generates target resources by optimizing and transforming feature resources, thereby providing more suitable resources for the rendering engine and improving rendering efficiency.

[0045] In addition, the resource processing module can add new parsing and reorganization methods according to new requirements without completely changing the overall system structure, which enhances the scalability of the system.

[0046] Based on the same concept, the present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the rendering control method when running.

[0047] Based on the same concept, the present application also provides a vehicle-mounted terminal, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the rendering control method.

[0048] Compared with the prior art, the beneficial effects of this application are:

[0049] This application first obtains the configuration information of the upper-layer application, and confirms the rendering engine based on the configuration information; then implements the interface based on the rendering engine and returns to the upper-layer application; further obtains the target resource based on the upper-layer application, sends the target resource to the rendering engine, and finally renders the target resource through the rendering engine. This application ensures the independence between the development of the upper-layer application and the rendering engine by providing an interface, reducing the coupling between the two; due to the decoupling of the upper-layer application and the rendering engine, developers can focus more on the logic and function implementation of the application, thereby improving the development efficiency of the view end and shortening the overall development cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 This is a flow chart of the rendering control method described in this application.

[0051] Figure 2 A schematic diagram of the connection relationship between the view end, upper-layer application and rendering engine.

[0052] Figure 3 This is a framework diagram of the rendering control system described in this application.

[0053] Figure 4 A schematic diagram of the relationship between the rendering control system described in this application and the remaining components of the vehicle terminal. DETAILED DESCRIPTION

[0054] A rendering control method, system, storage medium and vehicle-mounted terminal of the present application are further described in detail below in conjunction with specific embodiments and drawings.

[0055] See also Figure 1, the present application embodiment provides a rendering control method, the current view end is configured with multiple rendering engines (see Figure 2 ), the rendering control method comprises the following steps:

[0056] First, the configuration information of the upper layer application is obtained, and the rendering engine is confirmed according to the configuration information.

[0057] Furthermore, the configuration information at least includes a view interface, environment variables and a configuration file; the confirmation rendering engine includes:

[0058] The configuration information is parsed to evaluate the priority of each rendering engine according to the parsing result.

[0059] A highest priority rendering engine is selected based on the priority.

[0060] In some embodiments, the view interface includes at least the layout, style and components of the user interface; the environment variables include at least system environment variables and hardware performance indicators, etc.; the configuration file includes at least the parameters and settings required for rendering, such as resolution, rendering mode and optimization items, etc.

[0061] After obtaining the configuration information, the system parses the information. The parsing process includes:

[0062] Extract relevant information of the user interface from the configuration information, such as interface size, resolution requirements, complexity of UI elements, etc.; then evaluate the hardware performance of the current system based on system environment variables, such as CPU (Central Processing Unit, central processing unit) and GPU (Graphics Processing Unit, graphics processing unit) performance indicators, memory size, etc.; further parse the configuration file to obtain rendering parameters, such as whether specific rendering effects are required, and performance optimization settings.

[0063] Based on the results of the analysis, the system begins to evaluate the priority of each rendering engine. The evaluation factors include but are not limited to the performance matching degree of the rendering engine, the effect requirement matching degree of the rendering engine, compatibility and historical performance data; after evaluating the priority of each rendering engine, all available rendering engines are sorted according to the evaluated priority, and the rendering engine with the highest priority in the sorting is selected as the final selected rendering engine.

[0064] Among them, the performance matching degree is mainly to determine whether the rendering engine can meet the performance requirements under the current hardware configuration; the effect requirement matching degree is mainly to confirm whether the rendering engine supports the specific rendering effects defined in the configuration file; the compatibility is to confirm the compatibility of the rendering engine with the current operating system and hardware environment; and the historical performance data is to evaluate the performance of each rendering engine based on previous usage.

[0065] It should be noted that those skilled in the art may set other configuration information requirements and evaluation factors according to actual application requirements, and are not limited to these.

[0066] In the above technical solution, by comprehensively considering various configuration information, the system can flexibly select the best rendering engine according to the actual application scenario and needs. This means that in different environments or conditions, it can automatically adapt to the most suitable rendering engine to ensure efficient rendering of resources.

[0067] Further, after the rendering engine is confirmed, an interface is implemented based on the rendering engine and returned to the upper layer application.

[0068] Furthermore, the implementation of the interface based on the rendering engine and returning it to the upper layer application includes:

[0069] Respond to the interface call request of the upper layer application, and determine whether the interface corresponding to the interface call request exists.

[0070] When the interface corresponding to the interface call request exists, the interface is called, and the function of the interface is implemented based on the rendering engine, and the implementation result is returned to the upper application.

[0071] Furthermore, after determining whether the interface corresponding to the interface call request exists, the method further includes:

[0072] When the interface corresponding to the interface call request does not exist, an error message is returned to the upper layer application.

[0073] In some embodiments, the system defines a set of unified interfaces that represent the functions required by upper-level applications, such as drawing graphics, processing textures, rendering animations, etc.; these unified interface definitions are exposed to upper-level applications through an abstract layer, and developers of upper-level applications only need to understand and use these unified interfaces without having to worry about the specific implementation details of the underlying rendering engine.

[0074] When an upper-layer application initiates an interface call request, the system first receives the request and then determines whether the requested interface exists.

[0075] If the interface does not exist, an error message is returned to the upper-level application, indicating that the interface does not exist; if it does exist, the system proceeds to the next step and calls the interface.

[0076] The implementation of the interface function depends on the underlying rendering engine. Each rendering engine may have different implementation methods for the same interface, but their functions are essentially similar. The system will call the corresponding implementation logic of the currently selected rendering engine to complete the interface function.

[0077] Among them, the system will map the call of the unified interface to the interface of the specific rendering engine; if the rendering engine supports an interface function defined by the system, the system will directly call the corresponding interface of the rendering engine; if a function requires a combination of multiple rendering engine interfaces to implement, the system will be responsible for combining these interfaces to ensure that the final implemented function meets the requirements of the upper-level application.

[0078] In other embodiments, if the rendering engine does not directly support certain interface functions, the system can also use other methods or alternatives to achieve the required functions through adaptation logic. For example, if a rendering engine does not support a certain type of texture compression, the system may find other compression methods or achieve similar effects at the software level.

[0079] In the above technical solution, by checking whether the interface exists before calling, system crashes or exceptions caused by calling non-existent or incorrect interfaces are avoided. This greatly improves the robustness of the system and the reliability of interface calls, ensuring that upper-level applications can interact smoothly with the rendering engine.

[0080] In addition, when developing upper-level applications and using different rendering engines, since different rendering engines have different interfaces, upper-level applications need to understand the interfaces of different rendering engines before they can develop applications. The resulting learning cost and development difficulty are bound to increase, and development efficiency is bound to decrease. However, although different rendering engines differ in interface definitions, they have common functions. Based on this premise, some simple and easy-to-understand interfaces are defined for upper-level application developers, so that when upper-level application developers switch engines, they do not need to redevelop or make minor changes to complete the development of upper-level applications. At the same time, the interface functions need to be implemented by the underlying rendering engine. If they are not implemented, there will be functional deficiencies, and the corresponding functions on the application view side will be lost.

[0081] It should be noted that comprehensive considerations need to be made when defining interfaces to support different application requirements. In addition, it may be easy for some rendering engines to implement certain interfaces, while difficult for some other rendering engines to implement. However, this is unavoidable. Interface functions that cannot be implemented by some rendering engines need to be marked during application development to remind developers to adopt other methods or other engine solutions.

[0082] Furthermore, when the interface does not exist or the call fails, the system can immediately detect and take corresponding actions, which helps to quickly locate and solve the problem and reduce the overall troubleshooting time of the system.

[0083] It should also be noted that the interface calling mechanism further decouples the dependency between the upper-layer application and the rendering engine. The upper-layer application only needs to care about the interface calling and does not need to understand the specific implementation details of the rendering engine.

[0084] Furthermore, after the interface is implemented, the target resource is obtained based on the upper layer application, and the target resource is sent to the rendering engine.

[0085] And, rendering the target resource through the rendering engine.

[0086] Further, the acquiring of target resources based on upper layer applications includes:

[0087] An initial resource is received from an upper layer application, and resource parsing is performed on the initial resource based on the rendering engine to extract feature resources.

[0088] The characteristic resources are reorganized based on the rendering engine to obtain target resources; wherein the resource reorganization at least includes resource conversion and resource alignment.

[0089] In some embodiments, the system first receives the initial resources provided by the upper layer application, which may include model data, textures, animation data, scene descriptions, etc. Based on the currently used rendering engine, the initial resources are parsed. The purpose of the parsing is to extract the feature resources required by the rendering engine (such as model data and texture data in a specific format).

[0090] Furthermore, after extracting feature resources, the system needs to convert these feature resources into a format that can be directly used by the rendering engine; resource conversion may include data format conversion (such as from OBJ format to GLTF format), data compression, data optimization, etc.

[0091] Furthermore, the resources are aligned according to the requirements of the rendering engine; for example, ensuring that the alignment of all vertex data in memory meets the access requirements of the GPU, or adjusting the resolution of texture data to meet the performance and effect requirements of the rendering engine.

[0092] After resource conversion and resource alignment, the original resources are reorganized into target resources, which can be directly used by the rendering engine.

[0093] In the above technical solution, by parsing the initial resources, the system can extract key feature resources and improve resource utilization; through resource conversion and resource alignment, the format of each resource is unified, and it is ensured that each resource can be aligned to the same timeline or spatial position during the rendering process, thereby reducing repeated calculations during the rendering process and further improving rendering efficiency.

[0094] Furthermore, the system sends the reorganized target resources to the selected rendering engine; these target resources include but are not limited to model data, texture data, lighting data, camera parameters, etc.; wherein, when sending the resources, the system ensures that the format and content of the resources fully comply with the input requirements of the rendering engine to avoid rendering errors or performance issues caused by data mismatch.

[0095] After receiving the target resources, the rendering engine first loads these resources; for example, loading 3D model data into GPU memory, loading texture data and binding it to the corresponding texture unit.

[0096] Furthermore, the rendering engine performs specific rendering operations based on the loaded resources and instructions from the upper-level application; this may include drawing 3D models, applying textures, lighting calculations, animation updates, etc.

[0097] Furthermore, the rendering engine outputs the final rendering result to the upper-layer application or directly displays it on the screen; the rendering result may be image data in a frame buffer or graphics drawn directly on the screen.

[0098] Further, based on the same concept, see Figure 3 The present application also provides a rendering control system using the above rendering control method, wherein the rendering control system is arranged at the view end (the relationship between this system and other components can be found in Figure 4 ), the system comprising:

[0099] The confirmation module is used to obtain the configuration information of the upper layer application and confirm the rendering engine according to the configuration information.

[0100] An interface implementation module is used to implement an interface based on the rendering engine and return it to the upper layer application.

[0101] Furthermore, the interface implementation module includes:

[0102] An interface calling unit is used to respond to the interface calling request of the upper layer application and determine whether the interface corresponding to the interface calling request exists. When the interface corresponding to the interface calling request exists, the interface is called, and the function of the interface is implemented based on the rendering engine, and the implementation result is returned to the upper layer application.

[0103] The error handling unit is used to return error information to the upper layer application when the interface corresponding to the interface call request does not exist.

[0104] In the above technical solution, judging whether the interface exists avoids system errors or crashes caused by calling non-existent interfaces, improves the robustness of the system, and ensures the stable operation of upper-layer applications; timely feedback of errors is given when the interface does not exist, helping developers to quickly locate and solve problems.

[0105] The resource processing module is used to obtain the target resource based on the upper layer application and send the target resource to the rendering engine.

[0106] Furthermore, the resource processing module includes:

[0107] The resource parsing unit is used to receive the initial resource from the upper layer application and perform resource parsing on the initial resource based on the rendering engine to extract feature resources.

[0108] A resource reorganization unit is used to reorganize the feature resources based on the rendering engine to obtain target resources.

[0109] A sending unit is used to send the target resource to the rendering engine.

[0110] In the above technical solution, the resource parsing unit can process a variety of initial resource formats, enhancing the system's adaptability to different types of resources and meeting diverse application needs; the resource reorganization unit generates target resources by optimizing and transforming feature resources, thereby providing more suitable resources for the rendering engine and improving rendering efficiency.

[0111] In addition, the resource processing module can add new parsing and reorganization methods according to new requirements without completely changing the overall system structure, which enhances the scalability of the system.

[0112] And a rendering module, used for rendering the target resource through the rendering engine.

[0113] Among them, the rendering control system, as a middleware connecting the upper-layer application and the lower-layer rendering engine, needs to decouple the upper-layer application and the lower-layer rendering engine to ensure that the upper-layer application can normally use the functions provided by the underlying rendering engine and can use the applications built based on different underlying layers normally; through this system, when it is necessary to switch to different rendering engines, the upper-layer application does not need to make any changes, and only needs to use a certain rendering engine from the external configuration to directly replace the rendering engine for rendering and display.

[0114] In addition, this system acts as a bridge to communicate between the upper-level application and the underlying rendering engine. When using different rendering engines, the same upper-level application code and resources can be used directly, which improves code reusability and development efficiency.

[0115] It should be noted that the rendering control system adopts the rendering control method as described above, and its specific embodiment will not be described in detail here.

[0116] Furthermore, based on the same concept, the present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the rendering control method when running.

[0117] In some embodiments, the storage medium stores several computer programs for enabling the vehicle-mounted terminal to execute all or part of the steps of the method described in each embodiment of the present application.

[0118] The medium may include a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0119] Furthermore, based on the same concept, the present application also provides a vehicle-mounted terminal, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the rendering control method.

[0120] In some embodiments, the memory and processor are interconnected via a bus; the processor may be one or more CPUs. When the processor is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor is used to control various functional modules of the vehicle terminal and process signals.

[0121] The memory includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), and CD-ROM (Compact Disc Read-Only Memory). The memory is used to store computer programs, operating systems, various applications and data, such as storing a computer program for implementing the rendering control method.

[0122] In summary, the present application provides a rendering control method, system, storage medium and vehicle-mounted terminal; first, the configuration information of the upper-layer application is obtained, and the rendering engine is confirmed according to the configuration information; then, the interface is implemented based on the rendering engine and returned to the upper-layer application; further, the target resource is obtained based on the upper-layer application, the target resource is sent to the rendering engine, and finally, the target resource is rendered by the rendering engine. By providing an interface, the present application ensures the independence between the development of the upper-layer application and the rendering engine, thereby reducing the coupling between the two; due to the decoupling of the upper-layer application and the rendering engine, developers can focus more on the logic and function implementation of the application, thereby improving the development efficiency of the view end and shortening the overall development cycle.

[0123] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present application to this. Those of ordinary skill in the art may make various changes and modifications therein without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as required by the appended claims.

[0124] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0125] In the several embodiments provided in this 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 only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0126] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some modules according to the embodiments of the present application. The application can also be implemented as a device program (e.g., computer program and computer program product) for executing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0127] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0128] Although the description of the present application is carried out in conjunction with the above specific embodiments, it is obvious that those skilled in the art can make many substitutions, modifications and changes based on the above content. Therefore, all such substitutions, improvements and changes are included in the spirit and scope of the appended claims.

Claims

1. A rendering control method, characterized in that: The current view end is configured with multiple rendering engines, and the rendering control method includes the following steps: Obtain configuration information of the upper layer application, and confirm the rendering engine according to the configuration information; Implementing an interface based on the rendering engine and returning it to the upper layer application; Acquire a target resource based on the upper layer application, and send the target resource to the rendering engine; And, rendering the target resource by means of the rendering engine.

2. The rendering control method according to claim 1, characterized in that: The configuration information at least includes a view interface, environment variables and configuration files; The confirmation rendering engine comprises: Parsing the configuration information to evaluate the priority of each rendering engine according to the parsing result; A highest priority rendering engine is selected based on the priority.

3. The rendering control method according to claim 2, characterized in that: The implementation of the interface based on the rendering engine and returning it to the upper layer application includes: Responding to the interface call request of the upper layer application, and determining whether the interface corresponding to the interface call request exists; When the interface corresponding to the interface call request exists, the interface is called, and the function of the interface is implemented based on the rendering engine, and the implementation result is returned to the upper application.

4. The rendering control method according to claim 3, characterized in that: After determining whether the interface corresponding to the interface call request exists, the method further includes: When the interface corresponding to the interface call request does not exist, an error message is returned to the upper layer application.

5. The rendering control method according to claim 4, characterized in that: The obtaining of target resources based on upper layer applications includes: Receiving initial resources from an upper layer application, and performing resource parsing on the initial resources based on the rendering engine to extract feature resources; The characteristic resources are reorganized based on the rendering engine to obtain target resources; wherein the resource reorganization at least includes resource conversion and resource alignment.

6. A system using the rendering control method according to any one of claims 1 to 5, characterized in that: The system includes: a confirmation module, used to obtain configuration information of an upper layer application and confirm a rendering engine according to the configuration information; An interface implementation module, used to implement an interface based on the rendering engine and return it to the upper layer application; A resource processing module, used for acquiring target resources based on the upper layer application, and sending the target resources to the rendering engine; And a rendering module, used for rendering the target resource through the rendering engine.

7. The rendering control system according to claim 6, characterized in that: The interface implementation module includes: an interface calling unit, which is used to respond to the interface calling request of the upper layer application, and determine whether the interface corresponding to the interface calling request exists, and when the interface corresponding to the interface calling request exists, call the interface, and implement the function of the interface based on the rendering engine, and return the implementation result to the upper layer application; The error handling unit is used to return error information to the upper layer application when the interface corresponding to the interface call request does not exist.

8. The rendering control system according to claim 7, characterized in that: The resource processing module includes: A resource parsing unit, configured to receive an initial resource from an upper layer application, and perform resource parsing on the initial resource based on the rendering engine to extract a feature resource; A resource reorganization unit, configured to reorganize the feature resources based on the rendering engine to obtain target resources; A sending unit is used to send the target resource to the rendering engine.

9. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the rendering control method according to any one of claims 1 to 5 when running.

10. A vehicle-mounted terminal, characterized in that: The vehicle-mounted terminal includes a processor and a memory, and the memory stores at least one instruction, at least one program, a code set or an instruction set. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the rendering control method described in any one of claims 1-5.

Images