RU2598591C2 - Receiving device, receiving method and program - Google Patents

Abstract

FIELD: information technology.

SUBSTANCE: invention relates to a receiving device, a receiving method and a program capable of preventing any process not intended by a user from being performed where a data broadcast service is implemented through transitions of documents. Receiving device acquires a description document described in a predetermined computer language for displaying a type of content different from AV content; determines whether acquired description document is managed by a broadcasting organisation broadcasting AV content or by a business operator other than broadcasting organisation; and controls execution of acquired description document in accordance with result of determination.

EFFECT: technical result is prevention of any process not specified by a user during broadcasting.

9 cl, 24 dwg

Description

FIELD OF THE INVENTION

This technology relates to a receiving device, a receiving method and a program. More specifically, this technology relates to a receiving device, a receiving method and a program for use in executing a type of content that is different from A-B (audio-video) content constituting the so-called TV programs, typically in digital TV broadcasting.

State of the art

Japan has digitized TV broadcasting, and digital terrestrial broadcasting, satellite (BS) digital broadcasting and the like are widespread in the country. In addition, in digital TV broadcasting, such as terrestrial digital broadcasting, not only AV broadcasting of content constituting the so-called TV programs is embodied, but also data transmission using the broadcast markup language (VJAR) (BML) (see, for example Patent literature 1).

For example, a TV receiver capable of receiving data transmission can display information about the current broadcast program, as well as information not related to the ongoing program (announcements of other programs, news, weather reports, traffic information, etc.) , and execute the application program associated with the transmitted program (AB content).

In addition, the aforementioned TV receiver is configured to operate differently in two cases: when implementing services managed by a broadcasting organization offering digital TV broadcasting (for example, a weather message display service), and when implementing services that are not run by broadcasting organizations (for example, an Internet connection service for displaying web pages, etc.).

That is, when, for example, weather messages should be displayed in the transmitted data as one of the services managed by the broadcasting organization, processes can be carried out to read the pre-registered information about the location where the user lives from the TV receiver so that weather messages are displayed for the area where the user lives.

On the other hand, when, for example, web pages are to be displayed via an Internet connection as one of the services that are not run by broadcasting organizations, the aforementioned reading process or the like is not performed, so that no process specified by the user (e.g. a process in which terrain information can be fraudulently read and sent to an malicious third party) will not be carried out.

Similarly, in Europe, a broadcast type corresponding to data transmission in Japan is implemented in accordance with the multimedia home digital video broadcasting platform (DVB-MHP), which determines how the content of the data broadcast should be described and delivered.

List of links

Patent Literature

PTL 1: Japanese Patent Application Laid-Open No. 2003-131981A.

SUMMARY OF THE INVENTION

Technical problem

Meanwhile, in digital television broadcasting in the United States, according to ATSC (Advanced Television Standard Committee) 2.0, a service corresponding to the transmission of data in digital TV broadcasting in Japan is planned to be implemented by receiving HTML documents described in HTML (hypertext markup language), of the services run by broadcasting organizations.

Assume that, as shown in FIG. 1, a service is implemented using an application program composed of resources representing pictures, sounds, video frames, etc. (respectively, "MPEG", "MP3" and "JPEG" in Figure 1), as well as scripts (executable programs) for executing predetermined processes by indicating links to these resources. In this case, operating modes can be set in the application program or the like, and in accordance with the operating modes set in this way, specific processes, such as a reading process, can be allowed (or disabled).

Specifically, in the case of an application received from a server controlled by the broadcasting organization, an operating mode may be set to allow (not prohibit) the execution of a particular process. And in the case of an application program received from a server on the Internet that is not run by broadcasting organizations, an operating mode can be set to block (prohibit) the execution of a specific process.

Applications such as those shown in FIG. 1 can be constructed, say, from a variety of class files (scripts) prepared in Java (registered trademark) and organized into a file structure called “jar” (Java ARchive), as well as from resources (pictures, sounds, video frames, etc.).

If the application programs are designed each of the resources and scenarios, as shown in FIG. 1, the boundaries between these application programs are distinguishable. This makes it possible to set the operating mode in each application program to enable (or disable) a specific process (reading process, etc.).

In contrast, when HTML documents are used as planned for digital TV broadcasting in the United States, operating modes cannot be set in application programs as shown in FIG. 1.

For example, when a service is implemented using HTML documents, a single application program, such as in FIG. 1, is not executed. Instead, HTML documents for execution execute a transaction from one document to another, and each HTML document is executed independently.

Therefore, no operating mode can be set in every HTML document executed independently as an application program for implementing the service.

For this reason, when HTML documents are used as planned in the United States, it is not possible to allow (or prohibit) specific processes in accordance with the operating modes; processes not specified by the user can still be carried out.

This technology was developed taking into account the above circumstances and offers mechanisms to prevent processes not specified by the user from being executed when the data broadcasting service is implemented through the interaction of documents.

Solution

According to a first object of this technology, there is provided a receiving device for receiving broadcasting of AB content by means of broadcast waves, including:

a receiving unit configured to obtain a descriptive document described in a predetermined computer language for displaying a type of content other than AB content; a determining unit, configured to determine whether a broadcasting organization transmitting AB content or a business operator other than the broadcasting organization manages the received descriptive document; and a control unit, configured to control the execution of the received descriptive document in accordance with the result of the determination made by the determining unit.

The receiving device further includes a start detection unit configured to detect start-up information that is transmitted along with the AB content and which relates to the management of the narrative document to be executed in connection with the passage of the AB content; based on the detected start-up information, the receiving unit receives a descriptive document from the information processing device controlled by the broadcasting organization, and the determining unit determines that the descriptive document received from the information processing device is controlled by the broadcasting organization.

When executing a descriptive document that can be executed independently without communication with AB content, the receiving unit receives a descriptive document from the information processing device controlled by the broadcasting organization, and the determining unit determines that the descriptive document received from the information processing device is controlled by the broadcasting organization.

When executing a descriptive document that can only be executed by a specific application program, the receiving unit receives a descriptive document from another information processing device that is controlled by another business operator, and the determining unit determines that the descriptive document received from another information processing device is controlled by another business operator.

The receiving device further includes an executive unit configured to execute the received descriptive document; at the same time, if it is determined that the broadcasting organization controls this descriptive document, the control unit controls the executive unit to work in the first control mode, in which the first predetermined specific process can be performed; and at the same time, if it is determined that another business operator is managing the descriptive document, the control unit controls the executive unit to work in the second control mode, in which a specific process cannot be performed.

When the executive unit operates in the first control mode, each time a descriptive document is received, the determining unit determines whether the broadcasting organization or other business operator controls the received descriptive document, and if it is determined that another business operator controls the descriptive document, the control unit forces the executive unit during operation, exit the first control mode and enter the second control mode.

If a predetermined operation is performed when the executive unit is operating in the second operating mode, the control unit forces the executive unit to exit the second operating mode and enter the first operating mode during operation.

The receiving unit receives a descriptive document transmitted using the first predetermined frequency range of the digital television broadcast signal of the broadcast waves.

The receiver can be either an independent device or an indoor unit as part of a single device.

According to other embodiments of this technology, a reception method and a program functionally corresponding to the receiving device outlined above according to one object of this technology are provided.

By using the receiving device, the receiving method and the program according to some objects of this technology, a descriptive document is obtained, which is described in a predetermined computer language, for displaying a type of content that is different from AB content transmitted on radio waves. Then it is determined whether the broadcasting organization transmitting the AB content or the business operator other than the broadcasting organization manages the received descriptive document. The execution of the resulting descriptive document is controlled in accordance with the result of this determination.

Advantageous Effect of the Invention

According to this technology, it is thus possible to prevent processes not specified by the user from being executed when the data broadcasting service is implemented through document interaction.

Brief Description of the Drawings

1 is a view showing a typical application composed of resources and scripts.

2 is a diagram showing a typical broadcast system as one embodiment.

Figure 3 is a view showing a typical screen displayed on a monitor by a receiving device.

Figure 4 is an explanatory view outlining this technology.

5 is a conditional view showing typical screen interactions displayed on a monitor.

6 is a view detailing various downloadable objects.

7 is a view detailing various events.

8 is a view listing the relationships between screen interactions and events.

Fig.9 is a diagram showing a typical structure of a receiving device.

10 is a view illustrating the idea of trigger information embedded in PCR packets in a TS during transmission.

11 is a view showing when trigger information is stored in a PCR packet.

12 is a view listing typical items of information included in the startup information.

13 is a view showing a typical syntax structure of the trigger information.

14 is a flowchart for explaining a process for starting NDO content.

15 is a view showing actually typical screen interactions when an HTML data broadcasting (TDO) document is executed in connection with the passage of a TV program.

FIG. 16 is a view showing actually typical screen interactions when an HTML data broadcasting (TDO) document not causing a screen display is executed in connection with the passage of a TV program.

Fig is a view showing a typical life cycle of an HTML document broadcast data (TDO).

FIG. 18 is a view showing one example of a transfer from an active operational state of a TDO to an active operational web state.

FIG. 19 is a flowchart for explaining a process for starting NDO content.

20 is a flowchart for explaining a PDO content start-up process.

21 is a flowchart for explaining a process of setting a control mode.

Fig is another view showing another typical life cycle of an HTML document broadcast data (TDO).

23 is another table view listing other typical pieces of information included in the startup information.

24 is a diagram showing a typical computer structure.

DETAILED DESCRIPTION OF THE INVENTION

1. Options for implementation

Typical broadcast system configuration

2 shows a broadcast system 1 as one embodiment. This broadcasting system 1 is composed of a broadcasting unit 11, servers 12, 21 and 22 and a receiving device 30. The broadcasting unit 11 and server 12 are installed on the side of the broadcasting organization, and the servers 21 and 22 are installed on the side of business operators other than the broadcasting organization. The receiving device 30 is installed on the side of the audience.

The servers 12, 21 and 22 and the receiving device 30 are interconnected via the Internet 30.

The broadcast unit 11 transmits (broadcasts) a digital TV broadcast signal.

It is also assumed that at predetermined times, the broadcasting unit 11 transmits the start information in packets containing a software clock reference signal (PCR); the packets are hereinafter referred to as OCHR packets) as part of the TP packets constituting the transport stream (hereinafter referred to as TP ( TS)) digital TV broadcast signal.

In this context, the start-up information is composed of information indicating time points for the execution of HTML data broadcasting documents as HTML documents to be executed for implementing the data broadcasting service, information indicating the destinations from which these HTML data broadcasting documents should be obtained, and like that. Starting information will be discussed in detail later with reference to FIGS. 10-13.

The server 12 is managed on the side of the broadcasting organization and stores HTML data broadcasting documents approved by the broadcasting organization. Server 12 provides HTML documents for broadcasting data and others that it stores under the influence of a request from a receiver 30 that accesses server 12 via the Internet 20.

The server 21 is not managed on the side of the broadcasting organization managing the server 12, and saves HTML data broadcast documents not approved by the broadcasting organization. Server 21 provides HTML documents for broadcasting data and others that it stores under the influence of requests from a receiver 30 that accesses server 21 via the Internet 20.

Server 22 provides websites 2 provides websites to terminal equipment connected to the Internet 20 and is not managed by the broadcasting organization managing server 12. Server 22 provides HTML documents from web pages and others under the influence of requests from the receiving device 30, accessing the server 22 via the Internet 20. In this case, an HTML document of a web page means an HTML document that represents a web page.

That is, the servers 21 and 22 are managed by business operators other than the broadcasting organization managing the server 12.

The receiving device 30 receives a digital TV broadcast signal transmitted from the broadcasting unit 11, and receives from it pictures and sounds AB of the content constituting the TV program. This receiving device 30 outputs the received pictures to the monitor (for example, to the monitor 30 in FIG. 3, which will be discussed later), and the received sounds to the speakers (not shown).

In addition, the receiving device 30 accesses the server 12 or the server 21 via the Internet 20 to receive and execute HTML data broadcasting documents. This allows the receiving device 30 to display a picture 43 made up of a content picture 41 AB, onto which a picture 42 of the data broadcast content is superimposed, not shown on the monitor 31. In this case, the receiving device 30 may be powered from a remote location by using the remote controller 32.

Returning to FIG. 2, the receiving device 30 also accesses the server 22 via the Internet 20 to receive and execute HTML documents of web pages.

This receiving device 30 can either be installed as a standalone unit, or integrated, for example, in a TV receiver or VCR. A detailed construction of the receiver 30 will be discussed later with reference to FIG. 9.

Broadcasting system 1 is designed as described in the above paragraphs.

Descriptive Document Management Method

Below, with reference to Figs. 4-8, a method for managing descriptive documents according to this technology is explained.

The essence of this technology is that the receiving device 30 is prompted to allow or prohibit specific processes that are performed by executing HTML documents, depending on whether the broadcast organization or some other business operator controls the specified HTML document received via the Internet 20 and executed .

For example, if the receiver 30 executes a broadcast organization-driven HTML document, such as an HTML document broadcasting data from a server 12 mounted on the side of the broadcast organization, a particular process is allowed to execute (not be prohibited) in accordance with the HTML document discussed.

On the other hand, if the receiving device 30 executes a non-broadcast organization-controlled HTML document, such as a data broadcast HTML document received from a server 21 installed on the side of some other business operator, or a web page HTML document received from a server 22, to a particular the process is not allowed to execute (is prohibited) in accordance with the HTML document being discussed.

The receiver 30 controls the HTML documents as described above. It should be noted that HTML documents are simply an example of descriptive documents described in a predetermined computer language for displaying content types that are different from AB content that makes up a TV program. Thus, other descriptive documents can be used instead of HTML documents.

Figure 4 gives an overview of this technology.

In Fig. 4, when HTML documents are executed on the left side of the border drawn by a bold line, specific processes are allowed, while HTML documents are executed on the right side of the border drawn by a bold line, specific processes are prohibited. In addition, FIG. 4 shows three areas that vary depending on how the HTML document is received: broadcast area, Internet area, and file system area. These areas are explained in detail below.

For example, when receiving start-up information (for example, corresponding to “Launching" Start "from the air" in Fig. 4) included in a digital TV broadcast signal transmitted from the broadcasting unit 11, the receiving device 30 receives HTML documents for broadcasting data (For example, corresponding to the “Linear TV PDZO” in the “Internet” of FIG. 4) from the server 12 and executes the received document. In addition, the receiving device 30 executes an HTML data broadcast document received in advance from the server 12 and recorded (for example, corresponding to the “Linear TV PDZO” in the “File system” of FIG. 4).

As another example, suppose that a TV program is viewed on the receiver 30 using the downloaded broadcast. In this case, upon receipt of the start-up information included in the recorded TV program (for example, corresponding to the "Start" Start from video files that is played by the local player "in Fig. 4), the receiving device 30 receives an HTML data broadcast document (for example, the corresponding "The content of the PDLP NRB" in Figure 4) from the server 12 and executes the received document. In addition, the receiving device 30 executes an HTML data broadcasting document (for example, the corresponding “PDLO NRB” in FIG. 4), obtained in advance by the downloaded broadcast from the broadcasting unit 11 and recorded.

As another example, the receiving device 30 receives from the server 21 an HTML document for broadcasting data (for example, corresponding to the “Content of the NMCH” in FIG. 4), which can only be displayed by a specific browser, and executes the received document.

And when the above-described HTML data broadcasting documents are executed, the receiving device 30 has a picture 43 of FIG. 3 displayed on the monitor 31.

In this case, the downloaded broadcast is a broadcast type, which includes receiving in advance the TV program (digital TV broadcast signal) from the broadcasting unit 11, recording the received TV program, and playing back the recorded TV program under the influence of the user operation. In the following description, the downloaded broadcast will be referred to as non-real-time broadcasting (NRV) (NRZ), and the downloaded content will be referred to as the content of the NRB.

In this case, it is assumed, for example, that the driver (person) displayed as the image 42 in FIG. 3 has a connection with the driver’s web page, which can be selected by the user.

If the user performs the operation to select the driver in Figure 42 in Figure 3, the receiving device 30 receives the HTML document of the web page (for example, "General Web Content" in Figure 4) from the server 22 and executes the resulting document to display the web driver page or the like on the monitor 31.

As explained above, when the receiving device 30 executes the data broadcasting HTML document, measures must be taken to allow specific processes to enhance the data broadcasting service.

Specifically, if the receiving device 30 is to display weather messages in the user's area of residence as a data broadcast service, for the data broadcasting HTML document, it is necessary to start the execution of specific processes, such as the process of reading the area information of the user's area of residence from the receiving device 30, in which Information is pre-registered.

On the other hand, if the receiving device 30 is to display a data broadcast or web page not approved by the broadcasting organization, it is undesirable to allow the respective specific triggering processes of the data broadcast HTML document or web page document.

For example, if data broadcasting not approved by the broadcasting organization is to be displayed, the corresponding data broadcasting HTML document is obtained from the server 21 not controlled by the broadcasting organization and executed. If a web page is to be displayed, the corresponding data broadcast HTML document is obtained from the server 21, which is not managed by the broadcasting organization, and executed. In these cases, unlike the server 12 managed by the broadcasting organization, the server 21 or 22, not managed by this broadcasting organization, may contain a data broadcasting HTML document or a webpage HTML document prepared by a malicious third party. One such HTML document could potentially be one that illegally reads pre-registered area information from the receiving device 30 and feeds the extracted information to a specific server.

In view of the foregoing, the receiving device 30 sets the control mode so that specific processes can be performed on the left side of the border In figure 4 and cannot be performed on the right side of it. Depending on the control mode set in this way, the receiving device 30 allows (or prohibits) the execution of a specific process by a given HTML document.

In this case, specific processes belong to the type of processes that can cause losses for the user when they are illegally executed by a malicious third party. One such specific process may be the process of illegally obtaining personal information or the like about the user, so that the security of the user may be jeopardized.

Specific processes are predetermined, for example, by the user or manufacturer of the receiving device 30. Potentially, these specific processes include a process for selecting a channel in which a channel is selected, a process for manipulating a tape recorder in which the receiving device 30 functioning as a video recorder is forced to record or the like, a receiving process in which program information about a currently selected TV program is obtained and an electronic bookmark management process in which a specific Uniform Resource Locator (URL) is marked.

FIG. 5 shows typical screen transitions displayed on the monitor 31 of the receiver 30 when the HTML documents shown in FIG. 4 are executed. An example of a possible use case is explained below with reference to FIG. 5.

In FIG. 5, each of the reference numbers UI1-UI12 (except for UI8 and UI9) indicates a user interface (hereinafter referred to as UI) displayed on the monitor 31 of the receiving device 30. In addition, in FIG. 5, the dashed line L1 denotes the boundary between the priority processing and background processing. Inside the area surrounded by this dashed line L1, the processes executed in UI8 and UI9 take place internally and are not displayed on the monitor 31.

In addition, each of the reference positions AE indicates an event for making a transition to a given UI. Each of the reference positions "a" - "e" means an event to complete the transition from one UI to the next. Further, the dashed line L2 in FIG. 5 corresponds to the boundary B shown in FIG. 4. The control modes are set so that a specific process can be performed outside this boundary, but could not be performed inside it. That is, outside the boundary of the dashed line L2, the control mode is set to “Controlled Broadcasting”, in which specific processes can be performed using HTML data broadcasting documents; within this boundary, the control mode is set to “Uncontrolled Broadcasting,” in which specific processes cannot be performed using HTML data broadcast documents or HTML web page documents.

“TDO”, “NDO” and “PDO” in FIG. 5 have their powers, gradually limited in order, as shown in FIG. 6. Specifically, each downloadable entity (DO) (DO) has the following features.

A startup downloadable entity (TDO) (TDO) is a DLT that has the highest priority among the three DLTs, and is an object that only the broadcasting organization can manipulate. It is expected that the content of the PDLA is subject to execution in connection with the AB content that makes up the TV program and the like. Since the PDE has a DLO that is being manipulated by the broadcasting organization, the control mode for the PDE is always set to “Managed Broadcasting”.

A downloadable NRV (DZO) facility (NDO) is a SAC that has the highest priority following the PZO. For example, DZON is an object that business operators other than a broadcasting organization, such as content-producing companies or NRV service providers, can manipulate. It is expected that the content of the NRV is subject to execution not only in connection with the AB content that makes up the TV program and the like, but also on an individual basis. For example, when an independent broadcasting channel provides data, the content of DZON is executed without communication with the AB content.

Two types of DZON are possible: those that are approved by the broadcasting organization, and those that are not approved by it. For DZON approved by the broadcasting organization, the control mode is set to “Managed Broadcasting”; for DZONs not approved by the broadcasting organization, the control mode is set to “Uncontrolled broadcasting”. With respect to the example of FIG. 5, only DZOs approved by the broadcasting organization are explained. In this case, the control mode for DZON is always set to “Managed broadcasting”.

An unmarked downloadable object (NMO) (PDO) is a DLO that has the lowest priority of the three DLOs and is an object that can only be displayed (executed) by a specific application (browser 73-2 in FIG. 9, which will be discussed later) . For example, a NMDZO can only be displayed by the browser provided for in “Profile A of the Browser” in NRV 1.0. In addition, NMDMs are objects that business operators other than a broadcasting organization, such as content-producing companies (for example, so-called third parties), can manipulate.

As for DZON, there are two types of NMDZO: approved by the broadcasting organization and not approved by it. With respect to the example of FIG. 5, only those NMDCs that are not approved by the broadcasting organization are explained. In this case, the control mode for the NMDZO is always set to “Uncontrolled broadcasting”.

Fig. 7 lists explanations of events AE shown in Fig. 5, and Fig. 8 lists the relationships between UI1-UI12 in Fig. 5 on the one hand and events "a" - "n" on the other hand. In the following descriptions, reference may be made to these drawings, if necessary.

As shown in FIG. 5, when a user selects a TV program of a particular channel as event A, the monitor 31 displays the UI1 constituting this TV program or the like of the selected channel (description of event A in FIG. 7). In addition, when receiving trigger information from the broadcasting node 11, when displaying UI1, the receiving device 30 receives an HTML data broadcasting document (PDZO) from the server 12 and has it superimposed on the picture of the TV program (description of event “a” in UI1 in Fig. 8 ) This causes the monitor 31 to display UI2, such as the picture 43 shown in FIG. 3.

Since UI2 is located outside the boundary of the dashed line L2, the control mode is set to “Managed Broadcast”, in which a specific process can be performed using the HTML broadcast document (PREV). That is, since the HTML broadcast document (PREV) is obtained from the server 12 managed by the broadcasting organization, a specific process is allowed to execute.

In addition, when receiving trigger information when UI2 is displayed, the receiving device 30 receives a new HTML data broadcasting document (PLC) and displays the received document (description of event “b” in UI2 of FIG. 8). This leads to the updating of the picture (for example, picture 42 in Figure 3) of the HTML data broadcasting document (PDZO) superimposed on the picture of the TV program. In addition, when receiving an HTML data broadcasting document (NMDMO) from the server 21 when UI2 is displayed, the particular browser causes the UI11 to be displayed on the monitor 31 (description of event “e” on the UI2 of FIG. 8). In addition, if the user selects the content of the NLMD as event C, the monitor 31 displays UI11.

Further, when the user selects different contents of the NMDL, when displaying UI11, the HTML data broadcasting document (NMDM) is received from the server 21, and the display of the UI11 is updated (description of the event “h” on the UI11 of FIG. 8). In addition, when a user selects a webpage when displaying UI11, the corresponding HTML document of the webpage is selected from the server 22, and UI12 is displayed on the monitor 31 (description of the “i” event on UI11 of FIG. 8).

Since UI11 and UI12 are inside the boundary of the dashed line L2, their control mode is set to “Uncontrolled broadcasting”, in which specific processes cannot be performed using an HTML data broadcasting document (NMDMO) or HTML web page documents. That is, an HTML data broadcasting document (NMDMO) and HTML documents of web pages are obtained from a server 21 or 22, which is not managed by the broadcasting organization, and thus are subject to prohibitions on specific processes.

In addition, when the user selects to start reproduction of the NRB content, when displaying UI2, the monitor 31 displays the UI2 of the reproduced NRV content (description of event “c” in UI2 of FIG. 8). Meanwhile, if the user selects to stop playing the NRB content being played back when UI7 is displayed, the currently playing NRB content is stopped, and the display on the monitor 31 returns to UI2 actually before the content is played back (event description “c” in UI7 of FIG. 8).

As will be explained in detail later, when the user selects to reserve loading of the NRV content, when displaying UI2, the process of backup loading the NRV content is performed (description of event “d” in UI8 of FIG. 8). At this point, if the subscription procedure for NRW services is to be carried out to view the discussed contents of the NRV, the process of manipulating the subscription process is performed (description of event “d” in UI9 of FIG. 8). These processes are conducted in the background.

When the user presses the Electronic Program Guide (EPG) (EPG) button on the remote controller 32 as event B, the monitor 31 displays the EPI UI3. If the user selects the item from the EPT whose detailed program information is to be displayed, the monitor 31 displays the UI5 of the detailed program information (description of the event “f” in the UI3 of FIG. 8).

In addition, when the user selects an independent data broadcast channel, for example, as event D, the broadcast HTML document (DZON) is received from the server 12, and the monitor 31 displays the UI3 of the DZON content.

Since UI5 is located outside the boundary of the dashed line L2, its control mode is set to “Managed Broadcast”, in which a specific process can be performed using the HTML broadcast document (DZON). That is, since the HTML broadcast document (DZON) is obtained from the server 12 managed by the broadcasting organization, a specific process is allowed to execute.

As another example, if the user selects the desired NRT content from the list of NRT contents when UI5 is displayed, the selected NRV content is reserved for download (description of event “n” in UI5 of FIG. 8). At the same time that the load reservation process is performed (description of event “n” in UI9 of FIG. 8), if necessary, a process of manipulating the procedure for subscribing to the NRV service is performed (description of event “n” in UI9 of FIG. 8) . These processes are conducted in the background. Alternatively, downloading the selected NRW content may begin immediately without redundant loading.

When the loading of the NRB contents is completed or already completed, the user can choose to start playing the contents of the NRB. In this case, the monitor 31 displays the UI7 of the reproduced NRB content (description of the event “t” in UI5 according to Fish. 8). On the other hand, if the user selects to stop the reproduced NRB content, the currently reproduced NRB content is stopped, and the display on the monitor 31 returns to UI5 actually before the content is reproduced (description of the event “t” in UI7 of FIG. 8).

When the user selects the content of the NMCH, when displaying the UI5, the HTML data broadcasting document (NMHS) is received from the server 21, and the monitor 31 displays the UI11 (description of the event “g” in the UI5 of FIG. 8).

Further, when the user presses the NRB button on the remote controller 32 as event E, the monitor 31 displays UI6 constituting a portal to the NRT contents. When the user selects the contents of the DZON from the portal, UI5 is displayed (description of the event “j” in UI6 of FIG. 8).

If the user chooses to reserve the loading of the NRB contents when displaying the UI6, a backup process of loading the contents of the NRB is performed (description of the event “k” in UI6 and UI8 of FIG. At this point, if necessary, the process of manipulating the subscription procedure for the NRV service is carried out (description of the event “k” in UI6 and UI9 of Fig. 8). In addition, when the user selects to start playing back the NRB contents when displaying UI6, the monitor 31 displays the UI7 of the reproduced NRB contents (description of event “I” in UI6 of FIG. 8). On the other hand, if the user selects to stop the NRB content, the currently played NRB content is stopped, and the display on the monitor 31 returns to UI6 actually before playing the content (description of event “I” in UI7 of FIG. 8).

UI transitions take place, as explained above, depending on each use case. In the example of FIG. 5, the control mode is set to “Managed Broadcasting” for HTML data broadcasting documents (PDZO) and HTML data broadcasting documents (DZON) and is set to “Uncontrolled Broadcasting” for HTML data broadcasting document (NMDZ) and HTML web pages .

As discussed above, the region of FIG. 5, indicated by the dashed line L2 constituting the boundary, is just an example, with a control mode set differently on each side of this boundary. For example, while FIG. 5 shows a typical HTML data broadcast document (DZON) approved by a broadcasting organization, in the case of an HTML data broadcasting document (DZON) not approved by a broadcasting organization, the control mode is set to “Uncontrolled Broadcasting”. In the latter case, UI5, for example, is inside the boundary of the dashed line L2. In addition, while FIG. 5 shows a typical HTML data broadcasting document (NMDMO) not approved by the broadcasting organization, in the case of the HTML data broadcasting document (NMDMO) approved by the broadcasting organization, the control mode is set to “Managed Broadcasting”. In this case, UI11, for example, is located outside the boundary of the dashed line L2.

In short, the “Managed Broadcast” management mode is always set for HTML Data Broadcasting Documents (PDZO); for other HTML data broadcasting documents (DZON) and for HTML data broadcasting documents (NMDMO), the control mode changes depending on the statement issued or not issued by the broadcasting organization, so setting the control mode to “Managed Broadcasting” or “Uncontrolled Broadcasting” is arbitrary. For HTML web pages, the control mode is always set to Uncontrolled Broadcast.

In this case, “Native adj.” In FIG. 5 refers to an application program intended for a receiver (i.e., an application program executed by a control unit 68, discussed later), and “Browser” refers to a browser for browsing websites and others (i.e., the browser 73-1 of FIG. 9, discussed later).

Typical receiver structure

Fig. 9 shows a typical structure of a receiving device 30. This receiving device 30 is composed of a tuner 61, a demultiplexing unit 62, an audio decoder 63, an audio output unit 64, a video decoder 65, a start detection unit 66, a video output unit 67, a control unit 68, a memory 69, an operating room unit 70, a recording unit 71, a communication interface 72, a browser 73-1, a browser 73-2, and an infrared receiving unit 74.

The tuner 61 receives a digital TV broadcast signal corresponding to the channel selected by the user, demodulates the received signal and outputs the resulting TP to the demultiplexing unit 62. The demultiplexing unit 62 demultiplexes the TP input from the tuner 61 into the encoded audio signal, the encoded video signal and the control signal and outputs these signals to an audio decoder 63, video decoder 65 and control unit 68, respectively.

Next, the demultiplexing unit 62 extracts the OCHR packets containing the start information from the TS and outputs the selected packets to the control unit 68.

The audio decoder 63 decodes the input encoded audio signal and outputs the audio signal resulting from the decoding to the audio output unit 64. The audio output unit 64 outputs the input audio signal to subsequent stages (for example, speakers).

Video decoder 65 decodes the input encoded video signal and outputs the video signal obtained by decoding to the start detection unit 66 and the video output unit 67.

The start detection unit 66 continuously monitors the inputted video signal to detect the start information embedded in the video signal, and provides the detected start information to the control unit 68. Alternatively, the start information may be transmitted embedded in the content video signal AB corresponding to the digital TV broadcast signal.

Thus, when the trigger information embedded in the video signal is transmitted from the broadcasting unit 11 to the receiver 30, the trigger detection unit 66 detects trigger information embedded in the input video signal.

In the following description, it is assumed that the trigger information is contained in the SINR packets during transmission. Explanations of cases where the trigger information is transmitted embedded in the video signal will be omitted if it turns out to be redundant.

The video output unit 67 outputs to the monitor 31 (FIG. 3) a video signal input from the video decoder 65. In addition, the video output unit 67 combines the video data broadcast signal (for example, corresponding to picture 42 in FIG. 3) input from the browser 73-1 or 73 -2, with a video signal (for example, corresponding to picture 41 in FIG. 3) inputted from video decoder 65, and causes the monitor 31 to display the resulting composite signal.

Next, the video output unit 67 outputs to the monitor 31 a video signal representing a web page or the like inputted from the browser 73-1.

The control unit 68 controls the units constituting the receiver 30 by executing corresponding control programs stored in the memory 69 in advance. In addition, based on the start-up information input from the demultiplexing unit 62 or the start detection unit 66, the control unit 68 controls the receipt of the document HTML data broadcasting (PDZO) for implementing a data broadcasting service associated with a TV program, executing (launching) a document, activating events and stopping execution.

The memory 69 stores in advance control programs to be executed by the control unit 68. These control programs can be updated based on updated data received through a digital TV broadcast signal or over the Internet 20.

In addition, the memory 69 has control mode information recorded therein as a control mode indicator. The control mode may change when this information of the control modes is overwritten. The control mode will be discussed in detail later.

The operation unit 70 receives various operations performed by the user and notifies the control unit 68 of the operation signals corresponding to these operations. The infrared receiving unit 74 receives the operational signals transmitted from the remote controller 32 (FIG. 3) wirelessly using infrared rays and notifies the control unit 68 of the received operational signals. The control unit 68 controls the components constituting the receiving device 30 based on operational signals supplied from the operation unit 70 or from the remote controller 32.

When data broadcasting HTML documents are delivered using a digital TV broadcast signal, the recording unit 71 has delivered data broadcasting HTML documents input from the demultiplexing unit 62 and stored on the internal recording medium.

The communication interface 72 under the control of the browser 73-1 or 73-2 is connected to the server 12 or 21 via the Internet 20. Then the communication interface 72 under the control of the browser 73-1 or 73-2 receives an HTML document for broadcasting data from the server 12 or 21 via the Internet 20 and submits the received document to the browser 73-1 or 73-2.

In addition, the communication interface 72 under the control of the browser 73-1 can connect to the server 22 via the Internet 20. Then the communication interface 72 under the control of the browser 73-1 can receive the HTML document of the web pages from the server 22 via the Internet 20 and submit the received document to the browser 73-1.

The browser 73-1, under the control of the control unit 68, executes an HTML data broadcasting document (PDZO) or an HTML data broadcasting document (DZON) from the communication interface 72 to generate a video broadcasting data signal, and supplies the generated video signal to the video output unit 67.

In addition, the browser 73-1, under the control of the control unit 68, executes an HTML web page document from the communication interface 72 to generate a video signal indicating a web page or the like, and supplies the generated video signal to the video output unit 67.

Browser 73-2 is a browser provided, say, in “Profile A of the browser” in NRT 1.0. A browser 73-2, under the control of the control unit 68, executes an HTML data broadcasting document (NMDMO) from the communication interface 72 to generate a video broadcasting data signal, and supplies the generated video signal to the video output block 67.

In addition, when the tuner 61 receives the NRV digital TV broadcast signal, the demultiplexing unit 62 demultiplexes the TP following demodulation and writes the TP to the recording unit 71. If the user assigns the playback of the NRB content, the recording unit 71 under the control of the control unit 68 provides an encoded audio signal and the encoded video signal to an audio decoder 63 and a video decoder 65, respectively. In this way, the content of the NRV is reproduced.

In this case, if the NRB content is obtained from a delivery server (not shown) connected to the Internet 20, the recording unit 71 records this NRB content received by the communication interface 72 from the delivery server.

The receiver 30 is structured as described in the paragraphs above.

Startup Information Details

Figure 10 illustrates the idea of start-up information embedded in OSHR packets when transmitting TP. As shown in FIG. 10, the trigger information is not embedded in all OSDP packets, but in those OSDP packets that are suitably synchronized for communication with AB content corresponding to the TV programs.

Depending on the nature of the start-up information, the same start-up information may be transmitted many times out of fear that the transmitted start-up information may be lost and not received by the receiving device 30.

11 shows when the trigger information is stored in the SINR packet. The OCHR packet is a TP packet in which adaptation_field (adaptation_field) contains the OCHR. The start information (Triggerlnfo_descriptor Descriptor_Inf) is contained in the transport_private_data_byte (transfer_private_data_byte) byte, which follows the OCHR. When the start-up information is contained in the packet, "transport_private_data_flag" (private_transfer_data_ flag) in the "Various_flags" preceding the OSHR is set to "I".

12 lists typical information points included in the startup information.

The item "trigger identifier" means information that identifies the discussed trigger information. When the trigger information of the same creature is transmitted many times, the trigger identifier of each set of trigger information is the same. The “startup type” item indicates that this startup information is one of four types: application launch (indicating the receipt and execution of an HTML data broadcasting document (PDZO)), application termination (indicating a stopping execution of an HTML data broadcasting document (PDZO)), application event (indicating the triggering of an event (for example, updating a display creature) in the currently executing HTML data broadcasting document (PLC)), and preliminary storage (indicating only receiving the HTML data broadcasting document (PLC)).

The paragraph “application identifier” means information that identifies an HTML Data Broadcasting Document (PDLO) corresponding to this starting information. The item “application type” denotes information that indicates the type (html) of the HTML data broadcasting document (PDZO) corresponding to this starting information. The item "identifier of a business operator" means information that identifies a business operator (for example, a broadcasting station) that performs the service of executing an HTML data broadcasting document (PDZO) corresponding to this starting information. The item “URL (Unified Resource Locator) of the application” means the URL of the destination from which the HTML data broadcasting document (PDZO) should be obtained when the launch type is “application launch” or “preliminary memorization”. The item “stored information identifier” is described only for the designation of an HTML data broadcasting document (PDLO), which must be launched and which has already been saved (received) when the launch type is “application launch” and when any HTML data broadcasting document (PLLD) should not be received immediately.

The “autorun flag” item is described when the launch type is “application launch”, and this flag is set either on or off. When the autorun flag is set to be enabled, autorun (i.e., an HTML data broadcasting document (PDZO) starts automatically) is in fact. When the autostart flag is set to off, manual start (that is, the user is prompted to enter the operation, and the document starts under the influence of the input of the operation).

The item “application stop time” means information indicating the time at which the currently executing HTML data broadcasting document (PDO) is to be stopped when the start information is not accepted, the type of launch of which is “application stop”.

The item “application name” means the name of the data broadcasting service (embodied by the HTML data broadcasting document (PDZO)) to be presented to the user when the “autorun flag” is set to start manually. The item “event identifier” means information that identifies an event when the trigger type is “application event”. It should be noted that not all of the points explained above are always included in the startup information; only items necessary for the synchronization in question are included.

FIG. 13 shows a typical syntax structure of trigger information. This syntactic structure of the trigger information is discretionary and is not limited to that shown in FIG. 13.

The start-up process of the content of the EAP

The following explains the process of manipulating trigger information to be executed by the receiving device 30 when receiving this trigger information.

Fig is a block diagram of an algorithm explaining the contents of the PDZO, which must be started by the process of manipulating the launch information. This process of triggering the content of the PDZO is executed when the events “a” or “b” in FIG. 5 occur, for example, when a user watches a TV program. The process of launching the content of the PDZO is carried out repeatedly while a digital TV broadcast signal is being received.

In step S1, on the basis of input from the demultiplexing unit 62, the control unit 68 awaits an OCHR packet including the trigger information to be received. Upon receipt of the OCHR packet including the trigger information, control proceeds to step S2.

In step S2, the control unit 68 detects the start information from the received SINR packet and, based on the extracted start information, determines whether the processing following the step S3 has already been completed. If it is determined that the processing following step S3 has already been completed, control returns to step S1 and the subsequent steps are repeated. On the other hand, if it is determined that the processing following step S3 has not yet been completed, control proceeds to step S3.

In step S3, the control unit 68 identifies the start type as “application start”, “application event”, “application stop” or “pre-storage”.

If, in step S3, the startup type of the discussed startup information is identified as “application startup”, control proceeds to step S4.

In step S4, the control unit 68 determines whether a stored application identifier is assigned in this start-up information and whether a data broadcasting HTML document (PLC) corresponding to the assigned identifier is already stored in the storage unit 71.

If the determination in step S4 is negative, control proceeds to step S5. In step S5, the control unit 68 controls the browser 73-1 to access the server 12 corresponding to the application URL in the start-up information to obtain a data broadcasting HTML document (PES) corresponding to the application identifier in the start-up information. If it turns out that the corresponding HTML data broadcasting document (PLC) has already been received from the server 12 corresponding to the aforementioned URL, and is already remembered "in step S14, which will be discussed later, step S5 is skipped, so that the discussed document can be used in step S7 and subsequent steps, then control proceeds to step S7.

On the other hand, if it is determined in step S4 that the stored application identifier is assigned in this start-up information and that the data broadcasting HTML document (PLC) corresponding to the assigned identifier is already stored in the recording unit 71, control proceeds to step S6. In step S6, the control unit 68 controls the browser 73-1 to read from the recording unit 71 of the HTML data broadcasting data document (PES) corresponding to the stored application identifier in the startup information. After that, control proceeds to step S7.

In step S7, the control unit 68 determines whether the startup flag for automatic start is set in the startup information.

If it is determined in step S7 that the startup flag in the startup information is not set to start automatically (i.e., set to start manually), control proceeds to step S8. In step S8, the browser 73-1, under the control of the control unit 68, prompts the user to perform an operation to start the HTML data broadcasting document (PLC) (ie, execute the operation) by displaying the message “Do you want to execute the“ application (its name)? ” or the like on the screen. If it is determined in step S9 that the user has entered a triggering operation under the influence of the prompt display, control proceeds to step S11. In step S11, the browser 73-1, under the control of the control unit 68, launches (executes) the data broadcasting HTML document (PSS) obtained in step S5 or read in step S6. In this way, the content of the PDZO is launched.

After that, the control returns to step S1, and the subsequent steps are repeated.

In step S9, following the prompting in step S8, it is determined whether the user has entered a triggering operation. If it is determined in step S9 that the user has not entered a triggering operation, and if it is determined in step S10 that a predetermined period of time has elapsed, then control returns to step S1 and the subsequent steps are repeated.

If it is determined in step S7 that the startup flag in the startup information is set to automatically start, control proceeds to step S11. In step S11, the browser 73-1, under the control of the control unit 68, launches the data broadcasting HTML document (PLC) obtained in step S5 or read in step S6. When the content of the ECD is started, control returns to step S1, and the subsequent steps are repeated.

If it is determined in step S3 that the trigger type of this trigger information is an “application event”, control proceeds to step S12. In step S12, the control unit 68 controls the browser 73-1 to initiate (execute) in the currently executing data broadcast HTML document (PLC) this event, which corresponds to the event identifier in the start information, only if the application identifier of this start information matches the application identifier the currently executing HTML data broadcasting document (PDZO). After that, the control returns to step S1, and the subsequent steps are repeated.

If it is determined in step S3 that the start type of this start-up information is “application stop”, control proceeds to step S13. In step S13, the control unit 68 controls the browser 73-1 to stop the currently executing HTML data broadcasting document (PELO) application identifier only if the application identifier of this start-up information matches the application identifier of the currently executing HTML data broadcasting document (PELO). After that, the control returns to step S1, and the subsequent steps are repeated.

Even if the start-up information of the type “application stop” is not accepted, when the current time reaches the “application stop time” described in the start-up information that launched the currently executing HTML data broadcasting document (PLC), the current HTML broadcasting data document (PDZO) stops.

If it is determined in step S3 that the trigger type of this start-up information is “pre-storage,” control proceeds to step S14. In step S14, the control unit 68 controls the browser 73-1 to access the server 12 corresponding to the application URL in the start-up information, to obtain a data broadcasting HTML document (PLC) corresponding to the application identifier in the start-up information, and save (previously remember) the received document in storage means, such as a cache, contained in a browser 73-1. After that, the control returns to step S1, and the subsequent steps are repeated.

If the trigger type is “pre-storage,” as in the case of step S14, it is possible to obtain the corresponding HTML data broadcasting document (PDLO) before the broadcast time of the TV program to be included. In this way, when the moment of the TV program to be included starts, the corresponding HTML data broadcasting document (PREV) can be executed immediately.

This paragraph completes the explanation of the start-up process of the content of the EAP.

Typical screen displays that appear when executing an HTML data broadcasting document (PDZO)

Fig. 15 shows typical screen transitions that occur when the autostart flag is set to off (i.e., manual start) in the start up information when an HTML data broadcasting document (PDZO) is executed in connection with the passage of a TV program.

When receiving the start-up information, the start-up type of which is “launch the application” and in which the autostart flag is off (manual start), when the user watches the TV program, the corresponding HTML data broadcasting document (PDZO) is obtained (corresponding HTML in Fig. 15). Then, the display (corresponding to “Launching adj.?” In FIG. 15), prompting the user to perform an operation to start the HTML data broadcasting document (PDZO), is displayed superimposed on the picture of the TV program. When the user enters a triggering operation under the influence of this prompt, an HTML data broadcasting document (PDZO) is executed. This translates the screen display into a composite picture 43, as shown in FIG. 3, for example, with a picture 42 of the content of the PDZO superimposed on the picture 41 of the TV program.

If the start-up information, the start-up type of which is the “application event”, is received during the execution of the HTML data broadcasting document (PDZO), the event corresponding to the event identifier in the start-up information is called in the currently executing HTML data broadcasting document (PLZO). This operation changes on the screen display what is shown in the display area of the content of the PDZO (for example, the area where the picture 42 is displayed in Figure 3), into the picture corresponding to the event identifier in the start information (for example, “information 1” is replaced by “ information 2 ”,“ information 2 ”is replaced by“ information 3 ”, etc.).

After that, when receiving the start-up information, the start-up type of which is “application stop”, the currently executing HTML data broadcasting document (PDZO) is completed, and only picture 41 of the TV program is displayed in full screen.

Other typical screen displays appearing during the execution of an HTML data broadcasting document (PDZO).

Meanwhile, an HTML data broadcasting document (PDZO), executed in connection with the passage of a TV program, may not cause a screen display. This type of data broadcasting HTML document (PELV) may be executed without the user of the receiving device 30 knowing that the data broadcasting HTML document (PELV) is being executed. This type of HTML data broadcasting document (PDZO) can be used when, for example, an audience study is carried out on TV programs. Specifically, whether or not a given TV program is being watched can be recorded for a given start-up information, the launch type of which is an “application event”, and the recorded result can be sent to a predetermined server in a synchronized manner, respectively. This makes it possible to check the ratings of TV programs at intervals in which starting information is transmitted, the launch type of which is the “application event”.

Fig. 16 shows typical screen transitions that occur when the autostart flag is set to on (startup) in the startup information when an HTML data broadcasting document (PREV) that does not cause a screen display is executed in connection with the passage of a TV program.

When receiving start-up information, the start-up type of which is “launch the application” and whose autorun flag is set to on (for automatic start), when the user watches the TV program, the corresponding HTML data broadcasting document (PDO) is obtained and executed. It should be noted here that only picture 41 of the TV program remains displayed on the screen.

When receiving the start-up information, the start-up type of which is the “application event”, when the HTML data broadcasting document (PDZO) is executed, the event corresponding to the event identifier in the start-up information is called in the currently executing HTML data broadcasting document (PDZO). In this case, also only the picture 41 of the TV program remains displayed on the screen.

After that, upon receiving the start-up information, the start-up type of which is “stopping the application”, the currently executing HTML data broadcasting document (PDZO) is completed.

PDZO Content Life Cycle

A typical life cycle of the content of the TLV is explained below with reference to FIG.

When receiving startup information. The type of launch of which is “launch of the application” when the HTML document for data broadcasting (PLC) to be received and executed by the receiving device 30 is in the operational state of the PZO stop (corresponding to the “PZO Stop” in FIG. 17), i.e. when the receiving device 30 still needs to receive an HTML data broadcasting document (ELCD), there is a transition from the operational state of the stop of the ECD to the operational state of the active ECD (corresponding to the “Active ECD” in FIG. 17), and the HTML data broadcasting document (ECD) is obtained from the server 12.

And the display prompting the user to perform an operation to start the HTML data broadcasting document (PDZO) appears superimposed on the picture of the TV program. When a user enters a triggering operation under the influence of this prompt, an HTML Data Broadcasting Document (PDLO) is launched. Then, as shown in FIG. 3, the composite picture 43 is displayed on the screen, for example, with a picture 42 of the content of the PDZO superimposed on the picture 41 of the TV program.

In the operational state of the active PDL, the received HTML data broadcasting document (PDL) allows the receiving device 30 to perform a specific process to display a picture 42 of the contents of the PDL. That is, in the operational state of the active PDZO, the control mode of the receiving device 30 is set to “Managed Broadcasting”, in which it is allowed to perform a specific process using an HTML data broadcasting document (PDZO) received from the server 12 managed by the broadcasting organization.

When receiving the start-up information, the start-up type of which is the “application event” in the operational state of the active PDLO, the event corresponding to the event identifier in the start-up information is called in the currently executing HTML data broadcasting document (PDLO).

In the operational state of the active PDZO, if start-up information is received, the type of start of which is “application stop” or if the application stops the time, the transition from the operational state of the active PDZO to the operational state of the PDZO stop occurs. Here, for example, the received HTML Data Broadcasting Document (PDLO) is discarded.

In addition, when receiving start-up information, the start-up type of which is “preliminary memorization” in the operational state of the shutdown of the PDZO, the transition from the operational state of the shutdown of the PDZO to the operational state of the ready preliminary memorization of the PDZO occurs. The corresponding HTML data broadcasting document (PDLO), for example, is obtained and pre-stored.

And when receiving start-up information, the start-up type of which is “launching the application” in the operational state of ready preliminary memorization, there is a transition from the operational state of ready preliminary memorization to the operational state of the active PDL. In the operational state of the active PDL, a previously stored HTML data broadcasting document (PDL) is launched.

In addition, in the operational state of the active PDZO, if the user presses a button, etc., associated with the web page of the automaker or the like, there is a transition from the operational state of the active PDZO to the operational state of the active web page (corresponding to the “Active web page "On Fig). In the operational state of the active web page, an HTML document of the web page is executed from the server 22, which is not managed by the broadcasting organization, whereby the automaker's web page or the like is displayed.

In the operational state of the active web page, the receiving device 30 is not allowed to perform specific processes using the resulting HTML web page document. That is, in the operational state of the active web page, the control mode of the receiving device 30 is set to "Uncontrolled broadcasting", in which specific processes cannot be performed using the HTML document of the web page received from the server 22, which is not controlled by the broadcasting organization.

In the operational state of the active PDZO (when the control mode is set to “Managed Broadcasting”), it is necessary to take measures to perform specific processes, such as reading pre-recorded area information from the receiving device 30 in order to provide data broadcasting service.

On the other hand, in the operational state of the active web page (when the control mode is set to “Uncontrolled broadcasting”), it is necessary to take measures to prohibit specific processes so that processes such as reading pre-recorded area information from the receiving device 30 are not fraudulent to obtain illegal leak.

Thus, when the HTML document to be executed is obtained from the server 12 managed by the broadcasting organization, the receiving device 30 has a control mode set to “Managed broadcasting” in which it is allowed to perform specific processes, as discussed above.

On the other hand, when the HTML document to be executed is obtained from a server not controlled by the broadcasting organization, the receiving device 30 has a control mode set to “Uncontrolled broadcasting” in which specific processes are prohibited.

About control mode

Fig. 18 shows an example of a transition originating from the operational state of the active PDZO to the operational state of the active web page when events are triggered one after the other in the operational state of the active web page, i.e. when the control mode is set from “Managed Broadcasting” to “Uncontrolled Broadcasting”.

Here, it is assumed that in each HTML Data Broadcasting Document (PLC) of the URL, identifying the HTML document to be executed to update the content of the PLC, picture 42 is described in connection with the event identifier.

With the relevant description given above when receiving the start-up information, the start-up type of which is the “application event”, the HTML document “al.html” for executing the event identified by the event identifier included in the start-up information is obtained and executed based on the URL “http: // www .a.com / al.html ”described in the HTML Data Broadcasting Document (PREV).

Further, when the start-up information, the start-up type of which is the “application event”, is received again, the HTML document “a2.html” for executing the event identified by the event identifier included in this start-up information is obtained and executed based on the URL: “http: // www.a.com/a2.html ”described in the HTML Data Broadcasting Document (PDLO). This causes the display of the image 42 to be sequentially updated by executing the HTML document “al.html” and with the image displayed by the execution of the HTML document “a2.html”.

In addition, it is assumed that the HTML Data Broadcasting Document (PDLO) describes the location “http://www.b.com/b1.html” associated with the HTML “b1.html” to be executed when the user performs the operation to select a driver picture displayed in the picture 42 of the content of the PDZO (Figure 3).

If the user performs an operation to select a driver picture shown in picture 42 (Figure 3) in the operational state of the active PDZO, the transition from the operational state of the active PDZO to the operational state of the active web page occurs.

In this operational state of the active web page based on the associated location “http://www.b.com/b1.html”, the receiving device 30 receives the HTML document of the web page “b1.html” from the server 22 not controlled by the broadcasting organization, and executes the received document.

As shown in FIG. 18, when some HTML documents aimed at execution must be received from the server 12 and executed in the operational state of the active PDZO, for example, HTML documents (“a1.html” and “a2.html in this case) each server 12 (“http: // www / a / com /” in this case) managed by the broadcasting organization is obtained.

Also in the operational state of the active web page, for example, another HTML document (“b1.html” in this case), aimed at execution, is obtained from server 22 (“http: //www.b.coml” in this case) not managed by the broadcasting organization.

As explained above, when HTML documents are to be received for execution from server 12, steps must be taken to perform the specific processes to be executed; when HTML documents are to be received for execution from a server other than server 12, measures must be taken to prohibit specific processes.

Then, the receiving device 30 determines whether the specified execution-oriented HTML document is received from the server 12 by checking whether the domain name of the server 12 managed by the broadcasting organization matches the domain name of the location from which the HTML document under discussion is obtained.

In this case, when implementing the data broadcasting service, the receiving device 30 determines whether the specified HTML document for execution is obtained from the server 13 by considering the domain name of the location from which the first HTML document is obtained, i.e. from which the HTML data broadcasting document (PDZO) is obtained (“www.a.com” in this case), as the domain name of the server 12 managed by the broadcasting organization.

Based on whether the domain name of the HTML document is the transition destination as the domain name of the server 12 managed by the broadcasting organization, the receiving device 30 sets the control mode to either “Managed Broadcasting” or “Uncontrolled Broadcasting”.

And when the control mode is set to “Managed Broadcasting” (ie, in the operational state of the active PDZO), the receiving device 30 may perform specific processes; when the control mode is set to "Uncontrolled broadcasting" (in the operational state of the active web page), the receiving device 30 cannot perform specific processes.

Whereas when implementing a data broadcasting service, the receiving device 30 considers the domain name of the location from which the HTML data broadcasting document (PDZO) is obtained, as the domain name of the server 12 managed by the broadcasting organization, it is alternatively also possible to preserve this domain name of the server managed by each speaker corresponding to each channel to be received.

Then, the receiving device 30 may select from a number of pre-stored domain names the domain name of the receiving channel and consider this domain name as the domain name of the server managed by the broadcasting organization.

As another alternative, while the receiving device 30 uses domain names to determine whether a given HTML document for execution is obtained from server 12, any other information can be used for this purpose if the information discussed uniquely identifies the location server from which is a document. For example, in addition to domain names, the receiver 30 may use media access control (MAC) addresses, Internet Protocol (IP) (IP) addresses, and the like, to determine if an HTML document is received from server 12 aimed at execution.

In this case, while the HTML document of the web pages received from the server 22 was explained above as a typical HTML document not approved by the broadcasting organization with reference to FIGS. 17 and 18, HTML data broadcasting documents (DZON) or HTML broadcasting data documents ( NMDZOs) not approved by the broadcasting organization are also processed in this way.

DZON Content Launch Process

Below, with reference to the flowchart of FIG. 19, the process of triggering the content of the DZON is explained.

In step S31, based on the control signal from the operation unit 70 or from the remote controller 32, the control unit 68 determines whether an event has occurred to trigger the content of the DZON. A typical event for triggering DZON content is event D in FIG. 5, which occurs when the user, for example, selects an independent data broadcast channel.

For example, if event D in FIG. 5 has occurred and if it is determined that an event for triggering the content of the DZON has occurred (“Yes” in step S31), control proceeds to step S32.

In step S32, the control unit 68 controls the browser 73-1 to access the server 12 corresponding to the URL of the DZON content to be launched to obtain a data broadcasting HTML document (DZON). Since the HTML data broadcasting document (DZON) obtained here is a document that is approved by the broadcasting organization, as in the case of FIG. 5, this document is obtained from the server 12 managed by the broadcasting organization. In this case, the control mode is set to "Managed broadcasting" for the discussed document HTML data broadcasting (DZON).

In step S33, the browser 73-1, under the control of the control unit 68, launches the data broadcasting HTML document (DZON) obtained in step S32. In this way, the content of DZON is launched.

After that, the control returns to step S31, and the subsequent steps are repeated.

It was explained above with reference to the example of FIG. 19 that the HTML data broadcasting document (DZON) is approved by the broadcasting organization in accordance with the use case of FIG. 5. If the data broadcasting HTML document (DZON) is not approved by the broadcasting organization, this HTML document is obtained from the server 21, and the control mode for this document is set to “Uncontrolled broadcasting”.

The preceding paragraph completes the explanation of the process of launching the content of DZON.

The process of launching the content of NMDZO

Below, with reference to the flowchart of FIG. 20, a process for triggering a content of a DMZO is explained.

In step S51, based on a control signal from the operation unit 70 or from the remote controller 32, the control unit 68 determines whether an event has occurred to trigger the contents of the DMDT. A typical event for triggering the content of an NMDZ is event C in FIG. 5, which occurs when a user, for example, selects a content channel of an NMDZ.

For example, if event C in FIG. 5 has occurred, and if it is determined that an event for triggering the content of the NMWD has occurred (“Yes” in step S51), control proceeds to step S52.

In step S52, the control unit 68 controls the browser 73-1 to access the server 21 corresponding to the URL of the content of the DMLC to be launched in order to obtain an HTML data broadcasting document (DMLC). Since the data broadcasting HTML document (NMDM) obtained here is a document that is not approved by the broadcasting organization, as in the case of FIG. 5, this document is obtained from the server 21 not controlled by the broadcasting organization. In this case, the control mode is set to “Uncontrolled broadcasting” for the discussed document HTML data broadcasting (NMDMO).

In step S53, the browser 73-1, under the control of the control unit 68, launches the data broadcasting HTML document (NMCD) obtained in step S52. In this way, the content of the NMDZO is launched.

After that, control returns to step 5

It was explained above with reference to the example of FIG. 20 that the HTML document of data broadcasting (NMDM) is not approved by the broadcasting organization in accordance with the use case of FIG. 5. If the HTML data broadcasting document (NMDM) is a document that is approved by the broadcasting organization, this HTML document is obtained from the server 12, and the control mode for this document is set to "Managed broadcasting".

The preceding paragraph completes the explanation of the launch process of the content of the NMDZ.

Details of the process of establishing a control mode

Below, with reference to the flowchart of FIG. 21, the control mode setting process performed by the receiving device 30 for setting the control mode based on the location domain name from which the HTML document is obtained is explained.

The control mode setting process is started, for example, when the data broadcasting HTML document (PLC) is started in step S11 of FIG. 14, or when the data broadcasting HTML document (DZON) is started in step S33 of FIG. 19.

In step S71, the control unit 68 obtains the domain name of the location from which the data broadcast HTML document to be launched is obtained.

That is, if, in step S5 or S14 of FIG. 14, an HTML data broadcasting document (PDLD) was received based on the URL in the start-up information, for example, the control unit 68 receives the domain name of the location (server 12) from which the document to be launched should be obtained HTML data broadcasting (PDZO) based on the URL application in the launch information.

As another example, if the data broadcast HTML document (PLC) to be started was read from the recording unit 71 in step S6 of FIG. 14, the control unit 68 controls the browser 73-1 to obtain the domain name of the server 12, which contains the HTML document to be read data broadcasting (PDZO), and for submitting the received domain name to the control unit 68. In this way, the control unit 68 receives the domain name.

In this case, if the HTML document for data broadcasting (PLC) is to be recorded in the recording unit 71, it is assumed that the domain name of the server 12, which contains the HTML document for broadcasting data (PLC), is subject to recording in connection with the HTML document (PZO).

As another example, if the HTML data broadcasting document (DZON) to be launched is obtained in step S32 of FIG. 19 based on the URL specified by the user-selected channel, the domain name of the location (server 12) from which the HTML broadcasting document to be launched is obtained data (DZON) is obtained on the basis of this UUR.

In step S72, the control unit 68 controls the browser 73-1 to operate in the "Managed Broadcast" control mode, in which specific processes are allowed to execute. That is, since the HTML data broadcasting document (PDZO) and the HTML data broadcasting document (DZON) in this example are obtained from the server 12 managed by the broadcasting organization, the control unit 68 controls the execution of these HTML documents through the browser 73-1 in a way that allows (not prohibiting ) specific processes through the execution of HTML documents.

In step S73, the control unit 68 determines whether a document transition including HTML documents has occurred based on the input trigger information, control signals from the operation unit 70 or the remote controller 32. When it is determined that the document has passed, control proceeds to step S74 .

In step S74, the control unit 68 determines whether the HTML document is received as the transition destination from the server 12 managed by the broadcasting organization, based on whether the domain name of the location from which the HTML document is obtained as the transition destination matches the domain name, obtained in step S71.

If it is determined in step S74 that the HTML document as the transition destination is received from the server 12, the control returns to step S73, and the subsequent steps are repeated, and the browser 73-1 is allowed to support the operation in the "Controlled broadcast" control mode.

In addition, if it is determined in step S74 that the HTML document as the transition destination is not obtained from the server 12, control proceeds to step S75.

For example, if the event “e” occurs when the UI2 is displayed in FIG. 5, there is a transition from an HTML data broadcasting document (LARP) to an HTML data broadcasting document (NMDM). In this case, the HTML document of data broadcasting (NMDM) as the destination of the transition is obtained from the server 21, and the domain names of the documents involved do not coincide with one another. Thus, the result of the determination process in step S74 is negative (“No”), and control proceeds to step S75.

As another example, if the event “g” occurs when displaying the UI5 in FIG. 5, there is a transition from an HTML data broadcasting document (DZON) to an HTML broadcasting data document (NDDM). In this case, also, the HTML data broadcasting document (NMDMO) as the transition destination is obtained from the server 21, and the domain names of the involved documents do not coincide with one another, so that control proceeds to step S75.

In step S75, the control unit 68 controls the browser 73-1 or 73-2 to operate in the "Uncontrolled broadcasting" control mode, in which specific processes are not permitted. That is, the control unit 68 controls the execution of the HTML documents by the browser 73-1 or 73-2 so that it is not allowed (forbidden) to carry out specific processes by executing the HTML document.

In this case, the browser 73-2, for example, is prohibited from executing specific processes, and it implements an HTML data broadcasting document (NMDM) as an HTML location document.

In this case, it is assumed that the HTML data broadcasting document (PDLO) is stopped based on the start-up information, the launch type of which is “application stop” when the HTML data broadcasting document (NMDZO) is executed.

Then, in step S76, based on the operation signal from the operation unit 70 or from the remote controller 32, the control unit 68 determines whether a predetermined operation, such as event B in FIG. 5, has been performed. When it is determined that the predetermined operation has been completed, control returns to step S71, and the subsequent steps are repeated. For example, the control unit 68 determines whether start-up information has been entered to launch a new HTML Data Broadcasting Document (PDLO). When it is determined that the corresponding start-up information has been input, the control returns to step S71, and the subsequent steps are repeated.

As explained above, in the transition of the control mode, if the domain name of the HTML document broadcasting data matches the domain name of the HTML document as the destination of the transition, the control mode is set to "Managed broadcast"; if the domain name of the HTML document broadcasting data does not match the domain name of the HTML document as the destination of the transition, the control mode is set to "Uncontrolled broadcasting".

When the control mode is set to “Managed Broadcasting”, processes such as reading user pre-stored area information from the receiving device 30 are carried out through the execution of an HTML data broadcasting document (PLCO) or an HTML data broadcasting document (NMCH). When the control mode is set to “Uncontrolled Broadcasting”, non-user-specific processes, such as a reading process, will not be executed by executing an HTML data broadcasting document (NMDMO) or an HTML web page document.

Thus, even if an HTML data broadcasting document (NMDMO) or an HTML web page document prepared by a malicious third party is obtained and executed, it is forbidden to execute processes not intended by the user.

2. Options

In the above embodiment, as shown in FIG. 17, the operational state of the HTML Data Broadcasting Document (PDLO) is one of four states: the operational state to stop the PDLO, the operational state to pre-remember the PDLO, the status of the active PDLO and the status of the active web page. Alternatively, as shown in FIG. 22, an operational state of a suspended EAP (corresponding to “Suspended EAP” in FIG. 22) can be added to the existing four states, so that there can be five states in total.

In this case, as shown in FIG. 23, a new start type “paused” is added as part of the start information. Thus, the startup type in the startup information can mean one of five types: application launch, application stop, application event, pre-memorization, and paused.

22, when receiving start-up information, the start-up type of which is “suspended” in the operational state of the active PDZO, the operational state of the corresponding HTML data broadcasting document (PDZO) transitions to the operational state of the suspended PDZO. In this case, with the corresponding HTML data broadcasting document (PESO) that has entered the operational state of the suspended PECA, another HTML data broadcasting document (PECO) can be placed in the operational state of the active PECA and executed.

When receiving start-up information, the launch type of which is “launching the application” in the operational state of the suspended PDZO, the corresponding HTML data broadcasting document (PDZO) switches to the operational state of the active PDZO. This makes it possible to trigger events in an HTML Data Broadcasting Document (PREV). At the same time, any other HTML document for data broadcasting (PZO) is forced to make a transition from the operational state of the active PZO to the operational state of the suspended PZO.

Although the above description has explained that HTML documents for broadcasting data are obtained by accessing servers connected to the Internet, an embodiment of this technology can alternatively transmit HTML documents for broadcasting data using a predetermined frequency band for broadcasting the broadcast data of the data as part of the broadcast range of the digital TV broadcast signal . For example, HTML documents for data broadcasting can be transmitted using the FLUTE - (File Delivery via Unidirectional Transport) sessions provided in RFC 3926. In this case, the channel information of the FLUTE session can be used, for example, to determine if the HTML document of the data broadcasting is the destination of the document transition that takes place under the control of the broadcasting organization (step S74 in FIG. 21).

Furthermore, if it is possible to obtain an HTML document for broadcasting data by communication or by broadcasting, this HTML document of broadcasting data can be obtained either by communication or by broadcasting in accordance with the priority of a predetermined destination from which this document is to be obtained.

Also, although the above description explained that the HTML documents of the data broadcasting approved by the broadcasting organization remain on the server 12 controlled by the broadcasting organization, and the HTML documents of the data broadcasting not approved by the broadcasting organization are stored on the server 21, managed by some other business operator , approved HTML data broadcasting documents may alternatively be stored on a server 21 operated by other business operators, such as content producers. That is, server 21 can store either approved HTML data broadcast documents, or non-approved HTML data broadcast documents, or both types of HTML documents. On the other hand, server 12 only stores approved HTML data broadcast documents.

Typical computer structure

In this case, the sequence of the processes described above can be executed either hardware or software. When a software-implemented processing sequence is to be carried out, the programs that make up the software can either be embedded in advance in the dedicated hardware of the computer to be used, or installed using a suitable recording medium in a universal personal computer or similar equipment capable of performing various functions based on these installed programs.

Fig is a block diagram showing a typical structure of a computer that performs the above sequence of processes using programs.

In this computer 100, a central processing unit (CPU) 101, a read-only memory (ROM) 102, and a random access memory (RAM) 103 are interconnected via a bus 104.

Additionally, an I / O interface 105 is connected to the bus 104. This I / O interface 105 is connected to an input unit 106, typically made of a keyboard, mouse, and microphone; with an output unit 107, typically consisting of a display and speakers; with a storage unit 108, typically formed by a hard disk, non-volatile memory, or the like; with a communication unit 109, typically formed by a network interface; and with a drive 110 that drives removable media 111, such as magnetic disks, optical disks, magneto-optical disks, or semiconductor storage devices.

In a computer having the structure outlined above, the CPU 101 performs the above sequence of processes by loading suitable programs from, say, a storage unit 108 via an input / output interface 105 and a bus 104 to RAM 103 for execution.

In this case, programs to be executed by a computer can be processed in the shown sequence of this description (i.e., based on a time sequence), in parallel, or in another accordingly synchronized form, such as when they are called if necessary.

In addition, these programs can be processed by a single computer or multiple computers on a distributed basis. Programs can also be transferred for execution to a remote computer or computers.

In this description, the expression "system" refers to the entire configuration made of many constituent devices.

In addition, it should be understood that this technology during the implementation is not limited to the above described embodiments and that various modifications, variations and changes to this technology can be made if they are in its essence and scope.

Further, this technology can also be implemented as follows. A device for receiving broadcast of AB content by means of broadcast waves, including: a receiving unit configured to receive a descriptive document described in a predetermined computer language for displaying a type of content other than AB content; a determining unit, configured to determine whether a broadcasting organization transmitting AB content or a business operator other than the broadcasting organization manages the received descriptive document; and a control unit, configured to control the execution of the received descriptive document in accordance with the result of the determination made by the determining unit.

1. A receiver for receiving broadcasts of AB content by means of broadcast waves, including:

- receiving unit, configured to obtain a descriptive document described in a predetermined computer language, to display a type of content other than AB content;

- a determining unit, configured to determine whether the broadcasting organization that transfers AB content or a business operator other than the broadcasting organization manages the additional descriptive document; and

- a control unit, configured to control the execution of the received descriptive document in accordance with the result of the determination made by the determining unit.

2. A receiving device, as described in paragraph 1 above, further comprising a start detection unit configured to detect start information. which is transmitted along with AB content and which relates to the management of a descriptive document to be executed in connection with the passage of AB content;

- in this case, based on the detected start-up information, the receiving unit receives a descriptive document from the information processing device controlled by the broadcasting organization, and

- while the determining unit determines that the descriptive document received from the information processing device is controlled by the broadcasting organization.

3. A receiving device, as described in paragraph 1 or 2 above, in which when executing a descriptive document that can be executed independently without communication with AB content, the receiving unit receives a descriptive document from the information processing device controlled by the broadcasting organization,

- while the determining unit determines that the descriptive document received from the information processing device is controlled by the broadcasting organization.

4. The receiving device, as described in any of paragraphs 1-3 above, in which when executing a descriptive document that can be executed only by a specific application program, the receiving unit receives a descriptive document from another information processing device that is controlled by another business operator, and the determining unit determines that a descriptive document received from another information processing device is controlled by another business operator.

5. The receiving device, as described in any of paragraphs 1-4 above, further comprising an executive unit configured to execute the received descriptive document;

- at the same time, if it is determined that the broadcasting organization controls this descriptive document, the control unit controls the executive unit to work in the first control mode, in which a predetermined specific process can be performed; and

- in this case, if it is determined that another business operator is managing the descriptive document, the control unit controls the executive unit to work in the second control mode, in which a specific process cannot be performed.

6. A receiving device, as described in paragraph 5 above, in which, when the executive unit is in the first control mode, each time a descriptive document is received, the determining unit determines whether the broadcasting organization or other business operator controls the received descriptive document, and

- in this case, if it is determined that another business operator is managing the descriptive document, the control unit forces the executive unit to exit the first control mode and enter the second control mode during operation.

7. The receiving device, as described in paragraph 5 above, in which if a predetermined operation is performed when the actuating unit is operating in the second operating mode, the control unit causes the actuating unit to exit the second operating mode and enter the first operating mode during operation.

8. A receiving device, as described in paragraph 1 above, in which the receiving unit receives a descriptive document transmitted using the first predetermined frequency range of a digital television broadcast signal of broadcast waves.

9. The method of admission, which includes stages in which:

- cause the receiving device to receive a descriptive document described in a predetermined programming language to display a type of content other than AB content transmitted by broadcast waves;

- make the receiving device determine whether the received descriptive document is controlled by the broadcasting organization transmitting the AB content or by the business operator other than this broadcasting organization; and

- force the receiving device to control the execution of the received descriptive document in accordance with the result of this determination.

10. A program for controlling a receiving device, forcing the computer of the receiving device to execute a process including the steps of:

- receive a descriptive document described in a predetermined programming language for displaying a type of content other than AB content transmitted through broadcast waves;

- determine whether the received descriptive document is managed by the broadcasting organization transmitting the AB content, or by the business operator other than this broadcasting organization; and

- control the execution of the resulting descriptive document in accordance with the result of this determination.

List of Reference Items

1 - Broadcast system

11 - Broadcast unit

12 - Server

21 - Server

22 - Server

30 - Receiving device

31 - Monitor

32 - Remote controller

61 - Tuner

62 - Demultiplexing unit

63 - Audio Decoder

64 - Audio output unit

65 - Video Decoder

66 - Start detection unit

67 - Video output unit

68 - Control unit

69 - Memory

70 - Operation unit

71 - Recording unit

72 - Communication Interface

73-1, 73-2 - Browser

74 - Infrared receiving unit

100 - Computer

101 - CPU

Claims (9)

1. A receiver for receiving broadcast audio-video (A-B) -content by means of broadcast waves, containing:
- a receiving unit configured to obtain a descriptive document described in a predetermined computer language to display a type of content other than said AB content;
- a determining unit, configured to determine whether a broadcasting organization transmitting said AB content or a business operator other than said broadcasting organization manages the received descriptive document;
- a control unit, configured to control the execution of said received descriptive document in accordance with the result of a determination made by said determining unit; and
- a start detection unit, configured to detect start-up information that is transmitted along with said AB content and which relates to the management of said descriptive document to be executed in connection with the passage of said AB content;
- in this case, on the basis of the detected start-up information, said receiving unit receives said descriptive document from an information processing device controlled by said broadcasting organization, and
- the determining unit determines that said descriptive document obtained from said information processing apparatus is controlled by said broadcasting organization. 2. The receiving device according to claim 1, in which:
- when executing a descriptive document that can be executed independently without communication with said AB content, said receiving unit receives said descriptive document from said information processing device controlled by said broadcasting organization, and
- wherein said determining unit determines that said descriptive document obtained from said information processing apparatus is controlled by said broadcasting organization. 3. The receiving device according to claim 1, in which:
- when executing a descriptive document that can only be executed by a specific application program, said receiving unit receives said descriptive document from another information processing device controlled by another business operator, and
- wherein said determining unit determines that said descriptive document obtained from said other information processing device is controlled by said other business operator. 4. The receiving device according to claim 1, further comprising an executive unit configured to execute the received descriptive document;
- in this case, if it is determined that said broadcasting organization manages said descriptive document, said control unit controls said executive unit to operate in a first control mode in which a predetermined specific process can be performed; and
- in this case, if it is determined that said other business operator controls the said descriptive document, said control unit controls said executive unit to operate in a second control mode in which said specific process cannot be executed. 5. The receiving device according to claim 4, in which
- when the executive unit operates in said first control mode, each time said descriptive document is obtained, said determining unit determines whether said broadcasting organization or said other business operator manages said received descriptive document, and
- at the same time, if it is determined that the mentioned other business operator controls the mentioned descriptive document, the said control unit forces the said executive unit to exit the first control mode and enter the second control mode during operation. 6. The receiving device according to claim 4, wherein if a predetermined operation is performed when said executive unit is operating in said second operating mode, said control unit causes said executive unit to exit said second operating mode and enter said first control mode during operation . 7. The receiving device according to claim 1, wherein said receiving unit receives said descriptive document transmitted using a first predetermined frequency range of a digital television broadcast signal of said broadcast waves. 8. A method for receiving broadcasting of audio-video (A-B) content through broadcast waves, including the steps of:
- make the receiving device receive a descriptive document described in a predetermined programming language to display a type of content other than AB content transmitted by broadcast waves;
- cause said receiving device to determine whether the received descriptive document is controlled by the broadcasting organization transmitting the said AB content or by a business operator other than the said broadcasting organization;
- cause said receiving device to control the execution of said received descriptive document in accordance with the result of this determination; and
- cause said receiving device to detect start-up information that is transmitted along with said AB content and which relates to the management of said descriptive document to be executed in connection with the passage of said AB content;
- wherein said descriptive document is obtained from an information processing device controlled by said broadcasting organization based on the detected trigger information, and
- said descriptive document obtained from said information processing apparatus is controlled by said broadcasting organization. 9. A recording medium containing a program recorded thereon for controlling a receiving device, causing the computer of said receiving device to execute a process including the steps of:
- receive a descriptive document described in a predetermined programming language to display a type of content other than AB content transmitted by broadcast waves;
- determine whether the received descriptive document is managed by the broadcasting organization transmitting the said AB content or by the business operator other than the broadcasting organization;
- control the execution of said descriptive document received in accordance with the result of this determination; and
- cause said receiving device to detect start-up information that is transmitted along with said AB content and which relates to the management of said descriptive document to be executed in connection with the passage of said AB content;
- wherein said descriptive document is obtained from an information processing device controlled by said broadcasting organization based on the detected trigger information, and
- said descriptive document obtained from said information processing apparatus is controlled by said broadcasting organization.

Images