WO2016107122A1

WO2016107122A1 - Method and device for converting between rapidio packet and ethernet packet

Info

Publication number: WO2016107122A1
Application number: PCT/CN2015/082978
Authority: WO
Inventors: 汪立林; 杜超; 王仰锋; 赵幸; 刘凯
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-12-18
Filing date: 2015-06-30
Publication date: 2016-07-07
Also published as: CN105791214A; CN105791214B

Abstract

A method and device for converting between a RapidIO packet and an Ethernet packet. The converting method comprises: a packet converting device receives a RapidIO device serial number and a non-fragment RapidIO packet sent by a RapidIO device; and form a control information header by using the RapidIO device serial number and a service data header in the RapidIO packet, find corresponding routing address information from a first mapping between information in the control information header and the routing address information, and add the found information into an Ethernet header to generate an Ethernet packet. Correspondingly, after a non-fragment Ethernet packet is received, a control information header can be extracted from a payload, and a corresponding RapidIO device address space is found according to a second mapping to generate a non-fragment RapidIO packet.

Description

Method and device for converting between RapidIO messages and Ethernet messages

Technical field

This document relates to the field of communication technologies, and in particular, to a method for converting a RapidIO message and an Ethernet message in a communication system and a corresponding message conversion device.

Background technique

RapidIO (no Chinese terminology) is a high-performance, low pin count, packet-switched interconnect architecture pioneered by companies such as Motorola and Mercury. It is designed to meet the needs of future high-performance embedded systems. An open interconnect technology standard. The RapidIO interconnect architecture is a high-performance interconnect technology based on packet switching. It is mainly used for internal interconnection of systems, supporting chip-to-chip and board-to-board communication, and has achieved performance levels of 1 Gbps to 60 Gbps.

Ethernet (Ethernet) is a LAN networking technology. The IEEE 802.3 standard gives the technical standard for Ethernet, which passes the payload to the destination correctly with enough header control information, making it the most popular LAN technology in the current application.

In the communication system, the internal chip-to-chip, single-board-to-board data communication between the system is often transmitted through the RapidIO interconnect architecture in the form of RapidIO packets; the systems often communicate with each other through Ethernet. . Figure 1 is an architectural diagram of a RapidIO device interconnected with an Ethernet device through an Ethernet interface. Figure 2 is an architectural diagram of a RapidIO device interconnected with a RapidIO device through an Ethernet interface. The multiple RapidIO devices of the source system or the destination system in Figure 1 and Figure 2 are directly or indirectly connected to the RapidIO switching device. Between the RapidIO switching device and the Ethernet device interface, the packet conversion device completes the RapidIO packet and Ethernet. Conversion between messages. The destination system or source system in FIG. 1 is an Ethernet device, and the destination system or source system structure of FIG. 2 also includes a plurality of RapidIO devices, a RapidIO switching device, an Ethernet device interface, and a packet conversion device. In the exemplary system architecture shown in Figures 1 and 2, there is a need for a RapidIO device (such as a chip or a single board) in the system to communicate with other system RapidIO devices (such as chips or boards) or Ethernet devices. This requires converting the internal RapidIO message data into Ethernet message data and interconnecting through the Ethernet interface.

The traditional message conversion scheme is usually completed by the CPU, and packet conversion is implemented by unpacking, grouping, and the like. The traditional scheme has many shortcomings, such as limited CPU architecture. For high-speed and large-capacity data of interfaces such as RapidIO and 10GE, the CPU has very limited data processing capability. In particular, in the system architecture shown in FIG. 1 and FIG. 2, the RapidIO switching device is interconnected with multiple single-board devices or chip devices, and large-capacity data needs to be processed, and CPU processing capability will restrict communication performance between systems; Sending and receiving messages are completed by means of interrupts, and the process of data processing waiting for interrupts makes the processing delay very large.

How to design a conversion method and corresponding equipment between RapidIO packets and Ethernet packets for implementing programmable logic devices, to avoid CPU processing capability and to control communication performance between systems, and to reduce data delay caused by CPU processing. It is an urgent problem to be solved.

Summary of the invention

The embodiment of the invention provides a method for converting a RapidIO packet to an Ethernet packet, including:

Receiving the RapidIO device number and the non-fragmented RapidIO packet sent by the RapidIO device;

And the service data header of the RapidIO device number and the RapidIO packet is formed into a control information header, and the first mapping relationship between the information and the routing address information in the configured control information header is used to find the corresponding information of the control information header. Routing address information;

Adding the found routing address information to the Ethernet header, and generating an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO packet.

Optionally,

The information in the control information header includes at least one of a destination system configuration information and a source system configuration information, or includes at least one of a RapidIO device number and destination system configuration information and source system configuration information;

The routing address information includes a destination MAC address, or at least one of a destination MAC address and a destination IP address and a VLAN value.

The embodiment of the invention further provides a method for converting an Ethernet packet to a RapidIO packet, including:

Receiving a non-sharded Ethernet packet, extracting the payload from the Ethernet packet, including RapidIO device number and control information header of the service data header;

Searching for the RapidIO device address space corresponding to the service data header from the second mapping relationship between the configured service data header and the RapidIO device address space;

Adding the discovered RapidIO device address space to the RapidIO header, and generating a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.

Optionally,

In the second mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device. A RapidIO device address space is divided. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

The embodiment of the invention further provides a method for converting a RapidIO packet to an Ethernet packet, including:

Receiving the RapidIO device number and the RapidIO first fragment packet sent by the RapidIO device;

And the service data header of the RapidIO device number and the RapidIO first fragment packet is formed into a control information header, and the corresponding information of the control information header is found in the first mapping relationship between the information and the routing address information in the configured control information header. Routing address information and adding it to the Ethernet header;

Generating an Ethernet first fragmented packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO first fragmented packet.

Optionally,

Receiving the RapidIO device number and the RapidIO subsequent fragment packet sent by the RapidIO device;

The service data header corresponding to the RapidIO device address space in the RapidIO subsequent fragmented packet is found in the second mapping relationship between the configured service data header and the RapidIO device address space.

The service data header and the RapidIO device number are combined into a control information header, and the routing address information corresponding to the control information header is found in the first mapping relationship;

Adding the found routing address information to the Ethernet header, and generating an Ethernet subsequent fragmentation packet according to the Ethernet header and the RapidIO data in the RapidIO subsequent fragmented packet.

Optionally,

When the Ethernet packet is an IP packet, the method further includes:

After the first packet of the RapidIO first packet and the subsequent fragment of the RapidIO packet are converted, the control information header is searched for from the third mapping relationship between the configured control information header and the IP packet identifier. The IP packet is identified and added to the Ethernet header.

Optionally,

The third mapping relationship is configured to: determine a RapidIO device number of each RapidIO device in the communication system, and use destination system configuration information, source system configuration information, and data type information, such that the RapidIO device number, destination system configuration information, The number of control information headers obtained by combining the source system configuration information and the data type is smaller than the number of optional IP identifiers in the IP packet and greater than the number of IP packets that can be transmitted by the communication system in a period in which the IP identifier cannot be repeated; Then, a one-to-one mapping relationship between the control information header and the IP identifier is established.

After receiving the Ethernet first fragment packet, perform the following conversion processing:

Extracting, from the payload of the Ethernet first fragment packet, a control information header including a RapidIO device number and a service data header;

Searching for the RapidIO device address space corresponding to the service data header and adding it to the RapidIO header in the second mapping relationship between the configured service data header and the RapidIO device address space.

And generating a RapidIO first fragment packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.

Optionally,

After receiving the subsequent fragments of the Ethernet packet, perform the following conversion processing:

Extracting routing address information or an IP packet identifier from a header of the subsequent fragmentation packet of the Ethernet;

Determining, according to the first mapping relationship between the information in the control information header and the routing address information, the control information header corresponding to the routing address information; or, in the third mapping relationship between the configured control information header and the IP packet identifier, Finding a control information header corresponding to the IP packet identifier; the control information header includes a RapidIO device number and a service data header;

Searching for the RapidIO device address space corresponding to the service data header from the second mapping relationship associated with the configured RapidIO device number, and adding the address to the RapidIO header;

The payload of the subsequent packet of the Ethernet is used as the RapidIO data, and the RapidIO subsequent fragment packet is generated together with the RapidIO header.

Optionally,

The routing address information includes a destination MAC address, or includes a destination MAC address and destination. At least one of an IP address and a VLAN value.

Optionally,

The embodiment of the invention further provides a packet conversion device for a RapidIO packet to an Ethernet packet, including:

The RapidIO packet parsing device is configured to receive the RapidIO device number and the non-fragmented RapidIO packet, and extract the service data header and the RapidIO data in the RapidIO packet;

a control information header generating device, configured to form the RapidIO device number and the service data header into a control information header;

The routing address mapping device is configured to: find the routing address information corresponding to the control information header from the first mapping relationship between the information and the routing address information in the configured control information header;

The Ethernet packet generating device is configured to add the routing address information to an Ethernet header, and generate an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data.

Optionally,

The message conversion device is implemented by a programmable logic device.

Optionally,

In the first mapping relationship configured in the routing address mapping device, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. And at least one of source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.

The embodiment of the invention further provides a packet conversion device for an Ethernet packet to a RapidIO packet, including:

An Ethernet packet parsing apparatus is configured to receive a non-fragmented Ethernet packet, and extract, from the payload of the Ethernet packet, a control information header and a RapidIO data including a RapidIO device number and a service data header;

The address space mapping device is configured to find a RapidIO device address space corresponding to the service data header from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space;

The RapidIO packet generating device is configured to add the discovered RapidIO device address space to the RapidIO header, and generate a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data.

Optionally,

The message conversion device is implemented by a programmable logic device.

Optionally,

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device, and different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

The RapidIO packet parsing device is configured to receive the RapidIO device number and the RapidIO first fragment packet, extract the service data header and the RapidIO data in the RapidIO first fragment packet, and notify the Ethernet packet of the received packet type. Text generation device;

a control information header generating device, configured to form the control information header by the RapidIO device number and the service data header extracted by the RapidIO packet parsing device;

The routing address mapping device is configured to: according to the control information header formed by the control information header generating device, find the corresponding routing address information from the first mapping relationship between the information and the routing address information in the configured control information header;

The Ethernet packet generating device is configured to add, when the received packet type is a RapidIO first fragment packet, the routing address information found by the routing address mapping device to the Ethernet header, according to the Ethernet header. The control information header and the RapidIO data generate an Ethernet first fragment message.

Optionally,

The message conversion device further includes an address space mapping device, wherein:

The RapidIO packet parsing apparatus is further configured to receive the subsequent fragment of the RapidIO, extract the RapidIO device address space and the RapidIO data in the subsequent fragmented fragmentation message, and notify the Ethernet packet generating apparatus of the received packet type. ;

The address space mapping device is configured to find a service data header corresponding to the address space of the RapidIO device from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space;

The control information header generating device is further configured to form, by the RapidIO device number and the service data header searched by the address space mapping device, a control information header;

The Ethernet packet generating device is further configured to: when the received packet type is a RapidIO subsequent fragment packet, add the routing address information found by the routing address mapping device to the Ethernet header, according to the The Ethernet header and RapidIO data generate Ethernet subsequent fragmented packets.

Optionally,

Service data associated with the RapidIO device number configured in the address space mapping device In the second mapping relationship between the header and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to a RapidIO device address space that is divided in the maximum address space of the RapidIO device. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

Optionally,

The packet conversion device further includes:

The IP identifier mapping device is configured to search for the IP packet corresponding to the control information header from the third mapping relationship between the configured control information header and the IP packet identifier according to the control information header formed by the control information header generating device. Identification

The Ethernet packet generating device is further configured to add the IP packet identifier that is found by the IP identifier mapping device to the Ethernet when the received packet type is a RapidIO first fragment packet and a RapidIO subsequent fragment packet. In the net header.

Optionally,

The message conversion device is implemented by a programmable logic device.

Optionally,

The Ethernet packet parsing device is configured to: after receiving the Ethernet first fragment packet, extract the control information header and the RapidIO data from the payload, and notify the RapidIO packet generating device of the received packet type, where the control The information header includes the RapidIO device number and the service data header;

An address space mapping device configured to receive a control letter according to the Ethernet packet parsing device The RapidIO device number and the service data header in the message header, and the RapidIO device address space corresponding to the service data header is found in the second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space. ;as well as

The RapidIO packet generating device is configured to add, when the received packet type is an Ethernet first fragment packet, the RapidIO device address space found by the address space mapping device to the RapidIO header, according to the RapidIO header, The service data header and the RapidIO data generate non-fragmented RapidIO messages.

Optionally,

The message conversion device further includes a routing address mapping device and/or an IP identification mapping device, wherein:

The Ethernet packet parsing device is further configured to parse the header and the payload after receiving the subsequent fragmentation packet of the Ethernet, and extract the routing address information or the IP packet identifier from the header.

The routing address mapping device is configured to search for a first mapping relationship between the information in the configured control information header and the routing address information according to the routing address information extracted by the Ethernet packet parsing device to determine a corresponding control information header;

The IP identifier mapping device is configured to search for a corresponding control information header from a third mapping relationship between the configured control information header and the IP packet identifier according to the IP packet identifier extracted by the Ethernet packet parsing device;

The address space mapping device is further configured to: according to the RapidIO device number and the service data header in the control information header obtained by the routing address mapping device or the IP identifier mapping device, the service data header associated with the configured RapidIO device number In the second mapping relationship with the address space of the RapidIO device, the RapidIO device address space corresponding to the service data header is found;

And the RapidIO packet generating device is further configured to: when the received packet type is an Ethernet subsequent fragment packet, add the RapidIO device address space found by the address space mapping device to the RapidIO header, and the The payload of the subsequent fragmented packet of the Ethernet is used as the RapidIO data, and the RapidIO subsequent fragmented packet is generated together with the RapidIO header.

Optionally,

The control informationgram in the first mapping relationship configured in the routing address mapping device The header information includes at least one of destination system configuration information and source system configuration information, or at least one of a RapidIO device number and destination system configuration information and source system configuration information; the routing address information includes a destination MAC address, Or include at least one of a destination MAC address and a destination IP address and a VLAN value.

Optionally,

The foregoing solution provides a method for converting between a RapidIO packet and an Ethernet packet, and implements data conversion between the RapidIO packet and the Ethernet packet by means of mapping, and is therefore applicable to a programmable logic device. Utilizing the high-speed processing capability of the programmable logic device, a large number of RapidIO messages and Ethernet packets can be converted between system devices with a small delay, reducing the data delay caused by CPU processing and maximizing the use of data links. Bandwidth resources.

BRIEF abstract

Figure 1 is an architectural diagram of a RapidIO device interconnected with an Ethernet device through an Ethernet interface.

Figure 2 is an architectural diagram of a RapidIO device interconnected with a RapidIO device through an Ethernet interface.

FIG. 3 is a schematic diagram of extracting a data service header from a RapidIO packet and forming a control information header according to Embodiment 1 of the present invention.

FIG. 4 is a flowchart of a message conversion method according to an embodiment of the present invention.

Figure 5, Figure 6, and Figure 7 are diagrams for mapping a RapidIO packet to a MAC packet, an IPV4 packet, and an IPV6 packet, respectively.

FIG. 8 is a schematic structural diagram of a message conversion device according to an embodiment of the present invention.

FIG. 9 is a flowchart of a packet conversion method according to Embodiment 2 of the present invention.

FIG. 10 is a schematic structural diagram of a message conversion device according to Embodiment 2 of the present invention.

FIG. 11 is a schematic diagram of a service data header obtained by the RapidIO device address space mapping according to the third embodiment of the present invention, and forming a control information message.

FIG. 12 and FIG. 13 are flowcharts respectively showing a method for converting a message of a first slice and a subsequent slice according to the third embodiment of the present invention.

FIG. 14 is a schematic structural diagram of a packet conversion device according to Embodiment 3 of the present invention.

FIG. 15 and FIG. 16 are flowcharts respectively showing a packet conversion method of a first slice and a subsequent slice according to an embodiment of the present invention.

FIG. 17 is a schematic structural diagram of a message conversion device according to Embodiment 4 of the present invention.

Embodiments of the invention

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Embodiment 1

Based on the consideration of transfer efficiency, RapidIO packets usually have fragmented packets delivered during the delivery process, and different fragments are transmitted alternately.

This embodiment relates to the conversion of non-fragmented RapidIO messages to non-fragmented Ethernet messages.

The structure of the non-fragmented RapidIO packet can be seen in Figure 3, including the RapidIO header and payload. The payload part contains a service data header in the position of the front field of the RapidIO data. The service data header carries the destination system configuration information (including But not limited to device information, subsystem information, status information, etc. of the destination system), source system configuration information (including but not limited to device information of the destination system, subsystem information, status information, etc.) and data type information (including but not limited to Message type, message number, etc.). The RapidIO device sends the RapidIO device number when sending RapidIO packets. The RapidIO device can identify the RapidIO device that sends RapidIO packets.

The method for converting a RapidIO packet to an Ethernet packet in this embodiment is as shown in FIG. 4, and includes:

Step 110: Receive a RapidIO device number and a non-fragmented RapidIO packet sent by the RapidIO device.

Optionally, the service data header and the RapidIO data in the RapidIO packet are also extracted in this step.

In step 120, the RapidIO device number and the service data header in the RapidIO packet are combined into a control information header, and the control information is found in the first mapping relationship between the information and the routing address information in the configured control information header. Routing address information corresponding to the header;

The control information header consisting of the RapidIO device number and the service data header is a link between the RapidIO packet and the Ethernet packet. The structure is shown in Figure 3.

If only the RapidIO packet of a RapidIO device needs to be translated, the information in the control information header in the configured first mapping relationship may not use the RapidIO device number. For example, the destination system configuration information and/or the source system configuration information and route may be used. Mapping relationship of address information. If the RapidIO packet of the plurality of RapidIO devices needs to be converted, the information in the control information header may include at least one of a RapidIO device number, a destination system configuration information, and a source system configuration information.

The routing address is used to determine the destination system for packet delivery. If the Ethernet packet is a MAC (Media Access Control) packet, the routing address information includes the destination MAC address, and may include at least one of a source MAC address and a VLAN (Virtual Local Area Network), if the Ethernet packet is an IP packet. The routing address information includes a destination IP address and a destination MAC address, and may further include at least one of a source IP address and a VLAN.

Optionally, in the first mapping relationship, the destination system configuration information and/or the source system configuration information is used as a mapping relationship between the information in the control information header or a part of the routing information, and the routing address is strongly correlated with the system configuration information. Conducive to fast indexing, speed up the lookup time of the mapping process.

The first mapping relationship is pre-configured.

Step 130: Add the found routing address information to the Ethernet header, and generate an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO packet.

The Ethernet header includes a MAC packet, an IPV4 packet, and an IPV6 packet. FIG. 5, FIG. 6, and FIG. 7 respectively show a case where a RapidIO packet is converted into these Ethernet packets.

As shown in FIG. 5, when the RapidIO packet is converted into a MAC packet, the routing control information is obtained according to the information mapping in the control information header, where at least the destination MAC address is included, and other fields in the MAC header may be filled according to the protocol. can. For example, the packet type can be padded to 0x0806, and the VLAN information is optional. The source MAC address is configured for each RapidIO device and can be obtained directly according to the configuration. For non-sharded MAC packets, the payload includes the control information header and the RapidIO data.

As shown in Figure 6, when converting a RapidIO packet to an IPV4 packet, you need to obtain the MAC header and the IPV4 header. The method of converting the MAC header according to the control information header is as follows. For the IPV4 in the non-fragmented IP packet. In the header, the destination IP address is obtained according to the control information header mapping, and other fields are filled according to the corresponding parameters of the configuration or the length of the data according to the relevant protocol, and no complicated operation is required, and details are not described herein again. The payload of the IPV4 message includes the control information header and the RapidIO data. In the figure, the VLAN information is the analog LAN information value; V/H is the version type/header length; TOS is the service type; Len is the total length of the message; ID is the message identifier; TTL is the lifetime.

As shown in Figure 7, when converting a RapidIO packet to an IPV4 packet, the MAC header and the IPV6 header are obtained, and the MAC header is obtained according to the control information header, as in the above, for the non-fragmented IP packet. In the IPV6 header, the destination IP address is obtained according to the control information header mapping. Other fields are filled according to the corresponding parameters of the configuration or the length of the data according to the relevant protocol, and no complicated operation is required, and details are not described herein. The payload of the IPV6 message includes the control information header and the RapidIO data.

Correspondingly, the embodiment further provides a packet conversion device for a RapidIO packet to an Ethernet packet, and the packet conversion device is implemented by a programmable logic device. Also shown in FIG. 8 is a RapidIO interface and an Ethernet interface connected to the packet conversion device. The packet conversion device receives the RapidIO device number and the non-fragmented RapidIO packet from the RapidIO interface, and converts the packet into an Ethernet packet. , sent to the Ethernet device interface. As shown in the figure, the message conversion device includes:

RapidIO message parsing device 10, configured to receive RapidIO device numbers and non-fragmented a RapidIO packet, which extracts a service data header and RapidIO data in the RapidIO packet;

The control information header generating device 20 is configured to form the RapidIO device number and the service data header into a control information header;

The routing address mapping device 30 is configured to find the routing address information corresponding to the control information header from the first mapping relationship between the information and the routing address information in the configured control information header;

The Ethernet packet generating device 40 is configured to add the routing address information to an Ethernet header, and generate an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data. For the method of generating three types of Ethernet packets, refer to the description in the process of this embodiment. The generated Ethernet packets are transmitted to the Ethernet device interface and sent to the RapidIO device or Ethernet device in the destination system through the network. Sent to the RapidIO device, which needs to convert Ethernet packets into RapidIO messages. If it is sent to an Ethernet device, there is no need to convert it.

Optionally,

In the first mapping relationship configured in the routing address mapping device 30, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. At least one of source system configuration information; the routing address information includes a destination MAC address, or at least one of a destination MAC address and a destination IP address and a VLAN value.

Although the RapidIO data in the figure is first transmitted to the control information header generating means 20 and then transmitted to the Ethernet message generating means 40, it may be directly transmitted to the control information header generating means 20. This embodiment of the present invention does not limit this.

Embodiment 2

This embodiment relates to the conversion of non-fragmented Ethernet messages to non-fragmented RapidIO messages.

The structure of the non-fragmented Ethernet message of this embodiment has been shown in FIGS. 5, 6, and 7. The payload of the message includes a control information header and RapidIO data, and the control information header includes a RapidIO device number and a service data header. The structure of the RapidIO message to be converted is shown in Figure 3, including the RapidIO header and payload, including the RapidIO device in the RapidIO header. Information about the address space (not shown), the RapidIO device address space indicates where the RapidIO header is stored in memory. In the RapidIO interconnect architecture, each RapidIO device is assigned a separate address space to store the packets of the RapidIO device. The payload includes the data service header and subsequent RapidIO data.

The method for converting the Ethernet packet to the RapidIO packet in this embodiment is as shown in FIG. 9, and includes:

Step 210: Receive a non-fragmented Ethernet packet, and extract a control information header including a RapidIO device number and a service data header from the payload of the Ethernet packet.

In step 220, the RapidIO device address space corresponding to the service data header is found in the second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space.

The second mapping relationship is pre-configured, and includes a mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space.

In the second mapping relationship between the service data header associated with the RapidIO device number and the address space of the RapidIO device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device and is divided. A RapidIO device address space, different service data headers corresponding to different RapidIO device address spaces. Optionally, each RapidIO device has the same address space, which is more convenient for data storage and positioning. The RapidIO device address space can be time multiplexed.

Step 230: Add the discovered RapidIO device address space to the RapidIO header, and generate a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.

In the data transmission, the RapidIO device number is parsed in step 210, and after the non-fragmented RapidIO packet is generated, the RapidIO device number and the non-fragmented RapidIO packet are transmitted to the RapidIO interface and then sent to the corresponding RapidIO device.

Correspondingly, the embodiment further provides a message conversion device for transmitting Ethernet packets to RapidIO messages, and the message conversion device is implemented by a programmable logic device. Also shown in FIG. 10 is a RapidIO interface and an Ethernet interface connected to the message conversion device, the message conversion device from the Ethernet device The interface receives non-fragmented Ethernet packets and converts them to RapidIO packets and sends them to the RapidIO interface. As shown in the figure, the message conversion device includes:

The Ethernet packet parsing device 50 is configured to receive a non-fragmented Ethernet packet, and extract, from the payload of the Ethernet packet, a control information header and a RapidIO data including a RapidIO device number and a service data header;

The address space mapping device 60 is configured to find a RapidIO device address space corresponding to the service data header from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space;

The RapidIO packet generating device 70 is configured to add the discovered RapidIO device address space to the RapidIO header, and generate a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data. As shown, the generated non-fragmented RapidIO message is transmitted to the RapidIO interface along with the RapidIO device number.

Optionally,

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device, and different service data headers correspond to different RapidIO device address spaces, and the size of each RapidIO device address space is the same.

Embodiment 3

This embodiment relates to the conversion of a fragmented RapidIO packet to a fragmented Ethernet packet.

Fragmented RapidIO packets, including RapidIO first fragmented packets and RapidIO subsequent fragmented packets. The structure of the RapidIO first fragmented packet is similar to that of the non-fragmented RapidIO packet. See Figure 3, including the RapidIO header and payload, and the payload includes the service data header. The RapidIO subsequent fragmentation message includes the RapidIO header and payload, but there is usually no service data header in the payload. Both of the RapidIO headers have information about the RapidIO device address space.

Correspondingly, the Ethernet packet in this embodiment also includes the Ethernet first fragment packet and the Ethernet subsequent. The fragmented packet is obtained by converting the first packet of the Ethernet packet to the first fragment of the RapidIO packet, and the subsequent fragmentation packet of the Ethernet is obtained by converting the subsequent fragmented packet of the RapidIO. The structure of the Ethernet first fragment packet is similar to that of the non-fragmented Ethernet packet. See Figure 5-7. In addition to the header, the payload also includes the control information header, and the Ethernet subsequent fragmented packet. There is no control information header in the payload. Through the direct conversion between the slices, the normal segmentation assembly process is not required, and the requirements for high-speed and large-capacity data processing can be adapted.

Therefore, when the RapidIO first fragment packet is converted into the Ethernet first fragment packet, the first mapping can be found according to the service data header and the RapidIO device number (sent with the packet) in the RapidIO first fragment packet. The relationship gets the corresponding routing address information. However, for RapidIO subsequent fragmented packets, which do not have a service data header, this cannot be directly converted. To this end, the first mapping relationship between the RapidIO device address space and the service data header is configured for the RapidIO device. When the RapidIO device sends the fragmented RapidIO packet, the second mapping is performed after the service data header is determined. Relationship, find the RapidIO device address space corresponding to the service data header and add it to the RapidIO header. In this way, the packet conversion device can find the corresponding service data header according to the RapidIO device address space in the subsequent fragmented packet of the RapidIO, and form the control data header by the service data header and the RapidIO device number, as shown in FIG. Then you can find the first mapping relationship to get the corresponding routing address information.

As shown in FIG. 12, the conversion of the RapidIO first fragment packet to the Ethernet first fragment packet in this embodiment includes:

Step 310: Receive a RapidIO device number and a RapidIO first fragment packet sent by the RapidIO device.

Step 320: The service data header in the RapidIO device number and the RapidIO first fragment packet is formed into a control information header, and the control information is found in the first mapping relationship between the information and the routing address information in the configured control information header. The routing address information corresponding to the header is added to the Ethernet header;

For the configuration of the first mapping relationship, refer to the first embodiment. The information in the control information header includes at least one of a destination system configuration information and a source system configuration information, or includes at least one of a RapidIO device number and a destination system configuration information and a source system configuration information; the routing address information includes a destination MAC address, Or include the destination MAC address and destination IP address and VLAN value. At least one.

Step 330: Generate an Ethernet first fragmentation packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO first fragmentation packet.

As shown in FIG. 13, the conversion of the subsequent fragmented packet of the RapidIO to the subsequent fragmented packet of the Ethernet includes:

Step 410: Receive a RapidIO device number and a RapidIO subsequent fragment packet sent by the RapidIO device.

In step 420, the service data header corresponding to the RapidIO device address space in the subsequent fragmented packet of the RapidIO is found in the second mapping relationship between the configured service data header and the RapidIO device address space.

In the second mapping relationship between the service data header associated with the RapidIO device number and the address space of the RapidIO device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device and is divided. A RapidIO device address space, different service data headers corresponding to different RapidIO device address spaces. Optionally, each RapidIO device address space is divided into the same size.

The second mapping relationship of the above RapidIO device may be configured in the following manner: determining the number M1 of the destination system configuration information used by the RapidIO device, the number M2 of source system configuration information, and the number M3 of data type information, and all data type occupied addresses. a maximum value M4 of the space, and M1·M2·M3·M4 is smaller than a maximum address space of the RapidIO device; then, in the maximum address space of the RapidIO device, the destination system configuration information, source system configuration information, and data are Each service data header obtained by combining the type information is mapped to a RapidIO device address space of size M4, thereby completing the configuration of the second mapping relationship.

Step 430, the service data header and the RapidIO device number are combined into a control information header, and the routing address information corresponding to the control information header is found in the first mapping relationship.

The first mapping relationship here is the first mapping relationship in FIG.

Step 440: Add the found routing address information to the Ethernet header, and generate an Ethernet subsequent segment according to the Ethernet header and the RapidIO data in the RapidIO subsequent fragmented packet. Piece of message.

