Data rendering method, electronic device, and storage medium

Abstract

This application provides a data rendering method, electronic device, and storage medium. The method includes: acquiring pre-rendered cache data, and displaying a 3D modeling component on a display screen based on the pre-rendered cache data. The 3D modeling component includes a 3D scene interface and multiple controls, including multiple scene switching controls and multiple interactive controls, with the multiple interactive controls embedded in the 3D scene interface; responding to a user's click operation on a target control among the multiple controls, generating a rendering request based on the target control; determining whether target rendering cache data corresponding to the rendering request exists in the pre-rendered cache data; if so, rendering the 3D scene interface based on the target rendering cache data; if not, sending a rendering request to a cloud server and receiving a rendering response from the cloud server, and rendering the 3D scene interface based on the rendering response, thereby improving the data rendering effect.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more particularly to a data rendering method, electronic device, and storage medium. Background Technology

[0002] 3D visualization technology has been widely used in fields such as industrial design, intelligent manufacturing, virtual reality, augmented reality, smart cities, healthcare, education, and digital twins.

[0003] For example, in industrial design, companies can use 3D models to visually display product structures and optimize design processes; in smart manufacturing scenarios, digital twin systems can use 3D visualization to monitor the production line's operating status in real time and assist in decision-making.

[0004] Currently, related 3D visualization technologies are usually based on building models using professional 3D modeling software, generating realistic images through graphics rendering engines, and using physically based rendering techniques to improve visual effects. However, the high computational complexity results in poor data rendering quality. Summary of the Invention

[0005] This application provides a data rendering method, electronic device, and storage medium to solve the problem of poor data rendering results.

[0006] In a first aspect, this application provides a data rendering method applied to a terminal device, the terminal device including a display screen, comprising:

[0007] Obtain pre-rendered cache data and display 3D modeling components on the display screen based on the pre-rendered cache data. The 3D modeling components include a 3D scene interface and multiple controls. The multiple controls include multiple scene switching controls and multiple interactive controls. Multiple interactive controls are embedded in the 3D scene interface.

[0008] In response to a user's click on a target control among multiple controls, a rendering request is generated based on the target control.

[0009] Determine whether the target rendering cache data corresponding to the rendering request exists in the pre-rendered cache data;

[0010] If so, then render the 3D scene interface according to the target rendering cache data;

[0011] If not, a rendering request is sent to the cloud server, and a rendering response is received from the cloud server. Based on the rendering response, the 3D scene interface is rendered.

[0012] In one possible implementation, generating a rendering request based on the target control includes:

[0013] Determine the control type of the target control, which includes scene transition type and interaction type;

[0014] Determine the target parameters based on the control type;

[0015] Generate a rendering request based on the target parameters.

[0016] In one possible implementation, determining the target parameters based on the control type includes:

[0017] When the control type is scene switching, the target parameters include the target scene identifier and the view parameters of the current scene;

[0018] When the control type is interactive, the target parameters include the interactive operation parameters and the view parameters of the current scene.

[0019] In one possible implementation, before retrieving the pre-rendered cache data, the following is included:

[0020] Retrieve at least one historical rendering request within the historical time period;

[0021] Based on at least one historical rendering request, the rendering priority identifier of each region in the 3D scene interface is determined by a semantic segmentation model.

[0022] Update the pre-rendered cache data based on multiple rendering priority indicators.

[0023] Secondly, this application provides a data rendering method applied to a cloud server, comprising:

[0024] Receive rendering requests sent by terminal devices, parse and process the rendering requests to obtain target tasks, which include target parameters;

[0025] Based on the target parameters, determine the target 3D model from multiple preset 3D models;

[0026] Generate rendering data based on the target task and the target 3D model;

[0027] Based on the rendering data, a rendering response is generated and sent to the terminal device.

[0028] In one possible implementation, rendering data is generated based on the target task and the target 3D model, including:

[0029] Based on the target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined by a preset load balancing algorithm.

[0030] Based on the target 3D model, the corresponding node task is executed through at least one target computing node to generate rendering data.

[0031] In one possible implementation, based on target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined using a preset load balancing algorithm, including:

[0032] Real-time monitoring of the load status of multiple preset computing nodes;

[0033] Based on the load status of multiple preset computing nodes, determine at least one target computing node and the allocation ratio of the target task.

[0034] Based on the allocation ratio and target parameters, determine the node tasks corresponding to at least one target computing node.

[0035] In one possible implementation, generating a rendering response based on the rendering data includes:

[0036] Get the current network parameters;

[0037] Based on the current network parameters, determine the target compression algorithm from among several preset compression algorithms;

[0038] Based on the target compression algorithm, the rendering data is compressed to generate a rendering response.

[0039] Thirdly, this application provides a data rendering apparatus for use in a terminal device, the terminal device including a display screen, comprising:

[0040] The display module is used to acquire pre-rendered cache data and display the 3D modeling components on the display screen based on the pre-rendered cache data. The 3D modeling components include a 3D scene interface and multiple controls. The multiple controls include multiple scene switching controls and multiple interactive controls. Multiple interactive controls are embedded in the 3D scene interface.

[0041] The generation module is used to respond to the user's click operation on the target control among multiple controls, and generate a rendering request based on the target control;

[0042] The judgment module is used to determine whether the target rendering cache data corresponding to the rendering request exists in the pre-rendered cache data;

[0043] The first rendering module is used to render the 3D scene interface based on the target rendering cache data if the condition is met.

[0044] The second rendering module is used to send a rendering request to the cloud server if no, and to receive the rendering response from the cloud server, and to render the 3D scene interface according to the rendering response.

[0045] In one possible implementation, the generation module is specifically used for:

[0046] Determine the control type of the target control, which includes scene transition type and interaction type;

[0047] Determine the target parameters based on the control type;

[0048] Generate a rendering request based on the target parameters.

[0049] In one possible implementation, the generation module is specifically used for:

[0050] When the control type is scene switching, the target parameters include the target scene identifier and the view parameters of the current scene;

[0051] When the control type is interactive, the target parameters include the interactive operation parameters and the view parameters of the current scene.

[0052] In one possible implementation, the apparatus further includes an update module, which is used to:

[0053] Retrieve at least one historical rendering request within the historical time period;

[0054] Based on at least one historical rendering request, the rendering priority identifier of each region in the 3D scene interface is determined by a semantic segmentation model.

[0055] Update the pre-rendered cache data based on multiple rendering priority indicators.

[0056] Fourthly, this application provides a data rendering apparatus for use on a cloud server, comprising:

[0057] The parsing module is used to receive rendering requests sent by the terminal device, parse and process the rendering requests to obtain the target task, which includes target parameters.

[0058] The determination module is used to determine the target 3D model from multiple preset 3D models based on the target parameters;

[0059] The generation module is used to generate rendering data based on the target task and the target 3D model;

[0060] The generation module is also used to generate a rendering response based on the rendering data and send the rendering response to the terminal device.

[0061] In one possible implementation, the generation module is specifically used for:

[0062] Based on the target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined by a preset load balancing algorithm.

[0063] Based on the target 3D model, the corresponding node task is executed through at least one target computing node to generate rendering data.

[0064] In one possible implementation, the generation module is specifically used for:

[0065] Real-time monitoring of the load status of multiple preset computing nodes;

[0066] Based on the load status of multiple preset computing nodes, determine at least one target computing node and the allocation ratio of the target task.

[0067] Based on the allocation ratio and target parameters, determine the node tasks corresponding to at least one target computing node.

[0068] In one possible implementation, the generation module is specifically used for:

[0069] Get the current network parameters;

[0070] Based on the current network parameters, determine the target compression algorithm from among several preset compression algorithms;

[0071] Based on the target compression algorithm, the rendering data is compressed to generate a rendering response.

[0072] Fifthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0073] The memory stores the instructions that the computer executes;

[0074] The processor executes computer-executable instructions stored in memory to implement any of the methods of the first aspect.

[0075] Sixthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0076] The memory stores the instructions that the computer executes;

[0077] The processor executes computer-executable instructions stored in memory to implement any of the methods in the second aspect.

[0078] In a seventh aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any of the first aspects.

[0079] Eighthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any of the second aspects.

[0080] Ninthly, this application provides a computer program product, including a computer program that, when executed by a computer, implements the method as described in any of the first aspects.

[0081] In a tenth aspect, this application provides a computer program product, including a computer program that, when executed by a computer, implements the method as described in any of the second aspects.

[0082] This application provides a data rendering method, electronic device, and storage medium. By acquiring pre-rendered cache data and displaying a 3D modeling component on a screen based on the pre-rendered cache data, the 3D modeling component includes a 3D scene interface and multiple controls, including multiple scene switching controls and multiple interactive controls. Multiple interactive controls are embedded in the 3D scene interface. In response to a user's click on a target control among the multiple controls, a rendering request is generated based on the target control. It is determined whether the pre-rendered cache data contains the target rendering cache data corresponding to the rendering request. If so, the 3D scene interface is rendered based on the target rendering cache data; otherwise, a rendering request is sent to a cloud server, and a rendering response is received from the cloud server. Based on the rendering response, the 3D scene interface is rendered. This collaborative approach, prioritizing local pre-rendered cache rendering and supplementing rendering with cloud computing power, improves the interactive response speed of the 3D modeling component and the user experience, expands the coverage of the rendered scene, reduces the real-time rendering computing load on the terminal device, and enhances the data rendering effect. Attached Figure Description

