Conference data processing method and device, equipment and storage medium

Abstract

The application provides a conference data processing method and device, equipment and a storage medium, and relates to the technical field of communication. The method comprises the following steps: determining that a conference data update trigger condition is met, obtaining a first scheduled conference list of a target user as a conference creator, the scheduled conferences in the first scheduled conference list being scheduled conferences created by the target user through an instant messaging client in the past, the instant messaging client being provided with an interface for calling an SDK of a target application, the target application being an application with an audio and video conference function, requesting a server of the target application to create a second scheduled conference list according to the first scheduled conference list through a fusion server, receiving the second scheduled conference list sent by the server of the target application through the fusion server, establishing an association between the scheduled conferences in the first scheduled conference list and the scheduled conferences in the second scheduled conference list, and setting an updated identifier for each scheduled conference in the first scheduled conference list.

Description

Technical Field

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

[0002] Instant Messaging (IM) refers to services that enable the instant sending and receiving of internet messages. With the development of mobile internet, instant messaging technology, due to its deep integration with internet social networking, has led to the widespread adoption of various instant messaging applications. Simultaneously, 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, resulting in the widespread use of applications with audio and video conferencing capabilities. Summary of the Invention

[0003] This application provides a conference data processing method, apparatus, device, and storage medium to merge conference data from two different applications with audio and video conferencing functions into one conference data, facilitating users to use the interoperable audio and video conferencing functions between the two applications.

[0004] In a first aspect, this application provides a method for processing conference data, including:

[0005] Once the meeting data update trigger condition is met, a first list of scheduled meetings where the target user is the meeting creator is obtained. The scheduled meetings in the first list are those historically created by the target user through an instant messaging client. 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.

[0006] The fusion server requests the server of the target application to create a second scheduled meeting list, which is created based on the first scheduled meeting list.

[0007] The fusion server receives the second scheduled meeting list sent by the server of the target application;

[0008] Establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and set an updated identifier for each scheduled meeting in the first scheduled meeting list.

[0009] Secondly, this application provides a conference data processing apparatus, comprising:

[0010] The determination module is used to determine whether the meeting data update trigger conditions are met;

[0011] The acquisition module is used to acquire a first list of scheduled meetings where the target user is the meeting creator. The scheduled meetings in the first list are scheduled meetings created by the target user in the past through an instant messaging client. 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.

[0012] The sending module is used to request the server of the target application to create a second scheduled meeting list through the fusion server, wherein the second scheduled meeting list is created based on the first scheduled meeting list;

[0013] A receiving module is configured to receive the second scheduled meeting list sent by the server of the target application through the fusion server;

[0014] The processing module is used to establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and to set an updated identifier for each scheduled meeting in the first scheduled meeting list.

[0015] Thirdly, this application provides a conference data processing device, including: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform the method described in the first aspect or any of the possible embodiments of the first aspect.

[0016] Fourthly, 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 embodiments of the first aspect.

[0017] Fifthly, 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 embodiments of the first aspect.

[0018] In summary, this application enables the instant messaging client to call the SDK of the target application (which is an application with audio and video conferencing capabilities) by setting an interface in the instant messaging client. As a result, when a user creates a scheduled meeting, the target application can be called to create the scheduled meeting, allowing the same user to view the same scheduled meeting data in both the instant messaging client and the target application's client. Furthermore, when the instant messaging server determines that the meeting data update trigger condition is met, it obtains the first list of scheduled meetings historically created by the target user through the instant messaging client. Then, it requests the target application's server to create a second list of scheduled meetings based on the first list of scheduled meetings through the fusion server. After receiving the second list of scheduled meetings forwarded by the fusion server, it establishes an association between the scheduled meetings in the first list and the scheduled meetings in the second list, and sets an updated identifier for each scheduled meeting in the first list. This updates the scheduled meetings created by the instant messaging client before it was upgraded to the fusion version of the instant messaging client to the scheduled meetings created by the fusion version of the instant messaging client. This achieves the fusion of meeting data from two different applications with audio and video conferencing capabilities into one set of meeting data. This allows the same user to view the same scheduled meeting data on both the instant messaging client and the target application's client. Users can choose to view scheduled meeting information or join meetings on either the instant messaging client or the target application's client as needed, improving convenience and facilitating seamless use of the interoperable meeting functions between the two applications. Attached Figure Description

[0019] 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.

[0020] Figure 1 A schematic diagram of a conference data processing method provided in this application embodiment;

[0021] Figure 2 A flowchart illustrating a meeting data processing method provided in this application embodiment;

[0022] Figure 3 An interactive flowchart of a meeting data processing method provided in an embodiment of this application;

[0023] Figure 4 This application provides an interactive flowchart of a conference data processing method.

[0024] Figure 5An interactive flowchart of a meeting data processing method provided in the application embodiment;

[0025] Figure 6 A schematic diagram of the structure of a conference data processing device provided in an embodiment of this application;

[0026] Figure 7 This is a schematic block diagram of the conference data processing device provided in the embodiments of this application. Detailed Implementation

[0027] 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.

[0028] 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 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 explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

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

[0030] 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.

[0031] 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.

[0032] 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 can simply open a browser, log in to the corresponding interface, and conduct efficient remote meetings.

[0033] The meeting data processing method provided in this application embodiment involves an application with audio and video conferencing functions that can be implemented based on the aforementioned cloud technology. Specifically, it can integrate the powerful cloud computing capabilities and audio and video technology capabilities of cloud technology, and the audio and video conferencing function can be realized based on communication software with audio and video conferencing functions.

[0034] An audio / video conferencing application and an instant messaging application both have audio / video conferencing capabilities. The technical problem to be solved in this application is how to merge the meeting data of these two different applications into a single meeting data set, so that users can use the interoperable audio / video conferencing functions between the two applications. The same user can view the same scheduled meeting data on both the instant messaging client and the target application's client (which is the audio / video conferencing application). Users can choose either the instant messaging client or the target application's client as needed to join the meeting and perform other operations, thus improving convenience.

[0035] To address the aforementioned technical issues, this application implements 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. In this embodiment, the instant messaging client with the interface for calling the target application's SDK is referred to as a converged meeting version instant messaging client. For example, instant messaging clients with version 4.0 or higher are converged meeting version instant messaging clients. Therefore, when a user creates a scheduled meeting using the converged meeting version instant messaging client, they can call the target application to create the scheduled meeting, ensuring that the same user views the same scheduled meeting data on both the instant messaging client and the target application's client. However, when users create scheduled meetings using a non-converged conferencing version of an instant messaging client (e.g., version 4.0 or earlier), the client's original audio and video conferencing functionality is used. Since the instant messaging application and the target application are two heterogeneous systems with their own defined meeting information structures, after the instant messaging client is upgraded to a converged conferencing version, the scheduled meeting data created by the user before the upgrade needs to be updated to ensure that the same user views the same scheduled meeting data on both the instant messaging client and the target application's client. To further address this technical problem, this application retrieves the first scheduled meeting list historically created by the target user through the instant messaging client when the instant messaging server determines that the meeting data update trigger condition is met. The system then requests the target application's server to create a second scheduled meeting list based on the first scheduled meeting list via the converged server. Upon receiving the second scheduled meeting list forwarded by the converged server, it establishes an association between the scheduled meetings in the first and second scheduled meeting lists and sets an updated identifier for each scheduled meeting in the first list. This updates scheduled meetings created by the instant messaging client before upgrading to the converged meeting version to those created by the converged meeting version of the instant messaging client. This ensures that the same user views the same scheduled meeting data on both the instant messaging client and the target application's client. Users can choose either the instant messaging client or the target application's client to view scheduled meeting information or perform operations such as joining a meeting, improving convenience.

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

[0037] For example, Figure 1 A system architecture diagram of a conference data processing method provided in this application embodiment is shown below. Figure 1As shown, the system architecture may include an instant messaging server 1, a target application server 2, a converged server 3, and a first terminal device 4. The target application is an application with audio and video conferencing capabilities. The first terminal device 4 may be a personal computer, laptop, smart terminal, tablet, or portable wearable device, etc. The instant messaging server 1, the target application server 2, and the converged server 3 may be independent physical servers, server clusters composed of multiple physical servers, or a distributed system. They may also be cloud servers 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.

[0038] The first terminal device 4 can install and run an instant messaging application client, and the first terminal device 4 can communicate with the instant messaging server 1 via a network. The first terminal device 4 can also install and run a target application client, and the first terminal device 4 can communicate with the target application's server 2 via a network.

[0039] For example, an instant messaging application client can be installed and run on the first terminal device 4. This instant messaging client has an interface for calling the SDK of the target application, thereby enabling the target application to use its audio and video conferencing functions, such as scheduling meetings, initiating instant meetings, etc. Figure 1 As shown, in one implementable method, the instant messaging client with an interface for calling the SDK of the target application is referred to as the converged meeting version of the instant messaging client. To update scheduled meetings created by the instant messaging client before upgrading to the converged meeting version, ensuring that the same user views the same scheduled meeting data on both the instant messaging client and the target application's client, the instant messaging server 1, upon determining that the meeting data update trigger condition is met, obtains a first list of scheduled meetings where the target user is the meeting creator. These first list contains scheduled meetings historically created by the target user through the instant messaging client. The converged server 3 requests the target application's server 2 to create a second list of scheduled meetings based on the first list. The converged server then receives the second list from the target application's server, establishing an association between the scheduled meetings in the first and second lists, and setting an updated identifier for each scheduled meeting in the first list. This achieves the goal of updating scheduled meetings created by the instant messaging client before upgrading to the converged meeting version to those created by the converged meeting version. The technical solution of this application will be described in detail below with reference to the accompanying drawings.

[0040] 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.

[0041] Figure 2 A flowchart of a meeting data processing method provided in this application embodiment is shown below. Figure 2 As shown, the execution entity in this embodiment can be an instant messaging server, and the method can include the following steps:

[0042] S101. Determine that the meeting data update trigger condition is met, and obtain the first scheduled meeting list where the target user is the meeting creator. The scheduled meetings in the first scheduled meeting list are scheduled meetings created by the target user in the past through the instant messaging client. The instant messaging client has an interface for calling the SDK of the target application. The target application is an application with audio and video conferencing function.

[0043] Specifically, in this embodiment, the instant messaging client is equipped with an interface for calling the 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.

[0044] In one feasible approach, an icon (tab) can be set in the instant messaging client, which can display a function prompt such as "Meeting". When the user clicks the icon, the instant messaging client responds to the user's click operation by initiating a call to the target application and displaying the corresponding interface of the target application (such as the target application's homepage).

[0045] In this embodiment, the instant messaging client is installed and runs on a terminal device, the target user is the user using the terminal device, and the scheduled meetings in the first scheduled meeting list are scheduled meetings historically created by the target user through the instant messaging client, specifically scheduled meetings historically created by the target user through the instant messaging client's own audio and video conferencing function. The first scheduled meeting list includes meeting information for at least one scheduled meeting, which may include, for example, a meeting identifier (ID), meeting participants, meeting start time, meeting duration, and meeting room, etc.

[0046] Before the meeting data update trigger condition is met, the instant messaging client in this embodiment does not have an interface for calling the target application's SDK. The instant messaging client uses its own audio and video conferencing functions to create scheduled meetings. In this embodiment, an instant messaging client that has an interface for calling the target application's SDK is called a converged meeting version instant messaging client. For example, instant messaging clients with version 4.0 or higher are all converged meeting version instant messaging clients. For instance, if a user creates a scheduled meeting using an instant messaging client with version 3.0, and after a period of time, the user upgrades the instant messaging client from version 3.0 to version 4.0, then the scheduled meeting created by the user using version 3.0 needs to be updated. This ensures that the scheduled meeting created by the user using version 3.0 is updated before the user uses the meeting-related functions of the instant messaging client with version 4.0, without the user's awareness.

[0047] In one feasible approach, to ensure user transparency, this embodiment has three trigger points for updating scheduled meetings historically created by the target user through the instant messaging client. The specific methods for determining whether the meeting data update trigger conditions are met include the following three:

[0048] Method 1: Determine if the meeting data update trigger conditions are met. Specifically, these conditions can be:

[0049] Upon receiving a user login request from an instant messaging client, which carries the target user's identifier and the instant messaging client's version, if the instant messaging client is determined to be the converged conferencing version of the instant messaging client, then the conferencing data update trigger condition is met.

[0050] Specifically, in Method 1, a new asynchronous logic branch could be added when a user logs into the instant messaging client to update the scheduled meetings created in the user's history.

[0051] Alternatively, if a user login request is received from an instant messaging client, and the user login request carries the target user's identifier and the version of the instant messaging client, and the instant messaging client is determined to be the converged conferencing version of the instant messaging client based on the instant messaging client version, and the target user is determined to have the permission to update meeting data based on the target user's identifier, then the meeting data update trigger condition is determined to be met.

[0052] Specifically, this method adds a determination to whether the target user has the permission to update meeting data compared to the above methods. For example, this function of the instant messaging client in the converged meeting version is not open to all users, and permission switches can be set to select some users to use it.

[0053] In this embodiment, by updating the scheduled meetings historically created by the target user through the instant messaging client when the target user first logs into the converged meeting version of the instant messaging client, the scheduled meeting data can be updated in a timely manner and without the user's awareness.

[0054] Method 2: Determine if the meeting data update trigger conditions are met, specifically:

[0055] Upon receiving an SDK initialization request from the instant messaging client, which carries the identifier of the target user, and determining that the instant messaging client is the converged conferencing version of the instant messaging client based on the SDK initialization request, it is determined that the conferencing data update trigger condition is met.

[0056] Specifically, the converged conferencing version of the instant messaging client can have a tab icon displaying a function prompt such as "Conference." When a user clicks this tab, the instant messaging client responds by initiating a call to the target application and displaying its interface (such as the target application's homepage). After the instant messaging client is upgraded to the converged conferencing version, the first time a user clicks this tab, it triggers SDK initialization, and the instant messaging client sends an SDK initialization request to the instant messaging server. Optionally, SDK initialization can be periodic; for example, the first click of the tab triggers SDK initialization, and subsequent clicks after a preset period also trigger SDK initialization.

[0057] Alternatively, if an SDK initialization request is received from an instant messaging client, and the SDK initialization request carries the identifier of the target user, and the instant messaging client is determined to be the converged conferencing version of the instant messaging client based on the SDK initialization request, and the target user is determined to have the permission to update meeting data based on the identifier of the target user, then the meeting data update trigger condition is determined to be met.

[0058] Similarly, this method adds a determination to whether the target user has the permission to update meeting data compared to the above methods. For example, this function of the instant messaging client in the converged meeting version is not open to all users, and permission switches can be set to select some users to use it.

[0059] In this embodiment, by updating the scheduled meetings historically created by the target user through the instant messaging client when determining SDK initialization, the scheduled meeting data can be updated in a timely manner and without the user's awareness.

[0060] In actual user experience, the permission settings may be time-sensitive for some users. For instance, when a user logs into the upgraded instant messaging client, they may not have permission to update meeting data. However, once the user starts using the meeting function in the upgraded client, the permission is granted, and the user can update the historical meeting schedules that are about to begin. This allows for more timely and seamless updates to scheduled meeting data for the user.

[0061] Method 3: Determine if the meeting data update trigger conditions are met, specifically:

[0062] Before the meeting invitation for the target scheduled meeting is sent to the instant client, it is determined whether the instant client is a converged meeting version of the instant messaging client. The target scheduled meeting is a scheduled meeting that has reached its start time. If it is determined that the instant client is a converged meeting version of the instant messaging client, then the meeting data update trigger condition is met.

[0063] Specifically, in this embodiment, historically created scheduled meetings are scheduled meetings yet to start. When the start time of a target scheduled meeting arrives, the instant messaging server sends a meeting invitation ringtone to the instant messaging clients of the participating users of the target scheduled meeting, reminding them to join the target meeting. In this embodiment, before sending the meeting invitation ringtone to the instant messaging clients when the start time of a target scheduled meeting arrives, it can be determined whether the instant messaging client is a converged meeting version of the instant messaging client. If the instant messaging client is a converged meeting version of the instant messaging client, then it is determined that the meeting data update trigger condition is met.

[0064] Alternatively, before the meeting invitation for the target scheduled meeting rings to the instant client, determine whether the instant client is a converged meeting version of the instant messaging client, and whether the target scheduled meeting is a scheduled meeting that has reached its start time. If it is determined that the instant client is a converged meeting version of the instant messaging client, and it is determined that the target user has the permission to update meeting data, then the meeting data update trigger condition is met.

[0065] Similarly, this method adds a determination to whether the target user has the permission to update meeting data compared to the above methods. For example, this function of the instant messaging client in the converged meeting version is not open to all users, and permission switches can be set to select some users to use it.

[0066] Optionally, for an upgraded instant messaging client, one can first use Method 1, then Method 2, and then Method 3 to determine whether the meeting data update trigger condition is met. For example, for some users, the permission switch setting is time-sensitive. For instance, when a user logs into the upgraded instant messaging client, they may not have permission to update meeting data, but when the scheduled meeting is about to start, the permission is granted, and the user has the permission to update meeting data. At this time, the scheduled meeting data can be updated. By adding Method 3 to trigger the update, scheduled meeting data can be updated more promptly and seamlessly for the user, avoiding missing updates when the user has the necessary permissions.

[0067] S102. Request the target application's server to create a second scheduled meeting list through the fusion server. The second scheduled meeting list is created based on the first scheduled meeting list.

[0068] S103. Receive the second scheduled meeting list sent by the server of the target application through the fusion server.

[0069] Specifically, as an implementable approach, S102 can be:

[0070] Send a scheduled meeting creation request to the convergence server, so that the convergence server sends a scheduled meeting creation request to the server of the target application. The scheduled meeting creation request carries a first scheduled meeting list.

[0071] Accordingly, S103 can specifically be: receiving a second scheduled meeting list sent by the fusion server. The second scheduled meeting list is created for the server of the target application and sent to the fusion server. The scheduled meetings in the second scheduled meeting list are created based on the scheduled meetings in the first scheduled meeting list.

[0072] S104. Establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and set an updated identifier for each scheduled meeting in the first scheduled meeting list.

[0073] Specifically, after receiving the second list of scheduled meetings, the instant messaging server establishes an association between the scheduled meetings in the first list and the scheduled meetings in the second list. For example, a mapping relationship can be established. Specifically, the meeting identifiers of the scheduled meetings in the first list and the scheduled meetings in the second list have different formats. The scheduled meetings in the first list and the scheduled meetings in the second list can be associated through the meeting identifiers. Specifically, the meeting information of the two types of scheduled meetings can be associated.

[0074] Setting an updated identifier for each scheduled meeting in the first scheduled meeting list serves two purposes: firstly, it identifies the scheduled meeting as an updated scheduled meeting; secondly, for scheduled meetings with an updated identifier, subsequent operations such as meeting ringing and meeting entry can be performed through the updated scheduled meeting's logic and data interface. For details, please refer to the processes in S105-S106.

[0075] In both methods one and two, further, in one implementable method, the method of this embodiment may also include:

[0076] S105. Determine the start time of the first scheduled meeting, where the first scheduled meeting is any scheduled meeting in the first scheduled meeting list.

[0077] S106. Based on the second scheduled meeting list associated with the first scheduled meeting, send a meeting invitation ringtone to the instant messaging client corresponding to the participating user of the first scheduled meeting. The meeting invitation ringtone carries the meeting identifier of the second scheduled meeting.

[0078] Specifically, upon determining the start time of the first scheduled meeting, the instant messaging server sends a meeting invitation ring to the instant messaging clients of the participating users (including the target user) of the first scheduled meeting. This meeting invitation ring carries the meeting identifier for the second scheduled meeting. This allows previously scheduled meetings to proceed through the updated scheduling logic and data interface.

[0079] In the above method, a meeting invitation ringtone is sent to the instant messaging client corresponding to the first scheduled meeting participant. Optionally, meeting entry information can also be sent to the instant messaging client corresponding to the first scheduled meeting participant, as follows:

[0080] Alternatively, S106 can also be: based on the second scheduled meeting list associated with the first scheduled meeting, send meeting entry information to the instant messaging client corresponding to the participating user of the first scheduled meeting, the meeting entry information carrying the meeting information of the second scheduled meeting.

[0081] Specifically, meeting entry information can be, for example, a meeting link, a meeting ID, or a meeting card, making it easy for users to click on the meeting entry information to join the meeting.

[0082] In both methods one and two, further, in one implementable method, the method of this embodiment may also include:

[0083] S107. Receive a scheduled meeting creation request sent by the target instant messaging client. The scheduled meeting creation request carries the identifier of the target user.

[0084] S108. If it is determined that the version of the target instant messaging client is not the converged conferencing version, an instruction message is sent to the target instant messaging client to instruct the target user to upgrade the version of the target instant messaging client.

[0085] Specifically, once the scheduled meetings in the target user's first scheduled meeting list are updated, it indicates that the instant messaging client used by the target user is now the converged meeting version of the instant messaging client. Since the target user may use different terminal devices, such as terminal device 1 (e.g., a mobile phone) and terminal device 2 (e.g., a computer), and the target user upgraded their instant messaging client to the converged meeting version while using terminal device 1, if the target user subsequently uses terminal device 2 to create a scheduled meeting, the server needs to intercept and prompt the target user to upgrade their instant messaging client version. Specifically, in S107, if the instant messaging server receives a scheduled meeting creation request initiated by the target user through the target instant messaging client, it determines whether the target instant messaging client version is the converged meeting version. If it is not, it needs to send an instruction message to the target instant messaging client, instructing the target user to upgrade their target instant messaging client version. This facilitates the user's use of the converged meeting version of the instant messaging client's meeting functions.

[0086] In Method 3, which is for a scheduled meeting, the corresponding step in S101 is to obtain the first list of scheduled meetings where the target user is the meeting creator. Specifically, this can be done by obtaining the target scheduled meeting and identifying the target scheduled meeting as a scheduled meeting in the first list of scheduled meetings.

[0087] Accordingly, in S102, the fusion server requests the target application's server to create a second scheduled meeting list. Specifically, the fusion server requests the target application's server to create a new scheduled meeting. The new scheduled meeting is created based on the target scheduled meeting, and the new scheduled meeting is identified as a scheduled meeting in the second scheduled meeting list.

[0088] Accordingly, in S104, the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list is established. Specifically, this can be done by establishing the association between the target scheduled meeting and the new scheduled meeting.

[0089] Optionally, in method three, the method of this embodiment may further include:

[0090] Based on the meeting information of the new scheduled meeting, a meeting invitation bell for the target scheduled meeting is sent to the instant client. The meeting invitation bell for the target scheduled meeting carries the meeting identifier of the new scheduled meeting.

[0091] The new scheduled meeting identifier is created by the target application. By sending a meeting invitation ringtone carrying the new scheduled meeting identifier to the instant messaging client, the instant messaging client can initiate the new scheduled meeting entry process, that is, the process of entering the meeting through the target application.

[0092] Optionally, the method of this embodiment may further include, before requesting the target application's server to create a second scheduled meeting list via the fusion server:

[0093] The convergence server requests the target application's server to pre-register the participants for each scheduled meeting in the first scheduled meeting list. Specifically, the instant messaging server sends a pre-registration request for a scheduled meeting to the convergence server. This pre-registration request carries the identifiers of the participants and the meeting identifier of the scheduled meeting. For example, the identifiers of the participants are A, B, and C, and the meeting identifier is 1. The convergence server then sends this pre-registration request to the target application's server. The target application's server pre-registers the participants for the scheduled meeting based on the identifiers of the participants and the meeting identifier. For example, the identifiers assigned to participants A, B, and C are A', B', and C', respectively.

[0094] The meeting data processing method provided in this embodiment enables the instant messaging client to call the SDK of the target application (which is an application with audio and video conferencing capabilities) by setting an interface in the instant messaging client. Thus, when a user creates a scheduled meeting, the target application can be called to create the scheduled meeting, allowing the same user to view the same scheduled meeting data in both the instant messaging client and the target application's client. Furthermore, when the instant messaging server determines that the meeting data update trigger condition is met, it obtains the first list of scheduled meetings historically created by the target user through the instant messaging client. Then, it requests the target application's server to create a second list of scheduled meetings based on the first list of scheduled meetings through the fusion server. After receiving the second list of scheduled meetings forwarded by the fusion server, it establishes an association between the scheduled meetings in the first list and the scheduled meetings in the second list, and sets an updated identifier for each scheduled meeting in the first list. This updates the scheduled meetings created by the instant messaging client before it was upgraded to the fusion version of the instant messaging client to the scheduled meetings created by the fusion version of the instant messaging client. This achieves the fusion of meeting data from two different applications with audio and video conferencing capabilities into one set of meeting data. This allows the same user to view the same scheduled meeting data on both the instant messaging client and the target application's client. Users can choose to view scheduled meeting information or join meetings on either the instant messaging client or the target application's client as needed, improving convenience and facilitating seamless use of the interoperable meeting functions between the two applications.

[0095] The following detailed description uses a specific embodiment to illustrate the conference data processing method provided in this application. (Specifically, in conjunction with...) Figures 3-5 This application describes the interactive processing procedure of the meeting data processing method provided in the embodiments.

[0096] Figure 3 An interactive flowchart of a meeting data processing method provided in this application embodiment is shown below. Figure 3 As shown, the method may include the following steps:

[0097] S201. In response to the login operation triggered by the target user, the instant messaging client sends a user login request to the instant messaging server. The user login request carries the target user's identifier and the version of the instant messaging client.

[0098] S202. The instant messaging server determines that the instant messaging client is the converged meeting version of the instant messaging client based on the instant messaging client version. If the instant messaging client version is determined to be the instant messaging client version of the converged meeting version, the server determines that the meeting data update trigger condition is met, obtains the first scheduled meeting list with the target user as the meeting creator, and sends a scheduled meeting creation request to the converged meeting server. The scheduled meeting creation request carries the first scheduled meeting list.

[0099] Optionally, S202 can also be: The instant messaging server determines that the instant messaging client is the converged meeting version of the instant messaging client based on the version of the instant messaging client, and determines that the target user has the permission to update meeting data based on the identifier of the target user. If the condition for triggering meeting data update is met, the server obtains the first list of scheduled meetings where the target user is the meeting creator, and sends a scheduled meeting creation request to the converged server. The scheduled meeting creation request carries the first list of scheduled meetings.

[0100] The first scheduled meeting list consists of scheduled meetings created by the target user in the past through the instant messaging client. The instant messaging client has an interface for calling the SDK of the target application, which is an application with audio and video conferencing capabilities.

[0101] S203. The converged server sends a pre-registration request to the server of the target application to schedule a meeting.

[0102] Specifically, if the first list of scheduled meetings includes multiple scheduled meetings, a pre-registration request for each scheduled meeting can be sent sequentially to the target application's server. This pre-registration request carries the identifier of a participating user and the meeting identifier of the scheduled meeting. Alternatively, multiple pre-registration requests can be sent to the target application's server, each carrying the identifiers of participating users and the meeting identifiers of multiple scheduled meetings.

[0103] S204. The converged server sends a scheduled meeting creation request to the server of the target application, and the scheduled meeting creation request carries the first scheduled meeting list.

[0104] S205. The server of the target application creates a scheduled meeting from the second scheduled meeting list based on the scheduled meetings in the first scheduled meeting list.

[0105] S206. The target application's server sends a second scheduled meeting list to the fusion server.

[0106] S207. The converged server sends a second list of scheduled meetings to the instant messaging server.

[0107] S208. The instant messaging server establishes the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and sets an updated identifier for each scheduled meeting in the first scheduled meeting list.

[0108] Optionally, the method in this embodiment may further include:

[0109] S209. In response to the user's action of triggering the scheduled meeting list, the target application client sends a request to the target application's server to obtain the scheduled meeting list.

[0110] S210. After receiving the request to obtain the list of scheduled meetings, the server of the target application sends a second list of scheduled meetings to the client of the target application.

[0111] Optionally, the method in this embodiment may further include:

[0112] S211. In response to a user's triggering of an operation to retrieve the list of scheduled meetings, the instant messaging client sends a request to the server of the target application to retrieve the list of scheduled meetings.

[0113] S212. After receiving the request to obtain the list of scheduled meetings, the server of the target application sends a second list of scheduled meetings to the instant messaging client.

[0114] Optionally, the method in this embodiment may further include:

[0115] S213. Determine the start time of the first scheduled meeting, where the first scheduled meeting is any scheduled meeting in the first scheduled meeting list.

[0116] S214. Based on the second scheduled meeting list associated with the first scheduled meeting, send a meeting invitation ringtone to the instant messaging client corresponding to the participating user of the first scheduled meeting. The meeting invitation ringtone carries the meeting identifier of the second scheduled meeting.

[0117] Alternatively, S214 can also be: based on the second scheduled meeting list associated with the first scheduled meeting, send meeting entry information to the instant messaging client corresponding to the participating user of the first scheduled meeting, the meeting entry information carrying the meeting information of the second scheduled meeting.

[0118] Figure 4 This application provides an interactive flowchart of a conference data processing method, as shown in the embodiments below. Figure 4 As shown, the method may include the following steps:

[0119] S301. The instant messaging client sends an SDK initialization request to the instant messaging server. The SDK initialization request carries the identifier of the target user.

[0120] S302. If the instant messaging server determines that the instant messaging client is the converged meeting version of the instant messaging client based on the SDK initialization request, then it determines that the meeting data update trigger condition is met, obtains the first scheduled meeting list with the target user as the meeting creator, and sends a scheduled meeting creation request to the converged server. The scheduled meeting creation request carries the first scheduled meeting list.

[0121] Optionally, S302 can also be: The instant messaging server determines that the instant messaging client is the converged meeting version of the instant messaging client based on the SDK initialization request, and determines that the target user has the permission to update meeting data based on the target user's identifier. If the target user's identifier is determined to be the target user, the server determines that the meeting data update trigger condition is met, obtains the first list of scheduled meetings where the target user is the meeting creator, and sends a scheduled meeting creation request to the converged server. The scheduled meeting creation request carries the first list of scheduled meetings.

[0122] S303-S311 are the same as S203-S211, and will not be described again here.

[0123] Figure 5 An interactive flowchart of a meeting data processing method provided in the application embodiment is shown below. Figure 5 The method may include the following steps:

[0124] S401. Before the instant messaging server sends a meeting invitation to the instant client for the target scheduled meeting, it determines whether the meeting data update triggering conditions are met. The target scheduled meeting is the scheduled meeting that has reached the meeting start time.

[0125] Specifically, it is determined whether the instant messaging client is a converged conferencing version of the instant messaging client. If so, the meeting data update trigger condition is met. Optionally, if the instant messaging client is a converged conferencing version of the instant messaging client, and it is determined that the target user has the permission to update meeting data, the meeting data update trigger condition is met.

[0126] S402. If it is determined that the meeting data update triggering condition is met, obtain the meeting information of the target scheduled meeting, and send a scheduled meeting creation request to the fusion server. The scheduled meeting creation request carries the meeting information of the target scheduled meeting.

[0127] S403. If it is determined that the meeting data update triggering condition is not met, a meeting invitation ring is sent to the instant messaging client. The meeting invitation ring carries the meeting identifier of the target scheduled meeting.

[0128] Specifically, after receiving a meeting invitation ring, the instant messaging client can display a meeting invitation interface, and users can join the meeting (i.e., join the meeting) by operating the meeting invitation interface.

[0129] S404. The converged server sends a pre-registration request for the target scheduled meeting to the server of the target application.

[0130] Specifically, the pre-registration request for the target scheduled meeting carries the identifiers of the participants of the target scheduled meeting and the meeting identifier of the target scheduled meeting.

[0131] S405. The converged server sends a scheduled meeting creation request to the server of the target application. The scheduled meeting creation request carries the meeting information of the target scheduled meeting.

[0132] S406. The target application's server creates a new scheduled meeting based on the meeting information of the target scheduled meeting.

[0133] S407. The target application's server sends a new scheduled meeting information to the converged server.

[0134] S408, the converged server sends meeting information for a new scheduled meeting to the instant messaging server.

[0135] S409. The instant messaging server establishes the association between the target scheduled meeting and the new scheduled meeting, and sets an updated identifier for the new scheduled meeting.

[0136] Optionally, the method in this embodiment may further include:

[0137] S410. Based on the meeting information of the new scheduled meeting, send a meeting invitation bell for the target scheduled meeting to the instant client. The meeting invitation bell for the target scheduled meeting carries the meeting identifier of the new scheduled meeting.

[0138] Specifically, after receiving a meeting invitation from a target scheduled meeting, the instant messaging client can display a meeting invitation interface, allowing users to join the meeting (i.e., enter the meeting) by interacting with the meeting invitation interface. Users can also interact with the target application client to join the meeting.

[0139] Figure 6 This is a schematic diagram of the structure of a conference data processing device provided in an embodiment of this application, as shown below. Figure 6 As shown, the device may include: a determining module 11, an acquiring module 12, a sending module 13, a receiving module 14, and a processing module 15, wherein,

[0140] Module 11 is used to determine whether the meeting data update trigger conditions are met;

[0141] The acquisition module 12 is used to acquire the first list of scheduled meetings where the target user is the meeting creator. The scheduled meetings in the first list are scheduled meetings created by the target user in the past through the instant messaging client. 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.

[0142] Sending module 13 is used to request the server of the target application to create a second scheduled meeting list through the fusion server. The second scheduled meeting list is created based on the first scheduled meeting list.

[0143] The receiving module 14 is used to receive a second scheduled meeting list sent by the server of the target application through the fusion server;

[0144] The processing module 15 is used to establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and to set an updated identifier for each scheduled meeting in the first scheduled meeting list.

[0145] Optionally, the sending module 13 is used to send a scheduled meeting creation request to the convergence server, so that the convergence server sends the scheduled meeting creation request to the server of the target application, and the scheduled meeting creation request carries a first scheduled meeting list;

[0146] The receiving module 14 is used to receive the second scheduled meeting list sent by the fusion server. The second scheduled meeting list is created by the server of the target application and sent to the fusion server. The scheduled meetings in the second scheduled meeting list are created according to the scheduled meetings in the first scheduled meeting list.

[0147] Optionally, the determining module 11 is configured to, upon receiving a user login request sent by the instant messaging client from the receiving module 14, wherein the user login request carries the identifier of the target user and the version of the instant messaging client, determine that the instant messaging client is a converged conferencing version of the instant messaging client based on the version of the instant messaging client, and thus determine that the meeting data update triggering condition is met; or, if the instant messaging client is determined to be a converged conferencing version of the instant messaging client based on the version of the instant messaging client, and the target user is determined to have the permission to update meeting data based on the identifier of the target user, then determine that the meeting data update triggering condition is met.

[0148] Optionally, the determining module 11 is used to determine the target user's identifier when the receiving module 14 receives an SDK initialization request sent by the instant messaging client.

[0149] If the instant messaging client is determined to be the converged conferencing version of the instant messaging client based on the SDK initialization request, then the conferencing data update trigger condition is met.

[0150] Alternatively, if the instant messaging client is determined to be the converged conferencing version of the instant messaging client based on the SDK initialization request, and the target user is determined to have the permission to update meeting data based on the target user's identifier, then the meeting data update trigger condition is determined to be met.

[0151] Optionally, the determining module 11 is also used to determine the meeting start time of the first scheduled meeting, which is any scheduled meeting in the first scheduled meeting list;

[0152] The sending module 13 is also used to send a meeting invitation ring to the instant messaging client corresponding to the participating user of the first scheduled meeting based on the second scheduled meeting associated with the first scheduled meeting in the second scheduled meeting list. The meeting invitation ring carries the meeting identifier of the second scheduled meeting.

[0153] Alternatively, based on the second scheduled meeting list associated with the first scheduled meeting, send meeting entry information to the instant messaging client corresponding to the participating user of the first scheduled meeting. The meeting entry information carries the meeting information of the second scheduled meeting.

[0154] Optionally, the receiving module 14 is also used to receive a scheduled meeting creation request sent by the target instant messaging client, the scheduled meeting creation request carrying the identifier of the target user;

[0155] The sending module 13 is also configured to: when the determining module 11 determines that the version of the target instant messaging client is not the converged conferencing version, send an instruction message to the target instant messaging client, the instruction message being used to instruct the target user to upgrade the version of the target instant messaging client.

[0156] Optionally, the determining module 11 is used to determine whether the instant client is a converged meeting version of the instant messaging client before the sending module 13 sends the meeting invitation ring to the instant client, and whether the target scheduled meeting is a scheduled meeting that has reached the meeting start time; if it is determined that the instant client is a converged meeting version of the instant messaging client, then it is determined that the meeting data update trigger condition is met; or, if it is determined that the instant client is a converged meeting version of the instant messaging client, and it is determined that the target user has the permission to update the meeting data, then it is determined that the meeting data update trigger condition is met.

[0157] Optionally, the acquisition module 12 is specifically used to acquire the target scheduled meeting and identify the target scheduled meeting as a scheduled meeting in the first scheduled meeting list.

[0158] The sending module 13 is specifically used to: request the server of the target application to create a new scheduled meeting through the fusion server; the new scheduled meeting is created according to the target scheduled meeting; and the new scheduled meeting is identified as a scheduled meeting in the second scheduled meeting list.

[0159] Processing module 15 is specifically used to: establish the association between the target scheduled meeting and the new scheduled meeting.

[0160] Optionally, the sending module 13 is also used to: send a meeting invitation ring for the target scheduled meeting to the instant client based on the meeting information of the new scheduled meeting, wherein the meeting invitation ring for the target scheduled meeting carries the meeting identifier of the new scheduled meeting.

[0161] Optionally, the sending module 13 is also configured to: request the target application's server to pre-register the participants for each scheduled meeting in the first scheduled meeting list before requesting the target application's server to create a second scheduled meeting list via the fusion server.

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

[0163] The conference data processing apparatus 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 embodiment can be completed by the integrated logic circuits in the processor 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.

[0164] Figure 7 This is a schematic block diagram of the conference data processing device provided in the embodiments of this application.

[0165] like Figure 7 As shown, the conference data processing device may include:

[0166] 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.

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

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

[0169] 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.

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

[0171] 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).

[0172] 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 data processing device.

[0173] like Figure 7As shown, the conference data processing equipment may also include:

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

[0175] 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.

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

[0177] 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.

[0178] 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 accessible to a computer 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)).

[0179] 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.

[0180] 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.

[0181] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; 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, depending on 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.

[0182] 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 method for processing conference data, characterized in that, include: Once the meeting data update trigger condition is met, a first list of scheduled meetings created by the target user is obtained. The scheduled meetings in the first list are those created by the target user in the past through an instant messaging client. 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 fusion server requests the server of the target application to create a second scheduled meeting list, which is created based on the first scheduled meeting list. The fusion server receives the second scheduled meeting list sent by the server of the target application; Establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and set an updated identifier for each scheduled meeting in the first scheduled meeting list.

2. The method according to claim 1, characterized in that, The step of requesting the target application's server to create a second scheduled meeting list via the fusion server includes: Send a scheduled meeting creation request to the fusion server, so that the fusion server sends the scheduled meeting creation request to the server of the target application, the scheduled meeting creation request carrying the first scheduled meeting list; The step of receiving the second scheduled meeting list sent by the server of the target application through the fusion server includes: The system receives the second scheduled meeting list sent by the fusion server. The second scheduled meeting list is created by the server of the target application and sent to the fusion server. The scheduled meetings in the second scheduled meeting list are created based on the scheduled meetings in the first scheduled meeting list.

3. The method according to claim 1, characterized in that, The determination that the meeting data update trigger condition is met includes: The system receives a user login request sent by the instant messaging client, the user login request carrying the identifier of the target user and the version of the instant messaging client; If the instant messaging client is determined to be a converged conferencing version of the instant messaging client based on its version, then the conferencing data update trigger condition is met. Alternatively, if the instant messaging client is determined to be a converged conferencing version of the instant messaging client based on its version, and the target user is determined to have the permission to update meeting data based on the target user's identifier, then the meeting data update trigger condition is determined to be met.

4. The method according to claim 1, characterized in that, The determination that the meeting data update trigger condition is met includes: The instant messaging client sends an SDK initialization request, which carries the identifier of the target user. If the instant messaging client is determined to be a converged conferencing version of the instant messaging client based on the SDK initialization request, then the conferencing data update trigger condition is met. Alternatively, if the instant messaging client is determined to be a converged conferencing version of the instant messaging client based on the SDK initialization request, and the target user is determined to have the permission to update meeting data based on the target user's identifier, then the meeting data update triggering condition is determined to be met.

5. The method according to claim 3 or 4, characterized in that, The method further includes: Determine the start time of the first scheduled meeting, which is any scheduled meeting in the first scheduled meeting list; According to the second scheduled meeting list associated with the first scheduled meeting, a meeting invitation ring is sent to the instant messaging client corresponding to the participating user of the first scheduled meeting. The meeting invitation ring carries the meeting identifier of the second scheduled meeting. Alternatively, based on the second scheduled meeting list associated with the first scheduled meeting, a meeting entry information is sent to the instant messaging client corresponding to the participating user of the first scheduled meeting, and the meeting entry information carries the meeting information of the second scheduled meeting.

6. The method according to claim 3 or 4, characterized in that, The method further includes: Receive a scheduled meeting creation request sent by the target instant messaging client, wherein the scheduled meeting creation request carries the identifier of the target user; If it is determined that the version of the target instant messaging client is not the converged conferencing version, an instruction message is sent to the target instant messaging client, which instructs the target user to upgrade the version of the target instant messaging client.

7. The method according to claim 1, characterized in that, The determination that the meeting data update trigger condition is met includes: Before the meeting invitation for the target scheduled meeting is sent to the instant messaging client, it is determined whether the instant messaging client is a converged meeting version of the instant messaging client, and the target scheduled meeting is a scheduled meeting that has reached the meeting start time. If it is determined that the instant messaging client is a converged conferencing version of the instant messaging client, then it is determined that the meeting data update trigger condition is met; Alternatively, if it is determined that the instant messaging client is a converged conferencing version of the instant messaging client, and it is determined that the target user has the permission to update meeting data, then the meeting data update trigger condition is met.

8. The method according to claim 7, characterized in that, The process of obtaining the first list of scheduled meetings where the target user is the meeting creator includes: Obtain the target scheduled meeting and identify it as a scheduled meeting in the first scheduled meeting list; The step of requesting the target application's server to create a second scheduled meeting list via the fusion server includes: The fusion server requests the server of the target application to create a new scheduled meeting, the new scheduled meeting is created based on the target scheduled meeting, and the new scheduled meeting is identified as a scheduled meeting in the second scheduled meeting list; Establishing the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list includes: Establish the association between the target scheduled meeting and the new scheduled meeting.

9. The method according to claim 7, characterized in that, The method further includes: Based on the meeting information of the new scheduled meeting, a meeting invitation ringtone for the target scheduled meeting is sent to the instant messaging client. The meeting invitation ringtone for the target scheduled meeting carries the meeting identifier of the new scheduled meeting.

10. The method according to claim 1, characterized in that, Before requesting the target application's server to create a second scheduled meeting list via the fusion server, the method further includes: The fusion server requests the server of the target application to pre-register the participants for each scheduled meeting in the first scheduled meeting list.

11. A conference data processing device, characterized in that, include: The determination module is used to determine whether the meeting data update trigger conditions are met; The acquisition module is used to acquire a first list of scheduled meetings where the target user is the meeting creator. The scheduled meetings in the first list are scheduled meetings created by the target user in the past through an instant messaging client. 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. The sending module is used to request the server of the target application to create a second scheduled meeting list through the fusion server, wherein the second scheduled meeting list is created based on the first scheduled meeting list; A receiving module is configured to receive the second scheduled meeting list sent by the server of the target application through the fusion server; The processing module is used to establish the association between the scheduled meetings in the first scheduled meeting list and the scheduled meetings in the second scheduled meeting list, and to set an updated identifier for each scheduled meeting in the first scheduled meeting list.

12. A conference data processing 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-10.

13. 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-10.

14. 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-10.

Images