Conference terminal interaction method and device

Abstract

The present application discloses a conference terminal interaction method and device, belonging to the field of interactive technology. The method includes: establishing a conference through the first terminal by connecting a first terminal to a second terminal by wire, confirming that the second terminal supports the target protocol, and adding the second terminal to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through the wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art, and can achieve the effect of improving the interaction stability between multiple terminals.

Description

Technical Field

[0001] The present application relates to the field of interactive technology, and in particular to a conference terminal interaction method and device. Background Art

[0002] In a multi-device, multi-user conference scenario, users can operate the terminal to achieve multi-device interaction, such as transferring conference materials.

[0003] A conference terminal interaction method is disclosed, in which multiple terminals interact with each other via a wireless network. If a first terminal wants to interact with a second terminal, both the first terminal and the second terminal need to be connected to the wireless network, and the first terminal needs to send an interaction request to a server via the wireless network. After the server receives the interaction request, it sends the interaction request to the second terminal via the wireless network. After receiving the interaction request, the second terminal responds to the interaction request.

[0004] However, in the related art, the interaction between multiple terminals relies on a wireless network, which has poor stability. Summary of the Invention

[0005] The present invention provides a conference terminal interaction method, device, conference system, and computer storage medium. The technical solution is as follows:

[0006] According to one aspect of the present application, a conference terminal interaction method is provided, the method being applied to a first terminal, where the first terminal and a second terminal are connected by wire, the method comprising:

[0007] Establish a meeting;

[0008] Sending a conference connection request to the second terminal through the wired connection, where the conference connection request is used to confirm whether the second terminal supports conference interaction through the target protocol;

[0009] In response to receiving the connection confirmation information sent by the second terminal, confirming that the second terminal supports the target protocol;

[0010] Based on the target protocol, receiving first confirmation information sent by the second terminal through the wired connection, where the first confirmation information is used to confirm joining the conference;

[0011] Based on the first confirmation information, it is confirmed that the second terminal joins the conference through the wired connection.

[0012] Optionally, the receiving, based on the target protocol and through the wired connection, first confirmation information sent by the second terminal includes:

[0013] Based on the target protocol, determining, through the wired connection, whether the second terminal has conference collaboration software installed;

[0014] In response to the second terminal being installed with the conference collaboration software, receiving first confirmation information sent by the second terminal through the wired connection based on the conference collaboration software;

[0015] In response to the second terminal not having the conference collaboration software installed, controlling the second terminal to install the conference collaboration software, and executing the step of receiving the first confirmation information sent by the second terminal through the wired connection based on the conference collaboration software in response to the second terminal having the conference collaboration software installed.

[0016] Optionally, the first confirmation information includes information of the first participant;

[0017] After receiving the first confirmation information sent by the second terminal through the wired connection, the method further includes:

[0018] The information of the first participant is displayed.

[0019] Optionally, after confirming that the second terminal joins the conference through the wired connection, the method further includes:

[0020] receiving a first connection switching request sent by the second terminal;

[0021] Sending wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection;

[0022] Second confirmation information sent by the second terminal based on the wireless connection is obtained to confirm that the second terminal joins the conference through the wireless connection.

[0023] Optionally, the method further includes:

[0024] First data information sent by the second terminal is obtained through the wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0025] Optionally, after obtaining the first data information sent by the second terminal through the wired connection, the method further includes:

[0026] Associating the first data information with the first participant information;

[0027] Acquire meeting minutes information of a user corresponding to the first participant information, where the meeting minutes information includes the first participant and first data information associated with the first participant.

[0028] Optionally, the first confirmation information includes information of a first participant, and the second confirmation information includes information of a second participant;

[0029] After obtaining the first data information sent by the second terminal through the wired connection, the method further includes:

[0030] obtaining, through the wired connection, first data information sent by the second terminal, where the first data information includes at least one of conference voice information and conference file information;

[0031] Associating the first data information with the first participant information;

[0032] After confirming that the second terminal joins the conference through the wireless connection, the method further includes:

[0033] In response to the first participant information and the second participant information being the same, the first data information is associated with the second participant information, where the first data information is data information associated with the first participant information.

[0034] Optionally, the wireless channel information includes a web conference link.

[0035] Optionally, the first terminal is connected to a wireless local area network, and after receiving the first connection switching request sent by the second terminal, the method further includes:

[0036] Sending second data information to the second terminal based on the first connection switching request, where the second data information includes an address and a password of a wireless local area network to which the first terminal is currently connected;

[0037] Receive connection information sent by the second terminal based on the address and password of the wireless local area network.

[0038] Optionally, the target protocol includes the Android Open Accessory Protocol.

[0039] Optionally, the wired connection comprises a USB connection.

[0040] According to another aspect of the present application, a conference terminal interaction method is provided, the method being applied to a second terminal, wherein a first terminal and the second terminal are connected by wire, the method comprising:

[0041] receiving a conference connection request sent by the first terminal, where the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol;

[0042] Sending connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol;

[0043] Based on the target protocol, first confirmation information is sent to the first terminal, where the first confirmation information is used to confirm joining a conference established by the first terminal.

[0044] Optionally, the sending first confirmation information to the first terminal based on the target protocol includes:

[0045] Based on the target protocol, determining whether conference collaboration software is installed;

[0046] In response to the conference collaboration software being installed, sending first confirmation information to the first terminal through the wired connection based on the conference collaboration software;

[0047] In response to the conference collaboration software not being installed, the conference collaboration software is installed under the control of the first terminal, and in response to the conference collaboration software being installed, the first confirmation information is sent to the first terminal through the wired connection based on the conference collaboration software.

[0048] Optionally, the first confirmation information includes first participant information.

[0049] Optionally, after sending the first confirmation information to the first terminal through the wired connection, the method further includes:

[0050] Sending a first connection switching request to the first terminal;

[0051] receiving wireless channel information sent by the first terminal, where the wireless channel information is used to indicate joining the conference via a wireless connection;

[0052] Based on the wireless channel information, join the conference through the wireless connection, and send second confirmation information to the first terminal through the wireless connection.

[0053] Optionally, the method further includes:

[0054] First data information is sent to the first terminal through the wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0055] Optionally, the second confirmation information includes second participant information.

[0056] Optionally, the wireless channel information includes a web conference link.

[0057] Optionally, the first terminal is connected to a wireless local area network. After sending the first connection switching request to the first terminal, the method further includes:

[0058] receiving second data information sent by the first terminal, where the second data information includes an address and a password of a wireless local area network to which the first terminal is currently connected;

[0059] Based on the address and password of the wireless local area network, connect to the wireless local area network, and send connection information to the first terminal.

[0060] Optionally, the target protocol includes the Android Open Accessory Protocol.

[0061] Optionally, the wired connection comprises a USB connection.

[0062] According to another aspect of the present application, a conference terminal interaction method is provided for a conference system, wherein the conference system includes a first terminal and a second terminal, the first terminal and the second terminal being connected by a wire, the method comprising:

[0063] The first terminal establishes a conference;

[0064] The first terminal sends a conference connection request to the second terminal through the wired connection, where the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol;

[0065] The second terminal sends connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol;

[0066] In response to receiving the connection confirmation information sent by the second terminal, the first terminal confirms that the second terminal supports the target protocol;

[0067] The second terminal sends, based on the target protocol, first confirmation information to the first terminal through the wired connection, where the first confirmation information is used to confirm joining the conference;

[0068] The first terminal confirms, based on the first confirmation information, that the second terminal joins the conference through the wired connection.

[0069] Optionally, the second terminal sends first confirmation information to the first terminal based on the target protocol, where the first confirmation information is used to confirm joining the conference;

[0070] The step of receiving, by the first terminal through the wired connection based on the target protocol, first confirmation information sent by the second terminal includes:

[0071] The second terminal determines whether conference collaboration software is installed based on the target protocol;

[0072] The first terminal determines, based on the target protocol, through the wired connection, whether the second terminal has conference collaboration software installed;

[0073] In response to the second terminal being installed with the conference collaboration software, the second terminal sends a first confirmation message to the first terminal through the wired connection based on the conference collaboration software;

[0074] In response to the second terminal having the conference collaboration software installed, the first terminal receives, based on the conference collaboration software, the first confirmation information sent by the second terminal through the wired connection;

[0075] In response to the conference collaboration software not being installed, the second terminal installs the conference collaboration software and executes the step of sending first confirmation information to the first terminal through the wired connection based on the conference collaboration software in response to the conference collaboration software being installed.

[0076] In response to the second terminal not having the conference collaboration software installed, the first terminal controls the second terminal to install the conference collaboration software, and performs the step of receiving, through the wired connection, first confirmation information sent by the second terminal based on the conference collaboration software in response to the second terminal having the conference collaboration software installed.

[0077] Optionally, the first confirmation information includes information of the first participant;

[0078] After the first terminal receives, through the wired connection, first confirmation information sent by the second terminal, the method further includes:

[0079] The first terminal displays the first participant information.

[0080] Optionally, after the first terminal confirms that the second terminal joins the conference through the wired connection, the method further includes:

[0081] The second terminal sends a first connection switching request to the first terminal;

[0082] The first terminal receives a first connection switching request sent by the second terminal;

[0083] The first terminal sends wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection;

[0084] The second terminal joins the conference through the wireless connection based on the wireless channel information, and sends second confirmation information to the first terminal through the wireless connection;

[0085] The first terminal obtains second confirmation information sent by the second terminal based on the connection information, and confirms that the second terminal joins the conference through the wireless connection.

[0086] Optionally, the method further includes:

[0087] The second terminal sends first data information to the first terminal through the wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0088] The first terminal obtains the first data information sent by the second terminal through the wired connection.

[0089] Optionally, after the first terminal obtains the first data information sent by the second terminal through the wired connection, the method further includes:

[0090] Associating, by the first terminal, the first data information with the first participant information;

[0091] The first terminal obtains meeting minutes information of a user corresponding to the first participant information, where the meeting minutes information includes the first participant and first data information associated with the first participant.

[0092] Optionally, the first confirmation information includes information of a first participant, and the second confirmation information includes information of a second participant;

[0093] After the first terminal obtains the first data information sent by the second terminal through the wired connection, the method further includes:

[0094] The first terminal obtains, through the wired connection, first data information sent by the second terminal, where the first data information includes at least one of conference voice information and conference file information;

[0095] Associating, by the first terminal, the first data information with the first participant information;

[0096] After the first terminal obtains second confirmation information sent by the second terminal based on the wireless channel information and confirms that the second terminal joins the conference through the wireless connection, the method further includes:

[0097] In response to the first participant information and the second participant information being identical, the first terminal associates the first data information with the second participant information, where the first data information is data information associated with the first participant information.

[0098] Optionally, the wireless channel information includes a web conference link.

[0099] Optionally, the first terminal is connected to a wireless local area network. After the first terminal receives the first connection switching request sent by the second terminal, the method further includes:

[0100] The first terminal sends second data information to the second terminal based on the first connection switching request, where the second data information includes an address and a password of a wireless local area network to which the first terminal is currently connected;

[0101] The second terminal receives the second data information sent by the first terminal, connects to the wireless local area network based on the address and password of the wireless local area network, and sends connection information to the first terminal.

[0102] Optionally, the target protocol includes the Android Open Accessory Protocol.

[0103] Optionally, the wired connection comprises a USB connection.

[0104] According to another aspect of the present application, a conference terminal interaction device is provided, the device being applied to a first terminal, the first terminal being connected to a second terminal by wire, and the device comprising:

[0105] The first establishment module is used to establish a meeting;

[0106] A first sending module is configured to send a conference connection request to the second terminal through the wired connection, wherein the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol;

[0107] a first receiving module, configured to confirm, in response to receiving the connection confirmation information sent by the second terminal, that the second terminal supports the target protocol;

[0108] a first processing module, configured to receive, based on the target protocol, first confirmation information sent by the second terminal through the wired connection, where the first confirmation information is used to confirm joining the conference;

[0109] The first confirmation module is configured to confirm, based on the first confirmation information, that the second terminal has joined the conference through the wired connection.

[0110] According to another aspect of the present application, a conference terminal interaction device is provided, the device being applied to a second terminal, the first terminal and the second terminal being connected by wire, the device comprising:

[0111] A second receiving module is configured to receive a conference connection request sent by the first terminal, wherein the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol;

[0112] A second sending module is configured to send connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol;

[0113] The second confirmation module is configured to send first confirmation information to the first terminal based on the target protocol, where the first confirmation information is used to confirm joining the conference established by the first terminal.

[0114] According to another aspect of the present application, a conference terminal interaction device is provided, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the conference terminal interaction method as described above.

[0115] According to another aspect of the present application, a computer storage medium is provided, characterized in that the computer storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the conference terminal interaction method as described above.

[0116] The beneficial effects of the technical solutions provided in the embodiments of the present application include at least:

[0117] A conference terminal interaction method is provided. A first terminal and a second terminal are connected by a wire. A conference is established through the first terminal. After confirming that the second terminal supports a target protocol, the second terminal is added to the conference. This allows the first and second terminals to interact locally via the wired connection, eliminating the need for a wired network for conference interaction. This addresses the issue of poor stability in interaction between multiple terminals in related technologies, improving the stability of interaction between multiple terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0118] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0119] Figure 1 This is an architectural diagram of a conference system provided by an embodiment of the present application;

[0120] Figure 2 This is a flowchart of a conference terminal interaction method provided by an embodiment of the present application;

[0121] Figure 3 This is a flowchart of another conference terminal interaction method provided by an embodiment of the present application;

[0122] Figure 4 This is a flowchart of another conference terminal interaction method provided by an embodiment of the present application;

[0123] Figure 5 This is a structural diagram of a conference terminal interaction device provided in an embodiment of the present application;

[0124] Figure 6 This is a flowchart of another conference terminal interaction method provided in an embodiment of the present application.

[0125] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0126] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0127] First, the application scenarios involved in the embodiments of the present application are introduced.

[0128] The conference terminal interaction method provided in the embodiment of the present application can be applied to a conference system, which includes multiple first terminals and multiple second terminals, such as an all-in-one conference machine and multiple smart tablets. In some examples, the all-in-one conference machine can share conference files with the smart tablet through the conference terminal interaction method, and the smart tablet can display the conference files. The smart tablet can send conference check-in information and conference voting information to the all-in-one conference machine through the conference terminal interaction method. It should be noted that the content of the interaction between the all-in-one conference machine and multiple smart tablets is not limited to the examples listed above.

[0129] Figure 1 This is an architectural diagram of a conference system provided by an embodiment of the present application. Figure 1 The conference system includes a first terminal 11, multiple second terminals 12, and a control component 13. The control component 13 is used to enable the first terminal 11 and the multiple second terminals 12 to interact. The control component 13 may include one or more processors.

[0130] Among them, the first terminal 11 and multiple second terminals 12 can establish a wired connection with the control component 13. The control component 13 can be located in the same device as the first terminal 11. For example, the control component 13 and the first terminal 11 can be located in an all-in-one conference machine. The control component 12 can also establish a wireless connection with the server, and the second terminal 12 can also establish a wireless connection with the server. For example, the second terminal can include a smart phone, a smart tablet or a computer and other devices.

[0131] Figure 2 This is a flow chart of a conference terminal interaction method provided by an embodiment of the present application. The method is applied to a first terminal, the first terminal and the second terminal are wired connected, and the wired connection may include a Universal Serial Bus (USB) connection. The first terminal and the second terminal may both have display functions and input functions. Please refer to Figure 2 , the method comprises the following steps:

[0132] Step 201: Establish a meeting.

[0133] Step 202: Send a conference connection request to the second terminal via a wired connection.

[0134] The conference connection request is used to confirm whether the second terminal supports conference interaction through the target protocol.

[0135] Step 203: In response to receiving the connection confirmation information sent by the second terminal, confirm that the second terminal supports the target protocol.

[0136] Step 204: Receive first confirmation information sent by the second terminal through a wired connection based on the target protocol.

[0137] The first confirmation information is used to confirm joining the conference.

[0138] Step 205: Based on the first confirmation information, confirm that the second terminal joins the conference through a wired connection.

[0139] In summary, the embodiments of the present application provide a conference terminal interaction method, in which a first terminal and a second terminal are connected by wire, a conference is established through the first terminal, and the second terminal is confirmed to support the target protocol, and the second terminal is added to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through the wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art, and achieving the effect of improving the interaction stability between multiple terminals.

[0140] In an embodiment of the present application, the first terminal can be an all-in-one conference machine, and the second terminal can be a mobile phone or a tablet computer. The all-in-one conference machine (first terminal) is used as the host device, and the mobile phone is used as the accessory device. The host device and each accessory device are connected via USB to realize local meetings without a network. Local meetings can be started when there is no network or the online network is limited, which can improve the user experience of the all-in-one conference machine.

[0141] Figure 3 This is a flowchart of another conference terminal interaction method provided by an embodiment of the present application. The method can be used in a conference system, which can include a first terminal and a second terminal. The method can include the following steps:

[0142] Step 301: The first terminal establishes a conference.

[0143] The conference can essentially be a virtual group established by the first terminal, allowing multiple terminals to join. The first terminal can be an all-in-one conference machine, which is an office device that integrates electronic components such as audio, display, computer, microphone, and camera. Users can start a conference by clicking the display control on the all-in-one conference machine's display. The conference is based on a wired connection for data transmission. The second terminal can be a smartphone or smart tablet, and the first and second terminals can be connected via a USB connection.

[0144] Step 302: The first terminal sends a conference connection request to the second terminal via a wired connection.

[0145] The conference connection request is used to confirm whether the second terminal supports conference interaction through the target protocol.

[0146] The target protocol includes the Android Open Accessory Protocol (AOA). The AOA protocol is the connection protocol for USB communication between Android devices. In USB communication, Android devices can choose between two modes when communicating with USB hardware: host mode and accessory mode. In terms of USB logical roles, host mode means the Android device acts as the USB host, initiating all activities. Accessory mode means the Android device acts as a USB device, with the connected USB hardware acting as the USB host.

[0147] In an embodiment of the present application, the second terminal can be connected to the first terminal through a USB interface, and the communication mode of the second terminal is an accessory mode, that is, the second terminal acts as a slave and establishes an AOA protocol communication connection with the first terminal, and the first terminal acts as a host and powers the USB bus.

[0148] For example, the first terminal may send a conference connection request to the second terminal via the AOA protocol. The conference connection request may be a protocol acquisition request to determine whether the second terminal supports the Android accessory mode. The protocol acquisition request has the following characteristics: a request type of USB DIR IN USB TYPE VENDOR and a request value of 51.

[0149] Step 303: The second terminal sends connection confirmation information to the first terminal based on the conference connection request.

[0150] The connection confirmation information is used to indicate that the second terminal supports the target protocol.

[0151] When the second terminal receives the conference connection request, if the second device supports the accessory mode, it can send a connection confirmation message to the first terminal. The connection confirmation message can be a non-zero number representing the protocol version supported by the second terminal.

[0152] In response to receiving the connection confirmation information sent by the second terminal, the first terminal confirms that the second terminal supports the target protocol. If the second terminal supports the AOA protocol, the first terminal can control the second terminal to start in accessory mode based on the AOA protocol and establish a communication connection.