After the subsequent fragmented packets of the RapidIO are converted to the subsequent fragments of the Ethernet, if the receiver is a RapidIO device, the control information needs to be used in the process of converting the subsequent fragments of the Ethernet packets into the subsequent fragments of the RapidIO. The header obtains the address space of the RapidIO device, but the subsequent fragmentation packet of the Ethernet does not have a control information header. However, according to the first mapping relationship between the routing address information and the information in the control information header, the recovered information may be only part of the information in the control information header. (related to the configuration of the first mapping relationship), therefore, optionally, when the RapidIO first fragment packet and the RapidIO subsequent fragment packet are converted, after the control information header is formed, the configured control information header and IP are also configured. The IP packet identifier corresponding to the control information header is found in the third mapping relationship of the packet identifier and added to the Ethernet header.

The third mapping relationship may be pre-configured in the following manner: determining the RapidIO device number of each RapidIO device in the communication system, and the destination system configuration information, source system configuration information, and data type information used, so that the RapidIO device number and destination system are obtained. The number of control information headers obtained by the combination of the configuration information, the source system configuration information, and the data type is smaller than the number of optional IP identifiers in the IP packet and greater than the IP address that the communication system can transmit during the period in which the IP identifier cannot be repeated. Number of texts; then establishing a one-to-one mapping relationship between the control information header and the IP identifier.

It should be noted that the IP packet identifier (such as the ID in the IPV4 header in Figure 6) is mainly associated with different fragments of the same Ethernet packet to distinguish it from the fragments in other packets. The numbering mode of this embodiment can be used. If the mapping of the IP packet identifier is not performed, other numbering methods can also be used. Or, in the process of transmitting an IP packet, if the transmission efficiency is not required, the IP packet identifier may not be set after the corresponding fragmentation packet is always present in the subsequent fragmentation packet of the Ethernet.

Correspondingly, the embodiment further provides a packet conversion device for a RapidIO packet to an Ethernet packet, and the packet conversion device is implemented by a programmable logic device. The packet conversion device receives the RapidIO device number and the fragmented RapidIO packet from the RapidIO interface, converts it into a fragmented Ethernet packet, and sends it to the Ethernet device interface.

The packet conversion device can convert the RapidIO first fragment packet into an Ethernet first fragment packet. You can also convert the subsequent fragmented fragments of RapidIO into Ethernet subsequent fragmented packets. As shown in FIG. 14, the packet conversion device includes:

The RapidIO packet parsing device 10' is configured to receive the RapidIO device number and the RapidIO first fragment packet, extract the service data header and the RapidIO data in the RapidIO first fragment packet, and receive the received packet type. The indication is that the fragmented packet or the non-fragmented packet is used to notify the Ethernet packet generating device; and is further configured to receive the RapidIO subsequent fragment, and extract the RapidIO device address space and the RapidIO data in the RapidIO subsequent fragmented packet. And notifying the received packet type to the Ethernet packet generating device;

The address space mapping device 40 is configured to find a service data header corresponding to the address space of the RapidIO device from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space.

The control information header generating device 20' is configured to form the service header of the RapidIO device and the service data header extracted by the RapidIO packet parsing device into a control information header; and further configured to set the RapidIO device number and the address The service data header found by the space mapping device constitutes a control information header;

The routing address mapping device 30' is configured to search for the corresponding routing address information from the first mapping relationship between the information and the routing address information in the configured control information header according to the control information header formed by the control information header generating device;

The Ethernet packet generating device 40' is configured to add, when the received packet type is a RapidIO first fragment packet, the routing address information found by the routing address mapping device to the Ethernet header, according to the Ethernet The network header, the control information header, and the RapidIO data generate an Ethernet first fragment packet; and are further configured to add the routing address information found by the routing address mapping device when the received packet type is a RapidIO subsequent fragment packet. In the Ethernet header, an Ethernet subsequent fragmented packet is generated according to the Ethernet header and the RapidIO data.

The figure also shows the flow of information when converting the RapidIO first fragment message and the RapidIO subsequent fragment message, which can be distinguished by referring to the text description.

It should be noted that, for the packet conversion device, the conversion of the fragmented and non-fragmented RapidIO to the fragmented and non-sharded Ethernet packets can be implemented at the same time, that is, the embodiment The above device can also be used to implement the functions of the corresponding device in the first embodiment.

Optionally,

In the first mapping relationship configured in the routing address mapping device 30', the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. And at least one of source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.

Optionally,

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device 40', each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

Optionally,

The packet conversion device further includes:

According to the above functional description, it can be determined that the IP identification mapping means is connected between the control information header generating means 20' and the Ethernet message generating means 40'.

Embodiment 4

This embodiment relates to the conversion of a fragmented Ethernet packet to a fragmented RapidIO packet.

The structure of the fragmented Ethernet packet and the fragmented RapidIO packet has been described in the third embodiment and will not be repeated here. In this embodiment, the conversion of the fragmented Ethernet packet to the fragmented RapidIO packet can be converted from the Ethernet first fragment packet to the RapidIO first fragment packet, and the Ethernet subsequent fragment packet to the RapidIO subsequent fragment. The description of the conversion of the message is described in two aspects.

The conversion of the Ethernet first fragment packet to the RapidIO first fragment packet is shown in Figure 15, including:

Step 510: After receiving the Ethernet first fragment packet, extracting, from the payload of the Ethernet first fragment packet, a control information header including a RapidIO device number and a service data header.

In step 520, the RapidIO device address space corresponding to the service data header is found and added to the RapidIO header in the second mapping relationship between the configured service data header and the RapidIO device address space.

Step 530: Generate a RapidIO first fragment packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.

The subsequent packet fragmentation of the Ethernet to the subsequent fragmentation of the RapidIO packet is shown in Figure 16, including:

Step 610: After receiving the subsequent fragmentation packet of the Ethernet, extracting the routing address information or the IP packet identifier from the header of the subsequent fragmentation packet of the Ethernet;

Step 620: Determine a control information header corresponding to the routing address information according to a first mapping relationship between the information in the configured control information header and the routing address information, or a third mapping from the configured control information header and the IP packet identifier. In the relationship, the control information header corresponding to the IP packet identifier is found; the control information header includes a RapidIO device number and a service data header;

Optionally, in the first mapping relationship, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or at least one of a RapidIO device number and destination system configuration information and source system configuration information. The routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.

Optionally, the third mapping relationship is configured as follows: determining a RapidIO device number of each RapidIO device in the communication system, and using destination system configuration information, source system configuration information, and data type information, so that the RapidIO device number and the destination system configuration are configured. The number of control information headers obtained by the combination of information, source system configuration information, and data type is smaller than the optional IP identifier in the IP packet. The number is greater than the number of IP packets that can be transmitted by the communication system in a period in which the IP identifier cannot be repeated; and then the one-to-one mapping relationship between the control information header and the IP identifier is established.

Step 630: Find the RapidIO device address space corresponding to the service data header from the second mapping relationship associated with the configured RapidIO device number, and add it to the RapidIO header.

Optionally, in the second mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device. In a RapidIO device address space, different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

Step 640: The payload of the subsequent packet of the Ethernet is used as the RapidIO data, and the RapidIO subsequent fragment packet is generated together with the RapidIO header.

In the data transmission, after the fragmented RapidIO packet is generated, the RapidIO device number and the fragmented RapidIO packet are transmitted to the RapidIO interface and then sent to the corresponding RapidIO device.

Correspondingly, the embodiment further provides a packet conversion device for an Ethernet packet to a RapidIO packet, and the packet conversion device is implemented by a programmable logic device. The packet conversion device receives the fragmented Ethernet packet from the Ethernet interface, converts it into a fragmented RapidIO packet, and sends it to the Ethernet device interface.

The packet conversion device can convert the Ethernet first fragmented packet into a RapidIO first fragmented packet, and can also convert the Ethernet subsequent fragmented packet into a RapidIO subsequent fragmented packet. As shown in FIG. 17, the packet conversion device includes:

The Ethernet packet parsing device 50' is configured to extract the control information header and the RapidIO data from the payload after receiving the Ethernet first fragment packet, and the received packet type (here, the fragmentation report) And the non-fragmented message is sent to the RapidIO packet generating device; optionally, after receiving the Ethernet subsequent fragmented packet, the header and the payload are parsed, and the route is extracted from the header. Address information or IP packet identifier;

The routing address mapping device 80' is configured to search for a first mapping relationship between the information in the configured control information header and the routing address information according to the routing address information extracted by the Ethernet packet parsing device to determine a corresponding control information header;

The IP identifier mapping device 90' is configured to search for a corresponding control information header from a third mapping relationship between the configured control information header and the IP packet identifier according to the IP packet identifier extracted by the Ethernet packet parsing device;

The address space mapping device 60' is configured to set a service data header and a RapidIO device address associated with the configured RapidIO device number according to the RapidIO device number and the service data header in the control information header extracted by the Ethernet packet parsing device. In the second mapping relationship of the space, the RapidIO device address space corresponding to the service data header is found; optionally, the RapidIO device in the control information header obtained according to the routing address mapping device or the IP identifier mapping device is further configured. And the number of the service data headers, in the second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space, the RapidIO device address space corresponding to the service data header is found;

The RapidIO message generating device 70' is configured to add the RapidIO device address space found by the address space mapping device to the RapidIO header when the received message type is an Ethernet first fragment message, according to the RapidIO The header, service data header, and RapidIO data generate non-fragmented RapidIO messages.

FIG. 17 also shows the flow of information when the RapidIO first fragment message and the RapidIO subsequent fragment message are converted, and can be distinguished by referring to the text description. It should be noted that, for the packet conversion device, the conversion of the fragmented and non-fragmented Ethernet packets to the fragmented and non-fragmented RapidIO packets can be implemented at the same time, that is, the embodiment. The above device can also be used to implement the functions of the corresponding device in the second embodiment.

The above routing address mapping means 80' and IP identification mapping means 90' may be selected one by one. The function of the above device can also be seen in the corresponding description in the process.

Optionally,

In the first mapping relationship configured in the routing address mapping device 80', the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes The RapidIO device number and at least one of the destination system configuration information and the source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.

Optionally,

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device 60', each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.

The foregoing implementation provides a method for packet conversion (involving data mapping, transmission, and exchange) between a RapidIO interface and an Ethernet interface, and implements communication between the RapidIO device and the Ethernet device and the RapidIO device, and is suitable for passing through the programmable logic device. As implemented by PLC, compared with the traditional CPU message conversion mode, the high-speed parallel data processing mode of the programmable logic device makes the data processing capability no longer limited by the processing power of the CPU, and maximizes the use of link bandwidth resources. At the same time, the data processing speed is faster, which greatly reduces the delay of the data processing process.

The embodiment of the present invention will be described below based on examples in several applications.

Example one

For the convenience of the transmission, the packet conversion can be switched between the RapidIO packet and the Ethernet MAC packet without distinguishing the fragmentation of different packets. The Ethernet packet in this example is a MAC packet. The control information header of the RapidIO packet only needs to be mapped to the MAC header, and then the payload of the RapidIO packet is converted into the MAC packet payload. See Figure 5 .

The mapping method of the control information header and the MAC header of one of the RapidIO packets is as shown in Table 1: All the RapidIO device information is numbered, from 1 to M0, for a total of M0; all the destination system configuration information is numbered. The number is from 1 to M1, and all source system configuration information is numbered, from 1 to M2, for a total of M2, so that N=M0*M1*M2. From Number 1 to number N, each number corresponding to a set of routing addresses (can cover all possible routes), respectively VLAN value (optional) and destination MAC address, can complete all source RapidIO device to destination system VLAN value and MAC The mapping of addresses.

Table 1

After receiving the RapidIO packet, the packet conversion device implemented by the programmable logic device parses the source system configuration information and the destination system configuration information of the control information header, and obtains the RapidIO number. According to the numbering rule, the left control information in Table 1 can be obtained. The number of the information in the header, and find the corresponding MAC header information. The source MAC address is fixed, and the packet type is also a fixed value (such as 0x0806). The destination MAC address, the source MAC address, the VLAN information (optional), and the packet type form a MAC packet header, and then the RapidIO packet is used. The payload is directly converted into a MAC packet payload, and the mapping between the RapidIO packet and the Ethernet packet is completed, and then the communication between the RapidIO device and the Ethernet device is completed through the Ethernet device interface.

Example two

During the transmission of IPV4 packets, packet conversion can be switched between fragmented RapidIO packets and fragmented IPV4 packets for transmission efficiency. The service data header of the RapidIO packet is only available in the RapidIO first fragment packet. Therefore, the RapidIO first fragment packet can directly form a control information header based on the service data header and the RapidIO device number carried in the packet to find the configuration control. The first mapping relationship between the information and the routing address in the information header can obtain information such as the destination IP address and the destination MAC address in the MAC header and the IPV4 header. See Figure 6.

For the RapidIO subsequent fragmented packets, first find the RapidIO device address space and service data configured for the corresponding RapidIO device through the RapidIO device address space in the RapidIO header. The second mapping relationship of the header, the searched service data header and the RapidIO device number form a control information header, and then the first mapping relationship is obtained to obtain information such as a destination IP address and a destination MAC address.

Therefore, the packet conversion device needs to be divided into the above two cases. For the RapidIO first fragmented packet, the routing address information is directly mapped through the control information header. For the RapidIO subsequent fragmented packet, the control information header is obtained through the address space mapping. Then, the routing address information is obtained through the control information header mapping.

In the RapidIO interconnect architecture, the maximum address space accessible to RapidIO devices in the system is deterministic. In the configuration of the second mapping relationship, the address space can be divided and mapped. An exemplary method for dividing and mapping is as follows: all the destination system configuration information is numbered, from 1 to M1, for a total of M1; The source system configuration information is numbered, from 1 to M2, for a total of M2; all packet types are numbered, from 1 to M3, for a total of M3; the address space occupied by each packet type may be different, The maximum address space occupied is M4. M1 to M4 can be adjusted during system planning/configuration so that M1*M2*M3*M4 is not larger than the maximum address space of the RapidIO device.

In this example, the routing address information in the first mapping relationship includes a next hop MAC address, a destination IP address, and VLAN information. The routing address information is mapped by the RapidIO device number, source system configuration information, and destination system configuration information in the control information header. One of the exemplary mapping relationships is shown in Table 2. For the numbering rule of the information in the control information header in the table, refer to the first example, which covers the routing address information used by all possible routes.

Form 2

