Online conference processing method and apparatus, and electronic device and storage medium

Abstract

An online conference processing method and apparatus, and an electronic device and a storage medium. The method comprises: acquiring session account state information, wherein the session account state information comprises a user account and device information of different terminal devices used to log in to the user account (210); integrating the same user account corresponding to the different terminal devices into the same common account for display (220); and binding to the common account the device information of the different terminal devices used to log in to the same user account (230).

Description

Online meeting processing method and device, electronic equipment and storage medium

[0001] Related applications

[0002] The present application claims priority to the Chinese patent application No. 2024107184940, filed on June 4, 2024, and entitled "Online meeting processing method, device, electronic equipment and storage medium", the contents of which are hereby incorporated by reference in their entirety. TECHNICAL FIELD

[0003] The present application relates to the field of computers, in particular to an online meeting processing method, device, electronic equipment, computer readable storage medium and computer program product. BACKGROUND

[0004] Online meeting refers to a meeting conducted in a virtual space through internet technology. Compared with traditional face-to-face meetings, online meetings do not require participants to actually gather in the same place, but to communicate and collaborate in different geographical locations through network connection.

[0005] In the prior art, when an online meeting is held, a participant often accesses the same online meeting through multiple terminals for the sake of operational convenience. For example, the participant accesses the online meeting through a computer terminal to view the video of the meeting, and accesses the online meeting through a mobile terminal to listen to the audio of the meeting.

[0006] However, when a user accesses the same online meeting through multiple terminals, the participant list will display multiple different accounts online, even though the multiple different accounts are used by the same natural person. The above phenomenon will increase the degree of disorder of the meeting order, which is not conducive to the smooth progress of the online meeting. SUMMARY

[0007] The present application provides an online meeting processing method, device, electronic equipment, computer readable storage medium and computer program product.

[0008] The present application provides an online meeting processing method, which is executed by an electronic device, and the method comprises: obtaining session account state information, the session account state information comprising a user account and device information of different terminal devices logging in the user account; integrating the same user account corresponding to different terminal devices into a same common account for display; and binding the device information of different terminal devices logging in the same user account to the common account.

[0009] The present application provides an online meeting processing device, and the device comprises:

[0010] An information receiving unit is configured to acquire session account status information, the session account status information including a user account and device information of different terminal devices logged in the user account.

[0011] An account integrating unit is configured to integrate the same user account corresponding to different terminal devices into a same common account for display.

[0012] An account binding unit is configured to bind the device information of different terminal devices logged in the same user account to the common account.

[0013] An online conference processing method is executed by a first terminal device, and the method comprises the following steps.

[0014] A to-be-session list interface is displayed, the to-be-session list interface including a multi-entry control, wherein the to-be-session list interface displays a target multi-person session joined by a second terminal device through a target user account.

[0015] In response to a triggering operation on the multi-entry control, the first terminal device enters a multi-person session interface of the target multi-person session through the target user account.

[0016] Embodiments of the present application also provide an online conference processing apparatus executed by a first terminal device, and the apparatus comprises the following steps.

[0017] A list display unit is configured to display a to-be-session list interface, the to-be-session list interface including a multi-entry control, wherein the to-be-session list interface displays a target multi-person session joined by a second terminal device through a target user account.

[0018] A session display unit is configured to, in response to a triggering operation on the multi-entry control, make the first terminal device enter a multi-person session interface of the target multi-person session through the target user account.

[0019] In another aspect, the present application also provides an electronic device, which comprises a processor and a memory, the memory storing a computer program, and the processor executes the computer program to execute the steps of the method embodiments of the present application.

[0020] In another aspect, the present application also provides a computer readable storage medium, which stores executable instructions, the executable instructions being loaded by a processor and executing the steps of the method embodiments of the present application.

[0021] In another aspect, the present application also provides a computer program product, which comprises computer instructions stored in a computer readable storage medium, and the computer program is executed by a processor to perform the steps of the method embodiments of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative effort on the basis of these drawings.

[0023] FIG. 1 is a schematic diagram of an application scenario of an online meeting processing method provided by the present application;

[0024] FIG. 2 is a schematic diagram of a flow of an online meeting processing method provided by an embodiment of the present application;

[0025] FIG. 3a shows a to-be-conversed list interface applied to a mobile terminal;

[0026] FIG. 3b shows a schematic diagram of a multi-person conversation interface;

[0027] FIG. 3c shows a to-be-conversed device list interface in a specific embodiment;

[0028] FIG. 3d shows a schematic diagram of a specific embodiment of a multimedia information playing area;

[0029] FIG. 3e shows a schematic diagram in which an audio control control is opened;

[0030] FIG. 3f shows a schematic diagram of a permission reminding interface in a specific embodiment;

[0031] FIG. 3g shows a schematic diagram of a to-be-conversed member list in a specific embodiment;

[0032] FIG. 4a shows a schematic diagram of a login device prompting control in a specific embodiment;

[0033] FIG. 4b shows a schematic diagram of a login device list interface in a specific embodiment;

[0034] FIG. 4c shows a schematic diagram of a detailed status panel;

[0035] FIG. 4d shows a schematic diagram of a to-be-multi-end-joined list interface;

[0036] FIG. 5a shows a schematic diagram of a to-be-conversed list interface applied to a PC (Personal Computer) terminal;

[0037] Fig. 5b shows a schematic diagram of a pop-up interface for selecting a joining mode on a PC;

[0038] Fig. 5c shows a schematic diagram of an interface corresponding to an audio control;

[0039] Fig. 5d shows a schematic diagram of an interface corresponding to a mute control;

[0040] Fig. 5e shows a schematic diagram of an interface corresponding to an unmute control;

[0041] Fig. 5f shows a schematic diagram of a selection menu corresponding to an expansion control;

[0042] Fig. 6a shows a schematic diagram of switching an audio device in an embodiment;

[0043] Fig. 6b shows a schematic diagram of switching an audio device in another embodiment;

[0044] Fig. 7a shows a schematic diagram of switching a video device in an embodiment;

[0045] Fig. 7b shows a schematic diagram of switching a video device in another embodiment;

[0046] Fig. 8 is a timing diagram of an online conference processing method according to another embodiment of the present application;

[0047] Fig. 9 is a flowchart of an online conference processing method according to yet another embodiment of the present application;

[0048] Fig. 10 is a schematic diagram of an online conference processing apparatus according to an embodiment of the present application;

[0049] Fig. 11 is a schematic diagram of an online conference processing apparatus according to another embodiment of the present application;

[0050] Fig. 12 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0052] The embodiments of the present application provide an online conference processing method, apparatus, electronic device, computer readable storage medium and computer program product.

[0053] The online conference processing apparatus can be integrated in an electronic device, which can be a terminal, a server, or the like. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a notebook computer, a personal computer (PC), or the like. The server can be a single server or a server cluster composed of multiple servers.

[0054] In some embodiments, the online conference processing apparatus can also be integrated in multiple electronic devices, for example, the online conference processing apparatus can be integrated in multiple servers to implement the online conference processing method of the present application.

[0055] In some embodiments, the server can also be implemented in the form of a terminal.

[0056] For details, refer to FIG. 1. The method provided in the embodiments of the present application can include: obtaining session account state information, the session account state information including a user account and device information of different terminal devices logging in the user account, integrating the same user account corresponding to different terminal devices into a same common account for display, and binding the device information of different terminal devices logging in the same user account to the common account.

[0057] In the above method, the same user account corresponding to different terminal devices can be integrated into a same common account for display according to whether the user accounts are the same, and the device information of different terminal devices logging in the same user account is bound to the common account. Even if there are users participating in a multi-person session through different terminal devices, the same user account logged in by the different terminal devices can be displayed as a same common account in the online conference, which avoids the disorder of the conference order caused by the same natural person participating in the online conference through multiple different user accounts, and is conducive to the smooth progress of the target multi-person session.

[0058] It can be understood that in the embodiments of the present application, user information and other related data are involved. When the embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of related data need to comply with relevant laws, regulations, and standards of countries and regions.

[0059] The multi-person session described in the embodiments of the present application can be applied in multiple scenarios, for example, it can be an online communication group with multiple users participating, or an online conference scenario. It should be understood that the specific scenario of the multi-person session should not be understood as a limitation of the present application. For ease of description, the multi-person session is taken as an online conference scenario in the following description.

[0060] The following are described in detail, respectively. It should be noted that the serial numbers of the following embodiments do not limit the preferred order of the embodiments.

[0061] In this embodiment, an online conference processing method is provided. As shown in FIG. 2, the online conference processing method is applied to an electronic device, and the specific flow of the method includes:

[0062] In step 210, session account status information is obtained, which includes a user account and device information of different terminal devices that log in to the user account.

[0063] The session account status information can be one or more. When there are multiple pieces of session account status information, each piece of session account status information includes a user account and device information of different terminal devices that log in to the user account.

[0064] The electronic device can obtain the session account status information. The electronic device can be a terminal device or a server. The server can send the session account status information to the terminal device, or multiple terminal devices can send the session account status information to the server.

[0065] The terminal device can be a mobile terminal or a PC terminal. As shown in FIGS. 3a to 3g and FIGS. 4a to 4d, related interface diagrams of the online conference processing method executed on a mobile terminal are provided. As shown in FIGS. 5a to 5f, related interface diagrams of the online conference processing method executed on a PC terminal are provided.

[0066] In one embodiment, for ease of description, the terminal device that executes steps 210 to 230 is referred to as a first terminal device, so as to be distinguished from a second terminal device in the following. Regarding the second terminal device, detailed description will be provided below.

[0067] The device information of the terminal device is information that reflects the uniqueness of the terminal device. Optionally, it can be an identity of the terminal device.

[0068] The session member list is used to display all users participating in the current target multi-person session. For details, please refer to FIG. 3g. It is assumed that the first terminal device is a terminal device that receives, the target user account logged in by the session application program of the first terminal device is the account of user A, and user B participates in the session through multiple devices.

[0069] The first terminal device can receive the session account status information sent by the server, which includes a user account and identities of different terminal devices that log in to the user account. For example, the server sends five pieces of session account status information, which are as follows:

[0070] Session account state information 1, including the account of user B, the identity of the terminal device B1;

[0071] Session account state information 2, including the account of user C, the identity of the terminal device c;

[0072] Session account state information 3, including the account of user B, the identity of the terminal device B3;

[0073] Session account state information 4, including the account of user D, the identity of the terminal device ddd;

[0074] Session account state information 5, including the account of user B, the identity of the terminal device B2.

[0075] Step 220, integrating the same user account corresponding to different terminal devices into the same common account for display.

[0076] The common account is the same account displayed to other users participating in the target multi-person session corresponding to the target user account. The common account can be the target user account itself, or a temporarily created account. The specific form of the common account should not be understood as a limitation on the present application. The avatar and nickname of the common account can come from the original avatar and nickname of the target user account.

[0077] The first terminal device can integrate the same user account logged in by different terminal devices into the same common account based on the user account in the session account state information.

[0078] Step 230, binding the device information of different terminal devices logging into the same user account to the common account.

[0079] The identity of each of the plurality of different terminal devices logging into the same user account is bound to the same common account.

[0080] Optionally, the same user account can be directly used as the common account, and the identity of different terminal devices logging into the same user account is bound to the user account. A new account can also be temporarily created, for example, the created account is denoted as account x, and the identity of different terminal devices logging into the same user account is bound to the account x.

[0081] Continuing the above example, in an embodiment, the first terminal device can directly use the account of user B as the common account, and bind the identities of different terminal devices B1, B2, and B3 to the account of user B. In another embodiment, the first terminal device can also temporarily create an account Bx, and bind the identities of different terminal devices B1, B2, and B3 to the account Bx.

[0082] In one embodiment, the first terminal device can also delete the temporarily created account Bx at the end of the target multi-person session.

[0083] In one embodiment, the electronic device includes a first terminal device, and the method further includes: displaying the common account and the un-integrated user accounts.

[0084] The un-integrated user accounts are user accounts that do not participate in the multi-person session through multiple terminal devices. By displaying the common account and the un-integrated user accounts, even if there are users participating in the multi-person session through different terminal devices, the same user account logged in through different terminal devices is displayed as a common account on the user interface, avoiding the disorderly situation of the online meeting caused by the same natural person participating in the online meeting through multiple different user accounts, and facilitating the smooth progress of the target multi-person session.

[0085] Optionally, in one embodiment, in addition to displaying the common account, a multi-device session identifier corresponding to the common account can also be displayed. The multi-device session identifier is used to represent that the corresponding user participates in the current target multi-person session through multiple terminal devices.

[0086] In one embodiment, the common account and the un-integrated user accounts can be displayed in the member session list. For details, please refer to FIG. 3g. As shown in FIG. 3g, the user A (i.e., the user corresponding to the first terminal device) and the user B participating in the multi-terminal device session both correspond to a multi-device session identifier in the session member list, while the user C and the user D do not correspond to a multi-device session identifier.

[0087] In one embodiment, the online meeting processing method is executed by the first terminal device, and the method includes: receiving session account state information sent by the server, wherein each piece of session account state information includes a user account and device information of different terminal devices logging in the user account; integrating the same user account corresponding to different terminal devices into the same common account for display, and binding the device information of different terminal devices logging in the same user account to the common account; and displaying the common account and the un-integrated user accounts.

[0088] In one embodiment, the online meeting processing method is executed by the server, and the method includes: receiving session account state information sent by different terminal devices, wherein each piece of session account state information includes a user account and device information of different terminal devices logging in the user account; integrating the same user account corresponding to different terminal devices into the same common account for display, and binding the device information of different terminal devices logging in the same user account to the common account.

[0089] In one of the embodiments, the method further comprises: sending the common account and the un-integrated user accounts to different terminal devices, so that each terminal device displays the common account and the un-integrated user accounts.

[0090] In the above-mentioned embodiments, the session account state information can be acquired, and based on the user accounts in each piece of session account state information, the same user accounts corresponding to different terminal devices are integrated into the same common account, and the device information of different terminal devices logged in the same user accounts is bound to the same common account, and the common account and the un-integrated user accounts are displayed, so that the users participating in the target multi-person session through different terminal devices are displayed as only one account in the user list of other users, and the situation of user list confusion can be avoided, the mutual recognition between users is facilitated, and the order of the target multi-person session is better maintained.

[0091] In one of the embodiments, the electronic device comprises a first terminal device, and the specific process of the method can comprise the following steps 101 to 103:

[0092] 101. Display a to-be-session list interface.

[0093] In one of the embodiments, the first terminal device is installed with a session application program, and the target user account is logged in the session application program. The first terminal device can display the to-be-session list interface of the session application program.

[0094] The to-be-session list interface can be directly displayed on the display screen of the first terminal device. Alternatively, the to-be-session list interface of the session application program can be displayed in response to a trigger operation for the session application program.

[0095] The session application program is an application program for holding a multi-person session. The trigger operation for the session application program is triggered by a user using the first terminal device, and the trigger operation is used to start the session application program. Alternatively, the trigger operation can comprise that the user clicks the session application program on the display screen through an input device or an extremity end; or the user clicks a meeting hyperlink to jump through an input device or an extremity end. It should be understood that the specific operation content of the trigger operation should not be understood as a limitation to the present application. The above-mentioned input device can be a mouse, a keyboard, a touchpad, etc.; and the above-mentioned extremity end can be a finger, a toe, etc. The session application program can specifically be an application program for holding an online meeting.

[0096] The to-be-session list interface is used to display a list of target multi-person sessions to be attended by the user. For details, please refer to FIG. 3a and FIG. 5a. FIG. 3a shows a to-be-session list interface applied to a mobile terminal; and FIG. 5a shows a to-be-session list interface applied to a personal computer (PC). For ease of description, the to-be-session list interface shown in FIG. 3a will be taken as an example for description in the following.

[0097] The user can view, from the to-be-session list interface, a target multi-person session being held, such as “zz meeting” shown in FIG. 3a; or a target multi-person session to be held in a future period of time and the corresponding holding time, such as “aa meeting” and the holding time “June 13, 14:30-16:00”, “bb meeting” and the holding time “June 16, 15:00-17:00” shown in FIG. 3a.

[0098] Optionally, in an embodiment, the to-be-session list interface displays a login device prompt control. The embodiment of the present application can further include the following steps S1 to S3:

[0099] S1, in response to a triggering operation on the login device prompt control, a login device list interface is displayed.

[0100] The login device prompt control is used to prompt the user that a terminal device on which the session application is installed and the session application is logged in the target user account. For example, for details, please refer to FIG. 3a. “1 device has joined zz meeting” shown in FIG. 3a is a login device prompt control in a specific embodiment, for details, please refer to C01 in FIG. 3a. For details, please refer to FIG. 4a. “3 devices have joined x…etc. 2 meetings” shown in FIG. 4a is a login device prompt control in another specific embodiment, for details, please refer to C01 in FIG. 4a. For ease of description, the login device prompt control will be taken as “3 devices have joined x…etc. 2 meetings” shown in FIG. 4a as an example for description in the following.

[0101] When there are multiple meetings being held simultaneously, the triggering of the multi-terminal joining C02 can include, but is not limited to, the following two cases. Taking the existence of x meeting and y meeting being held simultaneously shown in FIG. 4a as an example, the description is as follows:

[0102] In an embodiment, when the multi-entry control: multi-entry C02 is triggered, a "multi-entry list" interface can be popped up, please refer to FIG. 4d. The interface displays the ongoing conferences: x conference and y conference, and the "enter conference>" control corresponding to the x conference and the "enter conference>" control corresponding to the y conference. The user can select the conference that the current device joins by triggering the "enter conference>" control. For example, if the user taps the "enter conference>" control corresponding to the x conference, the current device joins the x conference.

[0103] In another embodiment, when the multi-entry control: multi-entry C02 is triggered, the first conference in the list of ongoing conferences can be joined by default. Please refer to FIG. 4a. In the list of ongoing conferences: x conference and y conference, the first conference is the x conference, and the x conference can be joined by default.

[0104] Optionally, please refer to FIG. 4a, the control for multi-device participation can also include a multi-entry special control: "multi-entry available>" C11. The x conference and the y conference each have a multi-entry special control corresponding thereto. As shown in FIG. 4a, if the user wants to join the x conference, the user can tap the "multi-entry available>" C11 corresponding to the x conference to enter the x conference; if the user wants to join the y conference, the user can tap the "multi-entry available>" C11 corresponding to the y conference to enter the y conference.

[0105] Please refer to FIG. 4a, the x conference and the y conference each have a switching control: "switch" C03. If the "switch" C03 corresponding to the x conference is tapped by the user, the server controls the two devices that have previously joined the x conference to exit the conference, and the current device operated by the user joins the x conference; if the "switch" C03 corresponding to the y conference is tapped by the user, the server controls the one device that has previously joined the y conference to exit the conference, and the current device operated by the user joins the y conference.

[0106] The trigger operation for the login device prompt control can be consistent with the trigger operation for the conference application, which will not be described herein.

[0107] The login device list interface is used to display the state information of the logged-in devices. The logged-in devices each have installed the conference application, and the conference applications each log in the target user account. Please refer to FIG. 4b, which shows the login device list interface in an embodiment. In FIG. 4b, four logged-in devices: device B1, device B2, device B3, and device B4 are shown, and the current state information of each logged-in device is shown: device B1 joins the x conference; device B2 joins the x conference; device B3 joins the y conference; and device B4 has not joined a conference and is in the state that the target user account is logged in.

[0108] S2, in response to a triggering operation on a device detail control corresponding to the target logged-in device, display a detailed state panel of the target logged-in device.

[0109] The target logged-in device is any logged-in device that joins a preset session group in all logged-in devices. The preset session group is any target multi-person session. Continuing the example above, assume that device B1 is the target logged-in device, and accordingly, the preset session group is the x meeting that device B1 joins.

[0110] The login device list interface includes device detail controls. The number of device detail controls is the same as the number of logged-in devices, and each device detail control corresponds to one logged-in device. After a device detail control is triggered by a user, a detailed state of the corresponding logged-in device can be displayed. For details, see FIG. 4b. In the login device list interface, each logged-in device option has a drop-down control representing expansion on the right side. The drop-down control can be the device detail control described above.

[0111] The triggering operation on the device detail control can be the same as the triggering operation mentioned above, and thus will not be described again. When a user triggers a device detail control through a triggering operation, a detailed state panel of the target logged-in device can be displayed.

[0112] The detailed state panel is used to display the session name of the target logged-in device. The detailed state panel can be provided with a switching control representing switching of devices participating in a session, and a multi-device entry control representing allowing multiple devices to participate in a session. For example, continuing the example above, when the device detail control (i.e., the drop-down control C04 shown in FIG. 4b) corresponding to device B1 is triggered by the user corresponding to the target user account, the detailed state panel corresponding to device B1 can be expanded. For details, see FIG. 4c. After the detailed state panel is expanded, the device detail control can be changed from the drop-down control C04 to the pull-up control C05. The detailed state panel can include the switching control C03 "Switch" and the multi-device entry control C02 "Multi-device entry". The specific functions of the two will be described in detail below.

[0113] S3, in response to a triggering operation on the switching control, send a session device switching instruction to the server. The session device switching instruction is used to instruct the server to control the target user account logged in the first terminal device to join the preset session group, and control the target user account logged in the target logged-in device to exit the preset session group.

[0114] The trigger operation for the switching control can be consistent with the trigger operation described above, and thus will not be repeated here. When the user triggers the switching control through the trigger operation, the first terminal device can send a switching session device instruction to the server. The switching session device instruction is used to instruct the switching of the session device.

[0115] After receiving the switching session device instruction, the server can control the target user account logged in the first terminal device to join the preset session group, and control the target user account logged in the target logged-in device to exit the preset session group, so as to switch the device participating in the preset session group from the target logged-in device to the first terminal device. For example, continuing the example above, when the target user account corresponding user clicks the "switch" control shown in FIG. 4c, the first terminal device sends a switching session device instruction to the server, and the server controls the current device (i.e., the first terminal device) to join the x conference and controls the device B1 to exit the x conference.

[0116] In this embodiment, the login device prompt control is used to real-time display the multi-device login state under the same account, which can support the user to view the specific session information of each terminal through the device detail interface, and when the user needs to switch the participating device, the switching control can be triggered directly in the detailed state panel to automatically add the new device to the conference and automatically exit the original device, which can realize the visual monitoring of the multi-device state and the seamless session transfer. In this way, the single-account multi-terminal exclusive participation ensures the uniqueness of the conference audio and video resources, provides flexible device switching capability, effectively solves the conference relay demand in the multi-device scenario, and significantly improves the cross-terminal collaboration efficiency.

[0117] In one embodiment, the detailed state panel further displays a multi-terminal entry control representing that the multi-device is allowed to participate in the session; and the method further includes: in response to a trigger operation for the multi-terminal entry control, sending a multi-terminal session instruction to the server, so that the server controls the target user account logged in the first terminal device to join the preset session group.

[0118] The trigger operation for the multi-terminal entry control can be consistent with the trigger operation described above, and thus will not be repeated here. When the user triggers the multi-terminal entry control through the trigger operation, the first terminal device can send a multi-terminal session instruction to the server. The multi-terminal session instruction is used to instruct the current device (i.e., the first terminal device) to join the target multi-person session.

[0119] After receiving the multi-terminal session instruction, the server can control the target user account logged in the first terminal device to join the preset session group, and maintain the terminal devices originally participating in the preset session group in the participating session state. For example, continuing the example above, when the user corresponding to the target user account clicks the "multi-terminal join" control shown in FIG. 4c, the first terminal device sends a multi-terminal session instruction to the server, and the server controls the current device (i.e., the first terminal device) to join the x conference, and maintains the terminal devices (such as device B1 and device B2) originally participating in the x conference in the participating session state.

[0120] In this embodiment, by adding a multi-terminal join control to the device detailed state panel, the user can autonomously select whether to enable the multi-device parallel participation mode. When the control is triggered, the new device can be allowed to join the conference with the same account while maintaining the online state of the original participating device, realizing single-account multi-terminal collaborative participation. Moreover, flexible switching of participation modes and autonomous selection and configuration of devices can be realized, which not only retains the resource exclusivity of the traditional single-device participation mode, but also provides scene adaptation capabilities for multi-device collaboration, effectively meeting the differentiated needs of users for conference terminal devices in different office scenarios, and significantly improving the flexibility of conference access in complex environments.

[0121] In the above embodiment, when the user enters the session list interface, the user can learn the states of the multiple devices logged in with the target user account through the login device prompt control, and the user can view the detailed state of each device in the login device list interface, and perform the switching device join or multi-terminal join operation on the device currently participating in the multi-person session, which is beneficial to the user to intuitively and conveniently manage multiple terminal devices logged in with the same user account.

[0122] 102, in response to the control display instruction, a multi-terminal join control is displayed on the session list interface, and the control display instruction indicates that the second terminal device joins the target multi-person session with the target user account.

[0123] The control display instruction is used to control the first terminal device to display the multi-terminal join control on the session list interface. The control display instruction can be sent by the server to the first terminal device. Specifically, when the server detects that the target user account joins the target multi-person session through a terminal device other than the first terminal device (for example, the second terminal device), the server sends the control display instruction to the first terminal device.

[0124] Alternatively, the multi-terminal join control can be a "multi-terminal join" virtual control C02 and a "multi-terminal joinable" virtual control C11 as shown in FIG. 3a.

[0125] The second terminal device is another terminal device different from the first terminal device. The number of the second terminal devices can be one or multiple. It should be understood that the number of the second terminal devices should not be construed as a limitation to the present application.

[0126] The multi-entry control is displayed in the session list interface of the first terminal device because the target user account has joined the target multi-person session through the session application installed on the second terminal device. For example, FIG. 3a shows that when the user logs in the session application of the first terminal device with the target user account, the existing device has joined a multi-person session: “1 device has joined zz meeting”, so the multi-entry control: the “multi-entry” virtual control C02 and the “can multi-entry >” virtual control C11 can appear in the session list interface. If the user does not participate in the target multi-person session through other terminal devices during the period of logging in the session application of the first terminal device with the target user account, the multi-entry control can not be displayed in the session list interface.

[0127] Optionally, before step 102, the target multi-person session recorded in step 102 can be set by a user with an administrator identity through an administrator terminal device to allow multiple devices to participate in the session. The administrator terminal device is a terminal device corresponding to the user with the administrator identity, i.e., a terminal device logged in by the user account managing the target multi-person session. Assuming that the administrator terminal device sets a multi-person session (not necessarily set as multi-person session e) to prohibit multiple devices from participating in the session, each user account in the multi-person session e is allowed to have only one device session. The administrator terminal device can be the first terminal device or the second terminal device, or other terminal devices except the two. The specific identity of the administrator terminal device should not be construed as a limitation to the present application. If the administrator terminal device sends a request to the server to remove the target user account from the current target multi-person session, the server can remove the multiple terminal devices corresponding to the target user account from the current target multi-person session after receiving the request and verifying that the administrator terminal device has the above removal authority. If the administrator terminal device sends a request to the server to mute the target user account, the server can find the terminal device with the microphone turned on from the multiple terminal devices corresponding to the target user account after receiving the request and verifying that the administrator terminal device has the above mute authority, and then turn off the microphone of the terminal device.

[0128] Optionally, please refer to FIG. 5a, in an embodiment, the user can also click the "Join Meeting" control shown in FIG. 5a, and input the conference number of the target multi-person session in the pop-up conference number search box (not shown in the figure), so as to display the pop-up window interface shown in FIG. 5b, in which the user can determine the participation mode of the first terminal device by clicking different virtual controls. Specifically, the user can click the "Not to join" control to select that the first terminal device does not participate in the target multi-person session; the user can also click the "Add current device to join the meeting" control to select the participation mode of the multi-terminal device in the session; and the user can also click the "Switch to current device to join the meeting" control to select that only the first terminal device participates in the session and the second terminal device stops participating in the session.

[0129] Optionally, please refer to FIG. 5c, in an embodiment, the user can also click the "Select Audio" control C06 shown in FIG. 5c to use computer audio. Please refer to FIG. 5d, when using computer audio, the original "Select Audio" control C06 becomes the "Mute" control C07, at this time the user can listen to the speech of other users in the meeting using computer audio, and can also speak in the meeting. The user can also click the expansion control C09 corresponding to the "Mute" control C07, so as to perform corresponding operations in the pop-up menu.

[0130] Please refer to FIG. 5f, which shows the selection menu C10 popped up after the expansion control C09 is clicked. In the selection menu C10:

[0131] Under the "Select Speaker" module, there are multiple speaker options that can be selected: speaker 1, speaker 2, and the system default option: speaker 1. The user can click the options under the "Select Speaker" module, and after clicking the selected speaker option, the user can listen to the speech of other users in the meeting using the selected speaker, and the right side of the selected speaker option displays a symbol: √ (not shown in the figure).

[0132] Under the "Select Microphone" module, there is one microphone option that can be selected: microphone 1, and the system default option: microphone 1. The user can click the options under the "Select Microphone" module, and after clicking the selected microphone option, the user can speak in the meeting using the selected microphone, and the right side of the selected microphone option displays a symbol: √ (not shown in the figure).

[0133] If the user clicks the "Disable computer audio" option, the interface shown in FIG. 5c is displayed.

[0134] If the user clicks the "Play prompt sound when microphone is on" option, a symbol: √ (not shown in the figure) can be displayed at the right side of the "Play prompt sound when microphone is on" option, indicating that a prompt sound will be played when the microphone is turned on to remind the user.

[0135] The user can also click the "sound effect setting" option to make more audio-related settings for the audio of the conference (not shown in the figure).

[0136] If the user clicks the "mute" control C07 shown in Figure 5d, the interface shown in Figure 5e is displayed, in which the user can listen to the speech of other users in the conference using the computer audio, but cannot speak in the conference.

[0137] If the user clicks the "unmute" control C08 shown in Figure 5e, the interface shown in Figure 5d is displayed, in which the user can listen to the speech of other users in the conference using the computer audio, and can also speak in the conference.

[0138] Optionally, in an embodiment, the multi-entry control included in the upcoming session list interface can be a function opened to the user due to the preset condition of the session application. The preset condition can be set by the developer based on the needs of the development work. For example, the preset condition can be that the software version of the session application reaches the latest version, or that the target user account logged into the session application opens the corresponding paid function, etc. It should be understood that the specific condition type of the preset condition should not be understood as a limitation of the present application.

[0139] 103、In response to the triggering operation on the multi-entry control, the first terminal device joins the target multi-person session through the target user account.

[0140] The triggering operation on the multi-entry control can be achieved by the user clicking the "multi-entry" control or the "multi-entry available" control shown in Figure 3a using an input device or a limb end. The input device can be a mouse, a keyboard, a touchpad, etc.; the limb end can be a finger, a toe, etc.

[0141] When the first terminal device joins the target multi-person session, a multi-person session interface of the target multi-person session is displayed on the display screen of the first terminal device. The multi-person session interface is the user interface of the session application holding the target multi-person session. Optionally, the multi-person session interface can be the interface shown in Figure 3b. The user corresponding to the target user account can intuitively view the name of the current multi-person session, such as "zz conference" shown in Figure 3b; the duration of the current multi-person session, such as "00:15" shown in Figure 3b; the number of devices participating in the current multi-person session, such as "2 devices have entered the conference" shown in Figure 3b; the multimedia information upload status of the first terminal device, such as the mute icon and the camera off icon shown at the bottom of Figure 3b.

[0142] Optionally, when the first terminal device successfully participates in the target multi-person session, the server can send a session device update message to each of the plurality of terminal devices logged in the same user account (i.e., the target user account). The terminal device receiving the session device update message updates the number of devices shown by the session device prompt control. For example, referring to FIGS. 3a and 3b, when the first terminal device has not yet participated in the target multi-person session, FIG. 3a shows that “1 device has joined the zz meeting” through the login device prompt control; when the first terminal device also successfully joins the target multi-person session, FIG. 3b shows that “2 devices have joined the meeting” through the session device prompt control. It should be understood that the multi-person session interface of the second terminal device can also update the number of devices shown by the session device prompt control.

[0143] In the embodiment, when the user joins the meeting through the second terminal device with the target account, a multi-terminal join control is automatically generated in the session list interface of the first terminal device. The user can quickly join the meeting with the same account through the current device by clicking the control, realizing real-time synchronization of cross-terminal meeting status and one-key multi-device join switching. In addition, the multi-terminal parallel participation capability of the same account is realized, which not only avoids repeated login operations, but also maintains the independent audio and video control of each terminal, significantly improving the meeting access efficiency and use experience in the multi-device collaborative office scenario.

[0144] Optionally, in an embodiment, the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface includes a multimedia information playing area. The method can further include steps A1 to A3 as follows:

[0145] A1, receiving the video information sent by the server, and displaying the video information in the multimedia information playing area.

[0146] The multimedia information playing area is used to play all or part of the multimedia information sent by the server. The multimedia information includes text, pictures, audio, video, etc. Specifically, the multimedia information playing area can be used to play video information. Specifically, FIG. 3d shows one specific embodiment of the multimedia information playing area. The first terminal device can receive the video information sent by the server and play the video information in the multimedia information playing area as shown in FIG. 3d.

[0147] A2, in response to an audio receiving trigger operation representing receiving audio information, sending an audio receiving request to the server. The audio receiving request is used to instruct the server to return the audio information and stop sending the audio information to the session application installed in the second terminal device.

[0148] The multi-person session interface can further include an audio control. Specifically, the user can press the audio control with an input device or an end of a limb to trigger an audio receiving operation. Alternatively, as shown in FIG. 3d and FIG. 3e, both of which show the audio control in an embodiment, FIG. 3d shows the audio control when no audio information is received, and FIG. 3e shows the audio control when audio information is received. Specifically, the audio control shown in FIG. 3d can change to the display state of the audio control shown in FIG. 3e in response to the audio receiving operation. It should be understood that the audio control shown in FIG. 3d and FIG. 3e is only an example, and the audio control can also be in other forms, such as text buttons: "mute state" and "non-mute state", and the specific form of the audio control should not be understood as a limitation of the present application.

[0149] When the user performs the audio receiving operation on the first terminal device, a corresponding audio receiving request is generated, and the first terminal device sends the audio receiving request to the server. The server can return audio information to the first terminal device based on the received audio receiving request, and stop sending audio information to the session application of the second terminal device.

[0150] A3, receiving the audio information returned by the server and playing the audio information.

[0151] The first terminal device receives and plays the audio information returned by the server.

[0152] In the above embodiment, if the first terminal device joins a multi-person session in a multi-device participation session mode, the server can default to push video information of the multi-person session to the first terminal device, and temporarily not push audio information of the multi-person session. When the first terminal device receives the audio receiving operation triggered by the user, the server pushes the audio information of the multi-person session to the first terminal device, and stops pushing the audio information to the second terminal device (i.e., other terminal devices except the first terminal device). The above process can ensure that when multiple terminal devices participate in a session, only one terminal device receives the audio information of the multi-person session, which can effectively avoid the situation that multiple terminal devices play the audio information at the same time, causing noise, and is conducive to the accurate and convenient reception of the conference content by the session participants.

[0153] Alternatively, when multiple terminal devices participate in the same multi-person session at the same time, the steps of collecting and uploading local multimedia information can always be performed by one terminal device, even if the terminal device performing the above steps is switched. The collection and uploading process of local multimedia information will be described in detail below in conjunction with steps B1 to B2.

[0154] Optionally, in an embodiment, the multi-person session interface comprises a multimedia uplink control. Accordingly, after step 102, the embodiments of the present application can further comprise steps B1 to B2 as follows:

[0155] B1, in response to a triggering operation on the multimedia uplink control, collecting local multimedia information by a multimedia collection tool provided in the first terminal device.

[0156] The multimedia uplink control is used to realize the collection and transmission of multimedia information. Optionally, in an embodiment, the multimedia uplink control can be the "unmute", "start video", and "share screen" virtual controls in the multi-person session interface, as shown in FIGS. 3b, 3c, and 3d.

[0157] The triggering operation on the multimedia uplink control can be consistent with the triggering operation described above, which will not be repeated here.

[0158] The multimedia collection tool is a tool for collecting locally generated multimedia information. The multimedia collection tool can be hardware or software. Different multimedia uplink controls have their own corresponding multimedia collection tools. Continuing the above example, the multimedia collection tool corresponding to the "unmute" virtual control can be a microphone, the multimedia collection tool corresponding to the "start video" virtual control can be a camera, and the multimedia collection tool corresponding to the "share screen" virtual control can be an application programming interface (API).

[0159] The local multimedia information refers to multimedia information collected by the local device (i.e., the first terminal device) through a non-networking manner, such as the sound emitted by the user participating in the target multi-person session collected by the microphone, or the video screen that the user wants to show to other users participating in the target multi-person session. The video screen can be the facial information of the user captured by the camera, or the screen of the display corresponding to the first terminal device of the user, which can be invoked through the API of the operating system of the first terminal device.

[0160] B2, sending the local multimedia information to the server, so that the server transmits the local multimedia information to other users participating in the target multi-person session, and disconnects the multimedia collection tool of the second terminal device.

[0161] The first terminal device sends the local multimedia information to the server, and the server receives the local multimedia information sent by the first terminal device and transmits it to other users participating in the target multi-person session. The server disconnects the multimedia collection tool of the second terminal device while transmitting the local multimedia information sent by the first terminal device to other users.

[0162] In one embodiment, taking the local multimedia information as audio as an example, as shown in FIG. 6a, when the user clicks the "unmute" virtual control, the multi-person conversation interface pops up a prompt information "switch to the current device audio, and the audio of other devices is disconnected". Meanwhile, the first terminal device starts the microphone to collect the audio of the user, and sends the collected audio to the server. The server receives the audio sent by the first terminal device, and controls the microphone of the second terminal device (i.e. the other device in the prompt information) to be disconnected.

[0163] Similarly, if the user clicks the "unmute" virtual control on the multi-person conversation interface displayed by the second terminal device, the server can also control the microphone of the first terminal device to be disconnected, and pops up a prompt information "switch to the audio of another device, and the audio of the current device is disconnected" on the multi-person conversation interface of the first terminal device, as shown in FIG. 6b.

[0164] In another embodiment, taking the local multimedia information as video as an example, as shown in FIG. 7a, when the user clicks the "start video" virtual control, the multi-person conversation interface pops up a prompt information "switch to the video of the current device, and the video of other devices is disconnected". Meanwhile, the first terminal device starts the camera to collect the video (such as the face) of the user, and sends the collected video to the server. The server receives the video sent by the first terminal device, and controls the camera of the second terminal device (i.e. the other device in the prompt information) to be disconnected.

[0165] Similarly, if the user clicks the "start video" virtual control on the multi-person conversation interface displayed by the second terminal device, the server can also control the camera of the first terminal device to be disconnected, and pops up a prompt information "switch to the video of another device, and the video of the current device is disconnected" on the multi-person conversation interface of the first terminal device, as shown in FIG. 7b.

[0166] Specifically, in the above two embodiments, after the user clicks the "unmute" or "start video" virtual control, the conversation application can first detect whether the hardware device (i.e. the microphone or the camera) of the first terminal device is available. If it is detected that the hardware device is not available, a prompt information can be popped up to remind the user to check the hardware device. If it is detected that the hardware device is available, it is further detected whether the conversation application has the permission to start the hardware device (i.e. the microphone or the camera), and when it is detected that the conversation application has the above permission, the starting of the hardware device (i.e. the microphone or the camera) is completed.

[0167] In the above two embodiments, the terminal device starting the microphone and the terminal device starting the camera can be different terminal devices. The user can click the "unmute" control on the first terminal device, collect the voice of his own session, and share it with other users participating in the target multi-person session. At the same time, the "start video" control can be clicked on the second terminal device to collect the facial information of his own session and share it with other users participating in the target multi-person session; or the "share screen" control can be clicked on the second terminal device to share the screen of the second terminal device in the form of a video stream with other users participating in the target multi-person session.

[0168] Optionally, when the user clicks the "share screen" virtual control on the session application of the first terminal device, the first terminal device can first send a permission acquisition request to the server, and the permission acquisition request is used to request a permission token. After the server authenticates the permission acquisition request, the server returns the permission token to the first terminal device. Subsequently, the first terminal device sends a request to start sharing the screen to the server, and the request to start sharing the screen carries the permission token. Based on the permission token, the server grants the first terminal device to share the screen, so as to share the screen of the first terminal device to other users participating in the target multi-person session, and close the screen sharing of other users.

[0169] Optionally, the terminal device participating in the target multi-person session can periodically acquire the real upload state of its own multimedia information, and compare the real upload state of the multimedia information with the permitted upload state of the multimedia information returned by the server. If the two are inconsistent, the real upload state of the terminal device is changed. For example, if the real upload state of terminal device H is to start screen sharing, and the permitted upload state returned by the server is that terminal device H is not allowed to perform screen sharing, terminal device H will change the real upload state from starting screen sharing to closing screen sharing after comparing the two.

[0170] Optionally, when the first terminal device of the target user account accesses the target multi-person session, the multimedia upload state corresponding to the target user account can be set according to the pre-set information of the target user account about multimedia upload. For example, if the user pre-selects "adjust to mute when entering the session" and "adjust to close the camera when entering the session" in the setting menu corresponding to the target user account, when the first terminal device of the target user account accesses the target multi-person session, the session application will automatically adjust the entering state to "mute state" and "close camera state".

[0171] In the above-mentioned embodiments, when the first terminal device receives a trigger operation for the multimedia uplink control, the multimedia collection tool is started to collect local multimedia information, and the local multimedia information is sent to the server. The server receives the local multimedia information sent by the first terminal device, and transmits the local multimedia information to other users participating in the target multi-person session, while the server stops collecting local multimedia information from the second terminal device (i.e., other terminal devices except the first terminal device). The above-mentioned process can ensure that one terminal device always collects local multimedia information and uploads it to the server during the multi-terminal device session, which can effectively avoid the situation of information redundancy caused by multiple terminal devices collecting local multimedia information at the same time.

[0172] Optionally, in an embodiment, the multi-person session interface displays a session device prompt control. The method can further include the following steps C1 to C3:

[0173] C1, in response to a trigger operation on the session device prompt control, a session device list interface is displayed.

[0174] The session device prompt control is used to prompt the number of terminal devices participating in the current multi-person session in the multi-person session interface. For details, please refer to "2 devices have joined the session" shown in FIG. 3b. The trigger operation on the session device prompt control can be consistent with the trigger operation described above, and thus will not be described here.

[0175] The session device list interface is used to display device information of all terminal devices participating in the target multi-person session. The device information can include device name, device model, multimedia uplink state of the device, etc. The multimedia uplink state can specifically refer to whether the microphone is turned on, whether the camera is turned on, etc.

[0176] For details, please refer to FIG. 3c, which shows a session device list interface in a specific embodiment. The session list interface includes two devices: device A1 and device A2. Among them, the multimedia uplink state of device A1 is to turn on the microphone and not to turn on the camera; the multimedia uplink state of device A2 is not to turn on the microphone and not to turn on the camera. Users participating in the target multi-person session can intuitively and quickly know from the session device list interface that the switch states of the microphones and cameras of the two devices participating in the target multi-person session: device A1 and device A2. It should be understood that the device model information is not shown in the session device list interface shown in FIG. 3c, and in other embodiments, the device model information can also be displayed on the right side of the device name.

[0177] C2, in response to a trigger operation on the target terminal device, a permission reminder interface is popped up, and the permission reminder interface displays a refuse session control.

[0178] The target terminal device is any one of all the terminal devices participating in the target multi-person session. The permission prompt interface is used to inquire whether the target terminal device is allowed to continue participating in the target multi-person session. Taking the example above as a continuation, it is assumed that the target terminal device is device A2 shown in FIG. 3c, and details can be referred to FIG. 3f. The permission prompt interface can be in the form of a pop-up window as shown in FIG. 3f. The session permission prompt pop-up window is used to inquire the user: whether device A2 is allowed to continue participating in the current target multi-person session. The "confirm" control in the pop-up window is an allow session control, and the "cancel" control in the pop-up window is a reject session control.

[0179] C3. In response to the trigger operation on the reject session control, a reject session instruction is sent to the server, so that the server controls the target user account logged in the target terminal device to exit the target multi-person session.

[0180] The reject session instruction is used to instruct the server to control the target user account logged in the target terminal device to exit the target multi-person session.

[0181] The trigger operation on the reject session control is consistent with the trigger operation mentioned above, and thus will not be described here. When the reject session control is triggered, the first terminal device packages the information representing rejection and the identity of the target terminal device in the reject session instruction, and sends the reject session instruction to the server. After the server receives the reject session instruction and authenticates, the target user account of the target terminal device can be controlled to exit the current target multi-person session according to the identity of the target terminal device in the reject session instruction. Moreover, the server can modify the session state of the target terminal device to non-session. After the target terminal device exits the target multi-person session, it can return to the waiting session list interface shown in FIG. 3a.

[0182] In the above embodiment, the user can view all the terminal devices participating in the current target multi-person session through the session device prompt control included in the multi-person session interface, and select any one of the terminal devices to decide whether the selected terminal device is allowed to continue participating in the current target multi-person session. This embodiment enables the user to quickly and conveniently determine the number of terminal devices participating in the same target multi-person session, thereby improving the management efficiency of the terminal devices.

[0183] In one of the embodiments, steps C1 to C3 can only occur in the user's mobile terminal device. Since the mobile terminal device is usually carried by the user, the security factor is higher, and the possibility of increasing the above operation being implemented by the user corresponding to the target user account is increased.

[0184] In one embodiment, after step 103, the embodiments of the present application can further include step 104:

[0185] 104. sending the target user account and the identity of the first terminal device to the server, so as to log the identities of the plurality of terminal devices of the target user account to the second common account and display the second common account to other users participating in the target multi-person session.

[0186] The first terminal device can package the target user account and the identity of the first terminal device in session account state information corresponding to the first terminal device, and send the session account state information to the server, so as to log the identities of the plurality of terminal devices of the target user account to another common account, distinguish the another common account from the common account obtained by integrating the target user account and the plurality of terminal devices of the target user account in step 220, and name the another common account as a second common account.

[0187] The above-mentioned step of "logging the identities of the plurality of terminal devices of the target user account to the second common account" can be executed on the server or on the terminal device as the receiver. If executed on the terminal device as the receiver, the server can send the received plurality of pieces of session account state information to the terminal device as the receiver, and the terminal device as the receiver can execute the above-mentioned step.

[0188] In one embodiment, the target user account is a user account managing the target multi-person session, and the method further comprises:

[0189] In response to a setting operation representing prohibition of multi-device participation in the session, the session permission of the target multi-person session is modified from allowing multi-device participation in the session to prohibiting multi-device participation in the session.

[0190] The first terminal device can modify the session permission of the target multi-person session from allowing multi-device participation in the session to prohibiting multi-device participation in the session in response to a setting operation representing prohibition of multi-device participation in the session triggered by the user.

[0191] Optionally, the setting operation representing prohibition of multi-device participation in the session can be determined by the user selecting an option of "whether to allow multi-terminal participation in the session" provided by a security menu of the session application program.

[0192] Optionally, the target user account is a user account managing the target multi-person session, and the method further comprises:

[0193] In response to a setting operation representing prohibition of multi-device participation in the session, an instruction of prohibiting multi-device participation in the session is sent to the server, so that the server modifies the session permission of the target multi-person session from allowing multi-device participation in the session to prohibiting multi-device participation in the session.

[0194] The instruction of prohibiting multi-device participation in the session is used to instruct the server to modify the session permission of the target multi-person session from allowing multi-device participation in the session to prohibiting multi-device participation in the session.

[0195] The user account managing the target multi-person session can change the permission of the target multi-person session. The user account managing the target multi-person session can be an account with a host identity or an account with an administrator identity, etc.

