A sound system that enhances the sound amplification experience.

Abstract

To provide a sound reinforcement system that offers a more favorable sound reinforcement experience to listeners in a reinforced space. [Solution] The public address system 1 comprises one or more public address devices 11 installed in each of one or more public address spaces, and a server 20 connected to the public address devices 11 via the Internet network. The server 20 maintains a history 26 associated with mobile communication terminals 15 located within the public address space.

Description

Technical Field

[0001] The present invention relates to a voice amplification system for improving the voice amplification experience in a voice amplification space.

Background Art

[0002] Conventionally, there is a voice amplification system for delivering voice information to people staying and moving around in a predetermined space. The voice amplification system includes one or more voice amplification devices such as an audio power amplifier and a speaker, and outputs and amplifies voice in a space (voice amplification space) where the voice amplification device is installed. The voice amplification system is provided in various spaces visited by an unspecified or specified number of people, such as in the street, at a station of public transportation, in a public facility such as a park, in a store, in an office building, in a factory, etc., and is also called a public address system.

[0003] Generally, the voice amplification system holds voice data related to a predetermined sound source such as BGM and plays back the voice data according to a schedule (scheduled broadcast), or plays back and broadcasts voice data related to the voice of a speaker input from a microphone. Examples of the voice amplification system are disclosed in Patent Documents 1 to 3. In such a voice amplification system, it is common to transmit an analog voice signal via a speaker line also called a 100V line, but it is also becoming popular to transmit a digitized voice signal via an Ethernet (registered trademark) cable (LAN cable) compliant with the IEEE802 standard. In a voice amplification system using an Ethernet (registered trademark) cable, more detailed voice amplification broadcasting can be performed using IP speakers that can be individually identified by an IP address.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Patent Document 3

[0005] The present invention aims to provide a sound reinforcement system that can provide a more favorable sound reinforcement experience to listeners in a reinforced sound space. [Means for solving the problem]

[0006] The public address system comprises one or more public address devices installed in one or more public address spaces, and a server connected to the public address devices via the Internet. The public address devices periodically or irregularly transmit first information related to the public address operation to the server, and the server stores the first information received from the public address devices and provides the first information to external clients connected via the Internet. [Effects of the Invention]

[0007] According to the present invention, a more favorable sound amplification experience can be provided to the listener. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows a public address system according to an embodiment of the present invention. [Figure 2] Figure 2 shows an example of the configuration of a sound system within a public address system. [Figure 3] Figure 3 shows an example of the configuration of a sound system within a public address system. [Figure 4] Figure 4 is a flowchart illustrating an example of the operation flow for a data management server within a public address system to provide public address broadcast status to a client. [Figure 5] Figure 5 shows an example of the configuration of a sound system within a public address system. [Figure 6]Figures 6(a) and 6(b) show examples of logs maintained by the data management server within the public address system. [Figure 7] Figures 7(a) and 7(b) show examples of broadcast logs among the logs maintained by the data management server. [Figure 8] Figure 8 shows an example of a GUI provided by the data management server to the client. [Figure 9] Figure 9 is a flowchart illustrating an example of the operation flow for a data management server to provide clients with various information collected from cameras, microphones, and mobile communication terminals within a public address space. [Figure 10] Figures 10(a) and 10(b) show examples of the public address broadcasting period and the corresponding response expectation period. [Figure 11] Figure 11 shows an example of a database for managing sound reinforcement equipment, cameras, microphones, and mobile communication terminals within a sound reinforcement space. [Figure 12] Figure 12 shows an example configuration of a public address system, including a public address device, camera, microphone, and mobile communication terminal. [Figure 13] Figure 13 is a flowchart illustrating an example of the workflow in which the data management server statistically processes logs to create improvement suggestions regarding the operation of the public address system. [Figure 14] Figure 14 is a flowchart showing an example of an anomaly detection service. [Figure 15] Figure 15 shows an example of the configuration of a sound system within a public address system. [Figure 16] Figure 16 shows an example of a data management server in a public address system that maintains multiple sound sources and their history. [Figure 17] Figure 17 shows an example of the history maintained by the data management server. [Figure 18] Figure 18 is a flowchart showing an example of an operational flow for personalized broadcasting in a public address system. [Figure 19] FIG. 19 is a diagram showing an example in which a data management server holds a sound source for inspection in a public address system. [Figure 20] FIG. 20 is a flowchart showing an example of an operation flow related to an inspection service of a public address device in a public address system. [Figure 21] FIG. 21 is a diagram showing a configuration example of a modified example of a public address system. [Figure 22] FIG. 22 is a diagram of a table included in an operation monitoring device. [Figure 23] FIG. 23 is a diagram showing an example of an embodiment of a public address system including a plurality of server elements according to the functions of the services provided. BEST MODE FOR CARRYING OUT THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 shows a public address system 1 according to an embodiment. The public address system 1 includes one or more public address devices 11 provided in a public address space 10. Each public address device 11 includes an audio power amplifier and a speaker, amplifies the sound obtained by reproducing the audio data, and outputs it from the speaker. As an example, the public address device 11 uses audio data held in a recording medium such as a CD (Compact Disc), SD card, HDD (Hard Disk Drive), SSD (Solid State Drive), etc. as a sound source and reproduces the audio data. As an example, the public address device 11 has a microphone, generates and reproduces audio data from the voice of a speaker input from the microphone as a sound source. The public address space 10 is an area having a certain size where the public address device 11 is installed and is amplified by the public address device 11. An example of the public address space 10 is an outdoor predetermined area in the middle of the street (for example, a park, a square, an intersection, etc.), a predetermined indoor and outdoor area (arena, each floor of a shopping mall, each floor of an office building, school, research institution, government office building, factory, etc.) managed by a predetermined administrator, etc.

[0010] The public address space 10 includes one or more cameras 12 for acquiring video data of the situation in the public address space 10. An example of a camera 12 is a surveillance camera installed in the public address space 10 together with the public address device 11. Another example of a camera 12 is a camera mounted on an unmanned aerial vehicle (UAV) or drone programmed to fly within the public address space 10. For example, if the public address space 10 is an intersection, the camera 12 may be a surveillance camera installed on a pole on the road to monitor the intersection. For example, if the public address space 10 is inside a building such as a shopping mall, the camera 12 may be a surveillance camera installed on the ceiling of the building. Each camera 12 can individually perform actions for shooting, such as panning, tilting, and zooming, to photograph subjects within the public address space 10, generate video data, and store it on an internal recording medium or transmit it externally. The camera 12, in conjunction with the loudspeaker 11's loudspeaker broadcasting operation, performs actions for shooting such as panning, tilting, and zooming, and can capture subjects, generate video data, and store it on an internal recording medium or transmit it externally.

[0011] The public address space 10 includes one or more microphones 13 for acquiring the conditions of the public address space 10 as audio data. An example of a microphone 13 is a microphone installed in the public address space 10 together with the public address device 11. For example, when the public address space 10 is outdoors, such as in a park or intersection, the microphone 13 may be a microphone installed on a support such as a utility pole. For example, when the public address space 10 is inside a building such as a shopping mall, the microphone 13 may be a microphone installed on a structure such as the wall, column, or ceiling of the building. The microphone 13 is directed towards the public address space 10, and can acquire sound from within the public address space 10, generate audio data, and store it in an internal storage medium or transmit it externally. The microphone 13 can also acquire sound, generate audio data, and store it in an internal storage medium or transmit it externally in conjunction with the public address broadcasting operation of the public address device 11.

[0012] The public address space 10 includes a mobile communication terminal 15 held by a person (user 14) who is inside the public address space 10 and is listening to the public address broadcast from the public address device 11. An example of a mobile communication terminal 15 is a mobile phone, smartphone, or other device that can connect to the internet network via cellular communication such as LTE (Long Term Evolution) or 5G, or LAN (LAN Area Network) communication such as Wi-Fi.

[0013] The public address system 1 includes a data management server 20 accessible from clients via the Internet. The public address device 11, camera 12, microphone 13, and mobile communication terminal 15 are each accessible from the data management server 20 via the Internet. As shown in Figure 1, in the public address system 1, there are multiple public address spaces 10, and the data management server 20 is interconnected with the public address devices 11, camera 12, microphone 13, and mobile communication terminal 15 in each public address space 10 via the Internet.

[0014] Figure 2 shows an example of the configuration of the public address system 11. The public address system 11 comprises an input system 110, a processing system 111, an output system 112, and a communication system 113. The processing system 111 is interconnected with each of the input system 110, output system 112, and communication system 113 using a wired interface such as a cable or a wireless interface. The input system 110 is a subsystem that receives input of audio to be broadcast from the public address system 11. The input system 110 includes, for example, a microphone 110a and a background music device 110b. The microphone 110a is equipped with a microphone element such as a dynamic microphone or a condenser microphone and outputs the speaker's voice as an audio signal. The background music device 110b plays sound sources (audio data) recorded on recording media such as CDs, SD cards, HDDs, and SSDs and outputs them as audio signals.

[0015] The processing system 111 is a subsystem that receives an audio signal from the input system 110, processes the audio signal by changing its frequency characteristics and amplifying it, generates a broadcast signal for public address broadcasting, and outputs it to the output system 112. The processing system 111 includes an equalizer 111a that changes the frequency identification of the audio signal according to the settings for each frequency band, and an audio power amplifier 111b that amplifies the audio signal according to the volume setting.

[0016] The output system 112 is a subsystem that receives broadcast signals (audio signals) from the processing system 111 and outputs broadcast signals. The output system 112 is equipped with one or more speakers 112a located at various points within the sound reinforcement space 10, and each speaker 112a outputs a broadcast signal.

[0017] If the output system 112 has multiple speakers 112a, the processing system 111 can configure the routing of the broadcast signal to determine which speaker 112a should output the broadcast signal from. The processing system 111 configures the routing and outputs the broadcast signal from one or more specified speakers 112a. For example, each speaker 112a is assigned unique identification information (e.g., an IP address), and the processing system 111 specifies the identification information of one or more speakers 112a that it wants to broadcast from in the routing configuration.

[0018] The communication system 113 transmits and receives data with the data management server 20 via the Internet. The communication system 113 is connected to the processing system 111, receives information about the processing performed by the processing system 111, and transmits it to the data management server 20 via the Internet. Conversely, it receives information about the processing performed by the processing system 111 from the data management server 20 and passes this information to the processing system 111. The loudspeaker 11 has identification information (loudspeaker identification information) that uniquely identifies it, and the communication system 113 transmits data to the data management server 20 with this loudspeaker identification information attached. For example, the loudspeaker identification information is the IP address assigned to the loudspeaker 11. For example, the loudspeaker 11 is equipped with a positioning system using GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), and the loudspeaker identification information is location information such as longitude and latitude acquired by the positioning system. For example, the loudspeaker 11 is equipped with an indoor positioning system that uses beacon signals using Bluetooth®, RFID (Radio Frequency Identification), ultrasound, geomagnetic fields, UWB (Ultra Wide Band) signals, etc., and the loudspeaker identification information is indoor location information acquired by the indoor positioning system. For example, the loudspeaker 11 has a SIM (Subscriber Identity Module) and performs cellular communication using LTE, etc., and the loudspeaker identification information is identification information such as ICCID (Integrated Circuit Card ID) that identifies the SIM, IMSI (International Mobile Subscriber Identity) registered in the SIM, or IMEI (International Mobile Equipment Identity) registered in the SIM. The communication system 113 transmits data to the data management server 20 with the loudspeaker identification information attached.

[0019] If multiple loudspeakers 11 are installed within the same loudspeaker space 10, the communication system 113 may be separated from the loudspeakers 11, and all loudspeakers 11 may be configured to be connected to a common communication system 113. In this case, as shown in Figure 3, multiple loudspeakers 11 are connected to a common communication system 113 in the loudspeaker space 10. The communication system 113 exists as a separate piece of hardware from the loudspeakers 11, as a communication device with an independent enclosure. The communication system 113 is connected to each loudspeaker 11 via a communication interface such as a LAN cable. The communication system 113 communicates with the processing system 111 of each loudspeaker 11, transmits data received from the processing system 111 to the data management server 20, and, conversely, receives data from the data management server 20 and passes it on to the processing system 111. The communication system 113 receives loudspeaker identification information from each loudspeaker 11 and transmits the data to the data management server 20 with this loudspeaker identification information attached, thereby identifying which loudspeaker 11 the data belongs to within the loudspeaker space 10 and transmitting the data to the data management server 20. Furthermore, as shown in Figure 3, since all loudspeakers 11 are aggregated and connected to a common communication system 113, the communication system 113 has a one-to-one relationship with the loudspeaker space 10, and identifying the communication system 113 is equivalent to identifying the loudspeaker space 10. For this reason, the communication system 113 has its own unique identification information (communication system identification information), and transmits the data to the data management server 20 with this communication system identification information attached, thereby identifying which loudspeaker space 10 the data belongs to and transmitting the data to the data management server 20. For example, the communication system identification information is the IP address assigned to the communication system 113. For example, the communication system 113 is equipped with a positioning system using GNSS such as GPS, and the communication system identification information is location information such as longitude and latitude acquired by the positioning system. For example, communication system 113 is equipped with an indoor positioning system that uses beacon signals such as Bluetooth (registered trademark), RFID, ultrasound, geomagnetic, UWB signals, etc., and communication system identification information is indoor location information acquired by said indoor positioning system.For example, communication system 113 is a cellular router that has a SIM and performs cellular communication using LTE, etc., and the communication system identification information is identification information such as the ICCID that identifies the SIM, the IMSI registered in the SIM, or the IMEI registered in the SIM.

[0020] Camera 12 is an imaging device that includes an image sensor such as a CCD image sensor or a CMOS image sensor, and its imaging direction is oriented so that it captures part or all of the soundproofing space 10 in which the camera 12 is installed, but is outside the housing of the camera 12. Camera 12 connects to the internet network via a LAN such as Wi-Fi or via cellular communication and communicates data with the data management server 20. Camera 12 transmits the video data of the captured image to the data management server 20, and in turn performs control based on the data received from the data management server 20.

[0021] The microphone 13 is equipped with a microphone element such as a dynamic microphone or a condenser microphone, and is oriented so as to pick up sound from the outside of the microphone 13's housing and from within the sound reinforcement space 10 in which the microphone 13 is installed. The microphone 13 connects to the internet network via a LAN such as Wi-Fi or via cellular communication and communicates data with the data management server 20. The microphone 13 transmits the audio data of the sound it has picked up to the data management server 20, and in turn performs control based on the data received from the data management server 20.

[0022] The mobile communication terminal 15 has an OS (Operating System) and applications installed. The applications include, for example, a web browser. The mobile communication terminal 15 has a display unit including an LCD (Liquid Crystal Display) or an organic EL display. The mobile communication terminal 15 has an input unit including a keypad, keyboard, mouse, etc. The mobile communication terminal 15 may also have a touchscreen in which the display unit and input unit are integrated to display information and accept touch input operations. The mobile communication terminal 15 connects to the internet network via a LAN such as Wi-Fi or via cellular communication and communicates data with the data management server 20. The mobile communication terminal 15 transmits information about user operations received from the input unit to the data management server 20 via applications, and performs control based on data received from the data management server 20.

[0023] The data management server 20 is a web server that communicates with clients via the internet and provides web services to clients. Clients include a loudspeaker 11, a camera 12, a microphone 13, and a mobile communication terminal 15.

[0024] (Web service: Monitoring service for loudspeaker device 11) An example of a web service is a monitoring service for the loudspeaker 11. Figure 4 is a flowchart of an example of a monitoring service. The loudspeaker 11 constantly transmits information regarding the status of loudspeaker broadcasting (loudspeaker status information) to the data management server 20 via the communication system 113 at predetermined time intervals (S10). The data management server 20 receives the loudspeaker status information from the loudspeaker 11 as needed (S11), stores it (S12), and provides it to external clients (external clients) (S13). This makes it possible to visualize the loudspeaker status of the loudspeaker 11. The loudspeaker status information (first information) transmitted by the loudspeaker 11 in S11 is, as an example, setting information set in the processing system 111. For example, the loudspeaker status information may be setting information for the equalizer 111a to change the frequency characteristics of the audio signal, or volume setting information for the audio power amplifier 111b to amplify the audio signal. Furthermore, as shown in Figure 5, the loudspeaker 11 is equipped with monitoring means (sensors) to monitor the operating status of the loudspeaker 11 and the internal conditions of the loudspeaker 11, and the loudspeaker status information may include measured values ​​acquired by the sensors. As an example, as shown in Figure 5, the loudspeaker 11 is equipped with a temperature sensor 120 that continuously measures the temperature inside the loudspeaker 11, particularly the temperature of the processing system 111, at predetermined time intervals. As an example, the loudspeaker 11 is equipped with an ammeter 121 that detects the broadcast signal (audio signal) as a current value. The ammeter 121 is installed on the transmission path that transmits the broadcast signal from the input system 110 through the processing system 111 to the output system 112, and measures the current value of the broadcast signal flowing through this transmission path. An example of the ammeter 121 is a current clamp installed on the outside of the cable that transmits the broadcast signal from the input system 110 through the processing system 111 to the output system 112. In the example shown in Figure 5, the ammeter 121 is installed on the transmission path connecting the audio power amplifier 111b of the processing system 111 and the speaker 112a of the output system 112. The ammeter 121 continuously measures the current value at predetermined time intervals, and the continuous current value obtained therefrom corresponds to the waveform of the broadcast signal. In addition, the public address status information may include sound source information indicating the sound source when the public address broadcast was made.For example, the sound source information indicates which sound source within the input system 110 (for example, whether it is microphone 110a or BGM device 110b) was broadcast, that is, which sound output from which sound source was processed by the processing system 111 and output to the output system 112. For example, as shown in Figure 5, the public address system 11 is equipped with a speech-to-text unit 122 that converts the input sound from microphone 110a into text using speech recognition technology, and the text information is generated by the speech-to-text unit 122. The speech-to-text unit 122 converts the audio signal input from microphone 110a into audio data and generates a string of characters corresponding to the audio by performing speech recognition.

[0025] The data management server 20 is equipped with recording media such as HDDs and SSDs, and in S12, it stores the received public address status information on the recording media. As an example, the data management server 20 stores the public address status information received sequentially in the form of a log. Figure 6 shows an example of a log 21 held by the data management server 20. As shown in Figure 6(a), the log 21 includes a temperature log 21a, a setting information log 21b, and a broadcast log 21c. The temperature log 21a is a log of measured values ​​(temperature) received continuously from the temperature sensor 120 at predetermined time intervals. The setting information log 21b is a log of the setting information of the equalizer 111a and the audio power amplifier 111b. The broadcast log 21c is a log of the time while the public address device 11 is broadcasting public address, and is a log that includes measured values ​​output by the ammeter 121 based on the input sound of the input system 110 and character information generated by the character conversion unit 122. As shown in Figure 6(b), the temperature log 21a and the setting information log 21b may be continuously generated and stored regardless of whether the loudspeaker 11 is broadcasting loudspeaker announcements, and the broadcast log 21c may be generated and stored while loudspeaker announcements are being made.

