Content sharing methods, content sharing devices, computer equipment, and computer programs

Abstract

The present invention relates to a content sharing method, the method being performed by a server and including the steps of: (202) responding to a content sharing request sent by a meeting member participating in a meeting, identifying meeting members waiting to share content, and adding the meeting members waiting to share content to a waiting space; (204) feeding back the meeting members in the waiting space to the meeting host terminal and instructing the host terminal to display each meeting member in the waiting space; and (3) responding to an activation command sent from the host terminal, identifying one meeting member from among the meeting members displayed on the host terminal that is specified in the activation command, and sending the content to be shared by the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting.

Description

Technical Field

[0001] This application claims the priority of the Chinese patent application with application number 2023112219288 and invention title "Content Sharing Method, Device, Equipment, Storage Medium and Program Product" filed on September 20, 2023, and all its contents are incorporated herein by reference.

[0002] This application relates to the technical field of computers, and particularly to content sharing methods, devices, equipment, storage media and program products.

Background Art

[0003] An online meeting is a meeting conducted through a network. Participants can use the shared screen or recording function of the online meeting to present PPT (PowerPoint (registered trademark), a type of presentation software) documents, web pages, and other meeting materials for other participants in the online meeting to discuss and make decisions on relevant matters, thereby solving the problem of remoteness of meeting members.

Summary of the Invention

Problems to be Solved by the Invention

[0004] In current online meetings, only one participant can share the screen. When other participants need to share the screen while a participant is sharing the screen, the sharing of the currently screen-sharing participant needs to be terminated, and then the screen sharing from other participants is started to achieve the switching of screen sharing.

[0005] When multiple participants need to share the screen, the screen sharing switching operation needs to be repeated multiple times. Such switching operations are cumbersome and time-consuming, resulting in a decrease in the content sharing efficiency in online meetings.

[0006] The embodiments of this application provide a content sharing method, device, equipment, storage medium and program product. [Means for solving the problem]

[0007] In one embodiment, the present invention provides a content sharing method performed by a server. The method includes the steps of: responding to a content sharing request sent by a meeting member participating in a meeting, identifying meeting members waiting to share content, and adding the meeting members waiting to share content to a waiting space; feeding back the meeting members in the waiting space to the host terminal of the meeting, and instructing the host terminal to display each meeting member in the waiting space; and responding to an activation command sent from the host terminal, identifying one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and transmitting the content to be shared of the meeting member specified in the activation command to a participant terminal used by each meeting member participating in the meeting.

[0008] In another embodiment, the present invention further provides a content sharing device. The device includes an additional module for responding to a content sharing request sent by a meeting member participating in a meeting, identifying meeting members waiting to share content, and adding the meeting members waiting to share content to a waiting space; a feedback module for feeding back the meeting members in the waiting space to the host terminal of the meeting and instructing the host terminal to display each meeting member in the waiting space; and a sharing module for responding to an activation command sent from the host terminal, identifying one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and transmitting the content to be shared by the meeting member specified in the activation command to a participant terminal used by each meeting member participating in the meeting.

[0009] In one embodiment, the present invention further provides a content sharing method performed by a host terminal. The method includes the steps of: displaying a conference interface for a conference, the conference interface including a content display area and a sharing guidance area; displaying in the sharing guidance area conference members waiting to share content and the activation status of each conference member, including at least "waiting for activation" and "activated"; and in response to an activation operation for any one of the waiting conference members, displaying the content to be shared for the conference member specified in the activation operation in the content display area, and updating the activation status of the conference member specified in the activation operation to "activated" in the sharing guidance area.

[0010] In another embodiment, the present invention further provides a content sharing device. The device is a meeting interface for a meeting and includes a first display module for displaying the meeting interface, which includes a content display area and a sharing guidance area; a second display module for displaying in the sharing guidance area meeting members waiting to share content and the activation status of each meeting member, which includes at least an activation waiting state and an activated state; and a third display module for displaying in the content display area the content to be shared by the meeting member specified in the activation operation in response to an activation operation for any one of the meeting members waiting to activate, and updating the activation status of the meeting member specified in the activation operation to activated in the sharing guidance area.

[0011] In one embodiment, the present invention further provides a content sharing method performed by a participant terminal. The method includes the steps of: sending a content sharing request in response to a content sharing operation triggered on the conference interface; displaying a sharing guidance area on the conference interface and displaying in the sharing guidance area conference members whose activation status is not activated and who are waiting to perform content sharing; and updating the activation status of the conference members waiting to perform content sharing to activated in the sharing guidance area in response to an activation command for the conference members waiting to perform content sharing, and performing the sharing of the content to be shared corresponding to the content sharing request.

[0012] In another embodiment, the present invention further provides a content sharing device. The device includes: a request sending module for sending a content sharing request in response to a content sharing operation triggered in a conference interface; a fourth display module for displaying a sharing guidance area in the conference interface and displaying conference members waiting to perform content sharing whose activation status is not yet activated in the sharing guidance area; and a fifth display module for updating the activation status of the conference members waiting to perform content sharing to activated in the sharing guidance area in response to an activation command for the conference members waiting to perform content sharing, and for performing the sharing of the content to be shared corresponding to the content sharing request.

[0013] In another embodiment, the present invention further provides a computer device, the computer device comprising memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps of the content sharing method are realized.

[0014] In another embodiment, the present invention further provides a computer-readable storage medium on which a computer program is stored, and the content sharing method is realized when the computer program is executed by a processor.

[0015] In another embodiment, the present invention further provides a computer program product, the computer program product comprising a computer program, the content sharing method being realized when the computer program is executed by a processor.

[0016] Details of one or more embodiments of the present application will be described in the following drawings and description. Other features, purposes and advantages of the present application will be apparent from the specification, drawings and claims. [Brief explanation of the drawing]

[0017] To more clearly illustrate the embodiments of this application or the technical solutions in the prior art, the following briefly introduces the drawings necessary for describing the embodiments or the prior art. Naturally, the drawings in the following description are merely embodiments of this application, and those skilled in the art will be able to create other drawings based on the disclosed drawings without requiring any ingenuity.

[0018] [Figure 1] Figure 1 is a diagram illustrating the application environment of a content sharing method in one embodiment. [Figure 2] Figure 2 is a schematic flowchart of a content sharing method in one embodiment. [Figure 3] Figure 3 is a state machine diagram of the meeting members in one embodiment. [Figure 4] Figure 4 is a schematic diagram of an open widget for opening a standby space on a host terminal in one embodiment. [Figure 5] Figure 5 is a schematic flowchart of a content sharing method in another embodiment. [Figure 6]FIG. 6 is a schematic diagram of the display interface of the host terminal when the standby space is not open in one embodiment. [Figure 7] FIG. 7 is a schematic diagram of the display interface of the host terminal after the standby space is opened in one embodiment. [Figure 8] FIG. 8 is a schematic diagram showing the conference members in the standby space and the activation status of each conference member on the host terminal in one embodiment. [Figure 9] FIG. 9 is a schematic diagram showing the activation waiting status of the conference members waiting for content sharing execution who have entered the standby space on the participating terminal in one embodiment. [Figure 10] FIG. 10 is a schematic diagram of the sharing guidance area of the host terminal in one embodiment. [Figure 11] FIG. 11 shows a schematic diagram of the sharing guidance area of the host terminal in another embodiment. [Figure 12] FIG. 12 shows a schematic diagram of the deletion widget within a predetermined adjacent range in one embodiment. [Figure 13] FIG. 13 is a schematic diagram of the first prompt information in one embodiment. [Figure 14] FIG. 14 is a schematic diagram of the second prompt information in one embodiment. [Figure 15] FIG. 15 is a schematic diagram of the operation logic of the host terminal in one embodiment. [Figure 16] FIG. 16 is a flow schematic diagram of the content sharing method in another embodiment. [Figure 17] FIG. 17 is a schematic diagram of the control logic for the participating terminal to execute content sharing in one embodiment. [Figure 18] FIG. 18 is a schematic diagram of the third prompt information in one embodiment. [Figure 19] FIG. 19 is a schematic diagram of the fourth prompt information in one embodiment. [Figure 20] FIG. 20 is a schematic diagram of the fifth prompt information in one embodiment. [Figure 21]Figure 21 is a detailed sequence diagram of a content sharing method in one embodiment. [Figure 22] Figure 22 is a structural block diagram of a content sharing device in one embodiment. [Figure 23] Figure 23 is a structural block diagram of a content sharing device in another embodiment. [Figure 24] Figure 24 is a structural block diagram of a content sharing device in another embodiment. [Figure 25] Figure 25 is an internal structure diagram of a computer device in one embodiment. [Figure 26] Figure 26 is an internal structure diagram of a computer device in another embodiment. [Modes for carrying out the invention]

[0019] The technical scheme of the embodiments of this application will be described clearly and comprehensively below in conjunction with the drawings of the embodiments of this application. Of course, the embodiments described are only a part of the embodiments of this application, not all of them. All other embodiments that a person skilled in the art could obtain without ingenuity based on the embodiments of this application are all within the scope of protection of this application.

[0020] The content sharing method provided in this embodiment can be applied in an application environment as shown in Figure 1. Here, the participant terminal 102 sends a content sharing request to the server 104, and the server 104 responds to the content sharing request sent by the meeting members participating in the meeting to identify the meeting members waiting for content sharing to be performed and adds the meeting members waiting for content sharing to the waiting space. The server 104 feeds back the meeting members in the waiting space to the meeting host terminal 106 and instructs the host terminal 106 to display each meeting member in the waiting space. The host terminal 106 sends an activation command to one of the displayed meeting members. In response to the activation command sent from the host terminal 106, which specifies one of the displayed meeting members, the server 104 sends the content to be shared for the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting.

[0021] Here, the meeting members 102 and host terminals 106 include various desktop computers, laptops, smartphones, tablet devices, IoT devices, etc., and IoT devices may include, but are not limited to, smart TVs, etc. The server 104 may be a standalone physical server, or a server group or distributed system consisting of multiple physical servers. Furthermore, it may be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain services, security services, CDN (Content Delivery Network), and big data and AI platforms. User terminals include, but are not limited to, mobile phones, personal computers, smart voice interaction devices, smart home appliances, in-car terminals, aircraft, etc. Terminals and servers can be connected directly or indirectly by wired or wireless communication methods, but this application does not limit this.

[0022] In one embodiment, a content sharing method as shown in Figure 2 is provided, and the case where this method is applied to the server shown in Figure 1 is described as an example. This method includes the following steps.

[0023] Step 202: In response to content sharing requests initiated by meeting members participating in the meeting, identify meeting members waiting for content sharing to be performed and add those members to the waiting area.

[0024] A meeting refers to a multi-person online meeting that uses network technology to share data from multiple users in different locations. A meeting includes multiple meeting members and one host member. The host member's device is the host terminal, and the meeting members' devices are the participant terminals; different meeting members have different devices.

[0025] A waiting space can be understood as a virtual waiting room for temporarily storing data. For example, a waiting space could specifically be a cache space on a server and / or host terminal, or a waiting queue. In some scenarios, data cached in the waiting space may have a certain order.

[0026] The host terminal is used to set permissions for meeting members. For example, the host terminal can control meeting members' entry into and exit from the waiting space, open or close the waiting space, and activate meeting members within the waiting space. However, meeting members who are not in the waiting space are in an unshared state, and the activation status of meeting members who have entered the waiting space includes "waiting for activation" and "activated." "Waiting for activation" refers to a state where a meeting member has entered the waiting space but has not yet shared content, and the initial state when a meeting member enters the waiting space is "waiting for activation." "Activated" refers to a state where a meeting member has entered the waiting space and is sharing content. For example, if the host terminal controls and opens the waiting space and controls an unshared meeting member to enter the waiting space, the meeting member who entered the waiting space will switch from the unshared state to the "waiting for activation" state, and when the host terminal activates the meeting member, it will switch from the "waiting for activation" state to the "activated" state.

[0027] Participant terminals are used to initiate content sharing requests. Once the host terminal's content sharing request is approved, the content to be shared on the participant terminal is sent to the participant terminals used by other meeting members participating in the meeting. Meeting members waiting for content sharing to be executed refer to meeting members who are logged into a participant terminal.

[0028] A content sharing request is initiated from a participant's terminal and is used to request the server to share the content that the requesting meeting member wants to share with other meeting members. The content that needs to be shared refers to the shared screen data currently being displayed by the meeting member who initiated the request. Meeting materials include PowerPoint presentations, web pages, text documents, video materials, etc.

[0029] In some embodiments, a content sharing request includes the content to be shared and member information of the meeting member who initiated the content sharing request. Specifically, member information may include the meeting member's name, image, or network address.

[0030] In some embodiments, the meeting members waiting for content sharing to be executed are the meeting members who initiated the content sharing request. In other embodiments, the meeting members waiting for content sharing to be executed are the meeting members who initiated the content sharing request and whose request has been approved.

[0031] Specifically, the server receives content sharing requests sent from multiple meeting members during a meeting, reviews the requests, and if they pass the review, adds the meeting members waiting to share content to the waiting area. Alternatively, the server forwards the received content sharing requests to the host terminal, where the host terminal reviews the requests. The server receives the review results returned from the host terminal, and if the review passes, adds the meeting members waiting to share content to the waiting area.

[0032] In some embodiments, for the first meeting member to submit a content sharing request, the server directly adds that member to the waiting area. For subsequent meeting members who submit content sharing requests, the server or host terminal reviews the request, and if it passes the review, the server adds the meeting member waiting to submit the content sharing request to the waiting area.

[0033] Step 204: Provide feedback to the meeting host terminal regarding the meeting members in the waiting area and instruct the host terminal to display each meeting member in the waiting area.

[0034] Specifically, the server retrieves the activation status, shared content, and member information of each meeting member in the waiting area, and feeds this information back to the meeting host terminal, instructing the host terminal to display the activation status, shared content, and member information of each meeting member in the waiting area on its screen.

[0035] Step 206: In response to the activation command sent from the host terminal, the host terminal identifies one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and sends the shared content of the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting.

[0036] An activation command is generated based on an activation operation performed by the host terminal for one of the conference members waiting to be activated in the waiting area. It is used to instruct the server to switch the conference member specified in the activation command from the waiting state to the activated state, and to send the shared content of that conference member to the participant terminals used by each conference member participating in the meeting, thereby enabling content sharing.

[0037] In some embodiments, the host terminal can activate one of the meeting members waiting to be activated in the waiting space, but only one meeting member can be activated in the waiting space at the same time, and all other meeting members in the waiting space remain in a waiting state for activation.

[0038] In some embodiments, the activation operation may involve the host terminal triggering an activation widget to switch to one of the conference members waiting to be activated in the waiting space.

[0039] In some embodiments, the states of meeting members are mutually transitionable, and Figure 3 shows a state machine diagram of meeting members in one embodiment. Referring to Figure 3, it can be seen that the state transitions of meeting members include the following cases.

[0040] (1) When no meeting members are in the waiting space, the corresponding state is "unshared," and other meeting members cannot see the corresponding shared content. The total number of meeting members in the waiting space is 0. When a meeting member in the "unshared" state enters the waiting space, the state changes from "unshared" to "waiting for activation," and the total number of meeting members in the waiting space increases by 1.

[0041] (2) If an unshared meeting member enters the waiting space and the total number of meeting members in the waiting space is 1, the unshared meeting member will be directly switched to the activated state.

[0042] (3) When the host terminal activates any one of the meeting members who is waiting to be activated, the status of that meeting member changes from waiting to activated, and the other meeting members can view the corresponding shared content. The other meeting members in the waiting space are switched to waiting to be activated, and the total number of meeting members in the waiting space remains unchanged.

[0043] (4) When the host terminal activates another meeting member in the waiting space, the status of the activated meeting member changes from activated to waiting for activation, and the total number of meeting members in the waiting space remains unchanged.

[0044] (5) When an activated meeting member leaves the waiting area, the status of that meeting member changes from activated to inactive, and the total number of meeting members in the waiting area decreases by 1.

[0045] (6) When a meeting member in the activation waiting state leaves the waiting space (the meeting member on the participant terminal closes the shared content that is awaiting activation), the state changes from activation waiting state to unshared state, and the total number of meeting members in the waiting space decreases by 1.

[0046] Alternatively, when the host terminal closes the waiting space, the status of all meeting members awaiting activation changes to "unshared," and the total number of meeting members in the waiting space is reset to 0. Or, when the host terminal removes one of the meeting members awaiting activation from the waiting space, that meeting member becomes "unshared," and the total number of meeting members in the waiting space decreases by 1.

[0047] Specifically, when the host terminal receives the activation status, shared content, and member information of the meeting members in the waiting space, it displays the activation status, shared content, and member information of each meeting member in the waiting space on the host terminal's interface. The host terminal then detects a user activation operation for one of the displayed meeting members and generates an activation command based on the detected activation operation. The host terminal sends the activation command to the server, and upon receiving the activation command, the server sends the shared content for the meeting member specified in the activation command to the participant terminals used by each meeting member participating in the meeting, thereby enabling content sharing.

[0048] In the content sharing method described above, after receiving a content sharing request from a meeting member participating in the meeting, the meeting members waiting to share content are added to a waiting space, and the meeting members in the waiting space are fed back to the meeting host terminal. In this process, multiple meeting members who need to share content in the meeting wait in the waiting space, and if it is necessary to switch content sharing, the host terminal directly activates the switch to enable the switching of shared content. Throughout the entire switching process, there is no need to wait for a meeting member who is currently sharing content to stop sharing, nor is there a need to wait for a meeting member waiting to share content to start sharing. Therefore, it is possible to achieve seamless switching of shared content during a meeting, simplify the sharing operation flow during the meeting, and improve the efficiency of content sharing.

[0049] In one embodiment, prior to the step of identifying meeting members waiting to share content in response to a content sharing request sent by a meeting member participating in the meeting and adding the meeting members waiting to share content to the waiting space, the content sharing method further includes the step of opening a waiting space in response to an open command to open the waiting space sent from the host terminal.

[0050] An open command is generated based on an open operation that occurs on the host terminal. The open operation may be a trigger operation by the host terminal to open an open widget that opens a waiting space.

[0051] For example, Figure 4 is a schematic diagram of an open widget for opening a waiting space on a host terminal in one embodiment. When a host member triggers the "Screen Sharing" widget in Figure 4, the sharing settings screen is displayed, and the sharing settings screen displays a sharing settings prompt window. The sharing settings prompt window displays the sharing settings for content sharing. For example, the sharing settings include options such as "Simultaneous sharing of terminal audio," "Person picture-in-picture," "Open waiting space," and "Meeting watermark settings," and "Open waiting space" is the open widget for opening the waiting space. Person picture-in-picture overlays the image of the meeting member performing content sharing onto the content display area, allowing other meeting members to view the shared content more immersively. Clicking "Open waiting space" once opens the waiting space, and clicking it again closes the waiting space. In Figure 4, screen sharing permissions can also be set, and the screen sharing permissions include options such as "All members can share" and "Only host members can share." When screen sharing permissions are set, the host terminal generates an open command based on the content of the triggered selected item and sends the open command to the server. The server opens a waiting space. Note that the trigger operations for each of the above widgets can be performed not only by clicking, but also by touching, double-clicking, swiping, and voice commands, and are not limited to these in this embodiment.

[0052] Specifically, when a host member triggers an open widget on the host terminal to open a standby space, the host terminal detects the open widget's trigger operation, generates an open command, and sends the open command to the server for the standby space. The server then opens the standby space based on the open command.

[0053] In the above embodiment, the standby space is opened only when the server receives an open command from the host terminal. This increases the security of the standby space and avoids problems such as meeting members entering the standby space without the host terminal's knowledge, or meeting members in the standby space being unable to share content due to network problems or failure to process content sharing requests in a timely manner, thus reducing content sharing efficiency.

[0054] In one embodiment, the step of responding to a content sharing request initiated by a meeting member participating in the meeting, identifying meeting members waiting to share content, and adding those meeting members to the waiting space includes the following steps:

[0055] The system receives content sharing requests from meeting members participating in the meeting and identifies the member who sent the request as a member waiting for content sharing to be performed. The content sharing request includes the content that needs to be shared. The system then forwards the content sharing request to the host terminal and instructs the host terminal to review the content that needs to be shared in the request. If the review is successful, the member waiting for content sharing to be performed is added to the waiting area.

[0056] Specifically, the host terminal reviewing the content to be shared included in the content sharing request means reviewing whether the content to be shared meets the requirements of the meeting.

[0057] Specifically, the server receives content sharing requests from meeting members participating in the meeting and identifies the meeting member who made the request as a meeting member waiting for content sharing to be performed. The server then forwards the content sharing request to the host terminal, which displays the content to be shared in the request and reviews the content. If the review is successful, the meeting member waiting for content sharing to be performed is added to the waiting space. If the review is unsuccessful, the review result is sent to the server, which forwards the review result to the meeting member and refuses to allow the meeting member who made the content sharing request to enter the waiting space.

[0058] In some implementations, the host terminal reviews the content to be shared, sends the review results to the server, and the server forwards the review results to the meeting members. There are two types of review results: approved and rejected. For example, if the image in the content to be shared is unclear, the text is inaccurate, or the content to be shared is irrelevant to the meeting, the host terminal will determine that the content to be shared has been rejected and feed the review results back to the server. The server will then refuse to allow the meeting member who initiated the content sharing request to enter the waiting area.

[0059] In this embodiment, the server forwards the content sharing request to the host terminal and instructs the host terminal to review the content to be shared in the content sharing request. If the review is successful, the meeting members waiting for content sharing are added to the waiting space. This prevents content that does not satisfy the meeting's requirements from being shared incorrectly, thus avoiding impacting the efficiency of content sharing.

[0060] In one embodiment, after adding meeting members waiting for content sharing to a waiting space, the content sharing method further includes the steps of identifying the total number of meeting members currently in the waiting space, and, if the total is 1, directly sending the content to be shared by the meeting member who initiated the content sharing request to the participant terminal used by each meeting member participating in the meeting.

[0061] The total number of meeting members in a waiting space changes, and when a waiting space is opened, there are zero meeting members stored inside. When one meeting member joins a waiting space, the number of meeting members in the waiting space increases by one. When one meeting member leaves a waiting space, the number of meeting members in the waiting space decreases by one. When a waiting space is closed, the number of meeting members stored inside is reset to zero. A total of 1 in a waiting space means that there is currently only one meeting member in that waiting space.

[0062] When a participant terminal shares content (a meeting member on the participant terminal enters the waiting space), and the total number of meeting members in the waiting space is 1, the shared content on the participant terminal is directly activated, allowing meeting members on other participant terminals to view the content, and the total number of meeting members in the waiting space increases by 1.

[0063] When a participant's terminal shares content (i.e., a meeting member on the terminal enters the waiting area), and the total number of meeting members in the waiting area is greater than 1, that meeting member enters an activation waiting state, and other participants cannot view that member's shared content. The total number of meeting members in the waiting area increases by 1.

[0064] Specifically, after opening a waiting space, the server counts the total number of meeting members currently in the waiting space. If the total is 1, the server directly sends the content to be shared by the meeting member who initiated the content sharing request to the participant terminal used by each meeting member participating in the meeting.

[0065] In this embodiment, if the total number of meeting members in the current waiting space is 1, the content to be shared by the meeting member who initiated the content sharing request can be sent directly to the participant terminal used by each meeting member participating in the meeting, without requiring an activation command from the host terminal. This simplifies the content sharing operation flow and improves the efficiency of content sharing.

[0066] In one embodiment, the content sharing method includes a step of terminating content sharing, which, if a content close request is received, includes a step of removing the meeting member who initiated the content close request from the waiting space, and a step of terminating the current content sharing if the meeting member who initiated the content close request is a meeting member currently performing content sharing.

[0067] A content close request includes member information of the meeting member who initiated the request. Content close requests are initiated by meeting members who are waiting for content sharing to be performed or who are currently performing content sharing in the waiting area. For example, if meeting member A, who is waiting for content sharing to be performed in the waiting area, no longer needs to share content based on the progress of the meeting, meeting member A will send a content close request to the server and leave the waiting area. For example, if meeting member B, who is currently performing content sharing, needs to end the current content sharing, meeting member B will send a content close request to the server and end the current content sharing.

[0068] Specifically, when the server receives a content close request, it analyzes the request and obtains the member information of the meeting member who initiated the request. Based on the member information obtained through analysis, the server removes the corresponding meeting member from the waiting area. If the meeting member who initiated the content close request is a member of a meeting currently sharing content, the server terminates the current content sharing.

[0069] In this embodiment, when the server receives a content close request, it can directly remove the meeting member who initiated the content close request from the waiting area without waiting for a decision from the host terminal. Furthermore, if the meeting member who initiated the content close request is a meeting member currently sharing content, the current content sharing can be directly terminated without waiting for a decision from the host terminal. This simplifies the content sharing termination flow and improves the efficiency of content sharing.

[0070] In one embodiment, when multiple content sharing requests exist, the step of adding meeting members waiting for content sharing to be performed to the waiting space includes the steps of adding multiple meeting members waiting for content sharing to be performed to the waiting space, and arranging the meeting members in the waiting space according to a predetermined arrangement scheme.

[0071] Possible arrangement methods include a specified order, the chronological order of content sharing requests sent by each meeting member, the order in which each meeting member was invited to the meeting, the order of the meeting members' job titles, i.e., their levels in the organizational structure tree, the order of the first letters of each meeting member's last name, the order of each meeting member's location, or the order in which each meeting member's network communication status is highest, but the present embodiment is not limited to these.

[0072] Specifically, if there are multiple content sharing requests, the server feeds back the host terminal with the multiple meeting members waiting to share their content. After passing the host terminal's review, the server adds the multiple meeting members waiting to share their content to the waiting space. The server then arranges the meeting members in the waiting space according to a predetermined arrangement scheme.

[0073] In some embodiments, the method further includes a step of automatically sharing content, which specifically includes, upon receiving a content close request from a meeting member currently sharing content, terminating the current content sharing and automatically sending the content awaiting sharing from the next meeting member whose sequence is after the meeting member currently sharing content to the participant terminal used by each meeting member participating in the meeting.

[0074] The server can determine the automatic sharing order for each meeting member in the waiting space based on the arrangement of meeting members in the waiting space. For example, if meeting member B is the next member after meeting member A in the waiting space, after meeting member A finishes sharing content, the server can automatically send meeting member B's content awaiting sharing to the participant terminals used by each meeting member participating in the meeting, based on the arrangement of meeting members in the waiting space, without requiring the host terminal to send an activation command.

[0075] In some embodiments, after arranging the meeting members in the waiting space, the server, upon receiving a content close request from a meeting member waiting to share content, removes the member who made the content close request from the waiting space and updates the waiting space arrangement. Then, when the current content sharing is finished, the server automatically sends the content to be shared by the next meeting member whose arrangement is after the meeting member currently sharing content, according to the updated arrangement, to the participant terminal used by each meeting member participating in the meeting.

[0076] For example, suppose the arrangement of meeting members in the waiting space is meeting member A, meeting member B, and meeting member C, and meeting member A is currently performing content sharing. If meeting member B sends a content close request before meeting member A finishes their ongoing content sharing, the server removes meeting member B from the waiting space. At this time, the arrangement of each meeting member in the waiting space is updated to meeting member A and meeting member C. When meeting member A finishes their ongoing content sharing, the server automatically sends the content that meeting member C needs to be shared to the participant terminals used by each meeting member participating in the meeting.

[0077] In this embodiment, after arranging the meeting members in the waiting space according to a predetermined arrangement scheme, the server receives a content close request from the meeting member currently sharing content. Upon receiving this request, the server terminates the current content sharing and automatically sends the content to be shared by the next meeting member, whose position in the arrangement follows the currently sharing member, to the participant terminal used by each meeting member. This enables automatic switching of content sharing, eliminating the need for the host terminal to activate the next meeting member, simplifying the sharing operation flow on the host terminal, and improving content sharing efficiency.

[0078] In one embodiment, the content sharing method further includes the step of removing meeting members from the waiting space, the step of removing meeting members from the waiting space includes the following steps:

[0079] In response to a delete command sent from the host terminal, the system identifies one of the meeting members specified in the delete command from the meeting members displayed on the host terminal and removes that member from the waiting space. If the member specified in the delete command is currently sharing content, the current content sharing session is terminated.

[0080] A delete command is generated by the host terminal based on a trigger operation on the delete widget of any conference member on the conference interface. The conference member specified in the delete command is either a conference member waiting for activation in the standby space or an activated conference member. For example, when a host member triggers the delete widget of any conference member on the host terminal's conference interface, the host terminal detects the trigger operation on the conference member's delete widget, generates a delete command for that conference member based on the trigger operation, and sends the delete command to the server. The server deletes the conference member specified in the delete command from the standby space.

[0081] Meeting members in the waiting space can either leave voluntarily or be removed by the host terminal. If a meeting member leaves the waiting space voluntarily, they can do so without the host terminal's consent. If a trigger operation occurs on the host terminal for the delete widget for a meeting member who is currently sharing content or waiting to share content, the host terminal generates a delete command based on that trigger operation and feeds the delete command back to the server. Based on the delete command sent from the host terminal for any one of the displayed meeting members, the server removes the meeting member specified in the delete command from the waiting space.

[0082] In this embodiment, when the host terminal removes a meeting member who is currently sharing content or waiting to share content from the waiting space, the server removes the meeting member specified in the removal command from the waiting space based on a removal command sent from the host terminal to any one of the displayed meeting members, thereby providing the host terminal with a function to remove meeting members from the waiting space. This is convenient for the server to quickly remove meeting members from the waiting space, and since meeting members participating in the meeting do not need to take any action themselves, the operation flow for meeting members to leave the waiting space is simplified, and the efficiency of content sharing is improved.

[0083] In one embodiment, the content sharing method further includes the step of closing a waiting space, the step of closing a waiting space in response to a close command sent from a host terminal, the step of closing the waiting space, closing the content to be shared by a meeting member that was in an activation waiting state within the waiting space, and the step of holding the sharing operation for the content to be shared by a meeting member that was in an activated state within the waiting space.

[0084] The close command is used to instruct the server to close the standby space, and is generated based on an action by the host terminal that triggers the standby space close widget. After the standby space is closed, the host terminal will no longer display any of the conference members in the standby space.

[0085] In some embodiments, when the host terminal clicks "Open standby space" once in the sharing settings prompt window shown in Figure 4, the host terminal detects the first trigger operation of "Open standby space" and generates an open command for the standby space based on the first trigger operation. When the host terminal clicks "Open standby space" a second time in the sharing settings prompt window shown in Figure 4, the host terminal detects the second trigger operation of "Open standby space" and generates a close command for the standby space based on the second trigger operation.

[0086] Specifically, the server receives a close command for a standby space sent from the host terminal, and in response to the close command, closes the standby space and the shared content of meeting members that were in an activation waiting state within the standby space, and holds the sharing operation for the shared content of meeting members that were in an activated state within the standby space.

[0087] In this embodiment, when the server receives a close command for a standby space from the host terminal, it closes the content requiring sharing for meeting members that were in an activation waiting state within the standby space, and holds the sharing operation for content requiring sharing for meeting members that were in an activated state within the standby space. This preserves the sharing operation of meeting members who are already sharing content, thus avoiding a situation where currently running content sharing is interrupted and the efficiency of content sharing decreases.

[0088] In one embodiment, a content sharing method as shown in Figure 5 is provided, and the case where this method is applied to the host terminal shown in Figure 1 is described as an example. This method includes the following steps.

[0089] Step 502: Display a meeting interface for a meeting, the meeting interface including a content display area and a shared guidance area.

[0090] The content display area is used to display shared content during a meeting. The host terminal's sharing guidance area is used to display meeting members in the waiting area so that the host terminal can switch to sharing content. For example, the sharing guidance area displays member information (name and profile picture) and activation status of meeting members in the waiting area. In other scenarios, the sharing guidance area may also display sharing content for meeting members in the waiting area.

[0091] In some embodiments, Figure 6 is a schematic diagram of the host terminal's display screen when the waiting space is not open. As can be seen from Figure 6, when the host terminal does not open the waiting space, the shared information area does not display any shared content or member information for any meeting members. Figure 7 is a schematic diagram of the host terminal's display screen after the waiting space has been opened in one embodiment. As can be seen from Figure 7, after the host terminal opens the waiting space, the shared information area displays the activation status, member information, and shared content of the meeting members in the waiting space.

[0092] Specifically, the host terminal sets up an online meeting with multiple participants, and upon successful setup, displays the meeting interface. If no waiting space is open, the sharing guidance area of ​​the meeting interface does not display any shared content or member information for any meeting members. When a waiting space is opened, the sharing guidance area displays the activation status, member information, and shared content of the meeting members in the waiting space.

[0093] Step 504: In the sharing guidance area, display the meeting members who are waiting to share content, and the activation status of each meeting member, including at least those who are waiting to be activated and those who are activated.

[0094] The status of a meeting member who is not in the waiting space is "not shared," and the activation status of a meeting member who is in the waiting space includes "waiting for activation" and "activated." For example, if the host terminal controls and opens the waiting space and controls a meeting member who is in the "not shared" state to enter the waiting space, the initial state of the meeting member who entered the waiting space will be "waiting for activation," and when the host terminal activates the meeting member, it will switch from "waiting for activation" to "activated."

[0095] Specifically, the host terminal retrieves the activation status, member information, and content requiring sharing for each meeting member in the waiting space from the server, and displays the activation status, member information, and content requiring sharing for the meeting members in the waiting space in the shared guidance area. The activation status of the first meeting member to enter the waiting space changes from unactivated to activated, while the activation status of the other meeting members in the waiting space remains in a waiting state. The activation status of each meeting member in the waiting space is displayed in the shared guidance area.

[0096] In some embodiments, Figure 8 is a schematic diagram showing the meeting members in the waiting space and the activation status of each meeting member displayed on the host terminal in one embodiment. In Figure 8, Meeting Member A is the name of the meeting member, and Meeting Member A is the meeting member who first entered the waiting space or was activated by the host terminal. Therefore, the activation status of Meeting Member A is activated, and the activation status of the other meeting members is waiting for activation.

[0097] In some embodiments, for participant terminals used by meeting members waiting for activation in the waiting space, the participant terminal generates prompt information to notify that a meeting member waiting to perform content sharing has entered the waiting space, and displays only the activation waiting status of the meeting member waiting to perform content sharing. For example, Figure 9 is a schematic diagram showing the activation waiting status of a meeting member waiting to perform content sharing that has entered the waiting space in one embodiment. When meeting member A enters the waiting space and is in the activation waiting state, the participant terminal used by meeting member A displays the schematic diagram shown in Figure 9 to notify meeting member A that they have entered the waiting space.

[0098] Step 506: In response to an activation operation for any one of the meeting members awaiting activation, the content display area displays the shared content of the meeting member specified in the activation operation, and the sharing guidance area updates the activation status of the meeting member specified in the activation operation to activated.

[0099] The activation operation may involve triggering an activation widget to switch one of the meeting members waiting to be activated in the waiting area. However, the activation widget is a switch widget (e.g., a slide switch widget, a toggle switch widget, etc.), and the activation state of the meeting member is switched by the on / off state of the switch widget. In some embodiments, the activation widget is a state switching widget, and the activation state of the meeting member can be switched simply by clicking the state switching widget.

[0100] Specifically, the host member triggers the activation widget for any one of the meeting members waiting for activation in the waiting space. When the host member's host terminal detects the host member's activation operation for any one of the meeting members waiting for activation in the waiting space, it responds to the activation operation by switching the currently shared content displayed in the host terminal's content display area to the shared content of the meeting member specified in the activation operation. Then, in the sharing guidance area, it updates the activation status of the meeting member specified in the activation operation to activated, and updates the activation status of the meeting member who was previously sharing content to waiting for activation.

[0101] In some embodiments, the host terminal can switch the activation status of any meeting member in the waiting area. For example, in Figure 8, the meeting member currently sharing content is meeting member A, and the activation status of meeting member B is "waiting for activation". Clicking on the "waiting for activation" status of meeting member B switches the meeting member currently sharing content from meeting member A to meeting member B. The sharing guidance area on the host terminal after the switch is shown in Figure 10.

[0102] In some embodiments, when a meeting member waiting for content sharing to be performed on a participant terminal sends a content close request to the server, and the content close request is forwarded to the host terminal via the server, the meeting member who sent the content close request is no longer displayed in the host terminal's sharing guidance area. For example, Figure 11 is a schematic diagram of the host terminal's sharing guidance area in another embodiment. After meeting member D, who is waiting for activation in Figure 8, sends a content close request, meeting member D is no longer displayed in the host terminal's sharing guidance area, as shown in Figure 11. After meeting member D sends a content close request, the host terminal responds to the activation operation of any one of the meeting members waiting for activation by displaying the content to be shared by the meeting member specified in the activation operation in the host terminal's content display area, and also updates the activation status of the meeting member specified in the activation operation to activated in the host terminal's sharing guidance area.

[0103] In some embodiments, when a meeting member currently sharing content on a participant terminal sends a content close request to the server, and the content close request is forwarded to the host terminal via the server, the meeting member who sent the content close request is no longer displayed in the host terminal's sharing guidance area. Furthermore, the host terminal automatically displays the content to be shared by the next meeting member in the host terminal's content display area, in the order in which meeting members waiting to share content entered the waiting space, following the meeting member who was currently sharing content.

[0104] In this embodiment, a sharing guidance area is displayed on the host terminal's conference interface, and the meeting members waiting to share content and their activation status are displayed in the sharing guidance area. In response to the host member's activation operation for any one of the meeting members waiting to activate in the waiting area, the content to be shared by the meeting member specified in the activation operation is displayed in the content display area, and the activation status of the meeting member specified in the activation operation is updated to activated in the sharing guidance area. In the switching process, there is no need to wait for a meeting member who is currently sharing content to stop sharing, or for a meeting member waiting to share to start sharing, allowing for seamless switching of shared content during a meeting, simplifying the sharing operation flow during a meeting, and improving content sharing efficiency.

[0105] In one embodiment, the step of displaying the meeting members in the meeting waiting area and the activation status of each meeting member in the shared guidance area includes the following steps:

[0106] In the shared information area, meeting members waiting to share content are displayed item by item, and the activation status of each meeting member is displayed within a predetermined adjacent area of ​​that meeting member.

[0107] Displaying by item means displaying meeting members in a bulleted list format within the shared information area.

[0108] The predetermined adjacent range refers to the area within the shared guidance area that is a predetermined adjacent distance from the meeting members. For example, the predetermined adjacent range for a meeting member may be the area to the right of the meeting member, at a predetermined distance from the meeting member. For example, the predetermined adjacent range for a meeting member may be limited to the row in which the meeting member is displayed in the shared guidance area.

[0109] Specifically, the host terminal displays the meeting members in the meeting waiting area in a bulleted list within the shared information area of ​​the meeting interface, and further displays the activation status of each meeting member within a predetermined adjacent area.

[0110] For example, as shown in Figure 8 or Figure 10, the host terminal displays a bulleted list of meeting members in the waiting area of ​​the meeting interface, and displays the activation status of each meeting member to the right of that member.

[0111] In this embodiment, the host terminal displays the meeting members in the meeting waiting area by item in the shared guidance area, making it easier for the host member to clearly confirm the activation status of each meeting member. Furthermore, by displaying the activation status of each meeting member within a predetermined adjacent area, the activation widget can be quickly found when switching between meeting members currently sharing content, thereby improving the efficiency of content sharing.

[0112] In one embodiment, displaying the activation status of each meeting member within a predetermined adjacent range of that meeting member includes displaying the activation status of that meeting member within a predetermined adjacent range of that meeting member, as well as displaying a delete widget within a predetermined adjacent range of each meeting member awaiting activation. The delete widget is used to remove the meeting member from the waiting space.

[0113] Specifically, the host terminal displays the activation status of each meeting member within a predetermined adjacent range, and displays a delete widget within a predetermined adjacent range for each meeting member awaiting activation.

[0114] Please refer to Figure 12, which shows the delete widgets within a predetermined adjacent range in one embodiment. As shown in Figure 12, the activation status and delete widgets for the same meeting member are displayed on the same line. By triggering the "Remove from Waiting Space" widget located after any meeting member in the "Waiting for Activation" state in Figure 12, that meeting member in the "Waiting for Activation" state can be removed from the waiting space.

[0115] In some embodiments, for meeting members that have been activated in the waiting space, a switching operation on the host terminal for the activated meeting members in the waiting space can switch them from an activated state to a meeting member waiting for activation. A delete widget is displayed within a predetermined adjacent range of meeting members that have been switched to the waiting for activation state, and the host terminal can delete the corresponding meeting member from the waiting space by triggering an operation on the delete widget.

[0116] In some embodiments, the host terminal can also display a delete widget within a predetermined adjacent range of an activated meeting member, and triggering the delete widget displayed within the predetermined adjacent range of an activated meeting member can remove the activated meeting member from the waiting space.

[0117] In this embodiment, the host terminal displays the activation status of each meeting member in the waiting space in the shared guidance area, and displays a delete widget within a predetermined adjacent range of each meeting member waiting to be activated. This allows the delete widget to be quickly found, enabling the deletion of meeting members waiting to be activated in the waiting space, thereby improving the efficiency of content sharing.

[0118] In one embodiment, when the host terminal switches between meeting members who are currently sharing content, a preview function is provided to the host member so that they can quickly switch to the required content to be shared. In this embodiment, the content sharing method further includes the step of displaying the content to be shared corresponding to each meeting member within a predetermined adjacent range of each member awaiting activation.

[0119] Content requiring sharing from meeting members awaiting activation is displayed as a thumbnail within a designated adjacent area of ​​the meeting member. The host member can preview the content requiring sharing from the meeting member awaiting activation and decide whether or not to display that content in the content display area of ​​the meeting interface.

[0120] In this embodiment, the host terminal displays the content to be shared corresponding to each meeting member awaiting activation within a predetermined adjacent range. This allows the host terminal to determine whether or not the content to be shared for the meeting member awaiting activation needs to be displayed in the content display area of ​​the meeting interface, using the content to be shared displayed within the predetermined adjacent range as reference material, and to quickly switch to the necessary content to be shared.

[0121] In one embodiment, the content sharing method further includes the steps of displaying first prompt information in response to a content sharing request made by a meeting member participating in the meeting, and adding and displaying the meeting member who made the content sharing request in the sharing guidance area in response to an permission operation for the first prompt information.

[0122] A content sharing request is sent from a participant's terminal to the server, and then forwarded from the server to the host terminal. It is used to request the host terminal to agree to allow the meeting member who initiated the content sharing request to enter the waiting area, and to request the server to share the content that the meeting member who initiated the content sharing request needs to be shared with the other meeting members.

[0123] In some embodiments, for the first meeting member to initiate a content sharing request, the server does not need to directly add that member to the waiting area and display the first prompt information on the host terminal's meeting interface. For subsequent meeting members who initiate a content sharing request, the server displays the first prompt information on the host terminal's meeting interface and, in response to the permission operation for the first prompt information, adds the meeting members waiting to share content to the waiting area.

[0124] The permission operation for the first prompt information on the host terminal means that the host terminal has reviewed the content sharing request and passed the review.

[0125] In some embodiments, the first prompt information is used to prompt the host terminal to perform an action of granting or denying permission to a meeting member who has initiated a content sharing request. The first prompt information includes instructions, a grant action widget, and a deny action widget. Here, the instructions are used to display what the host terminal needs to decide. When the host terminal triggers the grant action widget, it indicates that it agrees to the instructions in the first prompt information and has passed the review of the content sharing request. When the host terminal triggers the deny action widget, it indicates that it does not agree to the instructions in the first prompt information and has not passed the review of the content sharing request.

[0126] For example, Figure 13 is a schematic diagram of the first prompt information in one embodiment, where the instruction of the first prompt information is "Member A has requested screen sharing. Do you agree to enter the waiting space?", the corresponding permission operation widget is the "Yes" widget in Figure 13, and the corresponding denial operation widget is the "No" widget in Figure 13. When the host terminal triggers "Yes" in Figure 13, the host terminal displays meeting member A, who initiated the content sharing request, in the sharing guidance area.

[0127] In this embodiment, the host terminal responds to a content sharing request made by a meeting member participating in the meeting by displaying first prompt information, and in response to an permission operation for the first prompt information, adds and displays the meeting member who made the content sharing request in the sharing guidance area. In this process, the host terminal determines which meeting members will enter the waiting space based on the first prompt information, and can refuse to allow meeting members who are not participating in the meeting or who do not need to perform content sharing during the meeting to enter the waiting space, thereby improving the efficiency of content sharing.

[0128] In one embodiment, the content sharing request method further includes the steps of: displaying a second prompt information to instruct the current content sharing to activate other meeting members awaiting activation when the current content sharing has ended; and, in response to a switch operation to the second prompt information, detecting an activation operation for one of the meeting members awaiting activation, and, if an activation operation is detected, switching to and displaying the content to be shared for the meeting member specified by the activation operation.

[0129] The current content sharing has ended when, specifically, a meeting member who was sharing content finishes sharing their content, or when the host terminal removes the meeting member who was sharing content from the waiting area. After the current content sharing has ended, the meeting member who finished sharing content will no longer be displayed in the host terminal's sharing notification area.

[0130] In some embodiments, the second prompt information includes instructions prompting the host terminal to activate other meeting members awaiting activation, a confirmation widget, and a rejection widget. The instructions are used to display what the host terminal needs to decide. When the host terminal triggers the confirmation widget, it indicates that it agrees to the instructions in the second prompt information; when the host terminal triggers the rejection widget, it indicates that it does not agree to the instructions in the second prompt information.

[0131] In some embodiments, the switching operation for the second prompt information refers to the operation in which the host terminal, based on the instructions in the second prompt information, triggers the confirmation widget among the confirmation widget and reject widget in the second prompt information. For example, Figure 14 is a schematic diagram of the second prompt information in one embodiment, where the instructions of the second prompt information in Figure 14 are "Current content sharing has ended. Please activate other meeting members waiting for activation," the corresponding confirmation widget is the "Yes" widget in Figure 14, and the reject widget is the "No" widget in Figure 14. The switching operation for the second prompt information in Figure 14 refers to the operation of selecting and switching to the "Yes" widget among the "Yes" widget or "No" widget in Figure 14. When the "Yes" widget in Figure 14 is triggered, the host member performs an activation operation for one of the member members waiting for activation in the waiting space, and the host terminal detects the activation operation for one of the member members waiting for activation in the host member's waiting space. When the "No" widget in Figure 14 is triggered, the current content requiring sharing is paused, the host member does not perform the activation operation for any of the members waiting for activation in the waiting space, and the meeting enters a paused state.

[0132] Specifically, when the current content sharing ends, the host terminal displays a second prompt, and the host member follows the instructions in the second prompt. If the host terminal triggers the confirmation widget in the second prompt, the host member performs an activation operation for one of the member members waiting for activation in the waiting space. When the host terminal detects an activation operation for one of the member members waiting for activation in the host member's waiting space, it displays the content that needs to be shared for the meeting member specified in the activation operation in the host terminal's content display area. If the host terminal triggers the reject widget in the second prompt, the host member does not perform an activation operation for one of the member members waiting for activation in the waiting space, and the meeting enters a paused state.

[0133] In one embodiment, Figure 15 is a schematic diagram of the operation logic of the host terminal in one embodiment. As can be seen by referring to Figure 15, the host terminal has the following operations: open a waiting space, allow meeting members participating in a meeting to enter the waiting space, activate any meeting member in the waiting space, remove any meeting member from the waiting space, and close the waiting space.

[0134] When opening a waiting space, if the host terminal has not opened one, meeting members will share content using the existing method. In other words, content sharing cannot be achieved until the participant currently sharing their screen finishes sharing. When the host terminal opens a waiting space, it can seamlessly switch between multiple items that need to be shared.

[0135] In the process of allowing meeting members to enter a waiting area, the host member on the host terminal determines whether or not to allow a particular meeting member to enter the waiting area.

[0136] In the operation to activate any meeting member in the waiting area, the host member on the host terminal activates the desired meeting member in the waiting area. Only one meeting member can be activated at a time; other meeting members can only remain in a waiting state for activation.

[0137] In the operation of removing any meeting member from the waiting space, the host member on the host terminal can remove meeting members that are awaiting activation or have already been activated from the waiting space.

[0138] When closing a waiting space, the host member of the host terminal can close the waiting space. When the waiting space is closed, all shared content for meeting members awaiting activation is closed, while shared content for activated meeting members can continue to be shared.

[0139] In this embodiment, when the current content sharing ends, a second prompt is displayed. The host terminal responds to a host member's switch operation in response to the second prompt and an activation operation for any one of the meeting members waiting for activation in the waiting space, and displays the content to be shared for the meeting member specified in the activation operation in the host terminal's content display area. When the current content sharing ends, the content to be shared for other meeting members waiting for activation is displayed in the content display area. Switching of content to be shared can be achieved without requiring meeting members to start content sharing, improving content sharing efficiency.

[0140] In one embodiment, a content sharing method as shown in Figure 16 is provided, and the case where this method is applied to the participant terminal shown in Figure 1 will be described as an example. This method includes the following steps.

[0141] Step 1602: In response to a content sharing operation triggered in the conference interface, a content sharing request is sent.

[0142] Content sharing refers to the action taken by a meeting member to trigger the content sharing widget on the meeting interface of their terminal. The content sharing widget is a button used to display content that needs to be shared on the participant's terminal.

[0143] Content sharing requests originate from participant terminals. Specifically, they are generated by participant terminals based on content sharing operations triggered by meeting members waiting to share content in the meeting interface, and are used to request the server to share the content.

[0144] In some embodiments, a content sharing request includes the content to be shared and the member information of the meeting member who initiated the content sharing request.

[0145] Specifically, meeting members initiate content sharing operations on the meeting interface of their participating terminals, targeting the content sharing widget on the meeting interface. When a participating terminal detects a content sharing operation initiated by a meeting member, it generates a content sharing request in response, sends the request to the server, and then forwards the request to the host terminal via the server.

[0146] Step 1604: Display the sharing guidance area on the meeting interface, and in the sharing guidance area, display meeting members whose activation status is not activated and who are waiting to share content.

[0147] A meeting member waiting for content sharing to be executed refers to a meeting member who is logged into their participant terminal. When a meeting member waiting for content sharing to be executed enters the waiting space, their initial activation status is "waiting for activation".

[0148] The shared information area on the participant terminal is used to display member information and activation status for meeting members waiting to share content in the meeting's waiting area. For example, the meeting interface for meeting member A displays the content that needs to be shared and is currently being shared in the meeting. As shown in Figure 9, the shared information area displays only the member information and activation status of meeting member A. When the host terminal initiates an activation operation for meeting member A, meeting member A's activation status switches from waiting for activation to activated.

[0149] Specifically, when the host terminal agrees to a content sharing request initiated by a meeting member who is logged into a participant terminal and waiting for content sharing to be performed, and the server adds that meeting member to the waiting space, a sharing guidance area will appear on the participant terminal's meeting interface, and the meeting members waiting for content sharing to be performed who are in the meeting's waiting space will be displayed in the sharing guidance area.

[0150] In some embodiments, if the host terminal has already opened a waiting space and there are no meeting members currently sharing content, the activation status of meeting members waiting to share content, as displayed in the sharing guidance area of ​​the participant terminal, will be "activated." If the host terminal has already opened a waiting space and there are meeting members currently sharing content, the activation status of meeting members waiting to share content on the participant terminal will be "not activated."

[0151] Step 1606: In response to an activation command for meeting members waiting to share content, update the activation status of the meeting members waiting to share content to activated in the sharing guidance area, and perform the sharing of the content to be shared in response to the content sharing request.

[0152] Specifically, the host terminal sends an activation command to the server for meeting members waiting to share content on their participant terminals. The server responds to the activation command by sending the content that needs to be shared for the meeting member specified in the activation command to the participant terminal used by each meeting member, thereby enabling content sharing.

[0153] In some embodiments, if a meeting member waiting to share content is the first meeting member to initiate a content sharing request, they can be automatically added to the waiting space without requiring the host terminal's consent. The activation status of the meeting member waiting to share content automatically switches from the initial "waiting for activation" state to the "activated" state without the host terminal needing to issue an activation command to the meeting member waiting to share content. The activation status of the meeting member waiting to share content is then updated to "activated" in the sharing guidance area of ​​the participant terminal.

[0154] In some embodiments, the shared information area of ​​the participant's terminal may display the content that needs to be shared for meeting members who are waiting to share it.

[0155] In this embodiment, when a meeting member initiates a content sharing operation triggered by the meeting interface, a content sharing request is sent. When the host terminal agrees to the content sharing request from a meeting member logged into the participant terminal and waiting to share content, the participant terminal displays a sharing guidance area on the meeting interface. The sharing guidance area displays the meeting members waiting to share content who are in the meeting's waiting space, and their activation status is "not activated". When the host terminal sends an activation command to the meeting members waiting to share content, the participant terminal responds to the activation command by updating the activation status of the meeting members waiting to share content to "activated" in the sharing guidance area and sharing the content that needs to be shared corresponding to the content sharing request. After the meeting members waiting to share content on the participant terminal enter the waiting space, they can share their content simply by following the activation command sent from the host terminal. In this process, participant terminals do not need to wait for the previous meeting member who was sharing content to finish sharing the content currently being shared, simplifying the content sharing workflow and improving content sharing efficiency.

[0156] In some embodiments, Figure 17 is a schematic diagram of the control logic by which a participant terminal shares content in one embodiment. Specifically, as shown in Figure 17, it includes the following steps.

[0157] Step 1701: A meeting member whose terminal is waiting for content sharing to be executed sends a content sharing request.

[0158] Step 1702: Determine whether the host terminal has opened a standby space. If the host terminal has opened a standby space, execute step 1703. If the host terminal has not opened a standby space, execute step 1711.

[0159] Step 1703: Determine whether the host terminal has allowed meeting members waiting for content sharing to be performed on their terminals to enter the waiting area. If the host terminal has allowed meeting members waiting for content sharing to be performed on their terminals to enter the waiting area, perform Step 1704. If the host terminal has not allowed meeting members waiting for content sharing to be performed on their terminals to enter the waiting area, perform Step 1705.

[0160] Step 1704: Add 1 to the total number of meeting members in the waiting area, and then perform Step 1706.

[0161] Step 1705: Switch the status of meeting members waiting for content sharing to be executed on their terminals to the "not sharing" state.

[0162] Step 1706: Determine whether the total number of meeting members in the waiting area is 1 or not. If the total number of meeting members in the waiting area is 1, perform step 1707. If the total number of meeting members in the waiting area is greater than 1, perform step 1708.

[0163] Step 1707: The activation status of meeting members waiting for content sharing to be executed on their participant terminals changes from "waiting for activation" to "activated," and Step 1710 is executed.

[0164] Step 1708: If the activation status of a meeting member waiting to share content on their terminal is in the "waiting for activation" state, perform Step 1709.

[0165] Step 1709: If the activation status of a meeting member waiting to share content is in the "waiting for activation" state, and the meeting member waiting to share content on a participant terminal sends a content close request, or the host terminal sends a delete command for the meeting member waiting to share content on a participant terminal, or the host terminal sends a close command for the waiting space, then step 1705 is executed.

[0166] Step 1710: If the activation status of a meeting member waiting to share content is activated, and the meeting member waiting to share content on a participant terminal sends a content close request, or if the host terminal sends a delete command to the meeting member waiting to share content on a participant terminal, then step 1705 is executed.

[0167] Step 1711: Determine if there are any meeting members currently sharing content. If there are any meeting members currently sharing content, perform Step 1705. If there are no meeting members currently sharing content, perform Step 1707.

[0168] In one embodiment, after the step of issuing a content sharing request, the method further includes the step of issuing a third prompt indicating that the content to be shared included in the content sharing request is currently awaiting review, and, if the review is passed, the meeting members awaiting content sharing are permitted to enter a waiting space.

[0169] Specifically, when the server receives a content sharing request from a participant terminal, it forwards the content sharing request to the host terminal. The host terminal displays a first prompt and reviews the content to be shared in the content sharing request. While the host terminal is reviewing the content to be shared, the participant terminal displays a third prompt, and meeting members logged into the participant terminal who are waiting for content sharing to be executed wait. If the host terminal's review is passed, the host terminal sends an permission operation to the first prompt information and generates a permission message based on the permission operation. The server forwards the permission message to the participant terminal, informing the meeting members logged into the participant terminal who are waiting for content sharing to be executed that they are permitted to enter the waiting space. If the host terminal's review is not passed, the host terminal sends a rejection operation to the first prompt information and generates a rejection message based on the rejection operation. The server forwards the rejection message to the participant terminal, informing the meeting members logged into the participant terminal who are waiting for content sharing to be executed that they are denied entry to the waiting widget.

[0170] Please refer to Figure 18, a schematic diagram of the third prompt information in one embodiment. The instruction of the third prompt information is, "Please wait until the host member moves your content to be shared to the waiting space."

[0171] In some embodiments, the third prompt information further includes a confirmation widget and a rejection widget to acknowledge the third prompt information. If a participant terminal detects a trigger operation on the confirmation widget in the third prompt information, the meeting members waiting for the participant terminal to perform content sharing will wait. If a participant terminal detects a trigger operation on the rejection widget in the third prompt information, the participant terminal will withdraw the content sharing request made by the meeting members waiting for content sharing to perform.

[0172] In this embodiment, the participant terminal displays a third prompt indicating that the content to be shared included in the content sharing request is currently awaiting review. If the review is successful, the meeting members waiting to share the content are allowed to enter the waiting space. In this process, the host terminal can determine which meeting members can enter the waiting space and can refuse to allow meeting members who are not participating in the meeting or who do not need to perform content sharing during the meeting to enter the waiting space, thereby improving the efficiency of content sharing.

[0173] In one embodiment, the method further includes the steps of: displaying a fourth prompt in response to a command to remove a meeting member waiting to share content, indicating that the meeting member waiting to share content has been removed from the waiting space; and displaying a fifth prompt in response to a command to close the waiting space, indicating that the waiting space has been closed, and continuing to display the content to be shared if the activation status of the meeting member waiting to share content is activated.

[0174] A delete command is generated based on a trigger operation by the host terminal on a delete widget within a predetermined adjacent range of meeting members waiting to share content on the meeting interface. For example, when a host member triggers the delete widget of a meeting member waiting to share content on the host terminal's meeting interface, the host terminal detects the trigger operation on the delete widget of the meeting member waiting to share content, generates a delete command for the meeting member waiting to share content based on the trigger operation, and forwards the delete command via the server to the participant terminal used by the meeting member waiting to share content.

[0175] In some embodiments, the fourth prompt information includes an instruction and a close widget, which is used to close the fourth prompt information. For example, Figure 19 is a schematic diagram of the fourth prompt information in one embodiment. The instruction of the fourth prompt information is "Your content awaiting activation has been removed from the waiting space by the host member," and the corresponding close widget is the "Confirm" widget in Figure 19. When a meeting member waiting for content sharing to be executed on their terminal triggers the "Confirm" widget in Figure 19, the fourth prompt information is closed.

[0176] The close command is used to instruct the server to close the waiting space, and the close command is generated based on an action by the host terminal that triggers the waiting space close widget. When the waiting space is closed, the host terminal does not display each meeting member in the waiting space, and for meeting members whose activation status is activated, it continues to display the content that needs to be shared in the meeting content display area of ​​the host terminal, and further displays a fifth prompt information on the meeting interface of the participant terminal used by each meeting member whose activation status is pending activation.

[0177] In some embodiments, the fifth prompt information includes an instruction and a close widget, which is used to close the fifth prompt information. For example, Figure 20 is a schematic diagram of the fifth prompt information in one embodiment. If the activation status of a meeting member waiting for content sharing to be executed on their participant terminal is "waiting for activation," the instruction of the fifth prompt information is "The host member has closed the waiting space. Your waiting content for activation has been closed." The corresponding close widget is the "Confirm" widget in Figure 20. When a meeting member waiting for content sharing to be executed on their participant terminal triggers the "Confirm" widget in Figure 20, the fifth prompt information is closed.

[0178] In some embodiments, if the activation status of a meeting member waiting for content sharing to be executed on their terminal is already activated, the message in the fifth prompt may be "The host member has closed the waiting space. Your activated shared screen will not be affected."

[0179] Specifically, when a participant terminal receives a delete command for a meeting member waiting to share content, it responds to the delete command by displaying a fourth prompt on the participant terminal's meeting interface. If the participant terminal receives a close command for the waiting space and the activation status of the meeting member waiting to share content on the participant terminal is "waiting for activation," it displays a fifth prompt on the participant terminal's meeting interface. If the participant terminal receives a close command for the waiting space and the activation status of the meeting member waiting to share content on the participant terminal is "activated," the content requiring sharing continues to be displayed in the host terminal's meeting content display area.

[0180] In this embodiment, when a meeting member waiting for content sharing to be executed on a participant terminal is removed from the host terminal, a fourth prompt is displayed, and when the waiting space is closed, the participant terminal displays a fifth prompt. Furthermore, if the activation status of a meeting member waiting for content sharing to be executed is activated, the content to be shared continues to be displayed in the content display area. In the above process, even if the waiting space is closed, meeting members whose activation status is activated are not affected by the closure of the waiting space, and the content to be shared continues to be displayed. This avoids the problem that the closure of the waiting space would close the session for activated meeting members, thereby affecting the efficiency of content sharing.

[0181] A detailed embodiment of the content sharing method is provided. Please refer to Figure 21, which is a detailed sequence diagram of the content sharing method in one embodiment. Specifically, it includes the following steps.

[0182] 1. The server receives an open command for a standby space sent from the host terminal and opens the standby space in response to the open command.

[0183] 2. The participant terminal sends a content sharing request to the server in response to a content sharing operation triggered in the conference interface.

[0184] 3. The participant terminal displays a third prompt indicating that the content to be shared included in the content sharing request is currently awaiting review.

[0185] 4. The server receives a content sharing request from a meeting member participating in the meeting and identifies the meeting member who sent the request as a meeting member waiting for content sharing to be performed. The content sharing request includes content that needs to be shared.

[0186] 5. The content sharing request is forwarded to the host terminal, and the host terminal is instructed to review the content to be shared in the content sharing request.

[0187] 6. The host terminal displays the first prompt information in response to a content sharing request initiated by a meeting member participating in the meeting. The host terminal, in response to the permission operation of the first prompt information, generates a review result indicating that the review has been passed and feeds it back to the server.

[0188] 7. If the review is successful, the server will add the meeting members waiting to share content to the waiting area.

[0189] 8. If the review is successful, the participant's terminal will display a sharing guidance area on the conference interface. The sharing guidance area will display conference members waiting to share content, and the activation status of these members will be "not activated".

[0190] 9. The server determines the total number of meeting members in the current waiting space. If the total is 1, it directly sends the content to be shared by the meeting member who initiated the content sharing request to the participant terminal used by each meeting member participating in the meeting. If the total is not 1, the server responds to the activation command sent from the host terminal by identifying one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and sends the content to be shared by the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting.

