Receiving device and transmitting method

Abstract

This embodiment makes it easy to understand the operations of scheduling and canceling viewing and scheduling and canceling recording. [Solution] In an embodiment, in a receiving device configured to be able to schedule viewing of a broadcast program in accordance with the hybrid cast method using application functions embedded in an HTML document related to digital broadcasting, the HTML document includes information that can be used to determine whether a viewing reservation or cancellation of a viewing reservation, or a recording reservation or cancellation of a recording reservation can be made under the hybrid cast method, thereby improving user convenience.

Description

[Technical field]

[0001] This embodiment relates to a technology that applies an API (Application Programming Interface: a set of commands and functions that can be used when developing software for an application execution environment) for digital broadcasting that complies with the Hybridcast technical specifications. [Background technology]

[0002] Hybridcast is a system that integrates broadcasting and communications using HTML5 (Hyper Text Markup Language 5), enabling a wide variety of services. Hybridcast technical specifications have been standardized as IPTV Forum technical specifications and ARIB (Association of Radio Industries and Businesses) standards. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2015-27082 A [Non-patent literature]

[0004] [Non-Patent Document 1] "Hybridcast Technical Specifications Service Guidelines" IPTVFJ DOC-0002 1.6 Edition, revised April 19, 2013, IPTV Forum, General Incorporated Association [Non-Patent Document 2] "Broadcasting and Communication Collaboration System" IPTVFJ STD-0010 Version 2.1 Revised March 7, 2016, IPTV Forum, General Incorporated Association [Non-Patent Document 3] "HTML5 Browser Specification" IPTVFJ STD-0011 Version 2.2 Revised on March 7, 2016, IPTV Forum, General Incorporated Association [Non-Patent Document 4] "Hybridcast Operational Guidelines" IPTVFJ STD-0013 2.4 edition, revised June 22, 2016, IPTV Forum, General Incorporated Association [Non-Patent Document 5] "Data Broadcasting Coding and Transmission Standards for Digital Broadcasting" ARIB STD-B24 Version 6.3, revised July 6, 2016, Association of Radio Industries and Businesses [Non-Patent Document 6] "Standard for Multimedia Coding Method (2nd Generation) for Digital Broadcasting" ARIB STD-B62 Version 1.6, revised September 29, 2016, Association of Radio Industries and Businesses Summary of the Invention [Problem to be solved by the invention]

[0005] There is a demand for a transmitting device, a receiving device, or a transmitting / receiving system based on the above-mentioned standards that is capable of implementing, for example, any one of viewing reservation, recording reservation, viewing reservation cancellation, recording reservation cancellation, or a combination of these. [Means for solving the problem]

