System and method for forwarding network traffic
By adding frame-specific information headers and non-transient memory to the network interface circuit to detect duplicate data frames, combined with error detection, the problems of excessive traffic and data loops in cut-through forwarding networks are solved, achieving low-latency and high-efficiency data transmission.
Patent Information
- Application Number
- CN202380035290.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-19
- Filing Date
- 2023-06-21
- Publication Date
- 2024-11-29
AI Technical Summary
In pass-through networks, there are problems of excessive network traffic and unnecessary data loops, which lead to increased network complexity and latency, and bit errors may cause data frames to loop in the network.
By adding frame-specific information headers to the edge interface circuit and the internal interface circuit, and using non-transient memory for duplicate data frame detection and removal, combined with an error detector circuit, it is ensured that data frames are CRC checked and duplicate and erroneous frames are removed before forwarding.
It effectively prevents excessive network traffic and unnecessary data loops, reduces network latency, and improves the accuracy and efficiency of data transmission.
Smart Images

Figure CN119054270A_ABST
Abstract
Description
[0001] priority
[0002] This application claims priority to commonly owned U.S. Patent Application No. 63 / 404,736, filed on September 8, 2022, the entire contents of which are hereby incorporated by reference for all purposes. Technical Field
[0003] The present disclosure relates to forwarding traffic in a computer network. Background Art
[0004] In computer networks, the task of network components, including but not limited to switches and routers, is to receive data at their input ports (also called ingress ports) and forward the received data to the appropriate destination through their output ports (also called egress ports). This process of sending incoming data to the appropriate destination group is called forwarding in computer networking.
[0005] In one type of network, often referred to as a store and forward (S&F) network, a network element may receive incoming frames at its ingress port. The data frame is received in its entirety before a forwarding decision is made. Once the entire data frame is received and buffered, the network element compares the cyclic redundancy check (CRC) data included in the frame to determine the correctness of the received data. If the CRC check indicates that the data is correct, the data is forwarded to the appropriate media access control (MAC) address.
[0006] In another type of network, often referred to as a cut-through forwarding (CTF) network, only a small portion of an incoming frame is received, and once a forwarding decision is made, the network element begins sending the incoming frame data to the appropriate egress port. The forwarding decision may include a MAC address destination, or may include other information. The network element does not wait to receive the entire frame before beginning to forward the frame to the appropriate destination.
[0007] Cut-through forwarding is advantageous in many applications because it provides low latency forwarding through network elements, and this low latency can be fixed and independent of frame size.
[0008] Before forwarding to the next destination in the network, the cut-through forwarding may not detect and discard frames exposed to bit errors. The first network component may start forwarding the beginning of the frame before receiving the end of the frame at its inlet port, thereby forwarding the frame to the appropriate destination at the second network component at its outlet port. The second network component may receive the data frame at its inlet port, and similarly start forwarding the beginning of the frame before receiving the end of the frame at its inlet port, thereby forwarding the frame to the third network component at its outlet port. In a similar manner, data frames can be forwarded across many network components in the CTF network. When the end of the frame is received at the first network component, a CRC check can be performed. If an error is detected, the frame has been forwarded to at least one destination. In a broadcast or multicast network implementation, an erroneous data frame may be forwarded to many destinations in the network before the error is detected. Correcting these erroneous data frames increases the complexity of the network and increases delay. In addition, bit errors in the frame fields used in forwarding decisions may cause data frames to circulate in the network because data frames are continuously forwarded to incorrect destinations.
[0009] In a network using cut-through forwarding, a mechanism is needed to prevent excessive network traffic and unnecessary data traffic loops. Summary of the invention
[0010] Examples herein implement devices, systems, and methods for low-latency network forwarding that eliminates excess network traffic and unnecessary data loops.
[0011] According to one aspect, examples herein enable a device including an edge interface circuit to be coupled to a network component and to a repeater circuit. The edge interface circuit receives a data frame from the network component, appends a frame-specific information header to the front of the received data frame, and forwards the front-appended data frame to the repeater circuit. The edge interface circuit receives a data frame from the repeater circuit, removes duplicate data frames, and forwards non-duplicate data frames to the network component. The internal interface circuit is coupled to an internal network segment and to the repeater circuit, and the internal interface circuit receives a data frame from the internal network segment and forwards the received data frame to the repeater circuit. The internal interface circuit receives a data frame from the repeater circuit, removes duplicate data frames, and forwards non-duplicate data frames to the internal network segment.
[0012] According to one aspect, examples herein implement a system including a network. The network includes a plurality of network connection devices. The network connection device includes an edge interface circuit coupled to a network component and coupled to a repeater circuit, the edge interface circuit receiving a data frame from the network component, appending a frame-specific information header to the front of the received data frame, and forwarding the front appended data frame to the repeater circuit. The edge interface circuit receives the data frame from the repeater circuit, removes duplicate data frames, and forwards non-duplicate data frames to the network component. The internal interface circuit is coupled to an internal network segment and coupled to the repeater circuit, wherein the internal interface circuit receives the data frame from the internal network segment and forwards the received data frame to the repeater circuit. The internal interface circuit receives the data frame from the repeater circuit, removes duplicate data frames, and forwards the non-duplicate data frames to the internal network segment.
[0013] According to one aspect, an example implementation of the present invention includes a method of performing the following operations: receiving a data frame from a network component at an edge interface circuit; generating a frame-specific information header based on the received data frame; appending the frame-specific information header as a tag in front of the received data frame to generate the previously appended data frame; forwarding the previously appended data frame to a repeater circuit; receiving a data frame from a repeater circuit at the edge interface circuit and discarding a data frame with a detected error; identifying duplicate received data frames based on the contents of a non-volatile memory and the frame-specific information header; removing duplicate received data frames; removing the frame-specific information header from non-duplicate received data frames to create an updated data frame; forwarding the updated data frame to a network destination through an egress port; receiving a data frame from an internal network segment at an internal interface circuit; forwarding the received data frame to a repeater circuit; receiving a data frame from a repeater circuit at the internal interface circuit; identifying duplicate received data frames based on the contents of a non-volatile memory and the frame-specific information header; removing duplicate received data frames; and forwarding the non-duplicate data frames to a network component. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The accompanying drawings illustrate examples of systems for controlling network traffic.
[0015] Figure 1 One example among various examples of computer networks is shown.
[0016] Figure 2 One example among various examples of edge circuits is shown.
[0017] Figure 3 A method for controlling network traffic is shown. DETAILED DESCRIPTION
[0018] Figure 1 One example among various examples of computer network 100 is shown. Figure 1 Examples include network components 110, 130, and 140. Network components 110, 130, and 140 may include, but are not limited to, bridges, switches, and routers. It is not required that network components 110, 130, and 140 be of the same type. Internal network segment 150 may include one or more network components that utilize the CTF protocol. Edge circuits 115, 135, and 145 may connect internal network segment 150 to network components 110, 130, and 140, respectively. Cut-through forwarder circuits 151 and 152 of internal network segment 150 may forward data frames between edge circuits 115, 135, and 145 using the CTF protocol.
[0019] The network component 110 may be coupled to the internal network segment 150 via an edge circuit 115. The edge circuit 115 may include a first edge interface circuit 118 that communicates with the network component 110 using a store and forward protocol. The first edge interface circuit 118 may include at least one ingress port 111 and at least one egress port 112. The first edge interface circuit 118 may receive data from the network component 110 via the ingress port 111. The first edge interface circuit may send data to the network component 110 via the egress port 112. The edge circuit 115 may include one or more internal interface circuits 116, 117 to communicate with cut-through forwarder circuits 151 and 152 of the internal network segment 150.
[0020] Figure 1 The example shown includes two cut-through repeater circuits 151 and 152 for the internal network segment 150, but this is not intended to be limiting. Other examples may include, for example, Figure 1 More through-repeater circuits than those shown, or may include more through-repeater circuits than those shown. Figure 1 Those shown have fewer straight-through repeater circuits.
[0021] like Figure 1 The particular configuration of network elements and the particular paths between network elements shown are for illustrative purposes and are not intended to be limiting.
[0022] The edge circuit 115 may receive a data frame from the network component 110 via the ingress port 111 at the first edge interface circuit 118. The data frame received at the edge circuit 115 may include identification information. The edge circuit 115 may include an error detector circuit 172 to detect errors in the received data frame. The error detector circuit 172 may perform a CRC check or other error detection check on the received data frame. The edge circuit 115 may perform a CRC check or other error detection check on the received data frame. The edge circuit 115 may append a frame-specific information header in front of the received data frame to create the data frame appended in front. The frame-specific information header may be generated by the identification circuit 175. The identification circuit 175 may be implemented in hardware or software or a combination thereof. The identification circuit 175 may be integrated into the first edge interface circuit 118, or may be a separate component. The frame-specific information header may include a source MAC address for the received data frame. The frame-specific information header may include an identifier associated with the received data frame. The identifier may also be referred to as a frame number. The identifier or frame number can distinguish a first received data frame received from a specific MAC address from a second received data frame received from the same MAC address at an earlier or later point in time. The frame-specific information header can be part of a tag that is appended to the front of the received data frame to generate the previously appended data frame. The tag can be appended to the front by the tag insertion circuit 176. The tag insertion circuit 176 can be coupled to the identification circuit 175 and can be implemented in hardware or software or a combination thereof. The tag insertion circuit 176 can be integrated into the first edge interface circuit 118, or can be a separate component. The previously appended data frame with the frame-specific information header appended to the front can be forwarded to other destinations in the network. The previously appended data frame with the frame-specific information header appended to the front can be forwarded to the forwarder circuit 152 of the internal network segment 150 via the forwarder circuit 113, the internal interface circuit 117 and the path 162. The data frame having the frame-specific information header appended thereto may be forwarded by the forwarder circuit 113 to the forwarder circuit 151 of the internal network segment 150 via the forwarder circuit 113 , the internal interface circuit 116 , and the path 161 .
[0023] The edge circuit 115 may receive a data frame at the internal interface circuit 116 via the path 161. The data frame received at the edge circuit 115 may include identification information. The edge circuit 115 may update a portion of the received data frame and forward the updated data frame to the network component 110 via the egress port 112 using the S&F protocol. The edge circuit 115 may include an error detector circuit 172 to detect errors in the received data frame and discard the data frame with the detected errors. The error detector circuit 172 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The edge circuit 115 may read a portion of the received data frame including a frame-specific information header. The frame-specific information header may be present at a predetermined position in the received data frame. The edge circuit 115 may perform a lookup operation in cooperation with a remove duplicate table (RDT) 171 in the edge circuit 115 to determine whether the frame-specific information header in the received data frame matches the frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in the RDT 171 in the edge circuit 115. The RDT 171 may be a non-transitory memory. If the frame-specific information header of the received data frame is listed in the RDT 171, the received data frame may be discarded and not forwarded because it has been forwarded through the egress port 112. The lookup operation and discarding of duplicate data frames may be implemented by a duplicate removal circuit 173. The duplicate removal circuit 173 may be implemented in hardware or software or a combination thereof. If the frame-specific information header of the received data frame is not listed in the RDT 171, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 115 may add the frame-specific information header to the RDT 171. After performing the lookup operation, the edge circuit 115 may remove the frame-specific information header from the data frame to create an updated data frame. Removal of the frame-specific information header may be implemented by a label removal circuit 174. The label removal circuit 174 may be implemented in hardware or software or a combination thereof. The updated data frame may be forwarded to the first edge interface circuit 118 via the forwarder circuit 113. The updated data frame may be forwarded to the network component 110 at the egress port 112 via the first edge interface circuit 118.
[0024] The edge circuit 115 may receive a data frame at the internal interface circuit 117 via the path 162. The data frame received at the edge circuit 115 may include identification information. The edge circuit 115 may update a portion of the received data frame and forward the updated data frame to the network component 110 via the egress port 112 in the first edge interface circuit 118 using the S&F protocol. The edge circuit 115 may include an error detector circuit 172 to detect errors in the received data frame and discard the data frame with the detected error. The error detector circuit 172 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The edge circuit 115 may read a portion of the received data frame including a frame-specific information header. The frame-specific information header may be present at a predetermined position in the received data frame. The edge circuit 115 may perform a lookup operation in cooperation with the RDT 171 to determine whether the frame-specific information header matches the frame-specific information header of a previous data frame that has been forwarded. If the frame-specific information header of the received data frame is listed in the RDT 171, the received data frame may be discarded and not forwarded because it has been forwarded through the egress port 112 of the first edge interface circuit 118. The lookup operation and the discarding of duplicate data frames may be implemented by the duplicate removal circuit 173. If the frame-specific information header of the received data frame is not listed in the RDT 171, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 115 may add the frame-specific information header to the RDT 171. After performing the lookup operation, the edge circuit 115 may remove the frame-specific information header from the data frame to create an updated data frame. The removal of the frame-specific information header may be implemented by the label removal circuit 174. The updated data frame may be forwarded to the first edge interface circuit 118 via the repeater circuit 113. The updated data frame may be forwarded to the network component 110 at the egress port 112.
[0025] The network component 140 may be coupled to an edge circuit 145. The edge circuit 145 may include one or more edge interface circuits 148, 149 that communicate with the network component 140 using a store and forward protocol. The first edge interface circuit 148 may communicate with the network component 140 via an ingress port 141 and an egress port 142. The second edge interface circuit 149 may communicate with the network component 140 via an ingress port 143 and an egress port 144. The edge circuit 145 may include one or more internal interface circuits 146, 147 to communicate with other network components in the internal network segment 150.
[0026] The edge circuit 145 may receive a data frame from the network component 140 via the ingress port 141 at the first edge interface circuit 148. The edge circuit 145 may include an error detector circuit 182 to detect errors in the received data frame. The error detector circuit 182 may perform a CRC check or other error detection check on the received data frame. The data frame received at the edge circuit 145 may contain identification information. The edge circuit 145 may append a frame-specific information header to the front of the received data frame to create the front-appended data frame. The frame-specific information header may be generated by the identification circuit 185 of the edge circuit 145. The identification circuit 185 may be implemented in hardware or software or a combination thereof. The identification circuit 185 may be integrated into the first edge interface circuit 148, or may be a separate component. The frame-specific information header may include an identifier associated with the received data frame. The frame-specific information header may be part of a label that is appended to the front of the received data frame to generate the front-appended data frame. The label may be appended to the front by the label insertion circuit 186 of the edge circuit 145. The label insertion circuit 186 may be coupled to the identification circuit 185 and may be implemented in hardware or software or a combination thereof. The data frame having the frame-specific information header appended thereto may be forwarded to the pass-through forwarder circuit 151 of the internal network segment 150 via the forwarder circuit 174, the internal interface circuit 146, and the path 166. The data frame having the frame-specific information header appended thereto may be forwarded to the edge circuit 135 via the forwarder circuit 174, the internal interface circuit 147, and the path 164.
[0027] The edge circuit 145 may receive a data frame from the network component 140 via the ingress port 143 at the second edge interface circuit 149. The edge circuit 145 may include an error detector circuit 182 to detect errors in the received data frame. The error detector circuit 182 may perform a CRC check or other error detection check on the received data frame. The data frame received at the edge circuit 145 may contain identification information. The edge circuit 145 may append a frame-specific information header to the front of the received data frame to create the front-appended data frame. The frame-specific information header may be generated by the identification circuit 185. The identification circuit 175 may be integrated into the second edge interface circuit 149, or may be a separate component. The frame-specific information header may include an identifier associated with the received data frame. The identifier may also be referred to as a frame number. The identifier or frame number may distinguish between a first received data frame received from a specific MAC address and a second received data frame received from the same MAC address at an earlier or later point in time. The frame-specific information header may be part of a label appended to the front of the data frame. The label may be inserted by the label insertion circuit 186. The label insertion circuit 186 may be integrated into the second edge interface circuit 149, or may be a separate component. The previously appended data frame having the previously appended frame-specific information header may be forwarded to other destinations in the network. The previously appended data frame having the previously appended frame-specific information header may be forwarded to the edge circuit 135 via the repeater circuit 174, the internal interface circuit 147, and the path 164. The previously appended data frame having the previously appended frame-specific information header may be forwarded to the pass-through repeater circuit 151 of the internal network segment 150 via the repeater circuit 174, the internal interface circuit 146, and the path 166.
[0028] The edge circuit 145 may receive a data frame at the first internal interface circuit 146 via the path 166. The edge circuit 145 may include an error detector circuit 182 to detect errors in the received data frame and discard the data frame with the detected error. The error detector circuit 182 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The data frame received at the edge circuit 145 may contain identification information. The edge circuit 145 may update a portion of the received data frame and forward the updated data frame to the network component 140 via the egress port 142 using the S&F protocol. The edge circuit 145 may read a portion of the received data frame including a frame-specific information header. The edge circuit 145 may perform a lookup operation in cooperation with the RDT 181 in the edge circuit 145 to determine whether the frame-specific information header matches the frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in the RDT 181 in the edge circuit 145. The RDT 181 may be a non-transitory memory. If the frame-specific information header of the received data frame is listed in the RDT 181, the received data frame may be discarded and not forwarded because it has been forwarded via the egress port 142. The edge circuit 145 may include an error detector circuit 182 to detect errors in the received data frame and discard the data frame with the detected errors. The lookup operation and the discarding of duplicate data frames may be implemented by a duplicate removal circuit 183 in the edge circuit 145. The duplicate removal circuit 183 may be implemented in hardware or software or a combination thereof. The duplicate removal circuit 183 may include a first circuit for detecting duplicate data frames forwarded to the egress port 142 and a second circuit for detecting duplicate data frames forwarded to the egress port 144. If the frame-specific information header of the received data frame is not listed in the RDT 181, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 145 may add the frame-specific information header to the RDT 181. After performing the lookup operation, the edge circuit 145 may remove the frame-specific information header from the data frame to create an updated data frame. The removal of the frame-specific information header may be implemented by the label removal circuit 184 in the edge circuit 145. The label removal circuit 184 may be implemented in hardware or software or a combination thereof. The updated data frame may be forwarded to the first edge interface circuit 148 via the forwarder circuit 174. The updated data frame may be forwarded to the network component 140 at the egress port 142 via the first edge interface circuit 148.
[0029] The edge circuit 145 may receive a data frame at the internal interface circuit 147 via the path 164. The edge circuit 145 may include an error detector circuit 182 to detect errors in the received data frame and discard the data frame with the detected error. The error detector circuit 182 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The data frame received at the edge circuit 145 may contain identification information. The edge circuit 145 may update a portion of the received data frame and forward the updated data frame to the network component 140 via the egress port 144 using the S&F protocol. The edge circuit 145 may read a portion of the received data frame including a frame-specific information header. The frame-specific information header may be present at a predetermined position in the received data frame. The edge circuit 145 may perform a lookup operation in cooperation with the RDT 181 to determine whether the frame-specific information header matches the frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in the RDT 181 in the edge circuit 145. The RDT 181 may be a non-transitory memory. For a data frame forwarded to the egress port 144, if a frame-specific information header of a received data frame is listed in the RDT 181, the received data frame may be discarded and not forwarded because it has been forwarded through the egress port 144. For a data frame forwarded to the egress port 142, if a frame-specific information header of a received data frame is listed in the RDT 181, the received data frame may be discarded and not forwarded because it has been forwarded through the egress port 142. The lookup operation and the discarding of duplicate data frames may be implemented by the duplicate removal circuit 183. For a data frame forwarded to the egress port 144, if a frame-specific information header of a received data frame is not listed in the RDT 181, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 145 may add the frame-specific information header to the RDT 181. For the data frame forwarded to the egress port 142, if the frame-specific information header of the received data frame is not listed in the RDT 181, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 145 may add the frame-specific information header to the RDT 181. After performing the lookup operation, the edge circuit 145 may remove the frame-specific information header from the data frame to create an updated data frame. The removal of the frame-specific information header may be implemented by the label removal circuit 184 in the edge circuit 145. The updated data frame may be forwarded to the second edge interface circuit 149 via the repeater circuit 174. The updated data frame may be forwarded to the network component 140 at the egress port 144 via the second edge interface circuit 149.
[0030] The network component 130 may be coupled to an edge circuit 135. The edge circuit 135 may include a first edge interface circuit 138 that communicates with the network component 130 using a store and forward protocol. The first edge interface circuit 138 may communicate with the network component 130 via an ingress port 132 and an egress port 131. The edge circuit 135 may include one or more internal interface circuits 136, 137 to communicate with an internal network segment 150.
[0031] The edge circuit 135 may receive a data frame at the first edge interface circuit 138 via the ingress port 132. The edge circuit 135 may include an error detector circuit 192 to detect errors in the received data frame. The error detector circuit 192 may perform a CRC check or other error detection check on the received data frame. The data frame received at the edge circuit 135 may contain identification information. The edge circuit 135 may append a frame-specific information header to the front of the received data frame to create the front-appended data frame. The frame-specific information header may be generated by the identification circuit 195. The identification circuit 195 may be implemented in hardware or software or a combination thereof. The frame-specific information header may include an identifier associated with the received data frame. The identifier may also be referred to as a frame number. The frame-specific information header may be part of a tag that is appended to the front of the received data frame to generate the front-appended data frame. The tag may be appended to the front by the tag insertion circuit 196. The tag insertion circuit 196 may be coupled to the identification circuit 195 and may be implemented in hardware or software or a combination thereof. The label insertion circuit 196 may be integrated into the first edge interface circuit 138, or may be a separate component. The previously appended data frame having the previously appended frame-specific information header may be forwarded to the edge circuit 145 via the repeater circuit 133, the internal interface circuit 137, and the path 164. The previously appended data frame having the previously appended frame-specific information header may be forwarded to the pass-through repeater circuit 151 of the internal network segment 150 via the repeater circuit 133, the internal interface circuit 137, and the path 165. The previously appended data frame having the previously appended frame-specific information header may be forwarded to the pass-through repeater circuit 152 of the internal network segment 150 via the repeater circuit 133, the internal interface circuit 136, and the path 163.
[0032] The edge circuit 135 may receive a data frame at the first internal interface circuit 136 via the path 163. The edge circuit 135 may include an error detector circuit 192 to detect errors in the received data frame and discard the data frame with the detected error. The error detector circuit 192 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The data frame received at the edge circuit 135 may contain identification information. The edge circuit 135 may update a portion of the received data frame and forward the updated data frame to the network component 130 via the egress port 131 using the S&F protocol. The edge circuit 135 may read a portion of the received data frame including a frame-specific information header. The frame-specific information header may be present at a predetermined position in the received data frame. The edge circuit 135 may perform a lookup operation to determine whether the frame-specific information header matches a frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in an RDT 191 in the edge circuit 135. The RDT 191 may be a non-transitory memory. If the frame-specific information header of the received data frame is listed in the RDT 191, the received data frame may be discarded and not forwarded because it has already been forwarded through the egress port 131. The lookup operation and the discarding of duplicate data frames may be implemented by the duplicate removal circuit 193 of the edge circuit 135. The duplicate removal circuit may be implemented in hardware or software or a combination thereof. If the frame-specific information header of the received data frame is not listed in the RDT 191, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 135 may add the frame-specific information header to the RDT 191. After performing the lookup operation, the edge circuit 135 may remove the frame-specific information header from the data frame to create an updated data frame. The removal of the frame-specific information header may be implemented by the label removal circuit 194 of the edge circuit 135. The label removal circuit 194 may be implemented in hardware or software or a combination thereof. The updated data frame may be forwarded to the edge interface circuit 138 via the repeater circuit 133. The updated data frame may be forwarded to the network component 130 at the egress port 131 via the edge interface circuit 138. The error detector circuit 192 may be included in the duplicate removal circuit 193 or may be a separate circuit.
[0033] The edge circuit 135 may receive a data frame at the internal interface circuit 137 via path 164. The edge circuit 135 may receive data at the internal interface circuit 137 via path 165. The edge circuit 135 may include an error detector circuit 192 to detect errors in the received data frame and discard the data frame with the detected error. The error detector circuit 192 may perform a CRC check or other error detection check on the received data frame. If an error is detected, the frame may be discarded. The data frame received at the edge circuit 135 may contain identification information. The edge circuit 135 may update a portion of the received data frame and forward the updated data frame to the network component 130 via the egress port 131 using the S&F protocol. The edge circuit 135 may read a portion of the received data frame including a frame-specific information header. The edge circuit 135 may perform a lookup operation in cooperation with the RDT 191 to determine whether the frame-specific information header matches the frame-specific information header of a previous data frame that has been forwarded. If the frame-specific information header of the received data frame is listed in the RDT 191, the received data frame may be discarded and not forwarded because it has already been forwarded through the egress port 131. If the frame-specific information header of the received data frame is not listed in the RDT 191, the data frame may be referred to as a non-duplicate data frame, and the edge circuit 135 may add the frame-specific information header to the RDT 191. After performing the lookup operation, the edge circuit 135 may remove the frame-specific information header from the data frame to create an updated data frame. The removal of the frame-specific information header may be implemented by the label removal circuit 194 in the edge circuit 135. The updated data frame may be forwarded to the edge interface circuit 138 via the repeater circuit 133. The updated data frame may be forwarded to the network component 130 via the egress port 131 via the edge interface circuit 138.
[0034] Figure 1 The examples shown are for illustrative purposes only and are not intended to limit the invention. Figure 1 The example shown includes a certain number of network components, edge interface circuits, internal interface circuits, and network components of internal network segments and edge circuits, and cut-through repeater circuits. Figure 1 The specific paths shown between network components, edge interface circuits, internal interface circuits, cut-through repeater circuits, and edge circuits are for illustrative purposes and are not intended to limit the invention.
[0035] Figure 1 Other examples not shown may include Figure 1 The number of network components shown is a greater number of network components. Figure 1 Other examples not shown may include Figure 1 The network components shown are fewer network components.
[0036] Figure 1 Other examples not shown may include Figure 1 The number of edge circuits shown is greater than the number of edge circuits shown. Figure 1 Other examples not shown may include Figure 1 The edge circuits shown have fewer edge circuits.
[0037] Figure 1 Other examples not shown may include Figure 1 The edge interface circuits shown have a greater number of edge interface circuits. Figure 1 Other examples not shown may include Figure 1 The edge interface circuits shown have a smaller number of edge interface circuits.
[0038] Figure 1 Other examples not shown may include Figure 1 The internal interface circuits shown have a greater number of internal interface circuits. Figure 1 Other examples not shown may include Figure 1 The internal interface circuits shown have a smaller number of internal interface circuits.
[0039] Figure 1 Other examples not shown may include Figure 1 The number of network components shown is a greater number of network components. Figure 1 Other examples not shown may include Figure 1 The network components shown are fewer network components.
[0040] Figure 1 Other examples not shown may include Figure 1 The specific network components shown may vary from network component to network component.
[0041] Figure 2 FIG. 2 shows one example of various examples of edge circuit 200. Edge circuit 200 may represent Figure 1 One example of various examples of edge circuit 145 is shown. Figure 2 In the example of FIG. 1 , the first edge interface circuit 270 and the second edge interface circuit 275 can interface with the network component 201, and the first internal interface circuit 280 and the second internal interface circuit 285 can interface with the internal network segment 202. The internal network segment 202 can be one example of various examples of the internal network segment 150, such as reference Figure 1 As shown and described.
[0042] The edge circuit 200 may include an RDT 290. The RDT 290 may be a non-transitory memory. In one of the various examples, the first edge interface circuit 270, the second edge interface circuit 275, the first internal interface circuit 280, and the second internal interface circuit 285 may each include an RDT. In one of the various examples, the RDT may be shared by more than one of the first edge interface circuit 270, the second edge interface circuit 275, the first internal interface circuit 280, and the second internal interface circuit 285.
[0043] The first edge interface circuit 270 may include an error detector circuit 296. The error detector circuit 296 may generate an output signal based on the detection of an error. The second edge interface circuit 275 may include an error detector circuit 297. The error detector circuit 297 may generate an output signal based on the detection of an error. The first internal interface circuit 280 may include an error detector circuit 298. The error detector circuit 298 may generate an output signal based on the detection of an error. The second internal interface circuit 285 may include an error detector circuit 299. Figure 2 The illustrated example shows separate error detector circuits for the first edge interface circuit 270, the second edge interface circuit 275, the first internal interface circuit 280, and the second internal interface circuit 285, respectively, but this is not intended to be limiting. In one of the various examples, a single error detector circuit can be shared by more than one of the first edge interface circuit 270, the second edge interface circuit 275, the first internal interface circuit 280, and the second internal interface circuit 285.
[0044] The forwarder circuit 205 may receive data from the first edge interface circuit 270 , the second edge interface circuit 275 , the first internal interface circuit 280 , and the second internal interface circuit 285 , and may forward the received data to a suitable destination.
[0045] The first edge interface circuit 270 may receive a data frame from the repeater circuit 205 via the path 210. The data frame may be received by the error detector circuit 296. The error detector circuit 296 may check for errors in the data frame and may discard frames with detected errors. The check error may be a CRC check or another error checking technique. The error detector circuit 296 may detect errors in the data frame and may provide an error output to the duplicate removal circuit 211. The duplicate removal circuit 211 may remove the data frame with errors based on the error output. The duplicate removal circuit 211 may include a controller circuit for performing a lookup operation to determine whether a frame-specific information header of the received data frame matches a frame-specific information header of a previous data frame that has been forwarded at the egress port 272. Alternatively, the operation of the duplicate removal circuit 211 may be responsive to the controller 295. If the frame-specific information header of the received data is listed in the RDT 290, the received frame is discarded by the duplicate removal circuit 211 and is not forwarded because it has been forwarded through the egress port 272. If the frame-specific information header of the received data is not listed in the RDT 290, the data frame may be referred to as a non-duplicate data frame, and the controller circuit 295 may add the frame-specific information header to the RDT 290. The label removal circuit 212 may remove the frame-specific information header from the frame and forward the updated frame from the first edge interface circuit 270 to the network component 201 at the egress port 272. The error detector circuit 296 may be included in the duplicate removal circuit 211, or may be a Figure 2 The individual circuits are shown.
[0046] The first edge interface circuit 270 can receive a data frame from the network component 201 via an ingress port 271. The ingress port 271 can be coupled to an identification circuit 222. The identification circuit 222 can append a frame-specific information header in front of the received data frame. The frame-specific information header may include an identifier associated with the received data frame. The identifier may also be referred to as a frame number. The identifier or frame number can distinguish a first received data frame received from a specific MAC address from a second received data frame received from the same MAC address at an earlier or later point in time. The identification circuit 222 can be coupled to a label insertion circuit 221. The label insertion circuit 221 can combine the frame-specific information header with the received data frame to create a previously appended data frame. The previously appended data frame can be forwarded to the forwarder circuit 205 via the path 220 for forwarding to other destinations on the network.
[0047] The second edge interface circuit 275 may receive a data frame from the repeater circuit 205 via the path 230. The network component 201 may be handed over to the second edge interface circuit 275. The data frame may be received by the error detector circuit 297. The error detector circuit 297 may check errors in the data frame and may provide an error output to the duplicate removal circuit 231. The error check may be a CRC check or another error check technique. The duplicate removal circuit 231 may remove the data frame with errors based on the error output. The duplicate removal circuit 231 may include a controller circuit for performing a lookup to determine whether a frame-specific information header of the received data frame matches a frame-specific information header of a previous data frame that has been received. Alternatively, the operation of the duplicate removal circuit 231 may be responsive to the controller 295. If the frame-specific information header of the received data is listed in the RDT 290, the received frame is discarded by the duplicate removal circuit 231 and is not forwarded because it has been forwarded through the egress port 277. If the frame-specific information header of the received data is not listed in the RDT 290, the data frame may be referred to as a non-duplicate data frame, and the controller circuit 295 may add the frame-specific information header to the RDT 290. The label removal circuit 232 may remove the frame-specific information header from the frame and forward the updated frame from the second edge interface circuit 275 at the egress port 277. The error detector circuit 297 may be included in the duplicate removal circuit 231, or may be a Figure 2 The individual circuits are shown.
[0048] The second edge interface circuit 275 can receive a data frame via an ingress port 276. The ingress port 276 can be coupled to an identification circuit 242. The identification circuit 242 can append a frame-specific information header to the front of the received frame. The frame-specific information header may include an identifier associated with the received data frame. The identifier may also be referred to as a frame number. The identifier or frame number can distinguish a first received data frame received from a specific MAC address from a second received data frame received from the same MAC address at an earlier or later point in time. The identification circuit 242 can be coupled to a label insertion circuit 241. The label insertion circuit 241 can append a frame-specific information header to the front of the received data to create a front-appended data frame. The front-appended data frame including the frame-specific information header can be forwarded to the forwarder circuit 205 via the path 240 for forwarding to other destinations on the network.
[0049] The edge circuit 200 may receive a data frame from the internal network segment 202 at the first internal interface circuit 280 via the first ingress port 282. The received data frame may be forwarded to the repeater circuit 205 via the first egress port 250.
[0050] The first internal interface circuit 280 can forward the data frame through the second output port 281. The data frame can be received from the repeater circuit 205 via the second input port 255. The data frame can be received by the error detector circuit 298. The error detector circuit 298 can check the error in the data frame and can provide an error output to the duplicate removal circuit 251. The error check can be a CRC check or another error check technology. The duplicate removal circuit 251 can remove the data frame with errors based on the error output. The duplicate removal circuit 251 can read the portion of the received data frame including the frame-specific information header. The duplicate removal circuit 251 may include a controller circuit for performing a lookup operation and determining whether the frame-specific information header of the received data frame matches the frame-specific information header of the previous data frame that has been received and forwarded by the second output port 281. Alternatively, the operation of the duplicate removal circuit 251 can be responsive to the controller 295. If the frame-specific information header of the received data is listed in the RDT 290, the received frame is discarded and not forwarded because it has already been forwarded through the second egress port 281. If the frame-specific information header of the received data is not listed in the RDT 290, the data frame may be referred to as a non-duplicate data frame, and the controller circuit 295 may add this information to the RDT 290. The first internal interface circuit 280 may forward the frame via the second egress port 281. The error detector circuit 298 may be included in the duplicate removal circuit 251, or may be a Figure 2 The individual circuits are shown.
[0051] The edge circuit 200 may receive a data frame from the internal network segment 202 at the second internal interface circuit 285 via the first ingress port 287. The received data may be forwarded to the repeater circuit 205 via the first egress port 260.
[0052] The second internal interface circuit 285 may forward the data frame through the second egress port 286. Data may be received from the repeater circuit 205 via the second ingress port 265. The data frame may be received by the error detector circuit 299. The error detector circuit 299 may check for errors in the data frame and may provide an error output to the duplicate removal circuit 261. The error check may be a CRC check or another error checking technique. The duplicate removal circuit 261 may remove the data frame with errors based on the error output. The duplicate removal circuit 261 may read a portion of the received data frame including a frame-specific information header. The duplicate removal circuit 261 may include a controller circuit for performing a lookup to determine whether the frame-specific information header matches the frame-specific information of a previous data frame that has been forwarded by the second egress port 286. Alternatively, the operation of the duplicate removal circuit 231 may be responsive to the controller 295. If the frame-specific information header of the received data is listed in the RDT 290, the received frame is discarded and not forwarded because it has been forwarded through the second egress port 286. If the frame-specific information header of the received data is not listed in the RDT 290, the data frame may be referred to as a non-duplicate data frame, and the controller circuit 295 may add the frame-specific information header to the RDT 290. The second egress port 286 may forward the data to the internal network segment 202. The error detector circuit 299 may be included in the duplicate removal circuit 261, or may be a Figure 2 The individual circuits are shown.
[0053] Figure 3 A method for controlling network traffic is shown. Figure 2 The apparatus shown and described may perform the illustrated methods.
[0054] At operation 305, a data frame may be received by an edge interface circuit from a network component.
[0055] At operation 310, the edge interface circuit may generate frame identification information associated with the data frame. The frame-specific information header may include an identifier of the received data frame. The identifier may also be referred to as a frame number. The identifier or frame number may distinguish a first received data frame received from a particular MAC address from a second received data frame received from the same MAC address at an earlier or later point in time.
[0056] At operation 315, a frame-specific information header may be appended as a tag in front of the received data frame to generate a front-appended data frame.
[0057] At operation 320, the previously appended data frame may be forwarded to a repeater circuit.
[0058] At operation 325, a data frame may be received at the edge interface circuit from the repeater circuit. The data frame received at the edge interface circuit may be a previously appended data frame as described with reference to operations 305 to 320 inclusive. Error detection operations may be performed on the received data frame, and data frames with detected errors may be removed.
[0059] At operation 330, duplicate data frames received at the edge interface circuit may be selectively removed. A frame-specific information header may be read from a portion of the received data frame. The frame-specific information header may be present at a predetermined position in the received data frame. A lookup operation may determine whether the frame-specific information header in the received data frame matches a frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in the RDT. If the frame-specific information header of the received data frame is listed in the RDT, the received data frame may be discarded and not forwarded because it has already been forwarded.
[0060] At operation 335 , if the received data frame is not a duplicate, a frame-specific information header may be removed from the received data frame to create an updated data frame.
[0061] At operation 340, the updated data frame may be forwarded to a network component via an egress port.
[0062] At operation 345, a data frame may be received at the internal interface circuit from the network component. At operation 350, the received data frame may be forwarded to the repeater circuit.
[0063] At operation 355, a data frame may be received from a repeater circuit at an internal interface circuit. The data frame received at the internal interface circuit may be a previously appended data frame as described with reference to operations 305 to 320 (including these operations). An error detection operation may be performed on the received data frame, and a data frame with a detected error may be removed. At operation 360, if the received data frame is a duplicate data frame, the received data frame may be selectively removed. A frame-specific information header may be read from a portion of the received data frame. The frame-specific information header may be present at a predetermined position in the received data frame. A lookup operation may determine whether the frame-specific information header in the received data frame matches the frame-specific information header of a previous data frame that has been forwarded. The frame-specific information header may be stored in an RDT. If the frame-specific information header of the received data frame is listed in the RDT, the received data frame may be discarded and not forwarded because it has already been forwarded.
[0064] At operation 365, the non-duplicate received data frames may be forwarded to a network component.
Claims
1. A device, comprising: An edge interface circuit for coupling to a network component and for coupling to a repeater circuit, the edge interface circuit for: receiving a data frame from the network element, appending a frame-specific information header to the front of the received data frame and forwarding the front-appended data frame to the repeater circuit; as well as receiving data frames from the repeater circuit, removing duplicate data frames and forwarding non-duplicate data frames to the network component; and an internal interface circuit for coupling to an internal network segment and for coupling to the repeater circuit, the internal interface circuit for: receiving a data frame from the internal network segment and forwarding the received data frame to the repeater circuit, and Data frames are received from the repeater circuit, duplicate data frames are removed, and non-duplicate data frames are forwarded to the internal network segment.
2. The device of claim 1, wherein the edge interface circuit comprises: an ingress port, the ingress port being used to couple to the network component, the ingress port being used to receive a data frame; an identification circuit, the identification circuit being configured to be coupled to the first ingress port, the identification circuit being configured to generate a frame-specific information header based at least on the received data frame, and A label insertion circuit is coupled to the identification circuit, the label insertion circuit is used to append the frame-specific information header to the front of the received data frame to generate a front-appended data frame, and the label insertion circuit is used to forward the front-appended data frame to the repeater circuit.
3. The device of claim 2, wherein the edge interface circuit comprises: an error detector circuit for receiving a data frame from the repeater circuit; a duplicate removal circuit for removing duplicate data frames based at least on the contents of the non-transitory memory and the frame-specific information header; a label removal circuit, the label removal circuit being configured to be coupled to the duplicate removal circuit, the label removal circuit being configured to remove the frame-specific information header in the received data frame to generate an updated data frame; and An egress port, the egress port being configured to be coupled to the label removal circuit, the egress port being configured to forward the updated data frame to the network component.
4. The apparatus of claim 3, wherein the duplicate removal circuit comprises a controller circuit for searching the contents of the non-transitory memory for the presence of a portion of a received data frame within the contents of the non-transitory memory.
5. The apparatus of any one of claims 3 to 4, the duplicate removal circuit being operable to remove received data frames based on the output of the error detector circuit.
6. The device according to any one of claims 1, wherein the internal interface circuit comprises: a first ingress port, the first ingress port being configured to be coupled to an internal network segment and to be coupled to the repeater circuit, the first ingress port being configured to receive a data frame from the internal network segment and to forward the received data frame to the repeater circuit via a first egress port; a second ingress port, the second ingress port being configured to be coupled to the repeater circuit, the second ingress port being configured to receive a data frame from the repeater circuit; an error detector circuit, the error detector circuit being configured to be coupled to the second input port; a duplicate removal circuit for being coupled to the error detector circuit, the duplicate removal circuit for removing duplicate received data frames based at least on the contents of the non-transitory memory and the frame-specific information header, and A second egress port, wherein the second egress port is used to forward the non-duplicate data frame to the internal network segment.
7. The apparatus of claim 6, wherein the duplicate removal circuit comprises a controller circuit for searching the contents of the non-transitory memory for the presence of a portion of the received data frame within the non-transitory memory contents.
8. The apparatus of any one of claims 6 to 7, the duplicate removal circuit being operable to remove received data frames based on an output of the error detector circuit.
9. A system, comprising: A network, the network comprising: A plurality of network connection devices, wherein the plurality of network connection devices include: An edge interface circuit for coupling to a network component and for coupling to a repeater circuit, the edge interface circuit for: receiving a data frame from the network element, appending a frame-specific information header to the front of the received data frame and forwarding the front-appended data frame to the repeater circuit; receiving data frames from the repeater circuit, removing duplicate data frames and forwarding non-duplicate data frames to the network component; an internal interface circuit for coupling to an internal network segment and for coupling to the repeater circuit, the internal interface circuit for: receiving a data frame from the internal network segment and forwarding the received data frame to the repeater circuit, and Data frames are received from the repeater circuit, duplicate data frames are removed, and non-duplicate data frames are forwarded to the internal network segment.
10. The system of claim 9, wherein the edge interface circuit comprises: an ingress port, the ingress port being used to couple to the network component, the ingress port being used to receive a data frame; an identification circuit, the identification circuit being configured to be coupled to the first ingress port, the identification circuit being configured to generate a frame-specific information header based at least on the received data frame, and A label insertion circuit is coupled to the identification circuit, the label insertion circuit is used to append the frame-specific information header to the front of the received data frame to generate a front-appended data frame, and the label insertion circuit is used to forward the front-appended data frame to the repeater circuit.
11. The system of claim 10, wherein the edge interface circuit comprises: an error detector circuit for receiving a data frame from the repeater circuit; a duplicate removal circuit for receiving a data frame from the error detector circuit, the duplicate removal circuit for removing duplicate data frames based at least on the contents of the non-transitory memory and the frame-specific information header; a label removal circuit, the label removal circuit being configured to be coupled to the duplicate removal circuit, the label removal circuit being configured to remove the frame-specific information header in the received data frame to generate an updated data frame; and An egress port, the egress port being configured to be coupled to the label removal circuit, the egress port being configured to forward the updated data frame to the network component.
12. The system of claim 11, wherein the duplicate removal circuit comprises a controller circuit for searching the contents of the non-transitory memory for the frame-specific information header within the contents of the non-transitory memory.
13. The system of any one of claims 11 to 12, the duplicate removal circuit being operable to remove received data frames based on an output of the error detector circuit.
14. The system according to any one of claims 11 to 13, wherein the internal interface circuit comprises: a first ingress port, the first ingress port being configured to be coupled to an internal network segment and to be coupled to the repeater circuit, the first ingress port being configured to receive a data frame from the internal network segment and to forward the received data frame to the repeater circuit via a first egress port; a second ingress port, the second ingress port being configured to be coupled to the repeater circuit, the second ingress port being configured to receive a data frame from the repeater circuit; an error detector circuit, the error detector circuit being configured to be coupled to the second input port; a duplicate removal circuit for coupling to the error detector circuit, the duplicate removal circuit for removing duplicate received data frames based at least on the contents of the non-transitory memory and the frame-specific information header; and A second egress port, wherein the second egress port is used to forward the non-duplicate data frame to the internal network segment.
15. The system of claim 14, wherein the duplicate removal circuit comprises a controller circuit for searching the contents of the non-transitory memory for the presence of the frame-specific information header within the non-transitory memory contents.
16. The system of any one of claims 14 to 15, the duplicate removal circuit being operable to remove received data frames based on an output of the error detector circuit.
17. A method comprising: receiving a data frame from a network element at an edge interface circuit; generating a frame-specific information header based on the received data frame; appending the frame-specific information header as a tag to the front of the received data frame to generate the front-appended data frame; forwarding the previously appended data frame to a repeater circuit; receiving data frames from the repeater circuit at the edge interface circuit and discarding the data frames having detected errors; identifying duplicate received data frames based on the contents of the non-transitory memory and the frame-specific information header; Remove duplicate received data frames; removing the frame-specific information header from the non-duplicate received data frame to create an updated data frame; forwarding the updated data frame to a network destination via an egress port; receiving a data frame from an internal network segment at an internal interface circuit; forwarding the received data frame to the repeater circuit; receiving a data frame from the repeater circuit at the internal interface circuit; identifying duplicate received data frames based on the contents of the non-transitory memory and the frame-specific information header; remove duplicate received data frames, and Forwards non-duplicate data frames to network elements.
18. The method of claim 17, wherein removing duplicate received data frames comprises searching the contents of the non-transitory memory for the frame-specific information headers within the non-transitory memory contents.
