A conference implementation method, a conference system, an electronic device and a storage medium

Abstract

Embodiments of the present application relate to the technical field of communication, and disclose a conference implementation method, a conference system, an electronic device and a storage medium. The method is applied to a calling server, the calling server is connected to an intermediate server, and at least one called server belonging to a different domain from the calling server is also connected to the intermediate server. The method comprises: receiving a conference request sent by a calling terminal, the conference request carrying conference information and information of at least one first called terminal belonging to the called server; generating a first invitation link according to the conference information and the information of the first called terminal; and sending the first invitation link to the intermediate server, so that the intermediate server forwards the first invitation link to the first called terminal through the corresponding called server, to invite the first called terminal to participate in a conference indicated by the conference information. At least, the conference can be implemented between cross-domain terminals.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a meeting implementation method, a meeting system, an electronic device, and a storage medium. Background Technology

[0002] With the development of network technology and the progress of the times, remote conferencing systems have emerged. At the same time, because remote conferencing systems can greatly improve communication and work efficiency, they are being used by an increasing number of enterprises, organizations, and individuals. For example, in a work-from-home scenario, remote conferencing is particularly important for facilitating communication among employees.

[0003] Currently, remote conferencing typically involves the calling terminal initiating a request to its server to schedule a meeting. The server then sends the corresponding meeting link to the called terminal based on the participating terminals identified by the calling terminal. After receiving the meeting link, the called terminal can choose whether or not to participate in the scheduled meeting.

[0004] However, the above-mentioned meeting implementation method has some limitations, which affects the user experience. Summary of the Invention

[0005] This application provides a meeting implementation method, meeting system, electronic device, and storage medium, which can at least enable meetings between cross-domain terminals, overcome the limitations of cross-domain terminals in the meeting implementation process, and help improve user experience.

[0006] According to some embodiments of this application, one aspect of this application provides a conference implementation method applied to a calling server, wherein the calling server is connected to an intermediate server, and the intermediate server is also connected to at least one called server belonging to a different domain from the calling server. The method includes: receiving a conference request sent by a calling terminal, the conference request carrying conference information and information of at least one first called terminal belonging to the called server; generating a first invitation link based on the conference information and the information of the first called terminal; sending the first invitation link to the intermediate server, so that the intermediate server forwards the first invitation link to the first called terminal through the corresponding called server, so as to invite the first called terminal to participate in the conference indicated by the conference information.

[0007] According to some embodiments of this application, another aspect of this application provides a conference implementation method applied to a calling terminal. The method includes: generating a conference request, the conference request carrying conference information and information of at least one first called terminal belonging to a called server, the called server and the calling server to which the calling terminal belongs belonging to different domains; the called server and the calling server being connected to the same intermediate server; sending a conference request to the calling server, so that the calling server, according to the conference request, invites the first called terminal to participate in the conference indicated by the conference information through the intermediate server and the called server.

[0008] According to some embodiments of this application, another aspect of this application provides a conference implementation method applied to a called server, wherein the called server is connected to an intermediate server, and the intermediate server is also connected to at least one calling server belonging to a different domain than the called server. The method includes: receiving a first invitation link sent by the intermediate server, the first invitation link carrying conference information and information of at least one first called terminal belonging to the called server, wherein the domain of the conference indicated by the conference information is the domain of the calling server; forwarding the first invitation link to the corresponding first called terminal to invite the corresponding first called terminal to participate in the conference indicated by the conference information. According to some embodiments of this application, another aspect of this application provides a conference implementation method applied to a first called terminal, the method including: receiving a first invitation link sent by the called server, the first invitation link carrying conference information, wherein the domain of the conference indicated by the conference information is the domain of the calling server, and the calling server and the called server belong to different domains; determining whether to join the conference indicated by the conference information.

[0009] According to some embodiments of this application, another aspect of this application provides a conference implementation method applied to a first called terminal. The method includes: receiving a first invitation link sent by a called server, the first invitation link carrying conference information, the conference information indicating the domain where the conference is located is the domain where the calling server is located, the calling server and the called server belong to different domains and are connected to the same intermediate server; and determining whether to join the conference indicated by the conference information according to user instructions.

[0010] According to some embodiments of this application, another aspect of this application provides a conference implementation method applied to an intermediate server, wherein at least one calling server and at least one called server belonging to a different domain from the calling server are also connected to the intermediate server. The method includes: receiving a first invitation link sent by the calling server, the first invitation link carrying conference information and information of at least one first called terminal belonging to the called server; forwarding the first invitation link to the called server corresponding to the first called terminal, so that the corresponding called server forwards the first invitation link to the first called terminal to invite the first called terminal to participate in the conference indicated by the conference information.

[0011] According to some embodiments of this application, another aspect of this application provides a conferencing system, including: an intermediate server, at least two servers belonging to different domains connected to the intermediate server, and a plurality of terminals belonging to the at least two servers belonging to different domains; the intermediate server is used to implement the conferencing implementation method applied to the intermediate server as described above; the at least two servers belonging to different domains are used to implement the conferencing implementation method applied to the calling terminal and / or the first called terminal as described above; the terminals are used to implement the conferencing implementation method applied to the calling server and / or the called server as described above.

[0012] According to some embodiments of this application, another aspect of this application provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the conference implementation method as described in any of the preceding claims.

[0013] According to some embodiments of this application, another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the meeting implementation method as described in any of the preceding claims.

[0014] The technical solution provided in this application has at least the following advantages:

[0015] The calling server and the called server (belonging to a different domain) are connected to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. When a calling terminal belonging to the calling server sends a conference request, the calling server generates a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server via the intermediate server. The called server can then forward the first invitation link to its corresponding called terminal, inviting it to participate in the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience. Attached Figure Description