[0191] 10. The host terminal displays the meeting members in the meeting waiting area and the activation status of each meeting member in the shared information area. The activation status includes at least "waiting for activation" and "activated".

[0192] 11. When the host terminal receives an activation request for any one of the meeting members awaiting activation, it displays the content that needs to be shared by the meeting member specified in the activation request in the content display area, and updates the activation status of the meeting member specified in the activation request to "activated" in the sharing guidance area.

[0193] 12. When the server receives a content close request from a participant terminal, it removes the meeting member who made the content close request from the waiting area. If the meeting member who made the content close request is currently sharing content, the current content sharing is terminated.

[0194] 12. The host terminal removes the meeting member who initiated the content close request from the waiting area in the shared guidance area.

[0195] 13. The host terminal displays the activation status of each meeting member within a predetermined adjacent range of that meeting member, and displays a delete widget within a predetermined adjacent range of each meeting member awaiting activation. The delete widget is used to remove the meeting member from the waiting space.

[0196] 14. If the server receives a delete command from the host terminal for any of the displayed meeting members, it will respond to the delete command by removing the meeting member specified in the delete command from the waiting space. If the meeting member specified in the delete command is a meeting member currently sharing content, the current content sharing will be terminated.

[0197] 15. When the current content sharing ends, the host terminal displays a second prompt to instruct it to activate other meeting members awaiting activation. The host terminal then responds to the switch operation in response to the second prompt to detect an activation operation for one of the meeting members awaiting activation in the waiting space. If an activation operation is detected, it switches to and displays the content that needs to be shared for the meeting member specified by the activation operation.

[0198] 16. In response to the command to remove a meeting member waiting to share content, the participant terminal displays a fourth prompt indicating that the meeting member waiting to share content has been removed from the waiting space.

[0199] 17. When the server receives a close command for a standby space sent from the host terminal, it responds to the close command by closing the standby space. It closes the shared content of meeting members that were in the activation waiting state within the standby space, while retaining the sharing operation for shared content of meeting members that were in the activated state within the standby space.

[0200] 18. When a participant terminal receives a close command for the waiting space, it displays a fifth prompt indicating that the waiting space has been closed. If the activation status of the meeting members waiting to share content is activated, the content to be shared continues to be displayed in the content display area.

[0201] In this embodiment, the server switches the meeting member currently sharing content based on the host terminal's activation command. In the switching process, there is no need to wait for the meeting member currently sharing content to stop sharing, nor is there a need to wait for the meeting member waiting to share content to start sharing. This enables seamless switching of shared content during a meeting, simplifies the sharing operation flow during a meeting, and improves the efficiency of content sharing.

[0202] In the flowcharts of the above embodiments, each step is shown sequentially according to the arrows, but these steps do not necessarily have to be performed in the order indicated by the arrows. Unless otherwise explicitly stated herein, there are no strict restrictions on the execution order of these steps, and they may be performed in other orders. Furthermore, at least some of the steps in the flowcharts of each of the above embodiments may include multiple steps or stages, and these steps or stages do not necessarily have to be completed at the same time; they may be performed at different times. The execution order of these steps or stages also does not necessarily have to be in order; they may be performed in rotation or alternately with other steps, or at least some of the steps or stages in other steps.

[0203] Based on a similar inventive concept, embodiments of the present application further provide a content sharing device for realizing a content sharing method relating to the server described above. The means of implementation provided by this device for solving the problem are similar to the means of implementation described in the above method, and the specific limitations in the embodiments of one or more content sharing devices provided below refer to the limitations on the above content sharing method, and are therefore not described again here.

[0204] In one embodiment, a content sharing device as shown in Figure 22 is provided. The device includes the following modules.

[0205] The add-on module 2401 is used to respond to content sharing requests initiated by meeting members participating in a meeting, identify meeting members waiting to share content, and add those members to the waiting area.

[0206] The feedback module 2402 is used to provide feedback to the conference host terminal regarding the conference members in the waiting space and to instruct the host terminal to display each conference member in the waiting space.

[0207] The shared module 2403 is used to respond to an activation command sent from the host terminal, identify one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and send the shared content of the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting.

[0208] In one embodiment, the additional module 2401 is further used to open a standby space in response to an open command to open a standby space sent from the host terminal.

[0209] In one embodiment, the feedback module 2402 further receives a content sharing request containing content to be shared, sent by a meeting member participating in the meeting, determines that the meeting member who sent the content sharing request is a meeting member waiting for content sharing to be performed, forwards the content sharing request to the host terminal, instructs the host terminal to review the content to be shared in the content sharing request, and, if the review is successful, adds the meeting member waiting for content sharing to be performed to the waiting space.

[0210] In one embodiment, the feedback module 2402 is further used to identify the total number of meeting members in the current waiting space, and if the total is 1, to send the content to be shared by the meeting member who initiated the content sharing request directly to the participant terminal used by each meeting member participating in the meeting.

[0211] In one embodiment, the shared module 2403 is further used to remove the meeting member who initiated the content close request from the waiting space when it receives a content close request, and to terminate the current content sharing if the meeting member who initiated the content close request is a meeting member currently sharing content.

[0212] In one embodiment, the additional module 2401 is further used to add meeting members waiting to share content to the waiting space and to arrange the meeting members in the waiting space according to a predetermined arrangement scheme.

[0213] In one embodiment, the additional module 2401 is further used to terminate the current content sharing when it receives a content close request from a meeting member currently sharing content, and to automatically send the content awaiting sharing from the next meeting member, whose sequence is positioned after the meeting member currently sharing content, to the participant terminal used by each meeting member participating in the meeting.

[0214] In one embodiment, the sharing module 2403 is further used to respond to a delete command sent from the host terminal by identifying one of the meeting members specified in the delete command from among the meeting members displayed on the host terminal, deleting the meeting member specified in the delete command from the waiting space, and terminating the current content sharing if the meeting member specified in the delete command is a meeting member currently sharing content.

[0215] In one embodiment, the shared module 2403 is further used to close the standby space in response to a close command sent from the host terminal, to close the shared content of meeting members that were in an activation waiting state within the standby space, and to maintain the sharing operation of shared content of meeting members that were in an activated state within the standby space.

[0216] Based on a similar inventive concept, the present embodiment further provides a content sharing device for realizing the content sharing method relating to the host terminal described above. Since the implementation measures for solving the problem provided by this device are similar to those described in the above method, the specific limitations in the one or more embodiments of the content sharing device provided below can be referenced to the limitations on the above content sharing method and will not be described again here.

[0217] In one embodiment, a content sharing method as shown in Figure 23 is provided. The device includes the following modules.

[0218] The first display module 2301 is a meeting interface for a conference, and is used to display a meeting interface that includes a content display area and a shared guidance area.

[0219] The second display module 2302 is used to display in the shared guidance area the meeting members waiting to share content, and the activation status of each meeting member, which includes at least "waiting for activation" and "activated".

[0220] The third display module 2303 is used to respond to an activation operation for any one of the meeting members awaiting activation by displaying the content that needs to be shared for the meeting member specified in the activation operation in the content display area, and by updating the activation status of the meeting member specified in the activation operation to "activated" in the sharing guidance area.

[0221] In one embodiment, the second display module 2302 is further used in the shared guidance area to display meeting members who are in the meeting waiting space for each item, and to display the activation status of each meeting member within a predetermined adjacent range of that meeting member.

[0222] In one embodiment, the second display module 2302 is further used to display the activation status of each meeting member within a predetermined adjacent range of that meeting member, and to display a delete widget for removing the meeting member from the waiting space within a predetermined adjacent range of each meeting member waiting for activation.

[0223] In one embodiment, the second display module 2302 is further used to display the corresponding shared content within a predetermined adjacent range of each meeting member awaiting activation.

[0224] In one embodiment, the third display module 2303 is further used to display first prompt information in response to a content sharing request made by a meeting member participating in the meeting, and to add and display the meeting member who made the content sharing request in the sharing guidance area in response to an permission operation for the first prompt information.

[0225] In one embodiment, the third display module 2303 is further used to display a second prompt information to instruct other meeting members awaiting activation to activate when the current content sharing ends, and to detect an activation operation for any one of the meeting members awaiting activation in the waiting space in response to a switch operation for the second prompt information, and, if an activation operation is detected, to switch and display the content to be shared for the meeting member specified by the activation operation.

[0226] Based on a similar inventive concept, the present embodiment further provides a content sharing device for realizing the content sharing method for the above-mentioned participant terminal. Since the implementation measures for solving the problem provided by this device are similar to those described in the above method, the specific limitations in the one or more embodiments of the content sharing device provided below can be understood by referring to the limitations on the above-mentioned content sharing method, and therefore will not be repeated here.

[0227] In one embodiment, a content sharing device as shown in Figure 24 is provided. The device includes the following modules.

[0228] The request sending module 2401 is used to send a content sharing request in response to a content sharing operation triggered in the conference interface.

[0229] The fourth display module 2402 is used to display a sharing guidance area on the conference interface, and to display conference members who are waiting to share content and whose activation status is not yet activated within the sharing guidance area.

[0230] The fifth display module 2403 is used to respond to an activation command for a meeting member waiting to share content, to update the activation status of the meeting member waiting to share content to "activated" in the sharing guidance area, and to perform the sharing of the content to be shared in response to the content sharing request.

[0231] In one embodiment, the fourth display module 2402 is further used to display a third prompt information indicating that the content to be shared included in the content sharing request is currently awaiting review, and if the review is successful, the meeting members waiting to share the content are allowed to enter the waiting area.

[0232] In one embodiment, the fifth display module 2403 is further used to display a fourth prompt in response to a command to remove a meeting member waiting to share content, indicating that the meeting member waiting to share content has been removed from the waiting space; to display a fifth prompt in response to a command to close the waiting space, indicating that the waiting space has been closed; and to continue displaying the content to be shared if the activation status of the meeting member waiting to share content is activated.

[0233] All or some of the modules in the above-described content sharing device can be implemented by software, hardware, or a combination thereof. Each of the above modules may be embedded in the processor of the computer device, in separate hardware form, or stored in the memory of the computer device in software form so that the processor can call it and perform the operations corresponding to each of the above modules.

[0234] In one embodiment, a computer device is provided. The computer device may be a server. Its internal structure may be as shown in Figure 25. The computer device includes a processor, memory, an input / output interface (abbreviated as I / O), and a communication interface. The processor, memory, and I / O interface are connected via a system bus, and the communication interface is connected to the system bus via the I / O interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal storage. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal storage provides an execution environment for the operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store content that needs to be shared. The I / O interface of the computer device is used for information exchange between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via a network. When the computer program is executed by the processor, it implements a content sharing method.

