Graph rendering management method and device, cloud server and readable storage medium

Abstract

The embodiment of the invention provides a graphic rendering management method and device, a cloud server and a readable storage medium. The method comprises the steps of determining whether an application program corresponding to the cloud terminal needs to render an interface in real time or not; if the application program does not need to render the interface in real time, logic operation is executed in the process of running the application program, the graphic rendering interface is skipped, a virtual frame is generated for the graphic rendering interface, rendering information is recorded, and the virtual frame comprises dynamic element data of the interface of the application program; and when the application program needs to recover the real-time rendering interface, calling the graphic rendering interface to render the interface of the application program based on the virtual frame and the rendering information. According to the embodiment of the invention, the scene which does not need to render the interface in real time can be identified, logic processing is executed, but the graphic rendering interface is skipped, the virtual frame and the rendering information are generated, and the interface is recovered as soon as possible when the interface needs to be rendered in real time. Therefore, resources can be saved, performance can be improved, and the interface can be recovered as soon as possible.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a graphics rendering management method, apparatus, cloud server, and readable storage medium. Background Technology

[0002] A cloud terminal is a terminal device that is only responsible for command input and interface display. It communicates with a cloud server via a network, and all computation and data storage are performed within the cloud server. Cloud terminals can include, but are not limited to, cloud phones and cloud computers.

[0003] In existing technologies, after receiving instructions from a cloud terminal, the cloud server needs to perform logical operations, graphics rendering, and other processing to obtain interface data, and then return it to the cloud terminal. The cloud terminal then displays the application's interface on the screen based on the received interface data.

[0004] However, the above solutions suffer from problems such as wasted cloud server resources and low performance. Summary of the Invention

[0005] The purpose of this application is to provide a graphics rendering management method, apparatus, cloud server, and readable storage medium to save cloud server resources and improve cloud server performance. The specific technical solution is as follows: In a first aspect of this application, a graphics rendering management method is provided, applied to a cloud server, the method comprising: Determine whether the application corresponding to the cloud terminal needs to render the interface in real time; if the application does not need to render the interface in real time, then execute logical operations and skip the graphics rendering interface during the running of the application, and generate a virtual frame for the graphics rendering interface and record rendering information, the virtual frame including dynamic element data of the application's interface; when the application needs to restore the real-time rendering interface, call the graphics rendering interface to render the application's interface based on the virtual frame and the rendering information.

[0006] Optionally, generating virtual frames and recording rendering information for the graphics rendering interface includes: The scene complexity of the interface and the performance status of the cloud server are obtained, including the memory performance status and the processor performance status. Target parameters are determined based on the scene complexity and the cloud server performance status, including the richness of virtual frames and the information recording level, which are positively correlated with the scene complexity and the performance status. Virtual frames of the interface are generated based on the richness, and the information recording level and subsequent rendering information are recorded.

[0007] Optionally, the target parameters are determined based on the complexity of the interface and the performance status of the cloud server, including: Obtain the number of cloud accounts running on the cloud server and the priority of the cloud account corresponding to the application; determine the target parameter based on the scenario complexity, the performance status, the number of cloud accounts, and the priority, wherein the target parameter is negatively correlated with the number of cloud accounts and positively correlated with the priority.

[0008] Optionally, the rendering information includes: graphics model information, texture information, and material information. Rendering the interface based on the virtual frame and the rendering information includes: Render the basic graphic elements in the interface based on the graphic model information; load the texture information and material information into the basic graphic elements; load the dynamic element data in the virtual frame into the interface.

[0009] Optionally, the method further includes: The system acquires a sequence of behavioral data from the application, which includes user behavior data at multiple times. It then searches a preset behavior database for a target behavioral data sequence that matches the sequence and acquires the target operation behavior corresponding to the target behavioral data sequence in the preset behavior database. Based on the target operation behavior, the system predicts whether the application needs to restore the real-time rendering interface.

[0010] Optionally, determining whether the application corresponding to the cloud terminal needs to render the interface in real time includes: When the application is a target application preset for the corresponding cloud account, the running status of the application is obtained. The target application includes applications that can stop rendering within the current time period. When the running status includes the target running status, it is determined that the application does not need to render the interface in real time. The target running status includes at least one of the following: background running status, idle status, and automated testing status.

[0011] In a second aspect of this application, a graphics rendering management apparatus is also provided, applied to a cloud server, the apparatus comprising: The rendering recognition module is used to determine whether the application corresponding to the cloud terminal needs to render the interface in real time.

[0012] The rendering skip module is used to perform logical operations and skip the graphics rendering interface during the running of the application if the application does not need to render the interface in real time, and to generate virtual frames for the graphics rendering interface and record rendering information, wherein the virtual frames include dynamic element data of the application's interface.

[0013] The rendering recovery module is used to call the graphics rendering interface to render the application's interface based on the virtual frame and the rendering information when the application needs to restore the real-time rendering interface.

[0014] Optionally, the render skip module is also used for: The scene complexity of the interface and the performance status of the cloud server are obtained, including the memory performance status and the processor performance status. Target parameters are determined based on the scene complexity and the cloud server performance status, including the richness of virtual frames and the information recording level, which are positively correlated with the scene complexity and the performance status. Virtual frames of the interface are generated based on the richness, and the information recording level and subsequent rendering information are recorded.

[0015] Optionally, the render skip module is also used for: Obtain the number of cloud accounts running on the cloud server and the priority of the cloud account corresponding to the application; determine the target parameter based on the scenario complexity, the performance status, the number of cloud accounts, and the priority, wherein the target parameter is negatively correlated with the number of cloud accounts and positively correlated with the priority.

[0016] Optionally, the rendering information includes: graphics model information, texture information, and material information, and the rendering recovery module is further used for: Render the basic graphic elements in the interface based on the graphic model information; load the texture information and material information into the basic graphic elements; load the dynamic element data in the virtual frame into the interface.

[0017] Optionally, the device further includes: The prediction module is used to acquire the behavior data sequence of the application, which includes user behavior data of the application at multiple times; search for a target behavior data sequence that matches the behavior data sequence from a preset behavior database, and acquire the target operation behavior corresponding to the target behavior data sequence in the preset behavior database; and predict whether the application needs to restore the real-time rendering interface based on the target operation behavior.

[0018] Optionally, the rendering recognition module is further configured to: when the application is a target application preset for the corresponding cloud account, obtain the running status of the application, wherein the target application includes: an application that can stop rendering within the current time period; and when the running status includes a target running status, determine that the application does not need to render the interface in real time, wherein the target running status includes at least one of the following: background running status, idle status, and automated testing status. In a third aspect of this application, a cloud server is also provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus. Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the method described in the first aspect above.

[0019] In a fourth aspect of this application, a computer-readable storage medium is also provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform the method described in the first aspect above.

[0020] In a fifth aspect of this application, a computer program product comprising instructions is also provided, which, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0021] The graphics rendering management method, apparatus, cloud server, and readable storage medium provided in this application determine whether the application corresponding to the cloud terminal needs real-time rendering of the interface. If the application does not need real-time rendering, logical operations are performed during the application's execution, skipping the graphics rendering interface. A virtual frame is generated for the graphics rendering interface, and rendering information is recorded. The virtual frame includes dynamic element data of the application's interface. When the application needs to restore real-time rendering, the graphics rendering interface is called to render the application's interface based on the virtual frame and rendering information. This application can identify scenarios where real-time rendering is not required, perform logical processing while skipping the graphics rendering interface, generate virtual frames and rendering information, and restore the interface as quickly as possible when real-time rendering is needed. This not only saves resources and improves performance but also allows for rapid interface restoration. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0023] Figure 1 This is a schematic diagram of a scenario according to an embodiment of this application; Figure 2 This is a flowchart illustrating the steps of a graphics rendering management method in an embodiment of this application; Figure 3 This is a flowchart illustrating another graphics rendering management method in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a graphics rendering management device according to an embodiment of this application; Figure 5This is a schematic diagram of a cloud server in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application. (Refer to...) Figure 1 As shown, the cloud server and cloud terminals communicate, with cloud terminals including various terminal devices such as cloud phones and cloud computers. The cloud terminal sends instructions to the cloud server, and the cloud server sends interface data to the cloud terminal. All logical processing, calculations, and storage are performed on the cloud server; the cloud terminal is only responsible for display and sending instructions.

