A method for implementing one-to-many based on cloud rendering

Abstract

This invention belongs to the field of cloud rendering technology and provides a method for implementing one-to-many cloud rendering. The one-to-many cloud rendering method comprises three parts: basic cloud rendering service, cloud rendering program, and cloud rendering room service. The method includes the following steps: creating an identification code, generating a session, binding user information, creating a user room, joining a user room, and exiting the user room. After a user selects a cloud rendering program, the webpage first sends a room query request to the room service for the corresponding cloud rendering program. Upon receiving the request, the room service queries all room numbers with more than one user through the program ID and returns the results to the front-end webpage. After receiving the room information, the webpage displays all rooms, and the user selects a room to join. This effectively utilizes the cloud rendering service and rationally allocates program request methods, making the utilization of cloud rendering server resources more efficient.

Description

Technical Field

[0001] This invention belongs to the field of cloud rendering technology, specifically a method for achieving one-to-many based on cloud rendering. Background Technology

[0002] The cloud rendering model is similar to conventional cloud computing, in which the 3D program is placed on a remote server for rendering. The user terminal accesses the resource by clicking a "cloud rendering" button through web software or directly in the local 3D program and using high-speed Internet access. The command is issued from the user terminal, the server executes the corresponding rendering task according to the command, and the rendering result is sent back to the user terminal for display, thus completing the cloud rendering process.

[0003] Real-time cloud rendering technology establishes a connection between the front-end and back-end through a signaling service, enabling the back-end to push the rendered screen to the front-end via video stream. The signaling service is like a room; once a user joins the room, all web pages can access the rendered screen from the back-end. If only one user is browsing, it is a one-to-one service; if multiple users are browsing, it is a one-to-many service.

[0004] As can be seen from the above, the cloud rendering signaling service itself can complete one-to-many communication. As long as the signaling service address is known, anyone can access the cloud rendering program. However, without the concept of users, it is impossible to meet our actual needs. Therefore, we need a way to solve the user's access needs and determine whether the user needs one-to-one or one-to-many program access. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a method for implementing one-to-many relationships based on cloud rendering. By using basic cloud rendering services, cloud rendering programs, and cloud rendering room services, it manages users' one-to-one or one-to-many permissions, thereby solving the problem that current technologies cannot quickly determine whether a user needs one-to-one or one-to-many relationships.

[0006] The specific technical solution of this invention is as follows:

[0007] A method for implementing one-to-many cloud rendering, comprising three parts: basic cloud rendering service, cloud rendering program, and cloud rendering room service, includes the following steps:

[0008] S1: Create identification codes. First, the basic cloud service generates a batch of program identification codes runid, which are used to assign to each started cloud rendering program. A user information table is created with the identification code as the ID to record all connected users.

[0009] S2: Session generation. The cloud-rendered room service first generates a session. When a user accesses the cloud-rendered room service and obtains a business webpage (viewing the program and opening the webpage to join the program), the service first checks whether there is a session value in the cookie in the request header. If it does not exist, a session is generated.

[0010] S3: User information binding. The cloud rendering program will store the identification code runid obtained from S1. When the webpage successfully connects to the cloud rendering program, it will receive the session value sent by the webpage and bind and store the cloud rendering connection user with the session value.

[0011] S4: User Room Creation. Users can freely create a cloud-rendered room and specify the number of people in the room.

[0012] S5: When a user joins a room, after the user selects a cloud rendering program, the webpage first sends a room query request to the room service for the corresponding cloud rendering program, and then displays all rooms to the user through the webpage. The user then selects a room to join.

[0013] S6: User exit, and finally, room exit and disband. When a newly added user closes the interface, only the current user exits, without affecting other people in the room; when the room is created and the interface is closed, the room is disbanded directly.

[0014] Among them, the basic cloud rendering service is the basic service for accessing the cloud rendering program. After the user sends a start request, the basic cloud rendering service is responsible for launching the signaling service and the cloud rendering program, and returning the signaling service address for the user to access the cloud rendering program. The basic cloud rendering service provides the basic access capabilities of the cloud rendering program.

[0015] A cloud rendering program is a 3D program created based on business needs. After adding a cloud rendering plugin, the rendered image is transmitted to a webpage, and the program responds to the webpage's interactive events.

[0016] The cloud rendering room service is a user-facing service that displays cloud rendering programs to users and provides creation or joining functions. It manages access permissions for the current cloud rendering program by allowing users to specify one-to-one or one-to-many permissions, giving the current program exclusive or shared permissions. At the same time, it displays online cloud rendering programs with shared permissions and provides users with the join function, enabling users to join the current cloud rendering program and realize one-to-many service.

[0017] As a further aspect of the present invention, in step S2, during the session generation process, the cloud rendering room service first obtains the remote IP of the request connection, then obtains the "User-Agent" field in the request header, merges the IP and "User-Agent" content into a base string, converts the base string into a ten-digit string of 0-9a-z according to a fixed rule, and uses it as the user identification code of the browser corresponding to the IP. This information is stored in the request return information cookie and added to the session field.

[0018] As a further aspect of the present invention, in step S3, after the cloud rendering program binds and stores the cloud rendering connection user with the session value, it sends a user connection message to the basic cloud rendering service, the content of which includes runid, session, join / leave (join / leave).

[0019] As a further aspect of the present invention, in step S4, during the process of a user creating a cloud-rendered room, after the server receives the creation request, it obtains the cloud rendering program ID and the user session, and begins to create a room object, the content of which includes the program ID, personnel information, cloud rendering address and personnel limit. Then, the cloud rendering address is returned to the front-end webpage, and the room creation is completed when the front-end opens the address.

[0020] As a further aspect of the present invention, in step S5, after a user joins a cloud-rendered room, the webpage sends the room number selected by the user to the room server. After receiving the user's request to join the room, the room service obtains the user's session, adds it to the room user list, and returns the cloud-rendered address of the room to the webpage. The front-end can join the room by opening the address, and the page will synchronize the latest program screen for the user to watch, thereby realizing one person operating and multiple people watching.

[0021] As a further solution of the present invention, in step S6, when the user closes the cloud rendering webpage, the connection between the webpage and the cloud rendering program is disconnected. The program queries the session of the connection object and sends a message to the basic cloud rendering service. After receiving the message, the basic cloud rendering service queries the running user under the runid and determines the identity of the currently exiting user.

[0022] If the user is not the creator, remove the session information from the user list; otherwise, shut down the cloud rendering program and push service.

[0023] Compared with the prior art, the present invention has the following beneficial effects:

[0024] 1. This invention, upon receiving a cloud rendering room creation request from the server, obtains the cloud rendering program ID and user session, creates a room object including the program ID, personnel information (session), cloud rendering address, and personnel limit; only then does it send a cloud rendering program start command to the cloud rendering basic service to start the specified program ID. After startup, it obtains the cloud rendering connection address, preventing the server address from being exposed, preventing malicious requests, and protecting data.

[0025] 2. In this invention, after a user selects a cloud rendering program, the webpage first sends a room query request to the room service for the corresponding cloud rendering program. After receiving the request, the room service queries all room numbers with more than 1 people by program ID and returns them to the front-end webpage. After receiving the room information, the webpage displays all rooms, and the user selects a room to join. Thus, by effectively utilizing the cloud rendering service and rationally allocating the program request method, the cloud rendering server resources are utilized more efficiently. Attached Figure Description

[0026] Figure 1 This is a basic principle diagram of the cloud rendering room service of this invention;

[0027] Figure 2 This is a flowchart of the program startup and session acquisition process of this invention;

[0028] Figure 3 This is a flowchart of the session generation process of this invention;

[0029] Figure 4 This is a flowchart of the multiplayer room creation process of this invention;

[0030] Figure 5 This is a flowchart of the user joining a room according to the present invention;

[0031] Figure 6 This is a flowchart of the user's exit and entry / exit process in this invention. Detailed Implementation

[0032] The embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and should not be construed as limiting the scope of the invention.

[0033] like Figure 1-6 As shown, the method for implementing one-to-many based cloud rendering proposed in this invention consists of three parts: basic cloud rendering service, cloud rendering program, and cloud rendering room service; the basic cloud rendering service adds storage of online user information of the running cloud rendering program on the basis of traditional services, and provides a query interface; the cloud rendering program needs to add reporting of connected user information; room and user management is completed by the cloud rendering room service, which manages the one-to-one or one-to-many permissions of users.

[0034] One method for achieving one-to-many based on cloud rendering targets the concept of weak users, where a weak user is defined as an IP address plus a browser model and version number.

[0035] Its basic principle is as follows Figure 1 As shown, when a user accesses the room service homepage through a browser, the room server generates a session by obtaining the IP address and browser version number, and writes it to the browser's cookies. At this time, the browser acts as a user. When a user creates a cloud rendering program example, a shared room or a private room is created based on the user's choice. A startup request is then sent to the basic cloud rendering service to execute the startup operation. After startup, the user begins connecting to the cloud rendering program. When a user connects, the webpage sends the current session to the cloud rendering program, which then reports the currently connected user to the basic cloud rendering service. When other users access the service, the shared room is pushed to the new user. When a user joins the room, the cloud rendering address corresponding to the current room is returned to the new user for joining. When the cloud rendering program receives connections from other users, it reports the connection information sequentially. The specific implementation steps of the one-to-many method for cloud rendering are as follows:

[0036] Step 1: Create an identification code

[0037] First, the basic cloud rendering service generates a batch of program identification codes (runids) to be assigned to each started cloud rendering program. It also creates a user information table with the identification code as the ID to record all connected users.

[0038] Step 2: Session generation

[0039] like Figure 2 As shown, the cloud rendering room service first needs to perform session generation. When a user accesses the cloud rendering room service and obtains the business webpage (viewing the program and opening the webpage to join the program), the service first checks whether there is a session value in the cookie in the request header. If it does not exist, a session is generated.

[0040] like Figure 3 As shown, to generate a session: First, obtain the remote IP of the request connection, then obtain the "User-Agent" field in the request header. This field contains browser information. Combine the IP and "User-Agent" content into a base string, and convert the base string into a ten-digit string of 0-9a-z according to a fixed rule. This string serves as the user identification code for the browser corresponding to the IP. Store this information in the cookie returned by the request and add it to the session field.

[0041] Step 3: User Information Binding

[0042] When a cloud rendering program is started, the basic cloud rendering service assigns a program identifier (runid) to the cloud rendering program as a startup parameter. The cloud rendering program then retrieves and stores the runid after startup. Once a webpage successfully connects to the cloud rendering program, it receives the session value sent by the webpage, binds and stores the cloud rendering connection object, and sends a user connection message to the basic cloud rendering service, including the runid, session information, and join / leave details.

[0043] When the basic cloud rendering service receives a join or leave message, it records the current user accessing the program, adds the session to the user list with the corresponding runid, and removes the session from the user list when the user leaves.

[0044] Step 4: Creating User Rooms

[0045] like Figure 4 As shown, the next step is user creation. Users can freely create a cloud rendering program room and specify the number of people in the room (one or more). After receiving the creation request, the server obtains the cloud rendering program ID and the user's session, and creates a room object, including the program ID, personnel information (session), cloud rendering address, and maximum number of people. By sending a cloud rendering program start command to the cloud rendering basic service, the specified program ID is started. After the start is complete, the cloud rendering connection address is obtained, saved in the room information, and then the cloud rendering address is returned to the front-end webpage. The front-end opens the address to complete the room creation.

[0046] Step 5: Joining a User's Room

[0047] like Figure 5 As shown, a further step involves user addition, enabling multi-user processing. When a user selects a cloud rendering program, the webpage first sends a room query request to the room service for the corresponding cloud rendering program. Upon receiving the request, the room service retrieves all room numbers with more than one user by program ID and returns them to the front-end webpage. After receiving the room information, the webpage displays all rooms, and the user selects a room to join. The webpage then sends the selected room number to the room server. Upon receiving the user's request to join the room, the room service obtains the user's session, adds it to the room's user list, and returns the room's cloud rendering address to the webpage. The front-end user can join the room by opening the address. Simultaneously, the webpage will synchronize the latest program screen for the user to view, thus enabling one-to-many interaction and cloud rendering.

[0048] Step 6: User Logout

