JP2007124389A - Module management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem, wherein a module cannot be managed only with a module ID over a plurality of channels, since the module IDs have no uniqueness in a plurality of channels, although conventionally, the modules received in a digital broadcasting receiver, etc., are managed with the use of the module IDs, etc., so that there is a case where the different modules have the same module ID, when the modules of the plurality of channels are stored collectively in an HDD, etc., in association with channel transition. <P>SOLUTION: A module management device is provided, capable of holding the acquired modules in connection with not only the module IDs, etc., but service identification information of a service which acquires the module. A service ID can be used as the service identification information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a module management apparatus for managing a data broadcast module acquired from a digital broadcast wave.

In digital broadcasting, data broadcasting is provided in addition to video and audio of broadcast programs. Data for data broadcasting is stored and stored in a hard disk (hereinafter referred to as “HDD”) of a digital broadcasting receiver such as a digital television. It is displayed on a display screen or the like based on the obtained data. Data for data broadcasting is configured in units of modules, and there are a module ID, a module name, and the like as identification information for identifying a module. In the digital broadcast receiving apparatus, the stored module can be identified by storing the module ID or the like in association with the module in the HDD or the like. By the way, since one module is composed of a plurality of packets, it takes time to receive all the packets before the data broadcast is displayed on the display screen or the like. Therefore, if the module stored in the HDD or the like can be used instead of receiving the module when displaying the data broadcast, the time until the display can be shortened. However, since the content of the data broadcast changes with time, when the content of the data broadcast changes, a new module must be received again. Therefore, in order to determine whether the content of the data broadcast has changed, it is necessary to compare whether the module currently provided in the digital broadcast wave is the same as the module stored in the HDD or the like. . For example, Patent Document 1 discloses a system for acquiring in a short time a data block (a data unit that constitutes a module, and one module is constituted by a plurality of data blocks) that the receiving device has failed to receive. However, in Patent Document 1, a module ID is used to identify a module.
JP 2002-368707 A

  However, although a module can be uniquely identified by a module ID within one channel, the module ID is not unique among a plurality of channels. Therefore, if a module with multiple channels is stored in the HDD or the like when there is a channel transition, different modules may have the same module ID. Can not manage. Under such circumstances, in a conventional digital broadcast receiving apparatus, when a channel transition is performed, information related to the module of the channel before the transition is generally deleted from the HDD or the like. Therefore, the inconvenience that all the modules have to be acquired every time the channel transition is performed occurs.

  Therefore, the present invention proposes a module management apparatus that associates and holds a module acquired from a received digital broadcast wave and service identification information. The module includes at least a module ID and module data. The service identification information is information for identifying the service that has acquired the module, and corresponds to information for identifying a channel that provides data broadcasting, for example. That is, by storing not only the module ID but also the service identification information in association with the module, the module can be uniquely identified among a plurality of channels. A service ID may be used as service identification information. Further, by acquiring module update information indicating whether or not the module has been updated, it is determined whether the already held module has been updated, a new module has been added, etc., and acquired again. Only necessary modules may be acquired from digital broadcast waves. The module update information may be a transaction ID included in a DII (Download Information Indicator).

  According to the module management apparatus of the present invention, a module can be uniquely identified among a plurality of channels. For example, even when a channel transition is performed by a channel change by a user or the like, from the HDD or the like. There is no need to delete module information. Furthermore, it is possible to use a module stored in the HDD or the like when displaying or displaying the data broadcast, and until the data broadcast is displayed by acquiring only the updated module from the digital broadcast wave. Time can be shortened.

