SONIC WAVE RECEPTION DEVICE, SONIC WAVE RECEPTION METHOD, AND PROGRAM

Abstract

To easily add an acoustic communication function to a built-in device or a terminal device such as an information terminal.SOLUTION: A sound wave receiving device connected to a terminal device includes a sound wave acquisition unit that acquires sound waves around the sound wave receiving device, a sound wave analysis unit that analyzes the sound wave acquired by the sound wave acquisition unit and extracts identification information represented by the sound wave, a notification unit that notifies the terminal device of the identification information extracted by the sound wave analysis unit, and a setting unit that sets identification information to be notified to the terminal device by the notification unit or notification timing to notify the terminal device of the identification information.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a sound wave receiving device, a sound wave receiving method, and a program. [Background technology]

[0002] There is known an acoustic communication system that transmits data by sound waves using a microphone and a speaker. For example, there is known an acoustic communication system that provides an acoustic communication function to built-in devices such as washing machines, microwave ovens, and televisions, and general-purpose information terminals such as smartphones (for example, see Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0003] In the conventional technology as shown in Patent Document 1, in order to provide an embedded device with an acoustic communication function, control software was developed for each device. In addition, in general-purpose information terminals such as smartphones, application programs for acoustic communication (hereinafter referred to as apps) can be used, but due to restrictions on the OS (Operating System), etc., there are problems such as acoustic communication not being possible unless the app is in the foreground state. Furthermore, in general-purpose information terminals, acoustic communication is not taken into consideration, so the position and directional characteristics of the microphone may not be suitable for acoustic communication.

[0004] As described above, with conventional technology, it has been difficult to add an acoustic communication function to embedded devices, information terminals, and the like.

[0005] An embodiment of the present invention has been made in consideration of the above problems, and makes it possible to easily add an acoustic communication function to a terminal device such as an embedded device or an information terminal. [Means for solving the problem]

[0006] In order to solve the above problems, an ultrasonic wave receiving device according to one embodiment of the present invention is a ultrasonic wave receiving device that is connected to a terminal device, and includes a ultrasonic wave acquisition unit that acquires ultrasonic waves around the ultrasonic wave receiving device, a ultrasonic wave analysis unit that analyzes the ultrasonic waves acquired by the ultrasonic wave acquisition unit and extracts identification information represented by the ultrasonic waves, a notification unit that notifies the terminal device of the identification information extracted by the ultrasonic wave analysis unit, and a setting unit that sets the identification information that the notification unit notifies the terminal device, or the notification timing for notifying the terminal device of the identification information. The notification unit has a notification permission list that stores identification information to be notified to the terminal device, and the notification unit notifies the terminal device of the identification information stored in the notification permission list. Effect of the Invention

[0007] According to one embodiment of the present invention, an acoustic communication function can be easily added to an embedded device or a terminal device such as an information terminal. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of a sound wave receiving system according to an embodiment. [Diagram 2] 1 is a diagram showing an example of the appearance of a sound wave receiving device according to an embodiment; [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a sound wave receiving device according to an embodiment. [Figure 4] FIG. 1 is a diagram illustrating an example of a functional configuration of a sound wave receiving system according to an embodiment. [Diagram 5] 5 is a flowchart showing an example of processing performed by the sonic wave receiving device according to the first embodiment. [Figure 6] 10 is a flowchart showing an example of a notification process of a sound wave ID according to the first embodiment. [Figure 7] 4 is a sequence diagram showing an example of processing of the sound wave receiving system according to the first embodiment. FIG. [Figure 8] 10 is a flowchart showing an example of processing performed by a sound wave receiving device according to a second embodiment. [Figure 9] FIG. 11 is a sequence diagram showing an example of processing of the sound wave receiving system according to the second embodiment. [Figure 10]FIG. 11 is a diagram showing an example of a notification permission list according to the second embodiment. [Figure 11] 13 is a flowchart showing an example of processing performed by a sound wave receiving device according to the third embodiment. [Figure 12] 13 is a flowchart showing an example of processing performed by a sound wave receiving device according to a fourth embodiment. [Figure 13] 13 is a flowchart showing another example of the process of the sonic wave receiving device according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0010] <System configuration> 1 is a diagram showing an example of a system configuration of a sonic wave receiving system according to an embodiment. The sonic wave receiving system 100 includes a sonic wave receiving device 110 that receives sonic waves 101 output from a sonic wave output device 130, and a terminal device 120 that connects the sonic wave receiving device 110. The sonic wave receiving system 100 may also include a sonic wave output device 130.

[0011] The sonic wave output device 130 is a device that outputs a sonic wave 101 that represents predetermined identification information (hereinafter referred to as a sonic ID). For example, the sonic wave output device 130 outputs a sonic wave that represents a sonic ID by using a sonic wave of a frequency (for example, about 20 Hz to 24 kHz) that can be acquired by a general microphone (hereinafter referred to as a microphone). However, the present invention is not limited to this, and the sonic wave output device 130 may output the sonic wave 101 that represents a sonic ID by using a frequency that is difficult to acquire by a general microphone.

[0012] The sonic wave output device 130 may be a standalone device, or may communicate with an information processing device such as a management server or an information terminal, and output the sonic wave 101 representing the sonic ID instructed by the information processing device. Alternatively, the sonic wave output device 130 may be a speaker included in a broadcasting facility such as a facility or a vehicle, and output the sonic wave 101 representing the sonic ID broadcast by the broadcasting facility. Furthermore, the sonic wave output device 130 may be, for example, an information terminal such as a smartphone, a tablet terminal, or a wearable terminal that executes an application program (hereinafter, referred to as an app) corresponding to the sonic wave receiving system 100. In short, the sonic wave output device 130 may be a device that outputs the sonic wave 101 representing the sonic ID in a predetermined format, and may have any configuration.