[0006] According to one embodiment, a receiving device is configured to be able to schedule viewing or recording of a broadcast program in accordance with a hybrid cast system by using a function of an application embedded in an HTML document related to digital broadcasting, comprising: The function includes: A first function related to the viewing reservation and a second function related to the cancellation of the viewing reservation are included, When the first function is obtained, a function is started to inquire a user before executing the viewing reservation whether or not to make the viewing reservation; When the first function is obtained, a function is started to create an EPG in which one or more programs to be scheduled are marked; When the second function is obtained, a function is activated to inquire of the user before executing whether or not to cancel the viewing reservation; When the second function is obtained, a function is started to create an EPG in which one or more programs to be reserved for viewing are marked, and the EPG can be removed from the EPG, and the function is started to create an EPG in which one or more programs to be reserved for viewing are marked, and the EPG can be removed from the EPG. The function further includes: a third function related to the recording reservation and a fourth function related to canceling the recording reservation; When the third function is obtained, a function is started to inquire of the user before executing the recording reservation. If the third function is obtained, a function is started to create an EPG in which one or more programs to be scheduled for recording are marked; When the fourth function is obtained, a function is started to inquire of the user before executing whether or not to cancel the scheduled recording; When the fourth function is obtained, a function for creating the EPG that allows one or more programs to be marked for recording to be removed from the EPG in which one or more programs to be recorded are marked is started, means for enabling the viewing reservation to be set based on detection of the first function; a means for enabling cancellation of the viewing reservation based on detection of the second function; means for enabling the recording reservation to be set based on detection of the third function; a means for enabling cancellation of the scheduled recording based on detection of the fourth function; A receiving apparatus is provided having the following: [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of an entire system of hybridcast specifications to which an embodiment is applied. [Diagram 2] FIG. 2 is a diagram showing the configuration of FIG. 1 in more detail. [Diagram 3] FIG. 3 is a diagram showing a schematic configuration of a broadcasting station. [Figure 4] FIG. 4 is an explanatory diagram for explaining main streams and information in the broadcast wave transmission path and the hybridcast transmission path. [Diagram 5] FIG. 5 is a diagram illustrating an example of a schematic configuration of a receiver to which the embodiment is applied. [Figure 6] FIG. 6 is a block diagram showing a schematic configuration of a part of the main points of a receiver to which the embodiment is applied. [Figure 7]FIG. 7 is a schematic explanatory diagram of the above-mentioned Hybridcast-compliant receiver from the standpoint of hardware, reception or communication functions, and applications. [Figure 8] FIG. 8 is a diagram for explaining an example of functions related to viewing reservation, recording reservation, reservation cancellation, and the like. [Figure 9] FIG. 9 is a diagram for explaining an example of a rule related to an argument (event_ref) of a viewing reservation function, a recording reservation function, a reservation cancellation function, and the like (when specifying an event transmitted in the MPEG2-TS format). [Figure 10] FIG. 10 is a diagram for explaining another example of the rules regarding the arguments (event_ref) of the viewing reservation function, the recording reservation function, the reservation cancellation function, and the like (when specifying an event transmitted in the MMT method). [Figure 11A] FIG. 11A is a diagram for explaining other examples of functions related to viewing reservation, recording reservation, reservation cancellation, and the like. [Figure 11B] FIG. 11B is a continuation of FIG. 11A. [Figure 12] FIG. 12 is a diagram for explaining an example of a function (method) relating to confirmation of a connection state to an IP network. [Figure 13] FIG. 13 is a diagram for explaining an example of a function (method) related to acquisition of an application object. [Figure 14A] FIG. 14A is a diagram for explaining part of the correspondence between classes and extension function group designations in broadcast extension functions (including EPG-related functions, etc.). [Figure 14B] FIG. 14B is a diagram for explaining other parts of the correspondence relationship between classes and extension function group designations in broadcast extension functions (including AIT controlled application cooperation functions, etc.). [Figure 15] FIG. 15 is a diagram illustrating an example of the correspondence between receiver modes and service modes regarding data broadcasting activated by a receiver. [Figure 16] FIG. 16 is a flowchart for explaining an example of the start-up operation of the data broadcast processing system in the BML / ARIB-J shared receiver. [Figure 17]FIG. 17 is a diagram illustrating an example of the correspondence between the broadcast extension function (AIT controlled application cooperation function) and the name space that can be specified. [Figure 18A] FIG. 18A is a diagram illustrating an example of a correspondence relationship (part 1) between some extension functions (getBrowserSupport()) and character strings specified as arguments thereof. [Figure 18B] FIG. 18B is a diagram illustrating a second example of the correspondence between some extension functions (getBrowserSupport()) and character strings specified as their arguments. [Figure 18C] FIG. 18C is a diagram illustrating a third example of a correspondence relationship between some extension functions (getBrowserSupport()) and character strings specified as arguments thereof. [Figure 19] FIG. 19 is a diagram illustrating an example of how the permission bitmap (permission_bitmap) used in the embodiment is used. [Figure 20A] FIG. 20A is a diagram illustrating an example of the relationship (part 1) between bit values, function assignments, and operations in bitmap 0 and bitmap 1. [Figure 20B] FIG. 20B is a diagram illustrating an example of the relationship (part 2) between bit values, function assignments, and operations in bitmap 0 and bitmap 1. [Figure 21] FIG. 21 is a diagram illustrating a data structure of an external application control descriptor that can be used in the embodiment. [Figure 22] FIG. 22 is a diagram illustrating a bitmap showing the correspondence between application classes and bit values. [Diagram 23] FIG. 23 is a diagram illustrating an example of the correspondence between broadcast extension functions (IPTV linkage functions) and name spaces that can be specified. [Figure 24] FIG. 24 is a flowchart illustrating an example of a process on the transmitting side to which the embodiment is applied. [Figure 25A] FIG. 25A is a flowchart (part 1) illustrating an example of a receiving-side process to which the embodiment is applied. [Figure 25B]FIG. 25B is a flowchart (part 2) illustrating an example of the process on the receiving side to which the embodiment is applied. [Figure 26] FIG. 26 is a diagram showing an example of an alert screen (a window screen that overlaps with the currently displayed video) that asks the user whether or not to accept a reservation using a function. [Figure 27] FIG. 27 is a diagram showing an example of a screen display when a recording or viewing reservation is made. [Figure 28] FIG. 28 is a diagram showing an example in which an alert screen for inquiring of the user as to whether or not to accept a reservation using a function is displayed in an overlapping window on the screen display of FIG. [Figure 29] FIG. 29 is a diagram showing an example of a reservation list when recording reservations have been made. [Diagram 30] FIG. 30 is a diagram showing an example of an operation screen that enables a user on the receiver side to check the reservation details and cancel part of the reservation. [Diagram 31] FIG. 31 is a diagram showing an example of an EPG display screen on which reserved programs are marked. [Diagram 32] FIG. 32 shows another example of a program guide display used when viewing a broadcast program, or when programming a viewing schedule, cancelling a viewing schedule, programming a recording schedule, or cancelling a recording schedule. [Diagram 33] FIG. 33 is a diagram showing yet another example of a display of a program guide used when viewing a broadcast program, or when programming a viewing reservation, canceling a viewing reservation, programming a recording, or canceling a recording reservation. [Diagram 34] FIG. 34 is a diagram showing still another example of the display of a program guide used when viewing a broadcast program, or when programming a viewing reservation, canceling a viewing reservation, programming a recording, or canceling a recording reservation. [Diagram 35] FIG. 35 is a diagram showing yet another example of the display of a program guide used when viewing a broadcast program, or when programming a viewing reservation, canceling a viewing reservation, programming a recording, or canceling a recording reservation. [Diagram 36]FIG. 36 is a flow chart shown for explaining an example of the operation of the service providing device and the receiver when viewing a broadcast program, or when making a viewing reservation, canceling a viewing reservation, or making a recording reservation, or canceling a recording reservation. [Figure 37] FIG. 37 is a flow chart shown for explaining an example of the operation when the parental lock function is activated in the above-mentioned receiver. [Figure 38] FIG. 38 is a flow chart shown for explaining the operation when the personal parental lock function is used in the above-mentioned receiver. [Figure 39] FIG. 39 is a diagram showing an embodiment showing an expanded use form of the terminal link function of the receiver. [Diagram 40] FIG. 40 is an explanatory diagram showing the functional blocks of the home gateway and the types of sensors in the sensor group 7200. [Diagram 41] FIG. 41 is a diagram showing an embodiment regarding power-on of the first and second processing units of the receiver. [Diagram 42] FIG. 42 is a diagram illustrating another example of a start-up sequence of an HTML application. [Diagram 43] FIG. 43 is a diagram showing an embodiment showing a further expanded use of the terminal link function of the receiver and the home gateway. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment will be described with reference to the drawings. Fig. 1 is a diagram showing an example of the configuration of an entire system of the hybridcast specification (also called the hybridcast standard or the IPTV standard) to which the embodiment is applied. Fig. 2 is a diagram showing the configuration of Fig. 1 in more detail.

[0009] The following description will be given with reference to FIG. 1 and FIG.

[0010] <Broadcast Station 1000> The broadcast station 1000 includes a broadcast station server 1100 and a security device 1200. The broadcast station 1000 transmits broadcast signals (in this specification, any signal such as BS broadcast, CS broadcast, or terrestrial digital broadcast) via radio waves. The broadcast station 1000 also transmits digital broadcast signals, application control information, control information related to presentation, and the like, and can provide metadata related to programs, video content, and the like to a service provider device (sometimes referred to as a service business operator) 3000 based on a contract.

[0011] The application control information notifies receivers compatible with this system of applications linked to programs, and also includes commands and control information for starting and stopping the applications.

[0012] The transmission method of the application control signal includes, for example, a transmission method using a dedicated ES (Elementary Stream), a data cart (a transmission method that repeatedly transmits the same data), and a method of acquiring a control signal file stored on a server in a communication network. A hybridcast-compatible receiver, which will be described later, acquires the application from the specified URL according to the instructions of the application control signal and executes control such as application boundaries.

[0013] In this system, the broadcast station 1000 operates the broadcast station server 1100. The broadcast station server 1100 provides metadata such as a program title, a program ID, a program summary, performers, broadcast date and time, and other data to the receiver. The information provided by the broadcast station 1000 to the service provider device 3000 is provided through an API (Application Programming Interface) provided in the broadcast station server 1100.

[0014] In addition, the broadcast station 1000 can exchange data with the hybridcast service provider device 3000. In other words, the broadcast station 1000 can provide metadata about programs, video content, and the like to the service provider device 3000 based on a contract.

[0015] <Service provider device 3000> The service provider device 3000 includes a server 3100 for each service and an application database 3200. The service provider device 3000 is used by the service provider to produce and distribute contents and applications for providing services to the receiver 5000, and to realize individual services. The service provider device 3000 is also used when the service provider sells various services to users and makes contracts with them. The service provider may also be a platform provider such as a broadcasting station or a VOD service.

[0016] Furthermore, when the service provider device 3000 is accessed by the receiver 5000 which is the user, the access is not necessarily limited to an API.

[0017] The service provider device 3000 manages applications and can distribute the applications to the receiver 5000. The service-specific server 3100 in this device has a server function for implementing each service (e.g., a VOD program recommendation service, a multilingual subtitle service, a social TV service, etc.). The service-specific server 3100 not only implements the functional aspects of the service, but also transmits the content (VOD content, subtitle data, etc.) that constitutes the service.

[0018] The server 3100 for each service also includes a repository. The repository is used to register applications for this system for distribution, and can provide or search for a list of available applications in response to an inquiry from a receiver.

[0019] <Receiver 5000> The receiver 5000 can receive various broadcast programs and various service information by receiving broadcast signals. The receiver 5000 has a function for realizing a broadcast communication function cooperation service in addition to a function (basic function) for receiving digital broadcasts.

[0020] That is, the receiver 5000 has the following functions in addition to a broadband network connection function: a function to execute an application in response to application control information transmitted by broadcast, a function to perform presentation by linking broadcast and communication, a terminal linking function, etc.

[0021] The terminal link function can access broadcast resources such as program information in response to a request from another terminal, and can call up a receiving function such as playback control.

[0022] A storage medium 5001 for recording and reproducing data can be connected to the receiver 5000, and it is also possible to connect a display device 5002 and a speaker system 5003 (these may already be included in the receiver 5000).

[0023] <Linked terminal 7000> The linked terminal 7000 can communicate with the receiver 5000 by using the communication function. The mobile terminal 7000 can also communicate with the service provider device 3000 by using the communication function.

[0024] 3 shows an outline of the main components of the broadcast station 1000. The broadcast station 1000 includes a video encoder 1301, an audio encoder 1302, a subtitle encoder 1303, and an auxiliary data generator 1304 that generates other control data, service data, and the like. The broadcast station 1000 is also connected to a broadcast station server 1100 and a security device 1200.

[0025] The outputs of the video encoder 1301, audio encoder 1302, subtitle encoder 1303, and auxiliary data generator 1304, which generates other control data, service data, and the like, are converted into streams, and the streams are multiplexed in a multiplexer 1305. The multiplexed stream is sent to a transmitter 1306 as a transport stream, multiplexed onto broadcast waves, and transmitted from an antenna.

[0026] The broadcast station 1000 also includes a transceiver 1310 for communicating with the service industry device 3000 .

[0027] 4 shows main streams and information in the broadcast wave transmission path 2100 and the hybridcast transmission path 2200. In each transmission path, a video stream, an audio stream, application control information, and service information are transmitted. In the hybridcast transmission path 2200, not only a downstream stream from the service provider device 3000 to the receiver 5000, but also an upstream stream from the receiver 5000 to the service provider device 3000 exists.

[0028] 5 is a diagram showing a schematic configuration example of a receiver 5000 to which an embodiment is applied. The receiver 5000 has a first processing unit (which may be called a communication content processing unit) 5100 of the hybrid cast specification connected to a network, and a second processing unit (which may be called a broadcast content processing unit) 5300 that receives broadcast waves. The network is connected to the service provider device 3000 mentioned above.

[0029] The first processing unit 5100 includes an IP communication interface 5101. A stream captured via the IP communication interface 5101 is received by a streaming reception processing unit 5102, and the demodulated stream is restored to its original arrangement by a demultiplexer 5103. A DRAM processing unit 5104 is connected to the demultiplexer 5103, and the DRAM processing unit 5104 can operate a program, for example, to execute an automatic download.

[0030] The video stream separated by the demultiplexer 5103 is decoded by a video decoder 5111 , the audio stream is decoded by an audio decoder 5112 , and the subtitle stream is decoded by a subtitle decoder 5113 .

[0031] The decoded video data and subtitle data can be mixed by a mixer 5501 and input to a display device 5002. The decoded audio data can be input via a mixer 5502 to a speaker system.

[0032] The second processing unit 5300 includes a broadcast tuner 5301. A stream received and demodulated by the broadcast tuner 5301 is input to a descrambler 5302. In the descrambler 5302, the input stream is descrambled by a key from a CAS (Conditional Access System) module 5304. The stream descrambled by the descrambler 5302 is input to a demultiplexer 5303. The demultiplexer 5303 outputs data for data broadcasting to a data broadcasting reception processing unit 5330. In addition, the video stream separated by the demultiplexer 5303 is decoded by a video decoder 5311, the audio stream is decoded by an audio decoder 5312, and the subtitle stream is decoded by a subtitle decoder 5313. The decoded video data and subtitle data can be mixed by a mixer 5501 and input to a display unit 5002. The decoded audio data can be input to the speaker system 5003 via the synthesizer 5502 .

[0033] The data broadcast signal separated by the demultiplexer 5303 is received by the data broadcast reception processing unit 5330 and input to the data broadcast engine 5315. The display signal transmitted by the data broadcast is input to the combiner 5501 and displayed on the display 5502.

[0034] An integrated controller 5200 is provided as a means for controlling the overall operation of the receiver 5000. The integrated controller 5200 has an application control unit 5201 and a security management unit 5202. The application control unit 5201 controls each block of the receiver 5000 based on various information and control information included in application control information.

[0035] The security management unit 5202 manages applications and realizes security functions. For example, it has an application authentication function and treats authenticated applications as management applications. It also has an access control function, a presentation function, an enforcement function, a revocation function (function for management applications other than broadcasting), etc.

[0036] The access control function allows applications that are permitted to use it to refer to broadcast resources (video, audio, metadata SI information, etc.) and receiver resources (receiver video and audio output, network interface, etc.) It also restricts the receiver APIs that can be accessed according to the security class of the application.

[0037] The presentation control function determines how applications are displayed (whether or not to overlay broadcast videos, display area and size, display / hide, etc.) based on the broadcaster's intentions. Furthermore, in emergencies such as disaster reporting, it is possible to control the full-screen display of broadcast programs by temporarily hiding applications or related displays, for example.

[0038] The revocation function allows the disabling of problematic applications that harm the interests of broadcasters and users.

[0039] The application engine 5130 forms an environment for executing applications. As the application engine 5130, for example, an HTML5 browser equipped with an extended API for supporting hybrid cast is used.

[0040] The terminal cooperation control unit 5500 is an interface that executes cooperation with an external cooperation terminal.

[0041] Fig. 6 shows the overall configuration of the receiver in Fig. 5, with the parts related to the hybrid cast receiver being clearly shown. Broadcast waves are received and processed by the second processing unit 5300. Signals received via the Internet are processed by the first processing unit 5100. The integrated control unit 5200 controls the first processing unit 5100 and the second processing unit 5300, and also controls a GUI (graphic interface) to control the display states of the first processing unit 5100 and the second processing unit 5300.

[0042] FIG. 7 is an explanatory diagram showing a schematic view of the above-mentioned Hybridcast-compliant receiver from the standpoint of hardware 5601, reception or communication function 5602, and application 5603.

[0043] The hardware 5601 includes a communication interface (communication I / F), a tuner, a decoder, and the like.

[0044] In the reception or communication function 5602, the broadcast reception and playback function is a function that receives broadcast waves, selects a specific broadcast service, and synchronizes and plays back the video, audio, subtitles, and data broadcasts that constitute the service. The communication content reception and playback function is a function that accesses video content stored in a server on a communication network, receives it as VOD streaming, and synchronizes and plays back the video, audio, and subtitles that constitute the content. The application control function is a function that works on the application engine mainly for management applications based on application control information acquired from a server on a communication network or a broadcast signal, and controls and manages the life cycle and events of each application. The security management function is a function that, mainly related to the application control function, appropriately implements functional restrictions on applications based on rules related to security management that are specified, depending on the application state and instructions specified by broadcast signals, etc. The terminal linkage control function is a function that performs device discovery in linkage with an external linkage terminal, and manages the connection between the receiver and the linkage terminal and the linkage of applications, and acts as an interface. There is a presentation synchronization control function, which is a function that controls the presentation synchronization of streams such as video and audio received by broadcasting and streams such as video and audio received by streaming.

[0045] In the application 5603, the application engine is a function for acquiring and executing an application (corresponding to an HTML5 browser). The application launcher mainly executes navigation for the user to select and launch a managed application other than broadcasting.

[0046] <Explanation regarding hybrid cast specifications> Meanwhile, the broadcast station 1000 in FIG. 1 is configured to transmit a broadcast signal including high-resolution content, for example, 2K, 4K, or 8K, to the receiver 5000. A service provider 3000 that develops a service business in cooperation with the broadcast station 1000 distributes applications to the receiver 5000, for example, using the Internet, to provide various services. This service can be provided using HTML5 (or later versions of HTML). The distributed application can be a script-type computer program (JavaScript (registered trademark) using Java (registered trademark), ECMA script, etc.) that can be embedded in an HTML document. (Hereinafter, this computer program will be abbreviated as "script" as appropriate. In the embodiment, JavaScript can be adopted as the script.) Scripts embedded in HTML (HTML5 and later) can include various functions. For example, when scheduling viewing or recording, the script can include functions described in ARIB STD-B62 Part 2 (Multimedia Coding Language Specification) and ARIB TR-B39 Part 3 (Advanced BS Digital Broadcasting Multimedia Service Operational Provisions). An example is shown below: partial interface ReceiverDevice { boolean isScheduledToTune( ISDBResourceReference event_ref, optional Date startTime); void scheduleToTune( ISDBResourceReference event_ref, optional Date startTime); void unscheduleToTune( ISDBResourceReference event_ref); boolean isScheduledToRecord( ISDBResourceReference event_ref, optional Date startTime); void scheduleToRecord( ISDBResourceReference event_ref, optional Date startTime); void unscheduleToRecord( ISDBResourceReference event_ref);};……….

[0047] In the above example, "isScheduledToTune()" and "scheduleToTune()" are functions related to viewing schedules (see Figs. 8(a) and (b)), "isScheduledToRecord()" and "scheduleToRecord()" are functions related to recording schedules (see Figs. 8(d) and (e)), and "unscheduleToTune()" and "unscheduleToRecord()" are functions related to reservation cancellation (see Figs. 8(c) and (f)). The viewing schedule function, recording schedule function, reservation cancellation function, etc. are functions used as appropriate by the transmitting side (broadcast station and / or service provider) and are executed (or monitored or detected or utilized) as appropriate by the receiving side (receiver user). The reservation cancellation function can be used when the receiver user cancels part or all of a program that is about to be (or has been) reserved by the transmitting side by operating the remote control, etc.

[0048] Alternatively, the functions described in ARIB STD-B24 Part 2 (XML-based multimedia coding method) (see the EPG-related function classes in FIG. 14A) can be used in the script.

[0049] Recording on the receiving side can also be considered as an operation of storing recorded content (one or more programs that have been scheduled for recording) in the receiving side's storage (hard disk drive, flash memory, optical disk, etc.). Therefore, in the embodiment, the term "recording" will also cover the case of storage as appropriate.

[0050] Different rules can be set for the argument (event_ref) of the reservation-related functions (isScheduledToTune(), scheduleToTune(), isScheduledToRecord(), scheduleToRecord(), unscheduleToTune(), unscheduleToRecord()) depending on the event transmission method.

[0051] When specifying an event transmitted in MPEG2-TS format, event_ref must be an object that is interpreted as referring to a resource transmitted in MPEG2-TS, and the handling of each of its properties is specified as shown in Figure 9.

[0052] When specifying an event transmitted using the MMT method, event_ref must be an object that is interpreted as referring to a resource transmitted using MMT, and the handling of each of its properties is specified as shown in Figure 10.

[0053] Note that functions (methods) such as those shown in (a) to (f) of FIGS. 11A to 11B can also be used for viewing reservation, recording reservation, reservation cancellation, and the like.

[0054] The connection state of the receiver to the IP network can be confirmed, for example, by using the function (method) in Fig. 12. In addition, the receiver can obtain an application object, for example, by using the function (method) in Fig. 13.

[0055] In a system compatible with (compliant with) the hybridcast system (for example, the transmission / reception system in FIG. 1), various operations can be performed using broadcast extension functions such as those shown in FIG. 14A and FIG. 14B. For example, the transmitting side (broadcast station 1000 and / or service provider 3000 in FIG. 1) can use an HTML document to schedule viewing, recording, cancel reservations, etc., for a receiver (receiver 5000 in FIG. 1) that complies with the hybridcast system. For these viewing, recording, and cancellation, functions (for example, EPG-related function functions shown in FIG. 14A) included in a script (JavaScript, etc.) embedded in the HTML document can be used.

[0056] Fig. 15 is a diagram illustrating the correspondence between receiver types and service types for data broadcasting activated by a receiver. When only BML is used as data broadcasting, it is not assumed that multiple BML documents will be switched in groups. However, with ARIB-J, multiple ARIB-J applications can be sent simultaneously, and it is assumed that the viewer (receiver user) will switch between them. Therefore, a mechanism is provided that manages the life cycle of ARIB-J applications using an application information table (AIT) and allows the viewer to switch between them using the receiver's functions.

[0057] In a receiver compatible with both BML and ARIB-J, BML documents are also managed as applications. For this purpose, ARIB STD-B23 specifies a receiver function called the application manager. In a receiver compatible with BML / ARIB-J, this application manager can control the life cycle of the processing presented by the BML document. Using this application manager, it is possible to control the launch of BML and ARIB-J, as shown in Fig. 15.

[0058] Fig. 16 is a flow chart explaining an example of the start-up operation of the data broadcast processing system in the BML / ARIB-J shared receiver. If data broadcasting by ARIB-J is being sent, additional_arib_j_info() exists as a data encoding method descriptor in the PMT. When the shared receiver tries to start the data broadcast processing system, it searches the PMT (ST10) and checks whether additional_arib_j_info() exists in the PMT (ST12).

[0059] If there is no additional_arib_j_info() (N in ST12), data broadcasting by ARIB-J is not being transmitted, so additional_bxml_info() in the PMT is obtained (ST14) and BML is started (ST20).

[0060] If additional_arib_j_info() is present (Y in ST12), refer to invocation_priority in additional_arib_j_info(). If invocation_priority is "0" (ARIB-J has priority), obtain the AIT transmitted by the AIT transmission method (ST16).

[0061] When invocation_priority is "1" (receiver setting takes priority), the receiver setting is obtained (ST18). When the receiver setting is set to "ARIB-J priority," the AIT is obtained (ST16). When the receiver setting is set to "BML priority," additional_bxml_info() is obtained (ST14) and BML is started (ST20). When invocation_priority is "2," BML takes priority, additional_bxml_info() is obtained (ST14), and BML is started (ST20).

[0062] After obtaining the AIT (ST16), to start ARIB-J, the application_control_code in the AIT is referenced (ST22). If application_control_code is AUTOSTART (Y in ST22), the ARIB-J application starts automatically (ST24). If application_control_code is not AUTOSTART (PRESENT, etc.) (N in ST22), the startup of the ARIB-J application is put on hold (ST26) and the AIT is monitored. If the AIT is updated during monitoring and application_control_code becomes AUTOSTART, the ARIB-J application starts automatically (ST24). By specifying a default ES (e.g. 0xA0) in which the ARIB-J application is placed, this type of monitoring and other startup sequences can be easily performed.

[0063] When the BML is started (ST20), the URL of the AIT described in the BML can be referenced to obtain the AIT (the AIT on the communication server) from the Internet. The above-mentioned permission bitmap (permission_bitmap) can be obtained from this AIT. (This permission_bitmap can be used in ST200 in FIG. 25A, for example. The acquisition of the AIT will be described later with reference to FIG. 42.) Fig. 17 is a diagram illustrating the correspondence between broadcasting extension functions (AIT controlled application linking function) and name spaces that can be specified. Here, for modules, resources, ES / NPT general-purpose event components, and name spaces on IP transmission paths, "startReceivingAIT() whose argument as a URI description element is ait_uri," "getReceivedAIT() whose argument as a URI description element is ait_uri," and "startAITControlledApp() whose argument as a URI description element is ait_uri" can be specified. Note that when the return value as a URI description element is Array[][2], the name spaces that the function "getReceivedAIT()" corresponds to are modules, resources, and name spaces on IP transmission paths.

[0064] 18A to 18C show examples of the correspondence between some extension functions (getBrowserSupport()) and character strings specified as their arguments.

[0065] Fig. 19 is a diagram illustrating how a permission bitmap (permission_bitmap) used in the embodiment is used. Fig. 20A and Fig. 20B are diagrams illustrating the relationship between bit values, function allocations, and operations in bitmap 0 and bitmap 1. Fig. 21 is a diagram illustrating the data structure of an external application control descriptor that can be used in the embodiment.

[0066] Whether a receiver can make viewing reservations, recording reservations, cancel reservations, etc. under the hybrid cast method can be configured to determine, for example, using the bit value of permission_bitmap (see the ``○'' mark in ``Viewing reservation, recording reservation API'' shown in bit 4 of Figure 20B).

[0067] Whether or not a receiver complies with the Hybridcast system can be determined using a specific bit value of permission_bitmap (eg, bits 0 to 2 in FIG. 20B).

[0068] The permission_bitmap is a bitmap that determines access authority, and the access permission for each broadcasting resource can be determined by a 16-bit bitmap for each function. The upper 3 bits of the permission_bitmap indicate the bitmap switching, and the assignment of other function bitmaps can be specified in the actual operation.

[0069] If the permission_bitmap determines that the user does not have access permission, the receiver disables the access. For example, if the permission_bitmap determines that the user does not have access permission for the hybrid cast method, the receiver can be configured not to access an HTML document that includes a reservation-related function.

[0070] The permission_bitmap can be included in the external application control descriptor (see FIG. 21). This external application control descriptor is transmitted in the application information table (AIT) specified in ARIB STD-B24, Part 4, 5.1. The AIT including the permission_bitmap (part of the information used to control non-broadcast managed applications) can be acquired by using the function of the AIT controlled application cooperation function (see FIG. 14B).

[0071] 22 is a diagram illustrating a bitmap showing the correspondence between application classes and bit values. This bitmap shows the class of the application for which access authority is set. In this bitmap, if multiple bits are 1, the range can be set by ORing the range of each class.

[0072] 23 is a diagram illustrating the correspondence between broadcasting extension functions (IPTV linkage functions) and name spaces that can be specified. Here, "startDlcDownload() whose argument as a URI description element is src_path" and "startVOD() whose argument as a URI description element is metafile_uri" can be specified as name spaces on an IP transmission line.

[0073] 24 is a flowchart for explaining an example of a process on the transmitting side to which the embodiment is applied. The contents of this process can be determined by the intention of the transmitting side (for example, the broadcast station 1000 and / or the service provider 3000 in FIG. 1).

[0074] First, if you want to reserve one or more programs sent by the broadcast station 1000 (Y in ST100), create a reservation script (JavaScript, etc.) for each program to be reserved using a reservation function (ST102). If you want to make the reservation cancelable (Y in ST104), write a reservation cancellation function in the script (ST106).

[0075] If you want to schedule recording (storage) of one or more programs sent by broadcast station 1000 (N in ST100, Y in ST110), create a schedule script (JavaScript, etc.) for each program to be scheduled for recording using a schedule recording function (ST112). If you want to be able to cancel the schedule (Y in ST114), write a schedule cancellation function in the script (ST116).

[0076] If the reservation cancellation function is not written in the script (N in ST104, N in ST114), or if two or more scripts have been created after the reservation cancellation function is written in the script (ST106, ST116), the contents of those scripts are merged in the processing order (ST120). The merged script is embedded in the HTML5 document.

[0077] As information for checking whether the receiving side complies with Hybridcast, for example, functions that can be used to acquire an AIT including a permission_bitmap (such as "startReceivingAIT()" and "getReceivedAIT()" in FIG. 14B) can be considered. If such check information is not present in the HTML document (N in ST122), the information is added to the HTML document (ST124). After the creation of the HTML document with the check information added is completed, if there is any further addition (or modification) of a reservation (N in ST126), the processes of ST100 to ST124 are repeated. If the created HTML document is OK, the process of FIG. 24 ends (Y in ST126). The HTML document created in this way (HTML5 or later document) can be sent to the receiving side via the Internet.

[0078] Fig. 25A and Fig. 25B are flowcharts for explaining an example of a receiving-side process to which the embodiment is applied. Fig. 26 is a diagram showing an example of an alert screen (a window screen overlapping a currently displayed video) that asks the user whether to accept a reservation using a function.

[0079] Fig. 27 is a diagram showing an example of a screen display when a recording or viewing reservation is made, and Fig. 28 is a diagram showing an example of a case where an alert screen for asking the user whether to accept a reservation using a function is displayed in an overlapping window on the screen display of Fig. 27.

[0080] Fig. 29 is a diagram showing an example of a reservation list when a recording reservation has been made. Fig. 30 is a diagram showing an example of an operation screen on which a user on the receiver side checks the reservation contents and cancels some of the reservations. Fig. 30 is a diagram showing an example of an EPG display screen on which reserved programs are marked.

[0081] When the receiving side (for example, one of the receivers 5000 in FIG. 1) receives the HTML document (HTML5 or later document) created by the process in FIG. 24, it starts the process in FIG. 25A. The reservation-related information in the sent HTML document is based on the premise of the hybridcast method. If a reservation-related script in the HTML document is processed by a receiver that does not support hybridcast, there is a possibility that the reservation operation intended by the sender will not be completed, so first it is checked whether the receiver complies with hybridcast (ST200).

[0082] This check can be performed, for example, by checking whether a specific bit in the permission_bitmap included in the AIT corresponds to a bit (ID bit) that identifies Hybridcast. (If the HTML document contains information other than the permission_bitmap that can indicate Hybridcast compliance, that information can be used for the check.) If the receiving side is not compliant with Hybridcast (N in ST202), the script in the received HTML document is not processed and the process returns to another step. If the receiving side is compliant with Hybridcast (Y in ST202), the script in the HTML document is checked to see if it has a function related to reservations (ST204). If there is no function related to reservations (N in ST204), the process returns to another step without any processing.

[0083] If the script in the HTML document contains one or more functions related to reservations (Y in ST204), the user is queried as to whether or not to make a reservation using one or more functions described in the script (ST206). This inquiry can be made immediately after the determination in ST204 is YES.

[0084] One possible method of inquiring whether or not to make a reservation is to display an overlapping window 200 (FIG. 26(b)) for "confirming the reservation" in a partial area 100a (FIG. 26(a)) of the screen 100 currently being displayed on the user's receiver. The window 200 popped up on the top of the screen 100 could display, for example, "A viewing reservation (or recording reservation) has been made by the broadcast station. Would you like to make a reservation? If you want to make a reservation, select "Yes" or if not, select "No" using the remote control keys and confirm." This display can be configured so that it does not disappear until the user selects "Yes" or "No" and confirms.

[0085] 27, when the window 300 for reserving recording or viewing is displayed, a reduced screen 400 of the program to be reserved can be displayed as a moving image. Browsers after HTML5 also support video display, so a screen display (100) including such a reduced screen display (400) of the video can be displayed on the browser screen. By being able to display a moving image, for example, when a user makes a reservation, the user can check the contents on the reduced screen and can accurately determine whether or not to accept the reservation.

[0086] When such a window 300 or reduced screen 400 is displayed, the receiver may receive an HTML document (HTML document of HTML5 or later) including a reservation function from the sender (broadcast station or server). In that case, as shown in the example of Fig. 28, an alert screen asking the user whether to accept a reservation using the function of the HTML document can be displayed in an overlapping window 200 on the current screen display (Fig. 27). For example, when the user selects and confirms the "Reserve" button in window 200 using the remote control, a program reservation (recording reservation and / or viewing reservation) is made based on the reservation function of the HTML document. The reservation at this time can include a program that the user himself selected for reservation (for example, a program to be broadcast from 10:00 on Saturday, October 22nd).

[0087] Along with or instead of outputting the overlapping window 200, voice guidance for "confirming the reservation" may be given. For example, voice guidance such as "A viewing reservation has been made by the broadcasting station. Would you like to reserve? If you want to reserve, say 'I will reserve' to the television, otherwise say 'I will not reserve,'" may be given through the speaker of the receiver 5000. (The receiver may be provided with a microphone and voice recognition unit (not shown) to recognize the user's response to the voice guidance and perform processing corresponding to the content of the response.) This voice guidance may be configured to be repeated at a fixed interval until the user replies with "I will reserve" or "I will not reserve." Whether or not this voice guidance is given can be determined by the user's prior settings for the receiver.

[0088] Returning now to the explanation with reference to Fig. 25A, if the user selects and confirms "No" in window 200 (Fig. 26(b)), or responds by voice "I don't want to make a reservation" (N in ST208), the program returns to another process without any processing. If the user selects and confirms "Yes" in window 200, or responds by voice "I want to make a reservation" (Y in ST208), the program performs processing according to the contents of the reservation.

[0089] That is, when there is one or more functions for recording reservation in the script in the HTML document, those functions are used to create a reservation list (see FIG. 29) of one or more programs for which recording reservation is available (ST210), or those functions are used to create an EPG (see the mark RRM in FIG. 31) in which one or more programs for which recording reservation is available are marked (ST210).

[0090] If there is one or more functions for viewing reservation in the script in the HTML document, those functions are used to create a reservation list (not shown, but equivalent to FIG. 29 excluding the "recording destination" item) of one or more programs to be viewed (ST212). Alternatively, those functions are used to create an EPG (see the mark RWM in FIG. 29) in which one or more programs to be viewed are marked (ST212).

[0091] A user viewing the recording reservation list (FIG. 29) or an EPG with recording reservation markings (FIG. 31) can cancel the recording of some or all of the reserved programs by operating the remote control, etc. If the user wishes to cancel some or all of the recording reservations (Y1 in ST214), and there is a function for canceling recording reservations, a user operation screen (see FIG. 30) for canceling recording reservations is created for each program on the reservation list (ST216). Alternatively, an EPG is created (ST216) that allows the user to remove the reservation marking for each program from an EPG in which one or more programs to be recorded are marked (see the Mark RRM in FIG. 31).

[0092] Similarly, the viewing reservation list (Figure 29 A user who views the EPG (FIG. 31) with the marking for viewing reservation (excluding the "recording destination" item from the EPG) or the EPG with the marking for viewing reservation can cancel the viewing reservations of some or all of the reserved programs. When a user wants to cancel some or all of the viewing reservations (Y2 in ST214), if there is a function for canceling viewing reservations, a user operation screen for canceling viewing reservations (not shown, but equivalent to FIG. 29 excluding the "USB_HDD1" item) is created for each program on the reservation list (ST218). Alternatively, an EPG is created so that the reservation marking can be removed for each program from an EPG (see the mark RWM in FIG. 31) in which one or more programs to be viewed are marked (ST218).

[0093] When one or more programs reserved on the reservation list or EPG are partially or entirely cancelled (Y in ST220), the viewing and / or recording reservation processing after the reservation cancellation operation is carried out (ST222). When none of the one or more programs reserved on the reservation list or EPG is cancelled (N in ST220), the viewing and / or recording reservation processing without reservation cancellation is carried out (ST224). When the above reservation processing is completed, the process returns to other processing.

[0094] Each receiver can be configured so that the user can change the reservation contents (including cancelling the reservation altogether) after the reservation has been made.

[0095] In other words, the function used to perform the above-mentioned scheduled viewing, scheduled recording, or reservation cancellation may be the function used to display the overlapping window as described above, or this function may include a separate function used to display the overlapping window. Note that the overlapping window is not necessarily limited to a window, and may be a confirmation display (button) used by the user to indicate whether or not to confirm the reservation or reservation cancellation, and may have a function to inquire the user about the availability of the recording and storage operations via the user interface of the receiver.

[0096] Fig. 42 is a diagram for explaining an example of a start-up sequence of an HTML application. Fig. 42 illustrates a network-related start-up sequence SQ1 starting from trigger A and a broadcast-related start-up sequence SQ2 starting from trigger B.

[0097] When starting an application that complies with the ARIB Phase 0 operation specifications, SQ1 is used for the application startup sequence. That is, it always starts with the startup of data broadcasting content (trigger A), and does not directly start an HTML (HTML5 or later version in this embodiment) application. When starting an application, the BML content is started first (sequence SQ1), the AIT on the communication server is obtained by the script written in the content, and thereafter, the HTML application (such as an application that uses reservation-related functions) is started according to the AIT.

[0098] In addition to sequence SQ1, sequence SQ2 can be used to start an application that complies with the ARIB Phase 1 operation specifications. That is, it is possible to specify whether to start BML content or directly start an HTML application, based on the priority information in the PMT (Program Map Table) and the priority information in the AIT in section format transmitted by the data carousel. When directly starting an HTML application, the application is obtained and started according to the information specified in the AIT transmitted by the data carousel.

[0099] The operation of application startup priority control can be in accordance with ARIB TR-B14, Part 3, Section 2, "8.5 Starting and terminating AIT controlled applications." In ARIB Phase 1 operation, the value of the startup priority (start_priority), which is an extension parameter of the "additional_arib_bxml_info()" structure described in ARIB STD-B24, Part 2, Section 9.3.2, is operated according to the standard, and the receiver is configured to operate in accordance with this operation.

[0100] - Regarding the designation of application identifiers in ARIB Phase 0 The isdb:orgID specified in the XML format AIT uses a value assigned to the service provider by the IPTV Forum. The value "0" is reserved as a special value, and can be interpreted as matching all isdb:orgIDs. This "0" cannot be used in the AIT description. The isdb:orgID is assigned by the service provider so that it is a unique value for each application.

[0101] -Application profile and version operation in ARIB Phase 0 To comply with the Phase 0 operation specifications defined in Chapter 8 of Part 2 of Volume 3 of ARIB TR-B14, the mhp:profile specified in the XML format AIT shall be "1", and mhp:versionMajor, mhp:versionMinor, and mhp:versionMicro shall each be fixed to "1".

[0102] Signaling in ARIB Phase 0 The signaling is, for example, by the XML_AIT file on the communication server in Figure 42. The XML_AIT file on the server has a MIME type of application / X-arib-ait-xml; charset="UTF-8" and is obtained from the server via http or https. The AIT file is effective only while the application started by it is valid.

[0103] - Designation of application identifiers in ARIB Phase 1 The organization_id specified in the section-format AIT transmitted in the data carousel is a value assigned to the service provider by the IPTV Forum. The value "0" is reserved as a special value, and can be interpreted as matching all organization_ids. This "0" cannot be used in the AIT description. On the other hand, the application_id is assigned a value so that it is unique for each application by the service provider.

[0104] -Application profile and version operation in ARIB Phase 1 To comply with the ARIB Phase 1 operational specifications defined in Chapter 8 of Part 2 of Volume 3 of ARIB TR-B14, the mhp:profile specified in the XML format AIT shall be "2", and mhp:versionMajor, mhp:versionMinor, and mhp:versionMicro shall each be "1". The mhp:profile specified in the section format AIT shall be "0x0002", and mhp:versionMajor, mhp:versionMinor, and mhp:versionMicro shall each be "0x01".

[0105] -About the operation of application_control_code in ARIB Phase 1 In phase 1 operation, the values ​​of application_control_code in the section format AIT are 0x01 (identifier: AUTOSTART), 0x02 (identifier: PRESENT), and 0x04 (identifier: KILL), and 0x05 (identifier: PREFETCH) is not used. A receiver that receives an unknown application_control_code ignores it, assuming that the application is not listed in the AIT.

[0106] -Operation of Probabilistic Operational Delay Descriptor in ARIB Phase 1 In the operation of Phase 1, the probabilistic operation delay descriptor is not used in the section-format AIT.

[0107] -Operation of cache information descriptors in ARIB Phase 1 In Phase 1 operation, cache information descriptors are not used as described in ARIB TR-B14, Part 3, Section 2, "8.3.4.7 Operation of cache information descriptors." For information on the operation of application caches in Phase 1 operation, see ARIB TR-B14, Part 3, Section 2, "8.3.4.7 Operation of cache information descriptors" and "8.4.1.5 Caching of auto-start applications."

[0108] Signaling in ARIB Phase 1 In phase 1 operation, both the AIT in the section format transmitted by the data carousel and the XML_AIT obtained from communication can be used. The AIT in a specific section format transmitted by the data carousel is constantly monitored by the receiver. If a change in the AIT status is detected as a result of this monitoring, the AIT controlled application can be started and stopped, and other controls can be performed. For operations related to AIT updates, see ARIB TR-B14, Part 2, Volume 3, "8.5.2 Starting and stopping AIT controlled applications based on the AIT constantly monitored."

[0109] The AIT (information that can be used to determine whether the receiving side complies with Hybridcast) including the permission_bitmap and the like described above can be transmitted, for example, from the broadcast station 1000 in Fig. 1 to the receiver 5000 via a broadcast signal (corresponding to SQ2 in Fig. 42). Alternatively, the AIT can be transmitted, for example, from the service provider 3000 in Fig. 1 to the receiver 5000 via the Internet (corresponding to SQ1 in Fig. 42). Furthermore, the AIT can be configured to be transmitted to the receiver 5000 via the broadcast signal and also to be transmitted to the receiver 5000 via the Internet.

[0110] When the reception times of the AIT sent via a broadcast signal and the AIT sent via the Internet are different, it is possible to configure so that the information content of the AIT with the latest reception time is preferentially adopted before executing a function in an HTML document related to that AIT (for example, when checking ST200 in FIG. 25A). Alternatively, if the priority between the AIT sent via a broadcast signal and the AIT sent via the Internet is determined in advance, it is possible to configure so that the AIT with the higher priority is adopted regardless of the reception time. (To determine this priority, the value of the start priority (start_priority), which is an extension parameter of the "additional_arib_bxml_info()" structure described in 9.3.2 of Volume 2 of ARIB STD-B24, can be referenced.) 32, 33 and 34 show examples of display of a program guide used when viewing a broadcast program, or when programming a viewing schedule, cancelling a viewing schedule, programming a recording schedule, or cancelling a recording schedule.

[0111] The display of the program guide can be switched by operating a linked terminal 7000 linked with a terminal linking function, for example. The linked terminal 7000 includes a button 7001 for displaying a terrestrial digital broadcasting program guide, a button 7002 for displaying a program guide for BS and CS broadcasting programs, and a button 7003 for displaying a program guide for IPTV broadcasting (distribution). The linked terminal 7000 also includes a button 7005 for selectively scrolling the screen vertically and horizontally when the program guide is displayed.

[0112] The linked terminal 7000 further includes a recording reservation button 7006 for a program to be reserved for recording, a viewing reservation button 7007 for a program to be reserved for viewing, and a reservation cancellation button 7008 for a program reserved for recording or a program reserved for viewing.

[0113] Fig. 32 shows a state where a program guide for terrestrial digital broadcasting programs is displayed on the display 5002. When a program guide for terrestrial digital broadcasting programs is displayed, an identification mark 7011 indicating the type of program guide is displayed on a part of the display 5002. Fig. 33 shows a state where a program guide for BS and CS broadcasting programs is displayed on the display 5002. When a program guide for BS and CS broadcasting programs is displayed, an identification mark 7012 indicating the type of program guide is displayed on a part of the display 5002. Fig. 34 shows a state where a program guide for IPTV broadcasting is displayed on the display 5002. When a program guide for IPTV broadcasting is displayed, an identification mark 7013 indicating the type of program guide is displayed on a part of the display 5002. The identification marks 7011, 7012, and 7013 may each be in a different color.

[0114] The example program guide shown in the figure indicates the period during which a program is broadcast repeatedly or at intervals in IPTV broadcasting. This program guide is also useful when there is video-on-demand distribution. However, a display format such as a program guide for terrestrial digital broadcasting programs or for BS and CS broadcasting programs may also be used.

[0115] The above-mentioned program guide for terrestrial digital broadcasting programs and program guide for BS and CS broadcasting programs are created, for example, in the integrated control unit 5200 based on electronic program guide information (EPG information) acquired via the second processing unit 5300, and are stored in memory. This EPG information is automatically updated, for example, periodically.

[0116] Furthermore, EPG information for IPTV is acquired via the first processing device 5100. The first processing device 5100 periodically acquires a program guide for each channel, and for example, in the integrated control unit 5200, the program guides for each channel are combined and stored in a memory as a program guide for display.

[0117] The above-mentioned program guides have been described as being displayed independently on the display device 5002. However, the present invention is not limited to such a display method, and multiple types of program guides may be displayed simultaneously on the display device 5002 in an overlapping manner.

[0118] FIG. 35 shows a state in which a program guide 5031 for digital terrestrial broadcast programs, a program guide 3012 for BS and CS broadcast programs, and a program guide 3013 for IPTV broadcast programs are simultaneously displayed on a display device 5002.

[0119] When multiple program listings are displayed simultaneously, the listings may be displayed overlapping each other. Also, the display area for each program may be divided on the screen. In either display format, when a part of each program listing is designated by the cursor, the listing can be scrolled vertically or horizontally on the screen.

[0120] In each of the embodiments showing the above-mentioned examples of program guide display, a viewing reservation and / or a recording reservation is made visually recognizable by coloring or adding a mark to the area for the program name, and also, a program that has already been recorded is made visually recognizable by coloring or adding a mark, etc.

[0121] In the embodiment of Figure 35, too, viewing reservations (or reservation cancellations), recording reservations (or reservation cancellations), etc. can be made by using button 7001 for operating the terrestrial digital broadcasting program guide provided on linked terminal 7000, button 7002 for operating the program guide for BS and CS broadcasting programs, and button 7003 for operating the program guide for IPTV broadcasting (distribution).

[0122] In the program guides shown in Figures 32-35, the horizontal axis represents time or date and the vertical axis represents channel (broadcast station), but the horizontal axis may be displayed as channel (broadcast station) and the vertical axis as time or date.

[0123] FIG. 36 is a diagram showing another example of a communication form between the receiver 5000 and the service provider device 3000 when making a viewing reservation, canceling a viewing reservation, making a recording reservation, or canceling a recording reservation.

[0124] The receiver 5000 displays an IPTV broadcast program guide (EPG) based on a user operation (AS1). The user can select and decide, for example, a program that the user wants to schedule for recording from the program guide by operating a remote controller (AS2, AS3).

[0125] The receiver 5000 uses the URL to access the service provider device 3000 of the program and requests information about the program (AS3). In response, the service provider device 5000 returns information including functions related to recording reservation (which may be referred to as API information) (or information including only information related to recording reservation) to the receiver 5000 in a description document in HTML5 (ES1).

[0126] The receiver 5000 checks the sent function (AS4), and if reservation is not possible, displays a message indicating that reservation is not possible on the display of the receiver 5000 and ends the process (AS6). If it is determined in the sent function that reservation is possible (AS7), a reservation screen is displayed on the display, and the user selects the reservation button and presses the setting button to end the operation.

[0127] In the receiver 5000, the program reservation information of the program is written in the reservation management table. For example, a reservation mark is added to the field of the information (including the channel (address), broadcast start time, broadcast end time, etc.) of the program in the reservation management table.

[0128] When the broadcast time of the reserved program approaches, the receiver 5000 sets the receiving channel of the first processing unit 5100 (AS8). Then, it starts receiving the program and starts automatic recording (AS9, AS10, AS11). At this time, it is assumed that the broadcast of the program by the service provider device 3000 starts (ES2). When the broadcast of the program ends, the service provider device 3000 notifies the receiver of an end function (ES3). When the receiver 5000 receives the end notification, it disconnects the connection with the service provider device 3000 and ends the reserved recording (SA12). After the connection is disconnected, a message saying "Reserved recording will end" may be displayed. By doing so, the user knows that the connection has been disconnected.

[0129] Although the above description is for a recording reservation, a viewing reservation is also made in a similar manner. However, in the case of a viewing reservation, recording is not performed, and the receiver 5000 is controlled to a state in which the reserved program is displayed.

[0130] When a viewing reservation or a recording reservation is cancelled, the reservation information of the reserved program is simply deleted from the reservation management table.

[0131] FIG. 37 is a flowchart for explaining the parental lock function and the lock release function. Depending on the program, parental functions may be attached to the program information (service information). In such a case, some people, for example, those aged 21 or over, have the authority to release the parental lock. This flowchart is a flowchart for realizing an operation processing function for a program with such a pan-rental lock. This function is also realized by an application in the integrated controller 5200.

[0132] Now, suppose that the receiver 5000 receives a program and receives an instruction to play it from an operating device (remote controller or mobile terminal) (step SB1). Then, it is determined whether parental lock level information is attached to the related information of the program (step SB2). If the program does not have parental lock level information, the received program is played and displayed (step SB3).

[0133] However, if the program is accompanied by parental lock level information, a message such as "This program is pan-rentally locked" is displayed on display 5002 (step SB4). If a release key is entered from the operating device (step SB5), it is determined whether or not the release key is correct (step SB6). If the release key is correct, the received program is played and displayed (step SB3). If the release key is incorrect, it is determined whether or not a certain amount of time has passed since the program was received (step SB7), and if the certain amount of time has not passed, the process waits for the release key to be entered, and if the certain amount of time has passed, the process ends (step SB7), and a message such as "Cannot view" is displayed.

[0134] FIG. 38 is a flow chart for explaining a function that allows a user to set a parental lock function for any program. For example, a parent may not want his / her child to watch a certain program. In such a case, the user can operate the operating device to activate the parental lock function (step SB1). Then, the desired program guide is displayed (step SB2). Next, the user uses the cursor to select the program for which the parental lock is to be set (step SB3). Next, when the enter button is pressed (SB4), the input of the unlock key for viewing is requested (step SB5). When the user then inputs the setting of the unlock key (step SB6), the process ends.

[0135] When viewing the program, the viewer must input the unlock key, as described above. The input timing of the unlock key is as described above in the flow chart.

[0136] 39 and 40 show an embodiment in which the terminal link function 5500 is effectively utilized. The terminal link function 5500 can search for a plurality of registered mobile terminals 7000a and 7000b, and can perform data communication (such as emergency communication) between them.

[0137] Furthermore, the terminal link function 5500 also possesses identification information of the home gateway 7100 (HGW) so as to be able to communicate with the home gateway 7100. In other words, the home gateway 7100 (HGW) can be recognized by the terminal link function 5500.

[0138] The HGW 7100 can communicate with a server 7800 via the Internet. The HGW 7100 includes a system controller 7102, a device manager 7103, a network interface (hereinafter referred to as network I / F) 7104, a record manager 7105, and a sensor control table 7106, as shown in FIG.

[0139] The control data management unit 7101 includes an application manager (hereinafter referred to as APP-Mg), an event manager (hereinafter referred to as EVT-Mg), and a configuration manager (hereinafter referred to as CONFIG-Mg).

[0140] The APP-Mg manages a number of applications for controlling various operations of the HGW 7100. The EVT-Mg manages event applications for controlling various operations in response to the occurrence of various events. The EVT-Mg can also control the recording manager 7105. The recording manager 7105 can record data or video in the storage medium 5001 via the terminal linking function 5500.

[0141] The CONF-Mg recognizes the functions within the HGW 7100 and various functions related to the HGW 7100, and manages configuration applications that, for example, perform operation priority and operation restrictions. The CONF-Mg can also set the initial settings of each functional block, function restrictions, function extensions, priority levels, operation times, etc. The system controller 7102 can control the sequences of each block in the HGW 7100.

[0142] The HGW 7100 can communicate with the various sensors 7200 by wired or wireless communication. When a mobile terminal 7000c located outside the range of the home network 7300 is under the management of the HGW 7100, it can communicate with the HGW 7100 and can also communicate with the terminal linkage function 5500 via the HGW 7100. As shown in Fig. 40, the various sensors 7200 include a camera 7201, a microphone 7202, a speaker 7203, and the like that can be controlled by the EVT-Mg. The camera 7201, the microphone 7202, and the speaker 7203 are installed in multiple locations in the home.

[0143] Furthermore, the EVT-Mg can determine detection data from external sensors and / or data from the camera 7201 and microphone 7203 received from the network I / F 7104, and control the next action or behavior.

[0144] The device manager 7103 can authenticate other devices operating in association with the HGW 7100 and register them in a memory. Therefore, the device manager 7103 can manage other sensors (sensor group 7200) connected via the network I / F 7104.

[0145] The device manager 7103 also registers and can recognize identification data of a server (not shown) connected via the Internet.

[0146] Furthermore, the sensor control table 7106 stores the name of each sensor in the sensor group 7200, the position information of each sensor, and data for controlling each sensor. Furthermore, the name and position information of each sensor can be displayed on, for example, smartphones 7000a and 7000b, allowing the user to confirm the type and installation position of the sensor.

[0147] The network I / F 7104 is connected to other sensors, etc. in the home via short-range wireless.

[0148] Some high-performance sensors may include a control data management unit. The control data management unit includes an application manager (APP-Mg), an event manager (EVT-Mg), and a configuration manager (CONFIG-Mg) such as those included in the HGW 7100. The sensing function included in the sensor includes various elements according to the sensing purpose. The various elements may be, for example, a camera and a microphone, as in the HGW 600. Further, the various elements may include a heat sensor, a temperature sensor, a humidity sensor, an illumination sensor, a pressure sensor, a switch, and the like. The sensor may include one or more sensing elements depending on its intended use.

[0149] The above sensors are placed in various locations within the home, for example, as sensors to detect the opening and closing of doors, sensors to detect the production of sounds of a certain volume, sensors to detect human movement, sensors to detect the opening and closing of windows, and sensors to take photographs.

[0150] In the above-described system, when a detection signal is output from one or more of the cameras, microphones, other sensors, etc., the control data management unit 7101 of the HGW 7100 recognizes this as an event occurrence. Then, the control data management unit 7101 controls an arbitrary camera 7201 via the record management unit 7105. As a result, the camera 7201 transmits monitoring data that has been cached from before the event occurrence time (e.g., 10 minutes before) to, for example, the storage medium 5001 via the record management unit 7105, and continues to transmit monitoring data captured for a certain period of time (e.g., 3 minutes, 5 minutes, 10 minutes, 20 minutes, or 30 minutes). In this system, event-related data (which may be referred to as event attribute data) at the time the event is detected is also transmitted to the storage medium 5001 together with this monitoring data.

[0151] The event-related data may include, for example, one or more of the time the event occurred, the type of sensor that detected the event, the sensor's location data, the recording start time, and the recording end time.

[0152] Here, in the figure, the storage medium 5001 is in the home, but it does not necessarily have to be a storage medium in the home. The storage location of the monitoring data may be a storage medium in a server 7800 connected via the Internet. The storage medium 5001 has a data area and a management area. The monitoring data is stored in the data area, and the event-related data is stored in the management area.

[0153] The monitoring data may include not only video data but also sound data and measurement data from sensors. The monitoring data may also include, for example, changes in temperature, humidity, or pressure at a specific location.

[0154] The management area describes management data for playing back the monitoring data. This management data also includes the event-related data. The management data includes the event-related data and recording addresses of the monitoring data corresponding to the event-related data. When multiple events occur, multiple event-related data and multiple monitoring data corresponding to the multiple event-related data exist.

[0155] The event-related data includes the type of event (which may be called a sensor). Furthermore, surveillance data (for example, surveillance video) is recorded based on the event, and the event-related data also includes the recording start time, recording end time, and the like.

[0156] In the above system, the terminal link function 5500 can communicate with the HGW 7100. The HGW 7100 can communicate with the server 7800. For this reason, the mobile terminal 7000c can access the terminal link function 5500 via the server 7800 and the HGW 7100.

[0157] The flowchart in Fig. 41 shows, in a simplified form, the operation of the receiver 5000 when the receiver is fully powered on. As described above, the receiver 5000 includes a first processing unit 5100 and a second processing unit 5200. In this embodiment, the receiver 5000 includes a means for storing which of the video outputs of the first processing unit 5100 or the second processing unit 5200, or both, were operating when the receiver was last powered off (note that a backup power source such as a memory is always on). Then, when the receiver is next powered on, for example, the integrated control unit 5200 starts up the system that was functioning immediately before the power was turned off.

[0158] For example, when the power is turned on, the integrated control unit 5200 checks the environmental data at the time of the previous power off (step SA1). Then, it is determined whether the content being viewed at the time of the previous power off was the broadcast wave signal A processed by the second processing unit 5300 or the distribution signal B according to the hybrid cast specification processed by the first processing unit 5100 (step SA2).

[0159] If the content being viewed immediately before the power was turned off was the broadcast wave signal A processed by the second processing unit 5300, the second processing unit 5300 is started. As a result, the video and audio signals from the second processing unit 5300 are supplied to the display unit 5002 and the speaker system 5003. In addition, for a certain period of time, the display unit 5002 displays that the source of the displayed content is the second processing unit (or broadcast signal) 5300. Alternatively, an indicator indicating that the signal is the broadcast signal from the second processing unit 5300 may be lit on the display unit 5002 (step SA3).

[0160] Conversely, if the content being viewed immediately before the power was turned off was distribution signal B processed by first processing unit 5100, first processing unit 5100 is started. As a result, video and audio signals from first processing unit 5100 are supplied to display unit 5002 and speaker system 5003. Also, for a certain period of time, display unit 5002 displays that the source of the displayed content is first processing unit (or distribution signal) 5100. Alternatively, an indicator indicating that the signal is a broadcast signal from first processing unit 5100 may be lit on display unit 5002 (step SA4).

[0161] 43 shows an embodiment that takes into consideration effective use of the terminal linkage function 5500, the recording medium 5001, and the HGW 7100. In this system, any one or a combination of a plurality of illuminators 7204, a plurality of speakers 7203, and a plurality of microphones 7201 that can emit light of various colors by combining the emission colors of R (red), G (green), and B (blue) are further used as control objects.

[0162] For example, there are cases where a guardian goes out, leaving an infant at home. The guardian may want to monitor the infant's condition from time to time. In such a case, the guardian can monitor the infant's condition at home using the mobile terminal 7000c that the guardian owns. If the guardian wants to talk to the infant, he or she can talk to the infant through the speaker 7203-1, and if the guardian wants to hear the infant's response, he or she can listen to the infant's response through the microphone 7202-1.

[0163] The above-mentioned system is also useful when introduced into a daycare center, where parents who leave their children at the daycare center and go to work can check on the condition of their children from outside.

[0164] Furthermore, if there is a care recipient at home, the caregiver can communicate his / her intentions to the care recipient using the speaker 7203-1 and the illuminator 7204-1. For example, for a care recipient with hearing impairment, the caregiver can communicate his / her intentions by changing the color of the illuminator 7204-1 in various ways. Also, for a care recipient with visual impairment, the caregiver can communicate his / her intentions through the speaker 7203-1.

[0165] The above-mentioned embodiment further includes the following means and methods. That is, the receiving device is configured to be able to make a reservation for viewing a broadcast program in compliance with the hybrid cast method by using a function of an application embedded in an HTML document related to digital broadcasting. The receiving device also includes a means and method for checking whether or not the hybrid cast method is complied with by using information that can be used to check whether or not the hybrid cast method is complied with. The receiving device also includes a means and method for displaying a first screen for inquiring a user whether or not to set the viewing reservation. The receiving device also includes a means and method for displaying a second screen for setting the viewing reservation when a predetermined input operation is performed using the first screen. The receiving device also includes a means and method for displaying a third screen indicating that the viewing reservation cannot be made due to a predetermined condition.

[0166] The device also includes means for displaying a fourth screen for inquiring whether or not to cancel the viewing reservation, and means and a method for displaying a fifth screen for canceling the viewing reservation when a specified input operation is performed using the fourth screen.

[0167] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0168] 1000...broadcast station, 1100...broadcast station server, 1200...security device, 2100...broadcast wave transmission path, 2200...hybridcast transmission path, 3000...service provider device, 3100...server for each service, 3200...application database, 5000...receiver, 5001...storage medium, 5002...display, 5003...speaker system, 7000...linked terminal.

Claims

1. A receiving device configured to be able to schedule viewing or recording of a broadcast program in accordance with a hybrid cast system by using a function of an application embedded in an HTML document related to digital broadcasting, comprising: The function includes: A first function related to the viewing reservation and a second function related to the cancellation of the viewing reservation are included, When the first function is obtained, a function is activated to inquire a user before executing the viewing reservation whether or not to make the viewing reservation; If the first function is obtained, a function is activated to create an EPG in which one or more programs to be scheduled are marked; If the second function is obtained, a function is activated to inquire of the user before executing whether or not to cancel the viewing reservation; When the second function is obtained, a function for creating an EPG that allows a program to be removed from the EPG in which one or more programs to be reserved for viewing are marked is started; The function further includes: a third function related to the recording reservation and a fourth function related to canceling the recording reservation; When the third function is obtained, a function is started to inquire of the user before executing the recording reservation. If the third function is obtained, a function is activated to create an EPG in which one or more programs to be scheduled for recording are marked; When the fourth function is obtained, a function is started to inquire of the user before executing whether or not to cancel the scheduled recording; When the fourth function is obtained, a function for creating the EPG in which one or more programs to be scheduled for recording are marked and which allows a program to be removed from the EPG is started; means for enabling the viewing reservation to be set based on detection of the first function; a means for enabling cancellation of the viewing reservation based on detection of the second function; means for enabling the recording reservation to be set based on detection of the third function; a means for enabling cancellation of the scheduled recording based on detection of the fourth function; A receiving device having the same.

2. A transmission method configured to enable a receiving side to schedule viewing or recording of a broadcast program in accordance with a hybrid cast system by using an application function embedded in an HTML document related to digital broadcasting, comprising: The function includes: A first function related to the viewing reservation and a second function related to the cancellation of the viewing reservation are included, When the first function is obtained, the receiving side starts a function of inquiring a user before executing whether or not to make the viewing reservation; If the first function is obtained, a function is activated to create an EPG in which one or more programs to be scheduled are marked; If the second function is obtained, a function is activated to inquire of the user before executing whether or not to cancel the viewing reservation; When the second function is obtained, a function for creating the EPG capable of removing a program from the EPG in which one or more programs to be reserved are marked is activated; The function further includes: A third function related to the recording reservation and a fourth function related to the cancellation of the recording reservation are included. It is included, When the third function is obtained, the receiving side starts a function of inquiring of the user before executing the recording reservation, if the third function is obtained, a function is activated for creating the EPG in which one or more programs to be scheduled for recording are marked; When the fourth function is obtained, a function is started to inquire of the user before executing whether or not to cancel the scheduled recording; When the fourth function is obtained, a function for creating the EPG in which one or more programs to be scheduled for recording are marked and which allows a program to be removed from the EPG is started; For a device receiving the broadcast program, enabling the viewing reservation to be set based on detection of the first function; enabling cancellation of the viewing reservation based on detection of the second function; enabling the recording reservation to be set based on detection of the third function; enabling cancellation of the scheduled recording based on detection of the fourth function; A transmission method comprising:

Images