Acoustic device network for layout estimation

Abstract

Methods and systems for configuring a network of acoustic devices are provided. In one example, a method includes: connecting a first device (e.g., a mobile device with audio control software) and a second device (e.g., a primary audio device) to a network; transmitting a first audio signal using a third device (e.g., an auxiliary audio device), wherein the first audio signal is encoded using a network address of the third device. The first audio signal can be detected on the second device and the network address can be decoded; the second device can transmit a connection request to the first device; in response to a connection confirmation received by the first device, a second audio signal can be transmitted using the second device, wherein the second audio signal is encoded using a network certificate of the network; the second audio signal can be detected using the third device and the network certificate can be decoded.

Description

Technical Field

[0001] This disclosure relates to systems and methods for use in networks of acoustic devices. Background Technology

[0002] Setting up and connecting speakers and estimating their placement in a space (such as in home music or theater equipment, concert halls, and other spaces) can be done in a variety of ways. In some methods, various devices with speakers can be added to a network via Wi-Fi, Bluetooth, or some other suitable wireless network protocol.

[0003] In some methods, a central device, such as a mobile device like a cell phone, may be present to manage audio from multiple other devices equipped with speakers. In this approach, the central device can be used to manage an acoustic device network and control the audio output, channel allocation, volume, etc., of each device connected in the network. For example, the mobile device (such as a mobile phone or some other suitable computing device) may include software that assists the user in connecting various audio devices to the acoustic device network and performing various control operations.

[0004] In some methods, such acoustic devices can connect to each other via wireless network protocols such as Wi-Fi. As an example, a software application can be installed on a mobile device (such as a phone) to which multiple acoustic devices will connect. The user can connect the mobile device to a Wi-Fi network, and the software application on the mobile device can access Wi-Fi certificates, such as the network's SSID and password. Next, each of the audio devices can be manually connected to the same Wi-Fi network using the same certificate. Once all devices are connected, the user can proceed to configure an "immersive audio" group and configure the device network using the connected audio devices.

[0005] The inventors of this paper have recognized various problems with such methods for setting up networks of acoustic devices. For example, in the methods described above, users may have to manually connect each device to the network and enter the network certificate for each device, which is very time-consuming and requires a lot of user intervention, thus creating obstacles to setting up networks of acoustic devices. Furthermore, adding or removing audio devices from the network in such methods can be difficult and time-consuming, as each device may have to be added or removed manually by the user. Such methods can lead to user frustration and other obstacles when setting up networks of acoustic devices. Summary of the Invention

[0006] To address the aforementioned and other issues, this document provides methods and systems for configuring a network of acoustic devices. In one example method, a method for configuring a network is provided, comprising: connecting a first device (e.g., a mobile device on which audio control software is installed) to a second device (e.g., a main audio device) via the network; transmitting a first audio signal via a speaker associated with a third device (e.g., an audio device to be added to the network), wherein the first audio signal includes an audio signal encoded using a network address of the third device; detecting the first audio signal via a microphone associated with the second device; decoding the network address from the first audio signal on the second device; transmitting a connection request from the second device to the first device; transmitting a second audio signal via a speaker associated with the second device in response to a connection confirmation received by the first device, wherein the second audio signal includes an audio signal encoded using a network certificate of the network; detecting the second audio signal via a microphone associated with the third device; and decoding the network certificate from the second audio signal on the third device.

[0007] This approach provides an ideal method for configuring device networks using audio signals instead of wireless signals, thereby making the setup and configuration of acoustic device networks more automated and user-friendly. In this method, the audio signals can be 'watermarked' with inaudible data packets, which are likely unique to each device and shared between devices during the calibration process. This reduces some of the frustration associated with setting up a device network and further simplifies the process.

[0008] It should be understood that the above brief description is provided to present the concept choices further described in the detailed embodiments in a simplified form. This is not intended to identify key or essential features of the claimed subject matter, the scope of which is uniquely defined by the claims appended to the detailed embodiments. Furthermore, the claimed subject matter is not limited to implementations that address any shortcomings pointed out above or in any part of this disclosure. Attached Figure Description

[0009] Figure 1 An example acoustic device network configuration system is shown.

[0010] Figure 2A and Figure 2B The example audio device network setup process is shown.

[0011] Figure 3 and Figure 4 An example method for setting up the master device in an acoustic device network is shown.

[0012] Figure 5 and Figure 6 An example method for device discovery in a point-to-point network configuration of acoustic devices is shown.

[0013] Figure 7 An example method for device discovery in acoustic broadcast network configuration is shown.

[0014] Figure 8 An example method for informed device deregistration in an acoustic device network is shown.

[0015] Figure 9 An example method for unknowing device deregistration in an acoustic device network is shown.

[0016] Figure 10 An example method for estimating the layout of non-simultaneous devices in an acoustic device network is shown.

[0017] Figure 11 An example method for simultaneous device layout estimation in acoustic device networks is shown. Detailed Implementation

[0018] As mentioned above, setting up and connecting speakers and estimating their placement in a space (such as in home music or theater equipment, concert halls, and other spaces) can be done in a variety of ways. In some methods, various devices with speakers can be added to a network via Wi-Fi, Bluetooth, or some other suitable wireless network protocol.