[0083] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0084] Figure 1 This application provides a schematic diagram of a data rendering system architecture.

[0085] Figure 2 A flowchart illustrating a data rendering method provided in an embodiment of this application;

[0086] Figure 3 A schematic diagram of an interactive interface provided in an embodiment of this application;

[0087] Figure 4 A flowchart illustrating another data rendering method provided in an embodiment of this application;

[0088] Figure 5 A flowchart illustrating yet another data rendering method provided in an embodiment of this application;

[0089] Figure 6This is a schematic diagram of the structure of a data rendering apparatus provided in an embodiment of this application;

[0090] Figure 7 This is a schematic diagram of another data rendering apparatus provided in an embodiment of this application;

[0091] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0092] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0093] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0094] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0095] It should be noted that the data rendering method, electronic device and storage medium provided in this application can be used in the field of data processing, or in any field other than data processing. The application field of the data rendering method, electronic device and storage medium in this application is not limited.

[0096] 3D visualization technology has been widely used in fields such as industrial design, intelligent manufacturing, virtual reality, augmented reality, smart cities, healthcare, education, and digital twins.

[0097] For example, in industrial design, companies can use 3D models to visually display product structures and optimize design processes; in smart manufacturing scenarios, digital twin systems can use 3D visualization to monitor the production line's operating status in real time and assist in decision-making.

[0098] Currently, related 3D visualization technologies are usually based on building models using professional 3D modeling software, generating realistic images through graphics rendering engines, and using physically based rendering techniques to improve visual effects. However, the high computational complexity results in poor data rendering quality.

[0099] To address the aforementioned technical issues, this application provides a data rendering method. By prioritizing the loading of pre-rendered cached data, a 3D modeling component, including a 3D scene interface, embedded interactive controls, and scene switching controls, is first presented on the terminal display screen. When a user clicks on a target control to trigger a rendering request, the method first checks whether the corresponding target data exists in the pre-rendered cache. If it exists, the cache is directly called to complete the rendering of the 3D scene interface; otherwise, a rendering request is sent to the cloud server, and the interface rendering is completed based on the response returned by the cloud server. This approach balances rendering efficiency and scene coverage integrity, improves the interactive response speed of the terminal's 3D modeling component and the user's operating experience, and enhances the data rendering effect.

[0100] Below, in conjunction with Figure 1 The architecture of the data rendering system will be explained.

[0101] Figure 1 This is a schematic diagram of a data rendering system architecture provided in an embodiment of this application. Please refer to [link / reference]. Figure 1 , Figure 1 It may include at least one terminal device and a cloud server, with the terminal device and the cloud server establishing a data transmission connection through a communication network.

[0102] Terminal devices can be used to provide users with a platform for displaying and interacting with 3D modeling components.

[0103] The terminal device may be equipped with a display screen.

[0104] The display screen can be used to present 3D modeling components, which include a 3D scene interface and multiple controls. The multiple controls are divided into multiple scene switching controls and multiple interactive controls, and the multiple interactive controls are embedded in the 3D scene interface to achieve integrated display of controls and scene.

[0105] Cloud servers can be used to provide rendering support for terminal devices.

[0106] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0107] Figure 2This is a flowchart illustrating a data rendering method provided in an embodiment of this application. The execution entity in this embodiment can be a terminal device or the processor of the terminal device. The processor can be implemented in software or a combination of software and hardware. The terminal device includes a display screen. Please refer to... Figure 2 The method includes:

[0108] S201. Obtain pre-rendered cache data and display the 3D modeling components on the display screen based on the pre-rendered cache data.

[0109] The 3D modeling components include a 3D scene interface and multiple controls.

[0110] The multiple controls include multiple scene switching controls and multiple interactive controls.

[0111] Multiple interactive controls are embedded in the 3D scene interface.

[0112] Pre-rendered cache data can refer to the basic data for rendering a 3D scene that is stored locally on the terminal device in advance.

[0113] Pre-rendered cache data can include basic display data of 3D modeling components, rendering data corresponding to high-frequency interactive scenes, etc.

[0114] 3D modeling components can be 3D visual interactive carriers displayed on the terminal device screen.

[0115] A 3D scene interface can be a visual scene carrier for 3D modeling components.

[0116] Scene switching controls are controls that allow users to switch between different 3D scenes.

[0117] Interactive controls can be embedded within the 3D scene interface to enable user interaction with the 3D model / scene, such as controls for scaling and rotating the model.

[0118] Interactive controls enable the integration of controls and scenes, ensuring a clean interface while improving user convenience, allowing users to perform related operations directly in the 3D scene through interactive controls.

[0119] The terminal device can read the cached data pre-stored in the local pre-rendering cache module, perform the pre-rendering cache data acquisition operation, and complete the initial display of the 3D modeling component on the display screen based on the data.

