Transfer device, transfer procedure, and transfer program

Abstract

A transfer device (10) forwards a received frame. A frame identification unit (121) assigns a corresponding identifier to a received frame based on its content. An allocation unit (122) stores a received frame in a receive queue (123) corresponding to an identifier assigned to the received frame. A receive gate control unit (124) executes a receive gate control process to read a received frame from the receive queue (123) based on a gate control setting determined by a setting unit (104) to place a received frame that has violated a communication cycle in a receive queue.

Description

Technical field

[0001] The present invention relates to a transfer device, a transfer method and a transfer program. Background on the state of the art

[0002] IEEE 802.1Q-2018 specifies TAS. TAS stands for "Time-Aware Shaper." TAS is a patent application for transfer devices designed to ensure the transmission quality of each communication stream in a network where communication streams with varying quality requirements coexist. TAS performs time-controlled transmissions based on the time synchronized within the network. However, if a communication stream occurs that violates a communication cycle defined during the network design phase, a planned transmission will fail due to TAS. To address this issue, IEEE 802.1Q-2018 also specifies PSFP as a method for discarding a communication stream that violates a communication cycle at the time of reception in a transfer device. PSFP stands for Per-Stream Filtering and Policing.

[0003] IEEE 802.1Q-2018 also specifies FP as a transmission device specification to ensure that no delays occur in high-priority communication streams. FP stands for Frame Preemption. In FP, if a transmission request for a high-priority frame requiring low-delay transmission occurs while a low-priority frame (which does not require low-delay transmission) is being transmitted, the transmission of the low-priority frame is interrupted and split to transmit the high-priority frame via an interrupted transmission, thereby reducing the transmission delay of the high-priority frame.After the transmission of the high-priority frame is complete, the low-priority frame split by the interrupt transmission is transferred to be combined and reintegrated into the frame before being split at a transfer device on the receiving side. Reference list Non-patented literature

[0004] Non-Patent Literature 1: “IEEE 802.1Q-2018-IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks” Summary of the invention: Technical problem

[0005] If the transfer device supports PSFP, the transmission quality of communication streams that do not violate the cycle is ensured. However, communication streams that violate this cycle are simply discarded without any guarantee of transmission quality. To prevent end devices from interrupting the communication stream cycle, it is necessary to synchronize the time between the end devices with high precision and to implement advanced transmission timing control based on the synchronized time. However, advanced transmission timing control using synchronized time typically increases the cost of the end devices.If end devices that can control the transmission time with high precision cannot be used, a problem with transmission control via PSFP is that the transmission quality of communication streams with large transmission time errors cannot be guaranteed.

[0006] One objective of the present disclosure is to reduce the required accuracy of transmission time synchronization between terminal devices in order to lower terminal device costs. Solution to the problem

[0007] A transfer device according to the present disclosure comprises a frame identification unit to assign an appropriate identifier to a received frame based on its content; an allocation unit for storing a received frame in a receive queue that corresponds to an identifier assigned to the received frame; a setting unit for setting a gate control setting to define open / close information for a receive queue, wherein the gate control setting is configured such that a received frame that has violated a communication cycle waits in the receive queue; and a receive gate control unit for executing a receive gate control process to read a received frame from the receive queue based on the gate control setting. Advantageous effects of the invention

[0008] In a transfer device according to the present disclosure, a received frame is read from a receive queue based on a gate control setting that causes a received frame that has violated a communication cycle to wait in a receive queue. Therefore, with the transfer device according to the present disclosure, transmission time errors from terminal devices are absorbed in the transfer device, thus reducing the required accuracy of transmission time synchronization between terminal devices and contributing to a reduction in terminal device costs. Brief description of the drawings Fig. Figure 1 is a representation illustrating the failure of a time-controlled transmission by TAS. Fig. Figure 2 is a representation that provides an overview of the operation of the transfer device that supports PSFP. Fig. Figure 3 is a representation which shows an example of the functional configuration of a transfer device according to embodiment 1. Fig. Figure 4 is a representation which shows an example of the general configuration of a transfer system and an overview of the operation of the transfer device according to embodiment 1. Fig. Figure 5 is a representation illustrating an example of the structure of the gate control settings according to embodiment 1. Fig. Figure 6 is a representation illustrating an example of gate opening / closing operations based on the gate control settings according to embodiment 1. Fig. Figure 7 is a representation that shows an example of the hardware configuration of the transfer device according to embodiment 1. Fig. Figure 8 is a representation which shows another example of the hardware configuration of the transfer device according to embodiment 1. Fig. Figure 9 is a representation which shows an example of the functional configuration of the transfer device according to embodiment 2. Description of embodiments

[0009] Exemplary embodiments of the present disclosure are described below with reference to the drawings. In the drawings, identical or corresponding parts are identified by the same reference numerals. In the description of the embodiments, the description of identical or corresponding parts is appropriately omitted or simplified. In the following drawings, the relative sizes of the components may differ from the actual sizes. In the description of the exemplary embodiments, directions or positions such as "top," "bottom," "left," "right," "front," "back," "top," and "rear" may be indicated. These terms are used only for ease of description and are not intended to restrict the placement and orientation of components such as devices, equipment, or parts. Design 1.

[0010] Fig. Figure 1 is a representation illustrating the failure of a time-controlled transmission by TAS.

[0011] Fig. Figure 2 is a representation that provides an overview of the operation of the transfer device that supports PSFP.

[0012] The Fig. 1 and Fig. Figure 2 shows examples of the transfer device that forms the basis of this embodiment.

[0013] In the Fig. In the TAS shown in Figure 1, time-controlled transmissions are carried out based on the time synchronized within a network. However, as in Fig. As shown in Figure 1, a time-controlled transmission through the TAS will fail if a communication stream occurs that violates a communication cycle defined in the network design phase.

[0014] As in Fig. As shown in Figure 2, the transmission quality of a communication stream No. 1 that has not violated the cycle is ensured if the transfer device supports PSFP. However, a communication stream No. 2 that violates the cycle is simply discarded without ensuring transmission quality. *** Configuration Description ***

[0015] Fig. Figure 3 is a representation which shows an example of the functional configuration of a transfer device 10 according to this embodiment.

[0016] As in Fig. As shown in Figure 3, the transfer device 10 comprises a connector 101, a receiving unit 102, a transmission unit 103 and a fixing unit 104.

[0017] The receiving unit 102 comprises a frame identification unit 121, an allocation unit 122, a receiving queue 123, a receiving gate control unit 124 and a multiplexing unit 125.

[0018] The transmission unit 103 comprises a separation unit 131, a transmission queue 132 and a transmission gate control unit 133.

[0019] Note that the number of these function blocks does not correspond to the number in Fig. 3. The specified number must be limited, and the number of each function block must be greater or less than the number in Fig. The number 3 can be specified. *** Description of a Functionality ***

[0020] The following describes the operation of the transfer device 10 according to this embodiment. A sequence of operations of the transfer device 10 is equivalent to a transfer process. A program that implements the operation of the transfer device 10 corresponds to a transfer program.

[0021] Fig. Figure 4 is a representation which shows an example of the general configuration of a transfer system 500 and an overview of the operation of the transfer device 10 according to this embodiment.

[0022] As in Fig. As shown in Figure 4, each transfer device in the transfer system 500 transmits a communication stream that is sent and received between terminal devices.

[0023] In a transfer system according to Fig. 2. Communication stream No. 2, which violated the cycle, is discarded without ensuring transmission quality.

[0024] On the other hand, the transfer device 10 in the transfer system 500 according to this embodiment causes a cycle-violating frame to wait in a queue so that communication stream No. 1 and communication stream No. 2 can be transmitted as planned.

[0025] The port 101 forwards a frame received from an external device to the frame identification unit 121.

[0026] The frame identification unit 121 assigns a corresponding identifier to the received frame based on the content of the frame received from port 101. The identifier is uniquely determined by pattern matching between the attributes of the received frame and the settings obtained from the configuration unit 104. The attributes of the received frame include attributes such as a receiving port number, header information, payload information, and error information.

[0027] The setting unit 104 provides configuration information for determining identifiers.

[0028] The setting unit 104 also sets the gate control settings.

[0029] The configuration unit 104 can also specify a type of branch port and trunk port for each port that receives frames.

[0030] The configuration information includes, for example, a setting such as assigning ID = 1 when the destination MAC address of a frame received on port number 1 is "12-34-56-AB-CD-EF" and the EtherType is "0x0800" (IP communication). MAC stands for Media Access Control. IP stands for Internet Protocol. ID stands for Identifier.

[0031] In this case, the frame identification unit 121 determines whether a received frame is a frame that matches the above setting and assigns ID = 1 to the received frame if there is a match.

[0032] The identifier can be assigned to the received frame by temporarily replacing part of the frame's content within the transfer device. Alternatively, a signal indicating the identifier can be transmitted separately from and in parallel to the received frame to a subsequent functional block.

[0033] Identification conditions can be set by a user in the setting unit 104 as described above, or identification conditions can be recorded statically in the frame identification unit 121.

[0034] The control of the gate setting and the setting of a connection type will be described later.

[0035] Allocation unit 122 receives the received frame from frame identification unit 121. Based on the identifier assigned to the received frame by frame identification unit 121, allocation unit 122 transfers the received frame to the receiving queue 123 that corresponds to the identifier.

[0036] In particular, if the transfer device 10 has a receive queue corresponding to the identifier assigned to the received frame, the allocation unit 122 stores the received frame in the corresponding receive queue. If, however, the transfer device 10 does not have a corresponding receive queue, the received frame is transferred to the receive gate control unit 124. That is, if the transfer device 10 does not have a corresponding receive queue, typical PSFP processing is performed.

[0037] The receive queue 123 temporarily collects frames received by the allocation unit 122. The receive queue 123 transmits information about the presence or absence of accumulated frames and the frame length of any frame at the head of the queue to the receive gate control unit 124. It is not necessary to provide a separate receive queue for each identifier. For example, by assigning multiple identifiers to one receive queue, there can be fewer receive queues than the number of identifiers that can be set in the transfer device 10.

[0038] A transfer device equipped with an FP function typically has a receive queue for combining split frames, and the receive queue used for the FP function can be used as receive queue 123.

[0039] The receive gate control unit 124 executes a receive gate control process to read received frames from the receive queue 123 based on the gate control settings defined in the setting unit 104. When frames have accumulated in the receive queue 123, the receive gate control unit 124 reads the frames from the receive queue 123 based on the gate control settings.

[0040] In particular, the receive gate control unit 124 selects a queuing operation or a rejection operation as the receive gate control process based on a difference between the gate control settings and the arrival timing of a received frame. That is, depending on the extent to which the cycle is violated, either a transmission or a rejection is selected.

[0041] The gate control settings define the information for opening and closing the receive queues. These settings determine whether a received frame, which has violated the communication cycle, waits in a receive queue.

[0042] Fig. Figure 5 is a representation illustrating an example of the structure of the gate control settings according to this embodiment.

[0043] Fig. Figure 6 is a representation illustrating an example of gate opening / closing operations based on the gate control settings according to this embodiment.

[0044] The gate control settings are arranged in a list structure and consist of a list index, opening / closing information for the receiving queues, and the time.

[0045] The open / close information for the receive queues is information for opening / closing each receive queue, which has a value of 0 or 1. 0 indicates a state in which reading from the receive queue is forbidden. 1 indicates a state in which reading from the receive queue is allowed.

[0046] A time setting specifies the period during which reading is permitted. For example, a time setting might be set to an integer value in nanoseconds.

[0047] The gate control setting of index = 1 in Fig. 5 indicates that reading from a receive queue 1 is allowed for 512 nanoseconds.

[0048] The receive gate control unit 124 refers to the gate control settings in ascending order of index numbers, reads frames only from a receive queue that is currently authorized to read from, and transmits the frames to the multiplex unit 125. If there are multiple receive queues from which reading is permitted, the receive queue from which frames are read is determined according to a specific rule. Specifically, the receive-side gate control unit 1024 repeats a process in which received frames from receive queue 1 with index = 1 are read for 512 ns, then received frames from receive queues 1 and 2 with index = 2 are read for 256 ns, and so on.

[0049] The specific rule could be, for example, a strict priority rule or a round-robin rule. A strict priority rule prioritizes read frames from receive queues in ascending order of queue number. A round-robin rule periodically rotates the receive queue from which the frame is read.

[0050] After the receiver gate control unit 124 has retrieved the gate control setting at the end of the list, it retrieves the list again sequentially from the beginning.

[0051] If the transfer device 10 does not have a receive queue that matches the identifier, the allocation unit 122 forwards the received frame to the receive gate control unit 124 without storing the received frame in a receive queue 123.

[0052] The receiving gate control unit 124 receives gate control settings from the setting unit 104 for each identifier for received frames that correspond to the one in Fig. The gate control settings for each receive queue are similar to those shown in Figure 5. The receive gate control unit 124 discards a frame that is not currently allowed to be read by the receive gate control unit 124. The gate control settings for each frame identifier, which are similar to the gate control settings for each receive queue, specifically relate to settings such as the number of seconds for a frame with ID = 1, the number of seconds for a frame with ID = 2, and so on.

[0053] With reference to the gate control settings for each receive queue and with reference to the gate control settings for each frame identifier, the following operations are performed in parallel.

[0054] The receive gate control unit 124 does not necessarily have to strictly adhere to the timing specifications in the gate control settings. The setting unit 104 can separately set timing information that specifies an allowable error, and if the current time is within the allowable error range compared to the allowable time, frames can be transmitted without being dropped. If frames accumulate in a receive queue even though the current time is outside the allowable error range compared to the allowable time, the accumulated frames can be dropped without being transmitted to the multiplex unit 125. By allowing such an allowable error, frames that clearly violate the cycle can be dropped, resulting in a reduction of bandwidth usage in the network.

[0055] As described above, the receive gate control unit 124 causes a frame whose transmission time from a terminal device does not match the schedule, i.e., does not match the gate control settings, to wait in a receive queue until the time is reached at which transmission is permitted by the gate control settings. This allows the transfer device to absorb a transmission timing error from the terminal device, thereby reducing the accuracy required of the terminal device in synchronizing the transmission time.

[0056] The configuration unit 104 can set a type of "branch port" or "trunk port" for each connection of the transfer device 10. The setting value of this connection type is transmitted to the receiving unit 102.

[0057] A "branch connection" is, for example, a connection that is linked to a terminal device.

[0058] A “trunk port”, for example, is a connection that is linked to another transfer device 10.

[0059] A port configured as a branch port performs the receive gate control process described above, and a port configured as a trunk port performs typical transmit control without performing the receive gate control process.

[0060] In a port configured as a trunk port, the process in which the frame identification unit 121 assigns an identifier to which the allocation unit 122 refers is omitted. The allocation unit 122 transfers frames to the receive gate control unit 124 instead of storing the frames in the receive queue 123. The control process in the receive gate control unit 124 can also be omitted.

[0061] The reason for this is as follows. If the receive gate control process is performed at branch ports to absorb transmission time errors from end devices, the normality of the transmission plan for each communication stream at the trunk port is ensured. Therefore, the trunk port does not need to perform any processing to compensate for transmission time errors.

[0062] By eliminating the receive gate control process at the trunk port, computing costs can be reduced and transmission delays in communication streams in a trunk line can be minimized.

[0063] The multiplexing unit 125 multiplexes several frames received by the receive gate control unit of each port. The separation unit 131 stores a received frame in the transmission queue 132 according to the destination of the received frame. The transmission queue 132 and the transmission gate control unit perform transmission control scheduling according to TAS as defined in IEEE 802.1Q-2018. *** Hardware Configuration Description ***

[0064] The transfer device 10 is a computer. In the transfer device 10, the functions of the receiving unit 102, the transmitting unit 103 and the fixing unit 104 are implemented by hardware, software, firmware or a combination thereof. <software-implementierung>

[0065] Fig. Figure 7 is a representation which shows an example of the hardware configuration of the transfer device 10 according to this embodiment.

[0066] The transfer device 10 is a computer. The transfer device 10 comprises a processor 910 and other hardware components such as a main memory 921, an auxiliary storage device 922, an input / output interface 930, and a communication interface 950. The processor 910 is connected to other hardware components via a signal line 80 and controls these other hardware components.

[0067] As described above, the transfer device 10 comprises the following functional elements: the connector 101, the receiving unit 102, the transmitting unit 103, and the fixing unit 104. The functions of the receiving unit 102, the transmitting unit 103, and the fixing unit 104 are implemented by software. These functions can be referred to as the functions of the transfer device 10. The receiving unit 102, the transmitting unit 103, and the fixing unit 104 can be referred to as the units of the transfer device 10.

[0068] The processor 910 is a device that executes the transfer program. The transfer program is a program that implements the functions of the transfer device 10.

[0069] The 910 processor is an integrated circuit (IC) that performs operational processing. Specific examples of the 910 processor include a CPU, a DSP, and a GPU. IC stands for Integrated Circuit. CPU stands for Central Processing Unit. DSP stands for Digital Signal Processor. GPU stands for Graphics Processing Unit.

[0070] The 921 main memory is a storage device for temporarily storing data. Specific examples of 921 main memory are SRAM and DRAM. SRAM stands for Static Random Access Memory. DRAM stands for Dynamic Random Access Memory.

[0071] The Auxiliary Storage Device 922 is a storage device for storing data. A specific example of the Auxiliary Storage Device 922 is a hard disk drive (HDD). Alternatively, the Auxiliary Storage Device 922 can be a portable storage medium, such as an SD (registered trademark), CF (registered trademark), NAND flash memory card, flexible disk, optical disk, compact disc, Blu-ray (registered trademark) disc, or DVD. HDD stands for Hard Disk Drive. SD (registered trademark) stands for Secure Digital. CF stands for CompactFlash (registered trademark). DVD stands for Digital Versatile Disc.

[0072] The 930 input / output interface is an interface for connecting input and output devices. Specific examples of the 930 input / output interface are a USB port and an HDMI port (registered trademark). USB stands for Universal Serial Bus. HDMI (registered trademark) stands for High-Definition Multimedia Interface.

[0073] The Communications Interface 950 is an interface for communicating with external devices. Specific examples of Communications Interface 950 include an Ethernet port (registered trademark) and a device that performs wireless communication. Communications Interface 950 is also referred to as data communication hardware.

[0074] Connection 101 is implemented via communication interface 950.

[0075] The transfer program is executed in transfer device 10. The transfer program is read into processor 910 and executed by processor 910. Memory 921 stores not only the transfer program but also an OS (operating system). OS is an abbreviation for Operating System. Processor 910 executes the transfer program while running the OS. The transfer program and the OS can be stored in auxiliary memory device 922. The transfer program and the OS stored in auxiliary memory device 922 are loaded into memory 921 and executed by processor 910. Part or all of the transfer program can be embedded within the OS.

[0076] The transfer device 10 can include a variety of processors as an alternative to processor 910. These multiple processors share the execution of the transfer program. Each processor is a device that executes the transfer program, just like processor 910.

[0077] Data, information, signal values ​​and variable values ​​used, processed or output by the transfer program are stored in the main memory 921 or in the auxiliary memory device 922 or in a register or cache memory within the processor 910.

[0078] Each unit of the transfer device 10 can be interpreted as a "circuit," "step," "procedure," "process," or "circuit arrangement." The transfer program instructs a computer to execute each process, with the "unit" of each unit of the transfer device 10 being interpreted as a "process." The "process" of each process of the transfer device 10 can be interpreted as a "program," "program product," "computer-readable storage medium that stores a program," or "computer-readable recording medium that records a program." The transfer procedure is a process that is carried out by the transfer device 10 executing the transfer program. The transfer program can be stored and made available on a computer-readable storage medium. The transfer program can be made available as a program product. <hardware-implementierung>

[0079] Fig. Figure 8 is a representation which shows an example of the hardware configuration of the transfer device 10 according to this embodiment.

[0080] In this embodiment, the functions of the units of the transfer device 10 are implemented by software. Alternatively, the functions of the units of the transfer device 10 can be implemented by hardware.

[0081] In particular, the transfer device 10 has an electronic circuit 909 instead of the processor 910.

[0082] The electronic circuit 909 is a dedicated electronic circuit that implements the functions of the units of the transfer device 10. Specifically, the electronic circuit 909 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0083] The functions of the units of the transfer device 10 can be realized by a single electronic circuit or can be distributed among and realized by a multitude of electronic circuits.

[0084] As a further variant, some of the functions of the units of the transfer device 10 can be implemented by the electronic circuitry, and the remaining functions can be implemented by software. In this embodiment, the functions of the units of the transfer device 10 are implemented by software.

[0085] Both the processor and the electronic circuit are also referred to as a processing circuit. This means that the functions of the units of the transfer device 10 are implemented by the processing circuit. *** Description of effects of this embodiment ***

[0086] In the transfer device according to this embodiment, each frame is assigned to a corresponding receive queue before the received frames are multiplexed in the transfer device. By holding a received frame in a queue according to the gate control settings, which are settings for scheduled transmissions, it is possible to compensate for transmission timing errors of devices and to avoid failures of scheduled transmissions after multiplexing.

[0087] Therefore, with the transfer device according to the present disclosure, transmission time errors from terminal devices are absorbed in the transfer device, so that the required accuracy of the transmission time synchronization between devices can be reduced and a reduction in device costs can be achieved. Design 2.

[0088] This embodiment mainly describes the differences to embodiment 1 and additions to embodiment 1.

[0089] In the present embodiment, components with essentially the same function as those in embodiment 1 are identified with the same reference numerals, and their description is omitted. *** Configuration Description ***

[0090] Fig. Figure 9 is a representation illustrating an example of the functional configuration of the transfer device 10 according to this embodiment.

[0091] In this embodiment, a configuration is described in which an end device is connected to a specific port of the transfer device 10.

[0092] For example, the configuration is designed such that one terminal device is connected to an electrical port of the transfer device 10 and another transfer device 10 is connected to an optical port of the transfer device 10.

[0093] If the connections to which terminal devices are connected are limited, as in this case, it is sufficient for the receiver gate control process to be carried out only at the branch connections to which terminal devices are connected, as described in embodiment 1.

[0094] It is sufficient to provide the allocation unit 122, the receiving queue 123 and the receiving gate control unit 124 only in certain ports, as in Fig. 9 shown. In the case of Fig. In 9, connection 101 corresponds to a branch port and connection 105 to a trunk port. The operation performed by the transfer device 10 is essentially the same as in embodiment 1. *** Description of effects of this embodiment ***

[0095] In the transfer device according to this embodiment, the costs of the transfer device can be further reduced in addition to the effects of embodiment 1.

[0096] In embodiments 1 and 2 above, each unit of the transfer device is described as an independent functional block. However, the configuration of the transfer device may differ from the configuration described above. The functional blocks of the transfer device may be arranged in any configuration, provided that the functions described in the embodiment above can be realized. The transfer device may be a system consisting of a plurality of devices instead of a single device.

[0097] Two or more parts of embodiments 1 and 2 can be implemented in combination. Alternatively, only a single part of these embodiments can be implemented. These embodiments can be implemented wholly or partially in any combination.

[0098] This means that, with regard to embodiments 1 and 2, each embodiment can be freely combined, and any component can be modified in each embodiment. Alternatively, any component can be omitted in each embodiment.

[0099] The embodiments described above are essentially preferred examples and are not intended to limit the scope of this disclosure, the scope of its possible applications, or the scope of its intended uses. The embodiments described above can be modified in various ways as needed. For example, a method described by means of a flowchart or a sequence diagram can be modified accordingly. Reference symbol list

[0100] 10: Transfer device; 101: Connector; 102: Receiver unit; 103: Transmit unit; 104: Fixing unit; 121: Frame identification unit; 122: Allocation unit; 123: Receive queue; 124: Receive gate control unit; 125: Multiplex unit; 103: Transmit unit; 131: Separation unit; 132: Transmit queue; 133: Transmit gate control unit; 500: Transfer system; 909: Electronic circuit; 910: Processor; 921: Main memory; 922: Auxiliary storage device; 930: Input / output interface; 950: Communication interface. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited non-patent literature

[0000] IEEE 802.1Q-2018-IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks

[0004]

Claims

[1] Transfer device comprising: a frame identification unit to assign an appropriate identifier to a received frame based on its content; an allocation unit for storing a received frame in a receive queue that corresponds to an identifier assigned to the received frame; a setting unit for setting a gate control setting to define open / close information for a receive queue, wherein the gate control setting is configured such that a received frame that has violated a communication cycle waits in the receive queue; and a receive gate control unit for executing a receive gate control process to read a received frame from the receive queue based on the gate control setting. [2] Transfer device according to claim 1, where the setting unit specifies setting information for determining an identifier, and wherein the frame identification unit assigns a corresponding identifier based on a pattern matching between attributes, including a receiving port, header information, payload information and error information of the received frame and the setting information. [3] Transfer device according to claim 1 or claim 2, wherein, if the transfer device includes a corresponding receive queue for an identifier assigned to a received frame, the allocation unit stores the received frame in the corresponding receive queue, and if the transfer device does not include a corresponding queue, the allocation unit transmits the received frame to the receive gate control unit. [4] Transfer device according to one of claims 1 to 3, wherein the receiving gate control unit selects either a queue operation or a reject operation as a receiving gate control process based on a difference between the gate control setting and the arrival timing of a received frame. [5] Transfer device according to any one of claims 1 to 4, wherein the configuration unit can specify a type of branch port and trunk port for each port that receives a received frame, and where a port designated as a branch port performs the receive gate control process and a port designated as a trunk port performs the general transfer control without performing the receive gate control process. [6] Transfer device comprising: the assignment of a corresponding identifier to a received frame based on the content of the received frame by a computer; The storage of a received frame by the computer in a receive queue corresponding to an identifier assigned to the received frame; Setting a gate control setting to specify open / close information for a receive queue, wherein the gate control setting is configured such that a received frame that has violated a communication cycle waits in the receive queue, by the computer; and The execution of a receive gate control process to read a received frame from the receive queue based on the gate control setting by the computer. [7] Transfer program that causes a computer to execute: a frame identification process in which a received frame is assigned a corresponding identifier based on its content; an allocation process for storing a received frame in a receive queue that corresponds to an identifier assigned to the received frame; a setting process for setting a gate control setting to establish open / close information for a receive queue, wherein the gate control setting is configured such that a received frame that has violated a communication cycle waits in the receive queue; and a receive gate control process for reading a received frame from the receive queue based on the gate control setting.

Images