Conference communication method, apparatus, device, and storage medium

Abstract

The application provides a conference communication method and device, equipment and storage medium, and relates to the technical field of communication. The method comprises the following steps: receiving a conference invitation ring sent by an instant messaging server, the conference invitation ring being sent by the instant messaging server when the instant messaging server receives a conference invitation ring request sent by a server of a target application, the conference invitation ring request being sent by the server of the target application when it is determined that a preset triggering condition is met, an interface for calling an SDK being set in an instant messaging application, the target application being an application with an audio and video conference function, if it is determined that the conference invitation ring is sent through a message channel, displaying an invitation interface of a target conference and ringing according to the conference invitation ring, and if it is determined that the conference invitation ring is sent through a long connection channel, popping up a conference invitation ring notification message of the target conference according to the conference invitation ring. Thus, the reach rate of the conference invitation and the access efficiency of the remote conference are improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a conference communication method, apparatus, device and storage medium. Background Technology

[0002] With the increasing prevalence of digital and networked office work, and the growing mobility of people's work and study, more and more companies are using audio and video conferencing to support remote work. Especially with the current pandemic, the usage rate of audio and video conferencing has risen even higher. A key aspect of remote work is the ability to promptly reach relevant work contacts when needed.

[0003] In existing conferencing software with audio and video conferencing capabilities, meeting invitations are typically sent to participants via a conferencing app by sending a meeting link or phone number. Participants then need to click the meeting link or dial the meeting number to join the meeting. This method results in low reach of meeting invitations, cumbersome user operations, and low efficiency in remote meeting access. Summary of the Invention

[0004] This application provides a conference communication method, apparatus, device, and storage medium to improve the reach rate of conference invitations and the access efficiency of remote conferences.

[0005] In a first aspect, this application provides a conference communication method applied to an instant messaging client, the method comprising:

[0006] The instant messaging client receives a meeting invitation ringtone sent by an instant messaging server. The meeting invitation ringtone is sent by the instant messaging server when it receives a meeting invitation ringtone request from the server of the target application. The meeting invitation ringtone request is sent by the server of the target application when it determines that a preset trigger condition is met. The instant messaging client is equipped with an interface for calling the software development kit (SDK) of the target application. The target application is an application with audio and video conferencing capabilities.

[0007] If it is determined that the meeting invitation ringtone was sent through the message channel, the invitation interface for the target meeting will be displayed and the ringtone will sound according to the meeting invitation ringtone;

[0008] If it is determined that the meeting invitation ringtone is sent through a long connection channel, a meeting invitation ringtone notification message for the target meeting will pop up based on the meeting invitation ringtone.

[0009] Secondly, this application provides a conference communication method, which is applied to an instant messaging server, and the method includes:

[0010] The instant messaging client receives a meeting invitation ringing request sent by the server of the target application when it determines that the preset triggering conditions are met. The instant messaging client is equipped with an interface for calling the software development kit (SDK) of the target application, which is an application with audio and video conferencing functions.

[0011] Based on the meeting invitation ringing request, obtain the participants of the target meeting;

[0012] If it is determined that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through the message channel;

[0013] If it is determined that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through a long connection channel.

[0014] Thirdly, this application provides a conference communication device, comprising:

[0015] The receiving module is used to receive a meeting invitation ringtone sent by the instant messaging server. The meeting invitation ringtone is sent by the instant messaging server when it receives a meeting invitation ringtone request sent by the server of the target application. The meeting invitation ringtone request is sent by the server of the target application when it determines that a preset trigger condition is met. The instant messaging client is provided with an interface for calling the software development kit (SDK) of the target application. The target application is an application with audio and video conferencing functions.

[0016] The display module is used to display the invitation interface of the target meeting and ring the bell when it is determined that the meeting invitation bell is sent through the message channel.

[0017] When it is determined that the meeting invitation ringtone is sent through a long connection channel, a meeting invitation ringtone notification message for the target meeting pops up based on the meeting invitation ringtone.

[0018] Fourthly, this application provides a conference communication device, comprising:

[0019] The receiving module is used to receive a meeting invitation ringing request sent by the server of the target application when a preset triggering condition is met. The instant messaging client is equipped with an interface for calling the software development kit of the target application, and the target application is an application with audio and video conferencing functions.

[0020] The acquisition module is used to acquire the participants of the target meeting based on the meeting invitation ringing request;

[0021] The sending module is used to send a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through a message channel when it is determined that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server.

[0022] When it is determined that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through a long connection channel.

[0023] Fifthly, this application provides a conference communication device, including: a processor and a memory, the memory for storing a computer program, and the processor for calling and running the computer program stored in the memory to perform the method described in the first aspect or any of the possible implementations of the first aspect or the second aspect or any of the possible implementations of the second aspect.

[0024] In a sixth aspect, this application provides a computer-readable storage medium for storing a computer program that causes a computer to perform the methods described in the first aspect or any of the possible implementations of the first aspect, or in the second aspect or any of the possible implementations of the second aspect.

[0025] In a seventh aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect or any of the possible implementations of the first aspect, or in the second aspect or any of the possible implementations of the second aspect.

[0026] In summary, this application achieves this by setting up an interface in the instant messaging client to call the SDK of the target application (which is an application with audio and video conferencing capabilities). When the instant messaging client receives a meeting invitation ringtone from the instant messaging server, if it determines that the meeting invitation ringtone was sent via a message channel, it displays the target meeting invitation interface and rings accordingly. If it determines that the meeting invitation ringtone was sent via a long-connection channel, it displays a meeting invitation ringtone notification message for the target meeting. When the instant messaging client is online, the meeting invitation ringtone is sent via a message channel, directly reaching the user; when the instant messaging client is offline, the meeting invitation ringtone is sent via a long-connection channel, also directly reaching the user. Thus, multi-channel delivery of meeting invitation ringtones is achieved, improving the reach rate of meeting invitations. When the instant messaging client is online, users can directly answer the meeting invitation ring to join the target meeting. On one hand, using a ringing method for meeting invitations, compared to message notifications, ensures timely delivery to users, increasing the reach rate of meeting invitations. On the other hand, compared to existing technologies where invited users need to click a meeting link or dial a meeting phone number, this application allows invited users to join the meeting with a simpler operation, improving the efficiency of remote meeting access. When the instant messaging client is offline (e.g., due to client malfunction or device restart), a meeting invitation ring is sent via a long-lived connection. The instant messaging client will display a meeting invitation ring notification message for the target meeting, which users will also receive promptly, thus increasing the reach rate of meeting invitations. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of the present invention, 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 the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 A schematic diagram of a conference communication method provided in this application embodiment;

[0029] Figure 2 A schematic diagram of a conference communication method provided in this application embodiment;

[0030] Figure 3 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0031] Figure 4 This is a schematic diagram of the invitation interface of a target conference in a conference communication method provided in an embodiment of this application;

[0032] Figure 5 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0033] Figure 6 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0034] Figure 7 A schematic diagram of a scheduled meeting interface displayed in an instant messaging client, provided as an embodiment of this application;

[0035] Figure 8 A schematic diagram of an interface for displaying candidate meeting participants in an instant messaging client, provided as an embodiment of this application;

[0036] Figure 9 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0037] Figure 10A A schematic diagram of the call status display interface for invited participants in a quick meeting, provided as an embodiment of this application;

[0038] Figure 10B A schematic diagram of the call status display interface for invited participants in a quick meeting, provided as an embodiment of this application;

[0039] Figure 11A A schematic diagram of a meeting invitation interface provided in an embodiment of this application;

[0040] Figure 11B A schematic diagram of a meeting invitation interface provided in an embodiment of this application;

[0041] Figure 12 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0042] Figure 13 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0043] Figure 14 An interactive flowchart of a conference communication method provided in an embodiment of this application;

[0044] Figure 15 This is a schematic diagram of the structure of a conference communication device provided in an embodiment of this application;

[0045] Figure 16 This is a schematic diagram of the structure of a conference communication device provided in an embodiment of this application;

[0046] Figure 17 This is a schematic block diagram of the conference communication device provided in the embodiments of this application. Detailed Implementation

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

[0048] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0049] Before introducing the technical solution of this application, the following is a brief introduction to relevant knowledge about this application:

[0050] 1. Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to achieve data computation, storage, processing, and sharing. Cloud technology is a general term encompassing network technology, information technology, integration technology, management platform technology, and application technology applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will require robust system support, which can only be achieved through cloud computing.

[0051] 2. Cloud conferencing: Cloud conferencing is an efficient, convenient, and low-cost meeting format based on cloud computing technology. Users only need to use an internet interface for simple and easy-to-use operations to quickly and efficiently share voice, data files, and video with teams and clients around the world. The complex technologies such as data transmission and processing during the meeting are handled by the cloud conferencing service provider.

[0052] Cloud conferencing primarily focuses on services based on the SaaS (Software as a Service) model, including telephone, internet, and video services. Video conferencing based on cloud computing is called cloud conferencing. In the era of cloud conferencing, data transmission, processing, and storage are all handled by the computer resources of the video conferencing provider. Users no longer need to purchase expensive hardware or install cumbersome software; they only need to open a browser, log in to the corresponding interface, and they can conduct efficient remote meetings.

[0053] The audio and video conferencing implementation method provided in this application embodiment can be implemented based on the above-mentioned cloud technology. Specifically, it can integrate the powerful cloud computing capabilities and audio and video technology capabilities in cloud technology, and can realize audio and video conferencing functions based on communication software with audio and video conferencing functions.

[0054] Existing conferencing software with audio and video conferencing capabilities suffers from low reach rates for meeting invitations, cumbersome user operations, and low efficiency in remote meeting access. To address these issues, this application establishes an interface within the instant messaging client for calling the Software Development Kit (SDK) of a target application (an application with audio and video conferencing capabilities). This allows the instant messaging client to access the target application. When the instant messaging client receives a meeting invitation ringtone from the instant messaging server, if it determines the ringtone was sent via a message channel, it displays the target meeting invitation interface and rings accordingly. If it determines the ringtone was sent via a long-connection channel, it displays a meeting invitation notification message for the target meeting. When the instant messaging client is online, the meeting invitation ringtone is sent via a message channel, directly reaching the user; when the client is offline, it is sent via a long-connection channel, also directly reaching the user. This multi-channel delivery of meeting invitation ringtones improves the reach rate of meeting invitations. When the instant messaging client is online, users can directly answer the meeting invitation ring to join the target meeting. On one hand, using a ringing method for meeting invitations, compared to message notifications, ensures timely delivery to users, increasing the reach rate of meeting invitations. On the other hand, compared to existing technologies where invited users need to click a meeting link or dial a meeting phone number, this application allows invited users to join the meeting with a simpler operation, improving the efficiency of remote meeting access. When the instant messaging client is offline (e.g., due to client malfunction or device restart), a meeting invitation ring is sent via a long-lived connection. The instant messaging client will display a meeting invitation ring notification message for the target meeting, which users will also receive promptly, thus increasing the reach rate of meeting invitations.

[0055] The technical solution of this application will be described in detail below:

[0056] For example, Figure 1 This application provides a schematic diagram of the system architecture for a conference communication method, as shown in the embodiments below. Figure 1 As shown, the system architecture may include an instant messaging server 1, a target application server 2, a first terminal device 3, and a second terminal device 4. The instant messaging application is an application capable of instant communication, and the target application is an application with audio and video conferencing capabilities. The first terminal device 3 and the second terminal device 4 can be personal computers, laptops, smart terminals, tablets, and portable wearable devices, etc. The instant messaging server 1 can be a standalone physical server or a server cluster or distributed system composed of multiple physical servers. The target application server 2 can be a standalone physical server or a server cluster or distributed system composed of multiple physical servers, or it can be 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 first terminal device 3 and the second terminal device 4 can communicate with the instant messaging server 1 or the target application server 2 via a network.

[0057] For example, an instant messaging application client can be installed and run on the first terminal device 3 and the second terminal device 4. This instant messaging application has an interface for calling the SDK of the target application. The first terminal device 3 can be a terminal device used by a first user, and the second terminal device 4 can be a terminal device used by a second user. The first user schedules a meeting or initiates a quick meeting through the first terminal device; therefore, the first user can be called the meeting initiator, and the second user can be a user invited by the first user to participate in the meeting (referred to as a meeting participant). Figure 1As shown, in one feasible approach, a first user can initiate a meeting invitation to a second user by operating an instant messaging application on a first terminal device 3, for example, during a meeting or at the very beginning of a meeting (e.g., when the first user invites participants when initiating a quick meeting). In response to the user's action of initiating the call for participants, the instant messaging client on the first terminal device 3 sends an invitation request to the instant messaging server 1. This invitation request carries the identifier of the calling user (e.g., the identifier of the second user) and a meeting identifier. The instant messaging server 1 sends the invitation request to the server 2 of the target application. Upon receiving the invitation request, the target application server 2 sends a meeting invitation ringing request to the instant messaging server 1. This meeting invitation ringing request carries the identifier of the calling user. The instant messaging server 1 then sends the meeting invitation ringing to the instant messaging client corresponding to the calling user based on the identifier of the calling user. Figure 1 As shown, a meeting invitation ring is sent to the instant messaging client corresponding to the second user. If the instant messaging client of the second terminal device 4 used by the second user determines that the meeting invitation ring is sent through a message channel, it displays the invitation interface of the target meeting and rings the bell according to the meeting invitation ring; if it determines that the meeting invitation ring is sent through a long connection channel, it pops up a meeting invitation ring notification message of the target meeting according to the meeting invitation ring.

[0058] Figure 2 This application provides a schematic diagram of the system architecture for a conference communication method, as shown in the embodiments below. Figure 2As shown, in another feasible approach, for example, a first user schedules a meeting by operating an instant messaging application on a first terminal device. When scheduling the meeting, the user can select the participants (e.g., including a second user, who naturally also includes the first user). When the server 2 of the target application determines the meeting start time, it sends a meeting invitation ringback request to the instant messaging server 1. This meeting invitation ringback request carries the identifier of the target meeting. Based on the meeting scheduling identifier carried in the meeting invitation ringback request, the instant messaging server 1 searches for the participants in the meeting scheduling list. Instant messaging server 1 can send meeting invitation ringtones to participating users (including the first user and the second user) who have scheduled a meeting. Specifically, instant messaging server 1 sends meeting invitation ringtones to the instant messaging clients of the first terminal device 3 and the second terminal device 4. If the instant messaging client of the first terminal device 3 determines that the meeting invitation ringtone is sent via a message channel, it displays the invitation interface for the target meeting and rings the bell; if it determines that the meeting invitation ringtone is sent via a long connection channel, it displays a meeting invitation ringtone notification message for the target meeting. Similarly, if the instant messaging client of the second terminal device 4 determines that the meeting invitation ringtone is sent via a message channel, it displays the invitation interface for the target meeting and rings the bell; if it determines that the meeting invitation ringtone is sent via a long connection channel, it displays a meeting invitation ringtone notification message for the target meeting.

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

[0060] Figure 3 An interactive flowchart of a conference communication method provided in an embodiment of this application is shown below. Figure 3 As shown, the method may include the following steps:

[0061] S101. When the target application's server determines that the preset triggering conditions are met, it sends a meeting invitation ringing request to the instant messaging server.

[0062] Specifically, in this embodiment, the instant messaging application is provided with an interface for calling the software development kit (SDK) of the target application. This interface can be an Application Programming Interface (API). Optionally, the instant messaging application can be an instant messaging application used for enterprise or company internal communication. The target application is an application with audio and video conferencing capabilities.

[0063] Optionally, the preset trigger condition can be: the meeting start time of the scheduled meeting is reached; or, receiving an invitation request from an instant messaging server to participate in the meeting.

[0064] In this embodiment of the application, there are three scenarios in which the meeting invitation ringtone is sent to the instant messaging client: the first is when the scheduled meeting start time arrives; the second is when the meeting initiator initiates a quick meeting; and the third is when a new user is invited to participate in an ongoing meeting. The preset trigger condition for the first scenario is when the scheduled meeting start time arrives. The preset trigger conditions for the second and third scenarios are when the server of the target application receives the request to invite users to participate from the instant messaging server.

[0065] S102. The instant messaging server retrieves the participants of the target meeting based on the meeting invitation ringing request.

[0066] Specifically, in the case of scheduled meetings, in one feasible approach, the meeting invitation ring request carries the identifier of the target meeting. Accordingly, step S102 can be: based on the identifier of the target meeting carried in the meeting invitation ring request, search for the participants of the target meeting from the meeting reservation list. When scheduling a meeting, the instant messaging server stores the identifiers of the participants and the meeting identifier of the scheduled meeting in the meeting reservation list. Based on the identifier of the target meeting, the identifier of the participants of the target meeting can be found from the meeting reservation list.

[0067] When a meeting initiator initiates a quick meeting, or when a meeting initiator invites new participants during an ongoing meeting, the instant messaging server sends an invitation request to the target application server. This invitation request carries the identifier of the calling participant and the meeting identifier (whether it's a quick meeting or an ongoing meeting). Upon receiving the invitation request, the target application server sends a meeting invitation ringing request to the instant messaging server. This ringing request carries the identifier of the calling participant. Accordingly, step S102 can be: determining the participants of the target meeting based on the identifier of the calling participant carried in the meeting invitation ringing request; that is, the identifier of the calling participant is the identifier of the participants in the target meeting.

[0068] Optionally, before S102, the following may also be included:

[0069] The meeting invitation ringing request is stored in a message queue. When the meeting invitation ringing request is removed from the message queue, the participants of the target meeting are retrieved based on the meeting invitation ringing request.

[0070] Specifically, since there may be a large number of invited participants, storing the meeting invitation ringing request in a message queue for asynchronous processing can avoid timeouts affecting system stability.

[0071] S103. If the instant messaging server determines that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server, it sends a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through the message channel; if it determines that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, it sends a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through the long connection channel.

[0072] Specifically, if a participant's instant messaging client is online (e.g., the instant messaging client is logged in or in use), the instant messaging server can determine that the participant's instant messaging client is connected to the instant messaging server; if a participant's instant messaging client is offline (e.g., the instant messaging client is not logged in), the instant messaging server can determine that the participant's instant messaging client is not connected to the instant messaging server.

[0073] Specifically, the instant messaging server sends a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through the message channel. This can be done by sending a message to the message channel of the participant of the target meeting. If the instant messaging client of the participant of the target meeting is online, the message will be received immediately.

[0074] If the instant messaging server determines that the instant messaging client corresponding to a participant in the target meeting is not connected to the instant messaging server, it sends a meeting invitation ringtone to the corresponding instant messaging client through a long-lived connection. Optionally, sending the meeting invitation ringtone to the corresponding instant messaging client through the long-lived connection can be done by the instant messaging server sending either a first message type meeting invitation ringtone or a second message type meeting invitation ringtone. Optionally, the first message type meeting invitation ringtone could be, for example, a pushkit message, which can reduce application power consumption; the second message type meeting invitation ringtone could be, for example, an APNS message.

[0075] Optionally, if the terminal device on which the instant messaging client is running is running an iOS system, the long connection channel can be a push channel; if the terminal device on which the instant messaging client is running is running an Android or other system, the long connection channel can be a message channel defined by the terminal device manufacturer.

[0076] S104. If the instant messaging client determines that the meeting invitation ringtone is sent through the message channel, it will display the invitation interface of the target meeting and ring the bell according to the meeting invitation ringtone.

[0077] Specifically, in one feasible approach, the invitation interface for the target meeting can be, for example, as follows: Figure 4 As shown, Figure 4 This is a schematic diagram of the invitation interface for a target meeting in a conference communication method provided in this application embodiment. This invitation interface is merely an example. The interface can display function keys to select "Slide to enter meeting" and "Don't enter yet," as well as the number of initiators and participants in the target meeting. Optionally, it can also display the names of the participants. It is understood that the ringing can be performed according to the user-defined ringing mode, such as normal ringing, vibration, and silence, and can be consistent with the ringing mode set on the user's terminal device.

[0078] Optionally, following S104, the following may also be included:

[0079] In response to the ringing of the meeting invitation by a participant in the target meeting, the instant messaging client calls the SDK of the target application and displays the meeting interface for the participant to join the target meeting.

[0080] Specifically, for example, the instant messaging client displays the invitation interface for the target meeting as follows: Figure 4 As shown, participating users follow Figure 4 When the circular icon is slid in the direction of the arrow shown, it indicates that the participating user has answered the meeting invitation ringing action. In response to this action by the participating user, the instant messaging client calls the SDK of the target application, which will then display the meeting interface for the participating user to join the target meeting.

[0081] S105. If the instant messaging client determines that the meeting invitation ringtone is sent through a long connection channel, it will pop up a meeting invitation ringtone notification message for the target meeting based on the meeting invitation ringtone.

[0082] Specifically, if the instant messaging client determines that the meeting invitation ringtone was sent via a long-lived connection, meaning the ringtone was sent while the client was offline, the client will then display a meeting invitation notification message for the target meeting. This notification message could, for example, say "A invites you to a meeting," where A is the meeting initiator. Optionally, the notification message may also include the time. Optionally, this notification message can be in a format similar to system push messages.

[0083] Specifically, as an implementable method, the instant messaging client can display a meeting invitation notification message for the target meeting upon receiving the meeting invitation ring. This can be:

[0084] If the message type of the meeting invitation ring is the first message type, a meeting invitation ring notification message for the target meeting will pop up, triggering the terminal device to ring and launching the instant messaging client.

[0085] Optionally, the first message type for the meeting invitation ringtone could be a Pushkit message, which can reduce application power consumption. The second message type for the meeting invitation ringtone could be an APNS message. The triggering of the terminal device's ringing can be based on the terminal device's current ringing state, such as vibration, ring, or silence. Alternatively, it can trigger the terminal device to ring according to a preset ringing method.

[0086] If the message type for the meeting invitation ring is the second message type, a meeting invitation ring notification message for the target meeting will pop up.

[0087] The conferencing communication method provided in this embodiment enables the instant messaging client to call the SDK of a target application (an application with audio and video conferencing capabilities) by setting an interface in the instant messaging client. When the instant messaging client receives a meeting invitation ringtone from the instant messaging server, if it determines that the meeting invitation ringtone was sent through a message channel, it displays the invitation interface of the target meeting and rings the bell; if it determines that the meeting invitation ringtone was sent through a long connection channel, it pops up a meeting invitation ringtone notification message for the target meeting. When the instant messaging client is online, the meeting invitation ringtone is sent through a message channel, directly reaching the user; when the instant messaging client is offline, the meeting invitation ringtone is sent through a long connection channel, also directly reaching the user. Therefore, multi-channel delivery of meeting invitation ringtones is achieved, improving the reach rate of meeting invitations. When the instant messaging client is online, users can directly answer the meeting invitation ring to join the target meeting. On one hand, using a ringing method for meeting invitations, compared to message notifications, ensures timely delivery to users, increasing the reach rate of meeting invitations. On the other hand, compared to existing technologies where invited users need to click a meeting link or dial a meeting phone number, this application allows invited users to join the meeting with a simpler operation, improving the efficiency of remote meeting access. When the instant messaging client is offline (e.g., due to client malfunction or device restart), a meeting invitation ring is sent via a long-lived connection. The instant messaging client will display a meeting invitation ring notification message for the target meeting, which users will also receive promptly, thus increasing the reach rate of meeting invitations.

[0088] The method in this embodiment is... Figure 3 Based on the illustrated embodiment, further, in S104, before the meeting invitation interface of the target meeting is displayed and the bell rings according to the meeting invitation, the following may also be included:

[0089] S106. The instant messaging client sends an inquiry request to the instant messaging server to inquire whether to display the invitation interface of the target meeting and ring the bell.

[0090] S107. After obtaining the login status of the target application client, the instant messaging server obtains the current status of the target meeting from the target application's server. The current status includes whether the meeting has ended or not.

[0091] Specifically, the instant messaging server can send a query request to the server of the target application to check the current status of the target meeting, in order to find out whether the target meeting has ended.

[0092] S108. The instant messaging server determines the response message for the query request based on the current status of the target meeting.

[0093] Specifically, if the current status of the target meeting is that the meeting has ended, the response message for the query request is determined to be that the invitation interface of the target meeting does not need to be displayed and the bell rings; if the current status of the target meeting is that the meeting has not ended, the response message for the query request is determined to be that the invitation interface of the target meeting needs to be displayed and the bell rings.

[0094] S109. The instant messaging server sends a response message to the instant messaging client regarding the query request.

[0095] Specifically, the response message to the query request includes instructions on whether to display the invitation interface for the target meeting and ring the bell.

[0096] S110: The instant messaging client determines and displays the invitation interface for the target meeting and rings the bell based on the response message of the inquiry request.

[0097] Specifically, if the response message to the query request indicates that the invitation interface of the target meeting is displayed and the ringing is performed, then it is determined that the invitation interface of the target meeting is displayed and the ringing is performed; if the response message to the query request indicates that the invitation interface of the target meeting is not displayed and the ringing is performed, then it is determined that the invitation interface of the target meeting is not displayed and the ringing is performed.

[0098] Furthermore, if the response message to the query request indicates that the invitation interface of the target meeting is displayed and a ringtone is sounded, the method of this embodiment may further include:

[0099] The instant messaging server obtains the current participation status of the participating user corresponding to the instant messaging client from the server of the target application. The current participation status includes whether the participating user has joined the target meeting or not. Based on the current participation status of the participating user corresponding to the instant messaging client, the server determines the response message for the query request.

[0100] Specifically, users can install and run the same instant messaging client on multiple terminal devices and use the same instant messaging account. A user may already be joining the target meeting on another terminal device, so there's no need for the same account to be used on multiple devices. If the current meeting status indicates that the user is already in the target meeting, the response message to the query request is to not display the target meeting's invitation interface and to ring the bell; otherwise, the response message is to display the target meeting's invitation interface and to ring the bell. In this embodiment, by obtaining the current meeting status of the user through the instant messaging server, it can be determined whether the user has joined the target meeting. If the user has joined, the instant messaging client is instructed not to display the target meeting's invitation interface and to ring the bell, thus preventing the same account from being used on multiple devices.

[0101] The conference communication method provided in this embodiment involves the instant messaging client sending an inquiry request to the instant messaging server before the invitation interface of the target conference is displayed and the ringing occurs. The instant messaging server then sends a response message to the instant messaging client based on the current status of the target conference. The instant messaging client determines whether to display the invitation interface of the target conference and ring the ringing based on the response message of the inquiry request, thereby avoiding the display of the invitation interface of the target conference and the ringing of the ringing even after the conference has ended.

[0102] Figure 5 An interactive flowchart of a conference communication method provided in an embodiment of this application is shown below. Figure 5 As shown, S201-S205 of this embodiment and Figure 3 In the illustrated embodiment, steps S101-S105 are the same. Further, after step S205, the following may also be included:

[0103] S206. The instant messaging client sends the meeting invitation ring status to the instant messaging server. The meeting invitation ring status includes any one of the following: answered, rejected, and sent and timed out.

[0104] Specifically, a user may answer or reject a meeting invitation ringtone, resulting in a status of "answered" or "rejected." Another scenario is that if the user's device is powered off or not connected to the network (e.g., out of service area), the device may not receive the meeting invitation ringtone, in which case the status will be "sent and timed out." For instance, after sending the meeting invitation ringtone to an instant messaging client, the instant messaging server simultaneously creates a task with a preset delay time (e.g., 45 seconds). If no meeting invitation ringtone is received from an instant messaging client after the preset time, the client's meeting invitation ringtone status is determined to be "sent and timed out."

[0105] S207. The instant messaging server updates the call status of each participant based on the meeting invitation ringing status of each participant in the target meeting.

[0106] Specifically, the call status of participating users includes callable status, calling status, and called status. If the instant messaging server receives the meeting invitation ringing status of a participating user, it can update the calling status of that participating user, for example, it can update the user's calling status to called status.

[0107] It should be noted that the same account's instant messaging client can run on multiple terminal devices. When multiple terminal devices' instant messaging clients report the meeting invitation ringing status, the instant messaging server only receives the meeting invitation ringing status reported by the first terminal device. Optionally, when the instant messaging server receives the meeting invitation ringing status reported by the first terminal device, it will send a multi-terminal screen reduction control message to the instant messaging clients on other terminal devices to notify them that they do not need to report the meeting invitation ringing status.

[0108] S208. When the meeting invitation ringing status is rejected or has been sent and timed out, the instant messaging server sends the entry information of the target meeting to the instant messaging client.

[0109] Specifically, the entry information for the target meeting can be any of the following: a short link, a meeting ID, or a meeting card, making it convenient for users to access the target meeting later using this entry information.

[0110] Optionally, the instant messaging server can send an entry information request to the server of the target application. The server of the target application sends the entry information of the target meeting to the instant messaging server, which then sends the entry information of the target meeting to the instant messaging client.

[0111] S209. The instant messaging client displays the entry information for the target meeting.

[0112] In the above embodiments of this application, there are three scenarios where a meeting invitation ring is sent to the instant messaging client: the first is when the scheduled meeting start time arrives; the second is when the meeting initiator initiates a quick meeting and invites participating users; and the third is when a new participating user is invited during an ongoing meeting. The preset trigger condition for the first scenario is the arrival of the scheduled meeting start time. The preset trigger conditions for the second and third scenarios are that the target application's server receives the invitation request for participating users sent by the instant messaging server. The following is a combination of... Figure 6 The illustrated embodiment provides a detailed description of the process for the first scenario, in conjunction with... Figure 9 The illustrated embodiment provides a detailed description of the second scenario, in conjunction with... Figure 12 The illustrated embodiment provides a detailed description of the process for the third scenario.

[0113] Figure 6 This application provides an interactive flowchart of a conference communication method, which illustrates the process of scheduling a conference and the process of sending a conference invitation ringing signal. Figure 6 As shown, the method in this embodiment may include:

[0114] S301. In response to the user clicking the icon used to enter the target application, the instant messaging client calls the SDK of the target application and displays the homepage of the target application.

[0115] Optionally, the icon used to access the target application can also display instructions such as "Meeting" to prompt the user to click. For example, if the user needs to use a remote meeting, they can click the icon to access the target application. The instant messaging client calls the SDK of the target application and can directly display the homepage of the target application, making it easier for the user to perform further operations.

[0116] S302. In response to the user's action of triggering a meeting appointment, the instant messaging client calls the SDK of the target application and displays the meeting appointment interface.

[0117] Optionally, the target application's homepage may display operation options such as "Schedule a Meeting", "Quick Meeting" and "Join a Meeting". The user can trigger the scheduling of a meeting by clicking the corresponding icon. Figure 7 A schematic diagram of a scheduled meeting interface displayed in an instant messaging client, as provided in an embodiment of this application, is shown below. Figure 7 As shown, the meeting scheduling interface displays the meeting start time (e.g., ...). Figure 7 The options shown include December 31st, 21:30, meeting duration, audio / video conferencing options, meeting settings, meeting room selection, calendar, etc., as well as icons for adding participants to the scheduled meeting (e.g., ...). Figure 7(Participants in the "+") Figure 7 This is just one example, and this application is not limited to it.

[0118] S303. In response to the user's action of adding participants to the scheduled meeting on the meeting scheduling interface, the instant messaging client displays an interface for the user to select candidate participants. The candidate participants include at least the users in the instant messaging client's address book.

[0119] Specifically, with Figure 7 Taking the meeting scheduling interface as an example, the user's action of adding participants to the meeting scheduling interface is the user clicking the "+" icon. The instant messaging client responds to this click by displaying an interface of candidate participants for the user to select. Figure 8 This application provides an embodiment of an interface diagram showing candidate meeting participants displayed in an instant messaging client. The candidate meeting participants include at least users from the instant messaging client's address book, such as... Figure 8 As shown, candidate participants include those selected from group chats, my clients, users from the company address book, and recent contacts, etc. Figure 8 This is just one example, and this application is not limited to it.

[0120] S304. In response to the user's operation of selecting participants for a scheduled meeting and the user's operation of setting meeting information for the scheduled meeting, the instant messaging client sends a meeting scheduling request to the instant messaging server. The meeting scheduling request includes the identifiers of the participants for the scheduled meeting and the meeting information for the scheduled meeting.

[0121] Specifically, such as Figure 8 As shown, after the meeting initiator selects the participants to schedule the meeting based on the candidate participant interface, according to... Figure 7 After setting the meeting information on the scheduled meeting interface, click... Figure 7 Once the save button is pressed, the meeting will be successfully scheduled. At this point, the instant messaging client sends a meeting scheduling request to the instant messaging server. The meeting scheduling request includes the identifiers of the participating users and the meeting information.

[0122] S305. The instant messaging server sends a meeting creation request to the server of the target application. The meeting creation request carries the meeting information of the scheduled meeting.

[0123] Optionally, in the method of this embodiment, before the instant messaging server sends a meeting creation request to the server of the target application in S305, it may further include:

[0124] The instant messaging server generates verification information for the participants of the scheduled meeting based on their identifiers, and stores the correspondence between the participants' identifiers and their verification information in the verification information list.

[0125] Accordingly, the instant messaging server sends a meeting invitation ringtone to the instant messaging client corresponding to the participants of the target meeting. Specifically, it can do this by verifying the verification information of the participants of the target meeting according to the verification information list, and sending a meeting invitation ringtone to the instant messaging client corresponding to the participants of the target meeting who have passed the verification.

[0126] By generating verification information for participants who have scheduled a meeting, the system ensures that when sending meeting invitation ringtones to the instant messaging clients of the target meeting participants, the meeting invitation ringtones are only sent to the instant messaging clients of the verified participants, thus guaranteeing the security of the meeting.

[0127] S306. The target application's server creates a scheduled meeting based on the meeting creation request and assigns a meeting identifier to the created scheduled meeting.

[0128] S307. The instant messaging server generates a link to schedule a meeting and sends the link to schedule the meeting to the target application's server.

[0129] Optionally, before the instant messaging server generates the link information for scheduling a meeting, it may also include: receiving a request from the target application's server to generate the link information for scheduling a meeting.

[0130] S308. The target application server sends a response message to the instant messaging server to indicate that the scheduled meeting has been successfully created. The response message carries the meeting identifier of the scheduled meeting.

[0131] S309. The instant messaging server stores the identifiers of the participants in the scheduled meeting and the meeting identifier in the meeting reservation list.

[0132] S310. When the server of the target application determines the meeting start time of the scheduled meeting, it sends a meeting invitation ringing request to the instant messaging server.

[0133] S311: The instant messaging server retrieves the participants of the target meeting based on the meeting invitation ringing request.

[0134] Specifically, the meeting invitation ring request carries the identifier of the target meeting. The meeting reservation list stores the correspondence between the identifiers of the users who have reserved the meeting and the meeting identifiers. The instant messaging server retrieves the users who will attend the target meeting based on the meeting invitation ring request. Specifically, this can be done by:

[0135] Based on the identifier of the target meeting carried in the meeting invitation ring request, find the participants of the target meeting from the meeting reservation list.

[0136] S312-S314 and Figure 3 The steps S103-S105 shown are the same, and will not be repeated here.

[0137] Figure 9 This application provides an interactive flowchart of a conference communication method. This embodiment describes the process of issuing a conference invitation bell when a conference initiator initiates a quick conference and invites participating users. Figure 9 As shown, the method in this embodiment may include:

[0138] S401: In response to the user's triggering of a quick meeting, the instant messaging client calls the target application's SDK and displays the quick meeting interface.

[0139] S402. In response to the user's action of adding participants to a quick meeting on the quick meeting interface, the instant messaging client displays an interface for the user to select candidate participants. The candidate participants include at least the users in the instant messaging client's address book.

[0140] Specifically, as an implementable approach, the interface for users to select candidate attendees can be [interface name missing]. Figure 8 The interfaces of the candidate participants shown are the same.

[0141] S403: In response to the user's selection of participants for a quick meeting, the instant messaging client displays the call status of the invited participants for the quick meeting. The invited participants are the participants selected by the user.

[0142] Specifically, after the meeting initiator (also known as the host) selects the participants for the quick meeting, the selected participants become the invited participants for that quick meeting. The instant messaging client displays a call status display interface for the invited participants. Optionally, the call status display interface includes at least one of the following: the identifier of the invited participant, the call status of the invited participant, the identifier of the participants who have joined the meeting, and the number of participants who have joined the meeting. Other information may also be included, and this application does not limit this information.

[0143] For example, Figure 10A This application provides a schematic diagram of a call status display interface for invited participants in a quick meeting, as shown in the embodiments of this application. Figure 10A As shown, the call status display interface will show the call status of each user to be invited to the meeting (in a callable state; the user can click the call button to call the corresponding user), and 5 users to be invited to the meeting (i.e., Figure 10A The participants not yet invited (5) are: Gao X, Li XX, gdl, Gigi, and jimmy. The meeting initiator can choose to click "Call All" or select individual participants one by one. Alternatively, the initiator can search for participants to be invited.

[0144] Figure 10B This application provides a schematic diagram of a call status display interface for invited participants in a quick meeting, as shown in the embodiments of this application. Figure 10B As shown, the call status display interface displays each user to be invited to the meeting, a selection box for choosing users to be invited, and the number of users who have already joined the meeting (i.e., the number of users who have joined the meeting). Figure 10A The meeting shown includes -1) and the number of users to be invited (i.e., Figure 10A As shown in Figure 5 (not yet entered), and the call button, the meeting initiator can select the invited participants to be called by clicking the selection box of the invited participants, such as... Figure 10B The current selected users are GaoX and Jimmy, who are initiating the call.

[0145] It should be noted that, Figure 10A and Figure 10B The call status display interface shown is merely an example and does not constitute a limitation of this application.

[0146] S404. In response to a user's action of triggering a call to at least one of the invited participants, the instant messaging client displays a meeting invitation interface and sends an invitation request to the instant messaging server.

[0147] Optionally, the meeting invitation interface may include at least one of the following: the identifier of the user to be invited, the call status of the user to be invited, the identifier of the user already connected to the meeting, and the number of users already connected to the meeting. Other information may also be included, and this application does not limit this.

[0148] Optional, with Figure 10A The interface shown depicts the call status of users awaiting invitation in a quick meeting. If the meeting initiator selects to click "Call All," the instant messaging client responds to this action by displaying the meeting invitation interface, as exemplified. Figure 11A A schematic diagram of a meeting invitation interface provided in an embodiment of this application, such as... Figure 11A As shown, the meeting invitation interface displays the call status (in progress) of each invited user. If the meeting initiator clicks the icon corresponding to "Not Entering -5", then... Figure 11A The interface shown will display the following if the meeting initiator clicks the icon corresponding to -1 (currently only one meeting host is in the meeting): Figure 11B The interface shown is Figure 11BA schematic diagram of a meeting invitation interface provided in an embodiment of this application, such as... Figure 11B As shown, the meeting invitation interface also displays "Calling 5 people including Jimmy to join the meeting," which is used to indicate the current call status to the user.

[0149] S405: The instant messaging server sends an invitation request to the target application's server, and the invitation request carries the identifier of the calling user and the identifier of the quick meeting.

[0150] S406. After receiving the request from the user inviting the meeting, the server of the target application sends a meeting invitation ringing request to the instant messaging server.

[0151] Specifically, the meeting invitation ringtone requests to carry the identifier of the user calling the meeting.

[0152] S407: The instant messaging server retrieves the participants of the target meeting based on the meeting invitation ringing request.

[0153] Specifically, the instant messaging server determines the participants of the target meeting based on the identifier of the calling user carried in the meeting invitation ring request.

[0154] S408-S410 and Figure 3 The steps S103-S105 shown are the same, and will not be repeated here.

[0155] Figure 12 This application provides an interactive flowchart of a conference communication method. This embodiment describes the process of issuing a conference invitation bell when a conference initiator invites a new participant during an ongoing conference. Figure 12 As shown, the method in this embodiment may include:

[0156] S501. In response to a user's action of adding a participant to an ongoing meeting on the interface of an ongoing meeting, the instant messaging client displays an interface for the user to select candidate participants. The candidate participants include at least the users in the instant messaging client's address book.

[0157] Specifically, as an implementable approach, the interface for users to select candidate attendees can be [interface name missing]. Figure 8 The interfaces of the candidate participants shown are the same.

[0158] S502: In response to the user's selection of participants in an ongoing meeting, the instant messaging client displays the call status of the pending participants in the ongoing meeting, with the pending participants being the users selected by the user.

[0159] Specifically, after the meeting initiator (also known as the host) selects the participants for the ongoing meeting, the selected participants become the invited participants for that ongoing meeting. The instant messaging client displays the call status display interface for the invited participants in the ongoing meeting. For example, the call status display interface for the invited participants in the ongoing meeting can be as follows: Figure 10A or Figure 10B As shown.

[0160] S503. In response to a user's action of triggering a call to at least one of the invited participants, the instant messaging client displays a meeting invitation interface and sends an invitation request to the instant messaging server.

[0161] Optional, also in Figure 10A Taking the call status display interface shown as an example, if the meeting initiator selects to click "Call All," the instant messaging client responds to this operation and displays the meeting invitation interface. For example, the meeting invitation interface can be as follows: Figure 11A As shown, the meeting invitation interface displays the call status (in progress) of each invited user. If the meeting initiator clicks the icon corresponding to "Not Entering -5", then... Figure 11A The interface shown will display the following if the meeting initiator clicks the icon corresponding to -1 (currently only one meeting host is in the meeting): Figure 11B The interface shown is Figure 11B A schematic diagram of a meeting invitation interface provided in an embodiment of this application, such as... Figure 11B As shown, the meeting invitation interface also displays "Calling 5 people including Jimmy to join the meeting," which is used to indicate the current call status to the user.

[0162] S504: The instant messaging server sends a request to invite participants to the server of the target application. The request to invite participants carries the identifier of the caller and the identifier of the meeting in progress.

[0163] S505. After receiving the request from the user inviting the meeting, the server of the target application sends a meeting invitation ringing request to the instant messaging server.

[0164] Specifically, the meeting invitation ringtone requests to carry the identifier of the user calling the meeting.

[0165] S506: The instant messaging server retrieves the participants of the target meeting based on the meeting invitation ringing request.

[0166] Specifically, the instant messaging server determines the participants of the target meeting based on the identifier of the calling user carried in the meeting invitation ring request.

[0167] S507-S509 and Figure 3The steps S103-S105 shown are the same, and will not be repeated here.

[0168] The following detailed description of the conference communication method provided in this application embodiment uses a specific example. Optionally, the instant messaging server may include multiple functional modules, and the server of the target application may also include multiple functional modules. The following description, in conjunction with... Figure 13 and Figure 14 This paper describes the information interaction process between various functional modules in the conference communication method provided in the embodiments of this application.

[0169] Figure 13 An interactive flowchart of a conference communication method provided in an embodiment of this application is shown below. Figure 13 As shown, in this embodiment, the instant messaging server may include a meeting logic access module, a schedule service module, a meeting service module, a meeting storage module, and an instant messaging application integration service module. The target application's server may include a target application integration service module, a user logic module, a meeting control module, an invitation service module, a meeting message queue module, a meeting cache module, and a meeting database module. The method in this embodiment may include:

[0170] S601: In response to the user's operation of selecting participants for a scheduled meeting and setting meeting information, the instant messaging client sends a meeting scheduling request to the meeting logic access module.

[0171] S602. The meeting logic access module sends a schedule creation request to the schedule service module.

[0172] S603. After creating a schedule, the schedule service module returns a response message to the meeting logic access module.

[0173] S604. The conference logic access module sends a request to the instant messaging application docking service module to obtain the login status of the target application.

[0174] Specifically, accessing the target application requires a login state to ensure security.

[0175] S605. The instant messaging application integration service module sends a request to the user logic module to obtain the login status of the target application.

[0176] S606. The conference logic access module sends a verification information generation request to the conference service module.

[0177] S607. The meeting service module generates verification information for the participants of the scheduled meeting based on their identifiers. The meeting service module then sends the verification information generated for the participants of the scheduled meeting to the meeting storage module, so that the meeting storage module stores the correspondence between the identifiers of the participants of the scheduled meeting and the verification information of the participants of the scheduled meeting in the verification information list.

[0178] S608. Participants in scheduled meetings pre-register through the instant messaging application's integration service module and user logic module.

[0179] If the attendee is not a registered user of the target application, pre-registration is required; otherwise, pre-registration is not required.

[0180] S609. The conference logic access module sends a conference creation request to the instant messaging application integration service module, and the instant messaging application integration service module sends a conference creation request to the conference control module.

[0181] S610, the conference control module sends a request to the target application integration service module to generate a link for scheduling a conference, and the target application integration service module sends a request to the conference service module to generate a link for scheduling a conference.

[0182] S611 The meeting service module generates the link information for scheduling a meeting and sends the link information to the meeting control module through the target application integration service module.

[0183] S612 The meeting control module stores the meeting information of the scheduled meeting into the meeting cache module (Redis), the meeting database module (DB), and the meeting message queue module (Kafka), respectively.

[0184] S613. The meeting logic access module sends an update schedule request to the schedule service module. The schedule service module updates the schedule and returns a response message to the meeting logic access module.

[0185] S614. The meeting logic access module sends a meeting storage update request to the meeting storage module through the meeting service module. The meeting storage module stores the identifiers of the participants who have scheduled the meeting and the meeting identifier of the scheduled meeting in the meeting reservation list.

[0186] Optionally, the conference storage module can send a response message to the conference logic access module through the conference service module to indicate that storage is complete.

[0187] The above describes the execution flow of each functional module in the meeting scheduling process.

[0188] Figure 14 An interactive flowchart of a conference communication method provided in an embodiment of this application is shown below. Figure 14As shown, in this embodiment, the instant messaging server may include a messaging system, a meeting queue module, a meeting service module, a meeting storage module, and an instant messaging application integration service module. The target application server may include a target application integration service module, a management service module, and an invitation service module. The method in this embodiment may include:

[0189] S701 The invitation service module uses a timer to detect when the appointment time has expired, thus determining the start time of the scheduled meeting.

[0190] S702. The invitation service module sends a meeting start time indication to the target application docking service module upon arrival of the scheduled meeting.

[0191] S703, The target application integration service module sends a meeting invitation ringing request to the instant messaging application integration service module.

[0192] S704, the instant messaging application integration service module sends a meeting invitation ringing request to the meeting queue module and a request to join the meeting queue.

[0193] S705, the conference queue module sends a response message to the instant messaging application integration service module, the instant messaging application integration service module sends a response message to the target application integration service module, and the target application integration service module sends a response message to the invitation service module.

[0194] S706 The meeting queue module verifies the verification information of the participants in the target meeting based on the verification information list.

[0195] Specifically, obtain a list of verification information and verify the verification information of the participants in the target meeting based on the list of verification information.

[0196] S707 The meeting queue module sends a meeting invitation ringtone to the instant messaging client corresponding to the verified participating user through the messaging system.

[0197] S708, the conference queue module starts sending a ringing delay task.

[0198] S709, The meeting queue module sends a request to the meeting storage module to store the ringing status of each issued meeting invitation.

[0199] It should be noted that, Figure 13 and Figure 14 This is merely an example, and the embodiments described in this application are not limited to this one.

[0200] Figure 15 This is a schematic diagram of the structure of a conference communication device provided in an embodiment of this application, as shown below. Figure 15 As shown, the device may include: a receiving module 11 and a display module 12.

[0201] The receiving module 11 is used to receive the meeting invitation ringtone sent by the instant messaging server. The meeting invitation ringtone is sent by the instant messaging server when it receives the meeting invitation ringtone request sent by the server of the target application. The meeting invitation ringtone request is sent by the server of the target application when it determines that the preset triggering conditions are met. The instant messaging client is equipped with an interface for calling the software development kit (SDK) of the target application. The target application is an application with audio and video conferencing functions.

[0202] The display module 12 is used to display the invitation interface of the target meeting and ring the bell when it is determined that the meeting invitation bell is sent through the message channel.

[0203] When it is determined that the meeting invitation ringtone is sent through a long connection channel, a meeting invitation ringtone notification message for the target meeting pops up based on the meeting invitation ringtone.

[0204] Optionally, the display module 12 is used to: if the message type of the meeting invitation ring is a first message type, pop up the meeting invitation ring notification message of the target meeting, trigger the terminal device to ring, and start the instant messaging client;

[0205] If the message type of the meeting invitation ring is the second message type, a meeting invitation ring notification message for the target meeting will pop up.

[0206] Optionally, the apparatus of this embodiment may further include a sending module, which is used to send an inquiry request to the instant messaging server, the inquiry request being used to inquire whether to display the invitation interface of the target meeting and ring the bell;

[0207] Optionally, the receiving module 11 is used to receive the response message of the inquiry request returned by the instant messaging server. The response message of the inquiry request is determined according to the current state of the target meeting, or the response message of the inquiry request is determined according to the current state of the target meeting and the current participation state of the participating user corresponding to the instant messaging client.

[0208] The display module 12 is also used to determine, based on the response message of the inquiry request, to display the invitation interface of the target meeting and ring the bell.

[0209] Optionally, the display module 12 is also used for:

[0210] In response to a user clicking an icon used to access the target application, the SDK of the target application is invoked to display the homepage of the target application;

[0211] In response to the user's action of initiating a meeting scheduling, the SDK of the target application is invoked to display the meeting scheduling interface;

[0212] In response to a user's action of adding a participant to the scheduled meeting on the meeting scheduling interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the address book of the instant messaging client.

[0213] The sending module is also configured to: in response to the user's operation of selecting the participants of the scheduled meeting and the user's operation of setting the meeting information of the scheduled meeting, send a scheduled meeting request to the instant messaging server, the scheduled meeting request including the identifiers of the participants of the scheduled meeting and the meeting information of the scheduled meeting.

[0214] Optionally, the display module 12 is also used for:

[0215] In response to the user's action of triggering a quick meeting, the SDK of the target application is invoked to display the quick meeting interface;

[0216] In response to a user triggering an operation to add a participant to the quick meeting on the quick meeting interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the address book of the instant messaging client.

[0217] In response to the user's operation of selecting a participant for the quick meeting, a call status display interface for the invited participants of the quick meeting is displayed, wherein the invited participants are the participants selected by the user.

[0218] In response to a user triggering an operation to call at least one of the invited participants, the meeting invitation interface is displayed.

[0219] The sending module is also configured to: send an invitation request to the instant messaging server, wherein the instant messaging server sends the invitation request to the server of the target application, and the invitation request carries the identifier of the calling user and the identifier of the quick meeting.

[0220] Optionally, the display module 12 is also used for:

[0221] In response to a user triggering an operation to add a participant to an ongoing meeting on the meeting's interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the instant messaging client's address book.

[0222] In response to the user's operation of selecting a participant in the ongoing meeting, a call status display interface for the pending participants in the ongoing meeting is displayed, wherein the pending participants are the participants selected by the user.

[0223] In response to a user triggering an operation to call at least one of the invited participants, the meeting invitation interface is displayed.

[0224] The sending module is also used to: send an invitation request to the instant messaging server, wherein the instant messaging server sends the invitation request to the server of the target application, and the invitation request carries the identifier of the calling user and the identifier of the ongoing meeting.

[0225] Optionally, the sending module is further configured to: send the status of the meeting invitation ringing to the instant messaging server, wherein the status of the meeting invitation ringing includes any one of being answered, rejected, and sent and timed out;

[0226] The receiving module 11 is also configured to: receive the entry information of the target meeting sent by the instant messaging server when the meeting invitation ringing status is rejected or sent and timed out;

[0227] The display module 12 is also used to display the entry information of the target meeting.

[0228] Figure 16 This is a schematic diagram of the structure of a conference communication device provided in an embodiment of this application, as shown below. Figure 16 As shown, the device may include: a receiving module 21, an acquiring module 22, and a sending module 23.

[0229] The receiving module 21 is used to receive the meeting invitation ringing request sent by the server of the target application when the preset triggering conditions are met. The instant messaging client is equipped with an interface for calling the software development kit of the target application. The target application is an application with audio and video conferencing functions.

[0230] The acquisition module 22 is used to acquire the participants of the target meeting based on the meeting invitation ringing request;

[0231] The sending module 23 is used to send a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through a message channel when it is determined that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server.

[0232] When it is determined that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through a long connection channel.

[0233] Optionally, the sending module 23 is used for:

[0234] A meeting invitation ringtone of either the first message type or the second message type is sent to the instant messaging client corresponding to the participating user of the target meeting via a long connection channel.

[0235] Optionally, module 22 is used for:

[0236] Store the meeting invitation ringing request in a message queue;

[0237] When the meeting invitation rings out of the message queue, the participants of the target meeting are obtained according to the meeting invitation ringing request.

[0238] Optional, preset trigger conditions include:

[0239] The scheduled meeting start time has arrived; or,

[0240] The instant messaging server received a request from a user inviting the user to participate in the meeting.

[0241] Optionally, the preset trigger condition is the arrival of the meeting start time of the scheduled meeting. The receiving module 21 is further configured to: receive the scheduled meeting request sent by the instant messaging client, wherein the scheduled meeting request includes the identifier of the participating user of the scheduled meeting and the meeting information of the scheduled meeting;

[0242] The sending module 23 is further configured to: send a meeting creation request to the server of the target application, the meeting creation request carrying the meeting information of the scheduled meeting, for the server of the target application to create the scheduled meeting according to the meeting creation request and assign a meeting identifier to the created scheduled meeting;

[0243] The sending module 23 is also configured to: generate the link information of the scheduled meeting, and send the link information of the scheduled meeting to the server of the target application;

[0244] The receiving module 21 is further configured to: receive a response message sent by the target application server indicating that the scheduled meeting has been successfully created, the response message carrying the meeting identifier of the scheduled meeting, and storing the identifiers of the participating users of the scheduled meeting and the meeting identifier of the scheduled meeting in the meeting reservation list.

[0245] Optionally, the apparatus of this embodiment may further include: a processing module, which is used for:

[0246] Before sending a meeting creation request to the server of the target application, the sending module 23 generates verification information for the participants of the scheduled meeting based on their identifiers, and stores the correspondence between the identifiers of the participants and their verification information in the verification information list.

[0247] Optionally, the receiving module 21 is further configured to: receive a request from the server of the target application to generate the link information for the scheduled meeting.

[0248] Optionally, the meeting invitation ringing request carries the identifier of the target meeting, and the acquisition module 22 is used for:

[0249] Based on the identifier of the target meeting carried in the meeting invitation ring request, the participants of the target meeting are found from the meeting reservation list.

[0250] Optionally, the preset trigger condition is receiving a user invitation request sent by the instant messaging server. The meeting invitation ringing request carries the identifier of the calling user. The acquisition module 22 is used for:

[0251] The participants of the target meeting are determined based on the identifier of the calling user carried in the meeting invitation ringing request.

[0252] Furthermore, the receiving module 21 is also configured to: receive an inquiry request sent by the instant messaging client, the inquiry request being used to inquire whether to display the invitation interface of the target meeting and ring the bell;

[0253] The acquisition module 22 is further configured to: after acquiring the login status of the target application client, acquire the current status of the target meeting from the server of the target application, wherein the current status includes whether the meeting has ended or not.

[0254] The response message for the inquiry request is determined based on the current state of the target meeting;

[0255] The sending module 23 is also used to send a response message of the inquiry request to the instant messaging client.

[0256] Furthermore, if the response message of the inquiry request indicates that the invitation interface of the target meeting is displayed and the bell rings, the acquisition module 22 is further configured to: obtain the current participation status of the participating user corresponding to the instant messaging client from the server of the target application, the current participation status including whether the participating user has joined the target meeting or not; and determine the response message of the inquiry request again based on the current participation status of the participating user corresponding to the instant messaging client.

[0257] Furthermore, the sending module 23 is used to: verify the verification information of the participants in the target meeting according to the verification information list, and send the meeting invitation ringtone to the instant messaging client corresponding to the participants in the target meeting who have passed the verification.

[0258] Optionally, the receiving module 21 is further configured to: receive the status of the meeting invitation ringing sent by the instant messaging client corresponding to the participating user of the target meeting, wherein the status of the meeting invitation ringing includes any one of being answered, rejected, and sent and timed out;

[0259] The processing module is also used to: update the call status of each participant based on the ringing status of the meeting invitation among the participants of the target meeting;

[0260] The sending module 23 is also used to: send the status of the meeting invitation ringing to the server of the target application;

[0261] The sending module 23 is used to send the entry information of the target meeting to the instant messaging client corresponding to the participating user whose meeting invitation ringing status is rejected or has been sent and timed out.

[0262] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be found in the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 15 The apparatus shown can execute the method embodiment corresponding to the terminal device, and Figure 15 The aforementioned and other operations and / or functions of each module in the illustrated device are respectively for implementing the method embodiments corresponding to the terminal device, and will not be described in detail here for the sake of brevity. Figure 16 The apparatus shown can execute the method embodiment corresponding to the server, and Figure 16 The aforementioned and other operations and / or functions of each module in the illustrated device are respectively for implementing the method embodiments corresponding to the server, and will not be described in detail here for the sake of brevity.

[0263] The conference communication device of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by the integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0264] Figure 17This is a schematic block diagram of the conference communication device provided in the embodiments of this application.

[0265] like Figure 17 As shown, the conference communication device may include:

[0266] The system includes a memory 710 and a processor 720. The memory 710 stores computer programs and transfers the program code to the processor 720. In other words, the processor 720 can retrieve and run the computer program from the memory 710 to implement the methods described in the embodiments of this application.

[0267] For example, the processor 720 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0268] In some embodiments of this application, the processor 720 may include, but is not limited to:

[0269] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0270] In some embodiments of this application, the memory 710 includes, but is not limited to:

[0271] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0272] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the conference communication device.

[0273] like Figure 17 As shown, the conference communication device may also include:

[0274] Transceiver 730, which can be connected to processor 720 or memory 710.

[0275] The processor 720 can control the transceiver 730 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include antennas, and the number of antennas may be one or more.

[0276] It should be understood that the various components in this conference communication equipment are connected through a bus system, which includes not only a data bus, but also a power bus, a control bus, and a status signal bus.

[0277] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0278] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0279] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0280] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0281] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0282] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A conference communication method, characterized in that, The method is applied to an instant messaging client, and the method includes: The instant messaging client receives a meeting invitation ringtone sent by an instant messaging server. The meeting invitation ringtone is sent by the instant messaging server when it receives a meeting invitation ringtone request from the server of the target application. The meeting invitation ringtone request is sent by the server of the target application when it determines that a preset trigger condition is met. The instant messaging client is equipped with an interface for calling the software development kit (SDK) of the target application. The target application is an application with audio and video conferencing capabilities. The meeting invitation ringtone is sent through a message channel when the instant messaging client is connected to the instant messaging server, and through a long connection channel when the instant messaging client is not connected to the instant messaging server. If it is determined that the meeting invitation ringtone was sent through the message channel, the invitation interface for the target meeting will be displayed and the ringtone will sound according to the meeting invitation ringtone; In response to the participation of the target meeting user answering the meeting invitation ringing, the SDK of the target application is invoked to display the meeting interface of the target meeting user who has joined the target meeting; If it is determined that the meeting invitation ringtone is sent through a long connection channel, a meeting invitation ringtone notification message for the target meeting will pop up based on the meeting invitation ringtone.

2. The method according to claim 1, characterized in that, The step of displaying a meeting invitation notification message for the target meeting based on the meeting invitation ringing includes: If the message type of the meeting invitation ring is the first message type, a meeting invitation ring notification message for the target meeting will pop up, triggering the terminal device to ring and launching the instant messaging client; If the message type of the meeting invitation ring is the second message type, a meeting invitation ring notification message for the target meeting will pop up.

3. The method according to claim 1, characterized in that, Before the step of ringing the bell according to the meeting invitation, displaying the invitation interface of the target meeting, and ringing the bell, the method further includes: Send an inquiry request to the instant messaging server, the inquiry request being used to ask whether to display the invitation interface of the target meeting and ring the bell; Receive a response message for the inquiry request returned by the instant messaging server. The response message for the inquiry request is determined based on the current state of the target meeting, or the response message for the inquiry request is determined based on the current state of the target meeting and the current participation state of the participating user corresponding to the instant messaging client. Based on the response message to the query request, determine to display the invitation interface for the target meeting and ring the bell.

4. The method according to claim 1, characterized in that, The method further includes: In response to a user clicking an icon used to access the target application, the SDK of the target application is invoked to display the homepage of the target application; In response to the user's action of initiating a meeting reservation, the SDK of the target application is invoked to display the meeting reservation interface; In response to a user's action of adding a participant to the scheduled meeting on the meeting scheduling interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the address book of the instant messaging client. In response to the user's operation of selecting participants for the scheduled meeting and the user's operation of setting meeting information for the scheduled meeting, a meeting scheduling request is sent to the instant messaging server. The meeting scheduling request includes the identifiers of the participants for the scheduled meeting and the meeting information for the scheduled meeting.

5. The method according to claim 1, characterized in that, The method further includes: In response to the user's action of triggering a quick meeting, the SDK of the target application is invoked to display the quick meeting interface; In response to a user triggering an operation to add a participant to the quick meeting on the quick meeting interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the address book of the instant messaging client. In response to the user's operation of selecting a participant for the quick meeting, the call status display interface of the invited participants for the quick meeting is displayed, wherein the invited participants are the participants selected by the user; In response to a user triggering an operation to call at least one of the invited participants, the meeting invitation interface is displayed. Send an invitation request to the instant messaging server, which is used by the instant messaging server to send the invitation request to the server of the target application. The invitation request carries the identifier of the calling user and the identifier of the quick meeting.

6. The method according to claim 1, characterized in that, The method further includes: In response to a user's action of adding a participant to an ongoing meeting on the meeting's interface, an interface for the user to select candidate participants is displayed, wherein the candidate participants include at least the users in the instant messaging client's address book. In response to the user's operation of selecting a participant in the ongoing meeting, a call status display interface for the pending participants in the ongoing meeting is displayed, wherein the pending participants are the participants selected by the user. In response to a user triggering an operation to call at least one of the invited participants, the meeting invitation interface is displayed. Send an invitation request to the instant messaging server, which is used by the instant messaging server to send the invitation request to the server of the target application. The invitation request carries the identifier of the calling user and the identifier of the ongoing meeting.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Send the meeting invitation ring status to the instant messaging server. The meeting invitation ring status includes any one of: answered, rejected, and sent and timed out. Receive the entry information of the target meeting sent by the instant messaging server when the meeting invitation ringing status is rejected or has been sent and timed out; Displays the entry information for the target meeting.

8. A conference communication method, characterized in that, The method is applied to an instant messaging server, and the method includes: The instant messaging client receives a meeting invitation ringing request sent by the server of the target application when it determines that the preset triggering conditions are met. The instant messaging client is equipped with an interface for calling the software development kit (SDK) of the target application, which is an application with audio and video conferencing functions. Based on the meeting invitation ringing request, obtain the participants of the target meeting; If it is determined that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through the message channel; If it is determined that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through a long connection channel.

9. The method according to claim 8, characterized in that, Sending a meeting invitation ringtone to the instant messaging client corresponding to the participating user of the target meeting via a long connection channel includes: A meeting invitation ringtone of either the first message type or the second message type is sent to the instant messaging client corresponding to the participating user of the target meeting via a long connection channel.

10. The method according to claim 8, characterized in that, The step of obtaining the participants of the target meeting based on the meeting invitation ringing request includes: Store the meeting invitation ringing request in a message queue; When the meeting invitation rings out of the message queue, the participants of the target meeting are obtained according to the meeting invitation ringing request.

11. The method according to claim 8, characterized in that, The preset triggering conditions include: The scheduled meeting start time has arrived; or, The instant messaging server received a request from a user inviting the user to participate in the meeting.

12. The method according to claim 11, characterized in that, The preset trigger condition is the arrival of the scheduled meeting start time, and the method further includes: Receive a meeting reservation request sent by the instant messaging client, the meeting reservation request including the identifiers of the users who will participate in the meeting and the meeting information of the meeting; A meeting creation request is sent to the server of the target application. The meeting creation request carries the meeting information of the scheduled meeting, which is used by the server of the target application to create the scheduled meeting according to the meeting creation request and assign a meeting identifier to the created scheduled meeting. Generate the link information for the scheduled meeting and send the link information for the scheduled meeting to the server of the target application; The system receives a response message from the target application server indicating that the scheduled meeting has been successfully created. The response message carries the meeting identifier of the scheduled meeting, and stores the identifiers of the participating users and the meeting identifier of the scheduled meeting in the meeting reservation list.

13. The method according to claim 12, characterized in that, Before sending the create meeting request to the server of the target application, the method further includes: Based on the identifier of the participants in the scheduled meeting, verification information is generated for the participants in the scheduled meeting, and the correspondence between the identifier of the participants in the scheduled meeting and the verification information of the participants in the scheduled meeting is stored in the verification information list.

14. The method according to claim 12, characterized in that, Before generating the link information for the scheduled meeting, the method also includes: Receive a request from the server of the target application to generate the link information for the scheduled meeting.

15. The method according to claim 12, characterized in that, The meeting invitation ringing request carries the identifier of the target meeting, and the step of obtaining the participants of the target meeting based on the meeting invitation ringing request includes: Based on the identifier of the target meeting carried in the meeting invitation ring request, the participants of the target meeting are found from the meeting reservation list.

16. The method according to claim 11, characterized in that, The preset trigger condition is receiving a user invitation request sent by the instant messaging server. The meeting invitation ringing request carries an identifier of the calling user. The step of obtaining the participants of the target meeting based on the meeting invitation ringing request includes: The participants of the target meeting are determined based on the identifier of the calling user carried in the meeting invitation ringing request.

17. The method according to claim 8, characterized in that, The method further includes: Receive an inquiry request sent by the instant messaging client, the inquiry request being used to ask whether to display the invitation interface of the target meeting and ring the bell; After obtaining the login status of the target application client, the current status of the target meeting is obtained from the server of the target application. The current status includes whether the meeting has ended or not. The response message for the inquiry request is determined based on the current state of the target meeting; Send a response message to the instant messaging client for the query request.

18. The method according to claim 17, characterized in that, If the response message to the inquiry request indicates that the invitation interface of the target meeting is displayed and a ringtone is sounded, the method further includes: Obtain the current participation status of the participating user corresponding to the instant messaging client from the server of the target application. The current participation status includes whether the participating user is currently connected to the target meeting or whether the participating user is currently not connected to the target meeting. Based on the current participation status of the participating user corresponding to the instant messaging client, the response message for the inquiry request is determined again.

19. The method according to claim 13, characterized in that, Sending a meeting invitation ringtone to the instant messaging client corresponding to the participating users of the target meeting includes: The verification information of the participants in the target meeting is verified according to the verification information list, and the meeting invitation ring is sent to the instant messaging client corresponding to the participants in the target meeting who have passed the verification.

20. The method according to any one of claims 8-19, characterized in that, The method further includes: The system receives the status of the meeting invitation ringing sent by the instant messaging client corresponding to the participating user of the target meeting. The status of the meeting invitation ringing includes any one of the following: answered, rejected, and sent and timed out. Update the call status of each participant based on the ringing status of the meeting invitation among the participants in the target meeting; Send the meeting invitation ringing status to the server of the target application; Send the entry information of the target meeting to the instant messaging client of the participating user whose meeting invitation status is rejected or has expired.

21. A conference communication device, characterized in that, include: A receiving module is used to receive meeting invitation ringtones sent by an instant messaging server. The meeting invitation ringtone is sent by the instant messaging server when it receives a meeting invitation ringtone request from the server of the target application. The meeting invitation ringtone request is sent by the server of the target application when it determines that a preset trigger condition is met. The instant messaging client is provided with an interface for calling the software development kit (SDK) of the target application. The target application is an application with audio and video conferencing capabilities. The meeting invitation ringtone is sent through a message channel when the instant messaging client is connected to the instant messaging server, and through a long connection channel when the instant messaging client is not connected to the instant messaging server. The display module is used to display the invitation interface of the target meeting and ring the bell when it is determined that the meeting invitation bell is sent through the message channel. In response to the participation of the target meeting user answering the meeting invitation ringing, the SDK of the target application is invoked to display the meeting interface of the target meeting user who has joined the target meeting; When it is determined that the meeting invitation ringtone is sent through a long connection channel, a meeting invitation ringtone notification message for the target meeting pops up based on the meeting invitation ringtone.

22. A conference communication device, characterized in that, include: The receiving module is used to receive a meeting invitation ringing request sent by the server of the target application when a preset triggering condition is met. The instant messaging client is equipped with an interface for calling the software development kit of the target application, and the target application is an application with audio and video conferencing functions. The acquisition module is used to acquire the participants of the target meeting based on the meeting invitation ringing request; The sending module is used to send a meeting invitation ringtone to the instant messaging client corresponding to the participant of the target meeting through a message channel when it is determined that the instant messaging client corresponding to the participant of the target meeting is connected to the instant messaging server. When it is determined that the instant messaging client corresponding to the participant of the target meeting is not connected to the instant messaging server, a meeting invitation ring is sent to the instant messaging client corresponding to the participant of the target meeting through a long connection channel.

23. A conference communication device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method of any one of claims 1-7 or 8-20.

24. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1-7 or 8-20.

25. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-7 or 8-20.

Images