Cloud rendering package deployment method, remote server, client, and storage medium

By generating and deploying mirror files on the client and updating the configuration files of the cloud rendering package on the remote server, the problem of fixed functions in existing cloud rendering technologies is solved, and the flexibility and efficiency of cloud rendering are achieved.

CN119987793BActive Publication Date: 2025-06-27SHENZHEN SMARTCITY TECH DEV GRP CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202510451951.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-04-11
Publication Date
2025-06-27
Estimated Expiration
2045-04-11

AI Technical Summary

Technical Problem

In the existing cloud rendering technology, the functions of the cloud service interface are fixed, making it difficult for users to adjust the rendering parameters according to actual needs, resulting in poor flexibility in cloud rendering.

Method used

The mirror file is generated by the client in response to the configuration operation of the renderer and sent to a remote server for container deployment. The remote server receives cloud rendering packages, updates its configuration files, and deploys the updated cloud rendering packages, so that it can directly call the rendering program in the image file to handle rendering tasks.

Benefits of technology

It realizes custom configuration and flexible combination of rendering programs, improves the flexibility of cloud rendering, simplifies the deployment process, and improves the efficient execution of rendering tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119987793B_ABST
    Figure CN119987793B_ABST
Patent Text Reader

Abstract

The present application discloses a method for deploying a cloud rendering package, a remote server, a client, and a storage medium, relating to the technical field of cloud rendering, including: receiving a mirror file sent by a client and deploying the mirror file through a container, wherein the mirror file is generated by the client in response to a configuration operation for a rendering program; receiving a cloud rendering package sent by the client and updating the configuration file of the cloud rendering package, and deploying the updated cloud rendering package; receiving a rendering task through the deployed cloud rendering package, and invoking a rendering program in the mirror file to process the rendering task, wherein the rendering task is generated by the client in response to a configuration operation for a front-end interface corresponding to the rendering program. By uploading the cloud rendering package to the remote server, the present application can directly invoke relevant interfaces of the rendering program in the mirror file, and freely combine and invoke relevant interfaces through the cloud rendering package, realizing custom rendering and improving the flexibility of cloud rendering.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of cloud rendering technology, and particularly to a cloud rendering package deployment method, a remote server, a client, and a storage medium. Background Art

[0002] With the rapid development of cloud computing technology, the ways of software development and deployment are also constantly evolving. Many application programs have started to migrate some or all of their functions to the cloud to achieve advantages such as elastic expansion and resource optimization.

[0003] Currently, 3D scene rendering methods usually rely on cloud servers. Through the predefined cloud service interfaces of cloud servers, communication between the client and the cloud server is realized, so as to achieve the loading, rendering, and interaction of the scene. However, the encapsulation of the access interface for the rendering program deployed on the cloud server in the cloud service interface of the cloud server is fixed, and the functions that the cloud service interface can provide are also fixed, resulting in difficulty for users to adjust rendering parameters according to actual needs to achieve custom rendering, and the flexibility of cloud rendering is poor. Summary of the Invention

[0004] The main purpose of this application is to provide a cloud rendering package deployment method, a remote server, a client, and a storage medium, aiming to solve the technical problem of how to improve the flexibility of cloud rendering.

[0005] To achieve the above purpose, this application proposes a cloud rendering package deployment method. The cloud rendering package deployment method is applied to a remote server deployed with containers, and the method includes:

[0006] Receiving a mirror file sent by a client, and deploying the mirror file through a container, where the mirror file is generated by the client in response to a configuration operation for a rendering program;

[0007] Receiving a cloud rendering package sent by the client, updating the configuration file of the cloud rendering package, and deploying the updated cloud rendering package;

[0008] Receiving a rendering task through the deployed cloud rendering package, and invoking the rendering program in the mirror file to process the rendering task, where the rendering task is generated by the client in response to a configuration operation for the front-end interface corresponding to the rendering program.

[0009] In an embodiment, the step of updating the configuration file of the cloud rendering package includes:

[0010] Determining the Internet Protocol (IP) address of the remote server as the IP address in the configuration file, and determining the access port of the mirror file as the port in the configuration file, where the access port is the port of the container.

[0011] In one embodiment, the step of updating the configuration file of the cloud rendering package includes:

[0012] In response to a configuration operation on the useOneByOne field, which is a field processed one by one in the configuration file, adjust the concurrent access support capability of the cloud rendering package.

[0013] In one embodiment, after the step of deploying the updated cloud rendering package, the following steps are further included:

[0014] In response to a trigger operation on the startup script of the cloud rendering package, detect the access path of the configuration file;

[0015] In the case where the access path exists, determine the environment variables of the remote server as the environment variables of the configuration file to obtain a target configuration file;

[0016] Start the cloud rendering package according to the target configuration file.

[0017] To achieve the above object, the present application proposes a method for deploying a cloud rendering package. The method for deploying the cloud rendering package is applied to a client, and the method includes:

[0018] In response to a configuration operation on the rendering program, generate an image file and send the image file to a remote server so that the remote server deploys the image file through a container;

[0019] Send a preset cloud rendering package to the remote server so that the remote server updates the configuration file of the cloud rendering package and deploys the updated cloud rendering package;

[0020] Display the front-end interface corresponding to the rendering program;

[0021] In response to a configuration operation on the front-end interface, generate a rendering task and send the rendering task to the cloud rendering package deployed on the remote server so that the deployed cloud rendering package invokes the rendering program in the image file to process the rendering task.

[0022] In one embodiment, the step of generating an image file in response to a configuration operation on the rendering program includes:

[0023] In response to a configuration operation on the rendering program, compile the source code corresponding to the rendering program to obtain an executable file of the source code, and generate an image file including the executable file and the running dependencies of the executable file, where the running dependencies of the executable file are the resources required for the executable file to run.

[0024] In one embodiment, the step of generating an image file in response to a configuration operation for a rendering program includes:

[0025] In the case where the rendering program is built based on a Web3D engine, in response to a configuration operation for the rendering program, an image file including the Web3D engine and the running dependencies of the Web3D engine is generated, where the running dependencies of the Web3D engine are the resources required for the Web3D engine to run.

[0026] In addition, to achieve the above object, the present application also proposes a cloud rendering package deployment device, which is applied to a remote server. The device includes:

[0027] A deployment module, configured to receive the image file sent by the client and deploy the image file through a container, where the image file is generated by the client in response to a configuration operation for the rendering program;

[0028] An update module, configured to receive the cloud rendering package sent by the client, update the configuration file of the cloud rendering package, and deploy the updated cloud rendering package;

[0029] An invocation module, configured to receive a rendering task through the deployed cloud rendering package, and invoke the rendering program in the image file to process the rendering task, where the rendering task is generated by the client in response to a configuration operation for the front-end interface corresponding to the rendering program.

[0030] In addition, to achieve the above object, the present application also proposes a cloud rendering package deployment device, which is applied to a client. The device includes:

[0031] An image file generation module, configured to generate an image file in response to a configuration operation for the rendering program, and send the image file to the remote server, so that the remote server deploys the image file through a container;

[0032] A cloud rendering package sending module, configured to send a preset cloud rendering package to the remote server, so that the remote server updates the configuration file of the cloud rendering package and deploys the updated cloud rendering package;

[0033] A front-end interface display module, configured to display the front-end interface corresponding to the rendering program;

[0034] A rendering task generation module, configured to generate a rendering task in response to a configuration operation for the front-end interface, and send the rendering task to the cloud rendering package deployed by the remote server, so that the deployed cloud rendering package invokes the rendering program in the image file to process the rendering task.

[0035] In addition, to achieve the above object, the present application further provides a remote server, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the cloud rendering package deployment method as described above.

[0036] In addition, to achieve the above object, the present application further provides a client, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the cloud rendering package deployment method as described above.

[0037] In addition, to achieve the above object, the present application further provides a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium, and when the computer program is executed by a processor, the steps of the cloud rendering package deployment method as described above are implemented.

[0038] In addition, to achieve the above object, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the cloud rendering package deployment method as described above are implemented.

[0039] One or more technical solutions provided by the present application have at least the following technical effects: First, by the client responding to the configuration operation for the rendering program, an image file is generated. By generating the rendering program image, it is convenient to quickly deploy the corresponding rendering program; and the client sends the image file to the remote server; then the remote server receives the image file and deploys the image file through a container. The deployment method of the image file shortens the deployment cycle of the cloud rendering service; then the remote server receives the cloud rendering package sent by the client and updates its configuration file, and by deploying the updated cloud rendering package, the cloud rendering package is allowed to access the above-deployed image file, so as to realize the invocation of the rendering program in the image file; further, the deployed cloud rendering package receives rendering tasks, and these rendering tasks are generated based on the configuration operations of the user on the front-end interface for the rendering program, reflecting the user's rendering requirements; then the rendering program in the previously deployed image file can be invoked by the cloud rendering package to process the rendering task, ensuring the efficient execution of the rendering task, and the cloud rendering package can directly call the back-end interface in the rendering program without passing through the existing cloud service interface, so various functions provided by the rendering program can be freely combined, thereby improving the flexibility of cloud rendering. In addition, through the full-link customization from configuration to rendering, the present application effectively realizes the comprehensive customization of the rendering service, which not only improves the deployment efficiency of the rendering service but also improves the flexibility of cloud rendering, facilitating the satisfaction of the diverse rendering needs of users. Description of the Drawings

[0040] The accompanying drawings here are incorporated into the description and form a part of this description, showing embodiments consistent with the present application, and are used together with the description to explain the principles of the present application.

[0041] To more clearly illustrate the technical solutions in the embodiments of the present application or in the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on these drawings.

[0042] Figure 1 It is a schematic flowchart provided for the first embodiment of the cloud rendering package deployment method of the present application;

[0043] Figure 2 It is a schematic flowchart for generating an image file provided for the third embodiment of the present application;

[0044] Figure 3 It is an interaction schematic diagram provided for the third embodiment of the present application;

[0045] Figure 4 It is a schematic module structure diagram of the cloud rendering package deployment device for the first embodiment of the present application;

[0046] Figure 5 It is a schematic module structure diagram of another cloud rendering package deployment device for the embodiment of the present application;

[0047] Figure 6 It is a schematic device structure diagram of the hardware operating environment of the remote server involved in the cloud rendering package deployment method for the embodiment of the present application;

[0048] Figure 7 It is a schematic device structure diagram of the hardware operating environment of the client involved in the cloud rendering package deployment method for the embodiment of the present application. Detailed implementation manners

[0049] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0050] To better understand the technical solutions of the present application, the following will be described in detail in combination with the accompanying drawings of the description and specific implementation manners.

[0051] In this embodiment, for the convenience of description, the following will be described with the terminal as the execution subject.

[0052] Since the conventional cloud rendering solution mainly deploys code to the server through Docker and accesses existing cloud service interfaces, the process includes: compiling and packaging the front-end code, creating a DockerFile, and building the packaged front-end code into an image file; deploying the image file to the Docker container on the server through the DockerFile; and realizing the rendering of the video stream by accessing the cloud service interface of the server. However, the functions provided by the cloud service interface are usually fixed, and it is difficult for ordinary users to modify the configuration of the cloud service interface, making it difficult to achieve custom rendering of the scene. Moreover, when the video stream to be rendered is deployed locally, it cannot access the image file, resulting in the inability to complete the rendering.

[0053] The present application provides a solution. The client generates an image file in response to a configuration operation for the rendering program. By generating the rendering program image, it is convenient to quickly deploy the corresponding rendering program; and the client sends the image file to the remote server; then the remote server receives the image file and deploys the image file through the container. The deployment method of the image file shortens the deployment cycle of the cloud rendering service; then the remote server receives the cloud rendering package sent by the client and updates its configuration file, and allows the cloud rendering package to access the deployed image file by deploying the updated cloud rendering package, thereby realizing the invocation of the rendering program in the image file; further, the deployed cloud rendering package receives rendering tasks, which are generated based on the configuration operations of the user on the front-end interface for the rendering program and reflect the user's rendering requirements; then the rendering program in the previously deployed image file can be invoked by the cloud rendering package to process the rendering task, ensuring the efficient execution of the rendering task. Moreover, the cloud rendering package can directly call the back-end interface in the rendering program without passing through the existing cloud service interface, so the free combination of various functions provided by the rendering program can be realized, thus enhancing the flexibility of cloud rendering. Even if the video stream is deployed locally, it can be uploaded to the cloud rendering package, and the rendering program in the image file can be invoked in the remote server for rendering processing, and then the rendering of the local video stream can be completed.

[0054] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions.

[0055] Taking the remote server deployed with containers as the execution subject as an example, this embodiment and the following embodiments will be described. Based on this, the embodiments of the present application provide a method for deploying a cloud rendering package, referring to Figure 1 , Figure 1 which is the flowchart of the first embodiment of the method for deploying a cloud rendering package of the present application.

[0056] In this embodiment, the method for deploying a cloud rendering package includes steps S10 to S30:

[0057] Step S10: Receive the mirror file sent by the client and deploy the mirror file through a container, where the mirror file is generated by the client in response to a configuration operation for the rendering program.

[0058] It should be noted that a mirror file refers to a packaged file containing an application program and its running environment, which is usually used in containerization technologies (such as Docker) to facilitate quick startup and running on a server.

[0059] Exemplarily, a user can select a mirror file to be deployed from a mirror repository or locally; then the client can send the obtained mirror file to the remote server; after receiving the mirror file, the remote server deploys it in a container, loads and runs the mirror file in the container; then the user or other devices can access the program in the mirror file through the network.

[0060] Exemplarily, after installing the environment related to Docker containers on the remote server, the remote server can automatically identify the operating system environment corresponding to the received mirror file, install the corresponding operating system kernel package in Docker, load and run the mirror file in Docker, and determine the default port allocated to Docker by the remote server as the access port for the mirror file; then the user or other devices can call the relevant components or pages of the application program in the mirror file by requesting the access port of the remote server.

[0061] Step S20: Receive the cloud rendering package sent by the client, update the configuration file of the cloud rendering package, and deploy the updated cloud rendering package.

[0062] It should be noted that a cloud rendering package refers to a software tool package encapsulating cloud rendering functions, which is mainly used to provide an API (Application Programming Interface), receive rendering tasks from the client, call the application program in the mirror file for rendering, and return the rendering result to the client after rendering is completed.

[0063] Exemplarily, the client sends the obtained cloud rendering package to the remote server; then after receiving the cloud rendering package, the remote server configures the cloud rendering package, including configuring its IP (Internet Protocol) address and port, ensuring that the cloud rendering package can normally call the mirror file to complete the rendering task after startup, and completing the deployment of the cloud rendering package.

[0064] In a feasible implementation manner, the step of updating the configuration file of the cloud rendering package in step S20 includes:

[0065] Step S21, determining the Internet Protocol (IP) address of the remote server as the IP address in the configuration file, and determining the access port as the port in the configuration file.

[0066] Exemplarily, in a Linux container, the default port of the container can be determined as the access port of the image file through the "docker run" instruction. For example, through "docker run -p 5173:80 image name", first map the 80 port of the container to the 5173 port of the remote server through -p, and then specify the image name to be run; then the user or other devices can access the service provided by the corresponding image file in the container through the port of the remote server. Through port mapping, the access to the image file in the container is realized, which is convenient for the user or other components to call and improves the flexibility of cloud rendering.

[0067] Exemplarily, after receiving the cloud rendering package, the remote server makes corresponding adjustments to the configuration file of the cloud rendering package, including modifying the IP address in the configuration file to the IP address of the remote server and modifying the port in the configuration file to the access port of the image file, so that the cloud rendering package can access the corresponding image file by reading the IP address and port in the configuration file and call the relevant configuration in the image file to render the video stream provided by the cloud rendering package; then after the rendering is completed, the rendering result is returned to the client through the cloud rendering package.

[0068] In this implementation manner, by adjusting the configuration file of the cloud rendering package, the cloud rendering package can normally access the image file and call the component interface therein to render the video stream, etc., so as to achieve custom rendering.

[0069] Step S30, receiving the rendering task through the deployed cloud rendering package, and calling the rendering program in the image file to process the rendering task, where the rendering task is generated by the client in response to the configuration operation for the front-end interface corresponding to the rendering program.

[0070] In a feasible embodiment, a front-end interface corresponding to a rendering program is displayed on a client. The front-end interface refers to an interactive interface including front-end controls corresponding to the back-end interface of the rendering program. A user can determine a video stream to be rendered and corresponding rendering operations in the front-end interface. Then, after the client detects a configuration operation for the front-end interface, it generates a rendering task according to the configuration operation and sends the rendering task to a remote server. The remote server receives the rendering task through a cloud rendering package, respectively calls the video stream reading interface and the corresponding rendering interface in the mirror file to process the rendering task, and returns the rendering result to the client after the processing is completed.

[0071] It should be noted that the rendering tasks received by the cloud rendering package can come from the client, or may come from the rendering software or rendering service on the local side of the remote server, or may also come from a web browser, other remote servers, etc.

[0072] Exemplarily, when a user determines a video stream to be rendered in the front-end interface, the user can package and upload a local video stream file to the cloud rendering package through the client, and then the cloud rendering package directly calls the rendering program in the mirror file to render the video stream, and returns the rendering result to the client after the rendering is completed. The user can also send the access interface corresponding to the video stream to the cloud rendering package, and then the cloud rendering package provides the video stream access interface to the mirror file, calls the rendering program in the mirror file to read and process the video stream, and returns the rendering result to the client after the rendering is completed.

[0073] This embodiment provides a method for deploying a cloud rendering package. By simultaneously deploying a mirror file corresponding to a rendering program and a cloud rendering package on a remote server, direct calls to relevant interfaces in the rendering program are realized, the flexibility of cloud rendering is improved, and the execution of fixed rendering operations through predefined cloud service interfaces is avoided, realizing custom rendering.

[0074] Based on the first embodiment of the present application, in the second embodiment of the present application, for the same or similar content as in the above-mentioned first embodiment, reference can be made to the above introduction and will not be elaborated hereinafter. On this basis, the steps of updating the configuration file of the cloud rendering package in step S20 include:

[0075] Step S22, in response to a configuration operation for the useOneByOne field, which is a field processed one by one in the configuration file, adjust the concurrent access support ability of the cloud rendering package.

[0076] In a feasible embodiment, the user can modify the useOneByOne field in the configuration file for the cloud rendering package through a configuration operation on the useOneByOne field, thereby adjusting the concurrent access support capability of the cloud rendering package; and then, after detecting the configuration operation on the useOneByOne field in the configuration file for the cloud rendering package, the cloud server determines the configuration operation as the modified useOneByOne field. For example, the useOneByOne field is modified to false, enabling multiple users to access the cloud rendering service simultaneously; or, the useOneByOne field is modified to true, and the cloud rendering package can only process the rendering tasks of one user at a time, and other users need to wait until the rendering tasks of the current user are completed before using the cloud rendering service.

[0077] Exemplarily, the remote server can also automatically adjust the useOneByOne field according to the current load.

[0078] In this embodiment, by modifying the useOneByOne field to adjust the concurrent access support capability of the cloud rendering package, concurrent access to the rendering cloud service is achieved. Furthermore, multiple users can access the cloud rendering service simultaneously, reducing the waiting time of users and enhancing the rendering experience of users.

[0079] In a feasible implementation manner, after the step of deploying the updated cloud rendering package in step S20, it further includes:

[0080] Step S211, in response to a trigger operation on the startup script for the cloud rendering package, detect the access path of the configuration file;

[0081] Exemplarily, the client can determine the access path of the configuration file by reading the attribute information or log file of the cloud rendering package, and then detect whether the access path exists, that is, whether the corresponding configuration file can be accessed through the access path.

[0082] Step S212, in the case where the access path exists, determine the environment variables of the remote server as the environment variables of the configuration file to obtain the target configuration file;

[0083] In a feasible embodiment, the user can start the cloud rendering service by clicking the startup script of the cloud rendering package; then, after the remote server detects a trigger operation for the cloud rendering package, it obtains the access path of the configuration file of the cloud rendering package and checks whether the path exists. If the access path does not exist, it means that the cloud rendering package does not have a configuration file, stops running the script, and prompts the user to restart the script after adding a configuration file to the cloud rendering package; if the access path exists, it obtains the environment variables of the current remote server, such as the development environment (dev) or the release environment (release), etc., and sets the environment variables in the configuration file to the environment variables of the current remote server; after the modification is completed, it prints the configuration file so that the user can check whether the modification has been completed.

[0084] Step S213, start the cloud rendering package according to the target configuration file.

[0085] Exemplarily, for different environment variables, the settings of the cloud rendering package in the target configuration file are different. In the development environment, the cloud rendering package is set to output the debugging information during the running process, which is convenient for developers to locate and solve possible problems in the rendering process; in the release environment, a more strict access control policy is configured for the cloud rendering package to prevent unauthorized access and data leakage.

[0086] Exemplarily, in addition to starting the cloud rendering package by triggering the script file, the user can also start the cloud rendering package by setting timed startup, event-triggered startup, etc.

[0087] In this embodiment, by responding to the trigger operation for the startup script, dynamically obtaining the configuration file path, and starting the cloud rendering package according to the configuration file, the operation of the user manually configuring the environment is reduced, ensuring that the cloud rendering package can run normally in different environments.

[0088] Based on the first embodiment and / or the second embodiment of the present application, in the third embodiment of the present application, the same or similar content as in the above-mentioned first embodiment and second embodiment can be referred to the above introduction and will not be repeated hereinafter. The following takes the client as the execution subject as an example to illustrate this embodiment. On this basis, the cloud rendering package deployment method includes steps E10 to E40:

[0089] Step E10, in response to a configuration operation for the rendering program, generate an image file and send the image file to the remote server so that the remote server deploys the image file through a container;

[0090] Exemplarily, the user can write a rendering program in the code writing program provided by the client. The user can directly write the source code or call the relevant interfaces of the Web3D engine for writing. After completion, the user triggers the relevant configuration operation of the rendering program to generate an image file. Then, after detecting the configuration operation for the rendering program, the client exports the rendering program and its running dependencies to obtain the image file.

[0091] It can be understood that through containerized deployment with the image file, the same application program can be quickly replicated and run in the cloud environment without manual installation and configuration of dependencies.

[0092] In a feasible implementation manner, the step of generating an image file in step E10 in response to the configuration operation for the rendering program includes:

[0093] Step A11, in response to the configuration operation for the rendering program, compile the source code corresponding to the rendering program to obtain an executable file of the source code, and generate an image file including the executable file and the running dependencies of the executable file. Here, the running dependencies of the executable file are the resources required for the executable file to run.

[0094] It should be noted that compilation refers to the process of converting source code into intermediate code or machine code that can be understood by a computer. These intermediate codes or machine codes constitute the executable file. The executable file usually exists in the form of a binary file, contains all the internal logic and internal dependencies for task execution, and can be directly run on the target operating system.

[0095] Exemplarily, the user writes the source code for rendering a video stream and hopes to deploy it to a remote server after compilation. Then, in response to the configuration operation for the rendering program, the client compiles the source code into an executable file according to the programming language and project type of the source code, identifies and extracts the library files and the like relied on by the executable file, packages the executable file and its library files and the like to generate an image file, and sends it to the remote server. After receiving the image file, the remote server deploys the image file inside the container and determines the default port of the container as the access port of the image file. The user can achieve quick access to the rendering program by accessing the IP of the remote server and the access port of the image file.

[0096] Exemplarily, please refer to Figure 2 , in response to the configuration operation for the rendering program, the client checks out the latest code version from the code repository to obtain the source code. After checking out, determine the address of the image file and output the image address. Perform project compilation to compile the source code into an executable file. After the project compilation is completed, Docker can be used to build and push the image (image file) and send the pushed image to the remote server.

[0097] In this embodiment, by compiling and exporting the source code, an image file containing all necessary components can be generated, thus simplifying the deployment process and reducing errors.

[0098] In a feasible embodiment, the step of generating an image file in response to a configuration operation for the rendering program in step E10 includes:

[0099] Step B11, in the case where the rendering program is built based on the Web3D engine, in response to a configuration operation for the rendering program, generate an image file including the Web3D engine and the running dependencies of the Web3D engine, where the running dependencies of the Web3D engine are the resources required for the Web3D engine to run.

[0100] It should be noted that the Web3D engine refers to a type of 3D graphics rendering engine developed based on Web technology, used to create and render three-dimensional graphics in a browser, such as WebGL (Web Graphics Library) and WebGPU (Web Graphics Processing Unit). The rendering program is software or code built based on the Web3D engine, and can complete the rendering of the video stream by calling the components included in the Web3D engine.