[0026] Figures 7(a) and 7(b) show an example of a broadcast log 21c. When the loudspeaker 11 broadcasts audio input from a microphone 110a, for example, it transmits the following to the data management server 20 as loudspeaker status information: time information indicating the time from the start to the end of the broadcast, sound source type information indicating that the broadcast sound source is a microphone, character information generated by the character conversion unit 122 based on the audio input to the microphone 110a from the start to the end of the broadcast, and information on the continuous current values ​​output by the ammeter 121 from the start to the end of the broadcast. In this case, as shown in Figure 7(a), the broadcast log 21c includes the broadcast time indicated by the time information, the sound source type indicated by the sound source type information, the broadcast content indicated by the character information, and the audio waveform indicated by the continuous current values. When the loudspeaker 11 broadcasts audio played by the background music (BGM) device 110b, for example, it transmits the following information to the data management server 20 as loudspeaker status information: time information indicating the time from the start to the end of the broadcast; sound source type information indicating that the broadcast sound source is the BGM device; name information indicating the name of the sound source played by the BGM device 110b between the start and end of the broadcast (for example, the file name of the played audio file); and information on the continuous current value output by the ammeter 121 between the start and end of the broadcast. In this case, as shown in Figure 7(b), the broadcast log 21c includes the broadcast time indicated by the time information, the sound source type indicated by the sound source type information, the sound source name indicated by the name information, and the audio waveform indicated by the continuous current value.

[0027] In S13, the data management server 20 accepts access from clients via the internet and provides the client with a log 21 that can be replayed on the client side. For example, the data management server 20 generates an HTML (HyperText Markup Language) file for displaying the log 21, sends the HTML file to the client, and allows the client to open the HTML file in a browser and view the broadcast log 21c.

[0028] The loudspeaker 11 maintains location information indicating the place or location where it is installed and transmits the location information along with the loudspeaker status information to the data management server 20. The location information may be added to the loudspeaker status information and transmitted simultaneously, or it may be transmitted separately from the loudspeaker status information. The data management server 20 receives the loudspeaker status information and location information from multiple loudspeakers 11 (S11), and generates and stores a log 21 for each loudspeaker 11, associated with the location information (S12). The data management server 20 generates an HTML file that displays the location of each loudspeaker 11 as a GUI according to the location information of each loudspeaker 11, and sends the HTML file to the client (S13). An example of a GUI is shown in Figure 8, which is a GUI in which icons 22 for each loudspeaker 11 are placed at corresponding locations on a map of the area including the location of each loudspeaker 11, based on the location information of each loudspeaker 11. The data management server 20 accepts a selection operation of any icon 22 from the client and sends an HTML file to the client to display the log 21 of the loudspeaker 11 corresponding to the selected icon 22 (S13).

[0029] In addition, in S13, the data management server 20 may provide the client with an audio stream containing the audio waveform included in the broadcast log 21c, allowing the client to listen to the audio. In this case, the data management server 20 encodes the audio waveform, which is a continuous current value, to generate audio data, and generates an audio stream using a streaming protocol such as HLS (HTTP Live Streaming), DASH (Dynamic Adaptive Streaming over HTTP), or RTSP (Real Time Streaming Protocol), and sends it to the client (S13). The client plays and outputs the audio stream using an application such as a browser that supports the streaming protocol. When the data management server 20 receives a selection of the loudspeaker 11 on a GUI as shown in Figure 8, it may send the client an audio stream relating to the audio waveform included in the broadcast log 21c of the loudspeaker 11 corresponding to the selected icon 22. The audio waveform included in the broadcast log 21c is the waveform of the audio broadcast by the loudspeaker 11, and is the waveform of the audio signal that actually flowed along the transmission path from the input system 110 to the output system 112. Therefore, by playing back the audio related to this audio waveform, the client can listen to and confirm the audio that was actually amplified from the loudspeaker 11 into the amplified space 10.

[0030] As described above, the data management server 20 stores the status of the loudspeaker 11 as a log, allowing clients with access to the data management server 20 to monitor the status of the loudspeaker 11. By monitoring the status of the loudspeaker 11 in this way, the user (the operator of the loudspeaker 11) can review the various settings and operating methods of the loudspeaker 11 while observing the status, thereby providing a more favorable loudspeaker experience to listeners in the loudspeaker space.

[0031] (Web service: Measuring the effectiveness of public address broadcasts) As an example of a web service, the data management server 20 provides visualization of the effects of the loudspeaker broadcast, showing what effects resulted from the loudspeaker broadcasting within the loudspeaker space 10, in addition to monitoring the status of the loudspeaker 11. Figure 9 is a flowchart of an example of a service for visualizing the effects of the loudspeaker broadcast. The camera 12 transmits video data of the captured image to the data management server 20 (S20) during the period when listeners in the loudspeaker space 10 are expected to react to the loudspeaker broadcasting made by the loudspeaker 11 (reaction expectation period). The microphone 13 transmits audio data of the input sound to the data management server 20 (S21) during the period when listeners in the loudspeaker space 10 are expected to react to the loudspeaker broadcasting made by the loudspeaker 11 (reaction expectation period). The mobile communication terminal 15 transmits predetermined data input by the user from its input section to the data management server 20 during the period (expected response period) in which listeners in the loudspeaker space 10 are expected to respond to the loudspeaker broadcast made by the loudspeaker device 11 (S22). The data management server 20 receives video data, audio data, and predetermined data from the camera 12, microphone 13, and mobile communication terminal 15, respectively (S23), and stores this data as loudspeaker response information (S24). The data management server 20 provides the stored data to external clients (S25).

[0032] The response expectation period in S20-S22 is the period during which it is expected that listeners in the loudspeaker space 10 will respond to the loudspeaker broadcast from the loudspeaker device 11. In other words, it is the period during which it is possible to determine whether or not there are listeners responding to the loudspeaker broadcast. One example of a response expectation period is shown in Figure 10(a), which includes the loudspeaker broadcast period during which the loudspeaker device 11 is broadcasting, and extends to a certain time T1 after the loudspeaker broadcast ends. This is based on the idea that listeners will start responding some time after the loudspeaker broadcast begins, and will continue to respond for a certain period after the loudspeaker broadcast ends. Another example of a response expectation period is shown in Figure 10(b), which does not include the loudspeaker broadcast period during which the loudspeaker device 11 is broadcasting, and extends to a certain time T1 after the loudspeaker broadcast ends. This is based on the idea that listeners will start responding after the series of loudspeaker broadcasts have finished playing, and will continue to respond for a certain period.

[0033] In S20, camera 12 may continuously transmit video data of the video it is capturing to the data management server 20 at predetermined time intervals. The data management server 20 may store the video data received during the expected response time as loudspeaker response information (second information) (S24). Alternatively, camera 12 may be configured to transmit video data to the data management server 20 in response to a request from the data management server 20. In this case, when the expected response time arrives, the data management server 20 sends a request message to camera 12 requesting video, and when the expected response time ends, it sends a message to camera 12 to stop transmitting video. In response to the request message, camera 12 transmits video data of the video it is capturing during the expected response time to the data management server 20 (S20), and the data management server 20 may store the received video data as loudspeaker response information (S24).

[0034] In S21, the microphone 13 may continuously transmit audio data of the input voice to the data management server 20 at predetermined time intervals. The data management server 20 may store the audio data received during the response expectation time as amplified response information (second information) (S24). Alternatively, the microphone 13 may be configured to transmit audio data to the data management server 20 in response to a request from the data management server 20. In this case, when the response expectation time arrives, the data management server 20 sends a request message to the microphone 13 requesting audio, and when the response expectation time ends, it sends a message to the microphone 13 to stop transmitting audio. In response to the request message, the microphone 13 transmits audio data of the input voice during the response expectation time to the data management server 20 (S21), and the data management server 20 may store the received audio data as amplified response information (S24).

[0035] In S22, the mobile communication terminal 15 may continuously transmit predetermined data that the user is inputting from the input unit to the data management server 20 in response to the input. The data management server 20 may store the data it receives during the response expectation time as amplified response information (second information) (S24). Alternatively, the mobile communication terminal 15 may be configured to transmit predetermined data to the data management server 20 in response to a request from the data management server 20. In this case, when the response expectation time arrives, the data management server 20 sends a request message to the mobile communication terminal 15 requesting predetermined data, and when the response expectation time ends, it sends a message to the mobile communication terminal 15 to stop transmitting data. In response to the request message, the mobile communication terminal 15 transmits predetermined data that the user is inputting from the input unit within the response expectation time to the data management server 20 (S22), and the data management server 20 may store the received data as amplified response information (S24).

[0036] In S22, an example of predetermined data transmitted by the mobile communication terminal 15 is character data entered through an application on the mobile communication terminal 15. For example, the mobile communication terminal 15 may have a browser application for performing web searches and displaying desired web pages, and the character data may be character data of characters entered through the input field for web searches via the browser. For example, the mobile communication terminal 15 may have an application for SNS (Social Networking Service), and the character data may be character data of characters entered through the input field for SNS posting via the application.

[0037] In S24, the data management server 20 may store public address response information for each public address device 11 in association with the log 21 stored for each public address device 11 (S24). In particular, since the public address response information among the log 21 is information regarding the response to the public address broadcast, it may be stored in association with the broadcast log 21c related to the public address broadcast (S24). In this case, the data management server 20 stores the broadcast log 21c generated within the public address broadcast period of a certain public address device 11 in association with the public address response information of the same public address device 11 within the response expectation time corresponding to the public address broadcast period (S24). For example, in the example shown in Figure 10(a), when a certain public address device 11 starts a public address broadcast and enters the public address broadcast period, the data management server 20 sets the start of the response expectation time to be after a predetermined time has elapsed from the start of the public address broadcast, and sets the end of the response expectation time to be after time T1 has elapsed after the public address device 11 ends the public address broadcast and the public address broadcast period ends. The data management server 20 receives time information, sound source type information, character information, sound source name information, audio waveform information, etc. from the loudspeaker device 11 during the loudspeaker broadcast period (S11) and generates a broadcast log 21c (S12). It also receives various data from the camera 12, microphone 13, and mobile communication terminal 15 in the loudspeaker space 10 where the loudspeaker device 11 is located during the expected response time (S23) and generates loudspeaker response information, which is associated with the broadcast log 21c (S24). For example, in the example shown in Figure 10(b), when a loudspeaker device 11 broadcasts loudspeaker information and the loudspeaker broadcast period ends, the data management server 20 sets an expected response time that starts at a time T1 elapsed from the end of the loudspeaker broadcast. The data management server 20 receives time information, sound source type information, character information, sound source name information, audio waveform information, etc. from the loudspeaker device 11 during the loudspeaker broadcast period (S11) and generates a broadcast log 21c (S12). It also receives various data from the camera 12, microphone 13, and mobile communication terminal 15 in the loudspeaker space 10 where the loudspeaker device 11 is located within the expected response time (S23) and generates loudspeaker response information, which is then associated with the broadcast log 21c (S24).

[0038] The data management server 20 manages the loudspeaker 11, camera 12, microphone 13, and mobile communication terminal 15 located within the same loudspeaker space 10. For example, as shown in Figure 11, each loudspeaker space 10 maintains a database 23 that manages the loudspeaker 11, camera 12, microphone 13, and mobile communication terminal 15 located within that space. In the example shown in Figure 11, the database 23 indicates that the loudspeaker space 10-1 contains one loudspeaker 11 (11-1), two cameras 12 (12-1, 12-2), one microphone 13 (13-1), and three mobile communication terminals 15 (15-1, 15-2, 15-3), while the loudspeaker space 10-2 contains two loudspeakers 11 (11-3, 11-4), one camera 12 (12-3), two microphones 13 (13-3, 13-4), and two mobile communication terminals 15 (15-4, 15-5). The data management server 20 may generate the database 23 according to the location information of each loudspeaker 11, each camera 12, each microphone 13, and each mobile communication terminal 15. For example, when forming a public address space 10 using a LAN, in other words, when a public address space 10 is defined as an area where one or more public address devices 11 connected to a single LAN broadcast public address information, the public address devices 11, camera 12, microphone 13, and mobile communication terminal 15 connected to the same LAN are registered in the database 23 as existing in the same public address space 10. For example, for each LAN router identifier (e.g., IP address), the public address devices 11, camera 12, microphone 13, and mobile communication terminal 15 connected to LAN routers with the same identifier are registered in the database 23 as existing in the same public address space 10. Alternatively, as explained with reference to Figure 3, if the communication system 113 is independent of the public address device 11, the camera 12, microphone 13, and mobile communication terminal 15 are also connected to the communication system 113, as shown in Figure 12, and all of the public address devices 11, camera 12, microphone 13, and mobile communication terminal 15 communicate with the data management server 20 via the communication system 113.In this case, the data management server 20 registers in the database 23, for each communication system identification information (e.g., ICCID, IMSI, IMEI, etc.) of the communication system 113, the loudspeaker 11, camera 12, microphone 13, and mobile communication terminal 15 connected to the communication system 113 having the same identification information, as existing in the same loudspeaker space 10. Furthermore, for example, the loudspeaker 11, camera 12, microphone 13, and mobile communication terminal 15 are configured to acquire their own location information using GNSS or an indoor positioning system, etc., and transmit it to the data management server 20. The data management server 20 then refers to the received location information and registers in the database 23, as existing in the same loudspeaker space 10, the loudspeaker 11, camera 12, microphone 13, and mobile communication terminal 15 having the same or similar location information within a predetermined range.

[0039] In S24 described above, the data management server 20 refers to the database 23 to identify the camera 12, microphone 13, and mobile communication terminal 15 located in the same sound reinforcement space 10 as the sound reinforcement device 11, which is the source of time information, sound source type information, character information, sound source name information, and audio waveform information. The server receives various data from the camera 12, microphone 13, and mobile communication terminal 15 and generates sound reinforcement response information corresponding to the broadcast log 21c.

[0040] In S25, the data management server 20 accepts access from a client via the Internet network and provides the client with loudspeaker response information that can be replayed on the client side (S25). For example, the data management server 20 generates an HTML file for displaying the loudspeaker response information, sends the HTML file to the client, and allows the client to open the HTML file in a browser and display the loudspeaker response information (S25). In S25, the data management server 20 may also generate an HTML file for displaying the broadcast log 21c and the loudspeaker response information corresponding to the broadcast log 21c, and send it to the client, so that the client can check the status of the loudspeaker broadcast and the listener's response to the loudspeaker broadcast. When the data management server 20 accepts the selection of a loudspeaker 11 on a GUI as shown in Figure 8, it is preferable to generate an HTML file for displaying the broadcast log 21c of the loudspeaker 11 corresponding to the selected icon 22 and the loudspeaker response information corresponding to the broadcast log 21c, and send it to the client.

[0041] As described above, the data management server 20 measures the effectiveness of the public address broadcasts made by the public address system 11, allowing clients with access to the data management server 20 to verify the effectiveness of the public address broadcasts made by the public address system 11. By measuring the effectiveness of the public address broadcasts in this way, users (the operators of the public address system 11) can evaluate the effectiveness and improve various settings and operating methods of the public address system 11, thereby providing listeners in the broadcast space with a more favorable public address experience.

[0042] (Web service: Suggestions for improving public address systems) As an example of a web service, the data management server 20 provides improvement suggestions for public address broadcasting for each public address device 11 (each public address space 10) based on log 21 (first information) and public address response information (second information). Figure 13 is a flowchart of an example of a service that provides improvement suggestions for public address devices 11 (public address space 10). The data management server 20 statistically processes the accumulated (S12, S24) log 21 and public address response information (S30) and creates improvement suggestions that lead to improvements in public address broadcasting (S31). The data management server 20 provides the created improvement suggestions to the client (S32).

[0043] As an example of statistical processing in S30, the data management server 20 statistically processes the time-series accumulated logs 21 and creates suggestions for improving the operation of the public address system 11. For example, it statistically processes the temperature log 21a to identify periods when the temperature remains high for a predetermined period of time, and creates suggestions for improvement, such as strengthening the air conditioning in the public address space 10 during these periods. For example, if it statistically processes the setting information log 21b and finds that the frequency setting of the equalizer 111a or the volume setting of the audio power amplifier 111b is inappropriate, it creates suggestions for improvement, such as prompting the user to set the appropriate frequency and volume.

[0044] As an example of statistical processing in S30, the data management server 20 statistically processes the relationships between at least two of the temperature log 21a, the configuration information log 21b, and the broadcast log 21c, and creates suggestions to improve the operation of the public address system 11 based on the relationships between multiple elements. For example, from the temperature log 21a and the configuration information log 21b, it identifies the time periods when the volume setting should be lowered based on the relationship between temperature and the volume setting of the audio power amplifier 111b, and creates improvement suggestions to encourage adjustment of the volume setting.

[0045] In S30, the data management server 20 processes the public address response information, determines whether or not the corresponding public address broadcast was effective and to what extent, and creates a proposal to improve the operation of the public address system 11 based on the effectiveness of the public address broadcast. For example, it statistically processes the video data captured by the camera 12 included in the public address response information to identify the actions taken by listeners in the public address space 10 after the public address broadcast and determines the effectiveness of the public address broadcast. For example, if the corresponding public address broadcast was a broadcast that encouraged listeners to move (for example, an evacuation guidance broadcast during a disaster), and the statistical processing of the video data identifies that multiple listeners began to move in one direction after the public address broadcast, it can be determined that the public address broadcast was effective (highly effective). For example, if the corresponding public address broadcast was an advertisement broadcast promoting a specific product within the public address space 10, which is a store such as a supermarket, and the statistical processing of the video data identifies that listeners began to move to the sales area for that product after the public address broadcast, it can be determined that the public address broadcast was effective (highly effective). Furthermore, for example, the system statistically processes the sound data picked up by the microphone 13 included in the public address response information to identify conversations conducted by listeners in the public address space 10 after the public address broadcast, and determines the effectiveness of the public address broadcast. For example, if the corresponding public address broadcast was an advertisement promoting a specific product, and the statistical processing of the sound data identifies that listeners were having a conversation about the product after the public address broadcast, it can be determined that the public address method was effective (highly effective). In addition, for example, the system statistically processes the text data (text data entered through the application of the mobile communication terminal 15) included in the public address response information to identify the content of web searches and SNS posts conducted by listeners in the public address space 10 after the public address broadcast, and determines the effectiveness of the public address broadcast. For example, if the corresponding public address broadcast was an advertisement promoting a specific product, and the statistical processing of the sound data identifies that listeners were conducting web searches or SNS posts about the product after the public address broadcast, it can be determined that the public address method was effective (highly effective). In S31, if the data management server 20 determines in S30 that the public address broadcasting effect was low, it creates improvement suggestions to review the sound source to be amplified, the volume settings, and the frequency settings of the equalizer 111a.

[0046] As an example of statistical processing in S30, the data management server 20 processes the public address response information as described above to determine the presence and degree of the effect of the public address broadcast, and refers to the log 21 corresponding to the public address broadcast to create a proposal to improve the operation of the public address system 11 based on the relationship between the effect of the public address broadcast and the log 21. For example, by referring to the setting information log 21b, it identifies the relationship between the volume setting of the audio power amplifier 111b and the frequency setting of the equalizer 111a and the effect of the public address broadcast (for example, the volume setting and frequency setting when the effect of the public address broadcast was high), and creates an improvement proposal that recommends the volume setting and frequency setting when the effect of the public address broadcast was high (S31).

[0047] In S30, the data management server 20 processes the public address response information and the corresponding log 21, determines the effectiveness of the public address broadcast based on the relationship between multiple elements contained in both (S30), and creates a proposal to improve the operation of the public address device 11 based on the effectiveness of the public address broadcast. For example, it processes the broadcast log 21c and the video data captured by the camera 12 included in the public address response information, identifies the broadcast content contained in the broadcast log 21c and the actions taken by listeners in the public address space 10 after the public address broadcast, and determines the effectiveness of the public address broadcast based on the relationship between the two (S30). In this case, for example, first the broadcast content (text data) of the broadcast log 21c is analyzed to estimate the intent of the public address broadcast (the action that the public address broadcast wants to encourage listeners to take), and then the video data is analyzed to determine whether multiple listeners acted according to the intent of the public address broadcast after the public address broadcast (whether they took the action that the public address broadcast wanted listeners to take), thereby determining the effectiveness of the public address broadcast. That is, if multiple listeners act according to the intent of the public address broadcast after the public address broadcast, it can be determined that the effectiveness of the public address broadcast is high. For example, if, as a result of analyzing the broadcast content of broadcast log 21c, characters indicating a location (e.g., building exit) can be recognized and it is estimated that the broadcast is encouraging movement to that location (e.g., evacuation guidance broadcast), then the captured video data is analyzed to determine whether the listener has moved toward that location (S30). For example, if, as a result of analyzing the broadcast content of broadcast log 21c, characters indicating staying in that location (e.g., "Please wait," "Please do not move," etc.) can be recognized and it is estimated that the broadcast is encouraging not to move, then the captured video data is analyzed to determine whether the listener has stayed in that location (S30). For example, if the loudspeaker broadcast is an advertisement broadcast promoting a specific product within a loudspeaker space 10, such as a supermarket, then the broadcast content of broadcast log 21c can be analyzed to estimate the name of the advertised product, and then the captured video data is analyzed to determine whether the listener has started moving toward the sales area for that product (S30). In S31, if the data management server 20 determines in S30 that the public address system is ineffective, it creates an improvement suggestion to review the content of the public address system (what the speaker says into the microphone 110a).

[0048] In S30, the data management server 20 processes the loudspeaker response information and the corresponding log 21, determines the loudspeaker broadcast effect based on the relationship between multiple elements contained in both (S30), and creates a proposal to improve the operation of the loudspeaker device 11 based on the loudspeaker broadcast effect. For example, it processes the broadcast log 21c and the sound data picked up by the microphone 13 contained in the loudspeaker response information, identifies the broadcast content contained in the broadcast log 21c and the content of conversations made by listeners in the loudspeaker space 10 after the loudspeaker broadcast, and determines the loudspeaker broadcast effect based on the relationship between the two (S30). In this case, for example, first the broadcast content (text data) of the broadcast log 21c is analyzed to estimate the intent of the loudspeaker broadcast (the message to be conveyed by the loudspeaker broadcast), and then the sound data is analyzed to determine the content of conversations made by listeners after the loudspeaker broadcast, thereby determining the loudspeaker broadcast effect. That is, if multiple listeners converse in accordance with the intent of the loudspeaker broadcast after the loudspeaker broadcast, it can be determined that the loudspeaker broadcast effect is high. For example, if the loudspeaker broadcast is an advertisement for a specific product broadcast within a loudspeaker space 10, such as a supermarket, the broadcast content of the broadcast log 21c is analyzed to estimate the name of the advertised product. Next, the sound data collected in the loudspeaker response information is analyzed to determine whether or not the listener used the product name in conversation (S30). In S31, if the loudspeaker broadcast effect determined in S30 was low, the data management server 20 creates an improvement suggestion to review the content of the loudspeaker broadcast (what the speaker says into the microphone 110a).

[0049] In S30, the data management server 20 processes the public address response information and the corresponding log 21, determines the effectiveness of the public address broadcast based on the relationship between multiple elements contained in both (S30), and creates a proposal to improve the operation of the public address device 11 based on the effectiveness of the public address broadcast. For example, it processes the broadcast log 21c and the text data contained in the public address response information (text such as web searches and SNS posts made on the mobile communication terminal 15), identifies the broadcast content contained in the broadcast log 21c and the actions taken by listeners in the public address space 10 after the public address broadcast, and determines the effectiveness of the public address broadcast based on the relationship between the two (S30). In this case, for example, first the broadcast content (text data) of the broadcast log 21c is analyzed to estimate the intent of the public address broadcast (the message to be conveyed by the public address broadcast), and then the text data is analyzed to determine the content of web searches and SNS posts made by listeners via the mobile communication terminal 15 after the public address broadcast, thereby determining the effectiveness of the public address broadcast. That is, if multiple listeners perform web searches or SNS posts as intended by the public address broadcast after the public address broadcast, it can be determined that the effectiveness of the public address broadcast is high. For example, if the loudspeaker broadcast is an advertisement for a specific product broadcast within a loudspeaker space 10, such as a supermarket, the broadcast content of the broadcast log 21c is analyzed to estimate the name of the advertised product. Next, the text data included in the loudspeaker response information is analyzed to determine whether the listener used the product name in a web search or SNS post (S30). In S31, if the loudspeaker broadcast effectiveness determined in S30 was low, the data management server 20 creates an improvement suggestion to review the content of the loudspeaker broadcast (what the speaker says into the microphone 110a).

[0050] The improvement suggestion includes text, images, etc., describing the improvement. In S32, the data management server 20 receives access from the client via the internet and provides the client with the improvement suggestion in a format that can be reproduced on the client side. For example, the data management server 20 generates an HTML file for displaying the improvement suggestion, sends the HTML file to the client, and allows the client to open the HTML file in a browser and view the improvement suggestion. When the data management server 20 receives a selection of the loudspeaker 11 on a GUI as shown in Figure 8, it may generate an HTML file for displaying the improvement suggestion for the loudspeaker 11 corresponding to the selected icon 22 and send it to the client.

[0051] As described above, the data management server 20 creates improvement suggestions regarding the settings and operation of the loudspeaker 11, and clients that can access the data management server 20 can review these improvement suggestions. In this way, by making improvement suggestions for loudspeaker broadcasting, users (operators of the loudspeaker 11) can improve various settings and operating methods of the loudspeaker 11 based on the suggestions, thereby providing listeners in the loudspeaker space with a more favorable loudspeaker experience.

[0052] (Web service: Anomaly detection in public address systems) An example of a web service is an anomaly detection service for the public address system 11. Figure 14 is a flowchart of an example of an anomaly detection service. The public address system 11 constantly determines at predetermined time intervals whether the input system 110, processing system 111, and output system 112 are operating normally (S40), and transmits the determination result to the data management server 20 via the communication system 113 (S41). The data management server 20 receives the determination result from the public address system 11 (S42), stores the determination result (S43), and provides it to external clients (S44). This makes it possible to visualize whether the public address system 11 is operating normally or if an anomaly has occurred.

[0053] As shown in Figure 15, the loudspeaker 11 includes a determination unit 114. The determination unit 114 is connected to the input system 110, the processing system 111, and the output system 112, and monitors the operating status of each system 110 to 112 at predetermined time intervals to determine whether or not they are operating normally (S40). For example, the determination unit 114 includes a temperature sensor that measures temperature at predetermined time intervals, and measures the temperature of the input system 110, the processing system 111, and the output system 112, and determines whether or not the temperature is normal for each system (S40). For example, if the measured temperature value is within a predetermined temperature range, it may be determined to be normal, and if it is outside the predetermined temperature range, it may be determined to be abnormal. For example, the determination unit 114 includes a current sensor that measures current, and measures the current flowing on the electrical circuit boards (electronic circuit boards) of the input system 110, the processing system 111, and the output system 112, and determines whether or not each system is operating normally (S40). For example, if the measured current value falls within a predetermined range, it can be determined to be normal; if it falls outside this range, it can be determined to be abnormal.

[0054] In S41, the loudspeaker 11 transmits the system-specific judgment result determined by the judgment unit 114 to the data management server 20. The judgment result includes information indicating whether each system is normal or abnormal.

[0055] In S44, the data management server 20 accepts access from clients via the internet and provides the clients with the received judgment results in a format that can be replayed on the client side. For example, the data management server 20 generates an HTML file to display the judgment results, sends the HTML file to the client, and allows the client to open the HTML file in a browser and view the judgment results.

[0056] As described above, the data management server 20 collects judgment results indicating whether the loudspeaker 11 is operating normally, and these judgment results can be confirmed through clients that can access the data management server 20. Based on the judgment results, the user (the operator of the loudspeaker 11) can repair or replace the loudspeaker 11, improving maintainability and providing a more favorable public address experience from the loudspeaker 11.

