Protocol device connection method, device, storage medium

Abstract

The application discloses a protocol device connection method and device and a storage medium, and relates to the technical field of network audio. The method comprises the following steps: listening to connection requests sent by various protocol devices through a preset discovery protocol type, wherein the protocol devices comprise network audio devices, wireless audio devices and control devices; in the case that the connection requests are listened to, querying device attribute information of the corresponding protocol devices in a system device list according to the connection requests, wherein the system device list stores device attribute information of the protocol devices which are discovered and registered in advance; determining a communication connection mode suitable for the corresponding protocol devices according to the device attribute information, establishing a data transmission channel with the corresponding protocol devices based on the communication connection mode, and performing data transmission with the corresponding protocol devices based on the data transmission channel. Through the above technical means, the process of automatic discovery and connection of various protocol devices is effectively unified, and the deployment efficiency, reliability and expansibility of the audio system are optimized.

Description

Technical Field

[0001] This application relates to the field of network audio technology, and in particular to a protocol device connection method, device, and storage medium. Background Technology

[0002] An audio system is a technological system integrating audio acquisition, transmission, processing, and playback functions, widely used in live performances, conference systems, broadcast production, and film and television post-production. With the development of networking and wireless technologies, audio systems have gradually evolved into complex architectures with multiple protocols, encompassing the following core modules: network audio devices, wireless audio devices, and control devices. Network audio devices transmit audio according to network audio protocol standards such as AES67; wireless audio devices are audio devices that transmit audio based on wireless audio technology, such as wireless microphones; and control devices are terminal devices provided to users for managing the audio system, such as conference control panels. After discovering and connecting to network audio devices, wireless audio devices, and control devices, the audio system can configure and manage them. The different discovery and connection protocols used by network audio devices, wireless audio devices, and control devices contribute to the evolution of audio systems into complex multi-protocol architectures.

[0003] In existing technologies, audio systems have evolved into complex architectures integrating multiple protocols. The discovery mechanisms for multiple devices under these protocols are isolated, leading to different methods for discovering and connecting network audio devices, wireless audio devices, and control devices. This necessitates manual configuration by professionals for each device's discovery and connection process, resulting in inconsistent device management. Therefore, in complex network audio scenarios, the lack of a unified and automated solution for discovering and connecting devices severely restricts the deployment efficiency, reliability, and scalability of audio systems. Summary of the Invention

[0004] This application provides a method, device, and storage medium for connecting protocol devices, which uses different discovery protocols to listen for connection requests sent by different protocol devices, and selects a connection process that is compatible with the protocol device according to the connection request. The data transmission channel is established with the protocol device according to the connection process, which effectively unifies the automated discovery and connection process of various protocol devices. It solves the problem in the prior art that relies on professionals to manually configure the discovery and connection process of each device independently, and optimizes the deployment efficiency, reliability, and scalability of the audio system.

[0005] Firstly, this application provides a method for connecting protocol devices, including:

[0006] By using a preset discovery protocol type, the system listens for connection requests sent by various protocol devices, including network audio devices, wireless audio devices, and control devices.

[0007] Upon detecting the connection request, the system queries the device attribute information of the corresponding protocol device in the system device list based on the connection request. The system device list stores the device attribute information of the protocol devices that have been discovered and registered in advance.

[0008] Based on the device attribute information, determine the communication connection method adapted to the corresponding protocol device, establish a data transmission channel with the corresponding protocol device based on the communication connection method, and perform data transmission with the corresponding protocol device based on the data transmission channel.

[0009] Using the above-mentioned technical means, a multi-protocol compatible audio system can be constructed. The audio system can automatically discover and connect to devices with multiple protocols, realize unified management of the discovery and connection process of multiple protocol devices, eliminate the need for professionals to manually configure the discovery and connection process of each protocol device independently, simplify the deployment and operation of the audio system, and provide a user-friendly, highly reliable, highly compatible and highly scalable audio system.

[0010] Optionally, the step of listening for connection requests sent by various protocol devices through a preset discovery protocol type includes:

[0011] According to the Session Advertisement Protocol, listen to whether the first network interface receives a Session Description Protocol message sent by the network audio device, and obtain the connection request sent by the network audio device according to the Session Description Protocol message;

[0012] According to the wireless protocol, the wireless receiving host connected to the second network interface listens to whether it receives a response signal sent by the wireless audio device, and obtains the connection request sent by the wireless audio device based on the response signal. The response signal is sent by the wireless audio device based on the scan signal broadcast by the wireless receiving host.

[0013] Listen to the third network interface to see if it receives a service request from the control device according to the multicast domain name protocol, and obtain the connection request sent by the control device according to the service request.

[0014] Specifically, the first network interface, the second network interface, and the third network interface are monitored in parallel.

[0015] Through the above technical means, the network interfaces of various protocol devices are monitored based on the discovery protocols supported by various protocol devices to accurately listen for connection requests from each protocol device, ensuring that the discovery and connection processes of protocol devices can operate normally, and providing a technical foundation for the discovery and connection of multiple protocol devices.

[0016] Optionally, determining the communication connection method adapted to the corresponding protocol device based on the device attribute information includes:

[0017] Obtain the communication protocol type and device type of the protocol device from the device attribute information;

[0018] Based on the communication protocol type and device type of the protocol device, determine the communication connection method adapted to the protocol device.

[0019] By employing the aforementioned technical means, a communication connection method that is compatible with the protocol device is selected based on the communication protocol type and device type of the protocol device, so as to accurately establish a data transmission channel with the protocol device and ensure the accuracy and reliability of the connection.

[0020] Optionally, establishing a data transmission channel with the corresponding protocol device based on the communication connection method includes:

[0021] When the communication protocol type is Real-Time Transport Protocol and the device type is Network Audio Device, a Real-Time Transport Connection Response is sent to the Network Audio Device so that the Network Audio Device establishes a Real-Time Audio Stream Transmission Channel with the Audio System based on the Real-Time Transport Connection Response.

[0022] When the communication protocol type is a proprietary protocol and the device type is a wireless audio device, a wireless receiver sends a wireless connection response to the wireless audio device so that the wireless audio device establishes a wireless audio transmission channel with the audio system based on the wireless connection response.

[0023] When the communication protocol type is WebSocket and the device type is a control device, a WebSocket connection response is sent to the control device so that the control device establishes a bidirectional real-time data transmission channel with the audio system based on the WebSocket connection response.

[0024] Through the above technical means, data transmission channels adapted to the data types to be transmitted are established for network audio devices, wireless audio devices, and control devices using their respective supported communication protocols. This achieves automated and unified management of the connection process for various protocol devices, eliminating the need for staff to participate in configuration and improving the connection efficiency and management convenience of protocol devices.

[0025] Optionally, before listening for connection requests sent by various protocol devices through a preset discovery protocol type, the method further includes:

[0026] By using preset discovery protocol types, listen for announcement information sent by devices using various protocols;

[0027] Upon receiving the announcement information, the device attribute information of the corresponding protocol device is obtained based on the announcement information, and the corresponding protocol device is registered to the system device list based on the device attribute information.

[0028] By employing the aforementioned technical means, different discovery protocols are used to listen to the announcement information sent by different protocol devices, thereby registering the protocol devices based on the announcement information. This effectively unifies the automated discovery and registration process for various protocol devices, eliminating the need for staff to participate in configuration and improving the efficiency of protocol device discovery and management convenience.

[0029] The step of obtaining the device attribute information of the corresponding protocol device based on the announcement information includes:

[0030] The announcement information is parsed according to the discovery protocol type corresponding to the protocol device, and the field content of each device attribute field is extracted from the parsed announcement information.

[0031] The content of each of the device attribute fields is mapped to the field of the same device attribute in the unified data model to obtain standard device data;

[0032] The standard device data is encapsulated into a standard data format to obtain the device attribute information of the protocol device.

[0033] By using the above technical means, the device attributes of various protocol devices are described with unified fields, eliminating the field differences of the same device attribute between different protocols. The device attributes of each protocol device are converted into a standard data format, eliminating the data format differences between the device attribute information of different protocol devices. This allows the network audio host to register each protocol device in a unified manner, which is beneficial to improving the registration and connection efficiency of protocol devices.

[0034] Optionally, registering the corresponding protocol device to the system device list based on the device attribute information includes:

[0035] The device attribute information of the protocol device is stored as a device record in the system device list;

[0036] Assign a system internal identifier to the protocol device, and add the system internal identifier to the device record of the protocol device;

[0037] Update the index and / or data structure of the system device list.

[0038] Using the aforementioned technical methods, the device attribute information of the protocol devices is saved as device records in the system device list, thereby maintaining the device attribute information of the corresponding protocol devices through these records. A unique internal system identifier is assigned to each protocol device and associated with the device record, which is used to reference and manage the device attribute information of the corresponding protocol device within the system device list. After a new device record is added, the index and / or data structure of the system device list are updated accordingly to ensure the accuracy of the index and data structure, facilitating subsequent rapid retrieval of device attribute information within the system device list.