[0019] As described in more detail below, for example, a network of devices can communicate acoustically with each other (i.e., “wireless”) without any wired connection using an imperceptible watermark embedded in the host audio content; that is, various data can be encoded into audio signals that can be shared between devices in the network.

[0020] This article describes the use of, for example, the following Figure 1 The methods and systems for creating and configuring acoustic data networks (ADNs) using audio watermarking are illustrated in the acoustic device network configuration system. In some examples, device layout calibration using audio watermarking can also be performed. As used herein, the phrase "audio watermarking" is intended to refer to encoding data into an audio signal that can be transmitted by a loudspeaker and received by a microphone. In some examples, the audio watermark may be substantially inaudible, which can be understood as meaning that even if the embedded audio watermark is within the range of human audible frequencies, the modification to the host audio signal will not be perceptible to humans.

[0021] As described herein, using audio watermarking for acoustic device network configuration and layout estimation enables an ideal experience for setting up multiple devices for immersive audio applications with minimal user intervention. In some examples, the method described herein can be extended to multiple types of devices with at least one microphone and at least one speaker. In some examples, the method described herein is backward compatible with legacy devices that do not support Wi-Fi Direct.

[0022] In some approaches, the acoustic network framework can leverage software applications on devices with Wi-Fi Direct connectivity (e.g., mobile devices, such as mobile phones) to create and operate networks with multiple audio devices. Wi-Fi Direct devices can connect to each other without needing to join a traditional home, office, or public network. With Wi-Fi Direct, devices may be able to establish one-to-one connections, or a group of devices may be able to connect simultaneously using various methods.

[0023] exist Figure 2A In one example method shown, an acoustic software application (APP) can be installed on a mobile device 202 to which multiple acoustic devices 204, 206, and 208 are to be connected. The user can connect the mobile device to a Wi-Fi network, and the software application on the mobile device can access Wi-Fi certificates, such as the network's SSID and password. Next, each of the audio devices can be manually connected to the same Wi-Fi network using the same certificate. Once all devices are connected, the user can proceed to configure an "immersive audio" group and configure the device network using the connected audio devices.

[0024] Once the device network is created and configured, data transfer between audio devices can be handled as explained below. First, dedicated Wireless Access Message Protocol (WAMP) messages can be defined. A process can be used to monitor and capture these messages, which are then broadcast to the peer-to-peer (P2P) network. All audio devices in the P2P network can subscribe to their own messages. The process can also deliver or repackage messages.

[0025] For the "Immersive Audio" group feature, at least two audio devices must be connected to the same Wi-Fi network. Next, in the acoustic software application, the names of the audio devices to be added to the device network can be selected. Then, on-screen instructions output by the application guide the user through the calibration and configuration steps. Audio devices can share data between the primary and secondary devices via a P2P connection.

[0026] An acoustic device network (ADN) is a collection of multiple audio devices (at least one microphone and speaker) in a shared acoustic environment, such as a living room, dormitory, etc. The method described herein provides an ideal device network configuration approach that uses audio signals for connectivity instead of wireless signals, thereby making the setup and configuration of acoustic device networks more automated and user-friendly. In this approach, the audio signals can be 'watermarked' with inaudible data packets, which may be unique to each device and shared between devices during calibration steps. This reduces some of the frustration associated with setting up a device network and further simplifies the process.

[0027] In some examples, it can be assumed that the devices are acoustically unobstructed (i.e., each device can hear every other device) and that the devices maintain a signal-to-noise ratio (SNR) higher than the ambient noise level. The following description... Figure 2B The diagram below provides a high-level summary of some example methods described herein. First, a master audio device 204 can be connected to a device 202 on which an acoustic software application (APP) is installed. For example, device 202 can be a mobile device such as a mobile phone. The acoustic software application accesses a Wi-Fi certificate and can be in calibration mode. In calibration mode, the master device's speaker can continuously broadcast a watermarked host signal (e.g., a music signal, a tone signal, a voice signal, etc.), which may contain encrypted messages about a unique master device ID and Wi-Fi information. Each time a new device wants to join the network, it 'listens' to the watermarked music, decodes the message, and joins the network. Each time a new device joins the network, the acoustic software application may register and allow the user to confirm and select a network configuration (e.g., stereo, 4.0, 5.0, etc.). Processing can be done locally on the device without sending data to any cloud infrastructure, so the device can be in listening mode when needed without privacy concerns.

[0028] Wi-Fi Direct devices operate like any Wi-Fi device, with a range of up to 200 meters. They can connect from a few feet away or throughout the entire house. Wi-Fi Direct supports Wi-Fi speeds up to 250 Mbps. For example, devices under a Wi-Fi Direct plan can protect security features certified under a WPA2 plan, but may be managed separately from security systems in AP-based networks (home, business, hotspot).

[0029] Devices registered in an ADN can form both P2P and / or broadcast networks. Devices registered in an ADN can be designed to create a multi-channel listening experience within the same room. Therefore, in some examples, their range may be limited to less than 6 meters by the microphone's signal-to-noise ratio (SNR). For example, devices registered in an ADN can support data transfers up to several hundred bps. Due to the lower transfer speeds, in some examples, channel routing / streaming can be done directly through the acoustic software application. In some examples, network security within the ADN can be managed by the user through the acoustic software application.