[0153] Exemplarily, the first terminal acts as an AOA host mode and enables the second terminal to restart the USB connection in accessory mode through AOA. Specifically, the first terminal can send a control request to the second terminal through AOA to request the device to start in accessory mode. The control request has the following characteristics: the request type is USB DIR OUT USB TYPE VENDOR, and the request value is 53.

[0154] Step 304: The first terminal determines whether the second terminal has conference collaboration software installed through a wired connection based on the target protocol.

[0155] The second terminal may determine whether it has conference collaboration software installed based on the target protocol.

[0156] After entering the accessory mode communication connection, the first terminal can directly or indirectly detect whether the second terminal has the conference collaboration software installed. In an optional embodiment, detecting whether the second terminal has the conference collaboration software installed specifically includes: the first terminal sending software identification information of the conference collaboration software to the second terminal, so that the second terminal performs a match based on the software identification information and feeds back the matching result to the first terminal; and the first terminal determines whether the second terminal has the conference collaboration software installed based on the matching result.

[0157] Exemplarily, the first terminal sends a control request containing identification string information to the second terminal via AOA. The control request can be used to detect whether conference collaboration software is installed in the second terminal. The control request has the following characteristics: the request type is USB DIR OUT USB TYPE VENDOR, the request value is 52, and the various string information sent are: manufacturer (string ID: 0, string value: company name), model (string ID: 1, string value: first terminal model), description (string ID: 2, string value: current conference collaboration software description), version (string ID: 3, string value: current collaboration version number), URI (string ID: 4, string value: download address of conference collaboration software), serial number (string ID: 5, string value: preset mode serial number, which can be any value).

[0158] The second terminal can store the software identification information installed in the second terminal. When the second terminal receives the software identification information of the conference collaboration software sent by the first terminal, the second terminal matches the software identification information of the conference collaboration software with the stored software identification information and feeds back the matching result to the first terminal. If the software identification information of the conference collaboration software is stored in the second terminal, the matching is successful and the conference collaboration software is installed in the second terminal; if the matching fails, it means that the conference collaboration software is not installed in the second terminal.

[0159] For example, the conference collaboration software on the second terminal in the present application can display a USB ACCESSORY ATTACHED sign on the display interface to indicate receipt of a USB accessory connection notification. The connection notification includes a USB-accessory element, which declares the manufacturer, model, and version attributes in the identification string information sent by the first terminal to the second terminal via AOA. After the second terminal is started in AOA accessory mode, the second terminal will check whether its own device has the conference collaboration software installed based on the identification string information sent by the first terminal via AOA. Specifically, whether the second terminal has installed an application with the same manufacturer, model, and version attributes as those in the identification string information.

[0160] Step 305: In response to the installation of the conference collaboration software, the second terminal sends a first confirmation message to the first terminal through a wired connection based on the conference collaboration software.

[0161] The number of second terminals can be multiple, and the multiple second terminals can be connected to the first terminal by wire. If the second terminal connected to the first terminal supports AOA accessory mode, the accessory mode is started. After entering the accessory mode, it can be detected whether conference collaboration software is installed in the second terminal. If conference collaboration software is installed, the conference collaboration software is run. In the embodiment of the present application, the conference collaboration software may include conventional office software such as text editing software, spreadsheet editing software, and handwriting board software. The conference collaboration software can be used to implement functions such as conference sign-in and meeting minutes generation in the embodiment of the present application.

[0162] In response to the second terminal being installed with conference collaboration software, the first terminal receives first confirmation information sent by the second terminal through a wired connection based on the conference collaboration software, where the first confirmation information is used to confirm joining the conference.

[0163] Optionally, the first confirmation information includes the first participant information. That is, when the conference collaboration software on the second terminal enters the running state, the user can sign in on the second terminal, so that the second terminal obtains the first participant information and sends the first participant information to the first terminal, indicating that the second terminal has joined the meeting.

[0164] Optionally, if the second terminal responds that the conference collaboration software is not installed, it installs the conference collaboration software and executes the step of sending a first confirmation message to the first terminal via a wired connection based on the conference collaboration software in response to the conference collaboration software being installed (step 305).

[0165] If the conference collaboration software is not installed in the second terminal, a target website address may be displayed on the display interface of the second terminal. The target website address is the download address of the conference collaboration software. The user may download the conference collaboration software by clicking on the target website address.

[0166] For example, the second terminal will display information such as manufacturer, model, description, version, Uniform Resource Identifier (URI) and serial number to the user in a pop-up window based on the received identification string information. The user needs to click on the URL in the URI part to install the conference collaboration software.

[0167] Alternatively, in response to the second terminal not having the conference collaboration software installed, the first terminal may control the second terminal to install the conference collaboration software. In an embodiment of the present application, when the first terminal detects that the second terminal has the conference collaboration software installed, it may control the second terminal to run the conference collaboration software. When the conference collaboration software is run, preset functions such as conference check-in and file transfer may be implemented.

[0168] The second terminal that sends the conference confirmation information may be a target second terminal, and a method for obtaining the target second terminal from the multiple second terminals may include the following two methods:

[0169] In a first approach, a first terminal sends a first interaction request to one or more second terminals among a plurality of terminals. Thus, the second terminal that receives the first interaction request may be a target second terminal.

[0170] In a second approach, the first terminal sends a first interaction request to all second terminals, and uses the second terminal corresponding to the received conference confirmation information as the target second terminal.

[0171] Step 306: The first terminal confirms, based on the first confirmation information, that the second terminal joins the conference through a wired connection.

[0172] After the first terminal receives the first participant information, it can confirm that the second terminal has joined the conference, so that the first terminal and the second terminal that has joined the conference can perform subsequent conference interaction steps.

[0173] Step 307: The first terminal displays the first participant information.

[0174] The second terminal may include a first display and a first encoder. The first display has an input function, and the first encoder is capable of encoding the first participant information input via the first display to generate first data information. The second terminal (mobile phone) can directly send the first participant information, serialized into binary data, to the first terminal (all-in-one conference device) via a binary data stream for check-in.

[0175] The first terminal may include a first decoder and a second display. The first terminal obtains the first participant information in binary data form through a local connection. The first decoder decodes the first participant information to obtain the first participant information. The first display displays the first participant information so that the user can understand the current number of participants and the participants.

[0176] Exemplarily, the first participant information may be user information of the participant, which may include the participant's user ID, user name, user MAC address, and user participation method (eg, local participation method).

[0177] Step 308: The second terminal sends the first data information to the first terminal through a wired connection.

[0178] The first data information includes at least one of conference voice information and conference file information.

[0179] A first terminal can receive first data information sent by a second terminal via a wired connection. The first and second terminals can communicate via an AOA data stream. That is, the second terminal can send first data information serialized into binary data to the first terminal via a binary data stream, so that the first terminal can receive the first data information. In this way, the first and second terminals can send real-time conference messages or share file information via a wired connection.

[0180] Step 309: The first terminal associates the first data information with the first participant information.

[0181] The first terminal can receive the first data information (real-time message or shared file information) serialized into binary data form sent by the second terminal through a binary data stream, and deserialize it into recognizable real-time message or file information data and display it. For example, the target second terminal sends real-time information (text, voice and picture) and conference files to the first terminal.

[0182] After receiving the first data information, the first terminal may associate the first data information with the first participant information corresponding to the target second terminal that sends the second data information, so that the participants know the participant to whom the first data information belongs.

[0183] Step 310: The first terminal obtains the meeting minutes information of the user corresponding to the first participant information.

[0184] The meeting minutes information includes the first participant and first data information associated with the first participant.

[0185] The meeting minutes information can be obtained from meeting-related data generated during the entire meeting process from the establishment of the meeting (step 301) to the end of the meeting.

[0186] Alternatively, the conference may be started by establishing a conference (step 301 ), and during the conference, the conference minutes information may be acquired and updated in real time according to the first data information sent by the second terminal.

[0187] When the meeting ends, the second terminal may receive the meeting minutes information serialized into binary data form sent by the first terminal through a binary data stream. The meeting minutes information may include meeting to-do items, meeting minutes, and meeting documents.

[0188] Step 311: The second terminal sends a first connection switching request to the first terminal.

[0189] The second terminal sends a first connection switching request to the first terminal through a wired connection, and the first terminal receives the first connection switching request sent by the second terminal.

[0190] A user can click a first connection switching control on a second terminal, and the second terminal can then receive a first connection switching request, which is used to request that the connection mode between the first terminal and the target second terminal be switched from a wired connection to an online connection. The online connection may include a network online connection or a local area network online connection.

[0191] Step 312: The first terminal sends second data information to the second terminal based on the first connection switching request.

[0192] The second data information includes the address and password of the wireless local area network to which the first terminal is currently connected.

[0193] The first terminal can have three connection modes: wired connection (local connection), network online connection, and LAN online connection. When the first terminal is connected to a wireless LAN, the connection mode between the second terminal and the first terminal can be switched to LAN online connection. That is, the second terminal's conference participation mode can be switched from wired connection to LAN online connection. This LAN online connection allows the first and second terminals to transmit conference data based on the LAN connection.

[0194] Exemplarily, since the first terminal and the second terminal are still in a wired connection state at this time, the second terminal can communicate with the first terminal through the AOA data stream, and send a request serialized in the form of binary data to the first terminal through the binary data stream to request to obtain the address and password data of the currently connected wireless local area network (WiFi).

[0195] After receiving the request through the AOA data stream, the first terminal may send the address and password of the currently connected wireless local area network to the second terminal through the binary data stream.

[0196] Step 313: The second terminal sends connection information to the first terminal based on the second data information.

[0197] The second terminal can receive the second data information sent by the first terminal, where the second data information includes the address and password of the wireless local area network to which the first terminal is currently connected. Based on the address and password of the wireless local area network, the second terminal connects to the wireless local area network and sends connection information to the first terminal. The first terminal can receive the connection information sent by the second terminal based on the address and password of the wireless local area network. Exemplarily, after the target second terminal receives the address and password of the wireless local area network sent by the first terminal through the AOA data stream, it can identify the address and password of the wireless local area network and automatically connect to the wireless local area network.

[0198] In this way, the first terminal and the target second terminal can be connected to the same wireless local area network (WiFi network) so that the meeting can continue. After the target second terminal successfully connects to the WiFi network, it can send a connection success message to the first terminal.

[0199] Step 314: The first terminal sends wireless channel information to the second terminal based on the first connection switching request.

[0200] The wireless channel information is used to indicate joining the conference via a wireless connection. The wireless channel information may include a web conference link.

[0201] Since the first terminal and the target second terminal still maintain an online connection (ie, a local connection) at this time, the first terminal can directly send the conference link serialized in the form of binary data to the target second terminal through the binary data stream.

[0202] Optionally, the first terminal may also generate a conference link for participating in the conference via a local area network connection according to the local terminal ID (MAC or serial number), and send the conference link to the second terminal.

[0203] Alternatively, the first terminal may display the conference connection as a QR code for the second terminal to scan to connect to the local area network and participate in the conference.

[0204] Optionally, both the first terminal and the second terminal are connected to the internet online, and the first terminal and the second terminal can transmit conference data based on the internet connection. In this case, steps 312 and 313 above may not be performed. The conference system may also include a server for enabling data exchange between the first terminal and the second terminal connected online.

[0205] Since the first terminal and the target second terminal still maintain an online connection (ie, a local connection) at this time, the first terminal can directly send the conference link serialized in the form of binary data to the target second terminal through the binary data stream.

[0206] Optionally, the first terminal may also generate a conference link for participating in the conference through an online network connection according to the local ID (MAC or serial number), and send the conference link to the second terminal.

[0207] Alternatively, the first terminal may display the conference link as a QR code for the second terminal to scan to participate in the conference.

[0208] In an optional implementation, the first terminal may also register a conference with a unique ID to the server based on the local ID (MAC or serial number) and generate a conference link. For example, the conference link may be displayed as a QR code for the second terminal to scan to participate in the conference.

[0209] Step 315: The second terminal joins the conference through a wireless connection based on the wireless channel information, and sends a second confirmation message to the first terminal through the wireless connection.

[0210] After receiving the conference link, the second terminal may display the conference link so that the user can click the conference link to join the conference via a wireless connection.

[0211] Alternatively, after receiving the conference link, the second terminal may automatically identify the conference link and join the conference corresponding to the conference link.

[0212] Optionally, the second confirmation information includes the second participant's information. The user can enter the conference interface through the conference link displayed on the second terminal and send the second participant's information to the first terminal via a wireless connection to sign in to the meeting. The second terminal can send the user information (user ID, user name, user MAC address) of the device to the server for sign-in.