[0039] Optionally, after registering the corresponding protocol device to the system device list based on the device attribute information, the method further includes:

[0040] Obtain the IP address of the protocol device from its device attribute information;

[0041] A registration success message is generated based on the system internal identifier of the protocol device;

[0042] The protocol device sends a registration success message back to the protocol device by using the discovery protocol type and IP address, so that the protocol device can send a connection request based on the registration success message.

[0043] Through the above technical means, after the protocol device is successfully registered, a registration success message carrying the system's internal identifier of the protocol device is sent back based on the IP address of the protocol device. This prompts the protocol device to continue sending connection requests to the network audio host, realizing an automatic transition from the discovery to the connection process of the protocol device and reducing manual intervention.

[0044] Optionally, after establishing a data transmission channel with the corresponding protocol device based on the communication connection method, the method further includes:

[0045] Upon receiving a disconnect control command, the data transmission channel with the corresponding protocol device will be disconnected according to the disconnect control command.

[0046] By employing the aforementioned technical means, the data transmission channel with the corresponding protocol device is disconnected upon receiving a disconnection control command, thereby providing users with a protocol device disconnection function. This allows users to select the protocol device that maintains a connection with the network audio host according to their actual needs, achieving unified management of the disconnection and connection of various protocol devices and improving the flexibility of the audio system.

[0047] Optionally, after establishing a data transmission channel with the corresponding protocol device based on the communication connection method, the method further includes:

[0048] Based on a preset periodic detection, it is determined whether the data transmission channel with the protocol device remains connected;

[0049] If the data transmission channel is detected to be disconnected without receiving a disconnection control command from the protocol device, a new data transmission channel is established with the protocol device according to the communication protocol type and device type of the protocol device.

[0050] By employing the aforementioned technical means, in the absence of a disconnection control command related to the protocol device, the disconnection of the data transmission channel of the protocol device is identified as an abnormal interruption. This allows for the re-establishment of a connection with the protocol device based on its device type and communication protocol type, thereby achieving unified management of abnormal interruptions of various protocol devices, preventing abnormal interruptions from affecting continuous audio playback, and improving the reliability of the audio system.

[0051] Optionally, after storing the device attribute information of the protocol device as a device record in the system device list, the method further includes:

[0052] Add the connection status of the protocol device to the device record of the protocol device, and initialize the connection status to a disconnected state.

[0053] Accordingly, the method further includes:

[0054] After the data transmission channel with the protocol device is established, the connection status in the device record of the protocol device is updated to the connected status;

[0055] After the data transmission channel with the protocol device is disconnected, the connection status in the device record of the protocol device is updated to a disconnected status.

[0056] By using the above technical means, the connection status of the protocol devices is added to the device record of the protocol devices, and the connection status in the device record is updated in real time according to the connection and disconnection of the data transmission channel of the protocol devices, so as to realize the real-time monitoring of the connection status of the protocol devices, facilitate the unified management of the connection or disconnection of each protocol device, and improve the reliability of the audio system.

[0057] Optionally, the method further includes:

[0058] After the connection status of any device in the system device list is updated, status feedback information is generated based on the updated connection status.

[0059] The status feedback information is sent to the control device, front end, and / or preset control terminal to indicate the connection status.

[0060] Using the above technical means, after the connection status recorded by any device is updated, the updated connection status and device name in the device record are packaged into status feedback information. The status feedback information is used to notify the control device, front-end and / or preset control terminal that the connection status of the corresponding protocol device has been updated. This allows the control device, front-end and / or preset control terminal to update the connection status of the protocol device in the corresponding control interface in real time, ensuring that users can confirm the latest connection status of each protocol device in real time and realize the visual monitoring of the protocol devices.

[0061] Secondly, this application provides a protocol device connection device, including:

[0062] One or more processors; a memory storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the protocol device connection method as described in the first aspect.

[0063] Thirdly, this application provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the protocol device connection method as described in the first aspect.

[0064] In this application, different types of discovery protocols are pre-configured to listen for connection requests from devices using different protocols. Upon detecting a connection request from a protocol device, the system retrieves device attribute information for each protocol device from the system's device list based on the connection request. Based on the device attribute information, the system determines the appropriate communication connection method for the protocol device and establishes a compatible data transmission channel with the protocol device based on the communication connection method. This achieves unified management and automated operation of the discovery and connection process for different protocol devices. Through these technical means, a multi-protocol compatible audio system can be constructed. This system can automatically discover and connect to multiple protocol devices, achieving unified management of the discovery and connection process for various protocol devices. It eliminates the need for professionals to manually configure the discovery and connection processes for each protocol device independently, simplifying the deployment and operation of the audio system. This provides a user-friendly, highly reliable, highly compatible, and highly scalable audio system. Attached Figure Description

[0065] Figure 1 This is a schematic diagram of the structure of the audio system provided in the embodiments of this application;

[0066] Figure 2 This is a flowchart of a protocol device connection method provided in an embodiment of this application;

[0067] Figure 3 This is a schematic diagram of the device discovery proxy module listening protocol device provided in the embodiments of this application;

[0068] Figure 4 This is a flowchart of the standardization process for declaration information provided in an embodiment of this application;

[0069] Figure 5 This is a schematic diagram of the structure of the unified data model provided in the embodiments of this application;

[0070] Figure 6 This is a flowchart of the registration agreement device adopted in the embodiments of this application;

[0071] Figure 7 This is a schematic diagram illustrating the communication process between the network audio host and various protocol devices provided in the embodiments of this application;

[0072] Figure 8 This is a schematic diagram of the control interface of the control device provided in the embodiments of this application;

[0073] Figure 9 This is a schematic diagram of the structure of a protocol device connection device provided in an embodiment of this application. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. A process can be terminated when its operation is completed, but it may also have additional steps not included in the drawings. A process can correspond to a method, function, procedure, subroutine, subroutine, etc.

[0075] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0076] In common implementations, multi-functional halls integrating meetings, training sessions, lectures, and small performances often deploy traditional audio systems. These systems include wired microphones, wireless microphones, speakers, a main unit, and a control panel, resulting in complex cabling and difficult wiring and maintenance. Wired microphones and speakers are network audio devices, wireless microphones are wireless audio devices, and the control panel is a control device. These devices use different discovery and connection protocols, requiring manual configuration by professional audio technicians to connect them to the main unit. This leads to lengthy preparation times and low deployment efficiency. Adding microphones or speakers necessitates rewiring and reconfiguration, resulting in high upgrade costs and long cycles, and poor scalability. Newly purchased equipment may use different network audio protocols, making interoperability with existing analog or early digital equipment difficult, further complicating system integration. Therefore, traditional audio systems cannot uniformly and automatically discover and connect devices, resulting in poor deployment efficiency, reliability, and scalability.

[0077] To address the aforementioned issues, this embodiment provides a protocol device connection method that employs different discovery protocols to listen for connection requests sent by different protocol devices. Based on the connection request, a connection process compatible with the protocol device is selected, and a data transmission channel is established with the protocol device according to the connection process. This effectively unifies the automated discovery and connection process for various protocol devices, optimizing the deployment efficiency, reliability, and scalability of the audio system.

[0078] The protocol device connection method provided in this embodiment can be executed by a protocol device connection device, which can be implemented through software and / or hardware. This protocol device connection device can consist of two or more physical entities, or it can consist of a single physical entity. For example, the protocol device connection device can be an audio system, which includes system components such as a network audio host and a wireless receiver host. The network audio device, wireless audio device, and control device can be considered as sub-devices of the audio system, or as external devices of the audio system. Optionally, the protocol device connection device can also be a network audio host, which runs the protocol device connection method to establish connections with the network audio device, wireless audio device, and control device. The wireless receiver host is used to establish a wireless communication connection between the network audio host and the wireless audio device.

[0079] Furthermore, network audio devices are audio devices that use network audio protocol standards for audio transmission, such as AES67 (an open network digital audio standard that enables low-latency, high-performance professional audio transmission based on IP network architecture), such as wired microphones and PoE (Power over Ethernet) network speakers. Wireless audio devices are audio devices that use wireless audio technology for audio transmission, such as wireless microphones. Control devices are terminal devices provided to users for managing the audio system, such as control panels. Control devices can display a user interface to provide control functions such as device management, volume adjustment, and scene switching through the user interface.

[0080] When deploying an audio system in a multi-functional hall, if the hall is pre-equipped with wired microphones, network speakers, wireless microphones, wireless receivers, a control panel, and a network switch, the cabling for the audio system can be completed simply by connecting the cables of the wired microphones, network speakers, wireless receivers, control panel, and the network audio host in the audio system to the network switch. After staff power on these devices, they can automatically enter the discovery and connection workflow. The network audio host can automatically discover and connect to the wired microphones, network speakers, wireless microphones, and control panel through the wireless receiver and network switch, achieving unified management of the discovery and connection process for devices using multiple protocols.

[0081] Of course, the network audio host can integrate a network switch. If a network switch is not provided in the multi-functional hall, the internally integrated network switch can be used to connect wired microphones, network speakers, wireless receivers, and the audio system.

[0082] For example, Figure 1 This is a schematic diagram of the structure of the audio system provided in an embodiment of this application. Figure 1 As shown, the network speakers, wired microphone, control panel, and wireless receiver are wired to the network switch, the network audio host is wired to the network switch, and the wireless receiver is wirelessly connected to the wireless microphone. After the network audio host successfully establishes a data transmission channel with the network speakers, wired microphone, wireless microphone, and control panel, the network audio host transmits audio data to the network speakers and wired microphone for playback via wired communication, transmits audio data to the wireless microphone for playback via wireless communication, and receives control commands transmitted from the control panel via wired communication. The establishment of the data transmission channel requires a device discovery and connection process. This embodiment aims to achieve unified management of the discovery and connection process of various protocol devices through a protocol device connection method, eliminating the need for professionals to manually configure the discovery and connection process of each protocol device independently, simplifying the deployment and operation of the audio system, and providing a user-friendly, highly reliable, highly compatible, and highly scalable audio system.

[0083] The protocol device connection device has at least one type of operating system installed, including but not limited to Android, Linux, and Windows. The protocol device connection device can install at least one application based on the operating system; the application can be a built-in application of the operating system or an application downloaded from a third-party device or server. In this embodiment, the protocol device connection device has at least one application capable of executing the protocol device connection method.

[0084] For ease of understanding, this embodiment uses a network audio host as the main body for implementing the protocol device connection method as an example for description.

[0085] Figure 2 This is a flowchart illustrating a protocol device connection method provided in an embodiment of this application. For example... Figure 2 As shown, the steps of this protocol device connection method include:

[0086] S110. Listen for connection requests sent by various protocol devices, including network audio devices, wireless audio devices, and control devices, through a preset discovery protocol type.

[0087] The discovery protocol is used to discover various protocol devices. In this embodiment, based on the discovery protocol types adapted to the various protocol devices to be connected in the audio system, the network audio host is configured with the discovery protocol types for each protocol device. This allows the host to listen for connection requests sent by various protocol devices during the discovery process. A connection request can be understood as a message from a protocol device requesting to establish a data transmission channel with the network audio host.

[0088] For example, network audio devices and control devices are directly connected to the signal interfaces of the network switch, while wireless audio devices are indirectly connected to the signal interfaces of the network switch through a wireless receiver. Connection requests sent by the network audio devices, control devices, and wireless audio devices are transmitted to the network audio host through the network switch. The network audio host can receive connection requests from the network audio devices, control devices, and wireless audio devices by listening to the signal interfaces of the network switch. Each signal interface of the network switch connects to one protocol device. Operators pre-configure the network audio host with information on which interfaces of the network switch are connected to network audio devices, which to control devices, and which to wireless receivers to ensure that connection requests are correctly listened to. Therefore, after startup or initialization, the network audio host loads configuration information, which specifies the signal interfaces used to listen to network audio devices, control devices, and wireless receivers.

[0089] Furthermore, the configuration information also includes the discovery protocol types supported by network audio devices, control devices, and wireless audio devices. After loading the configuration information, the network audio host can listen for connection requests sent by protocol devices on the signal interface of the corresponding network switch based on the discovery protocols supported by various protocol devices.

[0090] Optionally, network audio devices support discovery protocols including the Session Advertisement (SAP) protocol, which can be used to listen for connection requests sent by network audio devices on the corresponding signal interface. Wireless audio devices support discovery protocols including wireless protocols, such as proprietary protocols or RF pairing protocols (2.4GHz band protocols, U-band protocols, Wi-Fi protocols, and Bluetooth protocols, etc.), which can be used to listen for connection requests sent by wireless audio devices on the corresponding signal interface of the wireless receiver. Control devices support discovery protocols including the Multicast Domain Name Protocol (mDNS) protocol, which can be used to listen for connection requests sent by control devices on the corresponding signal interface of the control device.

[0091] The network audio host can listen for connection requests from multiple protocol devices in parallel. The specific implementation process is as follows: It listens for Session Description Protocol (SMAP) messages sent by the network audio device on the first network interface to obtain the connection request from the network audio device; it listens for response signals sent by the wireless audio device on the second network interface to obtain the connection request from the wireless audio device based on the response signals, which are sent by the wireless audio device based on the scan signals broadcast by the wireless audio device; it listens for service requests sent by the control device on the third network interface to obtain the connection request from the control device based on the service requests. The first, second, and third network interfaces are listened to in parallel. The first network interface is the signal interface of the network switch used to connect the network audio device; the second network interface is the signal interface of the network switch used to connect the wireless audio device; and the third network interface is the signal interface of the network switch used to connect the control device.

[0092] For example, a network audio device includes a device discovery proxy module. After the network audio device is powered on, the device discovery proxy module enters an initialization process. During initialization, it loads configuration information to obtain the signal interface to be monitored, the discovery protocol types supported by each protocol device, and other system parameters. After the device discovery proxy module completes initialization, it monitors the protocol devices in the network based on the discovery protocols supported by the protocol devices at the corresponding signal interface. Figure 3 This is a schematic diagram of the device discovery proxy module monitoring protocol device provided in the embodiments of this application. Figure 3As shown, the network speaker, wired microphone, wireless receiver, and control panel are connected to signal interfaces A, B, C, and D of the network switch, respectively. After loading configuration information, the device discovery agent module confirms that signal interfaces A and B are connected to the network audio device, signal interface C is connected to the wireless audio device, and signal interface D is connected to the control device. Therefore, it monitors signal interfaces A and B based on the SAP protocol, signal interface C based on the wireless protocol, and signal interface D based on the mDNS protocol. The network speaker and wired microphone generate Session Description Protocol (SDP) messages based on the internal system identifier assigned to them when registering with the network audio host, and send these SDP messages to signal interfaces A and B based on the SAP protocol. During the process of monitoring signal interfaces A and B based on the SAP protocol, the network audio host receives the SDP messages sent by the network speaker and wired microphone, and confirms that the SDP messages are connection requests from the network speaker and wired microphone based on the content information carried in the SDP messages. The wireless receiver broadcasts a scanning signal. After continuously scanning the broadcast signal, the wireless microphone generates a response signal based on its internal system identifier assigned during registration with the network audio host. Both the response signal and the scanning signal are radio frequency (RF) signals. The wireless microphone sends the response signal to the wireless receiver via a wireless protocol, and the wireless receiver transmits the received response signal to signal interface C. While the network audio host is monitoring signal interface C via the wireless protocol, it receives the response signal from the wireless receiver and confirms that the response is a connection request from the wireless microphone based on the information carried in the response signal. After the control panel is powered on, it generates a service request (mDNS service request) based on its internal system identifier assigned during registration with the network audio host and sends the service request to signal interface D via the mDNS protocol. While the network audio host is monitoring signal interface D via the mDNS protocol, it receives the service request from the control panel and confirms that the service request is a connection request from the control panel.

[0093] This embodiment can listen to the network interfaces of various protocol devices through the discovery protocols supported by various protocol devices, so as to accurately listen to the connection requests from various protocol devices, ensure that the discovery and connection processes of protocol devices can run normally, and provide a technical foundation for the discovery and connection of multiple protocol devices.

[0094] It should be noted that connection requests can be automatically generated and sent by the protocol device after receiving a registration success message from the network audio host, or they can be generated and sent by the user through a control panel, the network audio host's front-end user interface, or other control terminals. The network audio host will continuously monitor various signal interfaces of the network switch to receive connection requests sent by the protocol devices.

[0095] S120. Upon receiving a connection request, query the device attribute information of the corresponding protocol device in the system device list based on the connection request. The system device list stores the device attribute information of the protocol devices that have been discovered and registered in advance.

[0096] Device attribute information can be understood as data containing various device attributes of the protocol device. Device attributes can include device type, device name, communication protocol type, network address, etc. For example, when the network audio host detects a session description protocol message, response signal, and / or service request that is a connection request, it parses the connection request according to the corresponding discovery protocol and obtains the system internal identifier of the protocol device from the parsed connection request. Based on the system internal identifier of the protocol device, it queries the associated device record in the system device list and obtains the device attribute information of the protocol device from the device record. This allows for subsequent selection of a communication connection method suitable for the protocol device to establish a data transmission channel based on the device attribute information.

