Content protection processing method

Abstract

To provide a digital broadcast receiver capable of executing higher value-added functions. [Solution] The device includes a receiving unit that receives video data of a digital broadcast program, program linkage data, and screen layout control information, a video generation unit that generates video information by combining multiple areas as output video information, a display unit that displays the output video information, and a control unit. If there is no valid screen layout control information, the control unit controls the video generation unit to generate the program video information as output video information without dividing the video display area. After acquiring valid screen layout control information, the control unit controls the video generation unit to divide the video display area into multiple areas based on the valid screen layout control information, and to arrange the program video information generated based on the video data of the received digital broadcast program and any of text information, graphic information, and video information generated based on the received program linkage data.

Description

[Technical Field]

[0001] The present invention relates to broadcast reception technology and output video information generation technology. [Background technology]

[0002] One of the extension functions of digital broadcasting services is data broadcasting, which transmits digital data via broadcast waves and displays various information such as weather forecasts, news, recommended programs, etc. Many television receivers capable of receiving data broadcasting are already commercially available, and many technologies related to receiving data broadcasting have been published, including Patent Document 1 below. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-186486 Summary of the Invention [Problem to be solved by the invention]

[0004] In response to recent changes in the content distribution environment, television receivers are also being required to have various functional extensions. In particular, there are many demands for the distribution of content and linked applications using broadband network environments such as the Internet, and for higher resolution / high definition video content. However, it is difficult to realize a high-value-added television receiver that can meet these demands by simply utilizing the data broadcasting reception function and the like that is provided in current television receivers or by simply extending the function of the data broadcasting reception function and the like.

[0005] An object of the present invention is to provide a content protection processing method that can execute higher value-added functions. [Means for solving the problem]

[0006] The technology described in the claims is used as a means for solving the above problems. [Effects of the Invention]

[0007] By using the technology of the present invention, it is possible to realize a content protection processing method that can execute functions with higher added value. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a system configuration diagram illustrating an example of a broadcast communication system including a broadcast receiving device according to a first embodiment. [Figure 2A] FIG. 1 is an explanatory diagram of an overview of a coded signal in MMT. [Figure 2B] This is a diagram of the MPU configuration in MMT. [Figure 2C] This is a diagram showing the structure of an MMTP packet in MMT. [Figure 3] This is a conceptual diagram of the protocol stack of a broadcasting system that uses MMT. [Figure 4] FIG. 1 is a diagram showing a hierarchical structure of control information used in a broadcasting system. [Figure 5A] This is a list of tables used in the TLV-SI of the broadcasting system. [Figure 5B] This is a list of descriptors used in the TLV-SI of the broadcasting system. [Figure 6A] This is a list of messages used in the MMT-SI broadcasting system. [Figure 6B] 1 is a list of tables used in the MMT-SI of the broadcasting system. [Figure 6C] This is a list (part 1) of descriptors used in the MMT-SI broadcasting system. [Figure 6D] This is a list of descriptors used in the MMT-SI broadcasting system (part 2). [Figure 6E] FIG. 2 is a diagram showing the relationship between data transmission in a broadcasting system and each table. [Figure 7A] 1 is a block diagram of a broadcast receiving device according to a first embodiment. [Figure 7B]1 is a configuration diagram of a logical plane structure of a presentation function of a broadcast receiving device according to a first embodiment. [Figure 7C] 1 is a system configuration diagram of clock synchronization / presentation synchronization of a broadcast receiving device according to a first embodiment. [Figure 7D] 2 is a software configuration diagram of the broadcast receiving device according to the first embodiment. FIG. [Figure 8] FIG. 2 is a block diagram of a broadcast station server according to the first embodiment. [Figure 9] FIG. 2 is a block diagram of a service provider server according to the first embodiment. [Figure 10A] FIG. 1 is a block diagram of a portable information terminal according to a first embodiment. [Figure 10B] FIG. 2 is a software configuration diagram of the portable information terminal according to the first embodiment. [Figure 11A] A diagram showing the data structure of MH-TOT of a broadcasting system. [Figure 11B] FIG. 10 is a diagram illustrating the format of the JST_time parameter of a broadcasting system. [Figure 12] 10 is a diagram illustrating a method for calculating the current date from the MJD of the broadcast receiving device according to the first embodiment. FIG. [Figure 13A] FIG. 1 is a diagram showing the configuration of an NTP format for a broadcasting system. [Figure 13B] A diagram showing the data structure of an MPU timestamp descriptor for a broadcasting system. [Figure 13C] FIG. 10 is a diagram showing the data structure of time information in the TMCC extended information area of ​​a broadcasting system. [Figure 14] FIG. 3 is an operational sequence diagram of the broadcast receiving device according to the first embodiment during channel scanning. [Figure 15A] A diagram showing the data structure of TLV-NIT of a broadcasting system. [Figure 15B] FIG. 10 is a diagram illustrating the data structure of a satellite distribution system descriptor for a broadcasting system. [Figure 15C] FIG. 10 is a diagram illustrating the data structure of a service list descriptor for a broadcasting system. [Figure 15D] FIG. 10 is a diagram showing the data structure of an AMT of a broadcasting system. [Figure 16] 4 is an operational sequence diagram of the broadcast receiving device according to the first embodiment when selecting a channel. FIG. [Figure 17] FIG. 1 is a diagram showing the data structure of an MPT of a broadcasting system. [Figure 18] A diagram showing the data structure of the LCT of the broadcasting system. [Figure 19A] FIG. 10 is a diagram showing an example of allocation of layouts to layout numbers based on the LCT. [Figure 19B] FIG. 10 is a diagram showing an example of allocation of layouts to layout numbers based on the LCT. [Figure 19C] FIG. 10 is a diagram showing an example of allocation of layouts to layout numbers based on the LCT. [Figure 19D] FIG. 10 is a diagram showing an example of allocation of layouts to layout numbers based on the LCT. [Figure 20A] 10A and 10B are diagrams illustrating the operation of exception handling in screen layout control based on LCT. [Figure 20B] 10A and 10B are diagrams illustrating the operation of exception handling in screen layout control based on LCT. [Figure 21] FIG. 10 is a diagram showing the data structure of the MH-EIT of the broadcasting system. [Figure 22A] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 22B] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 22C] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 23] 3 is a diagram showing a screen display when an emergency alert broadcast is displayed on the broadcast receiving device according to the first embodiment. FIG. [Figure 24] FIG. 10 is a block diagram of a broadcast receiving device according to a second embodiment. [Figure 25] 10A and 10B are diagrams illustrating inconsistencies in the current time display when switching broadcast services. [Figure 26] FIG. 10 is a diagram illustrating the operation of the current time information reference source selection control according to the second embodiment. [Figure 27A] FIG. 10 is a screen display diagram of an EPG screen of a broadcast receiving device according to a second embodiment. [Figure 27B] FIG. 10 is a screen display diagram of an EPG screen of a broadcast receiving device according to a second embodiment. [Figure 28] FIG. 2 is a diagram showing the structure of program data. [Figure 29] FIG. 2 is a structural diagram of asset data. [Figure 30] FIG. 10 is a diagram illustrating the data structure of a PA message. [Figure 31] A diagram showing the data structure of MMT_general_location_info. [Figure 32] FIG. 10 is a diagram showing the data structure of a PLT. [Figure 33] FIG. 10 is a diagram illustrating the meaning of location types. [Figure 34] FIG. 10 is a diagram illustrating the data structure of an MPU presentation area specification descriptor. [Figure 35A] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. [Figure 35B] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. [Figure 36A] FIG. 10 is a diagram illustrating the data structure of an LCT expiration date descriptor. [Figure 36B] FIG. 10 is a diagram illustrating the data structure of a layout expiration date descriptor. [Figure 36C] FIG. 10 is a diagram illustrating the data structure of a presentation area expiration date descriptor. [Figure 37] FIG. 10 is a diagram illustrating the data structure of a common presentation area information descriptor. [Figure 38] FIG. 10 is a diagram showing the meaning of full_set_flag. [Figure 39] FIG. 10 is a diagram illustrating the data structure of an overlapping presentation area designation descriptor. [Figure 40] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. [Figure 41] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. [Figure 42] FIG. 10 is a diagram illustrating the data structure of a dependency descriptor. [Figure 43] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. [Figure 44]FIG. 10 is a diagram illustrating a data structure of a modified example of a dependency descriptor. [Figure 45] FIG. 10 is a diagram illustrating the meaning of dependency_type. [Figure 46] 10A and 10B are diagrams illustrating a presentation operation according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] [System Configuration] 1 is a system configuration diagram showing an example of a broadcast communication system including a broadcast receiving device of this embodiment. The broadcast communication system of this embodiment is composed of a broadcast receiving device 100, an antenna 100a, a broadband network such as the Internet 200, a router device 200r, an access point 200a, a broadcast station radio tower 300t, a broadcast satellite (or communication satellite) 300s, a broadcast station server 300, a service provider server 400, other application servers 500, a mobile telephone communication server 600, a base station 600b of a mobile telephone communication network, and a mobile information terminal 700.

[0011] The broadcast receiving device 100 receives broadcast waves transmitted from a radio tower 300t via a broadcast satellite (or communication satellite) 300s and an antenna 100a. Alternatively, the broadcast waves transmitted from the radio tower 300t may be received directly from the antenna 100a without going through the broadcast satellite (or communication satellite) 300s. The broadcast receiving device 100 can also be connected to the Internet 200 via a router device 200r, and can transmit and receive data via communication with each server device and other communication devices on the Internet 200.

[0012] The router device 200r is connected to the Internet 200 via wired communication, and is connected to the broadcast receiving device 100 via wired or wireless communication, and to the mobile information terminal 700 via wireless communication. The wireless communication may use a method such as Wi-Fi (registered trademark). This allows each server device or other communication device on the Internet 200 to transmit and receive data to and from the broadcast receiving device 100 and the mobile information terminal 700 via the router device 200r. Note that communication between the broadcast receiving device 100 and the mobile information terminal 700 may be performed directly using a method such as Bluetooth (registered trademark) or NFC (Near Field Communication), without going through the router device 200r.

[0013] The radio tower 300t is a broadcasting facility of a broadcasting station, and transmits broadcast waves including encoded data of broadcast programs, subtitle information, other applications, general-purpose data, etc. The broadcast satellite (or communication satellite) 300s is a repeater that receives broadcast waves transmitted from the broadcasting station's radio tower 300t, performs appropriate frequency conversion, etc., and then retransmits the broadcast waves to the antenna 100a connected to the broadcast receiving device 100. The broadcasting station is also assumed to have a broadcasting station server 300. The broadcasting station server 300 stores broadcast programs (video content, etc.) and metadata for each broadcast program, such as the program title, program ID, program summary, cast information, and broadcast date and time, and is capable of providing the video content and each metadata to a service provider based on a contract. The video content and each metadata may be provided to the service provider via an API (Application Programming Interface) provided by the broadcasting station server 300.

[0014] The service provider server 400 is a server device provided by a service provider and is capable of providing various services linked to broadcast programs distributed by broadcast stations. The service provider server 400 stores, manages, and distributes video content and metadata provided by the broadcast station server 300, as well as various content and applications linked to broadcast programs. The service provider server 400 also has the function of searching for and providing a list of available content and applications in response to inquiries from television receivers and the like. The storage, management, and distribution of the content and metadata and the storage, management, and distribution of the applications may be performed by different server devices. The broadcast station and the service provider may be the same or different. Multiple service provider servers 400 may be provided for different services. The broadcast station server 300 may also have the functions of the service provider server 400.

[0015] The other application server 500 is a known server device that stores, manages, and distributes other general applications, operating programs, content, data, etc. There may be multiple other application servers 500 on the Internet 200.

[0016] The mobile telephone communication server 600 is connected to the Internet 200, and is also connected to the mobile information terminal 700 via a base station 600b. The mobile telephone communication server 600 manages telephone communications (calls) and data transmission / reception of the mobile information terminal 700 via the mobile telephone communication network, and enables data transmission / reception between the mobile information terminal 700 and each server device or other communication device on the Internet 200. The communication between the base station 600b and the mobile information terminal 700 may be performed using the W-CDMA (Wideband Code Division Multiple Access) (registered trademark) system, the GSM (Global System for Mobile communications) (registered trademark) system, the LTE (Long Term Evolution) system, or other communication systems.

[0017] The mobile information terminal 700 has functions for telephone communication (calls) and data transmission / reception via a mobile telephone communication network, as well as functions for wireless communication using Wi-Fi (registered trademark) or the like. The mobile information terminal 700 can connect to the Internet 200 via a router device 200r or an access point 200a, or via a base station 600b of the mobile telephone communication network and a mobile telephone communication server 600, and can transmit and receive data through communication with each server device and other communication devices on the Internet 200. The access point 200a is connected to the Internet 200 via wired communication, and is connected to the mobile information terminal 700 via wireless communication. The wireless communication may use a method such as Wi-Fi (registered trademark). Note that communication between the mobile information terminal 700 and the broadcast receiving device 100 may be performed via the access point 200a, the Internet 200, and the router device 200r, or via the base station 600b, the mobile telephone communication server 600, the Internet 200, and the router device 200r.

[0018] [Overview of the MMT method] 1 is a television receiver that supports MMT (MPEG Media Transport), which is an alternative to the TS (Transport Stream) (hereinafter referred to as MPEG2-TS) defined in the MPEG (Moving Picture Experts Group)-2 system, which is widely used in conventional digital broadcasting systems, as a media transport method for transmitting data such as video and audio. The television receiver may also be compatible with both MPEG2-TS and MMT.

[0019] MPEG2-TS is characterized by multiplexing the video, audio, and other components that make up a program into a single stream along with control signals and clocks. Because the clock is treated as a single stream, it is suitable for transmitting a single piece of content over a single transmission path with guaranteed transmission quality, and has been adopted in many conventional digital broadcasting systems. However, in recent years, the diversification of content, the diversification of devices that use content, the diversification of transmission paths for delivering content, and the diversification of content storage environments have made it difficult for MPEG2-TS to adapt to these changes in the content delivery environment. Therefore, a new media transport method, MMT, has been established.

[0020] FIG. 2A shows an example of an outline of an encoded signal in MMT according to this embodiment. As shown in the figure, the MMT according to this embodiment has MFUs (Media Fragment Units), MPUs (Media Processing Units), MMTP (MMT Protocol) payloads, and MMTP packets as elements constituting an encoded signal. The MFU is a format for transmitting video, audio, etc., and may be configured in NAL (Network Abstraction Layer) unit or access unit units. The MPU may be configured with MPU metadata containing information about the overall configuration of the MPU, movie fragment metadata containing information about the encoded media data, and sample data, which is the encoded media data. It is also assumed that the MFU can be extracted from the sample data. For media such as video components and audio components, the presentation time and decoding time may be specified in MPU or access unit units. FIG. 2B shows an example of the configuration of an MPU.

[0021] An MMTP packet consists of a header section and an MMTP payload, and carries MFUs and MMT control information. The MMTP payload has a payload header corresponding to the content (data unit) stored in the payload section. Figure 2C shows an example of an overview of how an MFU is constructed from a video / audio signal, then stored in the MMTP payload to construct an MMTP packet. Note that for video signals encoded using inter-frame prediction, it is desirable to construct MPUs in GOP (Group of Pictures) units. Furthermore, if the size of the MFU to be transmitted is small, one MFU may be stored in one payload section, or multiple MFUs may be stored in one payload section. Furthermore, if the size of the MFU to be transmitted is large, one MFU may be divided and stored in multiple payload sections. Furthermore, MMTP packets may be protected using techniques such as Application Layer Forward Error Correction (AL-FEC) and Automatic Repeat Request (ARQ) to recover from packet loss on the transmission path.

[0022] In the broadcasting system of this embodiment, MPEG-H HEVC (High Efficiency Video Coding) is used as the video encoding method, and MPEG-4 AAC (Advanced Audio Coding) or MPEG-4 ALS (Audio Lossless Coding) is used as the audio encoding method. The encoded data of the video and audio of a broadcast program encoded by each of the above methods is in MFU or MPU format, and then loaded onto an MMTP payload to be packetized as MMTP packets and transmitted in IP (Internet Protocol) packets. Data content related to the broadcast program may also be in MFU or MPU format, and then loaded onto an MMTP payload to be packetized as MMTP packets and transmitted in IP packets. Four types of data content transmission methods are provided: a subtitle / superimposed text transmission method used for streaming data synchronized with broadcasting; an application transmission method used for data transmission asynchronous with broadcasting; an event message transmission method used for synchronous / asynchronous message notification to applications running on a television receiver; and a general-purpose data transmission method for transmitting other general-purpose data synchronously or asynchronously.

[0023] For the transmission of MMTP packets, UDP / IP (User Datagram Protocol / Internet Protocol) is used on the broadcast transmission path, and UDP / IP or TCP / IP (Transmission Control Protocol / Internet Protocol) is used on the communication line. Furthermore, the TLV (Type Length Value) multiplexing method is used on the broadcast transmission path for efficient transmission of IP packets. An example of the protocol stack for the broadcast system of this embodiment is shown in Figure 3. In the figure, (A) is an example of a protocol stack on the broadcast transmission path, and (B) is an example of a protocol stack on the communication line.

[0024] The broadcasting system of this embodiment provides a mechanism for transmitting two types of control information: MMT-SI (MMT-Signaling Information) and TLV-SI (TLV-Signaling Information). MMT-SI is control information that indicates the configuration of a broadcast program, etc. It is in the form of an MMT control message, placed on an MMTP payload, packetized as an MMTP packet, and transmitted in an IP packet. TLV-SI is control information related to multiplexing of IP packets, and provides information for channel selection and information corresponding to IP addresses and services.

[0025] Furthermore, in broadcasting systems using MMT, time information is transmitted to provide absolute time. While MPEG2-TS indicates the display time of components based on a different clock for each TS, MMT indicates the display time of components based on Coordinated Universal Time (UTC). These mechanisms enable terminal devices to synchronize and display components transmitted from different transmission points over different transmission paths. To provide UTC, IP packets in NTP (Network Time Protocol) format are used.

[0026] [Control information for broadcasting systems using MMT] In the broadcast system compatible with the broadcast receiver 100 of the present embodiment, as described above, as control information, TLV-SI related to the TLV multiplexing method for multiplexing IP packets and MMT-SI related to MMT which is a media transport method are prepared. TLV-SI provides information for the broadcast receiver 100 to demultiplex the IP packets multiplexed on the broadcast transmission path. TLV-SI is composed of a "table" and a "descriptor". The "table" is transmitted in section format, and the "descriptor" is arranged within the "table". MMT-SI is transmission control information indicating information related to the configuration of MMT packages and broadcast services. MMT-SI is composed of three layers: a "message" storing a "table" and a "descriptor", a "table" having elements and attributes indicating specific information, and a "descriptor" indicating more detailed information. An example of the hierarchical structure of the control information used in the broadcast system of the present embodiment is shown in FIG. 4.

[0027] FIG. 5A shows a list of "tables" used in the TLV-SI of the broadcast system compatible with the broadcast receiver 100 of the present embodiment. In the present embodiment, the following are used as the "tables" of TLV-SI.

[0028] (1) TLV-NIT The Network Information Table for TLV (TLV-NIT) represents information on the physical configuration of the TLV stream transmitted by the network and the characteristics of the network itself.

[0029] (2) AMT The Address Map Table (AMT) provides a list of multicast groups of IP packets constituting each service transmitted in the network.

[0030] (3) Table set by the operator In addition, it is possible to prepare a table independently set by a service provider or the like.

