WO2002035791A1 - Method and device for the transmission of data in a television system - Google Patents

Method and device for the transmission of data in a television system Download PDF

Info

Publication number
WO2002035791A1
WO2002035791A1 PCT/EP2001/012333 EP0112333W WO0235791A1 WO 2002035791 A1 WO2002035791 A1 WO 2002035791A1 EP 0112333 W EP0112333 W EP 0112333W WO 0235791 A1 WO0235791 A1 WO 0235791A1
Authority
WO
WIPO (PCT)
Prior art keywords
atvef
data
address
announcements
range
Prior art date
Application number
PCT/EP2001/012333
Other languages
French (fr)
Inventor
Laurent Lesenne
Frédéric Pasquier
Original Assignee
Thomson Licensing Sa
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thomson Licensing Sa filed Critical Thomson Licensing Sa
Priority to MXPA03003505A priority Critical patent/MXPA03003505A/en
Priority to US10/399,987 priority patent/US7984471B2/en
Priority to EP01989002A priority patent/EP1329083B1/en
Priority to KR10-2003-7005041A priority patent/KR20030045108A/en
Priority to AU2002220658A priority patent/AU2002220658A1/en
Priority to DE60139332T priority patent/DE60139332D1/en
Priority to JP2002538639A priority patent/JP2004512772A/en
Publication of WO2002035791A1 publication Critical patent/WO2002035791A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • 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/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] 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/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/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving MPEG packets from an IP network
    • H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
    • 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/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/08—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division
    • H04N7/087—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division with signal insertion during the vertical blanking interval only
    • H04N7/088—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division with signal insertion during the vertical blanking interval only the inserted signal being digital
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols

Definitions

  • ATVEF Advanced Television Enhancement Forum
  • IP multicast Internet Protocol multicast
  • the object of the invention is a method for transmitting binary data in a video transmission system comprising the steps of:
  • the method further comprises the steps of: receiving a non-ATVEF announcement announcing transmission of receiver software update data, said announcement containing an IP multicast address on which signaling data describing the update data transmission is to be sent; listening to the address specified in the announcement; retrieving the signaling data and storing it in a memory which is not erased during download of the update data; launching of a loader program; having the loader program retrieve the stored signaling data; and proceeding with the download of the update data based on the stored signaling data.
  • the receiver further comprises a memory for receiving a third multicast address on which binary data transmission is announced, said memory being such as to maintain the multicast address during a receiver reboot process, said receiver further comprising means for listening to the third multicast address in the memory after reboot for downloading the binary data from said third multicast address.
  • FIG. 1a represents an ATVEF protocol stack
  • - figure 1 b represents a protocol stack of a device according to the embodiment
  • FIG. 4 is a flowchart of the processing of announcements in a broadcast server
  • FIG. 5 is a schematic diagram illustrating the principle of acquiring an IP multicast address in a first step when the receiver is in nominal mode and using the stored IP multicast address in a second step during which the receiver is in a loader mode;
  • the parameter 'c' of an announcement indicates to which address content and triggers will be sent, while the parameter 'm' indicates on which port they will be sent. Triggers and content may be sent on different ports at the same address, as well as on different addresses.
  • FIG. 1 b is a diagram of the protocol stack used by a receiver in conformance with the present embodiment.
  • the UHTTP layer has been replaced by a proprietary layer.
  • the stack includes UDP (User Datagram Protocol) over IP (Internet Protocol), SLIP (Serial
  • Enhancements and binary data are usually sent repeatedly, in order to enable receivers to access the corresponding data even when they do not listen from the beginning of the transmission, and in order to retrieve packets which were previously received with uncorrectable errors.
  • the first one indicates an address/port A5 for retrieving date and time information, while the second one indicates an address/port A6 for retrieving the binary data.
  • Applications of figure 2 act upon a socket layer 4 to listen to the required IP multicast addresses.
  • the socket layer 4 operates over an operating system 5 including a VBI Driver (which is not illustrated).
  • VBI Vertical Blanking Interval
  • the Vertical Blanking Interval (VBI) driver retrieves data from the VBI of the incoming analog video signal.
  • VBI Vertical Blanking Interval
  • IDLB packet format
  • the driver extracts the payload from these packets and applies an error correction process.
  • the receiver runs a browser 1 in charge of retrieving respectively the ATVEF announcements, content and triggers and listens respectively to addresses A1 , A3, A4, which the browser 1 has programmed at the socket level).
  • a first task 2 ('Binary data fetching manager') is in charge of retrieving the non-ATVEF announcements sent on address A2.
  • a second task 3 ('Code download signaling data retriever') is used to retrieve the binary file itself on an address A6.
  • the address A6 has previously been specified in a binary announcement on address A2.
  • Two different tasks are used to retrieve the update announcement and the update file itself: this avoids having to sort the incoming data relating to these addresses.
  • the binary data fetching module When the binary data fetching module receives a non-ATVEF announcement for an update, it starts a specific task (the code download signaling retriever of figure 2), which listens to an address specified in the update announcement.
  • the code to be downloaded is not sent to this address, eventually with other signaling information describing the download to be carried out. Instead, this address receives a stream which describes the upcoming download, and in particular a download address.
  • the code download signaling data retriever task stores this address in a predefined location in the flash memory 8 of the receiver, this location being protected from being erased during the subsequent download.
  • the task reboots the decoder.
  • the loader 7 is then launched. This program fetches the download address from the flash memory and downloads the code from this address.
  • This update process may also be used in other environments than that of the present embodiment (i.e. environments not related to ATVEF).

Abstract

The invention concerns a method for transmitting binary data in a video transmission system. The method comprises the steps of providing ATVEF announcements on a first predefined IP multicast address; providing ATVEF trigger and/or content transmission on a first range of IP multicast addresses; providing non-ATVEF announcements on a second predefined multicast address different from said first address; and providing non-ATVEF data transmission on a second range of IP multicast addresses, exclusive of the first range. The invention also concerns an emitter and a receiver for implementing the method.

Description

METHOD AND DEVICE FOR THE TRANSMISSION OF DATA IN A TELEVISION SYSTEM
The invention concerns a method for transmitting data in a television system, as well as an emitter and a receiver in such a system. The invention applies in particular, but is not limited to, systems implementing the ATVEF specification.
Television receivers are being developed to host resident interactive services, transmitted for example through a bi-directional return channel or simply broadcast over the same channel as the video signal. In this context, ATVEF (Advanced Television Enhancement Forum) specifies the use of a number of protocols such as IP multicast (Internet Protocol multicast) for transporting data for interactive television program enhancement services over a number of transmission media.
According to the ATVEF specification, when a service provider wishes to transmit an interactive service, he first has to transmit a message called an announcement, containing information describing the interactive service. This announcement is transmitted to a specific IP multicast address and to a specific port, known to all receivers (IP address 224.0.1.113 and UDP Port 2670).
Receivers compatible with the ATVEF specification continuously monitor this address/port couple. Their resident software modules retrieve the announcement, which contains a pair of IP addresses, one for the transmission of the interactive service (called the 'content'), another one of the transmission of triggers. Triggers are messages for triggering a certain behavior of interactive services at predetermined moments.
Software modules resident in the receivers may require updates. For flexibility reasons, it should be possible to make such an update in remote fashion, i.e. to transmit the updated software modules to the receivers in situ. Such a transmission should obviously use some of the already available transmission media, such as the return channel (be it through the PSTN or the cable network, or another type of bi-directional communication means) or the television broadcast medium. The ATVEF protocol stack (see figure 1 a) cannot be used directly to transmit the update - or other types of binary data -, because the software in charge of retrieving the interactive service (e.g. a browser) is not able to interpret the content data which represents the resident software module update. This update is typically binary data, instead of the UHTTP data expected by the browser. This could result in unpredictable behavior at the receiver level. Modifying the browser to detect and process binary data would be impractical. In addition, transporting binary data using UHTTP is cumbersome, since this protocol has not been developed for such a purpose.
Nevertheless, it is desired to respect as much a possible the ATVEF protocol, to remain within the constraints defined by the broadcast tools.
The object of the invention is a method for transmitting binary data in a video transmission system comprising the steps of:
- providing ATVEF announcements on a first predefined IP multicast address;
- providing ATVEF trigger and/or content transmission on a first range of IP multicast addresses; - providing non-ATΛ/EF announcements on a second predefined multicast address different from said first address;
- providing non-ATVEF data transmission on a second range of IP multicast addresses, exclusive of the first range.
According to an embodiment of the invention, said system comprises an emitter comprising a data inserter for inserting ATVEF and non-ATVEF information into a transmission signal, said method further comprising the steps of:
- providing ATVEF announcements and non-ATVEF announcements to the data inserter,
- dynamic insertion of IP multicast addresses by the data inserter into the announcements, in accordance with the first and second ranges.
According to an embodiment of the invention, the method further comprises the step of splitting each of the first and/or the second range of IP multicast addresses into a third and a fourth range, where the third range is reserved for automatic address determination by the data inserter, and the fourth range is reserved for addresses which are predefined in the announcements provided to the data inserter.
According to an embodiment of the invention, ranges are distinguished by different IP address ranges, different port ranges or both.
According to an embodiment of the invention, at the level of a receiver, the method further comprises the steps of: receiving a non-ATVEF announcement announcing transmission of receiver software update data, said announcement containing an IP multicast address on which signaling data describing the update data transmission is to be sent; listening to the address specified in the announcement; retrieving the signaling data and storing it in a memory which is not erased during download of the update data; launching of a loader program; having the loader program retrieve the stored signaling data; and proceeding with the download of the update data based on the stored signaling data.
Another object of the invention is an emitter device for broadcasting announcements in a transmission system compatible with ATVEF transmissions, characterized in that it comprises means for transmitting ATVEF announcements on a first predefined IP multicast address, A EF trigger and/or content data on a first range of IP multicast addresses, binary data announcements on a second predefined IP multicast address different from the first predefined address and binary data on a second range of IP multicast addresses, wherein the first and second address ranges are exclusive of each other.
According to an embodiment of the invention, the emitter comprises means for receiving an announcement, for determining whether the announcement comprises a predetermined IP multicast address in a first range, and in the negative, for selecting an IP multicast address in a second range, distinct from the first range, and for inserting the selected IP multicast address into the announcement. Another object of the invention is a receiver in an ATVEF compatible transmission system, characterized in that it comprises a memory for storing a first predefined IP multicast address for receiving ATVEF announcements, and a second predefined IP multicast address for receiving announcements relating to the transmission of binary data, where the first and second addresses are distinct.
According to a variant embodiment, the receiver further comprises a memory for receiving a third multicast address on which binary data transmission is announced, said memory being such as to maintain the multicast address during a receiver reboot process, said receiver further comprising means for listening to the third multicast address in the memory after reboot for downloading the binary data from said third multicast address.
According to an embodiment, the third multicast address on which binary data transmission is announced is provided in signaling data announced on said second multicast address.
According to an embodiment, the downloaded binary file is a complete system update.
Other characteristics and advantages of the invention will appear through the description of a detailed, non-limiting embodiment, explained with the help of the attached drawings, among which:
- figure 1a (prior art) represents an ATVEF protocol stack;
- figure 1 b represents a protocol stack of a device according to the embodiment;
- figure 2 represents the software structure of a receiver, as well as different applications and tasks and their evolution upon reception of an announcement;
- figure 3 is a flowchart of the processing of announcements and data by a receiver according to the invention;
- figure 4 is a flowchart of the processing of announcements in a broadcast server;
- figure 5 is a schematic diagram illustrating the principle of acquiring an IP multicast address in a first step when the receiver is in nominal mode and using the stored IP multicast address in a second step during which the receiver is in a loader mode;
- figure 6 is a schematic diagram of a network comprising an emitter and receivers according to the present embodiment.
In the figures, the symbol '@' is used to designate an address.
More information concerning the ATVEF specification can be found in the document "Enhanced Content Specification" ATVEF (Advanced Television Enhancement Forum) Specification v 1 .1 r26. This document is available for example on the ATΛ/EF website (www.atvef.com).
Reference is also made to the document 'SDP: Session Description Protocol', Internet Society, Network Working Group, RFC 2327 of April 1998, available at ftp.isi.edu/in-notes/rfc2327.txt. Announcements according to the ATVEF specification follow the format described in the SDP document mentioned in the previous paragraph, though ATVEF imposes some restrictions for some parameters. Parameters used in an SDP announcement according to the ATVEF specification are as follows:
Session description
v= protocol version, equal to 0 o= username, session identifier, version, network type (equal to IN in the present case), address type (equal to IP4 in the present case), ipaddress s= session name i= session information (optional) u= Universal Resource Identifier (URI) of a description of the enhancement (optional) e= email address p= phone number
(at least one of the e and p parameters is required) b= CT.number (bandwidth information) c= connection information
The following session attributes can or must be used: a= UUID:/JL//D (Universally Unique Identifier: unique enhancement identifier - optional) a= type:tve a= lang, a= sdplang (optional language attributes) a= tve-type:<types> (optional) a= tve-size: Kbytes a= tve-level:x (optional) a= tve-ends:secot? s (optional)
Media description
m= (media name and transport address)
Time description
t= (time during which the session is active)
As has already been mentioned in the introduction, ATVEF announcements are sent to a predefined IP address (224.0.1.1 13) and a predefined UDP port number (2670).
The parameter 'c' of an announcement indicates to which address content and triggers will be sent, while the parameter 'm' indicates on which port they will be sent. Triggers and content may be sent on different ports at the same address, as well as on different addresses.
The present embodiment concerns an analog television system in which the vertical blanking interval lines of the analog video signal are used to transmit digital data. Modulation of this kind of data on an analog television signal is well known per se.
Figure 1 b is a diagram of the protocol stack used by a receiver in conformance with the present embodiment. Compared to the ATVEF stack of figure 1 a, the UHTTP layer has been replaced by a proprietary layer. The stack includes UDP (User Datagram Protocol) over IP (Internet Protocol), SLIP (Serial
Line Internet Protocol) and IDL-B, as defined in ETS 300 708. The role of the proprietary layer is to manage binary data downloading. The binary data to be downloaded is split into sections having the size of IP packet payloads, i.e. 1472 octets. The layer assembles the different sections it receives in the right order. If a section contains uncorrectable errors, then the proprietary layer waits for a next transmission (see below) and inserts it at its proper place.
The proprietary layer also retrieves date/time information and announcements relating to binary data downloads and date/time information.
Enhancements and binary data are usually sent repeatedly, in order to enable receivers to access the corresponding data even when they do not listen from the beginning of the transmission, and in order to retrieve packets which were previously received with uncorrectable errors.
According to the present embodiment, in order to announce the transmission of binary data, an announcement of the SDP format is made at another address and port than the address and port used by the ATVEF announcements. Accordingly, as an example, the receiver listens to the address 235.0.1.113, port number 2670, to detect these novel types of announcements. In parallel, the receiver continues to listen to the standard ATVEF announcement address and port.
Figure 2 is a diagram of an example of the applications and tasks that a receiver according to the present embodiment runs in parallel according to the present embodiment. Of course, other applications and tasks may also run, but are not directly relevant to the present embodiment. The receiver listens to six different IP multicast addresses, numbered A1 to A6. An IP multicast address comprises an IP address and a port number. An ATVEF announcement is sent to the well-known ATVEF address/port couple A1 as already described above. ATVEF content and triggers ('ATVEF data') is sent to two different address/port couples, A3 and A4, which are specified by the ATVEF announcement. Two different non-ATVEF announcements are sent to predefined, fixed address/port A2. The first one indicates an address/port A5 for retrieving date and time information, while the second one indicates an address/port A6 for retrieving the binary data. Applications of figure 2 act upon a socket layer 4 to listen to the required IP multicast addresses. The socket layer 4 operates over an operating system 5 including a VBI Driver (which is not illustrated). The Vertical Blanking Interval (VBI) driver retrieves data from the VBI of the incoming analog video signal. Of course, in case another transmission path were used (e.g. all digital television signal such as an MPEG II Transport Stream), another driver than the VBI Driver would be used. The retrieved data is under a packet format called IDLB. The driver extracts the payload from these packets and applies an error correction process. The payload is a SLIP-format stream which enables the driver to identify and separate IP packets. Once the SLIP layer has been removed and the IP packets have been reconstructed, the driver hands these packets over to the upper layers in charge of de-encapsulating the IP and UDP layers. The browser 1 and the other applications are clients of the socket layer 4 which enables them to listen to an IP address and a UDP port in order to retrieve the transmitted content.
The upper part of figure 2 will be described first. The upper and lower parts show the receiver's state at different moments in time.
The receiver runs a browser 1 in charge of retrieving respectively the ATVEF announcements, content and triggers and listens respectively to addresses A1 , A3, A4, which the browser 1 has programmed at the socket level). In figure 2, it is supposed that at least one announcement has already been received. The browser may also listen to other addresses, which are not shown on figure 2. A first task 2 ('Binary data fetching manager') is in charge of retrieving the non-ATVEF announcements sent on address A2. A second task 3 ('Code download signaling data retriever') is used to retrieve the binary file itself on an address A6. The address A6 has previously been specified in a binary announcement on address A2. Two different tasks are used to retrieve the update announcement and the update file itself: this avoids having to sort the incoming data relating to these addresses.
The second task 3 need not be active all the time. It can be triggered by the first task 2, upon reception of an announcement relating to the kind of data retrieved by the second task 3.
According to the present embodiment, the ϊ field of an announcement is used to inform the task 2 of the nature of the data to be transmitted. For example, ϊ is equal to 'code download' for the transmission of binary data, and equal to 'date&time' for the transmission of the date and time information.
Contrary to ATVEF announcements, the announcement according to the present embodiment contains only one address and associated port value, to indicate to the receiver where to listen for the transmission of the binary data (code update, time, or other).
According to the present embodiment, such an announcement contains the following parameters relating to the address and port of the update file: m = data 22814 tvpe-file c=IN IP4 235.37.32.27.
Other parameters are similar to those used in ATVEF announcements. This is given as an example: other values may be used as well.
As an example, a non-ATΛ/EF announcement contains the following fields:
"v=0" see ATVEF "i=XXX" see below
"a=UUID:XXX" see ATVEF "a=tve-ends:XXX" or "t-start stop" see ATVEF "m=data XXX tve-file" see above and ATVEF "c=IN IP4 XXX" see above and ATVEF
Figure 2 also illustrates the dynamics of announcement handling in the receiver. The upper part of figure 2 shows the receiver's task at a time t. At this time, the browser 1 listens to its predetermined ATVEF announcement address A1 , and to two further addresses for content (A3) and triggers (A4). The binary data fetching module 2 listens to the address corresponding to binary data announcements.
At a given time, a binary announcement concerning the transmission of date and time is received by the binary data fetching module 2. This announcement contains an IP multicast address A5 on which data and time information is due to be transmitted. As illustrated by the lower part of figure 2, a third task 6, named 'Date and time data retriever' is launched, in order to listen to the address A5 specified in the announcement.
Figure 3 is a flowchart which further illustrates the processing of ATVEF and non-ATVEF announcements and data in the receiver.
It must be noted that from the point of view of the implementation, the test of whether an announcement is an ATVEF announcement or not corresponds in fact to the filtering carried out using the different IP multicast addresses. The field "a=UUID" serves to identify the announcement. If the proprietary layer, in its role of binary data fetching module, already received an announcement with the same UUID value although the expiration date of this announcement has not yet been reached, the new announcement is ignored. It is up to the operator to modify the UUID value in order to inform receivers of an announcement content change. This mechanism avoids having to further process announcements if their UUIDs correspond to those of already existing announcements.
When preparing an announcement, the service provider or the broadcaster's emitter selects the address values for data transmission in a certain range. According to the present embodiment, one such range is reserved for ATVEF transmissions, while another such range is reserved for non-ATVEF transmissions (e.g. software module updates according to the present example). This avoids having ATVEF data sent to non-ATVEF addresses and vice-versa.
Through this mechanism, different kinds of services may easily be multiplexed.
Figure 4 is a flowchart of the announcement creation process in a server, showing how IP multicast addresses are automatically selected and inserted into announcements by the emitter in the absence of preset addresses.
In a preferred embodiment, the broadcaster receives the ATVEF or non-ATVEF announcements and dynamically adds through its emitter the content, trigger or binary data transmission addresses according to the predefined ranges. As an example, the following address range is used for sending ATVEF enhancements on manually attributed addresses:
224.0.0.0 to 224.0.1.112 port numbers 0 to 2669.
The following address range is used for sending ATVEF enhancements on automatically attributed addresses:
224.0.1.114 to 234.255.255.255, port numbers 2671 to 65535.
The following address range is used for sending binary files on manually attributed addresses:
235.0.0.0 to 235.0.1.112, port numbers 0 to 2669. The following address range is used for sending binary files on automatically attributed addresses:
235.0.1.114 to 239.255.255.255, port numbers 2671 to 65535.
Manually attributed addresses are addresses which are predetermined in announcements received by the emitter from e.g. the service provider, i.e. the emitter does not itself select such addresses, as opposed to announcements were such a choice is made automatically by the emitter, when at least one address is missing in an announcement. Different address ranges are used to avoid having the emitter pick an address which has already been defined manually in another announcement.
According to a variant embodiment, the address ranges used for
ATVEF and non-ATVEF data transmissions are the same or at least overlap to a certain extent, but the port number ranges attributed to each kind of data transmission do not overlap. In other words, there will still be different IP multicast address ranges.
The two address ranges may be modified. In this case, an update mechanism is put in place at the receiver.
A variant embodiment, illustrated by figure 5, will now be described. This embodiment concerns the case in which the binary data to be downloaded may influence - and in particular interrupt - certain processes of the receiver.
One can consider a receiver in which downloading of executable code, for example all updatable code stored in a flash memory of the receiver, is to be performed. The receiver comprises a loader program 7 in order to perform the download. This program is stored in ROM, since all code stored in the flash memory is to be replaced.
The process in such a case is the following:
When the binary data fetching module receives a non-ATVEF announcement for an update, it starts a specific task (the code download signaling retriever of figure 2), which listens to an address specified in the update announcement. The code to be downloaded is not sent to this address, eventually with other signaling information describing the download to be carried out. Instead, this address receives a stream which describes the upcoming download, and in particular a download address. The code download signaling data retriever task stores this address in a predefined location in the flash memory 8 of the receiver, this location being protected from being erased during the subsequent download. When the download is to begin, the task reboots the decoder. The loader 7 is then launched. This program fetches the download address from the flash memory and downloads the code from this address. This update process may also be used in other environments than that of the present embodiment (i.e. environments not related to ATVEF).
Figure 6 is a schematic diagram of a network comprising an emitter 51 , and a plurality of receivers 52i. The emitter comprises a video signal source 53, a data inserter 54 controlled by a broadcast server 61. The broadcast server 61 is connected to a database 55, containing ATVEF and non-ATVEF data and announcements. The data inserter inserts data into the VBI lines of the video signal in an appropriate format, under control of the broadcast server, which defines timing and allocates signal resources. Data in database 55 may be provided by different sources, in particular a service provider 56. The broadcast server 61 automatically selects addresses as explained above, in case such an automatic selection is required. Receivers also comprise a microprocessor 57, a ROM 58 with a loader program 59 mentioned above, as well as a register or memory 60 adapted to hold a multicast address during receiver reset and/or reboot and/or power loss.
Although the present embodiment mainly concerns A EF-type protocols, the invention is not limited to that environment. In particular, other announcement formats than those of the ATVEF or SDP announcements may be used. The split multicast address ranges according to data type in particular constitutes an invention which may be employed in an other environment. Lastly, although the embodiment above concerns an implementation using the vertical blanking interval of an analog video signal to transmit the enhancement and update data, the invention can easily be applied within other system, in particular all-digital transmission systems.
The emitter and receiver in the described system both comprises processing means such as a microprocessor (reference 57 in receivers of figure 5) and memory, for processing and respectively sending or receiving announcements, triggers, enhancement content and binary data.