The best mode for carrying out the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to these embodiments, and can be implemented in various modes without departing from the spirit of the present invention. In addition, the relationship between the following embodiment and a claim is as follows. The first embodiment will mainly describe claims 1 and 5. The second embodiment will mainly describe claims 2 and 6. The third embodiment will mainly describe claims 3, 4, 7 and the like.
(Embodiment 1)

  (Embodiment 1: Overview) Embodiment 1 describes a module management apparatus having a function of acquiring a module and service identification information from a received digital broadcast wave, and holding them in association with each other.

  (Embodiment 1: Configuration) FIG. 1 illustrates a functional block diagram of a module device according to this embodiment. The module management device (0100) includes a “digital broadcast reception unit” (0101), a “module acquisition unit” (0102), a “service identification information acquisition unit” (0103), a “holding unit” (0104), Have

  Each unit which is a component of the present invention is configured by hardware, software, or both hardware and software. For example, as an example for realizing these, when a computer is used, there are hardware constituted by a CPU, a bus, a memory, an interface, a peripheral device, and the like, and software that can be executed on the hardware. As software, the functions of each unit are realized by sequentially executing a program developed on the memory, and processing, storing, and outputting data on the memory and data input via the interface. More specifically, FIG. 2 is a diagram illustrating the configuration of a general computer. The computer mainly includes a CPU (0210), an input / output interface (I / O) (0220), an HDD (0230), and a RAM (0240). ), ROM (0250), etc., the module management apparatus according to the present invention is realized with the same configuration as that of FIG. (The same applies throughout the specification.)

  The “digital broadcast receiving unit” (0101) has a function of receiving digital broadcast waves. Specifically, for example, a data string (stream) transmitted by a TS (Transport Stream) of MPEG (Moving Picture Experts Group) -2 generally used in digital broadcasting is received. Note that the digital broadcasting targeted by the present invention includes all digital broadcasting that provides data broadcasting using MPEG-2 TS as of October 19, 2005, regardless of whether in Japan or outside of Japan. In addition to video signals (video streams) and audio signals (audio streams) of broadcast programs, TS can transmit data in the form of sections, and a module for data broadcasting is also transmitted as section data. The section data is repeatedly transmitted by a transmission method called a data carousel method as shown in FIG. 3, and the section data includes a DII (Download Information Indicator) and a DDB (Download Data Block). DII indicates management information of each module transmitted in the data carousel method, and DDB is a data unit constituting the module, and includes data of each module itself. FIG. 4 shows the structure of DII. “Number of modules” indicates the number of modules described in the loop 1 in the DII. That is, loop 1 is repeated by the number indicated by “number of modules”. “Module ID” in the loop 1 is module identification information whose characteristics are described by “module size”, “module version”, and “module information”. Therefore, information about a plurality of modules is included in DII. One or more such DIIs are transmitted in the carousel. FIG. 5 shows the structure of the DDB. “Module ID” indicates the module ID of the module to which this block belongs. One module is composed of a plurality of blocks. The “block number” indicates the position of the main block in the module, and is “0” if the main block is the first block of the module. The “block data” is an area where the block data itself is stored. Therefore, the module data identified by the “module ID” is the “block data” arranged in the order of “block number”. FIG. 6 is a diagram showing the relationship between the “module”, the “block” of the DDB, and the “TS” of the MPEG-2 TS. One module is divided into a plurality of data blocks (DDB), and the data blocks are further divided and included in TS packets for transmission.

  FIG. 7 is a schematic diagram showing digital broadcast wave reception processing. First, a digital broadcast signal is received by an antenna (0701), and the received broadcast signal is subjected to processing such as demodulation, and a TS is output (0702). The output TS is separated into an audio stream (AS), a video stream (VS), and section data (S) (0703). Further, the separated audio stream (AS), video stream (VS), and section data (S) are separately decoded and analyzed (0704). Specifically, the processing of the digital broadcast receiving unit mainly corresponds to reception of a broadcast signal (0701) in FIG. Further, demodulation (0702) and TS separation processing (0703) may be performed.

  The “module acquisition unit” (0102) has a function of acquiring a data broadcast module from the digital broadcast reception unit (0101). “Module” generally refers to a data unit transmitted in a data carousel. Here, “module” is at least identification information for identifying a module such as a module ID included in DII or DDB, and It indicates information including module data itself composed of block data included in a plurality of DDBs. Specifically, the process of the module acquisition unit mainly corresponds to the decoding process (0704) in FIG. More specifically, module data is stored in a predetermined storage area such as a RAM or HDD in association with a module ID or the like obtained by executing the decoding process (0704). The module acquisition unit may include a program for causing the CPU to execute such processing. FIG. 8 shows an example of a module acquired by the module acquisition unit. “Module ID” is a module ID included in DII or DDB. “Module data” is data of a module identified by a module ID composed of block data included in a plurality of DDBs. FIG. 8 shows module data of a module whose module ID is “MD01”. ing.

  The “service identification information acquisition unit” (0103) has a function of acquiring service identification information for identifying the service that acquired the module from the digital broadcast reception unit (0101). The “service” corresponds to an organized channel. As shown in FIG. 9, one or a plurality of “transmission channels” exist in “broadcast networks” such as terrestrial digital broadcast and BS digital broadcast (note that one terrestrial digital broadcast has one transmission network). There are two transmission channels). The “transmission channel” is a channel unit called BS11 channel, BS4 channel, etc., for example. Further, a plurality of “organization channels” exist in the “transmission channel”. The “organized channel” is a channel represented by a three-digit channel number. For example, the BS4 channel currently has three organized channels 744, 745, and 746 as data broadcast organized channels. In addition, independent data broadcasting is provided in these organized channels. The broadcast station transmits a service ID, which will be described in detail in Embodiment 2, as information for identifying the data broadcasting service in units of organized channels. That is, in a digital broadcast receiving apparatus, when a data broadcast module is acquired, a service ID can be acquired as service identification information of the service that acquired the module. Further, since the service ID and the three-digit channel number of the organization channel are information held in a one-to-one relationship, the organization channel number may be used as the service identification information. Specifically, the processing of the service identification information acquisition unit mainly corresponds to the decoding process (0704) in FIG. More specifically, the service ID obtained by executing the decoding process (0704) is stored in a predetermined storage area such as a RAM or HDD. Further, the service identification information acquisition unit may include a program for causing the CPU to execute such processing.

  The “holding unit” (0104) has a function of holding a module and service identification information in association with each other. FIG. 10 shows a specific example of the holding unit. “Channel number” corresponds to service identification information, and “module ID” and “module data” correspond to modules. The holding unit is realized by storing information as illustrated in FIG. 10 as a database or the like in a predetermined storage area such as a RAM or an HDD. Further, as illustrated in FIG. 10, module IDs “MD01” and “MD02” are included in both channel numbers “744” and “745”. In this way, the same module ID may be used between different channels, but by holding the “channel number” that is service identification information as shown in FIG. 10, the “channel number” and the “module ID” are also stored. Each module can be uniquely identified among a plurality of channels by the combination. Specific processing of the holding unit includes, for example, a module stored in a predetermined storage area such as a RAM or HDD in the module acquisition unit (0102) and a RAM or the like stored in the service identification information acquisition unit (0103). The service identification information stored in a predetermined storage area such as an HDD is read, and the read module and service identification information are added to the information illustrated in FIG. 10 and held. “Add” means that, for example, if the information illustrated in FIG. 10 is realized in the database, “insert into module management information values ('744', 'MD01', '0x4A371BCF02... ')' (The database table name is “module management information”), and an SQL statement insert statement is generated and executed on the database. The holding unit may include a program for causing the CPU to execute such processing.

  (Embodiment 1: Process Flow) FIG. 11 illustrates a flowchart showing a process flow in the module management apparatus according to the present embodiment.

  First, a digital broadcast wave is received. This process is mainly executed by the digital broadcast receiver (step S1101). Next, a data broadcast module included in the digital broadcast wave received in step S1101 is acquired. This process is mainly executed by the module acquisition unit (step S1102). Next, service identification information of the service providing the module acquired in step S1102 is acquired from the digital broadcast wave received in step S1101. This process is mainly executed by the service identification information acquisition unit (step S1103). Finally, the module acquired in step S1102 and the service identification information acquired in step S1103 are stored in association with each other. This process is mainly executed by the holding unit (step S1104).

(Embodiment 1: Effect) The module management apparatus according to this embodiment can uniquely identify and manage a module even among a plurality of channels by holding the module in association with service identification information.
(Embodiment 2)

  (Embodiment 2: Overview) Embodiment 2 describes a module management apparatus characterized by acquiring a service ID as service identification information.

  (Embodiment 2: Configuration) FIG. 12 illustrates a functional block diagram of a module device according to this embodiment. The module management device (1200) includes a “digital broadcast reception unit” (1201), a “module acquisition unit” (1202), a “service identification information acquisition unit” (1203), a “holding unit” (1204), Have The service identification information acquisition unit (1203) includes a “service ID acquisition unit” (1205). That is, the module management apparatus according to the present embodiment is configured by adding “service ID acquisition means” (1205) to the module management apparatus according to the first embodiment.

  The “service ID acquisition unit” (1205) has a function of acquiring a service ID as service identification information. As described above, the “service ID” is information associated with the organization channel number on a one-to-one basis. Actually, the “service ID” is included in the NIT (Network Information Table) and transmitted. The NIT is a table for transmitting information such as the channel configuration and frequency in the broadcast network, and is transmitted from the broadcast station by MPEG-2 TS. Further, in the digital broadcast receiving apparatus, the organization channel number and the service ID are associated with each other, and the service ID and the frequency are associated with each other by receiving the NIT. For example, if a user switches the channel by specifying a three-digit organization channel number, the service ID is derived from the designated organization channel number, and the frequency of the broadcast wave to be acquired can be known from the service ID. It is.

  FIG. 13 shows a specific example of the holding unit in the present embodiment. In the holding unit in the present embodiment, the service ID is held in association with the module as service identification information instead of the channel number of the holding unit in FIG.

  (Embodiment 2: Process Flow) FIG. 14 exemplifies a flowchart showing a process flow in the module management apparatus according to the present embodiment.

  First, a digital broadcast wave is received. This process is mainly executed by the digital broadcast receiver (step S1401). Next, a data broadcast module included in the digital broadcast wave received in step S1401 is acquired. This process is mainly executed by the module acquisition unit (step S1402). Next, from the digital broadcast wave received in step S1401, a service ID is acquired as service identification information of the service providing the module acquired in step S1402. This process is mainly executed by the service ID acquisition unit (step S1403). Finally, the module acquired in step S1402 and the service ID acquired in step S1403 are stored in association with each other. This process is mainly executed by the holding unit (step S1404).

