CN116760911A - Heterogeneous protocol conversion system and method - Google Patents
Heterogeneous protocol conversion system and method Download PDFInfo
- Publication number
- CN116760911A CN116760911A CN202310664828.6A CN202310664828A CN116760911A CN 116760911 A CN116760911 A CN 116760911A CN 202310664828 A CN202310664828 A CN 202310664828A CN 116760911 A CN116760911 A CN 116760911A
- Authority
- CN
- China
- Prior art keywords
- protocol
- header data
- frame header
- target
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 107
- 238000000034 method Methods 0.000 title claims description 37
- 238000004364 calculation method Methods 0.000 claims description 12
- 238000004458 analytical method Methods 0.000 claims description 10
- 238000013507 mapping Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 abstract description 11
- 230000000694 effects Effects 0.000 abstract description 4
- 230000005540 biological transmission Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 6
- 125000004122 cyclic group Chemical group 0.000 description 5
- 102100033189 Diablo IAP-binding mitochondrial protein Human genes 0.000 description 4
- 101710101225 Diablo IAP-binding mitochondrial protein Proteins 0.000 description 4
- 238000007405 data analysis Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 235000019800 disodium phosphate Nutrition 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001902 propagating effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Abstract
The application relates to the technical field of communication, and provides a heterogeneous protocol conversion system, which comprises: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module; receiving/transmitting heterogeneous network messages of different protocol types through a protocol interface module; and then converting the received heterogeneous network messages with different protocol types by using a protocol conversion module to obtain the heterogeneous network message with the target protocol type. In this way, through the protocol interface module and the protocol conversion module, the heterogeneous protocol conversion system can receive heterogeneous network messages of different protocol types for conversion and then send the messages, so that the effect of conversion of different heterogeneous protocols is achieved. Therefore, flexible definition of port protocol, width and speed can be realized through the protocol interface module, so that different interconnection scenes are met, and on the other hand, the conversion module is based on hardware realization, has higher conversion timeliness and throughput rate, and reduces the constraint of network deployment.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a heterogeneous protocol conversion system and method.
Background
With the development of modern technologies, the requirement for implementing high-speed real-time communication between heterogeneous protocol networks is becoming urgent. Ethernet is currently the most commonly used computer network, and there are two main protocols for the ethernet transport layer: UDP, TCP, the scheme realizes the conversion to UDP protocol message. RapidIO is an interconnection technology based on high-performance packet switching, and has a main function of completing high-speed data transmission among a microprocessor, a DSP, a system memory and peripherals in a node system.
In the prior art, two implementation schemes are generally adopted aiming at the exchange requirement of the rapidIO protocol and the Ethernet protocol heterogeneous network, and one implementation scheme is a customized heterogeneous protocol conversion device based on FPGA. Such devices may implement specific RapidIO port controllers, ethernet port controllers, and fixed translation protocol types. Another is CPU-based protocol conversion. And the data frames are sent to the CPU, so that the conversion operations of analysis, encapsulation and the like of the data messages are realized on the CPU. And will be sent to the heterogeneous target network through the heterogeneous protocol controller.
In the above scheme for converting RapidIO and ethernet heterogeneous protocols, on one hand, the FPGA scheme does not have flexibility, cannot adjust the rate and width of the protocol ports, and cannot fully satisfy different application scenarios. On the other hand, the CPU scheme has low conversion efficiency, can not effectively meet the high real-time requirement of rapidIO, and the CPU scheme needs bridge matching or supports the rapidIO controller by the CPU, so that the network deployment has higher constraint.
Disclosure of Invention
In view of this, the present application provides a heterogeneous protocol conversion system and method, which aims to flexibly define protocol ports, rates and widths, improve conversion timeliness and throughput of different heterogeneous protocols, and reduce constraint of network deployment.
In a first aspect, the present application provides a heterogeneous protocol conversion system, the system comprising: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module;
the protocol interface module is used for receiving/transmitting heterogeneous network messages of different protocol types;
the protocol conversion module is used for converting the received heterogeneous network messages with different protocol types to obtain the heterogeneous network messages with the target protocol types.
Optionally, the protocol conversion module includes a message parsing module, a matching module and a message Wen Pinjie module; the message analysis module, the matching module and the message splicing module are connected in sequence; the message analysis module and the message splicing module are respectively connected with the protocol interface module;
the message analysis module is used for analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data;
The matching module is used for matching the frame header data of the source protocol message to obtain target protocol frame header data of a target protocol type; the corresponding relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type is stored in a matching module in advance;
the message splicing module is used for splicing the target protocol frame header data of the target protocol type and the source protocol message load data and converting the target protocol frame header data and the source protocol message load data to obtain the heterogeneous network message of the target protocol type.
Optionally, the message analysis module includes a message data splitting unit and a message data analysis unit;
the message data splitting unit is used for splitting the received heterogeneous network messages of different protocol types based on the corresponding protocol types to obtain source protocol message frame header data fields and source protocol message load data;
the message data analyzing unit is used for analyzing the source protocol message frame header data field to obtain source protocol message frame header data; when the protocol type of the received heterogeneous network message is rapidIO protocol, analyzing a header data field of the heterogeneous network message according to the rapidIO protocol to obtain a service class ID, a data class ID, TT and address data; and when the protocol type of the received heterogeneous network message is an Ethernet protocol, analyzing the header data field of the Ethernet protocol message of the heterogeneous network message according to the Ethernet protocol to obtain an MAC address, an IP address and a UDP port number.
Optionally, the matching module comprises a storage unit and a matching unit;
the storage unit is used for storing the relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type;
the matching unit is used for carrying out hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index, and matching the target protocol frame header data of the target protocol type from the storage unit based on the target protocol frame header data index.
Optionally, the matching unit is specifically configured to perform assembling according to the source protocol message frame header data to obtain a key value of a hash algorithm, and perform parallel hash computation according to the source protocol message frame header data to obtain a target protocol frame header data index, and match the target protocol frame header data of the target protocol type from the storage unit based on the target protocol frame header data index.
Optionally, the message analysis module includes a message data splitting unit and a message data analysis unit;
the message data splitting unit is used for splitting the received heterogeneous network messages of different protocol types based on the corresponding protocol types to obtain source protocol message header data fields and source protocol message load data;
The message data analysis unit is used for analyzing the source protocol message header data field to obtain source protocol message frame header data; when the protocol type of the received heterogeneous network message is rapidIO protocol, analyzing a header data field of the heterogeneous network message according to the rapidIO protocol to obtain a service class ID, a data class ID, TT and address data; and when the protocol type of the received heterogeneous network message is an Ethernet protocol, analyzing the header data field of the Ethernet protocol message of the heterogeneous network message according to the Ethernet protocol to obtain an MAC address, an IP address and a UDP port number.
Optionally, the protocol interface module is configured to receive/send heterogeneous network packets of different protocol types in response to heterogeneous network configuration operations of different protocol types.
In a second aspect, the present application provides a heterogeneous protocol conversion method, which is characterized in that the method is applied to the heterogeneous protocol conversion system described in any one of the above, and the method includes:
receiving heterogeneous network messages of different protocol types;
converting the received heterogeneous network messages with different protocol types to obtain heterogeneous network messages with target protocol types;
And sending the heterogeneous network message of the target protocol type to a target heterogeneous network.
Optionally, the converting the received heterogeneous network packet with different protocol types to obtain a heterogeneous network packet with a target protocol type includes:
analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data;
obtaining target protocol frame header data of a target protocol type according to the source protocol message frame header data matching;
assembling the target protocol frame header data of the target protocol type and the source protocol message load data, and converting the assembled target protocol frame header data and the source protocol message load data to obtain the heterogeneous network message of the target protocol type.
Optionally, the matching the source protocol message frame header data to obtain target protocol frame header data of a target protocol type includes:
assembling according to the source protocol message frame header data to obtain a key value of a hash algorithm, and simultaneously performing parallel hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index;
obtaining target protocol frame header data of a target protocol type based on the target protocol frame header data index matching; the relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type are stored in the storage unit in advance.
In a third aspect, the present application provides an apparatus comprising a memory for storing instructions or code and a processor for executing the instructions or code to cause the apparatus to perform the heterogeneous protocol conversion method of any of the preceding second aspects.
In a fourth aspect, the present application provides a computer storage medium having code stored therein, which when executed, causes an apparatus running the code to implement the heterogeneous protocol conversion method of any of the preceding second aspects.
The application provides a heterogeneous protocol conversion system, which comprises: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module; receiving/transmitting heterogeneous network messages of different protocol types through a protocol interface module; and then converting the received heterogeneous network messages with different protocol types by using a protocol conversion module to obtain the heterogeneous network message with the target protocol type. In this way, through the protocol interface module and the protocol conversion module, the heterogeneous protocol conversion system can receive heterogeneous network messages of different protocol types for conversion and then send the messages, so that the effect of conversion of different heterogeneous protocols is achieved. Therefore, flexible definition of port protocol, width and speed can be realized through the protocol interface module, so that different interconnection scenes can be met, and on the other hand, the conversion module is based on hardware realization, has higher conversion timeliness and throughput rate, reduces the constraint of network deployment, and can also reduce the cost of network deployment.
Drawings
In order to more clearly illustrate this embodiment or the technical solutions of the prior art, the drawings that are required for the description of the embodiment or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a heterogeneous protocol conversion system according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a protocol conversion module 102 according to an embodiment of the present application;
fig. 3 is a flowchart of a heterogeneous protocol conversion method according to an embodiment of the present application;
fig. 4 is a flowchart of a possible method of step S302 according to an embodiment of the present application
FIG. 5a is a schematic diagram of matching according to an embodiment of the present application;
fig. 5b is a schematic diagram of an embodiment of the present application;
fig. 6 is a schematic diagram of a heterogeneous protocol implementation topology according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a heterogeneous protocol conversion device according to an embodiment of the present application.
Detailed Description
As described above, there are a plurality of heterogeneous networks of protocol types, such as FC protocol networks that meet storage requirements and optical network characteristics, rapidIO protocol networks that meet high real-time interconnection requirements of CPUs, DSPs, and the like, and ethernet protocol networks that meet wide area interconnection. In the actual network interconnection exchange process, in order to realize effective transmission and interaction of data in different networks, there is also an exchange requirement for heterogeneous network interconnection. The inventor finds that in the research aiming at the heterogeneous network interaction, the related technology realizes the heterogeneous network data interaction and needs a customized heterogeneous protocol conversion device or occupies a CPU to process the heterogeneous protocol data. However, the customized heterogeneous protocol conversion device cannot have flexibility, and cannot adjust the speed, the width and the like of the protocol port, so that different application scenes cannot be satisfied, and the device has limitation in the practical application process. The CPU is occupied to process heterogeneous protocol data, so that on one hand, the memory of the CPU is occupied, the CPU performance is affected, meanwhile, the problem that the high-timeliness network requirements such as rapidIO and the like cannot be met due to low conversion efficiency of the CPU is solved, and on the other hand, the CPU scheme needs to be matched with a bridge or needs to support a rapidIO controller, and high constraint is achieved from the deployment of the network.
In view of this, the present application provides a heterogeneous protocol conversion system, the system comprising: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module; receiving/transmitting heterogeneous network messages of different protocol types through a protocol interface module; and then converting the received heterogeneous network messages with different protocol types by using a protocol conversion module to obtain the heterogeneous network message with the target protocol type. In this way, through the protocol interface module and the protocol conversion module, the heterogeneous protocol conversion system can receive heterogeneous network messages of different protocol types for conversion and then send the messages, so that the effect of conversion of different heterogeneous protocols is achieved.
Therefore, flexible definition of port protocol, width and speed can be realized through the protocol interface module, so that different interconnection scenes can be met, and on the other hand, the conversion module is based on hardware realization, has higher conversion timeliness and throughput rate, and can also reduce the cost of network deployment.
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a schematic structural diagram of a heterogeneous protocol conversion system according to an embodiment of the present application, where, as shown in fig. 1, the heterogeneous protocol conversion system according to the embodiment of the present application includes: a protocol interface module 101 and a protocol conversion module 102; the protocol interface module 101 is connected with the protocol conversion module 102;
the protocol interface module 101 is configured to receive/send heterogeneous network packets with different protocol types.
In this embodiment, heterogeneous networks refer to two or more communication systems that use different access technologies, or use the same access technology but have significant differences in network bandwidth, storage/computation/processing resources, and so on. For example, in embedded systems, two of the most common interconnections occur due to the advantages of bandwidth breakthrough: ethernet and RapidIO.
Wherein RapidIO is a high-performance, low-pin-count, packet-switching-based interconnect architecture, which is an open interconnect technology standard. rapidIO is mainly applied to internal interconnection of an embedded system, supports chip-to-chip and board-to-board communication, and can be used as a backboard (Backplane) connection of embedded equipment. RapidI0 adopts a three-layer hierarchical architecture including a logical layer, a transport layer, and a physical layer. The logic layer is positioned at the highest layer, defines all protocols and packet formats, and provides necessary data for the endpoint device to initiate and complete the transaction; the transmission layer specification is positioned in the middle layer and defines a rapidIO address space and routing data required by transmitting packets between endpoint devices; the physical layer specification is at the bottom of the overall hierarchy and includes details of the device-level interfaces such as packet transport mechanisms, flow control, electrical characteristics, and low-level error management functions.
The different fields of the RapidIO packet may each represent a different meaning, taking the RapidIO request packet as an example, starting from the physical layer field, the S bit indicates whether this is a packet or a control symbol (s=0 represents a packet and s=1 represents a control symbol), and the AckID indicates which packet the switching fabric device will use the control symbol to acknowledge. The PRIO field indicates packet priority for flow control. The TT, target Address (Target Address) and Source Address (Source Address) fields indicate the type of mechanism that transmitted the Address, the Address of the device to which the packet should be transferred, and the Address of the device that generated the packet. Ftype and transaction (transfer) indicate the transaction being requested. The length (Size) field is equal to the length of the encoded transaction, and the Payload (Payload) length of the RapidIO transaction data varies from 1 to 256 bytes. SrcTID (Source transaction ID) indicates a transaction ID, and the rapidIO device allows a maximum of 256 outstanding transactions between two endpoint devices. For a memory mapped transaction, the Source TID is followed by a device offset address (Device Offset Address) field. The write transaction must be accompanied by a valid payload of data, all packets ending with a 16-bit (2 bytes) cyclic redundancy check code (CRC).
Ethernet is a regional network interconnection technology, and is roughly classified into: standard ethernet (10 Mbit/s), fast ethernet (100 Mbit/s), gigabit ethernet (1000 Mbit/s), and faster gigabit ethernet (10 Gbit/s). The ethernet communication is performed through a connection line, so both ethernet receiving and transmitting parties have interfaces.
Similar to RapidIO, ethernet also has a certain packet format, mainly including a physical layer (MAC layer), a network layer (IP layer), a transport layer (UDP layer) and user data, and taking an ethernet request packet as an example, from a physical layer field, a Preamble (Preamble): the MAC physical layer uses 7 byte synchronization codes to achieve synchronization of data. Frame start delimiter (SFD, start Frame Delimiter): the start of a frame is indicated by a SFD of 1 byte (fixed value 0xd 5) followed by the frame header of the ethernet. Destination MAC address: i.e. the receiving end physical MAC address, takes up 6 bytes. Source MAC address: i.e. the sender physical MAC address, takes 6 bytes. Length/type: the length/type has two meanings, when the value of the two bytes is less than 1536, representing the length of the data segment in the ethernet; if the value of these two bytes is greater than 1536, it means that the data in the ethernet belongs to an upper layer protocol, for example, 0x0800 represents an IP protocol (network protocol), 0x0806 represents an ARP protocol (address resolution protocol), and the like. Data: the length of the data segment in the Ethernet is minimum of 46 bytes and maximum of 1500 bytes. Frame check sequence (FCS, frame Check Sequence): to ensure proper transmission of data, a cyclic redundancy check (CRC check) of 4 bytes is added at the end of the data to detect whether the data is transmitted in error. Frame Gap (IFG), intersacket Gap): that is, the time interval between two adjacent frames of the ethernet, the time of a frame gap is the time that the network device and component need a short time to recover and prepare for receiving the next frame after receiving a frame.
The ethernet includes a TCP (transmission control protocol)/IP (internet protocol) protocol cluster, wherein the TCP/IP protocol cluster includes hundreds of protocols, and most commonly used are a TCP protocol, an IP protocol, a UDP protocol, and the like. The TCP protocol is a reliable transmission protocol, and can ensure the integrity and order of data; the UDP protocol is an unreliable transport protocol, and because the UDP protocol does not require a connection, the transport speed is faster than TCP, and occupies fewer resources than TCP.
In the above-mentioned ethernet communication, since the communication is performed through a connection line, both ethernet receiving and transmitting parties have interfaces. The present embodiment may be used to receive/transmit heterogeneous network packets with different protocol types through the protocol interface module 101. Such as ethernet protocol messages and RapidIO protocol messages.
Alternatively, the protocol interface module 101 may receive and transmit heterogeneous network packets of different protocol types based on corresponding configuration data in response to heterogeneous network configuration operations of different protocol types. For example, when the communication network is an ethernet protocol, the protocol interface component is defined as an ethernet protocol, so that the protocol interface module can receive and transmit ethernet protocol messages; when the communication network is RapidIO protocol, the protocol interface component is defined as RapidIO protocol, so that the protocol interface module can receive and send RapidIO protocol messages.
Specifically, in order to meet the network bandwidth requirement when the RapidIO protocol transmission is performed, the port width and the rate of the RapidIO protocol interface module may be dynamically configured, for example: the link width is 1, 2 or 4, and the larger the link width is, the larger the transmission bandwidth of the data is; the transmission frequency, which represents the transmission rate of each serial link, is selected from the group consisting of 1.25, 2.5, 3.125, 5.0 and 6.25. The larger the transmission frequency, the larger the transmission bandwidth of the data.
In order to provide an interface with greater bandwidth, higher flexibility and availability and more balanced load when ethernet protocol transmission is performed, multiple ethernet interfaces may be combined or bundled together to form a link layer interface, referred to as an aggregate ethernet interface, where the protocol interface module 101 provided in this embodiment is an aggregate ethernet interface, and the aggregate attribute of the ethernet protocol interface module may be flexibly configured based on the protocol interface module 101, so that the configuration may be interrupted on any physical link, traffic will be redistributed to other member links, and when a link fails, the aggregate ethernet bundle balances the load between its member links, and the bandwidth of the interface is higher than that provided by each individual link, without requiring new equipment.
The protocol conversion module 102 is configured to convert the received heterogeneous network messages with different protocol types to obtain a heterogeneous network message with a target protocol type.
In this embodiment, after receiving heterogeneous network packets of different protocol types, the protocol conversion module 102 converts the received heterogeneous network packets of different protocol types to obtain heterogeneous network packets of a target protocol type. For example, when the received heterogeneous network packet is a RapidIO protocol packet and the target transmission network of the packet is an ethernet, it is understood that the RapidIO and the ethernet belong to different networks, that is, the packet transmission network is a heterogeneous network, and the RapidIO protocol packet cannot be parsed and transmitted in the ethernet. Therefore, the rapidIO protocol message needs to be converted to obtain the Ethernet protocol message, and then the data is sent to the Ethernet through the Ethernet protocol message, so that the aim of data interaction of different heterogeneous networks is achieved. The protocol conversion module 102 converts the received RapidIO protocol message to obtain an ethernet protocol message, and then sends the ethernet protocol message to the ethernet through the protocol interface module 101 configured as an ethernet protocol.
Optionally, fig. 2 is a schematic structural diagram of a protocol conversion module 102 according to an embodiment of the present application; the protocol conversion module 102 includes a message parsing module 1021, a matching module 1022 and a message Wen Pinjie module 1023; the message parsing module 1021, the matching module 1022 and the message Wen Pinjie module 1023 are connected in sequence; the message parsing module 1021 and the message Wen Pinjie module 1023 are respectively connected with the protocol interface module.
In this embodiment, the message parsing module 1021 is configured to parse received heterogeneous network messages with different protocol types based on corresponding protocol types to obtain source protocol message frame header data and source protocol message payload data. Specifically, the received heterogeneous network message of the protocol type is a source protocol message, and the source protocol message is analyzed based on the protocol type corresponding to the source protocol message to obtain source protocol message frame header data and source protocol message load data. Wherein the frame header data may include a service class ID, a data class ID, a TT and address data such as RapidIO protocol header fields, for example: ID:0x01, TT:0x0, TID:0xA; MAC address, IP address, and UDP port number as ethernet protocol header fields, for example: mac address: 00:AB:CD:00:00:01, IP address: 1.1.1.1, UDP source port: 1000, etc.
Optionally, the message parsing module 1021 specifically includes a message data splitting unit and a message data parsing unit.
The message data splitting unit is used for splitting the received heterogeneous network messages of different protocol types based on the corresponding protocol types to obtain source protocol message frame header data fields and source protocol message load data. Specifically, when the protocol type of the received heterogeneous network message is RapidIO protocol, firstly splitting the RapidIO protocol message to obtain RapidIO protocol message frame header data field and RapidIO protocol message load data, and similarly, when the protocol type of the received heterogeneous network message is ethernet UDP protocol, firstly splitting the ethernet UDP protocol message to obtain ethernet UDP protocol message frame header data field and ethernet UDP protocol message load data.
The message data analyzing unit is used for analyzing the source protocol message frame header data field to obtain source protocol message frame header data. Based on the obtained source protocol message frame header data field, when the source protocol is rapidIO protocol, the message data analysis unit analyzes the rapidIO protocol message header data field of the heterogeneous network message according to the rapidIO protocol to obtain service class ID, data class ID, TT and address data; and when the protocol type of the received heterogeneous network message is the Ethernet UDP protocol, analyzing the header data field of the Ethernet UDP protocol message of the heterogeneous network message according to the Ethernet protocol to obtain the MAC address, the IP address and the UDP port number.
The matching module 1022 is configured to obtain target protocol frame header data of the target protocol type according to the source protocol message frame header data matching.
In this embodiment, since the target frame header data of the corresponding target protocol type is required to be obtained by converting the source protocol message frame header data, matching is required to be performed in the matching module according to the source protocol message frame header data, so as to obtain the target protocol frame header data of the target protocol type uniquely corresponding to the source protocol message frame header data. It can be understood that the corresponding relationship between the source protocol message frame header data and the target protocol frame header data of the target protocol type is stored in the matching module in advance, and in the actual application process, the matching mode stores the corresponding relationship of multiple protocol conversions.
The system supports the conversion of the rapidIO protocol and the Ethernet UDP protocol, and the matching module at least stores the corresponding relation between the rapidIO protocol message frame header data and the Ethernet UDP protocol message frame header data and the corresponding relation between the Ethernet UDP protocol message frame header data and the rapidIO protocol message frame header data. It should be noted that, because RapidIO protocol and ethernet UDP protocol frame header data are different, rapidIO protocol message frame header data and ethernet UDP protocol frame header data are different, so that a correspondence between RapidIO protocol message frame header data and ethernet UDP protocol message frame header data and a correspondence between ethernet UDP protocol message frame header data and RapidIO protocol message frame header data are substantially completely different.
When the source protocol message frame header data is RapidIO protocol message frame header data, obtaining ethernet UDP protocol message frame header data according to matching of RapidIO protocol message frame header data based on a corresponding relation between RapidIO protocol message frame header data and ethernet UDP protocol message frame header data; when the source protocol message frame header data is Ethernet UDP protocol message frame header data, the rapidIO protocol message frame header data is obtained according to the matching of the Ethernet UDP protocol message frame header data based on the corresponding relation between the Ethernet UDP protocol message frame header data and the rapidIO protocol message frame header data. It should be noted that, the foregoing embodiment of the present application is described by taking RapidIO protocol and ethernet UDP protocol as examples, and in the actual application process, other types of protocol conversion may also be included, so long as the matching module stores the correspondence of the header data of the corresponding messages of different protocol types.
Alternatively, the matching module may include a storage unit and a matching unit.
The storage unit is used for storing the relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type.
In this embodiment, in order to implement conversion between heterogeneous network packets of different protocol types, the storage unit stores in advance a relationship between header data of packets of different source protocols and header data of a target protocol type and header data of the target protocol type. The method specifically comprises a key value random memory for storing the corresponding relation between the target protocol frame header data index and the target protocol frame header data key value and a session random memory for storing the target protocol frame header data field of the target protocol type. Taking RapidIO protocol and ethernet UDP protocol as an example, the storage unit includes at least four sub-storage modules, which may be a RapidIO protocol key random access memory, a RapidIO protocol session random access memory, an ethernet UDP protocol key random access memory, and an ethernet UDP protocol session random access memory, respectively.
The ethernet UDP protocol key value random memory is configured to store a relationship between the RapidIO protocol packet header data and an ethernet UDP protocol frame header data index of an ethernet UDP protocol type, and the ethernet UDP protocol session random memory is configured to store an ethernet UDP protocol frame header data field of the ethernet UDP protocol type, where the ethernet UDP protocol frame header data field of the ethernet UDP protocol type and the ethernet UDP protocol frame header data index of the ethernet UDP protocol type stored in the ethernet UDP protocol session random memory have a unique mapping relationship, that is, according to the ethernet UDP protocol frame header data index of the ethernet UDP protocol type, the ethernet UDP protocol frame header data field of the ethernet UDP protocol type uniquely corresponds to the ethernet UDP protocol frame header data index of the ethernet UDP protocol type.
Similarly, the RapidIO protocol key value random memory is used for storing the relation between the ethernet UDP protocol message frame header data and the RapidIO protocol frame header data index of the RapidIO protocol type, and the RapidIO protocol session random memory is used for storing the RapidIO protocol frame header data field of the RapidIO protocol type, where the RapidIO protocol session random memory stores the unique mapping relation between the target protocol frame header data field of the RapidIO protocol type and the RapidIO protocol frame header data index of the RapidIO protocol type, that is, the RapidIO protocol frame header data index according to the RapidIO protocol type can be indexed to the RapidIO protocol frame header data field of the RapidIO protocol type uniquely corresponding to the RapidIO protocol frame header data index of the RapidIO protocol type in the RapidIO protocol session random memory.
The matching unit is used for carrying out hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index, and matching is carried out from the storage unit based on the target protocol frame header data index to obtain target protocol frame header data of a target protocol type.
In this embodiment, the matching unit performs hash computation according to the source protocol message frame header data obtained by the message parsing module to obtain the target protocol frame header data index, and it may be understood that, because a relationship between the source protocol message frame header data and the target protocol frame header data of the target protocol type is stored in the storage unit of the matching module in advance, that is, a correspondence exists between the target protocol frame header data index obtained by performing hash computation on the source protocol message frame header data and the target protocol frame header data of the target protocol type, according to the correspondence, matching may be performed in the storage unit to obtain the target protocol frame header data of the target protocol type.
Optionally, the matching unit is specifically configured to perform assembling according to the source protocol message frame header data to obtain a key value of a hash algorithm, and perform parallel hash computation according to the source protocol message frame header data to obtain a target protocol frame header data index, and match the target protocol frame header data of the target protocol type from the storage unit based on the target protocol frame header data index.
In this embodiment, the key value of the hash algorithm is obtained by assembling the source protocol packet header data, and the ethernet endpoint device sends a packet to the RapidIO endpoint device, where the basic information of the ethernet endpoint device is known as a Mac address: 00:AB:CD:00:00:01, IP address: 1.1.1.1, UDP source port: 1000, virtual basic information of rapidio endpoint device is Mac address: 00:AB:CD:00:00:02, IP address: 1.1.1.2, UDP source port: 2000, header data of the ethernet protocol may be obtained by the above-mentioned packet parsing module: { smac=00:ab: cd:00:00:01, dmac=00:ab: cd: 00:02, sip=1.1.1.1, dip=1.1.2 }, the header data is assembled to obtain a key value of the hash algorithm, and it should be noted that in order to ensure the integrity of data transmission, a Cyclic Redundancy Check (CRC) needs to be performed on the data, so the hash algorithm in this embodiment is a cyclic redundancy check hash algorithm.
And simultaneously, carrying out parallel hash calculation according to source protocol message frame header data to obtain a target protocol frame header data index, wherein in the embodiment, three paths of parallel cyclic redundancy check hash calculation are optionally used to obtain the target protocol frame header data index of the three paths of hash calculation, and the timeliness and throughput rate of conversion can be improved through parallel calculation. Further, as the source protocol message frame header data is subjected to hash calculation to obtain the corresponding relation between the target protocol frame header data index and the target protocol frame header data of the target protocol type, according to the corresponding relation, the target protocol frame header data of the target protocol type can be obtained by matching in the storage unit.
The message Wen Pinjie module 1023 is configured to assemble the target protocol frame header data of the target protocol type and the source protocol message payload data, and convert the assembled target protocol frame header data and the source protocol message payload data to obtain a heterogeneous network message of the target protocol type.
In this embodiment, the matching module obtains the target protocol frame header data of the target protocol type from the source protocol message frame header data, and then assembles the target protocol frame header data of the target protocol type and the source protocol message payload data to obtain the heterogeneous network message of the target protocol type, thereby realizing conversion from the source protocol message to the heterogeneous network message of the target protocol type.
In the foregoing embodiment, a heterogeneous protocol conversion system is provided, including: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module; receiving/transmitting heterogeneous network messages of different protocol types through a protocol interface module; and then converting the received heterogeneous network messages with different protocol types by using a protocol conversion module to obtain the heterogeneous network message with the target protocol type. In this way, through the protocol interface module and the protocol conversion module, the heterogeneous protocol conversion system can receive heterogeneous network messages of different protocol types for conversion and then send the messages, so that the effect of conversion of different heterogeneous protocols is achieved. Therefore, flexible definition of port protocol, width and speed can be realized through the protocol interface module, so that different interconnection scenes can be met, and on the other hand, the conversion module is based on hardware realization, has higher conversion timeliness and throughput rate, reduces the constraint of network deployment, and can also reduce the cost of network deployment.
The heterogeneous protocol conversion system provided by the embodiment of the application is introduced above, and the heterogeneous protocol conversion method is exemplified below with reference to specific embodiments.
Referring to fig. 3, fig. 3 is a flowchart of a heterogeneous protocol conversion method provided by an embodiment of the present application, and in combination with the flowchart shown in fig. 3, the heterogeneous protocol conversion method provided by the embodiment of the present application may include:
s301, receiving heterogeneous network messages of different protocol types.
In this embodiment, for example, the ethernet endpoint device sends a packet to the RapidIO endpoint device, and first receives an ethernet UDP protocol packet of the ethernet endpoint device, specifically, the basic information of the ethernet endpoint device ETH-a includes a Mac address: 00:AB:CD:00:00:01, IP address: 1.1.1.1, UDP source port: 1000, when a message is sent to RapidIO endpoint equipment through the ethernet, the basic information of the RapidIO endpoint equipment RIO-B includes ID:0x01, TT:0x0, TID:0xA, where RapidIO endpoint devices are destination addresses of messages, and in combination with heterogeneous network characteristics, in order for ethernet endpoint devices to send messages to RapidIO endpoint devices, virtual ethernet ETH-B endpoint information of the RapidIO endpoint devices needs to be established at an ethernet side and stored in an ARP table of the ethernet, where the ARP table is a table entry of network devices such as routers that record a corresponding relationship between an IP address and an MAC address, and virtual ethernet ETH-B basic information of the RapidIO endpoint devices includes MAC addresses: 00:AB:CD:00:00:02, IP address: 1.1.1.2, UDP source port: 2000. when the data needs to be forwarded, besides the destination IP address of the opposite party, the MAC address of the opposite party needs to be known, and then whether the MAC address corresponding to the destination IP exists or not needs to be checked in a local ARP table. The present embodiment configures the virtual ethernet ETH-B entry information of the RapidIO endpoint device as described above in the ARP table of the ethernet endpoint device ETH-a. It can be understood that the basic information of the RapidIO endpoint device RIO-B and the basic information of the virtual ethernet ETH-B have a one-to-one correspondence. When the ethernet endpoint device ETH-a sends a UDP packet of the destination port 2000 to the ETH-B device virtualized by the RapidIO endpoint device, the protocol interface module is configured to receive a heterogeneous network packet of an ethernet UDP protocol type and may receive a heterogeneous network packet of an ethernet UDP protocol type sent to the ETH-B device virtualized by the RapidIO endpoint device.
S302, converting the received heterogeneous network messages with different protocol types to obtain the heterogeneous network message with the target protocol type.
In this embodiment, after receiving a heterogeneous network packet of a different protocol type, the packet needs to be sent to a target heterogeneous network, so that the received heterogeneous network packet of a source protocol type needs to be converted into a heterogeneous network packet of a target protocol type, and in the above example, when an ethernet endpoint device ETH-a sends a UDP packet of a destination port 2000 to an ETH-B device virtualized to a RapidIO endpoint device, after receiving the ethernet UDP packet, the ethernet UDP packet needs to be converted based on the RapidIO protocol, so as to obtain a heterogeneous network packet of a RapidIO protocol type, thereby enabling the RapidIO endpoint device to parse and use the packet.
In a possible implementation manner, fig. 4 is a flowchart of a possible method in step S302 provided by an embodiment of the present application, and in combination with the illustration in fig. 4, the converting the received heterogeneous network packet with different protocol types to obtain a heterogeneous network packet with a target protocol type may include:
s3021, analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data.
In this embodiment, in order to convert a source protocol packet into a target protocol packet, the source protocol packet needs to be parsed to obtain load data of the source protocol packet and frame header data of the source protocol packet, it may be understood that the load data of the source protocol packet is data that needs to be transmitted, and the frame header data of the source protocol packet is data information for parsing and effectively propagating based on packets of different protocol types, where the frame header data may include several contents, and at least needs to include a source protocol heterogeneous network address and a target protocol heterogeneous network address, so as to confirm the sending heterogeneous network information and the target heterogeneous network information of the load data.
Specifically, after the source protocol heterogeneous network packet is obtained, the source protocol heterogeneous network packet is split to obtain source protocol packet header data and source protocol packet payload data, and then the source protocol packet header data is parsed based on the source protocol type, where for example, the basic information of the ethernet endpoint device ETH-a includes a Mac address: 00:AB:CD:00:00:01, IP address: 1.1.1.1, UDP source port: 1000, when a message is sent to RapidIO endpoint equipment through the ethernet, virtual ethernet ETH-B basic information of the RapidIO endpoint equipment includes a Mac address: 00:AB:CD:00:00:02, IP address: 1.1.1.2, UDP source port: 2000. the header data of the ethernet protocol obtained after parsing is { smac=00:ab: cd:00:00:01, dmac=00:ab: cd: 00:02, sip=1.1.1.1, dip=1.1.1.2 }.
S3022, obtaining target protocol frame header data of a target protocol type according to the source protocol message frame header data matching.
In this embodiment, source protocol packet header data has been obtained through the above processing, and since the corresponding relationship between the source protocol packet header data and target protocol packet header data of the target protocol type has been stored in the matching module in advance, target protocol packet header data of the target protocol type can be obtained by processing the source protocol packet header data and then according to the corresponding relationship between the source protocol packet header data and the target protocol packet header data of the target protocol type.
Optionally, the matching of the source protocol message frame header data to obtain the target protocol frame header data of the target protocol type may specifically include assembling the source protocol message frame header data to obtain a key value of a hash algorithm, and performing parallel hash computation according to the source protocol message frame header data to obtain a target protocol frame header data index; obtaining target protocol frame header data of a target protocol type based on target protocol frame header data index matching; the relation between the source protocol message frame header data index and the target protocol frame header data of the target protocol type are stored in advance in the storage unit.
In this embodiment, the ethernet endpoint device is connected to send a message to the RapidIO endpoint device for example, where frame header data of the ethernet protocol is { smac=00:ab: cd:00:00:01, dmac=00:ab: cd: 00:02, sip=1.1.1.1.1.2 }, the data is assembled to obtain a key value of a hash algorithm, and three paths of parallel hash computation is performed according to the data, where it can be understood that hash functions of the three paths of parallel hash computation are different, and fig. 5a is a schematic diagram for performing matching according to the embodiment of the present application, and in combination with fig. 5a, parallel hash a, hash B and hash C computation are performed based on frame header data of the ethernet protocol to obtain three paths of target protocol frame header data indexes, respectively, and since a relationship between the source protocol frame header data index and target protocol frame header data of the target protocol type and the target protocol frame header data of the target protocol type are stored in advance, and the three paths of target protocol frame header data of the target protocol type are stored in a storage unit, so that the target protocol frame header data of the target protocol can be obtained by the target protocol frame header data of the target protocol type is unique.
Specifically, referring to fig. 5a, the storage unit includes a target protocol key value subunit and a target protocol session subunit, where the target protocol key value subunit is configured to store a relationship between source protocol packet header data and a target protocol header data index of a target protocol type, and the target protocol session subunit is configured to store a target protocol header data field of the target protocol type, and taking the conversion of the ethernet protocol header data into RapidIO protocol header data as an example, the storage unit may include a RapidIO protocol key value random memory and a RapidIO protocol session random memory.
The RapidIO protocol key value random memory is used for storing the relation between Ethernet UDP protocol message frame header data and RapidIO protocol frame header data indexes of RapidIO protocol types, the RapidIO protocol session random memory is used for storing RapidIO protocol frame header data fields of the RapidIO protocol types, and the RapidIO protocol frame header data fields of the RapidIO protocol types and the RapidIO protocol frame header data indexes of the RapidIO protocol types stored in the RapidIO protocol session random memory have unique mapping relation, that is, the RapidIO protocol frame header data indexes of the RapidIO protocol types can be indexed to the RapidIO protocol frame header data fields of the RapidIO protocol types which are uniquely corresponding to the RapidIO protocol frame header data indexes of the RapidIO protocol types in the RapidIO protocol session random memory.
In this embodiment, based on the relationship between the ethernet UDP protocol packet header data stored in the RapidIO protocol key value random memory and the RapidIO protocol packet header data index of the RapidIO protocol type, it is determined whether the key value of the hash algorithm is consistent with the target protocol packet header data index, if the result of the determination is consistent, the target protocol packet header data field of the target protocol type is mapped according to the target protocol packet header data index, and it can be understood that the mapping relationship between the target protocol packet header data index and the target protocol packet header data field of the target protocol type is stored in a storage unit in advance, for example, the above-described RapidIO protocol session random memory stores a unique mapping relationship between the RapidIO protocol packet header data field of the RapidIO protocol type and the RapidIO protocol packet header data index of the RapidIO protocol type, for example, in the RapidIO protocol key value random memory configuration { session raid=0, smac=00:ab:cd 00:01, dmac=1:00:1.02:1, d=1.0:1, and 1.0:0:1:0:0 { 1.0.0:1.0:1. Referring to fig. 5a, a target protocol frame header data field of a target protocol type can be obtained through a mapping relation between a target protocol frame header data index of a RapidIO protocol key value random memory configuration and a RapidIO protocol session random memory and a target protocol frame header data field of the target protocol type, and finally the target protocol frame header data field of the target protocol type is assembled to obtain target protocol frame header data of the target protocol type.
S3023, assembling the target protocol frame header data of the target protocol type and the source protocol message load data, and converting to obtain the heterogeneous network message of the target protocol type.
In this embodiment, fig. 5b is a schematic diagram of splicing according to the embodiment of the present application, and, with reference to fig. 5b, the target protocol frame header data and the source protocol load data of the target protocol type are already obtained through the above operation, and the target protocol frame header data and the source protocol load data of the target protocol type are spliced to obtain the heterogeneous network packet of the target protocol type. And transmitting the heterogeneous network message of the target protocol type to a protocol interface module.
S303, the heterogeneous network message of the target protocol type is sent to the target heterogeneous network.
In this embodiment, the heterogeneous network packet of the target protocol type is sent to the target heterogeneous network through the protocol interface module. Taking the application as an example, the protocol interface module is configured as a RapidIO protocol interface to perform the sending operation of the heterogeneous network message.
The embodiments of the present application provide some specific implementation manners of the heterogeneous protocol method, and based on this, the embodiments of the present application further provide corresponding topological structure diagrams. The following description will be made of the implementation of the embodiment of the present application from the aspect of functional modularization by taking an example of sending a message by an ethernet endpoint device to a RapidIO endpoint device.
Referring to fig. 6, fig. 6 is a schematic diagram of a topology structure implemented by a heterogeneous protocol method according to an embodiment of the present application, where the schematic diagram includes an ethernet endpoint device ETH-a601, a receiving protocol interface unit 602, a protocol parsing unit 603, a matching unit 604, a converting unit 605, a sending protocol interface unit 606, and a RapidIO endpoint device RIO-B607.
The ethernet endpoint device ETH-a601 includes the basic information Mac address of the ethernet endpoint device ETH-a: 00:AB:CD:00:00:01, IP address: 1.1.1.1, UDP source port: 1000, and an ARP table, where the ARP table includes virtual ethernet ETH-B basic information of RapidIO endpoint devices, specifically Mac address: 00:AB:CD:00:00:02, IP address: 1.1.1.2, UDP source port: 2000. for generating heterogeneous network messages of the ethernet protocol type destined for RapidIO endpoint device RIO-B.
The receiving protocol interface unit 602 is configured to receive an ethernet protocol type heterogeneous network packet sent by the ethernet endpoint device ETH-a.
The protocol parsing unit 603 is configured to parse the ethernet protocol type heterogeneous network packet sent by the ethernet endpoint device ETH-a to obtain ethernet protocol packet header data and ethernet protocol packet payload data.
The matching unit 604 specifically includes a key RAM (random access memory) and a session RAM (random access memory), where the key RAM stores a relationship between ethernet protocol packet header data and a target protocol frame header data index of a RapidIO protocol type, and the session RAM is used to store RapidIO protocol frame header data fields of the RapidIO protocol type. Based on the Ethernet protocol message frame header data and the key value RAM, the relation between the Ethernet protocol message frame header data and the target protocol frame header data index of the rapidIO protocol type is stored, and the session RAM is used for storing the rapidIO protocol frame header data field of the rapidIO protocol type to be matched with the target protocol frame header data field of the target protocol type.
The conversion unit 605 is configured to splice the target protocol frame header data of the target protocol type obtained by the matching unit 604 and the ethernet protocol packet payload data obtained by the protocol parsing unit 603, and convert the packet to obtain a heterogeneous network packet of the RapidIO protocol type.
The sending protocol interface unit 606 is configured to send the heterogeneous network packet of the RapidIO protocol type obtained by the converting unit 605 to the RapidIO endpoint device RIO-B.
The RapidIO endpoint device RIO-B607 is configured to receive a heterogeneous network packet sent by the ethernet endpoint device ETH-a to the RapidIO endpoint device RIO-B and converted into a RapidIO protocol type.
Based on the heterogeneous protocol conversion method provided by the embodiment, the embodiment of the application also provides a heterogeneous protocol conversion device. The heterogeneous protocol conversion device is described below with reference to the embodiments and drawings, respectively.
Fig. 7 is a schematic structural diagram of a heterogeneous protocol conversion device according to an embodiment of the present application. Referring to fig. 7, a heterogeneous protocol conversion device 700 provided in an embodiment of the present application may include:
a receiving module 701, configured to receive heterogeneous network packets of different protocol types;
the conversion module 702 is configured to convert the received heterogeneous network packets with different protocol types to obtain a heterogeneous network packet with a target protocol type;
a sending module 703, configured to send the heterogeneous network packet of the target protocol type to a target heterogeneous network.
In the embodiment of the application, the flexible definition of the port protocol, the width and the rate can be realized through the cooperation of the receiving module 701, the converting module 702 and the sending module 703, so that different interconnection scenes are satisfied, the high conversion timeliness and the high throughput rate are realized, the constraint of network deployment is reduced, and the cost of network deployment is also reduced.
For one embodiment, to improve the conversion timeliness and throughput, the conversion module 702 may specifically include:
the analysis module is used for analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data;
the frame header data matching module is used for matching the frame header data of the source protocol message to obtain target protocol frame header data of a target protocol type;
and the frame header data conversion module is used for splicing the target protocol frame header data of the target protocol type and the source protocol message load data and converting the target protocol frame header data and the source protocol message load data to obtain the heterogeneous network message of the target protocol type.
As an embodiment, to improve the conversion timeliness and throughput, the frame header data matching module may specifically include:
the storage unit is used for storing the relation between the source protocol message frame head data index and the target protocol frame head data of the target protocol type;
the key value assembling unit is used for assembling according to the source protocol message frame header data to obtain a key value of a hash algorithm, and simultaneously carrying out parallel hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index;
And the frame header data matching unit is used for obtaining target protocol frame header data of a target protocol type based on the target protocol frame header data index matching.
The storage unit may specifically include a target protocol key value subunit and a target protocol session subunit, where the target protocol key value subunit is configured to store a relationship between source protocol packet header data and a target protocol header data index of a target protocol type, and the target protocol session subunit is configured to store a target protocol header data field of the target protocol type.
The frame header data matching unit is specifically configured to determine whether a hash algorithm key value obtained by assembling the source protocol message header data is consistent with a target protocol frame header data index stored in the target protocol subunit based on a relationship between the stored source protocol message header data stored in the target protocol subunit and the target protocol frame header data index of a target protocol type; if yes, mapping according to the target protocol frame header data index to obtain a target protocol frame header data field of a target protocol type; and assembling the target protocol frame header data field based on the target protocol type to obtain target protocol frame header data of the target protocol type.
The embodiment of the application also provides corresponding equipment and a computer storage medium, which are used for realizing the scheme provided by the embodiment of the application.
The device comprises a memory and a processor, wherein the memory is used for storing instructions or codes, and the processor is used for executing the instructions or codes so as to enable the device to execute the heterogeneous protocol conversion method according to any embodiment of the application.
The computer storage medium stores code, and when the code is executed, the device executing the code realizes the heterogeneous protocol conversion method according to any embodiment of the application.
The "first" and "second" in the names of "first", "second" (where present) and the like in the embodiments of the present application are used for name identification only, and do not represent the first and second in sequence.
From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the method according to the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The foregoing description of the exemplary embodiments of the application is merely illustrative of the application and is not intended to limit the scope of the application.
Claims (10)
1. A heterogeneous protocol conversion system, the system comprising: a protocol interface module and a protocol conversion module; the protocol interface module is connected with the protocol conversion module;
the protocol interface module is used for receiving/transmitting heterogeneous network messages of different protocol types;
the protocol conversion module is used for converting the received heterogeneous network messages with different protocol types to obtain the heterogeneous network messages with the target protocol types.
2. The system of claim 1, wherein the protocol conversion module comprises a message parsing module, a matching module and a message Wen Pinjie module; the message analysis module, the matching module and the message splicing module are connected in sequence; the message analysis module and the message splicing module are respectively connected with the protocol interface module;
the message analysis module is used for analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data;
the matching module is used for matching the frame header data of the source protocol message to obtain target protocol frame header data of a target protocol type; the corresponding relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type is stored in a matching module in advance;
the message splicing module is used for splicing the target protocol frame header data of the target protocol type and the source protocol message load data and converting the target protocol frame header data and the source protocol message load data to obtain the heterogeneous network message of the target protocol type.
3. The system of claim 2, wherein the message parsing module comprises a message data splitting unit and a message data parsing unit;
The message data splitting unit is used for splitting the received heterogeneous network messages of different protocol types based on the corresponding protocol types to obtain source protocol message frame header data fields and source protocol message load data;
the message data analyzing unit is used for analyzing the source protocol message frame header data field to obtain source protocol message frame header data.
4. The system of claim 2, wherein the matching module comprises a storage unit and a matching unit;
the storage unit is used for storing the relation between the source protocol message frame header data and the target protocol frame header data of the target protocol type;
the matching unit is used for carrying out hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index, and matching the target protocol frame header data of the target protocol type from the storage unit based on the target protocol frame header data index.
5. The system of claim 4, wherein the matching unit is specifically configured to obtain a hash algorithm key value by assembling the source protocol message frame header data, and simultaneously obtain a target protocol frame header data index by performing parallel hash calculation according to the source protocol message frame header data, and obtain target protocol frame header data of a target protocol type by matching the target protocol frame header data index from the storage unit.
6. The system of claim 1, wherein the protocol interface module is configured to receive/transmit heterogeneous network messages of different protocol types in response to heterogeneous network configuration operations of different protocol types.
7. A heterogeneous protocol conversion method, wherein the method is applied to the heterogeneous protocol conversion system of any one of claims 1 to 6, the method comprising:
receiving heterogeneous network messages of different protocol types;
converting the received heterogeneous network messages with different protocol types to obtain heterogeneous network messages with target protocol types;
and sending the heterogeneous network message of the target protocol type to a target heterogeneous network.
8. The method of claim 7, wherein converting the received heterogeneous network messages of different protocol types to obtain the heterogeneous network message of the target protocol type comprises:
analyzing the received heterogeneous network messages with different protocol types based on the corresponding protocol types to obtain source protocol message frame header data and source protocol message load data;
obtaining target protocol frame header data of a target protocol type according to the source protocol message frame header data matching;
Assembling the target protocol frame header data of the target protocol type and the source protocol message load data, and converting the assembled target protocol frame header data and the source protocol message load data to obtain the heterogeneous network message of the target protocol type.
9. The method according to claim 8, wherein said matching the source protocol message header data to obtain target protocol header data of a target protocol type comprises:
assembling according to the source protocol message frame header data to obtain a key value of a hash algorithm, and simultaneously performing parallel hash calculation according to the source protocol message frame header data to obtain a target protocol frame header data index;
obtaining target protocol frame header data of a target protocol type based on the target protocol frame header data index matching; the relation between the source protocol message frame head data index and the target protocol frame head data of the target protocol type are stored in the storage unit in advance.
10. The method according to claim 9, wherein the storage unit includes a target protocol key value subunit and a target protocol session subunit, the target protocol key value subunit is configured to store a relationship between source protocol message frame header data and a target protocol frame header data index of a target protocol type, the target protocol session subunit is configured to store a target protocol frame header data field of a target protocol type, and the obtaining target protocol frame header data of a target protocol type based on the target protocol frame header data index matching includes:
Judging whether a key value of a hash algorithm obtained by assembling according to the source protocol message frame header data is consistent with a target protocol frame header data index of a target protocol type or not based on the relation between the stored source protocol message frame header data stored in the target protocol subunit and the target protocol frame header data index of the target protocol type;
if yes, mapping according to the target protocol frame header data index to obtain a target protocol frame header data field of a target protocol type; the mapping relation between the target protocol frame header data index and the target protocol frame header data field of the target protocol type is stored in a storage unit in advance;
and assembling the target protocol frame header data field based on the target protocol type to obtain target protocol frame header data of the target protocol type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310664828.6A CN116760911A (en) | 2023-06-06 | 2023-06-06 | Heterogeneous protocol conversion system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310664828.6A CN116760911A (en) | 2023-06-06 | 2023-06-06 | Heterogeneous protocol conversion system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116760911A true CN116760911A (en) | 2023-09-15 |
Family
ID=87952559
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310664828.6A Pending CN116760911A (en) | 2023-06-06 | 2023-06-06 | Heterogeneous protocol conversion system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116760911A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117651084A (en) * | 2024-01-26 | 2024-03-05 | 井芯微电子技术(天津)有限公司 | Heterogeneous protocol message processing method and device, electronic equipment and storage medium |
-
2023
- 2023-06-06 CN CN202310664828.6A patent/CN116760911A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117651084A (en) * | 2024-01-26 | 2024-03-05 | 井芯微电子技术(天津)有限公司 | Heterogeneous protocol message processing method and device, electronic equipment and storage medium |
| CN117651084B (en) * | 2024-01-26 | 2024-04-19 | 井芯微电子技术(天津)有限公司 | Heterogeneous protocol message processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7447233B2 (en) | Packet aggregation protocol for advanced switching | |
| CN100348000C (en) | Methods and apparatus for encapsulating a frame for transmission in a storage area network | |
| CN1890943B (en) | Method and architecture for optical networking between server and storage area networks | |
| US6687758B2 (en) | Port aggregation for network connections that are offloaded to network interface devices | |
| US7149819B2 (en) | Work queue to TCP/IP translation | |
| EP1902546B1 (en) | Transparent transport of fibre channel traffic over packet-switched networks | |
| Kumar et al. | The osi model: overview on the seven layers of computer networks | |
| US7394825B2 (en) | 10-gigabit Ethernet line interface apparatus and method of controlling the same | |
| US20040165534A1 (en) | Operations, administration and maintenance (OAM) systems and methods for packet switched data networks | |
| EP2003823B1 (en) | Autonegotiation over an interface for which no autonegotiation standard exists | |
| EP2291959A1 (en) | A method of data delivery across a network fabric in a router or ethernet bridge | |
| US8589776B2 (en) | Translation between a first communication protocol and a second communication protocol | |
| CN116760911A (en) | Heterogeneous protocol conversion system and method | |
| US7639616B1 (en) | Adaptive cut-through algorithm | |
| CN113542941A (en) | Optical fiber channel and Ethernet networking method based on network on chip | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| WO2022147792A1 (en) | Switching system, switching network and switching node | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| Cisco | Designing SDLC, SDLLC, and QLLC Internetworks | |
| CN110493191B (en) | Windows platform data forwarding method and device, electronic equipment and readable storage medium | |
| Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
| Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |