WO2000038367A1 - Aggregated error recovery in digital broadcasting - Google Patents

Aggregated error recovery in digital broadcasting Download PDF

Info

Publication number
WO2000038367A1
WO2000038367A1 PCT/US1999/029912 US9929912W WO0038367A1 WO 2000038367 A1 WO2000038367 A1 WO 2000038367A1 US 9929912 W US9929912 W US 9929912W WO 0038367 A1 WO0038367 A1 WO 0038367A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
receiver
repair server
faulty
repair
Prior art date
Application number
PCT/US1999/029912
Other languages
French (fr)
Inventor
Donald K. Newell
Raj Yavatkar
John Du
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Priority to AU21891/00A priority Critical patent/AU2189100A/en
Publication of WO2000038367A1 publication Critical patent/WO2000038367A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems

Definitions

  • This invention relates generally to digital broadcasting and more specifically to aggregated error recovery in digital broadcasting.
  • broadcasters are not concerned with error recovery. For example, a television station would not consider rebroadcasting the one second of flicker during a weather report. Because it is now possible, however, to broadcast anything that is in a digital format, such as by satellite or a computer network, other applications may benefit from error recovery.
  • a system includes a receiver and a repair server.
  • the receiver receives data from a data provider and checks the data against a recovery policy defined for the data.
  • the repair server receives a faulty data notification from the receiver and delivers to the receiver corrected data.
  • Other embodiments of the invention include a repair server and a method for correcting faulty data from a previous broadcast.
  • FIGS. 1-3 show systems according to different embodiments of the invention
  • FIG. 4 shows a repair server according to an embodiment of the invention.
  • FIG. 5 shows a flowchart of a method according to an embodiment of the invention.
  • the system of FIG. 1 includes a data provider 101, a plurality of receivers 102, a predetermined region 105, a repair server 103, and a primary repair server 104.
  • the data provider 101 broadcasts data.
  • the data provider may create the data it broadcasts or it may broadcast data received from another source.
  • the plurality of receivers 102 are able to receive the data broadcasted by the data provider.
  • the plurality of receivers 102 are located in the predetermined region 105.
  • the predetermined region 105 is not limited to geographic boundaries.
  • the predetermined region 105 may be a state, a county, or a defined set of receivers that receive the data over the internet with a modem.
  • Each receiver receives the data from the data provider 101 and verifies the data against a recovery policy defined for the data. Upon each receiver finding an error in the data, the repair server 103 is notified.
  • the repair server 103 is also located in the predetermined region 105.
  • the repair server 103 receives a faulty data notification from each receiver that has determined the data the receiver received violates the recovery policy defined for the data.
  • the repair server 103 ensures that the receiver receives corrected data.
  • the receiver receives corrected data from the repair server 103 after having sent the faulty data notification to the repair server 103.
  • the primary repair server 104 receives the faulty data notification that the plurality of receivers 102 sent to the repair server 103.
  • the primary repair server 104 may provide corrected data to each receiver or it may instruct the repair server 103 to provide corrected data.
  • the system described allows the data provider to broadcast data without having to address error recovery. The data provider can thus use its resources for broadcasting only and let the repair servers handle error recovery. The data provider may then broadcast data that might not otherwise have been broadcast.
  • This embodiment includes a data provider 101, a plurality of first receivers 102, a first repair server 103, a plurality of second receivers 206, a second repair server 207, a first predetermined region 105, a second predetermined region 208, and a primary repair server 104.
  • the plurality of first receivers 102, and the first repair server 103 operate as described above for FIG. 1.
  • the data provider 101 broadcasts data that may be received by both regions 105 and 208.
  • the plurality of second receivers 206 are located in the predetermined second region 208.
  • the predetermined second region 208 is distinct from the predetermined first region 105 but may be chosen in the same manner.
  • Each second receiver receives the data from the data provider and checks the data against the recovery policy.
  • the second repair server 207 for the predetermined second region 208 receives faulty data notification from each second receiver that has determined the data the second receiver received violates the recovery policy, and ensures that the second receiver receives corrected data.
  • the second repair server 207 may send the faulty data notification received from a second receiver to the primary repair server.
  • the primary repair server 104 ensures that corrected data will be delivered to the receiver by sending a resend data notification to the data provider 101. Upon receipt of the resend data notification, the data provider 101 then rebroadcasts the data.
  • the second repair server 207 may provide corrected data to each second receiver that needs it.
  • This system includes a hierarchy of repair servers.
  • the first repair server 103 and the second repair server 207 are part of a plurality of repair servers that make up the first-tier 301 of repair servers.
  • Each first-tier repair server is responsible for a plurality of receivers.
  • Each first-tier repair server may receive a faulty data notification from a receiver when the receiver determines that data violates the defined recovery policy and may ensure that the receiver receives corrected data.
  • the first-tier repair server may send the receiver the corrected data.
  • the hierarchy of repair servers further includes a second-tier 302.
  • the second-tier 302 includes at least one second- tier repair server 303.
  • Each second-tier repair server is responsible for at least one repair server from the group of first-tier 301 repair servers.
  • Each second-tier repair server receives a faulty data notification initially sent by a receiver and passed on to the second-tier repair server by a first-tier repair server that is responsible for the receiver.
  • the second-tier repair server Upon receiving a faulty data notification, the second-tier repair server ensures that the receiver receives corrected data.
  • the second-tier repair server may send the corrected data to the receiver.
  • Another embodiment includes at least one primary repair server 104 in the hierarchy.
  • the primary repair server receives faulty data notifications from at least one second-tier repair server and ensures that the receiver that originally reported the faulty data notification receives corrected data.
  • the primary repair server 104 may request that the data provider 101 resend data.
  • the system shown in FIG. 3 enables allocation of resources for reporting and correcting errors during broadcasting of data. This hierarchy is highly configurable and may be modified easily when implemented. Additional tiers of repair servers may be added.
  • a repair server is shown.
  • the repair server includes a repair server receiver 401 , a determiner 402, and a transmitter 403.
  • the repair server receiver 401 receives faulty data notices.
  • the determiner 402 determines whether the faulty data notices require providing the receivers with corrected data and creates an error report.
  • the transmitter 403 sends the error report.
  • the repair server receiver 401, the determiner 402, and the transmitter 403 may be implemented by hardware or software.
  • the error report is sent to a data provider 101.
  • the error report is sent to a parent repair server 405.
  • the faulty data notices are received from a plurality of receivers 407.
  • the faulty data notices are received from a plurality of child repair servers 406.
  • data is broadcast from a data provider.
  • the data provider may create the broadcasted data or it may get the data from another source prior to broadcasting it.
  • the data may be broadcast in any manner. An example is broadcasting a live interview over the internet.
  • the data is received at a receiver.
  • the receiver can be any device capable of receiving data. It may be a television set or a computer connected to a network.
  • the receiver is informed of its repair server at the start of broadcasting, before broadcasting, or during broadcasting. For example, this reporting can be done by an internet message or by phone.
  • the faulty data is corrected 505.
  • the data can be corrected by the data provider or repair server.
  • the correction can be a rebroadcasting of the data or sending corrected data to a receiver only.
  • the method described permits the data provider to devote its resources to broadcasting data, because the receiver is able to send faulty data notices to a repair server instead of the data provider. Because the repair server does not broadcast data, its resources can be dedicated to handling faulty data notices.
  • the invention described will permit the reliable broadcasting of data which might not be possible otherwise. A broadcaster has limited resources no matter how powerful it is or how fast it can transmit data. By freeing a broadcaster from the task of error recovery, more data can be broadcast reliably.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

