Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
  • H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
  • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
  • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
  • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
  • H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
  • H04N21/2362—Generation or processing of Service Information [SI]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/41—Structure of client; Structure of client peripherals
  • H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
  • H04N21/41407—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
  • H04N21/61—Network physical structure; Signal processing
  • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
  • H04N21/6131—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via a mobile phone network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
  • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
  • H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N7/00—Television systems
  • H04N7/16—Analogue secrecy systems; Analogue subscription systems
  • H04N7/162—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing
  • H04N7/163—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing by receiver means only

Definitions

• the invention relates generally to communications networks. More specifically, the invention relates to the signaling of an aggregate of data within a broadcast system.
• ESG Electronic Service Guide
• ESG fragments are independently existing pieces of the ESG.
• ESG fragments comprise XML documents, but more recently they have encompassed a vast array of items, such as for example, a SDP (Session Description Protocol) description, textual file, or an image.
• SDP Session Description Protocol
• the ESG fragments describe one or several aspects of currently available (or future) service or broadcast program. Such aspects may include for example: free text description, schedule, geographical availability, price, purchase method, genre, and supplementary information such as preview images or clips.
• Audio, video and other types of data comprising the ESG fragments may be transmitted through a variety of types of networks according to many different protocols.
• data can be transmitted through a collection of networks usually referred to as the "Internet” using protocols of the Internet protocol suite, such as Internet Protocol (IP) and User Datagram Protocol (UDP).
• IP Internet Protocol
• UDP User Datagram Protocol
• Data is often transmitted through the Internet addressed to a single user. It can, however, be addressed to a group of users, commonly known as multicasting. In the case in which the data is addressed to all users it is called broadcasting.
• IPDC IP datacasting
• ESG electronic service guide
• EPG electronic program guide
• DVB Digital video broadcasting-handheld
• the DVB-H is designed to deliver 10 Mbps of data to a battery-powered terminal device.
• DVB transport streams deliver compressed audio and video and data to a user via third party delivery networks.
• Moving Picture Expert Group is a technology by which encoded video, audio, and data within a single program is multiplexed, with other programs, into a transport stream (TS).
• the TS is a packetised data stream, with fixed length packets, including a header.
• the individual elements of a program, audio and video are each carried within packets having a unique packet identification (PID).
• PID packet identification
• PSI Program Specific Information
• SI Service Information
• SI Service Information
• the present invention is also is applicable to other traditional digital mobile broadcast systems such as, for example, T-DAB, T/S-DMB, ISDB-T, ATSC, MediaFlow, and non-traditional systems such 3GPP MBMS (Multimedia Broadcast/Multicast Services) and 3GPP2 BCMCS (Broadcast/Multicast Service).
• T-DAB Time Division Multiple Access
• T/S-DMB Time Division Multiple Access
• ISDB-T Time Division Multiple Access/Time Division Multiple Access
• ATSC ATSC
• MediaFlow MediaFlow
• non-traditional systems such as 3GPP MBMS (Multimedia Broadcast/Multicast Services) and 3GPP2 BCMCS (Broadcast/Multicast Service).
• 3GPP MBMS Multimedia Broadcast/Multicast Services
• 3GPP2 BCMCS Broadcast/Multicast Service
• a container comprises at least one ESG fragment, but may contain a plurality of fragments. Alternatively, a fragment may be carried in more than one container.
• the containers are transported to the receiver, for example, by using Asynchronous Layer Coding (ALC) / Layered Coding Transport (LCT) such that a single ALC/LCT transport object corresponds to a single container.
• ALC Asynchronous Layer Coding
• LCT Layered Coding Transport
• aspects of the present invention utilizes a simple and extensible header structure apart from the fragments independent of the type and format of the individual fragments, hi further embodiments, compression is applied over the entire container, including the fragments and any headers.
• other envelopes e.g. a 3GPP metadata envelope may be carried within the container without the need for unnecessary repetition of parameters, such as for example, version, validity time, and identification.
• Metadata within a 3GPP (3rd Generation Partnership Project) envelope or in any other form may include specific channels, specific programs, and/or specific channel bundles.
• Other types of metadata may include: package data, purchase data, such as operator identity data and technical data for performing the transaction, e.g., an address, protocol, price data which may be based upon package/day, channel/minute, program/minute; channel data, such as a textual description for a user, content provider branding information/logo, classification and rating data, such as genre and parental rating, channel SDP data, such as a description of capabilities needed to use the service, e.g., audio and video format and bit rate information, start and end time, addresses, addresses of synchronized auxiliary data feeds, proprietary extensions; and program data, such as a textual description for a user, start and end times, references for interactive services related to the program.
• This metadata may be loaded by an operator or may be performed automatically.
• Figure 1 illustrates a block diagram of a wireless communication system in which various aspects of the present invention may be implemented.
• Figure 2 illustrates a block diagram of a mobile terminal in accordance with an aspect of the present invention.
• Figure 3 illustrates a schematic diagram of an example transport object in accordance with an aspect of the present invention.
• Figure 4 illustrates a method of transporting a multitude of single object transports in accordance with an aspect of the present invention.
• FIG. 5 illustrates a block diagram of exemplary electronic service guide (ESG) fragment descriptor entries in accordance with at least one aspect of the present invention.
• ESG electronic service guide
• Figure 6 illustrates a block diagram of an exemplary container having a plurality of ESG objects in accordance with at least one aspect of the present invention.
• FIG. 7 is a block diagram illustrating further exemplary frames of electronic service guide (ESG) fragment descriptor entries in accordance with at least one aspect of the present invention.
• ESG electronic service guide
• Figure 8 is a block diagram of a simplified container system in accordance with one embodiment of the present invention configured for the updating of previously received fragments.
• Figure 9 is a block diagram illustrating the container and fragment management in an updating system in accordance with one embodiment of the invention.
• Figure 10 is a block diagram illustrating a container update performed in accordance with one embodiment of the invention.
• FIG. 1 illustrates an example of a wireless communication system 110 in which the systems and methods of the invention may be employed.
• One or more network-enabled mobile devices 112 such as a personal digital assistant (PDA), cellular telephone, mobile terminal, personal video recorder, portable television, personal computer, digital camera, digital camcorder, portable audio device, portable radio, or combinations thereof, are in communication with a service source 122 through a broadcast network 114 and/or cellular network 116.
• the mobile terminal/device 112 may comprise a digital broadcast receiver device.
• the service source 122 may be connected to several service providers that may provide their actual program content or information or description of their services and programs to the service source that further provides the content or information to the mobile device 112, which may be used and/or displayed as an electronic service guide for user to select their services and programs.
• the several service providers may include but are not limited to one or more television and/or digital television service providers, AM/FM radio service providers, SMS/MMS push service providers, Internet content or access providers.
• the broadcast network 114 may include a radio transmission of IP datacasting over DVB-H.
• the broadcast network 114 may broadcast a service such as a digital or analog. television signal and supplemental content related to the service via transmitter 118.
• the broadcast network may also include a radio, television or IP datacasting broadcasting network.
• the broadcast network 114 may also transmit supplemental content which may include a television signal, audio and/or video streams, data streams, video files, audio files, software files, and/or video games.
• the service source 122 may communicate actual program content to user device 112 through the broadcast network 114 and additional information such as user right and access information for the actual program content through the cellular network 116.
• the mobile device 112 may also contact the service source 122 through the cellular network 116.
• the cellular network 116 may comprise a wireless network and a base transceiver station transmitter 120.
• the cellular network may include a second/third-generation (2G/3G) cellular data communications network, a Global System for Mobile communications network (GSM), or other wireless communication network such as a WLAN network.
• 2G/3G second/third-generation
• GSM Global System for Mobile communications network
• mobile device 112 may comprise a wireless interface configured to send and/or receive digital wireless communications within cellular network 116.
• the information received by mobile device 112 through the cellular network 116 or broadcast network 114 may include user selection, applications, services, electronic images, audio clips, video clips, and/or other messages.
• one or more base stations may support digital communications with receiver device 112 while the receiver device is located within the administrative domain of cellular network 116.
• mobile device 112 may include processor 128 connected to user interface 130, memory 134 and/or other storage, and display 136. Mobile device 112 may also include battery 150, speaker 152 and antennas 154. User interface 130 may further include a keypad, touch screen, voice interface, one or more arrow keys, joy-stick, data glove, mouse, roller ball, touch screen, voice interface, or the like.
• Computer executable instructions and data used by processor 128 and other components within mobile device 112 may be stored in a computer readable memory 134.
• the memory may be implemented with any combination of read only memory modules or random access memory modules, optionally including both volatile and nonvolatile memory and optionally being detachable.
• Software 140 may be stored within memory 134 and/or storage to provide instructions to processor 128 for enabling mobile device 112 to perform various functions.
• some or all of mobile device 112 computer executable instructions may be embodied in hardware or firmware (not shown).
• Mobile device 112 may be configured to receive, decode and process transmissions based on the Digital Video Broadcast (DVB) standard, such as DVB-H or DVB-MHP, through a specific DVB receiver 141. Additionally, receiver device 112 may also be configured to receive, decode and process transmissions through FM/AM Radio receiver 142, WLAN transceiver 143, and telecommunications transceiver 144. Bi one aspect of the invention, mobile device 112 may receive radio data stream (RDS) messages.
• DVD Digital Video Broadcast
• RDS radio data stream
• one DVB 10 Mbit/s transmission may have 200, 50 kbit/s audio program channels or 50, 200 kbit/s video (TV) program channels.
• the mobile device 112 may be configured to receive, decode, and process transmission based on the Digital Video Broadcast-Handheld (DVB-H) standard or other DVB standards, such as DVB-MHP, DVB-Satellite (DVB-S), DVB-Terrestrial (DVB-T) or DVB-Cable (DVB-C).
• DVD-H Digital Video Broadcast-Handheld
• DVB-MHP DVB-Satellite
• DVD-T DVB-Terrestrial
• DVD-Cable DVB-Cable
• digital transmission formats may alternatively be used to deliver content and information of availability of supplemental services, such as ATSC (Advanced Television Systems Committee), NTSC (National Television System Committee), ISDB-T (Integrated Services Digital Broadcasting - Terrestrial), DAB (Digital Audio Broadcasting), DMB (Digital Multimedia Broadcasting) or DIRECTV.
• the digital transmission may be time sliced, such as in DVB-H technology. Time-slicing may reduce the average power consumption of a mobile terminal and may enable smooth and seamless handover. Time-slicing consists of sending data in bursts using a higher instantaneous bit rate as compared to the bit rate required if the data were transmitted using a traditional streaming mechanism.
• the mobile device 112 may have one or more buffer memories for storing the decoded time sliced transmission before presentation.
• FIG. 3 is a schematic diagram of an example transport object in accordance with at least one aspect of the present invention.
• a single transport object 300 comprises a container header 310 and a container payload 320.
• the container header 310 may contain configuration information regarding the header and/or the container payload 320.
• the header 310 is coded to inform a receiver of the entry length of the header.
• the header 310 may have a plurality of ESG fragment descriptor entries 330 that identify the ESG fragments 340 in the container payload 320 so that the receiver may determine the exact position and/or length of each contained ESG fragment 340.
• a field specifies where the particular ESG begins within the container payload 120 by providing, for example, an offset value 550, start and end points, or the like.
• metadata 350 may be associated with the individual ESG fragments 340, located within or proximate to the header 310, descriptor entries 330, a ESG fragment 340 or a mixture thereof.
• the association of a 3GPP metadata envelope with an ESG fragment 340 may substitute for, or negate the need of additional metadata to be located in the header 310 in relation to that particular ESG fragment.
• FIG 4 illustrates a method of transmitting a multitude of single object transports wherein the transports are in accordance with at least one aspect of the present invention.
• the transports objects (TO) of the current invention may be carried in, for example, FLUTE (File Delivery over Unidirectional Transport) sessions, or a pure ALC session.
• the ESG Root Channel data such as IP Address, port number and Transport Session Identifier (TSI), are announced in the IP/MAC Notification Table (INT Table).
• the FLUTE session of the ESG Root Channel comprises a File Delivery Table of the said session and one or more Transport Objects (TO).
• These Transport Objects contain mapping between the different types of ESGs and access parameters to the different ESG sessions in which the ESG data is transmitted.
• the ESGs may differ from each other e.g. as being in different languages and/or having different encoding or genre.
• the access parameters include IP Addresses, port numbers, TSIs, start and end times etc.
• the FLUTE session thus declares how the ESG data is distributed to different sessions.
• the TOs of the FLUTE session carrying this mapping data are described in the FDT of the FLUTE session.
• the ESG mapping data may be delivered in one or multiple TOs.
• the mapping can be made using XML Schema, plain ASCII text, Structured ASCII text such as multipart MIME or MIME headers, as binary with enumerated types or through various other means as is known in the art.
• the ESG data is in this example delivered in ESG sessions, which may be pure ALC sessions, in one or more TOs. The same ESG data may be delivered in one or more ESG sessions. The ESG data or parts of it may be delivered in some embodiments of the invention in one or more FLUTE sessions in addition to or instead of ALC sessions.
• FIG. 5 is a block diagram illustrating exemplary frames of electronic service guide (ESG) fragment descriptor entries in accordance with at least one aspect of the present invention.
• Frame 500 illustrates a format of the protocol frame for a header 310.
• the frames having descriptor entries 502A-D are exemplary instantiations which include a type field 505 to indicate the type and features of an entry 330.
• the type field may be extensible to allow for the addition of new types of entries. By inputting an entry type into this field 505, different information is available to the receiver.
• Frame instantiations 502 A-D we have pre-defined specific metadata associated with fragments. For example in 502B, the fields offset, start, end and baseURI are metadata for the corresponding fragment in the payload. Frame instantiation 502C in turn doesn't associate any metadata with the fragment it represents.
• the payload may contain an envelope which associates metadata with the fragment itself (both included in the envelope) or indicate that metadata is located in the header, or alternatively the type is an entry that provides predefined parameters of the ESG fragments located within the payload.
• a single descriptor entry may be configured by its type to describe a plurality of ESG fragments, or even different versions of the same ESG fragment.
• frame 502A is flagged as a type 1 entry, and includes information regarding the ESG fragments such as location, format, version information, a unique identifier.
• frames 502 may provide additional information fields regarding the ESG fragments 340, such as format 510, version 520, and a unique identifier 530.
• the format field 510 specifies whether an ESG fragment 500 is text, a video, and/or a picture.
• the format field 510 could specify virtually any information concerning the type of media contained in the ESG fragment 340.
• a version field 520 may be included to allow the updating of previously received ESGs. For example, a newer version of an ESG can be automatically detected and executed, whereas an outdated ESG fragment as specified by the version field 520 may not be executed or may be executed at the discretion of the user of the receiver. This is also often useful where local services are available. For example, when a mobile terminal moves from one geographical area to another geographical area, some services may remain available, some may no longer be available, and some may become available. Therefore, some of the ESG objects are valid in the new geographical area as in the old geographic area.
• a terminal may identify those ESG objects which are valid in the new geographic area and may store/cache objects that are no longer valid, hi another embodiment, a terminal may receive and store ESG objects from different frequencies, IP platforms, and network operators and then combine these objects with ESG objects from the current network into a unified ESG.
• a version field 520 may be coupled with or replaced by a validity field 570. While the version field 520 may indicate whether the received ESG fragment is the most current version or is configured to determine if compatibility issues exist, a validity field 570 may further separate useless or less prioritized ESG fragments. As illustrated in Figure 5, one or more validity fields 570 may indicate time periods at which the associated fragment is valid. Alternatively, validity may be based on the receiver's hardware, user defined settings, and/or the presence of other ESGs. By way of example, the presence of a BaseURI or location where the node was loaded, whether in the validity field 570, or another field, can permit verification of a received ESG fragment. In other embodiments, a BaseURI may allow the receiver to utilize the information located at the URI in conjunction with or in place of the ESG fragment.
• a unique identifier field 530 allows for the identification of an ESG fragment irregardless of the information in the container header 310. Such information would, for example, be useful when several ESGs are received, executed, or otherwise no longer associated with the header or otherwise need to be universally identifiable.
• Each of the above information fields 510, 520, 530, among other utilized fields may optionally contain a padding field 540 to compensate for improper alignment with the byte rules of the entries. For example, if the location of an ESG fragment contains a BaseURI that does not supply enough bits for the entry, ASCII characters, such as zero, may be used to fill the needed spaces to fulfill the bits requirement.
• each ESG fragment may be coded for a different bit rate than other ESG fragments. In yet further embodiments, different bit rates may be utilized for different parameters within a single ESG, for example, in the different information fields 510, 520, 530.
• Location of an ESG fragment may be obtained by utilizing an offset field 550 alone or in conjunction with an entry length field 560, wherein the fragment's offset can be measured from the header, an initial point within the payload, or any other point within the transport object.
• the fragment offset and length value can be measured in bits, bytes, or any like quantifying system.
• fields utilizing different systems ie. 6 bit, 10 bit, 32 bit
• Each descriptor entry 500 has a fragment identification field 530 which uniquely identifies the ESG fragment.
• the BaseURI is appended to the fragment's identification within the payload container to create a globally unique identifier.
• FIG. 6 illustrates a block diagram of an exemplary container having a plurality of ESG fragments in accordance with at least one aspect of the present invention.
• the transport object 600 has a container header 610 preceding a container payload 620, together forming a single transport object.
• the header 610 comprises a coding section regarding the header length 630.
• the header 610 may optionally contain a signaling mechanism or a transport encoding mechanism that is configured to signal that the transport object or a portion thereof is encoded or otherwise compressed.
• an LCT codepoint located in the beginning of the header 610, can signal that the entire transport including the header is compressed.
• a reserve field may comprise a codepoint that signals the encoding for the transport object 600.
• GZIP may be used for this purpose; however, one skilled in the art will recognize that numerous other alternatives will accomplish the goal of compression in this manner.
• additional information may optionally be included that relates, for example, to the ESGs, the header itself, or additional compression or encoding information.
• the container payload 620 comprises at least one ESG fragment 640, with some or all of the fragments having metadata (see figure 3). In some instances, the fragments do not have metadata, rather any requisite metadata is found in the header 610 associated with the appropriate descriptor entry.
• the transport object may be stored in a memory at the transmitter, intermediate transmission nodes, and/or in the various receivers.
• FIG. 7 is a block diagram illustrating further exemplary frames of electronic service guide (ESG) fragment descriptor entries in accordance with at least one aspect of the present invention.
• the frames 700, 710, 720, 730, and 740 include a type field 750 to indicate the type of frame received.
• the type field 750 may be extensible to allow for the addition of new types of entries.
• Frame 700 illustrates a simple ESG descriptor entry that provides the position of ESG fragments in the payload. ha the illustrated embodiment, an offset value of the ESG fragment is utilized to locate the fragments.
• Frames 710, 720, and 730 illustrate the various types of descriptor entries that do not associate with any container payload. Rather, frames 710, 720, and 730 may be used to validate ESG fragments already received. In further embodiments, such as illustrated by frame 740, the descriptor entry may comprise a declaration of a BaseURI for the entire container.
• the invention comprises a system and method of using the same to determine whether a newly transmitted container is a valid update of a previously received container without the need to decode or otherwise process the information within the container payload.
• a transmitter is configured to update numerous fragments as a single unit.
• the transmitted container may be further configured to mandate all targeted fragments are updated.
• the invention comprises a system and method of using the same that only requires a single instance of a container type to determine the combination of fragments in each other possible instance of the same type.
• FIG. 8 is a block diagram of a simplified container system in accordance with one embodiment of the present invention configured for the updating of previously received fragments.
• the system is configured to determine whether the newly transmitted container is a valid update without the need to decode or otherwise read the information within the container payload.
• An update container 800 generally comprises a container header 810 and a container payload 820.
• the header 810 contains information relating the number of fragments in the payload 820 and the associated offset values, however, it is within the scope of the invention to include information relating to the header 810 and/or payload 820.
• the payload comprises data items 830, 840 having fragment updates. While the embodiment shows two data items, additional data items are contemplated as well as transmitting a single data item. Each data item includes an indication of its type 850.
• the container may further indicate the presence of a payload header.
• a type 1 data item could be a binary envelope having metadata in a header as illustrated, being associated with predetermined fragments.
• Type 2 may indicate a 3GPP textual envelope associated with different fragments. The metadata therefore, is not fixed on the transport level.
• other container types may be defined.
• FIG. 9 is a block diagram illustrating the container and fragment management in an updating system in accordance with one embodiment of the invention.
• File Delivery Tables (FDT) 900 and 910 announce the instantiations of the grouping of fragments.
• the fragment types in each container type are determined by the receiver when initially receiving the first container instance. All different container instances of the same type use the same signature, for example FDT Content-Location, but a different transfer object identifier (TOI).
• Two different container instances may have different encoding applied, i.e. they have different Content types.
• a container holding fragments A of version Al and B of version Bl and a container holding fragments A of version A2 and B of version B2 have the same container type.
• a container holding fragment A (irregardless of the version) will have a distinctly different container type than a container holding fragments A, B and C (of any version).
• Additional optional fields, such as Content-Encoding can also remain in an unaltered state depending on the transmitter's preference. For example, if textual metadata is utilized, the entire container may be encoded with for example, GZip or other mechanisms known in the art. Alternatively only portions could be encoded.
• Container encoding and Forward Error Correction can be declared by different mechanisms.
• FDT parameters may declare the encoding mechanism.
• the encoding and FEC are declared through the use of LCT extensions.
• the containers are encoded to enable the receiver to determine if the container is to be decoded and processed without having to access or otherwise read the containers.
• Figure 10 is a block diagram illustrating a container update performed in accordance with one embodiment of the invention.
• the FDT 1010 and the associated container 1020 are received at a terminal, where they are processed or rejected.
• the File Delivery Table 1030 represents an update to FDT 1010, and is received after the receipt of FDT 1010.
• FDT still corresponds to a Type A container 1040, however it includes instance A2 in place of instance Al, and may comprise changes such as, for example, fragment 1: instance 4 is not changed, but fragment i: instance 3 is changed to instance 5.
• the terminal determines that instance A2 includes one or more fragment updates as compared to instance Al.
• the terminal may further determine that A2 contains the same type of fragments as Al.
• the terminal further determines, based on a myriad of factors, whether A2 is to be implemented.

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• General Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Mobile Radio Communication Systems (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Priority Applications (4)

Applications Claiming Priority (4)

Publications (1)

Family

ID=36564797

Family Applications (1)

Country Status (5)

Cited By (7)

Families Citing this family (3)

Citations (1)

Family Cites Families (2)

• 2005
  • 2005-11-21 WO PCT/IB2005/003607 patent/WO2006059209A1/en active Application Filing
  • 2005-11-21 AU AU2005311013A patent/AU2005311013A1/en not_active Abandoned
  • 2005-11-21 EP EP05806567A patent/EP1817904A4/en not_active Withdrawn
  • 2005-11-21 CN CN2005800454338A patent/CN101095342B/zh not_active Expired - Fee Related
• 2008
  • 2008-06-20 HK HK08106881.1A patent/HK1112139A1/xx not_active IP Right Cessation

Patent Citations (1)

Also Published As

Similar Documents

Legal Events