Emergency broadcast playback system
The emergency broadcast playback system addresses the limitation of conventional systems by automatically playing emergency broadcasts on user terminals, enhancing the reach of urgent information beyond those actively tuned to simulcasts.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2026-04-08
Smart Images
Figure 2026060517000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an emergency broadcast playback system.
Background Art
[0002] The following information distribution system is known. In this information distribution system, when there is a disaster prevention administrative radio broadcast while the user is listening to a simulcast, the disaster prevention administrative radio broadcast is interrupted to the simulcast that the user is listening to (for example, Patent Document 1).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] In the conventional information distribution system, by interrupting the simulcast with the disaster prevention administrative radio broadcast, information with high urgency was distributed to users listening to the simulcast. Such highly urgent emergency information is desirably delivered to more users who are receiving the simulcast using a terminal such as a smartphone when the emergency information is generated from the broadcasting station. In this regard, in the conventional information distribution system, while it is possible to distribute information with high urgency to users listening to the simulcast, it was not possible to deliver information with high urgency to users who were not listening to the simulcast. For this reason, if it were possible to automatically play back emergency information on the terminal even when the user is not listening to the simulcast, it would be possible to notify more users of the emergency information, but conventionally, no method for this has been studied at all.
Means for Solving the Problems
[0005] The emergency broadcast playback system according to the present invention comprises: streaming broadcast receiving means for receiving a streaming broadcast transmitted from a broadcasting station; emergency broadcast detection means for detecting when an emergency broadcast has started during a streaming broadcast received by the streaming broadcast receiving means; push notification instruction means for instructing a push notification distribution server to distribute a push notification to a user terminal owned by the user when the start of an emergency broadcast is detected by the emergency broadcast detection means; and simulcast redistribution means for converting the streaming broadcast received by the streaming broadcast receiving means into a format suitable for playback on the user terminal and redistributing the simulcast. The user terminal is characterized in that, when it receives a push notification from the push notification distribution server, it displays a playback screen for playing the simulcast and is equipped with playback means for receiving and playing the simulcast. The emergency broadcast playback system according to the present invention is an emergency broadcast playback system in which a streaming broadcast receiving server that receives streaming broadcasts transmitted from a broadcasting station, an automatic startup management server that manages the automatic startup of applications on a user terminal owned by a user, a simulcast redistribution server that redistributes simulcasts, and a user terminal are connected via a communication line, wherein the streaming broadcast receiving server includes streaming broadcast receiving means for receiving streaming broadcasts transmitted from a broadcasting station, emergency broadcast detection means for detecting when an emergency broadcast has started during a streaming broadcast received by the streaming broadcast receiving means, and when the start of an emergency broadcast is detected by the emergency broadcast detection means, the automatic startup management server notifies the user terminal that an emergency broadcast has started. The system is equipped with an instruction means for giving instructions to do so, and the automatic startup management server is equipped with a push notification instruction means for giving instructions to the push notification distribution server to give instructions to the user terminal to automatically start the application when it receives instructions from the streaming broadcast receiving server to notify the user terminal that an emergency broadcast has started, and the simulcast redistribution server is equipped with a simulcast redistribution means for receiving the streaming broadcast received by the streaming broadcast receiving server, converting it into a format suitable for playback on the user terminal, and redistributing the simulcast, and the user terminal is equipped with a playback means for receiving and playing the simulcast when it receives a push notification from the push notification distribution server to play the simulcast. [Effects of the Invention]
[0006] According to the present invention, when it is detected that an emergency broadcast has started during a streaming broadcast transmitted from a broadcasting station, a push notification is sent to the user's terminal. Upon receiving the push notification, the user's terminal can display a playback screen and automatically play the simulcast, thus allowing users who are not listening to the simulcast to also listen to the emergency broadcast. [Brief explanation of the drawing]
[0007] [Figure 1]This is a block diagram showing the configuration of one embodiment of the emergency broadcast playback system 10. [Figure 2] This is a block diagram showing the configuration of one embodiment of a streaming broadcast receiving server 100. [Figure 3] This is a block diagram showing the configuration of one embodiment of the automatic startup management server 200. [Figure 4] This is a block diagram showing the configuration of one embodiment of the simulcast redistribution server 300. [Figure 5] This is a block diagram showing the configuration of one embodiment of the interrupt broadcast server 400. [Figure 6] This is a block diagram showing the configuration of one embodiment of the user terminal 500. [Figure 7] This flowchart shows the flow of emergency broadcast notification instruction processing performed by the streaming broadcast receiving server 100. [Figure 8] This is a flowchart illustrating the flow of the streaming broadcast transmission process performed by the streaming broadcast receiving server 100. [Figure 9] This is a flowchart illustrating the processing flow executed by the automatic startup management server 200. [Figure 10] This is a flowchart illustrating the processing flow executed on the simulcast redistribution server 300. [Figure 11] This is a flowchart illustrating the processing flow executed by the interrupt broadcast server 400. [Figure 12] This is a flowchart illustrating the processing flow executed on user terminal 500. [Modes for carrying out the invention]
[0008] Figure 1 is a block diagram showing the configuration of one embodiment of the emergency broadcast playback system 10 in this embodiment. The emergency broadcast playback system 10 consists of a streaming broadcast receiving server 100, an automatic startup management server 200, a simulcast redistribution server 300, an interrupt broadcast server 400, and a user terminal 500. As shown in Figure 1, each device is connected via a communication line, such as the Internet. In this embodiment, the emergency broadcast playback system 10 can automatically play an emergency broadcast when it is broadcast from a broadcasting station by executing the processing described later, displaying a playback screen for playing the emergency broadcast on the user terminal 500. In this embodiment, the broadcasting station is assumed to be, for example, a television station, a cable television station, a radio station, or a community FM station.
[0009] The streaming broadcast receiving server 100 is a device for receiving streaming broadcasts from broadcasting stations. Figure 2 is a block diagram showing the configuration of one embodiment of the streaming broadcast receiving server 100 in this embodiment. The streaming broadcast receiving server 100 includes a connection interface 101, a control device 102, and a storage medium 103.
[0010] The connection interface 101 is an interface for connecting the streaming broadcast receiving server 100 to a communication line such as the Internet. For example, a wired LAN module for connecting to the Internet via a wired connection or a wireless LAN module for connecting to the Internet wirelessly can be used. In this embodiment, the streaming broadcast receiving server 100 communicates with other devices via this connection interface 101.
[0011] The control unit 102 consists of a CPU, memory, and other peripheral circuits, and controls the entire streaming broadcast receiving server 100. The memory that makes up the control unit 102 is a volatile memory such as SDRAM. This memory is used as work memory for the CPU to load programs when executing programs, and as buffer memory for temporarily recording data. For example, data read via the connection interface 101 is temporarily recorded in the buffer memory.
[0012] The storage medium 103 is used to record various data stored by the streaming broadcast receiving server 100, as well as program data for execution by the control device 102. For example, an HDD (Hard Disk Drive) or SSD (Solid State Drive) may be used. The program data to be recorded on the storage medium 103 may be provided on a recording medium such as a CD-ROM or DVD-ROM, or via a network. By installing the program data acquired by the operator onto the storage medium 103, the control device 102 can execute the program.
[0013] The automatic startup management server 200 is a device that performs processing to manage the automatic startup of applications on the user terminal 500. In this embodiment, the automatic startup management server 200 manages the automatic startup of applications installed on the user terminal 500 by instructing the push notification distribution server 600 to distribute push notifications to the user terminal 500. Figure 3 is a block diagram showing the configuration of one embodiment of the automatic startup management server 200 in this embodiment. The automatic startup management server 200 includes a connection interface 201, a control device 202, and a storage medium 203.
[0014] The connection interface 201 is an interface for connecting the automatic startup management server 200 to a communication line such as the Internet. For example, a wired LAN module for wired connection to the Internet, a wireless LAN module for wireless connection to the Internet, or the like is used. In the present embodiment, the automatic startup management server 200 communicates with other devices via this connection interface 201.
[0015] The control device 202 is composed of a CPU, a memory, and other peripheral circuits, and controls the entire automatic startup management server 200. The memory constituting the control device 202 is a volatile memory such as SDRAM, for example. This memory is used as a work memory for the CPU to expand a program during program execution and as a buffer memory for temporarily recording data. For example, data read via the connection interface 201 is temporarily recorded in the buffer memory.
[0016] The storage medium 203 is a storage medium for recording various data stored by the automatic startup management server 200, program data for the control device 202 to execute, etc. For example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like is used. The program data recorded on the storage medium 203 is recorded on a recording medium such as a CD-ROM or a DVD-ROM and provided, or provided via a network, and the operator installs the obtained program data on the storage medium 203 so that the control device 202 can execute the program.
[0017] The simulcast re-distribution server 300 is a device that executes processing for converting streaming broadcasts from a broadcasting station into a format suitable for playback on an application installed on the user terminal 500 and re-distributing the simulcast. FIG. 4 is a block diagram showing the configuration of an embodiment of the simulcast re-distribution server 300. The simulcast re-distribution server 300 includes a connection interface 301, a control device 302, and a storage medium 303.
[0018] The connection interface 301 is an interface for connecting the simulcast redistribution server 300 to a communication line such as the Internet. For example, a wired LAN module for wired connection to the Internet or a wireless LAN module for wireless connection to the Internet can be used. In this embodiment, the simulcast redistribution server 300 communicates with other devices via this connection interface 301.
[0019] The control unit 302 consists of a CPU, memory, and other peripheral circuits, and controls the entire simulcast redistribution server 300. The memory that makes up the control unit 302 is a volatile memory such as SDRAM. This memory is used as work memory for the CPU to load programs when executing programs, and as buffer memory for temporarily recording data. For example, data read via the connection interface 301 is temporarily recorded in the buffer memory.
[0020] The storage medium 303 is used to record various data stored by the simulcast redistribution server 300, as well as program data for execution by the control device 302. For example, an HDD (Hard Disk Drive) or SSD (Solid State Drive) may be used. The program data to be recorded on the storage medium 303 may be provided on a recording medium such as a CD-ROM or DVD-ROM, or via a network. By installing the program data acquired by the operator onto the storage medium 302, the control device 302 will be able to execute the program.
[0021] The interrupt broadcast server 400 is a device that performs processing to independently interrupt the simulcast broadcast redistributed from the simulcast redistribution server 300 with audio and video. Figure 5 is a block diagram showing the configuration of one embodiment of the interrupt broadcast server 400. The interrupt broadcast server 400 includes a connection interface 401, a control device 402, and a storage medium 403.
[0022] The connection interface 401 is an interface for connecting the interrupt broadcast server 400 to a communication line such as the Internet. For example, a wired LAN module for wired connection to the Internet or a wireless LAN module for wireless connection to the Internet can be used. In this embodiment, the interrupt broadcast server 400 communicates with other devices via this connection interface 401.
[0023] The control unit 402 consists of a CPU, memory, and other peripheral circuits, and controls the entire interrupt broadcast server 400. The memory comprising the control unit 402 is a volatile memory such as SDRAM. This memory is used as work memory for the CPU to load programs during program execution and as buffer memory for temporarily recording data. For example, data read via the connection interface 401 is temporarily recorded in the buffer memory.
[0024] The storage medium 403 is used to record various data stored by the interrupt broadcast server 400, as well as program data for execution by the control device 402. For example, an HDD (Hard Disk Drive) or SSD (Solid State Drive) may be used. The program data to be recorded on the storage medium 403 may be provided on a recording medium such as a CD-ROM or DVD-ROM, or via a network. By installing the program data acquired by the operator onto the storage medium 402, the control device 402 can execute the program.
[0025] The user terminal 500 is a terminal that receives and plays back simulcast broadcasts redistributed from the simulcast redistribution server 300, and can be a personal computer, tablet, mobile phone, or smartphone. Figure 6 is a block diagram showing the configuration of one embodiment in which a smartphone is used as the user terminal 500 in this embodiment. The user terminal 500 includes a touch panel 501, a communication module 502, a control device 503, and a speaker 504.
[0026] The touch panel 501 is an input device that allows the device to be operated by pressing the display on the screen. For example, the operator of the user terminal 500 can operate the user terminal 500 by touching or sliding the display items such as buttons and menus displayed on the LCD panel with their finger or a stylus. The touch panel 501 detects operations such as touching or sliding by the operator and outputs the detection signal to the control device 503.
[0027] The communication module 502 includes a communication module for communicating with other devices wirelessly or via a wired connection.
[0028] The control unit 503 consists of a CPU, memory, and other peripheral circuits, and controls the entire user terminal 500. The memory comprising the control unit 503 includes volatile memory such as SDRAM and non-volatile memory such as flash memory. The volatile memory is used as work memory for the CPU to load programs when executing programs, and as buffer memory for temporarily recording data. The non-volatile memory stores firmware for operating the user terminal 500 and program data for software that runs various applications.
[0029] Speaker 504 is an output device for outputting sound.
[0030] In this embodiment, the emergency broadcast playback system 10 can automatically play an emergency broadcast when an emergency broadcast is made from a broadcasting station by displaying a playback screen for playing the emergency broadcast on the user terminal 500. To do this, the user of the user terminal 500 installs software for using the emergency broadcast playback system 10 on the user terminal 500 in advance. The software for using the emergency broadcast playback system 10 is an application (hereinafter referred to as "app") that has the function of playing back simulcasts redistributed from the simulcast redistribution server 300.
[0031] After installing the app, the user launches the app and configures it for use. The method and content of the configuration for using the app are not particularly limited, but in this embodiment, for example, the user will configure the following settings. In this embodiment, it is assumed that the user ID and password for using the emergency broadcast playback system 10 are recorded in advance along with the user management ID in the user information storage device of a user management server (not shown).
[0032] The control device 503 of the user terminal 500 launches the application when instructed by the user to launch it, and displays an authentication screen for user identification on the touch panel 501. The user operates the touch panel 501 and enters a user ID and password on the authentication screen. The control device 503 sends the user ID and password entered by the user to the user management server. The user management server checks whether the user ID and password match the records stored in the user information storage device. If a matching record exists in the user information storage device, the user management server retrieves the user management ID recorded in association with that user ID and sends the retrieved user management ID to the user terminal 500, thereby returning the user management ID to the application. On the other hand, if a matching record does not exist in the user information storage device, the user management server sends an error indicating that authentication failed to the user terminal 500, thereby returning an authentication failure error to the application. In the user terminal 500, when the control device 503 receives the user management ID from the user management server, it records the received user management ID in memory.
[0033] The control device 503 obtains a push notification token from the OS of the user terminal 500, which is used as an identifier for sending push notifications to the user terminal 500.
[0034] Next, the user sets the automatic playback method for emergency broadcasts. The control device 503 displays a screen for setting the automatic playback method for emergency broadcasts on the touch panel 501. On the automatic playback method setting screen for emergency broadcasts, the user selects "Automatically play" or "Do not automatically play" to set whether or not to automatically play emergency broadcasts. If the user sets the automatic playback of emergency broadcasts to "Do not automatically play," they then select either "Notify" or "Do not notify" for push notifications of emergency broadcasts.
[0035] On the other hand, if the user sets the automatic playback of emergency broadcasts to "Automatically play," they can configure the volume during automatic playback, the days and times when emergency broadcasts should be automatically played, the types of emergency broadcasts to be automatically played, and how to stop automatic playback after the emergency broadcast ends, on the automatic playback method settings screen for emergency broadcasts. The following explanation describes an example of setting the days and times when emergency broadcasts should be automatically played and the types of emergency broadcasts to be automatically played, but setting the days and times when emergency broadcasts should be automatically played and the types of emergency broadcasts to be automatically played may be optional. If the user is not allowed to set the days and times when emergency broadcasts should be automatically played, then emergency broadcasts should be automatically played 24 hours a day, 365 days a year, whenever an emergency broadcast begins. Also, if the user is not allowed to set the types of emergency broadcasts to be automatically played, then all types of emergency broadcasts should be included in the automatic playback target.
[0036] For automatic playback of emergency broadcasts, the volume can be selected from either "Maximum Volume" or "Device Volume". The days and times for automatic playback of emergency broadcasts can be set by the user, for example, "Monday 00:00 to 23:59", "Tuesday 00:00 to 23:59", "Wednesday 00:00 to 23:59", "Thursday 00:00 to 23:59", "Friday 00:00 to 23:59", "Saturday 00:00 to 23:59", "Sunday 00:00 to 23:59". The types of emergency broadcasts to be automatically played can be selected by the user from, for example, "All Emergency Broadcasts", "Earthquake Warning", "Tsunami Warning", "Volcanic Eruption Warning", "Special Warning", "Fire Information", "Flood Information", and "Emergency Safety Information". Furthermore, users can select multiple types of emergency broadcasts for which automatic playback will be triggered. After an emergency broadcast ends, users can choose their preferred method for stopping automatic playback from the following options: "Follow the broadcaster's instructions regarding the end of the emergency broadcast," "Continue playback," or "Stop playback after a specified time from the start of playback." If the user selects "Stop playback after a specified time from the start of playback," they can specify how many minutes later playback should stop.
[0037] The control device 503 records in memory information indicating the automatic playback method selected by the user on the setting screen for the automatic playback method of emergency broadcasts. The control device 503 also sends automatic playback setting information, including the user management ID, the push notification token, and the information indicating the automatic playback method selected by the user on the setting screen for the automatic playback method of emergency broadcasts, to the automatic startup management server 200.
[0038] In the automatic startup management server 200, when the control device 203 receives automatic playback setting information from the user terminal 500, it records the received automatic playback setting information on the storage medium 203. Then, the control device 203 sends the saved automatic playback setting information to the user terminal 500, thereby returning the saved result to the application.
[0039] Once the setup for using the app is complete, the user can use the emergency broadcast playback system 10 via the app. The following describes the process for automatically playing an emergency broadcast on the user terminal 500 when an emergency broadcast is made from a broadcasting station.
[0040] Broadcasting stations are equipped with devices to stream broadcasts to external servers via the internet. The format of the streaming broadcasts transmitted by broadcasting stations is publicly known, so a detailed explanation is omitted here.
[0041] In the streaming broadcast receiving server 100, the control device 102 receives the streaming broadcast transmitted from the broadcasting station. The control device 102 then uses a program within the streaming broadcast receiving server 100 to detect the start position of the emergency broadcast within the audio data included in the streaming broadcast. The method for detecting the start position of the emergency broadcast is not particularly limited, but for example, any of the following methods 1, 2, 3, or 4 are possible. Method 1: Detect the start position based on the DTMF (push) signal included in the streaming broadcast. Method 2: The waveform of the jingle background music used to signal the start of an emergency broadcast, which is included in the streaming broadcast, is pre-registered. When a waveform similar to the pre-registered waveform is detected from the streaming broadcast, that position is detected as the starting position. Method 3: Embed a specific frequency pattern as a marker in the jingle background music used to signal the start of an emergency broadcast included in the streaming broadcast, and detect the start position of that marker from the streaming broadcast. Method 4: A person in charge at the broadcasting station manually notifies the streaming broadcast receiving server 100 of the start of an emergency broadcast. For example, if a management screen for broadcasting station staff is provided on the streaming broadcast receiving server 100, and a staff member at the broadcasting station clicks the emergency broadcast start button displayed on the management screen, the broadcasting station will notify the streaming broadcast receiving server 100 of the start of an emergency broadcast.
[0042] If the emergency broadcast start position is detected, it means that the audio data included in the streaming broadcast contains the emergency broadcast, and the emergency broadcast will start from the detected emergency broadcast start position. Therefore, the control device 102 can detect that an emergency broadcast has started during the streaming broadcast by detecting the emergency broadcast start position.
[0043] When the control device 102 detects the start of an emergency broadcast, it determines the type of emergency broadcast. Possible methods for determining the type of emergency broadcast include determining it based on a DTMF signal or determining it based on a jingle background music. For example, in the method of determining it based on a DTMF signal, #001# can be determined as an earthquake early warning, and #002# as a tsunami warning. In the method of determining it based on a jingle background music, a jingle background music corresponding to the type of emergency broadcast can be added to the emergency broadcast in advance, and the determination can be made based on the added background music.
[0044] As a result, whereas previously it was impossible to know the type of emergency broadcast until the broadcast began and the content was heard or seen, in this embodiment, the type of emergency broadcast can be determined by incorporating the type of emergency broadcast into the DTMF signal or background music.
[0045] When the control device 102 detects the start of an emergency broadcast, it instructs the automatic startup management server 200 to notify the application on the user terminal 500 that an emergency broadcast has started. When the control device 202 receives a notification instruction from the streaming broadcast receiving server 100, the automatic startup management server 200 executes a process to send a push notification to the application on the user terminal 500 that an emergency broadcast has started. The process executed by the automatic startup management server 200 will be described later.
[0046] In the streaming broadcast receiving server 100, the control device 102 transmits the streaming broadcast received from the broadcasting station to the simulcast redistribution server 300. In the simulcast redistribution server 300, the control device 302 converts the streaming broadcast received from the streaming broadcast receiving server 100 into a format suitable for playback by an application installed on the user terminal 500 (bitrate, encoding, file format, etc.), and then performs simulcast redistribution. This makes it possible to redistribute the same content over the internet at the same time that the broadcasting station distributes the broadcast via radio waves. As a result, the user terminal 500 can receive and play the simulcast broadcast, which has been converted into a format suitable for playback by the application on the user terminal 500, rather than the application directly receiving and playing the streaming broadcast from the broadcasting station.
[0047] The format for simulcast redistribution is a publicly available format, so a detailed explanation will be omitted. However, for example, by using HLS (HTTP Live Streaming), distribution using a CDN (Content Delivery Network) becomes possible, and stable distribution is possible even when an increase in access is expected from CDN distribution. In addition, processing such as reducing the screen size, lowering the audio quality, or converting to a format supported by user terminal 500 may be performed.
[0048] In this embodiment, after the start of an emergency broadcast, an interrupt broadcast can also be inserted into the broadcast from the broadcasting station. For example, the control device 402 of the interrupt broadcast server 400 can interrupt the simulcast redistributed from the simulcast redistribution server 300 with information such as "Please act calmly. Once the shaking stops, check for fire hazards. When evacuating, turn off the power breaker" five minutes after the start of the emergency broadcast of the earthquake early warning. The sound source for the interrupt broadcast may be a fixed sound source prepared in advance on a storage server where the sound sources for interrupt broadcasts are recorded, or it may be a broadcast sound source of the disaster prevention administrative radio sent from the local government's disaster prevention server that is broadcast as an interrupt broadcast.
[0049] Next, the processes executed by the automatic startup management server 200 will be described. When the control device 202 receives an instruction from the streaming broadcast receiving server 100 to notify the application on the user terminal 500 that the emergency broadcast described above has started, it obtains the push notification token recorded on the storage medium 203. Then, it creates a push notification payload and a push notification token list and sends them to the push notification distribution server 600. The push notification token list is a list of multiple push notification tokens. For example, a push notification token list listing the three push notification tokens "aaaaaaaa", "bbbbbbbb", and "ccccccccc" would look like this: ["aaaaaaaa", "bbbbbbbb", "ccccccccc"]. The push notification payload is additional data sent along with the subject and body of the push notification. By using the push notification payload, it is possible to include data necessary for processing by the application in the push notification, in addition to the subject and body of the push notification display.
[0050] Next, the push notification payload that the control device 202 sends to the push notification distribution server 600 will be described. The control device 202 determines whether automatic startup management is enabled based on the automatic playback setting information described above. In this embodiment, the control device 202 determines that automatic startup management is enabled if either "automatically play" or "do not automatically play" is set for emergency broadcasts based on the automatic playback setting information described above, and determines that automatic startup management is disabled if neither "automatically play" nor "do not automatically play" is set for emergency broadcasts.
[0051] If the control device 202 determines that automatic startup is being managed, it includes the "Auto-play" or "Do not auto-play" type of automatic startup in the push notification payload. For example, in this embodiment, if the type of automatic startup is "Auto-play," the control device 202 sets the item in the push notification payload that manages the automatic startup of the app to "Auto-start." On the other hand, if the type of automatic startup is "Do not auto-play," the control device 202 sets the item in the push notification payload that manages the automatic startup of the app to "Do not auto-start."
[0052] On the other hand, if the control device 202 determines that automatic startup is not managed, it sends a push notification to all push notification tokens indicating that an emergency broadcast has started, and the decision of whether or not to automatically play the broadcast is made according to the settings stored in the app on the user terminal 500. Furthermore, by including a type indicating whether or not to force automatic startup in the push notification payload, the emergency broadcast may be automatically played even for users who do not wish to have automatic startup.
[0053] In this embodiment, the push notification payload may include information such as the following. Subject: Emergency broadcast has begun Body: Please check the information on the radio or television. alert_type(Type of emergency broadcast): Earthquake Early Warning alert_title(Subject of the emergency broadcast to be displayed on the autoplay screen): There has been a major earthquake. Simulcast URL: https: / / xxxxxx / stream.m3u8 simul_type (Type of simulcast): Audio video_url (static video file in case simulcast cannot be viewed when automatically launched): https: / / xxxxxx / video.mp4 audio_url (static audio file in case simulcast cannot be heard when automatically launched): https: / / xxxxxx / audio.m4a video_filename (In-app filename in case video file download fails due to network issues, etc.): offline.mp4 audio_filename (In-app filename in case the audio file cannot be downloaded due to network issues, etc.): offline.m4a auto_start(automatic startup): Starts automatically. force_start(force autostart): Do not force
[0054] The above example of a push notification payload is just one example and is not limited to it. Also, the above example of a push notification payload may not include video_url, audio_url, video_filename, audio_filename, auto_start, and force_start.
[0055] The push notification distribution server 600 is a server equipped to deliver push notifications to the user terminal 500. Therefore, the control device 202 can send push notifications to the application on the user terminal 500 by sending data to the push notification distribution server 600. In this embodiment, it is assumed that the push notification distribution server 600 is an externally provided server, but the emergency broadcast playback system 10 may also be equipped with the push notification distribution server 600.
[0056] On the user terminal 500, if the control device 503 receives a push notification from the push notification distribution server 600 indicating the start of an emergency broadcast, it checks the contents of the push notification payload. If the auto_start (automatic startup) setting, which manages the automatic startup of the application, is set to "Do not start automatically," and the automatic playback method is configured to receive notifications via push notifications, the control device 503 displays the push notification using the notification subject and body, and then terminates processing.
[0057] On the other hand, if the control device 503 determines that auto_start (automatic startup) is set to "automatically start", it performs a determination process to determine whether to automatically play the emergency broadcast based on the contents of the push notification payload and the automatic playback setting information described above. The determination process performed by the control device 503 is described below.
[0058] The control device 503 determines whether the type of emergency broadcast is one that can be automatically played back. If the type of emergency broadcast is one that can be automatically played back, the control device 503 determines whether the current time is a day and time when automatic playback is permitted. If, based on the current date and time, the current time is a day and time when automatic playback is permitted, the control device 503 determines to automatically launch the application by displaying a playback screen for playing back the emergency broadcast and to automatically play back the simulcast.
[0059] When the control device 503 determines that it will automatically launch the application and automatically play the simulcast, if the user terminal 500 is in sleep mode, it will wake the terminal from sleep mode. Then, the control device 503 will launch the application by displaying the application's playback screen on the touch panel 501. At this time, if the type of simulcast is specified as "audio", the control device 503 will display an audio playback player on the playback screen. If the type of simulcast is specified as "video", it will display a video + audio playback player on the playback screen.
[0060] On the playback screen, in addition to the player, the subject of the emergency broadcast, a button to return to the app's home screen, and a button to stop playback of the simulcast and exit the app are displayed. The control device 503 then receives the simulcast from the simulcast URL included in the push notification payload and starts playback of the simulcast on the displayed player. At this time, the control device 503 sets the playback volume based on the volume setting for automatic playback included in the automatic playback settings information.
[0061] This means that, whereas previously an emergency broadcast required a radio compatible with emergency broadcasts if it was audio, or a television compatible with emergency broadcasts if it was video, in this embodiment, emergency information can be delivered to the user by installing an application on a user terminal 500 such as a smartphone.
[0062] Subsequently, the control device 503 determines how to stop playback of the simulcast based on the method for stopping automatic playback after the emergency broadcast ends, which is included in the automatic playback setting information. Specifically, if the method for stopping automatic playback after the emergency broadcast ends is set to "Follow the broadcaster's emergency broadcast termination," the control device 503 stops playback of the simulcast when it detects the end of the emergency broadcast. Also, if the method for stopping automatic playback after the emergency broadcast ends is set to "Continue playback," the control device 503 continues playback of the simulcast even after the emergency broadcast ends. Furthermore, if the method for stopping automatic playback after the emergency broadcast ends is set to "Stop playback after a specified time has elapsed since playback started," the control device 503 stops playback of the simulcast after a predetermined time has elapsed since playback started.
[0063] As a result, conventionally, when an emergency broadcast was started and played back, playback had to stop either when the broadcasting station ended the emergency broadcast or when the user stopped playback themselves. However, in this embodiment, the user can set whether to play the emergency broadcast as is, stop playback at a time set by the user, or wait for the broadcasting station to end the emergency broadcast.
[0064] Here, we will describe the process for detecting when an emergency broadcast has ended at a broadcasting station. In the streaming broadcast receiving server 100, the control device 102 uses a program within the streaming broadcast receiving server 100 to detect the end of the emergency broadcast within the audio data included in the streaming broadcast. The method for detecting the end of the emergency broadcast is not particularly limited, but for example, the following methods 1, 2, 3, or 4 are possible. Method 1: Detect the end of the emergency broadcast based on the DTMF (push) signal included in the streaming broadcast. For example, the broadcast can be terminated when #999# is detected. Method 2: Detect waveforms similar to pre-registered waveforms from the streaming broadcast and find the starting position of a waveform similar to the background music at the end of the emergency broadcast. Method 3: Detect the start position of the emergency broadcast end marker from the streaming broadcast. Method 4: Detect when a broadcasting station staff member clicks the emergency broadcast end button.
[0065] If the control device 102 detects the end of the emergency broadcast, it instructs the automatic startup management server 200 to notify the application on the user terminal 500 that the emergency broadcast has ended.
[0066] In the automatic startup management server 200, the control device 202 sends a push notification payload to the push notification distribution server 600, for example, as shown below. Simulcast URL: https: / / xxxxxx / stream.m3u8 simul_type (Type of simulcast): Emergency broadcast ended
[0067] On the user terminal 500, if the control device 503 receives a push notification from the push notification server 600 indicating the end of the emergency broadcast, it will stop playing the simulcast and terminate the application if the following three conditions are met. 1: The simul_type (type of simulcast) is set to "Emergency Broadcast Termination". 2: The method for stopping automatic playback after an emergency broadcast ends, as included in the automatic playback settings information, is set to "Follow the broadcaster's emergency broadcast termination instructions." 3. The app is currently playing a simulcast.
[0068] Furthermore, if the control device 503 is unable to stream the simulcast due to a network failure or other reasons, it may play a static audio file or static video file stored within the application. Also, if the user terminal 500, or an application installed on the user terminal 500, can be automatically launched but does not support streaming playback such as simulcast, the control device 503 may access the URL of a static audio file or static video file specified in the push notification payload, download the static file, and play it. Furthermore, if the static audio file or static video file cannot be downloaded due to a network failure or other reasons, the control device 503 may play a static audio file or static video file stored within the application. Also, if the control device 503 is unable to play the static audio file or static video file, it may notify the user by displaying on the touch panel 501 that there has been an emergency broadcast, or by sending the subject and body of the payload via local notification and displaying it on the touch panel 501.
[0069] If the control device 503 detects that the user has clicked a button on the playback screen to transition to the app's home screen, it will transition to the app's home screen while the currently playing simulcast continues. Also, if the control device 503 detects that the user has clicked a button on the playback screen to stop the simulcast playback and close the app, it will stop the simulcast playback and close the app. Furthermore, if the user closes the app, the control device 503 will also stop the simulcast playback and close the app.
[0070] Figure 7 is a flowchart showing the flow of emergency broadcast notification instruction processing performed by the streaming broadcast receiving server 100 in this embodiment. The processing shown in Figure 7 is executed by the control device 102 as a program that starts when reception of a streaming broadcast sent from a broadcasting station begins.
[0071] In step S10, the control device 102 determines whether or not the reception of the streaming broadcast from the broadcasting station has finished. If the determination in step S10 is positive, the process ends. If the determination in step S10 is negative, the process proceeds to step S20.
[0072] In step S20, the control device 102, as described above, uses a program in the streaming broadcast receiving server 100 to detect the start position of the emergency broadcast within the audio data included in the streaming broadcast, thereby determining whether or not it has detected the start of the emergency broadcast. If the determination in step S20 is negative, the device returns to step S10. On the other hand, if the determination in step S20 is positive, the device proceeds to step S30.
[0073] In step S30, the control device 102 instructs the automatic startup management server 200 to notify the application on the user terminal 500 that an emergency broadcast has been initiated, as described above. Then, the process proceeds to step S40.
[0074] In step S40, the control device 102 determines whether or not the reception of the streaming broadcast from the broadcasting station has finished. If the determination in step S40 is positive, the process ends. If the determination in step S40 is negative, the process proceeds to step S50.
[0075] In step S50, the control device 102 uses the program in the streaming broadcast receiving server 100, as described above, to determine whether or not it has detected the end of the emergency broadcast. If the determination in step S50 is negative, the process returns to step S40. Conversely, if the determination in step S50 is positive, the process proceeds to step S60.
[0076] In step S60, the control device 102 instructs the automatic startup management server 200 to notify the application on the user terminal 500 that the emergency broadcast has ended, as described above. Then, the process returns to step S10.
[0077] Figure 8 is a flowchart showing the flow of the streaming broadcast transmission process executed by the streaming broadcast receiving server 100 in this embodiment. The process shown in Figure 8 is executed by the control device 102 as a program that starts when the reception of a streaming broadcast transmitted from a broadcasting station begins.
[0078] In step S110, the control device 102 starts transmitting the streaming broadcast received from the broadcasting station to the simulcast redistribution server 300. Then, the process proceeds to step S120.
[0079] In step S120, the control device 102 determines whether or not the reception of the streaming broadcast from the broadcasting station has finished. If the determination in step S120 is positive, the process is terminated.
[0080] Figure 9 is a flowchart showing the processing flow executed by the automatic startup management server 200 in this embodiment. The processing shown in Figure 9 is executed by the control device 202 as a program that is started when the streaming broadcast receiving server 100 instructs the application on the user terminal 500 to notify it that an emergency broadcast has started.
[0081] In step S210, the control device 202 obtains the push notification token recorded in the storage medium 203, as described above. Then, the process proceeds to step S220.
[0082] In step S220, the control unit 202 performs the above-described process to create the push notification payload and push notification token list. Then, the process proceeds to step S230.
[0083] In step S230, the control device 202 sends the push notification payload and push notification token list to the push notification delivery server 600. After that, the process ends.
[0084] Figure 10 is a flowchart showing the processing flow performed by the simulcast redistribution server 300 in this embodiment. The processing shown in Figure 10 is executed by the control device 302 as a program that is started when the reception of streaming broadcasts from the streaming broadcast receiving server 100 begins.
[0085] In step S310, the control device 302 converts the streaming broadcast received from the streaming broadcast receiving server 100 into a format suitable for playback by an application installed on the user terminal 500 (bitrate, encoding, file format, etc.). Then, the process proceeds to step S320.
[0086] In step S320, the control device 302 performs simulcast redistribution by distributing the broadcast converted in step S310. After that, the process ends.
[0087] Figure 11 is a flowchart showing the processing flow executed by the interrupt broadcast server 400 in this embodiment. The processing shown in Figure 11 is executed by the control device 402 as a program that is started when instructed to interrupt a broadcast from a broadcasting station.
[0088] In step S410, the control device 402, as described above, executes a process to interrupt the simulcast as an interrupt broadcast using a pre-prepared sound source for an interrupt broadcast or a broadcast sound source for the disaster prevention administrative radio sent from the local government's disaster prevention server. After that, the process ends.
[0089] Figure 12 is a flowchart showing the processing flow executed on the user terminal 500 in this embodiment. The processing shown in Figure 12 is executed by the control device 503 as a program that is activated when a push notification of the start of an emergency broadcast is received from the push notification distribution server 600. Note that in Figure 12, it is assumed that the user has already completed the installation of the application on the user terminal 500 and the settings required to use the application.
[0090] In step S510, the control device 503 checks the contents of the push notification payload as described above. Then, it proceeds to step S520.
[0091] In step S520, the control device 503 determines whether the auto_start (automatic startup) item, which manages the automatic startup of the application, is set to "automatically start". If the determination in step S520 is negative, that is, if auto_start (automatic startup) is set to "do not automatically start", the process proceeds to step S530.
[0092] In step S530, the control device 503 determines whether or not the device is configured to receive notifications via push notifications as an automatic playback method. If the determination in step S530 is negative, the process ends. On the other hand, if the determination in step S530 is positive, the process proceeds to step S540.
[0093] In step S540, the control device 503 displays a push notification using the subject and body of the notification, as described above, and then terminates the process.
[0094] On the other hand, if a positive determination is made in step S520, the process proceeds to step S550. In step S550, the control device 503 performs a determination process to determine whether to automatically play the emergency broadcast based on the contents of the push notification payload and the automatic playback setting information described above, as described above. After that, the process proceeds to step S560.
[0095] In step S560, a decision is made based on the result of the judgment process in step S550 whether or not to perform automatic playback of the emergency broadcast. If the decision in step S560 is negative, the process ends. On the other hand, if the decision in step S560 is positive, the process proceeds to step S570.
[0096] In step S570, the control device 503 starts playback of the simulcast. Specifically, as described above, if the user terminal 500 is in sleep mode, the control device 503 wakes the terminal from sleep mode. Then, the control device 503 displays the app playback screen on the touch panel 501, launches the app, and starts playback of the simulcast using the displayed player. After that, the process proceeds to step S580.
[0097] In step S580, as described above, the control device 503 performs a process to determine how to stop the playback of the simulcast based on the method for stopping automatic playback after the emergency broadcast ends, which is included in the automatic playback setting information. Then, as described above, the control device 503 controls the playback of the simulcast according to the determined stopping method. After that, the process proceeds to step S590.
[0098] In step S590, the control device 503 determines whether the user has pressed a button on the playback screen to transition to the app's home screen. If the determination in step S590 is negative, the process proceeds to step S610, which will be described later. Conversely, if the determination in step S590 is positive, the process proceeds to step S600.
[0099] In step S600, the control device 503 transitions to the app's home screen while the currently playing simulcast remains unchanged. Then, it proceeds to step S610.
[0100] In step S610, the control device 503 determines whether the user has pressed the button on the playback screen to stop playback of the simulcast and exit the application. If the determination in step S610 is negative, the device returns to step S590. Conversely, if the determination in step S610 is positive, the device proceeds to step S620.
[0101] In step S620, the control device 503 stops playback of the simulcast and terminates the application. After that, it terminates the process.
[0102] According to the embodiments described above, the following effects and advantages can be obtained. (1) The emergency broadcast playback system 10 is connected via a communication line to a streaming broadcast receiving server 100 that receives streaming broadcasts transmitted from a broadcasting station, an automatic startup management server 200 that manages the automatic startup of applications on a user terminal 500 owned by the user, a simulcast redistribution server 300 that redistributes simulcasts, and a user terminal 500. The control device 102 of the streaming broadcast receiving server 100 receives streaming broadcasts transmitted from a broadcasting station, and when it detects that an emergency broadcast has started during the received streaming broadcast, it instructs the automatic startup management server 200 to notify the user terminal 500 that an emergency broadcast has started. The control device 202 of the automatic startup management server 200, when instructed by the streaming broadcast receiving server 100 to notify the user terminal 500 that an emergency broadcast has started, instructs the push notification distribution server 600 to distribute a push notification to the user terminal 500 to manage the automatic startup of applications. In the simulcast redistribution server 300, the control device 302 receives the streaming broadcast received by the streaming broadcast receiving server 100, converts it to a format suitable for playback on the user terminal 500, and redistributes the simulcast. On the user terminal 500, when the control device 503 receives a push notification from the push notification distribution server 600, it displays a playback screen for playing the simulcast, and receives and plays the simulcast. This allows the simulcast to be automatically played when an emergency broadcast begins. In this way, by combining automatic detection of emergency broadcasts and automatic playback of simulcasts, users can quickly obtain emergency information without any operation when an emergency broadcast is made.
[0103] (2) When the user terminal 500 receives a push notification from the push notification distribution server 600, the control device 503 determines that it is set to automatically play when an emergency broadcast starts, and displays a playback screen for playing the simulcast, receives the simulcast, and plays it at a volume previously specified by the user. This allows the user to set in advance whether or not to play the emergency broadcast.
[0104] (3) When the user terminal 500 receives a push notification from the push notification distribution server, the control device 503 determines that the user has previously set the device to automatically play when an emergency broadcast starts, and that the type of emergency broadcast is one that can be automatically played. If the device determines that the current time is a day and time when automatic playback is performed based on the current date and time, it displays a playback screen for playing the simulcast, receives the simulcast, and plays it at a volume previously specified by the user. This allows the user to set whether or not to play the emergency broadcast and the time period during which they want to be notified of an emergency broadcast. For example, the user can set the time period during which they want to be notified of an emergency broadcast, so information can be delivered in a way that meets the user's needs, such as only wanting to be notified while sleeping. The user can also specify the volume when the emergency broadcast is played.
[0105] (4) In the user terminal 500, the control device 503 is configured to wake the user terminal 500 from sleep mode and then display the playback screen if the user terminal 500 is in sleep mode. This allows the playback screen to be displayed and emergency methods to be automatically played even when the user terminal 500 is in sleep mode.
[0106] (5) In the user terminal 500, the control device 503 stops the playback of the simulcast after it has started, based on a pre-specified method for stopping automatic playback. This allows the user to specify how to stop playback after the simulcast has started to play automatically.
[0107] (6) In the interrupt broadcast server 400, the control device 402 is configured to interrupt the simulcast broadcast that is redistributed by the simulcast redistribution server 300. This makes it possible to interrupt the simulcast broadcast that is redistributed for the application with a unique broadcast.
[0108] —Revised Version— Furthermore, the emergency broadcast playback system of the above-described embodiment can also be modified as follows. (1) In the above-described embodiment, an example was described in which the user ID and password for using the emergency broadcast playback system 10 are recorded in advance along with the user management ID in a user information storage device provided by a user management server (not shown). The control device 503 of the user terminal 500 sends automatic playback setting information, including the user management ID, a push notification token, and information indicating the automatic playback method selected by the user on the setting screen for the automatic playback method of the emergency broadcast, to the automatic startup management server 200 when setting up to use the application. The control device 203 of the automatic startup management server 200 records the automatic playback setting information received from the user terminal 500 in the storage medium 203. However, the automatic playback setting information may also be recorded in the memory of the user terminal 500 and managed within the application, in which case the user management ID is not required. Note that in this case, there is no need to register the user in advance, so this method is effective when it is desired to allow the user to use the emergency broadcast playback system 10 anonymously.
[0109] (2) In the embodiment described above, the control device 202 of the automatic startup management server 200 determines whether automatic startup is being managed based on the automatic playback setting information described above, and if it determines that automatic startup is being managed, it includes the type of automatic playback in the push notification payload. The control device 503 of the user terminal 500 checks the contents of the push notification payload when it receives a push notification of the start of an emergency broadcast from the push notification distribution server 600, and controls the automatic startup of the application according to the contents of the payload. However, if the automatic playback setting information is recorded in the memory of the user terminal 500 and managed within the application, the control device 503 only needs to control the automatic startup of the application according to the settings stored within the application.
[0110] (3) In the embodiments described above, an example was given of managing the automatic startup of an application on the user terminal 500 according to whether the emergency broadcast is set to "autoplay" or "do not autoplay" by the user. However, even if the user has set it to "do not autoplay", in the case of a more urgent emergency broadcast, the automatic startup management server 200 may be able to forcibly autoplay it. If automatic playback is to be forced, for example, it is sufficient to set it to autostart automatically regardless of whether it is a weekday or holiday, and to set the maximum volume to the standard setting.
[0111] (4) In the above-described embodiment, when the user sets the automatic playback of emergency broadcasts to "Automatically play," an example was described in which the user sets the volume during automatic playback of emergency broadcasts, the days and times when automatic playback of emergency broadcasts will be performed, the type of emergency broadcast to be automatically played, and the method for stopping automatic playback after the emergency broadcast has ended on the setting screen for the automatic playback method of emergency broadcasts. Of these, the volume during automatic playback of emergency broadcasts and the days and times when automatic playback of emergency broadcasts will be performed may be combined to set the volume during playback. This allows the user to set the playback volume in a way that suits their lifestyle, for example, to use the normal terminal volume normally and the maximum volume when going to sleep.
[0112] (5) In the embodiments described above, an example of delivering push notifications using a push notification token list was explained, but the method of delivering push notifications is not limited to this. For example, a method of delivery using a known topic may be used. In this method, by associating a push notification token with a topic, it becomes possible to deliver push notifications using the topic name and push notification payload.
[0113] Furthermore, the present invention is not limited in any way to the configurations of the embodiments described above, as long as the characteristic functions of the present invention are not impaired. Configurations combining the above embodiments with several modifications are also possible. [Explanation of Symbols]
[0114] 10. Emergency Broadcast Playback System 100 Streaming Broadcast Receiving Servers 101 Connection Interface 102 Control device 103 Storage medium 200 Automatic Startup Management Server 201 Connection Interfaces 202 Control Unit 203 Storage medium 300 Simulcast redistribution servers 301 Connection Interface 302 Control device 303 Storage medium 400 Interrupt Broadcast Server 401 Connection Interface 402 Control Unit 403 Storage medium 500 user terminals 501 Touch Panel 502 Communication Module 503 Control device 504 Speaker 600 push notification delivery servers
Claims
1. A streaming broadcast receiving means for receiving streaming broadcasts transmitted from a broadcasting station, An emergency broadcast detection means for detecting that an emergency broadcast has started during a streaming broadcast received by the aforementioned streaming broadcast receiving means, When the start of an emergency broadcast is detected by the emergency broadcast detection means, a push notification instruction means instructs the push notification distribution server to distribute a push notification to the user's terminal, The system includes a simulcast redistribution means that converts the streaming broadcast received by the streaming broadcast receiving means into a format suitable for playback on the user terminal and redistributes the simulcast, The aforementioned user terminal is An emergency broadcast playback system characterized by having a playback means that, upon receiving a push notification from the push notification distribution server, displays a playback screen for playing the simulcast and receives and plays the simulcast.
2. In the emergency broadcast playback system according to claim 1, The emergency broadcast playback system is characterized in that, when the playback means receives a push notification from the push notification distribution server and determines that it is set to automatically play when an emergency broadcast starts, it displays a playback screen for playing the simulcast, receives the simulcast, and plays it back.
3. In the emergency broadcast playback system according to claim 1, An emergency broadcast playback system characterized in that, when the playback means receives a push notification from the push notification distribution server, it determines that the system has been set in advance by the user to automatically play when an emergency broadcast starts, and when it determines that the type of emergency broadcast is one that can be automatically played, and that the current time is a day and time when automatic playback is performed based on the current date and time, it displays a playback screen for playing the simulcast, receives the simulcast, and plays it at a volume specified in advance by the user.
4. In the emergency broadcast playback system according to any one of claims 1 to 3, The playback means is characterized in that, if the user terminal is in a sleep state, it wakes the terminal from sleep before displaying the playback screen.
5. In the emergency broadcast playback system according to any one of claims 1 to 3, The emergency broadcast playback system is characterized in that, after the playback means has started playback of the simulcast, it stops playback of the simulcast based on a predetermined automatic playback stop method.
6. In the emergency broadcast playback system according to any one of claims 1 to 3, An emergency broadcast playback system characterized by further comprising an interruption broadcasting means for inserting an interruption broadcast into a simulcast redistributed by the aforementioned simulcast redistribution means.
7. An emergency broadcast playback system comprising a streaming broadcast receiving server that receives streaming broadcasts transmitted from a broadcasting station, an automatic startup management server that manages the automatic startup of applications on user terminals owned by users, a simulcast redistribution server that redistributes simulcasts, and the user terminals connected via a communication line, The aforementioned streaming broadcast receiving server is A streaming broadcast receiving means for receiving streaming broadcasts transmitted from a broadcasting station, An emergency broadcast detection means for detecting that an emergency broadcast has started during a streaming broadcast received by the aforementioned streaming broadcast receiving means, The system includes an instruction means that, when the start of an emergency broadcast is detected by the emergency broadcast detection means, instructs the automatic startup management server to notify the user terminal that an emergency broadcast has started. The aforementioned automatic startup management server is: The system includes a push notification instruction means that, upon receiving instructions from the streaming broadcast receiving server to notify the user terminal that an emergency broadcast has started, instructs the push notification distribution server to distribute a push notification to the user terminal to automatically launch the application. The simulcast redistribution server includes a simulcast redistribution means that receives the streaming broadcast received by the streaming broadcast receiving server, converts it into a format suitable for playback on the user terminal, and redistributes the simulcast. The aforementioned user terminal is An emergency broadcast playback system characterized by having a playback means that, upon receiving a push notification from the push notification distribution server, displays a playback screen for playing the simulcast and receives and plays the simulcast.
8. In the emergency broadcast playback system according to claim 7, The emergency broadcast playback system is characterized in that, when the playback means receives a push notification from the push notification distribution server and determines that it is set to automatically play when an emergency broadcast starts, it displays a playback screen for playing the simulcast, receives the simulcast, and plays it back.
9. In the emergency broadcast playback system according to claim 7, An emergency broadcast playback system characterized in that, when the playback means receives a push notification from the push notification distribution server, it determines that the system has been set in advance by the user to automatically play when an emergency broadcast starts, and when it determines that the type of emergency broadcast is one that can be automatically played, and that the current time is a day and time when automatic playback is performed based on the current date and time, it displays a playback screen for playing the simulcast, receives the simulcast, and plays it at a volume specified in advance by the user.
10. In the emergency broadcast playback system according to any one of claims 7 to 9, The playback means is characterized in that, if the user terminal is in a sleep state, it wakes the terminal from sleep before displaying the playback screen.
11. In the emergency broadcast playback system according to any one of claims 7 to 9, The emergency broadcast playback system is characterized in that, after the playback means has started playback of the simulcast, it stops playback of the simulcast based on a predetermined automatic playback stop method.
12. In the emergency broadcast playback system according to any one of claims 7 to 9, An emergency broadcast playback system characterized by further comprising an interrupt broadcast server that inserts interrupt broadcasts into the simulcast broadcasts redistributed by the aforementioned simulcast redistribution server.
Citation Information
Patent Citations
Information distribution system
JP2024021237A