Cascade networking method, audio interaction method, equipment and system

Abstract

The invention relates to the technical field of Bluetooth communication, and discloses a cascading networking method and an audio interaction method, device and system, and the method comprises the steps: a host searches a target pairing code of a device to be networked during cascading networking; if the target pairing code is matched with the local private pairing code, the host uses the equipment to be networked as a slave; if the target pairing code is not matched with the local private pairing code, the host judges whether the target pairing code is matched with the public pairing code, and if the target pairing code is matched with the public pairing code, the host takes the equipment to be networked as a slave; and the host is in communication connection with the slave so as to realize cascade networking. During audio interaction, if the host receives audio data sent by the conference terminal, synchronizing the audio data to the slave for playing; and if the host receives the recording data sent by the slave, the host performs centralized processing on the recording data and uploads the processed recording data to the conference terminal. The problem that the audio transmission distance is short due to the fact that the conference microphone is limited by the length of the network cable can be solved.

Description

Technical Field

[0001] The present invention relates to the technical field of Bluetooth communications, and in particular to a cascade networking method, an audio interaction method, terminal equipment, and a conference microphone management system. Background Art

[0002] Currently, conference microphones primarily utilize a cascaded network structure using wired Ethernet connections. In this method, the master and slave devices are connected via Ethernet cables, which enable audio transmission and state synchronization between the master and slave devices. However, this cascaded network structure relies solely on Ethernet cables for communication and synchronization, resulting in a relatively short audio transmission distance between the microphones, limited by the length of the Ethernet cables. Summary of the Invention

[0003] In view of this, the present invention provides a cascade networking method, an audio interaction method, a device and a system to solve the problem that the conference microphone is limited by the length of the network cable, resulting in a short audio transmission distance.

[0004] To achieve the above-mentioned object, an embodiment of the present invention provides a cascade networking method applicable to a terminal device serving as a host. The cascade networking method includes:

[0005] Search for the target pairing code of the device to be networked;

[0006] If the target pairing code matches the local private pairing code, the corresponding device to be networked is used as a slave;

[0007] If the target pairing code does not match the local private pairing code, determining whether the target pairing code matches the public pairing code;

[0008] When the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave;

[0009] Communicate with the slave machine to achieve cascade networking.

[0010] As an improvement to the above solution, when the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave, including:

[0011] When the target pairing code matches the public pairing code, obtaining a signal strength indicator value corresponding to the target pairing code;

[0012] When the signal strength indicator value is greater than a preset strength threshold, the corresponding device to be networked is used as a slave.

[0013] As an improvement to the above solution, the cascade networking method further includes, after the communication connection with the slave device is established:

[0014] receiving a target private pairing code sent by the slave device;

[0015] If the slave device is a temporary binding device, the target private pairing code is saved, and a temporary private pairing code is sent to all the slave devices, so that the slave devices are connected to the terminal device according to the temporary private pairing code;

[0016] If the slave device is not a temporarily bound device, the target private pairing code is returned to the slave device.

[0017] As an improvement to the above solution, the cascade networking method further includes:

[0018] When a preset network disbanding condition is met, a temporary binding removal instruction is sent to all the slaves, so that the slaves clear the received temporary private pairing codes.

[0019] To achieve the above-mentioned purpose, an embodiment of the present invention further provides an audio interaction method, which is applicable to a terminal device serving as a host. The audio interaction method includes:

[0020] Networking is performed with a terminal device serving as a slave based on the cascade networking method of any embodiment;

[0021] When receiving audio data sent by the conference terminal, synchronizing the audio data to the slave device so that the slave device plays the audio data;

[0022] When the recording data sent by the slave is received, the recording data is centrally processed to obtain processed recording data;

[0023] The processed recording data is uploaded to the conference terminal.

[0024] As an improvement to the above solution, the audio interaction method further includes:

[0025] When receiving a first volume operation instruction sent by the slave device, making a decision on the first volume operation instruction to obtain a decision result;

[0026] The decision result is fed back to the slave device and the conference terminal, so that the slave device and the conference terminal adjust the volume according to the decision result.

[0027] As an improvement to the above solution, the audio interaction method further includes:

[0028] When a second volume operation instruction sent by the conference terminal is received, the second volume operation instruction is sent to the slave device, so that the slave device adjusts the volume according to the second volume operation instruction.

[0029] As an improvement to the above solution, the audio interaction method further includes:

[0030] When communicating with the slave device, the slave device is controlled to turn off the Bluetooth function and the Universal Serial Bus function through the asynchronous link.

[0031] To achieve the above-mentioned purpose, an embodiment of the present invention also provides a terminal device, including: a microphone, a memory and a processor, the processor is communicatively connected to the microphone and the memory, the memory stores computer instructions, and the processor executes the computer instructions to execute the cascade networking method of any of the above-mentioned embodiments and / or the audio interaction method of any of the above-mentioned embodiments.

[0032] To achieve the above objectives, an embodiment of the present invention further provides a conference microphone management system, the system comprising:

[0033] Conference terminal;

[0034] Multiple terminal devices equipped with microphones; wherein the terminal device connected to the software protector serves as a host, the host is connected to the conference terminal, and the host is used to execute the cascade networking method of any of the above embodiments and / or execute the audio interaction method of any of the above embodiments.

[0035] Compared with the prior art, the present invention has the following beneficial effects:

[0036] On the one hand, when the terminal device acting as the host performs cascade networking, it searches for the target pairing code of the device to be networked. If the target pairing code matches the local private pairing code, the corresponding device to be networked is used as a slave. If the target pairing code does not match the local private pairing code, it determines whether the target pairing code matches the public pairing code. When the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave. The terminal device communicates with the slave to achieve cascade networking without the need for a wired connection using a network cable. Therefore, it can solve the problem of short audio transmission distance caused by the length of the network cable of the conference microphone. At the same time, the private pairing code and the public pairing code can be used to restrict the slave device from joining the network, thereby improving the security of the cascade network.

[0037] On the other hand, when the terminal device serving as the host performs audio interaction, the cascade networking method of the present invention is used to establish a wireless connection between the host and the slave. Furthermore, if audio data is received from the conference terminal, the audio data is synchronized to the slave so that the slave plays the audio data. If recording data is received from the slave, the recording data is centrally processed to obtain processed recording data, which is then uploaded to the conference terminal. Therefore, audio interaction and transmission between the conference terminal, the host, and the slave can be achieved, and compared to the audio interaction method using a wired connection via a network port, audio synchronization anomalies are less likely to occur, thereby improving audio quality. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0039] Figure 1 is a flow chart of a cascade networking method according to an embodiment of the present invention;

[0040] Figure 2 This is a schematic diagram of connections between various terminals in a conference microphone management system according to an embodiment of the present invention;

[0041] Figure 3 is a flow chart of another cascade networking method according to an embodiment of the present invention;

[0042] Figure 4 is a schematic diagram of interaction between a host and a slave according to an embodiment of the present invention;

[0043] Figure 5 is a flowchart of an audio interaction method according to an embodiment of the present invention;

[0044] Figure 6 is a flowchart of another audio interaction method according to an embodiment of the present invention;

[0045] Figure 7 is a structural block diagram of a terminal device according to an embodiment of the present invention;

[0046] Figure 8 This is a structural block diagram of a conference microphone management system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0047] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.

[0048] At present, the cascade networking method of wired connection via network port is mainly used between conference microphones. This method can only communicate and synchronize through the network cable, resulting in the audio transmission distance between conference microphones being limited by the length of the network cable, and the audio transmission distance is relatively short.

[0049] In view of this, an embodiment of the present invention provides a cascade networking method applicable to a terminal device serving as a host, such as a conference microphone. It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system, such as a set of computer-executable instructions, and that although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown.

[0050] Figure 1 FIG. 1 is a flow chart of a cascade networking method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0051] Step S11: searching for a target pairing code of the device to be networked.

[0052] It should be noted that the terminal device acting as the host is connected to the dongle. The terminal device that the dongle is connected to for the first time will be automatically identified as the host. When the host is powered on, it can be paired directly with the dongle without the need for keystrokes, simplifying the connection.

[0053] Specifically, the above step S11 includes searching for a target pairing code of the device to be networked within a preset detection range. Optionally, the preset detection range is 0.5m.

[0054] It is understandable that if a non-host terminal device wants to connect to the dongle, it needs to be within the preset detection range of the dongle (e.g., 0.5m) and turn on broadcasting to connect to the dongle.

[0055] Step S12: If the target pairing code matches the local private pairing code, the corresponding device to be networked is used as a slave.

[0056] It should be noted that if the target pairing code matches the local private pairing code stored locally on the host, it indicates that the device to be networked corresponding to the target pairing code is a terminal device bound to the host, and can be directly connected to the terminal device to enable the terminal device to join the network.

[0057] Step S13: If the target pairing code does not match the local private pairing code, it is determined whether the target pairing code matches the public pairing code.

[0058] It should be noted that each terminal device has a unique private pairing code, and the public pairing code is a preset value. When the dongle leaves the factory, the private pairing code stored locally on the dongle is the same as the public pairing code. When the dongle connects to another terminal device, it will record the private pairing code of the bound terminal device to form a binding relationship.

[0059] It should be noted that after powering on, the device to be connected will start broadcasting with its private pairing code. Each device to be connected has a corresponding button, such as a hardware button or a virtual button, which can be used to control the device to broadcast using the public pairing code. The host on the dongle side searches for all / preset detection range of terminal devices (i.e., devices to be connected) that are broadcasting.

[0060] Step S14: When the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave.

[0061] It should be noted that if the searched target pairing code does not match the local private pairing code, the corresponding device to be networked is not a bound device of this terminal device. Therefore, it is necessary to determine whether the target pairing code matches the public pairing code to determine whether the device to be networked is a public device.

[0062] Furthermore, when the target pairing code does not match the public pairing code, the process returns to step S11 to search for target pairing codes of other devices to be networked.

[0063] Step S15: communicate with the slave machine to achieve cascade networking.

[0064] For example, Figure 2 As shown in the figure, in a conference microphone management system, the dongle can be connected to the conference terminal through the universal serial bus (USB). The host on the dongle side can connect to each slave device through the next-generation Bluetooth audio technology standard LE Audio.

[0065] The cascade networking method provided in this embodiment is that when the terminal device serving as the host performs cascade networking, it searches for the target pairing code of the device to be networked; if the target pairing code matches the local private pairing code, the corresponding device to be networked is used as a slave; if the target pairing code does not match the local private pairing code, it determines whether the target pairing code matches the public pairing code; when the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave; and the terminal device is connected to the slave to achieve cascade networking without the need for a wired connection using a network cable. Therefore, it can solve the problem of a short audio transmission distance caused by the length of the network cable when the conference microphone is limited. At the same time, it can use private pairing codes and public pairing codes to restrict the slave from entering the network, thereby improving the security of the cascade network.

[0066] As one optional implementation, the above step S14 includes: when the target pairing code matches the public pairing code, obtaining a signal strength indicator value corresponding to the target pairing code; when the signal strength indicator value is greater than a preset strength threshold, using the corresponding device to be networked as a slave.

[0067] It should be noted that if the searched target pairing code does not match the local private pairing code, the corresponding device to be networked is not bound to the terminal device. Therefore, the host on the dongle side needs to use the signal strength indicator (RSSI) to determine whether it is connected to the device to be networked as a public device to prevent cascaded devices from connecting to the network at will.

[0068] Furthermore, when the target pairing code does not match the public pairing code, the target pairing codes of other devices to be networked are searched again.

[0069] As one of the optional implementations, the cascade networking method of the present invention further includes, after the communication connection with the slave machine: receiving the target private pairing code sent by the slave machine; if the slave machine is a temporarily bound device, saving the target private pairing code, and sending the temporary private pairing code to all slave machines, so that the slave machine is connected to the terminal device according to the temporary private pairing code; if the slave machine is not a temporarily bound device, returning the target private pairing code to the slave machine.

[0070] It should be noted that after connecting to a slave, the slave will send its target private pairing code to the master. If the master is not bound to the slave, it will save the slave's target private pairing code and use the slave as a bound device. The next time the slave is scanned, both parties can connect directly using the same private pairing code. At the same time, the master will send either a temporary private pairing code or a target private pairing code to all slaves, depending on whether the slave is a temporarily bound device. For example, if the slave is a bound device, the master will return the received target pairing code to the connected slave.

[0071] Therefore, if the private pairing code received by the slave is consistent with the slave's own target private pairing code, the slave does not need to save the target pairing code returned by the master. If the private pairing code received by the slave is inconsistent with the slave's own target private pairing code, the slave saves the temporary private pairing code sent by the master as a temporary network access device.

[0072] As you can understand, for a slave that is temporarily connected to the network, after receiving the temporary private pairing code sent by the master on the dongle side, it stores the temporary private pairing code in memory. Before receiving the temporary binding release command or power failure, the slave uses the temporary private pairing code to broadcast. At this point, the master and multiple slaves all use the same temporary private pairing code to mark a private network.

[0073] As an optional implementation manner, the cascade networking method of the present invention further includes: when a preset network dissolution condition is met, sending a temporary binding removal instruction to all slaves, so that the slaves clear the received temporary private pairing codes.

[0074] Understandably, after the work of a private network is completed, such as a meeting, the host on the dongle side sends a temporary binding removal instruction to all slaves, and each slave clears the temporary private pairing code in the memory, thereby achieving the effect of network dissolution.

[0075] As an example, the cascade networking method provided by the present invention is described below with a specific implementation method. Figure 3 and Figure 4 As shown, in this specific implementation mode, the host and the slave respectively perform the following steps:

[0076] 1. The host performs the following steps:

[0077] In step S21 , the host alternately searches for the public pairing code and the private pairing code, and then executes step S22 .

[0078] Step S22, determining whether a device to be networked is scanned, if so, executing step S23, if not, returning to step S21.

[0079] Step S23: Determine whether the received target pairing code is consistent with the local private pairing code. If so, execute step S26; if not, execute step S24.

[0080] Step S24, determining whether the device to be networked is a public device, if so, executing step S25, if not, returning to step S21.

[0081] Specifically, whether the target pairing code of the device to be networked is consistent with the public pairing code is determined to determine whether the device to be networked is a public device.

[0082] Step S25, determining whether the RSSI broadcast by the device to be networked is greater than a preset strength threshold, if so, executing step S26, if not, returning to step S21.

[0083] Step S26: The device to be networked is used as a slave, connected to the slave, and then step S27 is executed.

[0084] Step S27: Receive the private pairing code of the slave device, and then execute step S28.

[0085] Step S28: Return the private pairing code to the slave device, and then execute step S29.

[0086] Step S29, determine whether the host has a bound device, if so, execute step S31, if not, execute step S30.

[0087] In step S30 , the private pairing code of the slave device is saved as a bound device, and then step S31 is executed.

[0088] Step S31: Network access is successful, and then step S32 is executed.

[0089] Step S32, determining whether to release the temporary binding, if so, sending a release temporary binding command to the slave, if not, returning to step S31.

[0090] 2. The slave performs the following steps:

[0091] Step S41: broadcast the private pairing code, and then execute step S42.

[0092] Step S42, determining whether the broadcast button of the public pairing code is pressed, if so, executing step S43, if not, returning to step S41.

[0093] Step S43: broadcast the public pairing code, and then execute step S44.

[0094] Step S44, determining whether the slave device is connected, if so, executing step S45, if not, returning to step S41.

[0095] In step S45, the private pairing code is sent to the host, and then step S46 is executed.

[0096] Step S46: Receive the host's private pairing code, and then execute step S47.

[0097] Step S47, determining whether the received private pairing code is consistent with its own private pairing code, if so, executing step S48, if not, executing step S49.

[0098] Step S48: determine that the current terminal device is a bound device, do not save the received private pairing code, and end this process.

[0099] Step S49: determine that the current terminal device is an unbound device, save the received private pairing code as a temporary private pairing code, and then execute step S50.

[0100] Step S50, determining whether a temporary binding release command is received, if so, executing step S51, if not, continuing to execute step S50.

[0101] Step S51: Clear the temporary private pairing code and the process ends.

[0102] It is worth noting that in the relevant technology, the cascade networking method is: according to the logic of free pairing, the slave turns on the broadcast, and the host scans the slave's broadcast name. If the broadcast name matches, the host will connect to the slave without the need for private pairing codes, public pairing codes, signal strength indicator values ​​and other broadcast information. However, this method has the following defects: First, the slave needs to turn on the broadcast for each connection, and it is impossible to automatically connect to the host and bind the terminal device. Second, when the call between the host and the slave is disconnected, the slave cannot automatically reconnect to the network and needs to re-enter the call. Third, unrelated meeting participants can turn on the device broadcast and enter the meeting, and there is no access mechanism.

[0103] In contrast, the present invention is based on the cascade networking method of LE Audio's low-power Bluetooth isochronous connection (Connected Isochronous Stream, CIS). This networking method is simple and easy to use, and can achieve wireless connection and fast scanning connection between multiple terminal devices, and the connection distance is relatively long (e.g., more than 10 meters). Not only that, the pairing code matching mechanism of this embodiment and the preset strength threshold corresponding to the signal strength indicator value can have a network access mechanism and a network dissolution mechanism when binding the terminal device, so as to achieve automatic connection of the terminal device, and, when the bound terminal device is back online, automatically reconnect to avoid unauthorized terminal devices from entering the network. In addition, the number of terminal devices that can be connected by the present invention is related to the bandwidth. In theory, as long as the bandwidth is large enough, wireless cascading can be achieved.

[0104] In an embodiment of the present invention, an audio interaction method is provided, applicable to a terminal device serving as a host, such as a conference microphone. It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system, such as a set of computer-executable instructions, and that, although a logical sequence is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown.

[0105] Figure 5is a flow chart of an audio interaction method according to an embodiment of the present invention. Figure 5 As shown, the process includes the following steps:

[0106] Step S61: Networking is performed with a terminal device serving as a slave based on any of the above cascade networking methods.

[0107] Specifically, the host is connected to each slave via the new generation Bluetooth audio technology standard LE Audio.

[0108] Step S62: When the audio data sent by the conference terminal is received, the audio data is synchronized to the slave device so that the slave device plays the audio data.

[0109] As an optional embodiment, the audio interaction method of the present invention further includes disconnecting an asynchronous access control list (ACL) between the terminal device and the slave device when no communication with the slave device is in progress. In this case, there is no interaction between the host and the slave device, and the Bluetooth function and Universal Serial Bus (USB) function of each slave device are enabled.

[0110] As one optional embodiment, the audio interaction method of the present invention further includes, before synchronizing the audio data to the slave, controlling the opening of an asynchronous link and / or a synchronous link between the terminal device and the slave when communicating with the slave. Specifically, the synchronous link is an LE synchronous link (Isochronous Channels, ISOC).

[0111] Specifically, when the host receives downlink audio data sent by the conference terminal via the USB, it synchronizes the audio data to the slave via the synchronization link, so that the slave plays the audio data.

[0112] Step S63: When the recording data sent by the slave device is received, the recording data is centrally processed to obtain processed recording data.

[0113] Specifically, the slave collects recording data through its microphone and uploads it to the master via a synchronous link. The master then processes the data using various sampling and synchronization algorithms. The master then uploads the processed data to the conference terminal. For more information on centralized processing methods, refer to the methods used by other conference microphone management systems to process recording data. We will not elaborate on these methods here.

[0114] Step S64: Upload the processed recording data to the conference terminal.

[0115] Specifically, the processed recording data is uploaded to the conference terminal through the USB function.

[0116] The audio interaction method provided in this embodiment is that when the terminal device serving as the host performs audio interaction, if it receives audio data sent by the conference terminal, it synchronizes the audio data to the slave device so that the slave device can play the audio data; if it receives recording data sent by the slave device, it centrally processes the recording data to obtain processed recording data; and uploads the processed recording data to the conference terminal. Therefore, audio interaction transmission between the conference terminal, the host, and the slave device can be achieved. Compared with the audio interaction method of the network port wired connection, the audio synchronization of this embodiment does not require an algorithm to make decisions, the audio processing is relatively simple, audio synchronization anomalies are not likely to occur, the audio quality is relatively high, and the audio interaction method of wireless communication transmission has low transmission delay and high audio interaction efficiency.

[0117] As one of the optional implementations, the audio interaction method of the present invention also includes: formulating a private protocol with each slave machine, and synchronizing the target state with each slave machine through an asynchronous link, where the target state includes at least one of a volume state and a mute switch state.

[0118] It is understandable that the host develops a private protocol to achieve state synchronization between the host and the slave through an asynchronous link, such as volume synchronization, mute switch and other state control.

[0119] As one of the optional implementations, if the target state is volume synchronization, the audio interaction method of the present invention also includes: when receiving a first volume operation instruction sent by the slave machine, making a decision on the first volume operation instruction to obtain a decision result; and feeding back the decision result to the slave machine and the conference terminal so that the slave machine and the conference terminal adjust the volume according to the decision result.

[0120] Specifically, the slave device sends the received volume operation instruction (i.e., volume increase or decrease instruction) to the host through an asynchronous link, and the host makes a unified decision and then synchronizes the decision result (i.e., the decided volume value) to the slave device and the conference terminal.

[0121] As an optional implementation, the audio interaction method of the present invention further includes: when receiving a second volume operation instruction sent by the conference terminal, sending the second volume operation instruction to the slave device, so that the slave device adjusts the volume according to the second volume operation instruction.

[0122] Specifically, when the conference terminal returns a volume operation instruction to the host, the host will synchronize the volume operation instruction sent by the conference terminal to each slave.

[0123] It is understandable that the volume levels of the host, slaves, and conference terminals are synchronized with each other. Changing the volume of any one of the cascaded terminal devices will be synchronized with the other devices.

[0124] As an optional implementation manner, the audio interaction method of the present invention further includes: when communicating with the slave device, controlling the slave device to turn off the Bluetooth function and the Universal Serial Bus function through the asynchronous link.

[0125] It is worth noting that when the host communicates with the slave, the purpose of controlling the slave to turn off the Bluetooth function and the Universal Serial Bus function through the asynchronous link is to simplify the business layer logic to prevent business anomalies such as audio data, recording data, and volume synchronization.

[0126] It is worth noting that, in the embodiment of the present invention, the asynchronous link is used for connection and communication control between the host and the slave, and the synchronous link is used for transmission of audio data and recording data.

[0127] As an example, the audio interaction method provided by the present invention is described below with a specific implementation method. Figure 6 As shown, the specific implementation includes the following contents:

[0128] 1. The host and slave are connected through cascade networking.

[0129] 2. Determine whether the master and slave are in a call.

[0130] 3. If the host and the slave are not in a call, the asynchronous link between the host and the slave is disconnected, and the Bluetooth function and the universal serial bus function of the slave are used normally.

[0131] 4. If the host and the slave enter into a call, the asynchronous link interaction is started, and the slave turns off the Bluetooth function and the Universal Serial Bus function.

[0132] 5. During a call, the slave device sends uplink recording data, first volume operation instructions and other status synchronization to the master device, while the master device sends downlink audio data, second volume operation instructions and other status synchronization to the slave device.

[0133] See also Figure 7 , is a structural block diagram of a terminal device provided by an embodiment of the present invention.

[0134] An embodiment of the present invention provides a terminal device, such as Figure 7As shown, the terminal device includes: a microphone 71, one or more processors 72, a memory 73, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses for communication and can be installed on a common motherboard or installed in other ways as needed. The processor 72 can process instructions executed in the terminal device, including instructions stored in or on the memory 73 to display graphical information of a GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors 72 and / or multiple buses can be used together with multiple memories 73 and multiple memories 73. Similarly, multiple terminal devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0135] The processor 72 may be a central processing unit, a network processor, or a combination thereof. The processor 72 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0136] The memory 73 stores instructions that can be executed by at least one processor 72, so as to enable the at least one processor 72 to execute the method shown in the above embodiment.

[0137] The memory 73 may include a program storage area and a data storage area. The program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal device. In addition, the memory 73 may include high-speed random access memory and may also include non-transient memory, such as at least one disk storage device, flash memory device, or other non-transient solid-state memory device. In some optional embodiments, the memory 73 may optionally include a memory 73 remotely located relative to the processor 72, and these remote memories may be connected to the terminal device via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0138] The memory 73 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 73 may also include a combination of the above types of memory.

[0139] Among them, if the module / unit integrated in the terminal device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. Computer-readable media may include: any entity or device that can carry computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electrical carrier signal, telecommunication signal and software distribution medium, etc.

[0140] See also Figure 8 , is a structural block diagram of a conference microphone management system provided by an embodiment of the present invention.

[0141] A conference microphone management system provided by an embodiment of the present invention includes: a conference terminal and multiple terminal devices equipped with microphones; wherein the terminal device connected to the software protector dongle serves as a host, the host is connected to the conference terminal, and the host is used to execute the cascade networking method of any of the above-mentioned embodiments, and / or execute the audio interaction method of any of the above-mentioned embodiments.

[0142] Furthermore, the host is connected to the conference terminal via a universal serial bus. When executing the cascade networking method of any of the above embodiments, the host is connected to the terminal device serving as the slave via Bluetooth.

[0143] Specifically, the host is connected to each slave via the new generation Bluetooth audio technology standard LE Audio.

[0144] Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention. Such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A cascade networking method, characterized in that: Applicable to a terminal device serving as a host, the cascade networking method includes: Search for the target pairing code of the device to be networked; If the target pairing code matches the local private pairing code, the corresponding device to be networked is used as a slave; If the target pairing code does not match the local private pairing code, determining whether the target pairing code matches the public pairing code; When the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave; Communicate with the slave machine to achieve cascade networking.

2. The cascade networking method according to claim 1, wherein: When the target pairing code matches the public pairing code, the corresponding device to be networked is used as a slave, including: When the target pairing code matches the public pairing code, obtaining a signal strength indicator value corresponding to the target pairing code; When the signal strength indicator value is greater than a preset strength threshold, the corresponding device to be networked is used as a slave.

3. The cascade networking method according to claim 1, wherein: After the cascade networking method is connected to the slave device for communication, the method further includes: receiving a target private pairing code sent by the slave device; If the slave device is a temporary binding device, the target private pairing code is saved, and a temporary private pairing code is sent to all the slave devices, so that the slave devices are connected to the terminal device according to the temporary private pairing code; If the slave device is not a temporarily bound device, the target private pairing code is returned to the slave device.

4. The cascade networking method according to claim 3, wherein: The cascade networking method further includes: When a preset network disbanding condition is met, a temporary binding removal instruction is sent to all the slaves, so that the slaves clear the received temporary private pairing codes.

5. An audio interaction method, characterized in that: Applicable to a terminal device serving as a host, the audio interaction method includes: Networking with a terminal device serving as a slave based on the cascade networking method according to any one of claims 1 to 4; When receiving audio data sent by the conference terminal, synchronizing the audio data to the slave device so that the slave device plays the audio data; When the recording data sent by the slave is received, the recording data is centrally processed to obtain processed recording data; The processed recording data is uploaded to the conference terminal.

6. The audio interaction method according to claim 5, wherein: The audio interaction method further includes: When receiving a first volume operation instruction sent by the slave device, making a decision on the first volume operation instruction to obtain a decision result; The decision result is fed back to the slave device and the conference terminal, so that the slave device and the conference terminal adjust the volume according to the decision result.

7. The audio interaction method according to claim 5, wherein: The audio interaction method further includes: When a second volume operation instruction sent by the conference terminal is received, the second volume operation instruction is sent to the slave device, so that the slave device adjusts the volume according to the second volume operation instruction.

8. The audio interaction method according to claim 5, wherein: The audio interaction method further includes: When communicating with the slave device, the slave device is controlled to turn off the Bluetooth function and the Universal Serial Bus function through the asynchronous link.

9. A terminal device, characterized in that: include: A microphone, a memory and a processor, wherein the processor is communicatively connected to the microphone and the memory, the memory stores computer instructions, and the processor executes the cascade networking method according to any one of claims 1 to 4 and / or the audio interaction method according to any one of claims 5 to 8 by executing the computer instructions.

10. A conference microphone management system, characterized in that: The system comprises: Conference terminal; Multiple terminal devices equipped with microphones; wherein the terminal device connected to the software protector serves as a host, the host is connected to the conference terminal, and the host is used to execute the cascade networking method described in any one of claims 1 to 4, and / or the audio interaction method described in any one of claims 5 to 8.

Images