[0049] like Figure 6As shown, when a user who joined later closes the interface, only the current user leaves, without affecting other users in the room; when the interface is closed after the room is created, the room is directly disbanded.

[0050] When a user closes a cloud-rendered webpage, the connection between the webpage and the cloud rendering program is broken. The program retrieves the session of the connection object and sends a message (runid, session, leave) to the basic cloud rendering service. Upon receiving the message, the basic cloud rendering service queries the running user under that runid and determines whether the currently exiting user is the creator. If not, the session information is removed from the user list; if it is, the cloud rendering program and streaming service are shut down. Simultaneously, the room service queries the basic cloud rendering service to obtain the information that the program has closed, deletes the room corresponding to that program, and then disbands the room.

[0051] The embodiments of the present invention are given for the purposes of illustration and description, and are not intended to be exhaustive or to limit the invention to the forms disclosed. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features.

Claims

1. A method for implementing one-to-many based on cloud rendering, characterized in that, The cloud rendering implementation one-to-many includes three parts, namely, a basic cloud rendering service, a cloud rendering program and a cloud rendering room service, and the cloud rendering implementation one-to-many method includes the following steps: S1: Create an identification code, first, the basic cloud service generates a batch of program identification codes runid, which is used to assign to each started cloud rendering program, and creates a user information table with the identification code as the ID to record all connected users; S2: session generation, the cloud rendering room service first generates a session, when the user accesses the cloud rendering room service and obtains the business webpage, the service first checks whether the session value exists in the Cookie of the request header, if not, a session is generated; S3: User information binding, the cloud rendering program stores the identification code runid obtained in S1, when the webpage successfully connects the cloud rendering program, the session value sent by the webpage is received, and the cloud rendering connection user and the session value are bound and stored; S4: User room creation, users can freely create a cloud rendering room and specify the number of people in the room; S5: User room joining, after the user selects the cloud rendering program, the webpage first initiates a room query request for the corresponding cloud rendering program to the room service, and then displays all rooms to the user through the webpage, and the user selects a room to join; In step S5, after the user joins the cloud rendering room, the webpage sends the room number selected by the user to the room server, the room service receives the user's request to join the room, obtains the user session, adds it to the room user list, and returns the cloud rendering address of the room to the webpage, and the front end opens the address to join the room. The page synchronizes the latest program picture for the user to watch, thereby realizing one-person operation and multi-person watching; S6: User exit, finally, the room exit and disband, when the last joined user closes the interface, only the current user exits, which does not affect the watching of other personnel in the room; when the room is created, the interface is closed, and the room is directly disintegrated.

2. The method of claim 1, wherein the cloud-based rendering is implemented to achieve one-to-many. In step S2, the session generation process, first, the cloud rendering room service obtains the remote IP of the request connection, and then obtains the "User-Agent" field of the request header, combines the IP and "User-Agent" content into a basic string, converts the basic string into a ten-digit and English mixed string composed of 0-9, a-z according to a fixed rule, as the user identification code of the browser corresponding to the IP, and stores the user identification code in the Cookie of the request return information, and adds it to the session field.

3. The method of claim 1, wherein the cloud-based rendering is implemented to achieve one-to-many. In step S3, after the cloud rendering program binds and stores the cloud rendering connection user and the session value, it sends a user connection message to the basic cloud rendering service, including runid, session, join / leave.

4. The method of claim 1, wherein the cloud-based rendering is implemented to achieve one-to-many. In step S4, in the process of creating a cloud rendering room by the user, after the server receives the creation request, the cloud rendering program ID and the user session are obtained, the room object is created, the content includes the program ID, personnel information, cloud rendering address and personnel upper limit, and the cloud rendering address is returned to the front-end webpage. The front-end opens the address to complete the room creation.

5. The method of claim 1, wherein the cloud-based rendering is implemented to achieve one-to-many. In step S6, when the user closes the cloud rendering webpage, the connection between the webpage and the cloud rendering program is disconnected, the session of the connection object is queried, a message is sent to the basic cloud rendering service, the basic cloud rendering service receives the message, queries the running user under the runid, and judges the identity of the current exit user; If it is not the creator, the session information is removed from the user list; Otherwise, the cloud rendering program and the push service are closed.

Images