A method, client and server for controlling a conference terminal

Abstract

Embodiments of the present application provide a method for controlling a conference terminal, a client and a server, and relate to the technical field of communication. The method comprises: a first client logged in with a target user account, in response to a first obtaining operation of obtaining device identity information, obtaining device identity information of a target conference terminal, wherein a second client logged in with the device identity information is running on the target conference terminal. The first client controls the target conference terminal based on the device identity information of the target conference terminal. Therefore, the target user can install the first client in other devices to control the target conference terminal without directly operating the target conference terminal, thereby bringing convenience to the user for remote conference.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology, and in particular to a method for controlling a conference terminal, a client and a server. BACKGROUND

[0002] With the development of technology and the establishment of the concept of global village, off-site work becomes more and more common. In order to enable employees at different locations to hold a conference at the same time, a video conference system is applied. At present, participants realize remote conference by operating a conference terminal of the video conference system. However, the conference terminal is generally a large-size device, and the conference terminal is located at a fixed position in a conference room, which results in that it is not convenient for a user to operate the conference terminal. SUMMARY

[0003] Embodiments of the present application provide a method for controlling a conference terminal, a client and a server, which are used for controlling a conference terminal by a first client logged in with a target user account.

[0004] In one aspect, the present application provides a method for controlling a conference terminal, which comprises:

[0005] A first client logged in with a target user account acquires device identity information of a target conference terminal in response to a first acquisition operation of acquiring the device identity information, wherein a second client logged in with the device identity information is running on the target conference terminal;

[0006] The first client controls the target conference terminal based on the device identity information of the target conference terminal.

[0007] In one aspect, the present application provides a method for controlling a conference terminal, which comprises:

[0008] A second client receives a control instruction sent by a server, wherein the control instruction is sent by the server in response to a first acquisition operation of acquiring device identity information of a target conference terminal by a first client logged in with a target user account, and the second client is logged in with the device identity information and is running on the target conference terminal;

[0009] The second client controls the target conference terminal based on the control instruction.

[0010] Optionally, the method further comprises:

[0011] The second client receives the device identity information of the target conference terminal sent by the server, the device identity information is generated by the server according to the device information of the target conference terminal, the device information is obtained by the first client in response to a second acquisition operation of acquiring the device information of the target conference terminal, and the device information is sent to the server in response to a binding operation received through a device binding page.

[0012] Optionally, the control instruction is a first client logged in with a target user account, and the device identity information of the target conference terminal is sent to the server in response to a first acquisition operation of acquiring the device identity information, after the device identity information is acquired.

[0013] The control instruction is sent to the server by the first client in response to a first scanning operation of scanning the identity code of the target conference terminal displayed in the second client, after the device identity information is acquired.

[0014] The device information is obtained by the first client in response to a second acquisition operation of acquiring the device information of the target conference terminal.

[0015] The device information is acquired by the first client in response to a second scanning operation of scanning the device code of the target conference terminal displayed in the second client.

[0016] Optionally, the control instruction is a conference creation instruction, and the conference creation instruction is sent to the server by the first client in response to a conference creation operation received through the conference creation page, after the device identity information of the target conference terminal is acquired and the conference creation page is displayed in response to a first acquisition operation of acquiring the device identity information.

[0017] The second client controls the target conference terminal based on the control instruction, including:

[0018] The second client sends a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and displays a conference initiation page.

[0019] Optionally, the conference creation instruction includes a conference initiation account and a participant account, wherein the conference initiation account is an account of the target conference terminal, and the participant account includes a conference terminal account and / or a user account.

[0020] In one aspect, the embodiments of the present application provide a method for controlling a conference terminal, including:

[0021] The server receives a control instruction sent by a first client logged in with a target user account, the control instruction being sent by the first client in response to a first acquisition operation of acquiring device identity information of a target conference terminal, and the second client running on the target conference terminal is logged in with the device identity information;

[0022] The server sends the control instruction to the second client to control the target conference terminal based on the control instruction.

[0023] Optionally, further comprising:

[0024] The server receives the device information of the target conference terminal sent by the first client, and generates the device identity information of the target conference terminal according to the device information, the device information being acquired by the first client in response to a second acquisition operation of acquiring the device information of the target conference terminal, and sent to the server in response to a binding operation received through a device binding page;

[0025] The server sends the device identity information to the second client.

[0026] Optionally, the control instruction sent by the first client in response to the first acquisition operation of acquiring device identity information of a target conference terminal includes:

[0027] The control instruction is sent by the first client in response to a first scanning operation, and the device identity information is acquired by scanning the identity code of the target conference terminal displayed in the second client, and sent to the server; and

[0028] The device information acquired by the first client in response to the second acquisition operation of acquiring the device information of the target conference terminal includes:

[0029] The device information is acquired by the first client in response to a second scanning operation, and the device code of the target conference terminal displayed in the second client is scanned.

[0030] Optionally, the control instruction sent by the first client in response to the first acquisition operation of acquiring device identity information of a target conference terminal includes:

[0031] The server receives the conference creation instruction sent by the first client, the conference creation instruction is sent to the server by the first client in response to the first acquisition operation of acquiring the device identity information, the device identity information of the target conference terminal is acquired and a conference creation page is displayed, and the conference creation instruction is sent to the server in response to the conference creation operation received through the conference creation page;

[0032] The server sends the conference creation instruction to the second client, so that the second client sends a conference creation request to the server based on the device identity information of the target conference terminal and the conference creation instruction.

[0033] Optionally, the conference creation instruction includes a conference initiation account and a participant account, wherein the conference initiation account is an account of the target conference terminal, and the participant account includes a conference terminal account and / or a user account.

[0034] Optionally, the control instruction is sent to the server by the first client in response to the first acquisition operation of acquiring the device identity information, and includes:

[0035] The server receives the conference invitation operation instruction sent by the first client, the conference invitation operation instruction is sent to the server by the first client in response to the first acquisition operation of acquiring the device identity information, the device identity information of the target conference terminal is acquired, the conference invitation information is acquired from the second client through the server based on the device identity information of the target conference terminal, and a conference invitation operation page is generated, and the conference invitation operation instruction is sent to the server in response to the conference invitation operation received through the conference invitation operation page;

[0036] The server sends the conference invitation operation instruction to the second client, so that the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0037] Optionally, the control instruction is sent to the server by the first client in response to the first acquisition operation of acquiring the device identity information, and includes:

[0038] The server receives the conference control instruction sent by the first client, the conference control instruction is sent to the server by the first client in response to the first acquisition operation of acquiring the device identity information, the device identity information of the target conference terminal is acquired, the conference information is acquired from the second client through the server based on the device identity information of the target conference terminal, and a conference control page is generated, and the conference control instruction is sent to the server in response to the conference control operation received through the conference control page;

[0039] The server sends the conference control instruction to the second client, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0040] In an aspect, an embodiment of the present application provides a first client, comprising:

[0041] A first processing module, configured to acquire device identity information of a target conference terminal in response to a first acquisition operation of acquiring device identity information, wherein the second client logged in with the device identity information runs on the target conference terminal, and the first client is a client logged in with a target user account;

[0042] A first control module, configured to control the target conference terminal based on the device identity information of the target conference terminal.

[0043] Optionally, the first processing module is further configured to:

[0044] acquire device information of the target conference terminal in response to a second acquisition operation of acquiring device information of the target conference terminal, before acquiring the device identity information of the target conference terminal in response to the first acquisition operation of acquiring device identity information.

[0045] display a device binding page, and send the device information to a server in response to a binding operation received through the device binding page, so that the server generates the device identity information according to the device information, and sends the device identity information to the second client.

[0046] Optionally, the first processing module is specifically configured to:

[0047] acquire the device identity information in response to a first code scanning operation, and scan an identity code of the target conference terminal displayed in the second client; and

[0048] acquire the device information in response to a second code scanning operation, and scan a device code of the target conference terminal displayed in the second client.

[0049] Optionally, the first control module is specifically configured to:

[0050] display a conference creation page, and send a conference creation instruction to the second client through a server in response to a conference creation operation received through the conference creation page, so that the second client sends a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and displays a conference initiation page.

[0051] Optionally, the conference creation instruction comprises a conference initiator account and a participant account, wherein the conference initiator account is an account of the target conference terminal, and the participant account comprises a conference terminal account and / or a user account.

[0052] Optionally, the first control module is specifically configured to:

[0053] acquire, based on the device identity information of the target conference terminal, conference invitation information from the second client through a server;

[0054] display a conference invitation operation page, and in response to a conference invitation operation received through the conference invitation operation page, send a conference invitation operation instruction to the second client through the server, so that the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0055] Optionally, the first control module is specifically configured to:

[0056] acquire, based on the device identity information of the target conference terminal, conference information from the second client through a server;

[0057] display a conference control page, and in response to a conference control operation received through the conference control page, send a conference control instruction to the second client through the server, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0058] In one aspect, an embodiment of the present application provides a second client, comprising:

[0059] a first receiving module configured to receive a control instruction sent by a server, the control instruction being sent by a first client logged in with a target user account in response to a first acquisition operation of acquiring device identity information, the device identity information of a target conference terminal being acquired and sent to the server by a second client running on the target conference terminal and logged in with the device identity information;

[0060] a second control module configured to control the target conference terminal based on the control instruction.

[0061] Optionally, the first receiving module is further configured to:

[0062] receive the device identity information of the target conference terminal sent by the server, the device identity information being generated by the server according to device information of the target conference terminal, the device information being obtained by the first client in response to a second acquisition operation of acquiring the device information of the target conference terminal, and the device information being sent to the server in response to a binding operation received through a device binding page.

[0063] Optionally, the control instruction is a device identity information sent to the server by the first client in response to a first code scanning operation of scanning an identity code of the target conference terminal displayed in the second client after the device identity information is acquired.

[0064] The device information is acquired by the first client in response to a second code scanning operation of scanning a device code of the target conference terminal displayed in the second client.

[0065] Optionally, the control instruction is a conference creation instruction, and the conference creation instruction is a device identity information of the target conference terminal acquired by the first client in response to a first acquisition operation of acquiring the device identity information and displayed on a conference creation page, and is sent to the server in response to a conference creation operation received through the conference creation page.

[0066] The second control module is specifically configured to:

[0067] send a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and display a conference initiation page.

[0068] Optionally, the conference creation instruction includes a conference initiation account and a participant account, the conference initiation account is an account of the target conference terminal, and the participant account includes a conference terminal account and / or a user account.

[0069] Optionally, the control instruction is a conference invitation operation instruction, and the conference invitation operation instruction is a device identity information of the target conference terminal acquired by the first client in response to a first acquisition operation of acquiring the device identity information, and is sent to the server in response to a conference invitation operation received through a conference invitation operation page generated by the server from the second client based on the device identity information of the target conference terminal.

[0070] The second control module is specifically configured to:

[0071] send a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0072] Optionally, the control instruction is a conference control instruction, and the conference control instruction is obtained by the first client in response to a first obtaining operation of obtaining device identity information, obtaining device identity information of a target conference terminal, obtaining conference information from the second client through the server based on the device identity information of the target conference terminal, and generating a conference control page, and the conference control instruction is sent to the server in response to a conference control operation received through the conference control page.

[0073] The second control module is specifically configured to:

[0074] send a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0075] In one aspect, an embodiment of the present application provides a server, comprising:

[0076] The second receiving module is configured to receive a control instruction sent by a first client logged in with a target user account, and the control instruction is sent to the server by the first client in response to a first obtaining operation of obtaining device identity information, obtaining device identity information of the target conference terminal, and running a second client logged in with the device identity information on the target conference terminal.

[0077] The second processing module is configured to send the control instruction to the second client, so that the second client controls the target conference terminal based on the control instruction.

[0078] Optionally, the second receiving module is further configured to:

[0079] receive device information of the target conference terminal sent by the first client, and generate device identity information of the target conference terminal according to the device information, and the device information is obtained by the first client in response to a second obtaining operation of obtaining device information of the target conference terminal, and is sent to the server in response to a binding operation received through a device binding page;

[0080] The second processing module is further configured to:

[0081] send the device identity information to the second client.

[0082] Optionally, the control instruction is sent to the server by the first client in response to a first scanning operation of scanning identity code of the target conference terminal displayed in the second client to obtain the device identity information; and

[0083] The device information is obtained by the first client in response to a second scanning operation of scanning device code of the target conference terminal displayed in the second client.

[0084] Optionally, the second receiving module is further configured to:

[0085] receive the conference creation instruction sent by the first client, the conference creation instruction being sent by the first client in response to a first acquisition operation of acquiring device identity information, acquiring device identity information of a target conference terminal, and displaying a conference creation page, and being sent to the server in response to a conference creation operation received through the conference creation page;

[0086] The second processing module is further configured to:

[0087] send the conference creation instruction to the second client, so that the second client sends a conference creation request to the server based on the device identity information of the target conference terminal and the conference creation instruction.

[0088] Optionally, the conference creation instruction includes a conference initiator account and a participant account, wherein the conference initiator account is an account of the target conference terminal, and the participant account includes a conference terminal account and / or a user account.

[0089] Optionally, the second receiving module is further configured to:

[0090] receive the conference invitation operation instruction sent by the first client, the conference invitation operation instruction being sent by the first client in response to a first acquisition operation of acquiring device identity information, acquiring device identity information of a target conference terminal, acquiring conference invitation information from the second client through the server based on the device identity information of the target conference terminal, and generating a conference invitation operation page, and being sent to the server in response to a conference invitation operation received through the conference invitation operation page;

[0091] The second processing module is further configured to:

[0092] send the conference invitation operation instruction to the second client, so that the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0093] Optionally, the second receiving module is further configured to:

[0094] receive the conference control instruction sent by the first client, the conference control instruction being sent by the first client in response to a first acquisition operation of acquiring device identity information, acquiring device identity information of a target conference terminal, acquiring conference information from the second client through the server based on the device identity information of the target conference terminal, and generating a conference control page, and being sent to the server in response to a conference control operation received through the conference control page;

[0095] The second processing module is further configured to:

[0096] send the conference control instruction to the second client, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0097] In an aspect, the embodiments of the present application provide a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method for controlling a conference terminal when executing the program.

[0098] In an aspect, the embodiments of the present application provide a computer readable storage medium, which stores a computer program executable by a computer device, and when the program is executed on the computer device, the computer device executes the steps of the method for controlling a conference terminal.

[0099] In the embodiments of the present application, the first client logged in with the target user account acquires the device identity information of the target conference terminal, and controls the target conference terminal based on the device identity information of the target conference terminal, so that the target user can install the first client in other devices to control the target conference terminal, without directly operating the target conference terminal, thereby bringing convenience to the user for remote conference. BRIEF DESCRIPTION OF DRAWINGS

[0100] 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. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0101] Figure 1 A system architecture diagram applicable to the embodiments of the present application;

[0102] Figure 2 A flowchart of a method for controlling a conference terminal provided by the embodiments of the present application;

[0103] Figure 3 A schematic diagram of an identity two-dimensional code of a conference terminal provided by the embodiments of the present application;

[0104] Figure 4a An interface schematic diagram of a first client provided by the embodiments of the present application;

[0105] Figure 4b A schematic diagram of a two-dimensional code scanning page in the first client provided by the embodiments of the present application;

[0106] Figure 5 A flowchart of binding a target conference terminal provided for an embodiment of the present application is shown in FIG. 2;

[0107] Figure 6 A schematic diagram of a device two-dimensional code of a conference terminal provided for an embodiment of the present application is shown in FIG. 3;

[0108] Figure 7 A schematic diagram of a device binding page provided for an embodiment of the present application is shown in FIG. 4;

[0109] Figure 8a A schematic diagram of a binding success page provided for an embodiment of the present application is shown in FIG. 5;

[0110] Figure 8b A schematic diagram of a binding failure page provided for an embodiment of the present application is shown in FIG. 6;

[0111] Figure 9 A flowchart of a conference terminal initiating a conference provided for an embodiment of the present application is shown in FIG. 7;

[0112] Figure 10 A schematic diagram of a conference creation page provided for an embodiment of the present application is shown in FIG. 8;

[0113] Figure 11 A schematic diagram of a participant account selection page provided for an embodiment of the present application is shown in FIG. 9;

[0114] Figure 12 A schematic diagram of a participant selection page provided for an embodiment of the present application is shown in FIG. 10;

[0115] Figure 13 A schematic diagram of a conference device selection page provided for an embodiment of the present application is shown in FIG. 11;

[0116] Figure 14 A schematic diagram of a conference initiation page displayed by a first client provided for an embodiment of the present application is shown in FIG. 12;

[0117] Figure 15 A schematic diagram of a conference initiation page displayed by a second client provided for an embodiment of the present application is shown in FIG. 13;

[0118] Figure 16 A flowchart of a conference terminal processing a conference invitation provided for an embodiment of the present application is shown in FIG. 14;

[0119] Figure 17 A schematic diagram of a conference invitation page provided for an embodiment of the present application is shown in FIG. 15;

[0120] Figure 18 A schematic diagram of a conference invitation operation page provided for an embodiment of the present application is shown in FIG. 16;

[0121] Figure 19 A schematic diagram of a conference control page provided for an embodiment of the present application is shown in FIG. 17;

[0122] Figure 20 a conference page provided by the embodiment of the present application;

[0123] Figure 21 a flowchart of a conference terminal controlling a conference process provided by the embodiment of the present application;

[0124] Figure 22 a conference control page provided by the embodiment of the present application;

[0125] Figure 23 a flowchart of binding a target conference terminal provided by the embodiment of the present application;

[0126] Figure 24 a flowchart of a conference terminal initiating a conference provided by the embodiment of the present application;

[0127] Figure 25 a flowchart of a conference terminal processing a conference invitation provided by the embodiment of the present application;

[0128] Figure 26 a flowchart of a conference terminal controlling a conference process provided by the embodiment of the present application;

[0129] Figure 27 a structure diagram of a first client provided by the embodiment of the present application;

