Content protection processing method

Abstract

To provide a digital broadcast receiver capable of executing a function with a higher added value.SOLUTION: In the broadcast receiver 100 for storing a broadcast program whose video recording is reserved from an EPG menu, when protection is designated to a received broadcast program content, the broadcast program content is stored while being encrypted so as to be reproduced only by the broadcast receiver. The storage of the broadcast program content in the storage unit, the output of the broadcast program content to the external device, the copy of the broadcast program content to the external device, and the move of the broadcast program content to the external device can be performed via the IP interface, and the output of the broadcast program content to the external device can be performed by the HDMI in addition to the output performed by the IP interface.SELECTED DRAWING: Figure 8A

Description

[Technical Field]

[0001] The present invention relates to a content protection processing method. [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 enhancements. In particular, there are strong demands for the distribution of content and associated applications using broadband networks such as the Internet, as well as for higher resolution / higher definition video content. However, it is difficult to provide high-value-added television receivers that can meet these demands by simply utilizing the data broadcasting reception function and other features of current television receivers or by simply enhancing the function of the data broadcasting reception function and other features.

[0005] An object of the present invention is to realize 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 configuration diagram of a broadcast communication system including a broadcast receiving device according to a first embodiment. [Figure 2A] FIG. 1 is an explanatory diagram of components of an encoded 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 (1) of descriptors used in the MMT-SI of the broadcasting system. [Figure 6D] This is a list (2) of descriptors used in the MMT-SI of the broadcasting system. [Figure 6E] This is a list (3) of descriptors used in the MMT-SI of the broadcasting system. [Figure 7A] FIG. 2 is a diagram showing the relationship between components of a broadcasting system and each table. [Figure 7B]FIG. 1 is a diagram showing the data structure of an MPT of a broadcasting system. [Figure 7C] FIG. 10 is a diagram showing the data structure of location information of a broadcasting system. [Figure 7D] A diagram showing the data structure of an MPU timestamp descriptor for a broadcasting system. [Figure 7E] FIG. 10 is a diagram showing the data structure of the MH-EIT of the broadcasting system. [Figure 7F] FIG. 10 is a diagram illustrating the data structure of an event package descriptor for a broadcasting system. [Figure 8A] 1 is a block diagram of a broadcast receiving device according to a first embodiment. [Figure 8B] 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 8C] 2 is a software configuration diagram of the broadcast receiving device according to the first embodiment. FIG. [Figure 9] FIG. 2 is a block diagram of a broadcast station server according to the first embodiment. [Figure 10] FIG. 2 is a block diagram of a service provider server according to the first embodiment. [Figure 11A] FIG. 1 is a block diagram of a portable information terminal according to a first embodiment. [Figure 11B] FIG. 2 is a software configuration diagram of the portable information terminal according to the first embodiment. [Figure 12A] 1 is a system configuration diagram of clock synchronization / presentation synchronization of a broadcast receiving device according to a first embodiment. [Figure 12B] FIG. 10 is a diagram showing the data structure of the NTP format of a broadcasting system. [Figure 12C] A diagram showing the data structure of MH-TOT of a broadcasting system. [Figure 12D] FIG. 10 is a diagram illustrating the format of the JST_time parameter of a broadcasting system. [Figure 12E] FIG. 10 is a diagram showing the data structure of time information in the TMCC extended information area of ​​a broadcasting system. [Figure 12F] 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. 3 is an operational sequence diagram of the broadcast receiving device according to the first embodiment during channel scanning. [Figure 13B] A diagram showing the data structure of TLV-NIT of a broadcasting system. [Figure 13C] FIG. 10 is a diagram illustrating the data structure of a satellite distribution system descriptor for a broadcasting system. [Figure 13D] FIG. 10 is a diagram illustrating the data structure of a service list descriptor for a broadcasting system. [Figure 13E] FIG. 10 is a diagram showing the data structure of an AMT of a broadcasting system. [Figure 14A] 4 is an operational sequence diagram of the broadcast receiving device according to the first embodiment when selecting a channel. FIG. [Figure 14B] This is a conceptual diagram explaining the reference of the MPT of each package by the PLT of the broadcasting system. [Figure 14C] FIG. 10 is a diagram showing the data structure of a PLT in a broadcasting system. [Figure 15A] 1 is an external view of a remote controller capable of controlling a broadcast receiving device according to a first embodiment. [Figure 15B] FIG. 10 is a diagram illustrating the data structure of a remote control key descriptor for a broadcasting system. [Figure 16A] FIG. 10 is a diagram illustrating a process for selecting multiple channels. [Figure 16B] FIG. 10 is a diagram illustrating the angle selection process for a multi-view compatible program. [Figure 17A] A diagram showing the data structure of the LCT of the broadcasting system. [Figure 17B] FIG. 10 is a diagram illustrating the data structure of an MPU presentation area specification descriptor for a broadcasting system. [Figure 17C] FIG. 10 is a diagram illustrating the assignment of layouts to layout numbers based on the LCT. [Figure 17D] FIG. 10 is a diagram illustrating the assignment of layouts to layout numbers based on the LCT. [Figure 17E] FIG. 10 is a diagram illustrating the assignment of layouts to layout numbers based on the LCT. [Figure 17F] FIG. 10 is a diagram illustrating the assignment of layouts to layout numbers based on the LCT. [Figure 18A] 10A and 10B are diagrams illustrating exception handling in screen layout control based on LCT. [Figure 18B] 10A and 10B are diagrams illustrating exception handling in screen layout control based on LCT. [Figure 19A] FIG. 10 is a diagram illustrating the data structure of a video component descriptor for a broadcasting system. [Figure 19B] FIG. 10 is a diagram illustrating the meaning of the video signal aspect ratio in the video component descriptor. [Figure 19C] 4 is a diagram illustrating an aspect ratio conversion process performed by the broadcast receiving device according to the first embodiment. FIG. [Figure 19D] 4 is a diagram illustrating an aspect ratio conversion process performed by the broadcast receiving device according to the first embodiment. FIG. [Figure 20A] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 20B] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 20C] 3 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 21] 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 22A] FIG. 10 is a diagram illustrating the data structure of a content copy control descriptor for a broadcasting system. [Figure 22B] FIG. 10 is a diagram showing the meaning of copy control information in a content copy control descriptor. [Figure 23] FIG. 10 is a diagram showing the data structure of a content usage control descriptor for a broadcasting system. [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. 1 illustrates an application transmission method. [Figure 29] FIG. 10 is a diagram illustrating asset types. [Figure 30A] FIG. 10 is a diagram showing the data structure of location information of an asset acquisition destination. [Figure 30B] FIG. 10 is a diagram showing the meaning of asset acquisition destination types. [Figure 31] FIG. 10 is a diagram illustrating the data structure of an MPU presentation area specification descriptor. [Figure 32A] A diagram showing the data structure of MH-AIT. [Figure 32B] FIG. 10 is a diagram illustrating the allocation of application types. [Figure 32C] FIG. 10 is a diagram illustrating the definition of an application control code. [Figure 32D] FIG. 10 is a diagram illustrating a data structure of an application identifier. [Figure 33] FIG. 10 is a diagram illustrating the data structure of an MH-application descriptor. [Figure 34A] FIG. 10 is a diagram showing the data structure of an MH-transmission protocol descriptor. [Figure 34B] FIG. 10 is a diagram illustrating the meaning of protocol identification. [Figure 34C] FIG. 10 is a diagram illustrating the data structure of a selector area. [Figure 35] FIG. 10 is a diagram showing the data structure of an MH-simple application location descriptor. [Figure 36] FIG. 10 is a diagram illustrating the data structure of an MH-application boundary authority setting descriptor. [Figure 37] FIG. 10 is a diagram showing the data structure of an MH-activation priority information descriptor. [Figure 38A] FIG. 10 is a diagram illustrating the data structure of an MH-cache information descriptor. [Figure 38B] FIG. 10 is a diagram illustrating the data structure of an MH-application expiration date descriptor. [Figure 39]FIG. 10 illustrates the data structure of an MH-probabilistic adaptive delay descriptor. [Figure 40A] FIG. 11 is an operational sequence diagram of a broadcast receiving device according to a third embodiment when an application is started. [Figure 40B] FIG. 11 is an operational sequence diagram of a broadcast receiving device according to a third embodiment when an application is started. [Figure 40C] FIG. 11 is an operational sequence diagram of a broadcast receiving device according to a third embodiment when an application is started. [Figure 41A] FIG. 11 is an operational sequence diagram when the mobile information terminal according to the third embodiment cooperates with one another. [Figure 41B] FIG. 11 is an operational sequence diagram when the mobile information terminal according to the third embodiment cooperates with one another. [Figure 41C] FIG. 11 is an operational sequence diagram when an application is started in the broadcast receiving device and the portable information terminal according to the third embodiment. [Figure 42A] FIG. 11 is a screen display diagram of a basic screen of a cooperative control application of a portable information terminal according to a third embodiment. [Figure 42B] FIG. 11 is a screen display diagram of a basic screen of a cooperative control application of a portable information terminal according to a third embodiment. [Figure 43A] FIG. 11 is a screen display diagram of a notification screen of a broadcast receiving device according to a third embodiment. [Figure 43B] FIG. 11 is a diagram showing a screen display of a broadcast cooperative application launcher of a broadcast receiving device according to a third embodiment. [Figure 44] FIG. 11 is a screen display diagram of a data broadcast screen of a broadcast receiving device according to a third embodiment. [Figure 45A] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a broadcast receiving device according to a third embodiment. [Figure 45B] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a broadcast receiving device according to a third embodiment. [Figure 45C] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a broadcast receiving device according to a third embodiment. [Figure 45D] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a broadcast receiving device according to a third embodiment. [Figure 46] FIG. 11 is a diagram showing an error display screen of a broadcast receiving device according to a third embodiment. [Figure 47] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a mobile information terminal according to a third embodiment. [Figure 48A] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 48B] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 48C] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 48D] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 48E] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 48F] FIG. 11 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to a third embodiment. [Figure 49A] FIG. 11 is an operational sequence diagram of a broadcast receiving device according to a third embodiment when acquiring a broadcast cooperative application. [Figure 49B] FIG. 11 is an operational sequence diagram when a mobile information terminal according to a third embodiment acquires a broadcast cooperative application. [Figure 50] FIG. 10 is a diagram illustrating the data structure of an MH-application descriptor. [Figure 51A] FIG. 10 is an operational sequence diagram when terminals cooperate with each other according to the fourth embodiment. [Figure 51B] FIG. 13 is an operational sequence diagram when terminals cooperate with each other according to the fifth embodiment. [Figure 51C] FIG. 20 is an operational sequence diagram when terminals cooperate with each other according to the sixth embodiment. [Figure 51D] FIG. 20 is an operational sequence diagram when terminals cooperate with each other according to the sixth embodiment. [Figure 52A] FIG. 13 is a diagram showing a screen display of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52B] FIG. 13 is a diagram showing a screen display of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52C] FIG. 13 is a diagram showing a screen display of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52D]FIG. 13 is a diagram showing a screen display of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52E] FIG. 13 is a diagram showing a screen display of a broadcast receiving device according to a seventh embodiment. [Figure 52F] FIG. 13 is a diagram showing a screen display of a broadcast cooperative application on a mobile information terminal according to a seventh embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] Example 1 [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 and an antenna 100a, a broadband network such as the Internet 200, a router device 200r and an access point 200a, a broadcast station radio tower 300t and 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 and a base station 600b of a mobile telephone communication network, and a mobile information terminal 700.

[0011] Broadcast receiving device 100 receives broadcast waves transmitted from radio tower 300t via broadcast satellite (or communication satellite) 300s and antenna 100a. Alternatively, broadcast waves transmitted from radio tower 300t may be received directly from antenna 100a without going through broadcast satellite (or communication satellite) 300s. Broadcast receiving device 100 can also be connected to Internet 200 via router device 200r, and can transmit and receive data via communication with each server device and other communication devices on 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 also 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] Mobile telephone communication server 600 is connected to Internet 200, and is also connected to mobile information terminal 700 via base station 600b. Mobile telephone communication server 600 manages telephone communication (calls) and data transmission / reception of mobile information terminal 700 via the mobile telephone communication network, and enables transmission / reception of data between mobile information terminal 700 and each server device and other communication devices on Internet 200. Communication between base station 600b and mobile information terminal 700 may be performed using W-CDMA (Wideband Code Division Multiple Access) (registered trademark) system, GSM (Global System for Mobile communications) (registered trademark) system, LTE (Long Term Evolution) system, or other communication system.

[0017] The mobile information terminal 700 is assumed to have the functions of telephone communication (calls) and data transmission / reception via a mobile telephone communication network, as well as the function of 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] An example of an outline of an encoded signal in MMT of this embodiment is shown in Figure 2A. As shown in the figure, MMT of this embodiment has MFU (Media Fragment Unit), MPU (Media Processing Unit), MMTP (MMT Protocol) payload, and MMTP packet as elements that make up the encoded signal.

[0021] An MFU is a transmission format for video, audio, etc., and may be configured in NAL (Network Abstraction Layer) units or access units. An MPU includes one or more access units and is capable of decoding video and audio on its own. An 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. A single MPU may contain multiple movie fragment data and sample data. Furthermore, it is assumed that an MFU can be extracted from the sample data. Figure 2B shows an example of an MPU configuration. By assigning a sequence number to each MPU belonging to the same asset, it is assumed that any MPU can be distinguished from other MPUs by the asset ID that identifies the asset and the MPU sequence number. Furthermore, for media such as video components and audio components, the presentation time and decoding time may be specified on an MPU or access unit basis.

[0022] 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 and 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 of the same type 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.

[0023] 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. Encoded data such as video and audio of broadcast programs 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 broadcast programs 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: (1) a subtitle / superimposed text transmission method used for streaming data synchronized with broadcasting; (2) an application transmission method used for data transmission services asynchronous with broadcasting; (3) an event message transmission method used for synchronous / asynchronous message notifications from broadcasting stations to applications running on television receivers; and (4) a general-purpose data transmission method for transmitting other general-purpose data synchronously / asynchronously.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] [Control information for broadcasting systems using MMT] In the broadcast system to which the broadcast receiver 100 of this embodiment corresponds, 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 configuration of the control information used in the broadcast system of this embodiment is shown in FIG. 4.

[0028] FIG. 5A shows a list of the "tables" used in the TLV-SI of the broadcast system to which the broadcast receiver 100 of this embodiment corresponds. In this embodiment, the following are used as the "tables" of TLV-SI.