Aggregated error recovery in digital broadcasting is disclosed. In one embodiment of this invention a system includes a receiver and a repair server. The receiver receives data from a data provider and checks the data against a recovery policy defined for the data. The repair server receives a faulty data notification from the receiver and delivers to the receiver corrected data.

Description

AGGREGATED ERROR RECOVERY IN DIGITAL BROADCASTING
FIELD
This invention relates generally to digital broadcasting and more specifically to aggregated error recovery in digital broadcasting.
BACKGROUND Broadcasting data is commonplace. Television and radio stations typically come to mind when one thinks of a broadcaster. Applications for data broadcasting continue to grow, however, moving from broadcasting for radio and television to broadcasting for video phones and digital movies, such as by satellite.
For some applications, broadcasters are not concerned with error recovery. For example, a television station would not consider rebroadcasting the one second of flicker during a weather report. Because it is now possible, however, to broadcast anything that is in a digital format, such as by satellite or a computer network, other applications may benefit from error recovery.
When data is sent from a sender to a receiver, the sender can easily resend the data if it is not received properly. However, when the number of receivers grows to a large number, it becomes impractical for the sender to keep track of what receivers did not correctly receive the data and what data needs to be resent to them. In addition, the broadcaster may not have the capacity to correct faulty data that has been received by receivers. Consequently, there is a need for an improved method of error recovery for broadcast data.
SUMMARY The present invention relates to aggregated error recovery in digital broadcasting. In one embodiment of this invention, a system includes a receiver and a repair server. The receiver receives data from a data provider and checks the data against a recovery policy defined for the data. The repair server receives a faulty data notification from the receiver and delivers to the receiver corrected data. Other embodiments of the invention include a repair server and a method for correcting faulty data from a previous broadcast. BRIEF DESCRIPTION OF THE DRAWINGS
FIGS. 1-3 show systems according to different embodiments of the invention;
FIG. 4 shows a repair server according to an embodiment of the invention; and
FIG. 5 shows a flowchart of a method according to an embodiment of the invention.
DETAILED DESCRIPTION The following detailed description of exemplary embodiments and accompanying drawings provide specific examples for how the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be used and logical, mechanical, electrical and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
Referring first to FIG. 1, a system according to an embodiment of the invention is shown. The system of FIG. 1 includes a data provider 101, a plurality of receivers 102, a predetermined region 105, a repair server 103, and a primary repair server 104.
The data provider 101 broadcasts data. The data provider may create the data it broadcasts or it may broadcast data received from another source.
The plurality of receivers 102 are able to receive the data broadcasted by the data provider. The plurality of receivers 102 are located in the predetermined region 105. The predetermined region 105 is not limited to geographic boundaries. For illustrative purposes only, the predetermined region 105 may be a state, a county, or a defined set of receivers that receive the data over the internet with a modem. Each receiver receives the data from the data provider 101 and verifies the data against a recovery policy defined for the data. Upon each receiver finding an error in the data, the repair server 103 is notified.
The repair server 103 is also located in the predetermined region 105. The repair server 103 receives a faulty data notification from each receiver that has determined the data the receiver received violates the recovery policy defined for the data. The repair server 103 ensures that the receiver receives corrected data. In one embodiment, the receiver receives corrected data from the repair server 103 after having sent the faulty data notification to the repair server 103. In another embodiment, there is also a primary repair server 104. The primary repair server 104 receives the faulty data notification that the plurality of receivers 102 sent to the repair server 103. The primary repair server 104 may provide corrected data to each receiver or it may instruct the repair server 103 to provide corrected data. The system described allows the data provider to broadcast data without having to address error recovery. The data provider can thus use its resources for broadcasting only and let the repair servers handle error recovery. The data provider may then broadcast data that might not otherwise have been broadcast.
Referring next to FIG. 2, a system according to an embodiment of the invention is shown. This embodiment includes a data provider 101, a plurality of first receivers 102, a first repair server 103, a plurality of second receivers 206, a second repair server 207, a first predetermined region 105, a second predetermined region 208, and a primary repair server 104. The plurality of first receivers 102, and the first repair server 103 operate as described above for FIG. 1.
The data provider 101 broadcasts data that may be received by both regions 105 and 208.
The plurality of second receivers 206 are located in the predetermined second region 208. The predetermined second region 208 is distinct from the predetermined first region 105 but may be chosen in the same manner. Each second receiver receives the data from the data provider and checks the data against the recovery policy.
The second repair server 207 for the predetermined second region 208 receives faulty data notification from each second receiver that has determined the data the second receiver received violates the recovery policy, and ensures that the second receiver receives corrected data. The second repair server 207 may send the faulty data notification received from a second receiver to the primary repair server. In one embodiment, the primary repair server 104 ensures that corrected data will be delivered to the receiver by sending a resend data notification to the data provider 101. Upon receipt of the resend data notification, the data provider 101 then rebroadcasts the data. Alternatively, the second repair server 207 may provide corrected data to each second receiver that needs it.
Referring next to FIG 3., a system according to an embodiment of the invention is shown. This system includes a hierarchy of repair servers. The first repair server 103 and the second repair server 207 are part of a plurality of repair servers that make up the first-tier 301 of repair servers. Each first-tier repair server is responsible for a plurality of receivers. Each first-tier repair server may receive a faulty data notification from a receiver when the receiver determines that data violates the defined recovery policy and may ensure that the receiver receives corrected data. The first-tier repair server may send the receiver the corrected data. In another embodiment, the hierarchy of repair servers further includes a second-tier 302. The second-tier 302 includes at least one second- tier repair server 303. Each second-tier repair server is responsible for at least one repair server from the group of first-tier 301 repair servers. Each second-tier repair server receives a faulty data notification initially sent by a receiver and passed on to the second-tier repair server by a first-tier repair server that is responsible for the receiver. Upon receiving a faulty data notification, the second-tier repair server ensures that the receiver receives corrected data. The second-tier repair server may send the corrected data to the receiver.
Another embodiment includes at least one primary repair server 104 in the hierarchy. The primary repair server receives faulty data notifications from at least one second-tier repair server and ensures that the receiver that originally reported the faulty data notification receives corrected data. The primary repair server 104 may request that the data provider 101 resend data.
The system shown in FIG. 3 enables allocation of resources for reporting and correcting errors during broadcasting of data. This hierarchy is highly configurable and may be modified easily when implemented. Additional tiers of repair servers may be added. Referring to FIG. 4, a repair server is shown. The repair server includes a repair server receiver 401 , a determiner 402, and a transmitter 403. The repair server receiver 401 receives faulty data notices. The determiner 402 determines whether the faulty data notices require providing the receivers with corrected data and creates an error report. The transmitter 403 sends the error report. The repair server receiver 401, the determiner 402, and the transmitter 403 may be implemented by hardware or software. In one embodiment, the error report is sent to a data provider 101. In another, the error report is sent to a parent repair server 405. In another embodiment, the faulty data notices are received from a plurality of receivers 407. In another, the faulty data notices are received from a plurality of child repair servers 406.
Referring to FIG. 5, a method is shown for correcting faulty data from a previous broadcast. In 501, data is broadcast from a data provider. The data provider may create the broadcasted data or it may get the data from another source prior to broadcasting it. The data may be broadcast in any manner. An example is broadcasting a live interview over the internet. In 502, the data is received at a receiver. The receiver can be any device capable of receiving data. It may be a television set or a computer connected to a network. Next, in 503 it is determined whether the data comprises faulty data. This determination may be done by comparing what was received to what was expected. A checksum might be used. If the data is faulty, the faulty data is reported to a repair server 504. The receiver is informed of its repair server at the start of broadcasting, before broadcasting, or during broadcasting. For example, this reporting can be done by an internet message or by phone. Then, the faulty data is corrected 505. The data can be corrected by the data provider or repair server. The correction can be a rebroadcasting of the data or sending corrected data to a receiver only.
The method described permits the data provider to devote its resources to broadcasting data, because the receiver is able to send faulty data notices to a repair server instead of the data provider. Because the repair server does not broadcast data, its resources can be dedicated to handling faulty data notices. The invention described will permit the reliable broadcasting of data which might not be possible otherwise. A broadcaster has limited resources no matter how powerful it is or how fast it can transmit data. By freeing a broadcaster from the task of error recovery, more data can be broadcast reliably.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the invention as defined in the following claims and equivalents thereof.

Claims

I claim:
1. A system comprising: a receiver for receiving data from a data provider and checking the data against a recovery policy defined for the data; and a repair server for receiving a faulty data notification from the receiver and for delivering to the receiver corrected data.
2. The system of claim 1, wherein the receiver includes logic enabling it to receive data from the repair server after having sent a faulty data notification to the repair server.
3. The system of claim 1 , further comprising a primary repair server for receiving from the repair server a faulty data notification that the repair server received from the receiver.
4. A repair server comprising: a repair server receiver to receive faulty data notices from a receiver; a determiner to determine whether the faulty data notices require providing corrected data to a receiver and to create an error report; and a transmitter to send the error report.
5. The repair server of claim 4, wherein the transmitter includes logic enabling it to send the error reports to a data provider.
A method comprising: receiving data at a receiver; determining whether the data comprises faulty data; and reporting faulty data to a repair server.
The method of claim 6, further comprising correcting the faulty data.
8. The method of claim 7, wherein the step of correcting the faulty data comprises sending corrected data from a repair server to the receiver.
9. A machine readable storage medium having stored therein programming instructions which, when executed by a central processing unit, enable a receiver to receive data, determine whether the data comprises faulty data, report faulty data to a repair server, and receive corrected data.
PCT/US1999/029912 1998-12-21 1999-12-15 Aggregated error recovery in digital broadcasting WO2000038367A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU21891/00A AU2189100A (en) 1998-12-21 1999-12-15 Aggregated error recovery in digital broadcasting

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US21787598A 1998-12-21 1998-12-21
US09/217,875 1998-12-21