[0130] Figure 28 a structure diagram of a second client provided by the embodiment of the present application;

[0131] Figure 29 a structure diagram of a server provided by the embodiment of the present application;

[0132] Figure 30 a structure diagram of a computer device provided by the embodiment of the present application. DETAILED DESCRIPTION

[0133] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application.

[0134] In order to facilitate understanding, the terms involved in the embodiments of the present application are explained below.

[0135] Cloud technology: the general term of network technology, information technology, integration technology, management platform technology, application technology based on cloud computing business model, which can form a resource pool, use on demand, flexible and convenient. Cloud computing technology will become an important support. The background service of the technical network system needs a large amount of computing and storage resources, such as video websites, picture websites and more portals. With the high development and application of the Internet industry, every item may have its own identification mark in the future, and it needs to be transmitted to the background system for logical processing. Different levels of data will be processed separately, and various industry data will need strong system support, which can only be realized through cloud computing.

[0136] Cloud meeting: cloud meeting is a kind of efficient, convenient and low-cost meeting form based on cloud computing technology. Users only need to use the Internet interface and simple operation to quickly and efficiently share voice, data files and video with teams and customers around the world, and the complex technology of data transmission and processing in the meeting is operated by cloud meeting service providers. At present, the domestic cloud meeting mainly focuses on the service content of SaaS (Software as a Service) mode, including telephone, network, video and other service forms. The video conference based on cloud computing is called cloud meeting. For example, the multi-person voice or video conference in the embodiment of the application can be based on cloud computing.

[0137] In the cloud meeting era, data transmission, processing and storage are all handled by computer resources of video conference manufacturers, and users no longer need to purchase expensive hardware and install cumbersome software. They only need to open a browser and log in to the corresponding interface to conduct efficient remote meetings.

[0138] The cloud meeting system supports multi-server dynamic cluster deployment and provides multiple high-performance servers, which greatly improves the stability, security and availability of the meeting. In recent years, video conferences have been widely used in transportation, transportation, finance, operators, education, enterprises and other fields because they can greatly improve communication efficiency, continuously reduce communication costs and upgrade internal management levels. There is no doubt that video conferences using cloud computing have stronger appeal in convenience, speed and ease of use, and will stimulate a new high tide of video conference applications. For example, the video conference system in the embodiment of the application can be a cloud meeting system.

[0139] Instant messaging (Instant Messaging, IM for short): is the process of sending and receiving instant messages between mobile terminals, tablet computers and computer users using the network. Instant messaging can transmit text, pictures, even voice and video, share web links, and improve the communication efficiency between people.

[0140] Instant messaging application: an application software developed based on instant messaging technology, which is a social application capable of transmitting text, pictures, even voice and video, and sharing web links. According to the platform, organization or individual user, it can be divided into application and individual instant messaging application. Application can be understood as the instant messaging application used by enterprise, company, specific group or specific organization. The application can manage each team member in the team, and can also send management information to each team member. Individual instant messaging application refers to the instant messaging application used by individual user. Individual user can use the individual instant messaging application to transmit information with other individual users, or transmit information with members or groups in the application through the individual instant messaging application.

[0141] The design idea of the embodiments of the present application is introduced as follows.

[0142] At present, the participants realize remote conference by operating in the conference terminal of the video conference system, for example, the user can initiate video or voice conference through the conference terminal, or can answer the video or voice conference through the conference terminal. However, the conference terminal is generally a large-size device, and the conference terminal is located at a fixed position in the conference room, for example, the conference terminal is a large-size tablet computer, which can be fixed on the wall of the conference room. When the user needs to have remote conference, the user needs to go to the fixed position to operate the conference terminal, which brings inconvenience to the user.

[0143] Considering that the mobile phone and other user terminals are commonly used and carried by users, if the user controls the conference terminal to have remote conference by using the mobile phone and other devices, it will bring convenience to the user to have remote conference. Therefore, in the embodiments of the present application, a method for controlling conference terminal is provided, which comprises: installing a first client on a user terminal, and logging in the first client by a target user using a registered target user account. The first client acquires the device identity information of the target conference terminal in response to a first acquisition operation of acquiring device identity information, wherein a second client logged in with the device identity information is running on the target conference terminal. The first client controls the target conference terminal based on the device identity information of the target conference terminal.

[0144] In the embodiments of the present application, the first client logged in with the target user account acquires the device identity information of the target conference terminal, and controls the target conference terminal based on the device identity information of the target conference terminal. Therefore, the target user can install the first client in other devices to control the target conference terminal, without directly operating in the target conference terminal, thereby bringing convenience to the user to have remote conference.

[0145] The system architecture diagram to which the method for controlling conference terminal in the embodiments of the present application is applied is exemplarily introduced as follows, with reference to Figure 1Fig. 1 is a system architecture diagram applicable to an embodiment of the present application, which includes at least a user terminal 101, a conference terminal 102, and a server 103.

[0146] The first client can be installed on the user terminal 101, which can be a pre-installed client, a web-based client, or a mini-program client, etc. The first client is a client of an instant communication application, which can be a personal instant communication application or a team instant communication application. A target user inputs user basic information and a team identifier in the first client to register a user account, and the first client sends a registration request to the server 103 through the user terminal 101, which includes the user basic information and the team identifier. The server 103 binds the user basic information and the team identifier to generate a target user account and sends a registration response message to the first client. The target user logs in the first client by using the registered target user account. The user terminal 101 can include one or more processors 1011, a memory 1012, an I / O interface 1013 for interacting with the server 103, a display panel 1014, etc. The user terminal 101 can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto.

[0147] The second client can be pre-installed, a web client or an applet client, etc. The second client is a client of an instant messaging application, which can be a personal instant messaging application or a team instant messaging application. The second client sends the device information of the conference terminal 102 to the server 103 through the conference terminal 102, the server 103 generates the device code of the conference terminal 102 according to the device information of the conference terminal 102 and sends the device code to the second client, and the second client displays the device code. The target user inputs a code scanning operation in the first client, the first client responds to the code scanning operation, calls the camera of the user terminal 101, scans the device code of the conference terminal 102 displayed by the second client, and obtains the device information of the conference terminal 102. The first client generates a device binding page according to the device information of the conference terminal 102 and displays the device binding page, and receives the binding operation of the target user through the device binding page. The first client responds to the binding operation of the target user and sends the device information of the conference terminal 102 to the server 103. The server 103 generates the device identity information of the conference terminal 102 according to the device information of the conference terminal 102 and sends the device identity information to the second client. The second client is logged in with the device identity information, and after successful login, the second client displays the identity code of the conference terminal 102. The conference terminal 102 can include one or more processors 1021, a memory 1022, an I / O interface 1023 for interacting with the server 103, and a display panel 1024, etc. The conference terminal 102 can be a tablet computer, a notebook computer, a desktop computer, a television, etc., but is not limited thereto.

[0148] Server 103 is a backend server providing services to both the first and second clients. The target user inputs a QR code scan operation in the first client. The first client responds by calling the camera of user terminal 101 to scan the identity code of conference terminal 102 displayed on the second client, obtaining the device identity information of conference terminal 102. Based on the device identity information of conference terminal 102, the first client controls conference terminal 102. Server 103 may include one or more processors 1031, memory 1032, and I / O interfaces 1033 for interacting with user terminal 101 and conference terminal 102. Furthermore, server 103 may be configured with a database 1034. Server 103 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms. User terminal 101, conference terminal 102 and server 103 can be connected directly or indirectly through wired or wireless communication, and this application does not impose any restrictions on this.

[0149] based on Figure 1 The system architecture diagram shown in this application illustrates a flowchart of a method for controlling a conference terminal. Figure 2 As shown, the process of this method can be executed by a first client, a second client, and a server. The method includes the following steps:

[0150] Step S201: The first client, logged in with the target user account, responds to the first acquisition operation to obtain device identity information and obtains the device identity information of the target conference terminal.

[0151] Specifically, the first client can be a pre-installed client, a web-based client, or a mini-program client, etc. After registering a target user account in the first client, the target user can log in using the registered target user account. When the first client is a team instant messaging application client, the target user account is bound to a team identifier entered by the target user, which can be a company name, club name, school name, etc. The first acquisition operation can be scanning a QR code, taking a photo, recording audio, etc.

[0152] The second client logs in on the target conference terminal with the device identity information, specifically, the target conference terminal pre-installs the second client, the second client registers the target conference terminal by obtaining device information of the target conference terminal, obtains the device identity information of the target conference terminal, and then logs in the second client with the device identity information. The second client can be a pre-installed client, a web-based client, a mini-program client, etc. The device identity information of the target conference terminal can be displayed in the second client in the form of an identity code, characters, numbers, etc., wherein the identity code can be a two-dimensional code, a bar code, etc.

[0153] In step S202, the first client sends a control instruction to the server based on the device identity information of the target conference terminal.

[0154] In step S203, the server sends the control instruction to the second client.

[0155] In step S204, the second client controls the target conference terminal based on the control instruction.