[0101] Exemplarily, the developer writes a rendering program based on Three.js, defines a 3D scene and model. After writing is completed, the client is triggered to generate an image file; then, after the client receives the trigger operation for the rendering program, it packages the rendering program and its running dependencies to generate an image file and sends it to the remote server; after the deployment on the remote server is completed, the user can render the obtained video stream by calling the 3D scene and model in the rendering program, or directly perform custom rendering on the video stream based on the basic components of Three.js.

[0102] In this embodiment, by encapsulating the Web3D application and its running dependencies into an image file, the cumbersome environment adaptation in different environments can be avoided, and the rapid deployment of the Web3D application in different environments can be achieved.

[0103] It can be understood that the first embodiment of step E10 provided above has a lower cost and takes more time compared to the second embodiment. Therefore, the generation efficiency of the image file in the first embodiment is higher, and since the basic component design of the second embodiment is more perfect than that of the first embodiment, the scalability of the rendering program built by the second embodiment is higher.

[0104] The above are only two feasible implementation manners for obtaining at least one mirror file in step E10 provided in this embodiment, and this embodiment does not specifically limit the specific implementation manner for obtaining at least one mirror file in step E10.

[0105] Step E20: Send a preset cloud rendering package to a remote server, so that the remote server updates the configuration file of the cloud rendering package and deploys the updated cloud rendering package.

[0106] Step E30: Display the front-end interface corresponding to the rendering program.

[0107] Step E40: In response to a configuration operation on the front-end interface, generate a rendering task and send the rendering task to the cloud rendering package deployed on the remote server, so that the deployed cloud rendering package calls the rendering program in the mirror file to process the rendering task.

[0108] In a feasible embodiment, for the convenience of user operation, a front-end interface is displayed on the client, and the front-end interface includes front-end controls corresponding to the back-end interfaces of the rendering program; the user can upload a video stream and render it by manipulating the front-end controls; after the client detects a configuration operation on the front-end interface, according to the video stream file or video stream access address involved in the configuration operation, and the corresponding rendering operation, generate a rendering task and send the rendering task to the cloud rendering package; and then the cloud rendering package receives the rendering task, and according to the rendering operation included in the rendering task, calls the back-end interface corresponding to the rendering program in the mirror file to process the video stream included in the rendering task.

[0109] In this embodiment, generating a mirror file corresponding to the rendering program through the client facilitates rapid deployment; by sending the cloud rendering package to the remote server, the relevant interfaces in the mirror file can be directly called to process the rendering task, which is convenient for improving the flexibility of cloud rendering.

[0110] Exemplarily, to help understand the implementation process of the cloud rendering package deployment method obtained by combining the above Embodiment 1 and Embodiment 2 in this embodiment, please refer to Figure 3 , Figure 3 An interaction schematic diagram is provided. Specifically:

[0111] The user executes step S101 to configure the rendering program. The user can configure the rendering program by directly writing source code, or by calling relevant components or APIs of the Web3D engine.

[0112] After the user configuration is completed, the client executes S102. In response to the configuration operation for the rendering program, an image file including the rendering program and its running dependencies is generated. In the case where the user configures the rendering program by writing source code, the client compiles the corresponding source code to obtain an executable file, and then exports the executable file and its running dependencies to obtain the corresponding image file. In the case where the user constructs the rendering program based on the Web3D engine, the Web3D engine and its running dependencies are directly exported to generate an image file. After obtaining the image file, the client executes S103 and sends the image file to the remote server.

[0113] After receiving the image file sent by the client, the remote server executes S104, deploys the image file inside the container, and modifies the access port of the image file to the default port of the container.

[0114] The client executes S105 and sends the preset cloud rendering package to the remote server.

[0115] After receiving the cloud rendering package sent by the client, the remote server executes S106, updates the configuration file of the cloud rendering package, modifies the IP address in the configuration file to the IP address of the remote server, and modifies the port in the configuration file to the access port of the above-determined image file, so that the cloud rendering package can directly call the rendering program in the image file to complete the rendering task.

[0116] After the remote server configuration is completed, the user can execute S107 on the front-end interface corresponding to the rendering program to determine the rendering operation for the video stream; then the client executes S108. In response to the rendering operation for the video stream, a rendering task is generated, and S109 is executed to send the rendering task to the remote server.

[0117] After receiving the rendering task sent by the client, the remote server executes S110, parses the rendering task through the cloud rendering package, extracts the video stream expected to be rendered by the user and the corresponding rendering operation from it, and according to the rendering operation, calls the image file to render the video stream; after the rendering is completed, the remote server executes S111 and returns the rendering result to the client.

[0118] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the cloud rendering package deployment method of this application. Based on this technical concept, more forms of simple transformations are within the protection scope of this application.

[0119] The embodiment of this application also provides a cloud rendering package deployment device. Please refer to Figure 4 The cloud rendering package deployment device is applied to a remote server deployed with a container. The device includes:

[0120] A deployment module 10, configured to receive an image file sent by a client and deploy the image file through a container, where the image file is generated by the client in response to a configuration operation for a rendering program;

[0121] An update module 20, configured to receive a cloud rendering package sent by a client, update the configuration file of the cloud rendering package, and deploy the updated cloud rendering package;

[0122] An invocation module 30, configured to receive a rendering task through the deployed cloud rendering package and invoke a rendering program in the image file to process the rendering task, where the rendering task is generated by the client in response to a configuration operation for a front-end interface corresponding to the rendering program.

[0123] The cloud rendering package deployment device provided by the embodiments of the present application adopts the cloud rendering package deployment method in the above embodiments and can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the cloud rendering package deployment device provided by the present application are the same as those of the cloud rendering package deployment method provided by the above embodiments, and other technical features in the cloud rendering package deployment device are the same as the features disclosed in the method of the above embodiments, which will not be elaborated herein.

[0124] Embodiments of the present application further provide a cloud rendering package deployment device. Please refer to Figure 5 ., The cloud rendering package deployment device is applied to a client, and the device includes:

[0125] An image file generation module 40, configured to generate an image file in response to a configuration operation for a rendering program and send the image file to a remote server, so that the remote server deploys the image file through a container;

[0126] A cloud rendering package sending module 50, configured to send a preset cloud rendering package to a remote server, so that the remote server updates the configuration file of the cloud rendering package and deploys the updated cloud rendering package;

[0127] A front-end interface display module 60, configured to display a front-end interface corresponding to a rendering program;

[0128] A rendering task generation module 70, configured to generate a rendering task in response to a configuration operation for the front-end interface and send the rendering task to a cloud rendering package deployed on a remote server, so that the deployed cloud rendering package invokes a rendering program in the image file to process the rendering task.

[0129] The cloud rendering package deployment device provided by the embodiment of the present application adopts the cloud rendering package deployment method in the above embodiment, and can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the cloud rendering package deployment device provided by the present application are the same as those of the cloud rendering package deployment method provided by the above embodiment, and other technical features in the cloud rendering package deployment device are the same as the features disclosed in the above embodiment method, which will not be elaborated herein.

[0130] The embodiment of the present application provides a remote server, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the cloud rendering package deployment method in the first embodiment above.

[0131] Refer to the following Figure 6 , which shows a schematic structural diagram of a remote server suitable for implementing the embodiment of the present application. The remote server in the embodiment of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The remote server shown is only an example and should not impose any limitations on the functions and usage scope of the embodiment of the present application.

[0132] As Figure 6As shown, the remote server may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 into the random access memory (RAM: Random Access Memory) 1004. In the RAM 1004, various programs and data required for the operation of the remote server are also stored. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. The input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the remote server to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a remote server having various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or had alternatively.

[0133] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device, or installed from the storage device 1003, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above functions defined in the methods of the embodiments disclosed in the present application are executed.

[0134] The remote server provided by the embodiments of the present application adopts the cloud rendering package deployment method in the above embodiments, and can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the remote server provided by the present application are the same as those of the cloud rendering package deployment method provided by the above embodiments, and other technical features in the remote server are the same as those disclosed in the method of the previous embodiment, and will not be elaborated here.

[0135] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0136] As described above, the above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application, and all of them should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0137] An embodiment of this application provides a client, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the cloud rendering package deployment method in the first embodiment above.

[0138] The following refers to Figure 7 , which shows a schematic structural diagram of a client suitable for implementing the embodiments of this application. The client in the embodiments of this application can include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description), PMPs (Portable Media Player), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The client shown is only an example and should not impose any limitations on the functions and usage scope of the embodiments of this application.

[0139] As Figure 7As shown, the client may include a processing device 2001 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 2002 or a program loaded from a storage device 2003 into a random access memory (RAM: Random Access Memory) 2004. In the RAM 2004, various programs and data required for client operations are also stored. The processing device 2001, the ROM 2002, and the RAM 2004 are connected to each other through a bus 2005. An input / output (I / O) interface 2006 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 2006: an input device 2007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 2008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 2003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 2009. The communication device 2009 may allow the client to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a client having various systems, it should be understood that it is not required to implement or have all the systems shown. Instead, more or fewer systems may be implemented or had.

[0140] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device, or installed from the storage device 2003, or installed from the ROM 2002. When the computer program is executed by the processing device 2001, the above functions defined in the methods of the embodiments disclosed in the present application are executed.

[0141] The client provided by the embodiments of the present application adopts the cloud rendering package deployment method in the above embodiments, and can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the client provided by the present application are the same as those of the cloud rendering package deployment method provided by the above embodiments, and other technical features in the client are the same as those disclosed in the method of the previous embodiment, and will not be elaborated here.

[0142] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0143] As described above, the above are only specific embodiments of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0144] An embodiment of this application provides a computer-readable storage medium having computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the cloud rendering package deployment method in the above embodiments.

[0145] The computer-readable storage medium provided by an embodiment of this application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or combined with an instruction execution system or device. The program code contained on the computer-readable storage medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0146] The above computer-readable storage medium can be included in a remote server and / or a client; it can also exist independently without being assembled into the remote server and / or the client.