When configuring the third mapping relationship between the IP packet identifier and the control information header, an exemplary method is used. As follows: All RapidIO device information is numbered, from 1 to M0, for a total of M0; all destination system configuration information is numbered, from 1 to M1, for a total of M1; all source system configuration information is numbered, The number is from 1 to M2, for a total of M2; all the packet types are numbered, from 1 to M3, for a total of M3. M1 to M3 can be adjusted during system planning/configuration. Considering that the IP identifier only needs to distinguish different fragmented packets within a certain period of time (assuming 1ms, 10ms, depending on the system), it can be assumed that there are a total of M5 data packets exchanged in a fixed period. Therefore, if M0*M1*M2*M3 is greater than or equal to M5, it is possible to distinguish different fragmented messages within a period of time. The IP identifier is 16 bits in the IPV4 header, so M0*M1*M2*M3 should be less than or equal to 65536, that is, M5<=M0*M1*M2*M3<=65536 in a fixed period of time. For example, in 10 ms, the number of bytes transmitted by the 10G Ethernet interface is up to 12500000 bytes. If the average length of the data type is 500 bytes, the number of packets to be exchanged for 10 ms is M5000. Assume that there are 16 data types in 10ms, a total of 10 RapidIO device information numbers, 16 destination system configuration information numbers, 16 source system configuration information numbers, and 16 IP address identifiers. 40,960, able to distinguish up to 25,000 packets of 10ms. In the third mapping relationship, the IP identification field is numbered from 1 to 40960 (the number is less than 65536), and the one-to-one mapping relationship between the IP packet identifier and the control information header can be established.

After the routing address information and the IP packet identifier are obtained through the mapping, the information is added to the corresponding fields of the MAC header and the IPV4 header, and other fields are filled in to obtain the header of the IPV4 packet. The payload of the IPIO4 packet is directly converted into the IPV4 packet payload, and the IPV4 first fragment packet is generated according to the header, control information header and IPV4 packet payload of the obtained IPV4 packet, according to the header of the obtained IPV4 packet. The IPV4 packet payload is generated by the IPV4 packet payload.

During the transmission of IPV6 packets, packet conversion can be performed between the fragmented RapidIO packets and the fragmented IPV6 packets for the sake of transmission efficiency. The conversion of the fragmented RapidIO packet to the fragmented IPV6 packet is similar to the conversion of the fragmented IPV4 packet, and will not be described here.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the foregoing embodiment may be adopted. The form of hardware implementation can also be implemented in the form of software function modules. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

Claims

A method for converting a RapidIO packet to an Ethernet packet includes:

Receiving the RapidIO device number and the non-fragmented RapidIO packet sent by the RapidIO device;

And the service data header of the RapidIO device number and the RapidIO packet is formed into a control information header, and the first mapping relationship between the information and the routing address information in the configured control information header is used to find the corresponding information of the control information header. Routing address information;

Adding the found routing address information to the Ethernet header, and generating an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO packet.
The method of claim 1 wherein:

The information in the control information header includes at least one of a destination system configuration information and a source system configuration information, or includes at least one of a RapidIO device number and destination system configuration information and source system configuration information;

The routing address information includes a destination media access control MAC address, or at least one of a destination MAC address and a destination IP address and a virtual local area network (VLAN) VLAN value.
A method for converting an Ethernet packet to a RapidIO packet includes:

Receiving a non-fragmented Ethernet packet, and extracting, from the payload of the Ethernet packet, a control information header including a RapidIO device number and a service data header;

Searching for the RapidIO device address space corresponding to the service data header from the second mapping relationship between the configured service data header and the RapidIO device address space;

Adding the discovered RapidIO device address space to the RapidIO header, and generating a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.
The method of claim 3 wherein:

In the second mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device. One of the divisions In the RapidIO device address space, different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.
A method for converting a RapidIO packet to an Ethernet packet includes:

Receiving the RapidIO device number and the RapidIO first fragment packet sent by the RapidIO device;

And the service data header of the RapidIO device number and the RapidIO first fragment packet is formed into a control information header, and the corresponding information of the control information header is found in the first mapping relationship between the information and the routing address information in the configured control information header. Routing address information and adding it to the Ethernet header;

Generating an Ethernet first fragmented packet according to the Ethernet header, the control information header, and the RapidIO data in the RapidIO first fragmented packet.
The method of claim 5, the method further comprising:

Receiving the RapidIO device number and the RapidIO subsequent fragment packet sent by the RapidIO device;

The service data header corresponding to the RapidIO device address space in the RapidIO subsequent fragmented packet is found in the second mapping relationship between the configured service data header and the RapidIO device address space.

The service data header and the RapidIO device number are combined into a control information header, and the routing address information corresponding to the control information header is found in the first mapping relationship;

Adding the found routing address information to the Ethernet header, and generating an Ethernet subsequent fragmentation packet according to the Ethernet header and the RapidIO data in the RapidIO subsequent fragmented packet.
The method of claim 6 wherein:

In the second mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device. A RapidIO device address space is divided. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.
The method of claim 5 or 6 or 7, wherein:

The information in the control information header includes at least one of a destination system configuration information and a source system configuration information, or includes a RapidIO device number and destination system configuration information, and a source system configuration letter. At least one of the interest;

The routing address information includes a destination MAC address, or at least one of a destination MAC address and a destination IP address and a VLAN value.
The method of claim 5 or 6 or 7, wherein the method further comprises:

After the first packet of the RapidIO first packet and the subsequent fragment of the RapidIO packet are converted, the control information header is searched for from the third mapping relationship between the configured control information header and the IP packet identifier. The IP packet is identified and added to the Ethernet header.
The method of claim 9 wherein:

The third mapping relationship is configured to: determine a RapidIO device number of each RapidIO device in the communication system, and use destination system configuration information, source system configuration information, and data type information, such that the RapidIO device number, destination system configuration information, The number of control information headers obtained by combining the source system configuration information and the data type is smaller than the number of optional IP identifiers in the IP packet and greater than the number of IP packets that can be transmitted by the communication system in a period in which the IP identifier cannot be repeated; Then, a one-to-one mapping relationship between the control information header and the IP identifier is established.
A method for converting an Ethernet packet to a RapidIO packet includes:

After receiving the Ethernet first fragment packet, perform the following conversion processing:

Extracting, from the payload of the Ethernet first fragment packet, a control information header including a RapidIO device number and a service data header;

Searching for the RapidIO device address space corresponding to the service data header and adding it to the RapidIO header in the second mapping relationship between the configured service data header and the RapidIO device address space.

And generating a RapidIO first fragment packet according to the RapidIO header, the service data header, and the RapidIO data except the control information header in the payload.
The method of claim 11 further comprising:

After receiving the subsequent fragments of the Ethernet packet, perform the following conversion processing:

Extracting routing address information or an IP packet identifier from a header of the subsequent fragmentation packet of the Ethernet;

Determining, according to the first mapping relationship between the information in the control information header and the routing address information, the control information header corresponding to the routing address information; or, in the third mapping relationship between the configured control information header and the IP packet identifier, Finding a control information header corresponding to the IP packet identifier; the control information header includes a RapidIO device number and a service data header;

Searching for the RapidIO device address space corresponding to the service data header from the second mapping relationship associated with the configured RapidIO device number, and adding the address to the RapidIO header;

The payload of the subsequent packet of the Ethernet is used as the RapidIO data, and the RapidIO subsequent fragment packet is generated together with the RapidIO header.
The method of claim 12 wherein:

The information in the control information header includes at least one of a destination system configuration information and a source system configuration information, or includes at least one of a RapidIO device number and destination system configuration information and source system configuration information;

The routing address information includes a destination MAC address, or at least one of a destination MAC address and a destination IP address and a VLAN value.
A method as claimed in claim 12 or claim 13 wherein:

The third mapping relationship is configured to: determine a RapidIO device number of each RapidIO device in the communication system, and use destination system configuration information, source system configuration information, and data type information, such that the RapidIO device number, destination system configuration information, The number of control information headers obtained by combining the source system configuration information and the data type is smaller than the number of optional IP identifiers in the IP packet and greater than the number of IP packets that can be transmitted by the communication system in a period in which the IP identifier cannot be repeated; Then, a one-to-one mapping relationship between the control information header and the IP identifier is established.
The method of claim 11 or 12 or 13 wherein:

In the second mapping relationship between the service data header associated with the RapidIO device ID and the RapidIO device address space, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to the maximum address space of the RapidIO device. A RapidIO device address space is divided. Different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.
A packet conversion device for a packet from a RapidIO packet to an Ethernet packet, including:

The RapidIO packet parsing device is configured to receive the RapidIO device number and the non-fragmented RapidIO packet, and extract the service data header and the RapidIO data in the RapidIO packet;

a control information header generating device, configured to form the RapidIO device number and the service data header into a control information header;

The routing address mapping device is configured to: find the routing address information corresponding to the control information header from the first mapping relationship between the information and the routing address information in the configured control information header;

The Ethernet packet generating device is configured to add the routing address information to an Ethernet header, and generate an Ethernet packet according to the Ethernet header, the control information header, and the RapidIO data.
A message conversion device according to claim 16,

The message conversion device is implemented by a programmable logic device.
A message conversion device according to claim 16 or 17, wherein:

In the first mapping relationship configured in the routing address mapping device, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. And at least one of source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.
A packet conversion device for transmitting Ethernet packets to RapidIO packets, including:

An Ethernet packet parsing apparatus is configured to receive a non-fragmented Ethernet packet, and extract, from the payload of the Ethernet packet, a control information header and a RapidIO data including a RapidIO device number and a service data header;

The address space mapping device is configured to find a RapidIO device address space corresponding to the service data header from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space;

The RapidIO packet generating device is configured to add the discovered RapidIO device address space to the RapidIO header, and generate a non-fragmented RapidIO packet according to the RapidIO header, the service data header, and the RapidIO data.
A message conversion device according to claim 19,

The message conversion device is implemented by a programmable logic device.
A message conversion device according to claim 19 or 20, wherein:

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device, and different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.
A packet conversion device for a packet from a RapidIO packet to an Ethernet packet, including:

The RapidIO packet parsing device is configured to receive the RapidIO device number and the RapidIO first fragment packet, extract the service data header and the RapidIO data in the RapidIO first fragment packet, and notify the Ethernet packet of the received packet type. Text generation device;

a control information header generating device, configured to form the control information header by the RapidIO device number and the service data header extracted by the RapidIO packet parsing device;

The routing address mapping device is configured to: according to the control information header formed by the control information header generating device, find the corresponding routing address information from the first mapping relationship between the information and the routing address information in the configured control information header;

The Ethernet packet generating device is configured to add, when the received packet type is a RapidIO first fragment packet, the routing address information found by the routing address mapping device to the Ethernet header, according to the Ethernet header. The control information header and the RapidIO data generate an Ethernet first fragment message.
The message conversion device according to claim 22, wherein said message conversion device further comprises address space mapping means, wherein:

The RapidIO packet parsing apparatus is further configured to receive the subsequent fragment of the RapidIO, extract the RapidIO device address space and the RapidIO data in the subsequent fragmented fragmentation message, and notify the Ethernet packet generating apparatus of the received packet type. ;

The address space mapping device is configured to find a service data header corresponding to the address space of the RapidIO device from a second mapping relationship between the service data header associated with the configured RapidIO device number and the RapidIO device address space;

The control information header generating device is further configured to form, by the RapidIO device number and the service data header searched by the address space mapping device, a control information header;

The Ethernet packet generating device is further configured to: when the received packet type is a RapidIO subsequent fragment packet, add the routing address information found by the routing address mapping device to the Ethernet header, according to the The Ethernet header and RapidIO data generate Ethernet subsequent fragmented packets.
A message conversion device as claimed in claim 23, wherein:

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device, and different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.
The message conversion device according to claim 22 or 23 or 24, wherein the message conversion device further comprises:

The IP identifier mapping device is configured to search for the IP packet corresponding to the control information header from the third mapping relationship between the configured control information header and the IP packet identifier according to the control information header formed by the control information header generating device. Identification

The Ethernet packet generating device is further configured to add the IP packet identifier that is found by the IP identifier mapping device to the Ethernet when the received packet type is a RapidIO first fragment packet and a RapidIO subsequent fragment packet. In the net header.
A message conversion device according to claim 22 or 23 or 24,

The message conversion device is implemented by a programmable logic device.
A message conversion device according to claim 22 or 23 or 24, wherein:

In the first mapping relationship configured in the routing address mapping device, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. And at least one of source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.
A packet conversion device for transmitting Ethernet packets to RapidIO packets, including:

The Ethernet packet parsing device is configured to: after receiving the Ethernet first fragment packet, extract the control information header and the RapidIO data from the payload, and notify the RapidIO packet generating device of the received packet type, where the control The information header includes the RapidIO device number and the service data header;

The address space mapping device is configured to: according to the RapidIO device number and the service data header in the control information header extracted by the Ethernet packet parsing device, the service data header associated with the configured RapidIO device number and the RapidIO device address space In the second mapping relationship, the RapidIO device address space corresponding to the service data header is found;

The RapidIO packet generating device is configured to add, when the received packet type is an Ethernet first fragment packet, the RapidIO device address space found by the address space mapping device to the RapidIO header, according to the RapidIO header, The service data header and the RapidIO data generate non-fragmented RapidIO messages.
A message conversion device as claimed in claim 28,

The message conversion device further includes a routing address mapping device and/or an IP identification mapping device, wherein:

The Ethernet packet parsing device is further configured to parse the header and the payload after receiving the subsequent fragmentation packet of the Ethernet, and extract the routing address information or the IP packet identifier from the header.

The routing address mapping device is configured to search for a first mapping relationship between the information in the configured control information header and the routing address information according to the routing address information extracted by the Ethernet packet parsing device to determine a corresponding control information header;

The IP identifier mapping device is configured to search for a corresponding control information header from a third mapping relationship between the configured control information header and the IP packet identifier according to the IP packet identifier extracted by the Ethernet packet parsing device;

The address space mapping device is further configured to: according to the RapidIO device number and the service data header in the control information header obtained by the routing address mapping device or the IP identifier mapping device, the service data header associated with the configured RapidIO device number In the second mapping relationship with the address space of the RapidIO device, the RapidIO device address space corresponding to the service data header is found;

The RapidIO packet generating device is further configured to receive the received packet type as an Ethernet follow-up Adding a RapidIO device address space that is found by the address space mapping device to the RapidIO header, and using the payload of the subsequent Ethernet fragmentation packet as RapidIO data, and generating the same with the RapidIO header. RapidIO subsequent fragmentation message.
A message conversion device as claimed in claim 29, wherein:

In the first mapping relationship configured in the routing address mapping device, the information in the control information header includes at least one of destination system configuration information and source system configuration information, or includes a RapidIO device number and destination system configuration information. And at least one of source system configuration information; the routing address information includes a destination MAC address, or includes at least one of a destination MAC address and a destination IP address and a VLAN value.
A message conversion device as claimed in claim 28 or 29 or 30, wherein:

In the second mapping relationship between the service data header associated with the RapidIO device number and the RapidIO device address space configured in the address space mapping device, each service data header used by the RapidIO device identified by the RapidIO device number is mapped to A RapidIO device address space is allocated in the maximum address space of the RapidIO device, and different service data headers correspond to different RapidIO device address spaces, and each RapidIO device address space is divided into the same size.