Method for detecting network subscribers in an automation network and automation network
US-2021218584-A1 · Jul 15, 2021 · US
US11758024B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11758024-B2 |
| Application number | US-202117328314-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 24, 2021 |
| Priority date | Nov 26, 2018 |
| Publication date | Sep 12, 2023 |
| Grant date | Sep 12, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In an automation network comprising a plurality of network segments, fragmenting subscribers that support a fragmentation method as well as standard subscribers that do not support the fragmentation method can be provided for in the network. A distribution node in the automation network has at least one input/output interface that is in communication with a network segment. The switching unit in the distribution node checks whether a subscriber in a network segment to which a telegram is to be sent supports the fragmentation method, and whether the telegram to be sent is fragmented. If the subscriber does not support the fragmentation procedure and the telegram to be sent is fragmented, the switching unit in the distribution node assembles the telegram fragments to form the telegram and then sends the assembled telegram on to the subscriber.
Opening claim text (preview).
The invention claimed is: 1. A distribution node for an automation network having a plurality of network segments which each have at least one subscriber configured as a fragmenting subscriber or as a standard subscriber, wherein data are exchanged between the subscribers in the form of telegrams, wherein the transmission of the telegrams is carried out in accordance with a fragmentation method in the form of telegram fragments and wherein both fragmenting subscribers which support the fragmentation method and standard subscribers which do not support the fragmentation method are provided for in the automation network, wherein the distribution node comprises a plurality of input/output interfaces and a switching unit connected to the input/output interfaces, the switching unit being configured to control an operation of the distribution node, wherein at least one input/output interface is in communication with a network segment, wherein the switching unit is configured to check whether a subscriber at the input/output interface to which a telegram is to be sent supports the fragmentation method and whether the telegram to be sent is fragmented, and wherein the switching unit is configured, if the telegram to be sent is fragmented, to assemble the telegram fragments into the telegram and then to send the telegram to the subscriber if the subscriber is a standard subscriber that does not support the fragmentation method. 2. The distribution node according to claim 1 , further comprising: an allocation table which contains identifiers of the standard subscribers which do not support the fragmentation method, wherein the switching unit is configured to detect an identifier of the addressed subscriber upon receipt of a telegram and to compare the telegram with the identifiers of the standard subscribers in the allocation table, the switching unit being further configured, if the telegram to be sent is fragmented, to assemble the telegram fragments into the telegram if the compare of the telegram with the identifiers of the standard subscribers in the allocation table identifies a standard subscriber that does not support the fragmentation method. 3. The distribution node according to claim 1 , further comprising: an allocation table in which the input/output interface with the network segment is allocated information whether fragmented transmission is allowed via the input/output interface or not, and wherein the switching unit is configured, if the telegram to be sent is fragmented, to assemble the telegram fragments into the telegram if the allocation table indicates that the input/output interface to which the telegram is to be sent does not support the fragmentation method. 4. The distribution node according to claim 2 , wherein the switching unit is configured to create the allocation table at start-up of the automation network. 5. The distribution node according to claim 2 , wherein the switching unit is configured to autonomously perform a checking process with the subscribers in network segments connected to the input/output interfaces in order to determine the identifiers of the standard subscribers that do not support the fragmentation process. 6. The distribution node according to claim 1 , wherein the distribution node is configured to always first fully receive telegrams intended for a standard subscriber that does not support the fragmentation method before starting transmission to the standard subscriber. 7. The distribution node according to claim 1 , wherein: the switching unit is configured to abort a transmission process if the telegram is fragmented, and if the telegram is intended for a standard subscriber that does not support the fragmentation process, the standard subscriber discards the already transmitted telegram fragment. 8. The distribution node according to claim 1 , wherein the switching unit is configured, when a telegram is to be sent to a standard subscriber in a network segment connected to an input/output interface that does not support the fragmentation method, not to apply the fragmentation method to the telegram. 9. An automation network comprising: network segments which each have at least one subscriber configured as a fragmenting subscriber or as a standard subscriber, and at least one distribution node which has a plurality of input/output interfaces and a switching unit which is connected to the input/output interfaces, at least one input/output interface being connected to a network segment, the switching unit being configured to control an operation of said at least one distribution node; wherein data are exchanged between the subscribers in the form of telegrams configured to be transmitted in accordance with a fragmentation method in the form of telegram fragments, wherein both fragmenting subscribers which support the fragmentation method and the standard subscribers which do not support the fragmentation method are provided for, wherein the switching unit in the distribution node is configured to check whether a subscriber at the input/output interface to which a telegram is to be transmitted supports the fragmentation method, and whether the telegram to be sent is fragmented, and wherein the switching unit in the distribution node is configured, if the telegram to be sent is fragmented, to assemble the telegram fragments into the telegram and then to send the telegram to a standard subscriber that does not support the fragmentation method. 10. The automation network according to claim 9 , wherein: the at least one distribution node comprises an allocation table comprising identifiers of the standard subscribers that do not support the fragmentation method, and wherein the switching unit in the distribution node is configured to detect an identifier of the addressed subscriber upon receipt of a telegram and to compare the telegram with the identifiers of the standard subscribers in the allocation table. 11. The automation network according to claim 9 , further comprising: an allocation table in which the input/output interface with the network segment is allocated information whether fragmented transmission is allowed via the input/output interface or not, and wherein the switching unit is configured, if the telegram to be sent is fragmented, to assemble the telegram fragments into the telegram if the allocation table indicates that the input/output interface to which the telegram is to be sent does not support the fragmentation method. 12. The automation network according to claim 10 , wherein the switching unit in the distribution node is configured to create the allocation table at start-up of the automation network. 13. The automation network according to claim 10 , wherein: one subscriber acts as a master subscriber that monitors the further subscribers in the automation network and informs the at least one distribution node which subscribers in the automation network that are connected to an input/output interface via a network segment do not support the fragmentation method, and wherein the switching unit in the distribution node is configured to update the allocation table according to information received from the master subscriber. 14. The automation network according to claim 10 , wherein the switching unit in the distribution node is configured to autonomously perform a verification operation with the subscribers in network segments connected to the input/output interfaces to determine the identifiers of the standard subscribers that do not support the fragmentation procedure. 15. The automation network according to claim 9 , wherein the
involving priority mechanisms (hybrid switching fabrics H04L12/6402; intermediate storage or scheduling H04L49/90; time-division multiplex systems H04J3/00) · CPC title
IP fragmentation; TCP segmentation · CPC title
Packet splitting · CPC title
Arrangements for supporting packet reassembly or resequencing · CPC title
Address processing for routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.