SYNCHRONIZATION OF SEQUENCE NUMBERS IN A NETWORK
By synchronizing sequence numbers across redundant equipment units using a master-slave protocol, the challenge of generating identical sequence numbers in redundant networks is addressed, ensuring seamless network operations and proper frame handling.
Patent Information
- Application Number
- DE112020006396
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-02-27
- Filing Date
- 2020-10-05
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2040-10-05
AI Technical Summary
Existing technologies face challenges in generating identical sequence numbers in multiple frames from redundant equipment, leading to potential discrepancies that can disrupt seamless operation in networks with equipment redundancy.
The synchronization of sequence numbers is achieved by coordinating the generation of sequence numbers across redundant equipment units using a master-slave protocol, where a device with the highest or lowest identifier assumes a master role to distribute defined times for resetting sequence counters, ensuring identical sequence number progression.
This approach ensures that end systems receive identical sequence numbers, facilitating proper frame elimination and maintaining seamless network operations even in cases of equipment redundancy.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates generally to communication networks, and more particularly to the generation of sequence numbers in a communication network. More specifically, various embodiments of the disclosure relate to synchronizing sequence numbers on a number of devices of a communication network. BACKGROUND
[0002] When providing high-speed connectivity, various interface standards can be used to connect computers and external peripherals. A widely used, flexible network standard for connecting computers (e.g., in local area networks (LANs) and wide area networks (WANs)) is the Ethernet protocol. Ethernet communication is generally understood to be point-to-point communication within a network with multiple endpoints. Ethernet generally utilizes shared resources efficiently, is easily maintainable and reconfigurable, and is compatible with many systems.
[0003] The document US 2011 / 0 161 538 A1 discloses a method and system for implementing redundant master NIMs on a single bus in an industrial distributed I / O system for controlling selected I / O modules. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] While this disclosure concludes with claims particularly pointing out and distinctly claiming particular embodiments, various features and advantages of embodiments within the scope of this disclosure may be more readily ascertained from the following description when read in conjunction with the accompanying drawings in which: Fig. 1 illustrates a network including two devices; Fig. Figure 2 illustrates a network including a number of devices; Fig. 3 is a further illustration of a network including a number of devices according to various embodiments of the present disclosure; Fig. 4A illustrates a node element portion according to various embodiments of the present disclosure; Fig. Figure 4B illustrates an OSI model including a number of layers; Fig. 5 is a flowchart of an exemplary method for operating a node element according to various embodiments of the disclosure; Fig. 6A is a flowchart of an exemplary method for triggering a sequence number reset according to various embodiments of the present disclosure; Fig. 6B is a flowchart of an exemplary method for resetting a sequence number in response to a reset event, according to various embodiments of the present disclosure; Fig. 7 is a flowchart of an exemplary method for operating a node element at each of a number of devices of a network according to various embodiments of the present disclosure; Fig. 8 is a flowchart of another exemplary method for triggering a sequence number reset according to various embodiments of the present disclosure; and Fig. 9A and Fig. 9B illustrates a flowchart of an exemplary method for synchronizing sequence numbers on a number of devices of a network according to various embodiments of the present disclosure. MODE(S) FOR CARRYING OUT THE INVENTION
[0005] In the following detailed description, reference is made to the accompanying drawings, which form a part of this document, and in which is shown by way of illustration specific examples of embodiments in which the present disclosure may be practiced. These embodiments are described in sufficient detail to enable one of ordinary skill in the art to practice the present disclosure. However, other embodiments contemplated herein may be utilized, and changes in structure, material, and process may be made without departing from the scope of the disclosure.
[0006] The illustrations presented herein are not intended to be actual views of any particular method, system, device, or structure, but are merely idealized representations used to describe embodiments of the present disclosure. Similar structures or components in the various drawings may, in some cases, retain the same or similar numbering for the convenience of the reader; however, similarity in numbering does not necessarily imply that the structures or components are identical in size, composition, configuration, or any other characteristic.
[0007] The following description may include examples to enable one of ordinary skill in the art to practice the disclosed embodiments. The use of the terms "exemplary," "as an example," and "for example" means that the accompanying description is illustrative, and while the scope of the disclosure is intended to include the examples and their legal equivalents, the use of such terms is not intended to limit the scope of any embodiment or this disclosure to the specified components, steps, features, functions, or the like.
[0008] It should be understood that the components of the embodiments, as generally described herein and illustrated in the drawings, could be arranged and configured in a wide variety of different configurations. Thus, the following description of various embodiments is not intended to limit the scope of the present disclosure, but is merely representative of various embodiments. While the various aspects of the embodiments may be illustrated in the drawings, the drawings are not necessarily drawn to scale unless expressly indicated.
[0009] Furthermore, the specific implementations shown and described are only examples and should not be construed as the only way to implement the present disclosure unless otherwise stated herein. Elements, circuits, and functions may be shown in block diagram form in order not to obscure the present disclosure with unnecessary detail. Conversely, specific implementations shown and described are only examples and should not be construed as the only way to implement the present disclosure unless otherwise stated herein. Furthermore, block definitions and the partitioning of logic between various blocks are exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present disclosure may be implemented using numerous other partitioning approaches.Details of timing considerations and the like have largely been omitted to the extent that such details are not necessary for a complete understanding of the present disclosure and are within the capabilities of one of ordinary skill in the art.
[0010] One of ordinary skill in the art would understand that information and signals can be represented using a variety of different technologies and techniques. Some drawings may illustrate signals as a single signal for clarity of illustration and description. One of ordinary skill in the art will understand that the signal may represent a bus of signals, where the bus may have a variety of bit widths, and the present disclosure may be implemented on any number of data signals, including a single data signal.
[0011] The various illustrative logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed using a processor, such as a general-purpose processor, a special-purpose processor, a digital signal processor (DSP), an integrated circuit (IC), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to perform one or more of the features or functions described herein.A general-purpose processor (which may also be referred to herein as a host processor or simply a host) may be a microprocessor, but alternatively, it may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. A general-purpose computer including a processor is considered a special-purpose computer, while the general-purpose computer is configured to execute computational instructions (e.g., software code) related to embodiments of the present disclosure.
[0012] Embodiments may be described with respect to a process represented as a flowchart, a flow diagram, a structural diagram, or a block diagram. Although a flowchart may describe operational acts as a sequential process, many of these acts may be performed in a different sequence, in parallel, or substantially concurrently. Furthermore, the order of the acts may be changed. A process may correspond to a method, a thread, a function, a procedure, a subroutine, a subprogram, another structure, or combinations thereof. Furthermore, the methods disclosed herein may be implemented in hardware, software, or both. When implemented in software, the functions may be stored or transmitted as one or more instructions or as code on computer-readable media.Computer-readable media includes both computer storage media and communications media, including any media that supports the transmission of a computer program from one location to another.
[0013] Any reference to an element herein using a label such as "first," "second," etc., does not limit the quantity or order of those elements unless such a limitation is expressly stated. Rather, these labels may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to a first and a second element does not imply that only two elements may be substituted therein or that the first element must precede the second element in any way. Furthermore, unless otherwise stated, a set of elements may include one or more elements.
[0014] As used herein, the term "substantially" with respect to a given parameter, property, or condition means, and includes, to the extent understood by one of ordinary skill in the art, that the given parameter, property, or condition is satisfied with a small degree of variance, such as within acceptable manufacturing tolerances. By way of example, depending on the particular parameter, property, or condition that is substantially satisfied, the parameter, property, or condition may be at least 90% satisfied, at least 95% satisfied, or even at least 99% satisfied.
[0015] Auto / control systems (e.g., industrial control systems) are used to control the operation of, for example, processes and / or machines and are typically adaptable to various control applications by configuring and connecting multiple control system components or devices (e.g., control modules, input / output modules (I / O modules), I / O devices, without limitation). Some control systems may include a processor executing a control program to interact with an I / O system (e.g., typically one or more I / O modules or devices) to receive system information in the form of analog and / or digital inputs from field sensors and to provide (analog and / or digital) outputs to one or more actuators.Control systems may be connected to management information and other systems in a manufacturing facility and may be operably connected to any number of communications networks to facilitate various management functions (e.g., inventory control, accounting, manufacturing control, without limitation) in addition to process / machine control functionality.
[0016] The desire to integrate business and control network structures to connect control systems to general systems, as well as the expansion and development of Ethernet (e.g., in switch mode with full-duplex capability), have enabled Ethernet networks (e.g., such as Ethernet / Internet Protocol networks that allow direct connection of field devices to an Ethernet network) to be widely used in various applications (e.g., in industrial applications).
[0017] Time-Sensitive Networking (TSN) is a set of standards developed or currently being developed by the Time-Sensitive Networking Task Group of the IEEE 802.1 Working Group. TSN standards aim to improve network delay characteristics, robustness, reliability, redundancy, and fault detection capabilities, allowing Ethernet to be used for real-time control and safety-critical applications. IEEE 802.1CB ("Frame Replication and Elimination for Reliability") and IEC 62439-3 ("High-Availability Seamless Redundancy" (HSR) and "Parallel Redundancy Protocol" (PRP)) introduce redundancy and error mitigation, which is important for certain control applications using frame replication and duplicate elimination.
[0018] Increasing the availability of a network function can be achieved, for example, through redundant implementations of the network function. For example, in cases of network redundancy (e.g., using redundant grandmasters according to IEEE 1588 or IEEE 802.1AS), two functional units are part of a network and can perform identical functions, but have different network identities. In this example, a timing slave can be locked to one grandmaster, and if the grandmaster fails or the path to the grandmaster becomes unavailable, the timing slave can choose to become a slave of another grandmaster. In this case, frames (e.g., SYNC frames or so-called "announce" frames, without limitation) are sent by the grandmasters with sequence numbers specific to each network identity.
[0019] Fig. 1 shows a network 100 including a device 102 coupled to a device 104. The device 102 may be configured to transmit a frame 103 to the device 104 via redundant communication paths of a network. In particular, a sequence number may be inserted into the frame 103 at the device 102, and the frame 103 may be transmitted to the device 104 via a first path 108 and a second path 110. In the event that the device 104 receives both copies of the frame 103, one copy of the frame 103 (e.g., the copy received later in time) may be discarded by the device 104.
[0020] In some networks (e.g., in highly available automation networks, such as in the process industry (e.g., in a chemical plant)), equipment redundancy may be required. In cases of equipment redundancy, a functional unit in a network has two or more redundant equipment instances. Redundant equipment instances can be physically located together or separated by a network. One example is the use of the Virtual Router Redundancy Protocol (VRRP, IETF RFC 3768), which makes two routers appear as one to a host.
[0021] Equipment redundancy can be implemented using 1:1 / 1+1 and, more generally, N:M / N+M schemes, where N:M indicates that N units are standby and M units are active, and N+M indicates that all units with an excess capacity of N are active. In the 1:1 case, an active / standby scheme is typically used, where one piece of equipment is active and the other is passive (e.g., not generating frames), while 1+1 uses an active / active scheme, where both pieces of equipment are active (e.g., both generating frames). In both cases, if operations are to be maintained seamlessly during an equipment failure and a function is to generate frames that include sequence numbers, the sequence number generators on the redundant pieces of equipment must be coordinated.An example of this is the generation of synchronization frames (SYNC frames), where an active equipment unit generates the sequence number p, and the next SYNC frame is generated by a redundant equipment unit with the sequence number p+1. Another example includes the generation of redundant frames for network redundancy, such as according to IEEE 802.1CB, IEC 62439-3 PRP and HSR, and IEC 61458-6 MRPD, where one equipment unit generates a frame and the other unit generates a redundant frame, both with the same sequence number.
[0022] Fig. 2 illustrates a network 200 including devices 202A and 202B and a device 204. In this example, device 202A (e.g., a first piece of equipment) may be configured to transmit a frame 203A to device 204 via a path 208 over a network, and device 202B (e.g., a second piece of equipment) may be configured to transmit a frame 203B to device 204 via a path 210 over the network. Further, at each of devices 202A and 202B, a sequence number may be inserted into an associated frame before the frame is transmitted to device 204. Frame 203A transmitted from device 202A to device 204 is identical to, or slightly different from, frame 203B transmitted from device 202B to device 204. For example, frames 203A and 203B transmitted to device 204 may have different Ethernet headers (e.g.,For example, for reasons of forwarding through a network, configuration frames 203A and 203B are considered "identical" by device 204. Furthermore, the sequence number inserted into the frame at device 202A is identical to the sequence number inserted into the frame at device 202B. In the event that device 204 receives both frame 203A and frame 203B, either frame 203A or frame 203B (e.g., the copy of the frame received later in time) may be discarded by device 204.
[0023] Sequence numbers that have monotonically increasing values can be used for various purposes, such as indicating a current number of acknowledged bytes (e.g., according to TCP, IETF RFC 793 protocol) or counting an event (e.g., a number of transmitted SYNC frames (e.g., according to IEEE 1588)).
[0024] A technical problem recognized by the inventor of this disclosure is how to generate identical sequence numbers in multiple frames from redundant equipment units so that an end system does not realize that the frames do not originate from the same equipment unit, and so that the end system can perform a proper function (e.g., IEEE 802.1CB frame elimination) after receiving a number of frames.
[0025] The generation of identical sequence numbers in a number of devices (i.e., two pieces of equipment) is possible if the sequence number is derived from the time of day (TOD) at which the event occurs, assuming that each of the number of devices is TOD-synchronized. In event-based systems (i.e., using event-based sequence numbers), the sequence numbers can be consecutive (while TOD systems can skip sequence numbers), making it possible to count the number of packets sent. Furthermore, event-based systems may not require TOD formats and can consequently avoid time-based problems (e.g., leap second adjustments).
[0026] Various embodiments, as described in more detail below, relate to the synchronization of sequence numbers in networks. In particular, various embodiments relate to the synchronization of sequence numbers used in networks that include equipment redundancy (e.g., networks that utilize network redundancy protocols). It should be understood that various embodiments of the present disclosure may be implemented in event-based systems and / or networks (e.g., where a sequence number may represent an event count). For example, various embodiments may support the operation of a network (e.g., network 200 of Fig. 2) improve.
[0027] In some embodiments, the coordination of the generation of sequence numbers for event counting in two or more equipments (i.e., two or more devices) may be achieved, for example, via the configuration of one or more defined times (e.g., defined time(s) TR; see Fig. 4A), wherein a sequence number generator (e.g., a counter, without limitation) is reset (e.g., to an integer value N) at each piece of equipment. Since, in these embodiments, the number of frames generated by each piece of equipment is substantially identical, the sequence number may advance identically at each piece of equipment.
[0028] In some embodiments, a number of defined times at which each equipment is reset may be specified (e.g., set or programmed, without limitation) via a management system or specified by a master-slave protocol in which a device with the highest or lowest identifier assumes a master role and distributes the number of defined times.
[0029] Protocols other than master-slave protocols do not exceed the scope of this disclosure.
[0030] Fig. 3 shows a system (also referred to herein as a "network") 300 including a device (also referred to herein as a "piece of equipment," "unit," or "equipment unit") 302A, a device (also referred to herein as a "piece of equipment," "unit," or "equipment unit") 302B, a device (also referred to herein as an "end system" or "end device") 304, a frame 306A, and a frame 306B. It should be understood that in some examples, one of the devices 302A and 302B may be referred to, for example, as a "piece of equipment" or a "device," and the other of the devices 302A and 302B may be referred to, for example, as a "redundant piece of equipment," "redundant equipment instance," or a "redundant device." Further, device 302A and device 302B may be collectively referred to herein as “redundant units” or “redundant instances.”For example, each of device 302A and device 302B may include a node element portion 400 shown in FIG. Fig. 4A is illustrated.
[0031] According to some embodiments, device 302A is configured to generate frame 306A, and device 302B is configured to generate frame 306B that is the same as or similar to frame 306A. In other words, frames 306A and 306B may be the same or slightly different. For example, frames 306A and 306B may have different Ethernet headers (e.g., for forwarding purposes through a network), but frames 306A and 306B may be considered "identical" by the configuration of device 304. For example, each of device 302A and device 302B may be similarly configured and receive the same or similar inputs to generate the same or similar frames, as understood by one of ordinary skill in the art.
[0032] According to various embodiments, devices 302A and 302B may be configured to generate identical sequence numbers (e.g., substantially simultaneously). In other words, sequence numbers generated by devices 302A and 302B may be synchronized. In particular, according to some embodiments, each of device 302A and device 302B may each maintain a sequence counter (in Fig. 3 not shown); e.g., sequence counter 406 of Fig. 4A, without limitation, configured to increment and output a sequence number ("count"). Further, as described in more detail below, each of device 302A and device 302B may be configured to insert its respective generated sequence number into an associated frame. In particular, device 302A may be configured to insert a sequence number into frame 306A, and device 302B may be configured to insert a sequence number into frame 306B. As in Fig. 3, frames 306A and 306B have the same sequence number (i.e., Seq. No. = P).
[0033] Furthermore, each of device 302A and device 302B may be configured to transmit an associated frame to device 304 (e.g., via a bus) that includes the respective inserted sequence numbers. In some embodiments, device 302A and 302B are TOD-synchronized, and thus device 302A and device 302B may be configured to transmit an associated frame at approximately the same time. As described in more detail below, to coordinate a sequence counter on device 302A and a sequence counter on device 302B, the respective sequence counters may be reset in response to an event (e.g., a reset event, such as a power cycle, a timing event (e.g., a periodic reset), and / or one or more other defined times for a reset).
[0034] Fig. 4A illustrates a node element portion 400 according to various embodiments of the present disclosure. For example, each of the device 302A and the device 302B of Fig. 3 include respective instances of the node element section 400. Fig. Figure 4B illustrates an Open Systems Interconnection (OSI) model 450, which includes a number of layers, including an application layer, a presentation layer, a session layer, a transport layer, a network layer, a data link layer, and a physical layer. It should be understood that an OSI model is a conceptual framework that describes the functions of a network or telecommunications system.
[0035] With reference to Fig. 4A, the node element portion 400, which may include or be contained within, as a non-limiting example, a physical layer (PHY) element and / or a media access control (MAC) element, may be configured to receive or generate a frame 402 (e.g., at a particular time and / or in response to an event). It should be understood that, in particular, the frame 402 (also referred to herein as a "data frame") may include data (e.g., data from data storage and / or input data) and may be generated, for example, via one or more processors. For example, the frame 402 may be generated in whole or in part in a PHY layer or a data link layer by a PHY element or MAC element of a node.The generation of frame 402, in whole or in part, in layers other than the physical and data link layers, in multiple layers, between what are typically understood as network layers (e.g., an interface sublayer, without limitation), or outside of an OSI model-type network stack does not exceed the scope of this disclosure.
[0036] The node element section 400 may further include an event generator 404, a sequence counter 406 (by Fig. 4A as "counter 406"), logic 408, logic 410, and TOD counter 412. Event generator 404 may be configured to generate a pulse (e.g., an event signal 420) in response to a frame event (i.e., in response to the receipt and / or generation of frame 402 (i.e., at node element portion 400)). It should be understood that sequence counter 406 may further increment a stored count value (e.g., by one) for each event signal 420 received by event generator 404. Further, the sequence counter 406 (e.g., in response to a received event signal 420) may communicate the count value (i.e., via signal 422) to logic 408 (also referred to herein as "count insertion logic"), which may be configured to insert the count value as a sequence number into an available portion (e.g., bits or bytes) of the frame 402.For example, the count value indicating a current number of frame events (e.g., a number of frames generated and / or received at node element section 400 since the last reset / initialization) may be inserted into frame 402 as a sequence number (e.g., when frame 402 passes an associated stage of a processing pipeline). Furthermore, logic 408 may be configured to insert a sequence number into frame 402 at a specific offset (e.g., from the beginning of frame 402).
[0037] In some non-limiting embodiments, the sequence counter 406 may be logically implemented at one or more layers of the OSI model 450 (see Fig. 4B), such as at the data link layer (i.e., layer 2), at the network layer (i.e., layer 3), and / or one or more other layers of the OSI Model 450.
[0038] The TOD counter 412, which may be synchronized (e.g., according to IEEE 1588 (Precision Time Protocol)) with a network master clock (not shown), may communicate a TOD counter reading 411 to the logic 410. For example, the TOD counter 412 may include a counter (e.g., a nanosecond counter) configured to output a pulse (i.e., the TOD counter 411) every specified number of nanoseconds (e.g., 1, 2, 10, 100, without limitation). The logic 410, which may include and / or access a number of predefined times, each of which is referred to as a predefined time TR (e.g., 23h:59m:59s, 11h:59m:59s, 07hr:59m:59s, without limitation), may be configured to compare the TOD count 411 to each of the predefined times TR.In particular, for example, logic 410 may include comparison logic configured to compare TOD count 411 to one or more predefined times TR 415 (e.g., the predefined times TR may be contained in a database). Further, in response to TOD count 411 matching any of the predefined times TR 415, logic 410 may transmit a reset signal 424 (e.g., a pulse) to sequence counter 406, and in response to reset signal 424, sequence counter 406 may be reset to an initial predetermined count value.
[0039] Logic 410 may be configured to transmit a reset signal 424 to sequence counter 406, in addition to or alternatively to the TOD count 411, corresponding to any of the defined times TR, in response to a received signal 413 indicating a power reset (e.g., indicating a power cycle of an associated network, regardless of whether a power cycle has actually occurred). It should further be understood that sequence counter 406 may be reset by setting all bits (i.e., all outputs of one or more flip-flops) of sequence counter 406 to a specific value (e.g., zero or another initial predetermined count value).
[0040] In particular, one or more elements of node element section 400 may be implemented in the same or different communication layers (e.g., according to OSI model 450, without limitation). As a non-limiting example, event generator 404, sequence counter 406, TOD counter 412, and logic 410 may be implemented in a data link layer (e.g., in a MAC element, without limitation), and logic 408 may be implemented in the data link layer or a physical layer (e.g., in a PHY element, without limitation). Other arrangements between different layers do not exceed the scope of this disclosure.
[0041] Fig. 5 is a flowchart of an exemplary method 500 for operating a node element (e.g., node element portion 400 of Fig. 4A) (e.g., a single piece of equipment such as device 302A of Fig. 3). At block 502, a frame is generated (e.g., at the device), and the method 500 may continue with block 504. At block 504, a sequence number is determined (e.g., at the device via a sequence counter, such as the sequence counter 406 of Fig. 4A), and the method 500 may continue with block 506. For example, in response to the generation of the frame at block 504, the sequence number may be incremented by one (i.e., the sequence number may be equal to a previous sequence number + 1 (e.g., sequence number = sequence number + 1)), and the sequence number may be output from the sequence counter. At block 506, the sequence number may be inserted into the frame (e.g., via logic 408 of Fig. 4A), and the method 500 may continue to block 508. At block 508, the frame may be transmitted (e.g., from the device to another device (e.g., the end system 304) via a bus).
[0042] According to some embodiments, a sequence number generator may be initialized or a sequence number may be reset by a sequence counter (e.g., sequence counter 406 of Fig. 4A) in response to a reset event (e.g., a timing event). Fig. For example, Figure 6A shows a flowchart of an exemplary method 600 for initiating a sequence number reset according to various embodiments of the disclosure. At block 602, a variable RESET (e.g., the reset signal 424 of Fig. 4A) may be equal to a first value (e.g., zero (i.e., RESET = 0), i.e., the variable RESET is LOW or UNCONFIRMED), and the method 600 may proceed to block 604.
[0043] At block 604, it may be determined whether or not a reset event (e.g., a timing event) has occurred. If a reset event has occurred, the method 600 may proceed to block 606. If a reset event has not occurred, the method 600 may return to block 602.
[0044] At block 606, the variable RESET is set equal to a second value (e.g., one (i.e., RESET = 1), i.e., the variable RESET is HIGH or CONFIRMED) for a time period PERIOD, and the method may return to block 602. For example, the time period PERIOD is a sufficient time period such that a count of the sequence counter (sequence counter 406 of Fig. 4A) may be reset to the integer N (e.g., N = 0 or another initial predetermined count value). It is noted that the operations of method 600 may be performed in a number of network devices (e.g., device 302A and device 302B of Fig. 3) (e.g. essentially simultaneously).
[0045] Fig. 6B is a flowchart of an exemplary method 650 for initializing a sequence number generator or resetting a sequence number in response to a reset, according to various embodiments of the disclosure. It should be noted that the operations of method 650 may be performed in a number of network devices (e.g., device 302A and device 302B of Fig. 3) (e.g. essentially simultaneously).
[0046] At block 652, it can be determined whether a variable RESET is HIGH or not (i.e., RESET = 1?). For example, it can be determined whether an output of logic 410 (e.g., reset signal 424 - see Fig. 4A) transmitted to the sequence counter 406 is HIGH. If it is determined that the RESET variable is HIGH, the method 650 may proceed to block 654, where a sequence number (e.g., of the sequence counter 406) may be set equal to the integer N (e.g., N = 0 or another initially predetermined count value). If it is determined that the RESET variable is LOW, the method 650 may return to block 652.
[0047] Fig. 7 is a flowchart of an exemplary method 700 for operating a node element at each of a number of devices (i.e., two pieces of equipment, such as device 302A and device 302B of Fig. 3) a network according to various embodiments of the disclosure. At least a portion of the method 700 may, in some embodiments, be performed by a device or system such as the system 300 of Fig. 3, the node element section 400 of Fig. 4A or another device or system. Although illustrated as discrete blocks, various blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation.
[0048] At each of blocks 702A and 702B, a frame is generated or received, and the method 700 may continue to block 704. In particular, for example, at block 702A, a frame (e.g., a first instance of frame 402) is generated or received at a first device (e.g., at device 302A of Fig. 3) is generated, and at block 702B, a frame (e.g., a second instance of frame 402) is transmitted to a second device (e.g., device 302B of Fig. 3). For example, the frames 402 generated at blocks 702A and 702B may be the same or similar, and at least in these embodiments, the frames generated at blocks 702A and 702B may be considered "identical" (e.g., by a receiving device). Further, according to some embodiments, the first device and the second device are TOD-synchronized, and the frames generated / received at blocks 702A and 702B may be generated / received at approximately the same time. For example, each frame may be generated via a different node element (e.g., node element portion 400 of Fig. 4A), which is similarly configured and synchronized.
[0049] At each of blocks 704A and 704B, a sequence number is determined, and the method 700 may continue to block 706. For example, in response to the generation of the frame, the sequence number may be incremented by one (i.e., the sequence number may be equal to a previous sequence number + 1 (e.g., sequence number = sequence number + 1)), and the sequence number may be output from a sequence counter (e.g., sequence counter 406 of Fig. 4A). For example, the sequence number may be a count value of the sequence counter of a node element (e.g., node element section 400 of Fig. 4A). According to various embodiments disclosed herein, the sequence numbers determined at blocks 704A and 704B are identical.
[0050] At each of blocks 706A and 706B, the determined sequence number may be inserted into the frame (i.e., the frame generated in the associated block 702), and the method 700 may continue to block 708. For example, at block 706A, the sequence number determined at block 704A may be inserted into the frame at the first device (e.g., device 302A of Fig. 3) and at block 706B, the sequence number determined at block 704B may be inserted into the frame at the second device (e.g., device 302B of Fig. 3). For example, the specific sequence number can be specified via a logic (e.g. logic 408 in Fig. 4) into the frame (e.g. frame 402 of Fig. 4) should be inserted.
[0051] At each of blocks 708A and 708B, the frames including respective synchronized sequence numbers may be transmitted. For example, at block 708A, the frame transmitted at the first device (e.g., device 302A of Fig. 3) the frame generated is transmitted via the first device to a bus (e.g. to an end system (e.g. device 304 of Fig. 3)), and the second device (e.g., device 302B of Fig. 3) The frame generated may be transmitted via the second device to a bus (e.g., to an end system (e.g., device 304 of Fig. 3)).
[0052] Modifications, additions, or omissions may be made to method 700 without departing from the scope of the present disclosure. For example, the acts of method 700 may be implemented in different orders. Furthermore, the outlined acts and actions are provided only as examples, and some of the acts and actions may be optional, combined into fewer acts and actions, or expanded into additional acts and actions without affecting the essence of the disclosed embodiment.
[0053] In some embodiments, a sequence number of a number of devices (e.g., two or more) may be reset (i.e., to an integer) in response to an event (e.g., a timing event and / or a power reset event). In particular, according to some embodiments, in response to a timing event where a current network time (e.g., indicating a time of day) is equal to a predefined time (e.g., a programmed time), a sequence number of a number of devices (e.g., two or more devices) of a network may be reset (i.e., to the initial predetermined count common among the number of devices). Further, according to another embodiment, in response to the power reset (also referred to herein as a "power cycle") (e.g., of the network), a running sequence number of a number of devices (e.g.,two or more devices) of the network are reset (i.e., to the initially predetermined common count value). Fig. For example, Figure 8 is a flowchart of an exemplary method 800 for initiating a sequence number reset according to various embodiments of the disclosure. It should be noted that the operations of method 800 may be performed in a number of network devices (e.g., device 302A and device 302B of Fig. 3) (e.g. essentially simultaneously).
[0054] At block 802, a variable RESET may be equal to a first value (e.g., a LOW or UNCONFIRMED, RESET = 0), and the method 800 may continue to block 804. For example, the variable RESET may be an output of the logic 410 of Fig. 4A, which is provided to the sequence counter 406 as a reset signal 424.
[0055] At block 804, it may be determined whether or not a power cycle has occurred. For example, logic 410 of FIG. 410 may receive signal 413 indicating whether or not a power cycle has occurred. For example, received signal 413 may be HIGH or transition from a first state to a second state in response to a power cycle. If a power cycle has occurred, method 800 may proceed to block 808.
[0056] If a power cycle has not occurred, method 800 may continue to block 806.
[0057] At block 806, it may be determined whether or not a timing event has occurred. In particular, it may be determined whether a current network time is equal to one or more predefined times (e.g., predefined times TR 415 shown in Fig. 4A). For example, the logic 410 of Fig. 4A may be configured to receive the TOD count 411 from the TOD counter 412, compare the TOD count 411 to one or more predefined times, and determine whether or not a timing event has occurred based on the comparison. If the current network time is equal to one of the predefined times, a timing event has occurred, and the method 800 may proceed to block 808. If the current network time is not equal to one of the predefined times (i.e., a timing event has not occurred), the method 800 may return to block 802.
[0058] At block 808, the variable RESET is set to a second value (e.g., to a HIGH or CONFIRMED value, RESET = 1) for a time period PERIOD, and the method 800 may return to block 802. For example, the logic 410 of the Fig. 4A, generate the reset signal 424 as a pulse (e.g., a HIGH variable RESET) that may be received at the sequence counter 406. Further, for example, in response to receiving the reset signal 424 from the logic 410, the sequence counter 406 may be reset by setting all bits (i.e., all outputs of one or more flip-flops of the sequence counter 406) to an integer (e.g., N = 0 or another initial predetermined count value). For example, the time period PERIOD is a sufficient time period such that a count value of the sequence counter (sequence counter 406 of Fig. 4A) can be reset to the integer N (e.g. N = 0 or another initial predetermined count value).
[0059] Modifications, additions, or omissions may be made to method 800 without departing from the scope of the present disclosure. For example, the acts of method 800 may be implemented in different orders. Furthermore, the outlined acts and actions are provided only as examples, and some of the acts and actions may be optional, combined into fewer acts and actions, or expanded into additional acts and actions without affecting the essence of the disclosed embodiment. For example, the acts at blocks 804 and 806 may be interchanged. As another example, the act at block 804 may be omitted, and method 800 may proceed from block 802 to block 808.
[0060] For example, frames may be generated in a number M of devices of a network (e.g., some or all devices of the network) at a rate R starting at time Ts (e.g., frames are transmitted at TOD = Ts, Ts + 1 / R, Ts + 2*1 / R, etc.). The frame generation time TG for the j-th device is TG, j. The maximum difference in generation time, Max(TG, j - TG, k), with j = 1...M and k = 1...M, j ≠ k, is assumed to be much smaller than 1 / R. If a reset occurs at the reset time TR = Ts + N* 1 / R, i.e., at the frame generation time, a sequence number inserted into the frame may be indeterminate. In some embodiments, to avoid concurrent frame generation and sequence number reset operations in at least some devices of a network, a reset may be postponed by a fraction of 1 / R after a frame generation time.In particular, according to at least some embodiments, one or more defined times TR may lie between the frame generation times (e.g., TR = Ts + ½*1 / R + N* 1 / R).
[0061] Fig. 9A and Fig. 9B show a flowchart of an exemplary method 900 for synchronizing sequence numbers for a number of devices (ie, two pieces of equipment, such as devices 302A and 302B of Fig. 3) a network according to various embodiments of the disclosure. The method 900 may be performed according to at least one embodiment described in the present disclosure. At least a portion of the method 900 may, in some embodiments, be performed by a device or system, such as the system 300, the node element portion 400, or another device or system. Although illustrated as discrete blocks, various blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation.
[0062] At block 902, a reset event may be detected at both a first device and a second device of a network, and the method 900 may continue to block 904. For example, the logic 410 of Fig. 4A detect a timing event (e.g., upon receipt of TOD count 411 from TOD counter 412).
[0063] At block 904, an associated sequence number at both the first device and the second device may be reset to an initial predetermined count value in response to the reset event, where the initial predetermined count value is common to the first and second devices, and the method 900 may continue to block 906. For example, the sequence number may be reset to an integer (e.g., N = 0 or another initial predetermined count value) in response to a timing event (e.g., when the current network time is equal to a defined time TR).
[0064] At block 906, a frame for transmission may be generated at both the first device and the second device, and the method 900 may continue to block 908. A frame generated via the first device may be substantially identical to a frame generated via the second device. For example, the frame (e.g., frame 402 of Fig. 4A) via a node element (e.g. node element section 400 of Fig. 4A) can be generated.
[0065] At block 908, the associated sequence number may be incremented at both the first device and the second device in response to the generation of the associated frame, and the method 900 may continue to block 910. For example, a sequence number may be incremented via the sequence counter 406 from Fig. 4A in response to receiving an event signal 420 (e.g., a pulse) from the event generator 404.
[0066] At block 910, the associated sequence number indicating a number of frames generated and / or received at the associated device since the reset event of block 904 may be determined at both the first device and the second device, and the method 900 may continue with block 912. In particular, the sequence number indicating a number of frames generated and / or received at a node element (e.g., node element section 400 of Fig. 4A) were generated and / or received, are determined via a counter (e.g. sequence counter 406 of Fig. 4).
[0067] At block 912, the associated sequence number may be inserted into an associated frame at both the first device and the second device, and the method 900 may continue to block 914. For example, the sequence number may be inserted via logic (e.g., logic 408 in Fig. 4A) into an available section of a frame (e.g. frame 402 in Fig. 4A) should be inserted.
[0068] At block 914, the frame including a sequence number may be transmitted at both the first device and the second device, and the method 900 may continue to block 916. For example, an associated frame may be transmitted (e.g., via a bus) from the first device and the second device to an end system (e.g., end system 304).
[0069] At block 916, a first frame including the sequence number and received from the first device (e.g., device 302A of Fig. 3) and a second frame including the sequence number and transmitted by the second device (e.g., device 302B of Fig. 3) is transmitted to an end system (e.g. the end system 304 of Fig. 3) are received, and the method 900 may proceed to block 918.
[0070] At block 918, either the first frame or the second frame may be discarded at the end system. Specifically, because the first frame and the second frame include identical sequence numbers, the end system may discard either the first frame or the second frame.
[0071] Modifications, additions, or omissions may be made to method 900 without departing from the scope of the present disclosure. For example, the acts of method 900 may be implemented in different orders. Furthermore, the outlined acts and actions are provided only as examples, and some of the acts and actions may be optional, combined into fewer acts and actions, or expanded into additional acts and actions without affecting the essence of the disclosed embodiment.
[0072] As used in the present disclosure, the terms "module" or "component" may refer to specific hardware implementations configured to perform the actions of the module or component and / or software objects or software routines that may be stored on and / or executed by general-purpose hardware (e.g., computer-readable media, processing devices, etc.) of the computing system. In some embodiments, the various components, modules, engines, and services described in the present disclosure may be implemented as objects or processes that execute on the computing system (e.g., as separate threads).Although some of the systems and methods described in the present disclosure are generally described as being implemented in software (stored on and / or executed by general purpose hardware), specific hardware implementations or a combination of software and specific hardware implementations are also possible and are contemplated.
[0073] As used in the present disclosure, the term "combination" when referring to a plurality of elements may include a combination of all of the elements or any of various different subcombinations of some of the elements. For example, the phrase "A, B, C, D, or combinations thereof" may refer to any one of A, B, C, or D; the combination of any of A, B, C, and D; and any subcombination of A, B, C, or D, such as A, B, and C; A, B, and D; A, C, and D; B, C, and D; A and B; A and C; A and D; B and C; B and D; or C and D.
[0074] Terms used in the present disclosure, and in particular in the appended claims (e.g., contents of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including, but not limited to," the term "comprising" should be interpreted as "at least comprising," the term "includes" should be interpreted as "includes, but not limited to," etc.).
[0075] Furthermore, if a specific number of an introduced claim statement is intended, that intention will be expressly stated in the claim, and in the absence of such a statement, no such intention exists. As an aid to understanding, for example, the following accompanying claims may include the use of the introductory phrases "at least one" and "one or more" to introduce claim statements. However, the use of such language should not be construed to imply that the introduction of a claim statement by the indefinite articles "a" or "an" limits a particular claim containing such an introduced claim statement to embodiments containing only one such statement, even if the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" and / or "an" (e.g.,“a” and / or “an” should be interpreted to mean “at least one” or “one or more”; the same applies to the use of certain articles used to introduce claim particulars.
[0076] Furthermore, even if a specific number of introduced claim elements is explicitly stated, one skilled in the art will recognize that such an indication should be interpreted to mean at least the stated number (e.g., simply stating “two elements” without other modifiers means at least two elements or two or more elements). Furthermore, where a convention analogous to “at least one of A, B, and C, etc.” or “one or more of A, B, and C, etc.” is used, such a construction is generally intended to include A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together, etc.
[0077] Furthermore, any disjoint word or phrase representing two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibility of including either term, one or the other, or both. For example, the phrase "A or B" should be understood to include the possibilities "A" or "B" or "A and B." Although the present disclosure has been described herein with respect to certain illustrated embodiments, those of ordinary skill in the art will recognize and appreciate that the present invention is not so limited.Rather, numerous additions, omissions, and modifications may be made to the illustrated and described embodiments without departing from the scope of the invention as claimed below, along with its legal equivalents. Furthermore, features of one embodiment may be combined with features of another embodiment and still be included within the scope of the invention contemplated by the inventor.
Claims
[1] Network, comprising: a first device (302A); and a second device (302B) that is time-of-day synchronized (TOD-synchronized) with the first device (302A), wherein both the first device (302A) and the second device (302B) are configured to: generating (702A, 702B) a frame for transmission, wherein the frame generated via the second device (302B) is substantially identical to the frame generated via the first device (302A); Incrementing (704A, 704B) a count value in response to the generation of the associated frame at both the first device (302A) and the second device (302B), wherein the count value at the first device (302A) is the same as the count value at the second device (302B); Inserting (706A, 706B) the count value into the associated frame; Transmitting (708A, 708B) the associated frame including the count value; and Resetting the count value to a predetermined initial count value in response to a timing event detectable at the first device (302A) and the second device (302B). [2] The network of claim 1, wherein each of the first device (302A) and the second device (302B) is further configured to compare one or more defined times to a current network time to detect the timing event. [3] The network of claim 1, wherein the first device (302A) comprises a master device and the second device (302B) comprises a slave device, the first device (302A) being configured to define the timing event. [4] The network of claim 1, wherein each of the first device (302A) and the second device (302B) includes an associated sequence counter to generate the count value. [5] The network of claim 4, wherein each of the first device (302A) and the second device (302B) is configured to, in response to the timing event, reset its associated sequence counter for a sufficient period of time such that the count value is reset to the initial predetermined count value. [6] The network of claim 1, further comprising a third device configured to: Receiving a first frame including the count value from the first device (302A); Receiving a second frame including the count value from the second device (302B); and Discard either the first frame or the second frame. [7] A method for synchronizing sequence numbers in a number of redundant devices of a network, the method comprising: Resetting (904) a sequence number to an initial predetermined count in response to a reset event at both a first device (302A) and a second device (302B) of the network; generating (906) a frame for transmission at both the first device (302A) and the second device (302B), wherein the frame generated via the first device (302A) is substantially identical to the frame generated via the second device (302B); Incrementing (908) the sequence number in response to the generation of the associated frame at both the first device (302A) and the second device (302B), the sequence number indicating a number of frames generated at the associated device since the reset event (910); and Inserting (912) the sequence number into an associated frame at both the first device (302A) and the second device (302B). [8] The method of claim 7, wherein resetting (904) the sequence number to the initial predetermined count value in response to the reset event comprises resetting the sequence number in response to a timing event. [9] The method of claim 8, further comprising detecting the timing event. [10] The method of claim 9, further comprising comparing a current time to a defined time, wherein detecting the timing event comprises detecting the timing event in response to the current time being equal to the defined time. [11] The method of claim 8, further comprising: Receiving a signal indicative of a current network time at both the first device (302A) and the second device (302B); and Comparing the signal to one or more defined times to detect the timing event at both the first device (302A) and the second device (302B). [12] The method of claim 7, wherein incrementing (908) the sequence number comprises incrementing the sequence number via an associated sequence counter. [13] The method of claim 7, further comprising transmitting an associated frame including the sequence number from both the first device (302A) and the second device (302B). [14] The method of claim 13, further comprising: Receiving (916) a first frame including the sequence number from the first device (302A) at an end system (304); Receiving (916) a second frame including the sequence number from the second device (302B) at the end system (304); and Discarding (918) either the first frame or the second frame at the end system (304). [15] Equipment unit in a communications facility, comprising: a node element that is configured to: Generating a data frame for transmission; Incrementing a count value in response to generating the data frame; Inserting the count value into the data frame as a sequence number; Transmitting the data frame via a communication bus; and Resetting the count value to an initial predetermined count value in response to a timing event. [16] The equipment unit of claim 15, wherein the node element is further configured to detect the timing event in response to a current network time equal to a defined time. [17] Equipment unit according to claim 15, wherein the node element comprises logic configured to: Receiving a signal indicating a current network time; Comparing the signal with one or more defined times to detect the timing event; and in response to the timing event, transmitting a second signal to a sequence counter (406) to reset the sequence counter (406). [18] The equipment unit of claim 15, wherein the node element comprises a sequence counter (406) configured to increment the count value in response to the generation of the data frame. [19] The equipment unit of claim 18, wherein the node element is configured to reset the sequence counter (406) for a sufficient period of time such that the count value is reset to the initially predetermined count value. [20] The equipment unit of claim 18, wherein the node element includes logic configured to receive the count value from the sequence counter (406) and insert the count value into an available portion of the data frame.
Citation Information
Patent Citations
Method and System for Implementing Redundant Network Interface Modules in a Distributed I / O System
US20110161538A1