Claims

Claims
1. Method for transmitting binary data in a video transmission system comprising the steps of:
- providing ATVEF announcements on a first predefined IP multicast address;
- providing ATVEF trigger and/or content transmission on a first range of IP multicast addresses; - providing non-ATVEF announcements on a second predefined multicast address different from said first address;
- providing non-ATVEF data transmission on a second range of IP multicast addresses, exclusive of the first range.
2. Method according to claim 1 , wherein said system comprises an emitter (51) comprising a data inserter (54) for inserting ATVEF and non- ATVEF information into a transmission signal, said method further comprising the steps of:
- providing ATVEF announcements and non-ATVEF announcements to the data inserter (54),
- dynamic insertion of IP multicast addresses by the data inserter (54) into the announcements, in accordance with the first and second ranges.
3. Method according to claim 2, further comprising the step of splitting each of the first and/or the second range of IP multicast addresses into a third and a fourth range, where the third range is reserved for automatic address determination by the data inserter (54), and the fourth range is reserved for addresses which are predefined in the announcements provided to the data inserter.
4. Method according to one of the claims 1 to 3, wherein ranges are distinguished by different IP address ranges, different port ranges or both.
5. Method according to one of the claims 1 to 4, comprising, at the level of a receiver, the steps of: receiving a non-ATVEF announcement announcing transmission of receiver software update data, said announcement containing an IP multicast address (A6) on which signaling data describing the update data transmission is to be sent; listening to the address (A6) specified in the announcement; retrieving the signaling data and storing it in a memory which is not erased during download of the update data; launching of a loader program; having the loader program retrieve the stored signaling data; and proceeding with the download of the update data based on the stored signaling data.
6. Emitter device (51 ) for broadcasting announcements in a transmission system compatible with ATVEF transmissions, characterized in that it comprises means for transmitting ATVEF announcements on a first predefined IP multicast address, ATVEF trigger and/or content data on a first range of IP multicast addresses, binary data announcements on a second predefined IP multicast address different from the first predefined address and binary data on a second range of IP multicast addresses, wherein the first and second address ranges are exclusive of each other.
7. Device according to claim 6, further comprising means (54, 55) for receiving an announcement, for determining whether the announcement comprises a predetermined IP multicast address in a first range, and in the negative, for selecting an IP multicast address in a second range, distinct from the first range, and for inserting the selected IP multicast address into the announcement.
8. Receiver (52i) in an ATVEF compatible transmission system, characterized in that it comprises a memory for storing a first predefined IP multicast address for receiving ATVEF announcements, and a second predefined IP multicast address for receiving announcements relating to the transmission of binary data, where the first and second addresses are distinct.
9. Receiver according to claim 8, further comprising a memory (60) for receiving a third multicast address on which binary data transmission is announced, said memory being such as to maintain the multicast address during a receiver reboot process, said receiver further comprising means (57, 58, 59) for listening to the third multicast address in the memory after reboot for downloading the binary data from said third multicast address.
10. Receiver according to claim 9, wherein the third multicast address on which binary data transmission is announced is provided in signaling data announced on said second multicast address.
11. Receiver according to claim 10, wherein the downloaded binary file is a complete system update.
PCT/EP2001/012333 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system WO2002035791A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
MXPA03003505A MXPA03003505A (en) 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system.
US10/399,987 US7984471B2 (en) 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system
EP01989002A EP1329083B1 (en) 2000-10-23 2001-10-18 Methods and devices for the transmission and reception of data in an atvef television system
KR10-2003-7005041A KR20030045108A (en) 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system
AU2002220658A AU2002220658A1 (en) 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system
DE60139332T DE60139332D1 (en) 2000-10-23 2001-10-18 METHOD AND DEVICES FOR TRANSMITTING AND RECEIVING ATVEF DATA IN A TV SYSTEM
JP2002538639A JP2004512772A (en) 2000-10-23 2001-10-18 Method and apparatus for data transmission in a television system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP00402921A EP1202520A1 (en) 2000-10-23 2000-10-23 Method and device for data transmission in a television system
EP00402921.1 2000-10-23

Publications (1)

Publication Number Publication Date
WO2002035791A1 true WO2002035791A1 (en) 2002-05-02

Family

ID=8173914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2001/012333 WO2002035791A1 (en) 2000-10-23 2001-10-18 Method and device for the transmission of data in a television system

Country Status (9)

Country Link
US (1) US7984471B2 (en)
EP (2) EP1202520A1 (en)
JP (1) JP2004512772A (en)
KR (1) KR20030045108A (en)
CN (1) CN100496042C (en)
AU (1) AU2002220658A1 (en)
DE (1) DE60139332D1 (en)
MX (1) MXPA03003505A (en)
WO (1) WO2002035791A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7076467B1 (en) * 2000-08-04 2006-07-11 Sony Computer Entertainment America Inc. Network-based method and system for transmitting digital data to a client computer and charging only for data that is used by the client computer user
EP1631882A4 (en) * 2003-06-02 2011-10-05 Seiko Epson Corp Image display device and method of announcing a presence of an image display device over network
US20060230102A1 (en) * 2005-03-25 2006-10-12 Murray Hidary Automated training program generation and distribution system
KR101270275B1 (en) * 2005-08-17 2013-05-31 삼성전자주식회사 Apparatus and method for providing notification message in broadcasting system
US20070300273A1 (en) * 2006-06-21 2007-12-27 Gary Turner Interactive television application and content enhancement
US20080092193A1 (en) * 2006-10-17 2008-04-17 The Video Load, Llc Methods and systems for creating video files for a mobile device
US20080267589A1 (en) * 2007-04-27 2008-10-30 Gary Turner Television bandwidth optimization system and method
US20110067050A1 (en) * 2009-09-17 2011-03-17 Ad-Fuse Technologies Ltd. System and Method for Enhancing Video Data
TWI528749B (en) * 2011-09-06 2016-04-01 Sony Corp A signal receiving device, a signal receiving method, an information processing program and an information processing system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694163A (en) * 1995-09-28 1997-12-02 Intel Corporation Method and apparatus for viewing of on-line information service chat data incorporated in a broadcast television program
WO1999055088A1 (en) * 1998-04-22 1999-10-28 Siemens Aktiengesellschaft Method for transmitting supplementary information signals in blanking intervals of a video signal, and a device for receiving these supplementary information signals

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6009274A (en) * 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
US6055364A (en) * 1997-07-31 2000-04-25 Cisco Technology, Inc. Content-based filtering of multicast information
CN1147145C (en) * 1997-12-01 2004-04-21 星视电视广播公司 Electronic program guide system with advertising message in pop-ups
US6718387B1 (en) * 1997-12-10 2004-04-06 Sun Microsystems, Inc. Reallocating address spaces of a plurality of servers using a load balancing policy and a multicast channel
US6311165B1 (en) * 1998-04-29 2001-10-30 Ncr Corporation Transaction processing systems
US6040829A (en) * 1998-05-13 2000-03-21 Croy; Clemens Personal navigator system
US7370114B1 (en) * 1998-09-11 2008-05-06 Lv Partners, L.P. Software downloading using a television broadcast channel
JP2000156658A (en) 1998-11-19 2000-06-06 Nec Corp Terminal program update system, its method and recording medium
GB9826697D0 (en) 1998-12-05 1999-01-27 Philips Electronics Nv Television receiver
JP3644009B2 (en) * 1999-02-19 2005-04-27 富士通株式会社 Multicast session management device
US6278995B1 (en) * 1999-03-02 2001-08-21 Nms Communications Corporation Apparatus and method for providing a binary range tree search
JP3633356B2 (en) * 1999-03-31 2005-03-30 株式会社日立製作所 Server apparatus, service control gateway apparatus, service control apparatus, and communication control method
US6938270B2 (en) * 1999-04-07 2005-08-30 Microsoft Corporation Communicating scripts in a data service channel of a video signal
US6460180B1 (en) * 1999-04-20 2002-10-01 Webtv Networks, Inc. Enabling and/or disabling selected types of broadcast triggers
US6839348B2 (en) * 1999-04-30 2005-01-04 Cisco Technology, Inc. System and method for distributing multicasts in virtual local area networks
US7051357B2 (en) * 1999-05-28 2006-05-23 Intel Corporation Communicating ancillary information associated with a plurality of audio/video programs
US6415438B1 (en) * 1999-10-05 2002-07-02 Webtv Networks, Inc. Trigger having a time attribute
US7284261B1 (en) * 1999-10-05 2007-10-16 Intel Corporation Broadcasting and processing multiple data formats
US20010003212A1 (en) * 1999-10-29 2001-06-07 Jerilyn L. Marler Identifying ancillary information associated with an audio/video program
US6557111B1 (en) * 1999-11-29 2003-04-29 Xerox Corporation Multicast-enhanced update propagation in a weakly-consistant, replicated data storage system
US7174562B1 (en) * 1999-12-20 2007-02-06 Microsoft Corporation Interactive television triggers having connected content/disconnected content attribute
US7237253B1 (en) * 2000-04-27 2007-06-26 Microsoft Corporation User interface for interactive television systems
US7720903B1 (en) * 2000-08-31 2010-05-18 Intel Corporation Client messaging in multicast networks
US7024476B1 (en) * 2000-09-13 2006-04-04 Canon Kabushiki Kaisha Directory-enabled device management
US7263711B1 (en) * 2000-09-18 2007-08-28 Intel Corporation Terminating enhanced television broadcasts

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694163A (en) * 1995-09-28 1997-12-02 Intel Corporation Method and apparatus for viewing of on-line information service chat data incorporated in a broadcast television program
WO1999055088A1 (en) * 1998-04-22 1999-10-28 Siemens Aktiengesellschaft Method for transmitting supplementary information signals in blanking intervals of a video signal, and a device for receiving these supplementary information signals

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Advanced Television Enhancement Forum Specification (ATVEF), Version 1.1 revision 26, (02/02/99)", ATVEF, 2 February 1999 (1999-02-02), XP002142259 *

Also Published As

Publication number Publication date
EP1329083B1 (en) 2009-07-22
KR20030045108A (en) 2003-06-09
CN1471782A (en) 2004-01-28
US20040078826A1 (en) 2004-04-22
EP1329083A1 (en) 2003-07-23
CN100496042C (en) 2009-06-03
MXPA03003505A (en) 2003-08-07
DE60139332D1 (en) 2009-09-03
JP2004512772A (en) 2004-04-22
EP1202520A1 (en) 2002-05-02
US7984471B2 (en) 2011-07-19
AU2002220658A1 (en) 2002-05-06

Similar Documents

Publication Publication Date Title
KR101635890B1 (en) Method for receiving a broadcast signal and broadcast receiver
US7369520B2 (en) Internet protocol address to packet identifier mapping
US20060253544A1 (en) Method of announcing sessions
EP1337071B1 (en) Transmission burst time indications for power saving
EP1791362A2 (en) Method and apparatus for handling an electronic service guide transmission error in a digital video broadcasting system
JP2006528857A (en) How to handle feature availability in broadcasting
EP1329083B1 (en) Methods and devices for the transmission and reception of data in an atvef television system
EP1424853B1 (en) Digital broadcast reception apparatus and communication information transmission method
KR101046867B1 (en) Apparatus and methods, and related products, for performing conditional execution decisions in relation to received services and for generating information messages related to the services
US20090281907A1 (en) Method and arrangement for purchasing streamed media
EP2081360B1 (en) Method for transmitting and receiving notification message and apparatus thereof
CN1279858A (en) System for processing broadcasted signals
WO2005114905A1 (en) Announcing applications in a digital broadcasting system
JP3610534B2 (en) Service selection device
Reimers et al. DVB Data Broadcasting

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2001989002

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020037005041

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2002538639

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: PA/A/2003/003505

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 018178510

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 1020037005041

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2001989002

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWE Wipo information: entry into national phase

Ref document number: 10399987

Country of ref document: US