The invention relates to a process for selection and starting an image, in other words a copy of an executable software, for example to process reception of a digital television program. It is particularly applicable in the field of digital television decoders.
Existing digital television decoders have resident software that is the image of an executable software, that is for example executed every time that the decoder is switched on. This image is used to process programs received by the decoder to transform the received digital signal into a video signal in the broad sense of the term, in other words into a signal containing an image, sounds, synchronization signals, and also possibly text and in general a set of information that can be transformed into meaningful signals for a user of a terminal station comprising the decoder. The resident software may be stored in a memory of the decoder. It may also be loaded into this memory from an information stream received by the decoder. The resident or loaded software can be executed, or the software can possibly be loaded from a received digital flow, due to the presence of the boot software and loading software. The boot software and the loading software comprise an initial set of instructions with a cross reference to a resident software start address. The loading software started by the boot software checks that the resident software is present and is uncorrupted. It contains instructions necessary to load an executable software if necessary, and to start it from the digital data stream received by the decoder if returned information signals that there is no image present in any of the decoder storage means. If it is confirmed that there is an uncorrupted image present, or after the image has been loaded from the digital data stream if necessary, the loading software loads the resident software into a memory area in which it can be executed, and then executes it. The resident software is executed to decode the received programs. The entire resident software including the boot software and the loading software are stored in a memory of the decoder. The boot and the loading software are stored in a non erasable part of memory or preferably have erase protection by software. The resident executable software is stored in an erasable part of memory. If the resident software is loaded from the digital data stream received by the decoder, the received software will overwrite the software that is already resident in the erasable memory area, if any, in which the said software will be stored. The loading software is also used to load a new image or to update a resident image from the digital data stream.
In the current state of the art, only one executable software image is stored. Regardless of whether it was previously loaded from the broadcast stream or was resident, this software is executed from the memory in which it was loaded to be executed.
According to this invention, it is intended to store several executable software images in the decoder. Therefore, the invention relates to a process as described below, starting from the boot and loading software provided with the decoder by the decoder manufacturer, to
Obviously, the process according to the invention can be used to load an executable from the data stream, in the same way as in prior art, if there is no image of the executable software available in a memory of the decoder of if the available image is corrupted or if it is a superseded version that needs to be replaced.
In summary, the invention relates to a process that can be used in a digital television reception set, for example in a digital television reception decoder to select and run an image of an executable software, the process including starting a self executable boot software to run an image, the process being characterized in that the boot software and the loading software include the following steps:
Preferably, a step v1) is carried out before step c) to check that the boot software table is present and is uncorrupted.
In general, before the process according to the invention is executed, the references table containing an integer number n of references will have been created, each reference in the table containing a univocal cross reference to one of n images stored in a memory area, the self executable boot software containing a cross reference to the said boot software table, and then according to a routine carried out every time that the decoder is switched on or reinitialized:
Preferably, the n images are distributed in two parts, a first part composed of an integer number (n−m) of images stored in erasable parts of memory and a second part complementary to the first part composed of an integer number of images m less than or equal to n stored in parts of non erasable memory or areas with erase protection.
In this case, in preference the select reference step s) and the check integrity step v2) are carried out firstly for the (n−m) images contained in memory areas without erase protection, then if none of these images is uncorrupted, for the m images contained in the memory areas that are non erasable or with erase protection.
Preferably, the m images stored in the memory areas that are non erasable or with erase protection are stored on different media, such that there is not more than one image with erase protection on each medium, for example an image on the hard disk and an image on a fast memory.
If the table is corrupted, or if none of the images found by reading the entire table and making the check v2) firstly of the (n−m) images stored in a memory area without erase protection are uncorrupted, then the selection step a) and the check step v2) are repeated, and possibly the loading step and then the run step l) are also repeated, for the m images stored in the memory area with erase protection, these m images being read in a predetermined order corresponding to an order of preference.
In the step prior to execution of the process to create the reference table, an integer number n of images is loaded into the decoder, preferably distributing them into (n−m) images stored in memory areas without erase protection and m images stored in memory areas with erase protection, with one image per storage medium.
According to one embodiment, the memory areas with erase protection in which the m images are stored are memory areas on a hard disk.
According to one embodiment, before one of the images is loaded for execution, it is checked that this image is not stored in a compressed mode, and if it is the image is decompressed before being loaded and executed.
An embodiment of the invention will now be explained with reference to the attached drawings in which:
An embodiment of this invention will now be described with reference to the attached drawings.
Firstly, the state of prior art will be summarized with reference to
A first part 1 that is non erasable or with erase protection located in a fast memory 10 of a decoder, for example a “flash” type memory as loaded according to prior art, contains a boot software and a loading software. This boot software and this loading software are known and are loaded by the decoder manufacturer.
Part 2 of the memory contains other information that is not concerned by this invention.
An erasable part or a part without erase protection 3 in memory 10 contains a resident image of an executable software.
Operation is as follows. The boot software is self executed when the decoder changes from an off state to a standby or on state, or following a reinitialization. Thus, for example when the decoder is started, the boot software outputs an instruction to run the loading software. This loading software checks that the executable software image stored in part 3 of the decoder memory is present and is uncorrupted. The software means to check this integrity are known in themselves. For example, it could be a checksum or a longitudinal redundancy code (LRC) check.
If the result of the check shows that there is a software image loaded in 3 and that this image loaded in 3 is uncorrupted, then the boot software starts execution of the said executable software stored in 3 of the decoder memory. If the result of the check indicates that there is no software in 3 or that the software loaded in 3 is corrupted, then the boot software and the loading software start loading an image of an executable software from the data stream. The image loaded from the data stream then overwrites the corrupted image in 3.
The difference between one embodiment of the invention and the state of the art is that this embodiment includes several executable software images stored on different storage means in the decoder, for example a fast memory, a hard disk with a non-erasable part and an erasable part, these examples being not restrictive. Each of the executable images may be booted. The result is that the boot software contains a cross reference to a reference table 16 represented symbolically in
An example of a hardware system designed to form the hardware support of this invention is shown in
A fast memory (flash) 10, a random access memory 30, and a hard disk forming part of a decoder or connected locally to this decoder such that it can be considered that these means are internal to the decoder, are connected to each other and to a system unit 40 through a bus 50. The hard disk 20 contains an area 21 with erase protection and an area 22 without erase protection. The area 22 without erase protection contains a first, a second and a third image of the executable software in areas 25, 26 and 27 of area 22 respectively. An area 28 not used for this invention contains other data or an empty part. The area 21 with erase protection has an area 23 containing a fourth image of an executable software. An area 24 of the area 21 not used for this invention contains other data or an empty part. When one of the four software images stored has been selected by the loading and start software stored in area 1′, and if it cannot be executed directly from its support, this image is loaded for example into a part 31 of the random access memory 30.
The image selection and loading software stored in area 1′ will now be described with reference to
Firstly, note that the executable selection and loading software is called by the boot software stored in area 1, to be loaded for example into RAM memory if necessary for execution, and is executed. In the case described with relation to
The decoder manufacturer designs and loads this boot software into the decoder. The described software architecture in which a cross reference is made to the software loaded in area 1′ is adopted to satisfy the need to adapt to decoders as they exist at the moment. It is obvious that the software architecture could be different for decoders designed to be adapted to the invention, the essential point being that the functions that will be described are included.
The process according to the invention is initiated after the boot software delivered with the decoder has called the software located in area 1′ to select and possibly to load an executable according to this invention. Thus, according to a first modification from prior art, the instruction address specified by the boot software to check the presence and integrity of the resident software no longer corresponds to this first instruction, but rather to a cross reference instruction to the software according to the invention.
According to a first step v1) shown in 101, it is checked that the table 16′ is uncorrupted and contains at least one address for an executable software image, and that it is a reliable address.
If this is not the case, the next step 102 is performed in which it is checked that the executable software image stored in the area 23 of the hard disk 20 with erase protection is present and is uncorrupted.
If the check carried out in step 102 shows that the image of the executable software stored in the area 23 of the hard disk 20 with erase protection is present and is uncorrupted, then this image may be loaded in a step 103, for example into the random access memory 30, in area 31 to be started in execution in a step 104.
If the check carried out in step 102 confirms that the executable software image stored in the area 23 on the hard disk 20 with erase protection is not present or is corrupted, then the next step 105 is carried out in which it is checked that the executable software image stored in 3 of fast memory 10 with erase protection is present and is not corrupted. If the check is positive, steps 103 and 104 are executed.
In general, if the table 16 is corrupted or if none of the images selected by the table is uncorrupted, then the m images stored in the areas with erase protection are read in a predetermined order to select and load the first of these images that is found to be uncorrupted.
If the check v1 carried out in step 101 is positive, in other words if the table 16 is uncorrupted and contains a first address for an image of an executable software, step v2 106 is carried out in which it is checked that the first image of the executable software stored in area 25 of hard disk 20 without erase protection is present and is uncorrupted. If this check is positive, then the next steps 103 and then 104 are carried out.
If the check carried out in step 106 is negative, the next image of the table 16 is selected in a step 107. The same check that was carried out in step 106 is carried out in step 108 for the second image of the executable software stored in the area 26 of the hard disk 20 without erase protection. If this check is positive, then steps 103 and then 104 are carried out.
If the check carried out in step 108 is negative, then step 107 is repeated in which the same check is carried out for the third executable software image stored in the area 27 of the hard disk 20 without erase protection. Steps 107 and 108 are started again for each image until an uncorrupted image is found. When a positive check is carried out in step 108, step 103 and then step 104 are carried out such that the third image, or in general the first uncorrupted image found in a predetermined order of reading the table 16 is executed.
In general, if table 16 is uncorrupted, then the table is read to select the first uncorrupted image referenced by the table.
The process that has just been described is used to select, and possibly load if necessary and then run the preferred image among the executable software images available in the decoder, with preference given firstly to the images stored in areas 25-27 of the hard disk 20 without erase protection and then the images in areas 23, 3 of the hard disk 20 with erase protection, or the fast memory 10 respectively. In the example commented in relation with
If no executable software image is uncorrupted, then as in prior art a loop not shown in
Optionally, if it is intended to store or load images from the stream of images in compressed form, then a step 109 to check the state of compression of the selected image is carried out before step 103 of loading the selected image in RAM. If the image is not compressed, then step 103 is carried out directly. If the image is compressed, for example using a ZIP code, then step 103 is carried out through a decompression step 110. The table attached to this description contains the text that appears in each of the boxes in the flow chart shown in
| Number | Date | Country | Kind |
|---|---|---|---|
| 01 06112 | May 2001 | FR | national |
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/FR02/01567 | 5/7/2002 | WO | 00 | 3/25/2004 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO02/091099 | 11/14/2002 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 5535399 | Blitz et al. | Jul 1996 | A |
| 5622162 | Johansson et al. | Apr 1997 | A |
| 5652886 | Tulpule et al. | Jul 1997 | A |
| 5771064 | Lett | Jun 1998 | A |
| 5835864 | Diehl et al. | Nov 1998 | A |
| 5838383 | Chimoto et al. | Nov 1998 | A |
| 5951639 | MacInnis | Sep 1999 | A |
| 6016400 | Day et al. | Jan 2000 | A |
| 6092189 | Fisher et al. | Jul 2000 | A |
| 6173417 | Merrill | Jan 2001 | B1 |
| 6317162 | Matsumoto | Nov 2001 | B1 |
| 6331876 | Koster et al. | Dec 2001 | B1 |
| 6343299 | Huang et al. | Jan 2002 | B1 |
| 6343379 | Ozawa et al. | Jan 2002 | B1 |
| 6418555 | Mohammed | Jul 2002 | B2 |
| 6449682 | Toorians | Sep 2002 | B1 |
| 6519762 | Colligan et al. | Feb 2003 | B1 |
| 6525775 | Kahn et al. | Feb 2003 | B1 |
| 6532591 | Arai et al. | Mar 2003 | B1 |
| 6584080 | Ganz et al. | Jun 2003 | B1 |
| 6591376 | VanRooven et al. | Jul 2003 | B1 |
| 6704933 | Tanaka et al. | Mar 2004 | B1 |
| 6715074 | Chaiken | Mar 2004 | B1 |
| 6912711 | Curtis et al. | Jun 2005 | B1 |
| 6931523 | Tomoson et al. | Aug 2005 | B1 |
| 6931552 | Pritchard et al. | Aug 2005 | B2 |
| 6970960 | Sarfati | Nov 2005 | B1 |
| 6981253 | Asada et al. | Dec 2005 | B2 |
| 7051325 | Choi et al. | May 2006 | B2 |
| 7069578 | Prus et al. | Jun 2006 | B1 |
| 7165265 | Mori et al. | Jan 2007 | B2 |
| 7409546 | Platt | Aug 2008 | B2 |
| 7689983 | Kitayama | Mar 2010 | B2 |
| 7774820 | Prus et al. | Aug 2010 | B2 |
| 20010005902 | Bacon et al. | Jun 2001 | A1 |
| 20020019938 | Aarons | Feb 2002 | A1 |
| 20020042870 | Rocray et al. | Apr 2002 | A1 |
| 20020087965 | Lin | Jul 2002 | A1 |
| 20020120931 | Huber et al. | Aug 2002 | A1 |
| 20020188942 | Bryan et al. | Dec 2002 | A1 |
| 20060248542 | Wang et al. | Nov 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 700 205 | Mar 1996 | EP |
| 0 998 141 | May 2000 | EP |
| 0158146 | Aug 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20040146270 A1 | Jul 2004 | US |