CN116032862A - Method for transmitting BE data by TTE system with low delay and TTE system - Google Patents

Abstract

The invention relates to a method for transmitting BE data with low delay of a TTE system and the TTE system, wherein primary data frame type conversion is added in TTE end system driving, conversion of key BE data frames and RC data frames is realized according to a BE and RC virtual link mapping relation table, the priority of key BE traffic is improved on the basis of not influencing the transmission priority of an original TTE network PCF, TT, RC service, and efficient and reliable operation of upper BE application is ensured; the driving software modifies the scheduling rule of the bottom data, the upper application does not need to make any modification and adaptation, the transmission delay of the appointed BE service data is effectively reduced, and the transmission instantaneity and reliability of the appointed BE data service are improved; in some high traffic mixed BE contexts, the transmission delay of a given BE service can BE reduced from 20us by about 10us.

Description

Method for transmitting BE data by TTE system with low delay and TTE system

Technical Field

The present invention relates to the field of network transmission, and in particular, to a method for transmitting BE data with low delay in a TTE system, and a TTE system.

Background

In recent years, real-time network transmission requirements have brought new demands and challenges to real-time networks. Time triggered ethernet (TTEthernet, time Triggered Ethernet) combines the certainty, fault tolerance mechanism and real-time performance of time triggered technology with the flexibility, dynamic performance and "best effort" of classical ethernet, providing a real-time network with high bandwidth, real-time, certainty and compatibility with IEEE802.3 legacy ethernet, and thus, TTE networks are of great interest.

To meet the needs of different applications, SAE AS6802 protocol specifies that the TTE network supports three different real-Time and accuracy data communications, namely, time-Triggered (TT), rate-Control (RC), best Effort (BE) messages. The three data frame priority relationships are: TT traffic > RC traffic > BE traffic.

For the management of TTE networks, it is necessary to provide a network management protocol (SNMP), a configuration loading protocol (615A) service for transmission of traffic data. Because of the characteristic of 'best effort' of BE data, if the real-time performance and reliability in the bottom layer transmission process are not guaranteed, the problem that data frame loss or communication delay is increased in SNMP and 615A applications which depend on BE data transmission at the upper layer can BE caused. The SNMP and 615A applications use a socket protocol stack interface to realize data communication, and if the communication interface is to be modified into an RC communication mode, the workload of transplanting and adapting application codes is complicated.

Disclosure of Invention

In order to overcome at least one defect in the prior art, the embodiment of the application provides a method for transmitting BE data with low delay for a TTE system and the TTE system.

In a first aspect, a method for transmitting BE data with low delay in a TTE system is provided, including:

judging whether the BE data frame to BE sent is a key data frame or not;

if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

after receiving the RC data frame, analyzing the received RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table;

if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application;

and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

In one embodiment, the BE/RC mapping table stores the mapping between source node information, destination node information, and virtual link number VL of the RC data frame for the BE data frame.

In one embodiment, encapsulating a BE data frame to BE transmitted into an RC data frame according to a BE/RC mapping table includes:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to source end node information and destination end node information according to a BE/RC mapping relation table;

adding an RC Ethernet frame header for a BE data frame to BE sent to obtain an RC data frame; the RC Ethernet frame header comprises destination node information of the RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE transmitted, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE transmitted.

In one embodiment, the method further comprises:

the MTU value in the network device driver of each end system in the TTE system is modified.

In a second aspect, there is provided a TTE system comprising:

the first TTE end system is used for judging whether a BE data frame to BE sent is a key data frame or not; if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

the second TTE end system is used for analyzing the received RC data frame after receiving the RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table; if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application; and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

In one embodiment, the BE/RC mapping table stores the mapping between source node information, destination node information, and virtual link number VL of the RC data frame for the BE data frame.

In one embodiment, the transmit TTE-side system is further configured to:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to source end node information and destination end node information according to a BE/RC mapping relation table;

adding an RC Ethernet frame header for a BE data frame to BE sent to obtain an RC data frame; the RC Ethernet frame header comprises destination node information of the RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE transmitted, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE transmitted.

In a third aspect, a TTE system is provided, comprising:

the TTE end system is used for judging whether the BE data frame to BE sent is a key data frame or not; if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

the TTE exchange end system is used for analyzing the received RC data frame after receiving the RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table; if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application; and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