[0097] It should be noted that the system device list can be a historical device list generated from previous registrations of protocol devices, or a real-time device list generated each time a protocol device is registered. If it's a historical device list, then each connection to a protocol device only requires retrieving the device attribute information from the historical device list to establish a data transmission channel with the corresponding protocol device. If it's a real-time device list, then before connecting to a protocol device, the device attribute information of that protocol device must be registered in the real-time device list, and only then will a data transmission channel be established with that protocol device.

[0098] Optionally, the network audio host includes a connection manager module, which is responsible for executing the connection process of the protocol device. For example, after receiving a connection request, the connection manager module parses the connection request to obtain the system internal identifier of the protocol device. Using the system internal identifier, it queries the system device list for the device record row or data element containing the system internal identifier, and retrieves the content of other columns or other element attributes within the device record row or data element, thereby obtaining the device attribute information of the protocol device. Then, the connection manager module establishes a data transmission channel with the protocol device based on the device attribute information.

[0099] S130. Determine the communication connection method adapted to the corresponding protocol device based on the device attribute information, establish a data transmission channel with the corresponding protocol device based on the communication connection method, and perform data transmission with the corresponding protocol device based on the data transmission channel.

[0100] For example, different protocol devices support different communication connection methods. Therefore, the communication connection method adapted to the protocol device to be connected can be determined according to the device attribute information, and a data transmission channel can be established with the protocol device based on the communication connection method.

[0101] Generally, the device type and communication protocol type of a protocol device determine its communication connection method. These can be obtained from the device attribute information. Based on the communication protocol type and device type, the appropriate communication connection method is determined. For example, the communication protocol type and device type of the protocol device to be connected are obtained from the fields of communication protocol type and device type recorded in the device record. The communication protocol type determines the communication protocols supported by the protocol device, which in turn determines the data type transmitted by the protocol device based on the device type. Finally, the appropriate communication connection method is determined based on the communication protocol and the transmitted data type. This embodiment selects the appropriate communication connection method for the protocol device based on its communication protocol type and device type to accurately establish a data transmission channel with the protocol device, ensuring the accuracy and reliability of the connection.

[0102] For example, when the communication protocol type is Real-Time Transport Protocol (RTP) and the device type is a network audio device, a RTP connection response is sent to the network audio device to establish a real-time audio stream transmission channel with the audio system based on the RTP connection response. The RTP connection response is a message sent by the network audio host in response to the connection request from the network audio device. After determining that the protocol device is a network audio device and supports RTP, the connection manager module generates a RTP connection response based on the audio stream parameters, obtains the IP address of the protocol device from its device record, and sends the RTP connection response to the protocol device based on the IP address. Upon receiving the RTP connection response, the protocol device establishes a real-time audio stream transmission channel with the network audio host and configures audio decoding parameters according to the audio stream parameters. The real-time audio stream transmission channel is an audio stream transmission channel implemented based on RTP technology. When the network audio host sends audio data to the network audio device through the real-time audio stream transmission channel, the network audio data is decoded according to the audio decoding parameters to obtain an audio signal, which is then played.

[0103] When the communication protocol type is a proprietary protocol and the device type is a wireless audio device, a wireless receiver sends a wireless connection response to the wireless audio device, enabling the wireless audio device to establish a wireless audio transmission channel with the audio system based on the wireless connection response. The wireless connection response is a message sent by the network audio host in response to the connection request from the wireless audio device. After determining that the protocol device is a wireless audio device and supports the proprietary protocol, the connection manager module generates a wireless connection response based on the audio stream parameters, obtains the IP address of the protocol device from its device record, and sends the wireless connection response to the protocol device via the wireless receiver based on the IP address. Upon receiving the wireless connection response, the protocol device establishes a wireless audio transmission channel with the network audio host and configures the audio decoding parameters according to the audio stream parameters in the wireless connection response. The wireless audio transmission channel is an audio transmission channel implemented based on wireless communication technology. When the network audio host sends audio data to the wireless audio device through the wireless audio transmission channel, the wireless audio data is decoded according to the audio decoding parameters to obtain the audio signal, which is then played.

[0104] When the communication protocol type is WebSocket and the device type is a control device, a WebSocket connection response is sent to the control device to establish a bidirectional real-time data transmission channel between the control device and the audio system. The WebSocket connection response is a message sent by the network audio host in response to the connection request from the control device. After determining that the protocol device is a control device and supports the WebSocket protocol, the connection manager module generates a WebSocket connection response, obtains the control device's IP address from the protocol device's device record, and sends the WebSocket connection response to the protocol device based on the IP address. Upon receiving the WebSocket connection response, the protocol device establishes a bidirectional real-time data transmission channel with the network audio host. This bidirectional real-time data transmission channel is a bidirectional communication connection implemented based on the HTTP / WebSocket protocol. The control device can send control commands to the network audio host through this bidirectional real-time data transmission channel, and the network audio host can send the protocol device's status information to the control device through the same channel.

[0105] This embodiment establishes data transmission channels adapted to the data types to be transmitted using their respective supported communication protocols for network audio devices, wireless audio devices, and control devices. This achieves automated and unified management of the connection process for various protocol devices, eliminating the need for staff to participate in configuration and improving the connection efficiency and management convenience of protocol devices.

[0106] It should be noted that the connection process involves multiple message exchanges and parameter negotiations between the network audio host and the protocol device until a successful connection is established or the connection fails. The network audio host can send connection success or failure status information to the control device, which then notifies the user of the connection status of each protocol device.

[0107] In one embodiment, before sending a connection request, the protocol device sends an announcement message to the network audio host, enabling the network audio host to register the protocol device based on the announcement message, thereby establishing a data transmission channel with the registered protocol device. For example, the network audio host listens for announcement messages sent by various protocol devices using a preset discovery protocol type; upon detecting an announcement message, it obtains the device attribute information of the corresponding protocol device based on the announcement message, and registers the corresponding protocol device to the system device list based on the device attribute information.

[0108] The announcement message can be understood as a message used by a protocol device to inform a network audio host of its existence and connectivity. It should be noted that the same protocol device uses the same mechanism to send announcement messages and connection requests; only the content of the information carried in the announcement message and connection request differs. The announcement message carries the corresponding protocol device's device type, device name, network address, communication protocol type, and device function, while the connection request carries the system's internal identifier assigned to the corresponding protocol device after registration.

[0109] For example, after staff connect the cables of a wired microphone, network speakers, wireless receiver, control panel, and network audio host to the network switch, they power on all these devices. The wired microphone, network speakers, wireless receiver, network audio host, network switch, and wireless microphone then send announcement messages. The network audio host listens for these announcement messages using pre-configured discovery protocols. The network audio host remains in listening mode until it receives a listening control command from the control panel or is powered off. Because the network audio host is continuously listening, if a new wired microphone, network speaker, or wireless microphone is subsequently powered on, the network audio host may simultaneously detect connection requests from registered devices and announcement messages from newly powered-on devices.

[0110] refer to Figure 3The network audio system, wired microphone, wireless receiver, and control panel are connected to signal interfaces A, B, C, and D of the network switch, respectively. After loading configuration information, the device discovery agent module confirms that signal interfaces A and B are connected to the network audio device, signal interface C is connected to the wireless audio device, and signal interface D is connected to the control device. It then monitors signal interfaces A and B based on the SAP protocol, signal interface C based on the wireless protocol, and signal interface D based on the mDNS protocol. Upon power-on, the network audio system and wired microphone generate Session Description Protocol (SDP) messages based on their device type, device name, communication protocol type, and network address, and send these messages to signal interfaces A and B based on the SAP protocol. While the network audio host is monitoring signal interfaces A and B using the SAP protocol, it receives the SDP messages from the network audio system and wired microphone and confirms that the messages are announcements from the network audio system and wired microphone based on the information carried within them. After the wireless receiver and wireless microphone are powered on, the wireless receiver broadcasts a scan signal. The wireless microphone, upon continuously scanning the broadcast scan signal, generates a response signal based on its device type, device name, communication protocol type, and network address. Both the response signal and the scan signal are radio frequency (RF) signals. The wireless microphone sends the response signal to the wireless receiver based on the wireless protocol, and the wireless receiver transmits the received response signal to signal interface C. While the network audio host is monitoring signal interface C based on the wireless protocol, it receives the response signal from the wireless receiver and confirms that the response information is the announcement information from the wireless microphone based on the content information carried in the response signal. After the control panel is powered on, it generates a service request (mDNS service request) based on its device type, device name, communication protocol type, and network address, and sends the service request to signal interface D based on the mDNS protocol. While the network audio host is monitoring signal interface D based on the mDNS protocol, it receives the service request sent by the control panel and confirms that the service request is the announcement information from the control panel.

[0111] After receiving the announcement information from the protocol devices, the network audio host can register the protocol devices based on the announcement information. Successfully registered protocol devices can then send connection requests to the network audio host. The network audio host continuously uses signal interfaces A, B, C, and D to receive connection requests from network speakers, wired microphones, wireless microphones, and control panels.

[0112] When the protocol device can generate announcement information and connection request messages, the protocol device will add the corresponding message type to the message to indicate that the message is an announcement information or a connection request. The network audio host can select the corresponding processing procedure to process the announcement information or connection request according to the message type.

[0113] After receiving a Session Description Protocol (SMAP) message from a network audio device, the network audio host determines whether the message is an announcement or a connection request based on the message type carried in the SMAP message. If the SMAP message is an announcement, the host parses the announcement according to the Session Advertisement Protocol (SAP) and extracts the device type, device name, communication protocol type, network address, and device function as device attribute information. Based on this device attribute information, the host registers the network audio device in the system device list. Similarly, after receiving a response signal from a wireless audio device, the network audio host determines whether the response signal is an announcement or a connection request based on the message type carried in the response signal. If the response signal is an announcement, the host parses the announcement according to the wireless protocol and extracts the device type, device name, communication protocol type, network address, and device function as device attribute information. Based on this device attribute information, the host registers the wireless audio device in the system device list. When the network audio host detects an mDNS service request sent by the control device, it sends an mDNS service response to the control panel based on the mDNS service request. After receiving the mDNS service response, the control panel sends a declaration information containing the device attributes of the control panel. The declaration information is resolved according to the multicast domain name protocol. The device type, device name, communication protocol type, network address, device function, etc. are obtained from the resolved declaration information as device attribute information. Based on the device attribute information, the control device is registered in the system device list.

[0114] Optionally, the announcement information received by the network audio host is typically in its raw, protocol-specific data format. For example, the announcement information for network audio devices is in SDP description format, the announcement information for wireless audio devices is in proprietary protocol data format, and the announcement information for control devices is in TXT record format. To facilitate unified management of devices using multiple protocols by the network audio host, information such as device type, device name, communication protocol type, network address, and device function can be standardized to obtain device attribute information in a standard data format. For example, Figure 4 This is a flowchart illustrating the standardization process for declaration information provided in an embodiment of this application. For example... Figure 4 As shown, the steps for standardizing the declaration information specifically include S1401-S1403:

[0115] S1401. Parse the announcement information according to the discovery protocol type corresponding to the protocol device, and extract the field content of each device attribute field from the parsed announcement information.

[0116] For example, the announcement information of network audio devices is parsed according to the Session Advertisement Protocol (SAP), the announcement information of wireless audio devices is parsed according to the wireless protocol, and the announcement information of control devices is parsed according to the mDNS protocol. The content of device attribute fields such as device type, device name, network address, communication protocol type, and device function is extracted from the parsed announcement information.

[0117] S1402. Map the field content of each device attribute field to the field of the same device attribute in the unified data model to obtain standard device data.

[0118] For example, the content of the device name attribute field mentioned in the announcement information is mapped to the device name attribute field in the unified data model. Assuming the device name attribute field in the unified data model is "DeviceName", then the device name of each protocol device will be mapped to "DeviceName", and the content of other device attribute fields will be mapped similarly. Finally, information such as the device type, device name, network address, communication protocol type, and device function of each protocol device will be generated in the format of the unified data model, and data in this format will be used as the standard device data for the protocol devices.

[0119] For example, Figure 5 This is a schematic diagram of the structure of the unified data model provided in the embodiments of this application. For example... Figure 5 As shown, the device attribute fields of the unified data model include "DeviceName", "DeviceType", "IPaddress", "MACaddress", "Protocoltype", and "Devicefunctions", which belong to the fields of device name, device type, IP address, MAC address, communication protocol type, and device function, respectively. The device name, device type, IP address, MAC address, communication protocol type, and device function of the protocol device extracted from the announcement information are mapped to the fields of "DeviceName", "DeviceType", "IPaddress", "MACaddress", "Protocoltype", and "Devicefunctions" in the unified data model to obtain the standard device data of the protocol device.

[0120] S1403. Encapsulate the standard equipment data into a standard data format to obtain the equipment attribute information of the protocol equipment.

[0121] The standard data format is a predefined data format used by the network audio host to organize and encapsulate the device attributes of protocol devices. It can be JSON or other structured data formats. In essence, by encapsulating the standard device data of protocol devices into a standard data format, the device attributes of each protocol device are represented by a unified data format. The network audio host can process the device attribute information of protocol devices based on a unified process, thereby completing the unified registration of various protocol devices. This eliminates the data format differences between the device attribute information of different protocol devices, facilitating subsequent unified connection and management of various protocol devices.

[0122] This embodiment describes the device attributes of various protocol devices using a unified field, eliminating the field differences of the same device attribute between different protocols. It converts the device attributes of each protocol device into a standard data format, eliminating the data format differences between the device attribute information of different protocol devices. This allows the network audio host to uniformly register various protocol devices, which is beneficial to improving the registration and connection efficiency of protocol devices.

[0123] After obtaining the device attribute information of the protocol device, the protocol device is registered in the system device list based on this information. This allows for the establishment of a data transmission channel with the protocol device based on its device attribute information within the system device list. The system device list is a dynamic database or data structure maintained internally by the network audio host, used to store the device attribute information of discovered protocol devices. Optionally, Figure 6 This is a flowchart of the registration agreement device adopted in the embodiments of this application. For example... Figure 6 As shown, the specific steps for registering the device include S1404-S1406:

[0124] S1404. Store the device attribute information of the protocol device as a device record in the system device list.

[0125] For example, when the system device list is a relational database, a device record row for the protocol device can be created in the relational database, and the various fields of the device attribute information can be inserted into the corresponding columns of the device record row. When the system device category is a data structure, the device attribute information of the protocol device is added as a new element to the data structure, and this data element is the device record of the protocol device.

[0126] S1405. Assign the system internal identifier of the protocol device and add the system internal identifier to the device record of the protocol device.

[0127] For example, when the system device list is a relational database, the auto-incrementing primary key function of the relational database is used to assign a unique incrementing integer as the primary key to the device record row when inserting a new device record row. This primary key can serve as the system's internal identifier for the protocol device.

[0128] Optionally, since the MAC address of the protocol device is uniquely representative in the entire network, the MAC address of the protocol device can be obtained from the device attribute information and used as the internal system identifier of the protocol device.

[0129] After assigning the system internal identifier to the protocol device, the system internal identifier is added to the relevant column of the device record row, or added to the relevant attribute of the data element, thereby establishing the association between the system internal identifier and the device attribute information.

[0130] S1406. Update the index and / or data structure of the system device list.

[0131] For example, if an index (such as a B-tree index or hash index) is used to query device records in the system device list, then after adding a new device record, the index of the system device list needs to be updated to ensure that the device record can be correctly queried through the index. When the system device list is implemented using a specific data structure, adding a new device record may affect the balance of the data structure or other specific aspects. Therefore, the data structure of the system device list needs to be adjusted to maintain the structure and characteristics of the system device list.

[0132] In this embodiment, during the registration of protocol devices, the device attribute information of the protocol devices is saved as device records in the system device list, so as to maintain the device attribute information of the corresponding protocol devices through the device records. A unique internal system identifier is assigned to each protocol device and associated with the device record, which is used to reference and manage the device attribute information of the corresponding protocol device within the system device list. After a new device record is added, the index and / or data structure of the system device list are updated accordingly to ensure the accuracy of the index and data structure of the system device list, facilitating subsequent quick retrieval of device attribute information in the system device list.

[0133] It should be noted that after a network audio host successfully registers a protocol device, the protocol device's internal system identifier is used by the network audio host to identify the protocol device. To ensure proper handling of connection requests from registered devices, the protocol device's internal system identifier can be fed back to the corresponding protocol device after registration, allowing the protocol device to use this identifier to communicate with the network audio host.

[0134] For example, the IP address of the protocol device can be obtained from the device attribute information of the protocol device; a registration success message can be generated based on the system internal identifier of the protocol device; and the registration success message can be sent back to the protocol device using the discovery protocol type and IP address of the protocol device, so that the protocol device can send a connection request based on the registration success message. The registration success message is used to notify the protocol device that it has successfully registered with the network audio host. After registering the device attribute information of the protocol device to the system device list, the IP address is obtained from the "IPaddress" field of the protocol device's device record. The IP address is used to instruct the network audio device to accurately send the registration success message back to the corresponding protocol device. The system internal identifier is obtained from the "DeviceID" field of the protocol device's device record, and the system internal identifier is packaged to generate the registration success message. Then, the registration success message is sent to the protocol device through the discovery protocol supported by the protocol device. After receiving the registration success message, the protocol device parses the registration success message based on the discovery protocol to obtain the system internal identifier. After obtaining the system's internal identifier, the protocol device can generate a connection request based on it. The network audio host, using the connection request carrying the system's internal identifier, can identify which protocol device is requesting a connection. It then queries the system's device list for the corresponding device's record and establishes a data transmission channel with that device based on its various attributes. This embodiment, after successful registration of the protocol device, sends a registration success message carrying the device's internal identifier back to the network audio host based on the device's IP address. This allows the protocol device to continue sending connection requests to the network audio host, achieving an automatic transition from discovery to connection and reducing manual intervention.

[0135] In one embodiment, if multiple audio systems are installed in close proximity, for example, two audio systems are installed in adjacent multi-function halls, when the wireless receiving host broadcasts a scanning signal, the wireless microphones in the adjacent multi-function halls will receive the scanning signal and send a response signal to the wireless receiving host. At this time, the network audio host will listen for the response signals from the wireless microphones of other audio systems. To ensure that the network audio host can accurately connect to the wireless microphone of the corresponding audio system, the network audio host needs to identify whether the audio system corresponding to the wireless microphone is its own. Only when the audio system of the network audio host and the wireless microphone is consistent will the wireless microphone be registered, thus avoiding wasting registration resources and mistakenly connecting to the wireless microphone of other audio systems.

[0136] Optionally, a whitelist of connectable protocol devices can be pre-defined within the network audio host. When an announcement message from a protocol device is detected, the device name can be retrieved from the announcement message and matched against the whitelist. If a match is found, device attribute information for the protocol device is generated based on the announcement message, and the protocol device is registered according to this information. In other words, the network audio host can add wireless microphones from the corresponding multi-function hall to its whitelist. When the network audio host receives a response signal from a wireless microphone in an adjacent multi-function hall, it will check the device name in the response signal to confirm that the microphone is not on the whitelist. This indicates that the wireless microphone's audio system is not compatible with the network audio host's, and therefore, the microphone will not be registered.

[0137] Alternatively, the distance between the network audio host and the wireless microphone can be determined based on the signal strength of the response signal from the wireless microphone. If the distance exceeds a preset distance, it can be confirmed that the wireless microphone and the network audio data are not deployed in the same area, thus determining that the audio systems of the network audio host and the wireless microphone are not consistent. If the distance does not exceed the preset distance, it can be confirmed that the wireless microphone and the network audio data are deployed in the same area, thus determining that the audio systems of the network audio host and the wireless microphone are consistent.

[0138] In addition, the location information of the wireless microphone is used to determine whether the wireless microphone is deployed within the deployment area of ​​the network audio host. If so, it is determined that the audio systems of the network audio host and the wireless microphone are the same; otherwise, it is determined that the audio systems of the network audio host and the wireless microphone are not the same.

[0139] The location information of the wireless microphone can be determined through its positioning system. After determining its own location, the wireless microphone sends the location information, along with its device name and other attributes, as a response signal to the wireless receiver. The network audio host can then parse the wireless microphone's location information from the response signal. The deployment area is the multi-functional hall where the network audio host is deployed, which is also the coverage area of ​​the audio system corresponding to the network audio host.

[0140] If other devices with wireless scanning capabilities are set up around the network audio host, such as the control screen in the multi-functional hall where the network audio host is located, as well as the network audio hosts and control screens in adjacent multi-functional halls, these devices can be requested to broadcast scanning signals to obtain response signals from the wireless microphone. The distance between the wireless microphone and each device is determined based on the signal strength of the response signal, and the location information of the wireless microphone is determined based on the triangulation algorithm and this distance.

[0141] To provide a more intuitive understanding of the process by which network audio hosts discover and connect to devices using various protocols, this embodiment uses... Figure 7The following diagram illustrates the communication process between a network audio host and various protocol devices. Figure 7 As shown, during the device discovery phase, the control device sends an mDNS service request to the network audio host. The network audio host responds to the mDNS service request with an mDNS service response. The control device then sends an announcement message carrying device attributes to the network audio host based on the mDNS service response. The network audio host parses the device attributes in the announcement message, converts them into a standard data format, registers them in the system device list, and sends a successful registration message back to the control device. Next, the network audio device sends an SDP message to the network audio host. The network audio host parses the device attributes from the SDP message, converts them into a standard data format, registers them in the system device list, and sends a successful registration message back to the network audio device. Finally, the wireless receiver broadcasts a scan signal. When the wireless audio device receives the scan signal, it sends a response signal to the wireless receiver. The wireless receiver sends the response signal to the network audio host. The network audio host parses the device attributes carried in the response signal, converts them into a standard data format, registers them in the system device list, and sends a successful registration message back to the wireless audio device. After this, the device connection phase begins. The control device sends an mDNS service request to the network audio host to establish a connection, and the network audio host responds to the request to establish a WebSocket connection with the control device. The network audio device sends an SDP message to the network audio host to request a connection, and the network audio host responds to the message to establish an RTP connection with the network audio device. The wireless audio device sends a response signal to the network audio host through the wireless receiver to request a connection, and the network audio host responds to the request to establish a wireless connection with the wireless audio device.

[0142] Optionally, to monitor the connection status of each protocol device, the network audio host can add the connection status of the protocol device to the device record after registering the device record for the protocol device, and initialize the connection status to a disconnected state. For example, after creating a device record row or data element for the protocol device in the system device list, the device attribute information of the protocol device can be written into the device record row or data element, and the disconnected state can be added to the corresponding column of the device record row or the relevant attribute of the data element.

[0143] Subsequently, the connection status in the device record is updated according to whether the connection with the protocol device has been established or disconnected. For example, after a data transmission channel with the protocol device is established, the connection status in the protocol device's device record is updated to "connected"; after the data transmission channel with the protocol device is disconnected, the connection status in the protocol device's device record is updated to "disconnected". For instance, after the network audio host initially responds to a connection request sent by the protocol device and establishes a data transmission channel with the protocol device, confirming a successful connection, it queries the corresponding device record in the system device list based on the protocol device's internal system identifier and updates the connection status attribute in the device record to "connected". Conversely, after the network audio host disconnects the data transmission channel with the protocol device due to network issues or in response to a disconnection request, confirming that the connection with the protocol device has not been maintained, it queries the corresponding device record in the system device list based on the protocol device's internal system identifier and updates the connection status attribute in the device record to "disconnected".

[0144] This embodiment adds the connection status of the protocol devices to the device record of the protocol devices, and updates the connection status in the device record in real time according to the connection and disconnection of the data transmission channel of the protocol devices, so as to realize real-time monitoring of the connection status of the protocol devices, facilitate unified management of the connection or disconnection of each protocol device, and improve the reliability of the audio system.

[0145] Furthermore, the network audio host can synchronize the connection status of each protocol device with the user, allowing the user to confirm the connection status of each protocol device. For example, after the connection status of any device in the system device list is updated, status feedback information is generated based on the updated connection status; this status feedback information is sent to the control device, the front end, and / or the preset control terminal to indicate the connection status. The status feedback information is a message carrying the connection status of each registered device. The front end is the front-end platform provided by the network audio host, and the preset control terminal is a terminal device with the audio system management APP provided by the network audio host installed. When the preset control terminal runs the audio system management APP, it establishes a communication connection with the network audio host.

[0146] Whenever the network audio host updates the connection status recorded by a device—for example, during connection initialization, when the connection status is changed to "connected" upon successful connection, or when the connection status is changed to "disconnected" upon disconnection—it associates the connection status recorded by all devices in the system device list with the device name to generate status feedback information. The network audio host transmits this status feedback information to the control device via a bidirectional real-time data transmission channel. Upon receiving the status feedback information, the control device parses the device name and connection status of each protocol device from the feedback information and displays the connection status of each protocol device on the control interface based on the device name and connection status. Figure 8 This is a schematic diagram of the control interface of the control device provided in an embodiment of this application. For example... Figure 8 As shown, the control device parses the status feedback information and finds that the connection status of network audio, wired microphone A, wired microphone B, wireless microphone C, wireless microphone D and control screen are all connected. The control interface 10 displays network audio, wired microphone A, wired microphone B, wireless microphone C, wireless microphone D and control screen and their corresponding connected status side by side.

[0147] The process by which the network audio host sends status feedback information to the front end and / or preset control terminal is similar to the process of sending it to the control device, except that the transmission link for the status feedback information is different. The process by which the front end and / or preset control terminal receives and processes the status feedback information is similar to that of the control device described above, and will not be repeated here. In addition to generating status feedback information from the connection status and device name records of all devices in the system device list, the network audio host can also generate status feedback information only from the connection status and device name records of devices with updated connection status, thereby reducing the amount of data in the status feedback information and improving the efficiency of status feedback.

[0148] In this embodiment, after the connection status recorded by any device is updated, the updated connection status and device name in the device record are packaged into status feedback information. This status feedback information is used to notify the control device, front-end, and / or preset control terminal that the connection status of the corresponding protocol device has been updated. This allows the control device, front-end, and / or preset control terminal to update the connection status of the protocol devices in the corresponding control interface in real time, ensuring that users can confirm the latest connection status of each protocol device in real time and achieve visual monitoring of the protocol devices. Moreover, users can observe whether the working status of the protocol devices is abnormal through the connection status. For example, if a wireless microphone that should be connected is not connected, it may be that the wireless microphone is faulty. Users can perform fault maintenance on the wireless microphone in a timely manner, simplifying the user's daily maintenance work.

[0149] refer to Figure 8 The control interface 10 also includes a connection / disconnection control 11 to the right of each protocol device's connection status. When the slider 12 in the connection / disconnection control 11 remains on the left, the corresponding protocol device remains in a connected state; when the slider 12 remains on the right, the corresponding protocol device remains in a disconnected state; when the slider 12 moves from the left to the right, the network audio host disconnects the data transmission channel with the corresponding protocol device; when the slider 12 moves from the right to the left, the network audio host establishes a data transmission channel with the corresponding protocol device. Users can control the connection and disconnection between the protocol devices and the network audio host using the connection / disconnection control 11.

[0150] Optionally, when the control device detects that the user has moved the connection / disconnection control 11 of the wired microphone A from the left to the right, it generates a disconnection control command based on the internal system identifier of the wired microphone A and sends the disconnection control command to the network audio host through the bidirectional real-time data transmission channel. The disconnection control command is used to control the network audio host to disconnect the connection of the corresponding protocol device. Upon receiving the disconnection control command, the network audio host disconnects the data transmission channel with the corresponding protocol device according to the disconnection control command. That is, when the network audio host receives the disconnection control command transmitted through the bidirectional real-time data transmission channel, it parses the internal system identifier of the wired microphone A from the disconnection control command, confirms the real-time audio stream transmission channel with the wired microphone A based on the internal system identifier, and disconnects the real-time audio stream transmission channel. After disconnecting the real-time audio stream transmission channel of the wired microphone A, the connection status in the device record of the wired microphone A is updated to an unconnected state. Then, based on the updated connection status of the wired microphone A, status feedback information is generated and sent to the control device. The control device adjusts the connection status of the wired microphone A in the control interface 10 to an unconnected state based on the connection status of the wired microphone A in the status feedback information. By checking the disconnected status of wired microphone A in the control interface 10, the user can confirm that the network audio host has successfully disconnected the wired microphone A.

[0151] This embodiment controls the disconnection of the data transmission channel with the corresponding protocol device when a disconnection control command is received, thereby providing the user with a protocol device disconnection function. This allows the user to select the protocol device that maintains a connection with the network audio host according to actual needs, achieving unified management of the disconnection and connection of various protocol devices and improving the flexibility of the audio system.

[0152] After the network audio host disconnects the data transmission channel with wired microphone A according to the disconnect control command, if the user wants to restore the connection between the network audio host and wired microphone A, they can move the connection / disconnect control for wired microphone A from the right to the left in the control interface. At this time, the control device generates a connection control command based on the internal system identifier of wired microphone A and sends the connection control command to the network audio host through the bidirectional real-time data transmission channel. After receiving the connection control command, the network audio host parses the internal system identifier of wired microphone A in the connection control command, obtains the corresponding device type and communication protocol type from the device record of wired microphone A based on the internal system identifier, determines the communication connection method of wired microphone A based on the device type and communication protocol type, and establishes a data transmission channel with wired microphone A according to the communication connection method. Afterwards, the network audio host updates the connection status in the device record of wired microphone A to the connected state, generates status feedback information based on the updated connection status of wired microphone A, and sends the status feedback information to the control device. The control device adjusts the connection status of wired microphone A in the control interface to the connected state based on the connection status of wired microphone A in the status feedback information. By checking the connection status of wired microphone A on the control interface, the user can confirm that the network audio host has successfully restored the connection of wired microphone A.

[0153] It should be noted that, in addition to being sent by the control device, disconnect and connect control commands can also be sent by the front end and the preset control terminal. The process of generating and sending disconnect and connect control commands by the front end and the preset control terminal can be referred to the generation and sending process of the control device described above, and will not be repeated here.

[0154] Besides being actively disconnected by the network audio host, the data transmission channel of the protocol device may also be passively disconnected due to other external factors. In the case of passive disconnection, it confirms an abnormal interruption in the connection with the protocol device, requiring the re-establishment of the data transmission channel to avoid affecting continuous audio playback and improve the reliability of the audio system. Optionally, the network audio host can check whether the data transmission channel with the protocol device remains connected based on a preset period. If no disconnection control command is received from the protocol device, and a data transmission channel disconnection is detected, the data transmission channel is re-established with the protocol device according to its communication protocol type and device type. For example, if the network audio host currently establishes data transmission channels with wired microphone A, wired microphone B, wireless microphone C, and wireless microphone D, the network audio host checks whether these data transmission channels are continuously transmitting data based on a preset period. If data is being transmitted, the data transmission channel is confirmed to remain connected; if no data is being transmitted, the data transmission channel is confirmed to be disconnected. If wireless microphone C experiences a network abnormality or automatically shuts down due to low battery, the data transmission channel between wireless microphone C and the network audio host is automatically disconnected, and the network audio host detects the disconnection. Since the network audio host did not receive a disconnection control command for wireless microphone C, it can be confirmed that wireless microphone C was passively disconnected. Therefore, based on the system internal identifier of wireless microphone C, the device type and communication protocol type of wireless microphone C are obtained from the device record of wireless microphone C, and a data transmission channel is re-established with wireless microphone C based on the device type and communication protocol type.

[0155] This embodiment identifies the disconnection of the data transmission channel of a protocol device as an abnormal interruption when no disconnection control command related to the protocol device is received. Then, it re-establishes a connection with the protocol device according to the device type and communication protocol type, thereby achieving unified management of abnormal interruptions of various protocol devices, avoiding abnormal interruptions from affecting continuous audio playback, and improving the reliability of the audio system.

[0156] It should be noted that when the network audio host detects an abnormal interruption of a protocol device, it can confirm that the device's connection status has changed to a disconnected state. It can then update the device's connection status in the device log to disconnected. Once the device's connection status is updated, it will synchronously send status feedback information to control devices, etc. The control devices will then present the updated connection status to the user, allowing the user to identify which protocol devices have experienced abnormal interruptions. At this point, the user can intervene to maintain the protocol devices.

[0157] In addition, since the network audio host has a reconnection function, if the data transmission channel is abnormally interrupted due to network jitter, it will quickly restore the data transmission channel with the protocol device after the network audio host attempts to re-establish the connection. In this case, no user maintenance is required on the protocol device. To reduce user maintenance, a maximum reconnection timeout can be set for the network audio host. If the network audio host fails to re-establish the connection with the protocol device within the maximum timeout, it can be confirmed that the abnormal interruption of the protocol device was not caused by network jitter, thus determining that the protocol device itself is malfunctioning. At this point, the connection status in the protocol device's device record can be updated to "connected," and status feedback information is generated based on the updated connection status and sent to the control device. The control device then adjusts the connection status of the protocol device in the control interface to "connected" based on the status feedback information. After the user sees the protocol device's connection status changed to "connected," they can confirm that the protocol device's connection status is abnormal and can then manually check and maintain the protocol device.

[0158] refer to Figure 8 The control interface 10 also includes a volume control 13 on the right side of the connection status of each wireless audio device and network audio device. Users can adjust the playback volume of the wireless audio devices and network audio devices using the volume control 13, achieving unified management of the playback volume of both devices.

[0159] In one embodiment, the network audio host can pre-set various audio playback scenarios, such as small meetings, large performances, and remote conferences. Under different audio playback scenarios, the network audio host establishes data transmission channels with different network audio devices and wireless audio devices, and sets the playback volume of the network audio devices and wireless audio devices. The control device, front-end, and / or preset control terminal can provide audio playback scenario setting controls in the control interface. Users can input audio playback scenario settings through the setting controls. The control device, front-end, and / or preset control terminal respond to the setting operation, generate scene control commands, and send the scene control commands to the network audio host. The network audio host determines the corresponding audio playback scenario based on the scenario type in the scene control command, controls the relevant network audio devices and wireless audio devices to save or disconnect connections according to the audio playback scenario, and adjusts the volume of the connected network audio devices and wireless audio devices. It should be noted that the audio playback scenarios can be pre-configured by the user in the network audio host through the control device, front-end, and / or preset control terminal according to playback needs. In practice, users can switch audio playback scenarios with a single click on the control device, front end, and / or preset control terminal. The network audio host can automatically load preset audio routes and device connection configurations to quickly adapt to different playback needs, improving the flexibility of the audio system and enhancing the user experience.

[0160] Once the network audio host starts working, it continuously monitors all signal interfaces of the network switch. If new network audio devices and / or wireless audio devices need to be added during a meeting or other event, simply connect the network audio device to the network switch and / or power on the wireless audio device. The network audio host will automatically register the network audio devices and / or wireless audio devices into the audio system for unified management, eliminating the need for rewiring and complex configuration, thus improving the scalability of the audio system.