[0213] The first terminal obtains second confirmation information sent by the second terminal based on the wireless channel information, confirming that the second terminal has joined the conference via the wireless connection. The server can send the second confirmation information sent by the second terminal to the first terminal and display the second confirmation information on the first terminal, so that the first terminal can confirm that the second terminal has joined the online conference and can exchange conference information via the wireless connection.

[0214] Step 316: In response to the first participant information and the second participant information being the same, the first terminal associates the first data information with the second participant information.

[0215] The first data information is data information associated with the first participant's information. The first terminal can synchronously associate the first data information (such as sent real-time information and uploaded file information) associated with the first participant's information with the information of a second participant with the same user information. This prevents loss of conference-related data information after the second terminal switches the connection mode with the first terminal.

[0216] For example, when a second terminal participates in a meeting via a wireless connection, the first terminal can obtain the second participant's information through the server and display the second participant's information. The second participant's information may include the participant's user ID, user name, user MAC address, and user participation method (e.g., participating via a wireless connection). The first terminal can also obtain real-time messages sent by the participant or shared file information through the server.

[0217] When the meeting ends, meeting minutes information may be sent to the second terminal via a server, a wired connection, or a local area network connection. The meeting minutes information includes meeting to-do items, meeting minutes, and meeting documents.

[0218] After the second terminal joins the meeting wirelessly, the wired connection between the first terminal and the second terminal can be disconnected. In other words, the user can disconnect the USB connection between the first terminal and the target second terminal to seamlessly switch between participating in the meeting online and wirelessly.

[0219] In summary, the embodiments of the present application provide a conference terminal interaction method, in which a first terminal and a second terminal are connected by wire, a conference is established through the first terminal, and the second terminal is confirmed to support the target protocol, and the second terminal is added to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through the wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art, and achieving the effect of improving the interaction stability between multiple terminals.

[0220] Figure 4 This is a flow chart of another conference terminal interaction method provided by an embodiment of the present application. Figure 4 , the conference terminal interaction method may include:

[0221] Step 401, start.

[0222] Step 402: The first terminal starts a local conference.

[0223] Step 403: The second terminal is connected to the first terminal via USB.

[0224] Step 404: Whether the second terminal supports accessory mode.

[0225] If the second terminal supports the accessory mode, step 405 is executed. If the second terminal does not support the accessory mode, the process ends.

[0226] Step 405: The first terminal acts as a host to start the second terminal in accessory mode.

[0227] Step 406: After the second terminal is started in the accessory mode, the first terminal checks whether the second terminal has the conference collaboration software installed according to the AOA.

[0228] Step 407: Check whether the second terminal has installed conference collaboration software.

[0229] If the second terminal has the conference collaboration software installed, step 405 is executed. If the second terminal has not the conference collaboration software installed, the process ends.

[0230] Step 408: The first terminal in the host mode establishes communication with the second terminal in the accessory mode.

[0231] Step 409: After establishing communication, the second terminal participates in the local conference in USB local mode to perform conference collaboration: conference sign-in, information exchange with the first terminal, or upload conference files.

[0232] Step 410: When the meeting ends, the first terminal sends the meeting minutes, meeting materials and other information to the second terminal offline via USB.

[0233] Step 411, end.

[0234] The embodiment of the present application proposes a conference terminal interaction method based on Android USB connection, which can provide local conference collaboration functions in the absence of network or network limitation, and can improve user experience. By using the first terminal (all-in-one conference machine) as the host device and connecting multiple second terminals (mobile phones or tablets) via USB as accessory devices to achieve device interconnection under local connection conditions, the local conference collaboration experience of the all-in-one conference machine can be improved. By seamlessly switching the first terminal and the second terminal connected by USB to a wireless network connection, users can be provided with a quick conversion method for different connection methods for conference collaboration, which can improve the efficiency of conference collaboration of the all-in-one conference machine. Meeting minutes and meeting materials can also be pushed to users through local USB connection, without uploading meeting materials to cyberspace, which can improve the security of conference collaboration.

[0235] In summary, the embodiments of the present application provide a conference terminal interaction method, in which a first terminal and a second terminal are connected by wire, a conference is established through the first terminal, and the second terminal is confirmed to support the target protocol, and the second terminal is added to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through the wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art, and achieving the effect of improving the interaction stability between multiple terminals.

[0236] Figure 5 This is a structural diagram of a conference terminal interaction device 500 provided in an embodiment of the present application. The conference terminal interaction device 500 can be implemented as part or all of an electronic device by software, hardware, or a combination of both. The first terminal and the second terminal are connected by wire. The device is applied to the first terminal. Please refer to Figure 5 , the conference terminal interaction device 500 includes:

[0237] The first establishing module 510 is used to establish a conference.

[0238] The first sending module 520 is configured to send a conference connection request to the second terminal via a wired connection, where the conference connection request is used to confirm whether the second terminal supports conference interaction via a target protocol.

[0239] The first receiving module 530 is configured to confirm that the second terminal supports the target protocol in response to receiving the connection confirmation information sent by the second terminal.

[0240] The first processing module 540 is configured to receive first confirmation information sent by the second terminal through a wired connection based on a target protocol, where the first confirmation information is used to confirm joining the conference.

[0241] The first confirmation module 550 is configured to confirm, based on the first confirmation information, that the second terminal has joined the conference via a wired connection.

[0242] Optionally, the first processing module includes:

[0243] The first detection module is configured to determine whether the second terminal is installed with conference collaboration software through a wired connection based on a target protocol.

[0244] The first responding module is configured to receive, in response to the second terminal being installed with the conference collaboration software, first confirmation information sent by the second terminal through a wired connection based on the conference collaboration software.

[0245] The second response module is used to control the second terminal to install the conference collaboration software in response to the second terminal not having the conference collaboration software installed, and execute the step of receiving the first confirmation information sent by the second terminal through a wired connection based on the conference collaboration software in response to the second terminal having the conference collaboration software installed.

[0246] Optionally, the first confirmation information includes information of the first participant, and the conference terminal interaction device further includes:

[0247] The first display module is used to display the information of the first participant.

[0248] Optionally, the conference terminal interaction device further includes:

[0249] The third receiving module is configured to receive a first connection switching request sent by the second terminal.

[0250] The third sending module is configured to send wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection.

[0251] The third confirmation module is configured to obtain second confirmation information sent by the second terminal based on the wireless channel information, and confirm that the second terminal joins the conference through the wireless connection.

[0252] Optionally, the first confirmation information includes information about the first conference participant, the second confirmation information includes information about the second conference participant, and the conference terminal interaction device further includes:

[0253] The fourth receiving module is configured to obtain first data information sent by the second terminal through a wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0254] The first associating module is used to associate the first data information with the first participant information.

[0255] The first acquisition module is used to acquire the meeting minutes information of the user corresponding to the first participant information, where the meeting minutes information includes the first participant and first data information associated with the first participant.

[0256] The second associating module is configured to associate the first data information with the second participant information in response to the first participant information and the second participant information being the same, where the first data information is data information associated with the first participant information.

[0257] Optionally, the first terminal is connected to a wireless local area network, and the conference terminal interaction device further includes:

[0258] The fifth sending module is configured to send second data information to the second terminal based on the first connection switching request, where the second data information includes an address and a password of the wireless local area network to which the first terminal is currently connected.

[0259] The fifth receiving module is configured to receive connection information sent by the second terminal based on the address and password of the wireless local area network.

[0260] The present application also provides another conference terminal interaction device, which is applied to a second terminal, wherein the first terminal and the second terminal are connected by wire, and the device includes:

[0261] The second receiving module is configured to receive a conference connection request sent by the first terminal, where the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol.

[0262] The second sending module is configured to send connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol.

[0263] The second confirmation module is configured to send first confirmation information to the first terminal based on the target protocol, where the first confirmation information is used to confirm joining the conference established by the first terminal.

[0264] In summary, the embodiments of the present application provide a conference terminal interaction device, wherein a first terminal and a second terminal are connected by wire. A conference is established through the first terminal, and after confirming that the second terminal supports the target protocol, the second terminal is added to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through the wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art and achieving the effect of improving the interaction stability between multiple terminals.

[0265] Figure 6 This is a flowchart of another conference terminal interaction method provided by the embodiment of the present application. Please refer to Figure 6 The present application also provides a conference terminal interaction method for a conference system, wherein the conference system includes a first terminal and a second terminal, and the first terminal and the second terminal are connected by wire. The method includes:

[0266] Step 601: The first terminal establishes a conference.

[0267] Step 602: The first terminal sends a conference connection request to the second terminal via a wired connection.

[0268] The conference connection request is used to confirm whether the second terminal supports conference interaction through the target protocol.

[0269] Step 603: The second terminal sends connection confirmation information to the first terminal based on the conference connection request.

[0270] The connection confirmation information is used to indicate that the second terminal supports the target protocol.

[0271] Step 604: In response to receiving the connection confirmation information sent by the second terminal, the first terminal confirms that the second terminal supports the target protocol.

[0272] Step 605: The second terminal sends first confirmation information to the first terminal through a wired connection based on the target protocol, where the first confirmation information is used to confirm joining the conference.

[0273] Step 606: The first terminal confirms, based on the first confirmation information, that the second terminal joins the conference through a wired connection.

[0274] Optionally, the second terminal sends first confirmation information to the first terminal based on the target protocol, where the first confirmation information is used to confirm joining the conference.

[0275] The first terminal receives, based on a target protocol and through a wired connection, first confirmation information sent by the second terminal, including:

[0276] The second terminal determines whether the conference collaboration software is installed based on the target protocol.

[0277] The first terminal determines whether the second terminal has conference collaboration software installed through a wired connection based on a target protocol.

[0278] In response to the conference collaboration software being installed, the second terminal sends first confirmation information to the first terminal through a wired connection based on the conference collaboration software.

[0279] In response to the second terminal being installed with the conference collaboration software, the first terminal receives the first confirmation information sent by the second terminal through a wired connection based on the conference collaboration software.

[0280] In response to the conference collaboration software not being installed, the second terminal installs the conference collaboration software, and in response to the conference collaboration software being installed, sends first confirmation information to the first terminal through a wired connection based on the conference collaboration software.

[0281] In response to the second terminal not having the conference collaboration software installed, the first terminal controls the second terminal to install the conference collaboration software, and executes the step of receiving first confirmation information sent by the second terminal through a wired connection based on the conference collaboration software in response to the second terminal having the conference collaboration software installed.

[0282] Optionally, the first confirmation information includes information of the first participant.

[0283] After the first terminal receives the first confirmation information sent by the second terminal through the wired connection, the method further includes:

[0284] The first terminal displays the first participant information.

[0285] Optionally, after the first terminal confirms that the second terminal joins the conference via a wired connection, the method further includes:

[0286] The second terminal sends a first connection switching request to the first terminal.

[0287] The first terminal receives a first connection switching request sent by the second terminal.

[0288] The first terminal sends wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection.

[0289] The second terminal joins the conference through a wireless connection based on the wireless channel information, and sends second confirmation information to the first terminal through the wireless connection.

[0290] The first terminal obtains second confirmation information sent by the second terminal based on the connection information, and confirms that the second terminal joins the conference through the wireless connection.

[0291] Optionally, the method further comprises:

[0292] The second terminal sends first data information to the first terminal through a wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0293] The first terminal obtains the first data information sent by the second terminal through a wired connection.

[0294] Optionally, after the first terminal obtains the first data information sent by the second terminal through the wired connection, the method further includes:

[0295] The first terminal associates the first data information with the first participant information.

[0296] The first terminal obtains meeting minutes information of a user corresponding to the first participant information, where the meeting minutes information includes the first participant and first data information associated with the first participant.

[0297] Optionally, the first confirmation information includes information about the first participant, and the second confirmation information includes information about the second participant.

[0298] After the first terminal obtains the first data information sent by the second terminal through the wired connection, the method further includes:

[0299] The first terminal obtains first data information sent by the second terminal through a wired connection, where the first data information includes at least one of conference voice information and conference file information.

[0300] The first terminal associates the first data information with the first participant information.

[0301] After the first terminal obtains second confirmation information sent by the second terminal based on the wireless channel information and confirms that the second terminal joins the conference through a wireless connection, the method further includes:

[0302] In response to the first participant information and the second participant information being identical, the first terminal associates the first data information with the second participant information, where the first data information is data information associated with the first participant information.

[0303] Optionally, the wireless channel information includes a web conference link.

[0304] Optionally, the first terminal is connected to a wireless local area network. After the first terminal receives the first connection switching request sent by the second terminal, the method further includes:

[0305] The first terminal sends second data information to the second terminal based on the first connection switching request. The second data information includes the address and password of the wireless local area network to which the first terminal is currently connected.

[0306] The second terminal receives the second data information sent by the first terminal, connects to the wireless local area network based on the address and password of the wireless local area network, and sends connection information to the first terminal.

[0307] Optionally, the target protocol includes the Android Open Accessory Protocol.

[0308] Optionally, the wired connection comprises a USB connection.

[0309] In summary, an embodiment of the present application provides a conference terminal interaction method for a conference system, wherein a first terminal and a second terminal are connected by wire, a conference is established through the first terminal, and after confirming that the second terminal supports the target protocol, the second terminal is added to the conference. In this way, the first terminal and the second terminal can achieve local conference interaction through a wired connection, so that the conference interaction between the first terminal and the second terminal does not need to rely on a wired network, solving the problem of poor interaction stability between multiple terminals in the related art, and achieving the effect of improving the interaction stability between multiple terminals.

[0310] In addition, an embodiment of the present application also provides a conference terminal interaction device, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement a conference terminal interaction method as in any of the above embodiments.

[0311] In addition, an embodiment of the present application also provides a computer storage medium, which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement a conference terminal interaction method as in any of the above embodiments.

[0312] In addition, embodiments of the present application further provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the conference terminal interaction method of any of the above embodiments.

[0313] In this application, the terms "first", "second", "third", "fourth" and "fifth" are used for descriptive purposes only and should not be understood as indicating or implying relative importance. The term "plurality" refers to two or more, unless otherwise expressly limited.

[0314] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0315] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0316] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0317] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A conference terminal interaction method, characterized in that: The method is applied to a first terminal, wherein the first terminal and a second terminal are connected by a wire, wherein the wired connection includes a universal serial bus connection, and the method includes: Establish a meeting; Sending a conference connection request to the second terminal through the wired connection, where the conference connection request is used to confirm whether the second terminal supports conference interaction through the target protocol; In response to receiving the connection confirmation information sent by the second terminal, confirming that the second terminal supports the target protocol; Based on the target protocol, receiving first confirmation information sent by the second terminal through the wired connection, where the first confirmation information is used to confirm joining the conference; Confirming, based on the first confirmation information, that the second terminal joins the conference through the wired connection; receiving a first connection switching request sent by the second terminal; Sending wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection; Second confirmation information sent by the second terminal based on the wireless connection is obtained to confirm that the second terminal joins the conference through the wireless connection.

2. The method according to claim 1, characterized in that The receiving, based on the target protocol and through the wired connection, first confirmation information sent by the second terminal includes: Based on the target protocol, determining, through the wired connection, whether the second terminal has conference collaboration software installed; In response to the second terminal being installed with the conference collaboration software, receiving first confirmation information sent by the second terminal through the wired connection based on the conference collaboration software; In response to the second terminal not having the conference collaboration software installed, controlling the second terminal to install the conference collaboration software, and executing the step of receiving the first confirmation information sent by the second terminal through the wired connection based on the conference collaboration software in response to the second terminal having the conference collaboration software installed.

3. The method according to claim 1, characterized in that The first confirmation information includes the first participant information; After receiving the first confirmation information sent by the second terminal through the wired connection, the method further includes: Display the first participant's information.

4. The method according to claim 3, characterized in that The method further comprises: First data information sent by the second terminal is obtained through the wired connection, where the first data information includes at least one of conference voice information and conference file information.

5. The method according to claim 4, characterized in that After obtaining the first data information sent by the second terminal through the wired connection, the method further includes: Associating the first data information with the first participant information; Acquire meeting minutes information of a user corresponding to the first participant information, where the meeting minutes information includes the first participant and first data information associated with the first participant.

6. The method according to claim 1, characterized in that The first confirmation information includes the first participant information, and the second confirmation information includes the second participant information; After receiving the first confirmation information sent by the second terminal through the wired connection, the method further includes: obtaining, through the wired connection, first data information sent by the second terminal, where the first data information includes at least one of conference voice information and conference file information; Associating the first data information with the first participant information; After confirming that the second terminal joins the conference through the wireless connection, the method further includes: In response to the first participant information and the second participant information being the same, the first data information is associated with the second participant information, where the first data information is data information associated with the first participant information.

7. The method according to claim 1, characterized in that The wireless channel information includes a network conference link.

8. The method according to claim 1, characterized in that The first terminal is connected to a wireless local area network. After receiving the first connection switching request sent by the second terminal, the method further includes: Sending second data information to the second terminal based on the first connection switching request, where the second data information includes an address and a password of a wireless local area network to which the first terminal is currently connected; Receive connection information sent by the second terminal based on the address and password of the wireless local area network.

9. The method according to claim 1, characterized in that The target protocol includes the Android Open Accessory Protocol.

10. A conference terminal interaction method, characterized in that: The method is applied to a second terminal, the first terminal and the second terminal are connected by wire, the wired connection includes a universal serial bus connection, and the method includes: receiving a conference connection request sent by the first terminal, where the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol; Sending connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol; Based on the target protocol, sending first confirmation information to the first terminal, where the first confirmation information is used to confirm joining the conference established by the first terminal; Sending a first connection switching request to the first terminal; receiving wireless channel information sent by the first terminal, where the wireless channel information is used to indicate joining the conference via a wireless connection; Based on the wireless channel information, join the conference through the wireless connection, and send second confirmation information to the first terminal through the wireless connection.

11. A conference terminal interaction method, characterized in that: For a conference system, the conference system includes a first terminal and a second terminal, the first terminal and the second terminal are connected by a wire, the wired connection includes a universal serial bus connection, and the method includes: The first terminal establishes a conference; The first terminal sends a conference connection request to the second terminal through the wired connection, where the conference connection request is used to confirm whether the second terminal supports conference interaction through a target protocol; The second terminal sends connection confirmation information to the first terminal based on the conference connection request, where the connection confirmation information is used to indicate that the second terminal supports the target protocol; In response to receiving the connection confirmation information sent by the second terminal, the first terminal confirms that the second terminal supports the target protocol; The second terminal sends, based on the target protocol, first confirmation information to the first terminal through the wired connection, where the first confirmation information is used to confirm joining the conference; The first terminal confirms, based on the first confirmation information, that the second terminal joins the conference through the wired connection; The second terminal sends a first connection switching request to the first terminal; The first terminal sends wireless channel information to the second terminal based on the first connection switching request, where the wireless channel information is used to indicate joining the conference through a wireless connection; The second terminal joins the conference through the wireless connection based on the wireless channel information, and sends second confirmation information to the first terminal through the wireless connection; The first terminal obtains the second confirmation information, and confirms that the second terminal joins the conference through the wireless connection.

12. A conference terminal interactive device, characterized in that: The conference terminal interaction device includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the conference terminal interaction method as described in any one of claims 1 to 11.

Images