WO2016185821A1

WO2016185821A1 - Transmission device, transmission method, reception device, and reception method

Info

Publication number: WO2016185821A1
Application number: PCT/JP2016/061284
Authority: WO
Inventors: 北里　直久; 義治出葉
Original assignee: ソニー株式会社
Priority date: 2015-05-19
Filing date: 2016-04-06
Publication date: 2016-11-24

Abstract

Provided are a transmission device and a transmission method whereby emergency information is transmitted and a reception device and a reception method whereby emergency information is received. A broadcasting station adds information indicating an emergency application including target area information, to an MH-AIT and transmits same. When information indicating an emergency application appears in an MH-AIT, and only if within the specified target area, a receiver ends or hides a running application and starts up the emergency application. In addition, the receiver stops the running emergency application if the information indicating the emergency application disappears from the MH-AIT while the emergency application is running.

Description

Transmitting apparatus, transmitting method, receiving apparatus, and receiving method

The technology disclosed in this specification relates to a transmission apparatus and transmission method for transmitting emergency information, and a reception apparatus and reception method for receiving emergency information.

Communicating emergency information promptly for various disasters (earthquakes, tsunamis, storms, etc.) and incidents is one of the responsibilities of broadcasting. Standardization of digital broadcasting services is being promoted in countries around the world including Europe, the United States, and Japan, and technical support functions related to the transmission of emergency information are also stipulated. For example, a broadcast service (EWS: Emergency Warning System) that is performed by automatically starting a broadcast receiver in a standby state is known (see, for example, Patent Document 1).

JP 2007-281957 A JP 2014-110154 A

An object of the technology disclosed in the present specification is to provide a transmitting device and a transmitting method for transmitting emergency information, and a receiving device and a receiving method for receiving emergency information.

The technology disclosed in the present specification has been made in consideration of the above-mentioned problems, and the first aspect thereof is
A transmitter for transmitting the application;
A control information transmission unit that adds emergency application information indicating an emergency application and transmits application control information;
It is the transmitter which comprises.

According to the second aspect of the technology disclosed in this specification, the control information transmission unit of the transmission device according to the first aspect transmits the emergency application information to the application only during an emergency notification period in which emergency information should be notified. It is configured to be added to the control information.

According to the third aspect of the technology disclosed in the present specification, the control information transmission unit of the transmission device according to the first aspect is configured to include information related to a target area in the emergency application information and transmit the information. ing.

According to the fourth aspect of the technology disclosed in the present specification, the control information transmission unit of the transmission device according to the first aspect indicates whether or not it is necessary to recover to the state of the previous application after the emergency application ends. The information to be transmitted is included in the emergency application information and transmitted.

According to a fifth aspect of the technique disclosed in this specification, the control information transmission unit of the transmission device according to the first aspect transmits the application control information that specifies automatic activation of the emergency application. It is configured.

In addition, the sixth aspect of the technology disclosed in this specification is:
A send step for sending the application;
A control information transmission step for transmitting application control information by adding emergency application information indicating an emergency application,
Is a transmission method.

In addition, the seventh aspect of the technology disclosed in this specification is:
A receiver for receiving the application;
A control information receiver for receiving application control information;
A control unit that controls processing of the application based on the application control information;
Comprising
The control unit controls processing of an emergency application indicated by emergency application information included in the application control information.
It is a receiving device.

According to an eighth aspect of the technology disclosed in this specification, the control unit of the reception device according to the seventh aspect provides the emergency application in response to the emergence of the emergency application information in the application control information. Is configured to attempt to start.

According to the ninth aspect of the technology disclosed in this specification, when the target area is specified by the emergency application information of the receiving device according to the seventh aspect, or the target area is specified by the emergency application information Only if not, the controller is configured to activate the emergency application.

According to the tenth aspect of the technology disclosed in this specification, when the emergency application information of the receiving device according to the seventh aspect indicates that the recovery to the state of the previous application is instructed after the emergency application ends. The control unit is configured to activate the emergency application after maintaining the state of the previous application.

According to an eleventh aspect of the technology disclosed in this specification, the reception unit of the reception device according to the seventh aspect receives a video of a broadcast program, and the control unit captures the video of the broadcast program. It is configured to display the screen and information specified by the emergency application.

According to a twelfth aspect of the technology disclosed in this specification, the control unit of the reception device according to the seventh aspect provides the emergency application in response to the emergency application information disappearing from the application control information. Is configured to stop.

According to a thirteenth aspect of the technology disclosed in this specification, the control unit of the receiving device according to the twelfth aspect is designated to be automatically activated by the application control information when the emergency application is stopped. Configured to launch an application.

According to the fourteenth aspect of the technology disclosed in this specification, the control unit of the reception device according to the thirteenth aspect is configured to recover the state of the previous application that has been held.

Further, the fifteenth aspect of the technology disclosed in this specification is:
A receiving step for receiving the application;
A control information receiving step for receiving application control information;
A control step for controlling processing of the emergency application indicated by the emergency application information included in the application control information;
Is a receiving method.

According to the technology disclosed in this specification, it is possible to provide a transmission device and a transmission method that can transmit a data broadcast application that notifies emergency information.

In addition, according to the technology disclosed in the present specification, it is possible to provide a receiving device and a receiving method capable of notifying a user (viewer) of emergency information by starting a data broadcasting application received during an emergency notification period. Can do.

In addition, the effect described in this specification is an illustration to the last, and the effect of this invention is not limited to this. In addition to the above effects, the present invention may have additional effects.

Other objects, features, and advantages of the technology disclosed in the present specification will become apparent from a more detailed description based on embodiments to be described later and the accompanying drawings.

FIG. 1 is a diagram schematically illustrating a configuration example of a digital broadcasting system 10. FIG. 2 is a diagram showing a protocol stack 200 in the digital broadcasting system 10 using the MMT method. FIG. 3 is a diagram showing an image of a broadcast signal 300 according to the MMT method. FIG. 4 is a diagram showing a mechanism for designating each asset related to the broadcast service from the MP table in the PA message. FIG. 5 is a diagram for explaining a mechanism for acquiring a file related to a data broadcast transmitted by MMT. FIG. 6 is a diagram illustrating an example syntax 600 of an M2 section message. FIG. 7 is a diagram illustrating a syntax example 700 of MH-AIT. FIG. 8 is a diagram illustrating an example syntax 800 of an emergency application descriptor. FIG. 9 is a diagram showing a syntax 900 of a region designator designated by a prefecture. FIG. 10 is a diagram illustrating a syntax example 1000 of a transmission protocol descriptor. FIG. 11 is a diagram illustrating a configuration example of the broadcast transmission system 11. FIG. 12 is a diagram illustrating a configuration example of the receiver 12 that receives a broadcast signal from the broadcast transmission system 11. FIG. 13 is a diagram illustrating screen display control of emergency information using an emergency application. FIG. 14 is a diagram illustrating an example of regional filtering for an emergency application. FIG. 15 is a diagram illustrating an emergency application switching scenario. FIG. 16 is a flowchart illustrating an example of a procedure for processing an emergency application.

Hereinafter, embodiments of the technology disclosed in this specification will be described in detail with reference to the drawings.

A. One of the responsibilities of the requirement broadcasting of the technology disclosed in this specification is to promptly transmit emergency information for various disasters and incidents. The digital broadcasting standard also defines a technical support function for transmitting emergency information. However, the present applicant considers that the current broadcasting service does not sufficiently play a role in the notification of emergency information.

Urgent information has regional characteristics. In the event of an emergency, there is a demand for prompt notification of emergency information by subtitles, etc., on a regional basis. However, when a normal broadcast screen such as a TV program video or a data broadcast display overlaps with subtitles, emergency information is difficult to see or becomes inconspicuous, so it does not function effectively.

In recent years, TVs have become larger and more detailed. Coupled with this trend, the number of large screens will be divided into multiple and applications other than normal broadcast screens (TV program and data broadcast display) (games, content playback screens, etc.) will be displayed simultaneously. It is expected to come. Even when an emergency notification is made by a broadcast service on a screen in which various displays are mixed, there is a possibility that it will not stand out.

The Applicant lists the following (1) to (3) as requirements for emergency notification in broadcasting services.

(1) When making an emergency notification in a broadcast service, even if a display other than the broadcast screen is displayed on the TV screen, the broadcast screen is automatically switched to be displayed on the full screen of the TV screen (broadcast full screen display). control). In an emergency, viewers can be alerted by displaying the broadcast screen in full screen. In addition, after the emergency notification is finished, the TV screen returns to the state before the emergency notification.
(2) The operation of switching to the full screen display of (1) is performed only in the area targeted for emergency notification.
(3) When an emergency notification is made with a specific broadcast service (specifically, when the same provider provides a broadcast service with a plurality of broadcast channels and an emergency notification is made with one of the broadcast services), TV reception Even if the machine is receiving other broadcast services, the service is switched to the service that provides emergency notification. It is preferable to confirm the user (viewer) when switching the service.

In addition, the applicant lists the following (4) to (6) as requirements for emergency notification with captions in the broadcasting service.

(4) The emergency information subtitles are promptly displayed at an easily viewable position on the TV screen.
(5) Subtitles for emergency information can be designated to be displayed at a position that does not overlap with a normal broadcast screen (display of TV program video and data broadcast).
(6) Subtitles for emergency information are displayed only in the area targeted for emergency notification.

In this specification, the technology related to the broadcast service for realizing the above requirements (1) to (6) for performing the emergency notification by the broadcast full screen display and the emergency subtitle will be disclosed below.

For convenience, an embodiment in which the technology disclosed in this specification is applied to a broadcasting system that employs the MMT (MPEG Media Transport) system for media transmission will be described.

B. System Configuration As a next-generation digital broadcasting system, an ultra-high resolution TV broadcasting standard based on the MMT system standardized as a new media transport system in MPEG is being studied. The MMT system can be easily used in a combination of different transmission paths, and can be used in common for a plurality of broadcast and communication transmission paths.

In the MMT TV broadcasting standard, stream media of broadcast programs such as video, audio, and subtitles are transmitted in a Timed MPU (Media Processing Unit) format, while data broadcasting applications are transmitted in a non-timed MPU format. The transmission method is also defined. In the MMT data broadcasting system, the broadcasting station performs signaling (notification) of MMT-SI (Signaling Information), which is control information related to the broadcast service (see, for example, Patent Document 2).

FIG. 1 schematically shows a configuration example of the digital broadcasting system 10. The illustrated digital broadcast system 10 includes a broadcast transmission system 11 and a receiver 12.

The broadcast transmission system 11 applies the MMT system for transmission of broadcast signals, and transmits each component constituting the broadcast service as an IP (Internet Protocol) packet. Specifically, the broadcast transmission system 11 puts the video signal and audio signal codes of a broadcast program, content (data broadcast application, etc.) related to the broadcast program, and subtitle signals into an MMTP payload into an MMTP packet. Further, it is converted into an IP packet and transmitted in the form of a TLV (Type Length Value) packet on the broadcast transmission path. Here, components related to the broadcast program main body such as video, audio, and subtitles are timed media. In addition, content, that is, a data broadcasting application encoded in HTML (Hyper Text Transfer Protocol) 5 format or the like is non-timed media.

The broadcast transmission system 11 also performs MMT-SI signaling, which is control information related to a broadcast service that distributes timed and non-timed media. The MMT-SI includes a message, a table, and a descriptor. The table is transmitted as a container for messages. Some parameters shown in messages and tables are described in descriptor format.

On the other hand, the receiver 12 receives the TLV packet sent from the broadcast transmission system 11 through the broadcast transmission path. The receiver 12 then decodes transmission media such as video, audio, and subtitles from the received packet and presents images and audio. Further, when the receiver 12 acquires each data file for data broadcasting from the received packet, the receiver 12 starts an application engine such as an HTML browser and displays the data broadcast linked to the broadcast program and the video of the TV program. Display in part or all of the screen area.

The receiver 12 also receives MMT-SI that is control information related to the broadcast service. Based on the MMT-SI, the receiver 12 performs reception control of transmission media such as video, audio, captions, and data broadcasting, and output (display, audio output) control on the receiver 12.

FIG. 2 shows a protocol stack 200 in the digital broadcasting system 10 using the MMT method.

One broadcast service is composed of video 201, audio 202, subtitle 203, application 204, and content / download 205 components. The video 201 is encoded 211 in the HEVC (High Efficiency Video Coding) format, the audio 202 is encoded 212 in the AAC (Advanced Audio Coding) format, and the subtitle 203 is subtitle encoded 213. The application 204 includes EPG (Electric Program Guide), but is encoded 214 in, for example, HTML5 format.

On the MMT layer 220, these timed media and non-timed media encoding components 211 to 214 are converted into the MMTP packet in the MPU format and carried on the MMTP payload. In addition, MMT-SI 221 which is control information related to MMT which is a media transport system (indicating the configuration of a broadcast program) is also put into an MMTP packet on the MMTP payload. Details of the control information MMT-SI related to the MMT will be described later. There are four types of data transmission methods 215 for the content download 205, that is, a caption / text super transmission method, an application transmission method, an event / message transmission method, and a general-purpose data transmission method.

In the UDP (User Datagram Protocol) / IP layer 110, the MMTP packet is converted into an IP packet. An NTP (Network Time Protocol) packet 206 including information on the current time for timed media is also converted into an IP packet. Further, these IP packets are converted into TLV packets in the TLV layer 120 and transmitted through the broadcast transmission path 250 which is the lowermost physical layer. A TLV-SI 241 related to a TLV multiplexing format for multiplexing IP packets is also converted into a TLV packet and transmitted through the broadcast transmission path 250. The transmission slot in which the TLV packet is multiplexed is specified by using TLV stream identification information (TLV_stream_id) from a TMCC (Transmission and Multiplexing Configuration Control) signal 251 of the transmission path.

C. Configuration of Broadcast Signal FIG. 3 shows an image of a broadcast signal 300 transmitted from the broadcast transmission system 11 to the broadcast transmission path according to the MMT method.

The broadcast signal of one service is composed of timed media related to the main part of a broadcast program such as video, audio, and subtitles, and non-timed media such as data broadcasting. Corresponding to broadcast programs). Media data obtained by encoding these media is converted into MMTP packets in the MPU format and transmitted as IP packets. Also, MMT-SI, which is control information related to MMT, which is a media transport system (indicating the configuration of a broadcast program), is also transmitted in IP packets. These IP packets are transmitted as TLV streams in the form of TLV packets on the broadcast transmission path. Signaling information (TLV-SI) related to the TLV multiplexing format for multiplexing IP packets is also transmitted in the TLV packet format.

In the MMT method, it is easy to use each piece of media data constituting one broadcast service with a combination of different transmission paths. In the example shown in FIG. 3, as the broadcast signal 300, MMT transmission paths 301 to 305 for each type of data such as video, audio, caption, data broadcast, and control information (MMT-SI) related to broadcast service are used. Each MMT transmission line corresponds to one IP data flow. The IP data flow referred to here is that the values of the five types of fields of the IP header and the UDP header in the source IP address, destination IP address, IP header protocol type, source port number, and destination port number are all the same. Is a set of IP packets.

One broadcasting service can be said to be a “package” composed of a plurality of different types of assets such as video, audio, captions, and data broadcasting applications. The “package” referred to here is a logical set of media data transmitted using the MMT transmission path. “Assets” have a corresponding relationship with components (video assets correspond to video components, audio assets correspond to audio components, and data file assets for data broadcasting applications correspond to data file components. Corresponding to). Each asset is identified by unique asset identification information (asset_id).

Each asset is composed of a set (logical group) of one or more MPUs sharing the same asset identification information. MPU is a format that is a transmission unit in the MMT system. Each MPU is specified by asset identification information and the sequence number of the MPU on the corresponding transmission path. Further, the MMT transmission path for transmitting each medium can be identified by asset identification information.

Each MPU related to the same broadcast service is transmitted on a dedicated ES (Elementary Stream), that is, MMT transmission paths 301 to 305 to each asset in the package, that is, the broadcast signal 300. In the example shown in FIG. 3, the transmission path 301 transmits an MMTP packet of an encoded video signal composed of an MPU logical group having common asset identification information for a video signal. Similarly, an MMT packet of an encoded audio signal composed of an MPU logical group having common asset identification information for audio signals is transmitted on the transmission path 302, and has common asset identification information for subtitle signals on the transmission path 303. An MMTP packet of an encoded subtitle signal composed of an MPU group is transmitted, and an MMT packet of an encoded application composed of an MPU logical group having common asset identification information for data broadcasting applications is transmitted on the transmission paths 304-1 and 304-2. Is done.

In a single package (broadcast program), a plurality of assets having the same type (that is, having different asset identification information) may be transmitted. For example, in the case where a data broadcast application is provided independently from two or more delivery segments for the same broadcast program, different asset identification information is allocated and transmitted for each delivery segment. More specifically, a program-linked data broadcasting application linked to a broadcast program provided from a key station that produced the program, and a program non-linked data not linked to a broadcast program provided from a local station that distributes the program. Broadcast applications (for example, weather forecasts and news) are usually assigned different asset identification information as different assets, and are transmitted as different MPU logical groups on different MMT transmission paths. In the example shown in FIG. 3, transmission paths 304-1 and 304-2 are drawn for two data broadcasting applications to which different asset identification information is allocated.

In addition, the MMT method can be used in common for a plurality of broadcast and communication transmission paths. For example, non-timed media such as data broadcasting (HTML5 document, etc.) is transmitted together with timed media of the same broadcasting service using the transmission paths 304-1 and 304-2 of the broadcast signal 300 as shown in FIG. In addition, it can be provided via a communication transmission path (not shown) such as an IP network.

The transmission path 305 is used for signaling in the MMT system, that is, for transmitting MMT-SI, which is control information indicating information related to the configuration of the MMT package and the broadcast service. On the transmission line 305, an MMT message including MMT-SI is converted into an MMTP packet and repeatedly transmitted by the carousel method. In FIG. 3, the illustration of the transmission line for TLV-SI is omitted.

MMT-SI has messages, tables, and descriptors. Examples of the MMT message transmitted through the transmission path 305 include a PA (Package Access) message 310, an M2 section message 320, and a data transmission message 330.

The PA message 310 is control information indicating the configuration of a broadcast program and the like, and is a container that stores an MP (MMT Package) table 311 that describes information that configures a package such as an asset list and its position.

The MP (MMT Package) table 311 is a table indicating basic reception control information for each broadcast service, and specifically provides information constituting the package, such as an asset list and asset location information. The MP table 311 includes MPT descriptors such as application service descriptors. The application service descriptor indicates location information of control information necessary or important for the operation of the data broadcasting application (for example, location information of each M2 section message that transmits a data transmission message, MH-AIT, and EMT, respectively).

The PA message 310 is an entry point of the broadcast service, and fixed packet identification information (for example, 0x0000) is assigned to the MMTP packet that transmits the PA message 310. Therefore, on the receiver side, the PA message 310 can be acquired by directly specifying the fixed packet identification information on the MMT transmission path 304. Then, with reference to the MP table 311 transmitted by the PA message 310, each asset (video, audio, caption, data broadcast location information) constituting the package (broadcast program) can be indirectly specified.

Although omitted in FIG. 3, examples of tables stored in the PA message 310 include a PL (Package List) table (PLT) and an LC (Layout Configuration) table (LCT) in addition to the MP table. PLT indicates a list of IP data flows and packet IDs for transmitting PA messages of MMT packages provided as broadcasting services, and IP data flows for transmitting IP services. The LCT is used to associate layout information for presentation with a layout number. The PA message is a container that can store up to three tables: an MP table, a PL table, and an LC table.

The M2 section message 320 is a message that transmits the section extension format of MPEG-2 Systems, and is a container that stores the section format signaling table one by one. In the M2 section message 320, tables such as an MH-AIT (Application Information Table) 321 and an EMT (Event Message Table) 322 are stored one by one.

The MH-AIT 321 is a table for designating dynamic control information related to an application and additional information necessary for execution. Specifically, the MH-AIT 321 is a method for processing each data broadcast application (file data) sent through the MMT transmission path. Specify the location information (URL: Uniform Resource Locator) of each data broadcasting application (such as the activation state applied to the application). As an application processing method, AUTOSTART (AS) indicating automatic start of the application, PRESENT (PR) indicating that the application is in an executable state, KILL indicating the end of the application, acquisition and holding (pre-cache) of the application The PREFETCH (PF) shown can be mentioned.

The EMT 322 is a signaling table used for the event message transmission method, and stores information (event message descriptor) regarding the event message (synchronous / asynchronous message from the broadcasting station to the application on the receiver). The event / message transmission system provides a means for sending message information from a broadcasting station to a data broadcasting application operating on a receiver immediately or at a specified time.

The data transmission message 330 is a message for transmitting control information related to transmission of the data broadcasting application. The data transmission message 330 includes a data directory management table (Data Directory management Table: DDMT) 331, a data asset management table (Data Asset Management Table: DAMT) 332, a data content management table (Data Content Configuration Table 33DC). This is a container that can store up to three tables at the same time. The data directory management table and the data asset management table are indispensable for the data broadcasting service, but the data / content management table is optional.

Here, the data directory management table 331 is a table for managing the data broadcast application in a directory unit (in other words, a production unit of the data broadcast application). The table describes the directory structure for items (directories and subdirectories and files included in a directory) included in one package, so that the file structure of the application and the structure for file transmission can be separated. it can. The table shows the correspondence between the path name of each node, such as a directory or file, and the node tag that identifies each node in the data transmission message.

The data / asset management table 332 is a table for managing the data broadcasting application in units of assets, and describes version information for each MPU including the configuration of the MPU in the asset. Specifically, the table shows download identification information of each component, and a node tag and node on the MMT transmission path that identify a node (file or directory) included in each MPU that transmits the component in the data transmission message. The correspondence with the item identification information to identify is shown.

The data / content management table 333 is a table for managing a data broadcasting application for each presentation unit (PU). The table shows presentation unit identification information for identifying a data broadcasting application for each presentation unit, and a node tag for identifying a node (file or directory) included in each presentation unit in a data transmission message. In addition, the table can include link destination presentation unit identification information for identifying a presentation unit linked to the presentation unit, and information on cache control of each presentation unit. Can be used for flexible and effective cache control.

In the transmission system of the data broadcasting application by MMT, by utilizing the above three kinds of signaling tables 331 to 333 transmitted by the data transmission message, the transmission data structure of the file unit and the directory structure in contents (data broadcasting application) production Can independently represent the data structure of usage units such as application units and presentation units. The configuration of each of the signaling tables 331 to 333 is defined by ARIB STD B-60.

• Packet identification information of messages and tables transmitted as MMT-SI may be fixed or indirectly specified from other tables. Among these, the PA message is an entry point of the broadcast service, and fixed packet identification information (for example, 0x0000) is assigned. The MP table transmitted by the PA message indicates asset identification information and location information of each asset (video, audio, caption, data broadcasting application, etc.) constituting the package (broadcast program). Therefore, the receiver side can acquire the PA message by designating the fixed packet identification information on the MMT transmission path. Then, referring to the MP table transmitted in the PA message, as shown in FIG. 4, each asset (video, audio, caption, data broadcasting application, etc.) related to the broadcasting service and other signaling messages are indirectly Can be specified.

In MH-AIT, location information of a data broadcasting application is described in a URL format, in other words, a path name composed of a combination of a directory node name and a file name. The asset path name can be converted into identification information (packet identification information) on the MMT transmission path using the data directory management table and the data asset management table transmitted in the data transmission message. A mechanism for acquiring a data broadcasting application from the MMT transmission path is described in detail in, for example, Japanese Patent Application No. 2014-250279 already assigned to the present applicant. In this specification, a mechanism for acquiring data broadcast application items multiplexed in the same IP data flow on the broadcast signal receiver side will be briefly described with reference to FIG.

The receiver refers to the application information loop in the MH-AIT transmitted in the M2 section message, and detects an application to be started (for example, an application whose automatic start is specified by the application control code). be able to. In addition, the receiver can acquire application location information, that is, a path name, from a transmission protocol descriptor (described later) arranged in the MH-AIT. As indicated by reference numeral 501, the node tag of the file corresponding to the specified path name can be obtained from the data directory management table in the data transmission message.

Then, as indicated by reference numeral 502, the component tag of the asset to which the item having the node tag obtained in the data directory management table is also transmitted from the data asset management table in the data transmission message, download identification Information, MPU sequence number, and item identification information can be obtained.

Further, when the location information of the asset having the component tag obtained in the data asset management table is acquired from the MP table as indicated by the reference number 503, the corresponding file is actually stored as indicated by the reference number 504. The data asset to be transmitted can be identified.

Then, within the identified data asset, the file identification corresponding to the carousel is repeated using the download identification information obtained from the data asset management table and the download identification information described in the header area of the MMTP packet for transmitting the item. The unit of transmission can be uniquely identified. As indicated by a reference number 505, an item having an MPU sequence number and item identification information obtained from the data / asset management table among items repeatedly transmitted can be designated as a desired file.

D. Outline of the technology disclosed in this specification In the technology disclosed in this specification, notification of emergency information is performed using a data broadcasting application. The data broadcast application used for notifying emergency information is also referred to as “emergency application” below.

When transmitting an emergency application during an emergency notification period, a broadcaster (broadcast station) adds and transmits information indicating an emergency application including target area information to MH-AIT specifying application control information. The MH-AIT is a signaling table that is transmitted in units of broadcast services using M2 section messages as containers (described above).

On the receiver side, when information indicating an emergency application appears in the MH-AIT, the active application is terminated or hidden and the emergency application indicated by the MH-AIT is started only in the designated target area. To do.

Also, the broadcaster (broadcast station) deletes the information indicating the emergency application from the MH-AIT after the emergency notification period.

On the receiver side, if the information indicating the emergency application disappears from the MH-AIT while the emergency application is in operation, the active emergency application is stopped and the application for which automatic activation is designated by the MH-AIT at that time To do. Alternatively, the receiver makes visible the application that made the emergency application invisible at startup.

MH-AIT is a signaling table transmitted in units of broadcast services using M2 section messages as containers. FIG. 6 shows an example syntax 600 for an M2 section message. The M2 section message is a signaling message used for transmitting the section extension format of the MPEG-2 System as it is. Hereinafter, the meaning of each parameter of the M2 section message will be described.

Message_id (message identification) is a 16-bit fixed value for identifying the M2 section message in various signaling information, and is set to 0x8000. version (version) is an 8-bit integer parameter indicating the version of the M2 section message. The length (message length) is a 16-bit parameter indicating the size of the M2 section message counted in bytes immediately after this field.

Table_id (table identification) is an area used for identifying the table to which the section belongs. The section_syntax_indicator (section syntax instruction) is set to “1” indicating the extended format. Section_length (section length) is an area in which the byte length of data following the section length area is written. The table_id_extension (table identification extension) is an area for extending table identification. version_number (version number) is an area in which the version number of the table is written. The current_next_indicator (current next instruction) is set to “1” when the table is currently usable, and is set to “0” when the table is currently unusable and next valid.

Section_number (section number) is an area in which section numbers constituting the table are written. The last_section_number (last section number) is an area in which the last section number constituting the table is written. In a signaling data loop indicated by reference numeral 601, information constituting a table such as MH-AIT and EMT is described in byte units (signaling_data_bytes). At the end of the message, the ITU-T recommendation H.264. A cyclic redundancy code CRC32 (CRC) according to 222.0 is added.

FIG. 7 shows a syntax example 700 of MH-AIT, which is one of the signaling tables transmitted in the M2 section message. Hereinafter, the meaning of each parameter of MH-AIT will be described.

Table_id (table identification) is an 8-bit fixed value that identifies the application information (AI) table in various signaling information, and is 0x89 in this embodiment. The section_syntax_indicator (section syntax instruction) is a 1-bit field and is always “1”. sectoin_length (section length) is a 12-bit field and defines the byte length of the section from the section length field to the end of the section including CRC32. This value shall not exceed 4093 (0xEFD in hexadecimal).

Application_type (application type) is a 16-bit field indicating the type of application to be controlled by the MH-AIT. Application type assignments shall be in accordance with Table 1 below.

Version_number (version number) is a 5-bit field and is a partition number of the sub-table. version_number is the version number of the MH-AIT, and is incremented by +1 when there is a change in the information in the sub-table. When the value of the version number becomes “31”, it returns to “0” next. The current_next_indicator (current next instruction) is always “1”. The section_number (section number) is an 8-bit field and represents a section number. The section number of the first section in the subtable is 0x00. The section number is incremented by +1 each time a section with the same table identification and application type is added. The last_section_number (last section number) is an 8-bit field that defines the last section number in the subtable to which the section belongs.

Common_descriptor_length (common descriptor loop length) is an 8-bit field, indicating the byte length of the subsequent descriptor, and the descriptor (common descriptor) is written in a series of areas consisting of the common loop for the number of bytes. The common descriptor area applies to all applications in the AIT subtable.

Application_loop_length is an area in which the number of application information included in the MH AI table is written. Then, application information loops are arranged by the number indicated by application_loop_length.

In one application information loop, application_identifier (application identifier), application_control_code (application control code), and application information are arranged.

Here, application_identifier (application identifier) is a parameter for identifying an application. The application_control_code (application control code) is an 8-bit field that defines a control code for controlling the state of the application. The semantics of this field depend on the application type value. Table 2 shows the semantics of the application control code when it does not depend on the application type.

Application_descriptor_loop_length (application information descriptor loop length) indicates the byte length of the application information descriptor, and a descriptor (application information descriptor) is written in the application information descriptor area 701 composed of loops corresponding to the number of bytes. The application information descriptor in the descriptor area 701 is different from the above common descriptor and is applied only to the application specified by application_identifier. In the application information loop, for example, an MH-application descriptor and an MH-transmission protocol descriptor are arranged.

In this embodiment, it is assumed that an emergency application descriptor indicating an emergency application is newly arranged in the application information descriptor area 701 of the application information loop. The emergency application descriptor indicates that the corresponding application (that is, the application specified by application_identifier) is an emergency application, and describes information related to the target area of the emergency application. In addition, by designating the application control code of the application information loop of the emergency application to “autostart”, the automatic screen switching described above as the emergency notification requirement (1) can be realized. Details of the emergency application descriptor will be described later.

And at the end of the table, ITU-T recommendation H.264. A cyclic redundancy code CRC32 (CRC) according to 222.0 is added.

FIG. 8 shows a syntax example 800 of an emergency application descriptor arranged as one of application information descriptors in the MH-AIT. Hereinafter, the meaning of each parameter of the emergency application descriptor will be described.

Descriptor_tag indicates a 16-bit fixed value for identifying that the descriptor is an event message descriptor. Descriptor_length is an 8-bit field indicating the byte length from immediately after this field to the end of the descriptor.

The region_filtering_flag (region filter flag) indicated by reference number 801 is a flag that specifies whether or not to perform region filtering on the emergency application descriptor. When region_filtering_flag is 1, the target area of the emergency application descriptor is specified by each parameter region_spec_type and target_region_spec in the subsequent IF statement (described later). With the region_filtering_flag, it is possible to realize the emergency notification operation limited to only the area targeted for the emergency notification described above as the emergency notification requirement (2).

“Previous_app_recovery_flag” indicated by reference number 802 is a flag that indicates whether or not it is necessary to restore the state of the previous application after the emergency application ends. The flag value “1” instructs to return to the state of the previous application after the emergency application ends, and the flag value “0” instructs unconditional termination of the previous application. On the receiver side, if previous_app_recovery_flag = 1 is specified, the previous state (the state of the data broadcasting application) is maintained so that the screen display before the emergency notification can be returned after the emergency notification period ends. Try to keep it. By setting previous_app_recovery_flag = 1, it is possible to realize the recovery operation to the state before the emergency notification after the emergency notification is completed, which is described above as the emergency notification requirement (1). On the other hand, if previous_app_recovery_flag = 0 is specified, the receiver unconditionally terminates the running application and does not retain the previous state.

The region_spec_type indicated by the reference number 803 specifies the region description method in the subsequent target_region_spec () structure, and is encoded according to Table 3 below. When all regions are targeted (in other words, when region filtering is not performed), region_spec_type is set to all “1”.

Target_region_spec indicated by reference number 804 indicates a data structure for specifying a region specified for each region description method specification. FIG. 9 shows a syntax 900 of a region designator designated by a prefecture. Prefecture_bitmap is a 55-bit bitmap indicating 1 and 0 whether or not the area corresponding to each bit position is a target (for an emergency message).

FIG. 10 shows a syntax example 1000 of the transmission protocol descriptor. The transmission protocol descriptor is a MH-AIT common descriptor loop or application information descriptor for the purpose of designating a transmission protocol such as broadcasting and communication as application transmission means and indicating location information of the application depending on the transmission protocol. Placed in the loop. Hereinafter, the meaning of each parameter of the transmission protocol descriptor will be described.

Descriptor_tag indicates an 8-bit fixed value that identifies the descriptor 1000. Descriptor_length is an 8-bit area in which the byte length of the data of the descriptor following this field is written. protocol_id (protocol identification information) indicates a protocol for transmitting an application. As values, 0x0003 specifies HTTP and HTTPS transmission, and 0x0005 specifies MMT and non-timed transmission. The transport_protocol_label (transmission protocol label) is a value that uniquely identifies the transmission means when one application is transmitted through a plurality of paths, and corresponds to the field of the same name in the application information descriptor. In the selector_byte (selector byte), a syntax is defined for each protocol identification information.

FIG. 11 shows a configuration example of the broadcast transmission system 11 that transmits an application information table (MH-AIT) indicating an emergency application. The broadcast transmission system 11 shown in the figure includes a clock unit 1101, a signal transmission unit 1102, a video encoder 1103, an audio encoder 1104, a caption / character super encoder 1105, a signaling encoder 1106, and a file encoder 1107. An electronic data processing system (Electronic Data Processing System: EDPS) 1108, a TLV signaling encoder 1109, an IP service multiplexer (MUX) 1110, a TLV multiplexer (MUX) 1111, and a modulation / transmission unit 1112. I have.

The clock unit 1101 generates time information synchronized with time information acquired from an NTP server (not shown), and sends an IP packet including this time information to the IP service multiplexer 1110.

The signal transmission unit 1102 is a recording / playback device such as a studio of a TV broadcast station or a VTR, for example, stream data such as video, audio, subtitles, and character supertext as timed media, or a data broadcasting application as nontimed media. Are sent to the video encoder 1103, the audio encoder 1104, the subtitle / character super encoder 1105, and the file encoder 1107, respectively. In this embodiment, the signal sending unit 1102 sends an emergency application to the file encoder 1107 during the emergency notification period.

The electronic data processing system 1108 is a TV broadcast station scheduler and a file supply source. The electronic data processing system 1108 sends a data broadcast application that is non-timed media to the file encoder 1107. Also, the electronic data processing system 1108 sends control information indicating the configuration of the broadcast service to the signaling encoder 1106. Also, the electronic data processing system 1108 sends control information related to the emergency application to the signaling encoder 1106 during the emergency notification period. In addition, the electronic data processing system 1108 sends control information regarding multiplexing of IP packets to the TLV signaling encoder 1109.

The video encoder 1103 HEVC encodes the video signal transmitted from the signal transmission unit 1102, further packetizes it, and sends an IP packet including the MMT packet of the video signal to the IP service multiplexer 1110. Also, the audio encoder 1104 AAC-encodes the audio signal transmitted from the signal transmission unit 1102 and further packetizes it, and sends an IP packet including the MMT packet of the audio signal to the IP service multiplexer 1110. The subtitle / character super encoder 1105 encodes the subtitle signal and the character super signal transmitted from the signal transmission unit 1102, further generates an MPU in units of presentation processing, and generates an IP packet including a subtitle MMT packet. Send to IP service multiplexer 1110.

When the broadcast transmission system 11 transmits a plurality of broadcast services, HEVC encoding of the video signal, AAC encoding of the audio signal, and subtitle / text super encoding processing are performed for each broadcast service, and each broadcast service # 1 to #N are sent to the IP service multiplexers 1110-1,..., 1110-N.

The signaling encoder 1106 generates control information (MMT-SI) indicating the configuration of a broadcast program based on information transmitted from the electronic data processing system 1108, and an MMT packet in which the MMT-SI is arranged in the payload portion Is sent to the IP service multiplexer 1110. MMT-SI includes messages, tables, and descriptors (described above). The signaling encoder 1106 generates MMT-SI for each broadcast service, and also generates MMT-SI across broadcast services. Further, the signaling encoder 1106 adds an emergency application descriptor indicating the emergency application to the application information table (MH-AIT) based on the control information related to the emergency application supplied from the electronic data processing system 1108 during the emergency notification period. , Stored in the M2 section message and sent to the signaling encoder 1106.

The file encoder 1107 encodes the data broadcasting application transmitted from the signal transmission unit 1102 or the electronic data processing system 1108 into an HTML5 format data file, further packetizes the IP packet including the MMT packet, Send to multiplexer 1110. The data broadcast application encoded by the file encoder 1107 includes an emergency application used for notifying emergency information during the emergency notification period.

The broadcast transmission system 11 is equipped with a plurality of IP service multiplexers 1110-1,..., 1110-N for each broadcast service (broadcast channel) # 1 to #N to be transmitted. The IP service multiplexer 1110 for each broadcast service channel receives IP packets including video, audio, subtitles, (broadcast service unit) MMT-SI, and data broadcast applications sent from the encoders 1103 to 1107. Multiplexed to generate a TLV packet including a broadcast signal for each broadcast service and MMT-SI across the broadcast service.

Based on the information sent from the electronic data processing system 1108, the TLV signaling encoder 1109 generates a TLV packet in which the control information (TLV-SI) related to the multiplexing of the IP packet is arranged in the payload portion.

The TLV multiplexer 1111 multiplexes the TLV packets generated by the IP service multiplexers 1110-1 to 1110 -N and the TLV signaling encoder 1109 to generate a TLV stream identified by the TLV stream identification information .

The modulation / transmission unit 1112 performs RF modulation processing on the TLV stream generated by the TLV multiplexer 1111 and sends it to the broadcast transmission path.

The operation of the broadcast transmission system 11 shown in FIG. 11 will be described.

The clock unit 1101 generates time information synchronized with time information acquired from an NTP server (not shown), and generates an IP packet including this time information.

The video signal sent from the signal sending unit 1102 is supplied to the video encoder 1103. In the video encoder 1103, the video signal is HEVC encoded and further packetized to generate an IP packet including an MMT packet of the HEVC encoded video signal. This IP packet is sent to the IP service multiplexer 1110.

Also, the same processing is performed on the audio signal sent from the signal sending unit 1102 and the caption and character super signal. That is, an IP packet including the MMT packet of the AAC encoded audio signal generated by the audio encoder 1104 is sent to the IP service multiplexer 1110 and the subtitle encoded signal generated by the subtitle / character super encoder 1105 is transmitted. An IP packet including the MMT packet is sent to the IP service multiplexer 1110.

In addition, the signaling encoder 1106 generates control information (MMT-SI) indicating the configuration of the broadcast program based on information transmitted from the electronic data processing system 1108, and the MMT-SI is arranged in the payload portion. An IP packet including the MMT packet is generated. During the emergency notification period, the signaling encoder 1106 creates an application information table (MH-AIT) to which an emergency application descriptor indicating an emergency application is added based on information on the emergency application supplied from the electronic data processing system 1108. An IP packet including the stored M2 section message is generated. These IP packets are sent to the IP service multiplexer 1110.

Further, the data broadcast application transmitted from the signal transmission unit 1102 or the electronic data processing system 1108 is supplied to the file encoder 1107. In the file encoder 1107, the data broadcasting application is encoded in, for example, HTML5 format, further packetized, and an IP packet including this MMT packet is generated. This IP packet is sent to the IP service multiplexer 1110.

In each IP service multiplexer 1110-1,..., 1110-N, video, audio, subtitles, MMT-SI (broadcast service unit and service crossing), and data broadcast application sent from each encoder 1103 to 1107 An IP packet including each of the (HTML5 document) is multiplexed to generate a TLV packet constituting one channel.

The TLV signaling encoder 1109 generates a TLV packet in which the control information (TLV-SI) related to the multiplexing of the IP packet is arranged in the payload portion based on information transmitted from the electronic data processing system 1108.

The TLV multiplexer 1111 multiplexes the TLV packets generated by the IP service multiplexers 1110-1 to 1110 -N and the TLV signaling encoder 1109 to generate a TLV stream. Modulation / transmission unit 1112 performs RF modulation processing on the TLV stream generated by TLV multiplexer 1111 and sends the RF modulation signal to the broadcast transmission path.

FIG. 12 shows a configuration example of the receiver 12 that receives a broadcast signal from the broadcast transmission system 11. The illustrated receiver 12 includes a tuner / demodulator 1201, an MMT demultiplexer (DEMUX) 1202, a clock recovery unit 1203, a video decoder 1204, an audio decoder 1205, a character super decoder 1206, a subtitle. Decoder 1207, multimedia (MM) cache 1208, SI cache 1209, broadcast system control unit 1210, application (App) engine 1211, communication interface (IF) 1212, scaler 1214, synthesis unit 1215˜ 1218 is provided.

Tuner / demodulator 1201 selects and receives a broadcast signal, performs demodulation processing, and obtains a TLV stream. The MMT demultiplexer 1202 performs demultiplex processing and depacketization processing on this TLV stream. In this embodiment, the demultiplexer 1202 includes a packet filter 1202-1 and an SI filter 1202-2.

The packet filter 1202-1 performs filtering of the IP packet based on the TLV stream identification information and the IP address, and further filters the MMTP packet from the IP packet based on the information in the MMTP header so that the video, audio, subtitle , And an MMTP packet in which each encoding component of multimedia (data broadcasting application) and signaling information are placed are respectively converted into a video decoder 1204, an audio decoder 1205, a character super decoder 1206, a subtitle decoder 1207, and a multimedia (MM ) Allocation to cache 1208 and SI filter 1202-2. The SI filter 1302-2 filters the signaling information SI and caches it in the SI cache 1310.

During the emergency notification period, the broadcast transmission system 11 sends an M2 section message storing an application information table (MH-AIT) in which an emergency application descriptor indicating an emergency application is arranged. Therefore, during the emergency notification period, the SI filter 1202-1 filters this M2 section message, and the application information table (MH-AIT) in which the emergency application descriptor is arranged in the SI cache 1209 is cached.

Based on the current time information included in the NTP packet filtered by the packet filter 1202-1 in the MMT demultiplexer 1202, the clock recovery unit 1203 generates time information synchronized with this time information, In order to decode the timed media, they are output to the video decoder 1204, the audio decoder 1205, the character super decoder 1206, and the subtitle decoder 1207, respectively.

The video decoder 1204 decodes the encoded video signal obtained by the MMT demultiplexer 1202 to obtain a baseband video signal. The audio decoder 1205 decodes the encoded audio signal obtained by the MMT demultiplexer 1202 to obtain a baseband audio signal. Also, the character super decoder 1206 and the caption decoder 1207 decode the character super and the caption encoded signal obtained by the MMT demultiplexer 1202, respectively, and obtain the character super and caption display signals, respectively.

The broadcast system control unit 1210 controls the broadcast service reception operation of the entire receiver 12 based on the MMT-SI cached in the SI cache 1209. For example, when the broadcast system control unit 1210 analyzes the MMT-SI (MH-AIT) and finds a data broadcast application set in the default entry, the broadcast system control unit 1210 performs a data broadcast presentation process on the application engine 1211. Instruct.

In the emergency notification period, the broadcast system control unit 1210 adds an emergency application descriptor to the application engine 1211 by MH-AIT (that is, indicates that the application is an emergency application). The application is instructed to start (provided that the emergency application is designated to be automatically started by the application control code). If recovery to the state before the emergency notification after the emergency notification is finished is specified in the emergency application descriptor, the application engine 1211 keeps the state of the application being executed.

The application engine 1211 is, for example, an HTML browser or the like, and processes a data broadcasting application (HTML5 document or the like) cached in the multimedia cache 1208 to generate a data broadcasting display signal and an audio signal. In addition, the application engine 1211 acquires data files (media data used for data broadcast display, link destination applications, etc.) necessary for data broadcast display from the IP network via the communication interface 1212. You can also.

The scaler 1214 performs a scaling process on the video signal (broadcast video) decoded by the video decoder 1204 in accordance with the screen size of the receiver 12.

The synthesizing unit 1215 synthesizes the audio signal decoded by the audio decoder 1205 and the audio signal for data broadcasting reproduced by the application engine 1211 to generate an audio signal for output.

The synthesizing unit 1216 synthesizes the character super display decoded by the character super decoder 1206 and the subtitle display decoded by the subtitle decoder 1207. The combining unit 1217 combines the broadcast video scaled by the scaler 1214 and the data broadcast display signal generated by the application engine 1211. Further, the synthesizing unit 1218 at the subsequent stage synthesizes the broadcast video on which the data broadcast display is superimposed, the character super display and the subtitle display output from the synthesizing unit 1216, and generates an output video signal.

The operation of the receiver 12 shown in FIG. 12 will be described.

The tuner / demodulator 1201 receives a broadcast signal, performs demodulation processing, and obtains a TLV stream. The MMT demultiplexer 1202 performs demultiplex processing and packetization processing on the TLV stream, and includes NTP time information, video, audio, text super and subtitles, encoded data signals for data broadcasting, and Signaling information is extracted and distributed to a video decoder 1204, an audio decoder 1205, a character super decoder 1206, a caption decoder 1207, a multimedia (MM) cache 1208, and an SI filter 1202-1.

Also, the NTP packet extracted by the demultiplexer 1202 is distributed to the clock recovery unit 1203. The clock recovery unit 1203 generates time information synchronized with this time information based on the time information placed in the NTP packet. That is, the clock recovery unit 1203 generates time information that matches the time information generated by the clock unit 1101 on the broadcast transmission system 11 side.

The encoded video signal extracted by the MMT demultiplexer 1202 is sent to the video decoder 1204 and decoded to obtain a baseband video signal. The character super-encoded signal extracted by the demultiplexer 1202 is sent to the character super-decoder 1206 and decoded to obtain a character super display signal. Also, the caption encoded signal extracted by the demultiplexer 1202 is sent to the caption decoder 1207 and decoded, so that a caption display signal is obtained.

The broadcast system control unit 1210 controls the entire reception processing operation by the receiver 12 including the processing of the data broadcast application based on the MMT-SI received via the SI filter 1202-2 and the SI cache 1209.

The application engine 1211 processes a data broadcast application (HTML5 document or the like) cached in the multimedia cache 1208, and generates a data broadcast display signal and an audio signal.

In the emergency notification period, the broadcast system control unit 1210 instructs the application engine 1211 to start an application that is indicated to be an emergency application. When recovery to the state before the emergency notification after the emergency notification is finished is specified by the emergency application descriptor, the state of the application being executed in the application engine 1211 is held.

The scaler 1214 performs a scaling process on the video signal (broadcast video) decoded by the video decoder 1204. The synthesizing unit 1216 synthesizes the character super display decoded by the character super decoder 1206 and the subtitle display decoded by the subtitle decoder 1207. Subsequently, the synthesis unit 1217 synthesizes the broadcast video scaled by the scaler 1214 and the data broadcast display signal generated by the application engine 1211. Further, in the subsequent synthesis unit 1218, the broadcast video on which the display of the data broadcast is superimposed, the character super display and the subtitle display output from the synthesis unit 1216 are synthesized, and an output video signal is generated.

The data broadcast application transmitted from the broadcast transmission system 11 includes an emergency application for notifying emergency information. In the emergency notification period, the emergency application is indicated by adding the emergency application in the application information loop in the MH-AIT that specifies the control information of the application. On the receiver 12 side, when an emergency application descriptor appears in the MH-AIT, the active application is terminated or hidden only in the designated target area and indicated by the emergency application descriptor. Launch emergency application.

FIG. 13 shows a screen display control example of emergency information using an emergency application. FIG. 13A illustrates a display screen 1300 of the receiver before emergency notification. The illustrated screen 1300 is a reception screen for a normal broadcast service. FIG. 13B illustrates a screen 1310 in which the receiver activates the emergency application based on the emergency application descriptor specified by the MH-AIT during the emergency notification period.

A display screen 1300 shown in FIG. 13A includes a baseball broadcast video 1301 which is a broadcast program. In addition, when the data broadcasting application linked to the program is started, the program video display area 1301 is reduced by the scaler, and the data broadcasting display area 1302 is generated. In the display area 1302, for example, game scores, personal results of players appearing in the video, and the like are presented.

FIG. 13B illustrates a screen 1310 in which the receiver transitions from the screen illustrated in FIG. 13A based on the emergency application descriptor added to the MH-AIT during the emergency notification period. Yes. In the illustrated example, the emergency application is an application that presents an emergency message “An earthquake has occurred! Tsunami warning is issued! Please evacuate immediately to the hill!” This application display area 1312 is combined with the program video 1311. This is the output video.

When the broadcast station enters the emergency notification period, the MH-AIT with the emergency application descriptor added to the emergency application is stored in the M2 section message and transmitted. When the receiver receives the latest MH-AIT and detects that an emergency application descriptor appears in the application information loop, the receiver terminates the active data broadcasting application or hides its display area 1302. To do. Then, the emergency application indicated by the emergency application descriptor is activated.

Note that the screen display example shown in FIG. 13B is based on the assumption that the emergency application displays the broadcast program video in a small screen and emergency information such as an emergency message. However, the screen display of the emergency application is not limited to this.

In addition, when “previous_app_recovery_flag = 1” is specified in the emergency application descriptor, the receiver can return to the previous screen display before performing the emergency notification after the emergency notification period ends ( The state of the data broadcasting application at the time of termination is retained.

Also, the emergency application descriptor includes information on the target area (see the above and FIG. 8). The receiver can perform regional filtering of the emergency application based on the target region information.

FIG. 14 shows an example of regional filtering for emergency applications.

Before receiving an emergency notification, all the receivers in each region of Japan display a normal broadcast service reception screen in which the program video and the data broadcast display are combined as shown in FIG. Suppose that

Suppose that the emergency notification period starts and receivers throughout the country receive the same MH-AIT. In MH-AIT, an emergency application descriptor is added to an application that displays an emergency message “An earthquake has occurred! Tsunami warning is issued! Please evacuate immediately to high ground!”. The emergency application descriptor assumes that Kanto (target_region_spec = (only kanto)) is specified as the target area.

As indicated by reference numeral 1401, the receiver in the Kanto region displays a video obtained by synthesizing a program video and an application display area for presenting an emergency message, as shown in FIG. 13B. On the other hand, a receiver other than the Kanto region detects that it is not covered by the emergency application descriptor based on the description of the region designation (target_region_spec = (only kanto)). There is no display switching.

FIG. 15 illustrates an emergency application switching scenario. In the figure, a broadcast signal (TLV stream) transmitted from a certain broadcaster (broadcast station) is illustrated, and the horizontal axis is a time axis. The period t1 to t2 is an emergency notification period.

The broadcaster provides one broadcast service, and broadcast service # 1 is transmitted in the illustrated TLV stream. This broadcast service # 1 includes each asset (component) of video, audio, subtitles, and data broadcast, and control information (MMT-SI) for each broadcast service. The broadcaster may provide two or more broadcast services, but broadcast service # 1 is shown for the sake of simplicity of the drawing.

In the illustrated example, the application asset transmits an ordinary data broadcasting application (app1, app2) indicated by reference numeral 1501, and an emergency application (appE) in the emergency notification period indicated by reference numeral 1502. Includes two of the assets. However, the normal data broadcasting application and the emergency application may be transmitted using the same application asset, or may include application assets other than those shown in the figure.

Further, as control information (MMT-SI), the MH-AIT stored in the M2 section message indicated by reference number 1503 and the data directory management table and data asset management table indicated by reference number 1504 are stored. Data transmission messages are included. Although the MMT-SI includes control information other than these, the illustration is omitted because it is not directly related to the following description.

MH-AIT designates the status of all applications transmitted by each

application asset

1501 and 1502 using an application control code in an application information loop.

The MH-AIT in the period before time t1 designates the respective states autostart and present of the normal data broadcasting applications app1 and app2 transmitted by the normal application asset 1501, as indicated by reference numeral 1511.

Further, the MH-AIT in the emergency notification period from time t1 to time t2, as indicated by the reference number 1512, in addition to the normal data broadcasting applications app1 and app2 transmitted by the normal application asset 1501, the emergency application asset 1502 Each state autostart, present, and autostart of the emergency application appE transmitted in the above is specified, and an emergency application descriptor is added to the emergency application appE.

Further, the MH-AIT for the period after time t2 designates the respective states autostart and present of the normal data broadcasting applications app1 and app2 transmitted by the normal application asset 1501, respectively, as indicated by reference numeral 1513. Yes.

MH-AIT indicates the location information of each application using a transmission protocol descriptor. Then, as described with reference to FIG. 5, the location information indicated by the MH-AIT is changed to the application asset 1501 with reference to the data directory management table and the data asset management table transmitted by the data transmission message 1504. , 1502 can be converted into identification information on the file 1502 to obtain a file that is an entity of the application.

The operation of the receiver that receives the broadcast signal shown in FIG. 15 will be considered below.

The MH-AIT in the period before time t1 designates autostart (automatic activation) for the application app1 transmitted by the normal application asset 1501, as indicated by reference numeral 1511.

The receiver converts the location information of the application app1 specified by the transmission protocol descriptor into identification information on the application asset 1501 based on the data directory management table and the data asset management table in the data transmission message 1504. When the entity of the application app1 is acquired, the application engine 1211 executes it. In this way, the receiver can display the screen 1521 in which the display of the normal data broadcast application is combined with the video of the broadcast program.

Also, when the emergency notification period starts when time t1 is reached, an emergency application descriptor appears in the MH-AIT as indicated by reference numeral 1512. That is, the MH-AIT transmitted during the emergency notification period adds an emergency application descriptor to the emergency application appE transmitted by the emergency application asset 1502 and designates its state as “autostart”. Yes.

The receiver terminates or hides the running application app1 and starts the emergency application appE. The receiver converts the location information of the application appE specified by the transmission protocol descriptor into identification information on the application asset 1502 based on the data directory management table and the data asset management table in the data transmission message 1504. When the entity of the emergency application appE is acquired, the application engine 1211 executes it. In this way, the receiver can display a screen 1522 in which the emergency application display is combined with the broadcast program video.

As described above, the emergency application descriptor can specify whether or not to perform regional filtering using a region_filtering_flag (region filter flag). When the receiver is the target area of the emergency application or when the regional filtering is not performed, the screen display switching operation as indicated by reference numeral 1522 is performed, but the receiver that is not the target area performs the screen display switching operation. Do not do.

Also, the emergency application descriptor can specify whether to restore the state of the previous application after termination of the emergency application or to stop the previous application unconditionally with previous_app_recovery_flag. When the flag is set to 1, that is, when it is specified that the state is restored to the previous application state, the receiver starts the emergency application appE after maintaining the state of the application app1, and after the emergency notification period ends. Lets you return to the original app1 display (thus not temporarily ending app1, but temporarily hiding it). On the other hand, when the flag is 0, that is, when the unconditional stop of the previous application is designated, the receiver activates the emergency application appE without maintaining the state of the application app1.

In the example shown in FIG. 15, it is assumed that a normal data broadcasting application is being executed before the emergency notification period starts. Even when the emergency notification period is entered in a state where there is no active application, the receiver similarly activates the emergency application indicated by MH-AIT.

Also, when the time t2 is reached and the emergency notification period ends, the description of the application appE to which the emergency application descriptor is added from the MH-AIT disappears as indicated by reference numeral 1513. When the information indicating the emergency application disappears from the MH-AIT, the receiver stops the active emergency application, and operates the application designated to be automatically activated by the MH-AIT at that time.

MH-AIT after time t2 designates autostart (automatic activation) for app1 transmitted by the normal application asset 1501. Therefore, the receiver uses the location information of the application app1 specified by the transmission protocol descriptor to identify the identification information on the application asset 1501 based on the data directory management table and the data asset management table in the data transmission message 1504. When the entity of the emergency application app1 is acquired, the application engine 1211 executes it.

In addition, when “previous_app_recovery_flag = 1” is specified in the emergency application descriptor and the state of the application app1 that was operating at the time t1 is held, the receiver recovers the state and starts the emergency application appE. Make the application app1 that is sometimes invisible visible.

In this way, the receiver can display the screen 1523 in which the display of the normal data broadcast application is combined with the video of the broadcast program.

FIG. 16 shows an example of a procedure for processing an emergency application in the form of a flowchart in the receiver 12 shown in FIG. The broadcast system control unit 1210 in the receiver 12 starts this processing routine every time an emergency application descriptor appears in the MH-AIT.

The broadcast system control unit 1210 first checks whether or not the regional filtering flag (region_filtering_flag) is turned on in the emergent emergency application descriptor (step S1601).

If the regional filtering flag is on (Yes in step S1601), the broadcast system control unit 1210 indicates that the receiver 12 is specified by the target_region_spec () structure in the display priority specification descriptor. It is checked whether or not it is an area (step S1602). If the receiver 12 is not the target area for the display priority designation descriptor (No in step S1602), the processing routine is terminated.

On the other hand, when the receiver 12 is the target area of the emergency application (Yes in step S1602), or the area filtering flag is off (No in step S1601), the broadcast system control unit 1210 Performs subsequent processing.

Next, the broadcast system control unit 1210 checks whether or not the emergency application descriptor instructs to restore the previous application state after the emergency application ends, in other words, to retain the previous application state. (Step S1603).

If it is specified that the state of the previous application is to be restored (Yes in step S1603), the broadcast system control unit 1210 holds the state of the application (step S1604), and then starts the emergency application (step S1604). Step S1605). If unconditional stop of the previous application is designated (No in step S1603), the broadcast system control unit 1210 activates the emergency application without maintaining the application state (step S1605). .

Thereafter, when the description of the application with the emergency application descriptor added from the MH-AIT disappears (Yes in step S1606), the broadcast system control unit 1210 stops the emergency application in operation (step S1607), and at that time Then, the application whose automatic activation is designated by the MH-AIT is operated (step S1608).

Next, the broadcast system control unit 1210 checks whether or not the previous application state has been held in the preceding step S1603 (step S1609). If the previous application state is retained and the previous application matches the application automatically started in step S1608 (step S1609), the retained state is recovered (step S1610). .

As described above, the technology disclosed in this specification has been described in detail with reference to specific embodiments. However, it is obvious that those skilled in the art can make modifications and substitutions of the embodiments without departing from the scope of the technology disclosed in this specification.

In the present specification, the embodiment in which the technology disclosed in this specification is applied to a broadcasting system adopting the MMT method for media transmission has been mainly described. However, the gist of the technology disclosed in this specification is limited to this. It is not something. The technology disclosed in this specification can be similarly applied to various types of broadcasting systems that transmit data broadcasting applications together with control information, and control of broadcast full-screen display and emergency subtitle display at the time of emergency at the receiver is possible. Can be realized.

In short, the technology disclosed in the present specification has been described in the form of examples, and the description content of the present specification should not be interpreted in a limited manner. In order to determine the gist of the technology disclosed in this specification, the claims should be taken into consideration.

Note that the technology disclosed in the present specification can also be configured as follows.
(1) a transmission unit that transmits an application;
A control information transmission unit that adds emergency application information indicating an emergency application and transmits application control information;
A transmission apparatus comprising:
(2) The control information transmitting unit adds the emergency application information to the application control information only during an emergency notification period in which emergency information should be notified.
The transmission device according to (1) above.
(3) The control information transmission unit includes information related to the target area in the emergency application information and transmits the information.
The transmission device according to any one of (1) and (2) above.
(4) The control information transmission unit includes the emergency application information including information indicating whether or not it is necessary to recover to the state of the previous application after the emergency application ends.
The transmission device according to any one of (1) to (3) above.
(5) The control information transmission unit transmits the application control information designating automatic activation of the emergency application.
The transmission device according to claim 1.
(6) a transmission step of transmitting the application;
A control information transmission step for transmitting application control information by adding emergency application information indicating an emergency application,
A transmission method.
(7) a receiving unit for receiving an application;
A control information receiver for receiving application control information;
A control unit that controls processing of the application based on the application control information;
Comprising
The control unit controls processing of an emergency application indicated by emergency application information included in the application control information.
Receiver device.
(8) The control unit attempts to start the emergency application in response to the emergence of the emergency application information in the application control information.
The receiving device according to (7) above.
(9) The control unit activates the emergency application only when the target area is specified by the emergency application information or when the target area is not specified by the emergency application information.
The receiving device according to any one of (7) and (8).
(10) When the emergency application information instructs to restore the state of the previous application after the emergency application ends, the control unit starts the emergency application after holding the state of the previous application To
The receiving device according to any one of (7) to (9).
(11) The receiving unit receives an image of a broadcast program,
The control unit displays information of the emergency application specified by displaying the video of the broadcast program in a sub-screen;
The receiving device according to any one of (7) to (10) above.
(12) The control unit stops the emergency application in response to the disappearance of the emergency application information from the application control information.
The receiving device according to any one of (7) to (11) above.
(13) The control unit activates an application whose automatic activation is designated by the application control information when the emergency application is stopped.
The receiving device according to (12) above.
(14) The control unit recovers the state of the previous application held.
The receiving device according to (13) above.
(15) a receiving step of receiving an application;
A control information receiving step for receiving application control information;
A control step for controlling processing of the emergency application indicated by the emergency application information included in the application control information;
Receiving method.

DESCRIPTION OF SYMBOLS 10 ... Digital broadcasting system 11 ... Broadcast transmission system, 12 ... Receiver 1101 ... Clock part 1102 ... Signal transmission part 1103 ... Video encoder 1104 ... Audio encoder 1105 ... Subtitle / text super encoder 1106 ... Signaling encoder 1107 ... File encoder 1108 ... Electronic data processing system 1109 ... TLV signaling encoder 1110 ... IP service multiplexer 1111 ... TLV multiplexer 1112 ... Modulation / transmission unit 1201 ... Tuner demodulation unit 1202 ... MMT demultiplexer 1203 ... Clock recovery unit, 1204 ... Video decoder 1205 ... Audio decoder 1206 ... Character super decoder 1207 ... Subtitle decoder 1208 Multimedia cache 1209 ... SI cache, 1210 ... broadcasting system control unit 1211 ... application engine 1212 ... communication interface, 1214 ... scaler 1215-1218 ... synthesis unit

Claims

A transmitter for transmitting the application;
A control information transmission unit that adds emergency application information indicating an emergency application and transmits application control information;
A transmission apparatus comprising:
The control information transmission unit adds the emergency application information to the application control information only during an emergency notification period in which emergency information is to be notified.
The transmission device according to claim 1.
The control information transmission unit includes information related to the target area in the emergency application information,
The transmission device according to claim 1.
The control information transmission unit includes information indicating whether or not it is necessary to recover to the state of the previous application after the emergency application is finished, and transmits the emergency application information.
The transmission device according to claim 1.
The control information transmission unit transmits the application control information designating automatic activation of the emergency application.
The transmission device according to claim 1.
A send step for sending the application;
A control information transmission step for transmitting application control information by adding emergency application information indicating an emergency application,
A transmission method.
A receiver for receiving the application;
A control information receiver for receiving application control information;
A control unit that controls processing of the application based on the application control information;
Comprising
The control unit controls processing of an emergency application indicated by emergency application information included in the application control information.
Receiver device.
The control unit tries to start the emergency application in response to the emergence of the emergency application information in the application control information.
The receiving device according to claim 7.
The control unit activates the emergency application only when the target area is specified by the emergency application information or when the target area is not specified by the emergency application information.
The receiving device according to claim 7.
If the emergency application information indicates that recovery to the previous application state is instructed after the emergency application ends, the control unit starts the emergency application after holding the previous application state.
The receiving device according to claim 7.
The receiving unit receives a video of a broadcast program,
The control unit displays information of the emergency application specified by displaying the video of the broadcast program in a sub-screen;
The receiving device according to claim 7.
The control unit stops the emergency application in response to the disappearance of the emergency application information from the application control information.
The receiving device according to claim 7.
The control unit activates an application whose automatic activation is designated by the application control information at the time of stopping the emergency application,
The receiving device according to claim 12.
The control unit recovers the state of the previous application that has been held,
The receiving device according to claim 13.
A receiving step for receiving the application;
A control information receiving step for receiving application control information;
A control step for controlling processing of the emergency application indicated by the emergency application information included in the application control information;
Receiving method.