[0026] The aforementioned cloud server can run multiple applications, APP1 to APP4. Each cloud terminal can be logged in by one or more cloud accounts, for example, Figure 1 The example demonstrates logging into cloud account Z1 on a cloud phone and cloud account Z2 on a cloud computer. However, in practical applications, multiple cloud accounts can be logged into on each cloud phone or cloud computer. For example, cloud account Z1 can also be logged into on a cloud computer.

[0027] Each cloud account on the cloud terminal can access applications on the cloud server. For example, cloud account Z1 can access applications APP1 and APP2, while cloud account Z2 can access applications APP3 and APP4.

[0028] The aforementioned cloud servers require logical processing and graphics rendering during application execution, consuming significant computing and storage resources. However, in scenarios where users don't focus on the user interface, real-time rendering of the application's interface is unnecessary. Therefore, graphics rendering can be omitted, saving cloud server resources and improving both cloud server and cloud phone performance.

[0029] This application's embodiments can identify scenarios where real-time interface rendering is not required, perform logical processing but skip the graphics rendering interface, and generate virtual frames and rendering information to restore the interface as quickly as possible when real-time rendering is needed. This not only saves resources and improves performance but also allows for faster interface restoration.

[0030] The graphics rendering management method of this application will be described in detail below through specific embodiments.

[0031] Figure 2 A flowchart illustrating the steps of a graphics rendering management method provided in this application embodiment is applied to... Figure 1 The cloud server shown, such as Figure 2 As shown, the method may include: S101. Determine whether the application corresponding to the cloud terminal needs to render the interface in real time.

[0032] S102. If the application does not require real-time rendering of the interface, then the application performs logical operations and skips the graphics rendering interface during the application's operation, and generates virtual frames for the graphics rendering interface and records rendering information. The virtual frames include dynamic element data of the application's interface.

[0033] S103. When the application needs to restore the real-time rendering interface, call the graphics rendering interface to render the application interface based on the virtual frame and rendering information.

[0034] The applications corresponding to the aforementioned cloud terminals are applications that run on cloud servers but need to be displayed on cloud terminals.

[0035] Whether an application needs to render its interface in real time can be set by the user. For example, by default, an application needs to render its interface in real time. When a user clicks on a target control on a cloud terminal, the cloud terminal sends a non-real-time rendering instruction to the application. When the cloud server receives this non-real-time rendering instruction, it can determine that the application does not need to render its interface in real time, or it can assume that the cloud terminal can be in a screenless state. Otherwise, it determines that the application needs to render its interface in real time.

[0036] In other implementations, the cloud server can also determine whether real-time rendering is required based on the time of the operation instructions sent by the cloud terminal to the application. For example, if the time elapsed between the last operation instruction received by the cloud server from the cloud terminal to the current time is greater than or equal to a preset time, the cloud server can determine that the application does not need to render the interface in real time; otherwise, it can determine that the application needs to render the interface in real time.

[0037] In some possible implementations, the cloud server can also determine whether real-time interface rendering is required by: when the application is a target application preset for the corresponding cloud account, obtaining the running status of the application, wherein the target application includes applications that can stop rendering within the current time period; when the running status includes a target running status, determining that the application does not need real-time interface rendering, wherein the target running status includes at least one of the following: background running status, idle status, and automated testing status. When the application is not a target application, and / or the application's running status does not include the target running status, it can be determined that the application needs real-time interface rendering.

[0038] Understandably, users can set up target applications independently for each cloud account, and different cloud accounts can correspond to the same or different target applications. For example, Figure 1 The cloud account Z1 shown can set applications APP1 and APP5 as target applications, while cloud account Z2 can set applications APP3 and APP4 as target applications. In this way, users can set applications for which real-time interface rendering can be stopped according to their needs. Users can select some applications with lower interface importance as target applications, while excluding applications with higher interface importance.

[0039] Based on the application described above, users can further set the time period during which real-time rendering of the interface can be stopped. If the current time period in which the application is running falls within the time period during which real-time rendering of the interface can be stopped, then it is determined that real-time rendering of the interface can be stopped for that application; otherwise, it is determined that real-time rendering of the interface cannot be stopped for that application.

[0040] When setting a target application for a corresponding cloud account, it's necessary to further check whether the application is rendering the interface in real-time, taking into account whether its running status matches the target running status. This allows for more accurate identification of scenarios where the application doesn't need to render the interface in real-time, preventing rendering from stopping when the user is viewing the interface.

[0041] The background running state in the above target running state refers to the application's interface not being displayed on the cloud terminal screen, including: cloud terminal screen locked, and user closing the application interface. Specifically, cloud terminal screen locking can be due to the user locking the cloud terminal screen, or the cloud terminal screen automatically turning off and locking after a certain time. The user closing the application interface does not mean exiting the application.

[0042] In summary, the embodiments of this application can identify whether an application needs real-time interface rendering by combining one or more of the following: user settings, operation command time, target application, and target running state. This allows for a more accurate and comprehensive identification of scenarios that do not require real-time interface rendering from one or more dimensions, helping to improve the user experience of cloud terminals.

[0043] This application embodiment is for applications that do not require real-time rendering of the interface. The interface rendering is stopped through the steps of S202 to S203 described above and resumed when needed. When real-time rendering of the interface is required, the application runs normally, that is, it performs logic processing and calls the graphics rendering interface.

[0044] Regarding the stoppage of UI rendering in S202 above, the application's logical operations and rendering processing are separated to skip the graphics rendering interface. In other words, when real-time UI rendering is not required, only logical operations are retained, and graphics rendering is not performed. Furthermore, preparations need to be made for resuming UI rendering to reduce latency. Taking the OpenGL ES graphics system used by Android as an example, while preserving a certain context, the computational load on the GPU (Graphics Processing Unit) is reduced by decreasing the number of draw calls to the graphics rendering interface.

[0045] In one embodiment of this application, generating virtual frames and recording rendering information for the graphics rendering interface includes: first, obtaining the scene complexity of the interface and the performance status of the cloud server, the performance status including memory performance status and processor performance status; then, determining target parameters based on the scene complexity of the interface and the performance status of the cloud server, the target parameters including the richness of the virtual frames and the information recording level, the target parameters being positively correlated with the scene complexity and the performance status; finally, generating virtual frames of the interface based on the richness, and recording the information recording level and below rendering information.

[0046] The complexity of an interface scene can be determined by the number of objects and colors included in the interface. The larger the number of objects and colors, the greater the scene complexity; conversely, the smaller the number of objects and colors, the smaller the scene complexity.

[0047] Memory performance can be represented by the remaining storage space in the memory. Processor performance can be represented by the amount of data processed by the processor per unit time, or by some attributes of the processor, including: operating frequency, cache capacity, amount of data that the processor can process simultaneously, number of cores, instruction set, etc.

[0048] A comprehensive evaluation parameter can be obtained by weighting and summing the scenario complexity and memory performance status, and the corresponding target parameter can be selected based on this comprehensive evaluation parameter. The relationship between the target parameter and the comprehensive evaluation parameter can be represented by a mapping table or by a formula.

[0049] The virtual frames and rendering information in this embodiment are not only related to scene complexity, but also to the performance status of the cloud server. In this way, the virtual frames are dynamically generated and the rendering information is cached in a hierarchical manner, minimizing memory usage and ensuring the performance of the cloud server while guaranteeing the restoration of rendering effects.