[0031] <Descriptor used in TLV-SI> Fig. 5B shows a list of "descriptors" arranged in the TLV-SI of the broadcast system to which the broadcast receiver 100 of this embodiment corresponds. In this embodiment, the following shall be used as the "descriptors" of TLV-SI.

[0032] (1) Service list descriptor The service list descriptor provides a list of services by service identification and service format type.

[0033] (2) Satellite distribution system descriptor The satellite distribution system descriptor indicates the physical conditions of the satellite transmission path.

[0034] (3) System management descriptor The system management descriptor is used to distinguish between broadcast and non-broadcast.

[0035] (4) Network name descriptor The network name descriptor describes the network name by character code.

[0036] (5) Descriptor set by the operator In addition, it is possible to prepare a descriptor independently set by a service provider or the like.

[0037] <Message used in MMT-SI> Fig. 6A shows a list of "messages" used in the MMT-SI of the broadcast system to which the broadcast receiver 100 of this embodiment corresponds. In this embodiment, the following shall be used as the "messages" of MMT-SI.

[0038] (1) PA message The Package Access (PA) message is used to transmit various tables.

[0039] (2) M2 Section Message The M2 section message is used to transmit the section extension format of MPEG-2 Systems.

[0040] (3) CA Message The CA message is used to transmit a table for identifying the restricted reception method.

[0041] (4) M2 Short Section Message The M2 short section message is used to transmit the short section format of MPEG-2 Systems.

[0042] (5) Data Transmission Message The data transmission message is a message that stores a table related to data transmission.

[0043] (6) Message Set by Operator In addition, it is possible to prepare messages independently set by service providers and the like.

[0044] <Tables Used in MMT-SI> Figure 6B shows a list of the 'tables' used in the MMT-SI of the broadcast system corresponding to the broadcast receiver 100 of this embodiment. The table is control information having elements and attributes indicating specific information, and is to be stored in a message and transmitted by an MMTP packet. Note that the message storing the table may be determined according to the table. In this embodiment, the following are used as the 'tables' of MMT-SI.

[0045] (1) MPT The MMT package table (MMT Package Table: MPT) provides information constituting a package such as a list of assets and the positions of assets on the network. The MPT may be stored in the PA message.

[0046] (2) PLT The Package List Table (PLT) lists the IP data flows and packet IDs that transmit PA messages of MMT packages provided as broadcast services, as well as the IP data flows that transmit IP services. The PLT may be stored in the PA message.

[0047] (3)LCT The Layout Configuration Table (LCT) is used to associate layout information for presentation with a layout number, and can be stored in the PA message.

[0048] (4)ECM The Entitlement Control Message (ECM) is common information consisting of program information and control information, and delivers key information for descrambling, etc. The ECM may be stored in the M2 section message.

[0049] (5) EMM The Entitlement Management Message (EMM) transmits individual information including contract information for each subscriber and key information for decrypting ECM (common information). The EMM may be stored in the M2 section message.

[0050] (6) CAT(MH) The Conditional Access Table (CAT) (MH) is used to store descriptors for identifying conditional access systems. The CAT (MH) may be stored in a CA message.

[0051] (7) DCM The Download Control Message (DCM) transmits key-related information, such as a key for decrypting a transmission path encryption for downloading. The DCM may be stored in the M2 section message.

[0052] (8)DMM The Download Management Message (DMM) transmits key-related information, such as a download key for decrypting the DCM. The DMM may be stored in the M2 section message.

[0053] (9)MH-EIT The MH-Event Information Table (MH-EIT) is time-series information about events included in each service. The MH-EIT may be stored in the M2 section message.

[0054] (10)MH-AIT The MH-Application Information Table (MH-AIT) stores all information related to applications and the activation state required for the application, etc. The MH-AIT may be stored in the M2 section message.

[0055] (11)MH-BIT The MH-Broadcaster Information Table (MH-BIT) is used to present information about broadcasters present on the network. The MH-BIT may be stored in the M2 section message.

[0056] (12)MH-SDTT The MH-Software Download Trigger Table (MH-SDTT) is used for download notification information and may be stored in the M2 section message.

[0057] (13)MH-SDT The MH-Service Description Table (MH-SDT) has sub-tables that represent the services included in a specific TLV stream, and transmits information about the channel, such as the channel name, the broadcaster name, etc. The MH-SDT can be stored in the M2 section message.

[0058] (14)MH-TOT The MH-Time Offset Table (MH-TOT) carries JST time and date (Modified Julian Day) information. The MH-TOT can be stored in the M2 short section message.

[0059] (15)MH-CDT The MH-Common Data Table (MH-CDT) is used to transmit common data in the form of sections to be stored in non-volatile memory for all receivers that receive this. The MH-CDT may be stored in an M2 section message.

[0060] (16) DDM Table A Data Directory Management Table (DDM table) provides a directory structure of files that constitute an application in order to separate the file structure of the application from the structure for file transmission. The DDM table can be stored in a data transmission message.

[0061] (17) DAM Table The Data Asset Management Table (DAM table) provides the configuration of the MPUs in the asset and version information for each MPU. The DAM table can be stored in a data transmission message.

[0062] (18) DCC Table The Data Content Configuration Table (DCC Table) provides configuration information of files as data content in order to achieve flexible and effective cache control. The DCC table may be stored in a data transmission message.

[0063] (19)EMT The Event Message Table (EMT) is used to transmit information related to event messages. The EMT may be stored in the M2 section message.

[0064] (20)Tables set by operators In addition, it is possible to prepare tables independently set by service providers and the like.

[0065] <Descriptors used in MMT-SI> Figures 6C and 6D show a list of "descriptors" arranged in the MMT-SI of the broadcast system to which the broadcast receiving apparatus 100 of this embodiment corresponds. A descriptor is control information that provides more detailed information and is assumed to be arranged in a table. Note that the table in which the descriptor is arranged may be determined according to the descriptor. In this embodiment, the following are used as the "descriptors" of MMT-SI.

[0066] (1) Asset Group Descriptor The Asset Group Descriptor provides the group relationship of assets and the priority within the group. The Asset Group Descriptor may be arranged in MPT.

[0067] (2) Event Package Descriptor The Event Package Descriptor provides the correspondence between events representing programs and packages. The Event Package Descriptor may be arranged in the MH-EIT transmitted in the M2 section message.

[0068] (3) Background Color Specification Descriptor The background color specification descriptor provides the background color of the backmost element in the layout specification. The background color specification descriptor may be placed in the LCT.

[0069] (4) MPU presentation area specification descriptor The MPU presentation area specification descriptor provides the location where the MPU is presented. The MPU presentation area specification descriptor can be placed in the MPT.

[0070] (5) MPU timestamp descriptor The MPU timestamp descriptor indicates the presentation time of the first access unit in presentation order in the MPU. The MPU timestamp descriptor may be placed in the MPT.

[0071] (6) Dependency Descriptor The dependency descriptor provides the asset ID of the dependent asset. The dependency descriptor can be placed in the MPT.

[0072] (7) Access control descriptor The access control descriptor provides information for identifying the conditional access scheme. The access control descriptor can be placed in the MPT or CAT(MH).

[0073] (8) Scrambling method descriptor The scrambling method descriptor provides information for identifying the encryption target and the type of encryption algorithm used during scrambling. The scrambling method descriptor may be placed in the MPT or CAT(MH).

[0074] (9) Message authentication method descriptor The message authentication scheme descriptor provides information for identifying the message authentication scheme when performing message authentication. The message authentication scheme descriptor can be placed in the MPT or CAT(MH).

[0075] (10) Emergency Information Descriptor (MH) The emergency information descriptor (MH) is used when an emergency alert is broadcast. The emergency information descriptor (MH) may be placed in the MPT.

[0076] (11) MH-MPEG-4 Audio Descriptor The MH-MPEG-4 Audio Descriptor is used to describe basic information for specifying the coding parameters of an audio stream of ISO / IEC 14496-3 (MPEG-4 Audio). The MH-MPEG-4 Audio Descriptor can be placed in the MPT.

[0077] (12) MH-MPEG-4 Audio Extension Descriptor The MH-MPEG-4 Audio Extension Descriptor is used to describe the profile and level of an MPEG-4 audio stream and encoding method specific settings. The MH-MPEG-4 Audio Extension Descriptor can be placed in the MPT.

[0078] (13) MH-HEVC Video Descriptor The MH-HEVC video descriptor is used to describe the basic coding parameters of a video stream (HEVC stream) in ITU-T Recommendation H.265 | ISO / IEC 23008-2. The MH-HEVC video descriptor can be placed in the MPT.

[0079] (14) MH-Link Descriptor The MH-Link Descriptor identifies the service that will be provided if a viewer requests additional information related to a particular listing in the program service information system. The MH-Link Descriptor may be located in the MPT, MH-EIT, MH-SDT, etc.

[0080] (15) MH-Event Group Descriptor The MH-Event Group Descriptor is used to indicate that multiple events are grouped when there is a relationship between them. The MH-Event Group Descriptor may be placed in the MH-EIT.

[0081] (16) MH-Service List Descriptor The MH-Service List Descriptor provides a list of services by service identification and service type. The MH-Service List Descriptor may be placed in the MH-BIT.

[0082] (17)MH-Short Form Event Descriptor The MH-Short Event Descriptor represents the event name and a short description of the event in text form. The MH-Short Event Descriptor can be placed in the MH-EIT.

[0083] (18) MH-Extended Event Descriptor The MH-Extended Event Descriptor is used in addition to the MH-Short Event Descriptor to provide a detailed description of the event. The MH-Extended Event Descriptor may be placed in the MH-EIT.

[0084] (19) Video Component Descriptor The video component descriptor indicates parameters and descriptions related to the video component and is also used to express the elementary stream in text form. The video component descriptor may be placed in the MPT or MH-EIT.

[0085] (20) MH-Stream Identification Descriptor The MH-Stream Identification Descriptor is used to label the component stream of a service and to reference the description indicated by the video component descriptor in the MH-EIT using this label. The MH-Stream Identification Descriptor may be placed in the MPT.

[0086] (21) MH-Content Descriptor The MH-Content Descriptor indicates the genre of the event. The MH-Content Descriptor may be placed in the MH-EIT.

[0087] (22) MH-Parental Rate Descriptor The MH-ParentalRating Descriptor is used to indicate age-based viewing restrictions and to extend them to other restriction conditions. The MH-ParentalRating Descriptor can be placed in the MPT or the MH-EIT.

[0088] (23) MH-Audio Component Descriptor The MH-Audio Component Descriptor indicates each parameter of an audio elementary stream and is also used to express the elementary stream in text format. The MH-Audio Component Descriptor can be placed in the MPT or the MH-EIT.

[0089] (24)MH-Target Area Descriptor The MH-Target Region Descriptor is used to describe the region targeted by a program or some of the streams that make up a program. The MH-Target Region Descriptor may be placed in the MPT.

[0090] (25) MH-Series Descriptor The MH-series descriptor is used to identify a series of programs and may be placed in the MH-EIT.

[0091] (26) MH-SI Transmission Parameter Descriptor The MH-SI transmission parameter descriptor is used to indicate the transmission parameters of the SI, and may be located in the MH-BIT.

[0092] (27) MH-Broadcaster Name Descriptor The MH-Broadcaster Name Descriptor describes the name of the broadcaster. The MH-Broadcaster Name Descriptor may be placed in the MH-BIT.

[0093] (28)MH-Service Descriptor The MH-service descriptor represents the name of the organization channel and the name of its operator together with the service format type in character codes. The MH-service descriptor may be placed in the MH-SDT.

[0094] (29) IP Data Flow Descriptor The IP data flow descriptor provides information about the IP data flows that make up a service. The IP data flow descriptor can be placed in the MH-SDT.

[0095] (30)MH-CA startup descriptor The MH-CA startup descriptor describes startup information for starting a CAS program on the CAS platform. The MH-CA startup descriptor can be placed in the MPT or CAT (CA).

[0096] (31) MH-Type Descriptor The MH-Type descriptor indicates the type of file transmitted by the application transmission method. The MH-Type descriptor can be placed in the DAM table.

[0097] (32)MH-Info Descriptor The MH-Info descriptor describes information about an MPU or an item. The MH-Info descriptor can be placed in a DAM table.

[0098] (33)MH-Expire Descriptor The MH-Expire descriptor describes the expiration date of an item. The MH-Expire descriptor can be placed in the DAM table.

[0099] (34) MH-Compression Type Descriptor The MH-Compression Type descriptor indicates that the item being transmitted is compressed, and indicates the compression algorithm and the number of bytes of the item before compression. The MH-Compression Type descriptor can be placed in the DAM table.

[0100] (35) MH-Data Encoding Method Descriptor The MH-Data Coding Descriptor is used to identify the data coding scheme. The MH-Data Coding Descriptor can be placed in the MPT.

[0101] (36) UTC-NPT Reference Descriptor The UTC-NPT reference descriptor is used to convey the relationship between NPT (Normal Play Time) and UTC. The UTC-NPT reference descriptor can be placed in the EMT.

[0102] (37) Event Message Descriptor The event message descriptor conveys information about the event message in general and can be placed in the EMT.

[0103] (38)MH-Local Time Offset Descriptor The MH-Local Time Offset Descriptor is used when daylight saving time is in effect to provide a certain offset value between the actual time (e.g., UTC+9 hours) and the displayed time in the human system. The MH-Local Time Offset Descriptor may be placed in the MH-TOT.

[0104] (39)MH-Component Group Descriptor The MH-component group descriptor defines and identifies the combination of components in an event and can be placed in the MH-EIT.

[0105] (40) MH-Logo Transmission Descriptor The MH-Logo Transmission Descriptor is used to describe a simple logo character string, pointing to a logo in CDT format, etc. The MH-Logo Transmission Descriptor may be placed in the MH-SDT.

[0106] (41) MPU Extended Timestamp Descriptor The MPU extended timestamp descriptor provides the decoding time of an access unit within the MPU. The MPU extended timestamp descriptor may be placed in the MPT.

[0107] (42) MPU Download Content Descriptor The MPU download content descriptor is used to describe attribute information of content downloaded using an MPU. The MPU download content descriptor may be placed in the MH-SDTT.

[0108] (43)MH-Network Download Content Descriptor The MH-Network Download Content Descriptor is used to describe attribute information of content downloaded using a network. The MH-Network Download Content Descriptor may be placed in the MH-SDTT.

[0109] (44)MH-Application Descriptor The MH-application descriptor describes information about an application and may be placed in the MH-AIT.

[0110] (45)MH-Transmission Protocol Descriptor The MH-transmission protocol descriptor is used to specify a transmission protocol such as broadcasting or communication and to indicate location information of an application that depends on the transmission protocol. The MH-transmission protocol descriptor may be placed in the MH-AIT.

[0111] (46)MH-Simple Application Location Descriptor The MH-simple application location descriptor is written to indicate details of where to obtain the application. The MH-simple application location descriptor can be placed in the MH-AIT.

[0112] (47)MH-Application Boundary Authority Setting Descriptor The MH-application boundary authority setting descriptor is used to set an application boundary and to set broadcast resource access authority for each area (URL). The MH-application boundary authority setting descriptor may be placed in the MH-AIT.

[0113] (48)MH-Boot Priority Information Descriptor The MH-launch priority information descriptor is written to specify the launch priority of an application. The MH-launch priority information descriptor may be placed in the MH-AIT.

[0114] (49)MH-Cache Information Descriptor The MH-cache information descriptor is described for use in cache control when the resources that make up an application are cached and stored when the application is expected to be reused. The MH-cache information descriptor may be placed in the MH-AIT.

[0115] (50)MH-Probabilistic Adaptive Delay Descriptor The MH-probabilistic application delay descriptor is described to delay the timing of application control by a probabilistic delay amount, assuming load balancing of server access for application acquisition. The MH-probabilistic application delay descriptor may be placed in the MH-AIT.

[0116] (51) Link PU Descriptor The link destination PU descriptor describes other presentation units that may be transitioned from the presentation unit (PU). The link destination PU descriptor may be placed in the DCC table.

[0117] (52) Lock Cache Specification Descriptor The lock cache specification descriptor describes the specification of a file to be cached and locked in the presentation unit. The lock cache specification descriptor may be placed in the DCC table.

[0118] (53) Unlock cache specification descriptor The unlock cache specification descriptor describes the specification of a file to be unlocked among the files locked in the presentation unit. The unlock cache specification descriptor may be placed in the DCC table.

[0119] (54) Descriptors set by the operator In addition, it is possible to prepare descriptors independently set by service providers and the like.

[0120] <Relationship between data transmission and each control information in the MMT method> Here, using FIG. 6E, the relationship between data transmission and representative tables in the broadcast system corresponding to the broadcast receiving apparatus 100 of the present embodiment will be described.

[0121] In the broadcast system corresponding to the broadcast receiving apparatus 100 of the present embodiment, data can be transmitted through a plurality of paths, such as a TLV stream via a broadcast transmission path or an IP data flow via a communication line. The TLV stream includes TLV-SI such as TLV-NIT and AMT, and an IP data flow which is a data flow of IP packets. The IP data flow includes a video asset including a series of video MPUs and an audio asset including a series of audio MPUs. Similarly, the IP data flow may include a subtitle asset including a series of subtitle MPUs, a character super asset including a series of character super MPUs, a data asset including a series of data MPUs, and the like. These various assets are associated with each other in units of "packages" by an MPT (MMT package table) stored in a PA message and transmitted. Specifically, the association is performed by describing a package ID (corresponding to the "MMT_package_id_byte" parameter shown in FIG. 17 described later) and an asset ID of each asset included in the package (corresponding to the "asset_id_byte" parameter shown in FIG. 17 described later) in the MPT.

[0122] The assets that make up a package can be only assets in a TLV stream, but as shown in Fig. 6E, they can also include assets transmitted via IP data flows on communication lines. This can be achieved by including location information (corresponding to "MMT_general_location_info()" shown in Fig. 17, which will be described later) of each asset included in the package in the MPT, so that the broadcast receiving device 100 of this embodiment can grasp the reference destination of each asset. Specifically, by changing the value of the "MMT_general_location_infonolocation_type" parameter placed in the location information, (1) Data multiplexed in the same IP data flow as MPT (location_type=0x00) (2) Data multiplexed in IPv4 data flow (location_type=0x01) (3) Data multiplexed in IPv6 data flows (location_type=0x02) (4) Data multiplexed into broadcast MPEG2-TS (location_type=0x03) (5) Data multiplexed in MPEG2-TS format within the IP data flow (location_type=0x04) (6) Data at the specified URL (location_type=0x05) It is possible to configure the broadcast receiving device 100 so that it can refer to various types of data transmitted via various transmission paths such as the above.

[0123] Of the above-mentioned reference destinations, (1) is, for example, an IP data flow received via a digital broadcast signal received by the tuner / demodulator unit 131 of the broadcast receiving device 100 shown in FIG. 7A (described later). When the MPT is also transmitted as part of the IP data flow on the communication line, the reference destination of (1) may be an IP data flow received via the communication line by the LAN communication unit 121 (described later). Also, (2), (3), (5), and (6) are IP data flows received via the communication line by the LAN communication unit 121 (described later). Also, (4) can be used, for example, in the case of a broadcast receiving device having both a receiving function for receiving digital broadcast signals using the MMT system and a receiving function for receiving digital broadcast signals using the MPEG2-TS system, such as the broadcast receiving device 800 of the second embodiment shown in FIG. 24 (described later), to refer to data multiplexed in the MPEG2-TS received by the receiving function for receiving digital broadcast signals using the MPEG2-TS system, based on the location information ("MMT_general_location_info()") of the MPT included in the digital broadcast signals using the MMT system.

[0124] Although the data constituting a "package" is specified in this manner, in the broadcasting system compatible with the broadcast receiving device 100 of this embodiment, a series of data in this "package" unit is treated as a "service" unit for digital broadcasting.

[0125] Furthermore, the MPT describes presentation time information for each MPU designated by the MPT (corresponding to the "mpu_presentation_time" parameter shown in FIG. 13B, which will be described later), and using this presentation time information, it becomes possible to present (display, output, etc.) multiple MPUs designated by the MPT in a synchronized manner based on a clock based on NTP, which is time information in UTC notation. Presentation control of various data using this NTP-based clock will be described later.

[0126] The data transmission method of this embodiment shown in Figure 6E also has the concept of an "event." An "event" is a concept that indicates a so-called "program" handled by the MH-EIT that is included in the M2 section message and sent. Specifically, in a "package" indicated by an event package descriptor stored in the MH-EIT, a series of data included in a period from the start time stored in the MH-EIT (corresponding to the "start_time" parameter shown in Figure 21, which will be described later) to the duration (corresponding to the "duration" parameter shown in Figure 21, which will be described later) is the data included in the concept of the "event." The MH-EIT can be used in the broadcast receiving device 100 of this embodiment for various processes on an "event" basis (for example, generating a program guide, controlling recording and viewing reservations, and copyright management processes such as temporary storage).

[0127] [Broadcast receiving device hardware configuration] 7A is a block diagram showing an example of the internal configuration of broadcast receiving device 100. Broadcast receiving device 100 is made up of main control unit 101, system bus 102, ROM 103, RAM 104, storage (accumulation) unit 110, LAN communication unit 121, extension interface unit 124, digital interface unit 125, tuner / demodulation unit 131, separation unit 132, video decoder 141, video color gamut conversion unit 142, audio decoder 143, superimposed text decoder 144, subtitle decoder 145, subtitle synthesis unit 146, subtitle color gamut conversion unit 147, data decoder 151, cache unit 152, application control unit 153, browser unit 154, application color gamut conversion unit 155, sound source unit 156, video synthesis unit 161, monitor unit 162, video output unit 163, audio synthesis unit 164, speaker unit 165, audio output unit 166, and operation input unit 170.

[0128] The main control unit 101 is a microprocessor unit that controls the entire broadcast receiving device 100 in accordance with a predetermined operation program. The system bus 102 is a data communication path for transmitting and receiving data between the main control unit 101 and each operation block within the broadcast receiving device 100.

[0129] The ROM (Read Only Memory) 103 is a non-volatile memory that stores basic operation programs such as an operating system and other operation programs, and may be a rewritable ROM such as an EEPROM (Electrically Erasable Programmable ROM) or a flash ROM. The ROM 103 may also store operation setting values ​​necessary for the operation of the broadcast receiving device 100. The RAM (Random Access Memory) 104 serves as a work area when the basic operation programs and other operation programs are executed. The ROM 103 and the RAM 104 may be integrated with the main control unit 101. The ROM 103 may not be an independent configuration as shown in FIG. 7A, but may use a partial storage area within the storage (accumulation) unit 110.

[0130] The storage (accumulation) unit 110 stores the operating programs and operation setting values ​​of the broadcast receiving device 100, personal information of the user of the broadcast receiving device 100, etc. It can also store operating programs downloaded via the Internet 200 and various data created by the operating programs. It can also store content such as moving images, still images, and audio acquired from broadcast waves or downloaded via the Internet 200. A portion of the storage (accumulation) unit 110 may replace all or part of the functions of the ROM 103. Furthermore, the storage (accumulation) unit 110 needs to retain the stored information even when power is not supplied to the broadcast receiving device 100 from an external source. Therefore, devices such as nonvolatile semiconductor memory such as flash ROM or SSD (Solid State Drive), or magnetic disk drive such as HDD (Hard Disk Drive) are used.

[0131] It should be noted that the operation programs stored in the ROM 103 and storage (accumulation) unit 110 can be added, updated, and have their functions expanded by downloading from each server device on the Internet 200 .

[0132] The LAN (Local Area Network) communication unit 121 is connected to the Internet 200 via the router device 200r, and transmits and receives data to and from each server device and other communication devices on the Internet 200. It also acquires the MMT data string (or a part thereof) of a program transmitted via a communication line. The connection with the router device 200r may be a wired connection or a wireless connection such as Wi-Fi (registered trademark). The LAN communication unit 121 includes an encoding circuit, a decoding circuit, etc. The broadcast receiving device 100 may also include other communication units such as a Bluetooth (registered trademark) communication unit, an NFC communication unit, or an infrared communication unit.

[0133] The tuner / demodulator 131 receives broadcast waves transmitted from a radio tower 300t via the antenna 100a, and tunes (selects) to a channel of a service desired by the user under the control of the main controller 101. Furthermore, the tuner / demodulator 131 demodulates the received broadcast signal to acquire an MMT data string. Note that while the example shown in FIG. 7A illustrates a configuration with one tuner / demodulator, the broadcast receiving device 100 may be configured to include multiple tuner / demodulators for purposes such as simultaneous display on multiple screens or recording of a different program.

[0134] The demultiplexer 132 is an MMT decoder that distributes real-time presentation elements, such as a video data string, an audio data string, a superimposed text data string, and a subtitle data string, to the video decoder 141, the audio decoder 143, the superimposed text data string, and the subtitle decoder 145, based on control signals in the input MMT data string. The data input to the demultiplexer 132 may be an MMT data string transmitted via a broadcast transmission path and demodulated by the tuner / demodulator 131, or an MMT data string transmitted via a communication line and received by the LAN communication unit 121. The demultiplexer 132 also plays back multimedia applications and their component file-based data, temporarily storing them in the cache unit 152. The demultiplexer 132 also extracts general-purpose data and outputs it to the data decoder 151 for use in streaming data for a player or application that presents data other than video, audio, and subtitles. The demultiplexer 132 may also perform error correction and access restriction control on the input MMT data string under the control of the main control unit 101.

[0135] Video decoder 141 decodes the video data string input from separation unit 132 and outputs video information. Video color gamut conversion unit 142 performs color space conversion processing on the video information decoded by video decoder 141 as needed for video synthesis processing in video synthesis unit 161. Audio decoder 143 decodes the audio data string input from separation unit 132 and outputs the audio information. Streaming data in, for example, MPEG-DASH (MPEG-Dynamic Adaptive Streaming over HTTP) format acquired from the Internet 200 via LAN communication unit 121 may also be input to video decoder 141 and audio decoder 143. A plurality of video decoders 141, video color gamut conversion units 142, audio decoders 143, etc. may be provided in order to simultaneously decode and process multiple types of video data strings and audio data strings.

[0136] The superimpose decoder 144 decodes the superimpose data string input from the separation unit 132 and outputs superimpose information. The subtitle decoder 145 decodes the subtitle data string input from the separation unit 132 and outputs subtitle information. The superimpose information output from the superimpose decoder 144 and the subtitle information output from the subtitle decoder 145 are combined in the subtitle composition unit 146, and further, in the subtitle color gamut conversion unit 147, color space conversion is performed as necessary for the video composition process in the video composition unit 161. Note that in this embodiment, of the services that mainly consist of text information presented simultaneously with the video of a broadcast program, those related to the content of the video are referred to as subtitles, and other services are referred to as superimposes. Furthermore, when there is no need to distinguish between them, they are collectively referred to as subtitles.

[0137] Browser unit 154 presents multimedia application files and their constituent file data obtained from a server device on Internet 200 via cache unit 152 or LAN communication unit 121, in accordance with instructions from application control unit 153, which interprets control information included in an MMT data string and control information obtained from a server device on Internet 200 via LAN communication unit 121. The multimedia application files may be HTML (Hyper Text Markup Language) documents, BML (Broadcast Markup Language) documents, etc. The application information output from browser unit 154 is further subjected to color space conversion processing as necessary in application color gamut conversion unit 155 for video synthesis processing in video synthesis unit 161. Browser unit 154 also plays application audio information by instructing sound source unit 156.

[0138] The video synthesis unit 161 receives the video information output from the video color gamut conversion unit 142, the subtitle information output from the subtitle color gamut conversion unit 147, the application information output from the application color gamut conversion unit 155, and other information, and performs appropriate processing such as selection and / or superimposition. The video synthesis unit 161 includes a video RAM (not shown), and drives the monitor unit 162 and other units based on the video information and other information input to the video RAM. Furthermore, under the control of the main control unit 101, the video synthesis unit 161 performs scaling processing and superimposition processing of EPG (Electronic Program Guide) screen information created based on information such as the MH-EIT included in the MMT-SI, as necessary. The monitor unit 162 is a display device such as a liquid crystal panel, and provides the video information selected and / or superimposed by the video synthesis unit 161 to the user of the broadcast receiving device 100. The video output unit 163 is a video output interface that outputs the video information selected and / or superimposed by the video synthesis unit 161.

[0139] The presentation function of the broadcast receiving device 100 of this embodiment is assumed to have a logical plane structure to display multimedia services as intended by the provider. FIG. 7B shows an example of the logical plane structure of the presentation function of the broadcast receiving device 100 of this embodiment. In this logical plane structure, a subtitle plane for displaying subtitles is placed in the foreground, and a subtitle plane for displaying subtitles is placed in the next layer. A multimedia plane for displaying broadcast video, multimedia applications, or composite video thereof is placed in the third layer, and a background plane is placed in the background. The subtitle synthesis unit 146 and the video synthesis unit 161 draw subtitle information on the subtitle plane, subtitle information on the subtitle plane, and video information, application information, etc. on the multimedia plane. In addition, a background color is drawn on the background plane based on the LCT, etc. included in the MMT-SI. It is assumed that multiple third-layer multimedia planes can be prepared depending on the number of video decoders 141. However, even if multiple multimedia planes are present, application information, etc. output from the application color gamut conversion unit 155 is output only to the foreground multimedia plane.

[0140] The audio synthesis unit 164 receives the audio information output from the audio decoder 143 and the application audio information reproduced by the sound source unit 156 and performs processing such as appropriate selection and / or mixing. The speaker unit 165 provides the audio information that has been selected and / or mixed by the audio synthesis unit 164 to the user of the broadcast receiving device 100. The audio output unit 166 is an audio output interface that outputs the audio information that has been selected and / or mixed by the audio synthesis unit 164.

[0141] The expansion interface unit 124 is a group of interfaces for expanding the functions of the broadcast receiving device 100, and in this embodiment is configured with an analog video / audio interface, a USB (Universal Serial Bus) interface, a memory interface, etc. The analog video / audio interface inputs analog video signals / audio signals from external video / audio output devices, outputs analog video signals / audio signals to external video / audio input devices, etc. The USB interface connects to a PC or the like to send and receive data. A HDD may be connected to record broadcast programs and content. A keyboard or other USB device may also be connected. The memory interface connects to a memory card or other memory medium to send and receive data.

[0142] The digital interface unit 125 is an interface that outputs or inputs encoded digital video data and / or digital audio data. The digital interface unit 125 is capable of directly outputting an MMT data string obtained by demodulation in the tuner / demodulation unit 131, an MMT data string acquired via the LAN communication unit 121, or mixed data of the above-mentioned MMT data strings. The digital interface unit 125 may also be controlled so that the MMT data string input from the digital interface unit 125 is input to the separation unit 132. The output of digital content stored in the storage (accumulation) unit 110 or the storage of digital content in the storage (accumulation) unit 110 may be performed via the digital interface unit 125.

[0143] The digital interface unit 125 may be a DVI terminal, an HDMI (registered trademark) terminal, a Display Port (registered trademark) terminal, or the like, which outputs or inputs data in a format conforming to the DVI specification, the HDMI specification, the Display Port specification, or the like. It may also output or input data in the form of serial data conforming to the IEEE 1394 specification, or the like. It may also be configured as an IP interface which outputs digital interface data via hardware such as Ethernet (registered trademark) or wireless LAN. In this case, the digital interface unit 125 and the LAN communication unit 121 may share the same hardware configuration.

[0144] The operation input unit 170 is an instruction input unit that inputs operation instructions to the broadcast receiving device 100, and in this embodiment is configured with a remote control receiving unit that receives commands transmitted from a remote control (not shown) and an operation key with an array of button switches. Only one of them may be provided. The operation input unit 170 may also be replaced by a touch panel placed on top of the monitor unit 162. It may also be replaced by a keyboard or the like connected to the extension interface unit 124. The remote control (not shown) may also be replaced by a mobile information terminal 700 equipped with a remote control command transmission function.

[0145] As described above, when the broadcast receiving device 100 is a television receiver or the like, the video output unit 163 and the audio output unit 166 are not essential components of the present invention. Furthermore, the broadcast receiving device 100 may be a television receiver, an optical disk drive recorder such as a DVD (Digital Versatile Disc) recorder, a magnetic disk drive recorder such as an HDD recorder, a set-top box (STB), or the like. It may also be a personal computer (PC), tablet terminal, navigation device, game console, or the like equipped with a digital broadcast receiving function and a broadcast / communication linkage function. When the broadcast receiving device 100 is a DVD recorder, HDD recorder, STB, or the like, the monitor unit 162 and the speaker unit 165 may not be provided. Connecting an external monitor and external speaker to the video output unit 163 and the audio output unit 166 or the digital interface unit 125 enables the broadcast receiving device 100 to operate in the same manner as the broadcast receiving device 100 of this embodiment.

[0146] [System configuration for clock synchronization / presentation synchronization of broadcast receiving devices] FIG. 7C shows an example of a system configuration for clock synchronization / presentation synchronization in a broadcasting system compatible with the broadcast receiving device 100 of this embodiment. In this broadcasting system, UTC is transmitted from the broadcast transmission system to the receiver (such as the broadcast receiving device 100 of this embodiment) in a 64-bit NTP timestamp format. In this NTP timestamp format, UTC "seconds or more" are represented by 32 bits, and "less than a second" is represented by 32 bits. However, in practice, it is difficult to reproduce one second with 32-bit precision. For this reason, a system clock for synchronizing a video system or for operating an NTP-formatted clock may have a frequency of, for example, 2 to the 24th power Hz (approximately 16.8 MHz), as shown in the figure. Note that, considering that the system clock in conventional broadcasting systems was 27 MHz and the ease of constructing a receiver hardware configuration, it is desirable to use a frequency that is a power of 2, such as 2 to the 28th power, as the system clock.

[0147] In addition, when the system clock on the broadcast transmission system side or the receiver side is set to a frequency of a power of 2, such as "2 to the 24th power" to "2 to the 28th power," as described above, the lowest 8 to 4 bits of the NTP timestamp format transmitted from the broadcast transmission system side to the receiver side, which are not referenced by the PLL (Phase Locked Loop) system for regenerating the system clock or the NTP format clock, may be fixed to "0" or "1." In other words, if the system clock is "2 to the nth power" Hz (n=24 in the example of FIG. 7C), the lowest "32-n" bits of the NTP timestamp format may be fixed to "0" or "1." Alternatively, the receiver side may process the lowest "32-n" bits of the NTP timestamp format to be ignored.

[0148] When the broadcast transmission system receives NTP-formatted time information from an external source, it configures a PLL system with a 32+n-bit counter using a 2n-Hz VCO (Voltage Controlled Oscillator) to create a transmission system clock that synchronizes with the externally provided time information. The entire signal processing system operates in synchronization with the 2n-Hz system clock. Furthermore, the output of the transmission system clock is periodically transmitted to the receiver via the broadcast transmission path as NTP-formatted time information.

[0149] The receiver receives time information in NTP format via the broadcast transmission path and, like the broadcast transmission system, regenerates the receiving system clock using a PLL system based on a 2 to the nth power VCO. This synchronizes the receiving system clock with the broadcast transmission system. Furthermore, by operating the receiver's signal processing system in synchronization with the 2 to the nth power system clock, clock synchronization between the broadcast transmission system and the receiver is achieved, enabling stable signal playback. The broadcast transmission system sets the decoding time and presentation time for each presentation unit of the video / audio signal based on the NTP format time information. The MPT stored in the PA message transmitted in the broadcast signal contains the MPU timestamp descriptor shown in Figure 13B (described later). The "mpu_sequence_number" parameter in the MPU timestamp descriptor in Figure 13B indicates the sequence number of the MPU describing the timestamp, and the "mpu_presentation_time" parameter indicates the MPU presentation time in 64-bit NTP timestamp format. Therefore, the receiver can refer to the MPU timestamp descriptor stored in the MPT and control the presentation (display, output, etc.) timing of video signals, audio signals, subtitles, superimposed text, etc. for each MPU.

[0150] Note that, when focusing on the control of the decoding timing and presentation timing for each presentation unit of the aforementioned video / audio signals, etc., synchronization of the video / audio signals can be ensured even with a clock of about 2 to the power of 16 Hz (approximately 65.5 kHz). In this case, it is not necessary to refer to the lower 16 bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. In other words, if a clock of 2 to the power of m Hz generated by dividing the system clock, etc. is used to control the decoding timing and presentation timing, it is not necessary to refer to the lower 32-m bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. Therefore, the lower 32-m bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. may be fixed to "0" or "1."

[0151] [Software configuration of broadcast receiving device] 7D is a software configuration diagram of the broadcast receiving device 100 of this embodiment, and shows the software configuration in the ROM 103, RAM 104, and storage (accumulation) unit 110. In this embodiment, a basic operation program 1001 and other operation programs are stored in the ROM 103, and a receiving function program 1002 and other operation programs are stored in the storage (accumulation) unit 110. The storage (accumulation) unit 110 is also assumed to include a content storage area 1200 for storing content such as moving images, still images, and audio, an authentication information storage area 1300 for storing authentication information and the like required when accessing external mobile terminal devices and each server device, and various information storage areas for storing various other information.

[0152] The basic operation program 1001 stored in the ROM 103 is loaded into the RAM 104, and the main control unit 101 executes the loaded basic operation program to form a basic operation execution unit 1101. Similarly, the receiving function program 1002 stored in the storage (accumulation) unit 110 is loaded into the RAM 104, and the main control unit 101 executes the loaded receiving function program to form a receiving function execution unit 1102. The RAM 104 also includes a temporary storage area for temporarily storing data created when each operation program is executed, as needed.

[0153] For ease of explanation, the process of controlling each operation block by the main control unit 101 expanding the basic operation program 1001 stored in the ROM 103 into the RAM 104 and executing it will be described below as if the basic operation execution unit 1101 controls each operation block. Similar descriptions will be used for the other operation programs.

[0154] The reception function execution unit 1102 controls each operational block of the broadcast receiving device 100 to play back components such as video and audio transmitted in the broadcast system of this embodiment. In particular, the transport processing unit 1102a mainly controls the MMT decoder function of the separation unit 132 and distributes the video data stream, audio data stream, etc. separated from the MMT data stream to the corresponding decoding processing units. The AV decoding processing unit 1102b mainly controls the video decoder 141, audio decoder 143, etc. The application processing unit 1102c mainly controls the cache unit 152, application control unit 153, browser unit 154, and sound source unit 156. The superimposition processing unit 1102d mainly controls the superimposition decoder 144. The subtitle processing unit 1102e mainly controls the subtitle decoder 145. The general-purpose data processing unit 1102f mainly controls the data decoder 151. The EPG generation unit 1102g interprets the description contents of the MH-EIT etc. included in the MMT-SI and generates an EPG screen. The presentation processing unit 1102h mainly controls the video color gamut conversion unit 142, the subtitle synthesis unit 146, the subtitle color gamut conversion unit 147, the application color gamut conversion unit 155, the video synthesis unit 161, and the audio synthesis unit 164 based on the logical plane structure.

[0155] The operation programs may be stored in the ROM 103 and / or the storage unit 110 before shipping the product. After shipping the product, the operation programs may be acquired from another application server 500 or the like on the Internet 200 via the LAN communication unit 121. Alternatively, the operation programs may be stored in a memory card, an optical disk, or the like and acquired via the expansion interface unit 124 or the like.

[0156] [Broadcasting station server configuration] 8 is a block diagram showing an example of the internal configuration of the broadcast station server 300. The broadcast station server 300 is made up of a main control unit 301, a system bus 302, a RAM 304, a storage unit 310, a LAN communication unit 321, and a digital broadcast signal transmission unit 360.

[0157] The main control unit 301 is a microprocessor unit that controls the entire broadcast station server 300 in accordance with a predetermined operation program. The system bus 302 is a data communication path for transmitting and receiving data between the main control unit 301 and each operation block within the broadcast station server 300. The RAM 304 serves as a work area when each operation program is executed.

[0158] The storage unit 310 stores a basic operation program 3001, a broadcast content management / distribution program 3002, and a broadcast content transmission program 3003, and further includes a broadcast content storage area 3200 and a metadata storage area 3300. The broadcast content storage area 3200 stores program content and the like for each broadcast program broadcast by a broadcast station. The metadata storage area 3300 stores metadata for each broadcast program, such as the program title, program ID, program summary, cast, broadcast date and time, and copy control information for each program content.

[0159] In addition, the basic operation program 3001, broadcast content management / distribution program 3002, and broadcast content sending program 3003 stored in the storage unit 310 are each expanded into RAM 304, and the main control unit 301 executes each of the expanded programs to form a basic operation execution unit 3101, a broadcast content management / distribution execution unit 3102, and a broadcast content sending execution unit 3103.

[0160] For ease of explanation, the process of controlling each operation block by the main control unit 301 expanding the basic operation program 3001 stored in the storage unit 310 into the RAM 304 and executing it will be described below as if the basic operation execution unit 3101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0161] The broadcast content management / distribution execution unit 3102 manages the program content and metadata of each broadcast program stored in the broadcast content storage area 3200 and the metadata storage area 3300, and controls the provision of the program content and metadata of each broadcast program to the service provider based on a contract. Furthermore, when providing the program content and metadata of each broadcast program to the service provider, the broadcast content management / distribution execution unit 3102 may perform authentication processing of the service provider server 400 based on the contract, as necessary.

[0162] The broadcast content transmission execution unit 3103 performs time schedule management when transmitting the program content of the broadcast program stored in the broadcast content storage area 3200 and the MMT data string including the program title, program ID, copy control information of the program content, etc. of the broadcast program stored in the metadata storage area 3300 from the radio tower 300t via the digital broadcast signal transmission unit 360.

[0163] The LAN communication unit 321 is connected to the Internet 200 and communicates with the service provider server 400 and the like on the Internet 200. The LAN communication unit 321 is equipped with an encoding circuit, a decoding circuit, etc. The digital broadcast signal transmission unit 360 modulates an MMT data sequence made up of video data sequences, audio data sequences, program information data sequences, etc. of the program content of each broadcast program stored in the broadcast content storage area 3200, and transmits it as a digital broadcast wave via the radio tower 300t.

[0164] [Service provider server configuration] 9 is a block diagram showing an example of the internal configuration of the service provider server 400. The service provider server 400 is made up of a main control unit 401, a system bus 402, a RAM 404, a storage unit 410, and a LAN communication unit 421.

[0165] The main control unit 401 is a microprocessor unit that controls the entire service provider server 400 in accordance with a predetermined operation program. The system bus 402 is a data communication path for transmitting and receiving data between the main control unit 401 and each operation block in the service provider server 400. The RAM 404 serves as a work area when each operation program is executed.

[0166] The storage unit 410 stores a basic operation program 4001, a video content management / distribution program 4002, and an application management / distribution program 4004, and further includes a video content storage area 4200, a metadata storage area 4300, an application storage area 4400, and a user information storage area 4500. The video content storage area 4200 stores program content of broadcast programs provided by the broadcast station server 300 as video content. It also stores video content and the like produced by the service provider. The metadata storage area 4300 stores various metadata provided by the broadcast station server 300 and metadata related to video content produced by the service provider. The application storage area 4400 stores various applications and the like for realizing services linked to broadcast programs, which are distributed in response to requests from each television receiver. The user information storage area 4500 stores information (personal information, authentication information, etc.) related to users who are permitted to access the service provider server 400.

[0167] In addition, the basic operation program 4001, video content management / distribution program 4002, and application management / distribution program 4004 stored in the storage unit 410 are each expanded into RAM 404, and the main control unit 401 further executes the expanded basic operation program, video content management / distribution program, and application management / distribution program, thereby forming a basic operation execution unit 4101, a video content management / distribution execution unit 4102, and an application management / distribution execution unit 4104.

[0168] For ease of explanation, the process of the main control unit 401 controlling each operation block by loading the basic operation program 4001 stored in the storage unit 410 into the RAM 404 and executing it will be described below as if the basic operation execution unit 4101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0169] The video content management / distribution execution unit 4102 acquires program content and metadata of broadcast programs from the broadcast station server 300, manages the video content and metadata stored in the video content storage area 4200 and the metadata storage area 4300, and controls the distribution of the video content and metadata to each television receiver. Furthermore, the video content management / distribution execution unit 4102 may perform authentication processing for each television receiver as needed when distributing the video content and metadata to each television receiver. Furthermore, the application management / distribution execution unit 4104 manages applications stored in the application storage area 4400 and controls the distribution of each application in response to a request from each television receiver. Furthermore, the application management / distribution execution unit 4104 may perform authentication processing for each television receiver as needed when distributing the application to each television receiver.

[0170] The LAN communication unit 421 is connected to the Internet 200, and communicates with the broadcast station server 300 on the Internet 200 and the broadcast receiving device 100 via the router device 200r. The LAN communication unit 421 is assumed to include an encoding circuit, a decoding circuit, and the like.

[0171] [Hardware configuration of mobile information terminal] 10A is a block diagram showing an example of the internal configuration of a mobile information terminal 700. The mobile information terminal 700 is composed of a main control unit 701, a system bus 702, a ROM 703, a RAM 704, a storage unit 710, a communication processing unit 720, an expansion interface unit 724, an operation unit 730, an image processing unit 740, an audio processing unit 750, and a sensor unit 760.

[0172] The main control unit 701 is a microprocessor unit that controls the entire portable information terminal 700 in accordance with a predetermined operation program. The system bus 702 is a data communication path for transmitting and receiving data between the main control unit 701 and each operation block within the portable information terminal 700.

[0173] The ROM 703 is a memory in which basic operation programs such as an operating system and other operation programs are stored, and may be a rewritable ROM such as an EEPROM or flash ROM. The RAM 704 serves as a work area when the basic operation programs and other operation programs are executed. The ROM 703 and RAM 704 may be integrated with the main control unit 701. The ROM 703 may also use a partial storage area within the storage unit 710, rather than being an independent configuration as shown in FIG. 10A.

[0174] The storage unit 710 stores the operation programs and operation setting values ​​of the portable information terminal 700, personal information of the user of the portable information terminal 700, etc. It can also store operation programs downloaded via the Internet 200 and various data created by the operation programs. It can also store content such as moving images, still images, and audio downloaded via the Internet 200. A portion of the storage unit 710 may replace all or part of the functions of the ROM 703. The storage unit 710 must also retain the stored information even when power is not being supplied to the portable information terminal 700 from an external source. Therefore, for example, a device such as a nonvolatile semiconductor memory such as a flash ROM or SSD, or a magnetic disk drive such as an HDD, is used.

[0175] It should be noted that the operation programs stored in the ROM 703 and storage unit 710 can be added, updated, and have their functions expanded by downloading from each server device on the Internet 200 .

[0176] The communication processing unit 720 is composed of a LAN communication unit 721, a mobile telephone network communication unit 722, and an NFC communication unit 723. The LAN communication unit 721 is connected to the Internet 200 via the router device 200r and the access point 200a, and transmits and receives data to and from each server device and other communication devices on the Internet 200. The connection to the router device 200r and the access point 200a is assumed to be wireless, such as Wi-Fi (registered trademark). The mobile telephone network communication unit 722 performs telephone communication (calls) and data transmission and reception via wireless communication with a base station 600b of the mobile telephone network. The NFC communication unit 723 performs wireless communication when in proximity to a compatible reader / writer. The LAN communication unit 721, the mobile telephone network communication unit 722, and the NFC communication unit 723 each include an encoding circuit, a decoding circuit, an antenna, etc. The communication processing unit 720 may further include other communication units, such as a Bluetooth (registered trademark) communication unit or an infrared communication unit.

[0177] The expansion interface unit 724 is a group of interfaces for expanding the functions of the mobile information terminal 700, and in this embodiment is configured with a video / audio interface, a USB interface, a memory interface, etc. The video / audio interface inputs video signals / audio signals from external video / audio output devices, outputs video signals / audio signals to external video / audio input devices, etc. The USB interface connects to a PC or the like to send and receive data. It may also be used to connect a keyboard or other USB device. The memory interface connects to a memory card or other memory medium to send and receive data.

[0178] The operation unit 730 is an instruction input unit that inputs operation instructions to the mobile information terminal 700, and in this embodiment, is configured with a touch panel 730t arranged on top of the display unit 741 and operation keys 730k with an array of button switches. Only one of these may be used. The mobile information terminal 700 may be operated using a keyboard or the like connected to the extended interface unit 724. The mobile information terminal 700 may be operated using a separate terminal device connected by wired or wireless communication. In other words, the mobile information terminal 700 may be operated from the broadcast receiving device 100. The touch panel function may also be provided in the display unit 741.

[0179] The image processing unit 740 is composed of a display unit 741, an image signal processing unit 742, a first image input unit 743, and a second image input unit 744. The display unit 741 is a display device such as a liquid crystal panel, and provides image data processed by the image signal processing unit 742 to the user of the mobile information terminal 700. The image signal processing unit 742 includes a video RAM (not shown), and the display unit 741 is driven based on image data input to the video RAM. The image signal processing unit 742 also has functions such as format conversion and superimposition processing of menus and other on-screen display (OSD) signals as necessary. The first image input unit 743 and the second image input unit 744 are camera units that input image data of the surroundings or object by converting light input from a lens into an electrical signal using electronic devices such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor) sensor.

[0180] The audio processing unit 750 is made up of an audio output unit 751, an audio signal processing unit 752, and an audio input unit 753. The audio output unit 751 is a speaker, and provides an audio signal processed by the audio signal processing unit 752 to the user of the mobile information terminal 700. The audio input unit 753 is a microphone, and converts the user's voice, etc. into audio data and inputs it.

[0181] The sensor unit 760 is a group of sensors for detecting the state of the portable information terminal 700, and in this embodiment, is composed of a GPS receiver unit 761, a gyro sensor 762, a geomagnetic sensor 763, an acceleration sensor 764, an illuminance sensor 765, and a proximity sensor 766. These sensors make it possible to detect the position, inclination, direction, and movement of the portable information terminal 700, as well as the ambient brightness and the proximity of surrounding objects. The portable information terminal 700 may further include other sensors such as a barometric pressure sensor.

[0182] The portable information terminal 700 may be a mobile phone, a smartphone, a tablet terminal, etc. It may also be a PDA (Personal Digital Assistant) or a notebook PC. It may also be a digital still camera, a video camera capable of shooting video, a portable game console, a navigation device, or other portable digital devices.

[0183] 10A includes many components that are not essential to this embodiment, such as sensor unit 760, but the effects of this embodiment are not impaired even if these components are not provided. Furthermore, components not shown, such as a digital broadcast receiving function and an electronic money payment function, may be further added.

[0184] [Software configuration of mobile information terminal] 10B is a software configuration diagram of the mobile information terminal 700 of this embodiment, and shows the software configuration in the ROM 703, RAM 704, and storage unit 710. In this embodiment, a basic operation program 7001 and other operation programs are stored in the ROM 703, and a cooperative control program 7002 and other operation programs are stored in the storage unit 710. The storage unit 710 is also assumed to include a content storage area 7200 that stores content such as moving images, still images, and audio, an authentication information storage area 7300 that stores authentication information and the like required when accessing a television receiver or each server device, and various information storage areas that store various other information.

[0185] A basic operation program 7001 stored in ROM 703 is loaded into RAM 704, and the main control unit 701 executes the loaded basic operation program to form a basic operation execution unit 7101. Similarly, a cooperative control program 7002 stored in storage unit 710 is loaded into RAM 704, and the main control unit 701 executes the loaded cooperative control program to form a cooperative control execution unit 7102. The RAM 704 also includes a temporary storage area for temporarily storing data created when each operation program is executed, as needed.

[0186] For ease of explanation, the process of controlling each operation block by the main control unit 701 loading the basic operation program 7001 stored in the ROM 703 into the RAM 704 and executing it will be described below as if the basic operation execution unit 7101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0187] The cooperative control execution unit 7102 manages device authentication and connection, transmission and reception of data, etc. when the mobile information terminal 700 performs cooperative operation with the television receiver. The cooperative control execution unit 7102 also has a browser engine function for executing applications that work in conjunction with the television receiver.

[0188] The operation programs may be stored in the ROM 703 and / or the storage unit 710 before the product is shipped. After the product is shipped, the operation programs may be acquired from another application server 500 or the like on the Internet 200 via the LAN communication unit 721 or the mobile telephone network communication unit 722. Alternatively, the operation programs may be stored in a memory card, an optical disk, or the like and acquired via the extended interface unit 724 or the like.

[0189] [Time management for broadcast receiving devices] The broadcast receiving device of this embodiment has two types of time management functions. The first time management function is a time management function based on NTP, as already explained using Figure 7C. The second time management function is a time management function based on MH-TOT, and time is managed based on the time information transmitted by MH-TOT, as explained in Figure 6B.

[0190] FIG. 13A shows an example of the structure of time information transmitted by NTP. FIG. 13B shows an example of the data structure of the MPU timestamp descriptor. The "reference_timestamp" parameter and "transmit_timestamp" parameter in the NTP format are 64-bit time data in the NTP long format, and the "mpu_presentation_time" parameter in the MPU timestamp descriptor is also 64-bit time data in the NTP timestamp format. The NTP long format time data and the NTP timestamp format time data are data in which "seconds or more" in UTC are represented by 32 bits and "less than a second" by 32 bits. In other words, NTP format time information can transmit time information down to "less than a second." Furthermore, because the NTP format time information is expressed in UTC, it can be consistent with the NTP included in signals received over a communication line path (e.g., a communication line that can be received by the LAN communication unit 121 in FIG. 7A) as shown in FIG. 3B, unlike clock management in conventional digital broadcasting.

[0191] In contrast, the information transmitted by the MH-TOT is as follows: The broadcast receiving device 100 is assumed to be able to obtain the current date and Japan Standard Time from the MH-TOT. FIG. 11A shows an example of the data structure of the MH-TOT. The broadcast receiving device 100 is able to obtain the current date and current time from the "JST_time" parameter of the MH-TOT. As shown in FIG. 11B, the "JST_time" parameter includes the lower 16 bits of the coded data of the current date in Modified Julian Date (MJD) and 24 bits of information representing Japan Standard Time (JST) as six 4-bit binary-coded decimal (BCD) numbers. The current date can be calculated by performing a predetermined calculation on the 16-bit coded data of the MJD. The six 4-bit binary coded decimal numbers are: two 4-bit binary coded decimal numbers represent the hour in two decimal digits, the next two 4-bit binary coded decimal numbers represent the minute in two decimal digits, and the last two 4-bit binary coded decimal numbers represent the second in two decimal digits.

[0192] Therefore, the difference between time based on NTP and time based on MH-TOT is that the former, NTP, transmits time information in UTC notation, which can transmit time information down to the "second," as mentioned above, while the information transmitted by MH-TOT is information up to the "second" in JST notation.

[0193] The broadcast receiving device 100 of this embodiment can achieve more accurate synchronization by using a time management function based on NTP, which is time information in UTC, to synchronize the decoding and display of the video, audio, subtitles, superimposed text, and other presentation data that are the content of the broadcast signal. Furthermore, by referring to information in UTC rather than the clock notation of the broadcast station, it is also possible to synchronize the decoding and display of the video, audio, subtitles, superimposed text, or other data that are the content of the broadcast signal received by the broadcast signal with the video, audio, subtitles, superimposed text, or other data acquired via a communication line path.

[0194] Furthermore, the broadcast receiving device of this embodiment may use a time management function based on "JST_time," which includes 24-bit information expressed as six 4-bit binary-coded decimal numbers in the MH-TOT, for the process of presenting the current time to a user or for each process that handles the MH-Event Information Table (MH-EIT) described in FIG. 6B. Generally, the process of presenting the current time to a user in a broadcast receiving device rarely requires accuracy down to the second. Furthermore, each piece of time information described in the MH-Event Information Table (MH-EIT) is stored as 24-bit information expressed as six 4-bit binary-coded decimal numbers, each with two decimal digits for "hour," "minute," and "second," similar to the EIT of conventional digital broadcasts transmitted using the MPEG2-TS format. Therefore, the time management function based on the MH-TOT in the broadcast receiving device 100 of this embodiment is easily compatible with processes that use the MH-EIT. Specifically, processes that use the MH-EIT include the program guide generation process (described below), control of recording and viewing reservations, and copyright management processes such as temporary storage. This is because precision of less than a second is rarely required for any of the processes, and precision of one second is sufficient.

[0195] Furthermore, the generation of the program guide, control of recording reservations and viewing reservations, copyright management processes such as temporary storage, etc. are functions that are also installed in receivers of digital broadcasting systems using the conventional MPEG2-TS format. Therefore, if the broadcasting system of this embodiment is configured so that the generation of the program guide, control of recording reservations and viewing reservations, copyright management processes such as temporary storage, etc. can be handled using time management processes that are consistent with those of conventional MPEG2-TS digital broadcasting systems, when configuring a broadcast receiving device that has both the reception function for conventional MPEG2-TS digital broadcasting and the reception function for MMT digital broadcasting, it will no longer be necessary to design separate processing algorithms for these processes (generation of the program guide, control of recording reservations and viewing reservations, copyright management processes such as temporary storage, etc.), thereby reducing costs.

[0196] Furthermore, even in the case of a receiver that does not have the ability to receive digital broadcasts using the conventional MPEG2-TS format and only has the ability to receive digital broadcasts using the MMT format, it is possible to develop it at a lower cost because it is possible to reuse the algorithms for functions that are also installed in receivers for digital broadcasting systems using the conventional MPEG2-TS format, without having to create completely new algorithms for processes such as generating program guides, controlling recording and viewing reservations, and copyright management processes such as temporary storage.

[0197] Therefore, by configuring the time management function based on the MH-TOT "JST_time" parameter to be used for these processes (such as generating program guides, controlling recording and viewing reservations, and copyright management processes such as temporary storage), it will be possible to provide even MMT-based digital broadcasting receiving devices at a lower cost by increasing compatibility with conventional broadcasting systems.

[0198] As described above, the broadcast receiving device 100 of this embodiment has a time management function that uses two types of time information with different accuracy. One type of time information is time information written in a format that is consistent with conventional digital broadcasting systems, and the other type of time information is time information with higher resolution than the first type of time information. By using the latter type of time information for synchronizing each piece of content data in the broadcast signal, more advanced information presentation processing than conventional broadcasting systems is realized, and by using the former type of time information for generating a program guide, controlling recording and viewing reservations, and copyright management processing such as temporary storage, it is possible to provide a broadcast receiving device at low cost.

[0199] Therefore, by providing the two types of time management functions described above, the broadcast receiving device 100 of this embodiment can achieve both more advanced information presentation processing and lower costs.

[0200] [First variation of time management] Next, a first modification of the time management in the broadcasting system of this embodiment will be described below.

[0201] In a first variant, in order to improve the accuracy of the management time of the NTP-based time management function already explained using Figure 7C, information regarding the expected delay time in transmitting time information from a time management server (not shown) or broadcast station server 300 to the broadcast receiving device 100 may be included in the broadcast signal and transmitted, and the broadcast receiving device 100 may be configured to use the information regarding the expected delay time to correct the system clock of the NTP-based time management function.

[0202] In this case, information regarding the expected delay time may be transmitted within a TMCC (Transmission and Multiplexing Configuration Control) area outside the TLV multiplexed stream, rather than within the TLV multiplexed stream shown in FIG. 3(A). Transmission within the TMCC area allows the broadcast receiving device 100 to extract information regarding the expected delay time without undergoing demultiplexing (demuxing) of the TLV multiplexed stream. This allows the broadcast receiving device 100 to acquire information that is less susceptible to delays due to the demultiplexing process, thereby enabling highly accurate system clock adjustment. An example of the data structure of the time information transmitted in the TMCC signal is described with reference to FIG. 13C. The time information may be stored and transmitted, for example, in a TMCC extended information area. In the time information in the TMCC extended information area of ​​FIG. 13C, the “delta” parameter represents the expected transmission delay from a time management server that distributes UTC or a server device that creates a TMCC signal to a general broadcast receiving device, expressed as a 32-bit signed fixed-point number. The upper 16 bits describe the integer part, and the lower 16 bits describe the decimal point. The "transmit_timestamp" parameter is a transmission timestamp, and describes the time when this TMCC signal is sent from the server device in NTP timestamp length format. The upper 32 bits describe the integer part, and the lower 32 bits describe the decimal point.

[0203] In the first variant, the broadcast receiving device 100 of this embodiment can correct the system clock of the NTP-based time management function used for synchronizing each content data of the broadcast signal with higher accuracy by using information regarding the expected delay time described in the time information stored in the TMCC extended information area and transmitted (for example, the aforementioned ``delta'' parameter and / or ``transmit_timestamp'' parameter).

[0204] [Second variation of time management] Next, a second modification of the time management in the broadcasting system of this embodiment will be described below.

[0205] As described above, the broadcast receiving device 100 of this embodiment has a time management function that acquires the current date and Japan Standard Time from information transmitted in the MH-TOT and manages the time. The current date and Japan Standard Time acquired from the information transmitted in the MH-TOT can be superimposed on video information, application information, etc. by the video synthesis unit 161 of the broadcast receiving device 100, and output to the monitor unit 162 or video output unit 163 for provision to the user. As described above, the MH-TOT has the data structure shown in Fig. 11A, and the broadcast receiving device 100 can acquire the current date and current time from the "JST_time" parameter of the MH-TOT.

[0206] However, because the aforementioned "JST_time" parameter uses only the lowest 16 bits of the MJD encoded data, an overflow occurs at "April 22, 2038," and dates after "April 23, 2038" cannot be expressed using only the specified calculation. Therefore, in the second modified example of this embodiment, the calculation method is switched depending on whether the MJD value is equal to or greater than a specified value or less than the specified value, so that dates after "April 23, 2038" can be expressed.

[0207] FIG. 12 shows an example of a first calculation method used when the MJD value is equal to or greater than a predetermined value, and a second calculation method used when the MJD value is less than the predetermined value. For example, if the predetermined value is "32768 (0x8000)," the current date is calculated using the first calculation method when the MJD is equal to or greater than "32768," and the current date is calculated using the second calculation method when the MJD is less than "32768." Note that an MJD less than "32768" is equivalent to the most significant bit of the 16-bit MJD data being "0." This allows the broadcast receiving device 100 of this embodiment to represent dates after "April 23, 2038." However, the predetermined value can be set arbitrarily, such as "16384 (0x4000)" or "49152 (0xC000)." The condition for switching the calculation method may be when the most significant two bits of the 16-bit data of the MJD are "00" or when the most significant two bits of the 16-bit data of the MJD are not "11." Note that if the above-mentioned means is used with the predetermined value set to "32768," it will not be possible to represent dates prior to "September 4, 1948," but this will not pose any particular problem in practical use as a television receiver.

[0208] Alternatively, instead of switching between the first and second calculation methods based on the comparison result between the MJD and the predetermined value, the first and second calculation methods may be switched based on a flag that replaces part or all of the "reserved" parameter in the MH-TOT data structure shown in FIG. 11A or a newly added flag. For example, if the most significant bit of the 16-bit encoded data of the MJD is "0," the flag may be set to "1" if the MJD indicates "April 23, 2038" or later, or set to "0" if the MJD does not indicate "April 23, 2038" or later. Then, if the flag is "1," the second calculation method shown in FIG. 12 may be used, and if the flag is "0," the first calculation method may be used. Alternatively, a new descriptor having the same meaning as the flag may be prepared and placed in the MH-TOT.

[0209] Furthermore, in the broadcasting system of this embodiment, as described above, absolute time in NTP format is transmitted, and the broadcast receiving device 100 of this embodiment has a time management function based on the NTP. Furthermore, the broadcast receiving device 100 of this embodiment controls the decoding timing and presentation timing for each presentation unit of video / audio signals by referring to the NTP timestamp etc. described in the MPU timestamp descriptor set for each MPU. As described above, the time information in the NTP format has the structure shown in Figure 13A. Furthermore, the MPU timestamp descriptor has the structure shown in Figure 13B.

[0210] For this reason, the broadcast receiving device 100 of this embodiment may refer to the "reference_timestamp" parameter, the "transmit_timestamp" parameter, or the "mpu_presentation_time" parameter, etc., and select whether to use the first calculation method or the second calculation method depending on the value of the referenced time data, etc. That is, for example, if the most significant bit of the 64-bit NTP-length format time data is "0", the second calculation method may be used, and if it is not "0", the first calculation method may be used.

[0211] Either of the above methods makes it possible for the broadcast receiving device 100 of this embodiment to express dates after "April 23, 2038."

[0212] [Broadcast receiver channel selection process (initial scan)] The AMT of the broadcasting system of this embodiment provides a list of multicast groups for IP packets so that IP packets transmitted using the TLV multiplexing method can be received without distinction from IP packets transmitted over a communication line. Multiple IP multicast groups can be listed for one service identifier. Address masks can also be used to efficiently describe consecutive IP addresses.

[0213] In the broadcast receiving device 100 of this embodiment, when a channel scan is performed during initial setup or when a rescan is performed to change the settings, it is possible to store a list of services acquired from the TLV-NIT in a nonvolatile memory such as the ROM 103 or the storage unit 110, and further, it is possible to associate a list of IP multicast groups corresponding to each of the services with each of the services as IP-related information and store it in the nonvolatile memory. By storing the list of services and the IP-related information in a nonvolatile memory and making them available for constant reference, it is no longer necessary to reacquire the TLV-NIT or AMT when switching channels, etc., and it is possible to efficiently acquire broadcast content.

[0214] FIG. 14 is a diagram showing an example of an operation sequence during channel scanning (rescanning) in the broadcast receiving device 100 of this embodiment.

[0215] When a channel scan is started, the receiving function execution unit 1102 sets an initial frequency value to the tuner / demodulator unit 131 and instructs the tuner / demodulator unit 131 to tune to the initial frequency value (S101). If the tuner / demodulator unit 131 successfully locks onto the set frequency value (S102: Yes), the receiving function execution unit 1102 then acquires the TLV-NIT from the received signal (S103).

[0216] If the TLV-NIT acquired in the process of S103 is valid data (S104: Yes), the receiving function execution unit 1102 acquires information such as the TLV stream ID and original network ID from the acquired TLV-NIT (S105). FIG. 15A shows an example of the data structure of a TLV-NIT. The TLV stream ID information can be acquired from the "tlv_stream_id" parameter, and the original network ID information can be acquired from the "original_network_id" parameter. Furthermore, distribution system information related to the physical conditions of the broadcast transmission path corresponding to each TLV stream ID / original network ID is acquired from the distribution system descriptor (S106), and a list of service IDs is acquired from the service list descriptor (S107). FIG. 15B shows an example of the data structure of a satellite distribution system descriptor. FIG. 15C shows an example of the data structure of a service list descriptor. If the TLV-NIT has a plurality of different data such as the TLV stream ID, the original network ID, the distribution system information, the list of service IDs, etc., the processes of S105 to S107 are repeated. Next, the receiving function execution unit 1102 creates a service list based on the data such as the TLV stream ID, the original network ID, the distribution system information, the list of service IDs, etc. acquired in the processes of S105 to S107, and stores the created service list in the ROM 103 or the storage unit 110 (updates when rescanning) (S108).

[0217] Next, the reception function execution unit 1102 acquires an AMT from the received signal (S109), and further acquires a list of IP multicast groups related to each service ID stored in the service list (S110). An example of the data structure of an AMT is shown in FIG. 15D. If the AMT has lists of IP multicast groups related to multiple service IDs, the process of S110 is repeated. If there are multiple AMTs each having a list of IP multicast groups related to different service IDs, the processes of S109 to S110 are repeated. Next, the reception function execution unit 1102 associates the list of IP multicast groups acquired in the process of S110 with the service ID as IP-related information, and stores it in the ROM 103, the storage unit 110, etc. (updates it when rescanning) (S111).

[0218] In addition, if the tuner / demodulator unit 131 does not succeed in locking onto the set frequency value in the process of S102 (S102: No), and if the TLV-NIT acquired in the process of S103 is not valid data (S104: No), the processes of S105 to S111 are not performed.

[0219] After completing the process of S111, if the frequency value set in the tuner / demodulator unit 131 is the final frequency value of the channel scan range (S112: Yes), the receiving function execution unit 1102 ends the process. On the other hand, if the set frequency value is not the final frequency value of the channel scan range (S112: No), the frequency value set in the tuner / demodulator unit 131 is increased (S113), and the processes of S102 to S111 are repeated. Note that if service IDs related to all services constituting the broadcast network can be acquired with one TLV-NIT, and if an AMT having a list of IP multicast groups related to the service IDs can be acquired, the processes of S112 to S113 are not necessary.

[0220] Through the above-described series of processes, the broadcast receiving device 100 of this embodiment creates / updates a list of services (service list) that make up the broadcast network when scanning channels during initial setup or when rescanning to change settings, and at the same time creates / updates a list of IP multicast groups (IP-related information) corresponding to each of the services, and further stores this information in non-volatile memory such as ROM 103 or storage unit 110.

[0221] The rescan for the setting change may be performed automatically when a change in the information in the table is detected by referring to the "version_number" parameter of the TLV-NIT or AMT. When a change in the "version_number" parameter of either the TLV-NIT or the AMT is detected, only the information about the table in which the change in the parameter was detected may be automatically updated. However, when the automatic update is performed, it is desirable to notify the user that a rescan has been performed automatically. Alternatively, the user may be notified that a change has been made to the information in the table, and the user may be allowed to select whether or not to perform the rescan.

[0222] [Broadcast receiving device tuning process (channel switching)] FIG. 16 is a diagram showing an example of an operation sequence when selecting a station (switching channels) in the broadcast receiving device 100 of this embodiment.

[0223] When a user operates a remote control or the like (not shown) to instruct channel switching, the receiving function execution unit 1102 interprets the command transmitted from the remote control and specifies the service ID of the desired service (S201). Next, the receiving function execution unit 1102 starts acquiring an AMT from the signal received by the tuner / demodulator unit 131. If the AMT is successfully acquired within a predetermined time (S202: Yes), information regarding a list of IP multicast groups corresponding to the service ID is acquired from the acquired AMT (S204). On the other hand, if the AMT is not successfully acquired within the predetermined time (S202: No), the unit 1102 refers to IP-related information stored in the ROM 103 or the storage unit 110 (S203) to acquire information regarding a list of IP multicast groups corresponding to the service ID (S204). Note that the determination process of S202 may not be performed, and the IP-related information stored in the ROM 103 or the storage unit 110 may always be referenced.

[0224] Next, the reception function execution unit 1102 starts acquiring a TLV-NIT from the signal received by the tuner / demodulator unit 131. If the TLV-NIT is successfully acquired within a predetermined time (S205: Yes), distribution system information for acquiring an IP data flow corresponding to the service ID is acquired from the acquired TLV-NIT (S207). On the other hand, if the TLV-NIT is not successfully acquired within the predetermined time (S205: No), the service list stored in the ROM 103, the storage unit 110, etc. is referenced (S206) to acquire distribution system information for acquiring an IP data flow corresponding to the service ID (S207). Note that the service list stored in the ROM 103, the storage unit 110, etc. may always be referenced without performing the determination process of S205. After acquiring the distribution system information in the processing of S207, the receiving function execution unit 1102 then controls the tuner / demodulation unit 131 with the frequency value indicated in the acquired distribution system information, receives the IP data flow corresponding to the service ID (S208), extracts the MMT data string from the received IP data flow, and outputs it to the separation unit 132.

[0225] In the demultiplexer 132, the transport processor 1102a acquires an MMTP packet whose packet ID is "0" from the input MMT data sequence (S209), and further acquires the MPT contained in the acquired MMTP packet (S210). Next, the transport processor 1102a references the "MMT_package_id_byte" parameter in the acquired MPT and checks whether the lowest 16 bits of the "MMT_package_id_byte" parameter have the same value as the service ID. In the example of the MPT data structure shown in FIG. 17, if the lowest 16 bits of the "MMT_package_id_byte" parameter have the same value as the service ID (S211: Yes), it determines that the MMTP packet whose packet ID is "0" is an MMTP packet containing data of a program corresponding to the service ID, and acquires an MFU based on the information in the acquired MPT (S216).

[0226] On the other hand, if the lowest 16 bits of the "MMT_package_id_byte" parameter are not the same value as the service ID (S211: No), the transport processing unit 1102a determines that the MMTP packet with the packet ID of "0" is not an MMTP packet containing program data corresponding to the service ID. In this case, the transport processing unit 1102a acquires a PLT again (S212) and checks the acquired PLT to confirm the packet ID (assumed to be x) of the MMTP packet transmitting the MPT containing the "MMT_package_id_byte" parameter corresponding to the service ID (S213). Furthermore, the transport processing unit 1102a acquires an MMTP packet with the packet ID of "x" from the input MMT data string (S214) and acquires the MPT contained in the acquired MMTP packet (S215). Furthermore, the transport processing unit 1102a acquires an MFU based on the information contained in the acquired MPT (S216).

[0227] It is also possible to always perform the processes of S212 to S215 without performing the processes of S209 to S211. In this case, it is possible to shorten the processing time when the data of the program corresponding to the service ID is stored in an MMTP packet with a packet ID other than "0".

[0228] When the MFU is acquired in the processing of S216, the transport processing unit 1102a extracts encoded video data, encoded audio data, etc. from the acquired MFU and outputs them to the video decoder 141, audio decoder 143, etc. Next, video / audio decoding processing is performed under the control of the AV decoding processing unit 1102b, and presentation processing is performed under the control of the presentation processing unit 1102h, but since each of these processes is publicly known, detailed explanations will be omitted.

[0229] By the above series of processes, the broadcast receiving device 100 of this embodiment can perform a channel selection (channel switching) operation. In particular, as described with reference to Figures 14 and 16, when a channel scan is performed during initial setup or when a rescan is performed to change settings, a service list and IP-related information are created and stored in a nonvolatile memory such as the ROM 103 or the storage unit 110 so that they can be referenced at any time. When selecting a channel (switching a channel), the service list and IP-related information stored in the nonvolatile memory such as the ROM 103 or the storage unit 110 are referenced, thereby improving the efficiency of the operation when selecting a channel (switching a channel). In other words, compared to when AMT or TLV-NIT is reacquired when selecting a channel (switching a channel), it is possible to shorten the time from the start of channel selection (switching a channel) to the end of channel selection (switching a channel).

[0230] [Screen layout control for broadcast receiving devices] It is assumed that the broadcast receiving device 100 of this embodiment is capable of controlling the screen layout based on the description of the LCT. An example of the data structure of the LCT is shown in FIG.

[0231] In the diagram, the "left_top_pos_x" and "right_down_pos_x" parameters indicate the horizontal positions of the top left and bottom right of the region, respectively, as a percentage of the total number of horizontal pixels, with the left side of the full-screen display being "0" and the right side being "100." The "left_top_pos_y" and "right_down_pos_y" parameters indicate the vertical positions of the top left and bottom right of the region, respectively, as a percentage of the total number of vertical pixels, with the top side of the full-screen display being "0" and the bottom side being "100." The "layer_order" parameter indicates the relative position of the region in the depth direction.

[0232] An example of allocation of layouts to layout numbers based on the settings of each of the parameters is shown in FIGS. 19A to 19D, along with the setting values ​​of each of the parameters.

[0233] FIG. 19A shows a default layout setting for the broadcast receiving device 100 of this embodiment, in which only one area is set across the entire screen. FIG. 19B shows an example in which the entire screen is divided into three areas, designated "Area 0," "Area 1," and "Area 2." For example, if the number of pixels across the entire screen is 7,680 horizontally and 4,320 vertically, "Area 0" is set to the range (0,0)-(6143,3455) because the "left_top_pos_x" parameter is "0," the "left_top_pos_y" parameter is "0," the "right_down_pos_x" parameter is "80," and the "right_down_pos_y" parameter is "80." Similarly, "Area 1" is set to the range (6144,0)-(7679,4319), and "Area 2" is set to the range (0,3456)-(6143,4319).

[0234] Fig. 19C shows an example of setting three regions, similar to Fig. 19B, but "region 0" is set in the range of (0,0)-(7679,4319), and "region 1" and "region 2" are placed in front of "region 0" in the same range as described above, depending on the setting of the "layer_order" parameter. Fig. 19D shows an example of a case where "region 0" is set in device 0 (default device: broadcast receiving device 100 in this embodiment), and "region 1" is set in device 1 (mobile information terminal 700 in this embodiment).

[0235] As described above, in the broadcasting system of this embodiment, by using the LCT, it becomes possible to control the screen layout so that multimedia services are displayed on the receiver as intended by the service provider.

[0236] Note that fractions after the decimal point that result when dividing the screen according to the setting values ​​of parameters such as "left_top_pos_x" can be rounded up or down. Rounding (or rounding to the nearest integer in binary) is also acceptable. For example, if the total number of pixels on the screen is 7680 pixels x 4320 pixels vertically, and the "left_top_pos_x" parameter of "Area 0" is "0," the "left_top_pos_y" parameter is "0," the "right_down_pos_x" parameter is "51," and the "right_down_pos_y" parameter is "51," "Area 0" can be set to the range (0,0)-(3916,2203) by rounding up, or to the range (0,0)-(3915,2202) by rounding down. Furthermore, taking into account macroblocks during video compression processing, rounding up or down in 8-pixel or 16-pixel units can be used. This process makes it possible to efficiently set regions based on the LCT and to efficiently convert the resolution of multimedia content in the regions.

[0237] [Exception handling for screen layout control on broadcast receiving devices] In the broadcast receiving device 100 of this embodiment, even if the screen layout area control is performed by the above-mentioned LCT, if the user instructs to display an EPG screen, etc., it is possible to perform screen layout control that ignores the contents of the LCT as an exceptional process. Figure 20A shows an example of the operation of exceptional process of screen layout control based on the LCT.