[0016] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0017] Figure 1 This is a flowchart of a meeting implementation method provided in one embodiment of this application;

[0018] Figure 2 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0019] Figure 3 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0020] Figure 4 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0021] Figure 5 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0022] Figure 6 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0023] Figure 7 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0024] Figure 8 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0025] Figure 9 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0026] Figure 10 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0027] Figure 11 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0028] Figure 12 This is another flowchart of a meeting implementation method provided in one embodiment of this application;

[0029] Figure 13 This is an interactive flowchart of a meeting implementation method provided in one embodiment of this application;

[0030] Figure 14 This is a schematic diagram of the structure of a conference system provided in one embodiment of this application;

[0031] Figure 15 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0032] As can be seen from the background technology, the current methods of implementing meetings have some limitations, which affect the user experience.

[0033] Analysis revealed that the current conferencing implementation suffers from the following problems: The calling terminal can only identify the called terminal if it can obtain the called terminal's information; otherwise, it cannot be identified as a participant. When the called and called terminals belong to servers with different domains, cross-domain communication prevents communication between the servers, preventing the calling terminal from obtaining the called terminal's information and thus inviting it to the meeting. Furthermore, even if the called terminal obtains the meeting link from a server with a different domain, the meeting management system within that domain cannot match the participating called terminal with its locally managed terminal user, preventing the meeting from taking place. In other words, the current conferencing implementation is limited to terminals on servers with the same domain, resulting in the inability to hold meetings between cross-domain terminals and severely impacting user experience.

[0034] To address the aforementioned issues, this application provides a conferencing method, a conferencing system, an electronic device, and a storage medium. The calling server and a called server belonging to a different domain are connected to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conferencing request, the calling server generates a first invitation link based on the conferencing information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server via the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conferencing. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conferencing and improving user experience.

[0035] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been presented in the various embodiments of this application to enable readers to better understand this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments.

[0036] The division of the following embodiments is for ease of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0037] This application provides a conferencing implementation method applied to a calling server. The calling server is connected to an intermediate server, which in turn connects to at least one called server belonging to a different domain from the calling server. The calling server is the server to which the calling terminal belongs; it can be any server device or server device cluster providing conferencing calling services. The called server is the server to which the called terminal belongs; it can be any server device or server device cluster providing conferencing called services. The intermediate server can be any server device or server device cluster capable of connecting to other servers and enabling communication between connected servers; for example, the intermediate server can be a Cloud Intelligent Management (Cloud IM) server.

[0038] It should be noted that the servers in different domains mentioned in this application embodiment refer to servers whose communication with each other is cross-domain communication and therefore cannot communicate directly. It is understood that servers with different domain names (in some cases, different subdomains, and in some cases, different subdomains under a second-level domain) do not correspond to the same main server, and the two will not be able to communicate directly.

[0039] It's also important to clarify that whether a server is considered the calling server or the called server is relative to the current conference process, not a fixed designation of servers as either calling or called servers. Taking a conference between terminals A, B, and C as an example, in a conference where terminal A invites terminals B and C, the server belonging to terminal A is the calling server, and the servers belonging to terminals B and C are the called servers. Conversely, in a conference where terminal B invites terminals A and C, the servers belonging to terminals A and C are the called servers, and the server belonging to terminal B is the calling server. This distinction will not be elaborated upon further here.

[0040] To facilitate a better understanding by those skilled in the art of the conference implementation method applied to the calling server provided in the embodiments of this application, the following will be combined with Figures 1-3 Explain it.

[0041] In some embodiments, reference Figure 1 The process of implementing the meeting includes the following steps:

[0042] Step 101: Receive a conference request sent by the calling terminal. The conference request carries conference information and information about at least one first called terminal belonging to the called server.

[0043] In this embodiment, the first called terminal is any terminal belonging to a called server in a different domain than the calling server. That is, the conference request sent by the calling terminal carries information about participating terminals, including information about terminals belonging to a server in a different domain.

[0044] It should be noted that this application embodiment does not limit the number of first called terminals corresponding to the information carried in the conference request: in some cases, the conference information may carry the information of one first called terminal; in other cases, the conference information may carry the information of two or more first called terminals. Furthermore, when the conference information may carry the information of two or more first called terminals, this application embodiment does not limit the called server to which the first called terminal belongs: in some cases, these first called terminals may belong to the same called server; in other cases, these first called terminals may belong to different called servers. The number of first called terminals corresponding to the information carried in the conference information, and whether the called servers to which the first called terminals belong are the same, can both be determined by the calling terminal.

[0045] In this embodiment, the meeting information can be any or any information used to instruct the meeting, and this embodiment does not limit the specific content of the meeting information.

[0046] In some embodiments, meeting information may include one or a combination of the following: the domain name of the meeting, the meeting ID, and the meeting password.

[0047] As mentioned earlier, the calling terminal and the first called terminal belong to servers in different domains, indicating cross-domain participation in the meeting. Indicating the meeting's domain name helps the first called terminal obtain more information about the meeting, allowing users to better decide whether to join and improving meeting participation. The meeting room number facilitates more accurate and efficient meeting joining. The meeting password enhances meeting security, further improving the user experience.

[0048] It's important to note that when the meeting information includes the meeting's domain name, this domain name can be the domain name of the server hosting the calling terminal. This allows the calling server to quickly begin meeting preparation after receiving the meeting request from the calling terminal. Alternatively, the meeting's domain name can be the domain name of the server hosting a first called terminal, making it easier for the first called terminal to join the meeting more efficiently and quickly. The meeting's domain name can also be the domain name of another highly secure server, thus ensuring meeting security. In other words, the meeting's domain name can be determined based on meeting requirements, etc., which will not be elaborated further here.

[0049] In some embodiments, meeting information may also include one or a combination of the following: meeting start time, expected meeting end time, attendees, etc.

[0050] By providing information on the meeting start time, expected end time, and attendees, participants can better decide whether to attend and make necessary arrangements, thus improving the user experience.

[0051] Of course, the above are just specific examples of meeting information. In some cases, meeting information can also be other meeting-related information, which will not be elaborated here.

[0052] In some embodiments, reference Figure 2 Before receiving a conference request from the calling terminal, the conference implementation method also includes the following steps:

[0053] Step 104: Obtain information about each first called terminal belonging to the called server from the called server through an intermediate server.

[0054] It is understandable that the calling terminal may invite more than one first called terminal to participate in the meeting, and the calling terminal may initiate the meeting more than once. The first called terminals involved in each meeting may also be different. Therefore, when the calling server obtains the information of the first called terminal, it can obtain the information of each first called terminal belonging to the called server, thereby improving the efficiency of obtaining the information of the first called terminal.

[0055] Step 105: Send the information of the first called terminal associated with the calling terminal from the information of each first called terminal to the calling terminal, so that the calling terminal can determine the information of the first called terminal carried in the conference request.

[0056] In this embodiment, the information of the first called terminal associated with the calling terminal refers to the information of the first called terminal that has a predefined association relationship with the calling terminal. This predefined association relationship can be an association established between the calling terminal and the first called terminal through a third party. For example, if the user accounts of the calling terminal and the first called terminal have the same friend accounts, then the calling terminal and the first called terminal are considered to have a predefined association relationship. Alternatively, if the calling terminal and the first called terminal have the same or similar tags, then the calling terminal and the first called terminal are considered to have a predefined association relationship, and so on. These are just a few examples; they will not be elaborated upon here.

[0057] In this way, the calling server maintains information about each first called terminal belonging to the called server. When the calling terminal needs information about one or more first called terminals, it can directly obtain it from the information maintained by the calling server. This makes it more efficient for the calling terminal to obtain information about the first called terminals, further improving the user experience. Furthermore, the calling server no longer needs to frequently retrieve information through intermediate servers, saving its resources and reducing waste. Simultaneously, the calling server does not send information about each first called terminal directly to the calling terminal; instead, it sends information about the first called terminals associated with the calling terminal. This reduces the storage space occupied by the first called terminal information on the calling terminal and avoids the adverse effects of a large amount of first called terminal information on the calling terminal, such as slowing down the calling terminal's system efficiency, thus further improving the user experience.

[0058] In this way, by obtaining the called terminal's information from the called server through an intermediate server, the information of the first called terminal is automatically obtained, which helps to simplify user operations during cross-domain conferencing and can further improve the user experience.

[0059] In some embodiments, the user can input the information of the first called terminal from the calling terminal, and then the calling terminal reports it to the calling server for authentication. Specifically, if the calling server maintains information about each of the first called terminals of the called server, the calling server can perform authentication. If the calling server does not maintain information about each of the first called terminals of the called server, the calling server can continue to report to the Cloud IM server, and the Cloud IM server can query whether the first called terminal corresponding to the information of that first called terminal belongs to a connected server. In particular, if the calling server authentication fails, it can continue to report to the Cloud IM server for authentication to improve the accuracy of authentication, such as avoiding authentication errors that occur when the information of the first called terminal is not synchronized to the calling server in a timely manner.

[0060] This allows for more flexible acquisition of information from the first called terminal, enabling cross-domain conferencing in more scenarios, thereby meeting users' conferencing needs in different situations and further improving the user experience.

[0061] Of course, the above is only an example of how the calling side (calling terminal and / or calling server) can obtain information about the corresponding first called terminal. In some embodiments, other methods can be used to achieve this, which will not be elaborated here.

[0062] Step 102: Generate a first invitation link based on the meeting information and the information of the first called terminal.

[0063] This embodiment does not limit the form of the first invitation link; it can be any link that reflects meeting information and information about the first called terminal. For example, the first invitation link can be in the following form:

[0064] https: / / 192.168.133.123:8090 / # / invite / confdynamic / 6301 / d5ba3e3d-5be0-4204-9fcb-018d6de58fee / 0 / 0 / 1655448307620;

[0065] Understandably, the link includes meeting information, such as the domain name of the meeting, the meeting room number, and whether the meeting has a password; it also includes information about the first called terminal, such as the basic information of the invitee, so that the first called terminal can enter the corresponding meeting through the link.

[0066] Step 103: Send a first invitation link to the intermediate server, so that the intermediate server can forward the first invitation link to the first called terminal through the corresponding called server, so as to invite the first called terminal to participate in the meeting indicated by the meeting information.

[0067] As mentioned earlier, the calling server and the called server belong to different domains and cannot communicate directly. In this embodiment, the calling server sends a first invitation link to an intermediate server, which then forwards the first invitation link to the corresponding first called terminal via the corresponding called server. This allows the first called terminal to receive the first invitation link and join the conference based on it.

[0068] In some embodiments, the conference implementation also involves co-domain terminals, meaning the conference request also carries information about at least one second called terminal belonging to the calling server. In this case, such as... Figure 3 As shown, before receiving a conference request from the calling terminal, the conference implementation method also includes the following steps:

[0069] Step 106: Generate a second invitation link based on the conference information and the information of the second called terminal.

[0070] This embodiment does not limit the form of the second invitation link; it can be any link that reflects meeting information and information about the second called terminal. For example, the second invitation link can be in the following form:

[0071] https: / / 192.168.133.123:8090 / # / invite / confdynamic / 6301 / d5ba3e3d-5be0-4204-9fcb-018d6de58fee / 0 / 0 / 1655448307620;

[0072] Understandably, the link includes meeting information, such as the domain name of the meeting, the meeting room number, and whether the meeting has a password; it also includes information about the second called terminal, such as the basic information of the invitee, so that the second called terminal can enter the corresponding meeting through the link.

[0073] Of course, the above is just a specific example of the second invitation link, and the second invitation link can also take other forms. For example, the second invitation link may not include the domain name of the meeting, but instead default to the domain name of the server to which the second called terminal belongs. In this case, since the server to which the second called terminal belongs has the same domain name as the called server to which the calling terminal belongs, the second called terminal can still accurately determine the domain name of the meeting through the default domain name.

[0074] It should be noted that the "second called terminal" in this embodiment has no practical meaning compared to the "first" and "second" in the aforementioned "first called terminal". It is mainly used to distinguish called terminals belonging to different types of servers. Specifically, a called terminal belonging to a server in a different domain from the server to which the calling terminal belongs is called the "first called terminal", and a called terminal belonging to a server in the same domain as the server to which the calling terminal belongs is called the "second called terminal".

[0075] It should also be noted that the "second invitation link" in this embodiment has no practical significance compared to the "first" and "second" in the aforementioned "first invitation link". It is mainly used to distinguish the conference invitation links sent to different called terminals.

[0076] Step 107: Send a second invitation link to the second called terminal to invite the second called terminal to participate in the meeting indicated by the meeting information.

[0077] It is understandable that the server to which the second called terminal belongs is a server in the same domain as the server to which the calling terminal belongs. Therefore, sending a second invitation link to the second called terminal is similar to inviting only called terminals whose servers are in the same domain as the calling terminal to participate in the conference.

[0078] In other words, while inviting terminals from different domains to participate in the meeting, it is also possible to invite terminals from the same domain to participate in the meeting. This allows for the combination of the two, achieving compatibility and uniformity between inviting terminals from different domains and inviting terminals from the same domain, reducing the user's perception of cross-domain invitations, and further improving the user experience.

[0079] It should be noted that, Figure 3The implementation order in the example is only one example. In some cases, step 106 can be executed simultaneously with step 102, step 107 can be executed simultaneously with step 103, etc., which will not be elaborated here.

[0080] In this way, the above embodiment connects the calling server and the called server (belonging to a different domain) to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conference request to the calling server, the calling server can generate a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server through the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience.

[0081] This application also provides a conference implementation method, which is applied to the calling terminal. The calling terminal can be any terminal with conference initiation function, such as mobile phone, computer and other terminal devices, which will not be described in detail here.

[0082] To facilitate a better understanding by those skilled in the art of the conference implementation method applied to the calling terminal provided in the embodiments of this application, the following will be combined with Figures 4-5 Explain it.

[0083] In some embodiments, reference Figure 4 The meeting can be implemented by following these steps:

[0084] Step 401: Generate a conference request. The conference request carries conference information and information about at least one first called terminal belonging to the called server. The called server and the calling server to which the calling terminal belongs belong to different domains. The called server and the calling server are connected to the same intermediate server.

[0085] In this embodiment, the calling server, the called server, the first called terminal, the intermediate server, the conference information, and the "different domains" are largely the same as in the previous embodiments, and will not be described in detail here.

[0086] It should be noted that this embodiment does not limit the form of the conference request or the way it is generated; it can be any request that carries conference information and information of the first called terminal.

[0087] In some embodiments, reference Figure 5 Other methods for implementing meetings include:

[0088] Step 403: Receive information about the first called terminal sent by the calling server and present it to the user.

[0089] In this embodiment, the calling terminal may actively acquire the information sent by the calling server, that is, the calling terminal requests the information of the first called terminal from the calling server; or it may be passively synchronized, that is, the calling server periodically synchronizes the information of the first called server related to the calling terminal to the calling terminal, or the calling server synchronizes the information of the corresponding first called terminal to the calling terminal when the information of the first called server related to the calling terminal changes.

[0090] Step 404: Based on the user's instruction, determine the information of the first called terminal carried in the conference request from the information of the first called terminal sent by the calling server.

[0091] Generally, the initiation of a meeting is decided by the user. Therefore, in this embodiment, the information of the first called terminal carried in the meeting request is indicated by the user. The indication method can be user indication formed by key input, touch click, file reading, etc., which will not be described in detail here.

[0092] Accordingly, a conference request can be generated by generating a conference request based on the information of the first called terminal.

[0093] It should be noted that the above embodiment is merely an example illustrating the method of acquiring and determining the information of the first called terminal, and is not limited thereto. In some embodiments, the acquisition and determination of the information of the first called terminal can be achieved through user input, document reading, etc., which will not be elaborated here.

[0094] It should also be noted that the meeting information carried in the meeting request can also be implemented through user input, document reading, etc. The previous embodiment did not specifically limit this, and it will not be elaborated here.

[0095] Understandably, the calling terminal needs to recognize the existence of the first called terminal, i.e., obtain its information, in order to initiate a conference invitation to it. In this embodiment, the calling server obtains the first called terminal's information by connecting to the same intermediate server as the called server to which the first called terminal belongs. This overcomes the problem that the calling terminal cannot directly obtain the first called terminal's information because the called server and the calling server are in different domains. Therefore, the calling terminal can successfully send conference invitations to the first called terminal in a different domain. Furthermore, it can automatically obtain the first called terminal's information from the called server through the intermediate server, eliminating the need for manual input. This simplifies user operations during cross-domain conferencing and further improves the user experience.

[0096] Step 402: Send a conference request to the calling server, so that the calling server can invite the first called terminal to participate in the conference as indicated by the conference information through the intermediate server and the called server.

[0097] The conference request in this embodiment has roughly the same meaning as the conference request received by the calling server in the previous embodiment, so it will not be described in detail here.

[0098] Understandably, calling terminals have different conference invitation needs in different scenarios. For example, a calling terminal may invite not only the first called terminal but also a second called terminal belonging to the calling server to participate in the conference. In this case, the conference request also carries information about at least one second called terminal belonging to the calling server. This information can then be used by the calling server to invite the second called terminal to participate in the conference, enabling the calling terminal, the first called terminal, and the second called terminal to join the conference simultaneously. This allows for the simultaneous invitation of cross-domain and same-domain terminals, facilitating compatibility with existing conference implementations that invite same-domain terminals and further improving the user experience.

[0099] In this way, the above embodiment connects the calling server and the called server (belonging to a different domain) to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conference request to the calling server, the calling server can generate a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server through the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience.

[0100] This application also provides a conferencing implementation method applied to a called server, which is connected to an intermediate server. The intermediate server is further connected to at least one calling server belonging to a different domain than the called server. The called server, calling server, and intermediate server are as described above, and the meaning of "different domain" is also as described above, so they will not be repeated here.

[0101] To facilitate a better understanding by those skilled in the art of the conference implementation method applied to the called server provided in the embodiments of this application, the following will be combined with Figures 6-8 Explain it.

[0102] In some embodiments, reference Figure 6 The meeting can be implemented by following these steps:

[0103] Step 601: Receive a first invitation link sent by an intermediate server. The first invitation link carries conference information and information about at least one first called terminal belonging to the called server. The domain of the conference indicated by the conference information is the domain of the calling server.

[0104] In this embodiment, the "first invitation link" is largely the same as in the previous embodiments, and will not be described in detail here.

[0105] Step 602: Forward the first invitation link to the corresponding first called terminal to invite the corresponding first called terminal to participate in the meeting indicated by the meeting information.

[0106] It is understandable that after receiving the first invitation link sent by the calling server through an intermediate server, the called server can find the corresponding first called terminal based on the first invitation link, and then forward the first invitation link to the found first called terminal.

[0107] It should be noted that the called server can also verify the first invitation link, such as checking whether the corresponding first called terminal is a terminal belonging to this server, checking whether the first invitation link is secure, and checking whether the corresponding first called terminal allows the first invitation link, thereby ensuring the security of the first invitation link and / or the first called terminal.

[0108] In some embodiments, reference Figure 7 Before receiving the first invitation link sent by the intermediate server, the meeting implementation method also includes the following steps:

[0109] Step 603: The information of each first called terminal is sent to the calling server through the intermediate server, so that the calling server can generate and send the first invitation link based on the received information of each first called terminal.

[0110] This embodiment does not limit the method by which the called server sends the information of the first called terminal. It can be that the called server actively (periodically or when the information of the first called terminal changes) synchronizes the information of the first called terminal with the calling server. For example, the called server periodically synchronizes the information of each terminal belonging to its own server to other servers (or other servers that have passed security verification) connected to the same intermediate server. Alternatively, the calling server can actively request the information of the first called terminal from the corresponding called server through the intermediate server. These will not be elaborated on here.

[0111] In this way, the information of the first called terminal can be automatically obtained from the called server through the intermediate server without manual input, which helps to simplify user operations during cross-domain conferencing and further improves the user experience.

[0112] In some embodiments, reference Figure 8 After forwarding the first invitation link to the first called terminal, the meeting implementation method also includes the following steps:

[0113] Step 604: Receive a registration request initiated by the first called terminal based on the first invitation link. The registration request carries meeting information and user information of the first called terminal.

[0114] This embodiment does not limit the form of the registration request; it can be any request that carries conference information and user information of the first called terminal.

[0115] In this embodiment, the user information of the first called terminal is the information that can uniquely identify the user of the first called terminal. For example, if the first terminal has application G installed, and the user binds their mobile phone number, name, and other information to application G during registration, then the mobile phone number, name, and other information can be used as user information. Alternatively, if the first called terminal is bound to a user, the terminal identification code of the first called terminal can also be used as the user information of the first called terminal. Of course, other information can be used as user information in other examples, which will not be elaborated here.

[0116] Step 605: Verify the registration request.

[0117] This embodiment does not limit the verification method. It can be to verify only the first called terminal itself, or to verify the relationship between the first called terminal and each terminal that is to participate in the same conference, or to verify both of the above, etc., which will not be elaborated here.

[0118] Step 606: Return the verification result to the first called terminal, so that the first called terminal can determine whether to join the conference indicated by the conference information if the verification result is successful.

[0119] In this embodiment, the verification result includes two possibilities: verification success and verification failure.

[0120] Understandably, if the verification fails, it is more beneficial to ensure the security of the calling terminal, conference information, and other related information by having the first called terminal stop participating in the conference.

[0121] In this way, the verification process helps to ensure the security of participating terminals and the information security of the meeting.

[0122] In this way, the above embodiment connects the calling server and the called server (belonging to a different domain) to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conference request to the calling server, the calling server can generate a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server through the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience.

[0123] This application also provides a meeting implementation method, which is applied to a first called terminal. The first called terminal can be any terminal with the function of receiving meeting invitations, such as mobile phones, computers and other terminal devices, which will not be described in detail here.

[0124] To facilitate a better understanding by those skilled in the art of the conference implementation method applied to the called server provided in the embodiments of this application, the following will be combined with Figures 9-10 Explain it.

[0125] In some embodiments, reference Figure 9 The meeting can be implemented by following these steps:

[0126] Step 901: Receive the first invitation link sent by the called server. The first invitation link carries conference information. The domain of the conference indicated by the conference information is the domain of the calling server. The calling server and the called server belong to different domains and are connected to the same intermediate server.

[0127] The calling server, called server, intermediate server, conference information, and "different domains" in this embodiment are largely the same as those in the previous embodiments, and will not be described in detail here.

[0128] Step 902: Determine whether to join the meeting indicated by the meeting information based on the user's instructions.

[0129] It should be noted that user instructions in this embodiment can be implemented through key input, touch clicks, voice commands, etc.

[0130] Understandably, the calling server and the called server belong to different domains, therefore, they cannot communicate with each other, and thus cannot invite the first called terminal to participate in a conference located in the domain of the calling server. However, when the calling server and the called server are connected to the same intermediate server, enabling them to communicate, the first called terminal can successfully participate in a conference located in the domain of the calling server through the called server and the intermediate server.

[0131] In some embodiments, reference Figure 10 To determine whether to join the meeting indicated by the meeting information based on user instructions, the following steps can be taken:

[0132] Step 9021: Based on the meeting information and the obtained user information, send a registration request to the local server.

[0133] Step 9022: Receive the verification result of the called server's verification of the registration request, so that if the verification result is successful, determine whether to join the meeting indicated by the meeting information according to the user's instructions.

[0134] The user information, registration request, and verification result in this embodiment are largely the same as those in the previous embodiments, and will not be described in detail here.

[0135] In this way, the verification process helps to ensure the security of participating terminals and the information security of the meeting.

[0136] In this way, the above embodiment connects the calling server and the called server (belonging to a different domain) to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conference request to the calling server, the calling server can generate a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server through the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience.

[0137] This application also provides a conferencing implementation method applied to an intermediate server, which is further connected to at least one calling server and at least one called server belonging to a different domain from the calling server. The intermediate server, calling server, and called server are largely the same as in the aforementioned embodiments, and will not be described in detail here.

[0138] To facilitate a better understanding by those skilled in the art of the conference implementation method applied to the called server provided in the embodiments of this application, the following will be combined with Figures 11-12 Explain it.

[0139] In some embodiments, reference Figure 11 The meeting can be implemented by following these steps:

[0140] Step 1101: Receive a first invitation link sent by the calling server. The first invitation link carries conference information and information about at least one first called terminal belonging to the called server.

[0141] Step 1102: Forward the first invitation link to the called server corresponding to the first called terminal, so that the corresponding called server can forward the first invitation link to the first called terminal to invite the first called terminal to participate in the meeting indicated by the meeting information.

[0142] In this embodiment, the information of the first invitation link, the meeting information, and the information of the first called terminal are largely the same as in the previous embodiment, and will not be described in detail here.

[0143] In some embodiments, reference Figure 12 Before receiving the first invitation link sent by the calling server, the conference implementation method also includes the following steps:

[0144] Step 1103: Obtain information about each first called terminal from the called server.

[0145] It should be noted that the acquisition of the information of the first called terminal can be proactive, such as when the intermediate server actively requests the information of the first terminal from the called server; or it can be passive, such as when the called server sends the information of the first called terminal to the intermediate server.

[0146] Step 1104: Send the obtained information of each first called terminal to the calling server.

[0147] In some embodiments, the information sent to the calling server can be information about all first calling terminals. This allows the calling server to have a more comprehensive understanding of the information about the first called terminals, making it easier for users to invite more different first called terminals to participate in the conference, thus improving the user experience.

[0148] In some embodiments, the information sent to the calling server may also be information of all first calling terminals and some first called terminals. For example, if the security of the calling server cannot meet the security requirements of some first called terminals, the information of these first called terminals may not be sent to the calling server.

[0149] It is understandable that the servers connected to the intermediate server can act as either the calling server or the called server in the corresponding conference scenario. Therefore, in some cases, the intermediate server may request information about the terminals under each connected server and then send the terminal information to the corresponding connected server.

[0150] In this way, the information of the called terminal can be automatically obtained from the called server through the intermediate server without manual input, which helps to simplify user operations during cross-domain conferencing and further improves the user experience.

[0151] It should be noted that the above are just specific examples. In other examples, the way the terminal obtains and sends information can be set according to needs, which will not be elaborated here.

[0152] In this way, the above embodiment connects the calling server and the called server (belonging to a different domain) to the same intermediate server, enabling cross-domain communication between the calling server and the cross-domain called server. After a calling terminal belonging to the calling server sends a conference request to the calling server, the calling server can generate a first invitation link based on the conference information carried in the request and information about at least one first called terminal. This first invitation link is then sent across domains to the corresponding called server through the intermediate server. The called server can then send the first invitation link to its corresponding called terminal to invite it to the conference. This achieves cross-domain conferencing between cross-domain terminals, overcoming limitations imposed on cross-domain terminals during conference implementation and improving user experience.

[0153] It should be noted that the steps implemented by the calling server and the called server in the above embodiments are mainly implemented through the conference management system in the calling server and the called server.

[0154] To facilitate a better understanding of the meeting implementation method provided in the above embodiments by those skilled in the art, the following will be combined with Figure 13 The process of conferencing is explained, involving the calling terminal, calling server, intermediate server (using Cloud IM server as an example), called server, first called terminal, and second called terminal.

[0155] In some embodiments, parameters Figure 13 The interactive process of the meeting implementation method includes the following steps:

[0156] Step 1301: The calling terminal determines the first and second called terminals and conference information according to the user's instructions, and generates a conference request based on the information of the first called terminal, the information of the second called terminal and the conference information.

[0157] Step 1302: The calling terminal sends a conference request to the conference management system of the calling server to which it belongs.