(Embodiment 2: Effect) In the module management apparatus according to the present embodiment, by using a service ID that can be directly received by digital broadcast waves as service identification information, it is possible to omit a conversion process to a knitted channel number or the like. it can.
(Embodiment 3)

  (Embodiment 3: Overview) Embodiment 3 acquires module update information included in a digital broadcast wave, and acquires a missing module based on module identification information held in the holding unit in association with the module update information. A module management apparatus characterized by the above will be described.

  (Embodiment 3: Configuration) FIG. 15 illustrates a functional block diagram of a module management apparatus according to this embodiment. The configuration of the module management apparatus according to the present embodiment is obtained by adding an “insufficient module acquisition unit” (1506) to the configuration of the module management apparatus according to the first or second embodiment. In FIG. 15, the structure which added the said lack module acquisition part (1506) to the structure of the module management apparatus which concerns on Embodiment 2 is illustrated. The module management apparatus (1500) includes a “digital broadcast receiving unit” (1501), a “module acquisition unit” (1502), a “service identification information acquisition unit” (1503), a “holding unit” (1504), The “insufficient module acquisition unit” (1506). The service identification information acquisition unit (1503) includes a “service ID acquisition unit” (1505).

  The “insufficient module acquisition unit” (1506) is stored in the storage unit (1504) in association with the module update information acquired from the digital broadcast reception unit (1501) and the service identification information of the service that acquired the module update information. Based on the existing module identification information for identifying the module, the module has a function of acquiring a deficient module that is a deficient module in the holding unit. “Existing module identification information” is, for example, a module ID in FIGS. 10 and 13, that is, a module ID of a module that has already been acquired. The “insufficient module” is a module necessary for displaying and outputting the same contents as the data broadcast provided by the current digital broadcast wave. That is, among the modules included in the received broadcast wave, a new module that is not held in the holding unit (1504), a module whose contents are updated, and the like are applicable. “Acquiring a deficient module” specifically refers to acquiring module data itself composed of a module ID or the like and block data included in the DDB. In addition, the module ID of the missing module is passed to the module obtaining unit (1502) and the module is obtained from the digital broadcast wave without the missing module obtaining unit directly performing the process for obtaining the missing module. Or the like may be output. “Module update information” is information that directly or indirectly indicates that a module has been updated. For example, the module version and module size included in the DII are applicable. The module update information may be a transaction ID included in DII. The “transaction ID” is included in the DII DSM-CC message header as shown in FIG. 16, but the transaction is performed when the DII changes in accordance with the update or increase / decrease of the module managed by the DII. The ID also changes. When a module managed by DII is updated, the module ID included in DII does not change, but the module size and module version change. In addition, when the number of modules managed by DII increases or decreases, the module IDs listed in “Module ID” and the like of loop 1 in FIG. 4 increase and decrease.

  FIG. 17 is a diagram schematically illustrating a case where a module managed by DII is updated. First, it is assumed that the transaction ID has changed from “TR01” to “TR02”. Module IDs included in DII in (A) are “MD01”, “MD03”, and “MD04”, and module IDs included in DII in (B) are also “MD01”, “MD03”, and “MD04”. However, when comparing the module size and module version of the module ID “MD03”, the module size is “8KB” and the module version is “Ver03” in the DII of (A). In DII, the module size is “16 KB” and the module version is “Ver13”. Therefore, in the case of FIG. 17, the module ID managed by DII does not change, but it can be seen that the module with the module ID “MD03” has been updated.

  FIG. 18 is a diagram schematically illustrating a case where the number of modules managed by DII increases. First, it is assumed that the transaction ID has changed from “TR01” to “TR03”. Module IDs included in DII in (A) are “MD01”, “MD03”, and “MD04”, but module IDs included in DII in (B) are “MD01”, “MD02”, “MD03”, “ Since it is MD04 ", it can be seen that the module ID" MD02 "has increased. Therefore, in the case of FIG. 18, it can be seen that the module ID managed by the DII has increased.

  FIG. 19 shows a specific example of the holding unit in the present embodiment. The holding unit in the present embodiment is premised on holding the module size, the module version, and the like in addition to the information held in the holding unit illustrated in FIG. This is because, as will be described later, these pieces of information are usually required when determining the deficient module to be acquired by the deficient module acquisition unit.

  FIG. 20 shows a specific example of processing in the deficient module acquisition unit. This example is an example of processing when the module update information is a transaction ID. First, it is assumed that module IDs and the like having service IDs “SV1” and “SV2” are held in the holding unit (2002). This is the case, for example, when both the “SV1” and “SV2” modules have been acquired because the user has switched channels. When the module is acquired, the insufficient module acquisition unit (2001) associates and holds the service ID of the service that acquired the module and the transaction ID (2004) (in FIG. 20, the service ID “SV1”). Only the transaction ID "is shown). Here, assuming that the service ID of the service is “SV1” due to the channel switching, the deficient module acquisition unit (2001) first includes the transaction included in the DII (2005) acquired from the digital broadcast reception unit (2003). The ID is compared with the transaction ID (2004) of the held service ID “SV1”. As a result of comparison, if these transaction IDs have the same value, the module managed by DII (2005) is not changed, and the module of service ID “SV1” held by the holding unit (2002). Can be used to display and output data broadcasts. However, if these transaction IDs have different values, it indicates that the module managed by DII (2005) has been changed. In this example, the value of the transaction ID included in the DII (2005) acquired from the digital broadcast receiving unit (2003) is “TR02”, and the value of the transaction ID (2004) of the held service ID “SV1” is It is assumed that it is “TR01”. Since these transaction ID values are different, the module ID and the like included in DII (2005) are compared with the module ID and the like held in the holding unit (2002). Specifically, for example, first, it is determined whether there is an increased or decreased module ID by comparing the module ID included in DII (2005) with the module ID held in the holding unit (2002). If there is a module ID included in the DII (2005) but not held in the holding unit (2002), the module is a missing module. In addition, if there is a module ID that is not included in DII (2005) but is included in the holding unit (2002), information related to the module is deleted from the holding unit (2002), or predetermined information that holds information is stored. If this recording area is set as an overwrite-inhibited area and protected, processing such as setting to an overwritable area is performed. The module ID included in both the DII (2005) and the holding unit (2002) is determined by comparing the module size and module version to determine whether the module ID has been updated. Becomes a missing module. Here too, information relating to the updated module is deleted from the holding unit (2002), or when a predetermined recording area holding the information is set as an overwrite-inhibited area and protected, it is set as an overwritable area. And so on. In this example, the module ID included in the DII (2005) and the holding unit (2002) is the same, but the module size and module version of the module ID “MD03” are different. It can be seen that has been updated. Therefore, the module with the module ID “MD03” becomes a missing module and is acquired again. In addition, the module ID or the like may be directly compared without first comparing the transaction ID. However, when the module managed by the DII is not changed, the process of comparing the module ID and the like is a wasteful process. Therefore, such unnecessary processing can be omitted by comparing the transaction IDs first. More specifically, the deficient module acquisition unit may include a program for executing such a process. For example, when the digital broadcast receiving unit (1501) receives a digital broadcast wave, The service ID included in the broadcast wave and the transaction ID included in DII are associated with each other and stored in a predetermined storage area such as a RAM or HDD. In addition, the transaction ID included in the DII acquired from the digital broadcast wave is always acquired, and the acquired transaction ID is associated with the service ID of the service that acquired the transaction ID in a predetermined storage area such as a RAM or HDD. The stored transaction ID is read and compared, and the comparison result is stored in a predetermined storage area such as a RAM. Triggered by the comparison result indicating that the comparison result read from the predetermined storage area is different, the module ID included in the DII acquired from the digital broadcast wave, the RAM in the holding unit (1504), and the like A module ID stored as a database or the like in a predetermined storage area such as an HDD is compared to determine an insufficient module, and the module ID of the insufficient module is stored in a predetermined storage area such as a RAM. Further, these module IDs are read from a predetermined storage area, and the DDB of the read module ID is acquired from the digital broadcast wave. In addition, the processing method in the lack module acquisition part can have various methods other than the above processing methods.

  (Third Embodiment: Process Flow) FIG. 21 exemplifies a flowchart showing a process flow in the module management apparatus according to the present embodiment.

  First, a digital broadcast wave is received. This process is mainly executed by the digital broadcast receiver (step S2101). Next, a data broadcast module included in the digital broadcast wave received in step S2101 is acquired. This process is mainly executed by the module acquisition unit (step S2102). Next, a service ID is acquired as service identification information of the service providing the module acquired in step S2102 from the digital broadcast wave received in step S2101. This process is mainly executed by the service ID acquisition unit (step S2103). Next, the module acquired in step S2102 and the service ID acquired in step S2103 are stored in association with each other. This process is mainly executed by the holding unit (step S2104). Next, module update information is acquired from the digital broadcast wave received in step S2101. This process is mainly executed by the missing module acquisition unit (step S2105). Finally, it is insufficient based on the module update information acquired in step S2105 and the existing module identification information for identifying the module held in step S2104 in association with the service identification information of the service for which the module update information was acquired. Acquires the missing module that is the module to be executed. This process is mainly executed by the missing module acquisition unit (step S2106).

  (Embodiment 3: Effect) In the module management apparatus according to the present embodiment, not all modules transmitted by digital broadcast waves for acquiring data broadcast display output or the like are acquired, but only missing modules are acquired. Is possible. Therefore, the time until the data broadcast is displayed and output is shortened, and the user who views the data broadcast can view the data broadcast without stress.