[0030] Figure 1 An example acoustic device network configuration system 100 is illustrated. In some examples, the acoustic device network configuration system 100 as described herein can be distributed among multiple devices, such as distributed among a first device 102, a second device 104, a third device 105, and so on. Devices 106, etc. Each of these devices can be an acoustic device including a processor, at least one microphone, at least one speaker, a wired or wireless transmitter / receiver, and memory. For example, first device 102 may include processor 108, microphone 110, speaker 112, transmitter / receiver 114, and memory 150; second device 104 may include processor 116, one or more microphones 118, speaker 120, transmitter / receiver, and memory 152; and the third... The device 106 may include a processor 124, one or more microphones 126, a speaker 128, a transmitter / receiver 130, and a memory 154.

[0031] Each of the processors in the multiple devices (such as processors 108, 116, and 124) can be single-core or multi-core, and the programs executing on them can be configured for parallel or distributed processing. In some embodiments, the processor may optionally include components distributed across two or more devices that can be remotely located and / or configured for coordinated processing. In some embodiments, one or more aspects of the processor may be virtualized and executed by a remotely accessible networked computing device configured in a cloud computing environment.

[0032] Memory (such as memories 150, 152, and 154) may include instructions executable by the respective processor. For example, memory may be a non-transitory memory storage medium configured with instructions such as algorithms, methods, procedures, etc., as will be described herein. For example, each of the memories described herein may include one or more modules or systems storing instructions. In some examples, portions of the instructions may be stored in the memory of one device but not in the memory of another device, while in other examples, all instructions may be stored in all devices.

[0033] The memory of the acoustic layout estimation system 100 may store an encoder 134, audio input / output (I / O) 136, a decoder 138, and a layout estimator 140, and may include various other subsystems. The encoder 134 may store instructions for acquiring desired host audio signals (e.g., predefined single-channel or multi-channel tones or user-selected audio content) from multiple devices in the system and, in some examples, embedding watermarks into the audio signals. The audio I / O 136 may simultaneously play and record watermarked signals from multiple devices. In some examples, watermarking performed via the encoder 134 may be performed in real-time, frame-by-frame; however, in other examples, the encoder may perform watermarking and store the watermark for later use. Therefore, the method performed via the encoder 134 can also be performed in real-time.

[0034] In some examples, decoder 138 may store instructions for estimating the time of arrival (TOA) between each device based on the recorded watermarked audio signal. The estimated TOA may also include a TOA confidence level. Layout estimator 140 may store instructions for determining device locations based on the estimated TOA. Specifically, the layout estimation may be robust to anomalous TOAs, thereby detecting and filtering out anomalous TOAs, thus improving the accuracy of layout determination.

[0035] As described above, the instructions for encoder 134, audio I / O 136, decoder 138, and layout estimator 140 can be stored in multiple devices, and in some instances, in all devices. In this way, the method disclosed herein can be executed by multiple devices without the use of external processing devices or equipment. In some examples, processing of the instructions stored in memory can be distributed among different devices; for example, each device can independently encode its own speaker input, such as watermarking the host audio before playback, and independently decode its own microphone output, such as estimating the TOA and corresponding confidence level between one or more of its microphones and the acoustic signals simultaneously derived from each speaker in the system. The independently estimated TOA and confidence level at each device can then be transmitted via wired or wireless communication modules of each device to a selected master device, which can execute, for example, the instructions for the layout estimator.

[0036] Each of the devices (e.g., first device 102, second device 104, and Nth device 106) may be communicatively coupled to preprocessor 132. Preprocessor 132 may include instructions for generating a watermark (e.g., a PN sequence or other suitable method for generating a watermark). Preprocessor 132 may be a single processing unit and may store watermarks generated for each device within the device network. In some examples, watermark generation may be performed offline (e.g., separately from some of the routines described herein). Therefore, each device may retrieve a specified watermark from preprocessor 132 (e.g., from the memory of preprocessor 132) to perform layout estimation and / or perform other operations described herein.

[0037] In some examples, the acoustic device network configuration system 100 may include or otherwise couple to a display device 142 configured to output a graphical user interface (GUI). For example, one of a plurality of devices may include the display device. In other examples, the acoustic layout estimation system 100 may, for example, be coupled to an external display device, such as a TV, laptop computer, tablet computer, or smartphone, via a wired or wireless connection.

[0038] Figure 3 and Figure 4 An example method 300 for setting up a master device 204 in an acoustic device network is shown. Specifically, Figure 3 Example steps of method 300 are shown, and Figure 4 Method 300 is shown from a device perspective, in which an initial setup process can be performed to connect a primary audio device (hereinafter referred to as the second device) to a first device 202 on which an acoustic software application (APP) is installed. For example, the first device 202 may include a mobile device having an acoustic software application for configuring and managing a network of acoustic devices.

