Content protection processing method
The MMT system enhances television receivers with advanced functionalities by using MPEG-H HEVC and MPEG-4 AAC encoding, along with MMT-SI and TLV-SI control information, addressing the limitations of existing receivers in broadband environments and high-definition content distribution.
Patent Information
- Application Number
- JP2024135786
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-15
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2035-11-24
AI Technical Summary
Existing television receivers struggle to provide high-value-added functions, particularly in the context of broadband network environments, higher resolution, and higher definition video content distribution, by simply reusing or expanding data broadcasting reception functions.
A content protection processing method utilizing the MMT (MPEG Media Transport) system for enhanced media transport, including MPEG-H HEVC for video encoding, MPEG-4 AAC or ALS for audio encoding, and MMT-SI and TLV-SI control information for efficient data transmission and synchronization across various transmission paths.
Enables advanced functionalities such as multi-view compatible programs, emergency warning broadcasts, and cooperative applications between television receivers and mobile information terminals, with improved synchronization and data management.
Smart Images

Figure 2024164092000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a content protection processing method. [Background technology]
[0002] One of the expansion functions of the digital broadcasting service 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] JP 2001-186486 A Summary of the Invention [Problem to be solved by the invention]
[0004] In response to recent changes in the content distribution environment, television receivers are also being required to have various functional extensions. In particular, there are many demands for the distribution of content and associated applications using broadband network environments such as the Internet, and for higher resolution / definition video content. However, it is difficult to provide a television receiver with high added value that can meet the demands by only utilizing the data broadcasting reception function and the like that is provided in current television receivers, or by only extending the function of the data broadcasting reception function and the like.
[0005] An object of the present invention is to realize a content protection processing method capable of executing functions with higher added value. [Means for solving the problem]
[0006] As a means for solving the above problems, the technology described in the claims is used. Effect of the Invention
[0007] By using the technology of the present invention, it is possible to realize a content protection processing method capable of executing functions with higher added value. [Brief description 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 showing the configuration of an MPU in MMT. [Figure 2C] FIG. 1 is a diagram showing the structure of an MMTP packet in MMT. [Diagram 3] FIG. 1 is a conceptual diagram of a protocol stack for a broadcasting system using MMT. [Figure 4] FIG. 2 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 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 the components of a broadcasting system and each table. [Figure 7B]A diagram showing the data structure of the MPT of the broadcasting system. [Figure 7C] 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 in a broadcasting system. [Figure 7E] A diagram showing the data structure of the MH-EIT of the broadcasting system. [Figure 7F] A diagram showing 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] 2 is a configuration diagram of a logical plane structure of a presentation function of the broadcast receiving device according to the first embodiment. FIG. [Figure 8C] 2 is a software configuration diagram of the broadcast receiving device according to the first embodiment. [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. 2 is a block diagram of a portable information terminal according to the 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] 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] A diagram showing the format of the JST_time parameter of a broadcasting system. [Figure 12E] A diagram showing the data structure of time information in the TMCC extended information area of a broadcasting system. [Figure 12F] 11 is a diagram illustrating a method of calculating the current date from the MJD of the broadcast receiving device in accordance with the first embodiment. FIG. [Figure 13A]FIG. 4 is an operational sequence diagram during channel scanning of the broadcast receiving device according to the first embodiment. [Figure 13B] A diagram showing the data structure of the TLV-NIT of a broadcasting system. [Figure 13C] A diagram showing the data structure of a satellite distribution system descriptor of a broadcasting system. [Figure 13D] A diagram showing the data structure of a service list descriptor for a broadcasting system. [Figure 13E] A diagram showing the data structure of AMT of a broadcasting system. [Figure 14A] 4 is a diagram showing an operation sequence when the broadcast receiving device according to the first embodiment selects a channel. FIG. [Figure 14B] A conceptual diagram explaining reference to the MPT of each package by the PLT of a broadcasting system. [Figure 14C] A diagram showing the data structure of a PLT for a broadcasting system. [Figure 15A] 1 is an external view of a remote control capable of controlling a broadcast receiving device in accordance with a first embodiment. [Figure 15B] A diagram showing the data structure of a remote control key descriptor for a broadcasting system. [Figure 16A] FIG. 10 is a diagram illustrating a process of selecting multiple channels. [Figure 16B] FIG. 11 is a diagram illustrating an 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] A diagram showing the data structure of an MPU presentation area designation descriptor for a broadcasting system. [Figure 17C] FIG. 13 illustrates the assignment of layouts to layout numbers based on the LCT. [Figure 17D] FIG. 13 illustrates the assignment of layouts to layout numbers based on the LCT. [Figure 17E] FIG. 13 illustrates the assignment of layouts to layout numbers based on the LCT. [Figure 17F] FIG. 13 illustrates the assignment of layouts to layout numbers based on the LCT. [Figure 18A] 11A and 11B are diagrams for explaining exception handling of screen layout control based on LCT. [Figure 18B] 11A and 11B are diagrams for explaining exception handling of screen layout control based on LCT. [Figure 19A] A diagram showing the data structure of a video component descriptor for a broadcasting system. [Figure 19B] 13 is a diagram for explaining the meaning of the video signal aspect ratio of the video component descriptor. FIG. [Figure 19C] 4 is a diagram for explaining the aspect ratio conversion process of the broadcast receiving device according to the first embodiment. FIG. [Figure 19D] 4 is a diagram for explaining the aspect ratio conversion process of the broadcast receiving device according to the first embodiment. FIG. [Figure 20A] 4 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 20B] 4 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 20C] 4 is a screen display diagram of an EPG screen of the broadcast receiving device according to the first embodiment. FIG. [Figure 21] 4 is a screen display diagram of the broadcast receiving device according to the first embodiment when an emergency alert broadcast is displayed. FIG. [Figure 22A] A diagram showing the data structure of a content copy control descriptor for a broadcasting system. [Figure 22B] FIG. 13 is a diagram showing the meaning of copy control information in a content copy control descriptor. [Figure 23] A diagram showing the data structure of a content usage control descriptor for a broadcasting system. [Figure 24] FIG. 11 is a block diagram of a broadcast receiving device according to a second embodiment. [Diagram 25] 11A and 11B are diagrams illustrating inconsistencies in the current time display when switching broadcast services. [Figure 26A] FIG. 11 is a diagram illustrating an operation of current time information reference source selection control according to the second embodiment. [Figure 26B] FIG. 11 is an operation sequence diagram of an update process of current time information according to the second embodiment. [Figure 27A] FIG. 11 is a screen display diagram of an EPG screen of a broadcast receiving device according to a second embodiment. [Figure 27B] FIG. 11 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. 1 is a diagram showing types of assets. [Figure 30A] FIG. 13 is a diagram showing a data structure of location information of an asset acquisition destination. [Figure 30B] FIG. 13 is a diagram showing the meaning of the types of asset acquisition destinations. [Diagram 31] 13 is a diagram illustrating the data structure of an MPU presentation area designation descriptor. [Figure 32A] A diagram showing the data structure of MH-AIT. [Figure 32B] FIG. 13 is a diagram illustrating the allocation of application types. [Figure 32C] FIG. 13 is a diagram showing the definition of an application control code. [Fig. 32D] FIG. 13 illustrates a data structure of an application identifier. [Diagram 33] A diagram showing the data structure of an MH-application descriptor. [Figure 34A] A diagram showing the data structure of an MH-transmission protocol descriptor. [Figure 34B] FIG. 13 is a diagram illustrating the meaning of protocol identification. [Figure 34C] FIG. 13 is a diagram showing the data structure of a selector area. [Diagram 35] A diagram showing the data structure of an MH-simple application location descriptor. [Diagram 36] A diagram showing the data structure of an MH-application boundary authority setting descriptor. [Figure 37] A diagram showing the data structure of an MH-startup priority information descriptor. [Figure 38A] 13 is a diagram showing the data structure of an MH-cache information descriptor. [Figure 38B]13 is a diagram showing the data structure of an MH-application validity period descriptor. [Figure 39] A diagram showing 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 portable information terminal according to the third embodiment cooperates with one another. [Figure 41B] FIG. 11 is an operational sequence diagram when the portable 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 screen display diagram of a broadcast cooperative application launcher of a broadcast receiving device according to a third embodiment. [Diagram 44] FIG. 11 is a screen display diagram of a data broadcast screen of the broadcast receiving device according to the third embodiment. [Figure 45A] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the third embodiment. [Figure 45B] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the third embodiment. [Figure 45C] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the third embodiment. [Figure 45D]FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the third embodiment. [Diagram 46] FIG. 11 is a screen display diagram of an error display screen of the broadcast receiving device according to the third embodiment. [Figure 47] FIG. 11 is a screen display diagram of a broadcast cooperative application execution screen of a portable information terminal according to a third embodiment. [Figure 48A] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Figure 48B] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Figure 48C] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Figure 48D] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Figure 48E] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Fig.48F] 13 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to Example 3. FIG. [Figure 49A] 13 is an operational sequence diagram of a broadcast receiving device according to a third embodiment when acquiring a broadcast cooperative application. FIG. [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] A diagram showing the data structure of an MH-application descriptor. [Figure 51A] FIG. 13 is an operational sequence diagram during terminal cooperation according to the fourth embodiment. [Figure 51B] FIG. 13 is an operational sequence diagram during terminal cooperation according to the fifth embodiment. [Figure 51C] FIG. 23 is an operational sequence diagram during terminal cooperation according to the sixth embodiment. [Fig. 51D] FIG. 23 is an operational sequence diagram during terminal cooperation according to the sixth embodiment. [Figure 52A] FIG. 13 is a screen display diagram of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52B]FIG. 13 is a screen display diagram of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52C] FIG. 13 is a screen display diagram of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Fig. 52D] FIG. 13 is a screen display diagram of a broadcast cooperative application launcher of a broadcast receiving device according to a seventh embodiment. [Figure 52E] FIG. 13 is a screen display diagram of a broadcast receiving device according to a seventh embodiment. [Fig. 52F] FIG. 13 is a screen display diagram of a broadcast cooperative application of a portable information terminal according to a seventh embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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, an antenna 100a, a broadband network such as the Internet 200, a router device 200r, an access point 200a, a radio tower 300t of a broadcast station, a broadcast satellite (or a communication satellite) 300s, a broadcast station server 300, a service provider server 400, other application servers 500, a mobile telephone communication server 600, a base station 600b of a mobile telephone communication network, and a mobile information terminal 700.
[0011] The broadcast receiving device 100 receives broadcast waves transmitted from a radio tower 300t via a broadcast satellite (or communication satellite) 300s and an antenna 100a. Alternatively, the broadcast waves transmitted from the radio tower 300t may be received directly from the antenna 100a without passing through the broadcast satellite (or communication satellite) 300s. The broadcast receiving device 100 can also be connected to the Internet 200 via a router device 200r, and can transmit and receive data by communicating with each server device on the Internet 200 and other communication devices.
[0012] The router device 200r is connected to the Internet 200 by wired communication, and is connected to the broadcast receiving device 100 by wired communication or wireless communication, and to the mobile information terminal 700 by wireless communication. The wireless communication may use a method such as Wi-Fi (registered trademark). This allows each server device on the Internet 200 and other communication devices 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 the 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, and the like. The broadcasting satellite (or communication satellite) 300s is a repeater that receives broadcast waves transmitted from the radio tower 300t of the broadcasting station, performs appropriate frequency conversion, 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 is assumed to store broadcast programs (video content, etc.) and metadata of each broadcast program, such as program title, program ID, program summary, performer information, broadcast date and time, and to provide 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 through an API (Application Programming Interface) provided in the broadcasting station server 300.
[0014] The service provider server 400 is a server device prepared by a service provider, and is capable of providing various services linked to broadcast programs distributed from a broadcast station. The service provider server 400 also stores, manages, and distributes video content and metadata provided by the broadcast station server 300, and various content and applications linked to broadcast programs. The service provider server 400 also has a function of searching for and providing a list of available content and applications in response to inquiries from a television receiver or 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. A plurality of service provider servers 400 may be prepared for each different service. The broadcast station server 300 may also have the function of the service provider server 400.
[0015] The other application servers 500 are known server devices that store, manage, and distribute other general applications, operating programs, content, data, etc. There may be a plurality of other application servers 500 on the Internet 200.
[0016] The mobile telephone communication server 600 is connected to the Internet 200, and is also connected to the mobile information terminal 700 via a base station 600b. The mobile telephone communication server 600 manages telephone communication (calls) and data transmission / reception of the mobile information terminal 700 via the mobile telephone communication network, and enables data transmission / reception by communication between the mobile information terminal 700 and each server device on the Internet 200 and other communication devices. The communication between the base station 600b and the mobile information terminal 700 may be performed by a W-CDMA (Wideband Code Division Multiple Access) (registered trademark) system, a GSM (Global System for Mobile communications) (registered trademark) system, a LTE (Long Term Evolution) system, or other communication system.
[0017] The mobile information terminal 700 has a function of telephone communication (call) and data transmission / reception via a mobile telephone communication network, and a function of wireless communication by Wi-Fi (registered trademark) or the like. The mobile information terminal 700 can be connected to the Internet 200 via the router device 200r or the 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 by communication with each server device on the Internet 200 and other communication devices. The access point 200a is connected to the Internet 200 by wired communication, and is connected to the mobile information terminal 700 by wireless communication. The wireless communication may use a method such as Wi-Fi (registered trademark). The 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] [Outline of the MMT method] The broadcast receiving device 100 shown in Fig. 1 is a television receiver that is compatible with MMT (MPEG Media Transport) instead of 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 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. As the clock is also 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, there has been a diversification of content, diversification of devices that use content, diversification of transmission paths for distributing content, diversification of content storage environments, and other changes in the content distribution environment. As a result, MPEG2-TS has limitations in its functionality. Therefore, a new media transport method, MMT, has been established.
[0020] An example of an outline of an encoded signal in the MMT of this embodiment is shown in Fig. 2A. As shown in the figure, the MMT of this embodiment has an MFU (Media Fragment Unit), an MPU (Media Processing Unit), an MMTP (MMT Protocol) payload, and an MMTP packet as elements constituting the encoded signal.
[0021] The MFU is a format for transmitting video and audio, and may be configured in NAL (Network Abstraction Layer) unit units or access unit units. The MPU includes one or more access units, and is capable of performing video and audio decoding processing by itself. The MPU may be configured with MPU metadata including information on the overall configuration of the MPU, movie fragment metadata including information on encoded media data, and sample data which is encoded media data. One MPU may have multiple movie fragment data and sample data. Also, it is assumed that the MFU can be extracted from the sample data. FIG. 2B shows an example of the configuration of an MPU. Note that by adding 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 sequence number of the MPU. Also, in the case of media such as video components and audio components, the presentation time and the decoding time may be specified in MPU units or access unit units.
[0022] An MMTP packet is composed of a header section and an MMTP payload, and transmits MFU and MMT control information. The MMTP payload is equipped with a payload header according to the contents (data unit) stored in the payload section. FIG. 2C shows an example of an overview of constructing an MFU from a video / audio signal, storing it in an MMTP payload, and constructing an MMTP packet. For video signals that are encoded using interframe prediction, it is desirable to configure MPUs in GOP (Group Of Pictures) units. 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. If the size of the MFU to be transmitted is large, one MFU may be divided and stored in multiple payload sections. In addition, the MMTP packet may be protected using a technique such as AL-FEC (Application Layer Forward Error Correction) or ARQ (Automatic Repeat Request) to recover 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 coding method, and MPEG-4 AAC (Advanced Audio Coding) or MPEG-4 ALS (Audio Lossless Coding) is used as the audio coding method. The coded data of the video and audio of the broadcasting program coded by each of the above methods is in MFU or MPU format, and is further loaded on the MMTP payload to be packetized as MMTP packets and transmitted in IP (Internet Protocol) packets. Data content related to the broadcasting program may also be in MFU or MPU format, and further loaded on the 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 / text superimposition 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. In addition, the TLV (Type Length Value) multiplexing method is used on the broadcast transmission path for efficient transmission of IP packets. An example of a protocol stack for the broadcasting 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] In the broadcasting system of this embodiment, a mechanism for transmitting two types of control information, MMT-SI (MMT-Signaling Information) and TLV-SI (TLV-Signaling Information), is provided. 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 correspondence information between IP addresses and services.
[0026] In addition, in broadcasting systems using MMT, time information is also 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. IP packets in NTP (Network Time Protocol) format are used to provide UTC.
[0027] [Control information for broadcasting systems using MMT] In the broadcast system compatible with the broadcast receiver 100 of the present embodiment, as described above, as control information, TLV-SI related to the TLV multiplexing method for multiplexing IP packets and MMT-SI related to MMT which is a media transport method are prepared. TLV-SI provides information for the broadcast receiver 100 to demultiplex the IP packets multiplexed on the broadcast transmission path. TLV-SI is composed of a "table" and a "descriptor". The "table" is transmitted in section format, and the "descriptor" is arranged within the "table". MMT-SI is transmission control information indicating information related to the configuration of MMT packages and broadcast services. MMT-SI is composed of three layers: a "message" storing a "table" and a "descriptor", a "table" having elements and attributes indicating specific information, and a "descriptor" indicating more detailed information. An example of the hierarchical configuration of the control information used in the broadcast system of the present embodiment is shown in FIG. 4.
[0028] FIG. 5A shows a list of "tables" used in TLV-SI of the broadcast system compatible with the broadcast receiver 100 of the present embodiment. In the present embodiment, the following are used as the "tables" of TLV-SI.
[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 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] <Descriptors used in TLV-SI> Fig. 5B shows a list of "descriptors" arranged in the TLV-SI of the broadcast system corresponding to the broadcast receiving apparatus 100 of the present embodiment. In the present embodiment, the following are used as the "descriptors" of the 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 using 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 descriptors independently set by a service provider or the like.
[0039] <Messages used in MMT-SI> Fig. 6A shows a list of "messages" used in the MMT-SI of the broadcast system corresponding to the broadcast receiving apparatus 100 of the present embodiment. In the present embodiment, the following are used as the "messages" of the 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) Messages 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 receiving apparatus 100 of the present embodiment. The table is control information having elements and attributes indicating specific information, and is to be stored in a message and transmitted in an MMTP packet. Note that the message storing the table may be determined according to the table. In the present 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) indicates a list of IP data flows and packet IDs that transmit PA messages of MMT packages provided as broadcast services, and 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. The LCT 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 a descriptor for identifying a conditional access method. The CAT (MH) may be stored in a CA message.
[0053] (7)DCM The Download Control Message (DCM) transmits key-related information including a key for decrypting a transmission line 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 an M2 section message.
[0055] (9)MH-EIT The MH-Event Information Table (MH-EIT) is time-series information on events included in each service. The MH-EIT may be stored in an M2 section message.
[0056] (10)MH-AIT The MH-Application Information Table (MH-AIT) stores all information about the application and the required activation state of the application, etc. The MH-AIT may be stored in the M2 section message.
[0057] (11)MH-BIT The MH-BIT (MH Broadcaster Information Table) is used to present information about broadcasters present on the network. The MH-BIT may be stored in an M2 section message.
[0058] (12)MH-SDTT The MH-Software Download Trigger Table (MH-SDTT) is used for download notification information. The MH-SDTT may be stored in the M2 section message.
[0059] (13)MH-SDT The MH-Service Description Table (MH-SDT) has sub-tables that represent services included in a specific TLV stream, and transmits information about the organization channel, such as the organization channel name, the broadcaster name, etc. The MH-SDT may 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 Date) information. The MH-TOT may 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 to be stored in non-volatile memory in section format 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 configure an application in order to separate the file structure of the application from the structure for file transmission. The DDM table may be stored in a data transmission message.
[0063] (17) DAM table The Data Asset Management Table (DAM table) provides the configuration of MPUs in an 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 the configuration information of files as data content in order to achieve flexible and effective cache control. The DCC table may be stored in the data transmission message.
[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 the "descriptors" arranged in the MMT-SI of the broadcast system corresponding to the broadcast receiving apparatus 100 of the present embodiment. The 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 the present embodiment, the following are used as the "descriptors" of the 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 the MPT.
[0069] (2) Event Package Descriptor The Event Package Descriptor provides the correspondence between the event representing the program and the package. 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 IDs of the dependent assets. 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 may 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 scheme descriptor provides information for identifying a message authentication scheme when performing message authentication. The message authentication scheme descriptor may 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 ISO / IEC 14496-3 (MPEG-4 Audio) audio stream. The MH-MPEG-4 Audio Descriptor may 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 the coding method specific settings. The MH-MPEG-4 Audio Extension Descriptor may be placed in the MPT.
[0080] (13) MH-HEVC Video Descriptor The MH-HEVC video descriptor is used to describe basic coding parameters of a video stream (HEVC stream) of ITU-T Recommendation H.265|ISO / IEC 23008-2. The MH-HEVC video descriptor may 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 the events. 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 type. The MH-Service List Descriptor may be located in the MH-BIT.
[0084] (17)MH-Short Form Event Descriptor The MH-ShortEventDescriptor represents the event name and a short description of the event in text form. The MH-ShortEventDescriptor can be placed in the MH-EIT.
[0085] (18) MH-Extended Event Descriptor The MH-ExtendedEventDescriptor is used in addition to the MH-ShortEventDescriptor to provide a detailed description of the event. The MH-ExtendedEventDescriptor 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 a text format. The video component descriptor may be placed in the MPT or the 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 refer to the description indicated by the video component descriptor in the MH-EIT by 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-Parental Rating Descriptor is used to indicate age-based viewing restrictions and to extend to other restriction conditions. The MH-Parental Rating Descriptor may 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 character form. 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. The MH-series descriptor 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. The MH-SI transmission parameter descriptor 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 expresses the organization channel name and its operator name 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 constitute a service. The IP data flow descriptor can be placed in the MH-SDT.
[0097] (30)MH-CA startup descriptor The MH-CA start descriptor describes start information for starting a CAS program on the CAS platform. The MH-CA start descriptor may 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 may 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 time 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 may be placed in the DAM table.
[0102] (35) MH-Data Encoding Method Descriptor The MH-Data-Encoding Descriptor is used to identify a data encoding scheme. The MH-Data-Encoding Descriptor may 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. The event message descriptor can be located in the EMT.
[0105] (38)MH-Local Time Offset Descriptor The MH-Local Time Offset Descriptor is used when daylight saving time is implemented, to give a certain offset value to the actual time (e.g., UTC+9 hours) and the display 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 a combination of components within an event. The MH-component group descriptor 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 extension timestamp descriptor provides the decoding time of an access unit in the MPU. The MPU extension 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 the 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. The MH-application descriptor 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 may be placed in the MH-AIT.
[0114] (47)MH-Application Boundary Authority Setting Descriptor The MH-application boundary authority setting descriptor is described to set an application boundary and to set authority of broadcast resource access 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 for use in cache control when the resources constituting an application are cached and held 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 probabilistically set 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 arranged 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 arranged in the DCC table.
[0121] (54)MH-Download Protection Descriptor The MH-download protection descriptor describes location information and transmission information of an MMTP packet that transmits a 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 an application related to a 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 a 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 information about copying or the maximum transmission rate to a digital recording device when digital recording is assumed to be performed. 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 or 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 the present 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 the present embodiment, data transmission can be performed through a plurality of paths such as a TLV stream via a broadcast transmission path or an IP data flow via a communication line. The TLV stream includes TLV-SI such as TLV-NIT and AMT, and an IP data flow which is a data flow of IP packets. The IP data flow includes a video asset including a series of video MPUs and an audio asset including a series of audio MPUs. Similarly, the IP data flow may include a subtitle asset including a series of subtitle MPUs, a character super asset including a series of character super MPUs, a data asset including a series of data MPUs, and the like.
[0131] These various assets are associated with a "package" by the description of 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 the package may be only assets in the TLV stream, but may also include assets transmitted in the IP data flow of the communication line, as shown in Fig. 7A. This can be achieved by describing the location information of each asset included in the package together with an asset ID that identifies the asset in the MPT, so that the broadcast receiving device 100 of this embodiment can 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 Fig. 7B. An example of the data structure of location information is shown in Fig. 7C.
[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 flows (location_type=0x01) (3) Data multiplexed in IPv6 data flows (location_type=0x02) (4) Data multiplexed into the 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] Among the above-mentioned reference destinations, (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, when the MPT is also included in the IP data flow on the communication line side and transmitted, the reference destination of (1) may be the IP data flow received via the communication line. Also, the above (2), (3), (5), and (6) are IP data flows received by the broadcast receiving device 100 of this embodiment via the communication line. Also, the above (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 method and a receiving function for receiving digital broadcast signals using the MPEG2-TS method, such as the broadcast receiving device 800 of the second embodiment described later, when referring to data multiplexed in the MPEG2-TS received by the receiving function for receiving digital broadcast signals using the MPEG2-TS method based on the location information of the MPT included in the digital broadcast signal using the MMT method.
[0135] In addition, for media such as video components and audio components, the presentation time and decode time can be specified in MPU units or access unit units. Information on the presentation time and decode time is described in the MPT as an MPU timestamp descriptor or an MPU extended timestamp descriptor. FIG. 7D shows an example of a data structure of an MPU timestamp descriptor describing information on the presentation time. Presentation time information of 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. In the broadcast receiving device 100 of this embodiment, the presentation time information can be used to present (display, output, etc.) multiple MPUs specified by the MPT in conjunction with each other based on a clock based on NTP, which is time information in UTC notation. Information on the decode time is also described by an MPU extended timestamp descriptor, but detailed description will be omitted. Note that the presentation control of various data using the clock based on the NTP will be described later.
[0136] In the broadcasting system of this embodiment, a series of data in units of the "package" corresponds to a "service" of digital broadcasting. Moreover, the "service" is a series of "programs" transmitted according to a schedule. The "programs" are treated as "events" in the MMT method. The start time and duration of each event are specified by the MH-EIT. Moreover, the ID of the MMT package to which each event corresponds is specified by the event package descriptor placed in the MH-EIT. FIG. 7E shows an example of the data structure of the MH-EIT. The start time is specified by the "start_time" parameter in the figure, and the duration is specified by the "duration" parameter. FIG. 7F shows an example of the data structure of the event package descriptor. The correspondence between each event and an MMT package can be specified by the "MMT_package_id_byte" parameter of the event package descriptor placed in the MH-EIT. The MH-EIT can be used for various processes in units of the "events" in the broadcast receiving device 100 of this embodiment (for example, generation of an electronic program guide, control of recording and viewing reservations, copyright management processes such as temporary storage, etc.).
[0137] [Hardware configuration of broadcast receiving device] 8A is a block diagram showing an example of the internal configuration of the broadcast receiving device 100. The broadcast receiving device 100 is composed of a main control unit 101, a system bus 102, a ROM 103, a RAM 104, a storage (accumulation) unit 110, a LAN communication unit 121, an extension interface unit 124, a digital interface unit 125, a tuner / demodulation unit 131, a separation unit 132, a video decoder 141, a video color gamut conversion unit 142, an audio decoder 143, a superimposed text decoder 144, a subtitle decoder 145, a subtitle synthesis unit 146, a subtitle color gamut conversion unit 147, a data decoder 151, a cache unit 152, an application control unit 153, a browser unit 154, an application color gamut conversion unit 155, a sound source unit 156, a video synthesis unit 161, a monitor unit 162, a video output unit 163, an audio synthesis unit 164, a speaker unit 165, an audio output unit 166, and an 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 in the broadcast receiving device 100.
[0139] The ROM (Read Only Memory) 103 is a non-volatile memory in which a basic operation program such as an operating system and other operation programs are stored, and a rewritable ROM such as an EEPROM (Electrically Erasable Programmable ROM) or a flash ROM is used. The ROM 103 may 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 program 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 part of the storage area in the storage (accumulation) unit 110.
[0140] The storage (accumulation) unit 110 stores the operation program 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 operation programs downloaded via the Internet 200 and various data created by the operation programs. It can also store content such as moving images, still images, and audio acquired from broadcast waves or downloaded via the Internet 200. A part of the area of the storage (accumulation) unit 110 may replace all or part of the functions of the ROM 103. The storage (accumulation) unit 110 needs to hold the stored information even when power is not supplied from the outside to the broadcast receiving device 100. Therefore, for example, devices such as non-volatile semiconductor element memories such as flash ROM and SSD (Solid State Drive), magnetic disk drives such as HDD (Hard Disk Drive), etc. are used.
[0141] It should be noted that the operation programs stored in the ROM 103 and the 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 of it) of a program transmitted via a communication line. The connection to 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, and the like. The broadcast receiving device 100 may further include other communication units such as a BlueTooth (registered trademark) communication unit, an NFC communication unit, and 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) 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 obtain 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 tuners / demodulators for the purpose of simultaneous display of multiple screens, recording of a counter program, etc.
[0144] The separation unit 132 is an MMT decoder, and distributes the video data string, audio data string, superimposed text data string, subtitle data string, etc., which are real-time presentation elements, to the video decoder 141, audio decoder 143, superimposed text data string, subtitle data string, etc., based on a control signal in the input MMT data string. The data input to the separation unit 132 may be an MMT data string transmitted via a broadcast transmission path and demodulated by the tuner / demodulator unit 131, or an MMT data string transmitted via a communication line and received by the LAN communication unit 121. The separation unit 132 also reproduces a multimedia application and file-based data, which is a component of the application, and temporarily stores the data in the cache unit 152. The separation unit 132 also extracts general-purpose data and outputs it to the data decoder 151 in order to use the data for streaming to the data or application used by a player that presents data other than video, audio, and subtitles. The separation unit 132 may also perform error correction and access restriction control on the input MMT data string based on the control of the main control unit 101.
[0145] The video decoder 141 decodes the video data string input from the separation unit 132 and outputs video information. The video color gamut conversion unit 142 performs color space conversion processing on the video information decoded by the video decoder 141 as necessary for video synthesis processing in the video synthesis unit 161. The audio decoder 143 decodes the audio data string input from the separation unit 132 and outputs the audio information. In addition, streaming data in, for example, MPEG-DASH (MPEG-Dynamic Adaptive Streaming over HTTP) format acquired from the Internet 200 via the LAN communication unit 121 may be input to the video decoder 141 and the audio decoder 143. In addition, a plurality of the video decoder 141, the video color gamut conversion unit 142, the audio decoder 143, etc. may be provided in order to simultaneously decode a plurality of types of video data strings and audio data strings.
[0146] The superimposed text decoder 144 decodes the superimposed text data string input from the separation unit 132 and outputs superimposed text information. The subtitle decoder 145 decodes the subtitle data string input from the separation unit 132 and outputs subtitle information. The superimposed text information output from the superimposed text decoder 144 and the subtitle information output from the subtitle decoder 145 are subjected to a synthesis process in the subtitle synthesis unit 146, and further, in the subtitle color gamut conversion unit 147, a color space conversion process is performed as necessary for the video synthesis process in the video synthesis unit 161. In this embodiment, among the services mainly based on 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 the rest are referred to as superimposed text. Furthermore, when there is no distinction between them, they are collectively referred to as subtitles.
[0147] The browser unit 154 presents the multimedia application file and its component file data acquired from the server device on the Internet 200 via the cache unit 152 or the LAN communication unit 121 in accordance with an instruction from the application control unit 153 that interprets the control information included in the MMT data string and the control information acquired from the server device on the Internet 200 via the LAN communication unit 121. The multimedia application file may be an HTML (Hyper Text Markup Language) document or a BML (Broadcast Markup Language) document, etc. The application information output from the browser unit 154 is further subjected to color space conversion processing in the application color gamut conversion unit 155 as necessary for video synthesis processing in the video synthesis unit 161. The browser unit 154 also plays back application audio information by influencing the 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 the like, and performs processing such as selection and / or superimposition as appropriate. The video synthesis unit 161 includes a video RAM (not shown), and the monitor unit 162 and the like are driven based on the video information and the like input to the video RAM. The video synthesis unit 161 also performs scaling processing and superimposition processing of EPG (Electronic Program Guide) screen information created based on information such as MH-EIT included in MMT-SI, as necessary, based on the control of the main control unit 101. 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 provided with a logical plane structure in order to display the multimedia service as intended by the provider. FIG. 8B shows an example of the configuration of the logical plane structure provided by the presentation function of the broadcast receiving device 100 of this embodiment. In the logical plane structure, a character superimposition plane for displaying character superimposition is arranged in the foreground, and a subtitle plane for displaying subtitles is arranged in the next layer. A multimedia plane for displaying broadcast video, multimedia applications, or composite video thereof is arranged in the third layer, and a background plane is arranged in the background. In the subtitle synthesis unit 146 and the video synthesis unit 161, drawing of character superimposition information on the character superimposition plane, drawing of subtitle information on the subtitle plane, drawing of video information, application information, etc. on the multimedia plane are performed. 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 a plurality of multimedia planes in the third layer can be prepared according to the number of video decoders 141. However, even if there are a plurality of multimedia planes, 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 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 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 an external video / audio output device, outputs analog video signals / audio signals to an external video / audio input device, 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] The digital interface unit 125 is an interface that outputs or inputs encoded digital video data and / or digital audio data. The digital interface unit 125 is capable of outputting an MMT data string obtained by demodulation in the tuner / demodulator unit 131, an MMT data string acquired via the LAN communication unit 121, or mixed data of the MMT data strings as is. In addition, the digital interface unit 125 may control the MMT data string input to the separator 132. The output of digital content stored in the storage unit 110, or the storage of digital content in the storage unit 110 may be performed via the 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 output or input data in the form of serial data conforming to the IEEE1394 specification, or the like. It may also be configured as an IP interface that performs digital interface output 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 used. The operation input unit 170 may also be replaced by a touch panel that is placed over the monitor unit 162. It may also be replaced by a keyboard or the like connected to the extended 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. In addition to a television receiver, the broadcast receiving device 100 may be an optical disk drive recorder such as a DVD (Digital Versatile Disc) recorder, a magnetic disk drive recorder such as a HDD recorder, a STB (Set Top Box), or the like. It may be a PC (Personal Computer), a tablet terminal, a navigation device, a game machine, or the like, equipped with a digital broadcast receiving function or a broadcast communication linking function. When the broadcast receiving device 100 is a DVD recorder, a HDD recorder, an STB, or the like, the monitor unit 162 and the speaker unit 165 may not be provided. By connecting an external monitor and an external speaker to the video output unit 163 and the audio output unit 166 or the digital interface unit 125, the same operation as the broadcast receiving device 100 of this embodiment is possible.
[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, the RAM 104, and the storage (accumulation) unit 110. In this embodiment, a basic operation program 1001 and other operation programs are stored in the ROM 103, and a receiving function program 1002, a link function program 1003, a recording and 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 for accessing an external mobile terminal device or each server device, and various information storage areas for storing various other information.
[0157] A basic operation program 1001 stored in the ROM 103 is loaded onto the RAM 104, and the main control unit 101 executes the loaded basic operation program 1001 to constitute a basic operation execution unit 1101. Similarly, a reception function program 1002, a link function program 1003, and a recording and playback function program 1004 stored in the storage (accumulation) unit 110 are loaded onto the RAM 104, and the main control unit 101 executes the loaded reception function program 1002, link function program 1003, and recording and playback function program 1004 to constitute a reception function execution unit 1102, link function execution unit 1103, and recording and playback function execution unit 1104. The RAM 104 is also provided with a temporary storage area for temporarily storing data created when each operation program is executed, as necessary.
[0158] In the following, for the sake of simplicity, 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 as the basic operation execution unit 1101 controlling each operation block. Similar descriptions will be used for the other operation programs.
[0159] The receiving function execution unit 1102 controls each operation block of the broadcast receiving device 100 to reproduce components such as video and audio transmitted in the broadcasting 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 string and audio data string separated from the MMT data string to the corresponding decoding processing units. The AV decoding processing unit 1102b mainly controls the video decoder 141, the audio decoder 143, etc. The application processing unit 1102c mainly controls the cache unit 152, the application control unit 153, the browser unit 154, and the sound source unit 156. The superimposed text processing unit 1102d mainly controls the superimposed text 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 to generate 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, connection, transmission and reception of each data, etc., when the broadcast receiving device 100 performs linkage operation with an external device such as the mobile information terminal 700. The recording and playback function execution unit 1104 controls recording of broadcast programs acquired from digital broadcast waves of this broadcasting system and contents acquired from each server device on the network in the content storage area 1200 of the storage (accumulation) unit 110 or in an external storage connected to the expansion interface unit 124, or controls playback of the broadcast programs, contents, etc.
[0161] The operation programs may be stored in the ROM 103 and / or the storage (accumulation) unit 110 beforehand at the time of product shipment. After product shipment, the operation programs may be acquired from another application server 500 or the like on the Internet 200 via the LAN communication unit 121. Moreover, the operation programs may be stored in a memory card, an optical disk, or the like and acquired via the expansion interface unit 124 or the like.
[0162] [Broadcasting 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 in 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 sending 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 of each broadcast program broadcast by a broadcast station. The metadata storage area 3300 stores metadata such as the program title, program ID, program summary, cast, broadcast date and time, and copy control information related to each program content of each of the broadcast programs.
[0165] In addition, the basic operation program 3001, broadcast content management / distribution program 3002, and broadcast content transmission 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 transmission execution unit 3103.
[0166] In the following, for ease of explanation, the process in which the main control unit 301 loads the basic operation program 3001 stored in the storage unit 310 into the RAM 304 and executes it to control each operation block will be described as being performed by the basic operation execution unit 3101. Similar descriptions will be used for the other operation programs.
[0167] The broadcast content management / distribution execution unit 3102 manages the program contents and each 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 contents and each metadata of each broadcast program to the service provider based on a contract. Furthermore, when providing the program contents and each 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, etc., when transmitting MMT data strings including program content of broadcast programs stored in the broadcast content storage area 3200 and program titles, program IDs, copy control information of program content, etc. of broadcast programs 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 a service provider server 400 on the Internet 200, etc. 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 composed of video data sequences, audio data sequences, program information data sequences, etc. of program contents 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 the program content of the broadcast program provided by the broadcast station server 300 as video content. It also stores the video content and the like produced by the service provider. The metadata storage area 4300 stores each metadata provided by the broadcast station server 300 and metadata related to the video content produced by the service provider. The application storage area 4400 stores various applications and the like for realizing services linked to the broadcast program to be distributed in response to requests from each television receiver. The user information storage area 4500 stores information (personal information, authentication information, and the like) 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] In the following, for ease of explanation, the process in which the main control unit 401 loads the basic operation program 4001 stored in the storage unit 410 into the RAM 404 and executes it to control each operation block will be described as the basic operation execution unit 4101 controlling each operation block. Similar descriptions will be used for the other operation programs.
[0175] The video content management / distribution execution unit 4102 acquires program contents and metadata of broadcast programs from the broadcast station server 300, manages the video contents and metadata stored in the video content storage area 4200 and the metadata storage area 4300, and controls the distribution of the video contents and metadata to each television receiver. Furthermore, the video content management / distribution execution unit 4102 may perform authentication processing of each television receiver as necessary when distributing the video contents 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 of each television receiver as necessary when distributing the applications 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 includes an encoding circuit, a decoding circuit, and the like.
[0177] [Mobile information terminal hardware configuration] 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 in the portable information terminal 700.
[0179] ROM 703 is a memory in which basic operation programs such as an operating system and other operation programs are stored, and a rewritable ROM such as an EEPROM or flash ROM is used. 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 use a part of the storage area in storage unit 710 instead of being an independent configuration as shown in FIG. 11A.
[0180] The storage unit 710 stores the operation program and operation setting values of the mobile information terminal 700, personal information of the user of the mobile information terminal 700, etc. It can also store operation programs downloaded via the Internet 200 and various data created by the operation programs. It can also store content such as video, still images, and audio downloaded via the Internet 200. A part of the area of the storage unit 710 may replace all or part of the functions of the ROM 703. The storage unit 710 needs to hold the stored information even when power is not being supplied from the outside to the mobile information terminal 700. Therefore, for example, devices such as a nonvolatile semiconductor element memory such as a flash ROM or SSD, a magnetic disk drive such as an HDD, etc. are used.
[0181] It should be noted that the operation programs stored in the ROM 703 and the 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 made by a wireless connection such as Wi-Fi (registered trademark). The mobile telephone network communication unit 722 performs telephone communication (calls) and transmits and receives data by wireless communication with the base station 600b of the mobile telephone communication network. The NFC communication unit 723 performs wireless communication when in close proximity to a corresponding reader / writer. The LAN communication unit 721, the mobile telephone network communication unit 722, and the NFC communication unit 723 are assumed to each include an encoding circuit, a decoding circuit, an antenna, and the like. The communication processing unit 720 may further include other communication units such as a BlueTooth (registered trademark) communication unit and an infrared communication unit.
[0183] The expansion interface unit 724 is a group of interfaces for expanding the functions of the portable information terminal 700, and in this embodiment, is composed of a video / audio interface, a USB interface, a memory interface, etc. The video / audio interface inputs video signals / audio signals from an external video / audio output device, outputs video signals / audio signals to an external video / audio input device, 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 arranged with button switches. Only one of them 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. That is, the mobile information terminal 700 may be operated from the broadcast receiving device 100. The touch panel function may 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 a function of performing format conversion, superimposition processing of menus and other OSD (On Screen Display) signals, etc., 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 and objects by converting light input from a lens into an electrical signal using an electronic device such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor) sensor.
[0186] The audio processing unit 750 is composed 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 brightness of the surroundings, the proximity of surrounding objects, and the like. The portable information terminal 700 may further include other sensors, such as an air 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 moving images, a portable game machine, a navigation device, or other portable digital devices.
[0189] 11A includes many components that are not essential to this embodiment, such as the sensor unit 760, but the effects of this embodiment are not impaired even if these components are not included. Also, components not shown, such as a digital broadcast receiving function and an electronic money settlement function, may be added.
[0190] [Mobile information terminal software configuration] 11B is a software configuration diagram of the mobile information terminal 700 of this embodiment, and shows the software configuration in the ROM 703, the RAM 704, and the storage unit 710. In this embodiment, a basic operation program 7001 and other operation programs are stored in the ROM 703, and a linkage 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 for storing content such as moving images, still images, and audio, an authentication information storage area 7300 for storing authentication information and the like required for accessing a television receiver or each server device, and various information storage areas for storing various other information.
[0191] A basic operation program 7001 stored in ROM 703 is loaded onto RAM 704, and the main control unit 701 executes the loaded basic operation program to constitute a basic operation execution unit 7101. Similarly, a cooperative control program 7002 stored in the storage unit 710 is loaded onto RAM 704, and the main control unit 701 executes the loaded cooperative control program to constitute a cooperative control execution unit 7102. The RAM 704 also includes a temporary storage area for temporarily holding data created during execution of each operation program as necessary.
[0192] In the following, for ease of explanation, the process of the main control unit 701 loading the basic operation program 7001 stored in the ROM 703 into the RAM 704 and executing it to control each operation block will be described as being performed by the basic operation execution unit 7101 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 each data, etc., when the mobile information terminal 700 performs cooperative operation with the television receiver. The cooperative control execution unit 7102 also includes a browser engine function for executing an application that works in conjunction with the television receiver.
[0194] The operation programs may be stored in the ROM 703 and / or the storage unit 710 beforehand at the time of product shipment. After product shipment, the operation programs may be acquired from other application servers 500 on the Internet 200 via the LAN communication unit 721 or the mobile telephone network communication unit 722. Moreover, the operation programs may be acquired via the extended interface unit 724 from memory cards, optical disks, 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 the system configuration for clock synchronization / presentation synchronization in the 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 the 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 or more' of UTC is represented by 32 bits, and the 'less than seconds' is represented by 32 bits. However, in reality, it is difficult to reproduce 1 second with 32-bit accuracy. Therefore, as the system clock for synchronizing the video system or the system clock for operating the NTP-formatted 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 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 is set to a frequency of a power of 2 such as "2 to the power of 24" to "2 to the power of 28" on the broadcast transmission system side or the receiver side as described above, the lower 8 to 4 bits in 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 power of n" Hz (n=24 in the example of FIG. 12A, 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 format time information from the outside, it configures a PLL system with a 32+n bit counter using a VCO (Voltage Controlled Oscillator) of 2 n Hz, and realizes a transmission system clock that is synchronized with the time information provided from the outside. In addition, the entire signal processing system is operated in synchronization with the system clock of 2 n Hz. Furthermore, the output of the transmission system clock is periodically transmitted to the receiver side as NTP long format time information via the broadcast transmission path. Note that the NTP long format time information transmitted to the receiver side may also have the lower 32-n bits of the 32 bits representing "less than a second" fixed to "0" or "1". In other words, this is because the system clock counter on the broadcast transmission system side is composed of 32+n bits.
[0200] The receiver receives the time information in NTP long format via the broadcast transmission path, and regenerates the receiving system clock using a PLL system based on a VCO of 2n Hz, just like the broadcast transmission system. This makes the receiving system clock synchronized with the broadcast transmission system. 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 and the receiver 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-mentioned video / audio signal, etc., synchronization of the video / audio signal can also be ensured by a clock of about '2 to the 16th power' Hz (about 65.5 KHz). In this case, it is not necessary to refer to the lower 16 bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. 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 the control of the decoding timing and presentation timing, it is not necessary to refer to the lower '32 - m' bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. Therefore, the lower '32 - m' bits of the NTP timestamp format described in the MPU timestamp descriptor, etc. may be fixed to '0' or '1'.
[0203] <Time management function based on MH-TOT> FIG. 12B shows an example of the configuration of time information transmitted in the NTP format in the time management function based on the NTP described above. The "reference_timestamp" parameter and the "transmit_timestamp" parameter in the NTP format are 64-bit time data in the NTP long format, and the "mpu_presentation_time" parameter in the MPU timestamp descriptor shown in FIG. 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 are data in which "seconds or more" of UTC are expressed in 32 bits and "less than seconds" is expressed in 32 bits. That is, the NTP format time information can transmit time information up to "less than seconds". Furthermore, since the NTP format time information is expressed in UTC, unlike the time management in conventional digital broadcasting, as shown in FIG. 3, 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, it is possible to easily match both 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 Fig. 12C. The broadcast receiving device 100 of this embodiment can obtain the current date and the current time from the "JST_time" parameter of the MH-TOT. As shown in Fig. 12D, the "JST_time" parameter includes the lower 16 bits of the coded data of the current date based on the Modified Julian Date (MJD) and 24 bits of information that expresses 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 minutes in two decimal digits, and the last two 4-bit binary coded decimal numbers represent the seconds in two decimal digits.
[0206] In other words, the difference between time management based on the NTP format and time management based on MH-TOT is that the former, NTP format-based time management, can transmit time information down to the "second" as mentioned above, while the latter, MH-TOT-based time management, 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, for decoding and displaying synchronization processing of video, audio, subtitles, superimposed text, and other presented data, which are the contents of the broadcast signal. Furthermore, by referring to information in UTC notation instead of the clock notation of the broadcast station, it is also possible to perform synchronization processing of decoding and displaying video, audio, subtitles, superimposed text, or other data, which are the contents received by the broadcast signal, and video, audio, subtitles, superimposed text, or other data acquired through a communication line path.
[0208] Furthermore, in the broadcast receiving device 100 of this embodiment, the time management function based on "JST_time" including 24-bit information expressed by six 4-bit binary coded decimal numbers of MH-TOT may be used in the process of presenting the current time to a user or each process of handling the MH-EIT shown in FIG. 7E. Generally, in the process of presenting the current time to a user in a broadcast receiving device, accuracy to the nearest second is rarely required. Also, each piece of time information described in the MH-EIT is 24-bit information expressed by six 4-bit binary coded decimal numbers, and is stored in two decimal digits each for "hour", "minute", and "second", similar to the EIT of conventional digital broadcasting transmitted by the MPEG2-TS method. 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 each process of handling the MH-EIT. Specifically, each process of handling the MH-EIT is, for example, a process of generating an electronic program guide, control of recording and viewing reservations, copyright management process such as temporary storage, etc. This is because it is rare for any process to require accuracy below a second, and accuracy on the order of one second is sufficient.
[0209] Moreover, the generation process of the electronic program guide, the control of recording reservation and viewing reservation, copyright management process such as temporary storage, etc. are functions that are also installed in receivers of digital broadcasting systems using the conventional MPEG2-TS format. Then, in the broadcasting system of this embodiment, if the generation process of the electronic program guide, the control of recording reservation and viewing reservation, copyright management process such as temporary storage, etc. are configured to be compatible with time management process consistent with the conventional MPEG2-TS format digital broadcasting system, when configuring a broadcast receiving device having both the reception function of conventional MPEG2-TS format digital broadcasting and the reception function of MMT format digital broadcasting, it will be unnecessary to design processing algorithms separately for these processes (generation process of the electronic program guide, control of recording reservation and viewing reservation, copyright management process such as temporary storage, etc.), and costs can be reduced.
[0210] Furthermore, even if a receiver 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 not necessary 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. Instead, algorithms for functions that are also installed in receivers for digital broadcasting systems using the conventional MPEG2-TS format can be reused, making it possible to develop them at lower cost.
[0211] Therefore, by configuring the time management function based on the MH-TOT "JST_time" parameter for these processes (such as generation of electronic program guides, control of recording and viewing reservations, and copyright management processes such as temporary storage), it will be possible to provide even MMT-type digital broadcast receiving devices at a lower cost by improving compatibility with conventional broadcasting systems.
[0212] As described above, the broadcast receiving device 100 of this embodiment has a time management function using two types of time information with different accuracy. That is, the first time information is time information written in a manner consistent with conventional digital broadcasting systems, and the second time information is time information with a higher resolution than the first time information. By using the second time information for synchronization processing of each content data of a broadcast signal, a more advanced information presentation processing than that of conventional broadcasting systems is realized, and by using the first time information for generation processing of an electronic program guide, control of recording and viewing reservations, copyright management processing such as temporary storage, etc., a broadcast receiving device can be provided at a 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 modified example of 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 described with reference to FIG. 12A, information regarding an estimated delay time in transmitting time information from a time management server (not shown) or broadcast station server 300 to 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 estimated delay time to correct the system clock of the NTP-based time management function.
[0216] In this case, the information on the expected delay time may be configured to be transmitted not in the TLV multiplexed stream of the protocol stack in the broadcast transmission path shown in FIG. 3(A) but in a TMCC (Transmission and Multiplexing Configuration Control) area outside the TLV multiplexed stream. If the information is transmitted in the TMCC area, the broadcast receiving device 100 can extract the information on the expected delay time without undergoing a separation process (demux process) of the TLV multiplexed stream. That is, it is possible to obtain information that is not easily affected by the delay caused by the separation process in the broadcast receiving device 100, and therefore it is possible to perform a highly accurate system clock correction process. An example of the data structure of the time information transmitted by the TMCC signal will be 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 the figure, the "delta" parameter represents the expected value of the 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, using a 32-bit signed fixed point. The upper 16 bits describe the integer part, and the lower 16 bits describe the decimal part. 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 represent the integer part, and the lower 32 bits represent the decimal part.
[0217] In the first variant, the broadcast receiving device 100 of this embodiment can use information regarding the expected delay time described in the time information stored in the TMCC extended information area and transmitted (e.g., the aforementioned ``delta'' parameter and / or ``transmit_timestamp'' parameter) to more accurately correct the system clock of the NTP-based time management function used for synchronization processing of each content data of the broadcast signal.
[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 described above, the broadcast receiving device 100 of this embodiment has a time management function that acquires the current date and Japan Standard Time from information transmitted in the MH-TOT and manages the time. The current date and Japan Standard Time acquired from information transmitted in the MH-TOT can be superimposed on video information, application information, etc. by the video synthesis unit 161 of the broadcast receiving device 100, and output to the monitor unit 162 or video output unit 163 for provision to the user. As described above, the MH-TOT has the data structure shown in Fig. 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, since the aforementioned "JST_time" parameter uses only the lowest 16 bits of the encoded data of the MJD, an overflow occurs at "April 22, 2038", and dates after "April 23, 2038" cannot be expressed by the above-mentioned specified calculation alone. Therefore, in the second modified example of this embodiment, the calculation method is switched between when the MJD value is equal to or greater than a specified value and when it is less than a 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 value of MJD is equal to or greater than a predetermined value, and a second calculation method used when the value of MJD is less than the predetermined value. For example, if the predetermined value is "32768 (0x8000)", the first calculation method is used to calculate the current date when MJD is equal to or greater than "32768", and the second calculation method is used to calculate the current date when MJD is less than "32768". Note that the case where MJD is less than "32768" is equivalent to the case where the most significant bit of the 16-bit data of MJD is "0". This makes it possible to express dates after "April 23, 2038" in the broadcast receiving device 100 of this embodiment. However, the predetermined value can be set arbitrarily, and the predetermined value may be set to "16384 (0x4000)", "49152 (0xC000)", etc. The condition for switching the calculation method may be when the most significant 2 bits of the 16-bit data of the MJD are "00" or when the most significant 2 bits of the 16-bit data of the MJD are not "11." If the above-mentioned means is used with the predetermined value set to "32768," it will not be possible to express dates prior to "September 4, 1948," but this will not be a problem in practical use as a television receiver.
[0222] Also, instead of switching between the first calculation method and the second calculation method depending on the comparison result between the MJD and the predetermined value, the first calculation method and the second calculation method may be switched depending on a flag that replaces part or all of the "reserved" parameter in the data structure of the MH-TOT shown in FIG. 12C or a newly added flag. For example, when the most significant bit of the 16-bit encoded data of the MJD is "0", if the MJD indicates "April 23, 2038" or later, the flag may be set to "1", and if the MJD does not indicate "April 23, 2038" or later, the flag may be set to "0". Then, when the flag is "1", the second calculation method shown in FIG. 12F may be used, and when 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] In addition, as described above, the broadcasting system of this embodiment transmits absolute time in NTP format, and the broadcasting receiving device 100 of this embodiment has a time management function based on the NTP. Furthermore, in the broadcasting receiving device 100 of this embodiment, the decoding timing and presentation timing for each presentation unit of the video / audio signal are controlled by referring to the NTP timestamp 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 FIG. 12B. Moreover, the MPU timestamp descriptor has the configuration shown in FIG. 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 according to 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 receiving device channel selection process (initial scan)] The AMT of the broadcasting system of this embodiment provides a list of multicast groups of IP packets so that IP packets transmitted by the TLV multiplexing method can be received without distinction from IP packets transmitted over a communication line as much as possible. Multiple IP multicast groups can be listed for one service identification. Also, an address mask can be used to efficiently describe consecutive IP addresses.
[0227] In the broadcast receiving device 100 of this embodiment, when scanning channels for initial setting or when rescanning for changing settings, it is possible to store a list of services acquired from the TLV-NIT in a non-volatile memory such as the ROM 103 or the storage unit 110, and further, it is possible to store a list of IP multicast groups corresponding to each of the services as IP related information in the non-volatile memory in association with each of the services. By storing the list of services and the IP related information in a non-volatile memory and making it possible to refer to them at all times, it becomes unnecessary to reacquire the TLV-NIT or AMT when switching channels, etc., and it becomes possible to efficiently acquire broadcast contents.
[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 frequency value (S101). If the tuner / demodulator unit 131 succeeds in locking onto the set frequency value (S102: Yes), the receiving function execution unit 1102 then acquires a 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 a TLV stream ID and an original network ID from the acquired TLV-NIT (S105). FIG. 13B shows an example of a data structure of a TLV-NIT. The TLV stream ID information can be acquired from the "tlv_stream_id" parameter, and the original network ID information can be acquired from the "original_network_id" parameter. Furthermore, distribution system information related to the physical conditions of the broadcast transmission path corresponding to each TLV stream ID / original network ID is acquired from the distribution system descriptor (S106), and a list of service IDs is acquired from the service list descriptor (S107).
[0231] An example of the data structure of a satellite distribution system descriptor is shown in Fig. 13C. An example of the data structure of a service list descriptor is shown in Fig. 13D. If the TLV-NIT has a plurality of different 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 a 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 (updates 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). FIG. 13E shows an example of the data structure of an AMT. If the AMT has a list of IP multicast groups related to a plurality of service IDs, the process of S110 is repeated. If there are a plurality of AMTs having lists 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 131 is the final frequency value of the channel scan range (S112: Yes), the reception 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 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 obtained with one TLV-NIT and further, an AMT having a list of IP multicast groups related to the service IDs can be obtained, the processes of S112 to S113 are not necessary.
[0235] Through the series of processes described above, 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 for 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 the list 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 referring to the "version_number" parameter of the TLV-NIT or AMT. When a change in the "version_number" parameter of either the TLV-NIT or the AMT is detected, only the information on the table in which the change in the parameter is 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. In addition, the user may be notified that a change has been made in the information in the table, and the user may select whether or not to perform the rescan.
[0237] [Broadcast receiving device channel selection process (channel switching)] FIG. 14A is a diagram showing an example of an operation sequence when selecting a station (switching a channel) in the broadcast receiving device 100 of this embodiment.
[0238] When a user operates a remote control (not shown) to instruct channel switching, the receiving function execution unit 1102 interprets the command sent from the remote control and specifies the service ID of the target service (S201). Next, the receiving function execution unit 1102 starts acquiring the AMT from the signal received by the tuner / demodulator unit 131. If the AMT is successfully acquired within a predetermined time (S202: Yes), the receiving function execution unit 1102 acquires information on a list of IP multicast groups corresponding to the service ID from the acquired AMT (S204). On the other hand, if the AMT is not successfully acquired within the predetermined time (S202: No), the receiving function execution unit 1102 acquires information on a list of IP multicast groups corresponding to the service ID (S204) by referring to IP-related information stored in the ROM 103 or the storage unit 110 (S203). It is also possible to always refer to the IP-related information stored in the ROM 103 or the storage unit 110 without performing the judgment process of S202.
[0239] Next, the reception function execution unit 1102 starts acquiring the TLV-NIT from the received signal of the tuner / demodulator unit 131. If the TLV-NIT is successfully acquired within a predetermined time (S205: Yes), distribution system information for acquiring the 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 distribution system information for acquiring the IP data flow corresponding to the service ID is acquired (S207) by referring to a service list stored in the ROM 103 or the storage unit 110 or the like (S206). Note that the determination process of S205 may not be performed, and the service list stored in the ROM 103 or the storage unit 110 or the like may always be referred to.
[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 separation unit 132, the transport processing unit 1102a acquires an MMTP packet with a packet ID of "0" from the input MMT data string (S209), and further acquires an MPT included in the acquired MMTP packet (S210). Next, the transport processing unit 1102a refers to the "MMT_package_id_byte" parameter of the acquired MPT, and checks whether the lowest 16 bits of the "MMT_package_id_byte" parameter are the same value as the service ID. In the example of the data structure of the MPT shown in Fig. 7B, if the lowest 16 bits of the "MMT_package_id_byte" parameter are the same value as the service ID (S211: Yes), it is determined that the MMTP packet with the packet ID of "0" is an MMTP packet having data of a program corresponding to the service ID, and proceeds to MFU acquisition processing based on 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), it is determined that the MMTP packet with the packet ID of "0" is not an MMTP packet having data of a program corresponding to the service ID. In this case, the transport processing unit 1102a acquires a PLT again (S212), and by checking the acquired PLT, confirms the packet ID (assumed to be x) of an MMTP packet transmitting an MPT having the "MMT_package_id_byte" parameter corresponding to the service ID (S213). Furthermore, the transport processing unit 1102a acquires an MMTP packet with a packet ID of "x" from the input MMT data string (S214), and acquires an MPT included in the acquired MMTP packet (S215). Furthermore, based on the information contained in the acquired MPT, starts the acquisition process of an MFU.
[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, when the data of the program corresponding to the service ID is stored in an MMTP packet with a packet ID other than "0", it is possible to shorten the processing time.
[0244] Here, the above-mentioned process of identifying the packet ID of an MMTP packet having data of a program corresponding to the service ID and acquiring an MPT by checking the PLT will be described. An MMTP packet with a packet ID of "0" indicates that it transmits a PA message. When multiple packages are multiplexed, as shown in FIG. 14B, this PA message includes a PLT (package list table). The PLT has a list of packet IDs of MMTP packets that transmit PA messages including MPTs of other packages, and by checking the PLT, it is possible to identify an MMTP packet that transmits a PA message including an MPT that is an entry point of each service from the package ID. An example of the data structure of a PLT is shown in FIG. 14C. 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 operation sequence shown in FIG. 14A, in the MFU acquisition process, first, the transport processing unit 1102a refers to 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). In addition, the transport processing unit 1102a acquires the presentation time of the MPU from the MPU timestamp descriptor arranged in the MPT, and the layout number of the MPU from the MPU presentation area designation descriptor arranged 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, the encoded video data and encoded audio data, etc. are extracted from the acquired MFU, and video / audio decoding process is performed under the control of the AV decoding processing unit 1102b, and presentation process is performed based on the acquired information on the presentation time and information on layout control under the control of the presentation processing unit 1102h (S220).
[0246] If the PLT could not be acquired in the process of S212, if the "MMT_package_id_byte" parameter matching the service ID could not be confirmed in the process of S213, if the MMTP packet with the packet ID of "x" could not be acquired in the process of S215, etc., program output processing (i.e., the processes of S216 to S220) may be performed based on the data of the MMTP packet with the packet ID of "0" acquired in the process of S210. In this case, it is preferable to display a message to the effect that the program corresponding to the service ID selected by the user could not be displayed.
[0247] By the above series of processes, the broadcast receiving device 100 of this embodiment can execute a channel selection (channel switching) operation. In particular, as described with reference to Fig. 13A and Fig. 14A, at the time of channel scanning during initial setting or at the time of rescanning for setting change, a service list and IP related information are created and stored in a non-volatile memory such as the ROM 103 or the storage unit 110 so as to be always available for reference, and at the time of channel selection (channel switching), the service list and IP related information stored in the non-volatile memory such as the ROM 103 or the storage unit 110 are referenced, thereby improving the efficiency of the operation at the time of channel selection (channel switching). That is, it is possible to shorten the time from the start of channel selection (channel switching) to the end of channel selection (channel switching) compared to the case where AMT or TLV-NIT is reacquired at the time of channel selection (channel switching).
[0248] [Remote control key setting process for broadcast receiving device] 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, a decision key 100R7, and a color key 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 operation sequence at the time of channel selection shown in FIG. 14A, when instructing the broadcast receiving device 100 of this embodiment to switch 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 perform forward (or reverse) channel selection until the desired channel (service) is displayed by repeatedly pressing the channel up / down key 100R3 as necessary. The third method is a so-called one-touch channel selection method in which a specific channel (service) associated with each key of the numeric keypad 100R2 is called up by pressing the numeric keypad 100R2 only once. The one-touch channel selection, which is the third method, is a convenient channel selection method, but it is necessary to previously set the association of the specific channel (service) with each key of the numeric keypad 100R2 in the broadcast receiving device 100.
[0250] The broadcast receiving device 100 corresponding to the broadcast system of this embodiment is capable of automatically setting the association based on control information included in the digital broadcast wave received by the tuner / demodulator unit 131. That is, the broadcast 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] An example of the data structure of a remote control key descriptor is shown in Figure 15B. 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 of a 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 of 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 key 100R8. In this case, a numeric value corresponding to the "remote_control_key_id" parameter may be assigned in advance to each key of the color key 100R8.
[0253] The remote control key descriptor may be described as a TLV-NIT descriptor. Therefore, for example, when the TLV-NIT acquired in the process of S103 of the operation 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 the ROM 103 or the storage unit 110 of the broadcast receiving device 100 in conjunction with the processes of S105 to S107, thereby setting the association.
[0254] The association may be set according to the contents of the description of the remote control key descriptor as described above, or the user may assign services of any channel to each key of the numeric keypad 100R2 according to his / her preference. The association may be set according to the contents of the description of the remote control key descriptor and the association assigned according to the user's preference simultaneously stored in the non-volatile memory of the broadcast receiving device 100, and only one of the settings may be used by selecting a menu operation or the like. In this case, the association assigned according to the user's preference may be used preferentially. The association according to the contents of the description of the remote control key descriptor may be used preferentially over the association assigned according to the user's preference according to the value of the priority flag described in the remote control key descriptor. The priority flag may be set by using a 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 his / her 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 his / her preferences, and when the 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 the remote control key descriptor is not described in the TLV-NIT being received, the association settings assigned by the user according to his / her preferences may be used.
[0256] The process of changing the association of each key of the numeric keypad 100R2 with a specific channel (service) according to the description 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 old settings for the other services may be retained as they are. Also, when the "service_id" parameter is a specific value (e.g., 999, etc.), 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 the association of each key of the numeric keypad 100R2 with a specific channel (service).
[0258] [Multi-channel selection processing] In the broadcasting system of this embodiment, it is also possible to perform a multi-format broadcast in which multiple programs are broadcast in parallel on one channel (service). When broadcasting multiple programs simultaneously using a multi-format, the above-mentioned one-touch channel selection is possible only for the main channel of the multi-format, but not for the sub-channels of the multi-format. That is, when selecting a sub-channel of the multi-format, it is necessary to use a method of directly inputting and specifying a service ID, or to select the main channel of the multi-format once 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 sub-channel of a multi-channel configuration by repeatedly pressing the numeric keypad 100R2, to which a specified service ID is assigned, multiple times within a specified period of time.
[0260] The following description will be given with reference to FIG. 16A. For example, assume that the service of channel 011 is assigned in advance to the "1" key of the numeric keypad 100R2 of the remote controller 100R. In this case, if a channel selection operation is performed when multi-organization 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-organization 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 from the first pressing of the "1" key. Similarly, when the "1" key is pressed three times within a predetermined time, channel 013 is selected. Note that if the "1" key is pressed again after a predetermined time has elapsed since the first pressing of the "1" key, channel 011 may remain selected.
[0261] By enabling the above-mentioned operations, the broadcast receiving device 100 of this embodiment enables direct selection of a subchannel in a multi-channel format with a simpler operation.
[0262] Similarly, the angle of a multi-view compatible program or a specific video asset from a plurality of video assets may be selected by repeatedly pressing the numeric keypad 100R2 multiple times. As shown in FIG. 16B, when the service ID of a multi-view compatible program is assigned to the "1" key of the numeric keypad 100R2 of the remote control 100R, pressing the "1" key only once selects the multi-view compatible program and displays the main view. Pressing the "1" key again within a predetermined time from the first pressing of the "1" key displays the sub-view 1 of the multi-view compatible program. Similarly, pressing the "1" key three times within a predetermined time displays the sub-view 2 of the multi-view compatible program. If the "1" key is pressed again after a predetermined time has elapsed since the first pressing of the "1" key, the main view of the multi-view compatible program may remain displayed. Selection of a specific video asset from a plurality of video assets may also be possible by the same operations as described above.
[0263] By enabling the above-mentioned operations, the broadcast receiving device 100 of this embodiment makes it possible to select an angle for a multi-view compatible program or to select a specific video asset from multiple video assets with simpler operations.
[0264] In addition, when one or more programs in the multi-format are multi-view compatible programs or programs having multiple assets, only one of the above operations may be enabled and the other disabled. For example, when one or more programs in the multi-format are multi-view compatible programs or programs having multiple assets, the operation of pressing the same key multiple times within a predetermined time is assigned to the processing of direct selection of a sub-channel in the multi-format. Which operations are enabled and disabled may be determined in advance, or may be selected by the user.
[0265] [Screen layout control for broadcast receiving devices] It is assumed that the broadcast receiving device 100 of this embodiment is capable of controlling the screen layout based on the description of the LCT. An example of the data structure of the LCT is shown in Fig. 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 position of the top left and bottom right of the region, respectively, as a percentage of the total number of pixels in the horizontal direction, 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 position of the top left and bottom right of the region, respectively, as a percentage of the total number of pixels in the vertical direction, 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 in the depth direction of the region.
[0267] An example of the assignment of layouts to layout numbers based on the settings of each of the above parameters is described below, along with the setting values of each of the above parameters.
[0268] FIG. 17C shows a default layout setting of the broadcast receiving device 100 of this embodiment, and is an example in which only one area is set in the entire screen. FIG. 17D shows an example in which the entire screen is divided into three areas, each of which is designated as "area 0", "area 1" and "area 2". For example, if the number of pixels in the entire screen is 7680 pixels horizontally and 4320 pixels vertically, "area 0" is set in the range of (0,0)-(6143,3455) since 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 in the range of (6144,0)-(7679,4319), and "area 2" is set in the range of (0,3456)-(6143,4319).
[0269] Fig. 17E is an example of setting three regions like 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" according to the setting of the "layer_order" parameter, in the same range as above. Fig. 17F is an example of the 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 perform screen layout control for displaying multimedia services on a receiver as intended by the service provider.
[0271] In addition, in the area where the program video or data screen is not displayed by the above-mentioned screen layout control, a predetermined background color specified by the background color specification descriptor described in the LCT may be displayed. In addition, when the background color specification descriptor is not included in the LCT, when the broadcast receiving device 100 cannot correctly acquire the background color specification descriptor, when the predetermined background color specified by the background color specification descriptor cannot be displayed due to hardware limitations, etc., the video display device 100 may display a predetermined pattern in the above area. In addition, the above area may be used as a display area for a notice from the video display device 100 to the user. The notice may be any information.
[0272] The fractional part after the decimal point that occurs when dividing the screen according to the set values of the parameters such as "left_top_pos_x" may be rounded up or down. Rounding (or rounding down to the nearest whole number in binary) may also be used. For example, if the number of pixels on the entire screen is 7680 pixels / 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" may be set in the range of (0,0)-(3916,2203) by rounding up, or in the range of (0,0)-(3915,2202) by rounding down. Also, taking into account the macroblocks used in the video compression process, rounding up / down may be performed in units of 8 pixels or 16 pixels. This process makes it possible to efficiently set an area based on the LCT and to efficiently convert the resolution of multimedia content in the area.
[0273] Alternatively, the set 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 be performed appropriately.
[0274] The content to be displayed in each of the above regions is specified by the MPU presentation region specification descriptor shown in Fig. 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 above LCT by the "layout_number" parameter and the "region_number" parameter.
[0275] In addition, in the first "for" loop of the description of the MPU presentation area specification descriptor, multiple "layout_number" parameters and "region_number" parameters may be described for one "mpu_sequence_number" parameter, and the user may select which description to follow for layout control. For example, in the first "for" loop, when a "layout_number1", a "region_number1", a "layout_number2", and a "region_number2" parameter are described for a specific "mpu_sequence_number" parameter, the user may select whether the layout control of the MPU specified by the "mpu_sequence_number" parameter is performed based on the "layout_number1" and "region_number1" parameters, or based on the "layout_number2" and "region_number2" parameters. In this way, the user can perform layout control for video programs according to his / her preferences.
[0276] [Exception handling for screen layout control on broadcast receiving device] In the broadcast receiving device 100 of this embodiment, even if the screen layout area control is performed by the above-mentioned LCT, when 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 exception process. Figure 18A shows an example of the operation of exception process of screen layout control based on the LCT.
[0277] 17D is performed by the description of the LCT, and when a broadcast program image is displayed in "Area 0", and broadcast contents such as program linkage data linked to the broadcast program are displayed in "Area 1" and "Area 2", and the user instructs the display of the EPG screen using a remote control (not shown), the broadcast receiving device 100 of this embodiment returns the screen layout setting to the default setting (i.e., a state in which the same screen layout control as in FIG. 17C is performed) regardless of the description contents of the LCT, as shown in FIG. 18A(A), and controls the EPG screen to be displayed on the entire screen. Furthermore, when the user instructs the display of the EPG screen to end, the screen layout control according to the description contents of the LCT is re-executed.
[0278] By performing the above-mentioned 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 above-mentioned 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 a dual-screen of various setting screens of the broadcast receiving device 100 (the recording setting screen in the illustrated example), 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 is changed 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 is changed from the entire screen to only the split screen portion at the left middle section of the screen. In either case, the display area for displaying the broadcast content is narrower than when the entire screen is used, so it is not visually preferable to maintain the area control of the screen layout within the display area (i.e., to display multiple broadcast contents simultaneously by dividing the area). 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 the broadcast content in "Area 1" or "Area 2" may be selected and displayed depending on the immediately preceding area selection situation.
[0281] By performing the above-mentioned control, it is possible to improve the ease of viewing of the broadcast contents compared to when various broadcast contents are displayed while maintaining the area control of the screen layout. The same is true when displaying a sub-screen in the recorded program list screen, when displaying Internet contents 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, the 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. An aspect ratio different from that 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 broadcast service (such as the broadcast receiving device 100 of this embodiment) is generally 16:9. That is, when displaying video content with an aspect ratio of 4:3 or 21:9 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 horizontal by 2160 pixels vertical), the aspect ratio conversion process is not performed if the value of the "video_aspect_ratio" parameter is "0," "2," or "3," and is 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 horizontal by 2160 pixels vertical, etc.), then if the value of the "video_aspect_ratio" parameter is "0" or "5", aspect ratio conversion processing will not be performed, and if the value is "1", "2", or "3", aspect ratio conversion processing will be performed.
[0285] 19C and 19D show an example of the aspect ratio conversion process 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 displaying video content with an aspect ratio of "21:9" on the monitor unit 162 with an aspect ratio of "16:9", the aspect ratio may be converted to "16:9" by adding black bands above and below the video content with an aspect ratio of "21:9" (display A in the figure). In this way, it is possible to display the entire area of the original video content without distortion. Also, only the center part of the video content with an aspect ratio of "21:9" may be cut out and displayed on the monitor unit 162 (display B in the figure). In this way, it is possible to display the main part of the original video content in a large size. Also, it is possible to add a few black bands above and below the video content with an aspect ratio of "21:9" and further cut out the center part (display C in the figure). In this way, it is possible to display most of the original video content in a large 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 large 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 large size and with less distortion at the left and right edges.
[0286] The way in which the aspect ratio conversion process 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 receiving device] In the broadcasting system of this embodiment, time-series information on events (so-called programs) included in each service constituting the broadcasting network is transmitted by MH-EIT. The MH-EIT shown in Fig. 7E is identified into two classes by table ID (corresponding to the "table_id" parameter in the figure), and is capable of indicating information on the current / next event of its own TLV stream and schedule information of each event of its own TLV stream. The broadcast receiving device 100 of this embodiment is capable of acquiring information such as the start time and broadcast time of each event by identifying the event by service ID (corresponding to the "service_id" parameter in the figure) with reference to the MH-EIT, etc., and creating an EPG screen, and is capable of superimposing the created EPG on video information, etc. in the video synthesis unit 161 and displaying it on the monitor unit 162.
[0288] FIG. 20A is a diagram showing an example of an EPG screen in the broadcast receiving device 100 of this embodiment. The EPG screen 162a is in a matrix shape with the vertical axis indicating time and the horizontal axis indicating service ID (channel), and displays detailed information on broadcast programs broadcast on each channel in each time period. The detailed information 162a1 of each broadcast program is mainly composed of a title area 162a2 and a detailed explanation area 162a3. The detailed information 162a1 of each broadcast program may display program information and the like described in an MH-short format event descriptor or an MH-extended format event descriptor and distributed. When the capacity of the program information and the like described in each of the descriptors is large, the program information and the like may be omitted in normal times, and when a selection is made by operating a remote control not shown in the figure, all the program information may be displayed in a pop-up or the like. Alternatively, when a selection is made, the program information and the like described in each of the descriptors may be transmitted to the mobile information terminal 700 in the linked operation, and the mobile information terminal 700 may be instructed to display it on the display unit 741.
[0289] The title area 162a2 of the detailed information 162a1 of each broadcast program displays the program title of the broadcast program and symbols and the like representing the attributes of the broadcast program. The symbols and the like representing the attributes of the broadcast program are, for example, symbols / characters indicating that it is a new program, symbols / characters indicating that it is a rebroadcast program, etc. Alternatively, it may be a symbolized mark of "data" indicating that it supports data broadcasting by a broadcasting service. It may also be a symbolized mark 162a4 of "NetWork" indicating that content, applications, etc. related to the broadcast program can be obtained from a network. Furthermore, the symbols and the like representing the attributes of the broadcast program may be substituted by differentiating the background color of the detailed information 162a1 from others, or by surrounding the display area of the detailed information 162a1 with a thick frame.
[0290] 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 a 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 symbol 162a4 of "NetWork" etc. may be controlled not to be displayed.
[0291] In addition, when the broadcast program is a distributed program distributed via the Internet 200 and cannot be acquired only from the broadcast wave, and further, as described above, when the broadcast receiving device 100 is in a state where it cannot access each server device on the network, the detailed information 162b1 displayed on the EPG screen 162b may be controlled to be grayed out as shown in FIG. 20B. That is, the detailed information of the distributed program that cannot be viewed is controlled not to be displayed. In addition, the background color of the detailed information 162b1 may be differentiated from the others as an alternative to the graying out process. Alternatively, a message such as "This program cannot be viewed" may be displayed in the detailed explanation area 162a3 of the distributed program. When the detailed information 162b1 is selected by operating a remote control not shown, the user may be notified by a pop-up or the like that the broadcast receiving device 100 is in a state where it cannot access each server device on the network, or that the distributed program associated with the detailed information 162b1 cannot be viewed.
[0292] Through the above-mentioned controls, the broadcast receiving device 100 can provide the user with program information for each broadcast program in a format that feels 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 diagram, "M1 TV", "M2 Broadcast", "M3 Channel", "M4TV", "TV M5", etc. are the broadcast station names of the respective channels, and in particular, the "M2 Broadcast" station simultaneously provides a broadcast program distributed by airwaves and a distributed program distributed via the Internet 200 (information 162c1 of the slot indicated by "Internet Broadcast" in the diagram).
[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 not to display information for the "M2 broadcast (Internet broadcast)" channel that only has programs distributed via the Internet 200 (information 162c1 in figure (A)), as shown in EPG screen 162d in figure (B).
[0295] By the above-mentioned controls, the user of the broadcast receiving device 100 can eliminate the need to check information about channels that he or she cannot view.
[0296] [Emergency warning broadcast display on broadcast receiving device] The broadcast receiving device 100 of this embodiment is capable of performing receiving processing of an emergency alert broadcast 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), may be provided as a full-screen display application, or may be provided 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, when a user watches a normal broadcast program and receives an emergency alert broadcast while a program screen 162e of the broadcast program is displayed on the monitor unit 162, the text information 162e1 of the emergency alert broadcast is superimposed on the program screen 162e. Similarly, when a user instructs to display an EPG screen and receives an emergency alert broadcast while an EPG screen 162f is displayed on the monitor unit 162, the text information 162f1 of the emergency alert broadcast is superimposed on the EPG screen 162f.
[0298] By the above-mentioned 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 selects and displays an EPG screen, various setting screens, a recorded program list screen, an Internet browser, etc. This control may also be performed on text information of normal superimposed text that is not based on an emergency alert broadcast.
[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 transmitted to a mobile information terminal 700 that has a history of linked operation with the broadcast receiving device 100.
[0301] By the above-mentioned control, in the broadcast receiving device 100 of this embodiment, it is possible to avoid missing important broadcast programs and the display of application images 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 constituting 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 the 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 (see FIG. 7C) stored in the MPT. However, data transmitted through a data transmission path other than the TLV stream (for example, an IPv4 data flow or an IPv6 data flow of a communication line, an MPEG2-TS of a broadcast, etc.) indicated by the location information is data acquired by a receiving function other than the receiving function of the TLV / MMT stream. Therefore, even when the broadcast receiving device 100 is operating, there may be a situation in which data cannot be acquired from these transmission paths, such as a situation in which the receiving functions of these transmission paths are not operating, a situation in which the receiving functions themselves are operating but relay devices on the transmission paths are not operating, a situation in which these transmission paths are not connected by wire or wirelessly, or a situation in which the broadcast receiving device 100 is installed in an environment in which 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 to be included in the same package, the broadcast receiving device 100 of this embodiment may perform the following operations.
[0305] For example, in the case where the LCT sets multiple regions in the screen as shown in Fig. 17D or Fig. 17E, and the program video based on the data acquired from the TLV stream is displayed in "region 0", and the content based on the data acquired from a transmission path other than the TLV stream is displayed in "region 1" or "region 2", and if the data of the transmission path other than the TLV stream to be displayed in "region 1" or "region 2" cannot be acquired, the layout display of the multiple regions specified by the LCT may be prohibited. Specifically, even if the LCT is received, the program video based on the data acquired from the TLV stream is left displayed in "region 0" of the default layout display shown in Fig. 17C, and the layout display of the multiple regions as shown in Fig. 17D or Fig. 17E may not be changed. Furthermore, even if an instruction to change 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 Fig. 17C may be left as it is, or the display may be switched to another data broadcast screen, so that the layout display of the multiple regions as shown in Fig. 17D or Fig. 17E may not be changed.
[0306] In addition, in a case where 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 of 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 can be to temporarily 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 of a transmission path other than the TLV stream indicated by the MPT location information cannot be obtained even after a specified time has elapsed, the display can be switched back to the default layout display state shown in Figure 17C. In this case, when the layout of Figure 17C is changed to the layout of Figure 17D or Figure 17E, and when the layout of Figure 17D or Figure 17E is changed to the layout of Figure 17C, it is preferable 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 the data of the transmission path other than the TLV stream to be displayed in "Area 1" or "Area 2" cannot be obtained and the program video based on the data obtained from the TLV stream is displayed in "Area 0" of the default layout display shown in Fig. 17C, the operation of various communication functions and various reception functions of the broadcast receiving device 100 of this embodiment may start, 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 the data of the transmission path other than the TLV stream to be displayed in "Area 1" or "Area 2" can be obtained. 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 layout of multiple areas as shown in Fig. 17D or Fig. 17E shown by the LCT, and may display the program video based on the data obtained from the TLV stream in "Area 0", and display the content based on the data obtained from the transmission path other than the TLV stream in "Area 1" or "Area 2". Alternatively, the layout change may not be performed immediately, but may be performed after an instruction to change 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 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 the MPT or the like and transmitted to indicate the copy control status of the content referred to by the MPT or the like, such as "unlimited copying permitted" (which may be divided into two types: "unlimited copying permitted and encryption processing required for storage and output" and "unlimited copying permitted and encryption processing not required for storage and output"), "one generation only permitted", "prescribed number of times of copying permitted" (for example, so-called "dubbing 10" if nine copies and one move permitted), "copy prohibited", etc. 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 in a removable recording medium, output to an external device, copying to an external device, moving to an external device, etc., according to the copy control information.
[0309] The target of the accumulation process may include not only the storage (accumulation) unit 110 inside the broadcast receiving device 100, but also removable recording media and external devices that have been subjected to protection processes such as encryption processes so that they can be played back only by the broadcast receiving device 100. Specifically, for example, it includes external recording devices such as HDDs connected to the expansion interface unit 124 that have been made recordable and playable only by the broadcast receiving device 100.
[0310] <Content copy control> A specific example of the content copy control process 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", the broadcast receiving device 100 of this embodiment may perform, without restriction, the storage in the storage unit 110, the recording in a removable recording medium, the output to an external device, the copying to an external device, the move to an external device, etc. However, when the control based on the copy control information is divided into "unlimited copying and encryption processing required at the time of storage and output" and "unlimited copying and no encryption processing required at the time of storage and output", and indicates "unlimited copying and encryption processing required at the time of storage and output", the storage in the storage unit 110, the recording in a removable recording medium, the output to an external device, the copying to an external device, the move to an external device, etc. may be performed without restriction, but encryption processing must be performed in all cases.
[0312] Furthermore, when the copy control information included in the MPT or the like indicates "copyable for one generation only," the broadcast receiving device 100 of this embodiment may encrypt and store the content in the storage (accumulation) unit 110, or record the content in a removable recording medium that has been subjected to a protection process such as encryption so that the content can be played back only by the broadcast receiving device 100. Furthermore, when the stored content is output to an external device for viewing, the content is encrypted and output together with copy control information indicating "copy prohibited." Furthermore, so-called move processing to an external device (processing in which the content is copied to an external device and the content in the storage (accumulation) unit 110 of the broadcast receiving device 100 is erased or the like to make the content unplayable) is permitted.
[0313] Furthermore, when the copy control information included in the MPT or the like indicates "copyable a specified number of times," the broadcast receiving device 100 of this embodiment may encrypt and store the content in the storage (accumulation) unit 110, or record the content on a removable recording medium that has been subjected to a protection process such as encryption so that the content can be played back only by 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, copying and moving to an external device a predetermined number of times may be possible. In the case of the so-called "dubbing 10" provision, nine copies to an external device and one move process 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 time or a predetermined time specified by control information included in the broadcast signal (for example, by an MH-Expire descriptor or a content usage control descriptor). In this case, even when the copy control information included in the MPT or the like indicates "copy prohibited", the broadcast receiving device 100 enables temporary storage of the content in the storage (accumulation) unit 110 or the like. When the 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 of "copy prohibited".
[0315] The output for viewing to the external device described above may be performed via the video output unit 163 and the audio output unit 166 of the broadcast receiving device 100 of this embodiment, or via the digital I / F unit 125, the LAN communication unit 121, etc. The copy or move process to the external device described above may be performed via the digital I / F unit 125, the LAN communication unit 121, etc.
[0316] FIG. 22A shows an example of the data structure of the 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, and indicates information for controlling the copy generation 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 business operator, when the parameter is "10", it indicates "one generation copying only", and when the parameter is "11", it indicates "copying prohibited". FIG. 23 shows an example of the data structure of the content usage control descriptor in the broadcasting system of this embodiment. The "copy_restriction_mode" parameter in the figure is copy restriction mode, and indicates whether or not number-limited copying is possible.
[0317] In the broadcast receiving device 100 of this embodiment, when 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, which is determined in advance by the broadcasting company. Alternatively, when the digital copy control information is not "11" and the copy restriction mode indicates that a limited number of copies are permitted, it may be possible to execute a storage process that allows a predetermined number of copies to be made, which is determined in advance by the broadcasting company. 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 of the digital content usage descriptor.
[0318] By the above process, the broadcast receiving device 100 of this embodiment can realize the above-mentioned content copy control of "a specified number of copies allowed."
[0319] 23, the "retention_mode" parameter 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."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 allowable temporary storage time, it is possible to control whether or not temporary storage is permitted and the storage time when the digital copy control information of each content indicates "copy prohibited."
[0321] According to the above-described process, appropriate content protection can be achieved 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, which indicates whether or not image quality restriction is necessary when outputting the content to an external device. If the resolution restriction bit indicates that image quality restriction is necessary, 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 necessary when storing the target content in the storage (accumulation) unit 110 or the like. The image quality restriction may be, for example, converting received (or stored) UHD (7680 pixels x 4320 pixels) video content into SHD (3840 pixels x 2160 pixels) video and outputting it, or converting HD (1920 pixels x 1080 pixels) video into SD (640 pixels x 480 pixels) video and outputting it. Note that the extent to which the image quality restriction of the target content is performed, that is, the resolution of the image quality after the image quality restriction, may be specified by using a part or all of the "reserved_future_use" parameter of the digital content usage descriptor.
[0324] As described above, for example, a frame rate limiting bit or a pixel resolution limiting bit may be prepared using a part or all of the "reserved_future_use" parameter, and the frame rate limit or pixel resolution limit may be controlled when the content is output to an external device. If the frame rate limiting 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, a video content with a frame rate of 120 Hz may be converted to a frame rate of 60 Hz and output. Also, if the pixel resolution limiting 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 a video content with 12 bits may be converted to 8 bits and output.
[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 a part or all of the "reserved_future_use" parameter, and whether or not to restrict the image quality, the frame rate, or the pixel resolution may be controlled according to the resolution restriction control flag, the frame rate restriction control flag, or the pixel resolution restriction control flag. For example, when the resolution restriction control flag indicates that the resolution restriction control is performed according to the interface specifications, the image quality restriction may not be performed if the interface that outputs the target content has a predetermined content protection technology, and the image quality restriction may be 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, and 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 the resolution restriction control is performed according to the interface specification, the presence or absence of the image quality restriction may be controlled depending only on the resolution restriction bit. The same processing may be performed for the frame rate restriction control flag and the pixel resolution restriction control flag.
[0327] Furthermore, the copying process to an external device via LAN communication unit 121 of content whose copy control information indicates copy restrictions such as "copyable for one generation only," "copyable a specified number of times," or "copying prohibited" may be permitted only when the IP address of the external device that is the destination of a packet transmitted from broadcast receiving device 100 is in the same subnetwork as the IP address of broadcast receiving device 100, and may be prohibited when 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 and encryption processing required when stored and output" may also be handled in the same manner.
[0328] Similarly, after 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 processing 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 possible if the IP address of the external device that is the destination of the packet transmitted 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, the video output and audio output for viewing of the content stored in the storage (accumulation) unit 110 of the broadcast receiving device 100 are possible in principle only when the IP address of the external device, which is the destination of the transmission packet from the broadcast receiving device 100, is in the same subnetwork as the IP address of the broadcast receiving device 100, and are prohibited when the IP address of the external device is outside the same subnetwork as the IP address of the broadcast receiving device 100. However, if the external device is connected within the same subnetwork as the IP address of the broadcast receiving device 100 within a predetermined period of time and is a device that has been registered (paired) as a device that can be viewed even outside the same subnetwork as the IP address of the broadcast receiving device 100, the external device may be configured to be able to output the video output and audio output for viewing of the content stored in the storage (accumulation) unit 110 of the 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 the broadcast receiving device 100. In this case, the video output and audio output for viewing are performed by encrypting the content.
[0330] However, the encryption process may be controlled according to the value of the "encryption_mode" parameter of the content usage control descriptor shown in FIG. 23. That is, when the value of the "encryption_mode" parameter indicates that output protection of the IP interface output is required, the encryption process may be performed, and when 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 performing the encryption process. Also, when 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 performing the encryption process may be specified by using a part or all of the "reserved_future_use" parameter of the content usage control descriptor. That is, for a predetermined IP address, the viewing video output and audio output can be performed even if the IP address is not in the same subnet as the IP address of the broadcast receiving device 100.
[0331] Also, a period during which the registration process (pairing) is valid may be specified by using a part or all of the "reserved_future_use" parameter of the content usage control descriptor, etc. 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 output of video and audio for viewing to the external device may be permitted even if the external device is outside the same subnetwork as the IP address of the broadcast receiving device 100, and if it is outside the specified period, it may not be permitted.
[0332] Furthermore, the above-mentioned process of moving, copying, outputting, etc. of the 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, when the value of the "remote_view_mode" parameter does not allow remote viewing of the target content, control may be performed so that all of the process of moving, copying, outputting, etc. of the content to an external device via the LAN communication unit 121 is prohibited.
[0333] According to the above-described process, it is possible to realize appropriate content protection even when the content is output to an external device.
[0334] <Content copy control exception processing 1> In the data structure of the content copy control descriptor shown in Fig. 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 of the components that make 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 by 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 be considered 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 perform the following operation.
[0336] First, the first operation example is a method of controlling operation based on the copy generation control indicated in the first digital copy control information when the descriptions in the first digital copy control information and the second digital copy control information do not match, enabling simple copy generation control common to each component constituting the same content.
[0337] Next, the second operation example is a method of controlling operation based on the copy generation control indicated in the second digital copy control information when the descriptions in the first digital copy control information and the second digital copy control information do not match. In this case, different copy generation control is possible for each component even if the components constitute the same content, that is, more precise copy generation control is possible.
[0338] Furthermore, a third operation 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 information "one generation copying permitted" is followed. Or, if one is "a specified number of copies permitted" and the other is "copying prohibited," the information "copying prohibited" is followed. Or, if both are "a specified number of copies permitted," the information with the fewer number of copies permitted, which is separately specified, is followed. In this case, more strict copy generation control is possible.
[0339] By carrying out the above-mentioned 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 processing 2> As explained using FIG. 7A, in the digital broadcasting system compatible with the broadcast receiving device 100 of this embodiment, due to the location information in the MPT (see FIG. 7C), 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 in the case where 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 according to the copy control information included in the TLV stream even if the data is acquired via a different route (IPv4, IPv6, MPEG2-TS, URL, etc.) from the data acquired via the TLV stream of the broadcast route. As described above, the copy control state of the content specified by the copy control information can be specified as "unlimited copying" (which may be divided into two types: "unlimited copying and encryption processing required at the time of storage and output" and "unlimited copying and encryption processing not required at the time of storage and output"), "one generation only copying", "prescribed number of copies" (for example, 9 copies + 1 move is so-called "dubbing 10"), "no copying", etc.
[0342] Here, if the data position indicated by the location information includes MPEG2-TS data transmitted by other digital broadcast signals, the MPEG2-TS data is also associated with copy control information and broadcast in other digital broadcast signals. Then, the question arises as to which information to follow and how to perform copy control of the MPEG2-TS data (whether to follow 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, in order to solve this problem, the broadcast receiving device 100 may perform any one of the following solutions.
[0344] <Example 1> In a first 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 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 "predetermined number of times copy permitted," even if the data was acquired via a different route (digital broadcast in MPEG2-TS transmission format) from the data acquired in the TLV stream, copy control may be performed as "one-generation copy permitted" content. For example, if the copy control status indicated by the copy control information included in the TLV stream is "unlimited copy permitted" and the copy control status indicated by the copy control information included in the MPEG2-TS is "predetermined number of times copy permitted," even if the data was acquired via a different route (digital broadcast in MPEG2-TS transmission format) from the data acquired in the TLV stream, copy control may be performed as "unlimited copy permitted" content.
[0346] In the case of this operation, data acquired via a route other than the TLV stream can also be put into a copy state as desired for management 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 in the storage unit 110 or the like, recording on a removable recording medium, or outputting from a digital interface.
[0348] In this operation, for data obtained via a route other than the TLV stream, duplication of copy control states 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 states 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 description, 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 according to 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, and the like 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 as much as possible the description of the common points to avoid duplication. The following description is given assuming that the broadcast receiving device of this embodiment is a television receiver that supports both the MMT and MPEG2-TS media transport methods.
[0354] [Hardware configuration of broadcast receiving device] 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 expansion 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 the broadcast wave of the broadcast service adopting MMT as the media transport method via an antenna not shown, and tunes (selects) the channel of the service desired by the user based on 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 string, and outputs it to the MMT decoding processing unit 841. The second tuner / demodulation unit 832 receives the broadcast wave of the broadcast service adopting MPEG2-TS as the media transport method via an antenna not shown, and tunes (selects) the channel of the service desired by the user based on 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 string, and outputs it to the MPEG2-TS decoding processing unit 842.
[0357] The MMT decode processing unit 841 inputs the MMT data string output from the first tuner / demodulation unit 831, and performs separation processing and decoding processing of the video data string, audio data string, superimposed text data string, subtitle data string, etc., which are real-time presentation elements, based on the control signal included in the MMT data string. The MMT decode processing unit 841 is assumed to have functions equivalent to the 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, etc., in the broadcast receiving device 100 of the first embodiment. The MMT decode processing unit 841 is capable of performing various processes described in the first embodiment. The details of the various processes are as described in the first embodiment, so their description will be omitted.
[0358] The MPEG2-TS decoding processor 842 inputs the MPEG2-TS data string output from the second tuner / demodulator 832, and performs separation and decoding processes on the real-time presentation elements such as a video data string, an audio data string, a superimposed text data string, and a subtitle data string based on a control signal included in the MPEG2-TS data string. 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 of a broadcast service that employs MPEG2-TS as a 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 the monitor unit 862 and the like are driven based on the video information and the like input to the video RAM. The video synthesis unit 861 also 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 an MMT data sequence (or a part of it) or an MPEG2-TS data sequence (or a part of it) of a program transmitted via a communication line, and outputs it to an MMT decoding processing unit 841 or an MPEG2-TS decoding processing unit 842 as appropriate.
[0361] [Time display on broadcast receiving device] In the broadcast receiving device 800 of this embodiment, the current date and the current time can be displayed on the EPG screen, various setting screens, etc. The information on the current date and the current time is transmitted by MH-TOT or the like in a broadcast service that employs MMT as a media transport method, and is transmitted by TOT (Time Offset Table) or the like provided in SI (Service Information) defined in the MPEG-2 system in a broadcast service that employs MPEG2-TS as a media transport method. The broadcast receiving device 800 can acquire the information on the current date and the current time by referring to the MH-TOT or the TOT.
[0362] In general, when the video synthesis unit 861 mainly selects video information, etc. output from the MMT decoding processing unit 841, the information relating to the current date and current time obtained from the MH-TOT is superimposed on the video information, etc., and when the video synthesis unit 861 mainly selects video information, etc. output from the MPEG2-TS decoding processing unit 842, the information relating to the current date and current time obtained from the TOT is superimposed on the video information, etc.
[0363] However, since there are differences in encoding / decoding processes and transmission paths between a broadcast service that adopts MMT as a media transport method and a broadcast service that adopts MPEG2-TS as a media transport method, there is a possibility that inconsistency may occur, particularly in the current time display, when a broadcast service that adopts MMT as a media transport method is selected and when a broadcast service that adopts MPEG2-TS as a media transport method is selected. For example, as shown in Fig. 25, when the screen display is switched from an EPG screen 162g that displays channel information of a broadcast service that adopts MMT as a media transport method to an EPG screen 162h that displays channel information of a broadcast service that adopts MPEG2-TS as a media transport method, the display of the current time is switched from a current time display 162g1 to a current time display 162h1, which may cause the user to feel visual discomfort due to the inconsistency.
[0364] In the broadcast receiving device 800 of this embodiment, in order to prevent the user from feeling visual discomfort, even when the video synthesis unit 861 mainly selects the video information, etc. output from the MMT decoding processing unit 841, the broadcast receiving device 800 controls so that information related to the current date and current time acquired from the TOT is superimposed on the video information, etc. In other words, the broadcast receiving device 800 controls so that current time information provided by a broadcast service that adopts MPEG2-TS as a media transport method is superimposed on the content of the broadcast service that adopts MMT as a media transport method.
[0365] By performing the above control, the broadcast receiving device 800 of this embodiment always refers to the TOT when displaying the current time and displays the acquired current time information. Therefore, even when switching 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, it is possible to prevent the user from feeling visual discomfort due to inconsistency in the display of the current time.
[0366] 26A 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 the broadcast receiving device 800 is in a state where it is possible to receive a broadcast service that employs MPEG2-TS as the media transport method, it always refers to the TOT to acquire current time information, and only when it is not possible to receive a broadcast service that employs MPEG2-TS as the media transport method and it is possible to receive a broadcast service that employs MMT as the media transport method, it controls to acquire current time information by referring to the MH-TOT.
[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 current time information provided by a broadcast service that uses MMT as the media transport method, in the opposite manner to the above-mentioned control.
[0368] As described above, in either case, whether the current time information provided by a broadcast service that adopts MPEG2-TS as the media transport method is controlled to be 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 controlled to be 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] In addition, in both cases of 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 the MH-TOT or TOT transmitted by each broadcast service constituting the network may contain an error due to a malfunction of the transmitting system, a transmission error, etc. In the broadcast receiving device 800 of this embodiment, as a countermeasure against the MH-TOT or TOT error, when it is determined that the MH-TOT or TOT acquired from the service being received contains an error, the broadcast receiving device 800 has a function of acquiring the MH-TOT or TOT from another broadcast service in the same network or from an arbitrary broadcast service in another network, and performing a process of updating the time information of the built-in clock by referring to the current time information.
[0370] 26B shows an example of a current time information update process when a broadcast service using MPEG2-TS as a media transport method is received in the broadcast receiving device 800 of this embodiment. Note that even when a broadcast service using MMT as a media transport method is received, the same process as shown in the figure is possible.
[0371] When updating the time information of the built-in clock in the broadcast receiving device 800 of this embodiment, the receiving function execution unit 1102 first acquires the TOT from the MPEG2-TS data string of the currently being received broadcast service (broadcast service that employs MPEG2-TS as the media transport method) (S301), and further acquires the current time information by referring to the acquired TOT (S302). Next, the receiving function execution unit 1102 performs a process of comparing the current time information acquired in the process of S302 with the time information of the built-in clock.
[0372] If the result of the comparison process shows that the difference between the current time information acquired in the process of S302 and the time information of the built-in clock is within a predetermined value (for example, within 3 minutes) (S303: Yes), the receiving function execution unit 1102 updates the time information of the built-in clock with the current time information acquired in the process of S302 (S306). On the other hand, if the result of the comparison process shows that the difference between the current time information acquired in the process of S302 and the time information of the built-in clock is not within a predetermined value (S303: No), or if the TOT acquired in S301 has a flag or the like indicating that there is an error in the data, the receiving function execution unit 1102 acquires a TOT from an MPEG2-TS data string of another broadcasting service in the same network, or acquires an MH-TOT from an MMT data string of an arbitrary broadcasting service (broadcasting service that adopts MMT as a media transport method) in another network (S304), and further acquires current time information from the acquired TOT or MH-TOT (S305). The reception function execution unit 1102 may then perform the comparison process of S303 again using the current time information acquired in the process of S305.
[0373] Through the above processing, when the broadcast receiving device 800 of this embodiment determines that the MH-TOT or TOT obtained from the service being received contains an error, it becomes possible to update the time information of the built-in clock by obtaining the MH-TOT or TOT from another broadcast service on the same network, or from any broadcast service on another network, and referring to the current time information.
[0374] If the process of S304 to S305 is repeated and current time information whose difference with the time information of the built-in clock falls within a predetermined range cannot be obtained, such as during initial setting after shipping from the factory, the time information of the built-in clock can be set again using the current time information obtained in the process of S302. In this way, it is possible to deal with cases where there is an error in the time information of the built-in clock of the broadcast receiving device 800 of this embodiment.
[0375] [EPG display on broadcast receiving device] Event schedule information of a broadcast service that adopts MMT as a media transport method is transmitted by MH-EIT, etc. Meanwhile, event schedule information of a broadcast service that adopts MPEG2-TS as a media transport method is transmitted by EIT (Event Information Table) etc. provided in SI defined in the MPEG-2 system. Therefore, generally, when video information provided by a broadcast service that adopts MMT as a media transport method is displayed, the event schedule information (MH-EIT) of the broadcast service that adopts MMT can be acquired, and when video information provided by a broadcast service that adopts MPEG2-TS as a media transport method is displayed, the event schedule information (EIT) of the broadcast service that adopts MPEG2-TS can be acquired.
[0376] 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.
[0377] 27A shows an example of an EPG screen in the broadcast receiving device 800 of this embodiment. In the figure, the EPG screen 162i is an EPG screen created based on the MH-EIT of a broadcast service that adopts MMT as a media transport method, and "M1 TV", "M2 Broadcast", "M3 Channel", "M4TV", "TV M5", etc. are the broadcast station names of the broadcast service that adopts MMT as a media transport method. Also, the EPG screen 162j is an EPG screen created based on the EIT of a broadcast service that adopts MPEG2-TS as a media transport method, and "T6 TV", "T7 Broadcast", "T8 Channel", "T9TV", "TV TA", etc. are the broadcast station names of the broadcast service that adopts MPEG2-TS as a media transport method.
[0378] For example, when a user is watching a broadcast program provided by a broadcast service that employs MMT as a media transport method and instructs to display an EPG screen by operating a remote control (not shown), an initial screen of the EPG screen (not shown) 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 on broadcast programs on each channel from 17:00 (nearby the current time) on October 7, 2014 (today). Next, if the user wishes to check detailed information on broadcast programs on each channel from 20:00 on October 9, 2014, and instructs to update the EPG screen by operating a remote control (not shown), an EPG screen 162i is displayed.
[0379] Furthermore, if the user wishes to check detailed information on a broadcast program provided by a broadcast service that employs MPEG2-TS as a media transport method and instructs to switch the network by operating a remote control (not shown), the EPG screen 162j is displayed. At this time, the broadcast receiving device 800 of this embodiment controls to display detailed information on the broadcast programs of each channel on the same day and in the same time slot (i.e., from 20:00 on October 9, 2014) as the EPG screen 162i that was displayed immediately before, instead of the initial screen of the EPG screen (i.e., detailed information on the broadcast programs of each channel from 17:00 on October 7, 2014) created based on the EIT of the broadcast service that employs MPEG2-TS as a media transport method.
[0380] The above-mentioned control enables the user to continuously check detailed information about broadcast programs on the same day and at the same time on multiple networks using different media transport methods with a simple operation. In other words, the usability of the broadcast receiving device 800 is improved.
[0381] 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 where 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 a media transport method and channel information created based on the EIT of a broadcast service that employs MPEG2-TS as a media transport method are seamlessly displayed on the same time axis.
[0382] Therefore, even if a user desires to check channel information created based on the EIT of a broadcast service that adopts MPEG2-TS as a media transport method while checking channel information created based on the MH-EIT of a broadcast service that adopts MMT as a media transport method, it is possible to eliminate the need to instruct network switching by operating a remote control (not shown). Furthermore, the user can simultaneously check detailed information about broadcast programs 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.
[0383] Example 3 The following describes the third embodiment of the present invention. The configuration and effects of the third embodiment are the same as those of the first or second embodiment unless otherwise specified. Therefore, the following mainly describes the differences between the present embodiment and the first or second embodiment, and omits as much as possible the description of the common points to avoid duplication. In addition, in this embodiment, the cooperative operation between a broadcast receiving device and a mobile information terminal is described.
[0384] [Application transmission method overview] The application transmission method of this embodiment will be described with reference to FIG.
[0385] In the broadcasting system of this embodiment, a transmission method equivalent to the data carousel transmission method used in general digital broadcasting is possible. That is, in data download to a receiver or content transmission in a multimedia service, data is repeatedly transmitted so that the receiver can obtain necessary data at any time during broadcasting. Data is encapsulated and transmitted in asynchronous MPUs on a file-by-file basis. 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.
[0386] The path name of the files that compose the application is specified in the application description such as HTML5. The path name may be described 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 applied as information that links each table.
[0387] The receiver, to which a path name is specified by 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, from the data asset management table also in the data transmission message, 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 transmitted. Furthermore, by referring to the MP table, location information of the asset with the obtained component tag is obtained, and the asset to which the file is actually transmitted is specified. Within the specified asset, the unit of repeated transmission of the file corresponding to the carousel can be uniquely identified by the obtained download ID and the download ID written in the multi-extension header area of the MMTP packet transmitting the item, and among the repeatedly transmitted items, the item with the obtained MPU sequence number and item ID can be obtained as the desired file.
[0388] 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.
[0389] Furthermore, by constantly monitoring the data asset management table, the receiver can detect when the files that make up an application have been updated, and can always present the application in its latest state. Update detection may be possible at each stage, such as asset unit, MPU unit, or file unit. The data asset management table is 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 referring to the MP table, and an item having the obtained MPU sequence number and item ID can be acquired as the desired updated file.
[0390] The data content management table provides configuration information of files as data content in order to realize flexible and effective cache control. The unit presented within the data content (e.g., a page) is defined as a presentation unit, and information such as which items are related to that unit and which presentation units they are linked to is shown. This information makes it possible to know other items contained in the same presentation unit as the initially requested item. It is also possible to obtain information such as cache control on a presentation unit basis. As a result, the receiver can reduce the time required to retrieve the entire page and achieve preferential caching of the next page.
[0391] As mentioned above, applications and data are also transmitted as assets, and the asset type (asset_type) is described in the MP table (MPT: see FIG. 7B). The asset types are summarized in FIG. 29. In addition to broadcast video, audio, and subtitle data, applications and data used by applications are transmitted as assets. The assets of the applications and data used by the applications may be acquired from broadcast waves or via communication lines. An example of the data structure of location information (MMT_general_location_info) describing the acquisition destination of the assets is shown in FIG. 30A. The type of acquisition destination (location_type) and the acquisition destination are described in this location information. The meaning of the types of acquisition destinations is shown in FIG. 30B.
[0392] [Application presentation format] Like broadcast video and audio, applications are presented in regions defined in the layout setting table (LCT: see Fig. 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 Fig. 31.
[0393] [Application Control Information Summary] The application control information in this embodiment is information intended to inform a television receiver or the like (broadcast receiving device 100 in this embodiment) of the presence of an application (hereinafter, sometimes referred to as a broadcast-linked application) that links with a broadcast service and to instruct the control of the application in the broadcast communication linkage function supported by the 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.
[0394] 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 have an operating form in which start / stop, etc. are not controlled by the broadcast signal 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.
[0395] 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.
[0396] The type of application that is the subject of MH-AIT control is indicated by the "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" parameter. The application control code may be defined for each application type. If there is no definition for each application type, the code shall be used in the sense shown in Figure 32C.
[0397] An application is identified by an application identifier (application_identifier). An example of the data structure of an application identifier is shown in FIG. 32D. The application identifier is a value that uniquely identifies each application, defined for each application type. The application identifier may be composed of an organization identifier (organization_id) that identifies an 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 prevent the same identification value from being specified for different applications within the receiver, taking into account the validity period of the application cache (MH-cache information descriptor: see FIG. 6D).
[0398] [Descriptor to be included in MH-AIT] Information about each application is described in the parameters mentioned above as well as in the descriptors. Figures 6C and 6D show a list of the descriptors for this broadcasting system, but the main ones related to the MH-AIT are described in detail below.
[0399] (1) MH-Application Descriptor An MH-application descriptor shall 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 in which the target application can be executed. If the receiver implements this profile, it indicates that it has the capability to execute the target application. The content of the profile is defined for each application format.
[0400] (2) MH-Transmission Protocol Descriptor The purpose of this descriptor is to specify the transmission protocol for broadcasting, communication, etc. as the transmission means of the application, and to indicate the location information of the application depending on the transmission protocol, and the descriptor is placed in the common descriptor loop or application information descriptor loop of the MH-AIT for the number of transmission protocol labels of 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 sets 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 defined for each protocol identification. An example of the data structure of the selector area in the case of HTTP / HTTPS transmission and MMT non-timed transmission is shown in Figure 34C. It is possible to obtain information about the URL for acquiring the target application by the "URL_base_byte (URL base)" parameter, the "URL_extension_byte (URL extension)" parameter, etc.
[0401] (3) MH-Simple Application Location Descriptor The purpose of the MH-simple application location descriptor is 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. This 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.
[0402] (4) MH-Application Boundary Authority Setting Descriptor The purpose of the MH-application boundary permission setting descriptor is to set the application boundary and to set broadcast resource access permission for each area (URL), and one or more MH-application boundary permission setting 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.
[0403] (5) MH-Boot Priority Information Descriptor The purpose of the MH-launch priority information descriptor is 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 in which the application control code indicates an instruction to automatically launch the application (such as "AUTOSTART"). Also, 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.
[0404] (6)MH-Cache Information Descriptor The MH-cache information descriptor is intended for use in cache control when the resources that constitute an application are cached and stored when the application is expected to be reused, and a maximum of one shall be placed for each application in the application information descriptor loop of the MH-AIT. If this descriptor is not placed, the receiver may delete the resources that constitute the application without 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 of the target application. The higher 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.
[0405] The receiver stores the application version corresponding to the cached application, and if the application version is updated when the application is launched later, it does not use the application stored in the cache, but instead retrieves and uses a new application from the specified URL, and also rewrites the contents of the cache. The "expire_date (cache expiration date)" parameter indicates the cache expiration date of the target application as a date 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 is deleted from the cache. To set an indefinite expiration date, set this parameter to "0xFFFF". If this cache expiration date parameter is not set, the application may be prohibited from being cached after the program ends, placing importance on the operational stability of the application, or the cache may be held indefinitely for the convenience of the viewer, or the cache may be held for a predetermined period of time by balancing the two.
[0406] Also, instead of a cache expiration date, an expiration date for each application may be set. An example of the data structure of an MH-application expiration date descriptor, which describes the expiration date for each application, is shown in Fig. 38B. If this expiration date is exceeded, the use of the application is prohibited. Although long-term caching is not permitted, it is possible to permit a form of re-obtaining and using the application for a certain period of time, enabling a variety of application usage patterns.
[0407] (7)MH-Probabilistic Adaptive Delay Descriptor The MH-probabilistic application delay descriptor is intended to delay the timing of application control by a delay amount set probabilistically, assuming load balancing of server access for application acquisition, and a maximum of one is placed for each application in the application information descriptor loop of the MH-AIT. If this descriptor is not placed, the control action indicated by the control code is performed at the timing 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 (distribution 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 x range ÷ rate" based on the value "N" randomly selected from integers between "0" and "rate", and applies the control code by delaying it by the delay time from the time of receiving the MH-AIT. The "randomization_end_time (probabilistic application end time)" parameter indicates the time limit 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 lowest 16 bits of MJD, and the time is encoded in 24 bits of BCD for the hours, minutes, and seconds in JST.
[0408] Furthermore, the MH-AIT of this embodiment may further include parameters, descriptors, etc. different from those described above.
[0409] The operation of the broadcast receiving device 100 of this embodiment will be described below.
[0410] [Application startup sequence] First, the automatic start process of the broadcast cooperative 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. 40A. This is an example of the case where the broadcast cooperative app related to the selected channel is automatically started.
[0411] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs a process of selecting 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 (S1001). If the MH-AIT is not stored in the M2 section message, it may be determined that there is no broadcast-linked application related to the selected channel, and the automatic start process may be terminated. Next, the application format and application control code of each broadcast-linked application described in the MH-AIT are checked (S1002). If there is no broadcast-linked application having an application control code of "automatic start (AUTOSTART)" as a result of the process of S1002 (S1003: No), the automatic start process may be terminated. In this case, the launcher process can be performed again, which will be described later.
[0412] On the other hand, as a result of the process of S1002, if there is a broadcast linked application having an application control code of "automatic start" (S1003: Yes), the MH-start priority information descriptor of the MH-AIT related to the broadcast linked application is checked (S1004). Next, the broadcast linked application having the highest priority among the broadcast linked applications having the application control code of "automatic start" is selected (S1005), and the MH-application descriptor of the MH-AIT related to the selected broadcast linked application is checked (S1006). If the broadcast receiving device 100 satisfies the application profile described in the MH-application descriptor (S1007: Yes), proceed to the next process. If the broadcast receiving device 100 does not satisfy the application profile described in the MH-application descriptor (S1007: No), it is determined that the selected broadcast linked application cannot be started in the broadcast receiving device 100. In this case, it is checked whether there is a broadcast linked application with the next priority (S1008), and if there is no broadcast linked application with the next priority, the automatic start process may be terminated. If there is a broadcast cooperative application with the second highest priority, the broadcast cooperative application with the second highest priority is selected (S1009), and the processes of S1006 to S1007 are repeated.
[0413] If the broadcast receiving device 100 determines in the process of S1007 that the application profile described in the MH-application descriptor is satisfied, the MH-transmission protocol descriptor of the MH-AIT related to the selected broadcast linked application is checked (S1010). If the result of the process of S1010 indicates that the selected broadcast linked application can be acquired by HTTP / HTTPS transmission based on the protocol identification described in the MH-transmission protocol descriptor (S1011: Yes), the MH-simple application location descriptor of the MH-AIT related to the selected broadcast linked application is further checked (S1012), and the URL of the entry point of the selected broadcast linked application is acquired.
[0414] When the URL of the entry point of the selected broadcast cooperative app is acquired in the process of S1012, the LAN communication unit 121 then makes a broadcast cooperative app distribution request to a server (the service provider server 400 in this embodiment) on the Internet 200 specified by the URL (S1013). The service provider server 400 that has received the distribution request appropriately performs authentication processing of the broadcast receiving device 100 and then distributes the requested broadcast cooperative app (S1014). When the broadcast cooperative app is received from the service provider server 400 via the LAN communication unit 121, the broadcast receiving device 100 executes the launch of the received broadcast cooperative app in the browser unit 154 based on the control of the application control unit 153 (S1018). Note that the authentication processing of the broadcast receiving device 100 performed by the service provider server 400 may be a known processing, and detailed description thereof will be omitted.
[0415] On the other hand, if the process of S1010 shows that the selected broadcast-linked application 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 application is transmitted using the procedure described in the above-mentioned [Overview of application transmission method]. Furthermore, when the broadcast-linked application is acquired from the identified asset of the broadcast wave (S1017), the broadcast receiving device 100 executes the launch of the received broadcast-linked application in the browser unit 154 under the control of the application control unit 153 (S1018).
[0416] The above series of processes enables automatic start-up of a broadcast cooperative app based on the MH-AIT transmitted by broadcast waves in the broadcast receiving device 100 of this embodiment. Note that the MH-AIT confirmation process in each of the processes of S1004, S1006, S1010, and S1012 may be performed by acquiring the MH-AIT from the broadcast waves and confirming it each time, or by 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.
[0417] Next, the launcher process of the broadcast cooperative 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 the broadcast cooperative app related to the selected channel is started based on the user's instruction.
[0418] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs a process of selecting 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 (S1101). If the MH-AIT is not stored in the M2 section message, it may be determined that there is no broadcast-linked application related to the selected channel, and the automatic start process may be terminated. Next, the application format and application control code of each broadcast-linked application described in the MH-AIT are checked (S1102). If the result of the process of S1102 shows that there is a broadcast-linked application having an application control code of "automatic start (AUTOSTART)" (S1103: Yes), the automatic start process shown in FIG. 40A is possible.
[0419] On the other hand, if there is no broadcast linked application having an application control code of "automatic start" as a result of the process of S1102 (S1103: No), it is checked again whether there is a broadcast linked application having an application control code of "executable (PRESENT)", and if there is no broadcast linked application having an application control code of "executable" (S1104: No), the launcher process may be terminated. If there is a broadcast linked application having an application control code of "executable" (S1104: Yes), the MH-application descriptor of the MH-AIT related to each of the broadcast linked applications having the application control code of "executable" is confirmed (S1105). If there is no broadcast linked application whose application profile described in the MH-application descriptor is satisfied by the broadcast receiving device 100 as a result of the process of S1105 (S1106: No), the launcher process may be terminated. If there is at least one broadcast linked application whose application profile described in the MH-application descriptor is satisfied by the broadcast receiving device 100 (S1106: Yes), proceed to the next process.
[0420] After the processes of S1101 to S1103 and S1104 to S1106 are completed, the broadcast receiving device 100 is not yet executing the broadcast linked application, and a normal broadcast program video is displayed on the monitor unit 162. In this state, when the user instructs the broadcast receiving device 100 to start a broadcast linked application launcher using a remote control or a mobile information terminal capable of operating the broadcast receiving device 100 (S1107), a list of broadcast linked applications executable by the broadcast receiving device 100 is OSD-displayed on the monitor unit 162 (S1108). Furthermore, when the user instructs the selection of a desired broadcast linked application from the list of broadcast linked applications by operating the remote control or the mobile information terminal (S1109), the application control unit 153 selects a broadcast linked application based on the user's instruction (S1110), and acquires and starts the selected broadcast linked application (S1111 to S1119). The processes in S1111 to S1119 may be similar to the processes in S1010 to S1018 shown in FIG. 40A.
[0421] The above series of processes enables the broadcast receiving device 100 of this embodiment to perform launcher processing of the broadcast linked application based on the MH-AIT transmitted by the broadcast wave. Note that the confirmation processing of the MH-AIT in each of the processes of S1105, S1111, and S1113 may be performed by acquiring the MH-AIT from the broadcast wave each time, or by caching the MH-AIT acquired in the process of S1101 and confirming the cached MH-AIT. Also, the order of the processes of S1104 to S1106 and the processes of S1107 to S1110 may be interchanged. In this case, the profile confirmation processing of S1104 to S1106 may be performed only for the broadcast linked application selected in the process of S1110. Furthermore, the list of broadcast linked apps displayed in the processing of S1108 may display only those that are executable on the broadcast receiving device 100 according to 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 are not executable on the broadcast receiving device 100. Furthermore, the above-mentioned operation sequence is merely an example, and a different processing procedure may be used.
[0422] 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.
[0423] When the tuner / demodulator 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.
[0424] After the processes of S1201 to S2106 are completed, the broadcast receiving device 100 is not yet executing the broadcast cooperative application, and a normal broadcast program video is displayed on the monitor unit 162. In this state, when the user issues an instruction to start a data broadcast screen using a remote control or a mobile information terminal capable of operating the broadcast receiving device 100 (S1207), (if the data broadcast screen can be displayed), the data decoder 151 acquires a BML document or the like from the data carousel of the MMT data string, and creates a data broadcast screen by interpreting the acquired BML document or the like, and displays it on the monitor unit 162 (S1208). Note that, if there is at least one broadcast cooperative application that satisfies the application profile confirmed in the process of S1206 by the broadcast receiving device 100, an entry button related to the broadcast cooperative application is displayed on the data broadcast screen displayed in the process of S1208. If there is no broadcast cooperative application that satisfies the application profile confirmed in the process of S1206 by the broadcast receiving device 100, the entry button related to the broadcast cooperative application may not be displayed, or may be displayed in an invalid state.
[0425] Furthermore, when the user operates the remote control or mobile information terminal to instruct the selection (launch) of the entry button of the desired broadcast-linked application displayed on the data broadcast screen (S1209), the application control unit 153 selects a broadcast-linked application based on the user's instruction (S1210) and acquires the selected broadcast-linked application (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. When the acquisition of the selected broadcast-linked application is completed in 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 application (S1220).
[0426] The above series of processes enables the broadcast receiving device 100 of this embodiment to start a broadcast cooperative application based on the MH-AIT transmitted by the broadcast wave from the data broadcast screen. The MH-AIT confirmation process in each of the processes of S1205, S1211, and S1213 may be performed by acquiring the MH-AIT from the broadcast wave and confirming it, or the MH-AIT acquired in the process of S1201 may be cached and the cached MH-AIT may be confirmed. The order of the processes of S1204 to S1206 and S1207 may be interchanged. The process of S1219 may be performed immediately after the process of S1209. Alternatively, the process of S1219 may not be performed, and the broadcast cooperative application, the data broadcast screen, the broadcast program video, and the like may be simultaneously displayed in each area obtained by dividing the display area of the monitor unit 162 based on the description of the LCT. The above operation sequence is merely an example, and a different processing procedure may be used.
[0427] In the startup sequences of the broadcast linked app described using Figures 40A to 40C, examples are described 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.
[0428] Furthermore, if there is no response from the service provider server 400 or the like for a predetermined period of time or longer when a distribution request for the broadcast cooperative 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 cooperative app may be displayed.
[0429] 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 in a different sequence.
[0430] [Operation sequence when linking mobile information terminals] In the broadcast receiving device 100 of this embodiment, it is assumed that the function of the 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) prepared by a television receiver manufacturer, it is possible to use the mobile information terminal 700 as a high-function remote control for the broadcast receiving device 100. In addition, it is possible to execute the broadcast cooperative app on the mobile information terminal 700 and 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 the function by cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700, it is preferable that the cooperative control app is running on the mobile information terminal 700, and the broadcast cooperative app operating on the mobile information terminal 700 is controlled by the cooperative control app.
[0431] 41A is an operational sequence diagram showing an example of the operation when the cooperative control app is started up on the mobile information terminal 700. The diagram shows a series of flows 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 in the storage unit 710 of the mobile information terminal 700 as a cooperative control program 7002. If the cooperative control program 7002 has not been installed, the cooperative control program 7002 is first installed.
[0432] When a user operates the operation unit 730 of the mobile information terminal 700 to instruct the launch of a cooperative control application (S1301), the cooperative control execution unit 7102 of the mobile information terminal 700 first searches for television receivers capable of communicating (cooperative operation) on the network (S1302), and displays the search results as a list of television receivers on the 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 the mobile information terminal 700 in the past and those that do not, and in that case, it is desirable to be able to determine whether or not there is a history of cooperative operation in the past from the display format. Furthermore, if no television receiver capable of communication is found, a message to that effect may be displayed and the process may end.
[0433] When the user operates the operation unit 730 of the mobile information terminal 700 to select a specific television receiver (broadcast receiving device 100 of this embodiment) from the list of television receivers (S1304), if the broadcast receiving device 100 has a history of performing a linking operation with the mobile information terminal 700 in the past (S1305: Yes), authentication information related to the broadcast receiving device 100 (login name and password specified by the broadcast receiving device 100, etc.) is read from the authentication information memory area 7300 of the storage unit 710 (S1306), and the process proceeds to the next step.
[0434] On the other hand, if the broadcast receiving device 100 does not have a history of performing a linked operation with the mobile information terminal 700 in the past (S1305: No), the linked 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 linked control execution unit 7102 receives the login screen information and displays the login screen on the display unit 741 (S1309). Note that, if the linked control application has login screen information related to the broadcast receiving device 100 in advance, the processing of S1307 to S1308 may be omitted. When the user inputs authentication information to 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.
[0435] In addition, the determination as to 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 memory area 7300 of the storage unit 710, or may be made by other methods.
[0436] Next, the cooperative control execution unit 7102 transmits the authentication information read in the process of S1306 or the authentication information input in the process of S1310 to the broadcast receiving device 100 (S1311). Note that the process 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.
[0437] In the broadcast receiving device 100, the authentication information transmitted from the mobile information terminal 700 is compared with the authentication information stored in the authentication information storage area 1300 of the storage unit 110 to check whether the received authentication information is correct (S1312). If the process of S1312 checks 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 process of S1312 checks 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.
[0438] 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, a high-function remote control screen) on the display unit 741 (S1314). On the other hand, when the linkage control execution unit 7102 receives an authentication result (authentication NG), it does not display the basic screen of the linkage control app and ends the operation of the linkage control app. In this case, it is desirable to display an error message or the like notifying the fact that authentication is NG.
[0439] Through the above series of processes, the mobile information terminal 700 and the broadcast receiving device 100 are ready for cooperative operation.
[0440] Note that, in the case where a broadcast cooperative app is to be launched in the broadcast receiving device 100 following the above-mentioned processing, the processing in Figs. 40A to 40C may be performed after the above-mentioned processing.
[0441] 41B is an operation sequence diagram showing an example of the operation when the cooperative control app is started up 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-up sequence of the broadcast cooperative app, requests the start-up of the cooperative control app on the mobile information terminal 700.
[0442] 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 application having an application control code of "automatic start (AUTOSTART)", and checks the profile of the broadcast-linked application having the application control code of "automatic start" (S1401). Note that the processing of S1401 may be the same as the processing of S1001 to S1009 shown in FIG. 40A.
[0443] In the profile confirmation process of the top priority application in S1401, if the broadcast receiving device 100 satisfies the application profile of the top 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 of this embodiment) that has a history of cooperative operation with the broadcast receiving device 100 in the past by referring to the authentication information storage area 1300 of the storage unit 110 (S1402). In the profile confirmation process of the top priority application in S1401, if the broadcast receiving device 100 satisfies the application profile of the top priority application and it is determined that a cooperative operation with a mobile terminal device is not necessary, the same process as that of FIG. 40A may be performed. In the profile confirmation process of the top priority application in S1401, if the broadcast receiving device 100 does not satisfy the application profile of the top priority application, the start-up process of the broadcast cooperative application and the start-up process of the cooperative control application may be terminated.
[0444] The selection of the mobile information terminal 700 by referring to the authentication information storage area 1300 may be made by selecting the mobile terminal device having the latest collaboration history or the most frequently used mobile terminal device. Information on a plurality of mobile terminal devices having collaboration history may be displayed on the monitor unit 162 to allow 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 application may be started by an operation on the mobile information terminal 700 side. The process in this case is as shown in FIG. 41A.
[0445] The cooperative control execution unit (not shown) of the broadcast receiving device 100 transmits a cooperative control application start request to the portable information terminal 700 selected in the process of S1402 (S1403).
[0446] When the main control unit 701 of the mobile information terminal 700 starts the cooperative control app (cooperative control execution unit 7102) in response to the cooperative control app start request transmitted from the broadcast receiving device 100 (S1404), the cooperative control execution unit 7102 executes a series of processes (S1405 to S1408) such as reading authentication information related to the broadcast receiving device 100 from the authentication information memory area 7300 of the storage unit 710, transmitting the authentication information to the broadcast receiving device 100, and authenticating the mobile information terminal in the broadcast receiving device 100. Note that the processes of S1405 to S1408 may be similar to the processes of S1306 and S1311 to S1313 shown in FIG. 41A.
[0447] 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 on the display unit 741 (e.g., an advanced remote control screen) (S1409), and transmits a linkage control app startup success response to the broadcast receiving device 100 (S1410). On the other hand, when the linkage control execution unit 7102 receives an authentication result (authentication NG), 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 the operation of the linkage control app.
[0448] When the broadcast receiving device 100 receives a start success response from the mobile information terminal 700, it acquires and starts the broadcast cooperative app selected in the processing of S1401 (S1411). 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 start the broadcast cooperative app selected in the processing of S1401. If the broadcast cooperative app is capable of an operation mode that does not require cooperative operation with a mobile terminal device, it may be started in that operation mode.
[0449] Through the above series of processes, the mobile information terminal 700 and the broadcast receiving device 100 are ready for cooperative operation.
[0450] Note that, following the above-mentioned processing, in the case where the broadcast cooperative application (terminal side) is also started up in the mobile information terminal, the processing in FIG. 41C may be performed after the above-mentioned processing.
[0451] FIG. 41C is an operational sequence diagram showing an example of the operation when the broadcast cooperative application (terminal side) is started up in the mobile information terminal 700 based on the transmission information from the broadcast receiving device 100. As shown in FIG.
[0452] That is, after executing the processes of S1401 to S1411 in 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 application (S1502). If the result of the process of S1502 is that the terminal side broadcast cooperative application can be acquired by HTTP / HTTPS transmission according to 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 application (S1504) and acquires the URL of the entry point of the terminal side broadcast cooperative application. When the URL of the entry point of the terminal side broadcast cooperative application is acquired in the process of S1504, the application control unit 153 transmits the information of the URL to the mobile information terminal 700 (S1505).
[0453] 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 (the service provider server 400 in this embodiment) 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, distributes the requested terminal-side broadcast cooperative app after appropriately performing authentication processing of the mobile information terminal 700 (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 start of the received terminal-side broadcast cooperative app in the browser engine based on the control of the already-activated cooperative control app (coordination control execution unit 7102) (S1512). Note that the authentication processing of the mobile information terminal 700 performed by the service provider server 400 may be a known processing, and detailed description will be omitted.
[0454] On the other hand, if the result of the process of S1502 indicates that the terminal side broadcast cooperative 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 the DAM table stored in the data transmission message (S1508, S1509), and identifies the asset to which the terminal side broadcast cooperative app is transmitted using the procedure described in the above-mentioned [Outline of application transmission method]. Furthermore, when the terminal side broadcast cooperative app is acquired from the identified asset of the broadcast wave (S1510), the broadcast receiving device 100 transmits the acquired terminal side broadcast cooperative app to the mobile information terminal 700 (S1511). Furthermore, in the mobile information terminal 700, the terminal side broadcast cooperative app transmitted from the broadcast receiving device 100 is executed by a browser engine based on the control of the already started cooperative control app (cooperative control execution unit 7102) (S1512).
[0455] The terminal side broadcast cooperative app acquired in S1510 may be stored in the content information storage area 1200 of the storage unit 110, and in the process of S1511, instead of the transmission process of the terminal side broadcast cooperative app, the URL of the content information storage area 1200 may be transmitted, 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 cooperative app. If the mobile information terminal 700 has a function of receiving digital broadcasts, the mobile information terminal 700 may acquire the terminal side broadcast cooperative app from broadcast waves.
[0456] Furthermore, the processing of S1502 to S1512 may be executed with a terminal-side broadcast cooperative app transmission request (not shown) transmitted from the mobile information terminal 700 to the broadcast receiving device 100 as a trigger after S1501.
[0457] In addition, each operation sequence in Figures 40A to 40C and Figures 41A to 41C can be partially combined as appropriate, and further, some operation steps can be appropriately interchanged in order or operated simultaneously with other operation steps.
[0458] [Basic screen of mobile information terminal linkage control app] 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 a function as a high-performance remote control compatible with the broadcast receiving device 100.
[0459] The basic screen 741a of the cooperative control application is composed of a power key 741a1, a network selection key (digital terrestrial, BS, CS) 741a2, number keys (1 to 12) 741a3, a volume UP / DOWN key 741a4, a channel UP / DOWN key 741a5, an input switching key 741a6, a program guide key 741a7, a data key 741a8, a cooperative application key 741a9, a menu key 741aa, a back key 741ab, cursor keys (up, down, left, right) 741ac, a decision key 741ad, and color keys (blue, red, green, yellow) 741ae. Other operation keys may also be displayed.
[0460] For ease of use, each of the operation keys may have the same key arrangement / operation as that of a dedicated remote control included with the broadcast receiving device 100. In addition, the power key 741a1, network selection key 741a2, numeric keys 741a3, etc. have the same functions as the operation keys of a general television remote control, and detailed explanations thereof will be omitted. The linked application key 741a9 is an operation key provided for the broadcast communication linking function of this embodiment.
[0461] In the process of S1107 in Fig. 40B, it is assumed that a broadcast linked application launcher can be requested to be started by selecting the linked application key 741a9. In addition, in the process of S1207 in Fig. 40C, it is assumed that a data broadcasting start request can be made by selecting the data key 741a8. In addition, 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 key 741ac and the enter key 741ad.
[0462] In this way, by providing the linked application key 741a9 or another operation key having a similar function on the 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. In addition, the linked application key 741a9 or another operation key having a similar function may be provided on a dedicated remote control attached to the broadcast receiving device 100.
[0463] 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.
[0464] The basic screen 741b of the cooperative control app is composed of a cooperative control message 741b1 and a cooperative control app operation screen 741b2. Other objects may be further displayed. The cooperative control 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 in which an arbitrary screen display is performed by the cooperative control app, and detailed description is omitted in this embodiment. For example, the configuration in the cooperative control app operation screen 741b2 may be the same as the basic screen 741a of the cooperative control app described above. A sub-screen of a broadcast program displayed on the broadcast receiving device 100, etc. may be displayed.
[0465] 42B, by displaying the cooperative control in progress message 741b1, the user of the mobile information terminal 700 can easily understand that the mobile information terminal 700 is operating in cooperation with the broadcast receiving device 100. Note that the cooperative control in progress message 741b1 is not limited to a character display, and may be a symbol display, a graphic display, or the like. A difference in background color, or the like, may be used as an alternative to the cooperative control in progress message 741b1.
[0466] [Broadcast linkage app launcher screen on broadcast receiving device] FIG. 43A is a screen display diagram showing an example of a notification screen for notifying a user that there is a broadcast cooperative app that can be activated in the broadcast receiving device 100 of this embodiment.
[0467] For example, in the operation sequence shown in Fig. 40B, after the process of S1106, neither the data broadcast by the broadcast service nor the broadcast linked application is started, 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 inform the user that there is a broadcast linked application that can be started, 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 overlooking the existence of a broadcast linked application that can be started.
[0468] The display position of the icon 162m0 may be any position on the screen, but it is preferable that the display position is a position that does not interfere with viewing of a broadcast program. For example, 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 displayed at all times, 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.
[0469] Fig. 43B is a screen display diagram showing an example of the broadcast cooperative application launcher displayed by the process of S1108 in Fig. 40B. In this embodiment, it is assumed that three broadcast cooperative applications, cooperative application A, cooperative application B, and cooperative application C, are executable by the broadcast receiving device 100 according to the description of the MH-AIT or the like. In this case, the broadcast cooperative application launcher 162n1 is displayed at an arbitrary position on the broadcast program screen 162n, and further, an entry button 162n2 of the cooperative application A, an entry button 162n3 of the cooperative application B, an entry button 162n4 of the cooperative application C, and a back button 162n5 are displayed in the broadcast cooperative application launcher 162n1. The position where the broadcast cooperative application launcher 162n1 is displayed may be controlled by the description of the LCT.
[0470] 43B, 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 decision key 741ad on the basic screen 741a of the linkage control application, a linkage application A, a linkage application B, a linkage application C, or the like may be started under the control of the application control unit 153. When a back button 162n5 is selected, the display of the broadcast linkage application launcher 162n1 may be terminated.
[0471] In addition, when the broadcast cooperative application launcher 162n1 is displayed on the broadcast program screen 162n, the frame color, inner color, shape, font, size, blinking state, etc. of each entry button may be appropriately changed according to the type and security status 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 is blue, if the cooperative application B is a non-broadcast managed application, the frame color of the entry button 162n3 is yellow, and if the cooperative application C is a general application, the frame color of the entry button 162n4 is red, etc. Alternatively, if the cooperative application A is determined to be reliable in terms of security, the frame color of the entry button 162n2 is blue, if the cooperative application B is determined to be not necessarily reliable in terms of security, the frame color of the entry button 162n3 is yellow, and if the cooperative application C is determined to be dangerous in terms of security, the frame color of the entry button 162n4 is red, etc.
[0472] In addition, the frame color, inner 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 cooperative application, or depending on the expiration date of use of each broadcast cooperative application. The frame color, inner color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on whether the broadcast cooperative application has been acquired from a network or not. For example, if the cooperative application A has already been acquired from a network (already cached in the cache 152, etc.), the frame color of the entry button 162n2 is set to blue, if the cooperative application B is being acquired, the frame color of the entry button 162n3 is set to yellow, and if the cooperative application C has not been acquired, the frame color of the entry button 162n4 is set to red, etc.
[0473] In this way, the user of the broadcast receiving device 100 can easily grasp the types of broadcast cooperative applications that can be executed on the broadcast receiving device 100, the security status, and the like.
[0474] Also, the broadcast cooperative application launcher 162n1 may not be displayed if there is no broadcast cooperative application executable 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 cooperative application launcher 162n1.
[0475] [Data broadcasting screen on broadcast receiving device] Fig. 44 is a screen display diagram showing an example of a data broadcast screen displayed by the process of S1208 in Fig. 40C. In this embodiment, it is assumed that three broadcast cooperative applications, cooperative application A, cooperative application B, and cooperative application C, are executable by the broadcast receiving device 100 due to the description of the MH-AIT, etc. In this case, an entry button 162o2 of the cooperative application A, an entry button 162o3 of the cooperative application B, and an entry button 162o4 of the cooperative application C are displayed at arbitrary positions on the data broadcast screen 162o. Note that the display positions of the program video 162o1, the entry buttons 162o2 to 162o4, and other contents on the data broadcast screen 162o may be controlled by the description of the LCT after grouping them by area.
[0476] On the data broadcasting screen 162o as shown in FIG. 44, when the entry button 162o2, the entry button 162o3, the entry button 162o4, etc. are 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.
[0477] In addition, when displaying the data broadcasting screen 162o, the frame color, inner 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 in the case of displaying the entry button of each broadcast linked app on the broadcast linked app launcher 162n of Figure 43B.
[0478] In this way, the user of the broadcast receiving device 100 can easily grasp the types of broadcast cooperative applications that can be executed on the broadcast receiving device 100, the security status, and the like.
[0479] [Broadcast linkage app execution screen on broadcast receiving device] FIG. 45A is a screen display diagram showing an example of a broadcast cooperative application 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 application of this embodiment has graphics capabilities and effect capabilities by HTML5 description, and is capable of overlay display with the broadcast program screen on the monitor unit 162. For example, as shown in FIG. 45A, a broadcast cooperative application 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 application unit 162p1 may be controlled by the description of the LCT. The broadcast cooperative application 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 be further displayed.
[0480] In a state where the broadcast cooperative application section 162p1 is overlaid on the broadcast program screen 162p, it is possible to terminate the execution of the broadcast cooperative application and move to a data broadcast screen by selecting a data key 741a8 on the basic screen 741a of the cooperative control application. It is also possible to terminate the execution of the broadcast cooperative application and return to the display of only the broadcast program screen 162p by selecting a cooperative application key 741a9 on the basic screen 741a of the cooperative control application. The above process may be realized by a different operation key.
[0481] In addition, in a state where 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 of the basic screen 741a of the cooperative control application. The process of changing the transparency may be performed collectively for the entire broadcast cooperative application section 162p1, or may be performed individually for each o...
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 scheduled 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 for viewing; 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 names of broadcast programs and the attributes of the broadcast programs, in the storing step, when the broadcast program content received in the receiving step is a content designated as being copy-only-one-generation protected, or when the broadcast program content received in the receiving step is a content designated as being copy-able without restriction and as being protected by encryption, the broadcast program content stored in the storing step is stored in an encrypted state so that the broadcast program content 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 for viewing in the output step, and the move of the broadcast program content to the external device in the move processing step can be performed via the same IP interface configured with Ethernet-compatible hardware; When the IP address of the external device is not in the same subnet as the IP address of the broadcast receiving device, from a state in which the broadcast program content is stored in a storage unit at the output destination of the IP interface in the storage step, the broadcast program content can be output for viewing to the external device in the output step for the external device paired with the broadcast receiving device, but the broadcast program content is prohibited from being moved to the external device in the move processing step, In the display of the EPG screen, a broadcast program corresponding to data broadcasting is displayed to indicate that the broadcast program corresponds to data broadcasting. Content protection processing method.
Citation Information
Patent Citations
Digital information receiver and digital information receiving method
JP2007251962A
Recording system, receiving apparatus, recording apparatus, recording control method, and program
JP2010041329A
Receiver, receiving method, and output control method
JP2011139192A
Recording / reproducing device, recording / reproducing method
JP2011160153A
Digital content receiving apparatus and digital content receiving method
JP2013175272A