[0156] In specific implementation, the second client can control the remote conference function of the target conference terminal based on the control instruction, and can also control the start and shutdown functions of the target conference terminal. The remote conference includes voice conference, video conference, etc., and the first client controlling the remote conference function of the target conference terminal includes initiating a remote conference, answering a remote conference, ending a remote conference, and controlling a conference in the middle of the conference, etc.

[0157] In the embodiments of the present application, the first client logged in with the target user account obtains the device identity information of the target conference terminal, and controls the target conference terminal based on the device identity information of the target conference terminal, so the target user can install the first client in other devices to control the target conference terminal, without directly operating on the target conference terminal, thereby bringing convenience to the user for remote conference.

[0158] Optionally, in the above step 201, when the first acquisition operation is a code scanning operation, and the device identity information of the target conference terminal is displayed in the second client in the form of an identity code, the method for the first client to obtain the device identity information of the target conference terminal is specifically as follows:

[0159] The first client scans the identity code of the target conference terminal displayed in the second client in response to the first code scanning operation, and obtains the device identity information.

[0160] Exemplarily, the identity code is an identity two-dimensional code, and the identity two-dimensional code of the target conference terminal displayed in the second client is as shown in 301 of Figure 3 The target user clicks the "scan" button in the first client, specifically as shown in 302 of Figure 4aThe first client calls the camera of the user terminal, displays a two-dimensional code scanning page, and the two-dimensional code scanning page is as shown in FIG. 4A. Figure 4b The target user scans the identity two-dimensional code displayed in the second client by aligning the two-dimensional code scanning frame 401 displayed in the two-dimensional code scanning page with the identity two-dimensional code displayed in the second client, and obtains the device identity information of the target conference terminal.

[0161] In the embodiment of the application, the device identity information of the conference terminal is displayed in the second client in the form of an identity code, and the target user can obtain the device identity information of the target conference terminal by performing a code scanning operation on the identity code displayed in the second client by using the first client, thereby bringing convenience to the target user in operating the target conference terminal.

[0162] Optionally, in step 201, the device identity information of the target conference terminal is generated when the target conference terminal is registered, as shown in FIG. 4B. Figure 5 The method comprises the following steps:

[0163] In step S501, the first client obtains the device information of the target conference terminal in response to a second obtaining operation of obtaining the device information of the target conference terminal.

[0164] Specifically, the device information can be a device unique identification code, a MAC address, a hard disk identification, etc., and the second obtaining operation can be a code scanning operation, a photographing operation, a recording operation, etc.

[0165] In step S502, the first client displays a device binding page.

[0166] Specifically, after obtaining the device information of the target conference terminal, the first client generates and displays a device binding page based on the device information.

[0167] In step S503, the first client sends the device information of the target conference terminal to the server in response to a binding operation received through the device binding page.

[0168] Specifically, the binding operation is used to bind the target conference terminal and the target user account in the same team, i.e., the team identifiers are the same. The binding operation input by the target user in the binding page includes remarking the name of the target conference terminal, setting an administrator, setting a matched application, etc. The first client sends the device information to the server, and at the same time, sends the information input by the target user in the device binding page to the server with the team identifier of the target user account binding.

[0169] In step S504, the server generates the device identity information of the target conference terminal according to the device information of the target conference terminal.

[0170] Specifically, the server binds the target conference terminal as a team member to the team corresponding to the target user. The server can generate the device identity information of the target conference terminal based on the device information and the team identifier bound to the target user account, or it can generate the device identity information of the target conference terminal based on the device information, the team identifier bound to the target user account, and the information entered by the target user on the device binding page.

[0171] In step S505, the server sends the device identity information of the target conference terminal to the second client.

[0172] Specifically, the server sends the device identity information to the second client, which then logs in using the device identity information. In practice, the second client sends a login request carrying the device identity information to the server. The server verifies the device identity information, and upon successful verification, generates an identity code for the target conference terminal and sends the identity code to the second client, which then displays the target conference terminal's identity code.

[0173] Optionally, in step S501 above, when the second acquisition operation is a QR code scanning operation and the device information of the target conference terminal is displayed in the form of a device code on the second client, the method for the first client to acquire the device information of the target conference terminal specifically includes: the first client responds to the second QR code scanning operation, scans the device code of the target conference terminal displayed in the second client, and acquires the device information.

[0174] In practice, the device code can be a barcode, QR code, etc.

[0175] For example, the device code is set to a device QR code, and the device QR code of the target conference terminal displayed in the second client is as follows: Figure 6 As shown in step 601. The target user clicks the "Scan" button in the first client, specifically as follows: Figure 4a As shown in the image. The first client accesses the user terminal's camera to display a QR code scanning page, specifically as follows: Figure 4b As shown. The target user aligns the QR code scanning box 401 displayed on the QR code scanning page with the device QR code displayed on the second client, scans the device QR code displayed on the second client, and obtains device information.

[0176] After obtaining the device information of the target conference terminal, the first client displays the device binding page, as shown below. Figure 7 As shown in the image. The device binding page displays the target conferencing terminal as "XX Video Conferencing Tablet". The target user can add a note on the device binding page, naming the target conferencing terminal "1901 Meeting Room Conferencing Hardware", setting the associated application to "Conferencing", and then clicking the "Bind Device" button. The first client displays a successful binding page, as shown in the image. Figure 8aThe name of the target conference terminal, the administrator, the supporting application, and the introduction of the target conference terminal are displayed in the binding success page. The target user can also click the "remove device" button in the binding success page to remove the binding of the target conference terminal. When the name is not noted in the device binding page, if the target user clicks the "OK" button, the second client displays a binding failure page, as shown in Figure 8a The "remove device" button in the binding success page is clicked to remove the binding of the target conference terminal. When the name is not noted in the device binding page, if the target user clicks the "OK" button, the second client displays a binding failure page, as shown in Figure 8b As shown in the binding failure page, "no note name is input, please fill in again" is displayed.

[0177] In the embodiments of the present application, the device information of the conference terminal is displayed in the second client in the form of a device code. The target user can obtain the device information of the target conference terminal by using the first client to perform a code scanning operation on the device code displayed by the second client, thereby bringing convenience to the target user in binding the target conference terminal.

[0178] Optionally, in the above steps S202 to S204, when the first client controls the target conference terminal based on the device identity information of the target conference terminal, the embodiments of the present application at least provide the following several implementation manners:

[0179] One possible implementation manner is that the control instruction is a conference creation instruction, as shown in Figure 9 The conference creation page includes the following steps:

[0180] Step S901, the first client displays a conference creation page and responds to a conference creation operation received through the conference creation page.

[0181] Specifically, the first client responds to the first code scanning operation, scans the identity code of the target conference terminal displayed in the second client, obtains the device identity information of the target conference terminal, and generates a conference creation page based on the device identity information of the target conference terminal. The conference creation operation includes selecting a participating account, setting a conference name, and clicking a "conference initiation button", etc., wherein the participating account includes a conference terminal account and / or a user account.

[0182] Step S902, the first client sends a conference creation instruction to the server.

[0183] Specifically, the first client sends the conference creation instruction to the server through a c2c message protocol, and the conference creation instruction includes a conference initiation account and a participating account, wherein the conference initiation account is the account of the target conference terminal, and the participating account includes a conference terminal account and / or a user account.

[0184] Step S903, the server sends the conference creation instruction to the second client.

[0185] Specifically, the server sends the conference creation instruction to the second client through the c2c message protocol.

[0186] At step S904, the second client sends a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and displays a conference initiation page.

[0187] Specifically, after receiving the conference initiation request, the server sends the conference initiation request to the client logged in by the participant account in the conference creation instruction. The client logged in by the participant account can be a client installed on a user terminal or a client installed on a conference terminal. After receiving the conference initiation request, the client logged in by the participant account displays a conference invitation page.

[0188] For example, in response to the first scanning operation, the first client scans the identity code of the target conference terminal displayed in the second client, obtains the device identity information of the target conference terminal, and displays a conference creation page, as shown in Figure 10 The conference creation page displays the conference device for initiating the conference as “1901 conference room conference hardware”, and displays two buttons of “voice conference” and “video conference” for the target user to select. When the target user clicks the “video conference” button, the first client displays a participant account selection page, as shown in Figure 11 The participant account selection page includes a button for adding participants and a button for adding conference devices.

[0189] When the target user clicks the button for adding participants, the first client displays a participant selection page, as shown in Figure 12 The participant selection page displays a team directory and a group, and the target user can select participants from the team directory or the group. When the target user clicks the button for adding conference devices, the first client displays a conference device selection page, as shown in Figure 13 The conference device selection page displays a conference device list, and the conference device list includes 1801 conference room conference hardware, 1701 conference room conference hardware, and 1602 conference room conference hardware. The target user can select conference devices participating in the conference from the conference device list.

[0190] If the target user selects Zhang San, Li Si, and Wang Wu as participants in the participant selection page as shown in Figure 12 and selects “1801 conference room conference hardware” as the conference device participating in the conference in the conference device selection page as shown in Figure 13 the first client displays a conference initiation page, as shown in Figure 14The conference initiation page is shown in FIG. 16. The conference initiation page displays the conference initiation account "1901 conference room conference hardware", the participants selected by the target user, and the conference device. When the target user clicks the "initiate conference" button, the first client sends a conference creation instruction to the server, and the server sends the conference creation instruction to the second client. The second client sends a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and displays the conference initiation page. The second client displays the conference initiation page as shown in FIG. 16. Figure 15

[0191] In the embodiments of the present application, the first client controls the target conference terminal to initiate a remote conference based on the device identity information of the target conference terminal, and the participant account can be a conference terminal account or a user account. Therefore, the user can have a remote conference with the conference terminal even if the user is not in the conference room, thereby expanding the application range of the remote conference.

[0192] In a possible implementation, the control instruction is a conference invitation operation instruction, as shown in FIG. 16, including the following steps: Figure 16

[0193] Step S1601, the first client sends a conference invitation information acquisition request to the server based on the device identity information of the target conference terminal.

[0194] Specifically, when the target conference terminal is a conference device participating in the conference but not a conference device initiating the conference, after receiving the conference initiation request sent by the server, the target conference terminal displays a conference invitation page and displays the identity code of the target conference terminal in the conference invitation page. The first client scans the identity code of the target conference terminal displayed in the second client in response to the first scanning operation, acquires the device identity information of the target conference terminal, and then sends a conference invitation information acquisition request to the server based on the device identity information of the target conference terminal. Optionally, the first client sends the conference invitation information acquisition request to the server through the c2c message protocol.

[0195] Step S1602, the server sends the conference invitation information acquisition request to the second client.

[0196] Specifically, the server sends the conference invitation information acquisition request to the second client through the c2c message protocol.

[0197] Step S1603, the second client sends the conference invitation information to the server.

[0198] Step S1604, the server sends the conference invitation information to the first client.

[0199] Specifically, the second client sends the conference invitation information to the server through the c2c message protocol, and the server sends the conference invitation information to the first client through the c2c message protocol.​​

[0200] In step S1605, the first client displays a conference invitation operation page.

[0201] In step S1606, the first client sends a conference invitation operation instruction to the server in response to the conference invitation operation received through the conference invitation operation page.

[0202] In a specific implementation, the conference invitation operation page includes a conference initiator account, a participant account, a join button, a reject button, and the like. The conference invitation operation can be a join operation or a reject operation. When the target user clicks the join button, the first client sends a conference join instruction to the server. When the target user clicks the reject button, the first client sends a conference reject instruction to the server.

[0203] In step S1606, the server sends the conference invitation operation instruction to the second client.

[0204] In step S1607, the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0205] Specifically, when the conference invitation operation instruction is the conference join instruction, the second client sends a join conference request to the server. The second client displays a conference page and displays the identity code of the target conference terminal in the conference page. When the conference invitation operation instruction is the conference reject instruction, the second client sends a reject conference request to the server. The second client displays a conference end page and displays the identity code of the target conference terminal in the conference end page.

[0206] By way of example, when the target conference terminal is set as a conference device participating in a conference instead of a conference device initiating a conference, the target conference terminal displays a conference invitation page and displays the identity code of the target conference terminal in the conference invitation page after receiving the conference initiation request sent by the server. The conference invitation page is shown in FIG. 8. Figure 17 The conference invitation page displays “Zhang San invites you to enter a video conference”, a moderator: Zhang San, a participant: 10, a join button, a reject button, and the identity code of the target conference terminal.

[0207] After the first client scans the identity code of the target conference terminal displayed in the second client in response to the first scan code operation and obtains the device identity information of the target conference terminal, the conference invitation operation page displayed by the first client is shown in FIG. 9. The conference invitation operation page displays “Zhang San invites you to enter a video conference”, a moderator: Zhang San, a participant: 10, a join button, and a reject button. Figure 18

[0208] ​When the target user clicks the "answer" button in the conference invitation operation page, the first client displays a conference control page, as shown in Figure 19 The conference control page includes a conference initiator, a conference participant, a conference device, and "mute" buttons, "close camera" buttons, "document presentation" buttons, "select screen picture" buttons, and "end" buttons, and the like. The second client displays a conference page, as shown in Figure 20 The conference page includes a conference initiator, a conference participant, and an identity code of the target conference terminal.

[0209] In the embodiments of the present application, the first client controls the target conference terminal to answer or reject the remote conference based on the device identity information of the target conference terminal, so that the user can install the first client on the user terminal and operate on the user terminal, thereby facilitating the user to answer or reject the remote conference.

[0210] In a possible implementation, the control instruction is a conference control instruction, as shown in Figure 21 The conference control instruction includes the following steps:

[0211] In step S2101, the first client sends a conference information acquisition request to the server based on the device identity information of the target conference terminal.

[0212] Specifically, after the remote conference is answered, the second client displays a conference page and displays the identity code of the target conference terminal in the conference page. The first client scans the identity code of the target conference terminal displayed in the conference page in response to the first scanning operation, acquires the device identity information of the target conference terminal, and then sends a conference information acquisition request to the server based on the device identity information of the target conference terminal. Optionally, the first client sends the conference information acquisition request to the server through a c2c message protocol.

[0213] In step S2102, the server sends the conference information acquisition request to the second client.

[0214] Specifically, the server sends the conference information acquisition request to the second client through a c2c message protocol.

[0215] In step S2103, the second client sends the conference information to the server.

[0216] In step S2104, the server sends the conference information to the first client.

[0217] Specifically, the second client sends the conference information to the server through a c2c message protocol, and the server sends the conference information to the first client through a c2c message protocol.

[0218] In step S2105, the first client displays a conference control page.

[0219] Step S2106, the first client sends a conference control instruction to the server in response to the conference control operation received through the conference control page.

[0220] In specific implementation, the conference control page includes a conference initiator account, a participant account, a "mute" button, a "close camera" button, a "document presentation" button, a "select screen picture" button, an "end" button, an "invite participant account" button, etc. The conference control operation can be clicking each control button in the conference control page.

[0221] Step S2107, the server sends the conference control instruction to the second client.

[0222] Step S2108, the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0223] In specific implementation, when the conference control operation input by the target user in the conference control page is different, the corresponding conference control instruction is also different.

[0224] Exemplarily, the second client displays a video conference page, as shown in Figure 20 The video conference page includes video pictures of the conference initiator and the participant and the identity code of the target conference terminal. The first client scans the identity code of the target conference terminal displayed in the video conference page in response to the first scanning operation, and obtains the device identity information of the target conference terminal. Then, the first client displays a conference control page, as shown in Figure 19 The conference control page includes the conference initiator, the participant, the conference device, and the "mute" button, the "close camera" button, the "document presentation" button, the "select screen picture" button, the "end" button, etc.

[0225] When the target user clicks the "close camera" button in the conference control page, the second client displays a voice conference interface, and the video pictures of the conference initiator and the participant in the video conference page are hidden in the voice conference interface.

[0226] When the target user clicks the "end" button in the conference control page, the conference control page displays a "quit conference" button and an "end conference" button, as shown in Figure 22 When the target user clicks the "quit conference" button, the target conference terminal exits the video conference, and the second client displays a conference end page, which displays the identity code of the target conference terminal. When the target user clicks the "end conference" button, the clients corresponding to the conference initiator account and the participant account both exit the video conference, and the second client displays the conference end page, which displays the identity code of the target conference terminal.

[0227] In the embodiment of the application, the first client controls the target conference terminal by scanning the identity code of the target conference terminal in the middle of the conference, so that the user can install the first client on the user terminal and control the conference equipment flexibly through the first client.

[0228] To better explain the embodiment of the application, the flow of the method for controlling the conference terminal provided by the embodiment of the application is described below in combination with a specific implementation scenario. The flow of the method can be executed by the first client, the second client and the server. First, the registration flow of the conference terminal is introduced, as shown in the following table. Figure 23

[0229] In step S2301, the conference terminal starts the second client.

[0230] In step S2302, the second client sends the device information of the conference terminal to the server.

[0231] The device information is a device unique identification code.

[0232] In step S2303, the server sends the device two-dimensional code of the conference terminal to the second client.

[0233] In step S2304, the second client displays the device two-dimensional code of the conference terminal.

[0234] In step S2305, the first client scans the device two-dimensional code displayed by the second client in response to the code scanning operation of the user, and obtains the device information of the conference terminal.

[0235] The first client is a client logged in with a target user account, and the first client is pre-installed on a mobile phone.

[0236] In step S2306, the first client sends a binding request to the server in response to the binding operation received through the device binding page.

[0237] The binding operation input by the target user in the binding page includes remarking the name of the conference terminal, setting an administrator, setting a matching application, etc. The binding request includes the device information, the information input by the target user in the device binding page and the team identification bound with the target user account.

[0238] In step S2307, the server binds the conference terminal as a team member under the team corresponding to the target user, and allocates device identity information to the conference terminal after the binding is successful.

[0239] The device identity information of the conference terminal is vid identity information.

[0240] In step S2308, the server pushes the device identity information of the conference terminal to the second client through a long connection.​

[0241] Specifically, the server pushes the tgt ticket of the conference terminal to the second client through a long connection.