Publications (1)

Publication Number Publication Date
WO2000038367A1 true WO2000038367A1 (en) 2000-06-29

Family

ID=22812846

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/029912 WO2000038367A1 (en) 1998-12-21 1999-12-15 Aggregated error recovery in digital broadcasting

Country Status (2)

Country Link
AU (1) AU2189100A (en)
WO (1) WO2000038367A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008100982A1 (en) * 2007-02-16 2008-08-21 At & T Intellectual Property I, L.P. Multicast data packet recovery system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
KASERA S K ET AL: "A comparison of server-based and receiver-based local recovery approaches for scalable reliable multicast", PROCEEDINGS. IEEE INFOCOM '98, THE CONFERENCE ON COMPUTER COMMUNICATIONS. SEVENTEENTH ANNUAL JOINT CONFERENCE OF THE IEEE COMPUTER AND COMMUNICATIONS SOCIETIES. GATEWAY TO THE 21ST CENTURY (CAT. NO.98CH36169), PROCEEDINGS IEEE INFOCOM'98 CONFERENCE O, 29 March 1998 (1998-03-29) - 2 April 1998 (1998-04-02), 1998, New York, NY, USA, IEEE, USA, pages 988 - 995 vol.3, XP002136127, ISBN: 0-7803-4383-2 *
RUBENSTEIN D ET AL: "Improving reliable multicast using active parity encoding services (APES)", IEEE INFOCOM '99. CONFERENCE ON COMPUTER COMMUNICATIONS. PROCEEDINGS. EIGHTEENTH ANNUAL JOINT CONFERENCE OF THE IEEE COMPUTER AND COMMUNICATIONS SOCIETIES. THE FUTURE IS NOW (CAT. NO.99CH36320), PROCEEDINGS OF INFOCOM'99: CONFERENCE ON COMPUTER COMMU, 21 March 1999 (1999-03-21) - 25 March 1999 (1999-03-25), 1999, Piscataway, NJ, USA, IEEE, USA, pages 1248 - 1255 vol.3, XP002136129, ISBN: 0-7803-5417-6 *
XU X R ET AL: "Resilient multicast support for continuous-media applications", PROCEEDING OF THE IEEE 7TH INTERNATIONAL WORKSHOP ON NETWORK AND OPERATING SYSTEMS SUPPORT FOR DIGITAL AUDIO AND VIDEO (CAT. NO.97TH8259), PROCEEDINGS OF 7TH INTERNATIONAL WORKSHOP ON NETWORK AND OPERATING SYSTEM SUPPORT FOR DIGITAL AUDIO AND VIDEO (, 1997, New York, NY, USA, IEEE, USA, pages 183 - 194, XP002136128, ISBN: 0-7803-3799-9 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008100982A1 (en) * 2007-02-16 2008-08-21 At & T Intellectual Property I, L.P. Multicast data packet recovery system

Also Published As

Publication number Publication date
AU2189100A (en) 2000-07-12

Similar Documents

Publication Publication Date Title
US10333759B2 (en) Receiver for receiving data in a broadcast system
US11201692B2 (en) Receiver for receiving data in a broadcast system using redundancy data
JP3908490B2 (en) Retransmission control method and system in multicast distribution service, retransmission control apparatus, radio base station, and radio terminal
US7757146B2 (en) Transmission of data with forward error correction information
US6574795B1 (en) Reliable communication of data by supplementing a unidirectional communications protocol
US11843458B2 (en) Broadcast system and method for error correction using separately received redundant data and broadcast data
US8542593B1 (en) System and methods for error tolerant content delivery over multicast channels
KR100677511B1 (en) Bcast service system and contents transmitting method using the same
EP3269146B1 (en) Permissions management for watermarked data in a broadcast environment
US20150381268A1 (en) System and method for efficient retransmission over a satellite network
US8595581B2 (en) Data reception method, repair method and corresponding terminal
CA2611358A1 (en) Method of processing broadcast signal associated with emergency alert system in terrestrial broadcasting and broadcast receiver for the same
JP2005328267A (en) Content distribution system
US20210385535A1 (en) Apparatus and method for calculating viewer rating by using channel change data
WO2000038367A1 (en) Aggregated error recovery in digital broadcasting
KR101125558B1 (en) The method of downloading files to set-top boxes by digitally broadcasting over the air and transmitting on the internet, the apparatus thereof
KR20060083259A (en) Method and system for short message service
WO2000038358A2 (en) System and method for error detection in data broadcast transmissions using a plurality of monitoring receivers
WO2011152231A1 (en) Broadcast supplemental data transmission device and broadcast supplemental data transmission method, and broadcast system
CN104620525A (en) Method and arrangement for distributing information during broadcast delivery
US20090319846A1 (en) Adaptive error correction method for data transmission and devices thereof
CN101336548A (en) Method and apparatus for handling an electronic service guide transmission error in a digital video broadcasting system
KR20120066988A (en) Message transport system for high available multicast
WO2008082234A1 (en) Method of providing emm for digital mobile broadcasting

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase