Switching device and method
The switch device uses separate databases and queues with CAM and hash table configurations to address the challenge of low delay and high capacity, enhancing real-time performance and flexibility in Ethernet networks.
Patent Information
- Application Number
- JP2021099617
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-06-15
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-06-15
AI Technical Summary
Existing switch devices face challenges in achieving both low delay time and high database capacity for efficient frame transfer in Ethernet-based networks, particularly in industrial and in-vehicle networks requiring real-time performance.
The switch device employs separate databases and queues for real-time and best-effort frames, utilizing Content Addressable Memory (CAM) for fast access in the eFDB for real-time frames and a hash table for the larger capacity pFDB, along with frame preemption and time-aware shaper mechanisms to manage traffic.
This configuration minimizes delay and jitter for real-time frames while increasing the database capacity, ensuring high real-time performance and flexibility for varying network conditions.
Smart Images

Figure 0007577611000001 
Figure 0007577611000002 
Figure 0007577611000003
Abstract
Description
[Technical field]
[0001] FIELD An embodiment of the present invention relates to a switch device, a method, and a program. [Background technology]
[0002] For example, the use of Ethernet (registered trademark) is increasing in fields such as industrial networks that connect various devices placed in a factory and in-vehicle networks that connect various controllers of in-vehicle systems installed in vehicles such as automobiles.
[0003] Furthermore, in the above-mentioned industrial networks or in-vehicle networks, real-time performance may be required, and in order to realize this real-time performance, various network technologies (standards) that extend Ethernet have been proposed.
[0004] Incidentally, an Ethernet-based network is constructed using a switch device (communication control device) called an L2 switch. The switch device has multiple communication ports (network ports) and operates to transfer a frame (data) transmitted from an external communication device connected to a specific communication port to another external communication device connected to another communication port.
[0005] In order to realize real-time performance in a network constructed using such switch devices, it is important to reduce the delay time (transfer delay) and the jitter when the switch device transfers a frame.
[0006] On the other hand, a switch device refers to a database called an FDB (Forwarding / Filtering Database) to determine the communication port to which an external communication device to which a frame will be forwarded (destined) is connected. Considering the number of devices connected to the switch device, it is preferable for the capacity of the database (the number of entries it can accommodate) to be large.
[0007] However, when a database that can be accessed at high speed and with low latency is implemented to reduce the above-mentioned latency, it is difficult to increase the capacity of the database, i.e., it is difficult to achieve both latency reduction and database capacity increase in a switch device. [Prior art documents] [Patent documents]
[0008] [Patent Document 1] Patent No. 5433627 Summary of the Invention [Problem to be solved by the invention]
[0009] Therefore, an object of the present invention is to provide a switching device, a method, and a program that can achieve both a reduction in delay time and an increase in the capacity of a database. [Means for solving the problem]
[0010] According to an embodiment, there is provided a switch device having a plurality of communication ports. The switch device includes a receiving unit, first and second databases, and a determining unit. , a first receiving queue, and a second receiving queue.The communication system includes: a receiving unit configured to receive a frame transmitted from a first external communication device connected to a first communication port of the plurality of communication ports; and a first and second databases storing destination determination information used to determine a second communication port to which a second external communication device is connected, the second communication port being a destination of the received frame, among the plurality of communication ports. When the received frame is a first frame that requires low-latency transfer, the determining unit determines the second communication port by accessing the destination determination information stored in the first database based on header information added to the first frame, and when the received frame is a second frame different from the first frame, the determining unit determines the second communication port by accessing the destination determination information stored in the second database based on header information added to the second frame. The first receiving queue stores the first frame, and the second receiving queue stores the second frame. The first database is configured to be able to access the destination determination information at a higher speed than the second database. The determination unit includes a first and a second determination unit. The first determination unit determines the second communication port based on header information attached to a first frame retrieved from the first receiving queue. The second determination unit determines the second communication port based on header information attached to a second frame retrieved from the second receiving queue. [Brief description of the drawings]
[0011] [Figure 1] FIG. 2 is a diagram for explaining an example of the configuration of a switch device according to a first comparative example of the first embodiment. [Diagram 2] 4 is a diagram for explaining an example of the configuration of a destination determination unit included in a forwarding processing unit; FIG. [Diagram 3] 10 is a flowchart illustrating an example of a processing procedure of a destination determination unit. [Figure 4] 13 is a flowchart showing an example of a processing procedure for updating an FDB. [Diagram 5] FIG. 11 is a diagram for explaining an example of the configuration of a switch device according to a second comparative example of the embodiment. [Figure 6] 4 is a diagram for explaining an example of the configuration of a destination determination unit included in a forwarding processing unit; FIG. [Figure 7] FIG. 2 is a diagram for explaining an example of the configuration of a switch device according to the embodiment; [Figure 8]4 is a diagram for explaining an example of the configuration of a destination determination unit included in a forwarding processing unit; FIG. [Figure 9] 1A and 1B are diagrams for explaining specific application examples of the switch device according to the present embodiment. [Figure 10] FIG. 4 is a diagram for explaining the operation of a forwarding processing unit. [Figure 11] FIG. 4 is a diagram for explaining an example of the configuration of a switch device according to a first modified example of the embodiment. [Figure 12] FIG. 4 is a diagram showing an example of the configuration of a destination determination unit included in a forwarding processing unit; [Figure 13] FIG. 11 is a diagram for explaining an example of the configuration of a switch device according to a second modified example of the embodiment. [Figure 14] FIG. 4 is a diagram showing an example of the configuration of a destination determination unit included in a forwarding processing unit; [Figure 15] FIG. 4 is a diagram showing an example of a data structure of attribute information. [Figure 16] FIG. 2 is a diagram illustrating an example of a hardware configuration of a switch device. [Figure 17] FIG. 11 is a diagram for explaining an example of the configuration of a destination determination unit included in a forwarding processing unit in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Each embodiment will be described below with reference to the drawings. (First embodiment) First, a first embodiment will be described. The switch device according to this embodiment is a switch device (communication control device) such as an L2 switch used to construct a network based on Ethernet (hereinafter simply referred to as a network). The switch device has a plurality of communication ports (network ports) and operates to transfer a frame transmitted from an external communication device connected to a specific communication port to another external communication device connected to another communication port.
[0013] An example of the configuration of a switch device according to a first comparative example of this embodiment will be described below with reference to FIG.
[0014] 1 has, for example, N communication ports 1 to N, and is equipped with N communication processing units (communication interfaces) 11-1 to 11-N, N receive queues (Rx) 12-1 to 12-N, an FDB (Forwarding / Filtering Database) 13, a forwarding processing unit 14, N transmit queues (Tx) 15-1 to 15-N, and a management unit 16. It is assumed here that N external communication devices 1-1 to 1-N are connected to the N communication ports, respectively.
[0015] The N communication processing units 11-1 to 11-N correspond to the N communication ports 1 to N, and are configured to execute communication processing with the external communication devices 1-1 to 1-N.
[0016] Each of the communication processing units 11-1 to 11-N includes a function called a MAC (Media Access Controller) 11a and a PHY 11b, and performs processing required for transmitting and receiving frames according to the protocols of the data link layer and the physical layer in the network. That is, each of the communication processing units 11-1 to 11-N performs processing of the data link layer and the physical layer of the Ethernet.
[0017] The communication processing units 11-1 to 11-N receive frames transmitted from the external communication devices 1-1 to 1-N connected to the communication ports 1 to N. The frames received by the communication processing units 11-1 to 11-N are output to the receiving queues 12-1 to 12-N.
[0018] In the example shown in FIG. 1, the communication processing units 11-1 to 11-N are described as including MAC 11a and PHY 11b, but the communication processing units 11-1 to 11-N may be configured to include other functions (i.e., to execute other processes).
[0019] The N receiving queues 12-1 to 12-N correspond to the N communication processing units 11-1 to 11-N (communication ports 1 to N). The receiving queues 12-1 to 12-N are queues used to pass frames from the communication processing units 11-1 to 11-N to the forwarding processing unit 14. As described above, frames output from the communication processing units 11-1 to 11-N are stored in the receiving queues 12-1 to 12-N.
[0020] Here, as described above, the frames transmitted from the external communication devices 1-1 to 1-N need to be forwarded to other external communication devices, so the switch device 10 needs to determine the communication port (hereinafter referred to as the destination port) to which the external communication device that is the forwarding destination (destination) of the frame is connected.
[0021] The FDB 13 stores information (hereinafter referred to as destination determination information) for determining a destination port for a frame (the destination of the frame) stored in the receiving queues 12-1 to 12-N.
[0022] The forwarding processing unit 14 includes N destination determining units 14-1 to 14-N corresponding to the N receiving queues 12-1 to 12-N.
[0023] The destination determination units 14-1 to 14-N take out the frames stored in the receiving queues 12-1 to 12-N from the receiving queues 12-1 to 12-N, and refer to the FDB 13 (the destination determination information stored therein) to determine the destination port for the frame.
[0024] When the destination port for the frame is determined, the frame is output to a transmit queue corresponding to the destination port.
[0025] The N transmission queues 15-1 to 15-N correspond to the N communication processing units 11-1 to 11-N (communication ports 1 to N). The transmission queues 15-1 to 15-N are queues used to pass frames from the forwarding processing unit 14 (destination determination units 14-1 to 14-N) to the communication processing units 11-1 to 11-N. As described above, frames output from each of the destination determination units 14-1 to 14-N included in the forwarding processing unit 14 to a transmission queue corresponding to a destination port are stored in that transmission queue.
[0026] The frames thus stored in the transmission queues 15-1 to 15-N are extracted by the communication processing units 11-1 to 11-N and transmitted to the external communication devices 1-1 to 1-N.
[0027] The management unit 16 executes processes related to, for example, initialization, startup, and shutdown of the switch device 10, updating of the FDB 13 (addition and deletion of entries), and management of statistical information.
[0028] 1, the receiving queues 12-1 to 12-N and the transmitting queues 15-1 to 15-N are described as being provided outside the communication processing units 11-1 to 11-N, but the receiving queues 12-1 to 12-N and the transmitting queues 15-1 to 15-N may be held, for example, inside the communication processing units 11-1 to 11-N (for example, the MAC 11a). Alternatively, the receiving queues 12-1 to 12-N and the transmitting queues 15-1 to 15-N may be held inside the forwarding processing unit 14.
[0029] Next, an example of the configuration of the destination determining unit 14-1 included in the forwarding processing unit 14 shown in Fig. 1 will be described with reference to Fig. 2. As shown in Fig. 2, the destination determining unit 14-1 includes a determining unit 14a and a transmission processing unit 14b.
[0030] The determination unit 14a retrieves a frame from the receiving queue 12-1 corresponding to the destination determination unit 14-1, parses the header information added to the frame, and accesses the FDB 13 (the destination determination information stored therein) based on the header information. The determination unit 14a determines the destination port for the frame retrieved from the receiving queue 12-1 based on the destination determination information accessed in this manner.
[0031] The header information added to the frame includes the MAC address (destination MAC address) assigned to the external communication device that is the destination (forwarding destination) of the frame, the MAC address (source MAC address) assigned to the external communication device that is the source of the frame, the Ethernet type, etc.
[0032] The transmission processing unit 14b outputs the frame removed from the receiving queue 12-1 to a transmission queue (destination transmission queue) corresponding to the destination port determined by the determination unit 14a.
[0033] Next, an example of a processing procedure of the destination determination unit 14-1 will be described with reference to the flowchart of FIG.
[0034] First, when a frame is stored in the receiving queue 12-1 corresponding to the destination determining unit 14-1, the determining unit 14a removes the frame from the receiving queue 12-1 (step S1). Hereinafter, the frame removed in step S1 is referred to as a target frame for convenience.
[0035] Next, the determining unit 14a acquires the destination MAC address included in the header information added to the target frame (step S2).
[0036] Furthermore, the determining unit 14a acquires the Ethernet type contained in the header information added to the target frame (step S3).
[0037] Here, on a network configured using the switch device 10, a virtual LAN segment called a VLAN (Virtual LAN) to which at least some of the multiple communication ports 1 to N belong can be constructed. For example, a frame can be transmitted (broadcast transmitted) to all external communication devices present on the network, and this VLAN makes it possible to divide the broadcast domain. When a frame is broadcast transmitted, the header information added to the frame contains a MAC address for the broadcast transmission (hereinafter referred to as a broadcast address) as a destination MAC address.
[0038] When a VLAN to which the communication port 1 corresponding to the communication processing unit 11-1 that received the target frame belongs is established, the Ethernet type acquired in the above-mentioned step S3 is VLAN.
[0039] The determining unit 14a determines whether the type of Ethernet acquired in step S3 is VLAN (step S4).
[0040] Assume that it is determined in step S4 that the type of Ethernet is VLAN (YES in step S4). If the type of Ethernet is VLAN, the header information added to the target frame described above includes a VLAN header (information), and a PCP (Priority Code Point) is set in the VLAN header. In addition to the PCP, for example, a VLAN ID for identifying the VLAN is further set in the VLAN header.
[0041] The determination unit 14a obtains the PCP set in the VLAN header in this way, and obtains the TC (Traffic Class) by converting the PCP to a TC (step S5). This TC is, for example, information for identifying a transmission queue. Note that information for converting the PCP to a TC (i.e., information indicating the correspondence between the PCP and the TC) is held in advance in the determination unit 14a (for example, a traffic class table).
[0042] On the other hand, if it is determined that the Ethernet type is not VLAN (NO in step S4), the header information added to the target frame does not include a VLAN header, so it is not possible to obtain a PCP (i.e., convert the PCP into a TC). In this case, the determination unit 14a obtains a default value of TC (step S6). In other words, in step S6, a default value is set for the TC (for example, the PVID).
[0043] As described above, the target frame can be transmitted, for example, by broadcast, and the determining unit 14a determines whether the destination MAC address acquired in step S2 is a broadcast address (step S7).
[0044] If it is determined that the address is not a broadcast address (NO in step S7), the determining unit 14a refers to the FDB 13 based on the header information added to the target frame.
[0045] Here, FDB13 stores a plurality of destination determination information (entries) including, for example, an identifier for identifying a communication port (hereinafter referred to as a port identifier), a MAC address, a VLAN ID, and a last received time, which are associated with each other. The MAC address is a MAC address assigned to an external communication device connected to a communication port identified by the associated port identifier. If the external communication device is a switch, the MAC address also includes the MAC address connected to the external communication device. The VLAN ID is identification information for identifying the VLAN to which the communication port identified by the associated port identifier belongs. The last received time is, for example, the time when a frame was last transmitted from an external communication device to which the associated MAC address is assigned and received by the switch.
[0046] In this case, the determining unit 14a searches the FDB 13 for an entry including the destination MAC address acquired in step S2 and the VLAN ID set in the header information (VLAN header) added to the target frame (i.e., an entry in which the destination MAC address and the VLAN ID match). Hereinafter, the entry in which the destination MAC address and the VLAN ID match is referred to as the target entry for convenience.
[0047] The determining unit 14a determines whether or not the target entry exists in the FDB 13 based on the result of the above search (step S8).
[0048] If it is determined that the target entry exists (YES in step S8), the determining unit 14a determines the communication port identified by the port identifier included in the target entry (that is, the communication port in the target entry) as the destination port (step S9).
[0049] When the process of step S9 is executed, the transmission processing unit 14b outputs the target frame to a transmission queue identified based on the above-mentioned TC among the transmission queues corresponding to the destination port acquired in step S9 (step S10). By executing the process of step S10, the target frame is stored (written) in the transmission queue corresponding to the destination port.
[0050] Specifically, for example, if the destination port determined in step S9 is communication port 2, the target frame is output to the transmission queue 15-2 corresponding to the communication port 2. Similarly, if the destination port determined in step S9 is communication port N, the target frame is output to the transmission queue 15-N corresponding to the communication port N.
[0051] According to the configuration shown in Fig. 1, the communication port (communication processing unit) and the transmission queue correspond one-to-one. In this case, the transmission queue can be specified once the destination port is determined, so the above-mentioned TC does not need to be used.
[0052] On the other hand, in a configuration in which multiple transmission queues are prepared for one communication port, the transmission queue that should output the target frame is identified using the TC from among the multiple transmission queues prepared for the destination port.
[0053] In this case, information indicating the correspondence between the TC and the transmission queue identified based on the TC (that is, information for identifying the transmission queue from the TC) may be held in advance in the transmission processing unit 14b.
[0054] If it is determined in step S7 that the address is a broadcast address (YES in step S7), the determination unit 14a determines all communication ports other than the communication port 1 to which the external communication device 1-1 that transmitted the target frame is connected as the destination ports (step S11).
[0055] If it is determined in step S8 that the target entry does not exist (NO in step S8), the process proceeds to step S11. When there is no entry in the FDB, the frame is sent to all communication ports other than the communication port 1 to which the external communication device 1-1 that sent the target frame is connected. This is called flooding.
[0056] In addition, if the Ethernet type included in the header information added to the target frame described above is VLAN (i.e., a VLAN to which communication port 1 belongs has been established), all communication ports in the above-mentioned step S11 are all communication ports other than communication port 1 among the multiple communication ports belonging to the VLAN (the VLAN identified by the VLAN ID set in the VLAN header).
[0057] In addition, although the example shown in FIG. 3 has been described in which the destination MAC address is a broadcast address, the destination MAC address may be a multicast address. In this case, in the process shown in FIG. 3, it may be further determined whether the destination MAC address is a multicast address. The determination of whether the destination MAC address is a multicast address may be determined based on whether the I / G bit of the destination MAC address is 1. As a method of managing the destination determination information (entry) including a multicast address, a method of managing it by the FDB 13 or a method of providing an FDB for multicast addresses separately from the FDB 13 are conceivable. When the destination determination information (entry) including a multicast address is managed by the FDB 13, a plurality of port identifiers are held in the destination determination information, and the destination communication port is determined by referring to the FDB 13 in step S8, similarly to the unicast frame. When a separate FDB is provided for multicast addresses, if the destination MAC address is determined to be a multicast address, the destination communication port is determined by referring to the FDB for multicast addresses instead of the FDB 13.
[0058] Although the configuration and operation of the destination determining unit 14-1 included in the forwarding processing unit 14 have been described above, the configurations and operations of the other destination determining units 14-2 to 14-N are similar to that of the destination determining unit 14-1.
[0059] In the switch device 10 according to the first comparative example related to this embodiment, the forwarding processing unit 14 (destination determination units 14-1 to 14-N included in the forwarding processing unit 14) executes the process shown in Figure 3 described above, thereby making it possible to forward a frame transmitted from a specific external communication device to another external communication device.
[0060] Here, in the switch device 10 according to the first comparative example of this embodiment, it is assumed that the FDB 13 can be updated by learning MAC addresses based on frames transmitted from external communication devices 1-1 to 1-N (i.e., frames received by the switch device 10).
[0061] An example of the procedure for updating the FDB 13 will be described below with reference to the flowchart shown in Fig. 4. The updating of the FDB 13 is executed by the forwarding processing unit 14 (destination determination units 14-1 to 14-N), for example, but may also be executed by the management unit 16, or may be executed by an update processing unit (not shown) prepared separately from the forwarding processing unit 14 and the management unit 16. Here, the description will be given assuming that the forwarding processing unit 14 executes the updating of the FDB 13.
[0062] First, the forwarding processing unit 14 acquires a frame (step S21). The frame acquired in step S21 is, for example, a frame extracted from the receiving queues 12-1 to 12-N by each of the destination determining units 14-1 to 14-N included in the forwarding processing unit 14. Hereinafter, the frame acquired in step S21 is referred to as a target frame.
[0063] Next, the forwarding processing unit 14 acquires the source MAC address and the VLAN ID (source information) contained in the header information added to the target frame (step S22).
[0064] The forwarding processing unit 14 searches the FDB 13 for an entry (hereinafter, referred to as a target entry) including the source MAC address and VLAN ID acquired in step S22, and determines whether or not the target entry exists in the FDB 13 (step S23).
[0065] Here, the existence of a target entry in FDB13 means that an entry (destination determination information) indicating that an external communication device to which the MAC address included in the target entry is assigned is connected to a communication port (a communication port identified by a port identifier) belonging to the VLAN identified by the VLAN ID included in the target entry has already been registered in FDB13.
[0066] Therefore, when it is determined that the target entry exists in the FDB 13 (YES in step S23), the forwarding processing unit 14 updates the last received time included in the target entry to the current time (step S24).
[0067] On the other hand, if it is determined that the target entry does not exist in the FDB 13 (NO in step S23), the forwarding processing unit 14 adds a new entry to the FDB 13 (step S25).
[0068] Here, FDB13 needs to manage the correspondence between port identifiers, MAC addresses, and VLAN IDs, and the communication port to which the external communication device that sent the target frame (i.e., the external communication device to which the source MAC address contained in the target frame is assigned) is connected can be identified from the receive queue from which the target frame was extracted, etc.
[0069] Therefore, in step S25, an entry including a port identifier for identifying the communication port identified as described above, the source MAC address and VLAN ID obtained in step S22, and the current time (last received time) is added to FDB13.
[0070] By executing the processing of step S25, when a frame containing the MAC address contained in the entry added in step S25 as the destination MAC address is received by the switch device 10, the communication port identified by the port identifier contained in the entry can be determined as the destination port by referring to the entry.
[0071] Although the capacity of the FDB 13 is finite, if there is no free space in the FDB 13 at the time the process of step S25 is executed, the entry with the earliest (oldest) last received time is deleted and a new entry is added to the FDB 13. This allows the FDB 13 to hold (store) entries based on frames whose transmission times are closer to the present with priority. However, the algorithm for replacing entries in the FDB 13 is not limited to this.
[0072] 4, an administrator of the switch may manually add or delete entries. In this case, for example, the management unit 16 receives a control command from the administrator and performs the update process of the FDB 13.
[0073] Incidentally, networks such as industrial networks or in-vehicle networks may require high real-time performance, and the IEEE 802.1 TSN Task Group is working on standardizing Time-Sensitive Networking (TSN) as a standard for achieving high real-time performance on such networks. TSN is a standard that extends Audio / Video Bridging (AVB), which achieves low latency and is used in professional audio, for example. TSN aims to achieve high reliability in addition to higher real-time performance than AVB.
[0074] Here, TSN is composed of a plurality of standards (standards), one of which is IEEE 802.1Qbu / IEEE 802.3br (FPE: Frame Preemption). In the switch device 10 according to the first comparative example of this embodiment, the communication processing units 11-1 to 11-N have been described as including one MAC, but in FPE, Express MAC for high priority (hereinafter, referred to as eMAC) and Preemptable MAC for low priority (hereinafter, referred to as pMAC) are used.
[0075] According to such an FPE, when a transfer process of a high-priority frame (an Express frame of the FPE) occurs during a transfer (transmission) process of a low-priority frame (a Preemptable frame of the FPE), the transmission process of the low-priority frame can be interrupted and the high-priority frame can be interrupted. The transfer process of the low-priority frame is resumed after the transfer process of the high-priority frame is completed.
[0076] It is difficult to achieve high real-time performance in a network configured using the switch device 10 according to the first comparative example of this embodiment described above. However, if the switch device is compatible with FPE (standard), it is possible to reduce delays in the forwarding process for high priority frames and achieve high real-time performance compared to the switch device 10.
[0077] An example of the configuration of a switch device compatible with FPE (hereinafter, referred to as a switch device according to a second comparative example of this embodiment) will be described below with reference to Fig. 5. In the following description of the second comparative example of this embodiment, detailed descriptions of parts similar to those of the switch device according to the first comparative example of this embodiment described above will be omitted.
[0078] The switch device 20 shown in FIG. 5 includes N communication processing units 21-1 to 21-N, N first receiving queues (eRx) 22-1a to 22-Na, N second receiving queues (pRx) 22-1b to 22-Nb, an FDB 23, a forwarding processing unit 24, N first transmitting queues (eTx) 25-1a to 25-Na, N second transmitting queues (pTx) 25-1b to 25-Nb, and a management unit 26.
[0079] The second comparative example of this embodiment differs from the first comparative example of this embodiment in that the communication processing units 21-1 to 21-N correspond to FPE and include two MACs, eMAC 21a and pMAC 21b. Note that the PHY 21c included in the communication processing units 21-1 to 21-N corresponds to the PHY 11b included in the communication processing units 11-1 to 11-N in the first comparative example of this embodiment.
[0080] Here, in the second comparative example of this embodiment, the frames received by the communication processing units 21-1 to 21-N include real-time frames and best-effort frames. Note that a real-time frame is defined as a frame that requires high real-timeness in the transfer process and needs to be transferred with low delay, and corresponds to, for example, the Express frame of the FPE described above. On the other hand, a best-effort frame is a frame other than a real-time frame, and corresponds to, for example, the Preemptable frame of the FPE described above. It is assumed that whether a frame transmitted from the external communication devices 1-1 to 1-N is a real-time frame or a best-effort frame is set outside the switch device 20 (for example, the external communication devices 1-1 to 1-N, etc.).
[0081] In the above example, real-time frames and best-effort frames can be identified by referring to the SFD field and SMD field of the received Ethernet frame. For example, a value (0xD5) defined in SMD-E can be identified as a real-time frame (FPE Express frame), and SMD-S0 to 3 (0xE6, 0x4C, 0x7F, 0xB3) and SMD-C0 to 3 (0x61, 0x52, 0x9E, 0x2A) can be identified as a best-effort frame (FPE Preemptable frame). In addition, since FPE Express frames are received and processed by eMAC, and FPE Preemptable frames are received and processed by pMAC, they can also be identified by which MAC they are received by.
[0082] When the communication processing units 21-1 to 21-N receive a real-time frame, for example, the real-time frame is output to the first receive queues 22-1a to 22-Na via the eMAC 21a (and the PHY 21c). On the other hand, when the communication processing units 21-1 to 21-N receive a best-effort frame, for example, the real-time frame is output to the second receive queues 22-1b to 22-Nb via the pMAC 21b (and the PHY 21c).
[0083] The N first receiving queues 22-1a to 22-Na correspond to the N communication processing units 21-1 to 21-N, and are queues used for passing real-time frames from the communication processing units 21-1 to 21-N to the forwarding processing unit 24. As described above, the real-time frames output from the communication processing units 21-1 to 21-N are stored in the first receiving queues 22-1a to 22-Na.
[0084] The N second receiving queues 22-1b to 22-Nb correspond to the N communication processing units 21-1 to 21-N, and are queues used to deliver best effort frames from the communication processing units 21-1 to 21-N to the forwarding processing unit 24. As described above, the best effort frames output from the communication processing units 21-1 to 21-N are stored in the second receiving queues 22-1b to 22-Nb.
[0085] The FDB 23 stores destination determination information (entries) including a port identifier, a MAC address, a VLAN ID, and a last reception time in association with each other, similar to the FDB 13 described in the first comparative example of this embodiment.
[0086] The forwarding processing unit 24 includes N destination determining units 24-1 to 24-N corresponding to the N first receiving queues 22-1a to 22-Na and the N second receiving queues 22-1b to 22-Nb (that is, communication ports 1 to N).
[0087] The destination determination units 24-1 to 24-N extract the real-time frames stored in the first receive queues 22-1a to 22-Na from the first receive queues 22-1a to 22-Na, and refer to the FDB 23 (the destination determination information stored therein) to determine the destination port for the real-time frame.
[0088] In addition, the destination determination units 24-1 to 24-N extract the best effort frames stored in the second receive queues 22-1b to 22-Nb from the second receive queues 22-1b to 22-Nb, and determine the destination port for the best effort frames by referring to the destination determination information stored in FDB2.
[0089] For example, when a destination port for a real-time frame (a frame extracted from the first receive queues 22-1a to 22-Na) is determined, the real-time frame is output to the first transmit queue corresponding to the destination port.
[0090] On the other hand, when a destination port for a best effort frame (a frame extracted from the second receiving queues 22-1b to 22-Nb) is determined, the best effort frame is output to the second transmitting queue corresponding to the destination port.
[0091] The N first transmission queues 25-1a to 25-Na correspond to the N communication processing units 21-1 to 21-N (i.e., communication ports 1 to N). The first transmission queues 25-1a to 25-Na are queues used to deliver real-time frames from the forwarding processing unit 24 (destination determining units 24-1 to 24-N) to the communication processing units 21-1 to 21-N. As described above, the real-time frames output from each of the destination determining units 24-1 to 24-N included in the forwarding processing unit 24 to the first transmission queue corresponding to the destination port are stored in the first transmission queue.
[0092] The real-time frames thus stored in the first transmission queues 25-1a to 25-Na are extracted by the communication processing units 21-1 to 21-N and transmitted to the external communication devices 1-1 to 1-N via the eMAC 21a (and the PHY 21c).
[0093] The N second transmission queues 25-1b to 25-Nb correspond to the N communication processing units 21-1 to 21-N (i.e., communication ports 1 to N). The second transmission queues 25-1b to 25-Nb are queues used to deliver best effort frames from the forwarding processing unit 24 (destination determination units 24-1 to 24-N) to the communication processing units 21-1 to 21-N. As described above, the best effort frames output from each of the destination determination units 24-1 to 24-N included in the forwarding processing unit 24 to the second transmission queue corresponding to the destination port are stored in the second transmission queue.
[0094] The best effort frames thus stored in the second transmission queues 25-1b to 25-Nb are extracted by the communication processing units 21-1 to 21-N and transmitted to the external communication devices 1-1 to 1-N via the pMAC 21b (and the PHY 21c).
[0095] As described later, the destination determination units 24-1 to 24-N hold information (correspondence information between TCs and transmission queues) indicating whether each TC uses the first transmission queue (eTx) or the second transmission queue (pTx). Therefore, depending on the setting of the correspondence information between TCs and transmission queues, real-time frames (frames extracted from the first receiving queues 22-1a to 22-Na) may be output to the second transmission queue corresponding to the destination port, and best-effort frames (frames extracted from the second receiving queues 22-1b to 22-Nb) may be output to the first transmission queue corresponding to the destination port.
[0096] The management unit 26 corresponds to the management unit 16 in the first comparative example of this embodiment described above, and executes processes related to, for example, initialization, startup, and shutdown of the switch device 20, updating of the FDB 23 (addition and deletion of entries), and management of statistical information.
[0097] Next, with reference to Fig. 6, an example of the configuration of the destination determining unit 24-1 included in the forwarding processing unit 24 shown in Fig. 5 will be described. As shown in Fig. 6, the destination determining unit 24-1 includes a determining unit 24a and a transmission processing unit 24b.
[0098] The determination unit 24a retrieves a real-time frame from the first receiving queue 22-1a corresponding to the destination determination unit 24-1, and determines the destination port for the real-time frame by accessing the FDB 23 (the destination determination information stored therein) based on the header information attached to the real-time frame.
[0099] The determination unit 24a retrieves the best effort frame from the second receive queue 22-1b corresponding to the destination determination unit 24-1, and determines the destination port for the best effort frame by accessing the FDB 23 (the destination determination information stored therein) based on the header information added to the best effort frame.
[0100] The transmission processing unit 24b outputs the real-time frame extracted from the first receiving queue 22-1a to the first transmitting queue (first transmitting queue for the destination) or the second transmitting queue (second transmitting queue for the destination) corresponding to the destination port determined by the determination unit 24a.
[0101] The transmission processing unit 24b outputs the best effort frame extracted from the second receiving queue 22-1b to the first transmission queue (first transmission queue for the destination) or the second transmission queue (second transmission queue for the destination) corresponding to the destination port determined by the determination unit 24a.
[0102] Although the configuration of the destination determining unit 24-1 included in the forwarding processing unit 24 has been described above, the configurations of the other destination determining units 24-2 to 24-N are similar to that of the destination determining unit 24-1.
[0103] In addition, the destination determination units 24-1 to 24-N in the second comparative example of this embodiment perform processing similar to the processing shown in Figure 3 described above, except that they extract frames from the first receiving queues 22-1a to 22-Na and the second receiving queues 22-1b to 22-Nb, and output frames to the first and second transmitting queues.
[0104] In this case, the determination unit 24a selects one of the first receiving queue 22-1a and the second receiving queue 22-1b to extract a frame, but since real-time frames require low-delay transfer processing, the first receiving queue 22-1a is selected preferentially when extracting a frame. In other words, the determination unit 24a operates to preferentially extract a real-time frame from the first receiving queue 22-1a, and when no real-time frame exists in the first receiving queue 22-1a, extract a best-effort frame from the second receiving queue 22-1b. However, the determination unit 24a may select a receiving queue from which to extract a frame, for example, using a round robin method.
[0105] In the second comparative example of this embodiment, since there are two transmission queues (first and second transmission queues) in the communication port, the transmission processing unit 24b needs to determine to which of the first and second transmission queues for the destination port the frame should be output. In this case, the transmission processing unit 24b specifies the transmission queue to which the frame should be output based on the TC described in FIG. 3 above. Note that information indicating whether each TC uses the first transmission queue (eTx) or the second transmission queue (pTx) is held in advance inside the transmission processing unit 24b (for example, a frame preemption status table).
[0106] Here, an explanation will be given of access to the FDB 23 of the switch device 20 according to the second comparative example of this embodiment. In order to realize high real-time performance in the above-mentioned FPE (TSN), it is important to reduce the maximum value of delay time and jitter (fluctuation in response time) when accessing the FDB 23.
[0107] In this case, for example, by adopting a configuration in which the destination determination information stored in the FDB 23 provided in the switch device 20 according to the second comparative example of this embodiment is managed using a Content Addressable Memory (CAM) (i.e., the FDB 23 is realized by a CMA), it becomes possible to access the FDB 23 with low delay and low jitter. Note that when the CAM is implemented in hardware, it is possible to search for the destination determination information (target entry) in, for example, one clock cycle.
[0108] On the other hand, since the capacity of the FDB 23 affects the number of devices connected to the switch device 20, it is preferable to increase the capacity of the FDB 23. However, since the above-mentioned CAM is configured to operate many comparators in parallel to achieve low delay and low jitter, it consumes a lot of hardware resources and it is difficult to increase the capacity. When the switch device 20 is applied to, for example, an FPGA (Field Programmable Gate Array) or an embedded system, it becomes difficult to secure more hardware resources (i.e., to increase the capacity of the FDB 23).
[0109] In this case, it is conceivable to increase the capacity of the FDB 23 by using SDRAM or SRAM (BRAM) or the like and configuring it so that the destination determination information is managed using a hash table. However, in such a configuration, the delay time (search time) increases compared to when a CAM is used, making it difficult to achieve real-time performance. Furthermore, when a hash table is used, there is a possibility that a hash collision will occur, and the occurrence of such a hash collision can be a factor in causing fluctuations in response time (i.e., jitter). In addition, the increase in the capacity of the FDB 23 itself can be a factor in causing jitter.
[0110] Therefore, the switch device according to this embodiment has a configuration for achieving both a reduction in delay time (and jitter) for realizing real-time performance and an increase in the capacity of the FDB.
[0111] An example of the configuration of the switch device according to this embodiment will be described below with reference to Fig. 7. In the following description of this embodiment, detailed description of the same parts as those of the switch device according to the second comparative example of this embodiment will be omitted.
[0112] As shown in FIG. 7, the switch device 30 includes N communication processing units 31-1 to 31-N, N first receiving queues (eRx) 32-1a to 32-Na, N second receiving queues (pRx) 32-1b to 32-Nb, an eFDB 33a, a pFDB 33b, a forwarding processing unit 34, N first transmitting queues (eTx) 35-1a to 35-Na, N second transmitting queues (pTx) 35-1b to 35-Nb, and a management unit 26.
[0113] The switch device 30 of this embodiment is a switch device compatible with FPE, similar to the switch device 20 of the second comparative example of this embodiment described above, but differs from the switch device 20 of the second comparative example in that it is equipped with eFDB33a and pFDB33b (i.e., it utilizes two FDBs).
[0114] The eFDB 33a is an FDB for the above-mentioned real-time frames, and is configured to be able to access the eFDB 33a (destination determination information) (i.e., search for entries) at high speed and with low delay compared to the pFDB 33b. Specifically, the eFDB 33a has a limited capacity (i.e., the number of entries), but manages the destination determination information using a CAM to reduce delay time.
[0115] On the other hand, the pFDB 33b is an FDB for the above-mentioned best-effort frames, and may be configured to have a larger capacity than the eFDB 33a. Specifically, the pFDB 33b has a larger delay time and jitter than the eFDB 33a, but is implemented by SDRAM or the like in order to manage more destination determination information (entries). The destination information stored in the pFDB 33b is managed using, for example, a hash table.
[0116] Note that "managing destination determination information using a hash table" refers to managing the destination determination information (entries) using hash values calculated from at least a part of the above-mentioned destination determination information (port identifiers, MAC addresses, and VLAN IDs) using a predetermined hash function. This makes it possible to reduce the circuit scale of the pFDB 33b, and therefore further increase the number of destination determination information (entries) managed in the pFDB 33b.
[0117] The forwarding processing unit 34 includes N destination determination units 34-1 to 34-N. The destination determination units 34-1 to 34-N extract real-time frames stored in the first receiving queues 32-1a to 32-Na from the first receiving queues 32-1a to 32-Na, and determine destination ports for the real-time frames by referring to the eFDB 33a (destination determination information stored therein).
[0118] In addition, the destination determination units 34-1 to 34-N extract the best effort frames stored in the second receive queues 32-1b to 32-Nb from the second receive queues 32-1b to 32-Nb, and determine the destination port for the best effort frames by referring to the pFDB 33b (the destination determination information stored therein).
[0119] Note that the N communication processing units 31-1 to 31-N, the N first reception queues (eRx) 32-1a to 32-Na, the N second reception queues (pRx) 32-1b to 32-Nb, the N first transmission queues (eTx) 35-1a to 35-Na, the N second transmission queues (pTx) 35-1b to 35-Nb, and the management unit 36 are similar to the N communication processing units 21-1 to 21-N, the N first reception queues (eRx) 22-1a to 22-Na, the N second reception queues (pRx) 22-1b to 22-Nb, the N first transmission queues (eTx) 25-1a to 25-Na, the N second transmission queues (pTx) 25-1b to 25-Nb, and the management unit 26 in the second comparative example of this embodiment, and therefore detailed description thereof will be omitted here.
[0120] Next, with reference to Fig. 8, an example of the configuration of a destination determining unit 34-1 included in the forwarding processing unit 34 shown in Fig. 7 will be described. As shown in Fig. 8, the destination determining unit 34-1 includes a first determining unit 34a, a second determining unit 34b, and a transmission processing unit 34c.
[0121] The first determination unit 34a retrieves a real-time frame from the first receive queue 32-1a corresponding to the destination determination unit 34-1, and determines the destination port for the real-time frame by accessing the eFDB 33a (the destination determination information stored therein) based on the header information attached to the real-time frame.
[0122] The second determination unit 34b retrieves the best effort frame from the second receive queue 32-1b corresponding to the destination determination unit 34-1, and determines the destination port for the best effort frame by accessing the pFDB 33b (the destination determination information stored in the pFDB 33b) based on the header information added to the best effort frame.
[0123] The transmission processing unit 34c outputs the real-time frame extracted from the first receiving queue 32-1a to the first transmitting queue or the second transmitting queue corresponding to the destination port determined by the first determining unit 34a.
[0124] The transmission processing unit 34c outputs the best effort frame extracted from the second receiving queue 32-1b to the first transmitting queue or the second transmitting queue corresponding to the destination port determined by the second determining unit 34b.
[0125] Although the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 has been described here, the configurations of the other destination determining units 34-2 to 34-N are similar to that of the destination determining unit 34-1.
[0126] In addition, the destination determination units 34-1 to 34-N in this embodiment perform processing similar to that of the second comparative example of this embodiment described above, except that they determine the destination port for the real-time frame extracted from the first receive queue 32-1a by referring to the eFDB 33a, and determine the destination port for the best-effort frame extracted from the second receive queue 32-1b by referring to the pFDB 33b.
[0127] In the present embodiment, the switch device 30 has been described as simply a switch device compatible with FPE, but below, a specific application example of the switch device 30 will be briefly described with reference to Fig. 9. Note that only the differences from the switch device 30 shown in Fig. 7 will be mainly described.
[0128] Among the multiple standards constituting the above-mentioned TSN, there is IEEE 802.1Qbv (TAS: Time-Aware Shaper) which is a standard other than FPE. According to TAS, multiple transmission queues (transmission buffers) with different priorities are controlled according to pre-set transmission schedule information (gate control list), making it possible to strictly control the transmission timing of frames for each priority (TC). Each transmission queue in TAS is provided with a gate that allows frame transmission, and when the gate is open (in an open state), frame transmission is permitted, and when the gate is closed (in a closed state), frame transmission is prohibited.
[0129] The switch device 40 shown in FIG. 9 is realized as a switch-embedded NIC (Network Interface Card) that incorporates a switch device compatible with TAS in addition to the above-mentioned FPE.
[0130] In the example shown in FIG. 9, the switch device 40 is connected to N external communication devices 1-1 to 1-N via N communication interfaces (communication ports 1 to N), and is also connected to a host machine 2 equipped with a CPU, memory, etc. via PCI Express (PCIe) (registered trademark).
[0131] That is, the switch device 40 shown in FIG. 9 is configured, for example, to forward frames transmitted from the host machine 2 to the external communication devices 1-1 to 1-N, or to forward frames transmitted from the external communication devices 1-1 to 1-N to the host machine 2 or other external communication devices.
[0132] As shown in FIG. 9, the switch device 40 includes a PCIe interface 41, a DMAC 42, TAS processing units 43-0 to 43-N, and a receive queue 44.
[0133] The PCIe interface 41 is an interface for connecting the switch device 40 and the host machine 2.
[0134] The DMAC 42 receives a frame transmitted from the host machine 2 via the PCIe interface 41, and outputs the frame to the TAS processing unit 43-0. The DMAC 42 also extracts a frame stored in the receive queue 44 from the receive queue 44, and transmits the frame to the host machine 2 via the PCIe interface 41.
[0135] The TAS processing unit 43-0 corresponds to the host machine 2, and executes TAS processing on frames transmitted from the host machine 2. The TAS processing unit 43-0 includes, for example, transmission queues TC0(0) to TC7(0) and a TAS (Host), and determines the frame transmission timing according to pre-set schedule information (gate control list). The gate control list includes, for example, the gate status of queues corresponding to eight TCs (TC0 to TC7) for each time interval. The gate status indicates whether transmission in the queue corresponding to each TC is permitted or not. The TAS processing unit 43-0 can perform an operation such as taking out and outputting frames from transmission queues whose gates are open based on such a gate control list.
[0136] In addition, frames (real-time frames and best effort frames) output from the TAS processing unit 43-0 are stored in a receiving queue 32-0a (eRx) similar to the first receiving queues 32-1a to 32-Na shown in FIG. 7 and a receiving queue 32-0b (pRx) similar to the second receiving queues 32-1b to 32-Nb.
[0137] Although the TAS processing unit 43-0 has been described here, the TAS processing units 43-1 to 43-N correspond to the external communication devices 1-1 to 1-N (communication ports 1 to N) and execute the same processing as the TAS processing unit 43-0 described above.
[0138] The receive queue 44 is a queue used to pass frames from the forwarding processor 34 to the DMAC 42 .
[0139] 9, a TAS processing unit 43-0 is provided in the receiving direction from the host machine 2 to the switch device 40. That is, this TAS processing unit 43-0 is implemented to regard the host machine 2 as an external communication device connected to the switch device 40 and to execute a transmission process (TAS process) for the external communication device.
[0140] On the other hand, in the case of a switch device that supports TAS, TAS processing is necessary in all transmission directions, but the bus connected to the host machine 2 does not share a network with other communication devices, and it is assumed that the effect of avoiding collisions of multiple traffics by executing the TAS processing is low. For this reason, in the example shown in Fig. 9, a TAS processing unit is not provided in the transmission direction from the switch device 40 to the host machine 2.
[0141] However, the configuration shown in FIG. 9 is just one example, and for example, a TAS processing unit may be provided in the transmission direction from the external communication devices 1-1 to 1-N to the host machine 2 (between the receive queue 44 and the DMAC 42), or a configuration in which the TAS (Host) in the TAS processing unit 43-0 is omitted may be adopted.
[0142] 9 is the same as that described in the present embodiment (switch device 30 shown in FIG. 7), so detailed description thereof will be omitted here. However, the forwarding processing unit 34 further includes a destination determination unit 34-0 corresponding to the first and second receiving queues on the host machine 2 side, in addition to the above-described destination determination units 34-1 to 34-N.
[0143] 9, the management unit 36 in this embodiment is not provided in the switch device 40, and the host machine 2 includes a management unit 2a that corresponds to the management unit 36. Note that it is assumed that this management unit 2a is realized, for example, by a CPU provided in the host machine 2 executing a predetermined program (i.e., software).
[0144] Next, the operation of the forwarding processing unit 34 included in the switch device 40 will be briefly described with reference to FIG.
[0145] 10, destination determining units 34-0 to 34-N included in the forwarding processing unit 34 include eXmitter and pXmitter. Note that eXmitter executes, for example, the same process as the first determining unit 34a (and the transmission processing unit 34c) shown in FIG. 8, and pXmitter executes, for example, the same process as the second determining unit 34b (and the transmission processing unit 34c) shown in FIG. 8.
[0146] Further, the forwarding processing unit 34 includes N+1 selectors corresponding to the host machine 2 and each of the communication ports 1 to N (i.e., the external communication devices 1-1 to 1-N). In Fig. 10, the selector corresponding to the host machine 2 is indicated as selector S(0), and the selectors corresponding to the communication ports 1 to N are indicated as selectors S(1) to S(N).
[0147] In this case, for example, when a real-time frame is extracted from the first receiving queue 32-0a by the eXmitter included in the destination determining unit 34-0, the eXmitter refers to the eFDB 33a based on the header information added to the real-time frame, and determines the destination port for the real-time frame. The eXmitter outputs the real-time frame to the selector corresponding to the determined destination port. Note that, since the real-time frame extracted from the first receiving queue 32-0a (i.e., the real-time frame transmitted from the host machine 2) is transferred to the external communication devices 1-1 to 1-N other than the host machine 2, the eXmitter included in the destination determining unit 34-0 transmits the real-time frame to the selectors S(1) to S(N) other than the selector S(0).
[0148] Furthermore, for example, when a best effort frame is extracted from the second receiving queue 32-0b by the pXmitter included in the destination determining unit 34-0, the pXmitter refers to the pFDB 33b based on the header information added to the best effort frame, and determines the destination port corresponding to the best effort frame. The pXmitter outputs the best effort frame to the selector corresponding to the determined destination port. Note that, since the best effort frame extracted from the second receiving queue 32-0b (i.e., the best effort frame transmitted from the host machine 2) is transferred to external communication devices 1-1 to 1-N other than the host machine 2, the eXmitter included in the destination determining unit 34-0 transmits the best effort frame to the selectors S(1) to S(N) other than the selector S(0).
[0149] Also, for example, the selector S(0) (the selector corresponding to the host machine 2) inputs a frame output from the selector S(0) from the destination determination units 34-1 to 34-N (the eXmitters and pXmitters included in them) other than the destination determination unit 34-0 corresponding to the host machine 2, and outputs the input frame to one of the transmission queues TC0 to TC7 identified (selected) by the TC. The TC for identifying the transmission queue to output the frame is obtained by the destination determination unit 34-0 executing a process equivalent to the process shown in FIG. 3 described above.
[0150] Although the destination determining unit 34-0 and the selector S(0) have been described here, the same applies to the other destination determining units 34-1 to 34-N and the selectors S(1) to S(N).
[0151] In FIG. 10, the eXmitters that extract real-time frames from the first receiving queues 32-0a to 32-Na by the destination determination units 34-0 to 34-N are shown as eX(0) to eX(N), and the pXmitters that extract best-effort frames from the second receiving queues 32-0b to 32-Nb by the destination determination units 34-0 to 34-N are shown as pX(0) to pX(N).
[0152] Here, we have described the case where the switch device of this embodiment is implemented as a switch-embedded NIC that has a switch device that supports FPE and TAS built in, but the switch device may be implemented in other ways.
[0153] As described above, in this embodiment, for example, when a frame transmitted from an external communication device 1-1 (first external communication device) connected to a communication port 1 (first communication port) is received and the received frame is a real-time frame (a first frame that requires low-latency transfer), the destination port is determined by accessing destination determination information (information used to determine a second communication port to which a second external communication device that is the destination of the frame is connected) stored in the eFDB 33a (first database) based on header information added to the real-time frame. On the other hand, when the received frame is a best-effort frame (a second frame different from the first frame), the destination port is determined by accessing destination determination information stored in the pFDB 33b (second database) based on header information added to the best-effort frame. In this embodiment, the eFDB 33a is configured to be able to access destination determination information at a higher speed than the pFDB 33b.
[0154] In this embodiment, by preparing separate FDBs for real-time frames and best-effort frames as described above, it is possible to minimize the delay time (and jitter) when transferring real-time frames, while adding pFDB 33b to realize a larger capacity FDB compared to a configuration simply including eFDB 33a. In other words, in this embodiment, it is possible to achieve both a reduction in delay time and an increase in the capacity of the FDB (database).
[0155] Here, in this embodiment, for example, when a real-time frame transmitted from an external communication device 1-1 to 1-N is received, the eFDB33a may be updated by executing the process shown in FIG. 4, and when a best-effort frame transmitted from the external communication device 1-1 to 1-N is received, the pFDB33b may be updated by executing the process shown in FIG. 4, but the update process of eFDB33a may be different from the update process of pFDB33b.
[0156] Specifically, in this embodiment, when real-time communication devices (application programs that require real-time performance) and best-effort communication devices (application programs that do not require real-time performance) are mixed among the N external communication devices 1-1 to 1-N, it is expected that the number of real-time communication devices will be smaller than the number of best-effort communication devices.
[0157] In addition, communication devices (application programs) that perform communications requiring real-time communication, such as emergency signals, in industrial networks or in-vehicle networks, etc., rarely have the opportunity to dynamically connect to and disconnect from the network, and it is assumed that the number of devices is often determined when the network is configured (i.e., the number is fixed).
[0158] For this reason, in this embodiment, for example, the destination determination information stored in the eFDB 33a may not be updated when a real-time frame is received (that is, learning of MAC addresses for the eFDB 33a may be disabled). This allows real-time performance to be prioritized over updating of the destination determination information for the eFDB 33a, and makes it possible to prevent an increase in delay time or jitter when a real-time frame is transferred due to an update of the eFDB 33a.
[0159] On the other hand, the destination determination information stored in the pFDB 33b is updated when a best effort frame is received (i.e., learning of MAC addresses for the pFDB 33b is enabled). According to this, by updating the pFDB 33b (adding an entry, etc.) every time a best effort frame transmitted from the external communication devices 1-1 to 1-N is received, for example, it is possible to flexibly connect and disconnect external communication devices to and from the network, and to handle frame transfer to a larger number of external communication devices.
[0160] It should be noted that, although it has been explained here that the destination determination information stored in eFDB33a is not updated when a real-time frame is received, it is possible for the update of eFDB33a to be performed in response to, for example, instructions from outside the switch device 40.
[0161] As described above, the switch device 30 according to the present embodiment may be configured to execute different update processes for each FDB (eFDB 33a and pFDB 33b) as described above. In this case, the switch device 30 according to the present embodiment may operate such that the update process for the eFDB 33a is executed less frequently than the update process for the pFDB 33b.
[0162] Here, in the present embodiment, a configuration has been described in which two receive queues (first and second receive queues) are provided for one communication port (communication processing unit), but this embodiment may also be a configuration in which one receive queue is provided for one communication port (hereinafter referred to as a first modified example of this embodiment), as shown in Fig. 11. Note that in the following description of the first modified example of this embodiment, detailed descriptions of parts that are the same as those of the switch device according to the present embodiment described above will be omitted.
[0163] 11, the switch device 30 according to the first modification of this embodiment includes N receive queues 32-1 to 32-N corresponding to communication ports 1 to N (communication processing units 31-1 to 31-N), and for example, the receive queue 32-1 sequentially stores serialized real-time frames and best-effort frames output from the communication processing unit 31-1. The same applies to the other receive queues 32-2 to 32-N.
[0164] Next, an example of the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 shown in FIG. 11 will be described with reference to FIG.
[0165] 12, the destination determination unit 34-1 includes a determination unit 34d. In a first modified example of this embodiment, the determination unit 34d determines a destination port for a real-time frame by referring to the eFDB 33a, and determines a destination port for a best-effort frame by referring to the pFDB 33b, as described in the present embodiment.
[0166] However, in the first variant of this embodiment, there is only one receive queue that stores the frames extracted by the determination unit 34d (i.e., real-time frames and best-effort frames are extracted from one receive queue 32-1), so the determination unit 34d needs to determine whether the frame extracted from the receive queue 32-1 is a real-time frame or a best-effort frame.
[0167] For this reason, in the first modified example of this embodiment, the determination unit 34d is configured to determine whether the frame is a real-time frame or a best-effort frame based on, for example, a PCP included in header information added to the frame extracted from the receiving queue 32-1 or a TC converted from the PCP. In this case, the determination unit 34d can execute the above-mentioned determination process based on information by storing in advance, for example, for each PCP or TC, information indicating whether the frame is a real-time frame or a best-effort frame.
[0168] If the frame removed from the receive queue 32-1 is determined to be a real-time frame by this determination process, the destination port for the real-time frame is determined by referring to the eFDB 33a. On the other hand, if the frame removed from the receive queue 32-1 is determined to be a best-effort frame, the destination port for the best-effort frame is determined by referring to the pFDB 33b.
[0169] Although the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 has been described here, the configurations of the other destination determining units 34-2 to 34-N are similar to that of the destination determining unit 34-1.
[0170] In addition, the destination determination units 34-1 to 34-N in the first modified example of this embodiment execute the same processing as in the above-described embodiment, except that they determine whether the frame extracted from the receiving queues 32-1 to 32-N is a real-time frame or a best-effort frame.
[0171] In addition, this embodiment may have a configuration (hereinafter referred to as a second modified example of this embodiment) in which m (m is an integer equal to or greater than 3) receive queues are provided for one communication port, for example, as shown in Fig. 13. In the following description of the second modified example of this embodiment, detailed description of the same parts as those of the switch device according to the above-described embodiment will be omitted.
[0172] 13, the switch device 30 according to the second modification of this embodiment includes N×m receive queues corresponding to communication ports 1 to N (communication processing units 31-1 to 31-N). Specifically, for example, the receive queues corresponding to communication port 1 are m receive queues 32-11 to 32-1m, the receive queues corresponding to communication port 2 are m receive queues 32-21 to 32-2m, and the receive queues corresponding to communication port N are m receive queues 32-N1 to 32-Nm. The same applies to the receive queues corresponding to the other communication ports.
[0173] Here, in the second modified example of this embodiment, the N×m receiving queues include a receiving queue for real-time frames (i.e., a receiving queue in which real-time frames are stored) and a receiving queue for best-effort frames (i.e., a receiving queue in which best-effort frames are stored). That is, for example, a real-time frame output from the communications processing unit 31-1 is stored in a receiving queue for real-time frames among the receiving queues 32-11 to 32-1m. On the other hand, a best-effort frame output from the communications processing unit 31-1 is stored in a receiving queue for best-effort frames among the receiving queues 32-11 to 32-1m.
[0174] In addition, the switch device 30 according to the second variant of this embodiment is provided with an attribute information DB (database) 37 that pre-stores information (hereinafter referred to as attribute information) indicating whether each of the above-mentioned N×m receiving queues is a receiving queue for real-time frames or a receiving queue for best-effort frames.
[0175] Next, an example of the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 shown in FIG. 13 will be described with reference to FIG.
[0176] As shown in FIG. 14, the destination determining unit 34-1 includes a first frame extracting unit 34e and a second frame extracting unit 34f.
[0177] The first frame extractor 34e extracts a real-time frame from a receiving queue for real-time frames among the m receiving queues 32-11 to 32-1m, and outputs the extracted real-time frame to the first decision unit 34a.
[0178] The second frame extracting unit 34f extracts a best effort frame from a receiving queue for best effort frames among the m receiving queues 32-11 to 32-1m, and outputs the extracted best effort frame to the second determining unit 34b.
[0179] In the second modified example of this embodiment, the receiving queue for real-time frames and the receiving queue for best-effort frames can be distinguished based on the attribute information stored in the attribute information DB 37.
[0180] Specifically, in the attribute information stored in the attribute information DB 37, a real-time frame (Express) or a best-effort frame (Preemptable) is set in association with each of the receiving queues, as shown in Fig. 15. In Fig. 15, Rx1 to Rxm correspond to identification information for identifying the receiving queues 32-11 to 32-1m, for example.
[0181] The first frame extractor 34e can determine (specify) a receiving queue in which a real-time frame is set in the attribute information (i.e., a receiving queue for a real-time frame) and extract the real-time frame from the receiving queue. Similarly, the second frame extractor 34f can determine (specify) a receiving queue in which a best-effort frame is set in the attribute information (i.e., a receiving queue for a best-effort frame) and extract the best-effort frame from the receiving queue.
[0182] If there are multiple receiving queues for real-time frames among the m receiving queues 32-11 to 32-1m, the first frame extractor 34e extracts the real-time frames according to a priority, etc., that is determined in advance for each receiving queue for real-time frames. This priority may be set in the attribute information DB 37 (attribute information), for example. The first frame extractor 34e may operate to extract real-time frames from multiple receiving queues for real-time frames in a round robin manner, for example.
[0183] Although the case where the first frame extractor 34e extracts a real-time frame has been described here, the same applies to the case where the second frame extractor 34f extracts a best-effort frame.
[0184] Although the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 has been described here, the configurations of the other destination determining units 34-2 to 34-N are similar to that of the destination determining unit 34-1.
[0185] The first determination unit 34a and the transmission processing unit 34c execute the same processing as in the present embodiment described above after the first frame extraction unit 34e extracts the real-time frame (the real-time frame is output from the first frame extraction unit 34e to the first determination unit 34a). The second determination unit 34b and the transmission processing unit 34c execute the same processing as in the present embodiment described above after the second frame extraction unit 34f extracts the best-effort frame (the best-effort frame is output from the second frame extraction unit 34f to the second determination unit 34b).
[0186] According to the first and second variants of this embodiment described above, even if the number of receive queues provided for one communication port is other than two, it is possible to achieve both reduced delay time and increased FDB capacity.
[0187] In this embodiment, the eFDB33a manages the destination determination information using a CAM, and the pFDB33b manages the destination determination information using a hash table that holds hash values. However, as long as the eFDB33a is configured in a manner that allows faster access than the pFDB33b, the eFDB33a and the pFDB33b may be configured to manage the destination determination information in a manner different from that of this embodiment. In addition, in this embodiment, a configuration may be adopted in which the capacity of the pFDB33b that is referred to when transferring a best effort frame is made larger than the capacity of the eFDB33a.
[0188] In addition, although TSN has been described as a standard for achieving real-time performance in this embodiment, the switch device 30 of this embodiment may conform to other standards as long as it is configured to perform forwarding processing for frames equivalent to real-time frames (IEEE 802.1Qbu / IEEE 802.3br Express frames) and best-effort frames (IEEE 802.1Qbu / IEEE 802.3br Preemptable frames), for example.
[0189] In addition, while it is assumed that the forwarding processing unit 34 and management unit 36, etc. included in the switch device 30 in this embodiment are realized by hardware, the forwarding processing unit 34 and management unit 36 may also be realized by software.
[0190] 16 shows an example of a hardware configuration of the switch device 30 when the forwarding processing unit 34 and the management unit 36 are realized by software. As shown in FIG 16, the switch device 30 includes a CPU 301, a non-volatile memory 302, a main memory 303, a communication device 304, and the like.
[0191] The CPU 301 is a processor that controls the operation of the components in the switch device 30. The CPU 301 (i.e., the computer of the switch device 30) executes a predetermined program loaded from the non-volatile memory 302 to the main memory 303, thereby realizing the functions of the forwarding processing unit 34 and the management unit 36.
[0192] The communication device 304 is a device configured to execute communication with, for example, the external communication devices 1-1 to 1-N.
[0193] 16, memory areas used for the first receive queues 32-1a to 32-Na, the second receive queues 32-1b to 32-Nb, the eFDB 33a, the pFDB 33b, the first transmit queues 35-1a to 35-Na, and the second transmit queues 35-1b to 35-Nb included in the switch device 30 are secured, for example, in the main memory 303. Also, the communication processing units 31-1 to 31-N included in the switch device 30 are included in, for example, a communication device 304.
[0194] Second embodiment Next, a second embodiment will be described. The configuration of the switch device according to this embodiment is similar to that of the first embodiment described above, and therefore will be described with reference to Fig. 7 as appropriate. In the following description, detailed description of the same parts as those of the switch device according to the first embodiment described above will be omitted.
[0195] In the case of a configuration in which the destination port is determined by referring to the eFDB 33a and the pFDB 33b as described in the first embodiment, it is difficult for multiple destination determination units 34-1 to 34-N to simultaneously access the eFDB 33a and the pFDB 33b. Therefore, in this embodiment, as described above, copies of the eFDB 33a and the pFDB 33b (i.e., the destination determination information stored in the eFDB 33a and the pFDB 33b) are cached and held inside the destination determination unit 34-1, which is different from the first embodiment.
[0196] An example of the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 in this embodiment will be described with reference to FIG.
[0197] As shown in FIG. 17, the destination determination unit 34-1 internally holds an eFDB cache 34g which is a copy of the eFDB 33a and a pFDB cache 34h which is a copy of the pFDB 33b described in the first embodiment.
[0198] The eFDB cache 34g includes the destination determination information stored in the eFDB 33a, and in the eFDB cache 34g, the destination determination information is managed using a CAM in the same manner as in the eFDB 33a. The pFDB cache 34h includes the destination determination information stored in the pFDB 33b, and in the pFDB cache 34h, the destination determination information is managed using a hash table in the same manner as in the pFDB 33b.
[0199] The first determination unit 34a retrieves a real-time frame from the first receiving queue 32-1a corresponding to the destination determination unit 34-1, and determines a destination port for the real-time frame based on the header information attached to the real-time frame and the eFDB cache 34g (i.e., the cached destination determination information).
[0200] The second determination unit 34b retrieves a best effort frame from the second receive queue 32-1b corresponding to the destination determination unit 34-1, and determines a destination port for the best effort frame based on the header information attached to the best effort frame and the pFDB cache 34h (i.e., the cached destination determination information).
[0201] Although the configuration of the destination determining unit 34-1 included in the forwarding processing unit 34 has been described here, the configurations of the other destination determining units 34-2 to 34-N are similar to that of the destination determining unit 34-1.
[0202] In addition, the destination determination unit 34-1 in this embodiment performs processing similar to that of the first embodiment described above, except that the first determination unit 34a refers to the eFDB cache 34g when determining a destination port for a real-time frame, and the second determination unit 34b refers to the pFDB cache 34h when determining a destination port for a best-effort frame.
[0203] In this embodiment, the destination determination information (first destination determination information) stored in eFDB33a (first database) and the destination determination information (second destination determination information) stored in pFDB33b (second database) are cached, and the destination port (second communication port) is determined based on the cached destination determination information. This enables multiple destination determination units 34-1 to 34-N included in the forwarding processing unit 34 to operate simultaneously (refer to the destination determination information), thereby achieving higher real-time performance.
[0204] Incidentally, in the case of a configuration in which the destination determination information stored in the eFDB 33a and pFDB 33b is cached in the forwarding processing unit 34 (destination determination units 34-1 to 34-N) as described above, similar to the above-mentioned FDB update process, it is conceivable that the destination determination units 34-1 to 34-N update the eFDB cache 34g and the pFDB cache 34h (destination determination information) based on a frame received in the switch device 30. When the eFDB cache 34g and the pFDB cache 34h are updated in this way, a process (hereinafter referred to as a synchronization process) is required to synchronize the eFDB 33a and the pFDB 33b (the destination determination information stored therein) with the eFDB cache 34g and the pFDB cache 34h.
[0205] However, since eFDB cache 34g is a copy (cache) of the FDB for real-time frames (i.e., eFDB 33a), and synchronization processing between eFDB 33a and eFDB cache 34g involves a write process to eFDB 33a, performing this synchronization processing can cause delays and increased jitter in the transfer processing of real-time frames.
[0206] For this reason, in this embodiment, the synchronization process between the eFDB 33a and the eFDB cache 34g (i.e., the process of synchronizing the destination determination information stored in the eFDB 33a with the cached destination determination information) is not executed in response to the reception of a real-time frame in the switch device 30. This makes it possible to avoid delays and jitters caused by the synchronization process and to achieve high real-timeness in the transfer process for real-time frames. However, it is possible to execute the synchronization process between the eFDB 33a and the eFDB cache 34g in response to an instruction from outside the switch device 30, for example.
[0207] Although the case where the eFDB cache 34g (destination determination information) is synchronized with the eFDB 33a has been described here, it is assumed that the update process of the eFDB cache 34g itself is not executed when a real-time frame is received.
[0208] On the other hand, the pFDB cache 34h is a copy (cache) of the FDB for best effort frames (i.e., pFDB 33b), and in this pFDB cache 34h, it is preferable to prioritize managing a large number of entries (destination determination information) over reducing delay and jitter to achieve real-time performance.
[0209] For this reason, in this embodiment, the synchronization process between the pFDB 33b and the pFDB cache 34h (i.e., the process of synchronizing the destination determination information stored in the pFDB 33b with the cached destination determination information) is performed in response to reception of a best effort frame in the switch device 30.
[0210] Specifically, for example, when the pFDB cache 34h held in the destination determination unit 34-1 is updated based on a best-effort frame transmitted from the external communication device 1-1, a synchronization process is performed between the pFDB 33b and the updated pFDB cache 34h. In this case, a synchronization process is further performed between the pFDB 33b, which has been synchronized with the pFDB cache 34h held in the destination determination unit 34-1, and the pFDB caches 34h held in each of the other destination determination units 34-2 to 34-N. This makes it possible to synchronize the pFDB 33b with the pFDB caches 34h held in each of the destination determination units 34-1 to 34-N.
[0211] The synchronization process between the pFDB 33b and the pFDB cache 34h may be performed at a predetermined timing (for example, a timing managed by a timer or the like) after the pFDB cache 34h is updated in response to reception of a best effort frame.
[0212] That is, in this embodiment, the synchronization process between the eFDB 33a and the eFDB cache 34g is not performed in response to reception of a real-time frame, and the synchronization process between the pFDB 33b and the pFDB cache 34h is performed in response to reception of a best-effort frame.
[0213] Although it has been described here that synchronization processing between eFDB33a and eFDB cache 34g is not performed in response to reception of a real-time frame, the switch device 30 of this embodiment may be configured to operate so that synchronization processing between the eFDB33a and eFDB cache 34g is performed less frequently than synchronization processing between pFDB33b and pFDB cache 34h.
[0214] Furthermore, in the present embodiment, for example, the pFDB cache 34h has been described as a copy of the pFDB 33b, but the destination determination information included in the pFDB cache 34h may be different from the destination determination information stored in the pFDB 33b.
[0215] Specifically, the number of destination determination information included in the pFDB cache 34h (i.e., the capacity of the pFDB cache 34h) may be smaller than the number of destination determination information stored in the pFDB 33b (the capacity of the pFDB 33b). In this case, the destination determination information included in the pFDB cache 34h can be replaced with the destination determination information stored in the pFDB 33b according to an algorithm such as LRU (Least Recently Used). When the pFDB cache 34h is updated, the oldest destination determination information among the destination determination information included in the pFDB cache 34h may be discarded and new destination determination information (entry) may be added, but the discarded destination determination information may be reflected (added) in the pFDB 33b.
[0216] Furthermore, the pFDB 33b and the pFDB cache 34h may manage destination determination information using different algorithms.
[0217] According to at least one of the embodiments described above, it is possible to provide a switch device, a method, and a program that can achieve both a reduction in delay time and an increase in the capacity of a database.
[0218] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention. [Explanation of symbols]
[0219] 1-1 to 1-N: external communication devices, 30: switch device, 31-1 to 31-N: communication processing units, 32-1 to 32-N, 32-11 to 32-Nm: receiving queues, 32-1a to 32-1N: first receiving queues, 32-1b to 32-Nb: second receiving queues, 33a: eFDB (first database), 33b: pFDB (second database), 34: forwarding processing units, 34-1 to 34-N: destination determination units, 34a: first determination unit, 34b ...second decision unit, 34c...transmission processing unit, 34d...decision unit, 34e...first frame extraction unit, 34f...second frame extraction unit, 34g...eFDB cache, 34h...pFDB cache, 35-1a to 35-Na...first transmission queue, 35-1b to 35-Nb...second transmission queue, 36...management unit, 37...attribute information DB (third database), 301...CPU, 302...non-volatile memory, 303...main memory, 304...communication device.
Claims
1. In a switch device having a plurality of communication ports, a receiving unit configured to receive a frame transmitted from a first external communication device connected to a first communication port of the plurality of communication ports; a first database and a second database storing destination determination information used to determine a second communication port to which a second external communication device that is a destination of the received frame is connected among the plurality of communication ports; a determination unit that, when the received frame is a first frame that requires low-latency transfer, determines the second communication port by accessing destination determination information stored in the first database based on header information added to the first frame, and, when the received frame is a second frame different from the first frame, determines the second communication port by accessing destination determination information stored in the second database based on header information added to the second frame; a first receiving queue for storing the first frame; a second receiving queue for storing the second frame; Equipped with the first database is configured to be able to access the destination determination information at a higher speed than the second database; The determination unit includes a first determination unit and a second determination unit, the first determination unit determines the second communication port based on header information added to a first frame extracted from the first receiving queue; The second determination unit determines the second communication port based on header information added to the second frame extracted from the second receiving queue. Switch device.
2. a third database storing attribute information indicating that the first receiving queue is a receiving queue for the first frame and that the second receiving queue is a receiving queue for the second frame; The first frame is removed from a first receiving queue determined based on the attribute information; The second frame is removed from a second receiving queue determined based on the attribute information. The switch device according to claim 1.
3. A switch device having a plurality of communication ports, a receiving unit configured to receive a frame transmitted from a first external communication device connected to a first communication port of the plurality of communication ports; a first database and a second database storing destination determination information used to determine a second communication port to which a second external communication device that is a destination of the received frame is connected among the plurality of communication ports; a determination unit that determines the second communication port by accessing destination determination information stored in the first database based on header information added to the first frame when the received frame is a first frame that requires low-latency transfer, and that determines the second communication port by accessing destination determination information stored in the second database based on header information added to the second frame when the received frame is a second frame different from the first frame; Equipped with the first database is configured to be able to access the destination determination information at a higher speed than the second database; the determination unit caches the first destination determination information stored in the first database and the second destination determination information stored in the second database, and determines the second communication port based on the cached first and second destination determination information; a process of synchronizing the first destination determination information stored in the first database with the cached first destination determination information is not performed in response to receiving the first frame; The process of synchronizing the second destination determination information stored in the second database with the cached second destination determination information is executed in response to receiving the second frame. Switch device.
4. A switch device having a plurality of communication ports, a receiving unit configured to receive a frame transmitted from a first external communication device connected to a first communication port of the plurality of communication ports; a first database and a second database storing destination determination information used to determine a second communication port to which a second external communication device that is a destination of the received frame is connected among the plurality of communication ports; a determination unit that determines the second communication port by accessing destination determination information stored in the first database based on header information added to the first frame when the received frame is a first frame that requires low-latency transfer, and that determines the second communication port by accessing destination determination information stored in the second database based on header information added to the second frame when the received frame is a second frame different from the first frame; Equipped with The first frame includes an IEEE 802.1Qbu / IEEE 802.3br Express frame; The second frame includes an IEEE 802.1Qbu / IEEE 802.3br Preemptable frame. Switch device.
5. A method implemented by a switch device having a plurality of communication ports, comprising: receiving a frame transmitted from a first external communication device connected to a first communication port of the plurality of communication ports; determining a second communication port to which a second external communication device, which is the destination of the received frame, is connected by accessing destination determination information stored in a first database based on header information added to the first frame, when the received frame is a first frame that requires low-latency transfer; and determining the second communication port by accessing destination determination information stored in a second database based on header information added to the second frame, when the received frame is a second frame different from the first frame. Equipped with the first database is configured to be able to access the destination determination information at a higher speed than the second database; the switch device includes a first receiving queue for storing the first frame and a second receiving queue for storing the second frame; The determining step includes: determining the second communication port based on header information added to the first frame removed from the first receiving queue; determining the second communication port based on header information added to the second frame removed from the second receiving queue; Including, the switch device further includes a third database that stores attribute information indicating that the first receiving queue is a receiving queue for the first frame and that the second receiving queue is a receiving queue for the second frame; The first frame is removed from a first receiving queue determined based on the attribute information; The second frame is removed from a second receiving queue determined based on the attribute information. method.
Citation Information
Patent Citations
Input unit
JP1979033627A
Network node and network node program
JP2008148176A
Data transfer device
JP2011124799A
Communication device and priority control method
JP2013255159A
Network device
JP2017188814A
