EP2039041B1 - Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour - Google Patents

Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour Download PDF

Info

Publication number
EP2039041B1
EP2039041B1 EP07812631.5A EP07812631A EP2039041B1 EP 2039041 B1 EP2039041 B1 EP 2039041B1 EP 07812631 A EP07812631 A EP 07812631A EP 2039041 B1 EP2039041 B1 EP 2039041B1
Authority
EP
European Patent Office
Prior art keywords
receivers
fec
data
packets
errors
Prior art date
Legal status (The legal status 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 status listed.)
Not-in-force
Application number
EP07812631.5A
Other languages
German (de)
English (en)
Other versions
EP2039041A2 (fr
Inventor
William C. Versteeg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
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 Cisco Technology Inc filed Critical Cisco Technology Inc
Publication of EP2039041A2 publication Critical patent/EP2039041A2/fr
Application granted granted Critical
Publication of EP2039041B1 publication Critical patent/EP2039041B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint

Definitions

  • the present disclosure generally relates to communication systems, and more particularly, the disclosure relates to using forward error correction in a communication system.
  • a data packet usually includes a header, data area, and a trailer, wherein the header contains information that directs the packet to the correct receiver or receivers.
  • the header may also include information that can be used to determine a number of packets being transmitted within a data stream. For example, a sequence number may be used for each packet to indicate the sequence of the packet within the stream. Because of any number of problems that may be encountered in a communication system, however, some packets of data do not reach their intended destinations.
  • the receiver When the receiver does not receive certain packets or a certain number of packets as indicated in the header or headers, which can be determined from the sequence numbers, for example, the receiver can determine which packets were missed or the number of packets that were missed. As a result of a receiver missing a number of packets and the information not reaching its intended destination, the integrity of the signals and the communication system as a whole is compromised.
  • FEC forward error correction
  • the FEC code is typically transmitted immediately after the transmission of data and is applied on a different multicast channel.
  • the receiver can handle a certain number of missed packets. If a device receiving the data and FEC determines that it missed one or more packets, then the device uses the FEC code to attempt to correct the missing packets and fill in the gaps. If the amount of FEC code is not enough to correct all the errors, the receiver corrects as much as possible and forwards the data stream, with some missing packets, to the next device. In this respect, incomplete data can be transmitted through the communication system, which is undesirable. Also, many receivers do not contain enough memory to handle a larger amount of FEC.
  • Another solution for handling the problem of missed packets is to allow a receiving device to request for a "re-transmission" of the missed packets.
  • a receiver realized that it missed one or more packets, it can send a re-transmission request back to the sender.
  • the sender can then transmit a unicast transmission of the missing packets to the receiver.
  • this technique may be acceptable when one receiver requests re-transmission, it may experience difficulties when used in a multicast environment. If a sender transmits copies of the data packets to multiple receivers, the sender may also receive numerous re-transmission requests from multiple receivers, especially if there is a widespread problem affecting many transmissions. Too many requests in this situation can overwhelm the sender.
  • An edge device transmitting to multiple receivers in a multicast environment may therefore need to contain complex re-transmission circuitry to handle a potentially large number of requests.
  • WO 2005/112330 discloses performing a statistical analysis of negative acknowledgement messages received by a transmitter from a number of receivers, and determining a level of error protection measures based on the analysis.
  • the error protection measures may include sending redundancy packets and/or resending data packets.
  • the present disclosure describes systems and methods for utilizing forward error correction (FEC) in a communication system.
  • the communication system may be any system or network for transferring data, such as, for example, an Internet protocol television (IPTV) network for carrying digital video signals.
  • IPTV Internet protocol television
  • a first device of the communication system transmits streams of data packets and may also transmit a certain amount of FEC code.
  • the source transmits to one or more intended recipients, referred to herein as receivers, receiving devices, etc.
  • Data is typically transmitted on one multicast channel while the FEC code is transmitted on a multicast channel different from the transmitted data.
  • the receiver when the receiver determines that the FEC code is unable to compensate for missing data packets, the receiver sends a message back to the source including information about the missed packets.
  • the information may include a number of missed packets, a specific identification of the packets that were dropped, or any other suitable message that relays to the source an indication of an error due to dropped or missing packets.
  • the source transmits copies of the data packets to several different receivers. In this case, the source may receive messages concerning dropped packets from many receivers.
  • the source may perform various functions according to the teachings disclosed in the present application.
  • the source may send additional FEC to the receiver, or, in the case of a multicast system, to the multicast group of receivers.
  • a receiver is not able to request additional FEC.
  • the present application overcomes this deficiency by allowing the receiver to make such a request if needed.
  • the source may send redundant data and/or additional FEC in a unicast manner to particular receivers.
  • the source may also determine a strategy for incorporating a combination of multicast and unicast transmission depending on the pattern of error messages from the receivers.
  • the source and receivers may more efficiently transmit data packets through the communication system.
  • the communication system can maintain a desirable level of transmitted FEC to correct errors when they occur.
  • the receivers can correct practically any number of missed packets.
  • the communication system may initially transmit a minimum level of FEC code and then add more FEC to the FEC multicast when needed. In this way, the receivers can receive a sufficient amount of FEC to correct detected errors.
  • FIG. 1 is a block diagram of an embodiment of a communication system 10.
  • the communication system 10 includes a number of communication devices 12 arranged in a multicast configuration.
  • certain communication devices 12 can create copies of the data for transmission to the respective receivers and transmit the data to a group of destinations simultaneously over multiple communication links 14.
  • the source 12 S may be any component in the communication system 10 that transmits data downstream to another device.
  • the source 12 S may be, among others, an edge device, multiplexer, encoder, etc.
  • the source 12 S may be located in a head-end, central office, or other location, and/or may receive data from other sources.
  • the receiver 12 R may be any component in the communication system 10 that receives data from an upstream device.
  • upstream and downstream are used herein to refer to transfer of signals in one particular direction and are merely used for illustrative purposes.
  • the receiver 12 R may be, among others, an end device, such as a computer, set-top box, modem, etc.
  • the receiver 12 R may be located in a customer premises, such as a home, office, school, etc., and/or may distribute data to other downstream receivers.
  • the communication link 14 between the source 12 S and receiver 12 R can be any suitable transmission path or channel and may contain transmission lines, wireless channels, fiber optic, or combinations of these or other types of communication links. Also, other communication devices 12 may be communicatively interposed between the source 12 S and receiver 12 R . In addition, the source and receiver may be located anywhere in the communication system 10 and separated by any distance.
  • data is transmitted to a group of receivers in a first multicast group.
  • the minimum amount of FEC code transmitted with the data is sent in a second multicast group.
  • the receivers configured to tune to the first multicast group are also configured to tune to the second multicast group to receive both data and the minimum amount of FEC code.
  • Additional FEC code transmitted upon a request or requests from the receivers, is sent, in most embodiments, on the second multicast channel. In this respect, the volume of FEC on the second multicast channel is increased to supply the additional FEC code to the receivers.
  • the additional FEC may be transmitted on a third multicast channel. Some or all of the receivers may be configured to tune to the third multicast channel in order to receive the additional FEC as needed.
  • the particular use of multicast channels may be dependent upon the last-mile technology of the communication system 10.
  • the source 12 S and receiver 12 R can be implemented in hardware, software, firmware, or a combination thereof. If the source 12 S and receiver 12 R contain software or firmware for performing the disclosed functions, the software or firmware may be stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, the source 12 S and receiver 12 R can be implemented, for example, with discrete logic circuitry, an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any suitable combinations of logic components.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • FIG. 2 is a block diagram of an embodiment, illustrated in a simplified form, of the source 12 S shown in FIG. 1 .
  • the source 12 S may be configured to operate in conjunction with the receiver 12 R as described below with respect to FIG. 3 or with any suitable receiver having corresponding circuitry and/or functionality for receiving data and forward error correction (FEC) code transmitted in stages as described herein.
  • the source 12 S may be a multiplexer, digital subscriber line access multiplexer (DSLAM), decoder, router, digital contact manager (DCM), video acceleration module (VAM), edge device, or other communication device that transfers data to another location or component.
  • the source 12 S may be located at a head-end facility, central office, node, or at other locations in the communication system 10.
  • the source 12 S includes, among other things, a processor 20, a buffer 22, and a driver 24.
  • the buffer 22 receives streams of data packets from another source or group of sources.
  • the buffer 22 comprises a number of addressable registers (not shown), each register typically configured to temporarily store a single packet from a stream of data packets.
  • the driver 24 may include any suitable component or combination of components for outputting, driving, or transmitting signals to one or more destination devices.
  • the driver 24 may be configured to communicate with one receiver, or, in the case of a multicast system, to multiple receivers.
  • the processor 20 is configured to access the packets from the buffer 22 and calculate FEC code.
  • the processor 20 calculates N "portions" of FEC code (where N can be any number), depending on several factors as explained in more detail below.
  • N can be any number
  • a first portion of FEC code designed to overcome one missed data packet, is referred to as "F1”.
  • a second portion of FEC code designed to overcome two missed data packets when used in conjunction with F1, is referred to as "F2”.
  • Portions F1-F3 are designed to overcome three missed packets, and so on.
  • the processor 20 calculates N portions of FEC code such that the sum of F1 through FN is capable of handling N missed packets. It should be understood, however, that any suitable algorithms for creating FEC may be used. Also, other algorithms may result in FEC code that requires two or more "portions" to overcome each error.
  • the processor 20 stores the calculated portions of FEC code (F1 through FN) in additional registers in the buffer 22.
  • the processor instructs the driver 24 to transmit the data packets and FEC from the buffer 22 along the communication link 14 to the receiver 12 R or receivers.
  • the driver 24 is configured to transmit the FEC immediately before the data, simultaneously with the data, or immediately after the data, on a different multicast channel.
  • the FEC may be interleaved with the data or appended to the data and transmitted on the same multicast channel.
  • other transmission techniques may be used as well.
  • the relationship between the time of transmission of the data and the time of transmission of the FEC may be variable and may depend on certain factors as described herein.
  • the amount of FEC that is initially transmitted with the data may be predetermined.
  • the processor 20 may instruct the driver 24 to output only a minimum amount of FEC code, such as only F1, for example, or even no FEC at all, with the data.
  • the remaining FEC code that is not sent with the data is stored in the buffer 22 until needed, if needed at all.
  • the receiver 12 R receives the data packets and FEC and determines whether or not the initial FEC transmitted with the data is sufficient to correct any detected errors. If so, then the additional FEC in the buffer 22 of source 12 S is not needed, and the processor 20 may delete the unneeded FEC in the buffer 22 or simply allow the registers storing the unneeded FEC code to be overwritten. However, if the receiver 12 R determines that the original FEC is not sufficient to correct all the errors, then the receiver 12 R may send an error indication to the source 12 S , wherein the error indication may be interpreted as a request for additional FEC from the source 12 S . Requests from the receiver 12 R are received by the source 12 S via communication link 26. Communication link 26 may be a dedicated transmission path separate from the communication link 14 or may be associated with the communication link 14.
  • the source 12 S Upon receiving error indication messages from one or more receivers, the source 12 S performs an analysis of the messages. By analyzing multiple requests, the processor 20 can determine a strategy for transmitting additional FEC portions and/or one or more unicasts of data re-transmissions to a number of specific receivers. For example, the additional FEC portions may be sent in the multicast.
  • the FEC portions may include F2-FX, for example, where F1 is initially transmitted with the data and FX is an Xth FEC code portion of the FN portions where X-1 is the number of additional FEC portions.
  • the processor 20 instructs the driver 24 to transmit additional FEC and/or data to the receivers.
  • the processor 20 instructs the driver 24 to transmit F2-FX to a first group of receivers, which may include the receivers in a multicast group in communication with the source 12 S , and to transmit particular data packets to a second group of receivers in one or more unicasts.
  • the first group and second group of receivers may include sets having an overlapping group of receivers or completely distinct sets, depending on the application.
  • Analysis of the error indications may lead the source 12 S to select from a number of previously created FEC portions to determine one or more portions that are capable of correcting forward errors. Also, a first set of FEC portions may be selected for one group of receivers to correct certain errors and a second set of FEC portions may be selected for another group of receivers to correct other errors. The selected FEC portions may be transmitted to the receivers in a multicast or in one or more unicasts, as needed.
  • the possible strategies for analyzing error indications and determining various strategies for transmitting pre-calculated, selected, or customized FEC and/or redundant data in multicast and/or unicast transmission is virtually endless. Regardless of the strategies developed for sufficient error correction, the source 12 S is capable of changing the depth (as defined by N) of the FEC, substantially in real-time, to provide additional error correction on demand. This capability is not achieved in conventional communication devices.
  • FIG. 3 is a block diagram of an embodiment, illustrated in a simplified form, of the receiver 12 R shown in FIG. 1 .
  • the receiver 12 R may operate in conjunction with the source 12 S shown in FIG. 2 or with another respective source having related functionality for transmitting data and FEC in stages.
  • the receiver 12 R may be configured as or incorporated within, among other devices, a set-top box, computer, modem, VAM, etc.
  • the receiver 12 R includes, among other things, a processor 30, a buffer 32, and an input device 34.
  • the input device 34 receives the incoming data packets and FEC and stores it in the buffer 32, which may include registers (not shown). Initially, data is transmitted with a predetermined amount of FEC. This predetermined amount may include, for example, no FEC portions, one FEC portion, a minimum number of FEC portions, or any desirable number of FEC portions, depending on the application.
  • the buffer 32 is typically capable of storing a limited amount of FEC.
  • the processor 30 accesses the data and FEC from the buffer 32 to determine the condition of the received data. By analyzing the header, or particularly the sequence numbers in the headers of the data packets, to determine the packets that were transmitted, the processor 30 can determine if any packets were not received. For example, the processor 30 can determine either the number of packets that were missed or the specific packets that were missed.
  • the receiver 12 R determines how many packets it can afford to lose and still be within the ability of the FEC to correct the errors. If the initially received FEC is sufficient to recover the missed packet or packets, then the transmission is considered a success. In this case, the data is corrected, if necessary, and transmitted to the next component, if any, in the communication system 10.
  • the receiver 12 R may send a message to the source 12 S indicating that errors exist in the received packets. Essentially, the message may be considered a request for more FEC code to recover the missing packets.
  • the receiver 12 R may send the error message to a transmitting device other than the source 12 S from which data packets are received. In this respect, the receiver 12 R can join a multicast group that is not directly related to the source of data packets.
  • the receiver 12 R can download additional FEC code using a file transfer protocol (FTP) type of data exchange. In this case, the receiver 12 R may download from an FTP server not directly related to the source of data packets.
  • FTP file transfer protocol
  • the receiver 12 R may be designed such that it does not have the intelligence to know whether it might expect to receive a data unicast or additional FEC from the source 12 S , in response to the request. Instead, the receiver 12 R simply indicates the presence of errors regarding the particular missing packets or number of packets.
  • the processor 30 informs the source 12 S of the need for more FEC by sending an indication message or request along communication link 26.
  • the processor 30 may indicate the number of FEC portions that are needed or indicate which specific packets are missing.
  • the receiver 12 R can join a particular multicast group to receive any data or FEC that is transmitted on the multicast channel to fill the gaps in the data stream.
  • the source 12 S transmits the missing data or more FEC code to the receiver 12 R , according to the particular embodiments.
  • the input device 34 stores this data or additional FEC in the buffer 32 and the processor 30 can recover or restore the missing packets.
  • the processor 30 sends the data to the next communication device 12.
  • the processor 30 in the receiver 12 R may be configured to calculate new FEC code for the received data and repeat the process that the source 12 S executed to send data to the receiver.
  • the communication system 10 may include a number of communication devices 12 that act as both the source and receiver, as defined according to the teachings herein, to provide additional FEC upon request as data packets are transmitted through the system.
  • the processor 30 calculating new FEC code the FEC code received from a previous source and stored in the buffer 32 may be used during the next transmission to the next receiver.
  • FIG. 4 is a block diagram of an embodiment of the processor 20 of the source 12 S and/or the processor 30 of the receiver 12 R .
  • the processor 20, 30 may include all or some of the components shown in FIG. 4 . If omitted from this embodiment, the corresponding components may be located in the other respective source or receiver processor for accomplishing the various functions described herein. In addition, the corresponding source and receivers may have duplicate components, such that each of the source and receiver can accomplish the various functions as needed. Certain components may be placed in the source and others placed in the receiver, depending on the particular design. Other alternatives and/or modifications to the circuitry will be understood by one of ordinary skill in the art as being within the scope of the present disclosure.
  • the embodiment of the processor of FIG. 4 may include, among other things, a buffer interface 36, an FEC calculating module 38, an error processing module 40, and a request interface 42.
  • the buffer interface 36 is in communication with the buffer 22, 32 for accessing data packets and FEC code stored in the registers.
  • the request interface 42 is in communication with the communication link 26, which is used for transferring requests from the receiver to the source.
  • the FEC calculating module 38 may include any suitable combination of hardware and/or software to achieve the functions described below.
  • the FEC calculating module 38 may be configured together with the error processing module 40 or other hardware and/or software into one unit or can be divided into multiple units.
  • the FEC calculating module 38 receives the data packets from the buffer via the buffer interface 36 and calculates FEC code for correcting errors that may occur during transmission between the transmitter and receiver.
  • the FEC calculating module 38 may utilize any algorithm or combination of algorithms suitable for encoding FEC capable of overcoming missed packets.
  • the calculated FEC code may include FEC portions F1, F2, ... FX, wherein each FEC portion is capable of overcoming one missed packet.
  • the FEC calculating module 38 may create FEC as deeply as needed. If the need for FEC changes over time, the FEC calculating module 38 may be adjusted accordingly.
  • the FEC calculating module 38 instead of calculating new FEC code, may be configured to confirm the validity of FEC code already received from a previous source, in order to reduce the redundancy of calculating the same FEC code.
  • the FEC calculating module 38 stores the FEC code in the buffer 22, 32 via the buffer interface 36.
  • the buffer 22, 32 in which FEC code is stored may be separate from memory from which the processor 20, 30 accesses to compute FEC code.
  • the error processing module 40 corrects the errors, if any.
  • the error processing module 40 may also indicate that the data is acceptable by sending a message to the source 12 S that any or all errors have been corrected and no additional FEC is needed.
  • the error processing module 40 may instruct the FEC calculating module 38 to calculate FEC code, as described above, and may instruct the driver 24 to output the data to the next receiver in order to advance the data through the communication system 10.
  • the FEC calculating module 38 and error processing module 40 of the processor 20, 30 may comprise an ordered listing of executable instructions for implementing logical functions as discussed above.
  • the instructions and programs for executing these functions can be embodied in any computer-readable medium for use in or by an instruction execution system, apparatus, or device.
  • a "computer-readable medium” can be any medium that can contain, store, communicate, propagate, or transport the program for use by the instruction execution system, apparatus, or device.
  • the scope of the present disclosure is intended to include the functionality of the disclosed embodiments configured with logic in hardware and/or software mediums.
  • the total number of FEC portions is R+C, which is sufficient, in some scenarios, to handle up to R+C missed packets, which is an extremely deep FEC.
  • packet (1, 2) were dropped, for example, the dropped packet can be restored using packets (1, 0), (1, 1), (1, 3) through (1, C), and XOR ((1, 0) - (1, C)). Instead of using the row XOR and other packets of the row, packet (1, 2) can also be restored using the packets of the same column and the column XOR.
  • one strategy may be to initially transmit only the row FEC and send the column FEC upon request, or vice versa.
  • Another strategy may be to preemptively create several FEC portions based on different combination or blocks of an array. For example, assuming a particular data stream can be arranged in a 10X10 array, the FEC calculating module 38 may determine an FEC of the entire array in addition to sub-sets of the array, such as a 2X5 sub-set, 3X5 sub-set, 5X10 sub-set, etc. When additional FEC is needed, one or more of the various sub-sets may be selected for transmission to the receivers, based on a known capability of the particular sub-sets to correct certain errors. This strategy may be used, for example, with error correction algorithms such as PRO-MPEG.
  • FIG. 6 is a flow chart of an exemplary process executed, for example, by a source device configured to transmit additional FEC upon request.
  • the flow chart includes receiving a data stream, as indicated in block 50.
  • the data can be received, for example, from an upstream communication device or source.
  • FEC is calculated or encoded for enabling a downstream device to correct the data if necessary.
  • the encoding of FEC may include encoding a maximum amount of FEC to handle a maximum number of missed packets. In other embodiments, this block (block 52) may be omitted if no initial FEC code is transmitted with the data.
  • a minimum amount of FEC may be calculated, and, in this regard, additional FEC may be encoded at a later time, such as after transmission of the data and initial FEC or after receiving error indications, as discussed below.
  • the flow chart includes transmitting the data and a minimum amount of FEC to a downstream receiver.
  • the minimum amount of FEC may be a predetermined amount or may be varied based on changing characteristics or conditions of the communication system. As an example, the minimum amount may be enough FEC code to overcome one missed packet. If the communication system determines that the minimum amount of FEC is not enough or is too much, the minimum amount may be modified.
  • Block 72 includes various processes involved to create or gather additional FEC to be transmitted.
  • additional FEC is calculated in a manner to provide a number N of FEC portions to correct N errors.
  • This block may also include an embodiment where particular FEC code, such as code pre-calculated at an earlier time, is selected or matched based on its ability to correct certain data packets.
  • Another embodiment of block 72 includes creating a customized FEC based on the analysis of block 70 to provide an FEC that sufficiently handles a certain data packet error or combination of data packet errors.
  • the receiver may receive additional FEC portions or data, as indicated in decision block 94. If no data or additional FEC is received, the process flows to block 96, where the existing FEC is used to attempt to correct as many errors as possible. After block 96, flow proceeds to block 100. If it is determined in decision block 96 that data and/or additional FEC code was received, then flow proceeds to block 98 where the data is corrected or restored to its original pre-transmitted form. This block may also include decoding a customized FEC if the source created one. Also, the data is restored by retrieving the data and FEC stored according to block 82 and utilizing this data and FEC along with the newly acquired data and FEC.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (19)

  1. Procédé de correction d'erreurs, comprenant les étapes consistant à :
    recevoir (58, 60) une pluralité d'indications d'erreur en provenance d'une pluralité de récepteurs respectifs, les récepteurs étant configurés de façon à recevoir un flux de données de paquets transmis à l'intérieur d'un canal de multidiffusion, chaque indication d'erreur indiquant les paquets qui n'ont pas été reçus parmi un certain nombre de paquets ; et
    analyser (64) les indications d'erreur afin de déterminer un premier ensemble de récepteurs parmi la pluralité de récepteurs auquel un code de correction d'erreurs sans voie de retour (FEC) est transmis et un second ensemble de récepteurs parmi la pluralité de récepteurs auquel des données de monodiffusion sont transmises ; caractérisé en ce que l'étape consistant à analyser consiste à :
    en réponse à la détermination du fait de savoir si les indications d'erreur acheminent un motif qui peut être représenté par un code FEC personnalisé, créer (66) un code FEC personnalisé sur la base du motif ;
    le procédé comprenant l'étape consistant à transmettre (68) le code FEC personnalisé au premier ensemble de récepteurs.
  2. Procédé selon la revendication 1, comprenant en outre l'étape consistant à transmettre une indication des caractéristiques du code FEC personnalisé afin d'informer les récepteurs de la manière de gérer le code FEC personnalisé.
  3. Procédé selon la revendication 1, comprenant en outre l'étape consistant à :
    transmettre une multidiffusion de FEC supplémentaire au premier ensemble de récepteurs.
  4. Procédé selon la revendication 1, comprenant en outre l'étape consistant à :
    transmettre au moins un paquet de monodiffusion au second ensemble de récepteurs.
  5. Procédé selon la revendication 4, la ou les monodiffusions comportant au moins un paquet non reçu.
  6. Procédé selon la revendication 1, l'étape consistant à analyser les indications d'erreur comprenant une étape consistant à analyser sur la base d'un certain nombre de paquets non reçus par chaque récepteur.
  7. Procédé selon la revendication 1, l'étape consistant à recevoir des indications d'erreur comportant l'étape consistant à recevoir une indication de paquets manquants spécifiques.
  8. Procédé selon la revendication 7, comprenant en outre l'étape consistant à :
    transmettre au premier ensemble de récepteurs une quantité de code FEC afin de corriger un certain nombre d'erreurs sur la base des paquets manquants spécifiques.
  9. Procédé selon la revendication 7, comprenant en outre l'étape consistant à :
    transmettre au second ensemble de récepteurs des données correspondant aux paquets manquants spécifiques.
  10. Procédé selon la revendication 7, comprenant en outre les étapes consistant à :
    transmettre au premier ensemble de récepteurs une quantité de code FEC afin de corriger jusqu'à un premier nombre prédéfini d'erreurs ;
    transmettre au second ensemble de récepteurs des données afin de réparer jusqu'à un second nombre prédéfini d'erreurs ; et
    ignorer un ensemble de récepteurs ayant plus que le second nombre prédéfini d'erreurs.
  11. Procédé selon la revendication 1, comprenant en outre l'étape consistant à :
    transmettre une quantité de code FEC aux premier et second ensembles de récepteurs afin de corriger un nombre maximal de paquets manquants, le nombre maximal étant basé sur le plus grand nombre d'erreurs signalées par l'un des récepteurs.
  12. Dispositif source (12S) destiné à être utilisé dans un système de communication, le dispositif source comprenant :
    une mémoire tampon (22) configurée de façon à mémoriser une pluralité de paquets de données ; et
    un processeur (20) en communication avec la mémoire tampon, le processeur étant configuré de façon à :
    recevoir une pluralité d'indications d'erreur en provenance d'une pluralité de récepteurs respectifs, les récepteurs étant configurés de façon à recevoir un flux de données de paquets transmis à l'intérieur d'un canal de multidiffusion, chaque indication d'erreur indiquant les paquets qui n'ont pas été reçus parmi un certain nombre de paquets ; et
    analyser les indications d'erreur afin de déterminer un premier ensemble de récepteurs parmi la pluralité de récepteurs auquel un code de correction d'erreurs sans voie de retour (FEC) est transmis et un second ensemble de récepteurs parmi la pluralité de récepteurs auquel des données de monodiffusion sont transmises ; caractérisé en ce que l'étape consistant à analyser consiste à, en réponse à la détermination du fait de savoir si les indications d'erreur acheminent un motif qui peut être représenté par un code FEC personnalisé, créer (66) un code FEC personnalisé sur la base du motif ;
    le dispositif étant configuré de façon à transmettre le code FEC personnalisé au premier ensemble de récepteurs.
  13. Dispositif source selon la revendication 12, comprenant en outre un pilote (24) en communication avec la mémoire tampon et le processeur, le pilote étant configuré de façon à transmettre des données depuis la mémoire tampon jusqu'aux récepteurs.
  14. Dispositif source selon la revendication 13, le pilote étant en outre configuré de façon à transmettre la pluralité de paquets de données et une première partie des informations de correction d'erreur.
  15. Dispositif source selon la revendication 14, le pilote étant en outre configuré de façon à transmettre une seconde partie des informations de correction d'erreur sur un canal de multidiffusion correspondant à un canal de multidiffusion sur lequel la première partie des informations de correction d'erreur sont transmises.
  16. Dispositif source selon la revendication 14, le pilote étant en outre configuré de façon à transmettre une seconde partie des informations de correction d'erreur sur un canal de multidiffusion qui est différent d'un canal de multidiffusion sur lequel la première partie des informations de correction d'erreur sont transmises.
  17. Dispositif source selon la revendication 12, le système de communication étant un système de multidiffusion.
  18. Dispositif source selon la revendication 17, le système de multidiffusion étant un système de télévision sur IP (IPTV).
  19. Dispositif source selon la revendication 12, le processeur étant configuré de façon à transmettre une multidiffusion d'informations de correction d'erreur afin de corriger jusqu'à un premier nombre d'erreurs et de façon à transmettre une ou plusieurs monodiffusions de paquets de données spécifiques afin de corriger jusqu'à un second nombre d'erreurs, le second nombre étant supérieur au premier nombre, moyennant quoi un récepteur ayant plus que le second nombre d'erreurs ne reçoit pas suffisamment d'informations de correction d'erreur ou de données pour corriger complètement les erreurs.
EP07812631.5A 2006-07-07 2007-07-05 Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour Not-in-force EP2039041B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/482,439 US7899046B2 (en) 2006-07-07 2006-07-07 Determining strategy for multicast and/or unicast transmission to correct forward errors
PCT/US2007/072819 WO2008006011A2 (fr) 2006-07-07 2007-07-05 Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour

Publications (2)

Publication Number Publication Date
EP2039041A2 EP2039041A2 (fr) 2009-03-25
EP2039041B1 true EP2039041B1 (fr) 2016-04-06

Family

ID=38776133

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07812631.5A Not-in-force EP2039041B1 (fr) 2006-07-07 2007-07-05 Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour

Country Status (4)

Country Link
US (1) US7899046B2 (fr)
EP (1) EP2039041B1 (fr)
CA (1) CA2657174C (fr)
WO (1) WO2008006011A2 (fr)

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070107024A1 (en) * 2005-11-10 2007-05-10 Scientific-Atlanta, Inc. Atomic channel changes in a switched digital video system
US20070106782A1 (en) * 2005-11-10 2007-05-10 Scientific-Atlanta, Inc. Bandwidth management in each network device in a switched digital video environment
US8099756B2 (en) * 2005-11-10 2012-01-17 Versteeg William C Channel changes between services with differing bandwidth in a switched digital video system
US7742407B2 (en) * 2005-11-10 2010-06-22 Scientific-Atlanta, Llc Quality of service management in a switched digital video environment
US7873760B2 (en) 2005-11-11 2011-01-18 Versteeg William C Expedited digital signal decoding
US20080022320A1 (en) * 2006-06-30 2008-01-24 Scientific-Atlanta, Inc. Systems and Methods of Synchronizing Media Streams
US7774672B2 (en) 2006-07-07 2010-08-10 Scientific-Atlanta, Llc Requesting additional forward error correction
US7725797B2 (en) 2006-07-07 2010-05-25 Scientific-Atlanta, Llc Buffer for storing data and forward error correction (FEC)
US7877660B2 (en) * 2006-07-07 2011-01-25 Ver Steeg William C Transmitting additional forward error correction (FEC) upon request
US7870465B2 (en) 2006-10-18 2011-01-11 Versteeg William C Reducing channel-change time
CN101242342B (zh) * 2007-02-05 2012-09-19 华为技术有限公司 组播方法及组播路由方法
US20080244667A1 (en) * 2007-03-27 2008-10-02 Osborne Jason C Bandwidth sensitive switched digital video content delivery
US8370889B2 (en) * 2007-03-28 2013-02-05 Kanthimathi Gayatri Sukumar Switched digital video client reverse channel traffic reduction
US8776160B2 (en) 2007-07-27 2014-07-08 William C. Versteeg Systems and methods of differentiated requests for network access
US8832766B2 (en) * 2007-07-27 2014-09-09 William C. Versteeg Systems and methods of differentiated channel change behavior
TWI357245B (en) * 2007-12-31 2012-01-21 Ind Tech Res Inst System and method for downloading real-time intera
GB0802294D0 (en) * 2008-02-07 2008-03-12 British Telecomm Communications network
WO2009100730A1 (fr) * 2008-02-12 2009-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Commande de transmissions point à multipoint de données de contenu sur une interface radio
US8156234B1 (en) * 2008-02-14 2012-04-10 Trend Micro Incorporated Multicast distribution of computer virus pattern files with fail over mechanism
US8261148B2 (en) 2008-07-28 2012-09-04 At&T Intellectual Property Ii, Lp Internet protocol multicast with internet protocol unicast/multicast error correction
US8042143B2 (en) * 2008-09-19 2011-10-18 At&T Intellectual Property I, L.P. Apparatus and method for distributing media content
US8255779B2 (en) * 2009-05-13 2012-08-28 Applied Micro Circuits Corporation System and method for accelerated forward error correction (FEC) synchronization
US8867539B2 (en) 2009-09-18 2014-10-21 At&T Intellectual Property I, L.P. Multicast-unicast protocol converter
US8150993B2 (en) 2009-10-29 2012-04-03 At&T Intellectual Property I, Lp Synchronization of clients to maximize multicast opportunities
US8397120B2 (en) * 2009-12-15 2013-03-12 Hong Kong Applied Science And Technology Research Institute Co. Ltd. Method of error correction for a multicast message
US8306049B2 (en) * 2010-02-22 2012-11-06 Microsoft Corporation Multicast subscription based on forward error correction
US9015555B2 (en) 2011-11-18 2015-04-21 Cisco Technology, Inc. System and method for multicast error recovery using sampled feedback
US10659082B2 (en) 2014-07-18 2020-05-19 Sony Corporation Receiving device and receiving method
US10045058B2 (en) 2014-10-23 2018-08-07 At&T Intellectual Property I, L.P. Method and apparatus to deliver a personalized media experience
EP3420699A1 (fr) * 2016-02-26 2019-01-02 Net Insight Intellectual Property AB Commande de noeud périphérique
WO2020101639A1 (fr) 2018-11-12 2020-05-22 Nokia Technologies Oy Procédé et appareil de distribution efficiente de flux source et de correction d'erreur directe dans des systèmes prenant en charge une transmission mixte en monodiffusion et multidiffusion

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005112330A1 (fr) * 2004-05-14 2005-11-24 Siemens Aktiengesellschaft Procede, dispositif d'emission et de reception pour transmettre des paquets d'informations numeriques dans un reseau de donnees

Family Cites Families (127)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5572347A (en) 1991-07-30 1996-11-05 Alcatel Network Systems, Inc. Switched video architecture for an optical fiber-to-the-curb telecommunications system
US5594509A (en) 1993-06-22 1997-01-14 Apple Computer, Inc. Method and apparatus for audio-visual interface for the display of multiple levels of information on a display
US5485455A (en) 1994-01-28 1996-01-16 Cabletron Systems, Inc. Network having secure fast packet switching and guaranteed quality of service
JP4204067B2 (ja) 1994-04-15 2009-01-07 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ ビデオ信号の送信及び受信用の回路装置及び方法
US5600663A (en) * 1994-11-16 1997-02-04 Lucent Technologies Inc. Adaptive forward error correction system
EP0714192A1 (fr) 1994-11-24 1996-05-29 International Business Machines Corporation Procédé pour la préemption de connections dans un réseau de commutation de paquets à haute vitesse
US5913031A (en) 1994-12-02 1999-06-15 U.S. Philips Corporation Encoder system level buffer management
US5699369A (en) * 1995-03-29 1997-12-16 Network Systems Corporation Adaptive forward error correction system and method
US5815145A (en) 1995-08-21 1998-09-29 Microsoft Corporation System and method for displaying a program guide for an interactive televideo system
US5808662A (en) 1995-11-08 1998-09-15 Silicon Graphics, Inc. Synchronized, interactive playback of digital movies across a network
US5699365A (en) * 1996-03-27 1997-12-16 Motorola, Inc. Apparatus and method for adaptive forward error correction in data communications
US5793436A (en) 1996-06-17 1998-08-11 Samsung Electronics Co., Ltd. Buffer occupancy control method for use in video buffering verifier
US5870087A (en) 1996-11-13 1999-02-09 Lsi Logic Corporation MPEG decoder system and method having a unified memory for transport decode and system controller functions
US6480541B1 (en) 1996-11-27 2002-11-12 Realnetworks, Inc. Method and apparatus for providing scalable pre-compressed digital video with reduced quantization based artifacts
US6453471B1 (en) 1996-12-13 2002-09-17 Starsight Telecast, Inc. Electronic programming guide with movie preview
US6687906B1 (en) 1996-12-19 2004-02-03 Index Systems, Inc. EPG with advertising inserts
US5949795A (en) 1997-02-14 1999-09-07 General Instrument Corporation Processing asynchronous data within a set-top decoder
US6101221A (en) 1997-07-31 2000-08-08 Lsi Logic Corporation Video bitstream symbol extractor for use in decoding MPEG compliant video bitstreams meeting 2-frame and letterboxing requirements
US6310918B1 (en) 1997-07-31 2001-10-30 Lsi Logic Corporation System and method for motion vector extraction and computation meeting 2-frame store and letterboxing requirements
US6118498A (en) 1997-09-26 2000-09-12 Sarnoff Corporation Channel scanning and channel change latency reduction in an ATSC television receiver
US6307839B1 (en) 1997-12-31 2001-10-23 At&T Corp Dynamic bandwidth allocation for use in the hybrid fiber twisted pair local loop network service architecture
US6538992B1 (en) 1998-02-24 2003-03-25 Nokia Telecommunications Oy Adaptive scheduling method and apparatus to service multilevel QoS in AAL2
US6278716B1 (en) * 1998-03-23 2001-08-21 University Of Massachusetts Multicast with proactive forward error correction
US6119092A (en) 1998-06-26 2000-09-12 Lsi Logic Corporation Audio decoder bypass module for communicating compressed audio to external components
US6252849B1 (en) 1998-06-30 2001-06-26 Sun Microsystems, Inc. Flow control using output port buffer allocation
US6016166A (en) 1998-08-31 2000-01-18 Lucent Technologies Inc. Method and apparatus for adaptive synchronization of digital video and audio playback in a multimedia playback system
US6510553B1 (en) 1998-10-26 2003-01-21 Intel Corporation Method of streaming video from multiple sources over a network
US7185353B2 (en) 2000-08-31 2007-02-27 Prime Research Alliance E., Inc. System and method for delivering statistically scheduled advertisements
US6665751B1 (en) 1999-04-17 2003-12-16 International Business Machines Corporation Streaming media player varying a play speed from an original to a maximum allowable slowdown proportionally in accordance with a buffer state
US6718552B1 (en) 1999-04-20 2004-04-06 Diva Systems Corporation Network bandwidth optimization by dynamic channel allocation
US6594798B1 (en) 1999-05-21 2003-07-15 Microsoft Corporation Receiver-driven layered error correction multicast over heterogeneous packet networks
US6986156B1 (en) 1999-06-11 2006-01-10 Scientific Atlanta, Inc Systems and methods for adaptive scheduling and dynamic bandwidth resource allocation management in a digital broadband delivery system
US7065779B1 (en) 1999-10-13 2006-06-20 Cisco Technology, Inc. Technique for synchronizing multiple access controllers at the head end of an access network
US6173115B1 (en) 1999-11-04 2001-01-09 Thomson Licensing S.A. Record during pause and playback with rewritable disk medium
US6678332B1 (en) 2000-01-04 2004-01-13 Emc Corporation Seamless splicing of encoded MPEG video and audio
US7096481B1 (en) 2000-01-04 2006-08-22 Emc Corporation Preparation of metadata for splicing of encoded MPEG video and audio
US6792047B1 (en) 2000-01-04 2004-09-14 Emc Corporation Real time processing and streaming of spliced encoded MPEG video and associated audio
US6701528B1 (en) 2000-01-26 2004-03-02 Hughes Electronics Corporation Virtual video on demand using multiple encrypted video segments
JP4035806B2 (ja) 2000-01-31 2008-01-23 株式会社日立製作所 映像配信システム
US20030007507A1 (en) 2000-08-01 2003-01-09 Doron Rajwan Data streaming
US6628301B1 (en) 2000-02-16 2003-09-30 Microsoft Corporation Extensible framework for tuning to programming sources
AU2001259075A1 (en) 2000-04-17 2001-10-30 Circadence Corporation System and method for web serving
US6629227B1 (en) 2000-05-04 2003-09-30 Scientific-Atlanta, Inc. System and method for a communication terminal to manage memory and maintain a current application version for multiple applications
FI20001570A (fi) 2000-06-30 2001-12-31 Nokia Corp Synkronoitu palveluntarjonta tietoliikenneverkossa
US6871006B1 (en) 2000-06-30 2005-03-22 Emc Corporation Processing of MPEG encoded video for trick mode operation
US7490344B2 (en) 2000-09-29 2009-02-10 Visible World, Inc. System and method for seamless switching
GB0027812D0 (en) 2000-11-15 2000-12-27 Pace Micro Tech Plc Broadcast data receiver
US7246351B2 (en) 2001-02-20 2007-07-17 Jargon Software System and method for deploying and implementing software applications over a distributed network
US6973667B2 (en) 2001-03-01 2005-12-06 Minerva Networks, Inc. Method and system for providing time-shifted delivery of live media programs
US6970640B2 (en) 2001-05-14 2005-11-29 Microsoft Corporation Systems and methods for playing digital video in reverse and fast forward modes
US20020199203A1 (en) 2001-05-18 2002-12-26 John Duffy Switched digital video gateway
US8291457B2 (en) 2001-05-24 2012-10-16 Vixs Systems, Inc. Channel selection in a multimedia system
US7200855B2 (en) 2001-05-24 2007-04-03 Vixs Systems, Inc. Method and apparatus of multiplexing a plurality of channels in a multimedia system
US7093277B2 (en) 2001-05-30 2006-08-15 Digeo, Inc. System and method for improved multi-stream multimedia transmission and processing
US7277429B2 (en) 2001-06-01 2007-10-02 4198638 Canada Inc. Cell-based switch fabric with distributed scheduling
US7873972B2 (en) 2001-06-01 2011-01-18 Jlb Ventures Llc Method and apparatus for generating a mosaic style electronic program guide
US7114172B2 (en) 2001-06-28 2006-09-26 Koninklijke Philips Electronics N.V. Synchronized personal video recorders
US20030007724A1 (en) 2001-07-05 2003-01-09 Broadcom Corporation System, method, and computer program product for optimizing video service in ethernet-based fiber optic TDMA networks
US20030048808A1 (en) 2001-09-12 2003-03-13 Stahl Thomas Anthony Method and apparatus for changing received streaming content channels
US8713623B2 (en) 2001-09-20 2014-04-29 Time Warner Cable Enterprises, LLC Technique for effectively providing program material in a cable television system
US7426744B2 (en) 2001-09-27 2008-09-16 Broadcom Corporation Method and system for flexible channel association
KR100557167B1 (ko) 2001-11-02 2006-03-03 삼성전자주식회사 이동통신시스템에서의 재전송 장치 및 방법
US7017102B1 (en) * 2001-12-27 2006-03-21 Network Equipment Technologies, Inc. Forward Error Correction (FEC) for packetized data networks
JP3998983B2 (ja) 2002-01-17 2007-10-31 松下電器産業株式会社 ユニキャスト−マルチキャスト変換装置および映像監視システム
WO2003067845A2 (fr) 2002-02-04 2003-08-14 Imagine Broadband Limited Systeme et procede d'emission de contenu media
US20030149975A1 (en) 2002-02-05 2003-08-07 Charles Eldering Targeted advertising in on demand programming
US7266127B2 (en) 2002-02-08 2007-09-04 Lucent Technologies Inc. Method and system to compensate for the effects of packet delays on speech quality in a Voice-over IP system
US7054643B2 (en) 2002-02-20 2006-05-30 Nokia Corporation System for rate control of multicast data delivery in a wireless network
US20030159143A1 (en) 2002-02-21 2003-08-21 Peter Chan Systems and methods for generating a real-time video program guide through video access of multiple channels
US7073117B1 (en) 2002-02-21 2006-07-04 Ciena Corporation Method and apparatus for generating bit errors in a forward error correction (FEC) system to estimate power dissipation characteristics of the system
US6763019B2 (en) 2002-03-05 2004-07-13 Nokia Corporation Method and system for authenticated fast channel change of media provided over a DSL connection
US7246294B2 (en) * 2002-04-01 2007-07-17 Intel Corporation Method for iterative hard-decision forward error correction decoding
US20030196211A1 (en) 2002-04-10 2003-10-16 Peter Chan Systems, methods and apparatuses for simulated rapid tuning of digital video channels
US20090222875A1 (en) 2002-04-18 2009-09-03 Cheng David J Distributed tuner allocation and conflict resolution
KR100454958B1 (ko) 2002-04-18 2004-11-06 삼성전자주식회사 디지털 방송 서비스에서의 채널 변경 방법
US7610606B2 (en) 2002-05-03 2009-10-27 Time Warner Cable, Inc. Technique for effectively providing various entertainment services through a communications network
KR100644978B1 (ko) 2002-09-30 2006-11-14 산요덴키가부시키가이샤 네트워크 전화기 및 음성 복호화 장치
US7281058B1 (en) 2002-10-09 2007-10-09 Juniper Networks, Inc. Delivering and receiving multicast content across a unicast network
US7359939B2 (en) 2002-12-06 2008-04-15 Alcatel Canada, Inc. Fast service restoration for lost IGMP leave requests
US7228356B2 (en) 2002-12-12 2007-06-05 Alcatel Canada Inc. IGMP expedited leave triggered by MAC address
US7584404B2 (en) 2002-12-19 2009-09-01 Intel Corporation Method and apparatus for multimedia communication over packet channels
JP4241066B2 (ja) 2003-01-29 2009-03-18 キヤノン株式会社 予約装置およびその制御方法
WO2004091104A2 (fr) 2003-03-31 2004-10-21 Arris International, Inc. Module multimedia a interfaces multiples a large bande
US7539748B2 (en) 2003-05-16 2009-05-26 Time Warner Cable, A Division Of Time Warner Entertainment Company, L.P. Data transfer application monitor and controller
US7596595B2 (en) 2003-06-18 2009-09-29 Utah State University Efficient unicast-based multicast tree construction and maintenance for multimedia transmission
JP4227509B2 (ja) 2003-12-15 2009-02-18 キヤノン株式会社 通信端末装置及びその制御方法
AU2005208847B2 (en) 2004-01-23 2010-12-02 Camiant, Inc. Policy-based admission control and bandwidth reservation for future sessions
AU2005215010A1 (en) 2004-02-18 2005-09-01 Nielsen Media Research, Inc. Et Al. Methods and apparatus to determine audience viewing of video-on-demand programs
US7430222B2 (en) 2004-02-27 2008-09-30 Microsoft Corporation Media stream splicer
US20050289623A1 (en) * 2004-05-21 2005-12-29 Mowaffak Midani Bulk tuning of frequency-modulated video signals
US8843978B2 (en) 2004-06-29 2014-09-23 Time Warner Cable Enterprises Llc Method and apparatus for network bandwidth allocation
US7848343B2 (en) 2004-07-15 2010-12-07 Calix, Inc. Traffic management for a passive optical network terminal
US9031568B2 (en) 2004-07-28 2015-05-12 Broadcom Corporation Quality-of-service (QoS)-based association with a new network using background network scanning
US7729590B2 (en) 2004-08-03 2010-06-01 Sony Corporation Digital video stream trick play
US7433946B2 (en) 2004-08-12 2008-10-07 Microsoft Corporation Mechanism for transmitting elementary streams in a broadcast environment
US20060074968A1 (en) 2004-10-06 2006-04-06 Gyetko Gregory E Electronic content distribution management methods and systems
US7412149B2 (en) 2004-10-28 2008-08-12 Bitband Technologies, Ltd. Trick mode generation in video streaming
US7447978B2 (en) 2004-11-16 2008-11-04 Nokia Corporation Buffering packets of a media stream
US7873983B2 (en) 2004-11-23 2011-01-18 Palo Alto Research Center Incorporated Method and apparatus for controlling an experiential data stream in a social space
BRPI0516632A (pt) * 2004-12-02 2008-09-16 Thomson Licensing correção de erros antecipada e adaptativa
US7477653B2 (en) 2004-12-10 2009-01-13 Microsoft Corporation Accelerated channel change in rate-limited environments
US7567565B2 (en) 2005-02-01 2009-07-28 Time Warner Cable Inc. Method and apparatus for network bandwidth conservation
US8201205B2 (en) 2005-03-16 2012-06-12 Tvworks, Llc Upstream bandwidth management methods and apparatus
US7668914B2 (en) 2005-03-28 2010-02-23 Alcatel Lucent Milestone synchronization in broadcast multimedia streams
US7823179B2 (en) 2005-04-18 2010-10-26 Cisco Technology, Inc. System and method for edge resource management
US8144724B2 (en) 2005-06-30 2012-03-27 Qualcomm Incorporated Apparatus and method for resolving request collision in a high bandwidth wireless network
US20070044130A1 (en) 2005-08-16 2007-02-22 Alcatel System and method for implementing channel change operations in internet protocol television systems
EP1780971A1 (fr) 2005-10-28 2007-05-02 Koninklijke KPN N.V. Procédé et systéme pour obtenir des informations par un courtier de bande-passante pour contrôle d'accès
US20070107024A1 (en) 2005-11-10 2007-05-10 Scientific-Atlanta, Inc. Atomic channel changes in a switched digital video system
US8099756B2 (en) 2005-11-10 2012-01-17 Versteeg William C Channel changes between services with differing bandwidth in a switched digital video system
US7742407B2 (en) 2005-11-10 2010-06-22 Scientific-Atlanta, Llc Quality of service management in a switched digital video environment
US20070106782A1 (en) 2005-11-10 2007-05-10 Scientific-Atlanta, Inc. Bandwidth management in each network device in a switched digital video environment
US7873760B2 (en) 2005-11-11 2011-01-18 Versteeg William C Expedited digital signal decoding
US8713195B2 (en) 2006-02-10 2014-04-29 Cisco Technology, Inc. Method and system for streaming digital video content to a client in a digital video network
US20070220577A1 (en) 2006-03-15 2007-09-20 Kongalath George P Method and media manager client unit for optimising network resources usage
US20080022320A1 (en) 2006-06-30 2008-01-24 Scientific-Atlanta, Inc. Systems and Methods of Synchronizing Media Streams
US7774672B2 (en) 2006-07-07 2010-08-10 Scientific-Atlanta, Llc Requesting additional forward error correction
US7725797B2 (en) 2006-07-07 2010-05-25 Scientific-Atlanta, Llc Buffer for storing data and forward error correction (FEC)
US7877660B2 (en) 2006-07-07 2011-01-25 Ver Steeg William C Transmitting additional forward error correction (FEC) upon request
US7870465B2 (en) 2006-10-18 2011-01-11 Versteeg William C Reducing channel-change time
KR101465813B1 (ko) 2006-12-20 2014-11-27 톰슨 리서치 펀딩 코포레이션 Ｉｐｔｖ 시스템에서 로우 비트 레이트 스트림을 이용하는 비디오 데이터 손실 복원
US9270944B2 (en) 2007-02-14 2016-02-23 Time Warner Cable Enterprises Llc Methods and apparatus for content delivery notification and management
US7849490B2 (en) 2007-03-12 2010-12-07 Cisco Technology, Inc. Method and apparatus providing scalability for channel change requests in a switched digital video system
US20080244667A1 (en) 2007-03-27 2008-10-02 Osborne Jason C Bandwidth sensitive switched digital video content delivery
US8370889B2 (en) 2007-03-28 2013-02-05 Kanthimathi Gayatri Sukumar Switched digital video client reverse channel traffic reduction
US8832766B2 (en) 2007-07-27 2014-09-09 William C. Versteeg Systems and methods of differentiated channel change behavior
US8776160B2 (en) 2007-07-27 2014-07-08 William C. Versteeg Systems and methods of differentiated requests for network access

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005112330A1 (fr) * 2004-05-14 2005-11-24 Siemens Aktiengesellschaft Procede, dispositif d'emission et de reception pour transmettre des paquets d'informations numeriques dans un reseau de donnees

Also Published As

Publication number Publication date
WO2008006011A2 (fr) 2008-01-10
US20080008167A1 (en) 2008-01-10
CA2657174A1 (fr) 2008-01-10
WO2008006011A3 (fr) 2008-02-28
US7899046B2 (en) 2011-03-01
EP2039041A2 (fr) 2009-03-25
CA2657174C (fr) 2013-08-27

Similar Documents

Publication Publication Date Title
EP2039041B1 (fr) Détermination de stratégie pour une transmission diffusion et/ou monodiffusion en vue de corriger des erreurs sans voie de retour
CA2657178C (fr) Transmission de correction d'erreur sans voie de retour supplementaire (fec) sur demande
CA2657219C (fr) Memoire tampon permettant le stockage des donnees et la correction d'erreurs sans voie de retour
US7774672B2 (en) Requesting additional forward error correction
US9312989B2 (en) Importance-based FEC-aware error-repair scheduling
US7542438B2 (en) Reliable multicast data retransmission method by grouping wireless terminals in wireless communication medium and apparatus for the same
CN101802797B (zh) 生成和传达源标识信息以实现可靠的通信
US8386901B2 (en) Method, device and software application for transmitting data packets in a communication system
US20030226092A1 (en) Method for transmitting and receiving variable length packets based on forward error correction (FEC) coding
US9722763B2 (en) Highly utilized communication channel with order and retransmissions
CN102239658B (zh) 按需差错控制
EP2445162B1 (fr) Procédé de diffusion adaptative
KR102290779B1 (ko) 멀티미디어 데이터를 송수신하는 방법 및 장치
WO2010116616A1 (fr) Appareil de relais et procédé de contrôle de distribution d'un système de distribution de flux
WO2002087140A1 (fr) Canal retour pour emissions de radiodiffusion
Lochina et al. aENAC, University of Toulouse, Toulouse, France, bUniversite de la Reunion, Saint-Denis Reunion, France, cThales Communications, Colombes, France
Tan et al. Hybrid Error Correction schemes under strict delay constraints: Framework, optimization and analysis
Jolfaei et al. Multicopy ARQ strategies for heterogeneous networks
KR20150051395A (ko) 소거회복코드 기반의 멀티 블록 데이터 무선 네트워크 전송 시스템

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080318

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE FR GB NL

17Q First examination report despatched

Effective date: 20091002

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20151007

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CISCO TECHNOLOGY, INC.

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB NL

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602007045677

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20160406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160406

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602007045677

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20170110

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200727

Year of fee payment: 14

Ref country code: GB

Payment date: 20200727

Year of fee payment: 14

Ref country code: DE

Payment date: 20200729

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602007045677

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210705

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210705

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230525