[0242] In step S2309, the second client sends a login request carrying the device identity information to the server.

[0243] In step S2310, the server sends the identity QR code of the conference terminal to the second client upon determining that the device identity information is verified.

[0244] In step S2311, the second client displays the identity QR code of the conference terminal.

[0245] The process of the first client controlling the conference terminal to initiate a video conference is described below, as shown in Figure 24 The process includes the following steps:

[0246] In step S2401, the first client scans the identity QR code displayed by the second client to obtain the device identity information of the conference terminal in response to a user's scanning operation.

[0247] Specifically, the identity QR code displayed by the second client is the identity code of the conference terminal.

[0248] In step S2402, the first client displays a conference creation page and responds to a conference creation operation received through the conference creation page.

[0249] Specifically, based on the conference creation operation, conference data for creating a video conference is obtained, and the conference data includes a conference initiation account and a participant account, wherein the conference initiation account is the account of the conference terminal, and the participant account includes the account of the conference terminal and / or the account of the user.

[0250] In step S2403, the first client sends a conference creation instruction to the server through a c2c message protocol.

[0251] Specifically, the conference creation instruction includes the conference data for creating a video conference.

[0252] In step S2404, the server sends the conference creation instruction to the second client through the c2c message protocol.

[0253] In step S2405, the second client sends a conference initiation request to the server with the device identity information and the conference creation instruction.

[0254] Specifically, the second client displays a video conference initiation page and waits for the client logged in by the participant account to answer the video conference.

[0255] The process of the first client controlling the conference terminal to answer a video conference is described below, as shown in Figure 25As shown, comprising the following steps:

[0256] Step S2501, the second client displays the identity QR code of the conference terminal in the conference invitation page.

[0257] Step S2502, the first client scans the identity QR code displayed by the second client to obtain the device identity information of the conference terminal in response to the user's scanning operation.

[0258] Step S2503, the first client sends a conference invitation information acquisition request to the server through the c2c message protocol.

[0259] Step S2504, the server sends a conference invitation information acquisition request to the second client through the c2c message protocol.

[0260] Step S2505, the second client sends the conference invitation information to the server through the c2c message protocol.

[0261] Among them, the conference invitation information is video conference invitation information.

[0262] Step S2506, the server sends the conference invitation information to the first client through the c2c message protocol.

[0263] Step S2507, the first client displays the conference invitation operation page.

[0264] Step S2508, the first client sends a conference call instruction to the server through the c2c message protocol in response to the conference call operation received through the conference invitation operation page.

[0265] Step S2509, the server sends a conference call instruction to the second client through the c2c message protocol.

[0266] Step S2510, the second client sends a call conference request to the server based on the device identity information of the target conference terminal and the conference call instruction.

[0267] The process of the first client controlling the conference terminal in the middle of the conference will be introduced below, such as Figure 26 As shown, comprising the following steps:

[0268] Step S2601, the second client displays the identity QR code of the conference terminal in the conference page.

[0269] Step S2602, the first client scans the identity QR code displayed by the second client to obtain the device identity information of the conference terminal in response to the user's scanning operation.

[0270] Step S2603, the first client sends a conference information acquisition request to the server through the c2c message protocol.

[0271] Step S2604, the server sends a conference information acquisition request to the second client through the c2c message protocol.

[0272] Step S2605, the second client sends the conference information to the server through the c2c message protocol.

[0273] The conference information is video conference information.

[0274] Step S2606, the server sends the conference information to the first client through the c2c message protocol.

[0275] Step S2607, the first client displays a conference control page.

[0276] Step S2608, the first client sends a conference control instruction to the server through the c2c message protocol in response to a conference control operation received through the conference control page.

[0277] The conference control operation can be switching a video conference to a voice conference, or ending a video conference, etc.

[0278] Step S2609, the server sends the conference control instruction to the second client through the c2c message protocol.

[0279] Step S2610, the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0280] In the embodiments of the application, the first client logged in with the target user account acquires the device identity information of the target conference terminal, and controls the target conference terminal based on the device identity information of the target conference terminal, so that the target user can install the first client in other devices to control the target conference terminal, without directly operating the target conference terminal, thereby bringing convenience to the user for remote conference.

[0281] Based on the same technical concept, the embodiments of the application provide a first client, as shown in the figure, the first client 2700 comprises: Figure 27

[0282] The first processing module 2701 is configured to acquire the device identity information of the target conference terminal in response to a first acquisition operation of acquiring the device identity information, wherein the second client logged in with the device identity information is running on the target conference terminal, and the first client is a client logged in with a target user account;

[0283] The first control module 2702 is configured to control the target conference terminal based on the device identity information of the target conference terminal.

[0284] Optionally, the first processing module 2701 is further configured to:​

[0285] in response to the first acquisition operation of acquiring the device identity information of the target conference terminal, acquiring the device identity information of the target conference terminal before the second acquisition operation of acquiring the device information of the target conference terminal, in response to the second acquisition operation of acquiring the device information of the target conference terminal, acquiring the device information of the target conference terminal;

[0286] display a device binding page, and in response to a binding operation received through the device binding page, send the device information to the server, so that the server generates the device identity information according to the device information, and sends the device identity information to the second client.

[0287] Optionally, the first processing module 2701 is specifically configured to:

[0288] in response to the first scanning operation, scan the identity code of the target conference terminal displayed in the second client to obtain the device identity information; and

[0289] in response to the second scanning operation, scan the device code of the target conference terminal displayed in the second client to obtain the device information.

[0290] Optionally, the first control module 2702 is specifically configured to:

[0291] display a conference creation page, and in response to a conference creation operation received through the conference creation page, send a conference creation instruction to the second client through the server, so that the second client sends a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and displays a conference initiation page.

[0292] Optionally, the conference creation instruction includes a conference initiation account and a participant account, wherein the conference initiation account is an account of the target conference terminal, and the participant account includes a conference terminal account and / or a user account.

[0293] Optionally, the first control module 2702 is specifically configured to:

[0294] based on the device identity information of the target conference terminal, acquire conference invitation information from the second client through the server;

[0295] display a conference invitation operation page, and in response to a conference invitation operation received through the conference invitation operation page, send a conference invitation operation instruction to the second client through the server, so that the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0296] Optionally, the first control module 2702 is specifically configured to:

[0297] based on the device identity information of the target conference terminal, acquire conference information from the second client through the server;

[0298] display a conference control page, and in response to a conference control operation received through the conference control page, send a conference control instruction to the second client through the server, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0299] Based on the same technical concept, the embodiments of the present application provide a second client, as shown in the figure, the second client 2800 comprises: Figure 28

[0300] The first receiving module 2801 is configured to receive the control instruction sent by the server, the control instruction is sent to the server by the first client logged in with the target user account in response to a first obtaining operation of obtaining the device identity information, and the second client logged in with the device identity information on the target conference terminal;

[0301] The second control module 2802 is configured to control the target conference terminal based on the control instruction.

[0302] Optionally, the first receiving module 2801 is further configured to:

[0303] receive the device identity information of the target conference terminal sent by the server, the device identity information is generated by the server according to the device information of the target conference terminal, the device information is obtained by the first client in response to a second obtaining operation of obtaining the device information of the target conference terminal, and the device information is sent to the server in response to a binding operation received through the device binding page.

[0304] Optionally, the control instruction is sent to the server by the first client in response to a first scanning operation of scanning the identity code of the target conference terminal displayed in the second client to obtain the device identity information; and

[0305] The device information is obtained by the first client in response to a second scanning operation of scanning the device code of the target conference terminal displayed in the second client.

[0306] Optionally, the control instruction is a conference creation instruction, the conference creation instruction is sent to the server by the first client in response to the first obtaining operation of obtaining the device identity information, the device identity information of the target conference terminal is obtained and a conference creation page is displayed, and the conference creation instruction is sent to the server in response to a conference creation operation received through the conference creation page;

[0307] The second control module 2802 is specifically configured to:

[0308] send a conference initiation request to the server based on the device identity information of the target conference terminal and the conference creation instruction, and display a conference initiation page.

[0309] ​Optionally, the conference creation instruction comprises a conference initiation account and a participant account, wherein the conference initiation account is an account of the target conference terminal, and the participant account comprises a conference terminal account and / or a user account.

[0310] Optionally, the control instruction is a conference invitation operation instruction, and the conference invitation operation instruction is a first acquisition operation of the first client for acquiring the device identity information, the device identity information of the target conference terminal, conference invitation information from the second client based on the device identity information of the target conference terminal, and a conference invitation operation page, and the conference invitation operation instruction is sent to the server in response to a conference invitation operation received through the conference invitation operation page.

[0311] The second control module 2802 is specifically configured to:

[0312] The second control module 2802 is specifically configured to:

[0313] Optionally, the control instruction is a conference control instruction, and the conference control instruction is a first acquisition operation of the first client for acquiring the device identity information, the device identity information of the target conference terminal, conference information from the second client based on the device identity information of the target conference terminal, and a conference control page, and the conference control instruction is sent to the server in response to a conference control operation received through the conference control page.

[0314] The second control module 2802 is specifically configured to:

[0315] The second control module 2802 is specifically configured to:

[0316] Based on the same technical concept, the embodiment of the present application provides a server, as shown in the figure, the server 2900 comprises: Figure 29

[0317] The second receiving module 2901 is configured to receive the control instruction sent by the first client logged in with the target user account, the control instruction is sent to the server by the first client in response to a first acquisition operation of the first client for acquiring the device identity information, the device identity information of the target conference terminal, and the second client logged in with the device identity information on the target conference terminal.

[0318] The second processing module 2902 is configured to send the control instruction to the second client, so that the second client controls the target conference terminal based on the control instruction.

[0319] Optionally, the second receiving module 2901 is further configured to:

[0320] ​receive the device information of the target conference terminal sent by the first client, and generate device identity information of the target conference terminal according to the device information, the device information being obtained by the first client in response to a second obtaining operation of obtaining the device information of the target conference terminal, and being sent to the server in response to a binding operation received through the device binding page;

[0321] The second processing module 2902 is further configured to:

[0322] send the device identity information to the second client.

[0323] Optionally, the control instruction is sent to the server by the first client in response to a first scanning operation of scanning the identity code of the target conference terminal displayed in the second client to obtain the device identity information.

[0324] The device information is obtained by the first client in response to a second scanning operation of scanning the device code of the target conference terminal displayed in the second client.

[0325] Optionally, the second receiving module 2901 is further configured to:

[0326] receive a conference creation instruction sent by the first client, the conference creation instruction being sent to the server by the first client in response to a first obtaining operation of obtaining the device identity information, the conference creation instruction being used to obtain the device identity information of the target conference terminal and display a conference creation page, and the conference creation instruction being sent to the server by the first client in response to a conference creation operation received through the conference creation page;

[0327] The second processing module 2902 is further configured to:

[0328] send the conference creation instruction to the second client, so that the second client sends a conference creation request to the server based on the device identity information of the target conference terminal and the conference creation instruction.

[0329] Optionally, the conference creation instruction includes a conference initiation account and a participant account, the conference initiation account being an account of the target conference terminal, and the participant account including a conference terminal account and / or a user account.

[0330] Optionally, the second receiving module 2901 is further configured to:

[0331] receive a conference invitation operation instruction sent by the first client, the conference invitation operation instruction being sent to the server by the first client in response to the first obtaining operation of obtaining the device identity information, the conference invitation operation instruction being used to obtain the device identity information of the target conference terminal, obtain conference invitation information from the second client through the server based on the device identity information of the target conference terminal, and generate a conference invitation operation page, and the conference invitation operation instruction being sent to the server by the first client in response to a conference invitation operation received through the conference invitation operation page;

[0332] The second processing module 2902 is further configured to:

[0333] The conference invitation operation instruction is sent to the second client, so that the second client sends a conference invitation operation request to the server based on the device identity information of the target conference terminal and the conference invitation operation instruction.

[0334] Optionally, the second receiving module 2901 is further configured to:

[0335] The conference control instruction is sent to the second client, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0336] The second processing module 2902 is further configured to:

[0337] The conference control instruction is sent to the second client, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

[0338] Based on the same technical concept, the present application provides a computer device, as shown in the accompanying drawings, comprising at least one processor 3001 and a memory 3002 connected with the at least one processor. Figure 30 In the present application, the specific connection medium between the processor 3001 and the memory 3002 is not limited, for example, the processor 3001 and the memory 3002 are connected through a bus. Figure 30 The bus can be divided into an address bus, a data bus, a control bus, etc.

[0339] In the present application, the memory 3002 stores instructions executable by the at least one processor 3001, and the at least one processor 3001 can execute the steps included in the method for controlling the conference terminal by executing the instructions stored in the memory 3002.

[0340] The processor 3001 is the control center of the computer device, and can connect various parts of the computer device by using various interfaces and lines. The processor 3001 can control the conference terminal by running or executing instructions stored in the memory 3002 and calling data stored in the memory 3002. Optionally, the processor 3001 can include one or more processing units. The processor 3001 can integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, and an application program. The modem processor mainly processes wireless communication. It can be understood that the modem processor can also not be integrated into the processor 3001. In some embodiments, the processor 3001 and the memory 3002 can be implemented on the same chip, and in some embodiments, they can also be implemented on separate chips respectively.

[0341] The processor 3001 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as hardware processor execution or executed by a combination of hardware and software modules in the processor.

[0342] The memory 3002, as a non-volatile computer readable storage medium, can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 3002 can include at least one type of storage medium, for example, can include flash memory, hard disk, multimedia card, card type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage, magnetic disk, optical disk, etc. The memory 3002 is any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited thereto. The memory 3002 in the embodiments of the present application can also be a circuit or any other device capable of realizing a storage function, used for storing program instructions and / or data.

[0343] Based on the same inventive concept, the embodiments of the present application provide a computer readable storage medium storing a computer program executable by a computer device, which, when running on the computer device, causes the computer device to perform the steps of the above method for controlling a conference terminal.

[0344] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) containing computer-usable program code.

[0345] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system) and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device that implements the flowcharts and / or block diagrams. Figure 1one or more processes and / or blocks Figure 1 an apparatus for performing the functions specified in the flowchart

[0346] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the flowchart Figure 1 one or more processes and / or blocks Figure 1 an apparatus for performing the functions specified in the flowchart

[0347] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the flowchart Figure 1 one or more processes and / or blocks Figure 1 an apparatus for performing the functions specified in the flowchart

[0348] Although preferred embodiments of the application have been described herein, changes and modifications can be suggested to one skilled in the art, and it is intended that the scope of the application be limited only by the appended claims and equivalents thereof.

[0349] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for controlling a conference terminal, characterized in that, include: The first client, logged in with the target user account, responds to the second acquisition operation to acquire the device information of the target conference terminal, and acquires the device information of the target conference terminal. The first client generates and displays a device binding page based on the device information; The first client responds to the binding operation received through the device binding page by sending the device information, the team identifier bound to the target user account, and the information entered by the target user on the device binding page to the server. The server then generates device identity information based on the device information, the team identifier, and the information entered on the device binding page, and sends the device identity information to the second client running on the target conference terminal. The second client sends a login request carrying the device identity information to the server. The server verifies the device identity information, and upon successful verification, generates an identity code for the target conference terminal and sends the identity code to the second client. The second client then displays the identity code of the target conference terminal. The information entered on the device binding page includes: the name of the target conference terminal and the administrator settings; The first client responds to the first scanning operation, scans the identity code of the target conference terminal displayed in the second client, and obtains the device identity information; The first client controls the target conference terminal based on the device identity information of the target conference terminal, including: The first client displays the meeting creation page; The first client responds to the meeting creation operation received through the meeting creation page by sending a meeting creation instruction to the second client via the server. The meeting creation instruction includes a meeting initiator account and a participant account, enabling the second client to send a meeting initiation request to the server based on the device identity information of the target meeting terminal and the meeting creation instruction, and display the meeting initiation page. Furthermore, the server sends the meeting initiation request to the client logged in with the participant account in the meeting creation instruction, enabling the client logged in with the participant account to display a meeting invitation page. The meeting initiator account is the account of the target meeting terminal; the participant account includes: a meeting terminal account and a user account.

2. The method as described in claim 1, characterized in that, The first client responds to a second acquisition operation to obtain the device information of the target conference terminal, including: The first client responds to the second scanning operation by scanning the device code of the target conference terminal displayed in the second client to obtain the device information.

3. The method as described in claim 1, characterized in that, The first client controls the target conference terminal based on the device identity information of the target conference terminal, including: The first client obtains meeting invitation information from the second client through the server based on the device identity information of the target conference terminal; The first client displays a meeting invitation operation page and responds to the meeting invitation operation received through the meeting invitation operation page. It then sends a meeting invitation operation instruction to the second client through the server, so that the second client sends a meeting invitation operation request to the server based on the device identity information of the target meeting terminal and the meeting invitation operation instruction.

4. The method as described in claim 1, characterized in that, The first client controls the target conference terminal based on the device identity information of the target conference terminal, including: The first client obtains meeting information from the second client through the server based on the device identity information of the target conference terminal; The first client displays a conference control page and responds to conference control operations received through the conference control page. It then sends a conference control instruction to the second client through the server, so that the second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instruction.

5. A method for controlling a conference terminal, characterized in that, include: The second client sends a login request carrying the device identity information of the target conference terminal to the server, so that the server can verify the device identity information and generate the identity code of the target conference terminal when the verification is successful. A second client, logged in with the device's identity information, runs on the target conference terminal. The second client receives and displays the identity code sent by the server; The second client receives a control command sent by the server. The control command is a first client logged in with the target user account, responds to the first scanning operation, scans the identity code displayed in the second client, obtains the device identity information of the target conference terminal, and then sends it to the server. The device identity information is generated by the server based on the device information of the target conference terminal, the team identifier bound to the target user account, and the information entered by the target user on the device binding page; The information entered on the device binding page includes: the name of the target conference terminal and the settings administrator; the device information, the team identifier, and the information entered on the device binding page are sent by the first client in response to the binding operation received through the device binding page; the device binding page is generated and displayed by the first client after obtaining the device information of the target conference terminal in response to the second acquisition operation of the first client in response to the acquisition operation of the device information of the target conference terminal. The second client controls the target conference terminal based on the control commands, including: When the control command is a meeting creation command, the second client sends a meeting initiation request to the server based on the device identity information of the target meeting terminal and the meeting creation command, and displays a meeting initiation page; the meeting creation command includes a meeting initiation account and a participant account, so that the server sends the meeting initiation request to the client logged in with the participant account in the meeting creation command, so that the client logged in with the participant account displays a meeting invitation page, and the meeting initiation account is the account of the target meeting terminal; the participant account includes: meeting terminal account and user account; The meeting creation instruction is a first acquisition operation performed by the first client to obtain device identity information, which obtains the device identity information of the target meeting terminal and displays the meeting creation page. After responding to the meeting creation operation received through the meeting creation page, the instruction is sent to the server.

6. The method as described in claim 5, characterized in that, The control command is a meeting invitation operation command. The meeting invitation operation command is a first acquisition operation in which the first client responds to obtain device identity information, obtains the device identity information of the target meeting terminal, obtains meeting invitation information from the second client through the server based on the device identity information of the target meeting terminal, generates a meeting invitation operation page, and sends the response to the meeting invitation operation received through the meeting invitation operation page to the server. The second client controls the target conference terminal based on the control commands, including: The second client sends a meeting invitation request to the server based on the device identity information of the target meeting terminal and the meeting invitation operation instruction.

7. The method as described in claim 5, characterized in that, The control command is a conference control command. The conference control command is a first acquisition operation in which the first client responds to the acquisition of device identity information, acquires the device identity information of the target conference terminal, acquires conference information from the second client through the server based on the device identity information of the target conference terminal, generates a conference control page, and sends the response to the conference control operation received through the conference control page to the server. The second client controls the target conference terminal based on the control commands, including: The second client sends a conference control request to the server based on the device identity information of the target conference terminal and the conference control instructions.

8. A method for controlling a conference terminal, characterized in that, include: The server receives a control command from a first client logged in with a target user account. This control command involves the first client responding to a first scanning operation, scanning the identity code of the target conference terminal displayed in the second client, obtaining the device identity information of the target conference terminal, and then sending it to the server. The second client, logged in with the device identity information, then runs on the target conference terminal. The second client sends a login request carrying the device identity information to the server. The server verifies the device identity information, and upon successful verification, generates the identity code of the target conference terminal and sends it to the second client. The second client then displays the identity code of the target conference terminal. The device identity information is generated by the server based on the device information of the target conference terminal, the team identifier bound to the target user account, and the information entered by the target user on the device binding page. The information entered on the device binding page includes: the name of the target conference terminal and the settings administrator; the device information, the team identifier, and the information entered on the device binding page are sent by the first client in response to the binding operation received through the device binding page; the device binding page is generated and displayed by the first client after obtaining the device information of the target conference terminal in response to the second acquisition operation of the first client in response to the acquisition operation of the device information of the target conference terminal. The server sends the control command to the second client, enabling the second client to control the target conference terminal based on the control command, including: When the control command is a meeting creation command, the second client sends a meeting initiation request to the server based on the device identity information of the target meeting terminal and the meeting creation command, and displays a meeting initiation page; the meeting creation command includes a meeting initiation account and a participant account. The meeting creation command is sent to the server by the first client after responding to the first acquisition operation of acquiring device identity information, acquiring the device identity information of the target meeting terminal and displaying the meeting creation page, and responding to the meeting creation operation received through the meeting creation page. The server sends the meeting initiation request to the client logged in with the participating account in the meeting creation instruction, so that the client logged in with the participating account displays the meeting invitation page. The meeting initiation account is the account of the target meeting terminal. The participating account includes: meeting terminal account and user account.

9. A first client, characterized in that, include: The first processing module is used to respond to a second acquisition operation to acquire device information of the target conference terminal, and to acquire the device information of the target conference terminal. Based on the device information, a device binding page is generated and displayed; in response to a binding operation received through the device binding page, the device information, the team identifier bound to the target user account, and the information entered by the target user on the device binding page are sent to the server, so that the server generates device identity information based on the device information, the team identifier, and the information entered on the device binding page, and sends the device identity information to a second client running on the target conference terminal; the second client sends a login request carrying the device identity information to the server, the server verifies the device identity information, and when the verification is successful, generates an identity code for the target conference terminal and sends the identity code to the second client, and the second client displays the identity code of the target conference terminal; The information entered on the device binding page includes: the name of the target conference terminal and the administrator settings; In response to the first scanning operation, the identity code of the target conference terminal displayed in the second client is scanned to obtain the device identity information; the first client is a client logged in with the target user account; The first control module is used to control the target conference terminal based on the device identity information of the target conference terminal, including: The system displays a meeting creation page and responds to meeting creation operations received through the meeting creation page. It sends a meeting creation instruction to the second client via the server. This instruction includes a meeting initiator account and participant accounts, enabling the second client to send a meeting initiation request to the server based on the target meeting terminal's device identity information and the meeting creation instruction, and to display the meeting initiation page. Furthermore, the server sends the meeting initiation request to the client logged in with the participant account in the meeting creation instruction, causing the client logged in with the participant account to display a meeting invitation page. The meeting initiator account is the target meeting terminal's account; the participant accounts include: meeting terminal account and user account.

10. A second client, characterized in that, include: The first receiving module is used to send a login request carrying the device identity information of the target conference terminal to the server, so that the server can verify the device identity information and generate the identity code of the target conference terminal when the verification is successful. A second client, logged in with the device's identity information, runs on the target conference terminal; it receives and displays the identity code sent by the server; The system receives control commands sent by the server. The control commands are from a first client logged in with a target user account, respond to a first scanning operation, scan the identity code displayed in the second client, obtain the device identity information of the target conference terminal, and then send it to the server. The device identity information is generated by the server based on the device information of the target conference terminal, the team identifier bound to the target user account, and the information entered by the target user on the device binding page; The information entered on the device binding page includes: the name of the target conference terminal and the settings administrator; the device information, the team identifier, and the information entered on the device binding page are sent by the first client in response to the binding operation received through the device binding page; the device binding page is generated and displayed by the first client after obtaining the device information of the target conference terminal in response to the second acquisition operation of the first client in response to the acquisition operation of the device information of the target conference terminal. The second control module controls the target conference terminal based on the control commands, including: When the control command is a meeting creation command, a meeting initiation request is sent to the server based on the device identity information of the target meeting terminal and the meeting creation command, and a meeting initiation page is displayed. The meeting creation command includes a meeting initiation account and a participant account, so that the server sends the meeting initiation request to the client logged in by the participant account in the meeting creation command, so that the client logged in by the participant account displays a meeting invitation page. The meeting initiation account is the account of the target meeting terminal. The participant account includes: a meeting terminal account and a user account. The meeting creation command is sent to the server by the first client after responding to the first acquisition operation to obtain device identity information, obtaining the device identity information of the target meeting terminal and displaying the meeting creation page, and responding to the meeting creation operation received through the meeting creation page.

11. A server, characterized in that, include: The second receiving module is used to receive control instructions sent by a first client logged in with a target user account. The control instructions are sent by the first client in response to a first scanning operation, scanning the identity code of the target conference terminal displayed in the second client, obtaining the device identity information of the target conference terminal, and then sending it to the server. The second client, logged in with the device identity information, runs on the target conference terminal. The second client sends a login request carrying the device identity information to the server. The server verifies the device identity information. If the verification is successful, the server generates the identity code of the target conference terminal and sends the identity code to the second client. The second client displays the identity code of the target conference terminal. The device identity information is generated by the server based on the device information of the target conference terminal, the team identifier bound to the target user account, and the information entered by the target user on the device binding page; The information entered on the device binding page includes: the name of the target conference terminal and the settings administrator; the device information, the team identifier, and the information entered on the device binding page are sent by the first client in response to the binding operation received through the device binding page; the device binding page is generated and displayed by the first client after obtaining the device information of the target conference terminal in response to the second acquisition operation of the first client in response to the acquisition operation of the device information of the target conference terminal. The second processing module is configured to send the control command to the second client, so that the second client controls the target conference terminal based on the control command, including: When the control command is a meeting creation command, the second client sends a meeting initiation request to the server based on the device identity information of the target meeting terminal and the meeting creation command, and displays a meeting initiation page. The meeting creation command includes a meeting initiation account and a participant account. The meeting creation command is sent to the server by the first client after responding to a first acquisition operation to obtain device identity information, obtaining the device identity information of the target meeting terminal and displaying the meeting creation page, and responding to the meeting creation operation received through the meeting creation page. The meeting initiation request is sent to the client logged in with the participant account in the meeting creation command, so that the client logged in with the participant account displays a meeting invitation page. The meeting initiation account is the account of the target meeting terminal. The participant account includes: a meeting terminal account and a user account.

Images