[0013] The sonic wave receiving device 110 is a device that connects to the terminal device 120 by a predetermined communication method 102 such as USB (Universal Serial Bus) or short-distance wireless communication, and provides an acoustic communication function to the terminal device 120. For example, the sonic wave receiving device 110 acquires a sonic wave 101 output by the sonic wave output device 130, and extracts a sonic wave ID represented by the sonic wave 101. In addition, the sonic wave receiving device 110 notifies the terminal device 120 of the extracted sonic wave ID, for example, according to settings from the terminal device 120 or the like.

[0014] In this embodiment, the method of expressing the sonic wave ID by the sonic wave 101 is not particularly limited. As an example, the sonic wave output device 130 may express digital values ​​of "1" and "0" by "on" and "off" of a plurality of frequencies. In this case, the sonic wave output device 130 can output the sonic wave 101 expressing an N-bit sonic wave ID by using sonic waves of predetermined N frequencies (N is an integer of 2 or more). The sonic wave receiving device 110 can extract the sonic wave ID by performing a fast Fourier transform (FFT) on the acquired sonic wave 101 and determining whether or not there are sonic waves of predetermined N frequencies. Preferably, the sonic wave output device 130 outputs the sonic wave 101 expressing the sonic wave ID by using sonic waves of a frequency of 16 kHz or more among the frequencies (e.g., 20 Hz to 24 kHz, etc.) that can be acquired by the microphone provided in the sonic wave receiving device 110. In this way, the sonic wave output device 130 can transmit the sonic wave ID by the sonic wave 101 so that it is difficult for ordinary people to hear.

[0015] As another example, the sound wave output device 130 may superimpose a sound wave ID by digital watermarking on sound waves in the audible frequency band such as voice announcements, music, environmental sounds, etc. Furthermore, the sound wave output device 130 may generate the sound wave 101 representing the sound wave ID by modulating the sound wave by a predetermined modulation method.

[0016] The terminal device 120 is an information terminal or an embedded device that is communicatively connected to the sonic receiving device 110 by a predetermined communication method 102. For example, the terminal device 120 may be an information terminal such as a PC (Personal Computer), a smartphone, a tablet terminal, or a wearable terminal that executes an application corresponding to the sonic receiving system 100. The terminal device 120 may also be an output device such as a PJ (Projector), an IWB (Interactive White Board: a white board having an electronic blackboard function capable of mutual communication), or a digital signage. Furthermore, the terminal device 120 may also be an execution device that executes a predetermined function such as a smart robot, an industrial machine, an imaging device, a sound collecting device, a medical device, a network home appliance, or an automobile (Connected Car).

[0017] For example, the terminal device 120 stores a sonic wave ID in association with a predetermined execution content, and executes the execution content corresponding to the sonic wave ID notified from the sonic wave receiving device 110. This allows the user to cause the terminal device 120 to execute various execution contents by outputting the sonic waves 101 including various sonic wave IDs from the sonic wave output device 130.

[0018] In the conventional technology, in order to provide an acoustic communication function to an embedded device such as the output device or execution device, it was necessary to develop control software for each device. In addition, an application for the sonic wave receiving system 100 can be used in an information terminal, but even with this method, acoustic communication cannot be performed unless the application is in the foreground state due to restrictions of the OS (Operating System). Furthermore, since acoustic communication is not taken into consideration in general-purpose information terminals, there is also a problem that the position and directional characteristics of the microphone are not suitable for acoustic communication. For example, the microphone of a smartphone is provided at the bottom of the display in accordance with the positions of the human ears and mouth, and is often directional to reduce surrounding noise, and there are cases where it is not possible to efficiently acquire surrounding sound waves 101 under normal use conditions.

[0019] On the other hand, according to this embodiment, by simply connecting the sonic wave receiving device 110 to an embedded device, an acoustic communication function can be easily added to the embedded device without developing control software for each device. Also, according to this embodiment, by simply connecting the sonic wave receiving device 110 to an information terminal device, the terminal device 120 can acquire the sonic wave ID represented by the sonic wave 101 output by the sonic wave output device 130 even when the app is in the background. Furthermore, the sonic wave receiving device 110 can be an omnidirectional microphone or a microphone having a directionality suitable for acquiring the sonic wave ID, so that the surrounding sonic waves 101 can be acquired efficiently.

[0020] In this way, according to this embodiment, an acoustic communication function can be easily added to the terminal device 120, such as an embedded device or an information terminal. Furthermore, according to this embodiment, there is no need to disclose the acoustic communication algorithm to the outside, and it is possible to make it a black box, which also makes it possible to prevent the technology from leaking out.

[0021] <Hardware configuration> Next, the hardware configuration of the sound wave receiving device will be described.

[0022] (External appearance of the sonic receiving device) 2 is a diagram showing an example of the external appearance of a sonic wave receiving device according to an embodiment. Here, as an example, an example of the external appearance of a sonic wave receiving device 110 that is connected to a terminal device 120 using a USB interface will be described.

[0023] In the example of Fig. 2, the sonic wave receiving device 110 has a microphone 201, a communication port 202, and a main body 203 with a control board mounted therein. The microphone 201 is a microphone that acquires sound waves around the sonic wave receiving device 110 and converts the sound waves into a sonic signal. The communication port 202 is a connector, such as a USB port, for connecting the sonic wave receiving device 110 to the terminal device 120. Note that the external appearance of the sonic wave receiving device 110 shown in Fig. 2 is one example. For example, when the sonic wave receiving device 110 connects to the terminal device 120 by short-range wireless communication, the sonic wave receiving device 110 does not need to have the communication port 202 (it may have the communication port 202).

[0024] (Hardware configuration of the sound wave receiving device) 3 is a diagram showing an example of a hardware configuration of a sonic wave receiving device according to an embodiment. The sonic wave receiving device 110 includes, for example, a CPU (Central Processing Unit) 301, a memory 302, a storage device 303, a communication I / F (Interface) 304, a sonic wave input I / F 305, a microphone 201, and a bus 306.

[0025] The CPU 301 is a calculation device that realizes various functions of the sonic wave receiving device 110 by executing predetermined programs stored in, for example, the memory 302 and the storage device 303. The memory 302 includes, for example, a RAM (Random Access Memory) that is a volatile memory used as a work area or the like of the CPU 301, and a ROM (Read Only Memory) that is a non-volatile memory that stores a program for starting the CPU 301 in advance. The storage device 303 is, for example, a non-volatile, large-capacity storage device such as a flash ROM or an SSD (Solid State Drive) that stores programs such as apps, information, data, and the like.

[0026] The communication I / F 304 is a communication interface for connecting the sonic wave receiving device 110 to the terminal device 120 so that the sonic wave receiving device 110 can communicate with the terminal device 120. The communication I / F 304 may be, for example, a USB interface, a serial interface such as RS232C, or a wired communication interface such as a wired LAN interface. The communication I / F 304 may also be, for example, a wireless LAN interface, or a wireless communication interface such as a short-range wireless communication interface such as Bluetooth (registered trademark).

[0027] The sonic wave input I / F 305 is a circuit or device including, for example, an amplifier circuit for amplifying the audio signal output by the microphone 201, and an AD (Analog-to-Digital) converter for converting the audio signal into sonic data. The microphone 201 collects sound waves around the sonic wave receiving device 110, converts them into audio signals, and outputs them. The bus 306 is a bus for transmitting address signals, data signals, and various control signals.

[0028] The terminal device 120 is an information terminal or an embedded device having a computer configuration, and the specific hardware configuration is various, so a detailed description is omitted here. Also, the sonic wave output device 130 may have any configuration as long as it can output the sonic wave 101 representing the sonic wave ID. For example, the sonic wave output device 130 may be a speaker connected to a broadcasting facility, or may be a computer having a communication function and a sonic wave output function.

[0029] <Functional configuration> FIG. 4 is a diagram illustrating an example of a functional configuration of a sound wave receiving system according to an embodiment.

[0030] (Functional configuration of the sound wave receiving device) 3 executes a predetermined program, the sonic wave receiving device 110 realizes a sonic wave acquiring unit 401, a sonic wave analyzing unit 402, a communication unit 403, a notification unit 404, a setting unit 405, a storage unit 406, etc. Note that at least a part of the above functional configurations may be realized by hardware.

[0031] 3 and the sonic wave input I / F 305, etc. to execute a sonic wave acquisition process for acquiring sonic waves around the sonic wave receiving device 110. For example, the sonic wave acquisition unit 401 controls the sonic wave input I / F 305 to convert the sonic waves picked up by the microphone 201 into sonic wave data, and stores the data in the storage unit 406, etc.

[0032] The sonic wave analysis unit 402 executes a sonic wave analysis process to analyze the sonic waves acquired by the sonic wave acquisition unit 401 and extract a sonic wave ID represented by the sonic wave. For example, the sonic wave analysis unit 402 analyzes (e.g., FFT analysis) the sonic wave data stored in the storage unit 406 by the sonic wave acquisition unit 401 and extracts the sonic wave ID by determining the presence or absence of sound waves of multiple frequencies representing the sonic wave ID.

[0033] The communication unit 403 executes a communication process to communicate with the terminal device 120, for example, using the communication I / F 304 in Fig. 3. For example, when the sonic wave receiving device 110 is connected to the terminal device 120 via a USB interface, the communication unit 403 communicates with the terminal device 120 via the USB interface. Also, when the sonic wave receiving device 110 is connected to the terminal device 120 by short-range wireless communication, the communication unit 403 communicates with the terminal device 120 by short-range wireless communication.

[0034] The notification unit 404 executes a notification process of notifying the terminal device 120 of the sonic wave ID extracted by the sonic wave analysis unit 402 via the communication unit 403 .

[0035] The setting unit 405 executes a setting process for setting the sonic ID to be notified to the terminal device 120 by the notification unit 404, or the notification timing for notifying the terminal device of the sonic ID. For example, the sonic wave receiving device 110 can set a plurality of notification timings, and the setting unit 405 sets a designated notification timing from among the plurality of notification timings in response to a request from the terminal device 120. Note that a specific example of the plurality of notification timings will be described later in the first embodiment.

[0036] In addition, the sonic wave receiving device 110 has a notification permission list that stores the sonic wave ID that the notification unit 404 notifies the terminal device 120, and the setting unit 405 sets the sonic wave ID to be notified to the terminal device 120 in the notification permission list in response to a request from the terminal device 120.

[0037] The storage unit 406 is realized by, for example, the program executed by the CPU 301 in FIG. 3, the storage device 303, the memory 302, etc., and stores various information or data such as a notification permission list and sound wave data.

[0038] (Functional configuration of terminal device) The terminal device 120 realizes a communication unit 411, a request unit 412, an execution control unit 413, a storage unit 414, etc. by, for example, a computer included in the terminal device 120 executing a predetermined program. Note that at least a part of the above functional configurations may be realized by hardware.

[0039] The communication unit 411 communicates with the sonic wave receiving device 110 connected to the terminal device 120. For example, when the sonic wave receiving device 110 is connected to a USB interface provided in the terminal device 120, the communication unit 411 communicates with the sonic wave receiving device 110 via the USB interface. Also, when the sonic wave receiving device 110 is connected to a wireless communication interface provided in the terminal device 120, the communication unit 411 communicates with the sonic wave receiving device 110 via the wireless communication interface.

[0040] The request unit 412 controls the sonic wave receiving device 110 by transmitting request information, such as a setting request, a notification start request, or a notification stop request, to the sonic wave receiving device 110 via the communication unit 411 .

[0041] The execution control unit 413 executes various processes based on the sonic wave ID notified from the sonic wave receiving device 110. For example, the terminal device 120 stores correspondence information in advance, which stores a plurality of sonic wave IDs and execution contents corresponding to each sonic wave ID, in the storage unit 414, and executes the execution contents corresponding to the sonic wave ID notified from the sonic wave receiving device 110. As a result, the terminal device 120 executes various processes according to the sonic wave ID represented by the sonic wave 101 output by the sonic wave output device 130.

[0042] The storage unit 414 stores various information or data, such as the above-mentioned correspondence information, for example.

[0043] <Processing flow> Next, the process flow of the sound wave receiving method according to the present embodiment will be described by taking a number of exemplary embodiments as examples.

[0044] [First embodiment] (Processing of sonic receiving device) Fig. 5 is a flowchart showing an example of processing of the sonic receiving device according to the first embodiment. For example, the sonic receiving device 110 is connected to the terminal device 120, and when it receives a notification start request from the terminal device 120, it repeatedly executes the processing shown in Fig. 5 until it receives a notification stop request. However, this is not limited to this, and the sonic receiving device 110 may be one that repeatedly executes the processing shown in Fig. 5 when it is connected to the terminal device 120.

[0045] In step S501, the sonic wave acquiring unit 401 of the sonic wave receiving device 110 acquires sonic waves (sound wave data) around the sonic wave receiving device 110. For example, the sonic wave acquiring unit 401 converts the sonic waves around the sonic wave receiving device 110 picked up by the microphone 201 into digital data in a predetermined format using the sonic wave input I / F 305 in Fig. 3, and stores the digital data in the storage unit 406 or the like.

[0046] In step S502, the sonic wave analysis unit 402 of the sonic wave receiving device 110 analyzes the sonic waves (sound wave data) acquired by the sonic wave acquisition unit 401, and extracts a sonic wave ID.

[0047] In step S503, the sonic wave analysis unit 402 determines whether or not the sonic wave ID has been extracted. If the sonic wave ID has been extracted, the sonic wave analysis unit 402 shifts the process to step S504. On the other hand, if the sonic wave ID cannot be extracted, the sonic wave analysis unit 402 shifts the process to step S507. Note that if the sonic wave ID cannot be extracted, the sonic wave analysis unit 402 may end the process of FIG. 5.

[0048] In steps S504 and S505, the sonic wave analysis unit 402 compares the extracted sonic wave ID with the latest sonic wave ID stored in the storage unit 406 to determine whether the sonic wave ID has been updated. If the sonic wave ID has been updated, the sonic wave analysis unit 402 shifts the process to step S506. On the other hand, if the sonic wave ID has not been updated, the sonic wave analysis unit 402 shifts the process to step S507.

[0049] In step S506, the sonic wave analysis unit 402 stores the updated sonic wave ID in the storage unit 406 as the latest sonic wave ID.

[0050] When the process proceeds to step S507, the notification unit 404 of the sonic wave receiving device 110 executes a sonic ID notification process to notify the terminal device 120 of the sonic wave ID extracted by the sonic wave analysis unit 402. For example, the notification unit 404 executes a sonic ID notification process as shown in FIG.

[0051] (Sound ID notification processing) Fig. 6 is a flowchart showing an example of a sonic ID notification process according to the first embodiment. This process shows an example of a sonic ID notification process executed by the notification unit 404 of the sonic wave receiving device 110 in step S507 in Fig. 5. Here, as an example, a process example in which the sonic wave receiving device 110 can set four notification timings, from a first notification timing to a fourth notification timing, will be described.

[0052] In step S601, the notification unit 404 of the sonic wave receiving device 110 checks the notification timing setting. For example, the notification unit 404 reads out the notification timing setting of the sonic wave receiving device stored in the storage unit 406 or the like.

[0053] In step S602, the notification unit 404 determines whether the set notification timing is the first notification timing. Here, the first notification timing is set to notify the terminal device 120 of the extracted sonic wave ID when the sonic wave analysis unit 402 extracts the sonic wave ID.

[0054] If the notification timing is set to the first notification timing, notification unit 404 shifts the process to step S603. On the other hand, if the notification timing is not set to the first notification timing, notification unit 404 shifts the process to step S604.

[0055] In step S603, the notification unit 404 notifies the terminal device 120 via the communication unit 403 of the latest sound wave ID that the sound wave analysis unit 402 has stored in the storage unit 406.

[0056] On the other hand, when the process proceeds from step S602 to step S604, the notification unit 404 determines whether the set notification timing is the second notification timing. Here, the second notification timing is set to notify the terminal device 120 of the updated sonic wave ID when the sonic wave ID extracted by the sonic wave analysis unit 402 is updated.

[0057] If the notification timing is set to the second notification timing, notification unit 404 shifts the process to step S605. On the other hand, if the notification timing is not set to the second notification timing, notification unit 404 shifts the process to step S606.

[0058] When the process proceeds to step S605, the notification unit 404 determines whether the sonic wave ID extracted by the sonic wave analysis unit 402 has been updated. For example, when the process of step S506 in Fig. 5 has been executed, the notification unit 404 determines that the sonic wave ID has been updated. When the sonic wave ID has been updated, the notification unit 404 transitions the process to step S603. On the other hand, when the sonic wave ID has not been updated, the notification unit 404 ends the process in Fig. 6.

[0059] On the other hand, when the process proceeds from step S604 to step S606, the notification unit 404 determines whether the set notification timing is the third notification timing. Here, the third notification timing is set to notify the terminal device 120 of the sonic wave ID extracted by the sonic wave analysis unit 402 at a predetermined time interval.

[0060] If the notification timing is set to the third notification timing, notification unit 404 shifts the process to step S607. On the other hand, if the notification timing is not set to the third notification timing, notification unit 404 shifts the process to step S609.

[0061] In step S607, the notification unit 404 determines whether or not a predetermined time has elapsed since the last time the sound wave ID was notified to the terminal device 120. If the predetermined time has elapsed, the notification unit 404 transitions the process to step S608. On the other hand, if the predetermined time has not elapsed, the notification unit 404 ends the process in FIG.

[0062] In step S608, the notification unit 404 notifies the terminal device 120 via the communication unit 403 of the latest sound wave ID that the sound wave analysis unit 402 has stored in the storage unit 406.

[0063] On the other hand, when the process proceeds from step S606 to step S609, the notification unit 404 determines whether the set notification timing is the fourth notification timing. Here, the fourth notification timing is set to notify the terminal device 120 of the sonic wave ID extracted by the sonic wave analysis unit 402 when a notification request from the terminal device 120 is accepted.