[0196] The first terminal device can send an instruction to prohibit multi-device participation in the session to the server in response to a setting operation triggered by a user, which represents prohibition of multi-device participation in the session.

[0197] The server receives the instruction to prohibit multi-device participation in the session, and modifies the session permission of the corresponding target multi-person session from allowing multi-device participation in the session to prohibiting multi-device participation in the session.

[0198] Optionally, in an embodiment, the modification of the session permission from allowing multi-device participation in the session to prohibiting multi-device participation in the session can only take effect for subsequent session users. That is, the users who have participated in the session through multiple devices before the change of the session permission can not be affected; and when a user participates in the target multi-person session through terminal device A after the change of the session permission, the server can first detect whether the user has a device that has participated in the session, if there is a device that has participated in the session, return a prompt of refusing multi-device participation in the session, and prompt the user to switch the session device (i.e. switch the session device from the previous session device to terminal device A) or maintain the previous session device; if there is no device that has participated in the session, allow terminal device A to participate in the current target multi-person session.

[0199] Optionally, in another embodiment, the modification of the session permission from allowing multi-device participation in the session to prohibiting multi-device participation in the session can take effect not only for subsequent session users but also for users who have participated in the session through multiple devices before the change of the session permission. Specifically, for users who have participated in the session through multiple devices before the change of the session permission, one device can be randomly reserved as a session state from the multiple devices participating in the target multi-person session, and the other devices are all exited from the target multi-person session. For example, please refer to FIG. 3f. Suppose that device A1 is the device randomly reserved by the server, the server can control device A2 to exit the target multi-person session: zz conference.

[0200] In this embodiment, by giving the conference manager the ability to dynamically adjust the multi-device participation permission, the administrator can flexibly switch the session permission between multi-terminal access and forced single-device participation mode according to the conference security level or scene demand, which not only retains the flexibility of devices in regular conferences, but also provides strict terminal control means for sensitive conferences, effectively balancing the convenience and security needs of the conference.

[0201] The online conference processing method provided in the embodiments of the present application includes receiving a plurality of pieces of session account state information sent by a server. Each piece of session account state information includes a user account and terminal device information of a terminal device logging in the user account. The terminal device integrates the same user accounts into a common account and binds the terminal device information of the terminal devices logging in the same user accounts to the common account. The terminal device displays the common account and the user accounts that are not integrated in a session member list. In the embodiments of the present application, the plurality of devices corresponding to the same user account can be bound to a common account according to whether the user accounts are the same, and the common account and the user accounts that are not integrated are displayed together in the session member list. The user accounts that are not integrated are user accounts that do not participate in the multi-person session through a plurality of devices. Even if there is a user participating in the multi-person session through a plurality of devices, one account is still displayed for other users participating in the multi-person session.

[0202] The embodiments of the present application can avoid the situation that the same natural person participating in an online conference through a plurality of different accounts leads to conference order disorder, and facilitate the smooth progress of the target multi-person session.

[0203] The embodiments of the present application can link a single account of a user on a plurality of terminal devices, flexibly use the input mode and output mode of different terminal devices, and provide a more suitable experience for the user to participate in the target multi-person session. Specifically, the embodiments of the present application can combine a television, a car machine, a personal computer, a mobile terminal and a smart wearable device to achieve seamless switching of the multi-person session, and the operation of other users on the user participating in the session through a plurality of devices is still relatively simple in the multi-person session. For conference data records, since a plurality of terminal devices correspond to one common account, multiple conference records will not be generated, and information redundancy is avoided.

[0204] In one embodiment, an online conference processing method applied to a server is further provided. The specific process of the method can include:

[0205] Receiving session account state information sent by a plurality of terminal devices, each piece of session account state information including a user account and terminal device information of a terminal device logging in the user account; integrating the same user accounts into a common account and binding the terminal device information of the terminal devices logging in the same user accounts to the common account. Sending the common account and the user accounts that are not integrated to the plurality of terminal devices, so that each terminal device displays the common account and the user accounts that are not integrated.

[0206] The terminal device information of the terminal device logging in the user account can be information reflecting the uniqueness of the terminal device. Specifically, it can be an identity of the terminal device.

[0207] Each terminal device can send its corresponding session account status information to the server. For example, assume that the number of terminal devices is 5, and the 5 terminal devices and the session account status information sent by each terminal device are as follows:

[0208] The terminal device with identity B1 sends session account status information 1, which includes the account of user B and the identity B1 of the terminal device.

[0209] The terminal device with identity c sends session account status information 2, which includes the account of user C and the identity c of the terminal device.

[0210] The terminal device with identity B3 sends session account status information 3, which includes the account of user B and the identity B3 of the terminal device.

[0211] The terminal device with identity ddd sends session account status information 4, which includes the account of user D and the identity ddd of the terminal device.

[0212] The terminal device with identity B2 sends session account status information 5, which includes the account of user B and the identity B2 of the terminal device.

[0213] The server can integrate the same user account into a common account based on the user accounts in the plurality of pieces of session account status information, and bind the identities of the plurality of terminal devices corresponding to the same user account to the common account. Alternatively, the user account can be directly used as the common account, and the identities of the terminal devices corresponding to the user account can be bound to the user account; or a new account, which is temporarily created and denoted as account x, can be bound to the identities of the terminal devices corresponding to the user account.

[0214] For example, the server can directly use the account of user B as the common account, and bind the identities B1, B2 and B3 of the terminal devices to the account of user B. In another embodiment, the server can temporarily create an account Bx, and bind the identities B1, B2 and B3 of the terminal devices to the account Bx. When the target multi-person session ends, the server can delete the temporarily created account Bx.

[0215] Alternatively, in an embodiment, user A can participate in the target multi-person session through the two terminal devices A1 and A2, user B can participate in the target multi-person session through the terminal device B, and the server includes a service end and a media end. The interaction relationship among the server, the terminal devices A1, A2 and B is described.

[0216] The service end of the server is configured to process the opening or closing of the hardware device (i.e., the microphone or the camera) of the terminal device, and the media end of the server is configured to process the opening or closing of the audio and video function. For details, refer to FIG. 8. When user A participates in the target multi-person session through device A1, device A1 sends prompt information representing the entry of device A1 into the session to the service end. The service end creates a common account Ax and binds the identity of device A1, and then returns response information to device A1. The response information represents the success of the session of device A1, and the response information carries information representing the binding of the common account Ax and device A1: (A1: Ax). Device A1 sends (A1: Ax) to the media end, and the media end records it in the mapping list: (A1: Ax). The service end also pushes a message representing the entry of the common account Ax into the session to other users (e.g., device B corresponding to user B) of the session. The common account Ax is displayed in the member list of the other users of the session.

[0217] Then, when user A participates in the target multi-person session through device A2, device A2 sends prompt information representing the entry of device A2 into the session to the service end. The service end binds the identity of device A2 to the common account Ax, and then returns response information to device A2. The response information represents the success of the session of device A2, and the response information carries information representing the binding of the common account Ax and device A2: (A2: Ax). Device A2 sends (A2: Ax) to the media end, and the media end also records it in the mapping list: (A1: Ax); (A2: Ax). At this time, since device A2 also corresponds to the common account Ax, the service end does not need to push an entry message to other users (e.g., device B corresponding to user B) of the session.

[0218] When user A opens the microphone of device A1, device A1 sends prompt information representing the opening of the microphone of A1 to the service end and the media end, respectively. The service end records the audio state of the terminal device bound to Ax: device A1 opens the microphone; device A2 closes the microphone; and the common account displays externally: opens the microphone. Then, the service end sends prompt information representing the closing of the microphone to device A2: {A2: closes the microphone}. Device A2 closes the microphone and sends the state of the closed microphone to the media end. The media end records the opening and closing states of the microphone in the mapping list: (A1: Ax) opens the microphone; (A2: Ax) closes the microphone. The service end also pushes prompt information representing the opening of the microphone of the common account Ax to other users (e.g., device B corresponding to user B) of the session. Device B subscribes to the audio of the common account Ax based on the received prompt information, and the media end returns the audio of device A1.

[0219] When the user A opens the camera of the device A2, the device A2 sends the prompt information of opening the camera of the device A2 to the service end and the media end respectively. The service end records the audio and video state of the terminal device bound with the Ax: the device A1 opens the microphone and closes the video; the device A2 closes the microphone and opens the video; the joint account displays to the outside: opening the microphone and opening the video. Subsequently, the service end sends the prompt information of closing the camera to the device A1: {A1: close the video}. The device A1 closes the camera and sends the state of closing the camera to the media end. The media end records the opening and closing state of the microphone and the camera in the mapping list: (A1: Ax) opens the microphone and closes the video; (A2: Ax) closes the microphone and opens the video. The service end also pushes the prompt information to other users (for example, the device B corresponding to the user B) of the session: the joint account Ax opens the camera. The device B subscribes to the video of the joint account Ax based on the received prompt information. The media end returns the video of the device A2.

[0220] In the above embodiment, the server can receive the session account state information sent by the plurality of terminal devices respectively, integrate the same user account into a joint account based on the user account in the plurality of pieces of session account state information, bind the identity of the plurality of terminal devices corresponding to the same user account with the joint account, and display the joint account in the session member list. The above embodiment can make the user participating in the target multi-person session through the plurality of devices displayed as one user in the user list of other users, avoid the occurrence of the situation that the user list is chaotic, facilitate mutual identification between users, and better maintain the order of the target multi-person session.

[0221] Optionally, in an embodiment, the method can further include:

[0222] receiving a session leaving request sent by a terminal device, the session leaving request including a user account and an identity of the terminal device; controlling the terminal device corresponding to the identity to exit the target multi-person session; when there is still a terminal device logging in the user account participating in the session in the target multi-person session, maintaining the online state of the joint account; when there is no terminal device logging in the user account participating in the session in the target multi-person session, sending prompt information that the joint account has left the session to all terminal devices currently participating in the session.

[0223] When the server receives the session leaving request sent by the terminal device, the server can control the terminal device corresponding to the session leaving request to exit the target multi-person session.

[0224] The server can further determine, based on the user account included in the session leaving request, whether there is still a terminal device logged in the user account participating in the current target multi-person session. If there is, it indicates that the user corresponding to the user account has not completely left the session, but has only reduced the terminal devices participating in the session. Therefore, the online status of the common account can be maintained unchanged.

[0225] When there is no terminal device logged in the user account participating in the current target multi-person session, it indicates that the user corresponding to the user account has left the session. Therefore, the server can send prompt information to all terminal devices participating in the current session that the common account has left the session.

[0226] In the above embodiment, whenever a terminal device sends a session leaving request to the server, the server can determine, after controlling the terminal device to leave the session, whether there is still a terminal device logged in the user account participating in the current target multi-person session according to the user account included in the session leaving request. If there is, the online status of the common account is maintained unchanged. If there is not, the server sends prompt information to all terminal devices participating in the current session that the common account has left the session. In this way, the user using multiple terminal devices to participate in the session can be prompted to leave the session only when the user actually leaves the session, and information misdirection caused by prompting each terminal device to leave the session can be avoided.

[0227] In the online conference processing method provided by the embodiment of the application, the server can receive session account status information sent by multiple terminal devices respectively, integrate the same user account into a common account based on the user accounts in the multiple pieces of session account status information, bind the multiple terminal devices corresponding to the same user account with the common account, and display the common account in the session member list. The above embodiment can make the user participating in the multi-person session through multiple devices displayed as only one user in the user list of other users, avoid the occurrence of a situation of user list confusion, facilitate mutual recognition between users, and better maintain the order of the target multi-person session.

[0228] The embodiment of the application can avoid the situation of conference order confusion caused by the same natural person being online through multiple different accounts, and facilitate the smooth progress of the target multi-person session.

[0229] For details, refer to FIG. 9. FIG. 9 shows an online conference processing method provided by an embodiment of the application, applied to a first terminal device. The method includes the following steps:

[0230] In step 910, a to-be-session list interface is displayed, and the to-be-session list interface displays multiple session entry controls. The to-be-session list interface displays a target multi-person session joined by a second terminal device through a target user account.

[0231] The display timing of the multi-terminal joining control is not limited, for example, the multi-terminal joining control can be displayed when the to-be-conversation list interface is displayed, or the multi-terminal joining control can be displayed when the user triggers a preset operation in the to-be-conversation list interface. The multi-terminal joining control can also be displayed after the user has joined the target multi-person conversation through the second terminal device.

[0232] For details, refer to FIG. 3a and FIG. 5a. FIG. 3a shows a to-be-conversation list interface applied to a mobile terminal; and FIG. 5a shows a to-be-conversation list interface applied to a personal computer (PC). The multi-terminal joining in FIG. 3a and the multi-terminal joining in FIG. 5a can be a specific implementation of the multi-terminal joining control C02.

[0233] In one embodiment, the online meeting processing method can be applied to the first terminal device, the first terminal device is installed with a conversation application program, and the target user account is logged in the conversation application program; and the to-be-conversation list interface is displayed, including: displaying the to-be-conversation list interface of the conversation application program.

[0234] In one embodiment, taking the conversation application program as an example, the first terminal device is installed with an online meeting application program, and the target user account is logged in the online meeting application program. The first terminal device displays the to-be-conversation list interface of the online meeting application program.

[0235] In step 920, in response to the trigger operation on the multi-terminal joining control, the first terminal device enters the multi-person conversation interface of the target multi-person conversation through the target user account.

[0236] The multi-person conversation interface is a user interface in which the online meeting application program holds the target multi-person conversation. Optionally, the multi-person conversation interface can be as shown in FIG. 3b.

[0237] In one embodiment, the multi-person conversation interface displays a multimedia uplink control. The method can further include: in response to the trigger operation on the multimedia uplink control, displaying first switching prompt information in the multi-person conversation interface, the first switching prompt information being used to prompt switching of the multimedia uplink function to the first terminal device; and when the multimedia uplink control located at the second terminal device is triggered, displaying second switching prompt information in the multi-person conversation interface, the second switching prompt information being used to prompt switching of the multimedia uplink function to the second terminal device.

[0238] The multimedia uplink control is used to realize the collection and transmission of multimedia information. Optionally, in an embodiment, the multimedia uplink control can be the "unmute", "start video", and "share screen" virtual controls in the multi-person session interface, as shown in FIGS. 3b, 3d, and 3e. For ease of description, the "unmute" and "start video" virtual controls are taken as examples for description below:

[0239] For the "unmute" virtual control, if the "unmute" virtual control is triggered, it indicates that the user expects to collect and upload audio through the first terminal device, and thus the corresponding first switching prompt information "switch to the audio of the current device, and the audio of other devices is disconnected" can be displayed in the multi-person session interface, to prompt the user that the uplink function related to audio has been switched to the first terminal device, as shown in FIG. 6a.

[0240] For the "start video" virtual control, if the "start video" virtual control is triggered, it indicates that the user expects to collect and upload video through the first terminal device, and thus the corresponding first switching prompt information "switch to the video of the current device, and the video of other devices is disconnected" can be displayed in the multi-person session interface, to prompt the user that the uplink function related to video has been switched to the first terminal device, as shown in FIG. 7a.

[0241] For the "unmute" virtual control, if the "unmute" virtual control located at the second terminal device is triggered, it indicates that the user expects to collect and upload audio through the second terminal device, and thus the corresponding second switching prompt information "switch to the audio of another device, and the audio of the current device is disconnected" can be displayed in the multi-person session interface, to prompt the user that the uplink function related to audio has been switched to the second terminal device, as shown in FIG. 6b.

[0242] For the "start video" virtual control, if the "start video" virtual control located at the second terminal device is triggered, it indicates that the user expects to collect and upload video through the second terminal device, and thus the corresponding second switching prompt information "switch to the video of another device, and the video of the current device is disconnected" can be displayed in the multi-person session interface, to prompt the user that the uplink function related to video has been switched to the second terminal device, as shown in FIG. 7b.

[0243] In this embodiment, by dynamically displaying and triggering the multimedia uplink function switching prompt information corresponding to the device in the multi-person conversation interface, the user can intuitively identify the current switchable device options, realize the rapid cross-device transfer of media streams such as audio and video, and effectively solve the problem of chaotic media control management in a multi-terminal scenario. Through the precise matching of the first and second switching prompt information, the tediousness of manually searching for the target device in the traditional scheme is avoided, and the accuracy and immediacy of media uplink function switching are ensured, significantly improving the operation efficiency and media control experience during cross-device collaborative conferences.

[0244] Optionally, in an embodiment, the to-be-conversation list interface further displays a login device prompt control. The method can further include the following steps:

[0245] In response to a triggering operation on the login device prompt control, a login device list interface is displayed; wherein the login device list interface is used to display state information of the logged-in devices, and the logged-in devices all install the online conference application program and the online conference application program is logged in the target user account.

[0246] The login device list interface is used to display state information of the logged-in devices. The logged-in devices all install the online conference application program and the online conference application program is logged in the target user account. For details, please refer to FIG. 4b, which shows a login device list interface in a specific embodiment. In FIG. 4b, four logged-in devices are shown: device B1, device B2, device B3, and device B4, and the current state information of each logged-in device: device B1 joins x conference; device B2 joins x conference; device B3 joins y conference; and device B4 has not joined the conference and is in the state of the target user account being logged in.

[0247] In this embodiment, by providing a login device prompt control in the conversation list interface, the user can quickly view the real-time state of all logged-in devices under the current account, effectively improving the transparency and convenience of multi-terminal management. By centrally displaying device information of the online conference application program installed and logged in the same account, the user can clearly understand the account login situation, avoid account security risks or conference conflicts caused by unknown device states, and provide decision basis for subsequent multi-device collaborative operations (such as device switching or remote logout), thereby enhancing the account management capability and conference management efficiency in the cross-device usage scenario.

[0248] Optionally, in an embodiment, the to-be-conversation list interface further includes a join conference control, and the method can further include the following steps K1 to K2:

[0249] K1, in response to a triggering operation on the join conference control, a conference number search box is displayed.

[0250] Optionally, as shown in FIG. 5a, in an embodiment, the user can also click the join meeting control shown in FIG. 5a to pop up a meeting number search box (not shown).

[0251] K2, in response to the meeting number input operation on the meeting number search box, when the multi-person meeting corresponding to the meeting number input operation has been joined by the target user account through the second terminal device, a join meeting prompt interface is displayed.

[0252] The join meeting prompt interface includes at least one of a switch-in control, a multi-terminal participation control, or a temporary non-participation control. The switch-in control is used to switch the device participating in the multi-person meeting to the first terminal device. The multi-terminal participation control is used to join the multi-person meeting together with the first terminal device. The temporary non-participation control is used for the first terminal device to temporarily not join the multi-person meeting.

[0253] The meeting number of the target multi-person session can be input in the meeting number search box, and when the target multi-person session has been joined by the target user account through the second terminal device, a meeting prompt interface can be displayed. Optionally, the meeting prompt interface can be a pop-up window interface as shown in FIG. 5b, and the user can determine the participation mode of the first terminal device by clicking different virtual controls in the pop-up window interface.

[0254] The switch-in control corresponds to the "switch to the current device to join" control shown in FIG. 5b, the multi-terminal participation control corresponds to the "add the current device to join together" control shown in FIG. 5b, and the temporary non-participation control corresponds to the "temporarily not join" control shown in FIG. 5b.

[0255] Specifically, the user can click the "temporarily not join" control to select the first terminal device not to participate in the target multi-person session; the user can also click the "add the current device to join together" control to select the multi-terminal device participation mode; and the user can also click the "switch to the current device to join" control to select only the first terminal device to participate in the session and stop the second terminal device from participating in the session.

[0256] In this embodiment, by intelligently identifying whether the user input meeting number has been joined in other devices, the join meeting prompt interface is automatically triggered and provides differentiated options such as multi-terminal participation, device switching, or temporary non-participation, effectively solving the conflict problem of the same account multi-terminal repeated join meeting, avoiding waste of conference resources, providing flexible device selection for users, and simplifying the meeting decision-making process in the multi-terminal scenario through clear control design, significantly improving the cross-device meeting joining experience and system resource utilization.

[0257] In the online conference processing method provided in the embodiment, the target multi-person conference that the second terminal device has joined is intelligently displayed on the to-be-conferenced list interface of the first terminal device, and a multi-end conference control is provided, so that the user can join the target multi-person conference through the same account by one key by using the current device, seamless connection of cross-terminal conferences is realized, tedious operations such as repeated input of conference numbers or manual searching for conferences are avoided, conference joining efficiency in a multi-device scenario is improved, real-time synchronization of conference states of multiple devices under the same account is ensured, and conference participation experience of the user when switching devices is optimized. Moreover, conference order disorder caused by the same natural person online through multiple different accounts can be avoided, and the target multi-person conference can be smoothly conducted.

[0258] In the embodiment, the control is a virtual button, and the target multi-person conference is a target multi-person conference. The method is applied to a first terminal device, and the specific process of the method is as follows:

[0259] In response to a trigger operation on the conference application, a to-be-conferenced list interface of the conference application is displayed, and the to-be-conferenced list interface includes a multi-end conference button representing multi-device participation in a conference. The target user account has joined a target multi-person conference through a conference application installed on a second terminal device.

[0260] Optionally, the to-be-conferenced list interface can also include a login device prompt button. In response to a trigger operation on the login device prompt button, a login device list interface is displayed. The login device list interface is used to display state information of logged-in devices. The logged-in devices are all installed with the conference application, and the conference application is logged in to the target user account.

[0261] In response to a trigger operation on a device detail button corresponding to a target logged-in device, a detailed state panel of the target logged-in device is displayed. The detailed state panel displays a conference name of the target logged-in device. The detailed state panel is provided with a switch button representing switching of a device conference. The target logged-in device is any logged-in device in all logged-in devices that joins a preset conference group. The preset conference group is any target multi-person conference.

[0262] In response to a trigger operation on the switch button, a switch participation conference device instruction is sent to the server, so that the server controls the target user account logged in to the first terminal device to join the preset conference group, and controls the target user account logged in to the target logged-in device to exit the preset conference group. In response to a trigger operation on the multi-end conference button, a multi-end conference instruction is sent to the server, so that the server controls the target user account logged in to the first terminal device to join the preset conference group.

[0263] In response to a trigger operation on the multi-end conference button, a multi-person conference interface of the target multi-person conference is displayed on the conference application installed on the first terminal device.

[0264] sending the target user account and the identity of the first terminal device to the server, so as to log the identity of the plurality of terminal devices of the target user account into the same common account, and display the common account to other users participating in the target multi-person conference.

[0265] receiving the video information sent by the server, and displaying the video information in the multimedia information display area.

[0266] sending an audio receiving request to the server in response to an audio receiving trigger operation representing receiving the audio information. The audio receiving request is used to instruct the server to return the audio information and stop sending the audio information to the session application installed on the second terminal device.

[0267] receiving the audio information returned by the server, and playing the audio information.

[0268] starting the multimedia collection tool arranged on the first terminal device to implement collection of local multimedia information in response to a trigger operation on the multimedia uplink button.

[0269] sending the local multimedia information to the server, so that the server transmits the local multimedia information to other users participating in the target multi-person conference, and the server disconnects the multimedia collection tool of the second terminal device.

[0270] displaying a session device list interface in response to a trigger operation on the session device prompt button, the session device list interface being used to display device information of all terminal devices participating in the target multi-person conference.

[0271] popping up a permission reminder interface in response to a trigger operation on a target terminal device, the permission reminder interface including a session rejection button; the target terminal device being any one of all terminal devices participating in the target multi-person conference, the permission reminder interface being used to inquire whether to allow the target terminal device to continue participating in the target multi-person conference.

[0272] sending a session rejection instruction to the server in response to a trigger operation on the session rejection button, so that the server controls the target user account logged in the target terminal device to exit the target multi-person conference.

[0273] receiving session account state information sent by the server, each piece of session account state information including a user account and an identity of a different terminal device logged in the user account.

[0274] integrating different user accounts corresponding to different terminal devices into the same common account for display, and binding the identity of each of the different terminal devices logged in the same user account to the common account.

[0275] The session member list displays the common account and the multi-device session identifier corresponding to the common account.