[0029] (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.

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

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

[0032] <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.

[0033] (1) Service list descriptor The service list descriptor provides a list of services based on service identification and service format type.

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

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

[0036] (4) Network name descriptor The network name descriptor describes the network name with character codes.

[0037] (5) Remote control key descriptor The remote control key descriptor is used to set the service assigned to the one-touch channel selection button of the receiver remote control.

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

[0039] <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.

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

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

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

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

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

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

[0046] <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 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.

[0047] (1) MPT The MMT Package Table (MPT) provides information that configures a package, such as a list of assets and their locations on the network. The MPT can be stored in a PA message.

[0048] (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.

[0049] (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.

[0050] (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.

[0051] (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.

[0052] (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.

[0053] (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.

[0054] (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.

[0055] (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.

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

[0057] (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.

[0058] (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.

[0059] (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.

[0060] (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.

[0061] (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.

[0062] (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.

[0063] (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.

[0064] (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 data transmission messages.

[0065] (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.

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

[0067] <Descriptors used in MMT-SI> Figures 6C, 6D, and 6E show a list of "descriptors" arranged in the MMT-SI of the broadcast system corresponding to the broadcast receiver 100 of this embodiment. 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.

[0068] (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.

[0069] (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.

[0070] (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.

[0071] (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.

[0072] (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.

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

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

[0075] (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).

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

[0077] (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.

[0078] (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.

[0079] (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 coding method specific settings. The MH-MPEG-4 Audio Extension Descriptor can be placed in the MPT.

[0080] (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.

[0081] (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.

[0082] (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.

[0083] (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.

[0084] (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.

[0085] (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.

[0086] (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.

[0087] (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.

[0088] (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.

[0089] (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.

[0090] (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 may be placed in the MPT or the MH-EIT.

[0091] (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.

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

[0093] (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.

[0094] (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.

[0095] (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.

[0096] (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.

[0097] (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).

[0098] (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.

[0099] (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.

[0100] (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.

[0101] (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.

[0102] (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.

[0103] (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.

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

[0105] (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.

[0106] (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.

[0107] (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.

[0108] (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.

[0109] (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.

[0110] (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.

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

[0112] (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.

[0113] (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.

[0114] (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.

[0115] (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.

[0116] (49)MH-Cache Information Descriptor The MH-cache information descriptor is written to be used for 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.

[0117] (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.

[0118] (51) Link Destination 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.

[0119] (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.

[0120] (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.

[0121] (54)MH-Download Protection Descriptor The MH-Download Protection Descriptor describes the location and transmission information of the MMTP packet that carries the DCM or DMM. The MH-Download Protection Descriptor may be placed in the MPT or MH-SDTT.

[0122] (55) Application Service Descriptor The application service descriptor describes entry information of the application related to the service, etc. The application service descriptor may be placed in the MPT.

[0123] (56) MPU Node Descriptor The MPU node descriptor indicates that the MPU corresponds to a directory node defined in the data directory management table. The MPU node descriptor may be located in the DAM table.

[0124] (57) PU Configuration Descriptor The PU configuration descriptor indicates a list of MPUs that configure a presentation unit as mapping information between the presentation unit and the transmission unit. The PU configuration descriptor may be arranged in the DCC table.

[0125] (58)MH-layer encoding descriptor The MH-Hierarchical Coding Descriptor describes information for identifying a hierarchically coded video stream component. The MH-Hierarchical Coding Descriptor may be placed in the MPT.

[0126] (59) Content Copy Control Descriptor The content copy control descriptor indicates information for controlling the copy generation in a digital recording device for the entire service, and is used by the broadcasting station (copyright holder) to convey copy-related information or the maximum transmission rate to a digital recording device when digital recording is expected. The content copy control descriptor may be placed in the MPT, MH-EIT, MH-SDT, etc.

[0127] (60) Content Usage Control Descriptor The content usage control descriptor is used to indicate information regarding copy control and remote viewing control when the program is stored in a hard disk or the like, or when a video / audio signal is output from a receiver. The content usage control descriptor may be arranged in MPT, MH-EIT, MH-SDT, etc.

[0128] (61) Descriptor Set by a Service Provider In addition, it is possible to prepare descriptors independently set by service providers and the like.

[0129] <Relationship between Data Transmission and Each Control Information in the MMT System> Here, with reference to FIG. 7A, the relationship between each component such as video and audio transmitted by the broadcast system corresponding to the broadcast receiver 100 of this embodiment and representative tables of MMT-SI will be described. In the MMT system, a component is defined as an asset, and hereinafter, a component may be referred to as an asset in some cases.

[0130] In the broadcast system corresponding to the broadcast receiver 100 of this embodiment, data transmission can be performed through a plurality of paths such as a TLV stream via a broadcast transmission path and 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.

[0131] These various assets are associated with a "package" by the description in the MPT (MMT Package Table) stored in the PA message and transmitted. Specifically, the association can be achieved by describing in the MPT a package ID that identifies the package and an asset ID that identifies each asset included in the package. Figure 7B shows an example of the data structure of the MPT. In the figure, the "MMT_package_id_byte" parameter corresponds to the package ID, and the "asset_id_byte" parameter corresponds to the asset ID.

[0132] The assets constituting a package can be only assets in a TLV stream, but as shown in Figure 7A, they can also include assets transmitted via IP data flows on communication lines. This can be achieved by describing the location information of each asset contained in the package together with an asset ID that identifies the asset in the MPT, allowing the broadcast receiving device 100 of this embodiment to grasp the reference destination of each asset. The location information is specified by "MMT_general_location_info()" in the data structure of the MPT shown in Figure 7B. Figure 7C shows an example of the data structure of location information.

[0133] Depending on the value of the "location_type" parameter of 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.

[0134] Of the above-mentioned references, (1) is, for example, an IP data flow included in the TLV stream of the digital broadcast signal received by the broadcast receiving device 100 of this embodiment via the antenna 100a. However, if the MPT is also transmitted as part of the IP data flow on the communication line, the reference of (1) may be the IP data flow received via the communication line. Furthermore, (2), (3), (5), and (6) are IP data flows received by the broadcast receiving device 100 of this embodiment via the communication line. Furthermore, (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 a second embodiment 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 location information in the MPT included in the digital broadcast signals using the MMT system.

[0135] Furthermore, for media such as video components and audio components, presentation times and decoding times can be specified on an MPU or access unit basis. Information regarding the presentation times and decoding times is described in the MPT as an MPU timestamp descriptor or an MPU extended timestamp descriptor. Figure 7D shows an example of the data structure of an MPU timestamp descriptor describing information regarding the presentation times. The presentation time information for each MPU is specified by the "mpu_presentation_time" parameter of the MPU timestamp descriptor. The MPU to be specified can be identified by the "mpu_sequence_number" parameter. Using this presentation time information, the broadcast receiving device 100 of this embodiment can present (display, output, etc.) multiple MPUs specified by the MPT in a synchronized manner based on an NTP-based clock, which is time information in UTC notation. Information regarding the decoding time is also similarly described by an MPU extended timestamp descriptor, but a detailed description thereof will be omitted. Control of the presentation of various data using the NTP-based clock will be described later.

[0136] In the broadcasting system of this embodiment, a series of data in units of "packages" corresponds to a "service" in digital broadcasting. Furthermore, the "service" is a series of "programs" transmitted according to a schedule. In the MMT system, the "programs" are treated as "events." The start time and duration of each event are specified by the MH-EIT. Furthermore, the event package descriptor placed in the MH-EIT specifies the ID of the MMT package to which each event corresponds. Figure 7E shows an example of the data structure of the MH-EIT. The "start_time" parameter in the figure specifies the start time, and the "duration" parameter specifies the duration. Figure 7F shows an example of the data structure of an event package descriptor. The "MMT_package_id_byte" parameter of the event package descriptor placed in the MH-EIT allows the correspondence between each event and an MMT package to be specified. The MH-EIT can be used for various processes in units of "events" in the broadcast receiving device 100 of this embodiment (for example, generating an electronic program guide, controlling recording and viewing reservations, and copyright management processes such as temporary storage).

[0137] [Broadcast receiving device hardware configuration] 8A 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.

[0138] 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.

[0139] 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. 8A, but may use a partial storage area within the storage (accumulation) unit 110.

[0140] 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.

[0141] 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 .

[0142] 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.

[0143] 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, although the example shown in FIG. 8A 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.

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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. 8B 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.

[0150] 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.

[0151] 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.

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

[0153] 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.

[0154] 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.

[0155] 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, the audio output unit 166, or the digital interface unit 125 enables operation similar to that of the broadcast receiving device 100 of this embodiment.

[0156] [Software configuration of broadcast receiving device] 8C 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 reception function program 1002, a linkage function program 1003, a recording / playback function program 1004, 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.

[0157] A basic operation program 1001 stored in ROM 103 is loaded into RAM 104, and the main control unit 101 executes the loaded basic operation program 1001 to form a basic operation execution unit 1101. Similarly, a reception function program 1002, a linkage function program 1003, and a recording / playback function program 1004 stored in the storage unit 110 are loaded into RAM 104, and the main control unit 101 executes the loaded reception function program 1002, linkage function program 1003, and recording / playback function program 1004 to form a reception function execution unit 1102, linkage function execution unit 1103, and recording / playback function execution unit 1104. The RAM 104 also includes a temporary storage area for temporarily storing data created when each operation program is executed, as needed.

[0158] 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.

[0159] 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.

[0160] Furthermore, the linkage function execution unit 1103 manages device authentication and connection, transmission and reception of various data, etc., when the broadcast receiving device 100 performs linkage operation with an external device such as the mobile information terminal 700. The recording / playback function execution unit 1104 controls the recording of broadcast programs acquired from digital broadcast waves of this broadcast system and content acquired from each server device on the network in the content storage area 1200 of the storage (accumulation) unit 110 or in external storage connected to the expansion interface unit 124, or the playback of the broadcast programs, content, etc.

[0161] 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 on a memory card, an optical disk, or the like and acquired via the expansion interface unit 124 or the like.

[0162] [Broadcasting station server configuration] 9 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.

[0163] 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.

[0164] 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.

[0165] 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.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] [Service provider server configuration] 10 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.

[0171] 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.

[0172] 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 (such as personal information and authentication information) related to users who are permitted to access the service provider server 400.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] 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.

[0177] [Hardware configuration of mobile information terminal] 11A 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.

[0178] 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.

[0179] ROM 703 is a 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 or flash ROM. RAM 704 serves as a work area when the basic operation programs and other operation programs are executed. ROM 703 and RAM 704 may be integrated with main control unit 701. ROM 703 may also use a partial storage area within storage unit 710, rather than being an independent configuration as shown in FIG. 11A.

[0180] The storage unit 710 stores the operating 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 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 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.

[0181] 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 .

[0182] 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 transmits and receives data 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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.

[0188] 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 any other portable digital device.

[0189] 11A 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.

[0190] [Software configuration of mobile information terminal] 11B 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 the television receiver or each server device, and various information storage areas that store various other information.

[0191] 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.

[0192] 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.

[0193] The cooperative control execution unit 7102 manages device authentication and connection, transmission and reception of data, etc. when the mobile information terminal 700 operates cooperatively 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.

[0194] The operation programs may be stored in the ROM 703 and / or the storage unit 710 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 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.

[0195] [Time management for broadcast receiving devices] The broadcast receiver 100 of this embodiment has two types of time management functions. The first time management function is a time management function based on NTP, and the second time management function is a time management function based on MH-TOT. Hereinafter, the two types of time management functions will be described.

[0196] <Time management function based on NTP> First, the time management function based on NTP will be described.

[0197] FIG. 12A is an example of a system configuration for clock synchronization / presentation synchronization in a broadcast system to which the broadcast receiver 100 of this embodiment corresponds. In the broadcast system of this embodiment, UTC is transmitted from the broadcast transmission system to a receiver (such as the broadcast receiver 100 of this embodiment) in the form of a 64-bit NTP timestamp. In the NTP timestamp format, the "seconds and above" of UTC are represented by 32 bits, and the "less than seconds" are represented by 32 bits. However, in practice, it is difficult to reproduce 1 second with 32-bit accuracy. Therefore, as the system clock for synchronizing the video system or for operating the system clock of the NTP format clock, for example, a frequency of '2 to the 24th power' Hz (about 16.8 MHz) as shown in the figure may be used. Considering that the system clock in the conventional broadcast system was 27 MHz and that the hardware configuration of the receiver can be easily constructed, it is desirable to adopt a power-of-two frequency of about '2 to the 24th power' to '2 to the 28th power' as the system clock.

[0198] 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 lower 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. 12A, and the same applies below), the lower "32-n" bits of the NTP timestamp format may be fixed to "0" or "1." Alternatively, the receiver side may process the lower "32-n" bits of the NTP timestamp format to be ignored.

[0199] 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 2 to the nth power VCO (Voltage Controlled Oscillator) to create a transmission system clock synchronized with the externally provided time information. The entire signal processing system operates in synchronization with the 2 to the nth power VCO system clock. Furthermore, the output of the transmission system clock is periodically transmitted to the receiver via the broadcast transmission path as NTP-long formatted time information. The NTP-long formatted time information transmitted to the receiver may also have the lower 32-n bits of the 32 bits representing "fractions of a second" fixed to "0" or "1." This is because the system clock counter on the broadcast transmission system side is composed of 32+n bits.

[0200] On the receiver side, time information in NTP length format is received via the broadcast transmission path, and the receiving system clock is regenerated using a PLL system based on a 2n Hz VCO, just like on the broadcast transmission system side. This makes the receiving system clock synchronized with the broadcast transmission system side. In addition, by operating the receiver's signal processing system in synchronization with the 2n Hz system clock, clock synchronization between the broadcast transmission system side and the receiver side is achieved, enabling stable signal reproduction.

[0201] Also, the decoding time and presentation time for each presentation unit of the video / audio signal are set on the broadcast transmission system side based on the NTP-formatted time information. The decoding time is specified by an MPU extended timestamp descriptor (not shown) stored in the MPT. Also, the presentation time is specified by an MPU timestamp descriptor (see FIG. 7D) stored in the MPT. The'mpu_sequence_number (MPU sequence number)' parameter in the MPU timestamp descriptor indicates the sequence number of the MPU that describes the timestamp, and the'mpu_presentation_time (MPU presentation time)' parameter indicates the presentation time of the MPU in the 64-bit NTP timestamp format. That is, the receiver can control the presentation (display, output, etc.) timing for each MPU of the video / audio signal, subtitles, character super, etc. by referring to the MPU timestamp descriptor stored in the MPT.

[0202] Note that when focusing on the control of the decoding timing and presentation timing for each presentation unit of the above-described video / audio signal, etc., synchronization of the video / audio signal can be ensured even with a clock of about '2 to the 16th power' Hz (about 65.5 KHz). In this case, the lower ighteen bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. do not need to be referred to. That is, when using a clock of '2 to the mth power' Hz generated by frequency division of the system clock or the like for control of the decoding timing and presentation timing, the lower '32 - m' bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. do not need to be referred to. 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'.

[0203] <Time management function based on MH-TOT> An example of the structure of time information transmitted in NTP format in the NTP-based time management function described above is shown in Figure 12B. The "reference_timestamp" parameter and "transmit_timestamp" parameter in the NTP format are 64-bit time data in the NTP long format. The "mpu_presentation_time" parameter in the MPU timestamp descriptor shown in Figure 7D is also 64-bit time data in the NTP timestamp format. The NTP long format time data and the NTP timestamp format time data represent UTC seconds or more with 32 bits and UTC seconds less than a second with 32 bits. In other words, NTP format time information can transmit time information up to the "second." Furthermore, because the NTP format time information is expressed in UTC, unlike time management in conventional digital broadcasting, by managing both the data flow transmitted via the broadcast transmission path and the data flow distributed via the communication line with the NTP format time information, as shown in Figure 3, it is possible to easily ensure consistency between the two sets of data.

[0204] In contrast, the time information transmitted by MH-TOT is as follows:

[0205] An example of the data structure of the MH-TOT is shown in Figure 12C. The broadcast receiving device 100 of this embodiment can obtain the current date and time from the "JST_time" parameter of the MH-TOT. As shown in Figure 12D, 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. In addition, of the six 4-bit binary coded decimal numbers, the first 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.

[0206] In other words, the difference between time management based on the NTP format and time management based on the MH-TOT format is that the former, NTP format, can transmit time information down to the "second" as mentioned above, while the latter, MH-TOT format, can only transmit time information down to the "second" in JST notation.

[0207] 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 received by the broadcast signal with the video, audio, subtitles, superimposed text, or other data obtained via the communication line path.

[0208] Furthermore, in the broadcast receiving device 100 of this embodiment, 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, may be used in the process of presenting the current time to a user or in the processes handling the MH-EIT shown in FIG. 7E. Generally, the process of presenting the current time to a user in a broadcast receiving device rarely requires precision down to the second. Furthermore, the time information described in the MH-EIT is 24-bit information expressed as six 4-bit binary-coded decimal numbers, stored in two decimal digits for "hour," "minute," and "second," similar to the EIT of conventional digital broadcasts transmitted using the MPEG2-TS format. For this reason, the time management function based on the MH-TOT in the broadcast receiving device 100 of this embodiment is easily compatible with the processes handling the MH-EIT. Specifically, the processes handling the MH-EIT include, for example, the generation of an electronic program guide, 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.

[0209] Furthermore, the generation process of the electronic program guide, the 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 process of the electronic program guide, the 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 format digital broadcasting systems, when configuring a broadcast receiving device that has both the reception function for conventional MPEG2-TS format digital broadcasting and the reception function for MMT format digital broadcasting, it will no longer be necessary to design separate processing algorithms for these processes (the generation process of the electronic program guide, the control of recording reservations and viewing reservations, copyright management processes such as temporary storage, etc.), thereby enabling costs to be reduced.

[0210] 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 an electronic program guide, controlling recording and viewing reservations, and copyright management processes such as temporary storage.

[0211] Therefore, by configuring the time management function based on the MH-TOT "JST_time" parameter to be used for these processes (processing such as generating an electronic program guide, 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.

[0212] 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 degrees of accuracy. That is, the first time information is time information written in a format consistent with conventional digital broadcasting systems, and the second time information is time information with higher resolution than the first time information. By using the second time information for synchronization processing of each content data in the broadcast signal, more advanced information presentation processing than conventional broadcasting systems is realized, and by using the first time information for generating an electronic program guide, controlling recording and viewing reservations, and copyright management processing such as temporary storage, broadcast receiving devices can be provided at low cost.

[0213] 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.

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

[0215] 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 12A, 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.

[0216] 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 of the protocol stack in the broadcast transmission path 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 means that the broadcast receiving device 100 can acquire information that is less susceptible to delays caused by 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. 12E. 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 shown in FIG. 12E, 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.

[0217] 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 (for example, the aforementioned ``delta'' parameter and / or ``transmit_timestamp'' parameter) described in the time information stored in the TMCC extended information area and transmitted.

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

[0219] As mentioned 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 mentioned above, the MH-TOT has the data structure shown in Fig. 12C, and the broadcast receiving device 100 can acquire the current date and current time from the "JST_time" parameter of the MH-TOT.

[0220] 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.

[0221] FIG. 12F 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.

[0222] 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. 12C 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. 12F 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.

[0223] 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 configuration shown in Figure 12B. Furthermore, the MPU timestamp descriptor has the configuration shown in Figure 7D.

[0224] 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.

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

[0226] [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.

[0227] 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, a list of services acquired from the TLV-NIT can be stored in a nonvolatile memory such as the ROM 103 or the storage unit 110, and further, a list of IP multicast groups corresponding to each of the services can be stored in the nonvolatile memory as IP-related information in association with each of the services. 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 broadcast content can be acquired efficiently.

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

[0229] 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).

[0230] 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. 13B shows an example of the data structure of the 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).

[0231] Figure 13C shows an example of the data structure of a satellite distribution system descriptor. Figure 13D shows an example of the data structure of a service list descriptor. If the TLV-NIT has multiple different pieces of data, such as a TLV stream ID, an original network ID, distribution system information, and a list of service IDs, the processes of S105 to S107 are repeated. Next, the reception function execution unit 1102 creates a service list based on the data, such as the TLV stream ID, the original network ID, distribution system information, and the list of service IDs, acquired in the processes of S105 to S107, and stores the created service list in the ROM 103 or the storage unit 110 (updated when rescanning) (S108).

[0232] 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. 13E. 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 or the storage unit 110 (updates it when rescanning) (S111).

[0233] 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.

[0234] 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.

[0235] 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.

[0236] The rescan for the setting change may be performed automatically when a change in the information in the table is detected by referencing 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 related to 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.

[0237] [Broadcast receiving device tuning process (channel switching)] FIG. 14A 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.

[0238] When a user operates a remote control (not shown) or the like 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 unit 1100 may always refer to IP-related information stored in the ROM 103 or the storage unit 110.

[0239] 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.

[0240] 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.

[0241] In the demultiplexer 132, the transport processor 1102a acquires an MMTP packet with a packet ID of "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 Figure 7B, 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 with a packet ID of "0" is an MMTP packet containing data of a program corresponding to the service ID, and proceeds to MFU acquisition processing based on the information in the acquired MPT.

[0242] 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 sequence (S214) and acquires the MPT contained in the acquired MMTP packet (S215). Furthermore, the transport processing unit 1102a starts the MFU acquisition process based on the information contained in the acquired MPT.

[0243] 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".

[0244] Here, we will explain the process of identifying the packet ID of an MMTP packet containing program data corresponding to the service ID by checking the PLT, and obtaining the MPT. An MMTP packet with a packet ID of "0" indicates that it transmits a PA message. When multiple packages are multiplexed, this PA message contains a PLT (Package List Table), as shown in Figure 14B. The PLT contains a list of packet IDs of MMTP packets that transmit PA messages containing MPTs of other packages. By checking the PLT, it is possible to identify, from the package ID, the MMTP packet that transmits the PA message containing the MPT that is the entry point for each service. Figure 14C shows an example of the data structure of the PLT. The location information for transmitting the PA message of the package indicated by the "MMT_package_id_byte" parameter is specified by "MMT_general_location_info()."

[0245] Returning to the description of the operational sequence shown in Figure 14A, in the MFU acquisition process, first, the transport processing unit 1102a references the MPT acquired in the process of S210 or S215 and acquires the IP address and packet ID of the IP data flow that transmits the desired MFU (S216). The transport processing unit 1102a also acquires the MPU presentation time from the MPU timestamp descriptor placed in the MPT and the MPU layout number from the MPU presentation area designation descriptor placed in the MPT (S217, S218), and further acquires the MFU based on the IP address and packet ID of the acquired IP data flow (S219). Next, encoded video data and encoded audio data, etc. are extracted from the acquired MFU, and video / audio decoding processing is performed under the control of the AV decoding processing unit 1102b. Then, presentation processing is performed under the control of the presentation processing unit 1102h based on the acquired information related to the presentation time and information related to layout control (S220).

[0246] If a PLT cannot be acquired in the process of S212, if the "MMT_package_id_byte" parameter matching the service ID cannot be confirmed in the process of S213, if an MMTP packet with a packet ID of "x" cannot be acquired in the process of S215, etc., program image output processing based on the data of the MMTP packet with a packet ID of "0" acquired in the process of S210 (i.e., the processes of S216 to S220) may be performed. In these cases, it is preferable to display a message indicating that the program corresponding to the service ID selected by the user could not be displayed.

[0247] Through 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 13A and 14A, when a channel scan is performed during initial setup or when a rescan is performed to change the 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), the time from the start of channel selection (switching a channel) to the end of channel selection (switching a channel) can be shortened.

[0248] [Broadcast receiver remote control key setting process] 15A shows an example of the appearance of a remote control (remote controller) 100R used to input operation instructions to the broadcast receiving device 100 of this embodiment. The remote control 100R includes at least a power key 100R1, a numeric keypad 100R2, channel up / down keys 100R3, a menu key 100R4, an EPG key 100R5, cursor keys 100R6, an enter key 100R7, and color keys 100R8. The remote control 100R may further include volume up / down keys, a network switching key, an input switching key, a record key, a play key, etc.

[0249] For example, in the process of S201 of the operational sequence for channel selection shown in FIG. 14A, when instructing the broadcast receiving device 100 of this embodiment to change channels using the remote control 100R, the following three methods may be used. The first method is to directly input and specify the service ID of the desired channel (service) by pressing the numeric keypad 100R2 multiple times. The second method is to repeatedly press the channel up / down key 100R3 as necessary to advance (or reverse) through the channels until the desired channel (service) is displayed. The third method is a so-called one-touch channel selection method in which a predetermined channel (service) associated with each key on the numeric keypad 100R2 is called up by pressing the numeric keypad 100R2 only once. The third one-touch channel selection method is a user-friendly channel selection method, but it requires that the broadcast receiving device 100 be previously configured to associate each key on the numeric keypad 100R2 with a predetermined channel (service).

[0250] The broadcast receiving device 100 corresponding to the broadcasting system of this embodiment is capable of automatically setting the association based on control information included in the digital broadcasting wave received by the tuner / demodulator 131. That is, the broadcasting system of this embodiment provides a remote control key descriptor as a TLV-SI descriptor. The association can be set by referring to the remote control key descriptor.

[0251] Figure 15B shows an example of the data structure of a remote control key descriptor. The "service_id" parameter in the figure is a service ID that identifies a channel (service). The "remote_control_key_id" parameter is a recommended value for the remote control button number to which the channel (service) identified by the service ID is assigned. Depending on the values ​​of the above parameters, the channel (service) identified by the "service_id" parameter can be associated with the key specified by the value of the "remote_control_key_id" parameter on numeric keypad 100R2.

[0252] If there are many channels (services) in the same network, the channels (services) may be assigned to keys other than the numeric keypad 100R2. For example, a specific channel (service) may be assigned to the color keypad 100R8. In this case, a numeric value corresponding to the "remote_control_key_id" parameter may be assigned in advance to each key on the color keypad 100R8.

[0253] The remote control key descriptor may be described as a TLV-NIT descriptor. Therefore, for example, if the TLV-NIT acquired in the process of S103 of the operational sequence during channel scanning shown in Fig. 13A is valid data, the description content of the remote control key descriptor may be stored in a non-volatile memory such as ROM 103 or storage unit 110 of broadcast receiving device 100 in conjunction with the processes of S105 to S107, thereby setting the association.

[0254] In addition to the method of setting the associations according to the contents of the remote control key descriptor as described above, the user may also assign any channel service to each key of the numeric keypad 100R2 according to his or her own preference. Furthermore, both the association settings according to the contents of the remote control key descriptor and the association settings assigned according to the user's preference may be simultaneously stored in the non-volatile memory of the broadcast receiving device 100, and only one of the settings may be used by selecting it through a menu operation or the like. In this case, the association settings assigned according to the user's preference may be used preferentially. Furthermore, the association settings according to the contents of the remote control key descriptor may be used preferentially over the association settings assigned according to the user's preference according to the value of a priority flag described in the remote control key descriptor. The priority flag may be set by using part or all of the "reserved" parameter of the remote control key descriptor shown in FIG. 15B, or by adding a new parameter. In this case, the value of the priority flag may be controllable for each service ID.

[0255] Also, when the non-volatile memory stores the association settings assigned by the user according to their preferences, the association settings according to the description contents of the remote control key descriptor may not be stored in the non-volatile memory.Also, the non-volatile memory of the broadcast receiving device 100 may store only the association settings assigned by the user according to their preferences, and when a remote control key descriptor is described in the TLV-NIT being received, the association settings according to the description contents of the remote control key descriptor may be used, and when a remote control key descriptor is not described in the TLV-NIT being received, the association settings assigned by the user according to their preferences may be used.

[0256] The process of associating each key of the numeric keypad 100R2 with a specific channel (service) according to the contents of the remote control key descriptor may be performed simultaneously for all services described in the service list descriptor in the network specified by the TLV-NIT, or may be performed only for some of the services. When the process is performed only for some of the services, the previous settings for the other services may be retained as they are. Furthermore, when the "service_id" parameter is a specific value (e.g., 999), only the settings specified by the "remote_control_key_id" parameter may be erased from the settings stored in the non-volatile memory of the broadcast receiving device 100.

[0257] That is, in the broadcast receiving device 100 of this embodiment, it is possible to set association of each key of the numeric keypad 100R2 with a predetermined channel (service).

[0258] [Multi-channel selection processing] The broadcasting system of this embodiment also allows for multi-channel broadcasting, in which multiple programs are broadcast in parallel on one channel (service). When multiple programs are broadcast simultaneously using multi-channel broadcasting, the one-touch channel selection described above is only possible for the main channel of the multi-channel broadcasting, but not for the sub-channels of the multi-channel broadcasting. In other words, when selecting a sub-channel of the multi-channel broadcasting, it is necessary to either directly input and specify the service ID, or to first select the main channel of the multi-channel broadcasting using one-touch channel selection, and then select the desired sub-channel by pressing the channel up / down key 100R3, which results in a problem of cumbersome operations.

[0259] In order to solve the above problem, in the broadcast receiving device 100 of this embodiment, the one-touch channel selection function is expanded, and it is possible to directly select a multi-channel sub-channel by repeatedly pressing the numeric keypad 100R2, to which a predetermined service ID is assigned, multiple times within a predetermined time.

[0260] This will be explained using FIG. 16A. For example, assume that the service for channel 011 is pre-assigned to the "1" key on the numeric keypad 100R2 of the remote controller 100R. In this case, if a channel selection operation is performed when multi-programming is not being performed (see (A) in the figure), channel 011 is selected regardless of the number of times the "1" key is pressed. On the other hand, if a channel selection operation is performed when multi-programming is being performed (see (B) in the figure), channel 011 is selected when the "1" key is pressed only once, and channel 012 is selected when the "1" key is pressed again within a predetermined time after the first press of the "1" key. Similarly, channel 013 is selected when the "1" key is pressed three times within a predetermined time. Note that if the "1" key is pressed again after a predetermined time has elapsed since the first press of the "1" key, channel 011 may remain selected.

[0261] By enabling the above-described operations, the broadcast receiving device 100 of this embodiment allows direct selection of a sub-channel in a multi-programming situation with a simpler operation.

[0262] Similarly, angle selection for a multi-view compatible program or selection of a specific video asset from multiple video assets may be performed by repeatedly pressing the numeric keypad 100R2 multiple times. As shown in FIG. 16B , if the service ID of a multi-view compatible program is assigned to the “1” key on the numeric keypad 100R2 of the remote control 100R, pressing the “1” key once selects the multi-view compatible program and displays the main view. Pressing the “1” key again within a predetermined time after the first press of the “1” key displays subview 1 of the multi-view compatible program. Similarly, pressing the “1” key three times within a predetermined time displays subview 2 of the multi-view compatible program. Pressing the “1” key again after a predetermined time has elapsed since the first press of the “1” key may leave the main view of the multi-view compatible program displayed. Selection of a specific video asset from multiple video assets may also be performed using the same operations as described above.

[0263] By enabling the above-described operations, the broadcast receiving device 100 of this embodiment allows angle selection for a multi-view compatible program and selection of a specific video asset from multiple video assets with simpler operations.

[0264] In addition, if one or more programs in a multi-format system are multi-view compatible programs or programs with multiple assets, only one of the above operations can be enabled and the other can be disabled. For example, if one or more programs in a multi-format system are multi-view compatible programs or programs with multiple assets, pressing the same key multiple times within a predetermined time can be assigned to processing for direct selection of sub-channels in a multi-format system. Which operations are enabled and which are disabled can be determined in advance, or can be selected by the user.

[0265] [Screen layout control for broadcast receiving devices] In the broadcast receiving device 100 of this embodiment, it is assumed that screen layout control based on the description of the LCT is possible. An example of the data structure of the LCT is shown in Fig. 17A. An example of the data structure of the MPU presentation area specification descriptor is shown in Fig. 17B.

[0266] In the data structure of the LCT, 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, when the left side of the full-screen display is "0" and the right side is "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, when the top side of the full-screen display is "0" and the bottom side is "100". The "layer_order" parameter indicates the relative position of the region in the depth direction.

[0267] An example of assigning layouts to layout numbers based on the settings of each of the parameters will be described below, along with the setting values ​​of each of the parameters.

[0268] FIG. 17C 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. 17D 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).

[0269] Fig. 17E is an example of setting three regions, similar to Fig. 17D, 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 above, according to the setting of the "layer_order" parameter. Fig. 17F is 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).

[0270] 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.

[0271] In addition, in areas where program video or data screens are not displayed due to the above-mentioned screen layout control, a predetermined background color specified by a background color specification descriptor described in the LCT may be displayed. Furthermore, if the background color specification descriptor is not included in the LCT, if the broadcast receiving device 100 is unable to correctly acquire the background color specification descriptor, or if the predetermined background color specified by the background color specification descriptor cannot be displayed due to hardware limitations, the video display device 100 may display a predetermined pattern in the area. Furthermore, the area may be used as an area for displaying notifications from the video display device 100 to the user. The notifications may be any information.

[0272] Note that any fractional parts that appear when dividing the screen according to the set 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 screen pixel count 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, 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.

[0273] Alternatively, the setting values ​​of the parameters such as "left_top_pos_x" may be limited to only "multiples of 5" or "multiples of 10" in the range from "0" to "100." In this case, the area setting can also be performed appropriately.

[0274] The content to be displayed in each area is specified by the MPU presentation area specification descriptor shown in Figure 17B. The MPU content, whose sequence number is specified by the "mpu_sequence_number" parameter in the figure, is associated with the description of the LCT by the "layout_number" and "region_number" parameters.

[0275] Alternatively, in the first 'for' loop of the MPU presentation area specification descriptor, multiple 'layout_number' and 'region_number' parameters may be described for one 'mpu_sequence_number' parameter, allowing the user to select which of these parameters to use for layout control. For example, if the 'layout_number1', 'region_number1', 'layout_number2', and 'region_number2' parameters are described for a given 'mpu_sequence_number' parameter in the first 'for' loop, the user may be allowed to select whether the layout control of the MPU specified by the 'mpu_sequence_number' parameter should be performed based on the 'layout_number1' and 'region_number1' parameters or the 'layout_number2' and 'region_number2' parameters. This allows the user to perform layout control for video programs according to their preferences.

[0276] [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 18A shows an example of the operation of exceptional process of screen layout control based on the LCT.

[0277] 17D 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 Figure 17C is being performed) regardless of the description content of the LCT, as shown in Figure 18A(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.

[0278] 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 18A (B).

[0279] 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. 18B.

[0280] 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.

[0281] 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.

[0282] [Video signal aspect ratio conversion processing] Aspect ratios of video signals in television broadcasting services include "4:3" used in conventional SDTV, "16:9" used in recent HDTV, and "21:9" suitable for movie content. In the broadcasting system of this embodiment, information on the aspect ratio of the video signal may be described by a video component descriptor. FIG. 19A shows an example of the data structure of a video component descriptor. In the figure, the "video_aspect_ratio" parameter is information on the aspect ratio of the video signal. FIG. 19B shows an example of the meaning of the "video_aspect_ratio" parameter. Aspect ratios different from those shown in the figure may also be assigned.

[0283] On the other hand, the aspect ratio of the display unit of a television receiver capable of receiving the television broadcasting service (such as the broadcast receiving device 100 of this embodiment) is generally 16:9. That is, when video content with an aspect ratio of 4:3 or 21:9 is displayed on a general television receiver, aspect ratio conversion processing may be performed.

[0284] Whether or not to perform the aspect ratio conversion process can be determined by comparing the specifications of the monitor unit 162 of the broadcast receiving device 100 with the "video_aspect_ratio" parameter of the video component descriptor. For example, if the aspect ratio of the monitor unit 162 of the broadcast receiving device 100 is "16:9" (e.g., 3840 pixels horizontally by 2160 pixels vertically), the aspect ratio conversion process should not be performed if the value of the "video_aspect_ratio" parameter is "0," "2," or "3," and should be performed if the value is "1" or "5." Also, for example, if the aspect ratio of the monitor unit 162 of the broadcast receiving device 100 is "21:9" (5040 pixels horizontally x 2160 pixels vertically, etc.), aspect ratio conversion processing will not be performed if the value of the "video_aspect_ratio" parameter is "0" or "5", and aspect ratio conversion processing will be performed if the value is "1", "2", or "3".

[0285] 19C and 19D show an example of aspect ratio conversion processing when the aspect ratio of the monitor unit 162 of the broadcast receiving device 100 is 16:9 and the value of the "video_aspect_ratio" parameter is 5. When video content with an aspect ratio of 21:9 is displayed on the monitor unit 162 with an aspect ratio of 16:9, the aspect ratio may be converted to 16:9 by adding black bars above and below the 21:9 video content (display A in the figure). This allows the entire original video content to be displayed without distortion. Alternatively, only the center portion of the 21:9 video content may be cropped and displayed on the monitor unit 162 (display B in the figure). This allows the main portion of the original video content to be displayed enlarged. Alternatively, small black bars may be added above and below the 21:9 video content, and the center portion may be cropped further (display C in the figure). In this way, it is possible to display most of the original video content in a larger size. It is also possible to compress the left and right edges of video content with an aspect ratio of 21:9 to display the entire area (display D in the figure). In this way, it is possible to display the entire area of ​​the original video content in a larger size, and with the main part displayed without distortion. It is also possible to add small black bands to the top and bottom of video content with an aspect ratio of 21:9, and further compress the left and right edges to display the entire area (display E in the figure). In this way, it is possible to display the entire area of ​​the original video content in a larger size, and with less distortion on the left and right edges.

[0286] The way in which aspect ratio conversion is performed may be selectable by the user through settings such as a menu. Alternatively, it may be possible to switch by pressing a specific key on a remote control or the like. Note that the aspect ratio "21:9" mentioned above includes aspect ratios that are roughly "21:9", such as the so-called Cinemascope "2.35:1". The same applies to other aspect ratio values.

[0287] [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 the MH-EIT. The MH-EIT shown in Fig. 7E is distinguished 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.

[0288] FIG. 20A shows 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 IDs (channels), and displays detailed information about broadcast programs broadcast on each channel during each time period. The detailed information 162a1 for each broadcast program is primarily composed of a title area 162a2 and a detailed description area 162a3. The detailed information 162a1 for each broadcast program may display program information, etc., described in an MH-short event descriptor or an MH-extended event descriptor and distributed. If the volume of program information, etc., described in each descriptor is large, the information may be displayed in abbreviated form under normal circumstances, and when a program is selected by operating a remote control (not shown), all program information may be displayed in a pop-up or other format. Alternatively, when a program is selected, the program information, etc., described in each descriptor may be transmitted to the mobile information terminal 700 in cooperation with the mobile information terminal 700, and the mobile information terminal 700 may be instructed to display the program information, etc., described in each descriptor on the display unit 741.

[0289] The title area 162a2 of the detailed information 162a1 for each broadcast program displays the program title and symbols representing the attributes of the broadcast program. The symbols representing the attributes of the broadcast program may be, for example, symbols / characters indicating that the program is a new program or a rebroadcast program. Alternatively, the symbols may be a symbol representing "data," indicating that the program supports data broadcasting via a broadcast service. Alternatively, the symbols may be a symbol representing "NetWork," indicating that content, applications, etc. related to the broadcast program can be obtained over a network. The symbols representing the attributes of the broadcast program may be replaced 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.

[0290] 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.

[0291] 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. 20B . That is, the detailed information of the unavailable distributed program is not displayed. Alternatively, the graying-out process may be replaced by using a different background color for the detailed information 162b1. Alternatively, a message such as “This program cannot be viewed” may be displayed in the detailed description area 162a3 of the distributed program. 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 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.

[0292] 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.

[0293] 20C 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).

[0294] 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).

[0295] 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.

[0296] [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."

[0297] The emergency alert broadcast may be provided as a broadcast program on a dedicated channel (service ID), 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. 21 , 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, text information 162f1 from the emergency alert broadcast is superimposed on the EPG screen 162f.

[0298] 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.

[0299] Furthermore, when the emergency alert broadcast is provided as a broadcast program on a dedicated channel (service ID), the channel (service ID) of the emergency alert broadcast may be automatically selected regardless of the channel (service ID) of the currently viewed program. Furthermore, when the emergency alert broadcast is provided as a broadcast program on a dedicated channel (service ID) or as an application, the emergency alert broadcast program or application may be distributed to a linked external mobile terminal device (such as mobile information terminal 700 in this embodiment) under the control of linking function execution unit 1103.

[0300] Furthermore, if the power of the broadcast receiving device 100 is not on when the emergency alert broadcast is distributed, control may be performed so that the power of the broadcast receiving device 100 is automatically turned on. Alternatively, control may be performed so that a notification that an emergency alert broadcast has started is sent to a mobile information terminal 700 that has a history of linked operation with the broadcast receiving device 100.

[0301] By the above-described control, in the broadcast receiving device 100 of this embodiment, it is possible to avoid missing important broadcast programs and application video displays based on the emergency alert broadcast.

[0302] [Display control exception handling] When the broadcast receiving device 100 of this embodiment cannot acquire data that is transmitted via a path other than the TLV stream among the data that constitutes the same package, the broadcast receiving device 100 may perform, for example, the following exception processing.

[0303] As described with reference to FIG. 7A, in the broadcast system supported by the broadcast receiving device 100 of this embodiment, data acquired from a TLV stream and data acquired from a path other than the TLV stream can be included in the same package based on the location information stored in the MPT (see FIG. 7C). However, data transmitted via a data transmission path other than the TLV stream (e.g., an IPv4 data flow or IPv6 data flow on a communication line, or an MPEG2-TS broadcast) indicated by the location information is data acquired by a receiving function other than the TLV / MMT stream receiving 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 receiving functions of these transmission paths are not operating, when the receiving functions themselves are operating but relay devices on the transmission paths are not operating, when these transmission paths are not connected via wire or wireless, or when the broadcast receiving device 100 is installed in an environment where these transmission paths cannot be connected in the first place.

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

[0305] For example, in a case where an LCT defines multiple regions within a screen as shown in Figures 17D and 17E, and program video based on data acquired from a TLV stream is displayed in "Area 0," and content based on data acquired from 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 multiple regions specified by the LCT may be prohibited. Specifically, even when the LCT is received, the program video based on data acquired from the TLV stream may remain displayed in "Area 0" of the default layout display shown in Figure 17C, and a transition to a multi-region layout display such as Figures 17D and 17E 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 the broadcast receiving device 100 in this state, the default layout display shown in Figure 17C may remain, or a transition to another data broadcast screen may be prevented.

[0306] In addition, when the LCT sets multiple areas within the screen as shown in Figures 17D and 17E, and program video based on data obtained from the TLV stream is displayed in "Area 0," and content based on data obtained 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 obtained, another example of operation is to first display the display frames of the multiple areas shown in Figures 17D and 17E indicated by the LCT, and display a background color or a specified still image 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 obtained after a specified time has passed, the display may be switched back to the default layout display state shown in Figure 17C. In this case, when changing from the layout of Figure 17C to the layout of Figure 17D or Figure 17E, and when changing from the layout of Figure 17D or Figure 17E to the layout of Figure 17C, it is preferable to operate so that the program video based on the data obtained from the TLV stream continues to be displayed in ``Area 0'' of each layout, so that the user can continue watching the program video.

[0307] In addition, when data of transmission paths other than the TLV stream to be displayed in "Area 1" or "Area 2" cannot be obtained and program video based on data acquired from the TLV stream is displayed in "Area 0" of the default layout display shown in Fig. 17C, the broadcast receiving device 100 of this embodiment may start operating, or the communication environment / communication status of the various communication functions or the reception environment / reception status of the various reception functions may change, resulting in a situation where data of transmission paths other than the TLV stream to be displayed in "Area 1" or "Area 2" can be acquired. In this case, the broadcast receiving device 100 of this embodiment may immediately switch from the default layout display shown in Fig. 17C to a multi-area layout shown in Fig. 17D or 17E indicated by the LCT, and may display program video based on data acquired from the TLV stream in "Area 0", and switch to display content based on data acquired from transmission paths 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. In this case, it is preferable to notify the user that the layout change is now possible by an OSD display or the like.

[0308] [Copyright protection function] In a digital broadcasting system compatible with the broadcast receiving device 100 of this embodiment, copy control information may be included in and transmitted to the MPT or the like to indicate the copy control status of the content referenced by the MPT or the like, such as "unlimited copying permitted" (which may be divided into two types: "unlimited copying permitted with encryption processing required for storage and output" and "unlimited copying permitted with encryption processing not required for storage and output"), "one generation copying permitted", "a specified number of copies permitted" (for example, "dubbing 10" where nine copies are permitted and one move is 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, etc., in accordance with the copy control information.

[0309] The target of the storage process may be not only the storage (storage) unit 110 inside the broadcast receiving device 100, but also a removable recording medium or external device that has undergone a protection process such as encryption so that it can be played back only by the broadcast receiving device 100. Specifically, for example, it includes an external recording device such as an HDD connected to the expansion interface unit 124 that can be recorded and played back only by the broadcast receiving device 100.

[0310] <Content copy control> A specific example of content copy control processing based on the copy control information will be described below.

[0311] First, when the copy control information included in the MPT or the like indicates "unlimited copying permitted," the broadcast receiving device 100 of this embodiment may perform, without restriction, storage in the storage unit 110, recording on a removable recording medium, output to an external device, copying to an external device, moving to an external device, etc. However, when the control based on the copy control information is divided into "unlimited copying permitted and encryption processing required at storage and output" and "unlimited copying permitted and encryption processing not required at storage and output," and indicates "unlimited copying permitted and encryption processing required at storage and output," storage in the storage unit 110, recording on a removable recording medium, output to an external device, copying to an external device, moving to an external device, etc. may be performed without restriction, but encryption processing is required for all of them.

[0312] Furthermore, when copy control information included in the MPT or the like indicates "copy only once," the broadcast receiving device 100 of this embodiment may encrypt and store the content in the storage (accumulation) unit 110, or record it on a removable recording medium that has undergone protection processing, such as encryption processing, so that it can only be played on the broadcast receiving device 100. Furthermore, when the stored content is output to an external device for viewing, it is encrypted and output together with copy control information indicating "copy prohibited." Furthermore, 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, etc., is made unplayable by erasing processing, etc.) is permitted.

[0313] Furthermore, if the copy control information included in the MPT or the like indicates "copyable a predetermined number of times," the broadcast receiving device 100 of this embodiment may encrypt and store the content in the storage unit 110, or record the content on a removable recording medium that has undergone a protection process, such as encryption, that allows playback only on the broadcast receiving device 100. Furthermore, when outputting stored content to an external device for viewing, the content is encrypted and output together with copy control information indicating "copy prohibited." Furthermore, copying and moving to an external device a predetermined number of times may be permitted. In the case of the so-called "Dubbing 10" standard, nine copies and one move to an external device are possible.

[0314] Furthermore, when the copy control information included in the MPT or the like indicates "copy prohibited," the broadcast receiving device 100 of this embodiment prohibits storage (copying) in the storage (accumulation) unit 110 or the like. However, the broadcast receiving device 100 may be configured to have a "temporary storage" mode that enables storage in the storage (accumulation) unit 110 or the like only for a predetermined period of time or a predetermined period of time specified by control information included in the broadcast signal (for example, an MH-Expire descriptor or a content usage control descriptor). In this case, the broadcast receiving device 100 enables temporary storage of the content in the storage (accumulation) unit 110 or the like, even when the copy control information included in the MPT or the like indicates "copy prohibited." When content whose copy control information included in the MPT or the like indicates "copy prohibited" is output to an external device for viewing, the content is encrypted and output together with the copy control information indicating "copy prohibited."

[0315] The output for viewing to the external device described above may be performed via the video output unit 163 and audio output unit 166 of the broadcast receiving device 100 of this embodiment, or via the digital I / F unit 125 or LAN communication unit 121. The copy or move process to the external device described above may be performed via the digital I / F unit 125 or LAN communication unit 121.

[0316] FIG. 22A shows an example of the data structure of a content copy control descriptor in the broadcasting system of this embodiment. The "digital_recording_control_data" parameter in the figure is digital copy control information, which indicates information for controlling the number of copies of the content. FIG. 22B shows an example of the parameter value of the digital copy control information and its meaning. For example, when the parameter is "00," it indicates "unlimited copying," when the parameter is "01," it can be defined by the provider, when the parameter is "10," it indicates "one generation copying," and when the parameter is "11," it indicates "copying prohibited." FIG. 23 shows an example of the data structure of a content usage control descriptor in the broadcasting system of this embodiment. The "copy_restriction_mode" parameter in the figure is copy restriction mode, which indicates whether or not limited-number copying is possible.

[0317] In the broadcast receiving device 100 of this embodiment, if the digital copy control information is "01," it is possible to execute a storage process that allows a predetermined number of copies to be made, as determined in advance by the broadcaster. Alternatively, if the digital copy control information is not "11" and the copy restriction mode indicates that limited copies are permitted, it may be possible to execute a storage process that allows a predetermined number of copies to be made, as determined in advance by the broadcaster. In this case, the number of copies that can be made for each content may be specified by using part or all of the "reserved_future_use" parameter in the digital content usage descriptor.

[0318] By the above processing, the broadcast receiving device 100 of this embodiment can realize the content copy control of "a predetermined number of copies allowed" described above.

[0319] 23 is a temporary storage control bit, which indicates whether or not temporary storage of the target content is permitted when the digital copy control information indicates "copy prohibited." Also, the "retention_state" parameter is a temporary storage allowable time, which indicates the temporary storage allowable time when the temporary storage allowable bit permits temporary storage of the target content.

[0320] In the broadcast receiving device 100 of this embodiment, by referring to the information on the temporary storage control bit and the temporary storage allowable time, it is possible to control whether or not temporary storage is permitted and the storage time when the digital copy control information for each content indicates ``copy prohibited.''

[0321] 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.

[0322] <Content output control> Next, a specific example of the process of controlling the output of content to an external device will be described below.

[0323] In the content usage control descriptor shown in FIG. 23 , the “image_constraint_token” parameter is a resolution restriction bit that indicates whether image quality restriction is required when outputting content to an external device. If the resolution restriction bit indicates that image quality restriction is required, the broadcast receiving device 100 of this embodiment restricts the image quality of the target content when outputting the target content to an external device. Note that the image quality restriction may not be required when storing the content in the storage unit 110, etc. The image quality restriction may, for example, convert received (or stored) UHD (7680 pixels × 4320 pixels) video content to SHD (3840 pixels × 2160 pixels) video and output it, or convert HD (1920 pixels × 1080 pixels) video to SD (640 pixels × 480 pixels) video and output it. Note that the extent to which the image quality restriction of the target content is to be performed, i.e., the resolution of the image quality after the image quality restriction, may be specified by using part or all of the “reserved_future_use” parameter of the digital content usage descriptor.

[0324] As described above, for example, a frame rate limit bit or a pixel resolution limit bit may be prepared using part or all of the "reserved_future_use" parameter to control the frame rate limit or pixel resolution limit when outputting content to an external device. If the frame rate limit bit indicates that a frame rate limit is necessary, the broadcast receiving device 100 of this embodiment limits the frame rate of the target content when outputting the target content to an external device. For example, video content with a frame rate of 120 Hz may be converted to a frame rate of 60 Hz before outputting the content. Furthermore, if the pixel resolution limit bit indicates that a pixel resolution limit is necessary, the broadcast receiving device 100 of this embodiment limits the resolution of each pixel of the target content when outputting the target content to an external device. For example, each pixel of video content with 12 bits may be converted to 8 bits before outputting the content.

[0325] Furthermore, a resolution restriction control flag, a frame rate restriction control flag, or a pixel resolution restriction control flag may be prepared by using part or all of the "reserved_future_use" parameter, and whether or not to restrict image quality, frame rate, or pixel resolution may be controlled according to the resolution restriction control flag, frame rate restriction control flag, or pixel resolution restriction control flag. For example, if the resolution restriction control flag indicates that resolution restriction control is to be performed according to interface specifications, control may be performed so that the image quality restriction is not performed if the interface that outputs the target content has a predetermined content protection technology, and the image quality restriction is performed if the interface does not have the predetermined content protection technology.

[0326] Specifically, for example, when the digital interface unit 125 is an HDMI interface and the target content is output to an external device connected to the HDMI interface, if the HDMI interface of the external device supports HDCP (High-bandwidth Digital Content Protection) version 2.2 or later, the target content is output without the image quality restriction. However, if the HDCP version of the HDMI interface of the external device is lower than 2.2, the target content is output with the image quality restriction. That is, whether or not to restrict the image quality of the target content may be controlled depending on whether or not the interface that outputs the target content has a predetermined content protection technology, or, if the interface has the content protection technology, depending on the version of the content protection technology. Note that if the resolution restriction control flag does not indicate that resolution restriction control is to be performed according to the interface specifications, the presence or absence of the image quality restriction may be controlled only depending on the resolution restriction bit. Similar processing may also be performed for the frame rate restriction control flag and the pixel resolution restriction control flag.

[0327] Furthermore, with regard to the copying process to an external device via LAN communication unit 121 of content whose copy control information indicates copy restrictions such as "copyable only once," "copyable a specified number of times," or "copying prohibited," this 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.

[0328] Similarly, once content for which the aforementioned copy control information indicates copy restrictions such as "copyable for one generation only," "copyable a specified number of times," or "copyable an unlimited number of times with encryption required when storing and outputting" has been stored in the storage (accumulation) unit 110, moving or copying 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.

[0329] Furthermore, video and audio output for viewing of content stored in storage (accumulation) unit 110 of broadcast receiving device 100 is, in principle, only possible when 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 is prohibited when 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.

[0330] However, the encryption process may be controlled according to the value of the “encryption_mode” parameter in the content usage control descriptor shown in FIG. 23. That is, if the value of the “encryption_mode” parameter indicates that output protection of the IP interface output is required, the encryption process may be performed. If the value of the “encryption_mode” parameter indicates that output protection of the IP interface output is not required, the viewing video output and audio output may be performed without the encryption process. Furthermore, if the value of the “encryption_mode” parameter indicates that output protection of the IP interface output is required, a range of IP addresses of external devices that can perform the viewing video output and audio output without encryption may be specified, for example, by using part or all of the “reserved_future_use” parameter in the content usage control descriptor. That is, viewing video output and audio output may be performed for a predetermined IP address even if the IP address is not in the same subnet as the IP address of the broadcast receiving device 100.

[0331] Furthermore, a period during which the registration process (pairing) is valid may be specified by using part or all of the "reserved_future_use" parameter of the content usage control descriptor. In this case, if the date and time when the registration process (pairing) of the external device is performed is within the specified period, the external device may be permitted to output video and audio for viewing even if the external device is located outside the same subnetwork as the IP address of the broadcast receiving device 100, but may not be permitted if the date and time is outside the specified period.

[0332] Furthermore, the above-mentioned processes of moving, copying, outputting, etc. of content to an external device via the LAN communication unit 121 may be controlled according to the value of the "remote_view_mode" parameter of the content usage control descriptor. That is, if the value of the "remote_view_mode" parameter does not allow remote viewing of the target content, control may be performed to prohibit all processes of moving, copying, outputting, etc. of content to an external device via the LAN communication unit 121.

[0333] According to the process described above, it is possible to achieve appropriate content protection even when the content is output to an external device.

[0334] <Content copy control exception handling 1> In the data structure of the content copy control descriptor shown in Figure 22A, the first digital copy control information (the "digital_recording_control_data" parameter immediately after "descriptor_length") is copy generation control information for the entire content, and the second digital copy control information (the "digital_recording_control_data" parameter immediately after "component_tag") is copy generation control information for each component that makes up the content. Each component is specified by the "component_tag" parameter.

[0335] In the broadcasting system of this embodiment, when copy generation control is performed for the entire content (program), only the first digital copy control information is described in the content copy control descriptor, and copy generation control is performed using the first digital copy control information. On the other hand, when copy generation control is performed for each component constituting the content, both the first digital copy control information and the second digital copy control information are described in the content copy control descriptor, and copy generation control is performed. Furthermore, when copy generation control is performed for each component constituting the content, a situation may arise in which the descriptions of the first digital copy control information and the second digital copy control information described in the content copy control descriptor do not match. In the above situation, the broadcast receiving device 100 of this embodiment may be configured to perform the following operation.

[0336] In the first operation example, if the descriptions in the first digital copy control information and the second digital copy control information do not match, the system operates based on the copy generation control indicated in the first digital copy control information. In this case, simple copy generation control common to all components making up the same content becomes possible.

[0337] In the second example of operation, if the descriptions in the first digital copy control information and the second digital copy control information do not match, the system operates in accordance with the copy generation control indicated in the second digital copy control information. In this case, different copy generation control can be applied to each component, even if they constitute the same content, enabling more precise copy generation control.

[0338] Furthermore, a third operational example is a method of controlling operation based on the digital copy control information with the stricter conditions of the two different digital copy control information when the descriptions of the first digital copy control information and the second digital copy control information do not match. For example, if one is "unlimited copying permitted" and the other is "one-generation copying permitted," the "one-generation copying permitted" information is followed. Alternatively, if one is "a specified number of copies permitted" and the other is "copying prohibited," the "copying prohibited" information is followed. Alternatively, if both are "a specified number of copies permitted," the separately specified information with the fewer number of copies permitted is followed. In this case, stricter copy generation control is possible.

[0339] By performing the above processing, the broadcast receiving device 100 of this embodiment can operate appropriately even when two different pieces of digital copy control information are described in the content copy control descriptor.

[0340] <Content copy control exception handling 2> As explained using Figure 7A, in the digital broadcasting system compatible with the broadcast receiving device 100 of this embodiment, location information in the MPT (see Figure 7C) may mean 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, etc. will be explained.

[0341] First, when copy control information is included in MPT etc., 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 and encryption processing required for storage and output" and "unlimited copying allowed and encryption processing not required for storage and output"), "one generation only", "predetermined number of copies allowed" (for example, 9 copies allowed + 1 move allowed is known as "dubbing 10"), "no copying", etc.

[0342] 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?).

[0343] 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.

[0344] <Example 1> In the first operation example, when copy control information is included in the MPT etc. 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.

[0345] 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.

[0346] 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.

[0347] <Example 2> In a second operation example, when copy control information is included in the MPT or the like, 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.

[0348] 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.

[0349] 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.

[0350] 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.

[0351] 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 arranged is not limited to the MPT. In addition to the MPT, the copy control information may be arranged 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.

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

[0353] Example 2 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.

[0354] [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.

[0355] 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.

[0356] 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.

[0357] The MMT decoding processing unit 841 receives the MMT data sequence output from the first tuner / demodulation unit 831 and performs separation and decoding of 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 equivalent 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.

[0358] 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.

[0359] 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.

[0360] 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.

[0361] [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.

[0362] 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.

[0363] 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.

[0364] 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.

[0365] 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.

[0366] 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.

[0367] 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.

[0368] 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.

[0369] [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.

[0370] 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.

[0371] 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.

[0372] 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 on October 7, 2014 (today) (nearby the current time). 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.

[0373] 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 (i.e., detailed information about the broadcast programs on each channel from 5:00 p.m. on October 7, 2014) created based on the EIT of the broadcast service that employs MPEG2-TS as a media transport method.

[0374] 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.

[0375] 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.

[0376] 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.

[0377] Example 3 The following describes Example 3 of the present invention. The configuration, effects, etc. of this example are the same as those of Example 1 or Example 2 unless otherwise specified. Therefore, the following mainly describes the differences between this example and Example 1 or Example 2, and omits explanation of common points as much as possible to avoid duplication. In addition, this example describes the cooperative operation between a broadcast receiving device and a mobile information terminal.

[0378] [Application Transmission Method Overview] The application transmission method of this embodiment will be described with reference to FIG.

[0379] The broadcasting system of this embodiment is capable of a transmission method equivalent to the data carousel transmission method used in general digital broadcasting. That is, when downloading data to a receiver or transmitting content for multimedia services, data is repeatedly transmitted, allowing the receiver to obtain the necessary data at any time during the broadcast. Data is encapsulated in an asynchronous MPU on a file-by-file basis and transmitted. Control information related to application transmission may be transmitted using a data transmission message. The data transmission message is assumed to store a data directory management table, a data asset management table, and a data content management table.

[0380] The path names of the files that make up an application are specified in the application description, such as HTML5. The path name can be written as a combination of a directory node name and a file name. In addition, a node tag is defined as an identifier that integrates the directory node and the file, and is used as information that links each table.

[0381] A receiver that receives a path name from an application obtains the node tag of the file with the specified path name from the data directory management table in the data transmission message. Next, the receiver obtains the component tag, download ID, MPU sequence number, and item ID of the asset to which the item with the obtained node tag is to be transmitted from the data asset management table also in the data transmission message. Furthermore, the receiver references the MP table to obtain location information for the asset with the obtained component tag and identify the asset to which the file is actually to be transmitted. Within the identified asset, the obtained download ID and the download ID written in the multi-extension header field of the MMTP packet transmitting the item can uniquely identify the unit of repeated transmission of the file corresponding to the carousel. Of the repeatedly transmitted items, the item with the obtained MPU sequence number and item ID can be obtained as the desired file.

[0382] It is assumed that the node tag is unique within a data transmission message, the MPU sequence number is unique within an asset, and the item ID is unique within a service provider.

[0383] Furthermore, by constantly monitoring the data asset management table, the receiver can detect when the files that make up an application have been updated, allowing the application to always be presented in its latest state. Update detection may be possible at each level: asset-by-asset, MPU-by-MPU, or file-by-file. The data asset management table can be used to obtain the component tag, MPU sequence number, and item ID of the updated file. As with the file acquisition described above, the asset can be identified by referencing the MP table, and the item with the obtained MPU sequence number and item ID can be acquired as the desired updated file.

[0384] The data content management table provides file configuration information for data content in order to achieve flexible and effective cache control. It defines the unit of presentation within the data content (e.g., a page) as a presentation unit, and indicates information such as which items are related to each unit and which presentation units are linked to each other. This information makes it possible to know other items contained in the same presentation unit as the initially requested item. It also provides information such as cache control for each presentation unit. As a result, the receiver can reduce the time required to retrieve the entire page and prioritize caching of the next page.

[0385] As mentioned above, applications and data are also transmitted as assets, and the asset type (asset_type) is recorded in the MP table (MPT: see Figure 7B). The asset types are summarized in Figure 29. In addition to broadcast video, audio, and subtitle data, applications and data used by applications are transmitted as assets. Furthermore, the assets of the applications and data used by the applications may be acquired via broadcast waves or via a communication line. An example of the data structure of location information (MMT_general_location_info) that describes the acquisition source of the asset is shown in Figure 30A. This location information describes the type of acquisition destination (location_type) and the acquisition destination. The meaning of the acquisition destination type is shown in Figure 30B.

[0386] [Application presentation format] Like broadcast video and audio, applications are presented in regions defined in the layout setting table (LCT: see Figure 17A). The region to be used is specified by the layout number (layout_number) and region number (region_number) in the MPU presentation region specification descriptor (MPU_Presentation_Region_Descriptor). An example of the data structure of the MPU presentation region specification descriptor is shown in Figure 31.

[0387] [Application Control Information Summary] The application control information in this embodiment is information intended to notify a television receiver or the like (broadcast receiving device 100 in this embodiment) of the existence of an application (hereinafter, sometimes referred to as a broadcast-linked app) that links with a broadcast service and to instruct its control in the broadcast-communication linkage function supported by broadcast receiving device 100. Note that the application control information in this embodiment is transmitted in the form of an MH-application information table (MH-AIT: see FIG. 6B) in the broadcast system.

[0388] In addition, the broadcast-linked apps may be classified into (1) broadcast-managed applications that operate only in a broadcast reception state based on control signals such as start / stop included in the broadcast signal and are permitted to access broadcast resources based on the control signals, (2) non-broadcast-managed applications that operate in a form that is not controlled by the broadcast signal for start / stop etc. and are permitted to access broadcast resources based on means such as application authentication, and (3) other general applications that are not permitted to access broadcast resources.

[0389] The MH-AIT is stored in an M2 section message (see FIG. 6A) and transmitted. An example of the data structure of the MH-AIT is shown in FIG. 32A.

[0390] The type of application to be controlled by MH-AIT is indicated by the "application_type (application type)" parameter. The allocation of application types is shown in Figure 32B. The control code that controls the state of the application is indicated by the "application_control_code (application control code)" parameter. The application control code may be specified for each application type. If there is no specification for each application type, the code shall be used in the sense shown in Figure 32C.

[0391] Applications are identified by an application identifier (application_identifier). An example of the data structure of an application identifier is shown in Figure 32D. The application identifier is a value that is defined for each application format and uniquely identifies each application. The application identifier may consist of an organization identifier (organization_id) that identifies the operator and an application identifier (application_id) that is assigned to each operator. The same application identifier for each operator may be reused for different applications by separating them by time, but in that case, it is desirable to take into account the application cache expiration time (MH-cache information descriptor: see Figure 6D) and to prevent the same identification value from being assigned to different applications within the receiver.

[0392] [Descriptor to be included in MH-AIT] Information about each application is described in the parameters mentioned above as well as in descriptors. Figures 6C and 6D show a list of descriptors for this broadcasting system, but the main descriptors related to the MH-AIT are described in detail below.

[0393] (1) MH-Application Descriptor One MH-application descriptor must be placed for each application in the application information descriptor loop of the MH-AIT. An example of the data structure of an MH-application descriptor is shown in Figure 33. The "application_profile" parameter indicates the application profile of the receiver that can execute the target application. If the receiver implements this profile, it indicates that it has the ability to execute the target application. The content of the profile is defined for each application format.

[0394] (2) MH-Transmission Protocol Descriptor The purpose of this descriptor is to specify the transmission protocol for broadcasting, communication, etc. as the transmission means for an application and to indicate the location information of applications dependent on the transmission protocol. It shall be placed in the MH-AIT common descriptor loop or application information descriptor loop for the number of transmission protocol labels in the application descriptor. An example of the data structure of the MH-Transmission Protocol Descriptor is shown in Figure 34A. The "protocol_id (protocol identification)" parameter specifies the protocol for transmitting the target application. The meaning of the protocol identification is shown in Figure 34B. Furthermore, the "selector_byte (selector area)" stores supplementary information specified for each protocol identification. An example of the data structure of the selector area for HTTP / HTTPS transmission and MMT non-timed transmission is shown in Figure 34C. It shall be possible to obtain information about the URL for obtaining the target application using the "URL_base_byte (URL base)" parameter, the "URL_extension_byte (URL extension)" parameter, etc.

[0395] (3) MH-Simple Application Location Descriptor The MH-simple application location descriptor is intended to specify the details of where to obtain the application, and one must be placed for each application in the application information descriptor loop of the MH-AIT. An example of the data structure of the MH-simple application location descriptor is shown in Figure 35. The "initial_path_byte (application URL)" parameter indicates the URL that is the entry point of the target application. It may be indicated by a relative path rooted at the location where the target application can be obtained, as described in the transmission protocol descriptor.

[0396] (4) MH-Application Boundary Authority Setting Descriptor The MH-application boundary permission setting descriptor is intended to set the application boundary and to set broadcast resource access permission for each area (URL), and one or more descriptors shall be placed in the application information descriptor loop of the MH-AIT. If this descriptor is not placed, the application boundary will be infinite, and access to all broadcast resources will be permitted. An example of the data structure of the MH-application boundary permission setting descriptor is shown in Figure 36. The "permission_bitmap (access permission bitmap)" parameter configures the access permission for each broadcast resource using a bitmap for each function. The "managed_URL_byte (access permission management area setting information)" parameter indicates the URL of the area to which the access permission setting indicated by the access bitmap applies. The access permission management area setting information is specified by the domain or its subdirectory.

[0397] (5) MH-Boot Priority Information Descriptor The MH-launch priority information descriptor is intended to specify the application launch priority, and a maximum of one shall be placed per application in the application information descriptor loop of the MH-AIT. However, this descriptor may only be placed in application information descriptions where the application control code indicates an instruction to automatically launch the application (such as "AUTOSTART"). Furthermore, if this descriptor is not placed, it may be considered to have the lowest priority, including data broadcasting. An example of the data structure of the MH-launch priority information descriptor is shown in Figure 37. The "autostart_priority (launch priority)" parameter indicates the launch priority of the target application among data broadcasting and all applications linked to the currently received service.

[0398] (6)MH-Cache Information Descriptor The MH-cache information descriptor is intended for use in cache control when caching and retaining resources that make up an application when it is expected that the application will be reused, and a maximum of one shall be placed per application in the application information descriptor loop of the MH-AIT. If this descriptor is not placed, the receiver may delete the resources that make up the application rather than retaining them when the application is terminated. An example of the data structure of the MH-cache information descriptor is shown in Figure 38A. The "cache_priority" parameter indicates the priority for retaining the cache for the target application. The larger the value, the higher the priority is considered to be. If the cache capacity is exceeded, cache deletion shall be performed on an application-by-application basis based on this information. If no priority is specified, this parameter shall be "0xFF". The "application_version" parameter indicates the version number of the target application.

[0399] The receiver stores the application version corresponding to the cached application, and if the application version is updated when the application is launched, it will not use the application stored in the cache, but will instead retrieve and use the new application from the specified URL, rewriting the cache contents. The "expire_date (cache expiration date)" parameter indicates the cache expiration date of the target application as a year, month, and day in the lowest 16 bits of the MJD. The receiver can cache the target application until this expiration date. If the expiration date is exceeded, the application will be deleted from the cache. For an indefinite cache period, set this parameter to "0xFFFF." If this cache expiration parameter is not set, the receiver may prohibit cache retention after the program ends, prioritizing application stability, or may cache the application indefinitely for viewer convenience, or may balance these two and retain the cache for a predetermined period of time.

[0400] Also, instead of a cache expiration date, an expiration date for each application can be set. An example of the data structure of the MH-application expiration date descriptor, which describes the expiration date for each application, is shown in Figure 38B. If this expiration date is exceeded, the use of that application will be prohibited. Although long-term caching is not permitted, it is possible to permit the application to be re-acquired and used for a certain period of time, enabling a variety of application usage patterns.

[0401] (7)MH - Probabilistic Adaptive Delay Descriptor The MH-Probabilistic Application Delay Descriptor is intended to delay application control by a probabilistically set delay amount, assuming load balancing of server accesses for application acquisition. Up to one descriptor should be placed per application in the MH-AIT application information descriptor loop. If this descriptor is not placed, the control action indicated by the control code will be performed when a specific version of MH-AIT is first received. An example of the data structure of the MH-Probabilistic Application Delay Descriptor is shown in Figure 39. The "range" (delay time range) parameter indicates the maximum delay time from the current time until the control code is applied, in seconds. The "rate" (variance number) parameter indicates the number of stages of delay time until the control code is applied probabilistically. The receiver calculates the delay time using the formula "N × range ÷ rate" based on the value "N" randomly selected from integers between "0" and "rate," and applies the control code by this delay amount from the time the MH-AIT was received. The "randomization_end_time" (probabilistic application end time) parameter indicates the deadline for the probabilistic application delay processing. If MH-AIT is received after the time specified in this parameter, the control code is applied immediately. The date is encoded in the lower 16 bits of MJD, and the time is encoded in 24 bits of BCD as the hour, minute, and second in JST.

[0402] Furthermore, the MH-AIT of this embodiment may further include parameters and descriptors that are different from those described above.

[0403] The operation of the broadcast receiving device 100 of this embodiment will be described below.

[0404] [Application startup sequence] First, the automatic start-up process of a broadcast-linked app based on the MH-AIT transmitted by broadcast waves in the broadcast receiving device 100 of this embodiment will be described with reference to Fig. 40A. This is an example of a case where a broadcast-linked app related to a selected channel is automatically started.

[0405] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires an MMT data sequence, the application control unit 153 checks the MH-AIT stored in the M2 section message (S1001). If the MH-AIT is not stored in the M2 section message, it is assumed that there is no broadcast-linked app related to the selected channel, and the automatic startup processing may be terminated. Next, the application format and application control code of each broadcast-linked app described in the MH-AIT are checked (S1002). If, as a result of the processing of S1002, there is no broadcast-linked app with an application control code of "AUTOSTART" (S1003: No), the automatic startup processing may be terminated. In this case, launcher processing can be performed again, which will be described later.

[0406] On the other hand, if the result of the processing in S1002 is that there is a broadcast-linked app having an application control code of "auto-start" (S1003: Yes), the MH-start priority information descriptor in the MH-AIT related to the broadcast-linked app is checked (S1004). Next, the broadcast-linked app with the highest priority among the broadcast-linked apps having the application control code of "auto-start" is selected (S1005), and the MH-application descriptor in the MH-AIT related to the selected broadcast-linked app is checked (S1006). If the broadcast receiving device 100 satisfies the application profile described in the MH-application descriptor (S1007: Yes), the process proceeds to the next step. If the broadcast receiving device 100 does not satisfy the application profile described in the MH-application descriptor (S1007: No), the selected broadcast-linked app is determined to be unable to be started by the broadcast receiving device 100. In this case, it is checked whether there is a broadcast-linked app with a second priority (S1008). If there is no broadcast-linked app with a second priority, the automatic start process may be terminated. If there is a broadcast-linked application with the second highest priority, the broadcast-linked application with the second highest priority is selected (S1009), and the processes of S1006 to S1007 are repeated.

[0407] If the broadcast receiving device 100 determines in the processing of S1007 that the application profile described in the MH-application descriptor is satisfied, it checks the MH-transmission protocol descriptor of the MH-AIT related to the selected broadcast-linked app (S1010). If the result of the processing of S1010 shows that the selected broadcast-linked app can be acquired by HTTP / HTTPS transmission based on the protocol identification described in the MH-transmission protocol descriptor (S1011: Yes), it further checks the MH-simple application location descriptor of the MH-AIT related to the selected broadcast-linked app (S1012) and acquires the URL of the entry point of the selected broadcast-linked app.

[0408] After acquiring the URL of the entry point of the selected broadcast-linked app in the process of S1012, the LAN communication unit 121 then requests a server (in this embodiment, the service provider server 400) on the Internet 200 specified by the URL to distribute the broadcast-linked app (S1013). The service provider server 400, which has received the distribution request, performs appropriate authentication processing for the broadcast receiving device 100 and then distributes the requested broadcast-linked app (S1014). When the broadcast-linked app is received from the service provider server 400 via the LAN communication unit 121, the broadcast receiving device 100 launches the received broadcast-linked app in the browser unit 154 under the control of the application control unit 153 (S1018). Note that the authentication processing for the broadcast receiving device 100 performed by the service provider server 400 may be a well-known process, and detailed description thereof will be omitted.

[0409] On the other hand, if the result of the processing of S1010 indicates that the selected broadcast-linked app can be acquired by data carousel transmission using the protocol identification described in the MH-transmission protocol descriptor (S1011: No), the application control unit 153 checks the DDM table and DAM table stored in the data transmission message (S1015, S1016) and identifies the asset to which the selected broadcast-linked app is transmitted using the procedure described above in [Overview of Application Transmission Method]. Furthermore, after acquiring the broadcast-linked app from the identified asset of the broadcast wave (S1017), the broadcast receiving device 100, under the control of the application control unit 153, launches the received broadcast-linked app in the browser unit 154 (S1018).

[0410] The above series of processes enables the broadcast receiving device 100 of this embodiment to automatically start a broadcast-linked app based on the MH-AIT transmitted via broadcast waves. Note that the MH-AIT confirmation process in each of the processes of S1004, S1006, S1010, and S1012 may involve acquiring and confirming the MH-AIT from the broadcast waves each time, or may involve caching the MH-AIT acquired in the process of S1001 and confirming the cached MH-AIT. Note also that the above operation sequence is merely an example, and a different processing procedure may be used.

[0411] Next, the launcher process of the broadcast-linked app based on the MH-AIT transmitted by the broadcast wave in the broadcast receiving device 100 of this embodiment will be described with reference to Fig. 40B. This is an example of a case where a broadcast-linked app related to a selected channel is launched based on a user instruction.

[0412] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires an MMT data sequence, the application control unit 153 checks the MH-AIT stored in the M2 section message (S1101). Note that if the MH-AIT is not stored in the M2 section message, it may be determined that there is no broadcast-linked app related to the selected channel, and the automatic start processing may be terminated. Next, the application format and application control code of each broadcast-linked app described in the MH-AIT are checked (S1102). If the result of the processing in S1102 indicates that there is a broadcast-linked app with an application control code of "AUTOSTART" (S1103: Yes), the automatic start processing shown in FIG. 40A is possible.

[0413] On the other hand, if the result of the processing of S1102 is that there is no broadcast-linked app having an application control code of "auto-start" (S1103: No), the program checks again whether there is a broadcast-linked app having an application control code of "executable (PRESENT)." If there is no broadcast-linked app having an application control code of "executable" (S1104: No), the program may terminate the launcher processing. If there is a broadcast-linked app having an application control code of "executable" (S1104: Yes), the program checks the MH-application descriptors in the MH-AITs for each of the broadcast-linked apps having the application control code of "executable" (S1105). If the result of the processing of S1105 is that there is no broadcast-linked app whose application profile described in the MH-application descriptor is satisfied by the broadcast receiving device 100 (S1106: No), the program may terminate the launcher processing. If there is at least one broadcast-linked app whose application profile described in the MH-application descriptor is satisfied by the broadcast receiving device 100 (S1106: Yes), the program proceeds to the next processing.

[0414] After the processes of S1101 to S1103 and S1104 to S1106 have been completed, it is assumed that the broadcast receiving device 100 has not yet executed the broadcast-linked app, and a normal broadcast program video is being displayed on the monitor unit 162. In this state, when the user issues an instruction to launch a broadcast-linked app launcher using a remote control or a mobile information terminal capable of operating the broadcast receiving device 100 (S1107), an OSD display of a list of broadcast-linked apps executable on the broadcast receiving device 100 is displayed on the monitor unit 162 (S1108). Furthermore, when the user operates the remote control or the mobile information terminal to issue an instruction to select a desired broadcast-linked app from the list of broadcast-linked apps (S1109), the application control unit 153 selects a broadcast-linked app based on the user's instruction (S1110), and acquires and launches the selected broadcast-linked app (S1111 to S1119). The processes of S1111 to S1119 may be the same as the processes of S1010 to S1018 shown in FIG. 40A.

[0415] The above series of processes enables the broadcast receiving device 100 of this embodiment to perform launcher processing of the broadcast-linked app based on the MH-AIT transmitted via broadcast waves. Note that the MH-AIT confirmation process in each of S1105, S1111, and S1113 may involve acquiring and confirming the MH-AIT from the broadcast waves each time, or may involve caching the MH-AIT acquired in the process of S1101 and confirming the cached MH-AIT. The order of the processes of S1104 to S1106 and S1107 to S1110 may be reversed. In this case, the profile confirmation process of S1104 to S1106 may be performed only on the broadcast-linked app selected in the process of S1110. Furthermore, the list of broadcast-linked apps displayed in the processing of S1108 may be configured to display only those that can be executed on the broadcast receiving device 100 depending on the status of the application profile, or may display all broadcast-linked apps regardless of the status of the application profile and disable those that cannot be executed on the broadcast receiving device 100. Furthermore, the above-described operation sequence is merely an example, and a different processing procedure may be used.

[0416] Next, the process of starting a broadcast cooperative app based on the MH-AIT transmitted by broadcast waves from a data broadcast screen in the broadcast receiving device 100 of this embodiment will be described with reference to FIG. 40C.

[0417] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires an MMT data string, the application control unit 153 checks the MH-AIT stored in the M2 section message and checks whether there is a broadcast-linked application having an application control code of "AUTOSTART" or "PRESENT" (S1201 to S1206). Note that the processing of S1201 to S1206 may be the same as the processing of S1101 to S1106 shown in FIG. 40B.

[0418] After the processes of S1201 to S2106 are completed, it is assumed that the broadcast receiving device 100 is not yet executing the broadcast-linked app, and a normal broadcast program video is displayed on the monitor unit 162. In this state, when the user issues an instruction to launch a data broadcasting screen using a remote control or a mobile information terminal capable of operating the broadcast receiving device 100 (S1207), the data decoder 151 (if the data broadcasting screen can be displayed) acquires a BML document or the like from the data carousel of the MMT data string, interprets the acquired BML document, etc., creates a data broadcasting screen, and displays it on the monitor unit 162 (S1208). Note that, if there is at least one broadcast-linked app whose application profile the broadcast receiving device 100 satisfies in the process of S1206, an entry button related to the broadcast-linked app is displayed on the data broadcasting screen displayed in the process of S1208. If there is not at least one broadcast-linked app whose application profile the broadcast receiving device 100 satisfies in the process of S1206, the entry button related to the broadcast-linked app may not be displayed, or may be displayed in an inactive state.

[0419] Furthermore, when the user operates the remote control or mobile information terminal to instruct selection (launch) of the entry button of the desired broadcast-linked app displayed on the data broadcast screen (S1209), the application control unit 153 selects a broadcast-linked app based on the user's instruction (S1210) and acquires the selected broadcast-linked app (S1211 to S1218). Note that the processing of S1211 to S1218 may be the same as the processing of S1010 to S1017 shown in Fig. 40A. After the acquisition of the selected broadcast-linked app is completed by the processing of S1211 to S1218, the display of the data broadcast screen is terminated (S1219), and the application control unit 153 launches the selected broadcast-linked app (S1220).

[0420] The above series of processes enables the broadcast receiving device 100 of this embodiment to launch a broadcast-linked app from a data broadcast screen based on the MH-AIT transmitted via broadcast waves. The MH-AIT confirmation processes in steps S1205, S1211, and S1213 may involve acquiring the MH-AIT from the broadcast waves and confirming it each time, or may involve caching the MH-AIT acquired in step S1201 and confirming the cached MH-AIT. The order of steps S1204 to S1206 and S1207 may be reversed. The process of step S1219 may be performed immediately after step S1209. Alternatively, the process of step S1219 may be omitted, and the broadcast-linked app, data broadcast screen, broadcast program video, and the like may be simultaneously displayed in each of the divided areas of the display area of ​​the monitor unit 162 based on the description in the LCT. The above operational sequence is merely an example, and different processing procedures may be used.

[0421] In the startup sequences of the broadcast-linked app described using Figures 40A to 40C, examples are given in which the MH-AIT is obtained from broadcast waves, but the MH-AIT file may also be obtained from a specified server device (such as the broadcast station server 300) specified by location information (MMT_general_location_info) or the like.

[0422] Furthermore, if there is no response from the service provider server 400 or the like for a predetermined time or longer when a distribution request for the broadcast-linked app is made in S1013, S1114, or S1214, a message such as "Please wait a moment" may be displayed on the monitor unit 162. Alternatively, in this case, a message inquiring the user about stopping execution of the broadcast-linked app may be displayed.

[0423] Furthermore, the start-up sequence of the broadcast cooperative app is not limited to the three patterns described above, and the broadcast cooperative app may be started up by a different sequence.

[0424] [Operation sequence when linking mobile information terminals] In the broadcast receiving device 100 of this embodiment, it is assumed that the functionality of a broadcast / communication cooperative service can be expanded by cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700. For example, by installing an application (cooperative control app) provided by a television receiver manufacturer, it becomes possible to use the mobile information terminal 700 as a high-function remote control for the broadcast receiving device 100. In addition, by executing the broadcast cooperative app on the mobile information terminal 700, it becomes possible to display, for example, a service linked to a broadcast program being displayed on the broadcast receiving device 100 on the mobile information terminal 700. Note that in order to expand functionality through cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700, it is desirable that the cooperative control app be running on the mobile information terminal 700, and the broadcast cooperative app running on the mobile information terminal 700 operates under the control of the cooperative control app.

[0425] 41A is an operational sequence diagram showing an example of the operation when the cooperative control app is started on the mobile information terminal 700. The diagram shows a series of steps from when the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 until cooperative operation becomes possible. Note that the cooperative control app is assumed to be installed in advance as a cooperative control program 7002 in the storage unit 710 of the mobile information terminal 700. If the cooperative control program 7002 is not installed, the cooperative control program 7002 is first installed.

[0426] When a user operates operation unit 730 of mobile information terminal 700 to issue an instruction to launch the cooperative control app (S1301), cooperative control execution unit 7102 of mobile information terminal 700 first searches for television receivers on the network that can communicate (operate cooperatively) (S1302) and displays the search results as a list of television receivers on display unit 741 (S1303). The displayed list of television receivers may include a mixture of television receivers that have a history of cooperative operation with mobile information terminal 700 in the past and those that do not, and in that case, it is desirable that the display format make it possible to determine whether or not there is a history of past cooperative operation. Furthermore, if no television receivers that can communicate are found, a message to that effect may be displayed and the processing may end.

[0427] When the user operates the operation unit 730 of the mobile information terminal 700 to select a specific television receiver (the broadcast receiving device 100 of this embodiment) from the list of television receivers (S1304), if the broadcast receiving device 100 has a history of previously performing linked operations with the mobile information terminal 700 (S1305: Yes), authentication information related to the broadcast receiving device 100 (such as the login name and password specified by the broadcast receiving device 100) is read from the authentication information memory area 7300 of the storage unit 710 (S1306), and the process proceeds to the next step.

[0428] On the other hand, if the broadcast receiving device 100 has no history of linking with the mobile information terminal 700 in the past (S1305: No), the linkage control execution unit 7102 transmits a login screen information request to the broadcast receiving device 100 (S1307). When login screen information is transmitted from the broadcast receiving device 100 in response to the processing of S1307 (S1308), the linkage control execution unit 7102 receives the login screen information and displays the login screen on the display unit 741 (S1309). Note that if the linkage control app already has login screen information for the broadcast receiving device 100, the processing of S1307 to S1308 may be omitted. When the user inputs authentication information on the displayed login screen (S1310), the input authentication information is stored in the authentication information storage area 7300 of the storage unit 710, and the process proceeds to the next step.

[0429] In addition, the determination of whether or not there is a history of the above-mentioned collaborative operation may be made by checking whether or not authentication information related to the broadcast receiving device 100 is stored in the authentication information storage area 7300 of the storage unit 710, or by other methods.

[0430] Next, the cooperative control execution unit 7102 transmits the authentication information read in the processing of S1306 or the authentication information input in the processing of S1310 to the broadcast receiving device 100 (S1311). Note that the processing of transmitting the authentication information to the broadcast receiving device 100 may be performed via the LAN communication unit 721 and the router device 200r, or may be performed directly to the broadcast receiving device 100 via the NFC communication unit 723.

[0431] The broadcast receiving device 100 compares the authentication information transmitted from the mobile information terminal 700 with the authentication information stored in the authentication information storage area 1300 of the storage unit 110 to confirm whether the received authentication information is correct (S1312). If the processing of S1312 confirms that the received authentication information is correct, information capable of identifying the mobile information terminal 700 is stored in the authentication information storage area 1300, and an authentication result (authentication OK) is transmitted to the mobile information terminal 700 (S1313). If the processing of S1312 confirms that the received authentication information is incorrect, the information capable of identifying the mobile information terminal 700 is not stored in the authentication information storage area 1300, and an authentication result (authentication NG) is transmitted to the mobile information terminal 700.

[0432] When the linkage control execution unit 7102 of the mobile information terminal 700 receives an authentication result (authentication OK) from the broadcast receiving device 100, it displays the basic screen of the linkage control app (for example, an advanced remote control screen) on the display unit 741 (S1314). On the other hand, when the authentication result (authentication NG) is received, the linkage control execution unit 7102 does not display the basic screen of the linkage control app and terminates the operation of the linkage control app. In this case, it is desirable to display an error message or the like notifying that authentication has failed.

[0433] Through the above series of processes, the mobile information terminal 700 and the broadcast receiving device 100 are ready for cooperative operation.

[0434] Note that, if a broadcast cooperative app is to be launched in the broadcast receiving device 100 following the above-described processing, the processing of Figs. 40A to 40C may be performed after the above-described processing.

[0435] 41B is an operation sequence diagram showing an example of the operation when the cooperative control app is started on the mobile information terminal 700. The diagram shows a series of flows until cooperative operation becomes possible when the broadcast receiving device 100, which executes the start sequence of the broadcast cooperative app, requests the start of the cooperative control app on the mobile information terminal 700.

[0436] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires an MMT data string, the application control unit 153 checks the MH-AIT stored in the M2 section message, checks whether there is a broadcast-linked app having an application control code of "autostart (AUTOSTART)", and checks the profile of the broadcast-linked app having the application control code of "autostart" (S1401). Note that the processing of S1401 may be the same as the processing of S1001 to S1009 shown in FIG. 40A.

[0437] In the profile confirmation process of the highest priority application at S1401, if the broadcast receiving device 100 satisfies the application profile of the highest priority application and it is determined that a cooperative operation with a mobile terminal device is necessary, the broadcast receiving device 100 selects a mobile terminal device (mobile information terminal 700 in this embodiment) that has a history of cooperative operation with the broadcast receiving device 100 in the past by referencing the authentication information storage area 1300 of the storage unit 110 (S1402). In the profile confirmation process of the highest priority application at S1401, if the broadcast receiving device 100 satisfies the application profile of the highest priority application and it is determined that a cooperative operation with a mobile terminal device is not necessary, the same process as in Fig. 40A may be performed. In the profile confirmation process of the highest priority application at S1401, if the broadcast receiving device 100 does not satisfy the application profile of the highest priority application, the launch process of the broadcast cooperative application and the launch process of the cooperative control application may be terminated.

[0438] Note that the selection of the mobile information terminal 700 by referring to the authentication information storage area 1300 may be performed by selecting the mobile terminal device with the most recent collaboration history or the most frequently used mobile terminal device. Information about multiple mobile terminal devices with collaboration history may be displayed on the monitor unit 162, allowing the user to select a mobile terminal device to collaborate with. If there is no collaboration history, a message to that effect may be displayed on the monitor unit 162, and the collaboration control app may be started by operating the mobile information terminal 700. The processing in this case is as shown in FIG. 41A.

[0439] The cooperative control execution unit (not shown) of the broadcast receiving device 100 transmits a cooperative control application start request to the mobile information terminal 700 selected in the process of S1402 (S1403).

[0440] Main control unit 701 of mobile information terminal 700 starts the collaboration control app (collaboration control execution unit 7102) in response to the collaboration control app start request transmitted from broadcast receiving device 100 (S1404), and collaboration control execution unit 7102 executes a series of processes (S1405 to S1408), such as reading authentication information related to broadcast receiving device 100 from authentication information memory area 7300 of storage unit 710, transmitting the authentication information to broadcast receiving device 100, and authenticating the mobile information terminal in broadcast receiving device 100. Note that the processes of S1405 to S1408 may be the same as the processes of S1306 and S1311 to S1313 shown in FIG. 41A.

[0441] When the linkage control execution unit 7102 of the mobile information terminal 700 receives an authentication result (authentication OK) from the broadcast receiving device 100, it displays the basic screen of the linkage control app (e.g., an advanced remote control screen) on the display unit 741 (S1409) and transmits a linkage control app startup success response to the broadcast receiving device 100 (S1410). On the other hand, when the authentication result (authentication NG) is received, it does not display the basic screen of the linkage control app, but transmits a linkage control app startup failure response to the broadcast receiving device 100, and terminates operation of the linkage control app.

[0442] When the broadcast receiving device 100 receives a start success response from the mobile information terminal 700, it acquires and launches the broadcast-linked app selected in the processing of S1401 (S1411). Note that the processing of S1411 may be the same as the processing of S1010 to S1018 shown in FIG. 40A. On the other hand, when a start failure response is received from the mobile information terminal 700, the broadcast receiving device 100 may not acquire and launch the broadcast-linked app selected in the processing of S1401. If the broadcast-linked app is capable of operating in a mode that does not require cooperative operation with a mobile terminal device, it may be configured to launch the broadcast-linked app in that mode of operation.

[0443] Through the above series of processes, the mobile information terminal 700 and the broadcast receiving device 100 are ready for cooperative operation.

[0444] Note that, following the above-described processing, if the broadcast cooperative application (terminal side) is also to be started up on the mobile information terminal, the processing of FIG. 41C may be performed after the above-described processing.

[0445] FIG. 41C is an operational sequence diagram showing an example of the operation when a broadcast cooperative app (terminal side) is started on mobile information terminal 700 based on transmission information from broadcast receiving device 100. As shown in FIG.

[0446] That is, after executing the processes of S1401 to S1411 of FIG. 41B (S1501), the application control unit 153 of the broadcast receiving device 100 next checks the MH-transmission protocol descriptor of the MH-AIT related to the terminal-side broadcast cooperative app (S1502). If the result of the process of S1502 shows that the terminal-side broadcast cooperative app can be acquired by HTTP / HTTPS transmission based on the protocol identification described in the MH-transmission protocol descriptor (S1503: Yes), the application control unit 153 further checks the MH-simple application location descriptor of the MH-AIT related to the terminal-side broadcast cooperative app (S1504) and acquires the URL of the entry point of the terminal-side broadcast cooperative app. When the URL of the entry point of the terminal-side broadcast cooperative app is acquired in the process of S1504, the application control unit 153 transmits the URL information to the mobile information terminal 700 (S1505).

[0447] The mobile information terminal 700, which has received the URL information from the broadcast receiving device 100, then makes a distribution request for the terminal-side broadcast cooperative app to a server (in this embodiment, the service provider server 400) on the Internet 200 specified by the URL via the LAN communication unit 721 (S1506). The service provider server 400, which has received the distribution request, performs appropriate authentication processing for the mobile information terminal 700 and then distributes the requested terminal-side broadcast cooperative app (S1507). When the terminal-side broadcast cooperative app is received from the service provider server 400 via the LAN communication unit 721, the mobile information terminal 700 executes the launch of the received terminal-side broadcast cooperative app in the browser engine based on the control of the already-launched link control app (link control execution unit 7102) (S1512). Note that the authentication processing for the mobile information terminal 700 performed by the service provider server 400 may be a well-known processing, and detailed description thereof will be omitted.

[0448] On the other hand, if the result of the processing of S1502 indicates that the terminal-side broadcast-linked app can be acquired by data carousel transmission using the protocol identification described in the MH-transmission protocol descriptor (S1503: No), the application control unit 153 of the broadcast receiving device 100 checks the DDM table and DAM table stored in the data transmission message (S1508, S1509) and identifies the asset to which the terminal-side broadcast-linked app will be transmitted using the procedure described in the above-mentioned [Overview of Application Transmission Method]. Furthermore, after acquiring the terminal-side broadcast-linked app from the identified asset of the broadcast wave (S1510), the broadcast receiving device 100 transmits the acquired terminal-side broadcast-linked app to the mobile information terminal 700 (S1511). Furthermore, in the mobile information terminal 700, the terminal-side broadcast-linked app transmitted from the broadcast receiving device 100 is executed by a browser engine under the control of the already-activated link control app (link control execution unit 7102) (S1512).

[0449] Note that the terminal-side broadcast-linked app acquired in S1510 may be stored in the content information storage area 1200 of the storage unit 110, and in the processing of S1511, the URL of the content information storage area 1200 may be transmitted instead of the transmission processing of the terminal-side broadcast-linked app, and the mobile information terminal 700 may be caused to access the content information storage area 1200, thereby causing the mobile information terminal 700 to acquire the terminal-side broadcast-linked app. If the mobile information terminal 700 has a function for receiving digital broadcasts, the mobile information terminal 700 may acquire the terminal-side broadcast-linked app from broadcast waves.

[0450] Furthermore, the processing of S1502 to S1512 may be executed after S1501, triggered by a terminal-side broadcast cooperative app transmission request (not shown) transmitted from the mobile information terminal 700 to the broadcast receiving device 100.

[0451] In addition, the operation sequences of Figures 40A to 40C and Figures 41A to 41C can be partially combined as appropriate, and some operation steps can be rearranged in order or operated simultaneously with other operation steps as appropriate.

[0452] [Mobile device linkage control app basic screen] Fig. 42A is a screen display diagram showing an example of a basic screen of the cooperative control app displayed by the process of S1314 in Fig. 41A, the process of S1409 in Fig. 41B, etc. In this embodiment, the basic screen 741a of the cooperative control app has the function of a high-function remote control compatible with the broadcast receiving device 100.

[0453] The basic screen 741a of the linked control app is composed of a power key 741a1, a network selection key (digital terrestrial, BS, CS) 741a2, number keys (1 to 12) 741a3, volume UP / DOWN keys 741a4, channel UP / DOWN keys 741a5, input switch key 741a6, program guide key 741a7, data key 741a8, linked app key 741a9, menu key 741aa, back key 741ab, cursor keys (up, down, left, right) 741ac, enter key 741ad, and color keys (blue, red, green, yellow) 741ae. Other operation keys may also be displayed.

[0454] For ease of use, the operation keys may have the same key layout / operation as those of a dedicated remote control attached to broadcast receiving device 100. Furthermore, power key 741a1, network selection key 741a2, numeric keys 741a3, etc. have the same functions as those of the operation keys of a general television remote control, and detailed description thereof will be omitted. Linked application key 741a9 is an operation key provided for the broadcast / communication linking function of this embodiment.

[0455] In the process of S1107 in Fig. 40B, it is assumed that a request to launch the broadcast linked application launcher can be made by selecting the linked application key 741a9. Also, in the process of S1207 in Fig. 40C, it is assumed that a request to launch data broadcasting can be made by selecting the data key 741a8. Also, in the process of S1109 in Fig. 40B and the process of S1209 in Fig. 40C, it is assumed that the executable broadcast linked application can be selected by operating the cursor keys 741ac and the enter key 741ad.

[0456] In this way, by providing linked application key 741a9 or another operation key having a similar function on basic screen 741a of the linked control application, it becomes possible to easily select / launch each broadcast linked application used in the broadcast linked system of this embodiment. Also, linked application key 741a9 or another operation key having a similar function may be provided on a dedicated remote control attached to broadcast receiving device 100.

[0457] FIG. 42B is a screen display diagram showing an example of the basic screen of the cooperation control application displayed by the process of S1314 in FIG. 41A, the process of S1409 in FIG. 41B, etc., and is an example different from that of FIG. 42A.

[0458] The basic screen 741b of the cooperative control app is composed of a cooperative control in progress message 741b1 and a cooperative control app operation screen 741b2. Other objects may also be displayed. The cooperative control in progress message 741b1 is a message display for notifying the user that the mobile information terminal 700 is operating in cooperation with the broadcast receiving device 100. The cooperative control app operation screen 741b2 is an area where any screen display is performed by the cooperative control app, and detailed description thereof will be omitted in this embodiment. For example, the configuration within the cooperative control app operation screen 741b2 may be the same as the configuration of the basic screen 741a of the cooperative control app described above. A sub-screen of a broadcast program being displayed on the broadcast receiving device 100 may also be displayed.

[0459] 42B, by displaying cooperative control in progress message 741b1, the user of mobile information terminal 700 can easily understand that mobile information terminal 700 is operating in cooperative control with broadcast receiving device 100. Note that cooperative control in progress message 741b1 is not limited to text display, and may be symbol display, graphic display, etc. A different background color, etc. may be used as an alternative to cooperative control in progress message 741b1.

[0460] [Broadcast-linked app launcher screen on broadcast receiving device] FIG. 43A is a screen display diagram showing an example of a notification screen for notifying the user that there is a broadcast cooperative app that can be activated in the broadcast receiving device 100 of this embodiment.

[0461] For example, in the operation sequence shown in Fig. 40B, after the processing of S1106, neither the data broadcast by the broadcast service nor the broadcast-linked app is launched, and the display of the broadcast program video continues. On the other hand, in this case, if an icon 162m0 as shown in Fig. 43A is displayed on the broadcast program screen 162m to notify the user that there is a launchable broadcast-linked app, the usability of the broadcast receiving device 100 is improved. In other words, by displaying the icon 162m0, it is possible to prevent the user from missing the existence of a launchable broadcast-linked app.

[0462] The display position of the icon 162m0 may be any position on the screen, but it is desirable that it be a location that does not interfere with viewing of the broadcast program. For example, it may be one of the four corners of the screen. The display position may be controlled by the description of the LCT. The icon 162m0 may be a character display as shown in FIG. 43A, or may be a symbol, a figure, or the like. The icon 162m0 may be constantly displayed, or may be displayed for a predetermined time after the power is turned on or the channel is changed. Alternatively, the icon 162m0 may be displayed simultaneously with the display of program information, channel number, or the like.

[0463] 43B is a screen display diagram showing an example of a broadcast cooperative app launcher displayed by the processing of S1108 in FIG. 40B. In this embodiment, it is assumed that three broadcast cooperative apps, cooperative app A, cooperative app B, and cooperative app C, are executable on the broadcast receiving device 100 based on the description in the MH-AIT or the like. In this case, a broadcast cooperative app launcher 162n1 is displayed at an arbitrary position on the broadcast program screen 162n, and further, an entry button 162n2 for cooperative app A, an entry button 162n3 for cooperative app B, an entry button 162n4 for cooperative app C, and a back button 162n5 are displayed within the broadcast cooperative app launcher 162n1. The position where the broadcast cooperative app launcher 162n1 is displayed may be controlled by the description in the LCT.

[0464] 43B is displayed, when an entry button 162n2, an entry button 162n3, an entry button 162n4, or the like is selected using the cursor keys 741ac and the enter key 741ad on the basic screen 741a of the cooperative control app, cooperative app A, cooperative app B, cooperative app C, or the like may be launched under the control of the application control unit 153. When the back button 162n5 is selected, the display of the broadcast cooperative app launcher 162n1 may be terminated.

[0465] When the broadcast cooperative application launcher 162n1 is displayed on the broadcast program screen 162n, the frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on the type, security status, etc. of each broadcast cooperative application. For example, if the cooperative application A is a broadcast-managed application, the frame color of the entry button 162n2 may be blue; if the cooperative application B is a non-broadcast-managed application, the frame color of the entry button 162n3 may be yellow; and if the cooperative application C is a general application, the frame color of the entry button 162n4 may be red. Alternatively, if the cooperative application A is determined to be reliable in terms of security, the frame color of the entry button 162n2 may be blue; if the cooperative application B is determined not to be reliable in terms of security, the frame color of the entry button 162n3 may be yellow; and if the cooperative application C is determined to be a security risk, the frame color of the entry button 162n4 may be red.

[0466] In addition, the frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on the function or genre of the broadcast-linked app, or depending on the expiration date of use of each broadcast-linked app, etc. The frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on whether the broadcast-linked app has already been acquired from a network, etc. For example, if the linked app A has already been acquired from a network (cached in cache 152, etc.), the frame color of entry button 162n2 may be blue; if the linked app B is being acquired, the frame color of entry button 162n3 may be yellow; and if the linked app C has not yet been acquired, the frame color of entry button 162n4 may be red, etc.

[0467] In this way, the user of the broadcast receiving device 100 can easily grasp the types of broadcast cooperative apps that can be executed on the broadcast receiving device 100, the security status, and the like.

[0468] Furthermore, the broadcast linked application launcher 162n1 may not be displayed if there is no broadcast linked application that can be executed by the broadcast receiving device 100. Alternatively, in this case, a message such as "There is no available application" may be displayed inside the broadcast linked application launcher 162n1.

[0469] [Data broadcasting screen on broadcast receiving device] Fig. 44 is a screen display diagram showing an example of a data broadcasting screen displayed by the processing of S1208 in Fig. 40C. In this embodiment, it is assumed that three broadcast cooperative applications, i.e., cooperative application A, cooperative application B, and cooperative application C, are executable on the broadcast receiving device 100 based on the description in the MH-AIT, etc. In this case, an entry button 162o2 for cooperative application A, an entry button 162o3 for cooperative application B, and an entry button 162o4 for cooperative application C are displayed at arbitrary positions on the data broadcasting screen 162o. Note that the display positions of the program video 162o1, the entry buttons 162o2 to 162o4, and other content on the data broadcasting screen 162o may be controlled by the description in the LCT after grouping them into areas.

[0470] On the data broadcasting screen 162o as shown in FIG. 44, when the entry button 162o2, entry button 162o3, entry button 162o4, etc. is selected using the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the linked control app, the display of the data broadcasting screen 162o is terminated and linked app A, linked app B, linked app C, etc. may be launched under the control of the application control unit 153.

[0471] When displaying the data broadcasting screen 162o, the frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed appropriately depending on the type and security status of the broadcast-linked app, the function and genre of the broadcast-linked app, the acquisition status of the broadcast app from the network, etc., just as when displaying the entry button of each broadcast-linked app on the broadcast-linked app launcher 162n of Figure 43B.

[0472] In this way, the user of the broadcast receiving device 100 can easily grasp the types of broadcast cooperative apps that can be executed on the broadcast receiving device 100, the security status, and the like.

[0473] [Broadcast linkage app execution screen on broadcast receiving device] FIG. 45A is a screen display diagram showing an example of a broadcast cooperative app execution screen displayed in the process of S1018 in FIG. 40A, the process of S1119 in FIG. 40B, the process of S1220 in FIG. 40C, etc. The broadcast cooperative app of this embodiment is equipped with graphics capabilities and effect capabilities based on HTML5 description, and is capable of overlay display with a broadcast program screen on the monitor unit 162. For example, as shown in FIG. 45A, a broadcast cooperative app unit 162p1 that displays information such as a weather forecast and news is overlaid and displayed at an arbitrary position on the broadcast program screen 162p. The display position of the broadcast cooperative app unit 162p1 may be controlled by the description of the LCT. The broadcast cooperative app unit 162p1 is composed of a first main object 162p2, a second main object 162p3, a third main object 162p4, and a background object 162p5, etc. Other objects may also be displayed.

[0474] When the broadcast cooperative app section 162p1 is overlaid on the broadcast program screen 162p, the execution of the broadcast cooperative app can be terminated and the display can be switched to a data broadcast screen by selecting the data key 741a8 on the basic screen 741a of the cooperative control app. Furthermore, the execution of the broadcast cooperative app can be terminated and the display can be switched back to the broadcast program screen 162p by selecting the cooperative app key 741a9 on the basic screen 741a of the cooperative control app. The above process may be realized by using a different operation key.

[0475] In addition, while the broadcast cooperative application section 162p1 is overlaid on the broadcast program screen 162p, the transparency of the broadcast cooperative application section 162p1 can be changed by operating each operation key on the basic screen 741a of the cooperative control application. The transparency change process may be performed collectively for the entire broadcast cooperative application section 162p1, or may be performed individually for the first main object 162p2, the second main object 162p3, the third main object 162p4, and the background object 162p5. It may also be performed for each predetermined group (for example, multiple objects existing on the same graphics layer).

[0476] When performing the transparency change process, for example, an object is selected using cursor keys 741ac on the basic screen 741a of the collaboration control app, and the transparency of the object is increased by pressing the "blue" key on color keys 741ae and decreased by pressing the "yellow" key. The transparency change process may also be performed using different operation keys. The broadcast collaboration app unit 162p1 can be temporarily hidden by setting the entire broadcast collaboration app unit 162p1 to 100% transparency. For example, when an emergency broadcast is distributed via broadcast waves, the entire broadcast collaboration app unit can be set to 100% transparency, and only the broadcast program screen of the emergency broadcast can be displayed on the monitor unit 162. Alternatively, a commercial detection unit (not shown) may detect that the broadcast program has switched from the main video to a commercial video and control the entire broadcast collaboration app unit 162p1 to 100% transparency (or a transparency that allows the broadcast program video to be clearly seen).

[0477] When the display control of the broadcast cooperative application unit 162p1 is performed by the description of the LCT, the broadcast cooperative application unit 162p1 may be temporarily hidden by controlling the "layer_order" parameter of the broadcast cooperative application unit 162p1 and moving the broadcast cooperative application unit 162p1 behind the broadcast program screen 162p. In this case, the video display state on the monitor unit 162 will be the same as when the entire broadcast cooperative application unit 162p1 is collectively set to a transparency of 100%.

[0478] By performing the above-described processing, if you want to check the broadcast program screen in the background while the broadcast linked app is running, you can check the broadcast program screen without terminating the broadcast linked app.

[0479] FIG. 45B is a screen display diagram showing an example of the broadcast cooperative app execution screen displayed in the process of S1018 in FIG. 40A, the process of S1119 in FIG. 40B, the process of S1220 in FIG. 40C, etc., different from the above. In the example shown in FIG. 45B, a broadcast cooperative app section 162p6 introducing recommended programs is overlaid and displayed at an arbitrary position on the broadcast program screen 162p. The display position of the broadcast cooperative app section 162p6 may be controlled by the description of the LCT. The broadcast cooperative app section 162p6 displays first recommended program information 162p7, second recommended program information 162p8, third recommended program information 162p9, etc. More recommended program information may be displayed by scrolling, page switching, etc.

[0480] The recommended program information may be information on a program recommended in relation to the currently displayed broadcast program (broadcast program screen 162p), information on a program recommended based on the user's viewing history, or information on a program that is currently a hot topic on the Internet, etc. It may also be information on a recommended program sent to the user by a friend of the user of the broadcast receiving device 100. The recommended program may also be a program transmitted by broadcast waves of a digital broadcast service, or a VOD (Video On Demand) program distributed from a server device on the Internet 200. It may also be an information screen such as a homepage prepared on a server device on the Internet 200.

[0481] When the broadcast linked application section 162p6 is overlaid on the broadcast program screen 162p, the first recommended program information 162p7, the second recommended program information 162p8, the third recommended program information 162p9, etc. can be selected using the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the linked control application, and the images of each program recommended by these can be displayed on the monitor section 162.

[0482] Needless to say, the transparency of the broadcast cooperative application section 162p6 may also be changed on the broadcast cooperative application execution screen shown in FIG. 45B in the same manner as described above.

[0483] FIG. 45C is a screen display diagram illustrating an example in which a program video recommended by the broadcast cooperative application section 162p6 that introduces recommended programs is displayed. For example, when first recommended program information 162p7 of the broadcast cooperative application section 162p6 is selected using the cursor keys 741ac and the enter key 741ad on the basic screen 741a of the cooperative control application, a program video 162pa of the program recommended by the first recommended program information 162p7 is displayed on the monitor unit 162. The program video 162pa may be paused or jumped to by a specified time by a user operating the operation terminal. Furthermore, when displaying the program video 162pa, the original broadcast program screen 162p may be displayed at an arbitrary position in a PIP (Picture In Picture) format or the like. The display position of the original broadcast program screen 162p in the PIP format or the like may be controlled by the description of the LCT. In this case, the user may be able to change whether the program video 162pa of the recommended program or the original broadcast program screen 162p is the main screen by operating the operation terminal. The size of the window of the original broadcast program screen 162p may be adjusted by the user's operation on the operation terminal.

[0484] Furthermore, by displaying an icon display 162pb at any position on the screen, which indicates that the program video 162pa of the recommended program is a video that was displayed as a result of selecting any of the recommended program information displayed in the broadcast-linked application section 162p6, user convenience can be improved.

[0485] FIG. 45D is a screen display diagram showing an example of a broadcast cooperative app execution screen different from those described above, which is displayed in the process of S1018 in FIG. 40A, the process of S1119 in FIG. 40B, the process of S1220 in FIG. 40C, etc. In the example shown in FIG. 45D, a broadcast cooperative app unit 162pc, which serves as a portal for an SNS (Social Networking Service) service, is overlaid and displayed at an arbitrary position on a broadcast program screen 162p. The display position of the broadcast cooperative app unit 162pc may be controlled by the description of the LCT. The broadcast cooperative app unit 162pc displays an entry button 162pd for a first SNS service, an entry button 162pe for a second SNS service, an entry button 162pf for a third SNS service, etc. Entry buttons for even more SNS services may be displayed by scrolling, page switching, etc.

[0486] With the broadcast cooperative application section 162pc overlaid on the broadcast program screen 162p, by using the cursor keys 741ac and the enter key 741ad on the basic screen 741a of the cooperative control application to select the entry button 162pd of the first SNS service, the entry button 162pe of the second SNS service, the entry button 162pf of the third SNS service, or the like, functions assigned to each entry button, such as a chat function, a bulletin board function, or an Internet telephone function, are enabled. This allows users to enjoy the currently displayed broadcast program (broadcast program screen 162p) while exchanging information with others. At the same time, the basic screen 741a of the cooperative control application on the mobile information terminal 700 may be changed to a character input screen such as a software key...

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 recording reservation step for reserving a recording of a broadcast program from the EPG screen; a storage step of storing the broadcast program content received in the receiving step for the broadcast program reserved for recording in the recording reservation step; an output step of outputting the broadcast program content stored in the storage step to an external device; a copy processing step of copying the broadcast program content stored in the storage step to an external device; a move processing step of moving the broadcast program content stored in the storage step to an external device; Equipped with The EPG screen displays the program names and attributes of the broadcast programs, In the storing step, when the broadcast program content received in the receiving step is content for which protection allowing copying a predetermined number of times is designated, the broadcast program content stored in the storing step is stored in a state in which it can be copied nine times in the copy processing step and moved once in the move processing step, and in which it has been encrypted so as to be reproducible only by the broadcast receiving device; In the storing step, when the broadcast program content received in the receiving step is content that can be copied without restriction and is designated for protection by encryption, the broadcast program content stored in the storing step is stored in a state in which the broadcast program content has been encrypted 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 in the storage step, the output of the broadcast program content to the external device in the output step, the copying of the broadcast program content to the external device in the copy processing step, and the moving of the broadcast program content to the external device in the move processing step can all be performed via the same IP interface configured with Ethernet-compatible hardware, The output of the broadcast program content to the external device in the output step can be performed by the IP interface configured with hardware compatible with Ethernet, as well as by HDMI. Content protection processing method.

Images