[0147] The above computer-readable storage medium carries one or more programs, which, when executed by a remote server with containers deployed thereon, cause the remote server to: receive an image file sent by a client and deploy the image file through a container, where the image file is generated by the client in response to a configuration operation for a rendering program; receive a cloud rendering package sent by the client and update the configuration file of the cloud rendering package, and deploy the updated cloud rendering package; receive a rendering task through the deployed cloud rendering package, and call the rendering program in the image file to process the rendering task, where the rendering task is generated by the client in response to a configuration operation for the front-end interface corresponding to the rendering program.

[0148] The above computer-readable storage medium carries one or more programs, which, when executed by a remote server, cause the client to: in response to a configuration operation for a rendering program, generate an image file and send the image file to the remote server so that the remote server deploys the image file through a container; send a preset cloud rendering package to the remote server so that the remote server updates the configuration file of the cloud rendering package and deploys the updated cloud rendering package; display the front-end interface corresponding to the rendering program; in response to a configuration operation for the front-end interface, generate a rendering task and send the rendering task to the cloud rendering package deployed by the remote server so that the deployed cloud rendering package calls the rendering program in the image file to process the rendering task.

[0149] Computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0150] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0151] The modules described in the embodiments of the present application can be implemented in software or in hardware. In some cases, the name of the module does not constitute a limitation on the unit itself.

[0152] The readable storage medium provided in the embodiments of the present application is a computer-readable storage medium. The computer-readable storage medium stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned cloud rendering package deployment method, and can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as those of the cloud rendering package deployment method provided in the above embodiments, and will not be elaborated here.

[0153] The embodiments of the present application also provide a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of the cloud rendering package deployment method as described above are implemented.

[0154] The computer program product provided in the embodiments of the present application can solve the technical problem of how to improve the flexibility of cloud rendering. Compared with the prior art, the beneficial effects of the computer program product provided in the present application are the same as those of the cloud rendering package deployment method provided in the above embodiments, and will not be elaborated here.

[0155] The above are only some embodiments of the present application, and thus do not limit the patent scope of the present application. Any equivalent structural transformation made under the technical concept of the present application by using the content of the specification and drawings of the present application, or any direct / indirect application in other related technical fields, is included in the patent protection scope of the present application.

Claims

1. A cloud rendering package deployment method, characterized in that: The cloud rendering package deployment method is applied to a remote server and a client on which a container is deployed, and the method includes: The client generates an image file in response to the configuration operation on the rendering program, and sends the image file to the remote server; The remote server receives the image file sent by the client and deploys the image file through the container; The client sends a preset cloud rendering package to the remote server; The remote server receives the cloud rendering package sent by the client, updates the configuration file of the cloud rendering package, and deploys the updated cloud rendering package; The client displays the front-end interface corresponding to the rendering program; The client generates a rendering task in response to the configuration operation on the front-end interface, and sends the rendering task to the cloud rendering package deployed by the remote server, so that the deployed cloud rendering package calls the rendering program in the image file to process the rendering task; The remote server receives the rendering task through the deployed cloud rendering package, and calls the rendering program in the image file to process the rendering task; Wherein, the step of updating the configuration file of the cloud rendering package includes: The remote server determines the Internet Protocol IP address of the remote server as the IP address in the configuration file, and determines the access port of the image file as the port in the configuration file, wherein the access port is the port of the container.

2. The cloud rendering package deployment method according to claim 1, characterized in that: The step of updating the configuration file of the cloud rendering package includes: The remote server adjusts the concurrent access support capability of the cloud rendering package in response to a configuration operation on the useOneByOne field in the configuration file.

3. The cloud rendering package deployment method according to claim 1, characterized in that: After the step of deploying the updated cloud rendering package, the method further includes: The remote server detects an access path of the configuration file in response to a trigger operation on a startup script of the cloud rendering package; In the case where the access path exists, the remote server determines the environment variable of the remote server as the environment variable of the configuration file to obtain the target configuration file; The remote server starts the cloud rendering package according to the target configuration file.

4. The cloud rendering package deployment method according to claim 1, characterized in that: The step of generating an image file by the client in response to a configuration operation on the rendering program includes: In response to the configuration operation for the rendering program, the client compiles the source code corresponding to the rendering program, obtains an executable file of the source code, and generates an image file including the executable file and the running dependencies of the executable file, wherein the running dependencies of the executable file are resources required for the running of the executable file.

5. The cloud rendering package deployment method according to claim 1, characterized in that: The step of generating an image file by the client in response to a configuration operation on the rendering program includes: When the rendering program is built based on the Web3D engine, the client generates an image file including the Web3D engine and the running dependencies of the Web3D engine in response to the configuration operation on the rendering program, wherein the running dependencies of the Web3D engine are resources required for the running of the Web3D engine.

6. A remote server, characterized in that: The remote server includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the cloud rendering package deployment method according to any one of claims 1 to 5.

7. A client, characterized in that: The client comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the cloud rendering package deployment method according to any one of claims 1 to 5.

8. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the cloud rendering package deployment method according to any one of claims 1 to 5 are implemented.

Citation Information

Patent Citations

  • Access method and device of cloud rendering application service, equipment and medium

    CN115906136A

  • Instant cloud development method and device, equipment and medium

    CN117971170A