[0057] (Web service: Personalized broadcasting) One example of a web service is a service that provides personalized broadcasts optimized for users 14 within a public address space 10 from a public address system 11. In this example, users 14 can use a mobile communication terminal 15 to select sound sources to be broadcast from the public address system 11 and configure settings (volume, etc.) for the broadcast. Based on these selections and settings, the data management server 20 issues broadcasting instructions to the public address system 11. As shown in Figure 16, in this example, the data management server 20 maintains multiple sound sources 25 and a history 26. Each of the multiple sound sources 25 is a sound source that the public address system 11 can play and broadcast. Each sound source 25 is, for example, audio data related to a song or background music, and is audio data generated in a file format such as MP3 (MPEG Audio Layer 3) or AAC (Advanced Audio Coding). History 26 contains information including the history of settings (volume settings, etc.) and sound source selections for broadcasting from the loudspeaker 11, and includes the history for each user 14 who made such settings or selections.

[0058] Figure 17 shows an example of history 26. History 26 includes past history of user 14 accessing the data management server 20 using mobile communication terminal 15 and selecting sound sources 25 from the mobile communication terminal 15, as well as past history of setting amplification settings such as volume from the mobile communication terminal 15. History 26 records the history of sound source 25 selection and amplification settings such as volume performed from the mobile communication terminal 15 for each identification information of the mobile communication terminal 15 (user 14) that accessed the data management server 20 to select sound sources 25 or set amplification settings such as volume (for example, IP address, ICCID, IMSI, IMEI if the mobile communication terminal 15 has a SIM, or the ID used to log in to the data management server 20). In history 26, each time a sound source 25 is selected or amplification settings such as volume are set, the history of that selection or setting is recorded in association with the date and time it was performed. In the example shown in Figure 17, history 26 includes the history of sound source 25 selection and the history of volume settings. For example, history entry 26 shows that at 9:10 AM on March 1st, music 001 (sound source 25) was selected, and the volume for broadcasting music 001 was set to 31 dB.

[0059] Figure 18 is a flowchart illustrating an example of the operation flow for performing personalized broadcasting in this example. The data management server 20 accepts access from a client via the internet (S50, S51). In S50, the client transmits identification information that identifies the mobile communication terminal 15 (user 14), such as IP address, ICCID, IMSI, IMEI, and login ID (S50), and the data management server 20 authenticates the received identification information and accepts access (S51). The data management server 20 refers to the history 26 and determines whether there is a history associated with the identification information of the mobile communication terminal 15 (user 14) authenticated in S51 (S52). If there is a history (S52: Yes), the data management server 20 selects a sound source 25 and amplification settings such as volume based on that history, and instructs the amplification device 11 to play the selected sound source 25 with the selected amplification settings (S53). In S53, the data management server 20 transmits the selected sound source 25 (voice data) to the loudspeaker 11 and also transmits a setting message indicating the selected loudspeaker setting. In S53, based on one or more history entries, the data management server 20 estimates the sound source 25 that user 14 is most likely to want to play from the loudspeaker 11 at the time the mobile communication terminal 15 accessed the data management server 20 in S50, estimates the loudspeaker setting that user 14 is most likely to want to set, and selects these. Specifically, for example, the data management server 20 may refer to one or more history entries and select the sound source 25 that has been played most often in the past and the loudspeaker setting that has been set most often. Alternatively, for example, the data management server 20 may select the sound source 25 that was played most often and the loudspeaker setting that was set at the time closest to the time the access was received in S51, or select the sound source 25 that was played most often and the loudspeaker setting that was set most often during the time period in which the access was received in S51. As a result, the optimal sound source 25 and amplification settings are automatically selected, and the sound source 25 is played back from the amplification device 11 with those amplification settings and broadcast amplified.

[0060] If there is no history in history 26 (S52: No), the data management server 20 accepts the selection of sound source 25 and the specification of amplification settings entered by the client (S54) (S55). The data management server 20 provides the client with a UI for inputting the selection of sound source 25 and the specification of amplification settings, and accepts the selection of sound source 25 and the specification of amplification settings entered through the UI (S55). For example, the data management server 20 generates an HTML file to display the UI, sends the HTML file to the client, and enables the client to open the HTML file in a browser and display the UI.

[0061] The data management server 20 reads the sound source 25 selected in S55 (S56) and instructs the loudspeaker 11 to play the sound source 25 with the loudspeaker settings selected in S56 (S57). In S57, the data management server 20 transmits the sound source 25 read in S56 to the loudspeaker 11, along with a setting message indicating the loudspeaker settings selected in S55. The data management server 20 records the selection of the sound source 25 and the selection of the loudspeaker settings received in S55 as a new history in the history 26, associating it with time information indicating the time of reception in S55 (S61).

[0062] The public address system 11 receives the sound source 25 and a setting message transmitted from the data management server 20 in S53 or S57 (S58). The public address system 11 holds the received sound source 25 and sets the input system 110, processing system 111, or output system 112 according to the received setting message (S59). For example, if the setting message indicates a volume setting, the public address system 11 adjusts the volume of the audio power amplifier 111b of the processing system 111 according to the volume setting indicated in the setting message (S59). The public address system 11 plays the sound source 25 that was received and held in S58 and broadcasts an announcement (S60).

[0063] As described above, the data management server 20 records a history of what kind of sound reinforcement experiences user 14 has preferred in the past, and this history can be used to automatically provide the optimal sound reinforcement experience for each user 14.

[0064] (Web service: Sounding device 11 sound check) One example of a web service is an inspection service that checks whether the loudspeaker 11 is functioning correctly. In other words, if a malfunction occurs in the input system 110, processing system 111, or output system 112 of the loudspeaker 11, loudspeaker broadcasts may not be able to be made when desired (or even when intended to be made), which poses an operational problem for the loudspeaker 11. In particular, if highly public loudspeaker broadcasts, such as evacuation guidance broadcasts during disasters, cannot be made correctly, it can be dangerous and endanger human lives. For this reason, the data management server 20 checks whether the loudspeaker 11 is functioning correctly, either periodically or irregularly. In this example, as shown in Figure 19, the data management server 20 holds an inspection sound source 27. The inspection sound source 27 is audio data prepared for the purpose of inspecting the loudspeaker 11, and is, for example, audio data related to speech that lasts for several seconds.

[0065] Figure 20 is a flowchart showing an example of the operation flow related to the inspection service of the loudspeaker 11. The data management server 20 instructs the loudspeaker 11 to perform a test broadcast in order to inspect the loudspeaker 11 (S70). For example, the data management server 20 may maintain a schedule for inspections in advance and execute S70 according to that schedule. For example, the data management server 20 may execute S70 periodically (for example, once a month, on the first day of each month). For example, the data management server 20 may execute S70 irregularly, during times when the loudspeaker 11 is not broadcasting. In S70, the data management server 20 transmits an inspection sound source 27 to the loudspeaker 11 and sends a message instructing it to perform a test broadcast.

[0066] When the loudspeaker 11 receives the inspection sound source 27 and a message (S71), it responds by making a test public address broadcast (S72). In S72, the loudspeaker 11 holds the received inspection sound source 27 and plays the inspection sound source 27 to make a public address broadcast.

[0067] In S70, the data management server 20 instructs the loudspeaker 11 to perform a test public address, and in parallel, instructs the microphone 30 located in the same public address space 10 as the loudspeaker 11 to pick up sound (S73). In S73, the data management server 20 refers to the database 23 to identify the microphone 30 located in the same public address space 10 as the loudspeaker 11 instructed in S70, and sends a sound pickup instruction to the microphone 30. In S73, the data management server 20 sends a message to the microphone 30 instructing it to pick up sound. For example, the data management server 20 may execute S70 and S73 simultaneously. For example, the data management server 20 may execute S73 after a predetermined time (for example, a few seconds) that takes into account the time lag between executing S70 and the loudspeaker 11 starting the public address broadcast.

[0068] When the microphone 30 receives a message instructing it to pick up sound (S74), it starts picking up sound, generates audio data of the picked-up voice, and transmits it to the data management server 20 (S75). In S75, the microphone 30 may continue picking up sound for a predetermined time after receiving the message in S74, generate audio data of the voice picked up during this time and transmit it to the data management server 20, and then automatically terminate the sound pickup.

[0069] After executing S73, the data management server 20 waits for the reception of audio data of the sound picked up from the microphone 30. When the data management server 20 receives the audio data of the sound picked up from the microphone 30, it checks the loudspeaker 11 based on the audio data (S76). For example, in S76, the data management server 20 determines that the loudspeaker 11 is normal because it was able to receive the audio data in S76, and determines that the loudspeaker 11 is abnormal if it is not able to receive the audio data even after waiting for a predetermined time. For example, in S76, the data management server 20 compares the received audio data with the inspection sound source 27 and determines whether the loudspeaker 11 is normal or abnormal according to the degree of agreement. For example, if the received audio data and the inspection sound source 27 match within a predetermined range, it may be determined that it is normal, and if they do not match within a predetermined range, it may be determined that it is abnormal. For example, the received audio data can be played back to obtain an audio signal (audio waveform), which can then be compared with the audio signal related to the audio data of the inspection sound source 27. If the two signals match within a predetermined range, it can be determined that the system is normal; if they do not match within a predetermined range, it can be determined that the system is abnormal.

[0070] The data management server 20 stores the judgment results (inspection results) from S76 (S77) and provides them to the client (S78). In S78, the data management server 20 accepts access from the client via the internet and provides the client with the inspection results in a format that can be replayed on the client side. For example, the data management server 20 generates an HTML file to display the inspection results, sends the HTML file to the client, and allows the client to open the HTML file in a browser and view the inspection results.

