A conference transfer method and apparatus

Abstract

The specification provides a conference transfer method and device, applied to a first conference terminal, the method comprising: in response to a device switching instruction triggered for a target conference to which the first conference terminal has joined, generating a terminal switching request, the terminal switching request containing device information of a second conference terminal as a switching target; sending the terminal switching request to a server to make the server join the second conference terminal to the target conference and exit the first conference terminal from the target conference according to the terminal switching request.

Description

Technical Field

[0001] This specification relates to the field of conference communication, and in particular to a conference transfer method and apparatus. Background Technology

[0002] With the continuous development of internet and IoT technologies, it is becoming increasingly common to use mobile devices such as smartphones or dedicated conference equipment as meeting terminals for online meetings. In some cases, users may need to use different meeting terminals throughout the meeting, such as using a mobile phone outdoors and then switching to the conference equipment deployed in the meeting room once inside. Therefore, it is necessary to facilitate the transfer of meetings between different meeting terminals.

[0003] In related technologies, meeting transfer requires manual operation by the user: first, the user manually adds the new meeting terminal to the meeting containing the original terminal, and then manually removes the original terminal from the meeting after confirming the new terminal has successfully joined. However, this process is extremely cumbersome and inefficient. Summary of the Invention

[0004] In view of this, this specification provides a meeting transfer method and apparatus to address the shortcomings of the related art.

[0005] Specifically, this specification is implemented through the following technical solution:

[0006] According to a first aspect of the embodiments of this specification, a conference transfer method is provided, applied to a first conference terminal, the method comprising:

[0007] In response to a device switching instruction triggered for a target conference that the first conference terminal has joined, a terminal switching request is generated, the terminal switching request containing device information of the second conference terminal that is the target of the switching.

[0008] The terminal switching request is sent to the server, so that the server adds the second conference terminal to the target conference and removes the first conference terminal from the target conference according to the terminal switching request.

[0009] According to a second aspect of the embodiments of this specification, a conference transfer method is provided, applied to a server, the method comprising:

[0010] The system receives a terminal switching request sent by a first conference terminal. The terminal switching request is generated by the first conference terminal in response to a device switching instruction triggered for a target conference that the first conference terminal has joined. The terminal switching request includes device information of a second conference terminal that is the target of the switching.

[0011] The second conference terminal is added to the target conference according to the terminal switching request, and the first conference terminal is removed from the target conference.

[0012] According to a third aspect of the embodiments of this specification, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first or second aspect.

[0013] According to a fourth aspect of the embodiments of this specification, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method described in the first or second aspect.

[0014] In the technical solution provided in this specification, by generating a terminal switching request from the first conference terminal and sending the request to the server, and by including the device information of the first conference terminal and the device information of the second conference terminal as the switching target, the server can determine the operation target from the terminal switching request: determining the first conference terminal as the target to leave the conference and the second conference terminal as the target to join the conference. Based on this, the server automatically adds the second conference terminal to the target conference and removes the first conference terminal from the target conference, without requiring the user to pay attention to or participate in the switching process between multiple conference terminals, greatly simplifying user operations and improving conference transfer efficiency.

[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings.

[0017] Figure 1 This is a schematic diagram of the architecture of a conference transfer system shown in an exemplary embodiment of this specification;

[0018] Figure 2 This is a flowchart illustrating an exemplary embodiment of a meeting transfer method as shown in this specification;

[0019] Figures 3a-3c This is a schematic diagram illustrating a control interface according to an exemplary embodiment of this specification;

[0020] Figure 4This is a schematic diagram of the three-party interaction process of a meeting transfer method shown in an exemplary embodiment of this specification;

[0021] Figure 5 This is a flowchart illustrating another meeting transfer method as shown in an exemplary embodiment of this specification;

[0022] Figure 6 This is a schematic structural diagram of an electronic device shown in an exemplary embodiment of this specification;

[0023] Figure 7 This is a schematic diagram of the structure of a conference transfer device shown in an exemplary embodiment of this specification;

[0024] Figure 8 This is a schematic diagram of another conference transfer device illustrated in an exemplary embodiment of this specification. Detailed Implementation

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification.

[0026] It should be noted that in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the methods may include more or fewer steps than those described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments. It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0027] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0028] Figure 1 This is a schematic diagram of the architecture of a conference transfer system shown in an exemplary embodiment of this specification. The architecture may include a server 11, a first conference terminal 12, and a second conference terminal 13.

[0029] Server 11 can be deployed on a physical server containing a standalone host, or it can be deployed on a virtual server (such as a cloud server) hosted in a host cluster. Server 11 can run a server-side program for an application that supports meeting transfer functionality. Therefore, this server-side program can work in conjunction with the client-side program of the application to implement the meeting transfer solution described in this specification, thereby providing users with corresponding meeting transfer services. The application mentioned above can be any application that supports meeting transfer functionality, and this specification does not impose any restrictions on it. For example, the application can be an instant messaging (IM) application or a dedicated online conferencing application. Furthermore, the instant messaging application can be an enterprise instant messaging (EIM) application.

[0030] The first conference terminal 12 and the second conference terminal 13 can be electronic devices that support online conferencing. These electronic devices can be mobile phones, PCs (Personal Computers), and wearable devices (such as smartwatches and smart glasses) with applications that have online conferencing capabilities installed; this specification does not impose any limitations on this. These electronic devices can run client-side programs of applications with meeting transfer capabilities, thereby cooperating with the server-side programs described above to provide users with corresponding meeting transfer services. For example, if a user originally joined a meeting using the first conference terminal 12, the technical solution in this specification allows them to easily join the meeting using the second conference terminal 13 and leave the meeting using the first conference terminal 12, thus achieving meeting transfer between the first conference terminal 12 and the second conference terminal 13.

