EP1135882A1 - Selective repetition protocol - Google Patents
Selective repetition protocolInfo
- Publication number
- EP1135882A1 EP1135882A1 EP99963389A EP99963389A EP1135882A1 EP 1135882 A1 EP1135882 A1 EP 1135882A1 EP 99963389 A EP99963389 A EP 99963389A EP 99963389 A EP99963389 A EP 99963389A EP 1135882 A1 EP1135882 A1 EP 1135882A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- message
- protocol
- transmitted
- overhaul
- time
- 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.)
- Withdrawn
Links
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/1809—Selective-repeat protocols
-
- 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/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
-
- 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/1867—Arrangements specially adapted for the transmitter end
- H04L1/188—Time-out mechanisms
Definitions
- MTP Level 2 (Q.703) can also work with transmission media that do not have this property. It is essential for the functioning of the protocol (Basic Error Correction) even when the needle is overhauled that the MTP recognizes after a retransmission request whether a certain message was sent due to the retransmission request (then it is accepted) or whether it was sent before Retransmission request has been sent (then it will be discarded).
- a disadvantage of this protocol is that it does not have a selective retransmission mode, which can be inefficient. The full available bandwidth would also be used without modification of MTP Level 2, which can be a disadvantage.
- MTP Level 2 with Preventive Cyclic Retransmission Method can also work with message overhaul, since no retransmission requests are generated and messages that do not arrive in the correct order are rejected.
- Another disadvantage of the method is poor utilization of the bandwidth.
- TCP which uses IP as the underlying network protocol, also solved the problem. Transmitted blocks that are not acknowledged are retransmitted after the timer expires. Due to the protocol mechanism (only blocks received without gaps), depending on the round trip delay, unnecessary retransmissions occur, even if the acknowledgment timeout is chosen large enough, since the acknowledgment timer often also runs for messages that were correctly received after a lost message.
- the Reliable Data Protocol works in a similar way to TCP with the extension that messages that are not completely received can also be acknowledged.
- the present invention teaches how certain existing protocols can be extended / modified to include efficient, secure data transmission
- the present invention is based on the finding that, for a modern protocol which uses a transmission medium / protocol with possible message overhaul, it is efficient, ie faster
- Loss of an ACK does not lead to a retransmission b) explicit status comparison between sender and receiver c) retransmission of a message only if there is a certain probability that the message is lost d) messages received multiple times must not lead to incorrect behavior e) it should be possible to select parameters be to determine the trade-off between rapid error correction and minimal unnecessary message transmission.
- Another way to fix situation i) is to ignore such messages in general.
- a window could also be defined for ii) that messages which are received outside this window are generally ignored and do not lead to any retransmission requests.
- Figure 20 (sheet 40 of 51) for a malfunction (branching into connector D).
- Figure 20 (sheet 40 of 51) of Q.2110 also shows that a message with the properties required in 3ii) normally leads to a retransmission request (U ⁇ TAT). In turn, this usually leads to a branch in the error branch (connector D) in Figure 20 (sheet 43 of 51).
- an SD-PDU with repeated transmission is specifically identified, e.g. by setting bit 5 in the PDU trailer (see Figure 3 / Q.2110) to 1.
- Figure 20 sheet 40 of 51
- Figure 20 is modified in such a way that in both error situations described above it is first checked whether the SD-PDU is marked as repeated. In this case, the message is ignored and no misconduct can occur.
- Figure 20 (sheet 40 of 51) is modified so that error case 3i) is generally not checked and a message that has already been received is simply ignored. Furthermore, also in Figure 20 (sheet 40 of 51) after the query VR (H) ⁇ VR (MR) checks whether, for example, SD.N (S) ⁇ VR (R) + 2 ** 23. (This assumes that the window size used for flow control is always smaller than 2 ** 23, but this is not a relevant restriction.) If this is not the case, the message is discarded, otherwise it is handled as before.
- VR (H) ⁇ VR (MR) checks whether, for example, SD.N (S) ⁇ VR (R) + 2 ** 23. (This assumes that the window size used for flow control is always smaller than 2 ** 23, but this is not a relevant restriction.) If this is not the case, the message is discarded, otherwise it is handled as before.
- Point e can also be easily reached with SSCOP, e.g. USTATs could only be sent with a certain time delay in order to wait for messages that have been overhauled. Furthermore, with / at a STAT, only gaps that have existed for a certain time could be reported (or observed).
Abstract
The inventions shows how certain existing protocols can be enlarged/modified in order to guarantee an efficient, secure data transmission via transmission media/protocols, whereby message overhaul can occur. The invention relates to a method by means of which a message, which has been transmitted for at least the second time, is particularly marked by the transmitter. The message which is marked as transmitted for at least the second time is ignored by the receiver when said message has already been received or is new.
Description
Beschreibungdescription
SELEKTIVES WIEDERHOLUNGSPROTOKOLSELECTIVE REPEAT PROTOCOL
1. Welches technische Problem soll durch Ihre Erfindung gelöst werden?1. What technical problem should your invention solve?
2. Wie wurde dieses Problem bisher gelöst?2. How has this problem been solved so far?
3. In welcher Weise löst Ihre Erfindung das angegebene technische Problem ? 4. Ausführungsbeispiel (e) der Erfindung.3. How does your invention solve the stated technical problem? 4. Embodiment (s) of the invention.
1. Viele Ubertragungsmedien/-protokolle haben die Eigenschaft, daß Nachrichten, welche vom Sender dem Medium übergeben werden, beim Empfänger in gleicher Weise ankommen (vorausgesetzt, sie kommen an) , in der sie ausgesendet wurden. M.a.W., eine Nachrichtenüberholung findet nicht statt. Viele Protokolle, die für eine gesicherte Nachrichtenübertragung gewährleisten, setzen diese Eigenschaft bei den von ihnen verwendeten unterliegenden Übertragungsmedien/-protokollen voraus, da diese Eigenschaft es wesentlich erleichtert, eine effiziente, gesicherte Nachrichtenübertragung zu gewährleisten. Das Problem ist nun, Protokolle für eine gesicherte Nachrichtenübertragung zu definieren, welche ohne diese Eigenschaft auskommen.1. Many transmission media / protocols have the property that messages which are transferred from the sender to the medium arrive at the recipient in the same way (provided they arrive) in which they were sent. M.a.W., there is no news overhaul. Many protocols that ensure secure message transmission require this property in the underlying transmission media / protocols that they use, since this property makes it much easier to ensure efficient, secure message transmission. The problem now is to define protocols for secure message transmission that do not need this property.
2. Folgende Methoden werden dafür verwendet bzw. können dafür verwendet werden:2. The following methods are used for this:
Obwohl der MTP Standard (siehe Q.700 bis Q.706) Übertragungsmedien voraussetzt, auf denen eine Nachrichtenüberholung nicht passieren kann, kann der MTP Level 2 (Q.703) auch mit Übertragungsmedien funktionieren, welche diese Eigenschaft nicht haben. Wesentlich für das Funktionieren des Protokolls (Basic Error Correction) auch bei Nadhrichtenüberholung ist, daß der MTP nach einem Retransmissionrequest erkennt, ob eine bestimmte Nachricht aufgrund des Retransmissionrequests gesendet wurde (dann wird sie akzeptiert) , oder ob sie noch vor dem
Retransmissionrequest gesendet wurde (dann wird sie verworfen) . Ein Nachteil dieses Protokolls ist jedoch, daß es keinen selective retransmission Modus besitzt, was ineffizient sein kann. Auch würde ohne Modifikation des MTP Level 2 die volle, zur Verfügung stehende Bandbreite verwendet, was von Nachteil sein kann.Although the MTP standard (see Q.700 to Q.706) requires transmission media on which message overhaul cannot happen, MTP Level 2 (Q.703) can also work with transmission media that do not have this property. It is essential for the functioning of the protocol (Basic Error Correction) even when the needle is overhauled that the MTP recognizes after a retransmission request whether a certain message was sent due to the retransmission request (then it is accepted) or whether it was sent before Retransmission request has been sent (then it will be discarded). A disadvantage of this protocol, however, is that it does not have a selective retransmission mode, which can be inefficient. The full available bandwidth would also be used without modification of MTP Level 2, which can be a disadvantage.
Auch MTP Level 2 mit Preventive Cyclic Retransmission Methode kann mit Nachrichtenüberholung funktionieren, da keine Retransmissionrequests generiert werden und Nachrichten, welche nicht in der richtigen Reihenfolge eintreffen, verworfen werden. Nachteil der Methode ist wiederum eine schlechte Ausnutzung der Bandbreite.MTP Level 2 with Preventive Cyclic Retransmission Method can also work with message overhaul, since no retransmission requests are generated and messages that do not arrive in the correct order are rejected. Another disadvantage of the method is poor utilization of the bandwidth.
Auch TCP, welcher IP als darunterliegendes Netzwerkprotokoll verwendet, hat das Problem gelöst. Übertragene Blöcke, welche nicht acknowledged werden, werden nach Timerablauf neu gesendet. Aufgrund des Protokollmechanismus (nur lückenlos empfangene Blöcke acknowledged) kommt es, in Abhängigkeit des Roundtripdelays, zu unnötigen Retransmissions, selbst wenn das Acknowledgementtimeout groß genug gewählt wird, da der Acknowledgmenttimer oft auch für Nachrichten abläuft, welche nach einer verlorenen Nachricht korrekt empfangen wurden.TCP, which uses IP as the underlying network protocol, also solved the problem. Transmitted blocks that are not acknowledged are retransmitted after the timer expires. Due to the protocol mechanism (only blocks received without gaps), depending on the round trip delay, unnecessary retransmissions occur, even if the acknowledgment timeout is chosen large enough, since the acknowledgment timer often also runs for messages that were correctly received after a lost message.
Durch Methoden wie Fast Retransmission und explizitem NACK beim ersten Auftreten einer Lücke wird die Situation etwas verbessert.The situation is somewhat improved by methods such as fast retransmission and explicit NACK the first time a gap occurs.
Das Reliable Data Protocoll funktioniert ähnlich wie TCP mit der Erweiterung, daß auch nicht lückenlos empfangen Nachrichten quittiert werden können.The Reliable Data Protocol works in a similar way to TCP with the extension that messages that are not completely received can also be acknowledged.
3. Der vorliegende Erfindung lehrt, wie gewisse existierende Protokolle erweitert/modifiziert werden können, um eine effiziente, gesicherte Datenübertragung über3. The present invention teaches how certain existing protocols can be extended / modified to include efficient, secure data transmission
Übertragungsmedien/-protokolle, bei denen es zu Nachrichtenüberholung kommen kann, zu gewährleisten.
Der vorliegenden Erfindung liegt dabei die Erkenntnis zugrunde, daß für ein modernes Protokoll, welches über einem Übertragungsmedium/-protokoll mit möglicher Nachrichtenüberholung effizient, d.h. rascherEnsure transmission media / protocols that can cause message overhaul. The present invention is based on the finding that, for a modern protocol which uses a transmission medium / protocol with possible message overhaul, it is efficient, ie faster
Verlusterkennung bei Minimierung der unnötig übertragenen Information, funktionieren soll, folgende Eigenschaften vorteilhaft sind: a) multiple selective retransmission Methode ohne voller Abhängigkeit von einem Timer; im Speziellen sollte derLoss detection while minimizing the unnecessarily transmitted information, should work, the following properties are advantageous: a) multiple selective retransmission method without full dependence on a timer; in particular the
Verlust eines ACKs nicht zu einer Retransmission führen b) expliziter Statusabgleich zwischen Sender und Empfänger c) Retransmission einer Nachricht nur wenn eine gewisse Wahrscheinlichkeit besteht, daß die Nachricht verloren ist d) mehrfach erhaltene Nachrichten dürfen zu keinem Fehlverhalten führen e) es sollte über Parameterwertewahl möglich sein, den Trade- off zwischen rascher Fehlerkorrektur und minimaler unnötiger Nachrichtenübertragung zu bestimmen.Loss of an ACK does not lead to a retransmission b) explicit status comparison between sender and receiver c) retransmission of a message only if there is a certain probability that the message is lost d) messages received multiple times must not lead to incorrect behavior e) it should be possible to select parameters be to determine the trade-off between rapid error correction and minimal unnecessary message transmission.
Der wichtigste dieser Punkte ist der Punkt d) . Im speziellen gibt es zwei Möglichkeiten, daß wiederholt empfangene Nachrichten Fehlverhalten verursachen: i) die Nachricht wird als bereits empfangen erkannt und dies ist laut Protokoll als Fehler definiert ii) die Nachricht wird als neue Nachricht interpretiert und löst eine Aktion aus, welche später als Konsequenz beim Sender oder Empfänger zum Erkennen eines Fehlers führt. Z.B. kann durch so eine Nachricht ein vermeintlicher Nachrichtenverlust erkannt werden. Dieser führt zu einemThe most important of these points is point d). In particular, there are two possibilities that repeatedly received messages cause malfunctions: i) the message is recognized as already received and this is defined as an error according to the protocol ii) the message is interpreted as a new message and triggers an action which is later a consequence leads to the detection of an error at the transmitter or receiver. For example, a supposed message loss can be recognized by such a message. This leads to one
Retransmissionrequest für Nachrichten, welche noch gar nicht gesendet wurden, was der Sender als Fehler interpretiert.Retransmission request for messages that have not yet been sent, which the sender interprets as an error.
Eine Möglichkeit in Protokollen, welche den anderen Punkten ausreichend genügen, nicht aber Punkt d) , den Punkt d) zu garantieren ist es, eine Nachricht, welche zum zweiten oder öfteren Male übertragen wird, speziell zu kennzeichnen. Dann
können solche Protokolle leicht dahingehend geändert werden, daß solche Nachrichten in den unter i) und ii) beschriebenen Situationen einfach ignoriert werden.One possibility in protocols which sufficiently satisfy the other points, but not point d), to guarantee point d) is to specifically mark a message which is transmitted for the second or more times. Then Such protocols can easily be changed so that such messages are simply ignored in the situations described under i) and ii).
Eine andere Möglichkeit, die Situation i) zu beheben ist, solche Nachrichten generell zu ignorieren. Für ii) könnte auch ein Fenster definiert werden, daß Nachrichten, welche außerhalb dieses Fensters empfangen werden, generell ignoriert werden und zu keinen Retransmissionrequests führen.Another way to fix situation i) is to ignore such messages in general. A window could also be defined for ii) that messages which are received outside this window are generally ignored and do not lead to any retransmission requests.
4. Als Ausführungsbeispiel wird das in Q.2110 beschrieben Protokoll (SSCOP) gewählt. Dieses Protokoll erfüllt die Eigenschaften 3a, 3b, und 3c, hat aber die unter 3i) und 3ii) beschriebenen Probleme. Im speziellen führt 3i) in der4. The protocol (SSCOP) described in Q.2110 is chosen as the exemplary embodiment. This protocol fulfills the properties 3a, 3b, and 3c, but has the problems described under 3i) and 3ii). In particular, 3i) leads in the
Q.2110, Figure 20 (sheet 40 of 51) auf ein Fehlverhalten (Verzweigung in den Connector D) . Ebenso sieht man in Figure 20 (sheet 40 of 51) der Q.2110, daß eine Nachricht mit der in 3ii) vorausgesetzten Eigenschaft normalerweise zu einem Retransmissionrequest (UΞTAT) führt. Dieser wiederum führt normalerweise in Figure 20 (sheet 43 of 51) zu einer Verzweigung in den Fehlerzweig (Connector D) .Q.2110, Figure 20 (sheet 40 of 51) for a malfunction (branching into connector D). Figure 20 (sheet 40 of 51) of Q.2110 also shows that a message with the properties required in 3ii) normally leads to a retransmission request (UΞTAT). In turn, this usually leads to a branch in the error branch (connector D) in Figure 20 (sheet 43 of 51).
In einer Ausführung der Erfindung wird nun gemäß 3) eine SD-PDU bei wiederholter Übertragung speziell gekennzeichnet, z.B. indem Bit 5 im PDU Trailer (siehe Figure 3/Q.2110) auf 1 gesetzt wird. Figure 20 (sheet 40 of 51) wird dahingehend modifiziert, daß in beiden oben beschriebenen Fehlersituationen zuerst gecheckt wird, ob die SD-PDU als wiederholt gekennzeichnet ist. In diesem Fall wird die Nachricht ignoriert und es kann zu keinem Fehlverhalten kommen.In one embodiment of the invention, according to 3), an SD-PDU with repeated transmission is specifically identified, e.g. by setting bit 5 in the PDU trailer (see Figure 3 / Q.2110) to 1. Figure 20 (sheet 40 of 51) is modified in such a way that in both error situations described above it is first checked whether the SD-PDU is marked as repeated. In this case, the message is ignored and no misconduct can occur.
Alternative wird Figure 20 (sheet 40 of 51) dahingehend modifiziert, daß der Fehlerfall 3i) generell nicht überprüft wird und eine bereits empfangene Nachricht einfach ignoriert wird. Ferner wird, ebenfalls in Figure 20 (sheet 40 of 51)
nach der Abfrage VR(H) < VR(MR) überprüft ob z.B. SD.N(S) < VR(R) + 2**23 ist. (Dies setzt voraus, daß die zur Flußkontrolle verwendete Fenstergröße immer kleiner als 2**23 ist, was aber keine relevante Einschränkung darstellt.) Ist dies nicht der Fall, wird die Nachricht verworfen, ansonsten wie bisher behandelt.Alternatively, Figure 20 (sheet 40 of 51) is modified so that error case 3i) is generally not checked and a message that has already been received is simply ignored. Furthermore, also in Figure 20 (sheet 40 of 51) after the query VR (H) <VR (MR) checks whether, for example, SD.N (S) <VR (R) + 2 ** 23. (This assumes that the window size used for flow control is always smaller than 2 ** 23, but this is not a relevant restriction.) If this is not the case, the message is discarded, otherwise it is handled as before.
Auch der Punkt e) kann bei SSCOP leicht erreicht werden, z.B. könnten USTATs nur mit gewisser zeitlicher Verzögerung gesendet werden, um Nachrichten, welche überholt wurden, abzuwarten. Ferner könnten mit/bei einem STAT nur Lücken gemeldet (bzw. beachtet) werden, die schon für eine gewisse Zeit existieren.
Point e) can also be easily reached with SSCOP, e.g. USTATs could only be sent with a certain time delay in order to wait for messages that have been overhauled. Furthermore, with / at a STAT, only gaps that have existed for a certain time could be reported (or observed).
Claims
1. Verfahren zur gesicherten Datenübertragung, das schichtmäßig über einem Übetragungsverfahren mit möglicher Nachrichtenüberholung abläuft, dadurch gekennzeichnet, daß a) eine Nachricht, welche bereits mindestens zum zweiten Male übertragen wird, von dem Sender speziell gekennzeichnet wird, b) eine Nachricht, welche als mindestens zum zweiten Mal übertragen gekennzeichnet ist, von dem Empfänger ignoriert wird, wenn er die Nachricht als bereits empfangen erkennt oder wenn er die Nachricht als neue Nachricht interpretiert1. A method for secure data transmission, which runs in layers over a transmission method with possible message overhaul, characterized in that a) a message which has already been transmitted at least a second time is specifically identified by the transmitter, b) a message which is considered to be at least is transmitted for the second time, is ignored by the recipient when he recognizes the message as already received or when he interprets the message as a new message
2. Sender-Protokoll, das schichtmäßig über einem Sender- Protokoll mit möglicher Nachrichtenüberholung arbeitet, dadurch gekennzeichnet, daß es eine Nachricht, welche bereits mindestens zum zweiten Male übertragen wird, speziell kennzeichnet.2. Sender protocol, which works in layers over a sender protocol with possible message overhaul, characterized in that it specifically identifies a message which has already been transmitted at least a second time.
3. Empfänger-Protokoll, das schichtmäßig über einem Empfänger-Protokoll mit möglicher Nachrichtenüberholung arbeitet, dadurch gekennzeichnet, daß es eine Nachricht, welche als mindestens zum zweiten Mal übertragen gekennzeichnet ist, ignoriert, wenn es die Nachricht als bereits empfangen erkennt oder wenn es die Nachricht als neue Nachricht interpretiert. 3. Receiver protocol, which works in layers over a receiver protocol with possible message overhaul, characterized in that it ignores a message which is marked as being transmitted at least for the second time, if it recognizes the message as already received or if it recognizes the message Message interpreted as a new message.
4. Empfänger-Protokoll, das schichtmäßig über einem Empfänger-Protokoll mit möglicher Nachrichtenüberholung arbeitet, dadurch gekennzeichnet, daß es eine Nachricht ignoriert, wenn es die Nachricht als bereits empfangen erkennt oder wenn es die Nachricht zwar als neue Nachricht interpretiert, diese jedoch Nachricht außerhalb eines vorgegebenen Fensters liegt. 4. Receiver protocol, which works in layers over a receiver protocol with possible message overhaul, characterized in that it ignores a message if it recognizes the message as already received or if it interprets the message as a new message, but this message outside of a given window.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE19856078 | 1998-12-04 | ||
| DE19856078 | 1998-12-04 | ||
| PCT/EP1999/009496 WO2000035139A1 (en) | 1998-12-04 | 1999-12-04 | Selective repetition protocol |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| EP1135882A1 true EP1135882A1 (en) | 2001-09-26 |
Family
ID=7890036
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP99963389A Withdrawn EP1135882A1 (en) | 1998-12-04 | 1999-12-04 | Selective repetition protocol |
Country Status (2)
| Country | Link |
|---|---|
| EP (1) | EP1135882A1 (en) |
| WO (1) | WO2000035139A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5610595A (en) * | 1991-12-09 | 1997-03-11 | Intermec Corporation | Packet radio communication system protocol |
| US5745685A (en) * | 1995-12-29 | 1998-04-28 | Mci Communications Corporation | Protocol extension in NSPP using an acknowledgment bit |
| SG74018A1 (en) * | 1996-07-18 | 2000-07-18 | Matsushita Electric Ind Co Ltd | Retransmission control method |
| US6011796A (en) * | 1997-06-17 | 2000-01-04 | Qualcomm Incorporated | Extended range sequence numbering for selective repeat data transmission protocol |
-
1999
- 1999-12-04 WO PCT/EP1999/009496 patent/WO2000035139A1/en not_active Application Discontinuation
- 1999-12-04 EP EP99963389A patent/EP1135882A1/en not_active Withdrawn
Non-Patent Citations (1)
| Title |
|---|
| See references of WO0035139A1 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2000035139A1 (en) | 2000-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| DE69921512T2 (en) | communication method | |
| DE60132735T2 (en) | Error correction transmission method for transmitting data packets in a network communication system | |
| DE69935554T2 (en) | A method and computer program product for efficiently and reliably transferring small data messages from a sending system to a large number of receiving systems | |
| DE69531410T2 (en) | MORE COMPUTER ENVIRONMENTS | |
| DE10066463B4 (en) | Method of communication with delayed acknowledgment and alarm management | |
| DE2258623A1 (en) | ERROR PROTECTION ARRANGEMENT FOR MESSAGE TRANSMISSION | |
| DE2246826A1 (en) | SYSTEM FOR SECURE BLOCK TRANSFER OF BINARY CODED DATA | |
| EP1061688A2 (en) | Method for retransmitting messages in a centrally-controlled communication network | |
| DE60113766T2 (en) | System and method for data transmission in two modes and corresponding transmitter and receiver | |
| DE60036121T2 (en) | High-speed connection for embedded systems in a computer network | |
| DE10026927B4 (en) | Method for transmitting data packets in a communication system between a transmitter and a receiver and corresponding transmitter and receiver | |
| EP1135882A1 (en) | Selective repetition protocol | |
| EP1064590A1 (en) | Shortened data message of an automation system | |
| DE2246825C3 (en) | System and operating procedures for secure data transmission | |
| DE1207425B (en) | Method for the secure transmission of binary coded data | |
| EP1527547B1 (en) | Method and device for monitoring a data transmission | |
| EP0406741B1 (en) | Quasi-synchronous decision method for channel changing | |
| DE2542846C3 (en) | Method for data transmission between two stations in duplex or half-duplex operation with automatic error correction by querying and repeating the characters received with interference | |
| DE69820444T2 (en) | Automatic repeat request protocol of "go-back-N" type via virtual connections | |
| EP0458802B1 (en) | Process for operating a fail safe multicomputer system | |
| EP1262050B1 (en) | Transmitter in a protocol system for transmitting messages | |
| DE60319165T2 (en) | Procedure for the handling of obsolete information units | |
| DE10102435C2 (en) | Data transmission method | |
| DE2650702C3 (en) | Data transmission system for the transmission of data on telecommunication lines | |
| DE60316618T2 (en) | Selective retransmission procedure for an ARQ protocol |
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: 20010417 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
| 17Q | First examination report despatched |
Effective date: 20040312 |
|
| RBV | Designated contracting states (corrected) |
Designated state(s): DE GB IT |
|
| GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
| 18D | Application deemed to be withdrawn |
Effective date: 20061201 |