[0158] Step 1303: After receiving the conference request, the conference management system of the calling server generates a first invitation link based on the conference information carried in the conference request and the information of the first called terminal, and generates a second invitation link based on the conference information carried in the conference request and the information of the second called terminal.

[0159] Step 1304: The calling server's conference management system sends a second invitation link to the corresponding second called terminal.

[0160] Step 1305: The calling server's conference management system sends the first invitation link to the Cloud IM server.

[0161] Step 1306: The Cloud IM server forwards the first invitation link to the meeting management system of the corresponding called server.

[0162] Step 1307: After receiving the first invitation link, the conference management system of the called server forwards the first invitation link to the corresponding first called terminal.

[0163] Step 1308: After receiving the first invitation link, the first called terminal parses the first invitation link to obtain the meeting information.

[0164] Step 1309: The first called terminal sends a registration request to the conference management system of the called server based on the conference information and its own user information.

[0165] Step 1310: After receiving the registration request, the conference management system of the called server verifies it to generate a verification result. If the verification is successful, the first called terminal is registered.

[0166] Step 1311: After receiving the verification result, the first called terminal displays it to the user, allowing the user to determine whether to join the meeting indicated by the meeting information.

[0167] Step 1312: When the user confirms that they want to join the conference, the first called terminal sends a meeting request to the conference management system of the called server.

[0168] It should be noted that, in order to emphasize its difference from the existing conference implementation process, the above embodiments omit the interaction process between the second called terminal and the calling server to which it belongs during the process of joining the conference.

[0169] It should also be noted that, in the implementation of the above embodiments, the participating terminal determined by the user may not include the second called terminal, and thus the second invitation link will not be generated and sent, etc., which will not be elaborated here.

[0170] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this patent.

[0171] Another aspect of this application embodiment also provides a conference system, such as Figure 14 As shown, it includes: an intermediate server 1401, at least two servers 1402 belonging to different domains connected to the intermediate server 1401, and a number of terminals 1403 belonging to the at least two servers 1402 belonging to different domains.

[0172] The intermediate server 1401 is used to implement the conference implementation method applied to the intermediate server as described in any of the above embodiments; at least two servers 1402 belonging to different domains are used to implement the conference implementation method applied to the calling server as described in any of the above embodiments, and / or to implement the conference implementation method applied to the called server as described in any of the above embodiments; the terminal 1403 is used to implement the conference implementation method applied to the calling terminal as described in any of the above embodiments, and / or to implement the conference implementation method applied to the first called terminal as described in any of the above embodiments.

[0173] It is not difficult to see that this embodiment is a system embodiment corresponding to the method embodiment, and this embodiment can be implemented in conjunction with the method embodiment. The relevant technical details mentioned in the method embodiment are still valid in this embodiment, and will not be repeated here to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied to the method embodiment.

[0174] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this application, this embodiment does not introduce units that are not closely related to solving the technical problems proposed in this application; however, this does not mean that other units are absent in this embodiment.

[0175] Another aspect of this application embodiment also provides an electronic device, such as... Figure 15As shown, it includes: at least one processor 1501; and a memory 1502 communicatively connected to at least one processor 1501; wherein the memory 1502 stores instructions executable by at least one processor 1501, the instructions being executed by at least one processor 1501 to enable at least one processor 1501 to perform the method described in any of the above method embodiments.

[0176] The memory 1502 and processor 1501 are connected via a bus. This bus can include any number of interconnecting buses and bridges, connecting various circuits of one or more processors 1501 and memory 1502. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1501 is transmitted over a wireless medium via an antenna, which further receives data and transmits it to processor 1501.

[0177] Processor 1501 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory 1502 can be used to store data used by processor 1501 during operation.

[0178] Another aspect of this application provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the above-described method embodiments.

[0179] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0180] Those skilled in the art will understand that the above embodiments are specific embodiments for implementing this application, and in practical applications, various changes can be made to them in form and detail without departing from the spirit and scope of this application.

Claims

1. A method for implementing a meeting, characterized in that, The method, applied to a calling server, wherein the calling server is connected to an intermediate server, and the intermediate server is also connected to at least one called server belonging to a different domain from the calling server, includes: Receive a conference request sent by a calling terminal, the conference request carrying conference information and information of at least one first called terminal belonging to the called server; Based on the meeting information and the information of the first called terminal, a first invitation link is generated; The first invitation link is sent to the intermediate server, wherein the first invitation link is used by the intermediate server to forward to the called server based on the information of the first called terminal, and by the called server to forward to the first called terminal, so as to invite the first called terminal to initiate a meeting join request for the meeting information to the called server based on the first invitation link; the domain of the meeting indicated by the meeting information is the domain of the calling server.

2. The meeting implementation method according to claim 1, characterized in that, Before receiving the conference request sent by the calling terminal, the method further includes: Information about each first called terminal belonging to the called server is obtained from the called server through the intermediate server; The information of the first called terminal associated with the calling terminal from the information of each first called terminal is sent to the calling terminal, so that the calling terminal can determine the information of the first called terminal carried in the conference request.

3. The meeting implementation method according to claim 1 or 2, characterized in that, The conference request also carries information about at least one second called terminal belonging to the calling server; After receiving the conference request sent by the calling terminal, the method further includes: Based on the meeting information and the information of the second called terminal, a second invitation link is generated; Send the second invitation link to the second called terminal to invite the second called terminal to participate in the meeting indicated by the meeting information.

4. The meeting implementation method according to claim 1 or 2, characterized in that, The meeting information includes one or a combination of the following: the domain name of the meeting, the meeting ID, and the meeting password.

