Conference object management method and apparatus, electronic device, and storage medium

Abstract

Embodiments of the present application disclose a conference object management method and device, electronic equipment and a storage medium. Embodiments of the present application can create a target conference in a first client, the target conference including at least one object. When the opening condition of the target conference is triggered, the conference invitation information of the target conference is sent to the second client corresponding to the object through the message channel of the first client, and the object list of the target conference is created, the object list including at least the object with the conference invitation state of not joining the conference. The response information of the second client to the conference invitation information is obtained. The conference invitation state of the object in the object list is updated according to the response information. The scheme can efficiently manage the objects not joining the conference, thereby improving the management efficiency and use experience of the conference.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically to a method, apparatus, electronic device, and storage medium for managing meeting participants. Background Technology

[0002] With the widespread adoption of digitalization and networking, online meetings have become a common form of meeting. Participants can be invited to join a meeting, enabling them to participate online.

[0003] In the process of researching and practicing related technologies, the inventors of this application discovered that while it is possible to invite participants to join a meeting, the invited participants may not be able to join immediately for various reasons. Furthermore, the current management efficiency for non-participants in meetings is low, which affects both the management and use of the meeting. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for managing meeting participants, which can efficiently manage non-participating participants in a meeting, thereby improving meeting management efficiency and user experience.

[0005] This application provides a method for managing meeting participants, including:

[0006] A target meeting is created in the first client, the target meeting comprising at least one object;

[0007] When the conditions for starting the target meeting are triggered, the meeting invitation information of the target meeting is sent to the second client corresponding to the object through the message channel of the first client, and the object list of the target meeting is created. The object list includes at least objects whose meeting invitation status is "not yet joined".

[0008] Obtain the response information from the second client in response to the meeting invitation information;

[0009] The meeting invitation status of the objects in the object list is updated based on the response information.

[0010] Accordingly, embodiments of this application also provide a management device for meeting participants, including:

[0011] A creation unit is used to create a target meeting in a first client, the target meeting comprising at least one object;

[0012] The first sending unit is used to send the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client when the opening condition of the target meeting is triggered, and to create a list of objects of the target meeting, the list of objects including at least objects whose meeting invitation status is not yet joined.

[0013] The acquisition unit is used to acquire the response information of the second client to the meeting invitation information;

[0014] The first update unit is used to update the meeting invitation status of the objects in the object list based on the response information.

[0015] In one embodiment, the first update unit includes:

[0016] The association determination subunit is used to determine meeting invitation information that is associated with the object;

[0017] The first update subunit is used to update the information status of the meeting invitation information based on the response information;

[0018] The second update subunit is used to update the meeting invitation status of the object based on the updated information status.

[0019] In one embodiment, the first update subunit is configured to:

[0020] Determine the timing attribute of the response information; verify the response information based on the timing attribute; if the verification passes, update the information status of the meeting invitation information based on the response information.

[0021] In one embodiment, after sending the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, the management device of the meeting object further includes:

[0022] A setup unit is used to establish the association between the meeting invitation information and the object;

[0023] The second update unit is used to update the information status corresponding to the meeting invitation information based on the sending result and the association relationship.

[0024] In one embodiment, the second update unit includes:

[0025] The task creation subunit is used to create a delayed task for the meeting invitation information based on the sending result and the association relationship.

[0026] The first acquisition subunit is used to acquire the current information status of the meeting invitation information through the delayed task when the execution condition of the delayed task is triggered.

[0027] The first verification subunit is used to verify the current information status;

[0028] The third update subunit is used to update the information status corresponding to the meeting invitation information based on the verification result.

[0029] In one embodiment, the first transmitting unit includes:

[0030] The second acquisition subunit is used to acquire object information of the object;

[0031] The list creation sub-unit is used to create a list of non-attendance objects for the target meeting based on the object information. The list of non-attendance objects includes objects whose meeting invitation status is "non-attendance".

[0032] In one embodiment, after updating the meeting invitation status of objects in the object list based on the response information, the meeting object management device further includes:

[0033] The determining unit is configured to determine a third client from the second client to cancel the meeting invitation if the updated meeting invitation status of the object is detected to meet a preset status.

[0034] The first generation unit is used to generate invitation cancellation information for the target meeting, wherein the invitation cancellation information instructs the client to cancel the meeting invitation for the target meeting;

[0035] The second sending unit is used to send the invitation cancellation information to the third message client.

[0036] In one embodiment, the determining unit includes:

[0037] The second determining subunit is used to determine, from the second client, the fourth client corresponding to the object when it first responds to the meeting invitation information;

[0038] The first determining subunit is used to determine, based on the fourth client, a third client from the second clients to cancel the meeting invitation.

[0039] In one embodiment, the creation unit includes:

[0040] The third acquisition subunit is used to determine the meeting invitation recipients of the target meeting through the first client and to acquire the meeting settings information of the target meeting;

[0041] The meeting creation subunit is used to create a target meeting in the first client based on the meeting invitation recipients and the meeting settings information.

[0042] In one embodiment, the object list includes a list of non-participating objects, and the list of non-participating objects includes at least one non-participating object; after updating the meeting invitation status of the objects in the object list according to the response information, the meeting object management device further includes:

[0043] The display unit is used to display a meeting invitation control for the non-participating object in the non-participating list if the updated meeting invitation status of the non-participating object is detected to meet the preset status.

[0044] The invitation unit is used to respond to the meeting invitation operation of the meeting invitation control and to invite the non-participating object to the meeting.

[0045] In one embodiment, after updating the meeting invitation status of objects in the object list based on the response information, the meeting object management device further includes:

[0046] The second generation unit is used to generate a state set of the object based on the updated meeting invitation status of the object, wherein the state set includes the historical meeting invitation status of the object;

[0047] The third update unit is used to update the object list based on the state set.

[0048] Accordingly, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the meeting object management method as shown in embodiments of this application.

[0049] Accordingly, this application also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the meeting object management method shown in the embodiments of this application.

[0050] Accordingly, this application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the meeting object management method shown in this application embodiment.

[0051] In this embodiment, a target meeting can be created in a first client, the target meeting including at least one object; when the conditions for starting the target meeting are triggered, a meeting invitation message for the target meeting is sent to a second client corresponding to the object through the message channel of the first client, and a list of objects for the target meeting is created, the list of objects including at least objects whose meeting invitation status is "not yet joined"; response information from the second client to the meeting invitation message is obtained; and the meeting invitation status of the objects in the object list is updated according to the response information.

[0052] This solution manages absent participants in a meeting using a participant list. Specifically, it updates the meeting invitation status of participants in the list based on their client responses to the meeting invitation information. This allows for timely monitoring of participant responses and prompt updates to the absent participant list, enabling dynamic adjustments. Furthermore, updating the meeting invitation status of absent participants through the participant list allows meeting administrators to monitor their current invitation status and initiate meeting invitations accordingly. This improved efficiency in managing absent participants enhances overall meeting management efficiency and user experience. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0054] Figure 1 This is a schematic diagram illustrating a scenario of the meeting object management method provided in an embodiment of this application;

[0055] Figure 2 This is a flowchart of a meeting object management method provided in an embodiment of this application;

[0056] Figure 3 This is an interactive schematic diagram of the meeting object management method provided in the embodiments of this application;

[0057] Figure 4 This is another interactive schematic diagram of the meeting object management method provided in the embodiments of this application;

[0058] Figure 5 This is another interactive schematic diagram of the meeting object management method provided in the embodiments of this application;

[0059] Figure 6 This is another flowchart illustrating the meeting object management method provided in this application embodiment;

[0060] Figure 7 This is another flowchart illustrating the meeting object management method provided in this application embodiment;

[0061] Figure 8 This is another flowchart illustrating the meeting object management method provided in this application embodiment;

[0062] Figure 9 This is another flowchart illustrating the meeting object management method provided in this application embodiment;

[0063] Figure 10 This is a schematic diagram of the structure of the meeting object management device provided in the embodiments of this application;

[0064] Figure 11 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0065] Figure 12 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0066] Figure 13 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0067] Figure 14 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0068] Figure 15 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0069] Figure 16 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0070] Figure 17 This is another structural schematic diagram of the meeting object management device provided in the embodiments of this application;

[0071] Figure 18 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application. Detailed Implementation

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

[0073] This application provides a method, apparatus, electronic device, and storage medium for managing meeting participants. Specifically, this application provides a management apparatus for meeting participants suitable for computer equipment. The computer equipment can be a server or a terminal, etc. Specifically, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0074] This application embodiment will take the management method of meeting objects executed by the server as an example to introduce the management method of meeting objects.

[0075] refer to Figure 1 Terminal 20 can run a first client. By creating a target meeting that includes at least one object within the first client, server 10 can obtain the meeting settings information of the target meeting and determine the objects to be invited to the target meeting. When the conditions for starting the target meeting are triggered, the server can send the target meeting invitation information to the corresponding second client through the message channel of the first client, and create a list of objects for the target meeting. This list must include at least objects whose meeting invitation status is "not yet joined".

[0076] Furthermore, server 10 can obtain the response information of the second client to the meeting invitation information. For example, terminal 20 can report the response information of the second client to the meeting invitation information to the server, so that server 10 can obtain the response information; or server 10 can determine the response information of the second client to the meeting invitation information based on the execution result of the delayed task; and so on. Server 10 can update the meeting invitation status of objects in the object list according to the obtained response message. Optionally, it can subsequently perform meeting invitation operations on objects in the updated object list whose meeting invitation status is "not yet joined".

[0077] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the preferred order of the embodiments.

[0078] This application provides a method for managing meeting objects. This method can be executed by a server or a terminal, or by both. This application example illustrates the method by having the meeting object management method be executed by a server. Specifically, in this application embodiment, the method can be executed by a meeting object management device integrated into the server, such as... Figure 2 The specific process for managing the meeting participants can be as follows:

[0079] 101. Create a target meeting in the first client. The target meeting includes at least one object.

[0080] Here, the first client refers to the client corresponding to the meeting creation object. For example, the first client can specifically be the messaging client of the meeting creation object. A messaging client refers to a client capable of message interaction. Specifically, a messaging client can be an application running on a terminal for user interaction to achieve message interaction, such as a client providing chat functionality. In practical applications, messaging clients can include clients that implement message interaction in different application scenarios, such as instant messaging clients in social application scenarios, messaging clients in office application scenarios, and messaging clients in online education application scenarios.

[0081] The "objects" in the meeting refer to the participants in the meeting. For example, the objects in the meeting can be user members who participate in the meeting, or organizational members who participate in the meeting, and so on.

[0082] In this application, the server can create a target meeting including at least one object through a first client. There are several ways for the first client to create the target meeting. For example, the first client can obtain meeting information required to create the target meeting and create the target meeting based on that information. For instance, the first client can obtain meeting information sent by other devices and then create the target meeting based on that information. Alternatively, the first client can obtain meeting information provided by the user based on interaction with the user and then create the target meeting based on that information.

[0083] In one embodiment, the meeting information required to create the target meeting may include the meeting invitees and the meeting settings. Specifically, the step "creating the target meeting in the first client, the target meeting including at least one object" may include:

[0084] The first client identifies the recipients of the target meeting invitation and obtains the meeting settings information for the target meeting.

[0085] Create the target meeting in the first client based on the meeting invitees and meeting settings.

[0086] In this context, the "target meeting invitees" refers to the individuals or groups invited to participate in the target meeting. Specifically, this can be achieved by sending meeting invitation messages to these individuals or groups.

[0087] There are several ways to determine the meeting invitees for a target meeting through a first client. For example, the first client may have access to the target's address book or have permission to access the target's address book. Therefore, the first client can determine the meeting invitees for the target meeting from the address book. Alternatively, the first client may include at least one group of objects, such as a chat group or an organizational structure group. This group may contain at least one object, so the first client can determine the meeting invitees for the target meeting from the group of objects. Another example is that the first client may have object tag information set for objects. This object tag information can be used to determine the meeting invitees for the target meeting from the objects in the first client. And so on.

[0088] The meeting settings information of the target meeting refers to the relevant information describing the settings of the target meeting. For example, the meeting settings information of the target meeting may include the meeting topic, meeting start time, meeting duration, meeting format, meeting room settings, calendar settings, meeting host settings, meeting password, meeting recording settings, member joining time settings, meeting requirement settings, meeting mute settings, member restrictions, screen watermark settings, and other related information.

[0089] There are several ways to obtain the meeting settings information of the target meeting through the first client. For example, the meeting settings information set by the user for the target meeting can be obtained based on the interaction between the user and the first client. Alternatively, the device where the first client is located or other devices can send data including meeting settings information to the first client, so that the first client can obtain the meeting settings information of the target meeting by parsing the data.

[0090] In one embodiment, the target meeting invitee can be determined and the meeting settings information of the target meeting can be obtained in the first client based on interaction with the user. For example, see... Figure 3 The first client can provide, for example Figure 3The meeting reservation interface shown in the middle left figure can include an object acquisition control and at least one meeting settings control. The object acquisition control can be used to determine the meeting invitation recipients of the target meeting, and the meeting settings control can be used to set the relevant meeting information of the target meeting.

[0091] As an example, the terminal can display a meeting booking interface through the first client. For instance, this meeting booking interface could be... Figure 3 The interface shown in the left-middle image. This meeting reservation interface may include the object acquisition control shown in 1001; users can trigger this object acquisition control to determine the method for selecting meeting invitation recipients. Correspondingly, the terminal can respond to the trigger operation of the object acquisition control and display a meeting invitation recipient selection interface. For example, the selection interface could be... Figure 3 The interface shown in the right-hand image is as follows. This method selection interface can include a list of methods for selecting meeting invitation recipients. This list can include at least one invitation method control for each meeting invitation recipient, with each invitation method control corresponding to one invitation method for that meeting invitation recipient.

[0092] In this example, the user can further determine the invitation path for selecting meeting invitation objects by triggering the invitation path control. For example, the user can select the invitation path from multiple optional invitation paths such as through the address book, through recent contacts, or through group chat. Correspondingly, the terminal can respond to the trigger operation of the invitation path control and display a list of objects under the corresponding invitation path. The object list can include at least one optional candidate object. Furthermore, the user can select the target object from the object list as the meeting invitation object for the target meeting. Correspondingly, the terminal can respond to the selection operation of the candidate object and add the selected candidate object to the meeting invitation object set for the target meeting, thereby determining the meeting invitation object for the target meeting.

[0093] As another example, the terminal can display a meeting booking interface through the first client; for example, the meeting booking interface can be... Figure 3The interface shown in the left-middle image. This meeting booking interface includes a save control and at least one meeting settings control. The meeting settings control can be used to set relevant meeting information for the target meeting, such as meeting topic, meeting start time, meeting duration, meeting format, meeting room settings, calendar settings, meeting host settings, meeting password, meeting recording settings, member joining time settings, meeting requirements settings, meeting mute settings, member restrictions, screen watermark settings, etc. The save control can be used to save the meeting settings information corresponding to each meeting settings control. Users can set up the target meeting through the meeting settings controls in the meeting booking interface and save the meeting settings through the save control. Correspondingly, the terminal can respond to the trigger operation of the save control and obtain the meeting settings information corresponding to each meeting settings control.

[0094] It is worth noting that the controls in this embodiment can be in the form of icons, input boxes, and buttons. The triggering operation in this embodiment can be a specific touch operation, such as a single click, long press, double click, or swipe, or it can be triggered by voice. Optionally, the triggering operation can also be a combination of a series of operations; this embodiment does not limit this. To avoid redundancy, this will not be repeated in this application.

[0095] After identifying the target audience for the meeting and obtaining the meeting settings information, the target meeting can be created in the first client based on the meeting invitees and the meeting settings information.

[0096] 102. When the conditions for starting the target meeting are triggered, send the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, and create a list of objects for the target meeting. The list of objects must include at least objects whose meeting invitation status is "not yet joined".

[0097] The start conditions of the target meeting refer to the conditions that trigger the start of the target meeting. For example, the start conditions of the target meeting can be conditions set based on the meeting settings information of the target meeting. For instance, the start conditions of the target meeting may include time conditions, meeting location conditions, etc.

[0098] The client's message channel is used to send or receive meeting invitation information. In some examples, the first client can be an application integrated into or mounted on other clients, such as a mini-program or plugin. The first client can send or receive meeting invitation information through the message channel, so that a second client integrated into or mounted on other clients can also send or receive meeting invitation information accordingly, thereby improving the security and efficiency of data transmission.

[0099] In this context, the second client refers to the client corresponding to the meeting invitation recipient. For example, the meeting creator can send a meeting invitation message to the client corresponding to the meeting invitation recipient through the first client to invite the meeting invitation recipient to join the meeting. In this case, the client corresponding to the meeting invitation recipient can be the second client. For instance, the second client can specifically be the messaging client of the meeting invitation recipient.

[0100] The meeting invitation information is the relevant information used to invite participants to join the meeting. The meeting invitation information can take many forms, such as audio, vibration, and interface information, or a combination of these. As an example, the meeting invitation information can be presented as follows: Figure 4 As shown in the left-middle diagram, specifically, when the conditions for starting the target meeting are triggered, a meeting invitation message for the target meeting can be sent to the corresponding second client through the message channel of the first client. The second client can then receive this meeting invitation message. Specifically, the second client can display, based on the received meeting invitation message, as shown in the diagram. Figure 4 The meeting invitation interface shown in the left-middle image includes a meeting invitation text, a confirmation / cancellation control, and a cancellation / cancellation control. Optionally, in practical applications, the second client can also trigger vibration or audio playback on its corresponding terminal based on the received meeting invitation information to assist in the meeting invitation process.

[0101] The meeting invitation text describes relevant information about the meeting invitation, such as the recipients, the meeting moderator, the meeting type, and the number of participants. The "Confirm Join" control allows participants to join the meeting; they can trigger this control by swiping, long-pressing, clicking, or double-clicking. The "Cancel Join" control allows participants to cancel their participation; they can also trigger this control by swiping, long-pressing, clicking, or double-clicking to postpone joining the meeting.

[0102] In this application, when the conditions for starting the target meeting are triggered, a list of objects for the target meeting can also be created. The list of objects includes at least objects whose meeting invitation status is "not yet joined".

[0103] The target meeting's object list is a list that includes at least one object from the target meeting. For example, the target meeting's objects may include both those already in the meeting and those not yet in the meeting. It's worth noting that the object list can display relevant information about each object, such as its name, avatar, and meeting invitation status.

[0104] There are several ways to create a list of objects for a target meeting. For example, you can create a list that includes both invited and uninvited objects. Invited objects are those whose meeting invitation status is "Intended," while uninvited objects are those whose meeting invitation status is "Uninvited." The arrangement of invited and uninvited objects in this list can be varied. For instance, objects can be sorted based on whether they are invited or not; for example, uninvited objects could be placed at the beginning of the list, followed by invited objects. Alternatively, the order of invited and uninvited objects can be randomized, and so on.

[0105] There are several ways to create a list of objects for the target meeting. For example, you can create separate lists of already invited and not invited objects. The list of already invited objects can include at least one already invited object from the target meeting, and the list of not invited objects can include at least one not invited object from the target meeting. "Already invited" refers to objects whose meeting invitation status is "invited," and "not invited" refers to objects whose meeting invitation status is "not invited." See [example example] for details. Figure 4 The right image shows that you can create separate lists of members and non-members. The list of members includes an object named "XXXli", which is the meeting creation object for the target meeting. Figure 5 The left image shows the list of participants who have not yet joined the meeting, which includes the five participants who have not yet joined the target meeting.

[0106] The meeting invitation status of an object describes the state of the object in response to the meeting invitation of the target meeting. For example, the meeting invitation status of an object can include "joined" and "not joined". "Joined" means that the object has accepted the meeting invitation of the target meeting and is currently in the state of having joined the meeting, while "not joined" means that the object has not accepted the meeting invitation of the target meeting and is currently in the state of not joining the meeting.

[0107] More specifically, "not joining" can be further categorized based on the reason why an object did not join the meeting. For example, "not joining" can specifically include "invitable," "inviting" (or "calling"), "declined," and "timeout." "Invitable" means the object can currently be invited to join the meeting; for example, this can be done by sending a meeting invitation message. "Inviting" means the object is currently being invited; for example, the object's messaging client is currently displaying a meeting invitation message, thus placing the object in an invited state. "Declined" means the object has declined the meeting invitation from the target meeting; for example, the object can decline the meeting invitation by triggering a cancel join control when the meeting invitation interface is displayed on a second client. "Timeout" means the object has not responded to the meeting invitation from the target meeting within a timeout period (e.g., neither accepted nor declined); for example, when the terminal is powered off, the object cannot respond to the meeting invitation from the target meeting through that terminal, resulting in a timeout.

[0108] In one embodiment, a list of non-attendance objects in the target meeting can be created based on the object information of the objects in the target meeting. This allows the non-attendance objects to be identified through the list, enabling subsequent meeting invitation operations to be performed on the non-attendance objects based on their meeting invitation status, thereby improving meeting efficiency. Specifically, the step "creating a list of objects for the target meeting, the list of objects including at least objects whose meeting invitation status is non-attendance" can include:

[0109] Get object information about the object;

[0110] Based on the object information, create a list of non-attendees for the target meeting. The list of non-attendees includes objects whose meeting invitation status is "non-attendee".

[0111] The object information can include the object name, the object's meeting identity (e.g., meeting host, meeting administrator, meeting creator, etc.), the object's meeting invitation status, and the object's avatar.

[0112] For example, one could obtain object information for all objects in a target meeting and create a list of non-attendance objects based on that information. Alternatively, as initialization of the non-attendance object list, all objects in the target meeting could be listed as non-attendance objects, and the list could be updated subsequently based on the attendance status of each object in the target meeting.

[0113] As an example, the meeting creation object for the target meeting can determine the meeting invitees and meeting settings in the first client, and then create the target meeting in the first client. After joining the meeting, this meeting creation object can manage the list of non-participating objects through the object management interface displayed on the first client. Therefore, at this time, the meeting creation object is a member of the target meeting. When the meeting invitation information for the target meeting has just been sent to the second clients corresponding to each meeting invitee, and no meeting invitee has joined yet, these meeting invitees can be considered as non-participating objects of the target meeting. Furthermore, as meeting invitees join, the number of non-participating objects in the list can be reduced accordingly.

[0114] Furthermore, when creating a list of non-attending participants for a target meeting based on their object information, the list can display the object's information, such as its name, avatar, and meeting invitation status. Optionally, other object information, such as the object's meeting identity, can be selected for display as needed. See also [example example]. Figure 5 The left image shows that the object management interface displayed by the first client can include a list of joined objects and a list of unjoined objects. The list of unjoined objects can include at least one unjoined object of the target meeting, and the list of unjoined objects displays the object information of each unjoined object, including the object avatar, object name, and object meeting invitation status.

[0115] In one embodiment, when creating a list of non-attending objects based on the acquired object information, a meeting invitation control can also be set for the non-attending objects in the list based on their meeting invitation status. The terminal can then respond to a trigger operation on the meeting invitation control and perform a meeting invitation operation on the corresponding non-attending objects in the list. See also, as an example. Figure 5 The right image shows the object management interface displayed by the messaging client, which can include a list of joined objects and a list of unjoined objects. The list of unjoined objects can include at least one unjoined object from the target meeting, and a meeting invitation control is set for the unjoined objects in the list whose meeting invitation status is "invitable". Figure 5 The "Call" control in the middle right figure enables the terminal to respond to the trigger operation of the meeting invitation control and invite the corresponding non-participating objects in the list of non-participating objects to a meeting, such as sending the meeting invitation information of the target meeting to the message client of the non-participating object.

[0116] In this application, considering that the same object can have multiple clients—for example, a single user can have multiple terminals, each running a client—in application scenarios where the same object has multiple corresponding second clients, when the conditions for starting the target meeting are triggered, meeting invitation information for the target meeting will be sent to multiple second clients of that object. In application scenarios where the same object can have multiple second clients, each terminal corresponding to a second client, upon receiving the meeting invitation information, can report the object's response information to the meeting invitation information to the server. Therefore, the server needs to deduplicate the response information reported by the same object to the meeting invitation information so that the server can accurately determine the meeting invitation status of the object based on the response information reported by the object. Specifically, after sending the meeting invitation information for the target meeting to the object's message client through the message client's message channel, the meeting object management method may further include:

[0117] Establish a connection between meeting invitation information and recipients;

[0118] Based on the sending results and related relationships, the information status corresponding to the meeting invitation information is updated.

[0119] The association between meeting invitation information and objects refers to the correspondence between meeting invitation information and objects. Specifically, since the same object can have multiple second clients, when a meeting invitation for the target meeting is sent to each of the object's second clients, since these meeting invitations all correspond to the object, it can be determined that these meeting invitations are associated with the object.

[0120] In this application, there are multiple ways to establish the association between meeting invitation information and objects. For example, the association between the two can be established based on the object identifier of the object. For instance, when a meeting invitation is sent to a second client of object A, the meeting invitation can be marked by the object identifier of object A. In this way, the object associated with the meeting invitation can be identified as object A.

[0121] The information status corresponding to the meeting invitation information is a description of the meeting invitation information based on the interactive behavior of the object in response to the meeting invitation information. For example, the information status corresponding to the meeting invitation information may include "sending", "answered", "rejected", and "timeout".

[0122] "Sending in progress" refers to the status of sending meeting invitation information to the second client of the target; "Accepted" means that after the meeting invitation information was sent to the second client of the target, the target chose to accept the meeting invitation. For example, the meeting invitation information could be as follows: Figure 4 The left-hand diagram shows a ringing format where, when the second client of the object receives a meeting invitation, it can be displayed to the user as a ringing sound. If the user chooses to answer the ringing, for example, by triggering... Figure 4 The "Slide into Meeting" control shown in the middle left image indicates that the meeting invitation information is in a "Received" state; "Rejected" means that after the meeting invitation information is sent to the second client of the recipient, the recipient chooses to reject the meeting invitation. For example, the meeting invitation information could be specifically as follows: Figure 4 The left-hand diagram shows a ringing notification format. When the second client of the object receives the meeting invitation information, it can be displayed to the user as a ringing notification. If the user chooses to reject the ringing notification, for example, by triggering... Figure 4 The "Do Not Enter" control shown in the middle left image indicates that the status of the meeting invitation information is "rejected"; "timeout" means that after the meeting invitation information is sent to the second client of the object, the object has not interacted with the meeting invitation information within a preset time, for example, neither answering nor rejecting.

[0123] Since the information status of the meeting invitation information is described based on the interactive behavior of the object in response to the meeting invitation information, the information status of the meeting invitation information can be updated based on the sending result and the relationship.

[0124] In one embodiment, the information status of each meeting invitation message sent to the target can be updated based on the sending result. For example, the information status of each sent meeting invitation message can be maintained separately. When a meeting invitation message is first sent, the information status of the meeting invitation message can be determined to be "sent". When a meeting invitation message has been sent to the target's second client, and the terminal corresponding to the second client detects that the target has chosen to accept the meeting invitation, the terminal can report to the server. The server can then determine the information status of the meeting invitation message as "accepted" based on the terminal's reported data. When a meeting invitation message has been sent to the target's second client, and the terminal corresponding to the second client detects that the target has chosen to reject the meeting invitation, the terminal can report to the server. The server can then determine the information status of the meeting invitation message as "rejected" based on the terminal's reported data. When a meeting invitation message has been sent to the target's second client, and the terminal corresponding to the message client does not report data to the server within a preset time period, the information status of the meeting invitation message can be determined to be "timeout".

[0125] Furthermore, the update result of the information status corresponding to the meeting invitation information can be determined based on the association between the meeting invitation information and the object. Specifically, since an object can have multiple terminals, and each terminal can run a second client corresponding to that object, when each terminal detects an interactive behavior of the object in response to the meeting invitation information, such as answering or rejecting, the terminal can report it to the server. The server can then deduplicate the data reported by different terminals based on the association between the object and the meeting invitation information. For example, for data reported by different terminals that indicate the same interactive behavior of the object in response to the meeting invitation information, the server can use the first reported data received as the basis to determine the information status corresponding to the meeting invitation information of that object.

[0126] In another embodiment, considering that after the server sends a meeting invitation to the second client, the client may fail to respond to the received meeting invitation within a preset time period due to a terminal malfunction or individual reasons, resulting in the server not receiving data reported by the client's terminal within the preset time period, a delayed task can be created on the server side to update the information status corresponding to the meeting invitation. Specifically, the step "updating the information status corresponding to the meeting invitation based on the sending result and association relationship" can include:

[0127] Based on the sending results and related relationships, create a delayed task for the meeting invitation information;

[0128] When the execution conditions of the delayed task are triggered, the current information status of the meeting invitation information is obtained through the delayed task;

[0129] Verify the current information status;

[0130] Based on the verification results, update the information status corresponding to the meeting invitation information.

[0131] Delayed tasks refer to tasks that need to be executed at a later time. For example, a delayed task can be a task that is executed 45 seconds after it is created.

[0132] The execution condition of a delayed task refers to the condition that triggers the execution of the delayed task. For example, this condition can be a time condition, such as executing the delayed task 45 seconds after its creation. The specific execution condition can be set as needed, and this application does not impose any restrictions on it.

[0133] In this application, the server can address the issue of updating the information status of a meeting invitation when no data is received from the terminal regarding the invitation within a preset time period by creating a delayed task for that invitation. For example, after the server sends the meeting invitation to the second client corresponding to the target meeting, a delayed task for that invitation can be created. As an example, when the execution condition of the delayed task is triggered—for instance, when the execution time meets the execution condition—the task can specifically obtain the current information status of the meeting invitation and verify it. The server can then update the information status of the meeting invitation based on the verification result.

[0134] Specifically, the current status of the meeting invitation information can be verified to determine whether the server has not received the reporting data from the terminal within a preset time period, which instructs the object to respond to the received meeting invitation information (e.g., answer, decline, etc.). If so, the information status of the meeting invitation information corresponding to that object can be updated to "timeout".

[0135] As an example, after the server sends the meeting invitation information of the target meeting to the second client corresponding to the object, the server can create a delayed task for the meeting invitation information of that object. The execution condition of this delayed task is that it will be executed when the current time meets a preset time condition. Therefore, when the execution condition of the delayed task is triggered, the delayed task can obtain the current information status of the meeting invitation information of the object and verify the current information status. Specifically, if the current information status is not "answered" or "rejected", the information status corresponding to the meeting invitation will be updated to "timeout".

[0136] 103. Obtain the response information from the second client regarding the meeting invitation information.

[0137] The response information of the second client corresponding to the object to the meeting invitation information indicates the object's response to the meeting invitation information received by the second client. For example, the object's response to the meeting invitation information may include: accepting the meeting invitation to the target meeting, rejecting the meeting invitation to the target meeting, and not responding to the meeting invitation to the target meeting (e.g., if the invitation is not answered after a timeout).

[0138] Therefore, in this application, there are multiple ways for the server to obtain the response information of the second client corresponding to the object in response to the meeting invitation information. For example, the response information of the second client corresponding to the object in response to the meeting invitation information can be obtained through data reporting by the terminal; or the response information of the second client corresponding to the object in response to the meeting invitation information can be determined through the server's delayed task.

[0139] As an example, after the second client of the object receives the meeting invitation information of the target meeting, the object's response to the meeting invitation information can be to accept the meeting invitation of the target meeting. Then, the terminal corresponding to the second client can report to the server after detecting the object's response information to the meeting invitation information, so that the server can obtain the object's response information to the meeting invitation information.

[0140] As another example, after the second client of the object receives the meeting invitation information of the target meeting, the object's response to the meeting invitation information can be to reject the meeting invitation of the target meeting. Then, the terminal corresponding to the second client can report to the server after detecting the object's response information to the meeting invitation information, so that the server can obtain the object's response information to the meeting invitation information.

[0141] As another example, after a second client of an object receives a meeting invitation for the target meeting, it may fail to respond to the received meeting invitation (e.g., answer, decline) within a preset time period due to a malfunction in the terminal corresponding to the second client or due to individual reasons of the object. Consequently, the server does not receive any data reported by the object's terminal within the preset time period. Since the server can create a delayed task for the meeting invitation after sending it, it can detect that the status of the meeting invitation is not "answered" or "declined" after the preset time period. Therefore, the server can detect the object's failure to respond within the timeout period through the delayed task, thus determining that the object's response to the meeting invitation was not a response.

[0142] 104. Update the meeting invitation status of objects in the object list based on the response information.

[0143] The meeting invitation status of an object describes the state of the object's meeting invitation to the target meeting. For example, the meeting invitation status of an object can include "joined" and "not joined". More specifically, "not joined" can be further divided according to the reason why the object did not join. For example, "not joined" can specifically include "available to invite" (or "calling"), "inviting", "declined", "timeout", etc.

[0144] In this application, since the response information from the second client of the object to the meeting invitation information indicates the object's response to the meeting invitation information received by the second client, the server can update the meeting invitation status of the object in the object list based on the obtained response information. Specifically, the step of "updating the meeting invitation status of the object in the object list based on the response information" may include:

[0145] Identify meeting invitation information that is relevant to the target audience;

[0146] Update the status of the meeting invitation information based on the response information;

[0147] Update the meeting invitation status of the target based on the updated information status.

[0148] In this application, the server can send meeting invitation information to a second client of the object, and the server can record and update the information status corresponding to the meeting invitation information. For example, the information status of the meeting invitation information may include "sending", "accepted", "rejected", and "timeout". Furthermore, as mentioned above, after sending the meeting invitation information to the object, the server can also establish an association between the meeting invitation information and the object. Therefore, correspondingly, when the server receives the object's response information to the meeting invitation information, it can determine the meeting invitation information associated with that object.

[0149] Furthermore, since the object's response information to the meeting invitation information indicates its own response to the invitation—for example, accepting the invitation, rejecting it, or not responding (e.g., not responding after a timeout)—the status of the meeting invitation information can be updated based on the response information.

[0150] For example, if the server receives a response indicating that the object has accepted the meeting invitation, the status of the meeting invitation can be updated to "accepted"; if the server receives a response indicating that the object has rejected the meeting invitation, the status of the meeting invitation can be updated to "rejected"; and if the server receives a response indicating that the object has not responded to the meeting invitation (e.g., due to a timeout), the status of the meeting invitation can be updated to "timeout".

[0151] After updating the information status of the meeting invitation information, the meeting invitation status of the target can be further updated based on the updated information status.

[0152] For example, if the updated status of the meeting invitation information is "rejected", the meeting invitation status for that object can be updated to "rejected"; if the updated status of the meeting invitation information is "timeout", the meeting invitation status for that object can be updated to "timeout"; if the updated status of the meeting invitation information is "issuing", the meeting invitation status for that object can be updated to "inviting"; and if the status of the meeting invitation information is updated to "rejected" or "timeout", and the updated status remains unchanged for a preset duration (e.g., a 45-second cooldown), the meeting invitation status for that object can be updated to "invitable".

[0153] Specifically, when the status of the meeting invitation information is "answered" after an update is detected, it means that the object has accepted the meeting invitation sent by the meeting invitation information. Therefore, the object can be removed from the list of non-participating objects and added to the list of participating objects.

[0154] In one embodiment, considering that an object can have multiple terminals, and each terminal can run a second client corresponding to that object, each terminal can report to the server when it detects a response from the object to the meeting invitation information, such as answering or rejecting. That is, for the same object, the server can obtain multiple response messages from that object to the meeting invitation information. Therefore, in order to accurately determine the object's response to the meeting invitation information and avoid a poor user experience, the server can deduplicate the multiple response messages. Specifically, the step "updating the information status of the meeting invitation information based on the response information" can include:

[0155] Determine the timing attributes of the response information;

[0156] The response information is validated based on the timing attributes;

[0157] If the verification passes, the status of the meeting invitation information will be updated based on the response information.

[0158] The timing attribute of the response information describes the order in which the response information is received. Specifically, since the server can obtain multiple response messages from the same object in response to the meeting invitation, the timing attribute of each response message indicates the order in which the server obtained the response information. For example, for object B, the server first obtains response information D sent by object B through terminal C in response to the meeting invitation, and then obtains response information E sent by object B through terminal E in response to the meeting invitation. In this case, the timing attribute of response information D can be 1, indicating that it is the first response message from object B obtained by the server; the timing attribute of response information E can be 2, indicating that it is the second response message from object B obtained by the server.

[0159] In this application, to accurately determine the object's response to the meeting invitation information and avoid a poor user experience, for multiple response messages reported by the same object, the server can use the first response message it receives. That is, if the timing attribute of the response message indicates that it is the first reported data received by the server, then the response message can be determined to have passed verification, and the information status of the meeting invitation information can be updated based on this response message; otherwise, the response message can be determined to have failed verification, and the information status of the meeting invitation information will not be updated based on this response message.

[0160] In one embodiment, considering that an object can have multiple terminals, and each terminal can run a second client corresponding to that object, when the object responds to a meeting invitation message through a certain terminal—for example, accepting or rejecting the meeting invitation message—other terminals of the object can stop inviting the object to meetings in order to improve the user experience. To this end, the server can send an invitation cancellation message to the terminal that wants to cancel the meeting invitation, so that the terminal stops inviting the object to meetings. Specifically, after updating the meeting invitation status of objects in the object list based on the response information, the meeting object management method may further include:

[0161] If the updated meeting invitation status of the object is detected to meet the preset status, then the third message client to cancel the meeting invitation is determined from the second client.

[0162] Generate an invitation cancellation message for the target meeting, instructing the client to cancel the meeting invitation for the target meeting;

[0163] Send an invitation cancellation message to the third-party messaging client.

[0164] For example, the default status of the meeting invitation here can include "accepted" or "declined".

[0165] In this context, the third message client of the object refers to the client in the object's second client that is waiting to cancel the meeting invitation.

[0166] There are several ways to cancel a meeting invitation on a terminal. For example, the terminal can display a meeting invitation interface based on the received meeting invitation information. Optionally, it can also use vibration, audio playback, etc., to assist in the meeting invitation. Thus, the way the terminal cancels a meeting invitation can include displaying a cancellation meeting invitation interface. Optionally, it can also cancel the meeting invitation by stopping vibration, stopping audio playback, etc.

[0167] The invitation cancellation information for the target meeting is used to instruct the client to cancel the meeting invitation for the target meeting. Specifically, when the client receives the invitation cancellation information for the target meeting, the client can trigger its corresponding terminal to cancel the meeting invitation.

[0168] In this application, once the third messaging client to cancel the meeting invitation is determined from the second client of the object, the server can generate the invitation cancellation information for the target meeting and send the cancellation request information to the third messaging client so that the terminal corresponding to the third messaging client can cancel the meeting invitation.

[0169] In one embodiment, considering that an object can have multiple terminals, and each terminal can run a second client corresponding to that object, when a terminal detects a response from the object to the meeting invitation information, such as answering or rejecting, and reports the data to the server, it indicates that the object has responded to the meeting invitation information through that message client. Therefore, other message clients can be identified as third message clients to cancel the meeting invitation. Specifically, the step "determining the third message client to cancel the meeting invitation from the second clients" can include:

[0170] From the second client, determine the fourth messaging client that corresponds to the object's first response to the meeting invitation message;

[0171] Based on the fourth message client, determine the third message client from the object's message clients that is to cancel the meeting invitation.

[0172] In this context, the fourth message client of an object refers to the second client that responds to the meeting invitation information for the first time. Specifically, an object can have multiple terminals, and each terminal can run a second client corresponding to the object. When multiple second clients of the object receive meeting invitation information for the target meeting, the second client that responds to the meeting invitation information for the first time can be used as the fourth message client.

[0173] Furthermore, based on the determined fourth message client, the third message client to be canceled for the meeting can be determined from the second clients of the object. For example, the second clients of the object other than the fourth message client can be used as the third message clients to be canceled for the meeting; or, several can be selected from the second clients of the object other than the fourth message client as the third message clients to be canceled for the meeting; and so on.

[0174] In practical applications, after updating the meeting invitation status of objects in the object list based on the response information in step "update the meeting invitation status of objects in the object list", the management method for meeting objects may also include:

[0175] Perform meeting invitation operations on objects in the updated object list whose meeting invitation status is "not yet joined".

[0176] Among them, the meeting invitation operation refers to the relevant operations for making a meeting invitation. For example, the meeting invitation operation can be a specific touch operation, such as a single click, long press, double click, and swipe operation, or it can be triggered by voice. Optionally, the trigger operation can also be a combination of a series of operations.

[0177] As an example, an object whose meeting invitation status is "not invited" (which can be simply referred to as "not invited object") can include objects whose meeting invitation status is "invitable".

[0178] In this application, the meeting invitation operation on the updated object list can be implemented by triggering relevant controls. For example, in this application, the updated object list can display object information for objects that have not yet joined the meeting, such as object name, object avatar, and meeting invitation status. Furthermore, a meeting invitation control can be set for objects that have not yet joined the meeting to perform the meeting invitation operation, so that the terminal can respond to the triggering operation of the meeting invitation control and perform a meeting invitation operation on the corresponding objects in the list that have not yet joined the meeting.

[0179] In one embodiment, the created object list may specifically include a list of joined objects and a list of non-joined objects, and the list of non-joined objects may include at least one non-joined object of the target meeting. Specifically, after updating the meeting invitation status of the objects in the object list according to the response information in step "updating the meeting invitation status of the objects in the object list", the meeting object management method may further include:

[0180] If the updated meeting invitation status of a non-participant is detected to meet the preset status, then a meeting invitation control for the non-participant will be displayed in the non-participant list.

[0181] In response to a trigger action on the meeting invitation control, perform a meeting invitation operation on non-participating individuals.

[0182] The preset status of the meeting invitation here can include "invitable", "timeout", etc., and can be set as needed. This application does not impose any restrictions on this.

[0183] There are several ways to set up a meeting invitation control. For example, a meeting invitation control can be set up for a non-participating participant who meets a preset condition, such as... Figure 5 The "Call" control shown in the middle right image; another example is the meeting invitation control, which can be set for multiple non-participating participants who meet preset conditions, such as... Figure 5 The "Call All" control is shown in the middle right image.

[0184] There are several ways to display meeting invitation controls for non-participating individuals in the non-participating list. For example, the area in the object list that originally displayed the meeting invitation status can be updated to display the meeting invitation control corresponding to that object. Figure 5 The "Call" control shown in the middle right image; for example, a separate area can be used in the object list to display the meeting invitation control corresponding to the object; or, for example, the meeting invitation control can be displayed outside the object list, such as... Figure 5 The "Call All" control shown in the middle right image; etc.

[0185] As an example, see Figure 5 In the right figure, the object management interface displayed by the first client can include a list of joined objects and a list of unjoined objects. The list of unjoined objects can include at least one unjoined object of the target meeting, and a meeting invitation control is set for the unjoined objects whose meeting invitation status meets the preset status (e.g., ...). Figure 5 The "Call" control in the middle right image, and Figure 5 The "Call All" control in the middle right figure enables the terminal to respond to the trigger operation of the meeting invitation control and invite the corresponding non-participating objects in the list of non-participating objects to a meeting, such as sending the meeting invitation information of the target meeting to the second client of the non-participating object.

[0186] In one embodiment, considering that an object can receive at least one meeting invitation from a target meeting, the object can correspondingly have at least one meeting invitation status, and each meeting invitation status can correspond to one meeting invitation from a target meeting. Therefore, the object's historical meeting invitation status can be recorded so that, based on the object's historical meeting invitation status, specifically, after step "updating the meeting invitation status of objects in the object list according to the response information," the meeting object management method may further include:

[0187] Based on the updated meeting invitation status of the object, generate the object's state set, which includes the object's historical meeting invitation status.

[0188] The list of objects is updated based on the state set.

[0189] Here, the state set of an object refers to the dataset consisting of the object's historical meeting invitation states. For example, if object F has received three meeting invitations to the target meeting, and object F specifically rejected the first and second meeting invitations, and did not respond to the third meeting invitation (e.g., the invitation timed out), then the state set of object F can be {"rejected", "rejected", "timed out"}.

[0190] In this application, the updated meeting invitation status of an object can be added to the object set of that object, so as to update the object set of that object in a timely manner.

[0191] There are several ways to update an object list based on an object's state set. For example, since an object's state set includes the object's historical meeting invitation status, the object list can be updated by displaying the object's historical meeting invitation status.

[0192] As an example, a view control for the historical meeting invitation status can be set for each object in the object list. The terminal can then respond to the trigger operation of the view control, retrieve the historical meeting invitation status of the object from the object's status set, and display the historical meeting invitation status of the object. Alternatively, the historical meeting invitation status of each object can be displayed directly in the object list. And so on.

[0193] There are multiple ways to update an object list based on an object's state set. For example, since an object's state set includes its historical meeting invitation status, the sorting of objects in the object list can be updated based on each object's historical meeting invitation status, thus updating the object list.

[0194] As an example, different weights or scores can be assigned to objects based on their different meeting invitation states. For each object in the object list, its score can be calculated using its historical meeting invitation states. This score can then be used to update the order of objects in the object list, thus updating the object list. As another example, objects in the object list can be sorted based on their last meeting invitation state, thus updating the object list.

[0195] It is worth noting that there are multiple ways to create the target meeting object list in this application. For example, a list of already joined objects and a list of not joined objects can be created separately. The list of already joined objects can include at least one already joined object of the target meeting, and the list of not joined objects can include at least one not joined object of the target meeting. Therefore, in one embodiment, the step "generate a state set of objects based on the updated meeting invitation status of the objects, wherein the state set includes the historical meeting invitation status of the objects; update the object list based on the state set" can be specifically described as "generate a state set of not joined objects based on the updated meeting invitation status of the not joined objects, wherein the state set includes the historical meeting invitation status of the not joined objects; update the list of not joined objects based on the state set." The specific implementation method can be referred to the foregoing and will not be repeated here. In another embodiment, the step "generate a state set of objects based on the updated meeting invitation status of the objects, wherein the state set includes the historical meeting invitation status of the objects; update the object list based on the state set" can be specifically described as "generate a state set of already joined objects based on the updated meeting invitation status of already joined objects, wherein the state set includes the historical meeting invitation status of already joined objects; update the list of already joined objects based on the state set." The specific implementation method can refer to the foregoing and will not be repeated here.

[0196] As can be seen from the above, this embodiment can create a target meeting in the first client, the target meeting including at least one object; when the start condition of the target meeting is triggered, the meeting invitation information of the target meeting is sent to the second client corresponding to the object through the message channel of the first client, and a list of objects of the target meeting is created, the list of objects including at least objects whose meeting invitation status is not yet joined; the response information of the second client to the meeting invitation information is obtained; and the meeting invitation status of the objects in the object list is updated according to the response information.

[0197] This solution manages absent participants in a meeting using a list of attendees. Specifically, it updates the meeting invitation status of attendees in the list based on the responses of their respective message clients to the meeting invitation messages. This allows for timely monitoring of responses and prompt updates to the absent participant list, enabling dynamic adjustments to the list. Furthermore, updating the meeting invitation status of absent participants through the list allows meeting administrators to monitor their current invitation status and initiate meeting invitations accordingly. This improved efficiency in managing absent participants enhances overall meeting management efficiency and user experience.

[0198] Furthermore, this solution not only maintains the meeting invitation status of objects based on data actively reported by the terminal, but also proposes that the backend implement timeout reporting through delayed tasks, so as to maintain the meeting invitation status of objects in a timely manner even when the invitation is not accepted within a timeout period. In addition, by maintaining a list of objects who have not joined the meeting, the solution allows meeting users to intuitively see the meeting invitation status of each object through this list, and to perform meeting invitation operations on objects in the list whose meeting invitation status is not joined.

[0199] Based on the method described in the above embodiments, the following examples will provide further detailed explanations.

[0200] In this embodiment, the integration of a meeting participant management device into a server and a terminal is used as an example. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0201] like Figure 6 As shown, a method for managing meeting participants is described, with the following specific process:

[0202] 201. Create a target meeting in the first client of the terminal. The target meeting includes at least one object.

[0203] In one embodiment, the meeting settings information of the target meeting can be determined in the first client of the terminal, and the meeting invitation objects of the target meeting can be determined through the address book of the first client, thereby creating a target meeting that includes at least one object.

[0204] 202. When the conditions for starting the target meeting are triggered, the server sends the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, and creates a list of objects for the target meeting. The list of objects includes at least objects whose meeting invitation status is "not yet joined".

[0205] Taking a meeting invitation message as an example, specifically, this ringing message is essentially a message that can be sent to the terminal through the message channel of the first client. For example, the terminal can display something like this based on the received ringing message. Figure 4The meeting invitation interface shown in the middle left image allows the terminal to optionally vibrate, play audio, or perform other functions to assist in inviting participants to a meeting.

[0206] See Figure 7 When the conditions for starting the target meeting are triggered, the server, upon receiving a request from a terminal, can send a ringing message to the second client corresponding to the meeting invitation recipient through the message channel of the first client. Furthermore, the server can create a list of objects for the target meeting, which can include a list of already joined objects and a list of not joined objects. The list of not joined objects can include at least one object whose meeting invitation status is "not joined," i.e., an object that has not yet joined.

[0207] 203. The server obtains the response information from the second client regarding the meeting invitation information.

[0208] In one embodiment, a meeting invitation message can be used as an example for the ringing message; see [link to relevant documentation]. Figure 7 The server can obtain the response information of the second client to the ringing message in order to record the status of each ringing.

[0209] Specifically, the server records a separate state for each ringing message. Considering that an object can have multiple terminals, and each terminal can report its ringing state to the backend after receiving a response message, the backend needs a storage record for deduplication. Specifically, the backend only receives the first reported state. In addition, for ringing timeout cases, it is also necessary to detect whether the user has actively reported an answering status. If not, the backend can use the ringing timeout to reverse the object's meeting invitation state.

[0210] Regarding the determination of ringing timeout, the server can create a corresponding delayed task for each ringing message. This delayed task checks whether the object has answered or rejected the ringing. If neither is true, the ringing status can be set to timeout, triggering a reversal of the object's meeting invitation status. See also Figure 7 As can be seen, servers can manage delayed tasks through message queues.

[0211] 204. The server determines the meeting invitation information that is associated with the object.

[0212] 205. The server updates the status of the meeting invitation information based on the response information.

[0213] In one embodiment, taking a meeting invitation message as the ringing message as an example, the information status of the meeting invitation message is the ringing status. The ringing status can include "being sent", "answered", "rejected", and "timeout". It is worth noting that the ringing status can only change from "being sent" to one of the other three statuses. If the ringing status is not "being sent" when the terminal reports it, it will return directly without performing any subsequent actions.

[0214] As an example, see Figure 8 After receiving a ringing message, the terminal can display a ringing interface, where the recipient can choose to answer or not. The terminal can then report the recipient's selection status to the backend. Further, upon receiving the ringing status report, if the currently stored ringing status is still being sent, the backend updates the ringing status to "answered" or "rejected." Otherwise, it returns directly, as the terminal may report multiple times, and the first report is considered valid. The server can update the recipient's meeting invitation status based on the reported answering status. Specifically, if the recipient answers, no action is taken; if they reject the invitation, the meeting invitation status is changed to "rejected."

[0215] In addition, the server can send a drop-off message to the reporting object. Specifically, due to the presence of multiple terminals, the ringing of the object may still be occurring on some terminals. To improve the user experience, if the object answers a call on one terminal, the ringing on other terminals should stop. In practical applications, this effect is achieved through a drop-off message, which can be used to cancel a meeting invitation.

[0216] As another example, see Figure 9 Considering that the messaging client on the target's terminal may be completely offline, in which case the terminal will not receive any information or make any reports, the reversal of the meeting invitation status needs to be guaranteed by a background ringing timeout task. Specifically, when the ringing task times out, a check logic will be triggered to check whether the ringing status has been actively reported by the terminal. If it has been actively reported, it will return directly; otherwise, the ringing status will be updated to "timeout", and the target's meeting invitation status will be updated to "timeout".

[0217] 206. The server updates the meeting invitation status of the object based on the updated information status.

[0218] In one embodiment, a meeting invitation message can be used as an example of a ringing message. The meeting invitation status of an object can include "Available to invite," "Inviting," "Declined," and "Timeout." It is worth noting that the meeting invitation status of an object is not specifically set to "Answered," because once an object answers the ringing, that object will no longer appear in the list of unattended participants.

[0219] In addition, meeting invitations that are "rejected" or "timed out" will automatically revert to "available" status after a preset cooldown period (e.g., 45 seconds). Meeting invitations that are "inviting" will revert to "rejected" or "timed out" status via a ringing notification.

[0220] 207. The server performs a meeting invitation operation on objects in the updated object list whose meeting invitation status is "not yet joined".

[0221] As can be seen from the above, this application embodiment can manage non-attendees in a meeting through a meeting object list. Specifically, this solution updates the meeting invitation status of objects in the object list based on the response information of the corresponding client to the meeting invitation information. This allows for timely information on the object's response to the meeting invitation, and timely updates to the non-attendee list based on the response, enabling dynamic adjustments to the non-attendee list. Furthermore, by updating the meeting invitation status of non-attendees through the object list, the meeting administrator can be aware of the current meeting invitation status of non-attendees and then perform meeting invitation operations based on this status. This improves the efficiency of meeting management and the user experience by enhancing the management efficiency of non-attendees.

[0222] To better implement the above methods, this application also provides a management device for meeting participants, which can be integrated into a server or terminal. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these.

[0223] For example, such as Figure 10 As shown, the management device for the meeting object may include a creation unit 301, a first sending unit 302, an acquisition unit 303, and a first update unit 304, as follows:

[0224] The creation unit 301 can be used to create a target meeting in a first client, the target meeting including at least one object;

[0225] The first sending unit 302 can be used to send the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client when the opening condition of the target meeting is triggered, and to create a list of objects of the target meeting, the list of objects including at least objects whose meeting invitation status is not joined.

[0226] The acquisition unit 303 can be used to acquire the response information of the second client to the meeting invitation information;

[0227] The first update unit 304 can be used to update the meeting invitation status of objects in the object list based on the response information.

[0228] In one embodiment, reference Figure 11 The first update unit 304 may include:

[0229] The association determination subunit 3041 can be used to determine meeting invitation information that is associated with the object;

[0230] The first update subunit 3042 can be used to update the information status of the meeting invitation information according to the response information;

[0231] The second update subunit 3043 can be used to update the meeting invitation status of the object based on the updated information status.

[0232] In one embodiment, the first update subunit 3042 can be used to:

[0233] Determine the timing attribute of the response information; verify the response information based on the timing attribute; if the verification passes, update the information status of the meeting invitation information based on the response information.

[0234] In one embodiment, reference Figure 12 After sending the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, the management device of the meeting object further includes:

[0235] The establishment unit 305 can be used to establish the association between the meeting invitation information and the object;

[0236] The second update unit 306 can be used to update the information status corresponding to the meeting invitation information based on the sending result and the association relationship.

[0237] In one embodiment, reference Figure 13 The second update unit 306 may include:

[0238] The task creation subunit 3061 can be used to create a delayed task for the meeting invitation information based on the sending result and the association relationship.

[0239] The first acquisition subunit 3062 can be used to acquire the current information status of the meeting invitation information through the delayed task when the execution condition of the delayed task is triggered.

[0240] The first verification subunit 3063 can be used to verify the current information status;

[0241] The third update subunit 3064 can be used to update the information status corresponding to the meeting invitation information based on the verification result.

[0242] In one embodiment, reference Figure 14 The first sending unit 302 may include:

[0243] The second acquisition subunit 3021 can be used to acquire object information of the object;

[0244] The list creation subunit 3022 can be used to create a list of non-attendance objects for the target meeting based on the object information. The list of non-attendance objects includes objects whose meeting invitation status is "non-attendance".

[0245] In one embodiment, reference Figure 15 After updating the meeting invitation status of objects in the object list based on the response information, the meeting object management device further includes:

[0246] The determining unit 307 can be used to determine a third client from the second client to cancel the meeting invitation if the updated meeting invitation status of the object is detected to meet a preset status.

[0247] The first generation unit 308 can be used to generate invitation cancellation information for the target meeting, wherein the invitation cancellation information instructs the client to cancel the meeting invitation for the target meeting;

[0248] The second sending unit 309 can be used to send the invitation cancellation information to the third message client.

[0249] In one embodiment, reference Figure 16 The determining unit 307 may include:

[0250] The second determining subunit 3071 can be used to determine from the second client the fourth client corresponding to the object when it first responds to the meeting invitation information;

[0251] The first determining subunit 3072 can be used to determine, based on the fourth client, a third client from the second client to cancel the meeting invitation.

[0252] In one embodiment, reference Figure 17 The creation unit 301 may include:

[0253] The third acquisition subunit 3011 can be used to determine the meeting invitation recipients of the target meeting through the first client and obtain the meeting settings information of the target meeting;

[0254] The meeting creation subunit 3012 can be used to create a target meeting in the first client based on the meeting invitation recipients and the meeting settings information.

[0255] In one embodiment, the object list includes a list of non-participating objects, and the list of non-participating objects includes at least one non-participating object; after updating the meeting invitation status of the objects in the object list according to the response information, the meeting object management device may further include:

[0256] The display unit can be used to display a meeting invitation control for the non-participating object in the non-participating list if the updated meeting invitation status of the non-participating object is detected to meet a preset status.

[0257] The invitation unit can be used to perform a meeting invitation operation on the non-participating object in response to the meeting invitation control.

[0258] In one embodiment, after updating the meeting invitation status of objects in the object list based on the response information, the meeting object management device may further include:

[0259] The second generation unit can be used to generate a state set of the object based on the updated meeting invitation status of the object, wherein the state set includes the historical meeting invitation status of the object;

[0260] The third update unit can be used to update the object list based on the state set.

[0261] In practice, each of the above units can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units, please refer to the previous method embodiments, which will not be repeated here.

[0262] As can be seen from the above, in the meeting object management device of this embodiment, the creation unit 301 creates a target meeting in the first client, the target meeting including at least one object; when the opening condition of the target meeting is triggered, the first sending unit 302 sends the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, and creates a list of objects for the target meeting, the list of objects including at least objects whose meeting invitation status is "not yet joined"; the acquisition unit 303 acquires the response information of the second client to the meeting invitation information; and the first updating unit 304 updates the meeting invitation status of the objects in the object list according to the response information.

[0263] This solution manages absent participants in a meeting using a participant list. Specifically, it updates the meeting invitation status of participants in the list based on their client responses to the meeting invitation information. This allows for timely monitoring of participant responses and prompt updates to the absent participant list, enabling dynamic adjustments. Furthermore, updating the meeting invitation status of absent participants through the participant list allows meeting administrators to monitor their current invitation status and initiate meeting invitations accordingly. This improved efficiency in managing absent participants enhances overall meeting management efficiency and user experience.

[0264] Furthermore, this application embodiment also provides a computer device, which can be a server or terminal, etc. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. Figure 18 As shown, it illustrates a schematic diagram of the computer device involved in the embodiments of this application, specifically:

[0265] The computer device may include a memory 401 having one or more computer-readable storage media, an input unit 402, a processor 403 including one or more processing cores, and a power supply 404, etc. Those skilled in the art will understand that... Figure 18The computer device structure shown does not constitute a limitation on the computer device and may include, but is not limited to, computer devices. Figure 18 This indicates more or fewer components, a combination of certain components, or different arrangements of components. Among them:

[0266] The memory 401 can be used to store software programs and modules. The processor 403 executes various functional applications and data processing by running the software programs and modules stored in the memory 401. The memory 401 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device (such as audio data, telephone directory, etc.). In addition, the memory 401 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 401 may also include a memory controller to provide access to the memory 401 for the processor 403 and the input unit 402.

[0267] Input unit 402 can be used to receive input numerical or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, in one embodiment, input unit 402 may include a touch-sensitive surface and other input devices. A touch-sensitive surface, also known as a touch display or touchpad, can collect user touch operations on or near it (e.g., user operations using fingers, styluses, or any suitable object or accessory on or near the touch-sensitive surface) and drive corresponding connection devices according to a pre-set program. Optionally, the touch-sensitive surface may include a touch detection device and a touch controller. The touch detection device detects the user's touch orientation and the signal generated by the touch operation, transmitting the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 403, and can receive and execute commands from the processor 403. Furthermore, various types of touch-sensitive surfaces, such as resistive, capacitive, infrared, and surface acoustic wave, can be used. In addition to the touch-sensitive surface, input unit 402 may also include other input devices. Specifically, other input devices may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0268] The processor 403 is the control center of the computer device, connecting various parts of the mobile phone through various interfaces and lines. It executes various functions and processes data by running or executing software programs and / or modules stored in the memory 401, and by calling data stored in the memory 401. Optionally, the processor 403 may include one or more processing cores; preferably, the processor 403 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 403.

[0269] The computer device also includes a power supply 404 (such as a battery) to power various components. Preferably, the power supply can be logically connected to the processor 403 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 404 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0270] Although not shown, the computer device may also include a camera, Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 403 in the computer device loads the executable files corresponding to the processes of one or more applications into the memory 401 according to the following instructions, and the processor 403 runs the applications stored in the memory 401 to realize various functions, as follows:

[0271] A target meeting is created in the first client, the target meeting including at least one object; when the start condition of the target meeting is triggered, the meeting invitation information of the target meeting is sent to the second client corresponding to the object through the message channel of the first client, and a list of objects of the target meeting is created, the list of objects including at least objects whose meeting invitation status is not yet joined; the response information of the second client to the meeting invitation information is obtained; the meeting invitation status of the objects in the object list is updated according to the response information.

[0272] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0273] As can be seen from the above, the computer device in this embodiment can manage non-participating participants in a meeting through a meeting participant list. Specifically, the computer device can update the meeting invitation status of participants in the participant list based on the response information of the corresponding client to the meeting invitation information. In this way, the computer device can promptly obtain the response results of the participants to the meeting invitation information and update the non-participating participants in the participant list in a timely manner based on the response results, allowing for dynamic adjustment of the non-participating participants in the participant list. Moreover, by updating the meeting invitation status of non-participating participants through the participant list, the computer device enables the meeting administrator to know the current meeting invitation status of non-participating participants and then perform meeting invitation operations for non-participating participants based on the meeting invitation status. In this way, the management efficiency of the meeting and the user experience can be improved by improving the management efficiency of non-participating participants.

[0274] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0275] Therefore, embodiments of this application provide a storage medium storing multiple instructions that can be loaded by a processor to execute steps in any of the meeting object management methods provided in embodiments of this application. For example, the instructions can execute the following steps:

[0276] A target meeting is created in the first client, the target meeting including at least one object; when the start condition of the target meeting is triggered, the meeting invitation information of the target meeting is sent to the second client corresponding to the object through the message channel of the first client, and a list of objects of the target meeting is created, the list of objects including at least objects whose meeting invitation status is not yet joined; the response information of the second client to the meeting invitation information is obtained; the meeting invitation status of the objects in the object list is updated according to the response information.

[0277] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0278] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0279] Since the instructions stored in the storage medium can execute the steps in any of the meeting object management methods provided in the embodiments of this application, the beneficial effects that any of the meeting object management methods provided in the embodiments of this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0280] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations of the aforementioned aspects of conference object management.

[0281] The foregoing has provided a detailed description of a method, apparatus, electronic device, and storage medium for managing meeting participants according to embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for managing meeting participants, comprising: A target meeting is created in the first client, the target meeting comprising at least one object; When the conditions for starting the target meeting are triggered, the meeting invitation information of the target meeting is sent to the second client corresponding to the object through the message channel of the first client, and a delay task for the meeting invitation information of the object is created, and a list of objects for the target meeting is created. The list of objects includes at least objects whose meeting invitation status is "not yet joined". The delay task is used to obtain the current information status corresponding to the meeting invitation information of the object, and to verify the current information status so as to update the information status corresponding to the meeting invitation information according to the verification result. Obtain the response information from the second client in response to the meeting invitation information; The meeting invitation status of the objects in the object list is updated according to the response information; wherein, the meeting invitation status of the objects that have not joined the meeting includes available to invite, calling, rejected, or timed out; the object list has a view control for viewing the historical meeting invitation status for each object, and in response to the trigger operation of the view control, the historical meeting invitation status of the object is obtained from the object status set and displayed. Set a meeting invitation control for the non-participating objects. The meeting invitation control includes a call control for all non-participating objects and a single call control for each non-participating object. When the same object has multiple terminals, when the same object responds to the meeting invitation information through one terminal, invitation cancellation information is sent to the other terminals of the same object.

2. The method for managing meeting participants according to claim 1, characterized in that, Update the meeting invitation status of objects in the object list based on the response information, including: Determine meeting invitation information that is associated with the object; Update the information status of the meeting invitation information based on the response information; Update the meeting invitation status of the object based on the updated information status.

3. The method for managing meeting participants according to claim 2, characterized in that, Based on the response information, the information status of the meeting invitation information is updated, including: Determine the timing attributes of the response information; The response information is verified based on the timing attributes. If the verification passes, the information status of the meeting invitation information will be updated according to the response information.

4. The method for managing meeting participants according to claim 1, characterized in that, After sending the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, the method further includes: Establish the association between the meeting invitation information and the object; Based on the sending result and the aforementioned association, the information status corresponding to the meeting invitation information is updated.

5. The method for managing meeting participants according to claim 4, characterized in that, Based on the sending result and the aforementioned association, the information status corresponding to the meeting invitation information is updated, including: Based on the sending result and the aforementioned association, a delayed task is created for the meeting invitation information; When the execution condition of the delayed task is triggered, the current information status of the meeting invitation information is obtained through the delayed task; The current information status is verified; Based on the verification results, the information status corresponding to the meeting invitation information is updated.

6. The method for managing meeting participants according to claim 1, characterized in that, Create a list of objects for the target meeting, including at least objects whose meeting invitation status is "not yet joined," such as: Obtain the object information of the object; Based on the object information, a list of non-attendees for the target meeting is created, which includes objects whose meeting invitation status is "non-attendee".

7. The method for managing meeting participants according to claim 1, characterized in that, After updating the meeting invitation status of objects in the object list based on the response information, the method further includes: If the updated meeting invitation status of the object is detected to meet the preset status, then a third client to cancel the meeting invitation is determined from the second client. Generate an invitation cancellation message for the target meeting, the invitation cancellation message instructing the client to cancel the meeting invitation for the target meeting; Send the invitation cancellation information to the third client.

8. The method for managing meeting participants according to claim 7, characterized in that, The third client to be canceled from the second client includes: From the second client, determine the fourth client corresponding to the object when it first responds to the meeting invitation information; Based on the fourth client, a third client is determined from the second client to cancel the meeting invitation.

9. The method for managing meeting participants according to claim 1, characterized in that, A target meeting is created in the first client, the target meeting comprising at least one object, including: The first client identifies the recipients of the target meeting invitation and obtains the meeting settings information for the target meeting. Based on the meeting invitation recipients and the meeting settings information, a target meeting is created in the first client.

10. The method for managing meeting participants according to claim 1, characterized in that, The object list includes a list of non-members, and the list of non-members includes at least one non-member. After updating the meeting invitation status of objects in the object list based on the response information, the method further includes: If the updated meeting invitation status of the non-participating object is detected to meet the preset status, then a meeting invitation control for the non-participating object will be displayed in the non-participating list. In response to a meeting invitation operation on the meeting invitation control, a meeting invitation operation is performed on the non-participating object.

11. The method for managing meeting participants according to claim 1, characterized in that, After updating the meeting invitation status of objects in the object list based on the response information, the method further includes: Based on the updated meeting invitation status of the object, a state set of the object is generated, wherein the state set includes the historical meeting invitation status of the object; The object list is updated based on the state set.

12. A device for managing meeting participants, characterized in that, include: A creation unit is used to create a target meeting in a first client, the target meeting comprising at least one object; The first sending unit is configured to, when the start condition of the target meeting is triggered, send the meeting invitation information of the target meeting to the second client corresponding to the object through the message channel of the first client, and create a delay task for the meeting invitation information of the object, and create an object list of the target meeting, the object list including at least objects whose meeting invitation status is "not yet joined"; the delay task is configured to obtain the current information status corresponding to the meeting invitation information of the object, and verify the current information status so as to update the information status corresponding to the meeting invitation information according to the verification result; The acquisition unit is used to acquire the response information of the second client to the meeting invitation information; The first update unit is used to update the meeting invitation status of objects in the object list according to the response information; wherein, the meeting invitation status of the objects that have not joined the meeting includes available to invite, calling, rejected, or timed out; the object list has a viewing control for the historical meeting invitation status for each object, and in response to the trigger operation of the viewing control, the historical meeting invitation status of the object is obtained from the object status set and the historical meeting invitation status of the object is displayed. The control setting unit is used to set meeting invitation controls for the non-participating objects. The meeting invitation controls include a call control for all non-participating objects and a single call control for each non-participating object. The cancellation unit is used to send invitation cancellation information to other terminals of the same object when the same object responds to the meeting invitation information through one of the terminals.

13. An electronic device, characterized in that, It includes a memory and a processor; the memory stores an application program, and the processor runs the application program within the memory to perform the operations in the meeting object management method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the method for managing meeting objects according to any one of claims 1 to 11.

15. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps in the method for managing meeting objects as described in any one of claims 1 to 11.

Images