JP4149502B2 - Program replacement method and program replacement device - Google Patents

Description

  The present invention relates to an update method for downloading a program and replacing an existing program. In particular, in digital television, it relates to executing a program that has been downloaded by temporarily replacing an existing program.

  The function of downloading and updating a program in a conventional digital television is described in Patent Document 1 and Patent Document 2.

FIG. 43 is a configuration diagram of a digital cable television system that downloads and executes a conventional program, and includes a head end 4110 and two terminal devices 4120 and 4130. The head end 4110 stores three programs A 4111, B 4112, and C 4113, and supplies them to the terminal devices 4120 and 4130. The terminal device 4120 includes three programs A4121, B4122, and C4123 stored in advance, and a processor 4124 that executes these programs. Similarly, the terminal device 4130 also includes three programs A4131, B413, and C4133 that are stored in advance, and a processor 4134 that executes these programs. When a new program is transmitted from the head end 4110, the terminal devices 4120 and 4130 replace and store the existing program, and thereafter execute the updated program. For example, when a new program A 4111 is sent from the head end 4110 to the terminal devices 4120 and 4130, the terminal devices 4120 and 4130 replace the programs A 4121 and 4131 with the program A 4111. Thereafter, the processors 4124 and 4134 execute the updated program A4111 instead of the programs A4121 and 4131. Thus, by updating the program stored in the terminal device, it is possible to update the function of the terminal device and add a new function.
Japanese Patent Laid-Open No. 10-326192 JP 2003-122578 A

  However, in the prior art, since an existing program is updated, it is not possible to easily return to the program before the update. If you want to provide a specific function for a limited time or time, you need to download the program from the headend again and restore it. In general, downloading takes time and other functions of the terminal device cannot be used. Therefore, when the number of downloads increases, there is a problem that the user cannot use the terminal device.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a program replacement method that makes it possible to update a program in a broadcast receiving terminal device and at the same time easily return an existing program.

In order to achieve the above object, the present invention provides a message to / from the POD when a message is transmitted / received between a POD detachably attached to the broadcast receiving terminal device and a program in the broadcast receiving terminal device. The broadcast receiving terminal device operates so as to replace the program in the broadcast receiving terminal device registered so as to be able to transmit / receive the first information, and has a first identifier having an identifier for specifying the type of the program Registering the first program so that the program can send and receive messages to and from the POD; and after registering the first program, an identifier having the same content as the identifier of the registered first program the have already present in the broadcast receiving terminal in the apparatus, to register to allow transmission and reception of messages with the POD Step for the second program, to stop the the step of notifying that the second program stops the transmission and reception of messages with the POD, the sending and receiving of messages between the the second program the notification POD was And stopping transmission / reception of messages between the notified second program and the POD means that the second program that has been registered so as to be able to transmit / receive messages to / from the POD is not registered. It is characterized by that.

Name your, and POD, for example, a card that performs the descrambling called CableCard (TM).

  Note that stopping message transmission / reception between the second program and the POD means, for example, deregistration of the second program that has been registered so that message transmission / reception with the POD is possible. It is. The first program may be sent as part of a broadcast wave.

  In addition, the second program that has received the notification that the transmission / reception of the message with the POD is to be stopped is the non-registration of the second program that has been registered so that the transmission / reception of the message with the POD can be performed. It is also possible to execute processing necessary for the purpose. Thereby, the second program can execute post-processing after the update and the like.

  The present invention can be realized not only as such a program replacement method, but also as a program replacement device in which each step is implemented with a circuit or the like, or as a program for causing a computer to execute each step. It can be realized as a computer-readable recording medium on which the program is recorded.

  According to the present invention, instead of deleting an existing program, a temporarily downloaded program is executed instead, so that the program can be updated and at the same time the existing program can be easily returned. . Also, by downloading and saving a program so that it can be executed simultaneously with the existing program, it is possible to add a function that does not exist in the existing program.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

(Embodiment 1)
First, Embodiment 1 of the cable television system according to the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the relationship between the devices constituting the cable system, and includes a head end 101, three terminal devices A111, a terminal device B112, and a terminal device C113. In this embodiment, three terminal devices are coupled to one head end. However, the present invention can be implemented even if an arbitrary number of terminal devices are coupled to the head end.

  The head end 101 transmits broadcast signals such as video / audio / data to a plurality of terminal devices and receives data transmission from the terminal devices. In order to realize this, the frequency band used for transmission between the head end 101 and the terminal device A111, the terminal device B112, and the terminal device C113 is divided and used. FIG. 2 is a table showing an example of frequency band division. Frequency bands are roughly classified into two types, Out Of Band (abbreviated as OOB) and In-Band. 5 to 130 MHz is allocated to the OOB, and is mainly used for data exchange between the head end 101 and the terminal device A111, the terminal device B112, and the terminal device C113. 130 MHz to 864 MHz is assigned to In-Band and is mainly used for broadcast channels including video and audio. QPSK modulation is used for OOB, and QAM64 modulation is used for In-Band. The modulation technique is a well-known technique that is not very related to the present invention, and thus detailed description thereof is omitted. FIG. 3 is an example of a more detailed use of the OOB frequency band. 70 MHz to 74 MHz are used for data transmission from the head end 101, and all the terminal devices A111, B112, and C113 receive the same data from the headend 101. On the other hand, 10.0 MHz to 10.1 MHz is used for data transmission from the terminal device A 111 to the head end 101, and 10.1 MHz to 10.2 MHz is used for data transmission from the terminal device B 112 to the head end 101. 2 MHz to 10.3 MHz is used for data transmission from the terminal device C 113 to the head end 101. Thereby, data specific to each terminal device can be transmitted from each terminal device A111, terminal device B112, and terminal device C113 to the head end 101. FIG. 4 is an example of use for the In-Band frequency band. 150-156 MHz and 156-162 MHz are assigned to TV channel 1 and TV channel 2, respectively, and thereafter, TV channels are assigned at intervals of 6 MHz. After 310 MHz, radio channels are allocated in 1 MHz units. Each of these channels may be used as an analog broadcast or a digital broadcast. In the case of digital broadcasting, the data is transmitted in the MOEG2 transport packet format based on the MPEG2 specification, and various data broadcasting data can be transmitted in addition to audio and video.

  The head end 101 includes a QPSK modulation unit, a QAM modulation unit, and the like in order to transmit appropriate broadcast signals in these frequency bands. Moreover, in order to receive the data from a terminal device, it has a QPSK demodulator. The head end 101 is considered to have various devices related to the modulation unit and the demodulation unit. However, since the present invention mainly relates to the terminal device, detailed description thereof is omitted.

  The terminal device A111, the terminal device B112, and the terminal device C113 receive and reproduce the broadcast signal from the head end 101. In addition, data specific to each terminal device is transmitted to the head end 101. The three terminal devices have the same configuration in this embodiment.

  FIG. 5 is a block diagram illustrating a hardware configuration of the terminal device. Reference numeral 500 denotes a terminal device, which includes a QAM demodulation unit 501, a QPSK demodulation unit 502, a QPSK modulation unit 503, a TS decoder 505, an audio decoder 506, a speaker 507, a video decoder 508, a display 509, a secondary storage unit 510, and a primary storage unit. 511, a ROM 512, an input unit 513, and a CPU 514. Further, the POD 504 can be attached to and detached from the terminal device 500.

FIG. 6 is a thin television that is an example of the appearance of the terminal device 500.
Reference numeral 601 denotes a casing of a flat-screen television, which incorporates all the components of the terminal device 500 except for the POD 504.

Reference numeral 602 denotes a display, which corresponds to the display 509 in FIG.
Reference numeral 603 denotes a front panel unit composed of a plurality of buttons, which corresponds to the input unit 513 in FIG.

  Reference numeral 604 denotes a signal input terminal for connecting a cable line in order to transmit / receive a signal to / from the head end 101. The signal input terminal is connected to the QAM demodulator 501, QPSK demodulator 502, and QPSK modulator 503 of FIG.

  Reference numeral 605 denotes a POD card corresponding to the POD 504 in FIG. The POD 504 takes a form independent of the terminal device 500 and can be attached to and detached from the terminal device 500, like the POD card 605 in FIG. Details of the POD 504 will be described later.

Reference numeral 606 denotes an insertion slot into which the POD card 605 is inserted.
Referring to FIG. 5, QAM demodulating section 501 demodulates a signal that has been QAM modulated and transmitted by head end 101 with tuning information including a frequency designated by CPU 514, and delivers the signal to POD 504.

  The QPSK demodulator 502 demodulates a signal transmitted by QPSK modulation at the head end 101 with tuning information including a frequency designated by the CPU 514, and passes it to the POD 504.

  The QPSK modulation unit 503 performs QPSK demodulation on the signal passed from the POD 504 with demodulation information including the frequency designated by the CPU 514, and transmits it to the head end 101.

  The POD 504 is configured to be detachable from the terminal device body 500 as shown in FIG. An example of the POD 504 is a card that performs descrambling or the like called CableCard (TM). The connection interface between the terminal main body 500 and the POD 504 is defined by the OpenCable (TM) HOST-POD Interface Specification (OC-SP-HOSTOPOD-IF-I12-030210) and the specifications referenced from this specification. Here, the details are omitted, and only the part related to the present invention will be described.

  FIG. 7 is a block diagram showing the internal configuration of the POD 504. The POD 504 includes a first descrambler unit 701, a second descrambler unit 702, a scrambler unit 703, a first storage unit 704, a second storage unit 705, and a CPU 706.

  The first descrambler unit 701 receives an encrypted signal from the QAM demodulator 501 of the terminal device 500 according to an instruction from the CPU 706 and performs decryption. Then, the decoded signal is sent to the TS decoder 505 of the terminal device 500. Information such as a key necessary for decoding is appropriately given from the CPU 706. Specifically, the head end 101 broadcasts several pay channels. When the user purchases the paid channel, the first descrambler unit 701 receives necessary information such as a key from the CPU 706 and descrambles it, so that the user can view the paid channel. If necessary information such as a key is not given, the first descrambler unit 701 sends the received signal to the TS decoder 505 without performing descrambling.

  The second descrambler unit 702 receives the encrypted signal from the QPSK demodulator 502 of the terminal device 500 according to an instruction from the CPU 706 and performs decryption. Then, the decrypted data is delivered to the CPU 706.

  The scrambler unit 703 encrypts data received from the CPU 706 according to an instruction from the CPU 706 and sends the data to the QPSK modulation unit 503 of the terminal device 500.

  Specifically, the first storage unit 704 includes a primary storage memory such as a RAM, and is used for temporarily storing data when the CPU 706 performs processing.

  Specifically, the second storage unit 705 is composed of a secondary storage memory such as a flash ROM, stores a program executed by the CPU 706, and is used for storing data that cannot be erased even when the power is turned off. Is done.

  The CPU 706 executes a program stored in the second storage unit 705. The program is composed of a plurality of subprograms. FIG. 8 is an example of a program stored in the second storage unit 705. In FIG. 8, a program 800 is composed of a plurality of subprograms such as a main program 801, an initialization subprogram 802, a network subprogram 803, a reproduction subprogram 804, and a PPV subprogram 805.

  Here, PPV is an abbreviation for Pay Per View, and is a service that enables a specific program such as a movie to be viewed for a fee. When the user inputs a personal identification number, the purchase is notified to the head end 101, the scramble is released, and viewing is possible. By this viewing, the user pays the purchase price at a later date.

  The main program 801 is a subprogram activated first by the CPU 706 when the power is turned on, and controls other subprograms.

  The initialization subprogram 802 is started by the main program 801 when the power is turned on, performs information exchange with the terminal device 500, and performs initialization processing. The details of the initialization process are defined in the OpenCable (TM) HOST-POD Interface Specification (OC-SP-HOSTODD-IF-I12-03210) and the specifications referenced from this specification. Also, initialization processing that is not defined in the specification is performed. Here are some of them. When the power is turned on, the initialization subprogram 802 notifies the QPSK demodulation unit 502 of the first frequency stored in the second storage unit 705 through the CPU 514 of the terminal device 500. The QPSK demodulator 502 performs tuning at the given first frequency and sends a signal to the second descrambler unit 702. In addition, the initialization subprogram 802 provides the second descrambler unit 702 with decryption information such as the first key stored in the second storage unit 705. As a result, the second descrambler unit 702 performs descrambling and delivers it to the CPU 706 that executes the initialization subprogram 802. Therefore, the initialization subprogram 802 can receive information. In this embodiment, the initialization subprogram 802 receives information through the network subprogram 803. Details will be described later.

  In addition, the initialization subprogram 802 notifies the QPSK modulation unit 503 of the second frequency stored in the second storage unit 705 through the CPU 514 of the terminal device 500. The initialization subprogram 802 gives the encrypted information stored in the second storage unit 705 to the scrambler unit 703. When the initialization subprogram 802 gives information to be transmitted to the scrambler unit 703 via the network subprogram 803, the scrambler unit 703 encrypts data using the given encryption information, and the terminal device 500 is supplied to the QPSK modulator 503. The QPSK modulation unit 503 modulates the given encrypted information and transmits it to the head end 101.

  As a result, the initialization subprogram 802 can perform bidirectional communication with the head end 101 through the terminal device 500, the second descrambler unit 702, the scrambler unit 703, and the network subprogram 803.

  The network subprogram 803 is a subprogram for performing bidirectional communication with the head end 101, which is used from a plurality of subprograms such as the main program 801 and the initialization subprogram 802. Specifically, it behaves as if bidirectional communication with the headend 101 is performed by TCP / IP with respect to other subprograms using the network subprogram 803. TCP / IP is a known technique that defines a protocol for exchanging information between a plurality of devices, and detailed description thereof is omitted. When the network subprogram 803 is activated by the initialization subprogram 802 when the power is turned on, a MAC address (abbreviation for Media Access Control address) that is an identifier for identifying the POD 504 stored in the second storage unit 705 in advance is set. The head end 101 is notified through the terminal device 500 to request acquisition of the IP address. The head end 101 notifies the POD 504 of the IP address via the terminal device 500, and the network subprogram 803 stores the IP address in the first storage unit 704. Thereafter, the head end 101 and the POD 504 communicate using this IP address as the identifier of the POD 504.

  The playback subprogram 804 provides the first descrambler unit 701 with the decryption information such as the second key stored in the second storage unit 705 and the decryption information such as the third key provided from the terminal device 500. Enable scrambling. In addition, the network subprogram 803 receives information that the signal input to the first descrambler unit 701 is a PPV channel. When the PPV channel is found, the PPV subprogram 805 is activated.

  When the PPV subprogram 805 is activated, it displays a message prompting the user to purchase a program on the terminal device 500 and receives user input. Specifically, when information to be displayed on the screen is sent to the CPU 514 of the terminal device 500, a program that operates on the CPU 514 of the terminal device 500 displays a message on the display 509 of the terminal device 500. When the user inputs the personal identification number through the input unit 513 of the terminal device 500, the CPU 514 of the terminal device 500 receives the notification and notifies the PPV subprogram 805 operating on the CPU 706 of the POD 504. The PPV subprogram 805 transmits the received personal identification number to the head end 101 through the network subprogram 803. If the personal identification number is correct, the head end 101 notifies the PPV subprogram 805 of the decryption information such as the fourth key necessary for decryption via the network subprogram 803. The PPV subprogram 805 gives the received decryption information such as the fourth key to the first descrambler unit 701, and the first descrambler unit 701 descrambles the input signal.

  Referring to FIG. 5, TS decoder 505 performs filtering of the signal received from POD 504, and passes necessary data to audio decoder 506, video decoder 508, and CPU 514. Here, the signal coming from the POD 504 is an MPEG2 transport stream. Details of the MPEG2 transport stream are described in the MPEG standard document ISO / IEC13818-1, and the details are omitted in the present embodiment. The MPEG2 transport stream is composed of a plurality of fixed-length packets, and a packet ID is assigned to each packet. FIG. 9 is a configuration diagram of a packet. A packet 900 is composed of 188 bytes having a fixed length. The first 4 bytes are a header 901, which stores packet identification information, and the remaining 184 bytes are a payload 902, which contains information to be transmitted. Reference numeral 903 denotes a breakdown of the header 901. The packet ID is included in 13 bits from the 12th bit to the 24th bit from the top. FIG. 10 is a schematic diagram expressing a plurality of packets that are sent. The packet 1001 has a packet ID “1” in the header, and the payload contains the first information of the video A. The packet 1002 has a packet ID “2” in the header, and the payload contains the first information of the voice A. The packet 1003 has a packet ID “3” in the header, and the payload contains the first information of the voice B.

  The packet 1004 has a packet ID “1” in the header, and the payload contains the second information of the video A. This is a continuation of the packet 1001. Similarly, packets 1005, 1026, and 1027 also store subsequent data of other packets. In this way, continuous video and audio can be reproduced by concatenating the contents of packet payloads having the same packet ID.

  Referring to FIG. 10, when CPU 514 instructs packet decoder “1” and “video decoder 508” as an output destination to TS decoder 505, TS decoder 505 receives packet ID “1” from the MPEG2 transport stream received from POD 504. The packet is extracted and delivered to the video decoder 508. In FIG. 10, only video data is delivered to the video decoder 508. At the same time, when the CPU 514 indicates the packet ID “2” and “audio decoder 506” to the TS decoder 505, the TS decoder 505 extracts the packet with the packet ID “2” from the MPEG2 transport stream received from the POD 504, and the audio decoder 506. To hand over. In FIG. 10, only audio data is delivered to the video decoder 508.

  The process of extracting only necessary packets according to the packet ID is filtering performed by the TS decoder 505. The TS decoder 505 can simultaneously execute a plurality of filtering instructions from the CPU 514.

  Referring to FIG. 5, audio decoder 506 concatenates audio data embedded in the MPEG2 transport stream packet provided from TS decoder 505, performs digital-analog conversion, and outputs the result to speaker 507.

The speaker 507 outputs the signal given from the audio decoder 506 as sound.
The video decoder 508 connects the video data embedded in the packet of the MPEG2 transport stream supplied from the TS decoder 505, performs digital-analog conversion, and outputs the result to the display 509.

  The display 509 is specifically composed of a cathode ray tube, liquid crystal, or the like, and outputs a video signal given from the video decoder 508 or displays a message instructed from the CPU 514.

  Specifically, the secondary storage unit 510 is configured by a flash memory, a hard disk, or the like, and saves or deletes data or programs instructed from the CPU 514. The stored data and programs are referred to by the CPU 514. The stored data and programs continue to be stored even when the terminal device 500 is powered off.

  Specifically, the primary storage unit 511 is configured by a RAM or the like, and temporarily stores or deletes data and programs instructed from the CPU 514. The stored data and programs are referred to by the CPU 514. The stored data and programs are erased when the terminal device 500 is powered off.

  The ROM 512 is a non-rewritable memory device, and specifically includes a ROM, a CD-ROM, a DVD, and the like. The ROM 512 stores a program executed by the CPU 514.

  Specifically, the input unit 513 includes a front panel and a remote controller, and receives input from the user. FIG. 11 shows an example in which the input unit 513 is configured with a front panel. Reference numeral 1100 denotes a front panel, which corresponds to the front panel unit 603 in FIG. The front panel 1100 includes seven buttons, an up cursor button 1101, a down cursor button 1102, a left cursor button 1103, a right cursor button 1104, an OK button 1105, a cancel button 1106, and an EPG button 1107. When the user presses the button, the CPU 514 is notified of the identifier of the pressed button.

  The CPU 514 executes a program stored in the ROM 512. The QAM demodulating unit 501, the QPSK demodulating unit 502, the QPSK modulating unit 503, the POD 504, the TS decoder 505, the display 509, the secondary storage unit 510, the primary storage unit 511, and the ROM 512 are controlled in accordance with instructions of the program to be executed.

  FIG. 12 is an example of a configuration diagram of a program stored in the ROM 512 and executed by the CPU 514.

  The program 1200 includes a plurality of subprograms, and specifically includes an OS 1201, an EPG 1202, a Java (registered trademark) VM 1203, a service manager 1204, and a Java library 1205.

  The OS 1201 is a subprogram that is activated by the CPU 514 when the terminal device 500 is powered on. The OS 1201 is an abbreviation for an operating system, and Linux or the like is an example. The OS 1201 is a general term for known techniques including a kernel 1201a and a library 1201b that execute other subprograms in parallel, and detailed description thereof is omitted. In the present embodiment, the kernel 1201a of the OS 1201 executes the EPG 1202 and the Java VM 1203 as subprograms. Further, the library 1201b provides a plurality of functions for controlling the components held by the terminal device 500 for these subprograms.

  The tuning function is introduced as an example of the function. The tuning function receives tuning information including a frequency from another subprogram and passes it to the QAM demodulator 501. The QAM demodulator 501 can perform demodulation processing based on the given tuning information, and deliver the demodulated data to the POD 504. As a result, other subprograms can control the QAM demodulator through the library 1201b.

  The EPG 1202 includes a program display unit 1202a that displays a list of programs to the user and receives input from the user, and a playback unit 1102b that performs channel selection. Here, EPG is an abbreviation for Electric Program Guide. When the terminal device 500 is powered on, the EPG 1202 is activated by the kernel 1201a. In the activated EPG 1202, the program display unit 1202a waits for input from the user through the input unit 513 of the terminal device 500. Here, when the input unit 513 includes the front panel shown in FIG. 11, when the user presses the EPG button 1107 of the input unit 513, the identifier of the EPG button is notified to the CPU 514. The program display unit 1202a of the EPG 1202, which is a subprogram operating on the CPU 514, receives this identifier and displays program information on the display 509. FIGS. 13A and 13B are examples of the program guide displayed on the display 509. Referring to FIG. 13A, program information is displayed on the display 509 in a grid pattern. A column 1301 displays time information. A column 1302 displays a channel name “Channel 1” and a program broadcast in a time zone corresponding to the time in the column 1301. In “Channel 1”, the program “News 9” is broadcast from 9:00 to 10:30, and “Movie AAA” is broadcast from 10:30 to 12:00. Similarly to the column 1302, the column 1303 displays a channel name “channel 2” and a program that is broadcast in a time zone corresponding to the time in the column 1301. The program “Movie BBB” is broadcast from 9:00 to 11:00, and “News 11” is broadcast from 11:00 to 12:00. Reference numeral 1330 denotes a cursor. The cursor 1330 moves when the left cursor 1103 and the right cursor 1104 on the front panel 1100 are pressed. When the right cursor 1104 is pressed in the state of FIG. 13A, the cursor 1330 moves to the right, as shown in FIG. 13B. Further, when the left cursor 1103 is pressed in the state of FIG. 13B, the cursor 1330 moves to the left, as shown in FIG.

  When the OK button 1105 on the front panel 1100 is pressed in the state of FIG. 13A, the program display unit 1202a notifies the reproduction unit 1102b of the identifier of “channel 1”. When the OK button 1105 on the front panel 1100 is pressed in the state of FIG. 13 (2), the program display unit 1202a notifies the reproduction unit 1102b of the identifier of “channel 2”.

  Further, the program display unit 1202a periodically stores program information to be displayed in the primary storage unit 511 from the head end 101 through the POD 504. In general, it takes time to acquire program information from the head end. When the EPG button 1107 of the input unit 513 is pressed, by displaying the program information stored in the primary storage unit 511 in advance, the program guide can be displayed quickly.

  The playback unit 1102b plays back a channel using the received channel identifier. The relationship between the channel identifier and the channel is stored in advance in the secondary storage unit 510 as channel information. FIG. 14 is an example of channel information stored in the secondary storage unit 510. Channel information is stored in tabular form. A column 1401 describes channel identifiers. A column 1402 is a channel name. A column 1403 is tuning information. Here, the tuning information includes a frequency, a transfer rate, a coding rate, and the like, and is a value given to the QAM demodulator 501. A column 1404 is a program number. The program number is a number for identifying a PMT defined in the MPEG2 standard. The PMT will be described later. Each row of the rows 1411 to 1414 is a set of an identifier, a channel name, and tuning information of each channel. The row 1411 is a set including an identifier “1”, a channel name “channel 1”, tuning information having a frequency “312 MHz”, and a program number “101”. The playback unit 1102b delivers the received channel identifier to the service manager as it is to play back the channel.

  When the user presses the upper cursor 1101 and the lower cursor 1102 on the front panel 1100 during playback, the playback unit 1102b receives the pressed notification from the input unit 513 through the CPU 514 and changes the channel being played back. . First, the playback unit 1102b stores the identifier of the channel currently being played back in the primary storage unit 511. 15 (1), (2), and (3) are examples of channel identifiers stored in the primary storage unit 511. FIG. In FIG. 15 (1), the identifier “3” is stored, and referring to FIG. 14, it is indicated that the channel with the channel name “TV 3” is being reproduced. When the user presses the up cursor 1101 in the state of FIG. 15A, the playback unit 1102b refers to the channel information of FIG. 14 and plays back the channel with the channel name “channel 2” which is the previous channel in the table. In order to switch, the identifier “2” of the channel name “channel 2” is delivered to the service manager. At the same time, the channel identifier “2” stored in the primary storage unit 511 is rewritten. FIG. 15 (2) shows a state in which the channel identifier has been rewritten. In addition, when the user presses the down cursor 1102 in the state of FIG. 15A, the playback unit 1102 b refers to the channel information of FIG. 14 and sets the channel of the next channel in the table with the channel name “TV Japan”. In order to switch playback, the identifier “4” of the channel name “TV Japan” is delivered to the service manager. At the same time, the channel identifier “4” stored in the primary storage unit 511 is rewritten. FIG. 15 (3) shows a state in which the channel identifier has been rewritten.

  The Java VM 1203 is a Java virtual machine that sequentially analyzes and executes a program written in the Java (TM) language. Programs written in the Java language are compiled into intermediate codes called bytecodes that do not depend on hardware. The Java virtual machine is an interpreter that executes this bytecode. Some Java virtual machines also translate the bytecode into an execution format that can be understood by the CPU 514, and then deliver it to the CPU 514 for execution. The Java VM 1203 is activated by specifying a Java program to be executed by the kernel 1201a. In the present embodiment, the kernel 1201a designates the service manager 1204 as a Java program to be executed. Details of the Java language are described in many books such as the book “Java Language Specification (ISBN 0-201-63451-1)”. The details are omitted here. The detailed operation of JavaVM itself is described in many books such as “Java Virtual Machine Specification (ISBN 0-201-6451-X)”. The details are omitted here.

  The service manager 1204 is a Java program written in the Java language, and is sequentially executed by the Java VM 1203. The service manager 1204 can call or be called by other subprograms not described in the Java language through JNI (Java Native Interface). JNI is also described in many books such as the book “Java Native Interface”. The details are omitted here.

  The service manager 1204 receives the channel identifier from the playback unit 1102b through JNI.

  First, the service manager 1204 hands over the channel identifier to the Tuner 1205c in the Java library 1205 and requests tuning. The tuner 1205c refers to the channel information stored in the secondary storage unit 510 and acquires tuning information. Now, when the service manager 1204 hands over the channel identifier “2” to the Tuner 1205c, the Tuner 1205c refers to the column 1412 in FIG. 14 and acquires the corresponding tuning information “156 MHz,”. The Tuner 1205c delivers tuning information to the QAM demodulator 501 through the library 1201b of the OS 1201. The QAM demodulator 501 demodulates the signal transmitted from the head end 101 according to the given tuning information, and delivers it to the POD 504.

  Next, the service manager 1204 requests the CA 1205d in the Java library 1205 for descrambling. The CA 1205d gives information necessary for decoding to the POD 504 through the library 1201b of the OS 1201. The POD 504 decodes the signal given from the QAM demodulator 501 based on the given information and delivers it to the TS decoder 505.

  Next, the service manager 1204 gives a channel identifier to the JMF 1205a in the Java library 1205, and requests video / audio reproduction.

  First, the JMF 1205a first acquires a packet ID for specifying video and audio to be reproduced from the PAT and PMT. PAT and PMT are tables defined in the MPEG2 standard and representing the program structure in the MPEG2 transport stream, which are embedded in the payload of packets included in the MPEG2 transport stream and transmitted together with audio and video. It is. For details, refer to the specifications. Here, only an outline will be described. PAT is an abbreviation of Program Association Table, and is stored in a packet with a packet ID “0” and transmitted. The JMF 1205a designates the packet ID “0” and the CPU 514 to the TS decoder 505 through the library 1201b of the OS 1201 in order to obtain the PAT. The TS decoder 505 performs filtering with the packet ID “0” and passes it to the CPU 514, whereby the JMF 1205a collects the PAT packets. FIG. 16 is a table schematically illustrating an example of collected PAT information. A column 1601 is a program number. A column 1602 is a packet ID. The packet ID in column 1602 is used to obtain the PMT. Rows 1611 to 1613 are a set of channel program numbers and corresponding packet IDs. Here, three channels are defined. A row 1611 defines a set of a program number “101” and a packet ID “501”. Now, assuming that the identifier of the channel given to the JMF 1205a is “2”, the JMF 1205a refers to the column 1412 in FIG. 14 and obtains the corresponding program number “102”, and then the PAT column in FIG. Referring to 1612, the packet ID “502” corresponding to the program number “102” is acquired. PMT is an abbreviation of Program Map Table, and is stored and transmitted in a packet with a packet ID defined by PAT. The JMF 1205a designates the packet ID and the CPU 514 to the TS decoder 505 through the library 1201b of the OS 1201 in order to acquire the PMT. Here, the designated packet ID is “502”. The TS decoder 505 performs filtering with the packet ID “502” and passes it to the CPU 514, whereby the JMF 1205a collects the PMT packets. FIG. 17 is a table schematically illustrating an example of collected PMT information. A column 1701 is a stream type. A column 1702 is a packet ID. In the packet with the packet ID specified in the column 1702, information specified by the stream type is stored in the payload and transmitted. A column 1703 is supplementary information. Columns 1711 to 1714 are combinations of packet IDs and types of information being transmitted, which are called elementary streams. A column 1711 is a set of a stream type “voice” and a packet ID “5011”, and represents that voice is stored in the payload of the packet ID “5011”. The JMF 1205a acquires video and audio packet IDs to be reproduced from the PMT. Referring to FIG. 17, JMF 1205 a obtains audio packet ID “5011” from row 1711 and video packet ID “5012” from row 1712.

