The present invention relates to methods and systems related to digital televisions and broadcasting, and specifically methods and systems for efficiently updating digital television firmware and related services.
Modern digital TV devices perform a variety of functions, and may have a firmware component involved in the performance these functions. Firmware may include system level software, operating systems, configuration files, and applications. Updates to digital television firmware may be developed as a result of changes in the market, a desire for new features, or discovery of problems or bugs in existing firmware.
The frequency at which updates are developed for the firmware can be much greater than the rate at which consumers are able or willing to buy new televisions. Thus there exists a need to update firmware on already purchased digital televisions.
One current method for updating firmware includes mailing to purchasers media such as a flash card or memory stick comprising the update. This method may suffer from the drawback of requiring consumers to take affirmative steps to install updates, with the potential result of unreliability and slow distribution. Another current method is to send a technician to consumer homes to install an update. This method may be both costly and cause inconvenience for consumers.
The present invention relates to means of delivering digital television firmware update modules over broadcast signals for efficient, reliable delivery of update modules to digital televisions.
In one aspect the present invention relates to methods and systems for increasing the probability that an update module will successfully reach a receiving television. In one embodiment, a rotating carousel of updates is used to continually broadcast a series of update modules. In another embodiment, update broadcast start times are staggered in areas where geographical overlap will enable a digital tuner to receive signals from multiple sources at different times of the day. In another embodiment, a receiver agent may adjust to the use patterns of the television rather than requesting the use of the television for receiving updates at the same time each day.
In another aspect, the present invention relates to efficient methods and systems for storing update modules. In one embodiment, a database is used to store a carousel or queue of information relating to update modules. In another embodiment, XML is used to store and format the update modules.
In still another aspect, the present invention relates to efficient delivery networks for update modules for digital television. In one embodiment, a network consists of distributed, autonomous servers where each server is capable of running on its own, without communication to the centralized operation center, for a programmable period of time. In another embodiment a queue of update modules is created where modules are added and removed dynamically over time without stopping the broadcast of updates. In still another embodiment, a digital tuner in a broadcast server is used to automate the server installation, provide receipts of broadcast, and report network status.
In a fourth aspect, the present invention relates to consumer services that may be delivered via digital television networks. In one embodiment, advertisements may be displayed on a television screen along with volume and channel information in response to user input, such as when the channel and volume are changed. In another embodiment, a television channel may be displayed comprising information delivered via update modules.
In a fifth aspect, the present invention relates to a method of using broadcast bandwidth for updating firmware of digital televisions. In one embodiment, the method comprises: identifying a portion of unused bandwidth corresponding to a television station; selecting at least one update module, the update module comprising an update to firmware of a digital television; transmitting, via the unused bandwidth of the television station, the at least one update module; and receiving by a digital television, the at least one update module.
The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent and may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
The central processing unit 102 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 104. In many embodiments, the central processing unit is provided by a microprocessor unit, such as those manufactured by Intel Corporation of Mountain View, Calif.; those manufactured by Motorola Corporation of Schaumburg, Ill.; the Crusoe and Efficeon lines of processors manufactured by Transmeta Corporation of Santa Clara, Calif.; the lines of processors manufactured by International Business Machines of White Plains, N.Y.; or the lines of processors manufactured by Advanced Micro Devices of Sunnyvale, Calif.
Main memory unit 104 may be one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor 102, such as Static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM), synchronous DRAM (SDRAM), JEDEC SRAM, PC100 SDRAM, Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM), Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM). In the embodiment shown in
In the embodiment shown in
A wide variety of I/O devices 130 may be present in the computer system 100. Input devices include keyboards, mice, trackpads, trackballs, microphones, and drawing tablets. Output devices include video displays, speakers, inkjet printers, laser printers, and dye-sublimation printers. An I/O device may also provide mass storage for the computer system 800 such as a hard disk drive, a floppy disk drive for receiving floppy disks such as 3.5-inch, 5.25-inch disks or ZIP disks, a CD-ROM drive, a CD-R/RW drive, a DVD-ROM drive, tape drives of various formats, and USB storage devices such as the USB Flash Drive line of devices manufactured by Twintech Industry, Inc. of Los Alamitos, Calif.
In further embodiments, an I/O device 130 may be a bridge between the system bus 120 and an external communication bus, such as a USB bus, an Apple Desktop Bus, an RS-132 serial connection, a SCSI bus, a FireWire bus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a Gigabit Ethernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a Super HIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or a Serial Attached small computer system interface bus.
General-purpose computers of the sort depicted in
For embodiments comprising mobile devices, the device may be a JAVA-enabled cellular telephone, such as the i55sr, i58sr, i85s, or the i88s, all of which are manufactured by Motorola Corp. of Schaumburg, Ill.; the 6035 or the 7135, manufactured by Kyocera of Kyoto, Japan; or the i300 or i330, manufactured by Samsung Electronics Co., Ltd., of Seoul, Korea. In other embodiments comprising mobile devices, a mobile device may be a personal digital assistant (PDA) operating under control of the PalmOS operating system, such as the Tungsten W, the VII, the VIIx, the i705, all of which are manufactured by palmOne, Inc. of Milpitas, California. In further embodiments, the client 113 may be a personal digital assistant (PDA) operating under control of the PocketPC operating system, such as the iPAQ 4155, iPAQ 5555, iPAQ 1945, iPAQ 2215, and iPAQ 4255, all of which manufactured by Hewlett-Packard Corporation of Palo Alto, Calif.; the ViewSonic V36, manufactured by ViewSonic of Walnut, California; or the Toshiba PocketPC e405, manufactured by Toshiba America, Inc. of New York, N.Y. In still other embodiments, the mobile device is a combination PDA/telephone device such as the Treo 180, Treo 270, Treo 600, Treo 650, or the Treo 700, all of which are manufactured by palmOne, Inc. of Milpitas, Calif. In still further embodiments, the mobile device is a cellular telephone that operates under control of the PocketPC operating system, such as the MPx200, manufactured by Motorola Corp. A typical mobile device may comprise many of the elements described above in
In some embodiments, the device 100 may comprise a digital television. A digital television may comprise any device capable of receiving a digital signal and outputting a visual display signal. In some embodiments, digital televisions may also comprise functionality for receiving analog transmissions. Digital televisions may comprise functionality for receiving transmissions via any digital network, including IP networks, terrestrial networks, satellite networks, and cable networks. A digital television output display signal may comprise any display standard, including Standard Definition (SD), High Definition (HD), or Enhanced Definition (ED). In some embodiments a digital television may include a display element, such as a screen or projector. In other embodiments, a digital television may comprise an appliance receives digital television signals and output a video display signal to be displayed by another device. Examples of appliances which may comprise a digital television include cable boxes, tuners, PVRs, VCRs, and DVD players. In other embodiments, a digital television may comprise a personal computer which receives digital television signals.
Referring now to
Still referring to
Referring now to
Still referring to
In the embodiment shown, the appliance 301 may comprise any computing device 100. In the embodiment shown, the appliance comprises functionality for storing and transmitting update modules. Said update modules may comprise updates to digital television firmware. An update module may comprise any means of updating digital television firmware. In some embodiments, an update module may be an executable file intended for execution on a television 205. In other embodiments, an update module may comprise a configuration file. In still other embodiments, an update module may comprise content intended to be viewed by a user. An update module may comprise any programming language, file type, or file protocol. In one embodiment, an update module may comprise a single file, in another embodiment, and update module may comprise a plurality of files. In still other embodiments, an update module may comprise a plurality of modules or sub-modules.
In some embodiments, update modules may correspond to a particular brand or model of television 205. In one embodiment, an update module may update or modify any function, display, feature, or service of a given brand or model of television 205. In another embodiment, an update module may fix a bug or improve performance of a given television 205. In still another embodiment, an update module may provide functionality for viewing menus or displays relating to program selection 201. In one embodiment an update module may provide functionality for diagnosing problems or difficulties with the television 205. In another embodiment, an update module may provide or enhance viewing features including channel and program selection, picture-in-picture, and display definition. In another embodiment, an update module may provide or enhance features including recording and playback of content. In still another embodiment, an update module may comprise functionality for viewing content protected by any DRM functionality, including HDCP, ROM-Mark, AACS, BD+, and CSS.
In other embodiments, update modules may correspond to a particular broadcaster or broadcasters 201. In one embodiment, an update module may provide compatibility with a given feature, service, or function provided by a broadcaster. In another embodiment, the update module may provide interactive functionality for communicating with a given broadcaster 201. For example, an update module may provide functionality for ordering a given television or movie to be displayed. Or, for example, an update module may provide functionality for displaying or interacting with a user's subscription or billing information for a given broadcaster 201. In still another embodiment, an update module may provide functionality for viewing menus or displays relating to program selection corresponding to a given broadcaster 201.
In still other embodiments, an update module may correspond to a given service. In one embodiment, an update module may comprise content such as advertising, news, or local events. In one embodiment, the update module may comprise functionality for displaying said content in response to a user action such as changing the volume or channel of the television. In another embodiment, an update module may comprise functionality for displaying said content as a separate channel. For example, an update module or series of update modules may comprise functionality for displaying a “channel 0” when the user first turns on their digital television, or first activates a digital set-top box. Said channel may provide local news, and may also comprise information relating to television services received by the given user. In one embodiment, this channel may take the form of a home page, which allows users to select information to view from such information as local news, weather, sports, and television services.
In another embodiment, an update module may comprise scheduling information relating to current or future update modules. The scheduling information may comprise any information relating to the delivery of an update module, including the time of day and length of the update. In other embodiments, scheduling information relating to current or future update modules may be delivered via a separate information stream. In still another embodiment, an update module may provide functionality for collecting information from the digital television. In one embodiment, an update module might comprise functionality for transmitting to a central server information corresponding to the programs and advertisements viewed on a given television.
In other embodiments, an update module may comprise functionality for efficiently receiving current or future update modules. In other embodiments, said functionality may be delivered via a separate information stream. In one embodiment, an update module may comprise a schedule of future updates. In another embodiment, an update module may comprise functionality for decompressing future update modules. In still another embodiment, an update module may comprise a field specifying the type of encryption used on an update module. Any encryption or security techniques may be used in conjunction with the update modules including without limitation message digests and digital signatures. For example, an update module or one or more fields or sub modules of an update module may be encrypted with RSA encryption and triple-DES to prevent tampering and/or unauthorized access. In some embodiments, each brand or model of television may possess unique encryption or decryption keys for deciphering update modules.
In some embodiments, the appliance 301 may transmit update modules to digital televisions via any of the connections shown. In some embodiments, the update modules may be delivered to individual televisions via a broadcaster 201. In other embodiment, the update modules may be delivered to individual televisions via a cable network 203, or a satellite network 320. In still other embodiments, the update modules may be delivered to individual televisions via the internet 303 or another computing network. For example, a digital television may periodically connect to a specified IP address to check if any updates are available for the particular make or model of the television. If an update is available, the update may then be transmitted to the television.
In some embodiments, update modules are stored on the appliance 301 for transmitting. In other embodiments, update modules may be stored on any separate computing device, including a database or file server. In some embodiments, a single appliance 301 may transmit all updates to a given source or sources. In other embodiments, a plurality of appliances 301 may transmit updates to a given source or sources.
Update modules may be transmitted by any protocol used to communicate among or within devices. In some embodiments, update modules may be transmitted along with data corresponding to a given television program or channel. In one embodiment, update modules may be transmitted in bandwidth reserved for public television stations. In some embodiments, update modules may be broadcast at given times. In other embodiments update modules may be broadcast continuously. In some embodiments, update modules may be broadcast according to a carousel structure as described herein in
In some embodiments, a given update module may be transmitted at the same time across a plurality of networks. In other embodiments, a given update module may be transmitted at staggered times across a plurality of networks. For example, referring back to
In some embodiments, the appliance may receive update modules from any of the resources shown 303, 203, 201, 320. In some embodiments, update modules may be transmitted to the appliance via the internet 303, or a satellite network 320. In other embodiments the update modules may be transmitted to the appliance via a broadcaster 201 or a cable network 203. In some embodiments, a single appliance 301 may receive all updates from a given source or sources. In other embodiments, a plurality of appliances 301 may receive updates from a given source or sources.
In some embodiments, a plurality of appliances 301 may be installed in a plurality of geographic regions. In one embodiment, each of the plurality of appliances 301 would be responsible for transmitting update modules to each of the broadcasters in its given region. In another embodiment, the appliances 301 may be installed at local broadcast facilities 301. For example, one or more appliances 301 may be installed at a plurality of PBS broadcasting affiliates throughout the country.
Referring now to
Still referring to
In one embodiment, a carousel 400 may have a fixed cycle time. For example, a carousel 400 may be set to transmit all segments 405 in the carousel 400 within 4 days. In other embodiments, a carousel may have a fixed number of segments. In still other embodiments, a carousel may have a fixed total size of data.
In some embodiments, an appliance 301 may comprise a carousel structure for broadcasting updates. In other embodiments, an appliance may comprise multiple carousel structures. In some embodiments, a plurality of appliances may comprise carousel structures with synchronized broadcast times. For example, an appliance transmitting a data stream to a broadcaster 201a may comprise a carousel structure set to begin a series of update segments at 12:00 AM on a given day, while another appliance 301 transmitting to a second broadcaster 201c may comprise a carousel structure set to begin said series of update segments at 6:00 AM.
Referring now to
Still referring to
Each update segment 405 may comprise a number of software images 505. In some embodiments, each software image may correspond to a given brand or model of digital television. In other embodiments each software image may correspond to a geographic region.
Each software image may comprise a number of modules 510. In one embodiment, each module 510 may correspond to a discrete update for a given brand or model of digital television. In other embodiments, each module 510 may correspond to a set of updates made available on a given date.
Each module 510 may be repeated a given number of times. In one embodiment, each module 510 is repeated three times in a given software image. In one embodiment, a module may corresponds to a discrete update for a given brand or model of digital television. In other embodiments, each module 510 may correspond to a set of updates made available on a given date. Said modules may comprise any content or functionality previously described herein with respect to update modules.
In some embodiments, a module may be broken into a number of sub-modules for transmission. These sub-modules may be any size, and may contain any portion of the update module. In one embodiment, each sub-module may contain error detecting or error-correction mechanisms, including without limitation checksums, digital signatures, and CRCs. In some embodiments, a digital television may have the capability to store individual sub-modules and discard individual sub-modules in the event of corruption in the transmission. This capability may be used to increase the reliability of a delivery channel, such that a given digital television may be able to assemble a complete, uncorrupted update module from a number of transmissions of an update module, where one or more sub-modules was corrupted in each transmission. For example, a 10 MB update module may be broken into 5 2 MB sub-modules for transmission. Upon receiving each of the sub-modules, a television may check to see that the sub-module has been properly received, and store the properly received sub-modules. In the event that a sub-module is corrupted, the television may discard the corrupted module, and wait for the next transmission of that sub-module to assemble the complete update module.
In other embodiments, the update modules 405, software images 505, modules 510, and modules 515 may be stored and transmitted along any other content, overhead, headers, protocols, or encapsulations.
Referring now to
Still referring to
In the second example, a carousel structure 400b is used to generate a data stream 410b. In the embodiment shown, all the update modules 405 in the carousel 400b are broadcast in a period of time of 4 days. In the embodiment shown, the data stream 410a repeats at the end of the 4-day period shown.
In other embodiments, a carousel structure 400, or a data stream 410 may repeat after any given interval of time. In some embodiments, update modules 405 may be added or removed before, after, or during a given time interval.
Referring now to
Still referring to
In the embodiment shown, one segment 705 of the bandwidth 700 is used for transmitting material relating to digital televisions, or digital television services. The segment 705 may comprise any portion, segment, or percentage of the bandwidth 700. In the embodiment shown, a portion of the segment may be active while another portion may be reserved for future use.
In the embodiment shown, the activated portion of the segment is used to transmit a data stream 410 corresponding to a carousel 400. In other embodiments, a plurality of carousels may simultaneously transmit over a given available bandwidth. A portion 720 of the data stream 410 may be allocated for carousel overhead. The carousel overhead may comprise any information relating to the operation of the carousel, including scheduling information, file sizes, and error-checking.
Referring now to
Still referring to
The unused bandwidth may be identified in any manner. In some embodiments, unused bandwidth may be identified in one or more of frequency, time, amplitude, or coding domains. The unused bandwidth may be identified by any entity, including without limitation a broadcast station, an appliance 301, or a central server. In some embodiments, unused bandwidth may be scheduled and/or identified in advance. In other embodiments, unused bandwidth may be identified dynamically and/or on a just-in-time basis.
An update module comprising an update to firmware of a digital television may be selected in any manner (step 803). In some embodiments, the at least one update module may be selected by an appliance 301. In these embodiments, the appliance 301 may select an update module the appliance has received from a central server or from a digital television manufacturer. In some embodiments, the at least one update module may be selected by an appliance 301 and then transmitted to a broadcast station for retransmission to consumers.
The at least one update module may be selected by any algorithm or process. In some embodiments, the update module may be selected from a queue or carousel. In other embodiments, the update module may be selected on the basis of size, transmission time, corresponding television brand, corresponding television model, recentness of the update module, or any other factor.
The at least one update module may be transmitted, via the unused bandwidth of the television station in any manner (step 805). In one example, a digital television manufacturer may send a firmware update to a central server. The central server may then package the firmware update into an update module, such as, for example, packaging it into sub modules and adding identifying information. The central server may then transmit the update module to a number of appliances 301 which may then add the update module into a sequence of update modules awaiting transmission. At the designated time in the sequence, an appliance 301 may then select the update module and transmit the update module to a television broadcaster. The television broadcaster may then transmit the update module out via a broadcast.
In another example, a digital television manufacturer may maintain a number of televisions internally for testing purposes. These televisions may be connected to an appliance 301. If the manufacturer wants to distribute an update to the firmware of each of the televisions, the manufacturer may upload the firmware update to the appliance 301. The appliance 301 may then package the firmware update into an update module, and then transmit the update module to each of the digital televisions. This transmission may be performed via any television station, including any closed circuit or private stations maintained internally by the manufacturer.
An update module may be received by a digital television in any manner (step 807). A digital television may also use any means and techniques to identify whether an update module corresponds to the digital television and should therefore be installed. In some embodiments, a digital television may receive a schedule of when future update modules corresponding to the digital television will arrive. In other embodiments, a digital television may identify an update module by a serial number, key, or other identifier.
The following example section describes one embodiment of a protocol, referred to as “UpdateTV,” which may be used in the transmission and reception of update modules for digital televisions. The details of the protocol are one example, one of ordinary skill in the art will recognize that many additions, subtractions, and modifications may be made to the example below.
The UpdateTV network broadcasts may be based on the DSM-CC data carousel fundamentals and the standardized protocols defined in A/90 and A/97.
The UpdateTV network may be completely compatible with these specifications. However, the UpdateTV implementation may also provide network identification, improve security, conserve bandwidth, and to provide the expansion capabilities required in supporting a large number of manufacturers with a single carousel.
The DSI message announces network compatibility and manufacturer support information. A/90 specifies the use of the Group Information Indication (GII) field which occupies the privateDataByte section in the DSI message.
Within the GII, there are three fields that are left to be defined by the implementer. These are the groupCompatibility field, the groupInfoByte field, and the groupsInfoPrivateDataByte field. A/97 further restricts the data such that the groupCompatibilty field will contain the compatibilityDescriptor and the groupInfoByte field shall contain the descriptorStructure.
The following sections discuss the UpdateTV usage for these fields in the DSI.
A/90 compatibilityDescriptor within the GII
The UpdateTV implementation reduces the role of the A/90 compatibilityDescriptor in favor of enhancing the content of the flexible fields in the DII. The DSI is size limited and only one DSI is allowed per carousel.
In the interest of preserving bits in the DSI, UpdateTV uses the first two fields of the compatibilityDescriptor: Organization Unique Identifier (OUI) and Model.
To do this, we treat the Model field of the compatibilityDescriptor as a Model Group. The Model Group is used to identify a group of receivers that share a common code base or functionality and hence are signaled by the same DII.
Since the manufacturer defines each Model Group, it can be used by a manufacturer to signal to a receiver that the module payload is shared by a number of hardware models. Additional signaling to complete this functionality is provided in the DII.
The UpdateTV Implementation of the A/97 compatibilityDescriptor imposes the following restrictions:
The groupInfoByte field is defined by A/90 and A/97 to contain a descriptor structure.
The UpdateTV network does not use the GII groupInfoByte field.
A/90 groupsInfoPrivateDataByte Field
The groupsInfoPrivateDataByte field is defined by A/90 to contain private data. The format of private data is left to the implementer.
The UpdateTV network fills this private data section using a descriptor format. Each descriptor in the groupsInfoPrivateDataByte section of the DSI contains the following format:
Two descriptors are assigned, one for Network Identification (tag number 0) and one for a copy of the System Time Table (tag number 3).
The receiver should validate a complete match with the Network Identification field when scanning for compatible carousels. This descriptor identifies the carousel data as being broadcast by the UpdateTV Network.
The Network Identification descriptor must appear last in the groupsInfoPrivateDataByte field. The tag value of this descriptor is 0x00.
The time descriptor carries a copy of the STT from the original broadcast signal (see A65B section 6.1).
The copy of the STT data is provided because the STT from the original broadcast signal may be missing or replaced when the data carousel is rebroadcast. The STT format time is used when evaluating the schedule descriptors in the DII. The data in this descriptor is identical to the data provided in the STT. The tag value of this descriptor is 0x03.
Version 1 of the UpdateTV Server will format the data as follows.
Download Information Indication Message (DII)
The DII provides information each module's compatibility beyond the OUI/Model Group pair as specified in the DSI.
The A/90 specification allows implementer definition of the moduleVersion, moduleInfoByte, and privateDataByte fields.
This use of these fields is further restricted by A/97 which uses the moduleInfoByte field to contain instances of the moduleInfoDescriptor and/or scheduleDescriptor while the privateDataByte field contains a descriptorStructure.
The following additional restrictions are required in the UpdateTV implementation.
The module information loop of this descriptor (moduleld, moduleSize, . . . ) contains an inner loop of moduleInfoBytes which is limited in length to 256 bytes. This descriptor loop contains both moduleInfoDescriptors and scheduleDescriptors. The moduleInfoDescriptor contains two inner loops, nameBytes and privateModuleBytes.
If not used efficiently, these descriptors and inner loops may strain the 256 byte limit of moduleInfoByte. To avoid situation, UpdateTV conservatively defines the uses for these fields.
The Module Info Descriptor, as defined by A/97, allows implementer flexibility with the nameByte field and the privateModuleByte field.
The UpdateTV restrictions on these fields is defined below.
A/97 nameByte Field
The nameLength value of the moduleInfoDescriptor shall not exceed 16. While limited in size, the use of the nameByte field is not further restricted by this document.
When a receiver is capable of accepting multiple types of modules, the nameByte field may be used to communicate the purpose of the module to the receiver. For example when a large image is partitioned into multiple smaller, more manageable, modules this field may be used to specify the purpose and position of each module (for example “sw1of6.ROM”).
A/97 privateModuleByte Field
This field is used to specify the UpdateTV compatibility descriptor and module priority.
The first 8 bits shall contain the modulePriority byte. The modulePriority byte in the privateModuleByte field shall be followed by the descriptorStructure as follows. Only UpdateTV defined descriptors, as defined in this document, may be used in this descriptorStructure.
One descriptor has been defined for this structure, the updateTVCompatibilityDescriptor.
modulePriority—This field is used to specify a module's download priority. If two or more modules are available for download in the same time period, the one with the lowest numbered priority is chosen for download.
The UpdateTV Compatibility Descriptor lies in the privateModuleByte field, as specified above. Each descriptor contains a range of hardware models and software versions.
descriptorTag—This field shall be set to 0x82.
descriptorLength—This field shall be set to the length in bytes in this descriptor following this field.
hardwareModelBegin—This field represents the beginning of a range of compatible hardwareModel values.
hardwareModelEnd—This field represents the end of a range of compatible hardwareModel values.
softwareVersionBegin—This field represents the beginning of a range of compatible softwareVersion values.
softwareVersionEnd—This field represents the end of a range of compatible softwareVersion values.
After first confirming compatibility with the DSI compatibility descriptor (OUI and Model Group), the receiver will inspect each hardwareModel range and softwareVersion range to validate compatibility with this module. Several UpdateTV Compatibility Descriptors may appear in the privateModuleByte field. If the module meets any of the compatibility descriptors, it is considered a candidate for download.
The UpdateTV Compatibility Descriptor allows for a powerful way to select modules from the carousel. There may be up to about 20 UpdateTV Compatibility structures per module (limited by the 255 byte limit of the privateModuleByte field.
The UpdateTV Network is designed to deliver TV system level software updates. The UpdateTV Network can also be used to distribute any other digital content.
The hardwareModelBegin and hardwareModelEnd fields are used to specify a range of hardware models that the module is compatible with. The hardware model values are scoped by the Model Group and OUI.
Compatibility is indicated if the receiver's hardware model value for that Model Group is greater than or equal to the value of the hardwareModelBegin field and less than or equal to the value of the hardwareModelEnd field. The receiver's hardware model does not change when the system level software is updated.
Unique hardware model values are assigned to each unique hardware platform in a Model Group. The hardware model value must be determined by looking at hardware registers or configuration. The hardware model must not be a value that is coded in the system level software.
The softwareVersionBegin and softwareVersionEnd fields are used to specify a range of software versions that the module is compatible with. The software version values are scoped by the Model Group and OUI.
Compatibility is indicated if the receiver's software version value is greater than or equal to the softwareVersionBegin field and less than or equal to the softwareVersionEnd field. The software version is incremented for each system level software release. The value for the software version should be a value that is set by running system level software.
A system level software image on the carousel is software version 4. This system level software is applicable for hardware models 0 to 2 running software versions 0 through 3, and hardware model 4 running software versions 2 through 3. The following descriptor shows two ranges of hardware model and software version.
Signaling the Download Data Service
The ATSC A/97 specification provides signaling of a DSM-CC data carousel. This specification signals the download data service through a Virtual Channel in the VCT of service_type 0x05.
The Virtual Channel is used to locate the PMT with the Program specified that includes a Program Element of stream_type 0x0B. This mechanism relies on the presence of the VCT to locate the proper PMT.
In order to ensure reliable signaling through various MPEG transports, the UpdateTV PMT MRD is added to the PSI data. This is provided as an alternative to the A/97 PSIP signaling when the VCT is not available. The UpdateTV SDK attempts to locate the DSM-CC data carousel through the mechanism detailed above. If a DSM-CC data carousel is not located in this way, the UpdateTV SDK attempts to locate it by examining the Program Elements in each PMT signaled in the PAT for the presence of an UpdateTV MRD.
The UpdateTV MRD is an MPEG-2 Registration Descriptor which may be found in the ES info descriptor loop within each Program Element.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, it will be understood by those skilled in the relevant art(s) that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
The present application claims priority to U.S. Provisional Application 60/746,807 titled “Methods and Apparatus for Updating Digital Television Firmware” filed on May 9, 2007.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2007/068574 | 5/9/2007 | WO | 00 | 11/9/2009 |
Number | Date | Country | |
---|---|---|---|
60746807 | May 2006 | US |