[0161] In summary, the protocol device connection method provided in this application listens for connection requests from different protocol devices through pre-set discovery protocols of different types. When a connection request is detected, the system retrieves device attribute information of various protocol devices from the system device list based on the connection request. Based on the device attribute information, it determines the appropriate communication connection method for the protocol device and establishes an appropriate data transmission channel with the protocol device based on the communication connection method. This achieves unified management and automatic operation of the discovery and connection process for different protocol devices. Through the above technical means, a multi-protocol compatible audio system can be constructed. The audio system can automatically discover and connect to multiple protocol devices, achieving unified management of the discovery and connection process for multiple protocol devices. This eliminates the need for professionals to manually configure the discovery and connection process for each protocol device independently, simplifying the deployment of the audio system and providing a user-friendly, highly reliable, highly compatible, and highly scalable audio system.

[0162] Figure 9 This is a schematic diagram of the structure of a protocol device connection device provided in an embodiment of this application, with reference to... Figure 9 The protocol device connection device includes: a processor 31, a memory 32, a communication device 33, an input device 34, and an output device 35. The number of processors 31 and the number of memories 32 in the protocol device connection device can be one or more. The processor 31, memory 32, communication device 33, input device 34, and output device 35 of the protocol device connection device can be connected via a bus or other means.

[0163] The memory 32, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the protocol device connection method in any embodiment of this application. The memory 32 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the device. Furthermore, the memory 32 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0164] The communication device 33 is used for data transmission.

[0165] The processor 31 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory 32, thereby realizing the above-mentioned protocol device connection method.

[0166] Input device 34 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 35 may include display devices such as a display screen.

[0167] The protocol device connection device provided above can be used to execute the protocol device connection method provided in the above embodiments, and has corresponding functions and beneficial effects.

[0168] This application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a protocol device connection method. The protocol device connection method includes: listening for connection requests sent by various protocol devices, including network audio devices, wireless audio devices, and control devices, through a preset discovery protocol type; upon detecting a connection request, querying the device attribute information of the corresponding protocol device in the system device list according to the connection request, the system device list storing the device attribute information of pre-discovered and registered protocol devices; determining the communication connection method adapted to the corresponding protocol device based on the device attribute information; establishing a data transmission channel with the corresponding protocol device based on the communication connection method; and transmitting data with the corresponding protocol device based on the data transmission channel.

[0169] Storage medium – any type of memory device or storage device. The term “storage medium” is intended to include: mounting media, such as CD-ROM, floppy disk, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. Storage medium may also include other types of memory or combinations thereof. Furthermore, storage medium may reside in a first computer system in which the program is executed, or it may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term “storage medium” can include two or more storage media residing in different locations (e.g., in different computer systems connected via a network). Storage medium may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0170] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the protocol device connection method described above, but can also perform related operations in the protocol device connection method provided in any embodiment of this application.

[0171] The protocol device connection device, storage medium, and protocol device connection device provided in the above embodiments can execute the protocol device connection method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to the protocol device connection method provided in any embodiment of this application.

[0172] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application. The scope of this application is determined by the scope of the claims.

Claims

1. A method for connecting protocol devices, characterized in that, include: By using a preset discovery protocol type, the system listens for connection requests sent by various protocol devices, including network audio devices, wireless audio devices, and control devices. Upon detecting the connection request, the system queries the device attribute information of the corresponding protocol device in the system device list based on the connection request. The system device list stores the device attribute information of the protocol devices that have been discovered and registered in advance. Based on the device attribute information, determine the communication connection method adapted to the corresponding protocol device, establish a data transmission channel with the corresponding protocol device based on the communication connection method, and perform data transmission with the corresponding protocol device based on the data transmission channel.

2. The protocol device connection method according to claim 1, characterized in that, The method of listening for connection requests sent by various protocol devices through a preset discovery protocol type includes: According to the Session Advertisement Protocol, listen to whether the first network interface receives a Session Description Protocol message sent by the network audio device, and obtain the connection request sent by the network audio device according to the Session Description Protocol message; According to the wireless protocol, the wireless receiving host connected to the second network interface listens to whether it receives a response signal sent by the wireless audio device, and obtains the connection request sent by the wireless audio device based on the response signal. The response signal is sent by the wireless audio device based on the scan signal broadcast by the wireless receiving host. Listen to the third network interface to see if it receives a service request from the control device according to the multicast domain name protocol, and obtain the connection request sent by the control device according to the service request. Specifically, the first network interface, the second network interface, and the third network interface are monitored in parallel.

3. The protocol device connection method according to claim 1, characterized in that, The step of determining the communication connection method adapted to the corresponding protocol device based on the device attribute information includes: Obtain the communication protocol type and device type of the protocol device from the device attribute information; Based on the communication protocol type and device type of the protocol device, determine the communication connection method adapted to the protocol device.

4. The protocol device connection method according to claim 3, characterized in that, The establishment of a data transmission channel with the corresponding protocol device based on the communication connection method includes: When the communication protocol type is Real-Time Transport Protocol and the device type is Network Audio Device, a Real-Time Transport Connection Response is sent to the Network Audio Device so that the Network Audio Device establishes a Real-Time Audio Stream Transmission Channel with the Audio System based on the Real-Time Transport Connection Response. When the communication protocol type is a proprietary protocol and the device type is a wireless audio device, a wireless receiver sends a wireless connection response to the wireless audio device so that the wireless audio device establishes a wireless audio transmission channel with the audio system based on the wireless connection response. When the communication protocol type is WebSocket and the device type is a control device, a WebSocket connection response is sent to the control device so that the control device establishes a bidirectional real-time data transmission channel with the audio system based on the WebSocket connection response.

5. The protocol device connection method according to claim 1, characterized in that, Before listening for connection requests from various protocol devices using a preset discovery protocol type, the process also includes: By using preset discovery protocol types, listen for announcement information sent by devices using various protocols; Upon receiving the announcement information, the device attribute information of the corresponding protocol device is obtained based on the announcement information, and the corresponding protocol device is registered to the system device list based on the device attribute information.

6. The protocol device connection method according to claim 5, characterized in that, The step of obtaining the device attribute information of the corresponding protocol device based on the announcement information includes: The announcement information is parsed according to the discovery protocol type corresponding to the protocol device, and the field content of each device attribute field is extracted from the parsed announcement information. The content of each of the device attribute fields is mapped to the field of the same device attribute in the unified data model to obtain standard device data; The standard device data is encapsulated into a standard data format to obtain the device attribute information of the protocol device.

7. The protocol device connection method according to claim 5, characterized in that, The step of registering the corresponding protocol device to the system device list based on the device attribute information includes: The device attribute information of the protocol device is stored as a device record in the system device list; Assign a system internal identifier to the protocol device, and add the system internal identifier to the device record of the protocol device; Update the index and / or data structure of the system device list.

8. The protocol device connection method according to claim 5, characterized in that, After registering the corresponding protocol device to the system device list based on the device attribute information, the method further includes: Obtain the IP address of the protocol device from its device attribute information; A registration success message is generated based on the system internal identifier of the protocol device; The protocol device sends a registration success message back to the protocol device by using the discovery protocol type and IP address, so that the protocol device can send a connection request based on the registration success message.

9. The protocol device connection method according to claim 1, characterized in that, After establishing a data transmission channel with the corresponding protocol device based on the communication connection method, the method further includes: Received disconnect control command; The data transmission channel with the corresponding protocol device will be disconnected according to the disconnection control command.

10. The protocol device connection method according to claim 1, characterized in that, After establishing a data transmission channel with the corresponding protocol device based on the communication connection method, the method further includes: Based on a preset periodic detection, it is determined whether the data transmission channel with the protocol device remains connected; If the data transmission channel is detected to be disconnected without receiving a disconnection control command from the protocol device, a new data transmission channel is established with the protocol device according to the communication protocol type and device type of the protocol device.

11. The protocol device connection method according to claim 7, characterized in that, After storing the device attribute information of the protocol device as a device record in the system device list, the method further includes: Add the connection status of the protocol device to the device record of the protocol device, and initialize the connection status to a disconnected state. Accordingly, the method further includes: After the data transmission channel with the protocol device is established, the connection status in the device record of the protocol device is updated to the connected status; After the data transmission channel with the protocol device is disconnected, the connection status in the device record of the protocol device is updated to a disconnected status.

12. The protocol device connection method according to claim 11, characterized in that, The method further includes: After the connection status of any device in the system device list is updated, status feedback information is generated based on the updated connection status. The status feedback information is sent to the control device, front end, and / or preset control terminal to indicate the connection status.

13. A protocol device connection device, characterized in that, include: One or more processors; A memory that stores one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the protocol device connection method as described in any one of claims 1-12.

14. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the protocol device connection method as described in any one of claims 1-12.

Images