[0064] If the notification timing is set to the fourth notification timing, notification unit 404 moves the process to step S610. On the other hand, if the notification timing is not set to the fourth notification timing, notification unit 404 ends the process in FIG.

[0065] When the process proceeds to step S610, the notification unit 404 determines whether or not the transmission request flag is set to valid. Here, it is assumed that the sonic wave receiving device 110 executes a process of setting the notification request flag to valid when it receives a notification request for requesting notification of the sonic wave ID from the terminal device 120 in parallel with the process of FIG. 6. If the notification request flag is valid, the notification unit 404 transitions the process to step S611. On the other hand, if the notification request flag is invalid, the notification unit 404 ends the process of FIG. 6.

[0066] In step S611, the notification unit 404 notifies the terminal device 120 of the latest sound wave ID stored in the memory unit 406 by the sound wave analysis unit 402 via the communication unit 403. In addition, in step S612, the notification unit 404 clears the notification request flag (sets it to invalid).

[0067] Through the above process, the sonic wave receiving device 110 can notify the terminal device 120 of the sonic wave ID at the set notification timing among the first to fourth notification timings. The first to fourth notification timings are examples of multiple notification timings that can be set by the sonic wave receiving device 110. For example, the sonic wave receiving device 110 may be capable of setting only the first and second notification timings. In this case, if it is not the second notification timing in step S604 in FIG. 6, the notification unit 404 may end the process in FIG. 6.

[0068] Furthermore, the sonic wave receiving device 110 may be capable of setting any two or more of the first to fourth notification timings, or may be capable of setting five or more notification timings.

[0069] (Sound wave receiving system processing) 7 is a sequence diagram showing an example of processing of the sonic wave receiving system according to the first embodiment. This processing is a sequence diagram showing an example of processing of the entire sonic wave receiving system 100 including the sonic wave receiving device 110 that executes the processing described in FIGS.

[0070] Here, as an example for explanation, it is assumed that the sonic wave output device 130 outputs the sonic wave 101 representing "sound wave ID1" in steps S711 to S715 of Fig. 7. Similarly, it is assumed that the sonic wave output device 130 outputs the sonic wave 101 representing "sound wave ID2" in steps S716 to S718, and outputs the sonic wave 101 representing "sound wave ID3" in step S719.

[0071] In step S701, when the sonic wave receiving device 110 is connected to the terminal device 120, the request unit 412 of the terminal device 120 transmits a device information request to the sonic wave receiving device 110 to request acquisition of information related to the sonic wave receiving device 110.

[0072] In step S702, when the setting unit 405 of the sonic wave receiving device 110 receives a device information request from the terminal device 120, the setting unit 405 notifies the terminal device 120 of the device information of the sonic wave receiving device 110 stored in the storage unit 406, for example. The device information of the sonic wave receiving device 110 may include, for example, identification information (hereinafter referred to as a device ID) for identifying the sonic wave receiving device 110, or firmware version information. The device information of the sonic wave receiving device 110 may also include, for example, information on notification timing that can be set in the sonic wave receiving device 110.

[0073] In step S703, the request unit 412 of the terminal device 120 transmits, as an example, a setting request for requesting setting of the second notification timing (notification at the time of update) to the sonic wave receiving device 110. Note that the request unit 412 of the terminal device 120 can set, in the sonic wave receiving device 110, a notification timing required for controlling the terminal device 120, not limited to the second notification timing.

[0074] In step S704, the setting unit 405 of the sonic wave receiving device 110 sets the notification timing of the sonic wave receiving device 110 to the second notification timing in accordance with the setting request from the terminal device 120. Here, the second notification timing is a setting for notifying the terminal device 120 of the updated sonic wave ID when the sonic wave ID extracted by the sonic wave analysis unit 402 is updated, as described above.

[0075] In step S705, the request unit 412 of the terminal device 120 transmits a notification start request to the sonic wave receiving device 110. As a result, the sonic wave receiving device 110 repeatedly executes the processing of the sonic wave receiving device described with reference to FIG.

[0076] In step S706, when the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID1 output by the sonic wave output device 130 in step S714, the sonic wave receiving device 110 stores the sonic wave ID1 extracted from the sonic wave 101 in the storage unit 406 by the processing of steps S501 to S506 in Fig. 5. In addition, the sonic wave receiving device 110 notifies the terminal device 120 of a sonic wave ID notification including the latest sonic wave ID1 stored in the storage unit 406 by a sonic wave ID notification process as shown in Fig. 6.

[0077] When the sonic wave receiving device 110 receives the sonic wave representing the sonic wave ID1 output by the sonic wave output device 130 in step S715, the sonic wave ID has not been updated, so the sonic wave receiving device 110 does not notify the terminal device 120 of the sonic wave ID.

[0078] In step S707, when the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID2 output by the sonic wave output device 130 in step S714, the sonic wave receiving device 110 stores the sonic wave ID2 extracted from the sonic wave 101 in the storage unit 406 by the processes of steps S501 to S506 in Fig. 5. In addition, the sonic wave receiving device 110 notifies the terminal device 120 of a sonic wave ID notification including the latest sonic wave ID2 stored in the storage unit 406 by a sonic wave ID notification process as shown in Fig. 6.

[0079] When the sonic wave receiving device 110 receives the sonic waves representing the sonic wave ID2 output by the sonic wave output device 130 in steps S717 and S718, the sonic wave ID has not been updated, so the sonic wave receiving device 110 does not notify the terminal device 120 of the sonic wave ID.

[0080] In step S708, the request unit 412 of the terminal device 120 transmits a notification stop request to the sonic wave receiving device 110. As a result, the sonic wave receiving device 110 stops the sonic wave receiving device processing described in Fig. 5. When the sonic wave receiving device 110 stops the sonic wave receiving device processing, for example, in step S719, even if the sonic wave receiving device 110 receives a sonic wave 101 representing a new sonic wave ID3, it does not notify the terminal device 120 of the sonic wave ID.