In one embodiment, the BE/RC mapping table stores the mapping between source node information, destination node information, and virtual link number VL of the RC data frame for the BE data frame.

In one embodiment, the TTE-side system is further configured to:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to source end node information and destination end node information according to a BE/RC mapping relation table;

adding an RC Ethernet frame header for a BE data frame to BE sent to obtain an RC data frame; the RC Ethernet frame header comprises destination node information of the RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE transmitted, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE transmitted.

Compared with the prior art, the application has the following beneficial effects: according to the method for transmitting BE data by the TTE system with low delay and the TTE system, one-level data frame type conversion is added in a TTE end system driver, and key BE data frames and RC data frames are converted according to a BE and RC virtual link mapping relation table; the driving software modifies the scheduling rule of the bottom data, the upper application does not need to make any modification and adaptation, the transmission delay of the appointed BE service data is effectively reduced, and the transmission instantaneity and reliability of the appointed BE data service are improved; in some high traffic mixed BE contexts, the transmission delay of a given BE service can BE reduced from 20us by about 10us.

Drawings

The present application may be better understood by reference to the following description taken in conjunction with the accompanying drawings, which are incorporated in and form a part of this specification, together with the following detailed description. In the drawings:

FIG. 1 shows a block diagram of a TTE system according to an embodiment of the present application;

FIG. 2 shows a block flow diagram of transmitting BE data frames according to an embodiment of the present application;

FIG. 3 shows a schematic diagram of a conversion of BE data frames and RC data frames;

FIG. 4 shows a block flow diagram of receiving BE data frames according to an embodiment of the present application;

FIG. 5 shows a block diagram of a TTE system according to another embodiment of the present application;

fig. 6 illustrates a method for low latency transmission of BE data by a TTE system according to an embodiment of the application.

Detailed Description

Exemplary embodiments of the present application will be described hereinafter with reference to the accompanying drawings. In the interest of clarity and conciseness, not all features of an actual embodiment are described in the specification. It will of course be appreciated that in the development of any such actual embodiment, numerous implementation-specific decisions may be made to achieve the developers' specific goals, and that these decisions may vary from one implementation to another.

It should be noted that, in order to avoid obscuring the present application with unnecessary details, only the device structures closely related to the solution according to the present application are shown in the drawings, and other details not greatly related to the present application are omitted.

It is to be understood that the present application is not limited to the described embodiments due to the following description with reference to the drawings. In this context, embodiments may be combined with each other, features replaced or borrowed between different embodiments, one or more features omitted in one embodiment, where possible.

Fig. 1 shows a block diagram of a TTE system according to an embodiment of the application. In this embodiment, the TTE system includes two end systems, namely, a first end system and a second end system, and hereinafter, the first end system is taken as a transmitting end system, and the second end system is taken as a receiving end system as an example, and a workflow of the TTE system is described. The TTE system also comprises a TTE switch for realizing the forwarding of data.

According to the topology structure of the TTE system, RC virtual link configuration for transmitting BE service is added into the system through a configuration tool, and a corresponding BE/RC mapping relation table is generated according to the relation between source end node information and destination end node information of the virtual link. In the system configuration stage, the RC configuration of all end systems and TTE switches, and the BE/RC mapping relation table are updated, wherein the RC configuration can BE routing information, scheduling information and the like. Table 1 is a BE/RC mapping table.

TABLE 1

src_mac1	dst_mac1	VL1
			src_mac2	dst_mac2	VL2
src_mac3	dst_mac3	VL3
			src_mac4	dst_mac4	VL4

Because BE service can BE converted into RC flow at the bottom layer for transmission, the data field of the RC data frame is BE data frame, the maximum length of the data field is 1500 bytes, and 18 bytes occupied by BE frame header and check are subtracted, so that the maximum transmission unit MTU driven by network equipment of an end system is modified to 1482.

Fig. 2 shows a flow chart of transmission of BE data frames according to an embodiment of the present application, referring to fig. 2, the specific implementation functions of the first end system are as follows:

the SNMP/615A application calls a socket api interface to send a BE data frame, and the BE data frame reaches the bottom layer of the protocol stack to send a data interface; judging whether the BE data frame is a key data frame according to the protocol type and the port number carried in the BE data frame, wherein the key data frame is SNMP data or 615A data, if not, carrying out transmission scheduling of the BE data frame according to common BE data frame processing, if so, analyzing the BE data frame, and extracting source node information and destination node information of the BE data frame;

and then traversing the BE/RC mapping relation table to obtain virtual link numbers VL of RC data frames corresponding to the source end node information and the destination end node information.

Then, adding an RC Ethernet frame header for the BE data frame to obtain an RC data frame, wherein the BE data frame is used as a data load of the RC data frame; the RC Ethernet frame header comprises destination node information of the RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame, the destination node information of the RC data frame comprises a fixed domain ctmaker with 4 bytes high and a virtual link number VL of the RC data frame with 2 bytes low, and the frame length field length represents the byte length of the BE data frame. Fig. 3 shows a schematic diagram of the conversion of BE data frames and RC data frames.

The second end system is configured to receive the BE data frame, fig. 4 is a flow chart illustrating a procedure for receiving the BE data frame according to an embodiment of the present application, and referring to fig. 4, a specific implementation function of the second end system is as follows:

after the drive bottom layer of the second end system receives the RC data frame, analyzing the received RC data frame, extracting source node information and virtual link VL of the RC data frame, traversing a BE/RC mapping relation table, judging that the received RC data frame is the RC data frame obtained by encapsulation of the BE data frame if mapping corresponding to the source node information and the virtual link VL is found, namely, the BE data frame required by the upper application, converting the received RC data frame into the BE data frame, and transmitting the BE data frame to the upper application; if the mapping corresponding to the source node information and the virtual link VL is not found, judging that the received RC data frame is not the RC data frame obtained by encapsulation of the BE data frame, and storing the received RC data frame into an RC receiving buffer. Here, the received RC data frame is converted into the BE data frame, specifically, the ethernet frame header and the CRC field of the RC data frame may BE removed, and the data field be_frame is a complete BE data frame.

Fig. 5 shows a block diagram of a TTE system according to another embodiment of the application. In this embodiment, the TTE system includes a TTE end system and a TTE exchange end system, where the TTE exchange end system is an end system in a TTE exchange. In this embodiment, the TTE end system is a transmitting end system, the TTE exchange end system is a receiving end system, and specific implementation functions of the TTE end system and the TTE exchange end system are identical to those of the first TTE end system and the second TTE end system in the foregoing embodiment, which are not described in detail herein.

Fig. 6 illustrates a method for low latency transmission of BE data by a TTE system according to an embodiment of the application, the method including:

step S11, judging whether the BE data frame to BE sent is a key data frame or not; here, whether the BE data frame is a key data frame is determined according to the protocol type and the port number carried in the BE data frame, where the key data frame is SNMP data or 615A data.

Step S12, if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame; here, the BE/RC mapping relation table stores mapping relation among source node information, destination node information of the BE data frame, and virtual link number VL of the RC data frame.

Step S13, after receiving the RC data frame, analyzing the received RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent according to the BE/RC mapping relation table;

in the step, the received RC data frame is analyzed, source node information and virtual link VL of the RC data frame are extracted, a BE/RC mapping relation table is traversed, if mapping corresponding to the source node information and the virtual link VL is found, the received RC data frame is judged to BE the RC data frame obtained by encapsulation of the BE data frame, namely the BE data frame required by upper layer application, and if mapping corresponding to the source node information and the virtual link VL is not found, the received RC data frame is judged not to BE the RC data frame obtained by encapsulation of the BE data frame.

Step S14, if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application;

in this step, the received RC data frame is converted into a BE data frame, specifically, the ethernet frame header and the CRC field of the RC data frame may BE removed, and the data field is the complete BE data frame.

Step S15, if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, the received RC data frame is stored in an RC receiving buffer memory.

The method of the embodiment of the application improves the priority of the key BE traffic on the basis of not influencing the transmission priority of the original TTE network PCF, TT, RC service and ensures the efficient and reliable operation of the upper BE application.

In one embodiment, encapsulating a BE data frame to BE transmitted into an RC data frame according to a BE/RC mapping table includes:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to source end node information and destination end node information according to a BE/RC mapping relation table;

adding an RC Ethernet frame header for a BE data frame to BE sent to obtain an RC data frame; the RC Ethernet frame header comprises destination node information of the RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE transmitted, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE transmitted.