[0276] Optionally, the target user account can also be a user account managing the target multi-person conference; in response to the setting operation representing the prohibition of multi-device session participation, an instruction of prohibiting multi-device session participation is sent to the server, so that the server modifies the session permission of the target multi-person conference from allowing multi-device session participation to prohibiting multi-device session participation.

[0277] The specific execution process of each step can be referred to the above embodiments.

[0278] In the online conference processing method provided by the embodiment of the present application, the first terminal device displays a to-be-session list interface of the session application program in response to a trigger operation of the user on the session application program, and the to-be-session list interface includes a multi-terminal entry control. The multi-terminal entry control appears because the user has joined a target multi-person session through the session application program of the second terminal device. The user account logged in by the session application program of the second terminal device is the same as the user account logged in by the session application program of the first terminal device, and both are target user accounts. In response to a trigger operation of the user on the multi-terminal entry control, the first terminal device participates in the target multi-person session, and displays a multi-person session interface of the target multi-person session on the session application program of the first terminal device. The first terminal device also sends the target user account and the identity of the first terminal device to the server, so that the identities of the terminal devices logged in by the target user account belong to one account, which is named as a common account, and the common account is displayed to other users participating in the target multi-person session. In the embodiment of the present application, the multiple devices corresponding to the same user account can be bound in a common account according to whether the user accounts are the same, and the common account is displayed to other users of the session. Even if the user participates in the target multi-person session through multiple devices, only one account is displayed to other users of the session.

[0279] The embodiment of the present application can avoid the situation of conference order confusion caused by the same natural person participating in the conference online through multiple different accounts, and is beneficial to the smooth progress of the target multi-person session.

[0280] In order to better implement the above method, the embodiment of the present application further provides an online conference processing device, which can be integrated in an electronic device, and the electronic device can be a terminal device or a server. The terminal device can be a mobile phone, a tablet computer, a smart Bluetooth device, a notebook computer, or a personal computer (PC), etc. For example, as shown in FIG. 10, the device is applied to an electronic device, and the device includes:

[0281] The information receiving unit 1001 is configured to acquire session account status information, the session account status information comprising a user account and device information of different terminal devices logging in the user account. In other embodiments, the information receiving unit 401 is further configured to receive a plurality of pieces of session account status information sent by a server.

[0282] The account integrating unit 1002 is configured to integrate different user accounts corresponding to the same user account into a same common account for display.

[0283] The account binding unit 1003 is configured to bind the device information of different terminal devices logging in the same user account to the common account.

[0284] In one of the embodiments, the device further comprises:

[0285] The account display unit is configured to display the common account and the user account that is not integrated.

[0286] In one of the embodiments, the account display unit is further configured to display the common account and the user account that is not integrated in a session member list.

[0287] In one embodiment, the electronic device comprises a first terminal device, and the device further comprises:

[0288] The interface display unit is configured to display a to-be-session list interface.

[0289] The control display unit is configured to display a multi-entry control in the to-be-session list interface in response to a received control display instruction, the control display instruction indicating that the second terminal device joins a target multi-person session by using a target user account.

[0290] The session group joining unit is configured to join the first terminal device to the target multi-person session by using the target user account in response to a triggering operation on the multi-entry control.

[0291] In one embodiment, the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface comprises a multimedia information playing area. The device further comprises:

[0292] The playing area unit is configured to receive video information sent by a server and display the video information in the multimedia information playing area.

[0293] The audio receiving request unit is configured to send an audio receiving request to the server in response to an audio receiving triggering operation, the audio receiving request being used to instruct the server to return audio information and send the audio information to a session application installed in the second terminal device.

[0294] The audio playing unit is configured to receive the audio information returned by the server and play the audio information.

[0295] In an embodiment, the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface displays a multimedia uplink control for collecting and transmitting multimedia information; the apparatus further comprises:

[0296] A tool starting unit is configured to collect local multimedia information by using a multimedia collection tool installed in the first terminal device in response to a triggering operation on the multimedia uplink control.

[0297] An information sending unit is configured to send the local multimedia information to a server, so that the server transmits the local multimedia information to other users participating in the target multi-person session, and so that the server disconnects the multimedia collection tool of the second terminal device.

[0298] In an embodiment, the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface displays a session device prompt control; the apparatus further comprises:

[0299] A list interface display unit is configured to display a session device list interface in response to a triggering operation on the session device prompt control, and the session device list interface is configured to display device information of all terminal devices of the target user account participating in the target multi-person session.

[0300] A permission pop-up unit is configured to pop up a permission reminder interface in response to a triggering operation on a target terminal device, and the permission reminder interface displays a session rejection control, the target terminal device is any terminal device of all terminal devices of the target user account participating in the target multi-person session, and the permission reminder interface is configured to ask whether to allow the target terminal device to continue participating in the target multi-person session.

[0301] A rejection instruction sending unit is configured to send a session rejection instruction to a server in response to a triggering operation on the session rejection control, so that the server controls the target user account logged in the target terminal device to exit the target multi-person session.

[0302] In an embodiment, the session list interface displays a login device prompt control; the apparatus further comprises:

[0303] A login device display unit is configured to display a login device list interface in response to a triggering operation on the login device prompt control, and the login device list interface is configured to display state information of logged-in devices, and the logged-in devices all install a session application and the session application is logged in the target user account.

[0304] In an embodiment, the login device list interface displays a device detail control; the apparatus further comprises:

[0305] The panel display unit is configured to display a detailed state panel of the target logged-in device in response to a triggering operation on a device detail control corresponding to the target logged-in device, the detailed state panel displaying a session name of the target logged-in device, and the detailed state panel being provided with a switching control representing switching of a device participating in the session; the target logged-in device is any logged-in device in all logged-in devices that joins a preset session group, and the preset session group is any multi-person session group.

[0306] The instruction sending unit is configured to send a switching session device instruction to the server in response to a triggering operation on the switching control; the session device instruction is used to instruct the server to control the target user account logged in the first terminal device to join the preset session group and control the target user account logged in the target logged-in device to exit the preset session group.

[0307] In an embodiment, the detailed state panel further displays a multi-end access control representing allowing multiple devices to participate in the session; and the apparatus further includes:

[0308] The multi-end participating unit is configured to send a multi-end session instruction to the server in response to a triggering operation on the multi-end access control, so that the server controls the target user account logged in the first terminal device to join the preset session group.

[0309] In an embodiment, the target user account is a user account managing the target multi-person session; and the apparatus further includes:

[0310] The session setting unit is configured to modify a session permission of the target multi-person session from allowing multiple devices to participate in the session to prohibiting multiple devices to participate in the session in response to a setting operation representing prohibiting multiple devices to participate in the session.

[0311] In an embodiment, the target user account is a user account managing the target multi-person session; and the apparatus further includes:

[0312] The session setting unit is configured to send an instruction of prohibiting multiple devices to participate in the session to the server in response to a setting operation representing prohibiting multiple devices to participate in the session, so that the server modifies a session permission of the target multi-person session from allowing multiple devices to participate in the session to prohibiting multiple devices to participate in the session.

[0313] In implementation, each of the above units can be implemented as an independent entity, or can be combined as the same or several entities, and the specific implementation of each of the above units can be referred to the method embodiments above, which will not be described here.

[0314] The online conference processing method provided in the embodiments of the present application includes the following steps: receiving a plurality of pieces of session account state information sent by a server. Each piece of session account state information includes a user account and terminal device information of a terminal device logged in the user account. The terminal device integrates the same user accounts into a common account, and binds the terminal device information of the terminal devices logged in the same user accounts to the common account. The terminal device displays the common account and the user accounts that are not integrated in a session member list. In the embodiments of the present application, the plurality of devices corresponding to the same user account can be bound to a common account according to whether the user accounts are the same, and the common account and the user accounts that are not integrated are displayed together in the session member list. The user accounts that are not integrated are user accounts that do not participate in the multi-person session through a plurality of devices. Even if there is a user participating in the multi-person session through a plurality of devices, one account is still displayed for other users participating in the multi-person session.

[0315] The embodiments of the present application can avoid the situation that the online conference is prone to disorder due to the same natural person participating in the online conference through a plurality of different accounts, and facilitate the smooth progress of the target multi-person session.

[0316] In order to better implement the above method, the embodiments of the present application further provide an online conference processing device, which can be integrated in an electronic device, and the electronic device can be a server. The server can be a single server or a server cluster composed of a plurality of servers. For example, the device is applied to a server, and the device includes:

[0317] an information receiving unit, configured to receive session account state information sent by different terminal devices, and each piece of session account state information includes a user account and terminal device information of a terminal device logged in the user account;

[0318] an account integrating unit, configured to integrate the same user accounts corresponding to different terminal devices into a same common account;

[0319] an account binding unit, configured to bind device information of different terminal devices logged in the same user accounts to the common account;

[0320] an account sending unit, configured to send the common account and the user accounts that are not integrated to different terminal devices, so that each terminal device displays the common account and the user accounts that are not integrated.

[0321] In an implementation manner, the device further includes:

[0322] a leave session request receiving unit, configured to receive a leave session request sent by a terminal device, and the leave session request includes a user account and an identity of the terminal device;

[0323] A conference exit unit is configured to control a terminal device corresponding to the identity to exit the target multi-person conference;

[0324] An online maintenance unit is configured to maintain the online status of the common account when there is still a terminal device of the login user account participating in the conference in the target multi-person conference.

[0325] A leaving notification unit is configured to send prompt information that the common account has left to all terminal devices currently participating in the conference when there is no terminal device of the login user account participating in the conference in the target multi-person conference.

[0326] In the online conference processing method provided by the embodiments of the present application, the server can receive the conference account status information sent by different terminal devices respectively, integrate the same user account into a same common account based on the user account in the conference account status information, bind the plurality of terminal devices corresponding to the same user account with the common account, and display the common account in the conference member list. The above implementation manner can make the user participating in the target multi-person conference through a plurality of devices displayed as one user in the user list of other users, avoid the occurrence of the situation that the user list is chaotic, facilitate mutual identification between users, and better maintain the order of the target multi-person conference.

[0327] The embodiments of the present application can avoid the situation that the conference order is chaotic due to the same natural person participating in the conference online through a plurality of different accounts, and facilitate the smooth progress of the target multi-person conference.

[0328] In order to better implement the above method, the embodiments of the present application further provide an online conference processing device. The online conference processing device can be integrated in an electronic device, and the electronic device can be a first terminal device. The first terminal device can be a mobile phone, a tablet computer, a smart Bluetooth device, a notebook computer, or a personal computer (PC), etc. For example, as shown in FIG. 11, the device is applied to a first terminal device, and the device includes:

[0329] A list display unit 1101 is configured to display a to-be-conferenced list interface, and the to-be-conferenced list interface includes a multi-end conference control. The to-be-conferenced list interface displays a target multi-person conference joined by a second terminal device through a target user account.

[0330] A conference display unit 1102 is configured to, in response to a trigger operation on the multi-end conference control, make the first terminal device enter a multi-person conference interface of the target multi-person conference through the target user account.

[0331] In an implementation manner, the multi-person conference interface displays a multimedia uplink control. The device further includes:

[0332] The first switching unit is configured to display a first switching prompt information in the multi-person session interface in response to a triggering operation on the multimedia uplink control, and the first switching prompt information is used to prompt switching of the multimedia uplink function to the first terminal device.

[0333] The second switching unit is configured to display a second switching prompt information in the multi-person session interface when the multimedia uplink control on the second terminal device is triggered, and the second switching prompt information is used to prompt switching of the multimedia uplink function to the second terminal device.

[0334] In an embodiment, the to-be-session list interface displays a login device prompt control; and the device further includes:

[0335] The login interface unit is configured to display a login device list interface in response to a triggering operation on the login device prompt control, and the login device list interface is used to display state information of the logged-in devices, wherein the logged-in devices all install the session application and the session application all log in the target user account.

[0336] In an embodiment, the to-be-session list interface further displays a join meeting control; and the device further includes:

[0337] The search box pop-up unit is configured to display a meeting number search box in response to a triggering operation on the join meeting control.

[0338] The meeting prompt unit is configured to display a join meeting prompt interface in response to a meeting number input operation on the meeting number search box, when a multi-person meeting corresponding to the meeting number input operation has been joined by the target user account through the second terminal device.

[0339] The join meeting prompt interface includes at least one of a switching join control, a multi-terminal participation control or a temporary non-participation control, wherein the switching join control is used to switch the device participating in the multi-person meeting to the first terminal device, the multi-terminal participation control is used to add the first terminal device to the multi-person meeting, and the temporary non-participation control is used to temporarily not add the first terminal device to the multi-person meeting.

[0340] Embodiments of the present application also provide an electronic device, which can be a terminal, a server, etc. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a notebook computer, a personal computer, etc., and the server can be a single server or a server cluster composed of multiple servers, etc.

[0341] In some embodiments, the online meeting processing device can also be integrated in multiple electronic devices, for example, the online meeting processing device can be integrated in multiple servers to implement the online meeting processing method of the present application.

[0342] In this embodiment, the electronic device of this embodiment will be taken as an example to be described in detail, for example, as shown in FIG. 12, which shows a structural schematic diagram of the electronic device related to the embodiments of the present application, in particular:

[0343] The electronic device can include a processor 1201 with one or more processing cores, a memory 1202 with one or more computer readable storage media, a power supply 1203, an input module 1204, a communication module 1205, and the like. Those skilled in the art can understand that the electronic device structure shown in FIG. 12 does not constitute a limitation on the electronic device, and can include more or fewer components than shown, or combine certain components, or different component arrangements. Among them:

[0344] The processor 1201 is the control center of the electronic device, which connects various parts of the entire electronic device through various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 1202, and calling data stored in the memory 1202. In some embodiments, the processor 1201 can include one or more processing cores; in some embodiments, the processor 1201 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application program, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1201.

[0345] The memory 1202 can be used to store software programs and modules, and the processor 1201 executes various functions and online conference processing by running the software programs and modules stored in the memory 1202. The memory 1202 can mainly include a program storage area and a data storage area, wherein the program storage area can store the operating system, at least one application program required by the function (such as sound playing function, image playing function, etc.), etc.; the data storage area can store data created according to the use of the electronic device, etc. In addition, the memory 1202 can include a high-speed random access memory, and can also include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory device, or other volatile solid-state memory device. Accordingly, the memory 1202 can also include a memory controller to provide access for the processor 1201 to the memory 1202.

[0346] The electronic device can further include a power supply 1203 for supplying power to each component. In some embodiments, the power supply 1203 can be logically connected to the processor 1201 through a power management system, so that the power management system can manage charging, discharging, and power consumption management, etc. The power supply 1203 can also include one or more DC or AC power sources, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, etc.

[0347] The electronic device can further include an input module 1204, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0348] The electronic device can further include a communication module 1205, which in some embodiments can include a wireless module. The electronic device can use the wireless module of the communication module 1205 for short-range wireless transmission, thereby providing the user with wireless broadband Internet access. For example, the communication module 1205 can be used to help the user send and receive emails, browse web pages, and access streaming media, etc.

[0349] Although not shown, the electronic device can also include a display unit, etc., which will not be described here. In particular, in the present embodiment, the processor 1201 in the electronic device will load one or more executable files corresponding to the processes of one or more application programs into the memory 1202 according to the following instructions, and run the application programs stored in the memory 1202 by the processor 1201, thereby implementing various functions.

[0350] The specific implementation of each of the above operations can refer to the previous embodiments, which will not be described here.

[0351] Those of ordinary skill in the art can understand that all or part of the steps of the various methods of the above embodiments can be completed by instructions, or by instructions controlling relevant hardware, which can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0352] To this end, an embodiment of the present application provides a computer-readable storage medium, which stores a plurality of instructions capable of being loaded by a processor to execute the steps in any of the online meeting processing methods provided by the embodiments of the present application.

[0353] The storage medium can include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0354] According to an aspect of the present application, a computer program product or computer program is provided, which comprises computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device performs the method provided in any of the optional implementations provided in the above embodiments.

[0355] Due to the instructions stored in the storage medium, the steps in any of the online conference processing methods provided in the embodiments of the present application can be performed, thus the beneficial effects of any of the online conference processing methods provided in the embodiments of the present application can be achieved, which are described in detail in the above embodiments and will not be repeated here.

[0356] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined target, and can be implemented entirely or partially by using software, hardware (such as a processing circuit or a memory) or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an integral module or unit that includes the functions of the module or unit.

[0357] The technical features of the above embodiments can be combined in any manner. To make the description concise, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combinations of the technical features do not exist contradictions, they should be considered as the scope of the present application.

[0358] The above embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the scope of the patent. It should be pointed out that for ordinary skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of the patent of the present application should be subject to the appended claims.

Claims

1. A method for processing an online conference, executed by an electronic device, the method comprising: obtaining session account status information, the session account status information comprising user accounts and device information of different terminal devices logged in the user accounts; integrating the same user accounts corresponding to different terminal devices into a same common account for display; and binding the device information of the different terminal devices logged in the same user accounts to the common account. 2.The method of claim 1, wherein the electronic device comprises a first terminal device, and the method further comprises: displaying the common account and user accounts that are not integrated. 3.The method of claim 1 or 2, wherein the electronic device comprises a first terminal device, and the method further comprises: displaying a session list interface; in response to a control display instruction, displaying a multi-entry control on the session list interface, the control display instruction indicating that a second terminal device joins a target multi-person session using a target user account; and in response to a triggering operation on the multi-entry control, joining the first terminal device to the target multi-person session using the target user account. 4.The method of claim 3, wherein the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface comprises a multimedia information playing area; the method further comprises: receiving video information sent by the server and displaying the video information in the multimedia information playing area; in response to an audio receiving triggering operation, sending an audio receiving request to the server, the audio receiving request being used to instruct the server to return audio information and stop sending audio information to the second terminal device; and receiving the audio information returned by the server and playing the audio information. 5.The method of claim 3, wherein the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface displays a multimedia upload control, the multimedia upload control being used to collect and transmit multimedia information; the method further comprises: in response to a triggering operation on the multimedia upload control, collecting local multimedia information by a multimedia collection tool arranged on the first terminal device; and sending the local multimedia information to the server, so that the server transmits the local multimedia information to other users participating in the target multi-person session, and so that the server disconnects the multimedia collection tool of the second terminal device. 6.The method of claim 3, wherein the target multi-person session is displayed in a multi-person session interface, and the multi-person session interface displays a session device prompt control; the method further comprises: in response to a triggering operation on the session device prompt control, displaying a session device list interface, the session device list interface being used to display device information of all terminal devices participating in the target multi-person session by the target user account. ​ ​ ​ ​ ​ In response to a triggering operation on the target terminal device, a permission prompt interface is popped up, the permission prompt interface displays a session rejection control, the target terminal device is any one of all terminal devices of the target user account participating in the target multi-person session, and the permission prompt interface is used to inquire whether to allow the target terminal device to continue participating in the target multi-person session. And In response to a triggering operation on the session rejection control, a session rejection instruction is sent to the server, so that the server controls the target user account logged in the target terminal device to exit the target multi-person session.

7. The method of any one of claims 3-5, the to-be-session list interface displays a login device prompt control; and the method further comprises: In response to a triggering operation on the login device prompt control, a login device list interface is displayed, the login device list interface is used to display state information of logged-in devices, the logged-in devices all install a session application, and the session application is logged in the target user account, the login device list interface includes a device detail control; In response to a triggering operation on the device detail control corresponding to a target logged-in device, a detailed state panel of the target logged-in device is displayed, the detailed state panel displays a session name of the target logged-in device, the detailed state panel is provided with a switching control representing switching of a device participating in a session, the target logged-in device is any logged-in device of all logged-in devices participating in a preset session group, and the preset session group is any one multi-person session group; And In response to a triggering operation on the switching control, a switching participating session device instruction is sent to the server, the session device instruction is used to instruct the server to control the target user account logged in the first terminal device to join the preset session group and control the target user account logged in the target logged-in device to exit the preset session group.

8. The method of claim 7, the detailed state panel further displays a multi-end join control representing allowing multiple devices to participate in a session; and the method further comprises: In response to a triggering operation on the multi-end join control, a multi-end session instruction is sent to the server, so that the server controls the target user account logged in the first terminal device to join the preset session group.

9. The method of any one of claims 1-8, the target user account is a user account managing the target multi-person session; and the method further comprises: In response to a setting operation representing prohibition of multiple devices participating in a session, a session permission of the target multi-person session is modified from allowing multiple devices to participate in a session to prohibiting multiple devices to participate in a session.

10. The method of claim 1, the electronic device includes a server, and the method further comprises: Receiving a session exit request sent by a terminal device, the session exit request including a user account and an identity of a terminal device logging in the user account; Controlling the terminal device corresponding to the identity to exit a target multi-person session. when there is still a terminal device logged in the user account participating in the session in the target multi-person session, maintaining the online state of the common account; and when there is no terminal device logged in the user account participating in the session in the target multi-person session, sending prompt information that the common account has left the session to all terminal devices currently participating in the session.

11. An online conference processing method, executed by a first terminal device, comprising: displaying a to-be-session list interface, the to-be-session list interface displaying a multi-entry control, wherein the to-be-session list interface displays a target multi-person session joined by a second terminal device through a target user account; and in response to a triggering operation on the multi-entry control, causing the first terminal device to enter a multi-person session interface of the target multi-person session through the target user account.

12. The method of claim 11, wherein the multi-person session interface displays a multimedia uplink control; the method further comprises: in response to a triggering operation on the multimedia uplink control, displaying a first switching prompt information in the multi-person session interface, the first switching prompt information prompting to switch a multimedia uplink function to the first terminal device; and when the multimedia uplink control located at the second terminal device is triggered, displaying a second switching prompt information in the multi-person session interface, the second switching prompt information prompting to switch the multimedia uplink function to the second terminal device.

13. The method of claim 11 or 12, wherein the to-be-session list interface further displays a logged-in device prompt control; the method further comprises: in response to a triggering operation on the logged-in device prompt control, displaying a logged-in device list interface; wherein the logged-in device list interface is used to display state information of logged-in devices, the logged-in devices all install an online conference application program, and the online conference application programs all log in the target user account.

14. The method of any one of claims 11 to 13, wherein the to-be-session list interface further displays a join conference control; the method further comprises: in response to a triggering operation on the join conference control, displaying a conference number search box; and in response to a conference number input operation on the conference number search box, when a multi-person conference corresponding to the conference number input operation has been joined by the second terminal device through the target user account, displaying a join conference prompt interface; the join conference prompt interface comprises at least one of a switch-in control, a multi-terminal participation control or a temporary non-participation control, wherein the switch-in control is used to switch a device participating in the multi-person conference to the first terminal device, the multi-terminal participation control is used to join the multi-person conference by the first terminal device, and the temporary non-participation control is used for the first terminal device to temporarily not join the multi-person conference.

15. An online conference processing apparatus, comprising: an information receiving unit, configured to acquire session account state information, the session account state information comprising a user account and device information of different terminal devices logged in the user account; ​ The account integration unit is configured to integrate the same user accounts corresponding to different terminal devices into a same common account for display. And The account binding unit is configured to bind the device information of different terminal devices logging into the same user accounts to the common account.

16. An online conference processing apparatus, the apparatus comprising: a list display unit configured to display a to-be-session list interface including a multi-entry control, wherein the to-be-session list interface displays a target multi-person session joined by a second terminal device through a target user account; and a session display unit configured to, in response to a triggering operation on the multi-entry control, cause the first terminal device to enter a multi-person session interface of the target multi-person session through the target user account.

17. An electronic device comprising a processor and a memory, the memory storing a plurality of instructions; the processor loads the instructions from the memory to perform the steps in the online conference processing method of any one of claims 1 to 14.

18. A computer-readable storage medium storing executable instructions, the executable instructions being loaded and executed by a processor to perform the steps in the online conference processing method of any one of claims 1 to 14.

19. A computer program product comprising a computer program, the computer program being executed by a processor to implement the steps in the online conference processing method of any one of claims 1 to 14.

Images