[0120] Optionally, before obtaining the pre-rendered cache data, the process includes: obtaining at least one historical rendering request within a historical time period; determining the rendering priority identifier of each region in the 3D scene interface based on the at least one historical rendering request using a semantic segmentation model; and updating the pre-rendered cache data based on multiple rendering priority identifiers.

[0121] In this way, based on users' historical operating habits, scene rendering priorities are divided through models, thereby dynamically updating local cache data, improving the local hit rate of subsequent rendering requests, and reducing the frequency of cloud interactions.

[0122] S202. In response to the user's click operation on the target control among multiple controls, generate a rendering request based on the target control.

[0123] A rendering request can be a demand instruction generated by the terminal device in response to a user control click operation.

[0124] A rendering request may include information such as the rendering scene type, interaction parameters, and display resolution.

[0125] Rendering requests can be used to trigger rendering calculations locally or in the cloud.

[0126] When a user clicks on a target control among multiple controls, the corresponding rendering requirements can be parsed based on the type of the target control and the specific instruction triggered by the click, and a matching rendering request can be generated.

[0127] For example, if the target control is a scene switching control for "scene switching to device monitoring", the rendering request will include core information such as the rendering parameters and display precision of "device monitoring"; if the target control is an interactive control for "model scaling" in a 3D scene, the rendering request will include rendering-related parameters such as "scaling ratio" and "scaling area".

[0128] Optionally, a rendering request can be generated based on the target control in the following way: determine the control type of the target control, including scene switching type and interaction type; determine the target parameters based on the control type; and generate a rendering request based on the target parameters.

[0129] The scene switching type control is used to switch the overall display scene of the 3D modeling component, while the interactive type control is used to perform operations on the model or element in the current 3D scene.

[0130] Optionally, the target parameters can be determined based on the control type in the following ways: if the control type is a scene switching type, the target parameters include the target scene identifier and the current scene's view parameters; if the control type is an interactive type, the target parameters include the interactive operation parameters and the current scene's view parameters.

[0131] If the target control is a scene switching type, the target parameters include the unique identifier of the target scene, the scene display accuracy requirements, and the scene loading priority.

[0132] If the target control is interactive, the target parameters include the interactive operation instructions, the identifier of the target operation model, and the parameter values ​​of the interactive operation.

[0133] For example, interactive operation commands could include scaling, rotating, and modifying the color of the model.

[0134] S203. Determine whether the target rendering cache data corresponding to the rendering request exists in the pre-rendering cache data.

[0135] After receiving the rendering request, the rendering processing module of the terminal device immediately performs a cache matching judgment operation, extracts the target parameters in the rendering request, compares them with the parameters corresponding to each cached data stored in the pre-rendered cache data, and verifies whether there is target rendering cache data whose parameters completely match or meet the rendering requirements.

[0136] The core purpose of this judgment step is to prioritize the use of local cache resources, avoid unnecessary cloud interactions, and improve rendering response speed.

[0137] S204. If so, then render the 3D scene interface according to the target rendering cache data.

[0138] If the rendering processing module determines that the target rendering cache data exists in the pre-rendering cache data, i.e. the cache is hit, there is no need to interact with the cloud server. The target rendering cache data is directly called and the 3D scene interface is quickly rendered through the local rendering engine of the terminal.

[0139] This process can minimize rendering wait time, ensure that the interface can provide immediate feedback after user operation, and significantly improve the user interaction experience, especially suitable for high-frequency rendering scenarios.

[0140] S205. If not, send a rendering request to the cloud server and receive the rendering response from the cloud server. Based on the rendering response, render the 3D scene interface.

[0141] A rendering response can be feedback information containing target rendering data generated by the cloud server after receiving a rendering request and performing rendering calculations.

[0142] Rendering response can be used to support terminal devices in rendering 3D scene interfaces in scenarios where the cache is not hit.

[0143] If the rendering processing module determines that the target rendering cache data is not present in the pre-rendering cache data, i.e., a cache miss, the terminal device can send the above rendering request to the cloud server through the communication network. After receiving the rendering request, the cloud server parses the request parameters through its built-in rendering calculation module, performs the corresponding 3D scene rendering calculation, generates a rendering response containing the target rendering effect data, and then feeds the rendering response back to the terminal device through the communication network. After receiving the rendering response, the terminal device extracts the rendering data and renders the 3D scene interface through its local rendering engine.

[0144] This process leverages the powerful computing capabilities of the cloud to cover low-frequency, complex rendering scenarios not covered by local caching, ensuring the integrity of the rendering function and avoiding rendering failures caused by limitations in local computing power or caching on the terminal.

[0145] Below, in conjunction with Figure 3 Let's take the process of a user switching scenes as an example to illustrate this.

[0146] Figure 3 This is a schematic diagram of an interactive interface provided in an embodiment of this application. Please refer to [link / reference]. Figure 3 , Figure 3 Includes Interface 1 and Interface 2.

[0147] In Interface 1, a 3D modeling component is displayed on the screen. This component includes a 3D scene interface and multiple controls. These controls can be positioned at the bottom of the 3D scene interface.

[0148] Multiple controls may include equipment monitoring controls, environmental monitoring controls, fire monitoring controls, video monitoring controls, personnel access control controls, and vehicle access controls.

[0149] Multiple interactive controls are embedded in the 3D scene interface, such as the areas corresponding to each factory building.

[0150] The display screen also includes multiple two-dimensional display components, which can be associated with the three-dimensional scene interface.

[0151] Different 3D scene interfaces can correspond to multiple different 2D display components.

[0152] For example, the current 3D scene interface may include components such as production efficiency, meteorological data, power generation trend, inverter status analysis, alarm statistics, today's forecast, zone real-time power, power plant operation and maintenance statistics, inspection and maintenance plan, and environmental contribution.

[0153] If a user clicks on the device monitoring control, a rendering request is generated based on the device monitoring control. It is then determined whether the target rendering cache data corresponding to the rendering request exists in the pre-rendering cache data. If so, the 3D scene interface is rendered based on the target rendering cache data. If not, a rendering request is sent to the cloud server, and a rendering response is received from the cloud server. Based on the rendering response, the 3D scene interface is rendered.

[0154] After rendering the 3D scene interface, please refer to Interface 2.

[0155] Interface 2 displays the 3D scene interface corresponding to the device monitoring controls.

[0156] This embodiment provides a data rendering method that acquires pre-rendered cache data and displays a 3D modeling component on a screen based on the pre-rendered cache data. The 3D modeling component includes a 3D scene interface and multiple controls, including multiple scene switching controls and multiple interactive controls. Multiple interactive controls are embedded in the 3D scene interface. In response to a user's click operation on a target control among the multiple controls, a rendering request is generated based on the target control. It is determined whether the target rendering cache data corresponding to the rendering request exists in the pre-rendered cache data. If so, the 3D scene interface is rendered based on the target rendering cache data. If not, a rendering request is sent to a cloud server, and a rendering response is received from the cloud server. Based on the rendering response, the 3D scene interface is rendered. In this way, by using a collaborative approach of prioritizing local pre-rendered cache rendering and supplementing rendering with cloud computing power, the interactive response speed of the 3D modeling component and the user operation experience are improved, the coverage of the rendered scene is expanded, and the real-time rendering computing power load of the terminal device is reduced, thereby improving the data rendering effect.

[0157] Figure 4 This is a flowchart illustrating another data rendering method provided in an embodiment of this application. The execution entity in this embodiment can be a cloud server. The cloud server can be implemented through software or a combination of software and hardware. Please refer to... Figure 4 The method includes:

[0158] S401: Receive the rendering request sent by the terminal device, parse and process the rendering request, and obtain the target task.

[0159] The target task includes target parameters.

[0160] The specific content of the target parameters is related to the type of the target control on the terminal side.

[0161] If the target control is a scene switching type, the target parameters include the target scene identifier, scene loading precision, etc.; if the target control is an interactive type, the target parameters include interactive operation instructions, target model identifier, operation parameter values, etc.

[0162] The cloud server can listen for and receive rendering requests sent by terminal devices in real time through its built-in rendering request receiving module. The rendering request receiving module performs parsing processing on the requests, including but not limited to core information such as the identifier of the requesting terminal, the type of rendering scene, interactive operation instructions, and display precision requirements. By extracting and integrating the above information, the target task corresponding to the rendering request is obtained.

[0163] S402. Based on the target parameters, determine the target 3D model from multiple preset 3D models.

[0164] Multiple preset 3D models can cover different application scenarios and different levels of precision 3D basic models, and each preset 3D model is equipped with a unique model identifier, scene attribute label and parameter feature library.

[0165] The cloud server can read the target parameters in the target task, match the target parameters with the parameter feature library of each preset 3D model, and filter out the 3D models that match the scene attributes, model identifiers, accuracy requirements, etc. of the target parameters, and identify them as the target 3D model.

[0166] S403. Generate rendering data based on the target task and the target 3D model.

[0167] The cloud server can use the target task as an execution guide and perform targeted rendering calculations based on the target 3D model. If the target task is scene switching, the rendering calculations include loading texture maps of the target 3D model, configuring scene environment parameters, and rendering lighting effects. If the target task is model interaction, the rendering calculations include adjusting the topology of the target 3D model, optimizing local details, and transforming the form corresponding to the interaction.

[0168] S404. Generate a rendering response based on the rendering data and send the rendering response to the terminal device.

[0169] Cloud servers can encapsulate rendering data according to preset communication protocols to generate standardized rendering responses.

[0170] The encapsulated content of the rendering response can include the rendering data body, data checksum, response identifier, etc. Among them, the data checksum can be used by the terminal device to verify the integrity of the received data and avoid data loss or errors during transmission.

[0171] The rendering response can be sent back to the requesting terminal device via a communication network. After receiving the response, the terminal device can extract the rendering data to complete the rendering of the 3D scene interface.

[0172] Alternatively, a rendering response can be generated based on the rendering data in the following manner: obtaining the current network parameters; determining the target compression algorithm from multiple preset compression algorithms based on the current network parameters; and compressing the rendering data according to the target compression algorithm to generate a rendering response.

[0173] After generating rendering data and before packaging the rendering response, the cloud server will first detect the current communication link status between itself and the terminal device that initiated the request. The current network parameters obtained include, but are not limited to, network bandwidth, data transmission latency, link stability, packet loss rate, and other indicators.

[0174] Multiple preset compression algorithms can include lossless compression algorithms, lossy compression algorithms, and adaptive hybrid compression algorithms.

[0175] Lossless compression algorithms are suitable for scenarios with sufficient network bandwidth and low latency. The compressed data can completely restore the original rendering data without any loss of precision.

[0176] Lossy compression algorithms are suitable for scenarios with low network bandwidth, high latency, or unstable links, achieving high compression ratios and significantly reducing data size.

[0177] The adaptive hybrid compression algorithm can be applied to scenarios with fluctuating network conditions and can dynamically adjust the ratio of lossless / lossy compression.

[0178] In this way, by using a network-state adaptive rendering data compression strategy, the problems of large 3D rendering data size and susceptibility to network bandwidth and stability issues during direct transmission are solved, further improving the efficiency of terminal receiving rendering data and user experience.

[0179] The implementation details of each step in this application embodiment can be found in the description of the corresponding steps or operations in the above method embodiments; repeated content will not be repeated.

[0180] This embodiment provides a data rendering method that receives rendering requests sent by a terminal device, parses and processes the requests to obtain a target task, which includes target parameters. Based on the target parameters, a target 3D model is determined from multiple preset 3D models. Rendering data is generated based on the target task and the target 3D model. A rendering response is generated based on the rendering data and sent to the terminal device. In this way, by using a cloud server to handle rendering requests that are not cached by the terminal device, and relying on cloud computing power to complete target model matching and rendering data generation and feedback, the method effectively compensates for the limitations of local caching and computing power on the terminal. It covers low-frequency and complex rendering scenarios, avoids rendering failures on the terminal side, ensures the functional integrity of the entire data rendering method and the consistency of user interaction experience, and improves the data rendering effect.

[0181] Below, in conjunction with Figure 5 The process of generating rendering data based on the target task and the target 3D model is explained.

[0182] Figure 5 This is a flowchart illustrating another data rendering method provided in an embodiment of this application. Based on the above embodiments, please refer to... Figure 5 .

[0183] S501: Real-time monitoring of the load status of multiple preset computing nodes.

[0184] The cloud server can be deployed with multiple pre-set computing nodes, each with independent computing resources, for parallel execution of sub-tasks of 3D scene rendering.

[0185] The built-in node scheduling module in the cloud monitors the load status of all preset computing nodes in real time.

[0186] The monitored metrics include, but are not limited to: CPU utilization, memory usage, GPU computing power utilization, current queue length of pending tasks, and task execution latency of computing nodes.

[0187] The monitoring data is updated at preset time intervals to ensure that the node scheduling module can accurately grasp the real-time computing power idle status of each computing node.

[0188] S502. Based on the load status of multiple preset computing nodes, determine at least one target computing node and the allocation ratio of the target task.

[0189] Based on the real-time monitoring of the load status of each preset computing node, node filtering and task allocation ratio determination operations can be performed.

[0190] The node filtering operation can select computing nodes with low load status as target computing nodes.

[0191] The task allocation ratio determination operation can be based on the availability of computing power of the target computing nodes to determine the allocation ratio of the target tasks among the target computing nodes.

[0192] The higher the idle computing power of a node, the higher the proportion of tasks it is assigned.

[0193] For example, if node A has an idle computing power of 80% and node B has an idle computing power of 40%, the task allocation ratio can be set so that node A undertakes 2 / 3 of the task and node B undertakes 1 / 3 of the task.

[0194] S503. Based on the allocation ratio and target parameters, determine the node tasks corresponding to at least one target computing node.

[0195] Based on the task allocation ratio and target parameters, the target task can be split into multiple node tasks that can be executed in parallel, and a corresponding node task can be assigned to each target computing node.

[0196] For example, the target task can be broken down into sub-tasks such as model topology calculation task, texture mapping and rendering task, lighting and shadow effect calculation task, and detail optimization task; then, according to the allocation ratio, different sub-tasks or different data fragments of the same sub-task are allocated to the corresponding target computing nodes to ensure that the workload of each node matches the idle level of computing power.

[0197] S504. Based on the target 3D model, execute the corresponding node task through at least one target computing node to generate rendering data.

[0198] After receiving the assigned node task, each target computing node can use the target 3D model as the processing object and execute the corresponding computing operations in parallel. After completing the node task, each target computing node feeds back the computing results to the result aggregation module of the cloud server. The aggregation module integrates and verifies the computing results of each node, eliminates data redundancy and conflicts between nodes, and generates rendering data.

[0199] For example, the node responsible for calculating the model's topology performs detailed calculations on the vertices, face count, and geometry of the target 3D model; the node responsible for texture mapping and rendering matches the corresponding material textures to the target 3D model and completes the texture mapping; and the node responsible for calculating lighting and shadow effects generates the model's lighting and shadow rendering effects based on information such as the light source position and light intensity in the target parameters.

[0200] The implementation details of each step in this application embodiment can be found in the description of the corresponding steps or operations in the above method embodiments; repeated content will not be repeated.

[0201] This embodiment provides a data rendering method that monitors the load status of multiple preset computing nodes in real time. Based on the load status of these nodes, it determines at least one target computing node and the allocation ratio of target tasks. According to the allocation ratio and target parameters, it determines the node tasks corresponding to each target computing node. Based on the target 3D model, the corresponding node tasks are executed by the at least one target computing node to generate rendering data. This multi-node parallel processing significantly improves the processing efficiency of complex rendering tasks, shortens cloud response time, and avoids task lag caused by single-node overload, ensuring the stability and efficiency of the entire data rendering method.

[0202] Figure 6 This is a schematic diagram of a data rendering apparatus provided in an embodiment of this application. Please refer to... Figure 6 The data rendering device 600 includes a display module 601, a generation module 602, a judgment module 603, a first rendering module 604, and a second rendering module 605.

[0203] Display module 601 is used to acquire pre-rendered cache data and display 3D modeling components on the display screen based on the pre-rendered cache data. The 3D modeling components include a 3D scene interface and multiple controls. The multiple controls include multiple scene switching controls and multiple interactive controls. Multiple interactive controls are embedded in the 3D scene interface.

[0204] The generation module 602 is used to respond to the user's click operation on the target control among multiple controls and generate a rendering request based on the target control;

[0205] The judgment module 603 is used to determine whether the target rendering cache data corresponding to the rendering request exists in the pre-rendering cache data;

[0206] The first rendering module 604 is used to render the 3D scene interface according to the target rendering cache data if the condition is met.

[0207] The second rendering module 605 is used to send a rendering request to the cloud server if no, and to receive the rendering response sent by the cloud server, and to render the 3D scene interface according to the rendering response.

[0208] In one possible implementation, the generation module 602 is specifically used for:

[0209] Determine the control type of the target control, which includes scene transition type and interaction type;

[0210] Determine the target parameters based on the control type;

[0211] Generate a rendering request based on the target parameters.

[0212] In one possible implementation, the generation module 602 is specifically used for:

[0213] When the control type is scene switching, the target parameters include the target scene identifier and the view parameters of the current scene;

[0214] When the control type is interactive, the target parameters include the interactive operation parameters and the view parameters of the current scene.

[0215] In one possible implementation, the device further includes an update module 606, which is configured to:

[0216] Retrieve at least one historical rendering request within the historical time period;

[0217] Based on at least one historical rendering request, the rendering priority identifier of each region in the 3D scene interface is determined by a semantic segmentation model.

[0218] Update the pre-rendered cache data based on multiple rendering priority indicators.

[0219] Figure 7 This is a schematic diagram of another data rendering apparatus provided in an embodiment of this application. Please refer to... Figure 7 The data rendering device 700 includes a parsing module 701, a determining module 702, and a generating module 703.

[0220] The parsing module 701 is used to receive the rendering request sent by the terminal device, and to parse and process the rendering request to obtain the target task, which includes target parameters.

[0221] The determination module 702 is used to determine the target 3D model from multiple preset 3D models based on the target parameters;

[0222] The generation module 703 is used to generate rendering data based on the target task and the target 3D model;

[0223] The generation module 703 is also used to generate a rendering response based on the rendering data and send the rendering response to the terminal device.

[0224] In one possible implementation, the generation module 703 is specifically used for:

[0225] Based on the target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined by a preset load balancing algorithm.

[0226] Based on the target 3D model, the corresponding node task is executed through at least one target computing node to generate rendering data.

[0227] In one possible implementation, the generation module 703 is specifically used for:

[0228] Real-time monitoring of the load status of multiple preset computing nodes;

[0229] Based on the load status of multiple preset computing nodes, determine at least one target computing node and the allocation ratio of the target task.

[0230] Based on the allocation ratio and target parameters, determine the node tasks corresponding to at least one target computing node.

[0231] In one possible implementation, the generation module 703 is specifically used for:

[0232] Get the current network parameters;

[0233] Based on the current network parameters, determine the target compression algorithm from among several preset compression algorithms;

[0234] Based on the target compression algorithm, the rendering data is compressed to generate a rendering response.

[0235] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Please refer to... Figure 8 The electronic device 800 may include: a memory 801, a processor 802, and a transceiver 803.

[0236] Memory 801 is used to store program instructions;

[0237] The processor 802 is used to execute the program instructions stored in the memory so that the electronic device 800 performs the above-described method.

[0238] Transceiver 803 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter port, or transmitter interface, and the receiver may also be referred to as a receiver port, receiver interface, or similar descriptions. Exemplarily, memory 801, processor 802, and transceiver 803 are interconnected via bus 804.

[0239] This application also provides a computer program product that can be executed by a processor, and when the computer program product is executed, the above-described method can be implemented.

[0240] The data rendering apparatus, electronic device, computer-readable storage medium, and computer program product of the embodiments of this application can execute the technical solutions shown in the above method embodiments. Their implementation principles and beneficial effects are similar, and will not be repeated here.

[0241] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0242] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0243] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0244] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0245] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0246] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0247] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0248] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0249] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A data rendering method, characterized in that, Applied to a terminal device, the terminal device including a display screen, the method includes: Acquire pre-rendered cache data and display a 3D modeling component on the display screen based on the pre-rendered cache data. The 3D modeling component includes a 3D scene interface and multiple controls. The multiple controls include multiple scene switching controls and multiple interactive controls. The multiple interactive controls are embedded in the 3D scene interface. In response to a user's click on a target control among the plurality of controls, a rendering request is generated based on the target control; Determine whether the target rendering cache data corresponding to the rendering request exists in the pre-rendered cache data; If so, then the 3D scene interface is rendered according to the target rendering cache data; If not, the rendering request is sent to the cloud server, and the rendering response sent by the cloud server is received. Based on the rendering response, the interface of the 3D scene is rendered.

2. The method according to claim 1, characterized in that, Based on the target control, a rendering request is generated, including: Determine the control type of the target control, whereby the control type includes scene switching type and interaction type; Determine the target parameters based on the control type; A rendering request is generated based on the target parameters.

3. The method according to claim 2, characterized in that, Based on the control type, the target parameters are determined, including: When the control type is a scene switching type, the target parameters are determined to include the target scene identifier and the view parameters of the current scene; When the control type is interactive, the target parameters are determined to include interactive operation parameters and the viewpoint parameters of the current scene.

4. The method according to claim 2, characterized in that, Before retrieving pre-rendered cache data, the following is included: Retrieve at least one historical rendering request within the historical time period; Based on the at least one historical rendering request, the rendering priority identifier of each region in the 3D scene interface is determined by a semantic segmentation model. The pre-rendered cache data is updated based on multiple rendering priority identifiers.

5. A data rendering method, characterized in that, Applied to a cloud server, the method includes: Receive a rendering request sent by a terminal device, and parse the rendering request to obtain a target task, wherein the target task includes target parameters; Based on the target parameters, a target 3D model is determined from multiple preset 3D models; Rendering data is generated based on the target task and the target 3D model; Based on the rendering data, a rendering response is generated and sent to the terminal device.

6. The method according to claim 5, characterized in that, Based on the target task and the target 3D model, generate rendering data, including: Based on the target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined by a preset load balancing algorithm. Based on the target 3D model, corresponding node tasks are executed through at least one target computing node to generate rendering data.

7. The method according to claim 6, characterized in that, Based on the target parameters, at least one target computing node and the node tasks corresponding to each target computing node are determined using a preset load balancing algorithm, including: Real-time monitoring of the load status of multiple preset computing nodes; Based on the load status of the multiple preset computing nodes, determine at least one target computing node and the allocation ratio of the target task; Based on the allocation ratio and the target parameters, determine the node tasks corresponding to the at least one target computing node.

8. The method according to any one of claims 5-7, characterized in that, Based on the rendering data, a rendering response is generated, including: Get the current network parameters; Based on the current network parameters, a target compression algorithm is determined from multiple preset compression algorithms; The rendering data is compressed according to the target compression algorithm to generate a rendering response.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as claimed in any one of claims 1 to 4 or the method as claimed in any one of claims 5 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 4 or the method as described in any one of claims 5 to 8.

Images