[0238] 19B is performed by the description in the LCT, and when a broadcast program video is displayed in "Area 0" and broadcast content such as program linked data linked to the broadcast program is displayed in "Area 1" and "Area 2," if the user instructs the display of an EPG screen using a remote control (not shown), the broadcast receiving device 100 of this embodiment will return the screen layout setting to the default setting (i.e., a state in which the same screen layout control as in FIG. 19A is being performed) regardless of the description content of the LCT, as shown in Fig. 20A(A), and control will be performed so that the EPG screen is displayed on the entire screen. Furthermore, if the user instructs the display of the EPG screen to end, the screen layout control will be re-executed in accordance with the description content of the LCT.

[0239] By performing the above-described control, the EPG screen can be displayed larger and easier to view than when the EPG screen is displayed while maintaining area control of the screen layout, as shown in Figure 20A (B).

[0240] It should be noted that the exception processing of the screen layout control is not only applied when displaying the EPG screen, but may also be applied when displaying a sub-screen or dual-screen of various setting screens (recording setting screen in the illustrated example) of the broadcast receiving device 100, as shown in FIG. 20B.

[0241] In the case of the recording setting screen shown in FIG. 1A, the display area of ​​the broadcast content changes from the entire screen to only the sub-screen portion at the bottom right of the screen. Similarly, in the case of the dual-screen display shown in FIG. 1B, the display area of ​​the broadcast content changes from the entire screen to only the split-screen portion at the left middle of the screen. In either case, the display area for displaying the broadcast content is narrower than when the entire screen is used, so maintaining the area control of the screen layout within the display area (i.e., dividing the area and displaying multiple broadcast contents simultaneously) is not desirable from a visual standpoint. Therefore, in the broadcast receiving device 100 of this embodiment, in the above-mentioned situation, only the broadcast content in "Area 0" is selected and displayed in the display area. Note that it is also possible to select and display broadcast content in "Area 1" or "Area 2" depending on the immediately preceding area selection status.

[0242] By performing the above-described control, it is possible to improve the ease of viewing the broadcast content compared to when various broadcast content is displayed while maintaining the area control of the screen layout. The same is true when displaying a sub-screen on the recorded program list screen, displaying internet content in a browser, etc.

[0243] [EPG display on broadcast receiver] In the broadcasting system of this embodiment, time-series information about events (so-called programs) included in each service constituting the broadcasting network is transmitted using an MH-EIT. Figure 21 shows an example of the data structure of the MH-EIT of this embodiment. The MH-EIT is identified into two classes by a table ID (corresponding to the "table_id" parameter in the figure), and is capable of indicating information about the current / next event of its own TLV stream and schedule information for each event of its own TLV stream. The broadcast receiving device 100 of this embodiment refers to the MH-EIT and performs identification by service ID (corresponding to the "service_id" parameter in the figure), thereby acquiring information such as the start time and broadcast time of each event and creating an EPG screen. The video synthesis unit 161 is capable of superimposing the created EPG on video information and the like and displaying it on the monitor unit 162.

[0244] 22A is a diagram showing an example of an EPG screen in the broadcast receiving device 100 of this embodiment. The EPG screen 162a is in a matrix format with the vertical axis representing time and the horizontal axis representing service ID (channel), and displays detailed information about broadcast programs broadcast on each channel in each time slot. The detailed information 162a1 about each broadcast program is mainly composed of a title area 162a2 and a detailed description area 162a3.

[0245] The title area 162a2 displays the program title of the broadcast program and symbols or the like representing the attributes of the broadcast program. The symbols or the like representing the attributes of the broadcast program include, for example, symbols / characters indicating that the program is a new program or a rebroadcast program. Alternatively, the symbols or the like may be a symbolized symbol of "data," indicating that the program is compatible with data broadcasting by a broadcast service. Furthermore, the symbols or the like may be a symbolized symbol of "NetWork," such as the symbol 162a4, indicating that content, applications, or the like related to the broadcast program can be obtained from a network. The symbols or the like representing the attributes of the broadcast program may be substituted by using a different background color for the detailed information 162a1 or by surrounding the display area of ​​the detailed information 162a1 with a bold frame.

[0246] Furthermore, even if the control information (messages, tables, descriptors, etc.) in the broadcasting system of this embodiment indicates that content, applications, etc. related to the broadcast program can be obtained from the network, if the LAN cable is not connected to the LAN communication unit 121 of the broadcast receiving device 100, or if access to each server device on the network is not possible, the mark 162a4 symbolizing ``NetWork'' etc. may be controlled not to be displayed.

[0247] Furthermore, if the broadcast program is a distributed program distributed via the Internet 200 and cannot be acquired solely from broadcast waves, and further, as described above, if the broadcast receiving device 100 is unable to access each server device on the network, the detailed information 162b1 displayed on the EPG screen 162b may be grayed out, as shown in FIG. 22B . That is, the detailed information of the unavailable distributed program is not displayed. Alternatively, the graying out process may be performed by differentiating the background color of the detailed information 162b1 from the others. When the detailed information 162b1 is selected by operating a remote control (not shown), a pop-up or other notification may be displayed to the user to inform them that the broadcast receiving device 100 is unable to access each server device on the network or that the distributed program associated with the detailed information 162b1 is unavailable for viewing.

[0248] Through the above-described controls, the broadcast receiving device 100 can provide the program information of each broadcast program in a format that is more natural to the user, depending on the network connection status.

[0249] 22C is a diagram showing another example of an EPG screen in the broadcast receiving device 100 of this embodiment. In the figure, "M1 TV," "M2 Broadcast," "M3 Channel," "M4 TV," "TV M5," etc. are the names of the broadcast stations of each channel, and in particular, the "M2 Broadcast" station simultaneously provides broadcast programs distributed by airwaves and distributed programs distributed via the Internet 200 (slot information 162c1 indicated by "Internet Broadcast" in the figure).

[0250] As shown in the figure, when there is a channel that only has programs distributed via the Internet 200, control is normally performed to display information for all channels (including information 162c1), as shown in EPG screen 162c in figure (A). On the other hand, when the broadcast receiving device 100 is in a state where it cannot access each server device on the network, control may be performed so that information for the "M2 Broadcast (Internet Broadcast)" channel (information 162c1 in figure (A)) that only has programs distributed via the Internet 200 is not displayed, as shown in EPG screen 162d in figure (B).

[0251] By performing the above-described controls, the user of the broadcast receiving device 100 can eliminate the need to check information about channels that the user cannot view.

[0252] [Emergency warning broadcast display on broadcast receiver] The broadcast receiving device 100 of this embodiment is capable of receiving emergency alert broadcasts when the emergency alert broadcast start control signal bit of the TMCC signal contained in the transmission data including the TLV stream changes from "0" to "1."

[0253] The emergency alert broadcast may be provided as a full-screen application or as text information with superimposed text. When the emergency alert broadcast is provided as text information with superimposed text, it is preferable to display the text information of the superimposed text regardless of the state of the broadcast receiving device 100 immediately before receiving the emergency alert broadcast. That is, as shown in FIG. 23 , if a user is watching a regular broadcast program and a program screen 162e of the broadcast program is displayed on the monitor unit 162 when an emergency alert broadcast is received, text information 162e1 from the emergency alert broadcast is superimposed on the program screen 162e. Similarly, if a user instructs the display of an EPG screen and an EPG screen 162f is displayed on the monitor unit 162 when an emergency alert broadcast is received, control is performed to display text information 162f1 from the emergency alert broadcast superimposed on the EPG screen 162f.

[0254] By the above-described control, in the broadcast receiving device 100 of this embodiment, when an emergency alert broadcast is received, it is possible to avoid missing important text information based on the emergency alert broadcast, even if the user has selected and displayed an EPG screen, various setting screens, a recorded program list screen, an Internet browser, etc. This control may also be performed on text information in ordinary superimposed text that is not based on emergency alert broadcasts.

[0255] [Various exception handling] If the broadcast receiving device 100 of this embodiment cannot acquire data outside the TLV stream in the same package, it may perform, for example, the following exception processing.

[0256] As described in FIG. 6E, in the broadcast system supported by the broadcast receiving device 100 of this embodiment, data acquired within a TLV stream and data acquired via a path other than the TLV stream can be included in the same package based on the location information stored in the MPT (corresponding to "MMT_general_location_info()" in FIG. 17). However, data transmission paths other than the TLV stream indicated by the location information (e.g., IPv4 data flow, IPv6 data flow, broadcast MPEG2-TS, etc.) are reception functions separate from the TLV / MMT stream reception function. Therefore, even when the broadcast receiving device 100 is operating, there may be situations in which data cannot be acquired from these transmission paths, such as when the reception functions of these transmission paths are not operating, when the reception functions themselves are operating but relay devices or the like are not operating, when these transmission paths are not connected via wired or wireless connection, or when the broadcast receiving device 100 is installed in an environment where these transmission paths cannot be connected in the first place.

[0257] Under such circumstances, when an event is received in which the location information stored in the MPT indicates that data acquired within the TLV stream and data acquired via a route other than the TLV stream are to be associated so as to be included in the same package, the broadcast receiving device 100 of this embodiment may, for example, perform the following operations.

[0258] For example, in a case where the LCT defines multiple regions within the screen as shown in Figures 19B and 19C, and the video contained in the TLV stream is displayed in "Area 0," and data acquired via a transmission path other than the TLV stream is displayed in "Area 1" and "Area 2," and data from a transmission path other than the TLV stream that should be displayed in "Area 1" or "Area 2" cannot be acquired, the layout display of the multiple regions specified by the LCT may be prohibited. Specifically, even when the LCT is received, the video of the content received in the TLV stream may remain displayed in "Area 0" of the default layout display shown in Figure 19A, and a transition to a layout display of the multiple regions as shown in Figures 19B and 19C may be prevented. Furthermore, even if an instruction to change from the default layout to the layout indicated by the LCT is input to the operation input unit 170 of Figure 7A in this state, the default layout display shown in Figure 19A may remain or may be switched to another data broadcasting screen, preventing a transition to a layout display of the multiple regions as shown in Figures 19B and 19C.

[0259] In a case where the LCT sets multiple regions on the screen as shown in Figures 19B and 19C, and the video contained in the TLV stream is displayed in "Area 0," and data acquired via a transmission path other than the TLV stream is displayed in "Area 1" and "Area 2," and data from a transmission path other than the TLV stream to be displayed in "Area 1" or "Area 2" cannot be acquired, another example of operation when the display frames of the multiple regions shown in Figures 19B and 19C indicated by the LCT are temporarily displayed, and a background color or a predetermined still image is displayed in "Area 1" or "Area 2." If data from a transmission path other than the TLV stream indicated by the MPT location information cannot be acquired after a predetermined time has elapsed, the display may be switched back to the default layout display state shown in Figure 19A. In this case, it is preferable to continue displaying the program video contained in the TLV stream in "Area 0" even when the layout of Figures 19A, 19B, and 19C is changed, because the user's program video itself will continue to be displayed.

[0260] Furthermore, when the video of the content received in the TLV stream is displayed in "Area 0" of the default layout display shown in Fig. 19A due to the inability to acquire data of a transmission path other than the TLV stream to be displayed in "Area 1" or "Area 2," the broadcast receiving device 100 of this embodiment may enter a state where data of a transmission path other than the TLV stream to be displayed in "Area 1" or "Area 2" can be acquired due to the start of operation of various communication functions and various reception functions, or changes in the communication environment or communication status of the various communication functions or the reception environment or reception status of the various reception functions. In this case, the broadcast receiving device 100 of this embodiment may immediately switch from the default layout display shown in Fig. 19A to a multi-area layout shown in Fig. 19B or 19C indicated by the LCT, and may switch to display the video of the content received in the TLV stream in "Area 0," and display data acquired from a transmission path other than the TLV stream in "Area 1" or "Area 2." Alternatively, the layout change may not be performed immediately, but may be performed after an instruction to change from the default layout to the layout indicated by the LCT is input from the operation input unit 170.

[0261] [Copyright protection function] In a digital broadcasting system compatible with the broadcast receiving device 100 of this embodiment, by transmitting copy control information included in the MPT, the copy control information may be configured to transmit information indicating the copy control status of the content referenced by the MPT, such as "unlimited copying permitted" (which may be divided into two types: "unlimited copying permitted with encryption required for storage and output" and "unlimited copying permitted with encryption not required for storage and output"), "one generation copying permitted," "a specified number of copies permitted" (for example, "10 copies permitted" if nine copies and one move are permitted), or "copy prohibited." In this case, the broadcast receiving device 100 of this embodiment may be configured to control the storage of the content in the storage (storage) unit 110, recording on a removable recording medium, output to an external device, copying to an external device, moving to an external device, and the like, in accordance with the copy control information. Note that the storage process may not only be performed on the storage (storage) unit 110 within the broadcast receiving device 100, but may also include recordings that have been protected by encryption or other means so that they can only be played on the broadcast receiving device 100. Specifically, the targets of the storage process include external recording devices and the like that are in a state where recording and playback can be performed only by the broadcast receiving device 100.

[0262] A specific example of processing based on the copy control information will be described below.

[0263] First, when the copy control information included in the MPT indicates "unlimited copying," the broadcast receiving device 100 of this embodiment may store in the storage unit 110, record on a removable recording medium, output to an external device, copy to an external device, and move to an external device without any restrictions. However, when there is a distinction between "unlimited copying and encryption processing required for storage and output" and "unlimited copying and no encryption processing required for storage and output," in the case of "unlimited copying and encryption processing required for storage and output," storage in the storage unit 110, recording on a removable recording medium, output to an external device, copy to an external device, and move to an external device may be performed an unlimited number of times, but encryption processing is required for all of them.

[0264] Furthermore, if the copy control information included in the MPT indicates "copyable for one generation only," the broadcast receiving device 100 of this embodiment allows the content to be encrypted and stored in the storage (accumulation) unit 110, but when outputting the stored content to an external device for viewing, the content is encrypted and output together with copy control information indicating "copy prohibited." However, so-called move processing to an external device (processing in which content is copied to an external device and the content in the storage (accumulation) unit 110 of the broadcast receiving device 100 is made unplayable by erasing the content, etc.) is allowed.

[0265] Furthermore, if the copy control information included in the MPT indicates "copyable a predetermined number of times," the broadcast receiving device 100 of this embodiment can encrypt and store the content in the storage unit 110. However, when outputting the stored content to an external device for viewing, the content is encrypted and output together with copy control information indicating "copy prohibited." However, a predetermined number of copies and moves to an external device may be permitted. In the case of the so-called "Dubbing 10" standard, nine copies and one move to an external device may be permitted.

[0266] Furthermore, if the copy control information included in the MPT indicates "copy prohibited," the broadcast receiving device 100 of this embodiment prohibits copying to the storage (accumulation) unit 110. However, if the broadcast receiving device 100 is configured to have a "temporary storage" mode that allows storage in the storage (accumulation) unit 110 for only a predetermined time or a predetermined time specified by control information included in the broadcast signal (for example, by the MH-Expire descriptor shown in FIG. 6D), the content can be temporarily stored in the storage (accumulation) unit 110 even if the copy control information included in the MPT indicates "copy prohibited." When content whose copy control information included in the MPT indicates "copy prohibited" is output for viewing on an external device, the content is encrypted and output together with the copy control information indicating "copy prohibited."

[0267] The output for viewing to the external device described above may be performed via video output unit 163 and audio output unit 166 in Fig. 7A, or via digital I / F unit 125, LAN communication unit 121, etc. The copy or move process to the external device described above may be performed via digital I / F unit 125, LAN communication unit 121, etc. in Fig. 7A.

[0268] According to the process described above, it is possible to realize appropriate content protection in accordance with the copy control information associated with the content.

[0269] Furthermore, copying of content whose copy control information indicates copy restrictions such as "copyable only once," "copyable a specified number of times," or "copying prohibited" to an external device via LAN communication unit 121 may be permitted only if the IP address of the external device that is the destination of the packet transmitted from broadcast receiving device 100 is within the same subnetwork as the IP address of broadcast receiving device 100, and may be prohibited if the IP address of the external device is outside the same subnetwork as the IP address of broadcast receiving device 100. Content whose copy control information indicates "unlimited copying permitted but requires encryption processing when stored and output" may also be handled in the same manner.

[0270] Similarly, the process of storing content whose copy control information indicates copy restrictions such as "copyable only for one generation," "copyable a specified number of times," or "copyable an unlimited number of times and requires encryption processing when stored and output" in the storage (accumulation) unit 110 and then moving the content to an external device via the LAN communication unit 121 is only permitted if the IP address of the external device that is the destination of the packet sent from the broadcast receiving device 100 is within the same subnetwork as the IP address of the broadcast receiving device 100, and may be prohibited if the IP address of the external device is outside the same subnetwork as the IP address of the broadcast receiving device 100.

[0271] In principle, video and audio output for viewing of content stored in storage (accumulation) unit 110 of broadcast receiving device 100 is only possible when the IP address of the external device that is the destination of a packet transmitted from broadcast receiving device 100 is within the same subnetwork as the IP address of broadcast receiving device 100, and is prohibited if the IP address of the external device is outside the same subnetwork as the IP address of broadcast receiving device 100. However, if the external device has been connected within the same subnetwork as the IP address of broadcast receiving device 100 within a predetermined period of time and has been registered (paired) as a device that can be viewed even outside the same subnetwork as the IP address of broadcast receiving device 100, the external device may be configured to enable video and audio output for viewing of content stored in storage (accumulation) unit 110 of broadcast receiving device 100 to the external device even if the IP address of the external device is outside the same subnetwork as the IP address of broadcast receiving device 100. In this case, the video and audio output for viewing is performed after encrypting the content.

[0272] According to the processing described above, different processing is performed depending on whether the external device is located within the same subnetwork as the IP address of the broadcast receiving device 100 or outside the same subnetwork, thereby achieving both user convenience and content protection.

[0273] Next, as explained in Figure 6E, in the digital broadcasting system supported by the broadcast receiving device 100 of this embodiment, the location information in the MPT ('MMT_general_location_info()' in Figure 17) means that data acquired via a different route (IPv4, IPv6, MPEG2-TS, URL, etc.) from the data acquired via the TLV stream of the broadcast route may be included in the same package and the same event as the data acquired via the TLV stream. In this case, content protection when copy control information is included in the MPT will be explained.

[0274] First, when copy control information is included in the MPT, data included in the same package and the same event in the location information may be controlled in accordance with the copy control information included in the TLV stream, even if the data is obtained via a different path (IPv4, IPv6, MPEG2-TS, URL, etc.) than the data obtained via the TLV stream of the broadcast path. The copy control status of the content specified by this copy control information can be, as mentioned above, "unlimited copying allowed" (which may be divided into two types: "unlimited copying allowed, with encryption processing required for storage and output" and "unlimited copying allowed, with encryption processing not required for storage and output"), "one generation only," "a specified number of copies allowed" (for example, 9 copies allowed + 1 move allowed is known as "dubbing 10"), "no copying allowed," etc.

[0275] Here, if the data position indicated by the location information includes MPEG2-TS data transmitted in another digital broadcast signal, the MPEG2-TS data is also broadcast in association with copy control information in the other digital broadcast signal. This raises the question of how to control the copy of the MPEG2-TS data in accordance with what information (should it be in accordance with the copy control information included in the TLV / MMT stream or the copy control information included in the MPEG2-TS?).

[0276] In the digital broadcasting system of this embodiment, to solve this problem, the broadcast receiving device 100 may perform one of the following multiple solution operations.

[0277] <Example 1> In the first operation example, when copy control information is included in the MPT and data included in the same package and the same event in the location information includes MPEG2-TS data transmitted in another digital broadcast signal, the copy control state indicated by the copy control information included in the TLV stream is given priority over the copy control state indicated by the copy control information included in the MPEG2-TS.

[0278] For example, if the copy control status indicated by the copy control information included in the TLV stream is "one-generation copy permitted" and the copy control status indicated by the copy control information included in the MPEG2-TS is "a specified number of copies permitted," then even if the data was acquired via a different path (digital broadcast in MPEG2-TS transmission format) than the data acquired via the TLV stream, copy control may be performed on the data as "one-generation copy permitted." For example, if the copy control status indicated by the copy control information included in the TLV stream is "unlimited copying permitted" and the copy control status indicated by the copy control information included in the MPEG2-TS is "specified number of copies permitted," then copy control may be performed on the data as "unlimited copying permitted" even if the data was acquired via a different path (digital broadcast in MPEG2-TS transmission format) than the data acquired via the TLV stream.

[0279] In this operation, data acquired via a route other than the TLV stream can also be put into a copy state that is desired to be managed in the broadcast system supported by the broadcast receiving device 100 of this embodiment.

[0280] <Example 2> In a second operation example, when copy control information is included in the MPT and data included in the same package and the same event in the location information includes MPEG2-TS data transmitted in another digital broadcast signal, the copy control state indicated by the copy control information included in the TLV stream is compared with the copy control state indicated by the copy control information included in the MPEG2-TS, and if the copy control state indicated by the copy control information included in the MPEG2-TS is stricter than the copy control state indicated by the copy control information included in the TLV stream, the MPEG2-TS data is excluded from the content to be processed when storing the data in the storage unit 110 or the like, recording the data on a removable recording medium, or outputting the data from a digital interface.

[0281] In this operation, for data obtained via a route other than the TLV stream, duplication of copy control status on the broadcast receiving device 100 of this embodiment can be eliminated while respecting the original copy control information set in the broadcasting system that transmits the data.

[0282] Furthermore, if the comparison shows that the copy control status indicated by the copy control information contained in the MPEG2-TS is the same as or more lenient than the copy control status indicated by the copy control information contained in the TLV stream, then copy control can be performed on the MPEG2-TS data contained in the same package and the same event in the location information as content in the copy control status indicated by the copy control information contained in the TLV stream.

[0283] In this operation, for data obtained via a route other than the TLV stream, duplication of copy control status on the broadcast receiving device 100 of this embodiment can be eliminated while respecting the original copy control information set in the broadcasting system that transmits the data.

[0284] In the above explanation, the copyright protection function of the broadcast receiving device 100 of this embodiment has been described as being performed based on the copy control information included in the MPT. However, the table in which the copy control information is placed is not limited to the MPT. Other than the MPT, the copy control information may be placed and transmitted in the MH-Service Description Table (MH-SDT) or MH-Event Information Table (MH-EIT) described in FIG. 6B, or in other tables, and the broadcast receiving device 100 may perform copyright protection processing in accordance with these.

[0285] According to the present embodiment described above, it is possible to provide a broadcast receiver compatible with MMT digital broadcasting. Example 2

[0286] The following describes a second embodiment of the present invention. The configuration, processing, effects, etc. of this embodiment are the same as those of the first embodiment unless otherwise specified. Therefore, the following mainly describes the differences between this embodiment and the first embodiment, and omits explanations of common points as much as possible to avoid duplication. The following description also assumes that the broadcast receiving device of this embodiment is a television receiver that supports both the MMT and MPEG2-TS media transport methods.

[0287] [Broadcast receiving device hardware configuration] 24 is a block diagram showing an example of the internal configuration of a broadcast receiving device 800. The broadcast receiving device 800 is composed of a main control unit 801, a system bus 802, a ROM 803, a RAM 804, a storage unit 810, a LAN communication unit 821, an extension interface unit 824, a digital interface unit 825, a first tuner / demodulation unit 831, a second tuner / demodulation unit 832, an MMT decoding processing unit 841, an MPEG2-TS decoding processing unit 842, a video synthesis unit 861, a monitor unit 862, a video output unit 863, an audio synthesis unit 864, a speaker unit 865, an audio output unit 866, and an operation input unit 870.

[0288] The main control unit 801, system bus 802, ROM 803, RAM 804, storage unit 810, expansion interface unit 824, digital interface unit 825, monitor unit 862, video output unit 863, speaker unit 865, audio output unit 866, operation input unit 870, etc. are assumed to have functions equivalent to those of the main control unit 101, system bus 102, ROM 103, RAM 104, storage (accumulation) unit 110, expansion interface unit 124, digital interface unit 125, monitor unit 162, video output unit 163, speaker unit 165, audio output unit 166, operation input unit 170, etc. in the broadcast receiving device 100 of Example 1, and detailed explanations thereof will be omitted.

[0289] The first tuner / demodulation unit 831 receives, via an antenna not shown, broadcast waves of a broadcast service that employs MMT as a media transport method, and tunes (selects) to a channel of the service desired by the user under the control of the main control unit 801. Furthermore, the first tuner / demodulation unit 831 demodulates the received broadcast signal to obtain an MMT data stream, which it outputs to an MMT decoding processing unit 841. The second tuner / demodulation unit 832 receives, via an antenna not shown, broadcast waves of a broadcast service that employs MPEG2-TS as a media transport method, and tunes (selects) to a channel of the service desired by the user under the control of the main control unit 801. Furthermore, the second tuner / demodulation unit 832 demodulates the received broadcast signal to obtain an MPEG2-TS data stream, which it outputs to an MPEG2-TS decoding processing unit 842.

[0290] The MMT decoding processing unit 841 receives the MMT data sequence output from the first tuner / demodulation unit 831 and performs separation and decoding processes on the real-time presentation elements, such as a video data sequence, an audio data sequence, a superimposed text data sequence, and a subtitle data sequence, based on a control signal included in the MMT data sequence. The MMT decoding processing unit 841 has functions corresponding to the separation unit 132, the video decoder 141, the video color gamut conversion unit 142, the audio decoder 143, the superimposed text decoder 144, the subtitle decoder 145, the subtitle synthesis unit 146, the subtitle color gamut conversion unit 147, the data decoder 151, the cache unit 152, the application control unit 153, the browser unit 154, the application color gamut conversion unit 155, the sound source unit 156, and the like, in the broadcast receiving device 100 of the first embodiment. The MMT decoding processing unit 841 can perform the various processes described in the first embodiment. Note that the details of the various processes are the same as those described in the first embodiment, and therefore will not be described here.

[0291] The MPEG2-TS decoding processor 842 receives the MPEG2-TS data stream output from the second tuner / demodulator 832, and performs processes such as separation and decoding of real-time presentation elements such as video data streams, audio data streams, superimposed text data streams, and subtitle data streams based on the control signals included in the MPEG2-TS data streams. The MPEG2-TS decoding processor 842 has the same functions as an IRD (Integrated Receiver Decoder) unit of a conventional television receiver that receives broadcast waves from a broadcast service that uses MPEG2-TS as the media transport method, and detailed description thereof will be omitted.

[0292] The video synthesis unit 861 receives the video information, subtitle information, and application information output from the MMT decoding processing unit 841 and the video information, subtitle information, and application information output from the MPEG2-TS decoding processing unit 842, and performs processing such as appropriate selection and / or superimposition. The video synthesis unit 861 includes a video RAM (not shown), and drives the monitor unit 862 and the like based on the video information and the like input to the video RAM. Furthermore, the video synthesis unit 861 performs scaling processing, superimposition processing of EPG screen information, and the like as necessary based on the control of the main control unit 801. The audio synthesis unit 164 receives the audio information output from the MMT decoding processing unit 841 and the audio information output from the MPEG2-TS decoding processing unit 842, and performs processing such as appropriate selection and / or mixing.

[0293] The LAN communication unit 821 is connected to the Internet 200 via the router device 200r, and transmits and receives data to and from each server device and other communication devices on the Internet 200. It also acquires the MMT data string (or a part thereof) and MPEG2-TS data string (or a part thereof) of a program transmitted via a communication line, and outputs them to the MMT decoding processing unit 841 and MPEG2-TS decoding processing unit 842 as appropriate.

[0294] [Time display on broadcast receiving device] In the broadcast receiving device 800 of this embodiment, it is assumed that the current date and current time can be displayed on the EPG screen, various setting screens, etc. Information relating to the current date and current time is transmitted by MH-TOT or the like in broadcast services that employ MMT as the media transport method, and is transmitted by TOT (Time Offset Table) or the like included in SI (Service Information) defined in the MPEG-2 system in broadcast services that employ MPEG2-TS as the media transport method. The broadcast receiving device 800 can acquire the information relating to the current date and current time by referring to the MH-TOT or the TOT.

[0295] In general, when the video synthesis unit 861 mainly selects the video information etc. output from the MMT decoding processing unit 841, the information relating to the current date and time obtained from the MH-TOT is superimposed on the video information etc., and when the video synthesis unit 861 mainly selects the video information etc. output from the MPEG2-TS decoding processing unit 842, the information relating to the current date and time obtained from the TOT is superimposed on the video information etc.

[0296] However, because there are differences in encoding / decoding processes, transmission paths, etc. between a broadcast service that employs MMT as the media transport method and a broadcast service that employs MPEG2-TS as the media transport method, there is a possibility that inconsistencies may occur, particularly in the current time display, when selecting a broadcast service that employs MMT as the media transport method and a broadcast service that employs MPEG2-TS as the media transport method. For example, as shown in Fig. 25, when switching the screen display from EPG screen 162g displaying channel information for a broadcast service that employs MMT as the media transport method to EPG screen 162h displaying channel information for a broadcast service that employs MPEG2-TS as the media transport method, the current time display switches from current time display 162g1 to current time display 162h1, which causes an inconsistency that may cause the user to feel visually uncomfortable.

[0297] In the broadcast receiving device 800 of this embodiment, in order to prevent the user from experiencing visual discomfort, even when the video synthesis unit 861 mainly selects video information, etc. output from the MMT decoding processing unit 841, control is performed so that information related to the current date and current time obtained from the TOT is superimposed on the video information, etc. In other words, control is performed so that current time information provided by a broadcast service that adopts MPEG2-TS as the media transport method is superimposed on the content of a broadcast service that adopts MMT as the media transport method.

[0298] By performing the above control, the broadcast receiving device 800 of this embodiment always displays the current time information acquired by referring to the TOT when displaying the current time. Therefore, even when switching between a broadcast service that uses MMT as the media transport method and a broadcast service that uses MPEG2-TS as the media transport method, it is possible to prevent the user from feeling visual discomfort due to inconsistency in the display of the current time.

[0299] 26 shows an example of selection control of the current time information reference source according to the reception status of each broadcast service in the broadcast receiving device 800 of this embodiment. In the broadcast receiving device 800 of this embodiment, when reception of a broadcast service that employs MPEG2-TS as the media transport method is possible, the broadcast receiving device 800 always refers to the TOT to acquire current time information, and only when reception of a broadcast service that employs MPEG2-TS as the media transport method is impossible and reception of a broadcast service that employs MMT as the media transport method is possible, the broadcast receiving device 800 is controlled to refer to the MH-TOT to acquire current time information.

[0300] In addition, the same effect as described above can be obtained by controlling the content of a broadcast service that uses MPEG2-TS as the media transport method to be superimposed with the current time information provided by a broadcast service that uses MMT as the media transport method, in the opposite way to the above control.

[0301] As mentioned above, in either case, whether the current time information provided by a broadcast service that adopts MPEG2-TS as the media transport method is superimposed on the content of a broadcast service that adopts MMT as the media transport method, or the current time information provided by a broadcast service that adopts MMT as the media transport method is superimposed on the content of a broadcast service that adopts MPEG2-TS as the media transport method, the current time information can be corrected by referring to the "delta" parameter of the time information in the TMCC extended information area, as explained in "Time management of broadcast receiving device" in Example 1.

[0302] [EPG display on broadcast receiver] Event schedule information for broadcast services that use MMT as the media transport method is transmitted using MH-EIT, etc. On the other hand, event schedule information for broadcast services that use MPEG2-TS as the media transport method is transmitted using EIT (Event Information Table) or the like provided in the SI specified in the MPEG-2 system. Therefore, generally, when video information, etc. provided by a broadcast service that uses MMT as the media transport method is displayed, the event schedule information (MH-EIT) for the broadcast service that uses MMT can be acquired, and when video information, etc. provided by a broadcast service that uses MPEG2-TS as the media transport method is displayed, the event schedule information (EIT) for the broadcast service that uses MPEG2-TS can be acquired.

[0303] However, the broadcast receiving device 800 of this embodiment is capable of acquiring both the MH-EIT and the EIT, even when displaying video information, etc. provided by a broadcast service that adopts MMT as the media transport method, or when displaying video information, etc. provided by a broadcast service that adopts MPEG2-TS as the media transport method, thereby improving usability for the user.

[0304] 27A shows an example of an EPG screen in the broadcast receiving device 800 of this embodiment. In the figure, EPG screen 162i is an EPG screen created based on the MH-EIT of a broadcast service that uses MMT as the media transport method, and "M1 TV," "M2 Broadcast," "M3 Channel," "M4 TV," "Television M5," etc. are assumed to be the names of broadcast stations of the broadcast service that uses MMT as the media transport method. Also, EPG screen 162j is an EPG screen created based on the EIT of a broadcast service that uses MPEG2-TS as the media transport method, and "T6 TV," "T7 Broadcast," "T8 Channel," "T9 TV," "Television TA," etc. are assumed to be the names of broadcast stations of the broadcast service that uses MPEG2-TS as the media transport method.

[0305] For example, while a user is watching a broadcast program provided by a broadcast service that employs MMT as a media transport method, if the user operates a remote control (not shown) to instruct the display of an EPG screen, an initial screen (not shown) of the EPG screen is displayed. The initial screen of the EPG screen is an EPG screen created based on the MH-EIT of the broadcast service that employs MMT as a media transport method, and displays detailed information about broadcast programs on each channel from 5:00 PM (nearby the current time) on October 7, 2014 (today). Next, if the user wishes to check detailed information about broadcast programs on each channel from 8:00 PM on October 9, 2014, and instructs the remote control (not shown) to update the EPG screen, EPG screen 162i is displayed.

[0306] Furthermore, if the user desires to check detailed information about a broadcast program provided by a broadcast service that employs MPEG2-TS as a media transport method and instructs a network switch by operating a remote control (not shown), an EPG screen 162j is displayed. At this time, the broadcast receiving device 800 of this embodiment is controlled to display detailed information about the broadcast programs on each channel on the same day and in the same time slot (i.e., from 8:00 p.m. on October 9, 2014) as the EPG screen 162i that was displayed immediately before, rather than the initial screen of the EPG screen created based on the EIT of the broadcast service that employs MPEG2-TS as a media transport method (i.e., detailed information about the broadcast programs on each channel from 5:00 p.m. on October 7, 2014).

[0307] The above control allows the user to easily and continuously check detailed information about broadcast programs broadcast on the same day and at the same time on multiple networks using different media transport methods, thereby improving the usability of the broadcast receiving device 800.

[0308] Fig. 27B is a diagram showing an example of an EPG screen in the broadcast receiving device 800 of this embodiment that is different from the above. The EPG screen 162k shows a state in which the EPG screen 162i shown in Fig. 27A is scrolled in the channel direction (horizontal direction) by operating a remote control (not shown). That is, in the example shown in Fig. 27B, by scrolling the EPG screen in the channel direction (horizontal direction), channel information created based on the MH-EIT of a broadcast service that employs MMT as the media transport method and channel information created based on the EIT of a broadcast service that employs MPEG2-TS as the media transport method are seamlessly displayed on the same time axis.

[0309] Therefore, even if a user desires to check channel information created based on the EIT of a broadcast service that uses MPEG2-TS as the media transport method while checking channel information created based on the MH-EIT of a broadcast service that uses MMT as the media transport method, it is not necessary to issue an instruction to switch networks using a remote control (not shown). Furthermore, the user can simultaneously check detailed information about broadcast programs airing on the same day and at the same time on multiple networks that use different media transport methods. In other words, the usability of the broadcast receiving device 800 is improved. Example 3

[0310] The following describes Example 3 of the present invention. The configuration, effects, etc. of this example are the same as those of Examples 1 and 2 unless otherwise specified. Therefore, the following mainly describes the differences between this example and Examples 1 and 2, and omits explanations of common points as much as possible to avoid duplication. In this example, handling of presentation area information set by the layout setting table (LCT) shown in FIG. 18 will be described.

[0311] [Broadcast receiving device hardware configuration] The hardware configuration of the broadcast receiving device 100 is the same as that of the first embodiment, and therefore a description thereof will be omitted.

[0312] [Program data structure] FIG. 28 shows the structure of program data. Program data consists of information (assets 30003) to be presented to the broadcast receiving device 100, such as video, audio, and program linkage information, and control information. The program linkage information stores text information, graphic information, image information, or video information to be presented in conjunction with the program video. FIG. 28 shows a PA message 30000, which is part of the control information, that describes the presentation method and acquisition source information for the asset 30003. The acquisition source for the asset 30003 is described as MMT_general_location_info (FIG. 31) in the MP table (MPT) 30001 (FIG. 17) in the PA message 30000 (FIG. 30). In addition, a layout setting table (LCT) 30100 (FIG. 18) is placed in the PA message 30000, and the layout of the area in which each asset 30003 should be presented is described. Examples of presentation area layouts are shown in FIGS. 19A to 19D.

[0313] A package list table (PLT) 30002 (Fig. 32) is placed within the PA message 30000, and the MMT_general_location_info (Fig. 31) within the PLT can describe the location from which another PA message 30000 can be obtained. By specifying the location from which this PA message 30000 can be obtained, the PA message 30000 can be made into a hierarchical structure. The location types from which the PA message 30000 and asset 30003 can be obtained are shown in Fig. 33.

[0314] Normally, the hierarchical structure of the PA message 30000 is limited to two layers as shown in FIG. 28, but it is also possible to add more layers by placing a PLT 30002 in the PA message 30000 at the second layer.

[0315] Since assets are composed of Media Processing Units (MPUs), which serve as processing units (Fig. 29), the presentation area of ​​an asset 30003 is specified by specifying the presentation area of ​​the MPU in the MPU presentation area specification descriptor (Fig. 34). The MPU presentation area specification descriptor is placed in the asset descriptor area of ​​the MPT. Note that since a presentation area is specified for each MPU, it is also possible to use a presentation method in which the presentation area of ​​the same asset 30003 is changed during presentation. Note that in order to reduce the amount of data, a control method is also possible in which presentation areas are not specified for all MPUs belonging to the asset, but rather only the presentation area of ​​the first MPU and the first MPU of the group of MPUs whose presentation area is to be changed.

[0316] [Example of asset presentation] <Example 1> The broadcast receiving device 100 acquires presentation area information by reading the LCT 30100. FIG. 16 shows the flow of how the broadcast receiving device 100 acquires program control information, as an example of channel switching. Like the MPT 30001, the LCT 30100 is placed in an MMTP packet and transmitted. Because the MPT 30001 contains information specifying the presentation area of ​​asset 30003, it is preferable that the LCT 30100 be acquired before the MPT 30001. As shown in FIG. 16, it is preferable that the LCT 30100 be acquired as a step between S209 and S210 and between S214 and S215. Note that even if acquisition at the above timing is not possible, it is equally preferable to acquire the LCT before S216.

[0317] LCT30100 is placed in PA message 30000, but LCT30100 relating to asset 30003 corresponding to the second layer PA message is placed in either the first layer PA message 30000 or the second layer PA message 30000. When presenting asset 30003, the presentation area information of LCT30100 placed in the PA message 30000 to which asset 30003 to be presented belongs is used preferentially. If LCT30100 is not placed in the PA message 30100 to which asset 30003 belongs, the presentation area information of LCT30100 placed in the PA message 30100 of the upper layer is used.

[0318] By using the method of this operation example, if the same LCT30100 is used for the entire program data of Figure 28, by placing a common LCT30100 in the first layer PA message 30000, presentation area information can be obtained at an early stage, making it possible to present program data quickly.

[0319] <Example 2> If LCT30100 is not included in the MMTP packet, the broadcast receiving device uses the presentation area information of the LCT30100 that it has acquired up to that point. In other words, the broadcast receiving device stores the presentation area information of LCT30100, and updates the stored presentation area information each time it acquires a new LCT30100.

[0320] However, immediately after an event occurs that invalidates the presentation area information used up until that point, such as when the power is turned on or the channel is changed, there is no valid presentation area information, so even if the video and audio data of a program has been acquired, it may not be possible to present that data. Therefore, until valid presentation area information is acquired, presentation processing is performed assuming that the presentation area shown in FIG. 19A, for example, has been set as temporary presentation area information. The setting in FIG. 19A will be referred to as the default setting hereinafter. The presentation area shown in the default setting (FIG. 19A) is a full-screen display area set for the device with device_id=0, i.e., the main device, and is assigned 0 to layout_number, region_number, and layer_order.

[0321] Fig. 35A shows a state in which only main asset 30201 is presented using temporary presentation area information, while Fig. 35B shows a state in which, after acquiring LCT 30100, sub-asset 30202 is also presented according to the program's original presentation area information. When temporary presentation area information is used, the presentation area designation of the main asset is ignored, an area with layout_number 0 and region_number 0 is designated, and other assets are not presented. Note that here, a main asset refers to an asset that designates region_number 0 on the main device or an asset that designates region_number 0 in an asset transmitted by broadcast waves, and a sub-asset refers to any other asset.

[0322] By setting temporary presentation area information in this way, it becomes possible to perform presentation processing of at least the main asset even before the information of the LCT30100 is read.

[0323] <Example 3> In operation example 2, an example was shown in which only the main asset is presented using the default presentation area information until a new LCT30100 is obtained when changing channels, etc., but the LCT30100 used in the program that was being viewed up until that point may also be used. The asset (main asset) specified in the area with region_number 0 in the program after the channel change is presented in the area with region_number 0 in the presentation area information that was used up until that point, and other assets (sub-assets) are not displayed.

[0324] After acquiring the LCT30100 of the program after the channel change, all assets are presented using the presentation area information. Furthermore, if the LCT30100 used in the previously viewed program divides the display area as shown in Fig. 19B, the processing of operation example 2 may be performed, and if the LCT30100 used in the previously viewed program provides an overlay display as shown in Fig. 19C, the processing of operation example 3 may be performed. Furthermore, if the LCT30100 used in the previously viewed program has an area with region_number 1 or greater, a predetermined pattern or message may be displayed in the area.

[0325] By using the presentation area information of the program that has been viewed up until that point in time, it becomes possible to perform at least the presentation processing of the main asset even before the information of LCT30100 is read.

[0326] <Example 4> Since there may be cases where the original channel is returned to after the channel is changed, it is also possible to store the LCT30100 information once read in association with the channel information, and use the stored presentation area information when the channel is returned to. Note that storing the most recent LCT30100 for each of all channels that can be received by the broadcast receiving device 100 improves the convenience of presentation area control when changing channels.

[0327] Furthermore, since the presentation area information may change even during a program, an expiration date may be set in the LCT30100. If the expiration date has passed when the channel is changed back, the presentation area information is not used, and the default settings are used as shown in Operation Example 2 or Operation Example 3, or only the main asset is presented using the presentation area information of the program that was being viewed up until that point. Alternatively, only the main asset may be presented using the expired presentation area information of that channel. Of course, once a new LCT30100 is obtained, the normal presentation method is restored. Note that the control may be performed by referencing the expiration date, or may be performed by referencing the version instead of the expiration date information.

[0328] An example of setting an expiration date in the LCT 30100 is shown in Figure 36A. It is set in the LCT expiration date descriptor in NTP length format (ending_time). The descriptor is placed in the descriptor area of ​​the LCT 30100 (Figure 18).

[0329] Alternatively, an expiration date may be set for each layout, as shown as a layout expiration date descriptor in FIG. 36B.

[0330] Alternatively, an expiration date may be set for each area, as shown in the presentation area expiration date descriptor in FIG. 36C.

[0331] The expiration date may be set for a single layer or for multiple layers. When the expiration date is set for multiple layers, the earlier expiration date is given priority for each area.

[0332] This method allows presentation area information that has been acquired once to be used effectively while taking into consideration the expiration date.

[0333] <Example 5> In operation example 4, the presentation area information of a program is stored once it has been read, but it is also possible to prepare presentation area information (common presentation area information) that is used in common for multiple programs within a channel for each channel, obtain the common presentation area information in advance in broadcast receiving device 100, and use the common presentation area information for each program.

[0334] The broadcast receiving device 100 acquires the common presentation area information in advance in the format of the LCT (Fig. 18). To indicate that it is common presentation area information, the common presentation area descriptor shown in Fig. 37 is used. This descriptor is placed in the descriptor field of the LCT (Fig. 18), and the layout number of the common presentation area is listed together with the device number. The service_id indicates the broadcast channel. Furthermore, the start time (beginning_time) and end time (ending_time) of the validity period of the common presentation area information are written in NTP length format. The full_set_flag is also written so that it can be confirmed that all information is present when updating information. The meaning of the full_set_flag is summarized in Fig. 38.

[0335] This common presentation area information may be read once a day or once a week, for example, outside of broadcast hours, etc. Also, it may be obtained from broadcast waves or via the Internet.

[0336] In case the common presentation area information has not been read, the program data transmits the common presentation area information used in that program as LCT30100. At that time, the full_set_flag of the common presentation area descriptor indicates that this is only part of the common presentation area information.

[0337] By using this common presentation area information, asset 30003 can be presented promptly even immediately after broadcast receiving device 100 is powered on or immediately after a program change, before LCT 30100 is acquired.

[0338] <Example 6> Operation example 5 shows a method of using common presentation area information, but even if the common presentation area information is transmitted via broadcast waves or the Internet on a channel, depending on the program, a presentation area with a layout not described in the common presentation area information may be used.

[0339] Specifically, layout information that is not included in the common presentation area information can be described in the LCT30100 for the program. In this case, the layout number of the common presentation area is described in the common presentation area descriptor (FIG. 37). Therefore, the broadcast receiving device 100 determines whether the LCT30100 contains additional presentation area information that is not a common presentation area, and if so, uses that information. In this case, if the layout number and area number of the presentation area overlap with those of the common presentation area information, it is determined in advance which information will take priority. That is, depending on the broadcast system, the broadcast receiving device 100 may be configured to give priority to the common presentation area information. Furthermore, depending on the broadcast system, the broadcast receiving device 100 may be configured to give priority to program-specific presentation area information.

[0340] Furthermore, if the common presentation area descriptor (FIG. 37) is not placed in the LCT 30100, all presentation area information written in the LCT 30100 is treated as not being common area information.

[0341] The additional presentation area information for each program may be acquired from broadcast waves, but may also be acquired via the Internet instead of from broadcast waves.

[0342] According to this method, it is possible to use presentation area information optimized for each program while utilizing common presentation area information.

[0343] <Example 7> Asset 30003 is presented in one presentation area, but in cases where it is better to display it on as many devices as possible, such as breaking news, it is better to present the same content on all devices available at that time.

[0344] Specifically, in the overlap presentation area specification descriptor (Fig. 39), the layout_number is written that will set the same area on other devices as the layout setting of the main device (device with Device_id=0). This descriptor is placed in the descriptor area of ​​the LCT30100 (Fig. 18).

[0345] FIG. 40 shows an example in which the same screen content is presented on a sub-device (mobile information terminal 700) in addition to a main device (broadcast receiving device 100).

[0346] In addition, in preparation for when the original program is returned to after the breaking news has ended, the presentation area information used in the original program may be stored and used after the breaking news has ended.

[0347] This method increases the visibility of important and urgent information.

[0348] <Example 8> The presentation area of ​​each asset 30003 is specified by the layout_number (layout number) and region_number (region number) using the MPU presentation area specification descriptor (Figure 34). If there is no presentation area information corresponding to this layout number and region number, presentation is not possible, and the asset 30003 in question is not presented. However, if the asset 30003 with an abnormality is one that is presented in a partial area of ​​the screen, it may not be immediately obvious that there is a display abnormality. Therefore, if an asset 30003 that cannot be presented occurs, an error message like that shown in Figure 41 is displayed.

[0349] This method allows the viewer to recognize that the display is not being performed normally.

[0350] <Example 9> In Operation Example 8, the operation when a presentation area without presentation area information is specified is explained, but the operation when different assets 30003 specify the same presentation area is explained below. In the case of assets that display some kind of content, they cannot be displayed in the same presentation area, so the same presentation area must not be specified simultaneously by different assets 30003. If they are specified simultaneously, the asset transmitted via broadcast waves takes priority. Alternatively, the presentation of the asset 30003 that originally used the layout number and area number continues, and the presentation of the asset 30003 specified later is prohibited. Alternatively, the presentation of all assets 30003 with overlapping area specifications is prohibited. If an asset 30003 that cannot be presented occurs, an error message as shown in Figure 41 may be displayed.

[0351] However, it is possible that the same presentation area may be specified for different assets 30003, for example, when adding additional asset information to a video asset to enhance the gradation level. Dependency descriptor information is used to indicate that multiple assets are in a complementary relationship that makes up a single piece of content. The data structure of the dependency descriptor is shown in Figure 42. When this dependency exists, presentation is permitted even when the same presentation area is specified.

[0352] To manage the presentation area designation of assets 30003, a management table showing which assets 30003 designate which presentation areas may be used. An example of a management table is shown in Figure 43. Assets 30003 with asset IDs 1 and 3, and asset IDs 2 and 4, are dependent on each other, so they are allowed to be displayed even if the same area is designated. On the other hand, asset 30003 with asset ID 7 is a video asset, and there is no dependency between them, and it designates the same area as asset ID 0, so its display is prohibited.

[0353] Note that asset 30003 with asset ID 1 is transmitted via broadcast waves, so this is given priority. Also, asset 30003 with asset ID 7 from the same acquisition source has been prohibited from presentation, so asset 30003 with asset ID 8 is likely to be audio that is paired with asset ID 7, and is therefore also prohibited from presentation. Assets with asset IDs 2, 4, 6, and 8 are audio assets, and audio assets are not directly related to presentation processing in the monitor unit 162, so they do not necessarily need to be managed in the management table. In other words, only video assets may be managed in the management table.

[0354] By controlling the presentation in this way, it is possible to prevent abnormal presentation when there is an inconsistency in the control information.

[0355] <Example 10> Dependencies between assets 30003 can be parallel, where content is not complete unless multiple dependent assets 30003 are available, or they can be dependent, where data for improving image quality is provided by another asset 30003 to a subject asset 30003. Subject assets 30003 can be presented independently, but dependent assets 30003 are likely to be presented abnormally if the subject asset 30003 does not exist. Therefore, if the dependent asset 30003 cannot be acquired, the dependent asset 30003 is prohibited from being presented. Note that a multi-layered structure may also be used, where a dependent asset 30003 has yet another asset 30003 subordinate to it.

[0356] To specify a dependency relationship, it is necessary to decide in advance whether the asset 30003 described in the dependency descriptor (Fig. 42) indicates the asset 30003 that is dependent on the asset, or the asset 30003 that is dependent on the asset. In the case of assets 30003 that are in a parallel relationship, a dependency descriptor (Fig. 42) is placed indicating that both depend on each other.

[0357] Another way to specify a dependency relationship is to explicitly state the dependency relationship in the dependency descriptor (Fig. 42). A dependency descriptor that explicitly states a dependency relationship is shown in Fig. 44. A parameter called dependency_type is specified, which indicates the type of dependency for the dependent asset. The meaning of dependency_type is shown in Fig. 45. 0 means that one asset is dependent on the other, and 1 means that the other asset is dependent on it. In the case of a parallel relationship, each asset is specified as being dependent on the other asset.

[0358] An example of a presentation permission / prohibition management table is shown in Figure 46. Assets with IDs 3 and 4 are subordinate to IDs 1 and 2, but since assets with IDs 1 and 2 have been acquired, presentation is permitted. On the other hand, assets with IDs 7 and 8, which are subordinate to assets 9 and 10, have not been acquired, so presentation is prohibited.

[0359] Assets with IDs 11 and 12 are mutually dependent, but since both are available, their presentation is permitted. On the other hand, assets with IDs 13 and 14 are also mutually dependent, but since asset ID 14 has not been acquired, presentation of asset ID 13 is prohibited. If asset 30003 that cannot be presented occurs, an error message like that shown in Figure 41 may be displayed.

[0360] In this way, by controlling the presentation while taking into consideration the subordinate relationships, it is possible to prevent abnormal presentation when there is an inconsistency in the control information.

[0361] <Example 11> The broadcast receiving device 100 can present both asset 30003 acquired from broadcast waves and asset 30003 acquired from a communication line (Internet), but depending on the state of the communication line, it may be impossible to acquire asset 30003 via the communication line, or the broadcast receiving device 100 may not be connected to the communication line at all. Therefore, it may be possible to normally display only the broadcast video of the broadcast waves in full screen using the default setting (FIG. 19A), and when asset 30003 via the communication line is acquired, present asset 30003 in an area specified according to the setting of LCT30100.

[0362] For example, the case will be described in which the area settings of the LCT 30100 are as shown in FIG. 19B, with the broadcast video set to be presented in area 0 and the asset 30003 received via the communication line set to be presented in areas 1 and 2. When only the broadcast wave video is being received, the default setting (FIG. 19A) is used to display the broadcast video in full screen, and when the asset 30003 received via the communication line becomes available, the area settings of the LCT 30100 are used to present the broadcast video in area 0 in FIG. 19B and the asset 30003 received via the communication line in areas 1 and 2. In this case, the LCT 30100 may not be transmitted via the broadcast wave, but may be transmitted together with the asset 30003 received via the communication line. By using the method of this operation example, it is possible to display according to the actual program data reception status. Note that if only one of the assets 30003 received via the communication line has been acquired and the other has not yet been acquired, the default setting (FIG. 19A) may remain. It is desirable to control the transition to the area setting of FIG. 19B when assets 30003 via both communication lines are collected.

[0363] Although examples of the embodiment of the present invention have been described above using Examples 1 to 3, the configurations for realizing the technology of the present invention are not limited to the above examples, and various modifications are possible. For example, it is possible to replace part of the configuration of one example with the configuration of another example, or it is also possible to add the configuration of another example to the configuration of one example. All of these fall within the scope of the present invention. Furthermore, numerical values, messages, etc. appearing in the text and figures are merely examples, and the effects of the present invention will not be impaired even if different ones are used.

[0364] The functions of the present invention described above may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. Alternatively, they may be realized by software, such as by a microprocessor unit interpreting and executing an operating program that realizes each function. Hardware and software may also be used in combination.

[0365] The software that controls the broadcast receiving device 100 may be stored in the ROM 103 and / or storage unit 110 of the broadcast receiving device 100 before the product is shipped. Alternatively, the software may be acquired via the LAN communication unit 121 from another application server 500 on the Internet 200 after the product is shipped. Alternatively, the software may be stored on a memory card, optical disk, or the like and acquired via the expansion interface unit 124.

[0366] In addition, the control lines and information lines shown in the diagram are those considered necessary for explanation, and do not necessarily represent all the control lines and information lines on the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0367] 100,800...Broadcast receiving device, 100a...antenna, 101,801...main control unit, 102,802...system bus, 103,803...ROM, 104,804...RAM, 110,810...storage unit, 121,821...LAN communication unit, 124,824...extension interface unit, 125,825...digital interface unit, 131,831,832...tuner / demodulation unit, 132...separation unit, 141...video decoder, 142...video color gamut conversion unit, 143...audio decoder, 144...character superimposition decoder, 145...subtitle decoder, 146...subtitle synthesis unit, 147...subtitle color gamut conversion unit, 151...data decoder, 152...cache unit, 153...application control unit, 154...browser unit, 155...application color gamut conversion unit, 156...sound source unit, 161,861...video synthesis unit, 162,862...monitor unit, 163,863...video output unit, 164,864...audio synthesis unit, 165,865...speaker unit, 166,866...audio output unit, 170,870...operation input unit, 841...MMT decoding processing unit, 842...MPEG2-TS decoding processing unit, 200...Internet, 200r...router device, 200a...access point, 300t...radio tower, 300s...broadcasting satellite (or communication satellite), 300...broadcasting station server, 400...service provider server, 500...other application servers, 600...mobile telephone communication server, 600b...base station, 700...mobile information terminal.

Claims

[Claim 1] A content protection processing method in a broadcast receiving device that receives broadcast program content, comprising: a receiving step of receiving the broadcast program content; a storage step of storing the broadcast program content received in the receiving step; an output step of outputting the broadcast program content stored in the storage step to an external device; Equipped with In the storing step, when the broadcast program content received in the receiving step is content designated as copy-only-one-generation protected, the broadcast program content received in the receiving step is recorded and stored in an encrypted state so that it can be played back only by the broadcast receiving device, The storage of the broadcast program content in the storage step can be performed in a storage unit at the output destination of an IP interface configured with Ethernet-compatible hardware provided in the broadcast receiving device, and the storage of the broadcast program content in the storage unit at the output destination of the IP interface in the storage step in an encrypted state so that it can be played only by the broadcast receiving device, and the output of the broadcast program content stored in the storage unit at the output destination of the IP interface in the storage step in an encrypted state so that it can be played only by the broadcast receiving device, to the external device in the output step can be performed via the same IP interface configured with Ethernet-compatible hardware, In the storage step, the broadcast program content is recorded in an encrypted state so that it can be played back only by the broadcast receiving device in the storage unit at the output destination of the IP interface, and then the broadcast receiving device plays back the stored broadcast program content, and the stored broadcast program content is output from the broadcast receiving device. In the output step, the output control state to the external device via the IP interface is as follows: a first output control state in which, in the storage step, the broadcast program content is recorded in an encrypted state so that it can only be played back by the broadcast receiving device in the storage unit at the output destination of the IP interface, and then the broadcast receiving device completes storage by playing back the stored broadcast program content, and in the output step, the broadcast program content is output for viewing in an encrypted state when output to the external device via the IP interface when the IP address of the external device is within the same subnetwork as the IP address of the broadcast receiving device, and the output is prohibited when the IP address of the external device is outside the same subnetwork as the IP address of the broadcast receiving device, but when the external device is connected within the same subnetwork as the IP address of the broadcast receiving device and is paired with the IP address of the broadcast receiving device within a predetermined period of time, the external device is permitted to output even if the IP address of the external device is outside the same subnetwork as the IP address of the broadcast receiving device; and a second output control state for permitting a move to the external device via the IP interface when the stored broadcast program content is output from the broadcast receiving device after being recorded in an encrypted state so that it can be played back only on the storage unit at the output destination of the IP interface in the storage step and then played back by the broadcast receiving device to complete the storage. The second output control state permits a move to the external device when the IP address of the external device is within the same subnetwork as the IP address of the broadcast receiving device and prohibits a move when the IP address of the external device is outside the same subnetwork as the IP address of the broadcast receiving device. Content protection processing method.

Images