[0039] At 302, method 300 includes determining whether an initial condition is met. In this example method, the acoustic software application on the first device 202 can directly interface with the main audio device 204 (the second device). The application can transmit watermarked data through a speaker associated with the first device 202 and receive and decode watermarked microphone data from the main device (the second device). This process can be triggered by user input received through the acoustic software application on the first device 202, which can enable a listening mode on the device. Therefore, the initial condition can include user input on the acoustic software application on the first device 202 to initiate an initial setup routine and enable a listening mode on the device. Additionally, in some examples, the initial condition can include a sufficiently quiet environment, for example, where the volume of any ambient noise in the environment may be below a predetermined threshold. Furthermore, the initial condition can include a connection of the first device 202 to a network (e.g., a Wi-Fi network or via Bluetooth) and access to network credentials (e.g., the network's SSID and password) provided to the acoustic software application on the first device 202.

[0040] If the initial conditions are met at 302, method 300 proceeds to 304 to transmit an audio signal containing the network's SSID and password (SSID / PWD) from the first device 202. Specifically, at 302, method 300 may include transmitting the audio signal via a speaker associated with the first device 202, wherein the audio signal includes an audio signal encoded using the network's network certificate. For example, an acoustic software application on the first device 202 may play a tone containing the encrypted SSID / PWD through the speaker of the first device. The master device 204 (the second device) may be in listening mode near the first device; for example, the first device may be a mobile phone or other mobile device.

[0041] At 306, method 300 includes detecting an audio signal with SSID / PWD at the second device 204 (main audio device). Specifically, the audio signal encoded using a network certificate from the first device 202 can be detected by a microphone associated with the second device 204.

[0042] At 308, method 300 includes decoding the SSID / PWD from the audio signal at the second device 204. Specifically, the second device can decode the network certificate from the audio signal encoded with the network certificate from the first device 202. For example, the second device 204 can use a predetermined key to decode the network certificate from the audio signal.

[0043] At 310, method 300 includes transmitting an acknowledgment (ACK) audio signal encoded using a MAC ID from the second device 204. Specifically, if the second device successfully decodes the network certificate from the audio signal detected at step 306, the ACK audio signal can be transmitted via a speaker associated with the second device 204. The ACK message audio signal can be watermarked (i.e., encoded) using the network address (e.g., Media Access Control (MAC) ID) of the second device 204 (the master device).

[0044] At 312, method 300 includes determining whether the first device 202 has detected an ACK audio signal transmitted from the second device 204. If at 312, the first device 202 does not detect an ACK audio signal, method 300 proceeds to 314 to have the first device output a volume increase request, and then returns to 304 to transmit the audio signal with SSID / PWD from the first device again. Specifically, if no acknowledgment audio signal from the second device 204 is detected by the microphone associated with the first device 202 after a predetermined time period, a volume increase prompt can be output from the first device 202. In some examples, the volume increase prompt can be output to a display device associated with the first device. For example, if the acoustic software application on the first device 202 does not receive an ACK message after a predetermined timeout period, the acoustic software application on the first device 202 can retransmit the audio signal from step 304 and request the user to increase the speaker volume on the second device 204 to retry the connection.

[0045] However, if the first device 202 detects an ACK audio signal at 312, method 300 proceeds to 316 to decode the MAC ID from the ACK audio signal at the first device 202. Specifically, a microphone associated with the first device 202 can detect the ACK audio signal, and then an acoustic software application on the first device 202 can decode the network address from the ACK audio signal. At 318, method 300 includes recording the network address (MAC ID) at the first device 202 for P2P communication with the second device 204.

[0046] At 320, method 300 includes outputting a network name assignment prompt from the first device 202. For example, after the two devices have successfully connected, an acoustic software application on the first device 202 may prompt the user to assign a name to the network (e.g., "living room").

[0047] The methods described herein (e.g., those described above and in...) Figure 3 and Figure 4The method 300 shown herein can be used for additional devices in an acoustic device network. For example, the method described herein can be used to add a third, fourth, or Nth device to an acoustic device network.

[0048] Figure 5 and Figure 6 An example method 500 for device discovery in a point-to-point network configuration of acoustic devices is illustrated. Specifically, Figure 5 Example steps of method 500 are shown, and Figure 6 Method 500 is shown from a device perspective, wherein an auxiliary audio device 602 (hereinafter referred to as a third device) is added to an acoustic device network, wherein the first device 202 and the second device 204 (the main audio device) are already connected to the network. As described above, the first device 202 may include a mobile device or the like having an acoustic software application (APP) for configuring and managing the acoustic device network.

[0049] At point 502, method 500 includes determining whether the first device and the second device are connected to the network. Specifically, this can be found in the reference above. Figure 3 and Figure 4 After successful completion of the initial setup, method 500 is implemented, wherein both the first device 202 and the second device 204 are connected to the acoustic device network. If the first device and the second device are connected at 502, method 500 proceeds to 504 to determine whether the initial conditions are met.

[0050] After at least one device (the main device, also referred to herein as the second device 204) connects to the acoustic software application on the first device 202 via Wi-Fi, Bluetooth, or some other suitable wireless network protocol, an additional device can be added to the network. Examples of initial conditions include placing the new device (the third device 602) to be added to the network within acoustically close (unobstructed) range of the main device (the second device 204) during registration. The process can be triggered by user input from the acoustic software application on the first device 202 to initiate the process and enable listening mode on the device.

[0051] If the initial conditions are met at 504, method 500 proceeds to 506 to transmit an audio signal with a MACID from the third device 602. Specifically, method 500 may include transmitting a first audio signal via a speaker associated with the third device 602 (auxiliary audio device), wherein the first audio signal includes an audio signal encoded using the network address (e.g., MACID) of the third device. For example, once the Wi-Fi button is pressed on the new device (third device 602), the device can play calibration music with a watermark including the device's MAC ID. In some examples, the volume level of the new device may need to be higher than the background noise level at the location of the second device 204 (main device).

[0052] Then method 500 proceeds to 508 to determine whether the second device 204 has detected a first audio signal encoded using a network address (e.g., MAC ID). Specifically, method 500 may include detecting (or attempting to detect) the first audio signal via a microphone associated with the second device 204. If the second device 204 detects the first audio signal with a MAC ID at 508, method 500 proceeds to 510 to decode the network address (e.g., MAC ID) from the first audio signal at the second device 204. At 512, method 500 includes recording the network address (e.g., MAC ID) at the second device 204 for use in P2P communication with the third device 602.

[0053] At 514, method 500 includes outputting a connection notification from the second device 204 to the first device 202. Specifically, a connection request may be transmitted from the second device 204 to the first device 202 on which the acoustic software application is installed, to provide notification of a new device connection request. At 516, method 500 includes outputting an acknowledgment prompt from the first device 202. For example, the acoustic software application on the first device 202 may prompt the user to confirm whether to add the third device 602 to the network. At 518, method 500 includes determining whether the connection has been acknowledged. If the connection is not acknowledged at 518, method 500 terminates. However, if the connection is acknowledged at 518, method 500 proceeds to 520 to output a connection acknowledgment from the first device 202 to the second device 204. Then, at 522, method 500 includes transmitting an audio signal with the network SSID / PWD from the second device 204. Specifically, in response to the first device 202 receiving a connection confirmation, a second audio signal can be transmitted via a speaker associated with the second device 204, wherein the second audio signal includes an audio signal encoded using a network certificate. For example, the acoustic software application on the first device 202 can output a prompt to the display device associated with the first device, asking the user, "Do you want to add a new device?". If the user selects "yes" or otherwise provides appropriate confirmation input at the first device 202, the first device can send a Bluetooth / Wi-Fi message to the second device 204 (the master device) for password / SSID sharing. However, if the user selects "no," the acoustic software application on the first device 202 can ignore the connection request.

[0054] At 524, method 500 includes detecting an audio signal having an SSID / PWD at a third device 602. Specifically, the second audio signal can be detected via a microphone associated with the third device 602. At 526, method 500 includes decoding the SSID / PWD from the second audio signal at the third device 602. At 528, method 500 includes transmitting an acknowledgment (ACK) signal from the third device 602. For example, if the third device 602 successfully connects to the network using the decoded network certificate, the third device can play an acknowledgment tone via a speaker associated with the third device, wherein the acknowledgment tone contains an acknowledgment (ACK) message.

[0055] At 530, method 500 includes determining whether the second device 204 has detected an ACK audio signal from the third device 602. If the second device 204 does not detect an ACK signal at 530, method 500 proceeds to 532 to output a volume increase request from the first device 202, and then proceeds back to 506 to transmit an audio signal with a MAC ID from the third device 602. Specifically, if no acknowledgment audio signal from the third device 602 is detected by the microphone associated with the first device 202 after a predetermined time period, a volume increase prompt can be output from the first device 202. In some examples, the volume increase prompt can be output to a display device associated with the first device 202. For example, if the acoustic software application on the first device 202 does not receive an ACK message after a predetermined timeout period, the acoustic software application on the first device 202 can request the user to increase the speaker volume on the third device 602, and method 500 can return to step 506.

[0056] However, if the second device 204 detects an ACK signal at 530, method 500 may optionally proceed to 534 to perform a position estimation routine to estimate the position of the third device 602 and / or the layout estimation of all devices connected to the acoustic device network. See below for reference. Figure 10 and Figure 11 The example location estimation routine is described in more detail.

[0057] At 536, method 500 includes performing channel assignment and adding the third device 206 to the network. For example, a user can perform channel assignment on an acoustic software application on the first device 202, and the user can play music output to the third device 602 and the second device 204. After each device is successfully connected to the network, a device ID and device name can be added to the acoustic device network.

[0058] Figure 7 An example method for device discovery in the configuration of acoustic broadcast networks is shown from a device perspective. Figure 7 The method shown is similar to method 500 described above and can be used when adding multiple auxiliary audio devices 702 to an acoustic device network. Figure 7 In the method shown, the first device 202 and the second device 204 (main audio device) are already connected to a network. As described above, the first device 202 may include a mobile device or the like having an acoustic software application (APP) for configuring and managing the acoustic device network.

[0059] refer to Figure 7Once the Wi-Fi button on each of the multiple auxiliary audio devices 702 is pressed, each new device plays a calibration music, which may include the unique MAC ID of each new device. The master device 204 can decode the multiple MAC IDs and store them in a first-in-first-out (FIFO) buffer, and notify the acoustic software application on the first device 202. The acoustic software application on the first device 202 can prompt the user whether to add the new device to the network. If the user confirms with the acoustic software application on the first device 202, the first device 202 can send a Bluetooth / Wi-Fi message to the master device 204 for password / SSID sharing. If the user does not confirm the connection, the acoustic software application on the first device 202 can ignore the connection request.

[0060] Once the connection request is confirmed, the master device 204 can embed the SSID / PWD into the ongoing calibration music and broadcast it. Each new device in the multiple auxiliary audio devices 702 can detect the watermark and decode the password and SSID. If successful, each new device plays an acknowledgment tone containing a unique acknowledgment (ACK) message. If the acoustic software application on the first device 202 does not receive the same number of ACK messages as the number of MAC IDs in the buffer, after a timeout period, the acoustic software application on the first device 202 can request the user to increase the speaker volume on the device and retry the connection. For example, the user can provide input to verify the correct number of devices connected to the acoustic software application on the first device 202. After a device successfully connects, the device ID and device name can be added to the acoustic device network. After the acoustic device network is successfully configured, the acoustic software applications on the first device 202 and the master device 204 can assign, maintain, and share a dictionary with device ID, device priority, and unique watermark for each device via Bluetooth or Wi-Fi.

[0061] Figure 8 An example method for informed device deregistration in an acoustic device network is illustrated. In this method, at least one device (e.g., master device 204) can be connected via Wi-Fi (or Bluetooth) to an acoustic software application (APP) on a first device 202. Informed deregistration encompasses shutting down the device (e.g., Figure 8This scenario involves a device (602) whose power or battery is depleted. A specific command ID can be defined and embedded in a power-off tone. Device 602 can play the power-off tone to notify the master device 204 of deregistration. The master device 204 can receive a deregistration request and remove device 204 from the acoustic device network. If the master device 204 decodes the deregistration request with low confidence, it notifies the acoustic software application on the first device 202, prompting the user to select a device and confirm deregistration. After successful deregistration, the master device 204 can also send a request to the acoustic software application on the first device 202 to prompt the user to reassign a channel.

[0062] Figure 9 An example method for uninformed device deregistration in an acoustic device network is illustrated. Uninformed deregistration covers devices (e.g., Figure 9 The scenario depicted is a device 602 moving out of the acoustic range of the master device 204 or being obstructed for any reason. This scenario is detected using a confidence score calculated during background range estimation at the master device 204. All devices in the acoustic device network can periodically perform synchronous and asynchronous ranging using an imperceptible watermark in the background. If the confidence score of the ranging estimate falls below a predefined threshold, the master device 204 can notify the acoustic software application on the first device 202. The acoustic software application on the first device 202 can prompt the user to check the status of the device with low confidence or choose to log out of that device. The master device 204 can also periodically notify the acoustic software application on the first device 202 of device layout, etc. If the master device 204 loses its Wi-Fi connection for any reason, the acoustic software application on the first device 202 can prompt the user to select another device as the master device. In some examples, the master device can be automatically assigned by the first device 202.

[0063] Figure 10 An example method 1000 for estimating the layout of non-simultaneous devices in an acoustic device network is illustrated. At 1002, method 1000 includes determining whether initial conditions are met. For example, at least one device (the master device) may need to be connected to an acoustic software application on a first device 202 via Wi-Fi (or Bluetooth). This method can be used to estimate the device layout before the devices, such as when playing any audio content in a quiet living room or home theater, do so. This process can be triggered by a user via the acoustic software application on the first device 202, thereby enabling a listening mode on the device.

[0064] If the initial conditions are met at 1002, method 1000 proceeds to 1004 to transmit a first audio signal from each device. For example, each device may play a calibration tone sequentially according to device ID or device priority. At 1006, method 1000 includes receiving the first calibration audio signal at each device. For example, a microphone associated with each device in the network may detect the calibration audio signal. At 1008, method 1000 includes performing a time of arrival (TOA) estimation at each device. For example, each device may listen to the calibration tone and perform its own TOA estimation using any suitable method. At 1010, method 1000 includes transmitting a second calibration audio signal along with the TOA estimation from each device to a master device (e.g., master audio device 204). For example, all devices other than the master device may begin playing the second tone (watermarked for data transmission) to transmit the respective TOA estimates sequentially to the master device according to device ID or device priority. At 1012, method 1000 includes decoding the TOA estimate for each device on the master device. For example, master device 204 may decode all messages and estimate an initial device layout. At 1014, method 1000 includes determining whether the master device decodes with high confidence. If the master device does not decode with high confidence at 1014, method 1000 proceeds to 1016 to send an error notification and then terminates. For example, if master device 204 cannot successfully decode a message with high confidence (set by a predefined threshold), it may notify the acoustic software application on the first device 202. The acoustic software application on the first device 202 may then raise an error and prompt the user to repeat the calibration process with a different layout. However, if the master device decodes with high confidence at 1014, method 1000 proceeds to 1018 to estimate the device layout at the master device. At 1020, method 1000 includes displaying the device layout. At 1022, method 1000 includes performing channel allocation. For example, the main device 204 can share the estimated coordinates with the acoustic software application on the first device 202 via Wi-Fi or Bluetooth for user display and channel allocation, etc. Once successful, the acoustic software application on the first device 202 can display the device layout and perform channel allocation, channel routing, and other playback channel controls.

[0065] Figure 11 An example method 1100 for simultaneous device layout estimation in an acoustic device network is illustrated. At 1102, method 1100 includes determining whether initial conditions are met. For example, method 1100 can be used to dynamically estimate the device layout while devices are simultaneously playing host audio content, where interruptions are not desired. This can also be performed after estimating the initial layout as described above. This process can be triggered by a user via an acoustic software application on a first device 202, thereby enabling a listening mode on the device.

[0066] If the initial conditions are met at 1102, method 1100 proceeds to 1104 to transmit a position request audio signal from the master device (e.g., master device 204). For example, once the process is initiated, the master device can transmit a watermarked signal (along with a request for device position updates) to all auxiliary devices to trigger a layout estimation process. At 1106, method 1100 includes transmitting a calibration signal from all devices. For example, all audio devices in the acoustic device network can begin embedding their watermarked signals into the host audio channel content being played through the acoustic device network. At 1108, method 1100 includes performing a TOA estimation at each device. For example, each device can listen to the watermarked signal and perform its own TOA estimation for each other device using a watermark dictionary shared after successful configuration, using any suitable method. At 1120, method 1100 includes transmitting a calibration audio signal along with the TOA estimate from each device to the master device. For example, once each device has calculated its respective TOA over a specified duration, each device (except the master device) can transmit its respective TOA estimate to the master device by embedding a second set of watermark signals. At 1122, method 1100 includes decoding the TOA estimate of each device on the master device. For example, master device 204 can decode all messages and update the initial device layout. At 1124, method 1100 includes determining whether the master device decoded with high confidence. If the master device did not decode with high confidence at 1124, method 1100 proceeds to 1126 to send an error notification and then terminates. For example, if master device 204 cannot successfully decode the message with high confidence, it can notify the acoustic software application on the first device 202. The acoustic software application on the first device 202 can then raise an error and prompt the user to repeat the calibration process with a different layout. However, if the master device decodes at 1124 with high confidence (set by a predefined threshold), method 1100 proceeds to 1128 to estimate the device layout at the master device. For example, the master device can share the estimated coordinates with the acoustic software application on the first device 202 via Wi-Fi or Bluetooth for user display and channel allocation, etc. At 1130, method 1100 includes performing channel allocation. At 1132, method 1100 includes displaying the device layout. For example, once successful, the acoustic software application on the first device 202 can display the device layout and perform, for example, channel allocation, channel routing, and other playback channel controls.

[0067] The invention will be further described in the following paragraphs. In one aspect, a method for configuring a network is provided, comprising: connecting a first device to a second device through the network; transmitting a first audio signal via a speaker associated with a third device, wherein the first audio signal includes an audio signal encoded using a network address of the third device; detecting the first audio signal via a microphone associated with the second device; decoding the network address from the first audio signal on the second device; transmitting a connection request from the second device to the first device; transmitting a second audio signal via a speaker associated with the second device in response to a connection confirmation received by the first device, wherein the second audio signal includes an audio signal encoded using a network certificate of the network; detecting the second audio signal via a microphone associated with the third device; and decoding the network certificate from the second audio signal on the third device. In some examples, the network address of the third device may include the MAC ID of the third device. In some examples, the network certificate may include the SSID and password of the network. Furthermore, in some examples, the first audio signal and the second audio signal may be inaudible. In some aspects, the method may further include: outputting a volume increase prompt from the first device if no acknowledgment audio signal from the third device is detected by a microphone associated with the first device after a predetermined time period. In some examples, the volume increase prompt may be output to a display device associated with the first device. In some aspects, the method may further include: connecting the first device to the second device via the network, which includes: connecting the first device to the network; transmitting a third audio signal via a speaker associated with the first device, wherein the third audio signal includes an audio signal encoded using a network certificate of the network; detecting the third audio signal via a microphone associated with the second device; and decoding the network certificate from the third audio signal on the second device. In some examples, the third audio signal may be inaudible. In some aspects, the method may further include: outputting a volume increase prompt from the first device if no acknowledgment audio signal from the second device is detected by a microphone associated with the first device after a predetermined time period. In some examples, the volume increase prompt may be output to a display device associated with the first device. In some examples, the first device may include a mobile phone. In some examples, the method may also include estimating the location of the third device.

[0068] In an additional aspect, a method for configuring an acoustic device network is provided, comprising: connecting a first device to the acoustic device network; transmitting a first audio signal via a speaker associated with the first device, wherein the first audio signal includes an audio signal encoded using a network certificate of the acoustic device network; detecting the first audio signal via a microphone associated with a second device; decoding the network certificate from the first audio signal on the second device; connecting the second device to the acoustic device network using the network certificate; and transmitting a second audio signal via a speaker associated with a third device, wherein the second audio signal includes an audio signal encoded using the network certificate. The third device encodes an audio signal with its network address; detects the second audio signal via a microphone associated with the second device; decodes the network address from the second audio signal on the second device; transmits a connection request from the second device to the first device; in response to a connection confirmation received by the first device, transmits a third audio signal via a speaker associated with the second device, wherein the third audio signal includes an audio signal encoded with the network certificate of the acoustic device network; detects the third audio signal via a microphone associated with the third device; and decodes the network certificate from the third audio signal on the third device. In some examples, the network address of the third device includes the MAC ID of the third device, and the network certificate includes the SSID and password of the acoustic device network. In some examples, the first audio signal, the second audio signal, and the third audio signal may be audible signals with an inaudible watermark.

[0069] In an additional aspect, a system is provided comprising: a first device including a first loudspeaker, a first microphone, and a first processor; a second device including a second loudspeaker, a second microphone, and a second processor; and a third device including a third loudspeaker, a third microphone, and a third processor; wherein the first device and the second device are connected to a network; wherein the third processor is configured to transmit a first audio signal via the third loudspeaker, wherein the first audio signal includes an audio signal encoded using a network address of the third device; wherein the second processor is configured to: detect the first audio signal via the second microphone; decode the network address from the first audio signal; transmit a connection request to the first device; and transmit a second audio signal via the second loudspeaker in response to a connection confirmation received by the first device, wherein the second audio signal includes an audio signal encoded using a network certificate of the network; wherein the third processor is further configured to: detect the second audio signal via the third microphone; and decode the network certificate from the second audio signal. In some examples, the second processor may be further configured to estimate the location of the third device. In some examples, the first audio signal and the second audio signal may be audible signals with an inaudible watermark. In some examples, the network address of the third device includes the MAC ID of the third device, and the network certificate includes the SSID and password of the network.

[0070] When describing elements of various embodiments of this disclosure, the articles “a,” “an,” and “the” are intended to indicate the presence of one or more elements. The terms “first,” “second,” etc., do not indicate any order, quantity, or importance, but are used to distinguish one element from another. The terms “comprising” and “having” are intended to be inclusive and indicate that there may be additional elements besides those listed. When the terms “connected to,” “coupled to,” etc., are used herein, an object (e.g., a material, element, structure, component, etc.) may be connected to or coupled to another object, regardless of whether the object is directly connected to or coupled to another object, or whether there are one or more intermediate objects between the two objects. Furthermore, it should be understood that references to “one embodiment” or “implementation” of this disclosure are not intended to exclude the existence of additional embodiments that also include the listed features.

[0071] In addition to any modifications previously indicated, those skilled in the art can devise many other variations and alternative arrangements without departing from the spirit and scope of this specification, and the appended claims are intended to cover such modifications and arrangements. Therefore, while the information has been described in particular and detail above in conjunction with what is now considered the most practical and preferred aspects, it will be apparent to those skilled in the art that various modifications can be made without departing from the principles and concepts set forth herein, including but not limited to changes in form, function, operation, and manner of use. Furthermore, as used herein, the examples and embodiments are intended in all respects to be illustrative and should not be construed as limiting in any way.

Claims

1. A method for configuring a network, comprising: The first device is connected to the second device via the network; A first audio signal is transmitted via a speaker associated with a third device, wherein the first audio signal includes an audio signal encoded using the network address of the third device; The first audio signal is detected via a microphone associated with the second device; The network address is decoded from the first audio signal on the second device; Transmit a connection request from the second device to the first device; In response to a connection confirmation received by the first device, a second audio signal is transmitted via a speaker associated with the second device, wherein the second audio signal includes an audio signal encoded using the network certificate of the network; The second audio signal is detected via a microphone associated with the third device; and The network certificate is decoded from the second audio signal on the third device.

2. The method according to claim 1, wherein the network address of the third device includes the MAC ID of the third device.

3. The method according to claim 1, wherein the network certificate includes the network's SSID and password.

4. The method according to claim 1, wherein the first audio signal and the second audio signal are audible signals containing an inaudible watermark.

5. The method of claim 1, wherein the first audio signal and the second audio signal are audible signals containing an inaudible watermark, and wherein the network address of the third device includes the MACID of the third device.

6. The method according to claim 1, further comprising: If no acknowledgment audio signal from the third device is detected by the microphone associated with the first device after a predetermined time period, the first device outputs a volume increase prompt.

7. The method of claim 5, wherein the volume increase prompt is output to a display device associated with the first device.

8. The method of claim 1, wherein connecting the first device to the second device via the network comprises: Connect the first device to the network; A third audio signal is transmitted via a speaker associated with the first device, wherein the third audio signal includes an audio signal encoded using the network certificate; The third audio signal is detected via a microphone associated with the second device; and The network certificate is decoded from the third audio signal on the second device.

9. The method of claim 8, wherein the third audio signal is an audible signal with an inaudible watermark.

10. The method of claim 8, further comprising: If no acknowledgment audio signal from the second device is detected by the microphone associated with the first device after a predetermined time period, the first device outputs a volume increase prompt.

11. The method of claim 10, wherein the volume increase prompt is output to a display device associated with the first device.

12. The method of claim 1, wherein the first device includes a moving device, and the method further includes estimating the position of the third device.

13. A system comprising: A first device, the first device comprising a first loudspeaker, a first microphone and a first processor; The second device includes a second loudspeaker, a second microphone, and a second processor; The third device includes a third loudspeaker, a third microphone, and a third processor; The first device and the second device are connected to a network; The third processor is configured to transmit a first audio signal via the third speaker, wherein the first audio signal includes an audio signal encoded using the network address of the third device; The second processor is configured as follows: The first audio signal is detected via the second microphone; Decode the network address from the first audio signal; Transmit a connection request to the first device; In response to a connection confirmation received by the first device, a second audio signal is transmitted via the second speaker, wherein the second audio signal includes an audio signal encoded using the network certificate of the network; The third processor is further configured to: The second audio signal is detected via the third microphone; and The network certificate is decoded from the second audio signal.

14. The system of claim 13, wherein the processor is further configured to estimate the location of the third device.

15. The system of claim 13, wherein the first audio signal and the second audio signal are audible signals with an inaudible watermark, or wherein the network address of the third device includes the MACID of the third device, and wherein the network certificate includes the SSID and password of the network.

Images