Functional block diagram of the module management apparatus according to the first embodiment Example of general computer configuration Diagram explaining data carousel transmission system Diagram showing the structure of DII Diagram showing the structure of DDB Diagram showing the relationship between modules, blocks, and TS Schematic diagram showing digital broadcast wave reception processing Example of module Diagram showing the relationship between broadcast networks, transmission channels, and organization channels Example of configuration of holding unit FIG. 3 is a flowchart showing a processing flow of the module management apparatus according to the first embodiment. Functional block diagram of the module management apparatus according to the second embodiment An example figure of composition of a holding part concerning Embodiment 2 FIG. 9 is a flowchart showing a processing flow of the module management apparatus according to the second embodiment. Functional block diagram of the module management apparatus according to the third embodiment The figure which shows the structure of the DSM-CC message header of DII The figure explaining the case where the module managed by DII is updated The figure explaining the case where the module managed by DII increases An example figure of composition of a holding part concerning Embodiment 3. Example of processing in the missing module acquisition unit FIG. 9 is a flowchart showing a processing flow of the module management apparatus according to the third embodiment.

Explanation of symbols

0100 Module management device 0101 Digital broadcast reception unit 0102 Module acquisition unit 0103 Service identification information acquisition unit 0104 Holding unit

Claims (7)