Next, the JMF 1205a provides the TS decoder 505 with a set of the acquired audio packet ID and output destination as the audio decoder 506 and the video packet ID and output destination as the video decoder 508 through the library 1201b of the OS 1201. The TS decoder 505 performs filtering based on the given packet ID and output destination. Here, the packet with the packet ID “5011” is delivered to the audio decoder 506, and the packet with the packet ID “5012” is delivered to the video decoder 508. The audio decoder 506 performs digital-analog conversion of a given packet and reproduces sound through the speaker 507. The video decoder 508 performs digital-analog conversion of the given packet and displays an image on the display 509.

  Finally, the service manager 1204 gives a channel identifier to the AM 1205b in the Java library 1205 and requests data broadcast reproduction. Here, the data broadcast reproduction means that a Java program included in the MPEG2 transport stream is extracted and executed by the JavaVM 1203. As a method for embedding a Java program in an MPEG2 transport stream, a method called DSMCC described in the MPEG standard document ISO / IEC13818-6 is used. Here, detailed description of DSMCC is omitted. The DSMCC method defines a method for encoding a file system composed of directories and files used in a computer in a packet of an MPEG2 transport stream. Information on the Java program to be executed is embedded in a packet of the MPEG2 transport stream in a format called AIT and transmitted. AIT is an abbreviation of Application Information Table defined in Chapter 10 of the DVB-MHP standard (formally, ETSI TS 101 812 DVB-MHP specification V1.0.2).

  First, the AM 1205b acquires the PAT and PMT in the same manner as the JMF 1205a in order to acquire the AIT, and acquires the packet ID of the packet in which the AIT is stored. Now, if the given channel identifier is “2” and the PAT of FIG. 16 and the PMT of FIG. 17 are transmitted, the PMT of FIG. 17 is obtained in the same procedure as the JMF 1205a. The AM 1205b extracts the packet ID from the elementary stream having the stream type “data” and the supplementary information “AIT” from the PMT. Referring to FIG. 17, the elementary stream in row 1713 corresponds to the packet ID “5013”.

  The AM 1205 b gives the AIT packet ID and the output destination CPU 514 to the TS decoder 505 through the library 1201 b of the OS 1201. The TS decoder 505 performs filtering with the given packet ID, and delivers it to the CPU 514. As a result, the AM 1205b can collect AIT packets. FIG. 18 is a table schematically showing an example of collected AIT information. A column 1801 is an identifier of the Java program. A column 1802 is Java program control information. The control information includes “autostart”, “present”, “kill”, etc. “autostart” means that the terminal device 500 automatically executes this program immediately, and “present” means that it is not automatically executed. “Kill” means to stop the program. A column 1803 is a DSMCC identifier for extracting a packet ID including a Java program in the DSMCC format. A column 1804 is a program name of the Java program. Columns 1811 and 1812 are information sets of Java programs. The Java program defined in the column 1811 is a set of an identifier “301”, control information “autostart”, a DSMCC identifier “1”, and a program name “a / TopXlet”. The Java program defined in the column 1812 is a set of an identifier “302”, control information “present”, a DSMCC identifier “1”, and a program name “b / GameXlet”. Here, the two Java programs have the same DSMCC identifier, which indicates that two Java programs are included in a file system encoded in one DSMCC format. Here, only four pieces of information are defined for the Java program, but more information is actually defined. For details, refer to the DVB-MHP standard.

  The AM 1205b finds the “autostart” Java program from the AIT, and extracts the corresponding DSMCC identifier and Java program name. Referring to FIG. 18, AM 1205b extracts the Java program in line 1811 and acquires the DSMCC identifier “1” and the Java program name “a / TopXlet”.

  Next, the AM 1205b obtains, from the PMT, the packet ID of the packet storing the Java program in the DSMCC format, using the DSMCC identifier obtained from the AIT. Specifically, the packet ID of the elementary stream in which the stream type is “data” in the PMT and the DSMCC identifier of the supplementary information matches is acquired.

  Now, assuming that the DSMCC identifier is “1” and the PMT is FIG. 17, the elementary stream in the row 1714 matches and the packet ID “5014” is extracted.

  The AM 1205b designates the CPU 514 as the packet ID and output destination of the packet in which data is embedded in the TS decoder 505 by the DSMCC method through the library 1201b of the OS 1201. Here, the packet ID “5014” is given. The TS decoder 505 performs filtering with the given packet ID, and delivers it to the CPU 514. As a result, the AM 1205b can collect necessary packets. The AM 1205b restores the file system from the collected packets according to the DSMCC method, and saves it in the primary storage unit 511. The extraction of data such as a file system from the packet in the MPEG2 transport stream and saving it in the storage means such as the primary storage unit 511 is hereinafter referred to as download.

  FIG. 19 is an example of a downloaded file system. In the figure, a circle represents a directory, a square represents a file, 1901 is a root directory, 1902 is a directory “a”, 1903 is a directory “b”, 1904 is a file “TopXlet.class”, and 1905 is a file “GameXlet.class”. is there.

  Next, the AM 1205 b delivers the Java program to be executed from the file system downloaded to the primary storage unit 511 to the Java VM 1203. If the name of the Java program to be executed is “a / TopXlet”, the file “a / TopXlet.class” with “.class” added to the end of the Java program name is the file to be executed. “/” Is a delimiter between directories and file names. With reference to FIG. 19, the file 1904 is a Java program to be executed. Next, the AM 1205b delivers the file 1904 to the Java VM 1203.

The Java VM 1203 executes the delivered Java program.
When the service manager 1204 receives an identifier of another channel, the service manager 1204 stops the execution of the video / audio and the Java program being played through each library included in the Java library 1205 through each library also included in the Java library 1205. Based on the newly received channel identifier, video / audio playback and Java program execution are performed.

  The Java library 1205 is a set of a plurality of Java libraries stored in the ROM 512. In the present embodiment, here, the Java library 1205 includes JMF 1205a, AM 1205b, Tuner 1205c, CA 1205d, POD Lib 1205e, and the like.

  Next, Java program download / save and execution functions, which are the main functions of the present invention, will be described.

The service manager 1204 performs bi-directional communication with the head end 101 through the POD Lib 1205e included in the Java library 1205. This two-way communication is
The D Lib 1205e is realized by using the QPSK demodulator 502 and the QPSK modulator 503 via the OS 1201 library 1201b and the POD 504.

  The service manager 1204 receives information on the Java program that the terminal device 500 should store in the secondary storage unit 510 from the headend 101 using this communication. This information is called XAIT information. XAIT information is transmitted between the head end 101 and the POD 504 in an arbitrary format. Regardless of the transmission format, the present invention can be implemented as long as the information necessary for XAIT is included.

  FIG. 20 is a table schematically showing an example of XAIT information acquired from the head end 101. A column 2001 is an identifier of the Java program. A column 2002 is Java program control information. The control information includes “autoselect” and “present”. “Autoselect” means that the terminal device 500 automatically executes this program when the power is turned on, and “present” means that it is not automatically executed. A column 2003 is a DSMCC identifier for extracting a packet ID including a Java program in the DSMCC format. A column 2004 is a program name of the Java program. Column 2005 is the priority of the Java program. Columns 2011 and 2012 are information sets of Java programs. The Java program defined in the column 2011 is a set of an identifier “701”, control information “autoselect”, a DSMCC identifier “1”, and a program name “a / PPV1Xlet”. Here, only five pieces of information are defined for the Java program, but the present invention can be implemented even if more information is defined.

  Upon receiving the XAIT information, the service manager 1204 stores the file system from the MPEG2 transport stream in the primary storage unit 511 in the same procedure as the procedure for downloading the Java program from the AIT information. Thereafter, the saved file system is copied to the secondary storage unit 510. It is also possible to download directly to the secondary storage unit 510 without going through the primary storage unit 511. Next, the service manager 1204 associates the storage location of the downloaded file system with the XAIT information and stores it in the secondary storage unit 510. FIG. 21 shows an example in which the secondary storage unit 510 stores the XAIT information and the downloaded file system in association with each other. In FIG. 21, elements with the same numbers as in FIG. 20 are the same as those in FIG. Column 2101 stores the storage location of the corresponding downloaded file system. In the figure, the storage position is indicated by an arrow. A downloaded file system 2110 includes a top directory 2111, a directory “a” 2112, a directory “b” 2113, a file “PPV1Xlet.class” 2114, and a file “PPV2Xlet.class” 2115.

  Here, the XAIT information is saved after the Java program is saved, but it is also possible to save the XAIT information before saving the Java program.

  After the terminal device 500 is powered on, the OS 1201 designates the service manager 1204 as the Java VM 1203, and after the Java VM 1203 activates the service manager 1204, the service manager 1204 first stores the XAIT information stored in the secondary storage unit 510. refer. Here, referring to the control information of each Java program, the “autoselect” program is transferred to the Java VM 1203 and started. Referring to FIG. 21, the Java program “PPV1Xlet” defined in line 2011 is activated.

  Here, the Java program “PPV1Xlet” is a program that displays PPV target program information corresponding to the PPV subprogram 805 that the POD 504 has. When the terminal device 500 does not have the Java program “PPV1Xlet”, when the PPV subprogram 805 sends information to be displayed on the screen to the CPU 514 of the terminal device 500, the dialog display program included in the library 1201b of the OS 1201 is shown in FIG. A message prompting the user to purchase a program as shown is displayed on the display 509. Reference numeral 2201 denotes a dialog box, which has display elements of a message 2202, a password number box 2203 for inputting a 4-digit password, an OK button 2204, and a cancel button 2205. However, in this display, since the program content is unknown, it is inconvenient because the user needs to check the program content by referring to a book such as a program guide.

  When the Java program “PPV1Xlet” is stored in the terminal device 500 and activated, the Java program “PPV1Xlet” registers itself as a Java program that can be referred to from the POD 504 in the POD Lib 1205e of the Java library 1205. At the time of registration, the identifier of the own Java program, the operation type, and the priority are also registered. The POD Lib 1205e stores the registered contents in the secondary storage unit 510. FIG. 23 shows an example of a state in which the secondary storage unit 510 stores information on a Java program that can be referenced from the registered POD 504. In this example, the table is stored in a table format, the column 2301 stores the identifier of the Java program, the column 2302 stores the operation type of the Java program, the column 2303 indicates the priority of the Java program, and the column 2304 stores the name of the Java program. Here, the operation type of the Java program has two values of “1” and “2” as shown in FIG. 24, and the value “1” indicates the Java program in which the registered Java program is registered elsewhere, This means that it cannot be executed simultaneously with the program included in the library 1201b of the OS 1201. The value “2” represents that the registered Java program can be executed simultaneously with other registered Java programs or programs included in the library 1201b of the OS 1201. Referring to FIG. 23, rows 2311 to 2312 represent registered Java programs. A row 2311 is a set of an identifier “PPV”, an operation type “2”, a priority “200”, and a Java program name “PPV1Xlet”.

  The POD Lib 1205e notifies the POD 504 of information on the registered Java program, and data can be transmitted and received between the sub program in the POD 504 and the registered Java program. For example, the PPV subprogram 805 in the POD 504 sends the program contents to be purchased for PPV to the registered Java program indicated by the row 2311 in FIG. 23, and the Java program displays on the display 509 as shown in FIG. be able to. Elements having the same numbers as those in FIG. 22 are the same as those in FIG. Reference numeral 2501 denotes program information displayed by the registered Java program. Here, the dialog display program of the library 1201b of the OS 1201 and the registered Java program are executed simultaneously. At this time, the POD 504 identifies the partner Java program to which the data is to be sent with reference to the registered Java program type.

  On the other hand, the dialog display program of the library 1201b of the OS 1201 and the registered Java program are developed separately, and as a result, 2201 and 2501 may overlap and be displayed. In order to avoid this, the dialog display program of the library 1201b of the OS 1201 can be stopped. Specifically, the Java program has all the functions such as input of a personal identification number to be performed by the dialog display program of the library 1201b of the OS 1201, and further registers with the operation type “1”. FIG. 26 shows an example in which the registered Java program in this case displays on the display 509 in response to an instruction from the PPV subprogram of the POD 504.

  Here, it is assumed that the registered Java program is stored in the secondary storage unit 510 as shown in FIG. In this example, the two Java programs have the same identifier “PPV”, and the operation type is “1” and cannot coexist. In such a case, the POD Lib 1205e operates only the Java program having a high priority. Alternatively, both are operated, but the message from the POD 504 is delivered only to the Java program having a high priority.

  28 and 29 are flowcharts summarizing the operation of the POD Lib 1205e when the Java program is registered in the POD Lib 1205e. The POD Lib 1205e accepts registration of the Java program (step S2801). The received information is stored in the secondary storage unit 510 (step S2802). The Java program already registered in the secondary storage unit 510 is compared with the identifiers of the accepted Java programs, and it is determined whether there are a plurality of Java programs with the same identifier (step S2803). If there is a Java program with the same identifier, the process proceeds to step S2901 in FIG. If there is no Java program with the same identifier, it is checked whether or not the operation type of the accepted Java program can be executed together (step S2804). If not possible, message delivery from the POD 504 to the library 1201b of the OS 1201 is stopped (step S2805). Thereafter, message delivery from the POD 504 to the accepted Java program is validated (step S2806), and the registration process is terminated. If there is a Java program with the same identifier in step S2803, it is checked whether all the operation types of the plurality of Java programs with the same identifier can be executed together (step S2901). If there is a Java program that cannot be executed together, the priority of the accepted Java program is compared with the priority of the existing Java program (step S2902). When the received Java program has the highest priority, message delivery from the POD 504 to the existing Java program is stopped (step S2903), and message delivery from the POD 504 to the received Java program is enabled (step S2904). . If it is determined in step S2901 that all Java program operation types can be executed together, the process advances to step S2904. If the priority of the accepted Java program is not the highest in step S2902, the existing Java program continues to receive messages, so the process is terminated without doing anything.

  30, FIG. 31, and FIG. 32 are schematic diagrams showing changes in the delivery destination of messages from the POD 504 based on the flowchart of this operation. FIG. 30 (1) shows a state in which the Java program is not registered, and all messages are delivered from the POD 504 to the library 1201b of the OS 1201. Arrow 3001 represents message delivery. When the Java program is registered in the state of FIG. 30 (1), when the registered Java program operation types are capable of coexistence, steps S2801, S2802, S2803, S2804, The process of S2806 is performed, and the state shown in FIG. Here, reference numeral 3011 is a registered Java program, and an arrow 3002 is a message flow from the newly set POD 504 to the Java program 3011. Strictly speaking, a CPU 514 and a POD Lib 1205e are interposed between the POD 504 and the Java program. If the registered Java program operation type cannot coexist, the processing of steps S2801, S2802, S2803, S2804, S2805, S2806 is performed with reference to the flowchart of FIG. 28, and the state of FIG. become. The message flow from the POD 504 represented by the arrow 3001 to the library 1201b is stopped, and message delivery from the new POD 504 to the Java program 3011 is set.

  FIG. 31 (1) shows a state in which one Java program is registered and all messages are delivered from the POD 504 to the registered Java program 3111 with the library 1201 b of the OS 1201. Arrows 3101 and 3102 represent message delivery. When a Java program is registered in the state of FIG. 31 (1), if the registered operation type of the Java program can coexist, operations S2801, S2802, and S2803 are referred to with reference to the flowcharts of FIGS. , S2901 and S2904 are performed, and the state shown in FIG. Here, 3112 is a registered Java program, and an arrow 3103 represents delivery of a message from the newly set POD 504 to the Java program 3112.

  FIG. 32 (1) shows a state in which one Java program is registered and all messages are delivered from the POD 504 to the registered Java program 3211. The Java program 3211 is in this state because the operation types cannot be co-executed. Arrow 3201 represents message delivery. When a Java program is registered in the state shown in FIG. 31 (1), the priority of the registered Java program 3211 and the registered Java program is compared if the registered Java program operation types can coexist. . When the priority of the registered Java program is high, the processes of steps S2801, S2802, S2803, S2901, S2902, S2903, and S2904 are performed with reference to the flowcharts of FIGS. It becomes a state. Message delivery from the POD 504 represented by the arrow 3201 to the Java program 3211 is stopped, and message delivery from the new POD 504 to the Java program 3212 is set. When the priority of the existing Java program 3211 is high, the processing of steps S2801, S2802, S2803, S2901, and S2902 is performed with reference to the flowcharts of FIGS. 28 and 29, and the state of FIG. 31 (3) is obtained. Message delivery remains the same.

  When the highest priority of the existing Java program is equal to the priority of the accepted Java program in step S2902, control may be copied to step S2903 so that the accepted Java program can receive the message. This means that if a plurality of Java programs have the same priority, an arbitrary one is selected and considered.

  Alternatively, a plurality of Java programs are executed and the same message is sent to the plurality of Java programs. In this case, it is assumed that a plurality of Java programs are intentionally given the same priority and identifier, and are implemented so that they understand each other's operation and cause no problems even if they operate simultaneously. FIG. 33 shows an example in which a plurality of Java programs have the same identifier and priority. Here, the contents and fee information are sent from the POD 504 to the program. The Java program on the line 3311 can accept the charge display and the input of the password, and the Java program on the line 3312 can only display the program contents.

  The POD Lib 1205e accepts registration of a Java program and also accepts deletion. 34 and 35 are flowcharts summarizing the operation of the POD Lib 1205e when the POD Lib 1205e deletes the registration of the Java program. The POD Lib 1205e accepts the deletion of the Java program (Step S3401). The Java program received from the secondary storage unit 510 is deleted (step S3402). It is checked whether the Java program to be deleted currently receives a message from the POD 504 (step S3403). If received, the message delivery from the POD 504 to the Java program received is invalidated (step S3404). It is checked whether there is a Java program with the same identifier in the secondary storage unit 510 (step S3405). If not, message delivery from the POD 504 to the library 1201b of the OS 1201 is validated (step S3406). If the Java program to be deleted does not receive a message from the POD 504 in step S3403, the process ends. If it is determined in step S3405 that there is a Java program having the same identifier as the Java program to be deleted, it is checked whether or not all Java programs can be executed together with reference to FIG. 35 (step S3501). The message delivery from the POD 504 to all the coexisting Java programs having the same identifier and the library 1201b of the OS 1201 is enabled (step S3502). If all the Java programs are not co-executed, the Java program having the highest priority is extracted (step S3503). The message delivery from the POD 504 to the extracted Java program is validated (step S3504).

  As described above, according to the present embodiment, it is possible to update a program by executing a temporarily downloaded program instead without deleting the existing program, and at the same time, the existing program can be easily performed. It is also possible to return to. Also, by downloading and saving a program so that it can be executed simultaneously with the existing program, it is possible to add a function that does not exist in the existing program.

  In this embodiment, the PPV subprogram 805 and the Java program in the POD 504 exchange messages and perform operations. However, not only the PPV but also any subprogram on the POD 504 and the terminal device 500 It can be adapted to exchange messages between any Java programs. Further, the Java program may be a mixture of a part written in Java and a part in a binary format that can be directly executed by the CPU, or may be implemented only if it is composed only of a binary form that can be directly executed by the CPU.

  In the present embodiment, it is possible to delete the ROM 512 by storing the content stored in the ROM 512 in the secondary storage unit 510. Further, the secondary storage unit 510 is configured by a plurality of sub-secondary storage units, and can be implemented even when individual sub-secondary storage units store different information. For example, one sub-secondary storage unit stores only tuning information, another sub-secondary storage unit stores the library 1201b of the OS 1201, and another sub-secondary storage unit stores the downloaded Java program. It is possible to divide in detail, such as.

(Embodiment 2)
In the first embodiment, when the Java program is registered, the Java program already registered in the library 1201b of the OS 1201 or the secondary storage unit 510 suddenly stops message communication with the POD 504. For example, if a Java program is registered in the middle of a PPV purchase process, the purchase process may be interrupted and the password entered halfway may become invalid.

  Therefore, in the present embodiment, notification is made in advance to the library 1201b of the OS 1201 and the existing Java program for which message communication is to be stopped, and it is stopped after obtaining approval. Specifically, the message delivery stop to the library 1201b in step S2805 in FIG. 28 and the message delivery stop to the existing Java program in step S2903 in FIG. Replace with the flowchart described in.

  Referring to FIG. 36, the POD Lib 1205e notifies in advance that the message transmission is stopped to the object whose message transmission is stopped, specifically, the Java program or the library 1201b of the OS 1201 (step S3601). Upon receiving the stop notification, the Java program or the library 1201b of the OS 1201 notifies the POD Lib 1205e that the message transmission has been stopped after completing the necessary processing (step S3602). The POD Lib 1205e stops the message transmission (step S3603).

  Also, the subprogram on the POD 504 needs to notify that the message notification destination is changed. FIG. 37 is a flowchart showing an operation in which the POD Lib 1205e notifies the POD 504 that the message notification destination is changed.

  The POD Lib 1205e notifies the POD 504 in advance that message transmission will be stopped (step S3701). Upon receiving the stop notification, the POD 504 completes the necessary processing, and then notifies the POD Lib 1205e that the message transmission has been stopped (step S3702). The POD Lib 1205e stops message transmission (step S3703) and sets a new delivery destination (step S3704). Finally, the POD Lib 1205e notifies the POD 504 that a new delivery destination has been set (step S3705).

  In addition, the Java program newly set as the delivery destination and the library 1201b of the OS 1201 may also receive notification of the setting. This is because the Java program or the library 1201b of the OS 1201 not only receives a message from the POD 504 but also sometimes sends a message to the POD 504. Specifically, a password entered by the user using PPV is sent to the POD 504. If it is possible to know that message transmission is enabled, it is not necessary to send a message in vain.