[0235] In one embodiment, a computer device is provided. The computer device may be a terminal. Its internal structure may be as shown in Figure 26. The computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal storage. The non-volatile storage medium stores an operating system and computer programs. The internal storage provides an execution environment for the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used for information exchange between the processor and external devices. The communication interface of the computer device is used for wired or wireless communication with an external terminal. The wireless method is implemented by Wi-Fi®, cellular network, NFC (Near Field Communication), or other technology. When the computer program is executed by the processor, it implements a content sharing method. The display unit of the computer equipment is used to form a visible screen and may be a display, projection device, or virtual reality imaging device. The display may be a liquid crystal display or an E-Ink® display. The input device of the computer equipment may be a touch layer covering the display, or a push button, trackball, or touch control panel provided on the case of the computer equipment. It may also be an external keyboard, touch control panel, or mouse.

[0236] As those skilled in the art will understand, the structures shown in Figures 25 and 26 are merely block diagrams of the structures of the parts related to the method of the present invention and do not limit the computer equipment to which the method of the present invention is applied. Actual computer equipment may contain more or fewer components than those shown, or any combination of components, or the arrangement of components may differ.

[0237] In one embodiment, a computer device is provided. The computer device includes memory and a processor, the memory storing a computer program, and when the computer program is executed by the processor, the steps in each of the above embodiment of the method are realized.

[0238] In one embodiment, a computer-readable storage medium is provided. A computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps in each of the above embodiment of the method are realized.

[0239] In one embodiment, a computer program product is provided. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps in each of the above-described embodiment of the method are realized.

[0240] Furthermore, all user information (including but not limited to user device information and user personal information) and data (including but not limited to data for analysis, stored data, and displayed data) relating to this application must have undergone user authentication or sufficient authentication from all parties involved, and the collection, use, and processing of related data must comply with the relevant regulations.

[0241] As those skilled in the art will understand, all or some of the flows in the methods of the above embodiments can be implemented by instructing the relevant hardware with a computer program. The computer program is stored in a non-volatile computer-readable storage medium, and when the computer program is executed, the flows of each of the above embodiment of the method are included. All references to memory, databases, or other media used in each embodiment provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external high-speed buffer memory, etc. As a non-restrictive explanation, RAM may be of multiple forms, such as SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory). The database relating to each embodiment provided in this application may include at least one of relational databases and non-relational databases. Non-relational databases include, but are not limited to, blockchain-based distributed databases. The processor relating to each embodiment provided in this application may be, but are not limited to, a general-purpose processor, CPU, graphic processor, digital signal processor, programmable logic device, quantum computing-based data processing logic device, etc.

[0242] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described, but as long as there is no contradiction in these combinations of technical features, they should be considered to be within the scope of this specification.

[0243] The above embodiments represent only a few embodiments of the present application and, although described in a relatively specific and detailed manner, should not be understood as limitations on the scope of the patent of the present invention. Those skilled in the art may make some further modifications and improvements without departing from the spirit of the present application, and it should be noted that all of these fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent should be based on the "claims."

Claims

1. A content sharing method performed by a server, The process involves responding to content sharing requests initiated by meeting members, identifying meeting members waiting for content sharing to be performed, and adding those members to a waiting area. The steps include: feeding back the meeting members in the waiting space to the host terminal of the meeting, and instructing the host terminal to display each meeting member in the waiting space; The process includes the steps of: responding to an activation command transmitted from the host terminal, identifying one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and transmitting the shared content of the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting; Content sharing methods.

2. The aforementioned step of responding to a content sharing request initiated by a meeting member participating in the meeting, identifying meeting members waiting to share content, and adding those meeting members to the waiting space, The process involves receiving a content sharing request containing content to be shared from a meeting member participating in the meeting, and determining that the meeting member who sent the content sharing request is a meeting member waiting for content sharing to be performed. The steps include: forwarding the content sharing request to the host terminal and instructing the host terminal to review the content to be shared in the content sharing request; If the review is successful, the step of adding the meeting members waiting to share the content to the waiting space is included, The content sharing method according to claim 1.

3. The aforementioned content sharing method further, The steps include: adding meeting members waiting to share content to the waiting space, and then identifying the total number of meeting members currently in the waiting space; If the total number is 1, the process includes the step of directly sending the content to be shared by the meeting member who initiated the content sharing request to the participant terminal used by each meeting member participating in the meeting. The content sharing method according to claim 1 or 2.

4. The aforementioned content sharing method further, When a content close request is received, the steps include removing the meeting member who initiated the content close request from the waiting space, The process includes the step of ending the current content sharing if the meeting member who initiated the content close request is currently sharing content. A content sharing method according to any one of claims 1 to 3.

5. If multiple content sharing requests exist, the step of adding meeting members waiting for content sharing to the waiting space is: Steps include adding multiple meeting members waiting to share content to the waiting area, The step of arranging the meeting members in the waiting space in a predetermined arrangement method, A content sharing method according to any one of claims 1 to 4.

6. The aforementioned content sharing method further, When a content close request is received from a meeting member currently sharing content, the current content sharing is terminated, and the content awaited for sharing by the next meeting member, whose sequence is positioned after the meeting member currently sharing content, is automatically sent to the participant terminal used by each meeting member participating in the meeting. The content sharing method according to claim 5.

7. The aforementioned content sharing method further, In response to a deletion command transmitted from the host terminal, the host terminal identifies one of the meeting members specified in the deletion command from among the meeting members displayed on the host terminal, and deletes the meeting member specified in the deletion command from the waiting space. The process includes the step of terminating the current content sharing if the meeting member specified in the deletion command is a meeting member currently sharing content. A content sharing method according to any one of claims 1 to 6.

8. A content sharing method performed by a host terminal, A meeting interface for a meeting, comprising the steps of displaying the meeting interface which includes a content display area and a shared guidance area, The steps include displaying in the aforementioned shared guidance area the meeting members who are waiting to share content, and the activation status of each meeting member, which includes at least "waiting for activation" and "activated," The process includes the steps of: in response to an activation operation for any one of the meeting members awaiting activation, displaying the content that needs to be shared for the meeting member specified in the activation operation in the content display area, and updating the activation status of the meeting member specified in the activation operation to "activated" in the sharing guidance area; Content sharing methods.

9. The step of displaying the meeting members waiting to share content and the activation status of each meeting member in the shared guidance area is as follows: The steps include displaying the meeting members waiting to share content in the aforementioned shared guidance area, item by item, and The process includes the step of displaying the activation status of each meeting member within a predetermined adjacent area of ​​that meeting member, The aforementioned content sharing method further, A step to display a delete widget within a predetermined adjacent range of each meeting member awaiting activation, for removing the meeting member from the waiting space, The step includes displaying the content to be shared corresponding to each meeting member awaiting activation within a predetermined adjacent area of ​​each member, The content sharing method according to claim 8.

10. The aforementioned content sharing method further, The steps include: displaying a first prompt in response to a content sharing request initiated by a meeting member participating in the meeting; The process includes the step of adding and displaying the meeting member who initiated the content sharing request in the sharing guidance area in response to the permission operation for the first prompt information, The content sharing method according to claim 8 or 9.

11. The aforementioned content sharing method further, If the current content sharing ends, a second prompt will be displayed to instruct other meeting members who are waiting to be activated to activate. The process includes the steps of: detecting an activation operation for any one of the meeting members awaiting activation in response to a switch operation for the second prompt information; and, if an activation operation is detected, switching to and displaying the shared content for the meeting member specified by the activation operation. A content sharing method according to any one of claims 8 to 10.

12. A content sharing method performed by a participant terminal, The steps include: sending a content sharing request in response to a content sharing operation triggered in the meeting interface; The steps include: displaying a sharing guidance area on the meeting interface, and displaying meeting members whose activation status is not activated and who are waiting to share content in the sharing guidance area; The process includes the steps of: in response to an activation command for a meeting member waiting to share content, updating the activation status of the meeting member waiting to share content to "activated" in the sharing guidance area, and then sharing the content to be shared corresponding to the content sharing request. Content sharing methods.

13. After the step of issuing a content sharing request, the content sharing method further: The process includes a step of displaying a third prompt indicating that the content to be shared included in the aforementioned content sharing request is currently awaiting review, and if the review is successful, the meeting members waiting to share the content are allowed to enter the waiting area. The content sharing method according to claim 12.

14. The aforementioned content sharing method further, In response to the command to remove a meeting member waiting to share content, the step of displaying a fourth prompt indicating that the meeting member waiting to share content has been removed from the waiting space, The steps include: displaying a fifth prompt indicating that the waiting space has been closed in response to a close command for the waiting space, and continuing to display the content to be shared if the activation status of the meeting members waiting to share the content is activated; The content sharing method according to claim 12 or 13.

15. An additional module for responding to content sharing requests initiated by meeting members, identifying meeting members waiting for content sharing to be performed, and adding those members to a waiting space. A feedback module for providing feedback to the host terminal of the meeting regarding the meeting members in the waiting space, and for instructing the host terminal to display each meeting member in the waiting space, A sharing module is included for responding to an activation command transmitted from the host terminal, identifying one of the meeting members specified in the activation command from among the meeting members displayed on the host terminal, and transmitting the shared content of the meeting member specified in the activation command to the participant terminal used by each meeting member participating in the meeting. Content sharing device.

16. A meeting interface for a meeting, comprising a first display module for displaying the meeting interface, which includes a content display area and a shared guidance area, The shared guidance area includes a second display module for displaying meeting members waiting to share content, and the activation status of each meeting member, which includes at least an activation waiting state and an activated state. The system includes a third display module that, in response to an activation operation for any one of the meeting members awaiting activation, displays the content that needs to be shared by the meeting member specified in the activation operation in the content display area, and updates the activation status of the meeting member specified in the activation operation to "activated" in the sharing guidance area. Content sharing device.

17. A request sending module for sending a content sharing request in response to a content sharing operation triggered in the conference interface, A fourth display module is provided for displaying a sharing guidance area on the aforementioned meeting interface, and for displaying meeting members whose activation status is not activated and who are waiting to share content, within the sharing guidance area. The system includes a fifth display module that, in response to an activation command for a meeting member waiting to share content, updates the activation status of the meeting member waiting to share content to "activated" in the sharing guidance area, and performs the sharing of the content to be shared corresponding to the content sharing request. Content sharing device.

18. The system includes memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps of the content sharing method described in any one of claims 1 to 14 are realized. Computer equipment.

19. A computer program is stored, and when the computer program is executed by a processor, the steps of the content sharing method described in any one of claims 1 to 14 are realized. Computer-readable storage medium.

20. A computer program is included, and when the computer program is executed by a processor, the steps of the content sharing method described in any one of claims 1 to 14 are realized. Computer program products.

Images