A digital broadcast receiver;
A module acquisition unit for acquiring a module for data broadcasting from the digital broadcast reception unit;
A service identification information acquisition unit for acquiring service identification information for identifying the service that acquired the module from the digital broadcast reception unit;
A holding unit that holds the module and service identification information in association with each other;
A module management device.   The module management apparatus according to claim 1, wherein the service identification information acquisition unit includes a service ID acquisition unit that acquires a service ID as service identification information.   Insufficient in the holding unit based on the module update information acquired from the digital broadcast receiving unit and the existing module identification information for identifying the module held in the holding unit in association with the service identification information of the service that acquired the module update information The module management apparatus according to claim 1, further comprising a deficient module acquisition unit that acquires deficient modules that are modules to be executed.   The module management apparatus according to claim 3, wherein the module update information is a transaction ID included in a DII (Download Information Indicator). A digital broadcast receiving step;
A module acquisition step of acquiring a module for data broadcast from the digital broadcast wave received in the digital broadcast reception step;
Service identification information acquisition step for acquiring service identification information for identifying the service that acquired the module from the digital broadcast wave received in the digital broadcast reception step;
A holding step for holding the module and service identification information in association with each other;
A method of operating a module management apparatus having   6. The operation method of the module management apparatus according to claim 5, wherein the service identification information acquisition step includes a service ID acquisition substep of acquiring a service ID as service identification information.   Module update information acquired from the digital broadcast wave received in the digital broadcast reception step, existing module identification information for identifying the module held in the holding step in association with the service identification information of the service that acquired the module update information, The operation method of the module management apparatus according to claim 5, further comprising a deficient module acquisition step of acquiring a deficient module that is a deficient module based on the step.

Images