5. A method for implementing a meeting, characterized in that, Applied to a calling terminal, the method includes: A conference request is generated, which carries conference information and information about at least one first called terminal belonging to a called server. The called server and the calling server to which the calling terminal belongs belong to different domains. The called server and the calling server are connected to the same intermediate server. A conference request is sent to the calling server; wherein the conference request is used by the calling server to generate a first invitation link based on the conference information and the information of the first called terminal, and to send the first invitation link to the intermediate server; the first invitation link is used by the intermediate server to forward to the corresponding called server based on the information of the first called terminal, and by the called server to provide to the first called terminal, so that the first called terminal can initiate a conference join request to the called server based on the first invitation link; the domain of the conference indicated by the conference information is the domain of the calling server.

6. The meeting implementation method according to claim 5, characterized in that, Before generating the meeting request, the method further includes: Receive information about the first called terminal sent by the calling server and present it to the user; According to the user's instructions, the information of the first called terminal carried in the conference request is determined from the information of the first called terminal sent by the calling server; The generation of the meeting request includes: The conference request is generated based on the information of the first called terminal.

7. The meeting implementation method according to claim 5 or 6, characterized in that, The conference request also carries information about at least one second called terminal belonging to the calling server. The information of the second called terminal is used by the calling server to invite the second called terminal to participate in the conference indicated by the conference information.

8. A method for implementing a meeting, characterized in that, The method, applied to a called server, wherein the called server is connected to an intermediate server, and the intermediate server is also connected to at least one calling server belonging to a different domain from the called server, includes: The system receives a first invitation link sent by the intermediate server. The first invitation link carries conference information and information about at least one first called terminal belonging to the called server. The first invitation link is generated by the calling server and sent by the calling server to the intermediate server. The first invitation link is used by the intermediate server to forward to the called server based on the information of the first called terminal. The domain of the conference indicated by the conference information is the domain of the calling server. The first invitation link is forwarded to the corresponding first called terminal to invite the first called terminal to initiate a meeting join request for the meeting information to the called server based on the first invitation link.

9. The meeting implementation method according to claim 8, characterized in that, Before receiving the first invitation link sent by the intermediate server, the method further includes: The intermediate server sends information about each of the first called terminals to the calling server, so that the calling server can generate and send the first invitation link based on the received information about each of the first called terminals.

10. The meeting implementation method according to claim 8 or 9, characterized in that, After forwarding the first invitation link to the corresponding first called terminal, the method further includes: Receive a registration request initiated by the first called terminal based on the first invitation link, wherein the registration request carries the meeting information and the user information of the first called terminal; The registration request is verified. The verification result is returned to the first called terminal, so that the first called terminal can determine whether to join the conference indicated by the conference information if the verification result is successful.

11. A method for implementing a meeting, characterized in that, Applied to the first called terminal, the method includes: Receive a first invitation link sent by the called server. The first invitation link carries conference information. The domain where the conference is located, as indicated by the conference information, is the domain where the calling server is located. The calling server and the called server belong to different domains but are connected to the same intermediate server. Wherein, the first invitation link is generated by the calling server and sent by the calling server to the intermediate server; the first invitation link is used by the intermediate server to forward to the called server according to the information of the first called terminal, and by the called server to forward to the first called terminal, so as to invite the first called terminal to initiate a meeting join request for the meeting information to the called server based on the first invitation link. Determine whether to join the meeting indicated by the meeting information based on the user's instructions.

12. The meeting implementation method according to claim 11, characterized in that, The step of determining whether to join the meeting indicated by the meeting information based on user instructions includes: Based on the meeting information and the user information of the first called terminal, a registration request is sent to the called server. The system receives the verification result from the called server regarding the registration request, and if the verification result is successful, determines whether to join the meeting indicated by the meeting information based on the user's instructions.

13. A method for implementing a meeting, characterized in that, The method is applied to an intermediate server, which is further connected to at least one calling server and at least one called server belonging to a different domain from the calling server. The system receives a first invitation link sent by the calling server. The first invitation link carries conference information and information about at least one first called terminal belonging to the called server. The domain of the conference indicated by the conference information is the domain of the calling server. Based on the information of the first called terminal, the first invitation link is forwarded to the called server corresponding to the first called terminal; wherein, the first invitation link is provided by the called server to the first called terminal, so that the first called terminal can initiate a meeting join request for the meeting information to the called server based on the first invitation link.

14. The meeting implementation method according to claim 13, characterized in that, Before receiving the first invitation link sent by the calling server, the method further includes: Information about each of the first called terminals is obtained from the called server; The information obtained from each of the first called terminals is sent to the calling server.

15. A conference system, characterized in that, include: An intermediate server, at least two servers belonging to different domains connected to the intermediate server, and several terminals belonging to the at least two servers belonging to different domains; The intermediate server is used to implement the conference implementation method as described in claim 13 or 14; The at least two servers belonging to different domains are used to implement the conference implementation method as described in any one of claims 1 to 4, and / or to implement the conference implementation method as described in any one of claims 8 to 10; The terminal is configured to implement the conference implementation method as described in any one of claims 5 to 7, and / or to implement the conference implementation method as described in claim 11 or 12.

16. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the conference implementation method as described in any one of claims 1 to 4, or the conference implementation method as described in any one of claims 5 to 7, or the conference implementation method as described in any one of claims 8 to 10, or the conference implementation method as described in claim 11 or 12, or the conference implementation method as described in claim 13 or 14.

17. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the meeting implementation method as described in any one of claims 1 to 4, or implements the meeting implementation method as described in any one of claims 5 to 7, or implements the meeting implementation method as described in any one of claims 8 to 10, or implements the meeting implementation method as described in claim 11 or 12, or implements the meeting implementation method as described in claim 13 or 14.

Images