[0081] The process of the sonic wave receiving system shown in Fig. 7 is an example. For example, in step S703 in Fig. 7, the request unit 412 of the terminal device 120 may transmit a setting request for requesting the setting of the first notification timing (constant notification) to the sonic wave receiving device 110. In this case, the sonic wave receiving device 110 notifies the terminal device 120 of the latest sonic wave ID stored in the storage unit 406 every time it receives a sonic wave 101 representing a sonic wave ID from the sonic wave output device 130.

[0082] 7, the request unit 412 of the terminal device 120 may transmit a setting request for requesting the setting of a third notification timing (notification at a predetermined time interval) to the sonic wave receiving device 110. In this case, the sonic wave receiving device 110 notifies the terminal device 120 of the latest sonic wave ID stored in the storage unit 406 every time a predetermined time has elapsed since the sonic wave receiving device 110 last notified the terminal device 120 of the sonic wave ID.

[0083] 7, the request unit 412 of the terminal device 120 may transmit a setting request requesting the setting of a fourth notification timing (notification at the time of receiving a transmission request) to the sonic wave receiving device 110. In this case, when the sonic wave receiving device 110 receives a transmission request for a sonic wave ID from the terminal device 120, it notifies the terminal device 120 of the latest sonic wave ID stored in the storage unit 406.

[0084] As described above, according to the first embodiment, an acoustic communication function (a function for receiving an acoustic ID) can be easily added to a terminal device such as an embedded device or an information terminal. In addition, the acoustic receiver 110 can notify the terminal device 120 of the acoustic ID at an appropriate notification timing in response to a setting request from the terminal device 120.

[0085] [Second embodiment] In the second embodiment, an example of processing in the case where the sonic wave receiving device 110 has a notification permission list that stores a sonic wave ID to be notified to the terminal device 120 will be described.

[0086] (Processing of sonic receiving device) Fig. 8 is a flowchart showing an example of the process of the sonic receiving device according to the second embodiment. For example, the sonic receiving device 110 is connected to the terminal device 120, and when it receives a notification start request from the terminal device 120, it repeatedly executes the process shown in Fig. 5 until it receives a notification stop request. Note that the basic process flow is the same as the process of the sonic receiving device according to the first embodiment described in Fig. 5, so a detailed description of the process similar to that of the first embodiment will be omitted here.

[0087] In step S801, the sonic wave acquisition unit 401 of the sonic wave receiving device 110 acquires sonic waves (sound wave data) around the sonic wave receiving device 110.

[0088] In step S802, the sonic wave analysis unit 402 of the sonic wave receiving device 110 analyzes the sonic waves (sound wave data) acquired by the sonic wave acquisition unit 401, and extracts a sonic wave ID.

[0089] In step S803, the sonic wave analysis unit 402 determines whether or not the sonic wave ID has been extracted. If the sonic wave ID has been extracted, the sonic wave analysis unit 402 shifts the process to step S804. On the other hand, if the sonic wave ID cannot be extracted, the sonic wave analysis unit 402 ends the process of FIG.

[0090] In steps S804 and S805, the notification unit 404 of the sonic wave receiving device 110 compares the sonic wave ID extracted by the sonic wave analysis unit 402 with the sonic wave IDs registered in the notification permission list, and determines whether or not the sonic wave ID is registered in the notification permission list. If the sonic wave ID is registered in the notification permission list, the notification unit 404 shifts the process to step S806. On the other hand, if the sonic wave ID is not registered in the notification permission list, the notification unit 404 ends the process of FIG. 8.

[0091] In steps S806 and S807, the sonic wave analysis unit 402 of the sonic wave receiving device 110 compares the extracted sonic wave ID with the latest sonic wave ID stored in the storage unit 406, and determines whether the sonic wave ID has been updated. If the sonic wave ID has been updated, the sonic wave analysis unit 402 shifts the process to step S808. On the other hand, if the sonic wave ID has not been updated, the sonic wave analysis unit 402 shifts the process to step S809.

[0092] In step S808, the sonic wave analysis unit 402 stores the updated sonic wave ID in the storage unit 406 as the latest sonic wave ID.

[0093] When the process proceeds to step S809, the notification unit 404 of the sonic receiving device 110 executes a notification process of the sonic ID. Here, the notification process of the sonic ID executed by the notification unit 404 may be, for example, a process of notifying the terminal device 120 of the latest sonic ID stored in the storage unit 406, or may be the notification process of the sonic ID according to the first embodiment described in FIG. 6.

[0094] Through the above processing, the sonic wave receiving device 110 can selectively notify the terminal device 120 of a sonic wave ID registered in the notification permission list from among the sonic wave IDs extracted from the sonic waves 101 output by the sonic wave output device 130.

[0095] (Sound wave receiving system processing) 9 is a sequence diagram showing an example of processing of the sonic wave receiving system according to the second embodiment. This processing shows an example of the overall processing of the sonic wave receiving system 100 according to the second embodiment.

[0096] Here, as an example for explanation, it is assumed that the sonic wave output device 130 outputs the sonic wave 101 representing "sound wave ID1" in steps S911 to S916 in Fig. 9. Similarly, it is assumed that the sonic wave output device 130 outputs the sonic wave 101 representing "sound wave ID2" in steps S917 to S918, and outputs the sonic wave 101 representing "sound wave ID3" in step S919. Note that here, detailed explanation of the processing contents similar to the processing of the sonic wave receiving system according to the first embodiment described in Fig. 7 will be omitted.

[0097] In step S901, the request unit 412 of the terminal device 120 transmits a device information request to the sonic wave receiving device 110 to request acquisition of information related to the sonic wave receiving device 110.

[0098] In step S902, when the setting unit 405 of the sonic wave receiving device 110 accepts a device information request from the terminal device 120, it notifies the terminal device 120 of the device information of the sonic wave receiving device 110 stored in the storage unit 406, for example.

[0099] In step S903, the request unit 412 of the terminal device 120 transmits a setting request for requesting setting of the notification permission list to the sonic wave receiving device 110. Here, as an example, it is assumed that the request unit 412 transmits a setting request for requesting registration of the sonic wave ID1 and the sonic wave ID3 in the notification permission list to the sonic wave receiving device 110.

[0100] In step S904, the setting unit 405 of the sonic wave receiving device 110 sets the sonic wave ID1 and the sonic wave ID3 in, for example, a notification permission list 1000 as shown in Fig. 10 in accordance with the setting request from the terminal device 120. As shown in Fig. 10, the notification permission list 1000 stores the sonic wave ID1 and the sonic wave ID3 requested to be registered in the notification permission list setting request from the terminal device.

[0101] In step S905, the request unit 412 of the terminal device 120 transmits, as an example, a setting request for requesting setting of the second notification timing (notification at the time of update) to the sonic wave receiving device 110. In this way, the second embodiment can be applied in combination with the first embodiment.

[0102] In step S906, in accordance with the notification timing setting request from the terminal device 120, the setting unit 405 of the sonic wave receiving device 110 sets the notification timing of the sonic wave receiving device 110 to the second notification timing.

[0103] In step S907, the request unit 412 of the terminal device 120 transmits a notification start request to the sonic wave receiving device 110. As a result, the sonic wave receiving device 110 repeatedly executes the processing of the sonic wave receiving device according to the second embodiment described in FIG.

[0104] In step S908, when the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID1 output by the sonic wave output device 130 in step S915, the sonic wave receiving device 110 stores the sonic wave ID1 extracted from the sonic wave 101 in the storage unit 406 by the processes of steps S801 to S808 in Fig. 8. In addition, the sonic wave receiving device 110 notifies the terminal device 120 of a sonic wave ID notification including the latest sonic wave ID1 stored in the storage unit 406 by a sonic wave ID notification process as shown in Fig. 6.

[0105] When the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID1 output by the sonic wave output device 130 in step S716, the sonic wave ID has not been updated, so the sonic wave receiving device 110 does not notify the terminal device 120 of the sonic wave ID.

[0106] Furthermore, when the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID2 output by the sonic wave output device 130 in steps S917 to S918, the sonic wave receiving device 110 does not notify the terminal device 120 of the sonic wave ID since the sonic wave ID2 is not registered in the notification permission list 1000.

[0107] In step S909, when the sonic wave receiving device 110 receives the sonic wave 101 representing the sonic wave ID3 output by the sonic wave output device 130 in step S919, the sonic wave receiving device 110 stores the sonic wave ID3 extracted from the sonic wave 101 in the storage unit 406 by the processes of steps S801 to S808 in Fig. 8. In addition, the sonic wave receiving device 110 notifies the terminal device 120 of a sonic wave ID notification including the latest sonic wave ID3 stored in the storage unit 406 by a sonic wave ID notification process as shown in Fig. 6.

[0108] The process of the sonic wave receiving system according to the second embodiment shown in Fig. 9 is an example. For example, the process of step S905 in Fig. 9 is not essential and is optional. If the process of step S905 is omitted, the sonic wave receiving device 110 notifies the terminal device 120 of the extracted sonic wave ID every time the sonic wave analysis unit 402 extracts a sonic wave ID registered in the notification permission list 1000.

[0109] Through the above process, the sonic wave receiving device 110 according to the second embodiment can selectively notify the terminal device 120 of the sonic wave ID registered in the notification permission list 1000.

[0110] For example, when multiple sonic wave receiving systems 100 are operating in one area, acoustic communication does not establish a communication link as in wireless communication, so in conventional technology, the sonic wave ID contained in the sound waves 101 output by other sonic wave output devices 130 was also notified to the terminal device 120.

[0111] On the other hand, the sonic wave receiving device 110 of the second embodiment can selectively notify the terminal device 120 of the sonic wave ID registered in the notification permission list 1000, making it easier to control the terminal device 120 even when multiple sonic wave receiving systems 100 are operating in one area.

[0112] [Third embodiment] Fig. 11 is a flow chart showing an example of the processing of the sonic receiving device according to the third embodiment. The processing of the sonic receiving device according to the third embodiment shown in Fig. 11 is obtained by adding processing of step S1101 to the processing of the sonic receiving device according to the second embodiment described in Fig. 8. Among the processing shown in Fig. 11, the processing of steps S801 to S809 is similar to the processing of the sonic receiving device according to the second embodiment described in Fig. 8, so here, differences from the second embodiment will be mainly described.

[0113] In the sonic wave receiving device 110 according to the second embodiment, if it is determined in step S805 that the sonic wave ID extracted by the sonic wave analysis unit 402 is not a sonic wave ID registered in the notification permission list 1000, the processing is terminated.

[0114] On the other hand, if the sonic wave receiving device 110 of the third embodiment determines in step S805 that the sonic wave ID extracted by the sonic wave analysis unit 402 is not a sonic wave ID registered in the notification permission list 1000, it executes processing of step S1101.

[0115] When the process proceeds to step S1101, for example, the notification unit 404 of the sound wave receiving device 110 notifies the terminal device 120 of error information indicating that a sound wave ID not registered in the notification permission list 1000 has been received.

[0116] This allows the terminal device 120 to notify the user of the terminal device 120 of error information indicating that a sound wave ID not registered in the notification permission list 1000 has been received, by displaying the error information on the display screen or by using a voice message, etc. Therefore, the user can take measures such as changing the installation position of the terminal device 120 so as not to be affected by other sound wave receiving systems, or changing the frequency of the sound waves 101 output by the sound wave output device 130.

[0117] As another example, when proceeding to step S1101, the ultrasonic wave analysis unit 402 of the ultrasonic wave receiving device 110 may store error information indicating that a ultrasonic wave ID that is not registered in the notification permission list has been received in the memory unit 406, etc.

[0118] This makes it easy for a user of the terminal device 120, for example, when a malfunction occurs, to read error information from the sonic wave receiving device 110 and determine that the cause of the malfunction is the sound waves output by another sonic wave receiving system 100.

[0119] [Fourth embodiment] Fig. 12 is a flowchart showing an example of the sonic wave reception process according to the fourth embodiment. The sonic wave reception process according to the fourth embodiment shown in Fig. 12 is obtained by adding the process of step S1201 to the sonic wave reception process according to the second embodiment described in Fig. 8.

[0120] In step S1201, the sonic wave acquisition unit 401 of the sonic wave receiving device 110 according to the fourth embodiment determines whether or not a sonic wave ID is registered in the notification permission list 1000. If a sonic wave ID is registered in the notification permission list 1000, the sonic wave acquisition unit 401 executes the process of step S801. On the other hand, if a sonic wave ID is not registered in the notification permission list 1000, the sonic wave acquisition unit 401 stops the process of step S801 and ends the process of FIG.

[0121] By the above process, the sonic wave receiving device 110 does not perform the sonic wave acquisition process when the sonic wave ID is not registered in the notification permission list 1000. As a result, when the sonic wave ID is not registered in the notification permission list 1000, the sonic wave receiving device 110 can omit the execution of the processes of steps S801 to S809 in Fig. 12, thereby reducing the power consumption of the sonic wave receiving device 110.

[0122] Fig. 13 is a flowchart showing another example of the sonic wave reception process according to the fourth embodiment. In the sonic wave reception process according to the fourth embodiment shown in Fig. 13, the process of step S1301 is added to the sonic wave reception process according to the second embodiment described in Fig. 8.

[0123] In step S1301, the sonic wave analysis unit 402 of the sonic wave receiving device 110 according to the fourth embodiment judges whether or not a sonic wave ID is registered in the notification permission list 1000. If a sonic wave ID is registered in the notification permission list 1000, the sonic wave analysis unit 402 executes the process of step S802. On the other hand, if a sonic wave ID is not registered in the notification permission list 1000, the sonic wave analysis unit 402 stops the process of step S802 and ends the process of FIG.

[0124] By the above process, the sonic wave receiving device 110 does not perform the sonic analysis process if the sonic wave ID is not registered in the notification permission list 1000. As a result, when the sonic wave ID is not registered in the notification permission list 1000, the sonic wave receiving device 110 omits the execution of the processes of steps S802 to 809 in Fig. 13, and can reduce the power consumption of the sonic wave receiving device 110.

[0125] As described above, according to each embodiment of the present invention, an acoustic communication function can be easily added to an embedded device or a terminal device such as an information terminal.

[0126] <Supplementary Information> Each function of each embodiment described above can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), or a conventional circuit module designed to execute each function described above. [Explanation of symbols]

[0127] 100 Sonic Receiving System 110 Sonic Receiver 120 Terminal Equipment 130 Sonic output device 401 Sonic Acquisition Unit 402 Sound Wave Analysis Department 404 Notification Department 405 Settings 1000 Notifications Allowed List [Prior art documents] [Patent documents]

[0128] [Patent Document 1] JP 2015-177201 A

Claims

1. A sonic wave receiving device connected to a terminal device, A sound wave acquiring unit that acquires sound waves around the sound wave receiving device; a sound wave analysis unit that analyzes the sound waves acquired by the sound wave acquisition unit and extracts identification information represented by the sound waves; a notification unit that notifies the terminal device of the identification information extracted by the sound wave analysis unit; a setting unit that sets identification information to be notified to the terminal device by the notification unit or a notification timing for notifying the terminal device of the identification information; having a notification permission list for storing identification information to be notified to the terminal device by the notification unit; The notification unit notifies the terminal device of the identification information stored in the notification permission list. Sonic receiving device.

2. The sonic wave receiving device according to claim 1 , wherein the setting unit sets, in the notification permission list, identification information to be notified to the terminal device in response to a request from the terminal device.

3. The sound wave receiving device according to claim 1 , wherein the sound wave analysis unit stops acquiring the sound waves or extracting the identification information represented by the sound waves when no identification information is stored in the notification permission list.

4. When the sonic wave analysis unit extracts identification information that is not stored in the notification permission list, The sonic wave receiving device according to claim 1 , wherein the notification unit notifies the terminal device of error information.

5. The sonic wave receiving device is a first notification timing for notifying the terminal device of the extracted identification information when the sonic wave analysis unit extracts the identification information; or a second notification timing for notifying the terminal device of the updated identification information when the identification information extracted by the sound wave analysis unit is updated; It is possible to set The ultrasonic receiving device according to any one of claims 1 to 4, wherein the setting unit sets the notification timing of the ultrasonic receiving device to one of a plurality of notification timings that can be set in the ultrasonic receiving device in response to a request from the terminal device.

6. The sonic wave receiving device is a third notification timing for notifying the terminal device of the identification information extracted by the sound wave analysis unit at a predetermined time interval; or a fourth notification timing for notifying the terminal device of the identification information extracted by the sound wave analysis unit upon receiving a notification request from the terminal device; The sonic wave receiving device according to claim 5, further configurable to:

7. The sonic wave receiving device according to claim 1 , wherein the sonic wave receiving device is communicably connected to the terminal device via a USB interface or wireless communication.

8. A sonic wave receiving device connected to a terminal device, A sound wave acquisition process for acquiring sound waves around the sound wave receiving device; a sound wave analysis process for analyzing the sound waves acquired in the sound wave acquisition process and extracting identification information represented by the sound waves; A notification process of notifying the terminal device of the identification information extracted by the sound wave analysis process; and A setting process for setting identification information to be notified to the terminal device in the notification process or a notification timing for notifying the terminal device of the identification information; Run The sound wave receiving device has a notification permission list for storing identification information to be notified to the terminal device, The notification process notifies the terminal device of the identification information stored in the notification permission list. How to receive sound waves.

9. A sonic wave receiving device connected to a terminal device, A sound wave acquisition process for acquiring sound waves around the sound wave receiving device; a sound wave analysis process for analyzing the sound waves acquired in the sound wave acquisition process and extracting identification information represented by the sound waves; A notification process of notifying the terminal device of the identification information extracted by the sound wave analysis process; and A setting process for setting identification information to be notified to the terminal device in the notification process or a notification timing for notifying the terminal device of the identification information; Run the command, The sound wave receiving device has a notification permission list for storing identification information to be notified to the terminal device, The notification process notifies the terminal device of the identification information stored in the notification permission list. program.

Images