In one embodiment, the method further comprises: the MTU value in the network device driver of each end system in the TTE system is modified.

Because BE service can BE converted into RC flow at the bottom layer for transmission, the data field of the RC data frame is BE data frame, the maximum length of the data field is 1500 bytes, and 18 bytes occupied by BE frame header and check are subtracted, so that the maximum transmission unit MTU driven by network equipment of an end system is modified to 1482.

In summary, the present application has the following technical effects:

according to the method for transmitting BE data by the TTE system with low delay and the TTE system, one-level data frame type conversion is added in a TTE end system driver, and key BE data frames and RC data frames are converted according to a BE and RC virtual link mapping relation table; the driving software modifies the scheduling rule of the bottom data, the upper application does not need to make any modification and adaptation, the transmission delay of the appointed BE service data is effectively reduced, and the transmission instantaneity and reliability of the appointed BE data service are improved; in some high traffic mixed BE contexts, the transmission delay of a given BE service can BE reduced from 20us by about 10us.

The foregoing is merely various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method for low latency transmission of BE data in a TTE system, comprising:

judging whether the BE data frame to BE sent is a key data frame or not;

if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

after receiving an RC data frame, analyzing the received RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table;

if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application;

and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

2. The method of claim 1, wherein the BE/RC mapping table stores mapping relationships among source node information, destination node information of the BE data frame, and virtual link number VL of the RC data frame.

3. The method of claim 2, wherein encapsulating the BE data frame to BE transmitted into an RC data frame according to a BE/RC mapping table comprises:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to the source end node information and the destination end node information according to the BE/RC mapping relation table;

adding an RC Ethernet frame header for the BE data frame to BE sent to obtain the RC data frame; the RC Ethernet frame header comprises destination node information of an RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE sent, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE sent.

4. The method of claim 1, wherein the method further comprises:

the MTU value in the network device driver of each end system in the TTE system is modified.

5. A TTE system, comprising:

the first TTE end system is used for judging whether a BE data frame to BE sent is a key data frame or not; if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

the second TTE end system is used for analyzing the received RC data frame after receiving the RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table; if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application; and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

6. The system of claim 5, wherein the BE/RC mapping table stores mapping relationships among source node information, destination node information of the BE data frame, and virtual link number VL of the RC data frame.

7. The system of claim 6 wherein the transmit TTE-side system is further configured to:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to the source end node information and the destination end node information according to the BE/RC mapping relation table;

adding an RC Ethernet frame header for the BE data frame to BE sent to obtain the RC data frame; the RC Ethernet frame header comprises destination node information of an RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE sent, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE sent.

8. A TTE system, comprising:

the TTE end system is used for judging whether the BE data frame to BE sent is a key data frame or not; if the BE data frame to BE sent is a key data frame, packaging the BE data frame to BE sent into an RC data frame according to a BE/RC mapping relation table, and carrying out sending scheduling on the RC data frame;

the TTE exchange end system is used for analyzing the received RC data frame after receiving the RC data frame, and judging whether the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent or not according to the BE/RC mapping relation table; if the received RC data frame is the RC data frame obtained by packaging the BE data frame to BE sent, converting the received RC data frame into the BE data frame, and sending the BE data frame to an upper application; and if the received RC data frame is not the RC data frame obtained by packaging the BE data frame to BE sent, storing the received RC data frame into an RC receiving buffer memory.

9. The system of claim 8, wherein the BE/RC mapping table stores mapping relationships among source node information, destination node information of the BE data frame, and virtual link number VL of the RC data frame.

10. The system of claim 9 wherein the TTE-side system is further configured to:

analyzing the BE data frame to BE sent, and extracting source node information and destination node information of the BE data frame to BE sent;

acquiring virtual link numbers VL of RC data frames corresponding to the source end node information and the destination end node information according to the BE/RC mapping relation table;

adding an RC Ethernet frame header for the BE data frame to BE sent to obtain the RC data frame; the RC Ethernet frame header comprises destination node information of an RC data frame, source node information of the RC data frame and a frame length field length, the source node information of the RC data frame is consistent with the source node information of the BE data frame to BE sent, the destination node information of the RC data frame comprises a fixed domain ctmaker and a virtual link number VL of the RC data frame, and the frame length field length represents the byte length of the BE data frame to BE sent.

Images