[0050] The aforementioned virtual frames are used to synchronize the timeline and logical processing, avoiding data corruption. In this embodiment, virtual frames with varying levels of richness can be generated based on target parameters. For example, they can be categorized into primary virtual frames, intermediate virtual frames, and advanced virtual frames, with the primary virtual frame having the lowest richness, the intermediate virtual frame the next highest, and the advanced virtual frame the highest. For instance, for a game scene, a primary virtual frame only includes simplified data at the logical level of dynamic elements, including but not limited to: simplified motion trajectories of characters and object collision information. An intermediate virtual frame refines the motion trajectory and object collision information based on the primary virtual frame. An advanced virtual frame, based on the intermediate virtual frame, also includes graphical context information of important dynamic elements, model position information, basic material properties, etc.

[0051] Rendering information can include drawing instructions and vertex information, texture information, shader information, rendering pipeline status, transformation matrices, etc.

[0052] Drawing instructions and vertex information can be directly invoked during render restoration to restore the underlying graphics elements.

[0053] Textures and shaders can avoid reloading and mutating textures and shaders when restoring the rendering interface, which helps improve restoration efficiency.

[0054] The rendering pipeline state can include contextual information such as shader binding, texture binding, depth testing, and blending modes. The transformation matrix includes important data related to camera or scene changes, such as the view matrix and projection matrix, which can ensure that the view and scene can be directly restored when re-rendering.

[0055] In some possible implementations, the target parameter is determined based on the complexity of the interface scenario and the performance status of the cloud server. This includes obtaining the number of cloud accounts running on the cloud server and the priority of the cloud account corresponding to the application. The target parameter is then determined based on the scenario complexity, the performance status, the number of cloud accounts, and their priorities. The target parameter is negatively correlated with the number of cloud accounts and positively correlated with the priority. For example, the fewer the number of cloud accounts and the higher the priority of the current application's cloud account, the larger the target parameter; conversely, the more cloud accounts and the lower the priority of the current application's cloud account, the smaller the target parameter. Thus, combining the number of cloud accounts and their priorities allows for a more accurate determination of the target parameter, improving its accuracy.

[0056] Understandably, the priority of a cloud account can be determined during registration, with higher-priority accounts having priority access to more cloud server resources. Once a cloud account's priority is determined, the corresponding application (requested to run) also has a priority. For example, if cloud account Z1 has a higher priority than cloud account Z2, then the application running under cloud account Z1 will have a higher priority than the application running under cloud account Z2.

[0057] After obtaining the aforementioned virtual frame and rendering information, if the rendering interface needs to be restored, it can be restored as quickly as possible. In a conventional approach, the process of determining whether a real-time rendering interface is needed can be followed, similar to the previous method. To further improve the efficiency of interface restoration, it is possible to predict whether a real-time rendering interface needs to be restored, thus anticipating the need for restoration in advance. For example, if it can be predicted at time t1 that a real-time rendering interface restoration is needed at time t2, then restoration preparation can begin at time t1, without waiting until time t2 is determined. t1 is earlier than t2. Specifically, the above method may further include: first, acquiring the application's behavior data sequence, which includes user behavior data on the application at multiple times; second, searching for a target behavior data sequence matching the behavior data sequence in a preset behavior database, and acquiring the target operation behavior corresponding to the target behavior data sequence in the preset behavior database; finally, predicting whether the application needs to restore the real-time rendering interface based on the target operation behavior.

[0058] The behavioral data sequence is formed by multiple user actions on the application prior to the current time, with each action corresponding to a set of behavioral data. This behavioral data sequence describes the user's operational habits on the application, allowing analysis to determine whether the user will view the interface in the future, and thus predicting whether real-time rendering of the interface needs to be restored.

[0059] The target behavior data sequence is a preset behavior data sequence that matches the aforementioned behavior data sequence in the preset behavior database. The preset behavior database includes one or more preset behavior data sequences and a target operation behavior corresponding to each preset behavior data sequence. The target operation behavior is the behavior that is usually executed after the preset behavior data sequence is executed. The preset behavior database can be obtained by analyzing historical behavior data, statistically analyzing historical behavior sequences with a frequency greater than or equal to a preset frequency threshold, with a length of M, and using the first M-1 historical behavior data in the historical behavior sequences as the preset behavior data sequence, and the Mth historical behavior data as the target operation behavior.

[0060] By analyzing the target operation behavior mentioned above, it can be determined whether the real-time rendering interface needs to be restored. If the target operation behavior falls within the scope of behaviors that require real-time viewing of the interface, it can be determined that the real-time rendering interface needs to be restored; otherwise, it does not need to be restored.

[0061] In some possible implementations, the aforementioned preset behavior database may also store multiple behavior data sequences that need to be restored for the real-time rendering interface. If the current behavior data sequence exists in the rendering behavior library that needs to be restored, it is predicted that the real-time rendering interface needs to be restored.

[0062] Each preset behavior database can correspond to one application, thus improving prediction efficiency.

[0063] Of course, the behavioral data sequence can also be input into a pre-trained behavioral prediction model to determine whether the real-time rendering interface needs to be restored.

[0064] In some implementations, when it is predicted that a real-time rendered interface needs to be restored, the interface can be rendered first, but not sent to the cloud terminal for display. Instead, the interface data is sent to the cloud terminal for display only after receiving user input confirming that real-time rendering of the interface is required. In this way, not only can rendering be prepared in advance by predicting in advance, but the transmission resources consumed by sending interface data can also be reduced.

[0065] Specifically, the rendering information includes: graphics model information, texture information, and material information. Rendering the interface based on the virtual frame and the rendering information includes: rendering the basic graphics elements in the interface based on the graphics model information; loading the texture information and material information into the basic graphics elements; and loading the dynamic element data from the virtual frame into the interface. This application embodiment progressively restores the interface rendering, first restoring a simple 2D (2-dimensional) interface and basic scene structure based on the graphics model information describing the interface with basic graphics elements, then gradually loading textures and materials to make the interface more textured, and finally loading dynamic information into the interface to achieve dynamic effects. In this way, the interface rendering effect can be gradually improved.

[0066] Of course, if the cloud server resources allow, the resolution can be further increased to restore a standard or higher quality graphical interface.

[0067] Dynamic element data can include animations, particle effects, etc.

[0068] In some possible implementations, when it's necessary to restore the real-time rendered interface, the degree of rendering restoration can be determined based on the cloud server's performance status. The degree of rendering restoration is positively correlated with the performance status, which is represented by a performance status parameter. When the performance status parameter is greater than or equal to a preset performance parameter threshold, the performance status is considered high, and the degree of rendering restoration is higher; in this case, a higher quality interface can be restored. Conversely, when the performance status parameter is less than the preset performance parameter threshold, the performance status is considered poor, and the degree of rendering restoration is lower; in this case, a lower quality interface can be restored. For example, basic 2D or 3D graphics can be rendered based on virtual frames and rendering information, and the number of vertices can be reduced, replacing complex graphics with black blocks to avoid complex rendering calculations.

[0069] Figure 3 This is a flowchart illustrating the steps of another graphics rendering management method in this application embodiment, referring to... Figure 3 As shown, the above-mentioned graphics rendering management method includes the following steps: S201. When the application is a target application preset for the corresponding cloud account, obtain the running status of the application. The target application includes applications that can stop rendering within the current time period.

[0070] S202. Determine whether the operating status includes the target operating status.

[0071] If the running state includes the target running state, proceed to S203; if the running state does not include the target running state, proceed to S212.

[0072] The target running status includes at least one of the following: background running status, idle status, and automated testing status.

[0073] S203. Determine that the application does not require real-time rendering of the interface.

[0074] S204. Execute logical operations and skip the graphics rendering interface during the application's execution, and obtain the scene complexity of the interface and the performance status of the cloud server, including: memory performance status and processor performance status.

[0075] S205. Obtain the number of cloud accounts running on the cloud server and the priority of the cloud accounts corresponding to the applications.

[0076] S206. Determine the target parameters based on the scenario complexity, performance status, number of cloud accounts, and priority. The target parameters include the richness of virtual frames and the information recording level. The target parameters are negatively correlated with the number of cloud accounts and positively correlated with priority, scenario complexity, and performance status.

[0077] S207. Generate virtual frames of the interface based on the richness level, and record information including the rendering information at the recording level and below. The virtual frames include dynamic element data of the application's interface.

[0078] S208. Obtain the application's behavior data sequence, which includes user behavior data on the application at multiple times.

[0079] S209. Search for the target behavior data sequence that matches the behavior data sequence in the preset behavior database, and obtain the target operation behavior corresponding to the target behavior data sequence in the preset behavior database.

[0080] S210. Predict whether the application needs to restore the real-time rendered interface based on the target operation behavior.

[0081] If the application needs to restore the real-time rendering interface, proceed to S211; otherwise, return to S204.

[0082] S211. Call the graphics rendering interface to render the basic graphic elements in the interface based on the graphics model information, load texture information and material information into the basic graphic elements, and load the dynamic element data in the virtual frame into the interface.

[0083] S212. Determine that the application needs to render the interface in real time, and perform logical operations and graphics rendering interfaces during the running of the application, and return to step S201.

[0084] It should be noted that S201 to S202 described above can be referred to the foregoing embodiments, and will not be repeated here. In addition, the order of S201 to S212 can be flexibly adjusted on the basis of mutual independence, and the embodiments of this application do not limit their order.

[0085] Figure 4 This is a schematic diagram of the structure of a graphics rendering management device according to an embodiment of this application, applied to a cloud server, such as... Figure 3 As shown, the graphics rendering management device 400 may include: The rendering recognition module 401 is used to determine whether the application corresponding to the cloud terminal needs to render the interface in real time.

[0086] The rendering skip module 402 is used to perform logical operations and skip the graphics rendering interface during the running of the application if the application does not need to render the interface in real time, and to generate a virtual frame for the graphics rendering interface and record rendering information, wherein the virtual frame includes dynamic element data of the application's interface.

[0087] The rendering recovery module 403 is used to call the graphics rendering interface to render the application's interface based on the virtual frame and the rendering information when the application needs to restore the real-time rendering interface.

[0088] Optionally, the rendering skip module 402 is also used for: The scene complexity of the interface and the performance status of the cloud server are obtained, including the memory performance status and the processor performance status. Target parameters are determined based on the scene complexity and the cloud server performance status, including the richness of virtual frames and the information recording level, which are positively correlated with the scene complexity and the performance status. Virtual frames of the interface are generated based on the richness, and the information recording level and subsequent rendering information are recorded.

[0089] Optionally, the rendering skip module 402 is also used for: Obtain the number of cloud accounts running on the cloud server and the priority of the cloud account corresponding to the application; determine the target parameter based on the scenario complexity, the performance status, the number of cloud accounts, and the priority, wherein the target parameter is negatively correlated with the number of cloud accounts and positively correlated with the priority.

[0090] Optionally, the rendering information includes: graphics model information, texture information, and material information, and the rendering recovery module 403 is further used for: Render the basic graphic elements in the interface based on the graphic model information; load the texture information and material information into the basic graphic elements; load the dynamic element data in the virtual frame into the interface.

[0091] Optionally, the device further includes: The prediction module is used to acquire the behavior data sequence of the application, which includes user behavior data of the application at multiple times; search for a target behavior data sequence that matches the behavior data sequence from a preset behavior database, and acquire the target operation behavior corresponding to the target behavior data sequence in the preset behavior database; and predict whether the application needs to restore the real-time rendering interface based on the target operation behavior.

[0092] Optionally, the rendering recognition module 401 is further configured to: when the application is a target application preset for the corresponding cloud account, obtain the running status of the application, wherein the target application includes: an application that can stop rendering within the current time period; and when the running status includes a target running status, determine that the application does not need to render the interface in real time, wherein the target running status includes at least one of the following: background running status, idle status, and automated testing status.

[0093] The above embodiments are device embodiments of the foregoing method embodiments, and have the same implementation process and beneficial effects, which will not be repeated here.

[0094] This application also provides a cloud server 900, such as... Figure 5 As shown, it includes a processor 9001, a communication interface 9002, a memory 9003, and a communication bus 9004. The processor 9001, communication interface 9002, and memory 9003 communicate with each other via the communication bus 9004. The memory 9003 is used to store computer programs; the processor 9001 is used to implement the graphics rendering management method provided in the above embodiments when executing the program stored in the memory 9003.

[0095] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0096] The communication interface is used for communication between the aforementioned terminal and other devices.

[0097] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0098] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0099] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform any of the graphics rendering management methods described in the above embodiments.

[0100] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the graphics rendering management methods described in the above embodiments.

[0101] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0102] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0103] It should be noted that the various data-related processes in the embodiments of this application are carried out in compliance with the relevant data protection laws and policies of the country where the location is located, and with the authorization granted by the owner of the corresponding device.

[0104] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0105] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A graphics rendering management method, characterized in that, Applied to cloud servers, the method includes: Determine whether the application corresponding to the cloud terminal needs to render the interface in real time; If the application does not require real-time rendering of the interface, then during the running of the application, logical operations are performed and the graphics rendering interface is skipped, and a virtual frame is generated for the graphics rendering interface and rendering information is recorded. The virtual frame includes dynamic element data of the application's interface. When the application needs to restore the real-time rendered interface, the graphics rendering interface is invoked to render the application's interface based on the virtual frame and the rendering information.

2. The method according to claim 1, characterized in that, Generating virtual frames and recording rendering information for the graphics rendering interface includes: Obtain the scene complexity of the interface and the performance status of the cloud server, the performance status including: memory performance status and processor performance status; The target parameters are determined based on the scene complexity of the interface and the performance status of the cloud server. The target parameters include the richness of virtual frames and the information recording level. The target parameters are positively correlated with the scene complexity and the performance status. The interface virtual frames are generated based on the richness level, and the information recording level and below rendering information are recorded.

3. The method according to claim 2, characterized in that, The target parameters are determined based on the complexity of the interface and the performance status of the cloud server, including: Obtain the number of cloud accounts running on the cloud server and the priority of the cloud account corresponding to the application; The target parameter is determined based on the scenario complexity, the performance status, the number of cloud accounts, and the priority. The target parameter is negatively correlated with the number of cloud accounts and positively correlated with the priority.

4. The method according to claim 1, characterized in that, The rendering information includes: graphics model information, texture information, and material information. Rendering the interface based on the virtual frame and the rendering information includes: Render the basic graphic elements in the interface based on the graphic model information; Load the texture information and material information into the basic graphic element; The dynamic element data in the virtual frame is loaded into the interface.

5. The method according to claim 1, characterized in that, The method further includes: Acquire a sequence of behavioral data from the application, the sequence of behavioral data including user behavior data on the application at multiple times; Search for a target behavior data sequence that matches the behavior data sequence in a preset behavior database, and obtain the target operation behavior corresponding to the target behavior data sequence in the preset behavior database; Predict whether the application needs to restore the real-time rendering interface based on the target operation behavior.

6. The method according to any one of claims 1 to 5, characterized in that, Determining whether the application corresponding to the cloud terminal needs to render the interface in real time includes: When the application is a target application preset for the corresponding cloud account, the running status of the application is obtained, and the target application includes: an application that can stop rendering within the current time period; When the running state includes the target running state, it is determined that the application does not need to render the interface in real time. The target running state includes at least one of the following: background running state, idle state, and automated test state.

7. A graphics rendering management device, characterized in that, The device, applied to a cloud server, includes: The rendering recognition module is used to determine whether the application corresponding to the cloud terminal needs to render the interface in real time. The rendering skip module is used to perform logical operations and skip the graphics rendering interface during the running of the application if the application does not need to render the interface in real time, and to generate virtual frames for the graphics rendering interface and record rendering information. The virtual frames include dynamic element data of the application's interface. The rendering recovery module is used to call the graphics rendering interface to render the application's interface based on the virtual frame and the rendering information when the application needs to restore the real-time rendering interface.

8. A cloud server, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method of any one of claims 1 to 6.

9. A computer-readable storage 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 to 6.

10. A computer program, characterized in that, The computer program is executed by a computer to implement the method as described in any one of claims 1 to 6.

Images