Protocol packaging and routing communication system of Ethernet bridging FC

Abstract

The invention discloses a protocol packaging and routing communication system of an Ethernet bridging FC (Fiber Channel). An Ethernet software protocol stack is used for realizing Ethernet protocol stack processing of application data; virtualized Ethernet network card software maintains the information of a virtual MAC address and a virtual IP address of a channel corresponding to each CPU, and encapsulates and analyzes an Ethernet data frame according to the virtual MAC address and the virtual IP address; the virtualized MAC switch software puts Ethernet data needing FC communication into an annular buffer area to wait for Ethernet bridging FC drive software to be dispatched; and the Ethernet bridging FC driving software is used for completing routing addressing mapping of the Ethernet and the FC and establishment of an FC route, and external communication is performed through the FC network terminal after the Ethernet data frame on the annular cache region is added into an FC frame header. According to the invention, the Ethernet and the FC network are combined, and the platform advantages of the FC network and the advantages of good compatibility, wide technical support and the like of the Ethernet can be exerted.

Description

Technical Field

[0001] The present invention belongs to the technical field of airborne bus communication in avionics systems, and particularly relates to a protocol encapsulation and routing communication system for an Ethernet-bridged fiber channel network (hereinafter referred to as FC). Background Art

[0002] As a high-bandwidth and high-reliability communication network, the FC network is widely adopted at home and abroad. The main applications of the FC network in avionics systems are the avionics upgrades of F35 and F18, etc. There have been many applications of using the FC network as the avionics backbone network in avionics systems. Using multimode optical fiber as the transmission medium can provide a high-speed and high-reliability data exchange network for large aircraft. Its advantages include high transmission rate, with the network bandwidth reaching 2.125 Gbps. Currently, the 4.25 Gbps FC network has been widely used in the backbone communication network of avionics systems; through fiber optic interconnection, the weight of the interconnection cables can be effectively reduced; there is no electromagnetic compatibility problem during the transmission process, and the network has good anti-interference ability. As the existing mainstream airborne bus network in aviation, the FC is widely used.

[0003] The application of Ethernet is very extensive and has a good ecological foundation. With the rise of fields such as cloud computing, big data, and artificial intelligence, network data has shown exponential growth. It has positive exploration significance to introduce the Ethernet protocol stack and accumulated experience into the network communication field of traditional avionics systems. Summary of the Invention

[0004] The invention object of the present invention is to provide a protocol encapsulation and routing communication system for Ethernet-bridged FC, which completes the Ethernet Over FC protocol stack, frame encapsulation, routing establishment process, and data forwarding communication through a software architecture, thereby realizing the combination of the Ethernet protocol stack and the FC backbone network of the avionics system.

[0005] The invention object of the present invention is achieved through the following technical solutions:

[0006] A protocol encapsulation and routing communication system for Ethernet-bridged FC includes a main control end and an FC network terminal. The main control end is connected to the FC network through the FC network terminal. The main control end includes an Ethernet software protocol stack, a virtualized Ethernet network card software, a virtualized MAC switch software, and an Ethernet-bridged FC driver software;

[0007] The Ethernet software protocol stack is used to implement the processing of the Ethernet protocol stack for application data;

[0008] The virtualized Ethernet network card software maintains the virtual MAC address and virtual IP address information corresponding to each CPU path, and encapsulates and parses the Ethernet data frame according to the virtual MAC address and virtual IP address;

[0009] The virtualized MAC switch software places the Ethernet data that requires FC communication into a circular buffer and waits for the Ethernet bridging FC driver software to schedule it.

[0010] The Ethernet bridging FC driver software is used to complete the routing address mapping between Ethernet and FC and establish the FC route. It adds an FC frame header to the Ethernet data frame on the circular buffer and communicates externally through the FC network terminal. At the same time, it removes the FC frame header from the data obtained from the FC network terminal and distributes it to the virtualized Ethernet network card software on each core through the virtualized MAC switch software.

[0011] Preferably, in the virtualized Ethernet network card software, the set MAC or IP value is passed in through the interface input parameter and set in the local MAC and IP structures. The MAC and IP values are obtained through the interface return parameter for the encapsulation of the Ethernet data frame.

[0012] Preferably, when the virtualized Ethernet network card software sets the MAC and IP, it will synchronize the relevant configuration information to the virtualized switch software, and the virtualized MAC switch software will maintain the MAC and IP information tables of all local terminals.

[0013] Preferably, the virtualized MAC switch software mainly maintains the virtual MAC address and virtual IP address information configured by all local virtualized Ethernet network card software in the form of a structure table. When performing virtualized MAC communication within the same multi-core processor platform, the local virtualized MAC switch directly completes the information matching and Ethernet data frame forwarding process. Otherwise, the Ethernet data is placed in the circular buffer and waits for the Ethernet bridging FC driver software to schedule it.

[0014] Preferably, when the Ethernet bridging FC driver software performs routing address mapping, it converts the Ethernet route into a route relationship based on the MsgID used by the FC network according to the corresponding relationship of the virtual MAC address.

[0015] Preferably, when the Ethernet bridging FC driver software establishes a route, it performs the following steps:

[0016] First, each Ethernet bridging FC driver software establishes an ARP list to represent the corresponding relationship between the IP address and the MAC address.

[0017] When device A wants to send data to device B, it first checks whether there is a MAC address corresponding to the IP address of device B in the ARP list. If there is, it sends directly. If not, it sends an ARP data packet to all devices in the network. The data packet includes: the IP address of A, the MAC address of A, and the IP address of B.

[0018] When a device in the network receives the ARP data packet, it first checks whether the IP address in the data packet is its own IP address. If not, it does not reply to the query frame, but parses the relevant routing information of A from the frame and writes it into the ARP table of this device to complete the routing establishment from this device to A; if the IP address in the ARP data packet is its own, it extracts the IP and MAC addresses of A from the data packet and writes them into the ARP list of this device, and then writes its own MAC address into the ARP response packet and replies to device A.

[0019] After device A receives the ARP response packet, it writes the IP and MAC addresses of device B into the ARP list. Thus, the routing establishment process from device A to device B is completed, and the entire network can complete the establishment of the mesh routing table for all network nodes according to this process.

[0020] Preferably, when the Ethernet bridge FC driver software performs data forwarding, the sending process will query the ARP table to extract key routing information and then perform FC frame format encapsulation, and the receiving process will parse and verify the FC frame format.

[0021] The beneficial effects of the present invention are as follows:

[0022] The present invention completes the Ethernet bridge FC protocol stack, frame encapsulation, routing establishment process and data forwarding communication through software, realizing the combination of the Ethernet protocol stack and the avionics system FC backbone network. Ethernet is currently widely used, with relatively low cost, good compatibility and extensive technical support. The avionics system has already had many applications using the FC network as the avionics backbone network, and the system platform is extensive. The method of the present invention combines the two, which can give play to the platform advantages of the FC network and the advantages of good Ethernet compatibility and extensive technical support. This design method enriches the user's selection of avionics buses and the process of system transplantation and adaptation under the complex avionics system architecture, has a wide range of applications, and has significant market prospects and economic benefits. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 Schematic structural diagram of the protocol encapsulation and routing communication system of Ethernet bridge FC.

[0024] Figure 2 Schematic diagram of the operation process of the virtualized Ethernet network card software.

[0025] Figure 3 Schematic diagram of the operation process of synchronizing configuration information in the virtualized Ethernet network card software.

[0026] Figure 4 Schematic diagram of the operation process of the virtualized MAC switch software.

[0027] Figure 5Schematic diagram of virtualized MAC data path.

[0028] Figure 6 Schematic diagram of the operation process of Ethernet bridging FC driver software.

[0029] Figure 7 Schematic diagram of the division of Ethernet architecture.

[0030] Figure 8 Schematic diagram of the division of FC network architecture.

[0031] Figure 9 Schematic diagram of Ethernet bridging FC protocol stack.

[0032] Figure 10 Schematic diagram of FC network message frame format.

[0033] Figure 11 Schematic diagram of Ethernet bridging FC network message frame format.

[0034] Figure 12 Schematic diagram of Ethernet bridging FC routing addressing mapping.

[0035] Figure 13 Schematic diagram of the process of establishing Ethernet bridging FC routing.

[0036] Figure 14 Schematic diagram of the function of sending, receiving and parsing ARP routing frames.

[0037] Figure 15 Schematic diagram of Ethernet bridging FC data forwarding communication.

[0038] Figure 16 Schematic diagram of the communication management function in Ethernet bridging FC driver software. Detailed implementation manners

[0039] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0040] There have been many applications of using FC network as the avionics backbone network in avionics systems, and the hardware system platform is extensive. Ethernet is currently widely used, with relatively low cost, good compatibility, and extensive technical support. If the two can be combined, the platform advantages of the FC network and the advantages of good Ethernet compatibility and extensive technical support can be exerted, which is of great significance.

[0041] An Ethernet bridging FC protocol encapsulation and routing communication system shown in this embodiment has a design idea of adopting standard Ethernet programming for application access, performing Ethernet protocol processing through the protocol stack software built into the main processor CPU. The FC driver can control the transmit and receive circular buffers of the general Ethernet protocol stack on the OS side, and realize data transfer between the FC network terminal and the transmit and receive circular buffers of the Ethernet protocol stack on the main control side through the FC driver. When sending, the FC driver encapsulates the FC frame header outside the Ethernet data frame encapsulated by the main control, and when receiving, the FC driver removes the FC frame header, thus realizing Ethernet based on traditional FC infrastructure.

[0042] See Figure 1 As shown, an Ethernet bridging FC protocol encapsulation and routing communication system shown in this embodiment uses a multi-core processor platform as the main control side and an FPGA as the core protocol processing chip of the FC network terminal, and uses a PCIe interface to achieve transmission between the two. The main control side includes an Ethernet software protocol stack, virtualized Ethernet network card software, virtualized MAC switch software, Ethernet bridging FC driver software, etc., and is connected to the FC network switch through the FC network terminal.

[0043] The Ethernet software protocol stack is used to implement the complete Ethernet protocol stack processing of application data, interface with applications on the upper layer, and realize the flexible configuration and plug-and-play characteristics of Ethernet.

[0044] The virtualized Ethernet network card software maintains the virtual MAC address and virtual IP address information corresponding to each CPU path, and encapsulates and parses the Ethernet data frame according to the virtual MAC address and virtual IP address.

[0045] In traditional Ethernet, the MAC address corresponds to a specific hardware network card. When Ethernet bridges FC, there is no Ethernet network card, so virtualized Ethernet network card software is needed to virtualize the MAC terminal.

[0046] The virtualized Ethernet network card software mainly includes functions such as virtualized MAC terminal initialization, setting / getting network card MAC function, setting / getting network card IP function, terminal data communication function, configuration and data interaction with the virtualized MAC switch software, etc. Its main operation design process is as Figure 2 shown.

[0047] During the process of the virtualized Ethernet network card software setting / obtaining the network card MAC function and setting / obtaining the network card IP function, the set MAC or IP value is passed in through the interface input parameters and set to the local MAC and IP structures. The MAC and IP values can also be obtained through the interface return parameters for the encapsulation of Ethernet data frames. In addition, when the terminal sets the MAC and IP, it will synchronize the relevant configuration information to the virtualized switch software, and the virtualized MAC switch software maintains the MAC and IP information tables of all local terminals. The operation design process of its configuration update and synchronization information is as Figure 3 shown.

[0048] The virtualized MAC switch software mainly maintains the virtual MAC address and virtual IP address information configured by all local virtualized Ethernet network card software in the form of a structure table. The purpose of this design is that when communicating between virtualized MACs within the same multi-core processor platform, the local virtualized MAC switch directly completes the information matching and Ethernet data frame forwarding process. Otherwise, the Ethernet data is placed in the circular buffer waiting for the Ethernet bridge FC driver software to schedule.

[0049] The virtualized MAC switch software mainly includes functions such as internal switch initialization, maintenance of MAC and IP information tables of all local terminals, data flow transceiver processing, and interaction of information and data with other software. The main operation design process is as Figure 4 shown.

[0050] As Figure 5 shown, after two virtualized Ethernet network card software in the multi-core processor platform 1 complete the initialization of the virtualized MAC terminal, the IPs are set to 192.168.1.1 and 192.168.1.2. If data communication is required between these two nodes, the virtualized MAC switch software matches the MAC and IP information tables of the local virtualized terminals, finds that both terminals are local, and directly completes the internal exchange internally. The data flow is the green exchange path in the figure.

[0051] If data communication is required between the multi-core processor platform 1 and the multi-core processor platform 2, such as the communication between two virtualized MAC terminals with IPs of 192.168.1.1 and 192.168.1.6, the virtualized MAC switch software matches the MAC and IP information tables of the local virtualized terminals, finds that these two terminals belong to different processor platforms, then the data continues to be passed downwards, and the Ethernet bridge FC driver software completes the data communication. The relevant routing design and routing establishment process will be described in detail below. The data flow between different multi-core processor platforms is the orange exchange path in the figure.

[0052] The Ethernet bridging FC driver software is used to complete the routing addressing mapping between Ethernet and FC and establish the FC routing. It adds the Ethernet data frame on the circular buffer area with an FC frame header and communicates externally through the FC network terminal. At the same time, it removes the FC frame header from the data obtained from the FC network terminal and distributes it to the virtual Ethernet network card software on each core through the virtualized MAC switch software.

[0053] The Ethernet bridging FC driver software mainly includes initialization function, configuration loading function, ARP routing frame sending, receiving and parsing function, network management function, communication management function, network time synchronization function, terminal BIT management function, etc. Its main operation design process is as Figure 6 shown.

[0054] Through the protocol encapsulation and routing communication system of Ethernet bridging FC, it mainly realizes the Ethernet bridging FC protocol stack and frame encapsulation, routing addressing mapping design and routing establishment, data forwarding communication operation, and finally realizes the data communication interaction of application software on each CPU processor.

[0055] ● Ethernet bridging FC protocol stack and frame encapsulation

[0056] The Ethernet protocol is usually divided into five layers, and the structure division is as Figure 7 shown.

[0057] The application layer mainly provides corresponding services for applications and includes corresponding protocols such as FTP protocol, TFTP protocol, HTTP protocol, SNMP protocol, etc.

[0058] The transport layer is mainly responsible for providing services for the communication between two hosts. The transport layer mainly uses the following two protocols. Transmission Control Protocol TCP (Transmission Control Protocol): Connection-oriented, the unit of data transmission is a segment, and it can provide reliable delivery. User Datagram Protocol UDP (User Datagram Protocol): Connectionless, the unit of data transmission is a user datagram, and it does not guarantee reliable delivery.

[0059] The network layer is responsible for providing communication services for different hosts on the packet-switching network, encapsulating and grouping the data according to the IP protocol for transmission, and selecting an appropriate route to find the destination host through the route in the network. The included protocols are IP, ARP, etc.

[0060] The data link layer uses a dedicated link layer protocol to frame the data submitted by the network layer into data packets and transmit them.

[0061] The physical layer transmits data on the physical layer. Its task is to transparently transmit the bit stream.

[0062] The FC protocol is usually divided into five layers, and its architecture is divided as Figure 8 shown below.

[0063] The FC-4 layer mainly formulates protocols related to the FC network, such as protocol standards like FC-AE, FC-AV, and FC-SW. The FC network used in the avionics system mainly uses the FC-AE-ASM protocol.

[0064] The FC-3 layer mainly defines common services, such as data encryption and compression services.

[0065] The FC-2 layer is the network layer, which is the core of the FC network and defines frame formats, primitives, credit management, flow control, quality of service, etc.

[0066] The FC-1 layer, the data link layer, defines encoding and decoding signals, etc.

[0067] The FC-0 layer, the physical layer, defines standards for connecting physical media, cables, encoding, and decoding, etc.

[0068] The protocol encapsulation and routing communication system for Ethernet bridging FC, based on the existing capabilities of the end-system hardware platform, and on the characteristics of the Ethernet protocol and the FC protocol, proposes an implementation solution. Its design idea is to use the Ethernet software protocol stack controlled by the end-system master to implement application data access and protocol stack packaging based on Socket or other forms, and store the packaged data in the buffer space accessible by the Ethernet bridging FC driver software; start receiving data submitted by the FC network terminal through a standard Socket or other form of interface, and after protocol stack processing, provide the payload to the application; at the same time, the FC network terminal and the logical state maintain the functions in the currently verified state, thus realizing Ethernet based on the traditional FC infrastructure. Thus, Ethernet based on the traditional FC infrastructure is realized. The network architecture is as Figure 9 shown below.

[0069] In the current use of the avionics FC network, the FC network data communication uses the FC-AE-ASM protocol, and the network message frame format is as Figure 10 shown below.

[0070] In the Ethernet bridging FC solution, the frame formation process first virtualizes the Ethernet network card software to complete the encapsulation of the Ethernet data frame, and then the Ethernet bridging FC driver software adds the FC frame header on the basis of the Ethernet data frame, and designs the network message frame format as Figure 11 shown below.

[0071] ● Routing addressing mapping and route establishment

[0072] The routing addressing mapping and route establishment are mainly implemented by the ARP route frame sending and receiving parsing functions in the Ethernet bridging FC driver software.

[0073] 1) Routing addressing mapping

[0074] The flexibility of the Ethernet bridging FC network is reflected in the dynamic self-learning routing mechanism of Ethernet. The FC network terminal needs to support the dynamic network routing design on the Ethernet side, which is the key to realizing the dynamic reconstruction and rapid migration of the network architecture. In the current application of the FC network in the avionics system, the common routing method is to route based on the source and destination logical port numbers, and the FC-AE-ASM protocol is adopted. The FC network terminal is based on the configuration of sending and receiving messages, and the message number MsgID is a relatively key element. The message number is generally unique in the whole network. For ordinary unicast messages, the source and destination of the message number MsgID are unique in the whole network. After the FC network terminal sends a message, according to the configuration attributes of MsgID, the FC network terminal encapsulates the sending data into the FC frame format at the bottom layer, and encapsulates the key attributes such as the source and destination of the message into the FC frame.

[0075] The Ethernet bridging FC network needs to design a routing conversion function. In the network, the virtual Ethernet network card software needs to overall plan, configure and maintain the virtual MAC address situation of all nodes in the network. In the Ethernet bridging FC driver software, the routing conversion process is implemented, as Figure 12 shown.

[0076] As Figure 12 shown, when sending a message through Ethernet, the network routing is based on the source IP, destination IP, source MAC address and destination MAC address. The bottom layer of the Ethernet bridging FC network is the FC network, so routing conversion is required. According to the virtual MAC terminal and FC network configuration information, the Ethernet routing can be converted into a routing relationship based on the MsgID used by the FC network according to the corresponding relationship of the virtual MAC address, so that data can be sent through the FC network. The process of receiving network data is similar. For the message transmitted by the FC network, after completing the FC reception, according to the attributes of the received message MsgID, its source MAC address and destination MAC address can be determined, so as to determine the final destination of the message. For the routing construction of the main control end Ethernet system, the standard ARP protocol is adopted to implement. The ARP sender uses the broadcast mechanism during network transmission. The Ethernet bridging FC system constructs an FC broadcast message for the route establishment of each device end system. The FC driver obtains the packet in the Ethernet MAC sending buffer and extracts the Ethernet address information therein. When it is a broadcast address, it maps it to the FC broadcast message for sending.

[0077] 2) Design of the route establishment process

[0078] During the master control Ethernet transmission process, the application inputs data, the peer UDP, and IP into the Ethernet transmission interface, and packs them into data to be sent to the other party through the protocol stack. To do this, the IP address of the other party needs to be known. However, just having the IP address is not enough. The IP data packet must be encapsulated into a complete frame to be sent through the data link layer. The data frame must contain the destination MAC address. The target IP is looked up in the local routing table entries to obtain the destination MAC address. If there is no table entry, device A of this equipment uses the ARP protocol to obtain the destination MAC address through the destination IP address. The ARP protocol request for the destination MAC address message uses the broadcast mode. The peer device B receives the ARP request protocol, extracts the target IP and compares it with itself successfully, and then packs its own IP and MAC addresses and sends a unicast ARP response message for reply. Device A receives the ARP response message, extracts the IP and MAC addresses, and adds a routing table entry. The process of establishing the Ethernet bridging FC routing is designed as follows. As Figure 13 shown.

[0079] In the Ethernet bridging FC driver software, the ARP routing frame sending, receiving, and parsing function completes the operations related to routing addressing mapping and routing establishment process. The design and implementation method of this function is as Figure 14 shown.

[0080] The working process of establishing the Ethernet bridging FC routing is as follows:

[0081] First, each Ethernet bridging FC driver software will establish an ARP list by itself to represent the correspondence between the IP address and the MAC address.

[0082] When device A (IP: 192.168.1.1) wants to send data to device B (IP: 192.168.1.2), it first checks whether there is a MAC address corresponding to the IP address of B in the ARP list. If there is, it sends directly; if not, it sends an ARP data packet to all hosts in the network. The data packet contains: the IP address of A, the MAC address of A, and the IP address of B.

[0083] When the hosts in the network receive the ARP data packet, they first check whether the IP address in the data packet is their own IP address. If not, they do not reply to the query frame, but they will parse the relevant routing information of A from the frame and write it into the ARP table of this device to complete the routing establishment from this device to A. If the IP address in the ARP data packet is its own, it takes out the IP and MAC addresses of A from the data packet and writes them into the ARP list of this device, and then writes its own MAC address into the ARP response packet and replies to A that it is the MAC address it is looking for.

[0084] After A receives the ARP response packet, it writes B's IP and MAC address into the ARP list. At this point, the route establishment process from device A to device B is completed. The entire network can complete the establishment of a mesh routing table for all nodes in the network based on this process.

[0085] ●Data forwarding communication operation

[0086] Data forwarding communication operations are mainly implemented by the communication management function in the Ethernet bridge FC driver software.

[0087] The nodes in the network can complete the establishment of the whole network route through the routing design and routing establishment process. When the ARP route is established, the ARP route is as follows: Figure 15 shown.

[0088] In the Ethernet bridge FC driver software, the communication management function completes the data forwarding communication operation according to the maintained ARP route. The sending process will query the ARP table to extract key routing information, and then perform Ethernet frame format encapsulation and FC frame format encapsulation, packet assembly and other operations. The receiving process will parse and verify the relevant FC frame format and Ethernet frame format, and finally complete the entire data forwarding communication operation. The design and implementation of this function are as follows: Figure 16 shown.

[0089] When device A (IP: 192.168.1.1) wants to send data to device B (IP: 192.168.1.2), it sends data through the Socket programming interface, fills the UDP and IP addresses of the other end into the interface, obtains the local device IP and MAC through the protocol stack software processing, queries the routing table through the destination IP to obtain the MAC address of the destination device, completes the Ethernet UDP / IP / MAC message encapsulation of the entire data message, and writes it to the pre-defined MAC ring buffer to wait for scheduling and sending. According to the virtualized MAC terminal and FC network configuration information, the Ethernet route can be converted into a routing relationship based on the MsgID used by the FC network based on the correspondence between the virtual MAC addresses, determines that the message used is MsgID, and inputs the message number, the MAC message address and length stored in the MAC ring buffer by calling the FC driver API, executes the transfer from the master to the FC network terminal, the source port of the message is 0x10001, the destination port is 0x10002, and then completes the frame format packaging and encapsulation in sequence, and finally completes the data transmission through the FC network. The step of parsing data at the receiving end is the reverse process of the sending process. At this point, the Ethernet bridge FC data forwarding communication process is completed.

[0090] The present invention realizes the deployment of multiple independent and concurrent application execution environments on a multi-core processor platform. The virtualized MAC switch software can achieve application data communication between different cores on the same physical CPU without accessing an external link. It realizes the aggregation of the transmitted data of different cores to the Ethernet bridging FC driver software, communicates externally through the FC network terminal, and at the same time distributes the data obtained by the Ethernet bridging FC driver software from the FC network terminal to the applications on each core through the virtual switch.

[0091] It can be understood that for those of ordinary skill in the art, equivalent substitutions or changes can be made according to the technical solution of the present invention and its inventive concept, and all such changes or substitutions should fall within the protection scope of the appended claims of the present invention.

Claims

1. An Ethernet bridging FC protocol encapsulation and routing communication system, including a master control end and an FC network terminal, the master control end is connected to the FC network through the FC network terminal, characterized in that The master control end includes an Ethernet software protocol stack, a virtualized Ethernet network card software, a virtualized MAC switch software, and an Ethernet bridging FC driver software; The Ethernet software protocol stack is used to implement the processing of the Ethernet protocol stack for application data; The virtualized Ethernet network card software maintains the virtual MAC address and virtual IP address information corresponding to each CPU path, and encapsulates and parses Ethernet data frames according to the virtual MAC address and virtual IP address; The virtualized MAC switch software puts the Ethernet data that needs to perform FC communication into a circular buffer and waits for the Ethernet bridging FC driver software to schedule; The Ethernet bridging FC driver software is used to complete the routing addressing mapping between Ethernet and FC and establish an FC route. After adding an FC frame header to the Ethernet data frame on the circular buffer, it communicates externally through the FC network terminal. At the same time, the data obtained from the FC network terminal is distributed to the virtualized Ethernet network card software on each core after removing the FC frame header through the virtualized MAC switch software.

2. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 1, characterized in that In the virtualized Ethernet network card software, the set MAC or IP value is passed in through the interface input parameter and set to the local MAC and IP structures. The MAC and IP values are obtained through the interface return parameter for the encapsulation of Ethernet data frames.

3. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 1, wherein When setting the MAC and IP in the virtualized Ethernet network card software, it will synchronize the relevant configuration information to the virtualized switch software, and the virtualized MAC switch software will maintain the MAC and IP information tables of all local terminals.

4. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 3, characterized in that The virtualized MAC switch software mainly maintains the virtual MAC address and virtual IP address information configured by all local virtualized Ethernet network card software in the form of a structure table. When performing virtualized MAC communication within the same multi-core processor platform, the local virtualized MAC switch directly completes the information matching and Ethernet data frame forwarding process. Otherwise, the Ethernet data is put into a circular buffer and waits for the Ethernet bridging FC driver software to schedule.

5. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 1, wherein When performing routing addressing mapping, the Ethernet bridging FC driver software converts the Ethernet route into a route relationship based on the MsgID used by the FC network according to the corresponding relationship of the virtual MAC address.

6. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 1, characterized in that When establishing a route, the Ethernet bridging FC driver software performs the following steps: First, each Ethernet bridging FC driver software establishes an ARP list to represent the corresponding relationship between the IP address and the MAC address; When device A wants to send data to device B, it first checks whether there is a MAC address corresponding to the IP address of device B in the ARP list. If there is, it sends directly. If not, it sends an ARP data packet to all devices in the network. The data packet includes: the IP address of A, the MAC address of A, and the IP address of B; When a device in the network receives the ARP packet, it first checks whether the IP address in the packet is its own IP address. If not, it will not reply to the inquiry frame, but will parse the relevant routing information of A from the frame and write it into the ARP table of the device to complete the route establishment from the device to A. If the IP address in the ARP packet is its own IP, it will take out A's IP and MAC address from the packet and write them into the ARP table of the device, and then write its own MAC address into the ARP response packet and reply to device A. After device A receives the ARP response packet, it writes the IP and MAC addresses of device B into the ARP list. At this point, the route establishment process from device A to device B is completed. The entire network can complete the establishment of a mesh routing table for all nodes in the entire network based on this process.

7. The protocol encapsulation and routing communication system for Ethernet bridging FC according to claim 6, characterized in that When the Ethernet bridge FC driver software is forwarding data, the sending process will query the ARP table to extract key routing information, and then encapsulate it in the FC frame format. The receiving process will parse and verify the FC frame format.

Images