[0071] As described above, the data management server 20 inspects the loudspeaker 11, and the results of the inspection can be confirmed through clients that can access the data management server 20. Based on the inspection results, the user (the operator of the loudspeaker 11) can repair or replace the loudspeaker 11, improving maintainability and providing a more favorable public address experience from the loudspeaker 11.

[0072] (complex monitoring) A modified version of the public address system 1 will be described with reference to Figure 21. In addition to the public address device 11 and the data management server 20, the public address system 1 may also include an operation monitoring device 130. The public address system 1 may further include a monitoring information terminal 140. The monitoring information terminal 140 is connected to the operation monitoring device 130 via a local area network 131.

[0073] The operation monitoring device 130 monitors the loudspeaker 11 without using the Internet network. The operation monitoring device 130 may monitor the loudspeaker 11 directly, or it may monitor the loudspeaker 11 via the local area network 131. The operation monitoring device 130 individually monitors some of the components of the loudspeaker 11. For example, the operation monitoring device 130 monitors the input system 110 and the processing system 111 as monitored devices 132.

[0074] The operation monitoring device 130 performs a first monitoring by acquiring information via the local area network 131, and a second monitoring via contacts that do not go through the local area network 131. In the second monitoring, the operation monitoring device 130 monitors the contacts of the input system 110 or the contacts of the processing system 111. The input system 110 and the processing system 111 have contacts. The contacts are configured, for example, by relay switches.

[0075] For example, the input system 110 and processing system 111 respond to a predetermined abnormality occurring inside the device by outputting a contact signal to notify the system of the abnormality. In the first example, the predetermined abnormality is a temperature abnormality inside the device. For example, the input system 110 and processing system 111 periodically monitor the temperature inside the device, and when the temperature exceeds a predetermined level, they output a contact signal indicating a temperature abnormality. In the second example, the predetermined abnormality in the input system 110 is a sound source data reading error. For example, when attempting to read specific sound source data for sound source playback, if the sound source file is corrupted or otherwise unreadable, they output a contact signal indicating a reading error. In the third example, the predetermined abnormality in the processing system 111 is a current consumption abnormality of the audio power amplifier 111b. For example, the processing system 111 periodically monitors the current consumption value of the audio power amplifier 111b, and when it exceeds a predetermined current value range, it outputs a contact signal indicating a current consumption abnormality.

[0076] The contact output is configured as follows: When the input system 110 and the processing system 111 have relay switches as contacts, the relay switches are normally kept in the open state (break), and in the event of an abnormality, the relay switches are changed to the closed state (make). The operation monitoring device 130 monitors whether the relay switches are in the open state or not, and based on this monitoring, it determines whether there is an abnormality in the input system 110 and the processing system 111. The contact output configuration may be the reverse. Specifically, when the input system 110 and the processing system 111 have relay switches as contacts, the relay switches are normally kept in the closed state (make), and in the event of an abnormality, the relay switches are changed to the open state (break). The operation monitoring device 130 monitors whether the relay switches are in the closed state or not, and based on this monitoring, it determines whether there is an abnormality in the input system 110 and the processing system 111.

[0077] The operation monitoring device 130 has contact inputs that receive the contact state of the input system 110 or the processing system 111. For example, a relay switch of the input system 110 or the processing system 111 is connected to the contact input of the operation monitoring device 130 via a cable. The operation monitoring device 130 detects when the relay switch transitions from an open state to a closed state, and when it transitions from a closed state to an open state. For example, the operation monitoring device 130 has multiple ports as contact inputs. Each of the multiple ports is connected to an individual contact of the monitored device 132 (equipment of the input system 110 or the processing system 111). The operation monitoring device 130 monitors the contacts connected to the ports.

[0078] The operation monitoring device 130 stores the network address of the monitored device 132 in order to communicate with the monitored device 132 via the local area network 131. The network address is used in the first monitoring.

[0079] The operation monitoring device 130 has multiple ports for direct control of the monitored device 132 via the communication cable 133. These multiple ports are connected to contacts within the operation monitoring device 130. The multiple ports are identified by their port numbers. These multiple ports are used in the second monitoring stage.

[0080] The operation monitoring device 130 stores the monitored device 132, the network address of the monitored device 132, and the port number of the port to which the monitored device 132 is connected, associating them with each other.

[0081] For example, as shown in Figure 22, the operation monitoring device 130 has a table that associates the network address of the monitored device 132 with the port number of the port to which the monitored device 132 is connected. The table is stored in the memory unit of the operation monitoring device 130. In the example in Figure 22, port number 1 to which the contacts of the input system 110 are connected as the monitored device 132 is associated with the unique network address of the input system 110 (for example, an IP address). Also, port number 2 to which the contacts of the processing system 111 are connected as the monitored device 132 is associated with the unique network address of the processing system 111 (for example, an IP address).

[0082] The operation monitoring device 130, in its first monitoring phase, monitors the monitored device 132 via the local area network 131 using a Ping command defined by TCP / IP. For example, the operation monitoring device 130 monitors network-related anomalies using a Ping command. In its second monitoring phase, the operation monitoring device 130 directly monitors the operation of the monitored device 132 for hardware-related anomalies unrelated to the network.

[0083] The operation monitoring device 130 refers to a table and performs complex monitoring by using both the first and second monitoring for each monitored device 132. The operation monitoring device 130 periodically performs the first and second monitoring for each monitored device 132. This allows the operation monitoring device 130 to differentiate and monitor whether an abnormality has occurred for each monitored device 132 due to network causes or an abnormality specific to the device that is not due to network causes. When the operation monitoring device 130 performs the first and second monitoring, the monitoring of the loudspeaker 11 by the Web service using the data management server 20 described above may be performed only when an abnormality is detected in the first or second monitoring.

[0084] The operation monitoring device 130 may perform a third or fourth monitoring. As the third monitoring, the operation monitoring device 130 monitors the monitored device 132 based on the output signals output from the monitored device 132. Examples of output signals include signals output from the input system 110 to the processing system 111, and signals sent from the processing system 111 to the output system 112. The signals output from the input system 110 to the processing system 111 include audio signals between a sound source device such as a CD player (input system 110) and a power amplifier (processing system 111). In the third monitoring, the operation monitoring device 130 determines abnormalities in the waveform of the signals output from the input system 110 to the processing system 111, and abnormalities in the waveform of the signals sent from the processing system 111 to the output system 112. The operation monitoring device 130 may perform the third monitoring periodically. The operation monitoring device 130 may perform the third monitoring only while an audio signal is output from the input system 110 to the processing system 111 during a public address broadcast, and while an audio signal is output from the processing system 111 to the output system 112. For example, the operation monitoring device 130 monitors the audio signal between a sound source device such as a CD player (input system 110) and a power amplifier (processing system 111).

[0085] As a fourth monitoring step, the operation monitoring device 130 monitors the monitored device 132 based on the audio output from the output system 112. Specifically, the operation monitoring device 130 inspects the monitored device 132 by performing operations similar to the inspection service for the public address system 11 described above. For example, the monitored device 132 has the public address system 11 play test audio data and simultaneously picks up sound with the microphone 30. The operation monitoring device 130 then acquires audio data related to the audio from the microphone 30 and checks the output status of the monitored device 132 by comparing the audio data related to the audio with the test audio data. The microphone 30 may be connected to the operation monitoring device 130 via the local area network 131, or it may be connected directly to the operation monitoring device 130 via a phone cable or XLR cable. The audio data acquired by the microphone 30 may be an analog signal or a digital signal. If the audio data is a digital signal, the audio data is transmitted from the microphone 30 to the operation monitoring device 130 via the local area network 131. If the audio data is an analog signal, the audio data is transmitted to the operation monitoring device 130 via a cable.

[0086] The operation monitoring device 130 may periodically perform the fourth monitoring. The operation monitoring device 130 may also perform the fourth monitoring only while a loudspeaker broadcast is being made and an audio signal is being output from the processing system 111 to the output system 112.

[0087] The operation monitoring device 130 may perform a fifth monitoring. As the fifth monitoring, the operation monitoring device 130 acquires configuration information or operation information from within the monitored device 132 via the local area network 131. The fifth monitoring is different from the first monitoring. The fifth monitoring is not network monitoring using commands defined in general-purpose TCP / IP. The fifth monitoring is a monitoring in which the operation monitoring device 130 sends commands requesting configuration information and operation information according to a proprietary protocol predetermined between the operation monitoring device 130 and the monitored device 132, and the monitored device 132 responds by sending back configuration information and operation information from within its own device. An example of a command according to the proprietary protocol is a command that includes a combination of a predetermined method (e.g., GET method or POST method) defined in the HTTP protocol and a variable. An example of configuration information for the monitored device 132 is, for example, the volume setting in the input system 110, the schedule setting for playing the sound source, the volume setting in the processing system 111, the equalizer frequency setting, etc. Examples of operational information for the monitored device 132 include temperature information from the input system 110 and processing system 111, broadcast audio source content, broadcast time, and number of broadcasts.

[0088] The operation monitoring device 130 may perform the fifth monitoring periodically. The operation monitoring device 130 may also perform the fifth monitoring when an abnormality is detected after performing one or more of the first to fourth monitoring.

[0089] The operation monitoring device 130 may comprehensively monitor the monitored device 132 by performing at least two of the first to fifth monitoring steps. Through comprehensive monitoring, the operation monitoring device 130 can detect the operating status of the monitored device 132 and optimize the monitored device 132 by monitoring, analyzing, and comparing the state of the audio output from the input system 110 to the output system 112.

[0090] The operating status of the monitored device 132 includes hardware abnormality information obtained through contact monitoring (second monitoring), and network status, setting information (volume settings, frequency settings, etc.), and operation information (temperature information, broadcast audio content, broadcast time, number of broadcasts, etc.) obtained through local area network monitoring (first monitoring, fifth monitoring).

[0091] The audio status includes information such as the level and waveform of the audio signal transmitted between the input system 110 and the output system 112 (third monitoring), and the signal level and acoustic distortion of the audio output (amplified) from the output system 112 (fourth monitoring).

[0092] In one example, the operation monitoring device 130 compares the volume setting value of the monitored device 132 (information obtained by the fifth monitoring) with the actual sound level output from the output system 112 of the monitored device 132 (information obtained by the fourth monitoring). Based on the information obtained from the comparison, the operation monitoring device 130 determines the validity of the volume setting and automatically adjusts the volume setting of the operation monitoring device 130.

[0093] For example, the operation monitoring device 130 may compare the volume setting of the input system 110, the volume setting of the processing system 111, and the level of the sound output from the output system 112, and output comparison result information. Such information is useful in determining whether to adjust the volume of the input system 110 or the processing system 111 when the volume is insufficient. Furthermore, a predetermined volume adjustment model formed from the information obtained in this way may be used in a program that automatically adjusts the volume settings of the operation monitoring device 130.

[0094] The operation monitoring device 130 may compare the volume setting value (information obtained by the fifth monitoring), the level of the audio signal from the input system 110 to the output system 112 (information obtained by the third monitoring), and the level of the audio output from the output system 112 (information obtained by the fourth monitoring), and output comparison result information. Such information is useful in determining where the problem lies when the perceived volume is insufficient. Furthermore, a predetermined problem analysis model formed from the information obtained in this way may be used in the abnormality detection program of the operation monitoring device 130.

[0095] In another example, if the operation monitoring device 130 determines that there is an anomaly in the actual audio output from the output system 112 of the monitored device 132, it performs a first or second monitoring to determine whether there is a malfunction in the monitored device 132 or a malfunction in the transmission path between the monitored devices 132. Based on the information obtained from the first or second monitoring, the operation monitoring device 130 makes a determination to identify the cause, such as whether the local area network 131 is the cause. Then, the operation monitoring device 130 takes action for the cause based on the determination result. The operation monitoring device 130 has action information in advance regarding the action to take for the cause of the malfunction. The action information is stored in the memory unit of the operation monitoring device 130.

[0096] If an abnormality is detected in the first to fifth monitoring, the operation monitoring device 130 outputs abnormality data to the monitoring information terminal 140. The monitoring information terminal 140 displays the abnormality data on its display unit. The operation monitoring device 130 may output only a portion of the abnormality data to the monitoring information terminal 140. For example, the operation monitoring device 130 may output only simplified information indicating whether the monitored device 132 is operating normally to the monitoring information terminal 140. In this case, the monitoring information terminal 140 displays only the simplified information on its display unit. The operation monitoring device 130 may output both the simplified information and other information (detailed information) to the data management server 20. In this case, the user of the data management server 20 (the operator of the loudspeaker 11) can obtain detailed information from the first to fifth monitoring. The user can remotely understand the details of the abnormal condition using the detailed information. Detailed information includes setting information (volume settings, frequency settings, etc.) and operation information (temperature information, broadcast audio content, broadcast time, number of broadcasts, etc.) recorded by the computing device within the monitored device 132.

[0097] For example, the operation monitoring device 130 may output only the monitoring results of the first to fourth monitoring to the monitoring information terminal 140, and output the results of the fifth monitoring in addition to the monitoring results of the first to fourth monitoring to the data management server 20.

[0098] The operation monitoring device 130 may perform the web service described above. For example, the operation monitoring device 130 may perform a monitoring service as shown in Figure 4. In this case, the operation monitoring device 130 collects and transmits sound amplification status information (S10) from the sound amplification device 11.

[0099] Furthermore, the operation monitoring device 130 may perform an effectiveness measurement service for public address broadcasts as shown in Figure 9. In this case, the operation monitoring device 130 is connected to the camera 12 and microphone 13 and transmits video data from the camera 12 and audio data of the input sound from the microphone 13 (S20 and S21).

[0100] Furthermore, the operation monitoring device 130 may perform an abnormality detection service as shown in Figure 14. In this case, the operation monitoring device 130 collects and transmits the judgment result from the loudspeaker 11 (S40 and S41).

[0101] (supplement) The public address system 11 comprises a processing unit including a CPU (Central Processing Unit) and an MPU (Micro Processing Unit), and a memory that holds computer programs that the processing unit can execute. The various functions of the public address system 11 are realized by the processing unit executing the computer programs held in the memory. The computer programs held in the memory include program instructions that execute the various processes performed by the public address system 11 as described above, such as S10, S40-S41, S58-S60, S71-S72, etc.

[0102] The data management server 20 comprises a processing unit including a CPU and MPU, and memory that holds computer programs that the processing unit can execute. The various functions of the data management server 20 are realized by the processing unit executing the computer programs held in memory. The computer programs held in memory include program instructions that execute the various processes performed by the data management server 20 as described above, such as S11-S13, S23-S25, S30-S32, S42-S44, S51-S53, S54-S57, S61, S70, S73, S76-S78, etc.

[0103] The camera 12 comprises a processing unit including a CPU and MPU, and memory that holds computer programs that the processing unit can execute. The various functions of the camera 12 are realized by the processing unit executing the computer programs held in memory. The computer programs held in memory include program instructions that execute the various processes performed by the camera 12 as described above, such as S20.

[0104] The microphone 13 comprises a processing unit including a CPU and MPU, and a memory that holds computer programs that the processing unit can execute. The various functions of the microphone 13 are realized by the processing unit executing the computer programs held in the memory. The computer programs held in the memory include program instructions such as S21, S74-S75, etc., that execute various processes performed by the camera 12 described above.

[0105] The mobile communication terminal 15 comprises a processing unit including a CPU and MPU, and a memory that holds computer programs that the processing unit can execute. Various functions of the mobile communication terminal 15 are realized by the processing unit executing the computer programs held in memory. The computer programs held in memory include program instructions that execute various processes performed by the mobile communication terminal 15 as described above, such as S22, S50, and S54. When the mobile communication terminal 15 is a client that receives services provided by the data management server 20 in S13, S25, S32, S44, and S78, the computer programs held in memory include program instructions that execute processes for those services.

[0106] The operation monitoring device 130 comprises a processing unit including a CPU and MPU, and a memory that holds computer programs that the processing unit can execute. The various functions of the operation monitoring device 130 are realized when the processing unit executes the computer programs held in the memory. The computer programs held in the memory include program instructions that execute the various processes performed by the operation monitoring device 130 as described above.

[0107] Figure 23 shows an example of an embodiment of the public address system 1. In the public address system 1, the data management server 20 includes multiple server elements 20a to 20g according to the functions of the services provided. The content server 20a is a server that provides content to the public address device 11, and has the function of holding the sound source 25 and inspection sound source 27 mentioned above and transmitting them to the public address device 11 (S53, S57, S70). The equipment management server 20b is a server that manages equipment such as the public address device 11 in the public address space 10, and has the function of accumulating public address information (S12), accumulating various types of information (S24), accumulating judgment information (S43), and accumulating inspection results (S77), and also has the function of accumulating logs 21, databases 23, history 26, etc. The portal server 20c is a server that serves as a point of contact with the client, and has the function of executing S13, S25, S32, S44, S78, for example. The analysis server 20d is a server that performs data analysis and statistical processing, and has functions to execute, for example, S30, S31, and S76. The end-user server 20e is a server that serves as a point of contact with the mobile communication terminal 15 held by the user 14, and has functions to execute, for example, S51 and S53. The spatial awareness server 20f is a server that assesses the situation of the sound amplification space 10, and is a server that serves as a point of contact with the camera 12 and microphone 13, and has functions to execute, for example, S23 and S76. The diagnostic server 20g is a server that serves as a point of contact with the client for diagnosing the sound amplification device 11, and has functions to execute, for example, S13, S25, S32, S44, and S78. [Explanation of symbols]

[0108] 1. Public address system 10. Sound reinforcement space 11. Public address system 12 cameras 13 Microphone 20. Data Management Server (Server)

Claims

1. It is a public address system, The system comprises one or more sound amplification devices installed in each of one or more sound amplification spaces, and a server connected to the sound amplification devices via the Internet network. The server maintains a history associated with a mobile communication terminal located within the loudspeaker space. Public address system.

2. The history includes at least one of the settings for broadcasting from the loudspeaker and the information regarding the selection of a sound source. The loudspeaker system according to claim 1.

3. The aforementioned history is recorded on the server for each identification information of the mobile communication terminal accessing the server. Furthermore, the history is recorded on the server each time the history is set, in association with the date and time the setting was made. The loudspeaker system according to claim 1.

4. When the server receives access from the mobile communication terminal via the Internet network, if there is a history associated with the identification information of the mobile communication terminal, it refers to the history corresponding to the mobile communication terminal and instructs the loudspeaker to broadcast a loudspeaker based on the history. The loudspeaker system according to claim 3.

5. When the server receives access from the mobile communication terminal via the Internet network, if there is no history associated with the identification information of the mobile communication terminal, the server accepts a request from the mobile communication terminal to specify the loudspeaker settings for loudspeaker broadcasting using the loudspeaker device, and records the specified loudspeaker settings as history on the server. The loudspeaker system according to claim 3.

Images