(Embodiment 3)
In the first embodiment, the registered Java program is stored in the secondary storage unit 510, but it is also possible to store it in the primary storage unit 511.

  When storing in the primary storage unit 511, all stored information is erased when the power is turned off. However, as described above, when a Java program is downloaded and executed based on XAIT, the executed Java program registers itself in the POD Lib 1205e and can be restored. However, in this case, since the library 1201b of the OS 1201 is operating for a while after the power is turned on, switching occurs. FIG. 38 is a flowchart showing an operation from when the terminal device 500 is powered on until message delivery from the POD 504 is changed. When the terminal device 500 is turned on (step S3801), the programs of the terminal device 500 and the POD 504 are activated, and message delivery is established between the POD 504 and the library 1201b (step S3802). The AM 1205b downloads the Java program based on the XAIT information, and the Java VM 1203 executes this Java program (step S3803). When the Java program needs to exchange a message with the POD 504, the Java program registers itself in the POD Lib 1205e (step S3804). The message delivery is changed as necessary based on the flowcharts defined in FIGS. 28 and 29 (step S3805).

  On the other hand, when the registered Java program is stored in the secondary storage unit 510 as in the first embodiment, after the power is turned on, the registered Java program is transferred from the POD 504 to the registered Java program instead of the library 1201b of the OS 1201. The message is delivered. However, as described above, when a Java program is downloaded and executed based on XAIT, the executed Java program registers itself in the POD Lib 1205e, so double registration is performed. To prevent this, the POD Lib 1205e does not accept registration of Java programs that have already been registered. FIG. 39 is a flowchart showing an operation from when the terminal device 500 is powered on until message delivery from the POD 504 is changed. When the terminal device 500 is turned on (step S3901), the programs of the terminal device 500 and the POD 504 are activated, and a message is sent between the POD 504 and the Java program or library 1201b based on the registration information stored in the secondary storage unit 510. Delivery is established (step S3902). The AM 1205b downloads the Java program based on the XAIT information, and the Java VM 1203 executes the Java program (step S3903). When the Java program needs to exchange a message with the POD 504, the Java program registers itself in the POD Lib 1205e (step S3904). The POD Lib 1205e refers to the secondary storage unit 510 and checks whether the same Java program has already been registered (step S3905). If not stored, registration processing is performed, and message delivery is changed as necessary based on the flowcharts defined in FIGS. 28 and 29 (step S3906).

The following application is possible through the first, second, and third embodiments.
The present invention is applicable to any information device such as a personal computer or a mobile phone.

  Although the POD 504 is detachable, it can be implemented even if it is built in. Note that when the CPU 706 is incorporated, the CPU 706 of the POD 504 can be removed and the CPU 514 can also perform the operation of the CPU 706.

  The Java program registered in the POD Lib 1205e can be implemented not only by a downloaded Java program but also by a pre-built Java program. Further, when a removable storage medium such as an SD memory card is attached / detached, a slot portion can be attached and a Java program can be taken in from the slot portion. It is also possible to attach a network unit connected to the network and take out the Java program from the Internet.

  Further, in the first to third embodiments, only one subprogram on the POD 504 delivers a message to the Java program, but two or more subprograms and the Java program each deliver a message individually. Can also be implemented. FIG. 40 shows an example of message delivery between a plurality of subprograms and a plurality of Java programs on the POD 504. In the POD 504, a sub program A 4001, a sub program B 4002, and a sub program C 4003 operate. On the terminal device 500, a Java program X 4011, a Java program Y 4012, and a Java program Z 4013 operate. Arrows 4021, 4022, 4023, and 4024 indicate the set message delivery paths. A message delivery path 4021 is set from the subprogram A 4001 to the Java program X4011, and the subprogram and the Java program are in a one-to-one relationship. On the other hand, the sub-program B 4002 has a message delivery path in two Java programs, a Java program Y 4012 and a Java program Z 4013. Conversely, the Java program Z4013 receives messages from two subprograms, a subprogram B4002 and a subprogram C4003.

  In this figure, the message is delivered from the subprogram to the Java program, but it is also possible to deliver the message from the Java program to the subprogram. It is also possible to exchange messages in both directions.

  Here, a message path ID may be assigned to the message delivery path, and the subprogram and the Java program may specify the message transmission partner using the message path ID. In addition, when registering a Java program, the present invention can be implemented by using this message path ID instead of the identifier of the Java program to be registered at the same time. A Java program for delivering a message can be identified based on an operation type or the like with respect to a message path of a competing Java program and a subprogram on the POD 504. Alternatively, by defining a subprogram identifier for identifying a subprogram on the POD 504 and registering a Java program, the present invention can be implemented even if this subprogram identifier is used instead of the identifier of the Java program to be registered at the same time. Is possible.

  In addition, the Java program for delivering the message has been determined using the action type, but the action type is not used, and the Java program registered last is given priority, or the Java program registered first is given priority. It may be determined based on rules prepared in advance.

  In the first to third embodiments, the operation of the Java program registered in the POD Lib 1205e means an operation performed upon receipt of message delivery. In other words, the Java program operates by receiving message delivery. On the other hand, Java programs can generally perform a plurality of processes in parallel. In the present invention, other processes included in the Java program other than the processes that operate by receiving message delivery can be implemented without any limitation.

  Further, as described in the above embodiment, the POD Lib 1205e accepts deletion (that is, unregistration) as well as registration of message delivery to the Java program that is the target of message delivery.

  FIG. 41 is a flowchart summarizing the operations of the POD Lib 1205e when a Java program is registered in the POD Lib 1205e.

  When the POD Lib 1205e receives registration of message delivery (including at least one of transmission / reception or both) with the Java program, the POD Lib 1205e sends necessary information (for example, information shown in FIG. 27) to the secondary storage unit 510. Save (Step SX101) and compare the identifier of the Java program whose registration was accepted in Step SX101 with the identifier of another Java program already registered in the secondary storage unit 510, thereby accepting the registration of the Java program It is determined whether or not there is a Java program having the same identifier as that in the secondary storage unit 510 (step SX102).

  As a result, when a Java program with the same identifier exists in the secondary storage unit 510 (that is, registration for accepting message delivery to another Java program having the same identifier as the Java program accepted for registration in step SX101 is the time at step SX101). (If done by POD Lib 1205e before) (Yes in Step SX102), POD Lib 1205e is a target for which message transmission is stopped, specifically, other Java registered in secondary storage unit 510. A program (that is, another Java program that has the same identifier as that of the Java program that received the message delivery registration in step SX101 and has been registered to accept the message delivery) or the library 1201b of the OS 1201 Is notified in advance that the message transmission is stopped (step SX103). The Java program or the library 1201b of the OS 1201 that has received the stop notification requires the necessary processing (necessary internal processing to be terminated before stopping delivery of the message from the POD 504 (that is, unregistering message delivery)) After completing the above, the POD Lib 1205e is notified of the termination of message transmission (step SX104). The POD Lib 1205e that has received the notification of consent is an existing Java program from the POD 504 (already registered in the secondary storage unit 510 and subject to suspension of message delivery from the POD 504) or the library 1201b of the OS 1201. Message delivery registration is deleted (that is, unregistered), and message delivery to the Java program is stopped (step SX105). Then, after notifying the Java program that has received registration in step SX101 that message delivery is to be started (step SX106), registration for accepting delivery of the message from the POD 504 to the Java program that has received registration in step SX101 is performed. By doing so, message delivery is validated (step SX107).

  On the other hand, if there is no Java program with the same identifier in the secondary storage unit 510 (No in step SX102), the POD Lib 1205e notifies the Java program that has accepted registration in step SX101 that it will start message delivery. (Step SX106) The message delivery is validated by performing registration for accepting delivery of the message from the POD 504 to the Java program whose registration has been accepted in Step SX101 (Step SX107).

  FIG. 42 is a flowchart summarizing the operation of the POD Lib 1205e when the POD Lib 1205e deletes the registration of the Java program (that is, the registration of message delivery with the Java program registered in the secondary storage unit 510 is not registered). is there.

  When the POD Lib 1205e accepts the deletion of the Java program (step SX201), the POD Lib 1205e notifies the Java program to be deleted in advance that the message delivery is stopped (step SX202). The Java program that has received the stop notification finishes the necessary processing (necessary internal processing to be terminated before stopping the message delivery from the POD 504 (that is, unregistering the message delivery registration)), The POD Lib 1205e is notified of the completion of message delivery stop (step SX203). The POD Lib 1205e that has received the notification of approval deletes the message delivery registration to the requested Java program of the Java programs registered in the secondary storage unit 510 (that is, unregisters). ) To stop message delivery from the POD 504 to the target Java program (step SX204). Then, the POD Lib 1205e validates message delivery with the library 1201b of the OS 1201 by performing registration for accepting delivery of the message with the POD 504 to the library 1201b of the OS 1201 (step SX205).

  Also, when there is another Java program registered in the secondary storage unit 510 in step SX205 or a newly registered Java program, and it is desired to deliver (or be able to deliver) a message to any one of these Java programs. Alternatively, message delivery between the POD 504 and the target Java program may be validated by performing registration for accepting message delivery between the POD 504 and the target Java program. Further, if the Java program to be delivered and the library 1201b of the OS 1201 can coexist with each other in the delivery of the message to the POD 504 (that is, they do not compete with each other), registration for accepting delivery of the message to the library 1201b of the OS 1201 is performed. The message may be delivered to the Java program and the library 1201b of the OS 1201.

  As described above, according to the present embodiment, the program can be updated (replaced) by executing the temporarily downloaded program instead without deleting the existing program. It is also possible to return the program easily.

  The program replacement method according to the present invention can be used as a broadcast receiving terminal device or the like, particularly as a broadcast receiving terminal device or the like having a detachable POD.

It is a block diagram of Embodiment 1 of the cable television system which concerns on this invention. An example of how to use the frequency band used for communication between the head end and the terminal device in the cable television system according to the present invention is shown. An example of how to use the frequency band used for communication between the head end and the terminal device in the cable television system according to the present invention is shown. An example of how to use the frequency band used for communication between the head end and the terminal device in the cable television system according to the present invention is shown. It is a block diagram of a terminal device in the cable television system according to the present invention. 1 shows an example of the appearance of a terminal device in a cable television system according to the present invention. It is a block diagram of the hardware constitution of POD which concerns on this invention. It is a block diagram of the program structure which POD which concerns on this invention preserve | saves. It is a block diagram of a packet defined in the MPEG standard. An example of an MPEG2 transport stream is shown. An example of the external appearance when the input unit is configured by a front panel is shown. It is a block diagram of the program structure which the terminal device concerning this invention preserve | saves. An example of the display of the display which concerns on this invention is shown. An example of the information which the secondary memory | storage part which concerns on this invention preserve | saves is shown. An example of the information which the primary storage part which concerns on this invention preserve | saves is shown. It is a schematic diagram showing the content of PAT prescribed | regulated by the MPEG2 specification which concerns on this invention. It is a schematic diagram showing the content of PMT prescribed | regulated by the MPEG2 specification which concerns on this invention. It is a schematic diagram showing the content of AIT prescribed | regulated by the DVB-MHP specification which concerns on this invention. It is a schematic diagram showing the file system transmitted by the DSMCC system based on this invention. It is a schematic diagram showing the content of XAIT which concerns on this invention. An example of the information which the secondary memory | storage part which concerns on this invention preserve | saves is shown. An example of the display of the display which concerns on this invention is shown. An example of the information which the secondary memory | storage part which concerns on this invention preserve | saves is shown. The table | surface which put together the operation | movement classification code of the Java program which concerns on this invention, and its meaning. An example of the display of the display which concerns on this invention is shown. An example of the display of the display which concerns on this invention is shown. An example of the information which the secondary memory | storage part which concerns on this invention preserve | saves is shown. 4 is a flowchart illustrating an operation when a POD Lib receives registration of a Java program in the first embodiment. 4 is a flowchart illustrating an operation when a POD Lib receives registration of a Java program in the first embodiment. It is a schematic diagram showing delivery of the message from POD. It is a schematic diagram showing delivery of the message from POD. It is a schematic diagram showing delivery of the message from POD. An example of the information which the secondary memory | storage part which concerns on this invention preserve | saves is shown. 5 is a flowchart illustrating an operation when a POD Lib accepts deletion of a Java program in the first embodiment. 5 is a flowchart illustrating an operation when a POD Lib accepts deletion of a Java program in the first embodiment. 4 is a flowchart showing a part of an operation when a POD Lib accepts registration of a Java program in the first embodiment. 4 is a flowchart showing a part of an operation when a POD Lib accepts registration of a Java program in the first embodiment. It is a flowchart showing operation | movement until a message delivery from POD is changed after a terminal device is turned on. It is a flowchart showing operation | movement until a message delivery from POD is changed after a terminal device is turned on. It is a figure showing an example of the message delivery path | route between the Java program on a terminal device, and the subprogram on POD. It is the flowchart which put together the operation | movement of POD Lib when a Java program is registered into POD Lib. 6 is a flowchart summarizing the operation of the POD Lib when the POD Lib deletes the registration of the Java program (that is, unregisters message delivery registration with the Java program registered in the secondary storage unit). It is a block diagram showing the structure of the conventional program replacement method.

Explanation of symbols

111 Terminal A
112 Terminal device B
113 Terminal device C
500 Terminal device 501 QAM demodulator 502 QPSK demodulator 503 QPSK modulator 504 POD
505 TS decoder 506 Audio decoder 507 Speaker 508 Video decoder 509 Display 510 Secondary storage unit 511 Primary storage unit 512 ROM
513 Input unit 514 CPU
603 Front panel unit 605 POD card 701 First descrambler unit 702 Second descrambler unit 703 Scrambler unit 704 First storage unit 705 Second storage unit 706 CPU
800 program 801 main program 802 initialization subprogram 803 network subprogram 804 playback subprogram 805 PPV subprogram 1102b playback unit 1200 program 1201 OS
1201a Kernel 1201b Library 1202 EPG
1202a Program display section 1203 JavaVM
1204 Service manager 1205 Library 1205a JMF
1205b AM
1205c Tuner
1205d CA
1205e POD Lib

Claims (3)

The broadcast reception registered so that the message can be transmitted / received to / from the POD when the message is transmitted / received between the POD detachably attached to the broadcast receiving terminal device and the program in the broadcast receiving terminal device. A method for operating the broadcast receiving terminal device to replace a program in the terminal device,
Registering the first program so that a first program having an identifier for identifying the type of program can send and receive messages to and from the POD;
After registering the first program, it has an identifier with the same content as the identifier of the registered first program, already exists in the broadcast receiving terminal device, and can send and receive messages with the POD. Informing the second program that has been registered to stop sending and receiving messages between the second program and the POD;
A step of stopping transmission and reception of messages between the notified second program and the POD,
Stopping message transmission / reception between the notified second program and the POD is to unregister the second program that has been registered so that message transmission / reception with the POD is possible. A program replacement method characterized by that.   The second program that has received notification that the transmission / reception of the message with the POD has been stopped is to unregister the second program that has been registered so that the transmission / reception of the message with the POD can be performed. The program replacement method according to claim 1, further comprising: performing processing necessary for the program. The broadcast reception registered so that the message can be transmitted / received to / from the POD when the message is transmitted / received between the POD detachably attached to the broadcast receiving terminal device and the program in the broadcast receiving terminal device. A device that replaces a program in a terminal device,
A registration unit for registering the first program so that a first program having an identifier for specifying the type of the program can send and receive messages to and from the POD;
After registering the first program, it has an identifier with the same content as the identifier of the registered first program, already exists in the broadcast receiving terminal device, and can send and receive messages with the POD. A notification unit that notifies the second program that has been registered to stop sending and receiving messages between the second program and the POD;
A stop unit that stops transmission and reception of messages between the notified second program and the POD;
Stopping transmission / reception of messages between the notified second program and the POD by the stop unit means that the second program that has been registered so as to be able to transmit / receive messages to / from the POD is not registered. program replacement device according to claim that it is possible to.

Images