[0031] The network 14, which facilitates interaction between the first conference terminal 12, the second conference terminal 13, and the server 11, can include various types of wired or wireless networks. In one embodiment, the network can include the Public Switched Telephone Network (PSTN) and the Internet.

[0032] Figure 2 This is a flowchart illustrating an exemplary embodiment of a conference transfer method, which can be applied to a first conference terminal and specifically includes the following steps:

[0033] S201, in response to a device switching instruction triggered for a target conference that the first conference terminal has joined, a terminal switching request is generated, the terminal switching request containing device information of the second conference terminal that is the target of the switching.

[0034] When a user needs to transfer a target meeting already joined by the first conference terminal to another conference terminal, they can trigger a device switching command for the target meeting through human-computer interaction with the first conference terminal. The first conference terminal will then respond to the device switching command and generate a corresponding terminal switching request. The human-computer interaction between the user and the first conference terminal can take any form, such as clicking virtual button options displayed on the first conference terminal or issuing control voice commands to the first conference terminal; this manual does not impose any restrictions on this.

[0035] The terminal switching request includes device information for the first conference terminal and device information for the second conference terminal, which is the target of the switching. The device information can be a unique device identifier used to identify the corresponding conference terminal. For example, the device information can be information set at the factory for the corresponding conference terminal, such as MAC (Media Access Control) address, IMEI (International Mobile Equipment Identity), UDID (Unique Device Identifier), etc. This specification does not impose any limitations on this. Alternatively, the device information can be a unique identifier for the corresponding conference terminal temporarily generated during use based on a preset identification algorithm. This unique identifier can be calculated by the corresponding conference terminal itself (and, if necessary, synchronized to the server or other conference terminals), or it can be calculated by the server and assigned to the conference terminal. This specification does not impose any limitations on this.

[0036] The device information of the first conference terminal can be stored in a preset storage space corresponding to the first conference terminal, so that the first conference terminal can quickly obtain it when generating the aforementioned terminal switching request. The aforementioned preset storage space can be the local storage space of the first conference terminal or a corresponding remote storage space (such as cloud storage space). The first conference terminal can obtain the device information of the second conference terminal in any way, and this specification does not limit this; among them, several possible acquisition methods will be described below. It should be noted that the first conference terminal can temporarily obtain the device information of the second conference terminal when it confirms that a terminal switching request needs to be generated, or it can obtain the device information of the second conference terminal in advance to avoid affecting the efficiency of generating the terminal switching request.

[0037] In one embodiment, the first conference terminal can identify the second conference terminal and establish a data transmission link with it. Then, based on this data transmission link, the first conference terminal sends a device information acquisition request to the second conference terminal and receives device information from the second conference terminal returned by the second conference terminal based on the device information acquisition request. The first conference terminal can identify the second conference terminal in any way. For example, the first conference terminal can scan nearby conference terminals using near-field communication (NFC) technology and designate the scanned terminals as the second conference terminal, or it can display the scanned conference terminals to the user for selection as the second conference terminal, thereby establishing a data transmission link with the second conference terminal. As another example, the first conference terminal can scan a graphic code (such as a QR code) displayed on the second conference terminal under the user's operation to establish a data transmission link with the second conference terminal based on the information contained in the graphic code. The aforementioned data transmission link can be established using technologies such as Bluetooth, Near Field Communication (NFC), Long Range Radio (LoRa), infrared, or Wi-Fi, and this specification does not limit this to any particular method.

[0038] In another embodiment, the second conference terminal can transmit content containing its own device information to external devices via a preset transmission method. Correspondingly, the first conference terminal can collect content via a preset collection method corresponding to the preset transmission method, wherein: upon collecting content transmitted by any conference terminal, the first conference terminal can use that conference terminal as the second conference terminal, and the device information contained in the collected content as the device information of the second conference terminal. Compared to the data transmission link involved in the previous embodiment, the content transmission and collection in this embodiment do not involve establishing a data transmission link between the second and first conference terminals, thus offering greater flexibility and higher efficiency.

[0039] For example, the content transmitted by the second conference terminal can include any of the following: sound, images, or characters. For instance, for content containing sound: the second conference terminal can encode its own device information into an audio signal and generate a sound of a preset frequency through a speaker to transmit the audio signal; correspondingly, the first conference terminal can collect and analyze the sound through a pickup (such as a microphone) to obtain the device information of the second conference terminal. In a more specific embodiment, the audio signal can be transmitted and collected using ultrasound, thereby avoiding noise that could affect normal communication or participation by users.

[0040] For example, regarding content containing images: the second conference terminal can encode its own device information into an image (such as a QR code, barcode, or other pattern containing encoded information) and display the image through a screen or other display device; correspondingly, the first conference terminal can capture and analyze the image displayed by the second conference terminal through a camera, thereby obtaining the device information of the second conference terminal.

[0041] For example, regarding content containing characters: the second conference terminal can directly use its own device information as text information or encode the device information using a preset encoding method to obtain the corresponding encoded text information, and then display and transmit the text information through a screen or other display device; correspondingly, the first conference terminal can use a camera to recognize and parse the text information displayed by the second conference terminal, thereby obtaining the device information of the second conference terminal, or the first conference terminal can also display input options and allow the user to manually input the text information displayed by the second conference terminal, which is not limited in this specification.

[0042] In this embodiment, since there is no need to establish the aforementioned data transmission link between the first conference terminal and the second conference terminal, and there is no need to exchange the device information of the second conference terminal through a "request-feedback" method between the first conference terminal and the second conference terminal, unnecessary communication resources between the first conference terminal and the second conference terminal are saved, and the efficiency of the first conference terminal in obtaining the device information of the second conference terminal is improved.

[0043] S202, the terminal switching request is sent to the server, so that the server adds the second conference terminal to the target conference and removes the first conference terminal from the target conference according to the terminal switching request.

[0044] After successfully receiving the terminal switching request, the server can determine the first account information logged in on the first conference terminal and the second account information logged in on the second conference terminal. Then, it can send a join / leave command to the conference terminal corresponding to the logged-in account, for example, via push notification. Specifically, the join command can be pushed to the second conference terminal corresponding to the second account information, causing the second conference terminal to join the target conference; simultaneously, the leave command can be pushed to the first conference terminal corresponding to the first account information, causing the first conference terminal to leave the target conference. The process of the second conference terminal joining the target conference can be considered as establishing a conference channel between the server and the second conference terminal. This channel is used to transmit basic conference-related information (such as the conference identifier, number of participants, conference duration, and other participants' personal information) and audio / video streams. The process of the first conference terminal leaving the target conference can be considered as the server disconnecting the conference channel originally established with the second conference terminal.

[0045] In order to remove the first conference terminal from the target conference, the server needs to obtain the device information of the first conference terminal. The manual specifies several methods the server can use to obtain this device information, and this manual does not limit this approach. The following lists and explains several methods for obtaining the device information of the first conference terminal:

[0046] In one embodiment, by having the server maintain some mapping relationships, the device information of the first conference terminal can be obtained by combining the device information of the second conference terminal contained in the terminal switching request.

[0047] For example, the server can maintain a first mapping relationship between a first conference terminal and a second conference terminal. After receiving the terminal switching request, it can determine the device information of the first conference terminal based on the device information of the second conference terminal, so as to remove the first conference terminal from the target conference.

[0048] Regarding the aforementioned first mapping relationship, when the same second conference terminal has mapping relationships with multiple first conference terminals, the server can determine the corresponding first conference terminal from among the multiple first conference terminals according to preset mapping conditions. These preset mapping conditions include, but are not limited to: the current participation status of the first conference terminal conforming to a preset status, the geographical location of the first conference terminal matching a preset geographical range, and the device type of the first conference terminal conforming to a preset type. For example, if first conference terminals A and B have a mapping relationship with second conference terminal C, and assuming first conference terminal A is in a participating state while first conference terminal B is not in a participating state, then after receiving a terminal switching request containing device information of the second conference terminals, the server can determine first conference terminals A and B according to the established mapping relationship, and identify the first conference terminal A in a participating state, in order to transfer the meeting to it. Those skilled in the art will understand that reducing the amount of data in the terminal switching request can further improve the transmission efficiency of the request. In addition, the server can also ensure that a unique first conference terminal can be determined by increasing the number of mapping conditions or setting additional rules when the mapping conditions are met (for example, when both the first conference terminals A and B are in the conference state, the first conference terminal A is set as the default device that needs to be transferred to the conference). This specification does not impose any restrictions on this.

[0049] For example, the server can maintain the characteristic requirements of a second conference terminal and the characteristic information of the first conference terminal (such as the corresponding terminal's participation status, geographical location, device type, etc.). After receiving the terminal switching request, the server can determine the second conference terminal and its corresponding characteristic requirements based on the device information of the second conference terminal, and then determine the first conference terminal whose characteristic information matches the aforementioned characteristic requirements. Assume: The server maintains the characteristic requirements of a second conference terminal C, which is a geographical range (e.g., floor Y of building X). The server can also determine the first conference terminal whose geographical location is within the aforementioned geographical range from multiple conference terminals based on this characteristic requirement (e.g., first conference terminal A is located on floor Y of building X, and first conference terminal B is located on floor Z of building X; therefore, the characteristic information of first conference terminal B obviously matches the characteristic requirements of second conference terminal C, and thus first conference terminal B is the conference terminal that needs to be transferred). The geographical locations of the multiple conference terminals can be the default addresses set by each terminal or the location information most recently sent to the server; this specification does not impose any restrictions on this.

[0050] In another embodiment, by including descriptive information about the first conference terminal in the terminal switching request, the server can determine the device information of the first conference terminal accordingly.

[0051] For example, a terminal switching request can include device information for the first conference terminal. Upon receiving the request, the server can directly determine the device information of the first conference terminal from this request. Assuming that both first conference terminals A and B are in the target conference, when a user using first conference terminal A wants to transfer the conference to second conference terminal C, they can send a terminal switching request containing the device information of first conference terminal A to the server. This allows the server to determine to transfer the conference to first conference terminal A, rather than first conference terminal B or any other terminal.

[0052] For example, the terminal switching request can include information other than the device information of the first conference terminal to allow the server to indirectly determine the first conference terminal. For instance, the terminal switching request can also include characteristic information of the first conference terminal, and the server maintains a mapping relationship between the first conference terminal and the characteristic information. Based on the aforementioned characteristic information, the server can indirectly determine the first conference terminal, and then add the second conference terminal to the target conference according to the terminal switching request, and remove the first conference terminal from the target conference. Assuming the server maintains the following mapping relationship: First conference terminal A - Device type A, geographical location is building X, floor Y; First conference terminal A - Device type B, geographical location is building X, floor Y, then when the server receives characteristic information containing "device type B, geographical location is building X, floor Y", it can determine that a conference transfer needs to be performed on the first conference terminal B based on the above mapping relationship.

[0053] In the scheme described in this specification, the aforementioned target meeting can be determined by the server in different ways based on the actual situation. Examples of several possible determination methods employed by the server are given below.

[0054] In one embodiment, the server may maintain a second mapping relationship between the first conference terminal and the target conference. This second mapping relationship can be used to instruct the server to add the second conference terminal to the target conference and remove the first conference terminal from the target conference according to the terminal switching request. In this embodiment, the first conference terminal only needs to send the corresponding device information, and the conference information of the target conference can be quickly determined by the server according to the second mapping relationship, thereby reducing the amount of data transmission and reducing the data transmission pressure between the first conference terminal and the server. Furthermore, the second mapping relationship can be stored based on a structure such as a database table, and this specification does not limit this.

[0055] In another embodiment, the terminal switching request may include not only the device information of the first and second conference terminals, but also the meeting information of the target conference. This meeting information can be used to instruct the server to add the second conference terminal to the target conference and remove the first conference terminal from the target conference. In other words, in this embodiment, when the first conference terminal generates a terminal switching request, it can add the meeting information of the target conference it has already joined to the terminal switching request. Compared to the previous embodiment, the server in this embodiment does not need to indirectly determine the target conference through a method similar to a second mapping relationship, but can directly obtain the meeting information of the target conference from the terminal switching request. Therefore, it reduces the additional overhead required by the server in terms of storage space and processing performance, reduces equipment costs, and improves the efficiency of the terminal switching process.

[0056] In the technical solution of this specification, after joining the target conference, the second conference terminal can have the same participant identity as the first conference terminal, and thus have the corresponding operating permissions or capabilities.

[0057] In one embodiment, the server can determine the participant identity of the logged-in account of the first conference terminal in the target conference, and synchronize the determined participant identity to the logged-in account of the second conference terminal that has joined the target conference. The participant identity can be represented by the identity possessed by the corresponding account in the target conference (e.g., host or observer). The operational permissions or capabilities of the first conference terminal in the target conference depend on the participant identity of the logged-in account of the first conference terminal in the target conference (e.g., a host can speak and mute other participants, while an observer cannot speak). Therefore, the participant identity of the logged-in account of the second conference terminal in the target conference can be synchronized with the logged-in account of the first conference terminal, thereby enabling the second conference terminal to obtain the same operational permissions or capabilities as the first conference terminal. Specifically, the synchronization process can be regarded as recording the participant identity of the logged-in account of the first conference terminal and assigning the recorded participant identity to the logged-in account of the second conference terminal. Furthermore, the synchronization of participant identities can occur after the server adds the second conference terminal to the target conference and before it removes the first conference terminal from the target conference, or after the first conference terminal removes the target conference. This specification does not impose any restrictions on this.

[0058] After exiting the target meeting from the first conference terminal, the user can directly continue participating in the target meeting through the second conference terminal. During participation in the target meeting, if control of the second conference terminal is required (e.g., to implement control functions related to or unrelated to the target meeting), the user can operate directly on the second conference terminal without needing to use the first conference terminal, or they can control the second conference terminal through the first conference terminal.

[0059] In one embodiment, after exiting the target conference, the first conference terminal can display a control interface for the second conference terminal. This control interface includes device control options for the second conference terminal and / or conference control options for the target conference. The device control options and conference control options target different objects, which can change the way corresponding requests are sent and processed. Specifically, the device control options target the second conference terminal itself, such as the acquisition status of the audio and video streams, the specific device used to acquire the audio and video streams, the picture quality when playing the video stream, and the volume when playing the audio stream. The conference control options target the target conference, such as inviting other accounts to join the target conference, viewing the current conference participants, recording the current conference online, and displaying a QR code image containing relevant information about the target conference.

[0060] Therefore, the first conference terminal can respond to the trigger command for the aforementioned device control options by sending a corresponding device control request to the server, so that the server forwards the device control request to the second conference terminal, and the second conference terminal performs the corresponding device control operation according to the device control request. Alternatively, the first conference terminal can also respond to the trigger command for the aforementioned conference control options by sending a corresponding conference control request to the server, so that the server performs the corresponding conference control operation on the target conference according to the participant identity of the logged-in account of the second conference terminal in the target conference.

[0061] The following is combined with Figures 3a-3c Taking the example of the first conference terminal exiting the target conference and then acting as the remote control for the second conference terminal, this section introduces the corresponding interfaces of the first and second conference terminals. Figure 3aAs shown, assuming the first conference terminal 301 is a mobile device (e.g., a mobile phone or tablet), and the second conference terminal 311 is a fixed-position media terminal integrating audio and video capture functions, the first conference terminal 301 is in the corresponding target conference. The user can access the control panel 302 for that target conference by clicking or swiping up the screen. This control panel contains various operations for that target conference. When the user clicks the "Switch Device" option in the control panel 302, the first conference terminal 301 can obtain and display similar audio and video capture signals by analyzing the received ultrasonic waves. Figure 3b The device information 304 of the second conference terminal 311 can also display a "switch" button 303 to confirm the conference switch. When the user selects the corresponding device information 304 (at this time, the first conference terminal 301 may simultaneously receive and display multiple second conference terminals), they can click the button 303 to exit the target conference and display a similar... Figure 3c The interface, such as Figure 3c As shown, the first conference terminal 301 can display a device control option display interface 305 and a conference control option display interface 306. Furthermore, the second conference terminal 311 displays the original conference interface of the first conference terminal 301. In this embodiment, the first conference terminal 301 replaces the second conference terminal 311 in displaying its original control interface, allowing the second conference terminal 311 to only display important conference content, improving the user's conference experience and the efficiency of obtaining conference information. Of course, when the first conference terminal 301 is a mobile device, the above solution eliminates the extra process of searching for and controlling the second conference terminal 311, improving the smoothness and seamless experience of controlling the second conference terminal 311.

[0062] In one embodiment, the first conference terminal can record the conference configuration of the target conference, wherein the conference configuration includes the media device used by the first conference terminal when participating in the target conference; and simultaneously, when the first conference terminal receives a switching error notification returned by the server, it can restore the conference configuration of the first conference terminal for the target conference to the recorded conference configuration.

[0063] It is understandable that when any conference terminal joins a meeting, it needs to properly configure its meeting settings. These settings include the media devices used by the terminal, which can include, but are not limited to: devices for capturing conference audio (e.g., built-in or external microphones), devices for playing conference audio (e.g., built-in or external speakers), devices for capturing conference video (e.g., built-in or external cameras), and devices for playing conference video (e.g., built-in or external screens). This is to ensure a better meeting experience for users of any of these terminals. Especially if the default media device of any conference terminal malfunctions and is not set to a working media device, it may affect users' ability to participate in the meeting.

[0064] During the meeting transfer process between the first and second conference terminals, the first conference terminal will also cancel its original conference configuration when it exits the target meeting. For example, if the audio device used by the first conference terminal in the target meeting was a Bluetooth headset, it will switch back to the default audio device configuration after exiting the target meeting, such as the speaker and microphone on the first conference terminal. If the second conference terminal fails to join the target meeting (i.e., the switch fails) and the first conference terminal has already exited the target meeting, this embodiment can ensure that the first conference terminal can switch back to the original conference configuration used when it was in the target meeting after rejoining the target meeting based on the switch error notification. For example, the audio device can be switched from the speaker and microphone on the first conference terminal to a Bluetooth headset, without requiring the user to reconfigure the conference configuration of the first conference terminal. This also avoids the first conference terminal using the default configuration after rejoining the target meeting, which would affect the meeting experience or normal participation.

[0065] Figure 4 Figure 3 is a schematic diagram of a three-party interaction process of a meeting transfer method illustrated in an exemplary embodiment of this specification. The method specifically includes the following steps:

[0066] S401, Mobile phone receives device switching command.

[0067] In one embodiment, the first conference terminal is a user's personal mobile phone. When the user is outdoors, they can join the target conference using the conference software running on their phone. When the user returns to the office and wishes to transfer the target conference from their phone to a conference tablet in the office as a second conference terminal without interrupting the conference, the user can click the device switching option displayed on their phone to issue a device switching command to the phone.

[0068] S402. The conference tablet transmits information about its own device to external parties.

[0069] In one embodiment, the aforementioned conference tablet, as a dedicated conference device in the office, has the ability to continuously transmit ultrasonic waves to the outside world. The ultrasonic waves include the MAC address of the conference tablet, “9D-A8-87-29-C7-F5”, and the name, “Building A, 5th Floor, Room 502”.

[0070] S403: The content transmitted by the conference tablet is collected by the mobile phone.

[0071] S404. Obtain device information for the conference tablet using your mobile phone.

[0072] In one embodiment, the mobile phone receives ultrasonic waves emitted by the speaker of the conference tablet through its built-in microphone, and determines the MAC address and name of the conference tablet by analyzing the ultrasonic waves.

[0073] S405, The mobile terminal generates a terminal switching request.

[0074] In one embodiment, in response to the user's device switching command for the conference tablet, the mobile phone can generate a corresponding terminal switching request, which includes the MAC address of the mobile phone itself, the MAC address of the conference tablet, and the conference identifier of the target conference.

[0075] S406, The mobile phone sends a terminal switching request to the server.

[0076] S407. The server adds the conference tablet to the target conference based on the terminal switching request.

[0077] S408: The server removes the mobile phone from the target meeting based on the terminal switching request.

[0078] In one embodiment, after receiving a terminal switching request from the mobile phone, the server can establish a meeting link with the meeting tablet based on the MAC address of the meeting tablet and the meeting identifier of the target meeting in the terminal switching request, thereby inviting the meeting tablet to join the target meeting, and disconnect the meeting link between the mobile phone and the target meeting based on the MAC address of the mobile phone in the terminal switching request, thereby removing the mobile phone from the target meeting, and thus realizing the switching of the target meeting between the mobile phone and the meeting tablet.

[0079] The following is combined with Figure 5 The embodiments shown illustrate another aspect of the technical solution in this specification. Figure 5 This is a flowchart illustrating another meeting transfer method as shown in an exemplary embodiment of this specification, such as... Figure 5 As shown, this method, applied to a server, may include the following steps:

[0080] S501, Receive a terminal switching request sent by the first conference terminal. The terminal switching request is generated by the first conference terminal in response to a device switching instruction triggered for a target conference that the first conference terminal has joined. The terminal switching request includes device information of the second conference terminal that is the switching target.

[0081] S502, according to the terminal switching request, the second conference terminal is added to the target conference, and the first conference terminal is removed from the target conference.

[0082] As mentioned above, the method further includes:

[0083] The device information of the first conference terminal is obtained through the following method, so that the first conference terminal can be removed from the target conference:

[0084] If the server maintains a first mapping relationship between the first conference terminal and the second conference terminal, the device information of the first conference terminal is determined based on the device information of the second conference terminal and the first mapping relationship; or,

[0085] If the terminal switching request also includes the device information of the first conference terminal, the device information of the first conference terminal is obtained from the terminal switching request.

[0086] As mentioned above, the server maintains a second mapping relationship between the first conference terminal and the target conference; the server adds the second conference terminal to the target conference and removes the first conference terminal from the target conference based on the second mapping relationship and the device information of the first conference terminal and the device information of the second conference terminal in the terminal switching request.

[0087] As mentioned above, the terminal switching request also includes the meeting information of the target meeting; the server adds the second meeting terminal to the target meeting and removes the first meeting terminal from the target meeting based on the device information of the first meeting terminal, the device information of the second meeting terminal, and the meeting information of the target meeting in the terminal switching request.

[0088] As mentioned above, the server determines the participant identity corresponding to the logged-in account of the first conference terminal in the target conference; and synchronizes the determined participant identity to the logged-in account of the second conference terminal that has joined the target conference.

[0089] As mentioned above, after exiting the target conference, the first conference terminal displays a control interface for the second conference terminal. This control interface includes device control options for the second conference terminal and / or conference control options for the target conference. The method further includes: receiving a device control request sent by the first conference terminal in response to a trigger command for the device control options; forwarding the device control request to the second conference terminal; and causing the second conference terminal to perform a corresponding device control operation based on the device control request; and / or,

[0090] The system receives a meeting control request sent by the first meeting terminal in response to a trigger command for the meeting control option, and performs corresponding meeting control operations on the target meeting based on the participant identity of the logged-in account of the second meeting terminal in the target meeting according to the meeting control request.

[0091] As mentioned above, the first conference terminal records the conference configuration for the target conference, the conference configuration including the media devices used by the first conference terminal when participating in the target conference; the method further includes:

[0092] If the terminal switching request fails, a switching error notification is returned to the first conference terminal so that the first conference terminal can restore the conference configuration for the target conference to the recorded conference configuration.

[0093] As can be seen from the above embodiments, the solution in this specification generates a terminal switching request from the first conference terminal and sends it to the server. This terminal switching request includes the device information of the first conference terminal and the device information of the second conference terminal, which is the target of the switching. This allows the server to determine the operation target from the terminal switching request: identifying the first conference terminal as the target to leave the meeting and the second conference terminal as the target to join the meeting. The server then automatically adds the second conference terminal to the target meeting and removes the first conference terminal from the target meeting, without requiring user attention or participation in the switching process between multiple conference terminals. This greatly simplifies user operations and improves meeting transfer efficiency. Furthermore, the method of synchronizing participant identities ensures that the second conference terminal has the same operational permissions or capabilities as the first conference terminal in the target meeting. The display of the control interface of the first conference terminal for the second conference terminal also simplifies user control of the second conference terminal, improving the user experience when switching conference devices. It is worth mentioning that the solution in this specification also records the meeting configuration so that in the event of a switching anomaly, the meeting configuration of the first conference terminal for the target meeting can be restored to the recorded meeting configuration, improving the user-friendliness of the anomaly handling process.

[0094] Figure 6 This is a schematic structural diagram of an electronic device according to an exemplary embodiment. Please refer to... Figure 6 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile memory, and may also include other necessary hardware. The processor reads the corresponding computer program from the non-volatile memory into memory and then executes it, forming a conference transfer device at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution entity of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0095] Corresponding to the aforementioned embodiments of the meeting transfer method, this specification also provides an embodiment of a meeting transfer device.

[0096] Please refer to Figure 7 , Figure 7 This is a schematic diagram illustrating the structure of a conference transfer device in an exemplary embodiment. Figure 7 As shown, in a software implementation, the device may include:

[0097] The request generation unit 701 is configured to generate a terminal switching request in response to a device switching instruction triggered for a target conference that the first conference terminal has joined. The terminal switching request includes device information of the second conference terminal that is the target of the switching.

[0098] The request sending unit 702 is used to send the terminal switching request to the server, so that the server adds the second conference terminal to the target conference and removes the first conference terminal from the target conference according to the terminal switching request.

[0099] Optionally, the device further includes:

[0100] The first device information acquisition unit 703 is used to identify the second conference terminal and establish a data transmission link with the second conference terminal.

[0101] According to the data transmission link, a device information acquisition request is sent to the second conference terminal, and the device information of the second conference terminal is returned by the second conference terminal according to the device information acquisition request.

[0102] Optionally, the second conference terminal transmits content containing its own device information to external parties through a preset transmission method; the device further includes:

[0103] The second device information acquisition unit 704 is used to acquire content through a preset acquisition method corresponding to the preset propagation method;

[0104] If the content transmitted by any conference terminal is collected, the any conference terminal is used as the second conference terminal, and the device information contained in the collected content is used as the device information of the second conference terminal.

[0105] Optionally, the server maintains a first mapping relationship between the first conference terminal and the second conference terminal. This first mapping relationship instructs the server to: determine the device information of the first conference terminal based on the device information of the second conference terminal, so as to remove the first conference terminal from the target conference; or...

[0106] The terminal switching request also includes device information of the first conference terminal, instructing the server to remove the first conference terminal from the target conference.

[0107] Optionally, the server maintains a second mapping relationship between the first conference terminal and the target conference. The second mapping relationship is used to instruct the server to add the second conference terminal to the target conference according to the terminal switching request, and to remove the first conference terminal from the target conference.

[0108] Optionally, the terminal switching request may also include meeting information of the target meeting, which instructs the server to add the second meeting terminal to the target meeting and remove the first meeting terminal from the target meeting.

[0109] Optionally, the server is used to determine the participant identity corresponding to the logged-in account of the first conference terminal in the target conference, and synchronize the determined participant identity to the logged-in account of the second conference terminal that has joined the target conference.

[0110] Optionally, the device further includes:

[0111] The control interface display unit 705 is used to display a control interface for the second conference terminal after exiting the target conference. The control interface includes device control options for the second conference terminal and / or conference control options for the target conference.

[0112] In response to a trigger command for the device control option, a corresponding device control request is sent to the server, causing the server to forward the device control request to the second conference terminal, and causing the second conference terminal to perform the corresponding device control operation according to the device control request; and / or,

[0113] In response to the trigger command for the meeting control option, a corresponding meeting control request is sent to the server, so that the server performs the corresponding meeting control operation on the target meeting according to the meeting control request and the participant identity corresponding to the logged-in account of the second meeting terminal in the target meeting.

[0114] Optionally, the device further includes:

[0115] The meeting configuration recovery unit 706 is used to record the meeting configuration for the target meeting, the meeting configuration including the media device used by the first meeting terminal when participating in the target meeting;

[0116] Upon receiving a switching error notification from the server, the meeting configuration of the first meeting terminal for the target meeting is restored to the recorded meeting configuration.

[0117] This specification also provides an embodiment of another conference transfer device. Please refer to... Figure 8 , Figure 8 This is a schematic diagram illustrating the structure of another conference transfer device as shown in an exemplary embodiment. Figure 8 As shown, in a software implementation, the device may include:

[0118] The request receiving unit 801 is used to receive a terminal switching request sent by the first conference terminal. The terminal switching request is generated by the first conference terminal in response to a device switching instruction triggered for a target conference that the first conference terminal has joined. The terminal switching request includes device information of the second conference terminal that is the switching target.

[0119] The terminal switching unit 802 is used to add the second conference terminal to the target conference according to the terminal switching request, and to remove the first conference terminal from the target conference.

[0120] Optionally, the device further includes:

[0121] The device information acquisition unit 806 is used to acquire the device information of the first conference terminal in the following manner, so as to remove the first conference terminal from the target conference:

[0122] If the server maintains a first mapping relationship between the first conference terminal and the second conference terminal, the device information of the first conference terminal is determined based on the device information of the second conference terminal and the first mapping relationship; or,

[0123] If the terminal switching request also includes the device information of the first conference terminal, the device information of the first conference terminal is obtained from the terminal switching request.

[0124] Optionally, the server maintains a second mapping relationship between the first conference terminal and the target conference; the terminal switching unit 802 is specifically used for:

[0125] Based on the second mapping relationship and the device information of the first conference terminal and the second conference terminal in the terminal switching request, the second conference terminal is added to the target conference, and the first conference terminal is removed from the target conference.

[0126] Optionally, the terminal switching request may further include meeting information of the target meeting; the terminal switching unit 802 is specifically used for:

[0127] Based on the device information of the first conference terminal, the device information of the second conference terminal, and the conference information of the target conference in the terminal switching request, the second conference terminal is added to the target conference, and the first conference terminal is removed from the target conference.

[0128] Optionally, the device further includes:

[0129] The identity synchronization unit 803 is used to determine the identity of the participant corresponding to the logged-in account of the first conference terminal in the target conference;

[0130] The confirmed participant identities will be synchronized to the logged-in accounts of the second meeting terminal that has joined the target meeting.

[0131] Optionally, after exiting the target conference, the first conference terminal displays a control interface for the second conference terminal. The control interface includes device control options for the second conference terminal and / or conference control options for the target conference. The device further includes:

[0132] The control request processing unit 804 is configured to receive a device control request sent by the first conference terminal in response to a trigger command for the device control option, forward the device control request to the second conference terminal, and cause the second conference terminal to perform a corresponding device control operation according to the device control request; and / or,

[0133] The system receives a meeting control request sent by the first meeting terminal in response to a trigger command for the meeting control option, and performs corresponding meeting control operations on the target meeting based on the participant identity of the logged-in account of the second meeting terminal in the target meeting according to the meeting control request.

[0134] Optionally, the first conference terminal records the conference configuration for the target conference, the conference configuration including the media devices used by the first conference terminal when participating in the target conference; the apparatus further includes:

[0135] The meeting configuration recovery unit 805 is used to return a switching error notification to the first meeting terminal in the event that the terminal switching request fails, so that the first meeting terminal can restore the meeting configuration for the target meeting to the recorded meeting configuration.

[0136] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0137] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0138] The embodiments of the subject matter and functional operation described in this specification can be implemented in the following ways: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. Alternatively or additionally, the program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information and transmit it to a suitable receiving device for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or combinations thereof.

[0139] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs to perform corresponding functions by operating on input data and generating output. The processing and logic flow can also be executed by dedicated logic circuitry—such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as dedicated logic circuitry.

[0140] Computers suitable for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of processing unit. Typically, the processing unit receives instructions and data from read-only memory and / or random access memory. The basic components of a computer include a processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as disks, magneto-optical disks, or optical disks, or the computer will be operatively coupled to such mass storage devices to receive data from or transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0141] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0142] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0143] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0144] Therefore, specific embodiments of the subject matter have been described. Furthermore, the processes depicted in the figures are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0145] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A conference transfer method, applied to a first conference terminal, the method comprising: In response to a device switching instruction triggered for a target conference that the first conference terminal has joined, a terminal switching request is generated, the terminal switching request containing device information of the second conference terminal that is the target of the switching. The terminal switching request is sent to the server, so that the server adds the second conference terminal to the target conference and removes the first conference terminal from the target conference according to the terminal switching request. The server is used to determine the participant identity corresponding to the logged-in account of the first conference terminal in the target conference, and synchronize the determined participant identity to the logged-in account of the second conference terminal that has joined the target conference; the method further includes: After exiting the target meeting, a control interface for the second meeting terminal is displayed, which includes device control options for the second meeting terminal and / or meeting control options for the target meeting. In response to a trigger command for the device control option, a corresponding device control request is sent to the server, causing the server to forward the device control request to the second conference terminal, and causing the second conference terminal to execute the corresponding device control operation according to the device control request; and / or, In response to the trigger command for the meeting control option, a corresponding meeting control request is sent to the server, so that the server performs the corresponding meeting control operation on the target meeting according to the meeting control request and the participant identity corresponding to the logged-in account of the second meeting terminal in the target meeting.

2. The method according to claim 1, The method further includes: Identify the second conference terminal and establish a data transmission link with it. According to the data transmission link, a device information acquisition request is sent to the second conference terminal, and the device information of the second conference terminal is returned by the second conference terminal according to the device information acquisition request; or, The second conference terminal transmits content containing its own device information to the outside world through a preset transmission method; the method further includes: collecting content through a preset collection method corresponding to the preset transmission method; If the content transmitted by any conference terminal is collected, the any conference terminal is used as the second conference terminal, and the device information contained in the collected content is used as the device information of the second conference terminal.

3. The method according to claim 1, The server maintains a first mapping relationship between the first conference terminal and the second conference terminal. This first mapping relationship instructs the server to: determine the device information of the first conference terminal based on the device information of the second conference terminal, so as to remove the first conference terminal from the target conference; or... The terminal switching request also includes device information of the first conference terminal, instructing the server to remove the first conference terminal from the target conference.

4. The method according to claim 1, The server maintains a second mapping relationship between the first conference terminal and the target conference. This second mapping relationship instructs the server to: add the second conference terminal to the target conference according to the terminal switching request, and remove the first conference terminal from the target conference; or... The terminal switching request also includes meeting information of the target meeting, which instructs the server to add the second meeting terminal to the target meeting and remove the first meeting terminal from the target meeting.

5. The method according to claim 1, further comprising: Record the meeting configuration for the target meeting, the meeting configuration including the media device used by the first meeting terminal when participating in the target meeting; Upon receiving a switching error notification from the server, the meeting configuration of the first meeting terminal for the target meeting is restored to the recorded meeting configuration.

6. A meeting transfer method applied to a server, the method comprising: The system receives a terminal switching request sent by a first conference terminal. The terminal switching request is generated by the first conference terminal in response to a device switching instruction triggered for a target conference that the first conference terminal has joined. The terminal switching request includes device information of a second conference terminal that is the target of the switching. According to the terminal switching request, the second conference terminal is added to the target conference, and the first conference terminal is removed from the target conference; The method further includes: Determine the identity of the participant corresponding to the logged-in account of the first conference terminal in the target conference; The confirmed participant identities will be synchronized to the logged-in accounts of the second meeting terminal that has joined the target meeting; Wherein, after exiting the target conference, the first conference terminal displays a control interface for the second conference terminal, the control interface including device control options for the second conference terminal and / or conference control options for the target conference; the method further includes: The system receives a device control request sent by the first conference terminal in response to a trigger command for the device control option, forwards the device control request to the second conference terminal, and causes the second conference terminal to execute the corresponding device control operation according to the device control request; and / or, The system receives a meeting control request sent by the first meeting terminal in response to a trigger command for the meeting control option, and performs corresponding meeting control operations on the target meeting based on the participant identity of the logged-in account of the second meeting terminal in the target meeting according to the meeting control request.

7. The method according to claim 6, further comprising: The device information of the first conference terminal is obtained through the following method, so that the first conference terminal can be removed from the target conference: If the server maintains a first mapping relationship between the first conference terminal and the second conference terminal, the device information of the first conference terminal is determined based on the device information of the second conference terminal and the first mapping relationship. or, If the terminal switching request also includes device information of the first conference terminal, the device information of the first conference terminal is obtained from the terminal switching request.

8. The method according to claim 6, The server maintains a second mapping relationship between the first conference terminal and the target conference; the step of adding the second conference terminal to the target conference and removing the first conference terminal from the target conference according to the terminal switching request includes: Based on the second mapping relationship and the device information of the first and second conference terminals in the terminal switching request, the second conference terminal is added to the target conference, and the first conference terminal is removed from the target conference; or... The terminal switching request also includes the meeting information of the target meeting; the step of adding the second meeting terminal to the target meeting and removing the first meeting terminal from the target meeting according to the terminal switching request includes: adding the second meeting terminal to the target meeting and removing the first meeting terminal from the target meeting according to the device information of the first meeting terminal, the device information of the second meeting terminal and the meeting information of the target meeting in the terminal switching request.

9. A computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the steps of the method as claimed in any one of claims 1 to 8.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the steps of the method as claimed in any one of claims 1 to 8.

Images