CA2461530A1 - Realtime messages for identifying and preventing errors during the transmission of realtime-critical data - Google Patents
Realtime messages for identifying and preventing errors during the transmission of realtime-critical data Download PDFInfo
- Publication number
- CA2461530A1 CA2461530A1 CA002461530A CA2461530A CA2461530A1 CA 2461530 A1 CA2461530 A1 CA 2461530A1 CA 002461530 A CA002461530 A CA 002461530A CA 2461530 A CA2461530 A CA 2461530A CA 2461530 A1 CA2461530 A1 CA 2461530A1
- Authority
- CA
- Canada
- Prior art keywords
- data
- telegram
- identification
- replacement
- telegrams
- 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.)
- Abandoned
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/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0079—Formats for control data
- H04L1/0082—Formats for control data fields explicitly indicating existence of error in data being transmitted, e.g. so that downstream stations can avoid decoding erroneous packet; relays
Abstract
The invention relates to a method for transmitting real time-critical data using data messages in a data network. The data messages have an identification, useful data and a transfer status. According to the inventiv e method, data messages comprising errors are replaced by replacement messages that have the same structure as the data messages. The replacement message h as the same identification as the data message to be replaced and is thus forwarded via the switching node, which would have been used to route the error-free data message. The replacement message can contain details of the type of transmission error.
Description
2001P17530W0 CA 02461530 2004-03-24 pCT~7DE~2/03406 Description Realtime messages for identifying and preventing errors during the transmission of realtime-critical data The invention relates to a method for identifying and avoiding errors in the transmission of realtime-critical data using data messages in a data network, especially in an automation system.
Data networks are formed from a number of network nodes and allow communication between a number of subscribers. Communication here means the transmission of data between the subscribers . The data to be transmitted in this case is sent as data telegrams, which means that the data is packed into one or more packets and sent in this form over the data network to the appropriate recipient. The term data packet is thus used. The term transmission of data is therefore used in this document synonymously with the above-mentioned transmission of data telegrams or data packets.
For networking in switchable high-performance data networks for example, especially Ethernet, the subscribers are interlinked via coupling nodes. Each coupling node can be connected to more than two subscribers and can also be a subscriber itself. Subscribers are for example computers, Programmable Logic Controllers (PLC) or other machines which exchange electronic data with other machines and especially process it.
A method of transmitting data packets is known from EP~ 0 866 579 A1 in which the data packet is transferred from the transmit station to the receive station, without having an individual identification In distributed automation systems, for example in the area of drive technology, specific data must arrive at specific times at the intended subscribers and must be processed by the recipients. This is referred to as realtime-critical data or realtime-critical data traffic since if the data does not arrive at its intended AMENDED SHEET
2001P17530W0 CA 02461530 2004-03-24 pCTiIDE~2/03406 la destination at the right time this can produce undesired results at the subscriber AMENDED SHEET
WO x3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 de s t i n a t i o n a t t~.e-~.-t-~~--~~s.......o.a~~e._.~.~de,.s-~d -_ t-es.~.l a s..~~
t~_.,..saab~s-c'~''°l~ a r~.
The Use of a synchronous clocked communication system with equidistant characteristics in an automation system is also known from the prior art. This is taken to mean a system consisting of at least two subscribers that are linked via a data network for the purposes of mutual exchange of data or mutual transmission of data.
In this case data is exchanged cyclically in equidistant communication cycles which are specified by the communication clock used by the system. Subscribers are for example central automation devices, e.g., Programmable Logic Controllers (PLC) or other control units, computers or machines which exchange electronic data with other machines and process data, especially from other machines and peripheral devices, e.g.. input/output modules, drives, actors, sensors. In this document control units are taken to mean closed-loop controllers or control units of all types. Typical examples of communication systems used for data transmission are bus systems such as Field Bus, Profibus, Ethernet, Industrial Ethernet, FireWire or also PC-internal bus systems (PCI), etc. In such systems data telegrams are fed into the data network at fixed points for transmission by a subscriber.
Automation components (e. g. controllers, drives, ...) nowadays often have an interface to a cyclically clocked communication system. A
run level of the automation components (fast-cycle) (e. g. positional control in a controller, torque control of the drive) is synchronized to the communication cycle. This defines the communication timing. Other lower-performance algorithms (slow-cycle) (e. g. temperature controllers) of the automation components can also only communicate via this communication clock with other WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 components (e.g. binary switches for fans, pumps, ...), although a slower cycle would be adequate. Using only one communication clock for transmission of all information in the system produces high demands on the bandwidth of the transmission link and on the communications arrangement of the components.
These high demands cannot always be fulfilled and the result can be transmission errors. Possible transmission errors are:
- non-arrival or late arrival of a data telegram;
- overflow of a data buffer in a coupling node;
- incorrect length of a data telegram;
- a physical CRC (Cyclic Redundancy Check) error.
With data networks known from the prior art an incorrect data telegram can trigger an error reaction at all data network nodes via which it is forwarded. Error diagnosis is only possible with the telegrams intended for the purpose. This leads to an additional load on the data network, and makes error diagnosis more difficult and causes delays in diagnosis.
The object of the invention is to avoid error reactions in the transmission path of errored data telegrams and create an improved method of error diagnosis.
The object of the invention is achieved with the features of the Independent patent claims. Specific embodiments of the invention are specified in the dependent patent claims.
In the method in accordance with the invention data telegrams with errors are basically not forwarded. In this case it is to be viewed WO U3/028279 CA 02461530 2004-03-24 PCTIDE~2/03406 as advantageous that the errored data telegram does not trigger error reactions at any further data nodes. Instead of forwarding an errored data telegram a data network node at which no error-free data telegram with a specific identification has arrived by the forwarding time assigned to the identification or is still arriving during the forwarding time sends out a replacement telegram with the identification.
The store-and-forward method and the cut-through method can be used for the forwarding. With the store-and-forward method a data telegram is completely received and is buffered before forwarding By contrast, with the cut-through method, the data is not buffered but is forwarded directly from the receive buffer to the transmit port.
Data telegrams generally have an identification, useful data and a transfer status. Replacement telegrams likewise have an identification, useful data and a transfer status. The identification of the replacement telegram is that of the telegram to be replaced. The useful data can be any data. The transfer status identifies the telegram as a replacement telegram. The transfers status can also specify the type of transmission error that has occurred. It his advantageous that no additional data telegram is needed for error diagnosis.
Replacement telegrams that are received up to the time of forwarding are forwarded by a coupling node like normal data telegrams at the forwarding time via the transmit port assigned to the identification or identifications. In the preferred embodiment of the invention a coupling node can receive and forward a number of data telegrams with the same identification.
WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 In the case of an application it is assumed that initially a data telegram was received at the destination node which is not a replacement telegram and that its useful data and the assigned timer value were stored. If the destination node receives a further data 5 telegram with the same identification it first checks to see whether this is a replacement telegram. If it is, the stored user data and the assigned timer value are basically not replaced. In a preferred embodiment of the invention the arrival of a replacement telegram at the destination node is recorded. If the further data telegram is not a replacement telegram a further check is made on the basis of the timer value as to whether the saved useful data is still current. If the useful data is still current this can be replaced but it does not have to be replaced. If the useful data is not current it is basically replaced by the useful data of the further data telegram. Before the useful data is forwarded to an application of the destination node it must be completely received and buffered since forwarding of the useful data of a data telegram not yet completely received could lead to malfunctions of the application.
Preferred embodiments of the invention are explained in more detail below with reference to the drawings. The drawings show.
Figure 1 a network diagram of a data network in accordance with the invention for transmitting realtime-critical data;
Figure 2 a schematic connection between a source node and a destination node via a coupling node;
WO 03/028279 CA 02461530 2004-03-24 pCTIDE02/03406 Figure 3 the structure of a DTX Ethernet frame from the prior art and an Ethernet frame in accordance with invention;
Figure 4 a flowchart of an inventive method for transferring realtime-critical data with a coupling node;
Figure 5 a flowchart of an inventive method for transferring realtime-critical data at a destination node.
Figure 1 shows a data network in accordance with the invention for transmission of realtime-critical data. The source nodes i are connected directly via the coupling nodes j to the destination nodes k. The data is transmitted via data buses which link data network nodes to each other. A data telegram can for example be forwarded from transmit port 1 of the source node i=1 via the receive buffer 2 and the transmit port 3 of the coupling node j=1 to the receive buffer 4 of the coupling node j=2. But it can also be sent directly from transmit port 5 of the source node i=1 to the receive buffer 4 of the coupling node j=2. It his therefore evident that a data telegram can travel from the source node i=leither via the coupling node j=1 or the coupling node j=2 to the destination node k=1. This shows that both a coupling node and also a destination node can receive identical data telegrams, which can thus also possess an identical identification, via different network paths.
Figure 2 shows a connection between a source node and a destination node via a coupling node. The source node stores data which was identified with the aid of an application of the source node in the form of a data telegram with a specific identification. At the transmit time specified by the identification the data telegram will be transmitted via a transmit port to one or more coupling nodes.
The data telegram is received at a receive buffer of the coupling WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 node. It is then either stored in memory until the time of forwarding (store-and-forward method) or forwarded directly to transmit port (cut-through method) At the time of transmission at the data telegram will be forwarded via a transmission port to further coupling nodes or destination nodes. At the receive port of the destination node it is received, stored on this node and provided for an application of the destination node. The source nodes, coupling nodes and destination nodes are synchronized using a timer.
Figure 3 shows the structure of a DIX Ethernet frame of a data telegram known in the prior art and of an Ethernet frame in accordance with the invention. Header, destination address, source address, realtime type and CRC (cyclic redundancy check) are in the same positions and take up an equal amount of memory space. The DIX
Ethernet frame also includes up to 1.5 kbytes of user data. The same memory space is assigned for the Ethernet frame in accordance with the invention to the user data, data status and transfer status.
The flow diagram in accordance with Figure 4 illustrates the procedural steps in accordance with the invention for transferring realtime-critical data at a coupling node. The coupling node initially expects the arrival of one or more error-free data telegrams DT A, B... with a specific identification (step 6). Their number is taken from the receive list. Data telegrams DT A, B..., which arrive before the forwarding time are initially stored (store-and-forward method, step 7). By contrast data telegrams which are received at the forwarding time are forwarded directly from receive buffer to the send port (cut-through method). Instead of each expected, error-free data telegram which is not received by the forwarding time, a replacement telegram DT A, B... is created with the identification (step 8). At the forwarding time which is taken from the receive list the data telegram or telegrams or the replacement telegrams are forwarded (step 9).
WO ~3~~28279 CA 02461530 2004-03-24 pCTIDE~2/03406 In a preferred embodiment of invention the occurrence of a transmission error is stored at the node at which the transmission error occurred.
Figure 5 illustrates the procedural steps in accordance with the invention for transferring realtime-critical data at a destination node. It is assumed that initially a data telegram DT C, which is not a replacement telegram is received (step 10). The case where the first telegram received is a replacement telegram is not relevant for the intention. The data telegram DT C will be stored with an assigned timer value (step 11). If a further data telegram DT D with the same identification is received at the destination node (step 12) an initial check must be made as to whether this telegram is a replacement telegram (step 13). The useful data of the stored data telegram should basically not be replaced by any data of a replacement telegram. If the data telegram DT D is not a replacement telegram, a check is performed in the next step on the basis of the assigned timer value as to whether the data telegram DT C is current (step 14). A current data telegram DT C can be replaced but does not have to be. If the data telegram DT C is not current its useful data and its assigned timer value are replaced (step 15). In a preferred embodiment of the invention the arrival of a replacement telegram at the destination node is recorded. If the data telegram DT D is a replacement telegram, the data telegram DT C is basically not replaced (step 16).
Data networks are formed from a number of network nodes and allow communication between a number of subscribers. Communication here means the transmission of data between the subscribers . The data to be transmitted in this case is sent as data telegrams, which means that the data is packed into one or more packets and sent in this form over the data network to the appropriate recipient. The term data packet is thus used. The term transmission of data is therefore used in this document synonymously with the above-mentioned transmission of data telegrams or data packets.
For networking in switchable high-performance data networks for example, especially Ethernet, the subscribers are interlinked via coupling nodes. Each coupling node can be connected to more than two subscribers and can also be a subscriber itself. Subscribers are for example computers, Programmable Logic Controllers (PLC) or other machines which exchange electronic data with other machines and especially process it.
A method of transmitting data packets is known from EP~ 0 866 579 A1 in which the data packet is transferred from the transmit station to the receive station, without having an individual identification In distributed automation systems, for example in the area of drive technology, specific data must arrive at specific times at the intended subscribers and must be processed by the recipients. This is referred to as realtime-critical data or realtime-critical data traffic since if the data does not arrive at its intended AMENDED SHEET
2001P17530W0 CA 02461530 2004-03-24 pCTiIDE~2/03406 la destination at the right time this can produce undesired results at the subscriber AMENDED SHEET
WO x3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 de s t i n a t i o n a t t~.e-~.-t-~~--~~s.......o.a~~e._.~.~de,.s-~d -_ t-es.~.l a s..~~
t~_.,..saab~s-c'~''°l~ a r~.
The Use of a synchronous clocked communication system with equidistant characteristics in an automation system is also known from the prior art. This is taken to mean a system consisting of at least two subscribers that are linked via a data network for the purposes of mutual exchange of data or mutual transmission of data.
In this case data is exchanged cyclically in equidistant communication cycles which are specified by the communication clock used by the system. Subscribers are for example central automation devices, e.g., Programmable Logic Controllers (PLC) or other control units, computers or machines which exchange electronic data with other machines and process data, especially from other machines and peripheral devices, e.g.. input/output modules, drives, actors, sensors. In this document control units are taken to mean closed-loop controllers or control units of all types. Typical examples of communication systems used for data transmission are bus systems such as Field Bus, Profibus, Ethernet, Industrial Ethernet, FireWire or also PC-internal bus systems (PCI), etc. In such systems data telegrams are fed into the data network at fixed points for transmission by a subscriber.
Automation components (e. g. controllers, drives, ...) nowadays often have an interface to a cyclically clocked communication system. A
run level of the automation components (fast-cycle) (e. g. positional control in a controller, torque control of the drive) is synchronized to the communication cycle. This defines the communication timing. Other lower-performance algorithms (slow-cycle) (e. g. temperature controllers) of the automation components can also only communicate via this communication clock with other WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 components (e.g. binary switches for fans, pumps, ...), although a slower cycle would be adequate. Using only one communication clock for transmission of all information in the system produces high demands on the bandwidth of the transmission link and on the communications arrangement of the components.
These high demands cannot always be fulfilled and the result can be transmission errors. Possible transmission errors are:
- non-arrival or late arrival of a data telegram;
- overflow of a data buffer in a coupling node;
- incorrect length of a data telegram;
- a physical CRC (Cyclic Redundancy Check) error.
With data networks known from the prior art an incorrect data telegram can trigger an error reaction at all data network nodes via which it is forwarded. Error diagnosis is only possible with the telegrams intended for the purpose. This leads to an additional load on the data network, and makes error diagnosis more difficult and causes delays in diagnosis.
The object of the invention is to avoid error reactions in the transmission path of errored data telegrams and create an improved method of error diagnosis.
The object of the invention is achieved with the features of the Independent patent claims. Specific embodiments of the invention are specified in the dependent patent claims.
In the method in accordance with the invention data telegrams with errors are basically not forwarded. In this case it is to be viewed WO U3/028279 CA 02461530 2004-03-24 PCTIDE~2/03406 as advantageous that the errored data telegram does not trigger error reactions at any further data nodes. Instead of forwarding an errored data telegram a data network node at which no error-free data telegram with a specific identification has arrived by the forwarding time assigned to the identification or is still arriving during the forwarding time sends out a replacement telegram with the identification.
The store-and-forward method and the cut-through method can be used for the forwarding. With the store-and-forward method a data telegram is completely received and is buffered before forwarding By contrast, with the cut-through method, the data is not buffered but is forwarded directly from the receive buffer to the transmit port.
Data telegrams generally have an identification, useful data and a transfer status. Replacement telegrams likewise have an identification, useful data and a transfer status. The identification of the replacement telegram is that of the telegram to be replaced. The useful data can be any data. The transfer status identifies the telegram as a replacement telegram. The transfers status can also specify the type of transmission error that has occurred. It his advantageous that no additional data telegram is needed for error diagnosis.
Replacement telegrams that are received up to the time of forwarding are forwarded by a coupling node like normal data telegrams at the forwarding time via the transmit port assigned to the identification or identifications. In the preferred embodiment of the invention a coupling node can receive and forward a number of data telegrams with the same identification.
WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 In the case of an application it is assumed that initially a data telegram was received at the destination node which is not a replacement telegram and that its useful data and the assigned timer value were stored. If the destination node receives a further data 5 telegram with the same identification it first checks to see whether this is a replacement telegram. If it is, the stored user data and the assigned timer value are basically not replaced. In a preferred embodiment of the invention the arrival of a replacement telegram at the destination node is recorded. If the further data telegram is not a replacement telegram a further check is made on the basis of the timer value as to whether the saved useful data is still current. If the useful data is still current this can be replaced but it does not have to be replaced. If the useful data is not current it is basically replaced by the useful data of the further data telegram. Before the useful data is forwarded to an application of the destination node it must be completely received and buffered since forwarding of the useful data of a data telegram not yet completely received could lead to malfunctions of the application.
Preferred embodiments of the invention are explained in more detail below with reference to the drawings. The drawings show.
Figure 1 a network diagram of a data network in accordance with the invention for transmitting realtime-critical data;
Figure 2 a schematic connection between a source node and a destination node via a coupling node;
WO 03/028279 CA 02461530 2004-03-24 pCTIDE02/03406 Figure 3 the structure of a DTX Ethernet frame from the prior art and an Ethernet frame in accordance with invention;
Figure 4 a flowchart of an inventive method for transferring realtime-critical data with a coupling node;
Figure 5 a flowchart of an inventive method for transferring realtime-critical data at a destination node.
Figure 1 shows a data network in accordance with the invention for transmission of realtime-critical data. The source nodes i are connected directly via the coupling nodes j to the destination nodes k. The data is transmitted via data buses which link data network nodes to each other. A data telegram can for example be forwarded from transmit port 1 of the source node i=1 via the receive buffer 2 and the transmit port 3 of the coupling node j=1 to the receive buffer 4 of the coupling node j=2. But it can also be sent directly from transmit port 5 of the source node i=1 to the receive buffer 4 of the coupling node j=2. It his therefore evident that a data telegram can travel from the source node i=leither via the coupling node j=1 or the coupling node j=2 to the destination node k=1. This shows that both a coupling node and also a destination node can receive identical data telegrams, which can thus also possess an identical identification, via different network paths.
Figure 2 shows a connection between a source node and a destination node via a coupling node. The source node stores data which was identified with the aid of an application of the source node in the form of a data telegram with a specific identification. At the transmit time specified by the identification the data telegram will be transmitted via a transmit port to one or more coupling nodes.
The data telegram is received at a receive buffer of the coupling WO X3/028279 CA 02461530 2004-03-24 pCTIDE~2/03406 node. It is then either stored in memory until the time of forwarding (store-and-forward method) or forwarded directly to transmit port (cut-through method) At the time of transmission at the data telegram will be forwarded via a transmission port to further coupling nodes or destination nodes. At the receive port of the destination node it is received, stored on this node and provided for an application of the destination node. The source nodes, coupling nodes and destination nodes are synchronized using a timer.
Figure 3 shows the structure of a DIX Ethernet frame of a data telegram known in the prior art and of an Ethernet frame in accordance with the invention. Header, destination address, source address, realtime type and CRC (cyclic redundancy check) are in the same positions and take up an equal amount of memory space. The DIX
Ethernet frame also includes up to 1.5 kbytes of user data. The same memory space is assigned for the Ethernet frame in accordance with the invention to the user data, data status and transfer status.
The flow diagram in accordance with Figure 4 illustrates the procedural steps in accordance with the invention for transferring realtime-critical data at a coupling node. The coupling node initially expects the arrival of one or more error-free data telegrams DT A, B... with a specific identification (step 6). Their number is taken from the receive list. Data telegrams DT A, B..., which arrive before the forwarding time are initially stored (store-and-forward method, step 7). By contrast data telegrams which are received at the forwarding time are forwarded directly from receive buffer to the send port (cut-through method). Instead of each expected, error-free data telegram which is not received by the forwarding time, a replacement telegram DT A, B... is created with the identification (step 8). At the forwarding time which is taken from the receive list the data telegram or telegrams or the replacement telegrams are forwarded (step 9).
WO ~3~~28279 CA 02461530 2004-03-24 pCTIDE~2/03406 In a preferred embodiment of invention the occurrence of a transmission error is stored at the node at which the transmission error occurred.
Figure 5 illustrates the procedural steps in accordance with the invention for transferring realtime-critical data at a destination node. It is assumed that initially a data telegram DT C, which is not a replacement telegram is received (step 10). The case where the first telegram received is a replacement telegram is not relevant for the intention. The data telegram DT C will be stored with an assigned timer value (step 11). If a further data telegram DT D with the same identification is received at the destination node (step 12) an initial check must be made as to whether this telegram is a replacement telegram (step 13). The useful data of the stored data telegram should basically not be replaced by any data of a replacement telegram. If the data telegram DT D is not a replacement telegram, a check is performed in the next step on the basis of the assigned timer value as to whether the data telegram DT C is current (step 14). A current data telegram DT C can be replaced but does not have to be. If the data telegram DT C is not current its useful data and its assigned timer value are replaced (step 15). In a preferred embodiment of the invention the arrival of a replacement telegram at the destination node is recorded. If the data telegram DT D is a replacement telegram, the data telegram DT C is basically not replaced (step 16).
Claims (16)
1. Method for transmission of real-time a critical data using data telegrams in a data network with at least one coupling node, in which case the data telegrams feature an identification, useful data and a transfer status and the coupling node features at least a transmit list and a receiver list, with the transmit lists containing information about the number of data telegrams to be received at the corresponding coupling node with specific identifications and the send list containing information about the forwarding time assigned via an identification and one or more transmit ports assigned to an identification, with the following steps:
- Expectation (6) of the receipt of one or more data telegrams with an identification of the forwarding time assigned to the identification at a coupling of node;
- For the case in which one or more data telegrams with the identification was received by the forwarding time:
Forwarding (9) of the data telegram or telegrams via the transmit port or ports of the coupling node assigned to the identification;
- For the case in which one or more expected data telegrams with the identification was not received by the forwarding time: Creation (8) of a replacement telegram for each expected, not received data telegram with the identification and data transfer status that indicates that this telegram is a replacement telegram and of its application (9) via the transmit port or ports of the coupling node assigned to the identification.
- Expectation (6) of the receipt of one or more data telegrams with an identification of the forwarding time assigned to the identification at a coupling of node;
- For the case in which one or more data telegrams with the identification was received by the forwarding time:
Forwarding (9) of the data telegram or telegrams via the transmit port or ports of the coupling node assigned to the identification;
- For the case in which one or more expected data telegrams with the identification was not received by the forwarding time: Creation (8) of a replacement telegram for each expected, not received data telegram with the identification and data transfer status that indicates that this telegram is a replacement telegram and of its application (9) via the transmit port or ports of the coupling node assigned to the identification.
2. Method in accordance with Claim 1, in which case the occurrence of a transmission error is stored at the node at which it occurred.
3. Method in accordance with one of the Claims 1 or 2, with the replacement telegram containing any useful data.
4. Method in accordance with one of the Claims 1 to 3, with the replacement telegram containing information about the type of transmission error that has occurred in the transfer status.
5. Method in accordance with one of the Claims 1 to 4, where a replacement telegram received by a data network node on a data path to a destination node does not trigger an error reaction at the data network node.
6. Method in accordance with one of the Claims 1 to 5 with the following, further steps:
- Receipt (10) of a data telegram at a destination node;
- Storage (11) of the useful data of the first data telegram which is not a replacement telegram and of the assigned timer value;
- Receipt (12) of at least one further data telegram;
- For the case in which the further data telegram is a replacement telegram: no replacement (16) of the stored useful data and of the assigned timer value;
- For the case in which the further data telegram is not a replacement telegram and the stored useful data is no longer current according to the assigned timer value: Replacement (15) of the stored useful data and of the assigned timer value.
- Receipt (10) of a data telegram at a destination node;
- Storage (11) of the useful data of the first data telegram which is not a replacement telegram and of the assigned timer value;
- Receipt (12) of at least one further data telegram;
- For the case in which the further data telegram is a replacement telegram: no replacement (16) of the stored useful data and of the assigned timer value;
- For the case in which the further data telegram is not a replacement telegram and the stored useful data is no longer current according to the assigned timer value: Replacement (15) of the stored useful data and of the assigned timer value.
7. Method in accordance with Claim 6, with the receipt of a replacement telegram at the destination node being stored.
8. Coupling node in a data network for transmission of realtime-critical data by means of data telegrams, in which case each data telegram features an identification, useful data and a transfer status, with:
- a receive list which contains information about the number of data telegrams with specific identifications to be received at the coupling node concerned;
- a receive list which contains information about the forwarding time assigned to an identification and information about at least one transmit port;
- means for receiving one or more data telegrams;
- means for storing the data telegram or telegrams until the transfer time;
- means for forwarding the data telegram or telegrams via the transmit port or transmit ports assigned to the identification;
- means for creating one or more replacement telegrams.
- a receive list which contains information about the number of data telegrams with specific identifications to be received at the coupling node concerned;
- a receive list which contains information about the forwarding time assigned to an identification and information about at least one transmit port;
- means for receiving one or more data telegrams;
- means for storing the data telegram or telegrams until the transfer time;
- means for forwarding the data telegram or telegrams via the transmit port or transmit ports assigned to the identification;
- means for creating one or more replacement telegrams.
9. Coupling node in accordance with Claim 8 with means for storing the occurrence of a transmission error.
10. Coupling node in accordance with Claim 8 or 9, with the replacement telegram to be created containing information about the type of transmission error.
11. Destination node in a data network for transmission of realtime-critical data by means of data telegrams, in which case each data telegram features an identification, useful data and a transfer status, with:
- means for receiving a data telegram;
- means for storing the useful data of a data telegram which is not a replacement telegram and the assigned timer value;
means for receiving at least one further data telegram;
- means for replacing the useful data of the stored, no longer current data telegram with the useful data of a further data telegram which is not a replacement telegram
- means for receiving a data telegram;
- means for storing the useful data of a data telegram which is not a replacement telegram and the assigned timer value;
means for receiving at least one further data telegram;
- means for replacing the useful data of the stored, no longer current data telegram with the useful data of a further data telegram which is not a replacement telegram
12. Destination node in accordance with Claim 11 with means for storing the receipt of a replacement telegram.
13. Data network which features at least one of coupling node in accordance with one of the Claims 8 to 10.
14. Data network in accordance with Claim 13 which features at least one destination node in accordance with Claim 11 or 12.
15. Computer program product for a coupling node in a data network for transmission of realtime-critical data by means of data telegrams, in which case each data telegram features an identification, useful data and a transfer status, for executing a method with the following steps:
- Expecting the receipt of one or more data telegrams with an identification up to the forwarding time assigned to the identification at a coupling node;
- For the case in which one or more data telegrams with the identification was received by the forwarding time:
Forwarding of the data telegram or telegrams via the send port or send ports of the coupling node assigned to the identification;
- For the case in which one or more expected data telegrams with the identification was not received by the forwarding time: Creation of a replacement telegram for each expected, not received data telegram with the identification and data transfer status which indicates that this telegram is a replacement telegram and its transmission via the transmit port or ports of the coupling node assigned to the identification.
- Expecting the receipt of one or more data telegrams with an identification up to the forwarding time assigned to the identification at a coupling node;
- For the case in which one or more data telegrams with the identification was received by the forwarding time:
Forwarding of the data telegram or telegrams via the send port or send ports of the coupling node assigned to the identification;
- For the case in which one or more expected data telegrams with the identification was not received by the forwarding time: Creation of a replacement telegram for each expected, not received data telegram with the identification and data transfer status which indicates that this telegram is a replacement telegram and its transmission via the transmit port or ports of the coupling node assigned to the identification.
16. Computer program product for a destination node in a data network for transmission of realtime-critical data by means of data telegrams, in which case each data telegram features an identification, useful data and a transfer status, for executing a method with the following steps:
- Receipt of a data telegram at a destination node; -Storage of the useful data of the first data telegram which is not a replacement telegram and of the assigned timer value;
- Receipt of at least one further data telegram;
- For the case in which the further data telegram is a replacement telegram: no replacement of the stored useful data and of the assigned timer value;
- For the case in which the further data telegram is not a replacement telegram and the stored useful data is no longer current according to the assigned timer value: Replacement of the stored useful data and of the assigned at timer value;
- Receipt of a data telegram at a destination node; -Storage of the useful data of the first data telegram which is not a replacement telegram and of the assigned timer value;
- Receipt of at least one further data telegram;
- For the case in which the further data telegram is a replacement telegram: no replacement of the stored useful data and of the assigned timer value;
- For the case in which the further data telegram is not a replacement telegram and the stored useful data is no longer current according to the assigned timer value: Replacement of the stored useful data and of the assigned at timer value;
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE10147426 | 2001-09-26 | ||
| DE10147426.1 | 2001-09-26 | ||
| DE10228822.4 | 2002-06-27 | ||
| DE10228822A DE10228822A1 (en) | 2001-09-26 | 2002-06-27 | Replacement telegrams for error detection and error avoidance when transmitting real-time critical data |
| PCT/DE2002/003406 WO2003028279A2 (en) | 2001-09-26 | 2002-09-12 | Forwarding of data messages with double-node data replacement |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2461530A1 true CA2461530A1 (en) | 2003-04-03 |
Family
ID=26010226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002461530A Abandoned CA2461530A1 (en) | 2001-09-26 | 2002-09-12 | Realtime messages for identifying and preventing errors during the transmission of realtime-critical data |
Country Status (8)
| Country | Link |
|---|---|
| US (3) | US7770085B2 (en) |
| EP (1) | EP1430634B1 (en) |
| CN (1) | CN1317841C (en) |
| AT (1) | ATE329424T1 (en) |
| CA (1) | CA2461530A1 (en) |
| DE (1) | DE50207128D1 (en) |
| ES (1) | ES2266570T3 (en) |
| WO (1) | WO2003028279A2 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| SE526872C2 (en) | 2003-05-26 | 2005-11-15 | Infineon Technologies Wireless | Method and arrangement for removing DC offset from data symbols |
| WO2009018768A1 (en) * | 2007-08-07 | 2009-02-12 | Huawei Technologies Co., Ltd. | Method and apparatus of data package forwarding, apparatus of data package generating and communication system |
| CN101364939B (en) * | 2007-08-07 | 2012-08-15 | 华为技术有限公司 | Data packet forwarding method and device, data packet generating device and communication system |
| JP5647119B2 (en) | 2008-08-12 | 2014-12-24 | コーニンクレッカ フィリップス エヌ ヴェ | Communication method, primary station, secondary station and communication system |
| FR2939585B1 (en) * | 2008-12-08 | 2011-02-18 | Canon Kk | ROBUST NETWORK CODING METHOD FOR TRANSMISSION LOSSES IN A MESH NETWORK, RELAY NODE, DESTINATION NODE, COMPUTER PROGRAM PRODUCT, AND CORRESPONDING STORAGE MEDIUM. |
| FR2939584B1 (en) * | 2008-12-08 | 2011-02-18 | Canon Kk | NETWORK CODING METHOD IN MESH NETWORK, COMPUTER SOFTWARE PRODUCT, STORAGE MEDIUM AND CORRESPONDING COMMUNICATION NODES. |
| DE102011084364A1 (en) * | 2011-10-12 | 2013-04-18 | Endress + Hauser Wetzer Gmbh + Co Kg | Method for telegram-based data transmission |
| US10735218B2 (en) * | 2018-05-23 | 2020-08-04 | Beckhofff Automation GmbH | Data transmission method and automation-communication network |
| EP3657758B1 (en) * | 2018-11-20 | 2021-05-26 | Siemens Aktiengesellschaft | Method for functionally secure connection identification |
| DE102019121929A1 (en) * | 2019-08-14 | 2021-02-18 | Beckhoff Automation Gmbh | Network distributors, automation networks and methods for data transmission in an automation network |
Family Cites Families (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CS204190B1 (en) * | 1978-02-22 | 1981-03-31 | Jaroslav Drobnik | Activation method for hydrxyl groups containing insoluble carriers |
| US4494230A (en) * | 1982-06-25 | 1985-01-15 | At&T Bell Laboratories | Fast packet switching system |
| US4970714A (en) * | 1989-01-05 | 1990-11-13 | International Business Machines Corp. | Adaptive data link protocol |
| JPH04107027A (en) * | 1990-08-28 | 1992-04-08 | Fujitsu Ltd | Data transmission system |
| SE466754B (en) * | 1990-09-13 | 1992-03-30 | Berol Nobel Ab | COVALENT BINDING POLYMERS TO HYDROPHILIC SURFACES |
| JPH0783361B2 (en) * | 1991-05-14 | 1995-09-06 | 松下電器産業株式会社 | Ring packet communication network |
| US5588009A (en) * | 1994-02-03 | 1996-12-24 | Will; Craig A. | Personal paging, communications, and locating system |
| US5768250A (en) * | 1994-05-04 | 1998-06-16 | Hewlett-Packard Company | Error recovery in a network having cascaded hubs |
| US5875292A (en) * | 1995-02-10 | 1999-02-23 | Nec Corporation | Packet transmission method without sending serial numbers |
| US5699367A (en) * | 1995-12-29 | 1997-12-16 | Telefonaktiebolaget Lm Ericsson | Concatenated error detection coding and packet numbering for hierarchical ARQ schemes |
| EP0866579A1 (en) | 1997-03-20 | 1998-09-23 | Nec Corporation | Packet transmission method without sending serial numbers |
| US6205473B1 (en) * | 1997-10-03 | 2001-03-20 | Helius Development Corporation | Method and system for asymmetric satellite communications for local area networks |
| US6056691A (en) * | 1998-06-24 | 2000-05-02 | Ecton, Inc. | System for collecting ultrasound imaging data at an adjustable collection image frame rate |
| US6496481B1 (en) * | 1998-07-16 | 2002-12-17 | Industrial Technology Research Institute | Data transfer method for wire real-time communications |
| JP2002524920A (en) * | 1998-08-28 | 2002-08-06 | インテグラル アクセス， インコーポレイテッド | Redundant path data communication |
| US6373842B1 (en) * | 1998-11-19 | 2002-04-16 | Nortel Networks Limited | Unidirectional streaming services in wireless systems |
| EP1919117B1 (en) * | 1998-11-30 | 2014-10-15 | Panasonic Corporation | Packet retransmission control using priority information |
| US6584104B1 (en) * | 1999-07-06 | 2003-06-24 | Lucent Technologies, Inc. | Lost-packet replacement for a digital voice signal |
| GB9919920D0 (en) | 1999-08-24 | 1999-10-27 | Cedardell Ltd | Apparatus and method for wireless communication |
| US6721335B1 (en) * | 1999-11-12 | 2004-04-13 | International Business Machines Corporation | Segment-controlled process in a link switch connected between nodes in a multiple node network for maintaining burst characteristics of segments of messages |
| FR2825865A1 (en) * | 2001-06-06 | 2002-12-13 | Koninkl Philips Electronics Nv | SELECTIVE RETRANSMISSION OF PACKETS WITH TIME TRANSMISSION CONTROL |
| US7137626B2 (en) * | 2002-07-29 | 2006-11-21 | Intel Corporation | Packet loss recovery |
| US6728861B1 (en) * | 2002-10-16 | 2004-04-27 | Emulex Corporation | Queuing fibre channel receive frames |
| US7185138B1 (en) * | 2004-05-14 | 2007-02-27 | Peter Galicki | Multi-dimensional data routing fabric |
-
2002
- 2002-09-12 CA CA002461530A patent/CA2461530A1/en not_active Abandoned
- 2002-09-12 EP EP02769943A patent/EP1430634B1/en not_active Expired - Lifetime
- 2002-09-12 WO PCT/DE2002/003406 patent/WO2003028279A2/en active IP Right Grant
- 2002-09-12 ES ES02769943T patent/ES2266570T3/en not_active Expired - Lifetime
- 2002-09-12 US US10/490,534 patent/US7770085B2/en not_active Expired - Fee Related
- 2002-09-12 CN CNB028190378A patent/CN1317841C/en not_active Expired - Fee Related
- 2002-09-12 DE DE50207128T patent/DE50207128D1/en not_active Expired - Lifetime
- 2002-09-12 AT AT02769943T patent/ATE329424T1/en not_active IP Right Cessation
-
2010
- 2010-05-19 US US12/782,873 patent/US7900115B2/en not_active Expired - Fee Related
- 2010-10-06 US US12/898,770 patent/US8127195B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| ATE329424T1 (en) | 2006-06-15 |
| EP1430634B1 (en) | 2006-06-07 |
| DE50207128D1 (en) | 2006-07-20 |
| US7770085B2 (en) | 2010-08-03 |
| US8127195B2 (en) | 2012-02-28 |
| CN1561603A (en) | 2005-01-05 |
| WO2003028279A2 (en) | 2003-04-03 |
| WO2003028279A3 (en) | 2003-05-30 |
| US20110022914A1 (en) | 2011-01-27 |
| ES2266570T3 (en) | 2007-03-01 |
| US7900115B2 (en) | 2011-03-01 |
| US20040243902A1 (en) | 2004-12-02 |
| US20100229063A1 (en) | 2010-09-09 |
| CN1317841C (en) | 2007-05-23 |
| EP1430634A2 (en) | 2004-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8127195B2 (en) | Replacement messages for identifying and preventing errors during the transmission of realtime-critical data | |
| US7668994B2 (en) | Method for optimizing bandwidth utilization in bus systems | |
| EP2596602B1 (en) | Frame transmission and communication network | |
| US8144718B2 (en) | Control system having a plurality of spatially distributed stations, and method for transmitting data in such a control system | |
| US7852857B2 (en) | Coupler for a ring topology network and an ethernet-based network | |
| US8792518B2 (en) | Automation system | |
| US20210392011A1 (en) | User station for a serial bus system and method for communication in a serial bus system | |
| CN108702804B (en) | Wireless communication system for an industrial automation system, method for the operation thereof | |
| US7428250B2 (en) | System and associated method for receiving data telegrams in communication systems having redundant network paths | |
| CN113196710B (en) | Distribution node, automation network and method for transmitting messages | |
| US7701933B2 (en) | Method for transmitting a data telegram between a real-time domain and a non-real-time domain and a coupling unit | |
| US11778073B2 (en) | Protocol converter and automation system | |
| CN114531943B (en) | Data transmission method and automation communication network | |
| US7450607B2 (en) | Communication in a data network | |
| US20040105398A1 (en) | Method and electronic switching circuit for a scalable communication interface in automation components | |
| US7792029B2 (en) | Network data transmission based on predefined receive times | |
| CN115174370B (en) | Distributed mixed data deterministic transmission device and method | |
| Ojewale | On Preemption in Time-Sensitive Networking (TSN) | |
| CN1561614B (en) | Method for creating a dynamic address table for a switching node in a data network and a method for transmitting a data message | |
| CN115801161A (en) | Time synchronization in an industrial system | |
| CN115801162A (en) | Synchronization for backplane communications | |
| CA2461500A1 (en) | Method for processing consistent data sets | |
| JPH0410829A (en) | Data transmission method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |