Spaceborne POE measurement and control data transmission multi-interface UDP data sending system and method

Abstract

The application provides a satellite-borne POE measurement and control data transmission multi-interface UDP data sending system and method, which comprises a multi-channel packet assembling module and a pipeline frame assembling module, and comprises the following steps: based on multiple channels, the multi-channel packet assembling module assembles data in a parallel mode to form UDP data packets and sends the UDP data packets to the pipeline frame assembling module; based on the buffering of multiple FIFOs, the pipeline frame assembling module assembles the UDP data packets in a pipeline mode to form Ethernet data frames.The application has the beneficial effects that: it supports parallel reception of multiple channels, each channel of data can support different lengths, different rates and different port numbers; through buffering of data, checksums, lengths and port numbers at the same time, the pipeline mode is adopted, the frame assembling of the next frame of UDP data can be started before the sending of the previous frame of MAC data is completed, and the frame assembling rate of the UDP transmitted data is improved by nearly one time.

Description

Technical Field

[0001] This invention belongs to the field of spaceborne PoE telemetry and control, and in particular relates to a spaceborne PoE telemetry and control data transmission multi-interface UDP data transmission system and method. Background Technology

[0002] The function of the spaceborne PoE telemetry, tracking, and command (PTC) data transmission system is to establish a space-to-ground link in conjunction with the ground-based telemetry, tracking, and command (PTC) data transmission station, and to complete space-to-ground remote control and telemetry as well as ground data transmission tasks. It has the following functions:

[0003] (1) It has data transmission and downlink telemetry functions: it receives data generated by the payload and satellite telemetry information through the network port, and transmits it directly in frames according to the protocol; it modulates and amplifies the digital signal into an X-band data transmission signal suitable for satellite-to-ground wireless channel transmission, and transmits it to the ground through the data transmission antenna.

[0004] (2) It has the function of receiving uplink remote control commands and uplink injection data: it receives remote control commands and high-speed injection data sent by the ground station, converts them into digital signals after despreading and demodulation, and sends the injection data to the satellite computer through the network port.

[0005] PoE (Power over Ethernet) is a technology that utilizes the simultaneous transmission of data and power over an Ethernet network. Its main functions include: 1. Data transmission: Supports speeds of 10Mbps / 100Mbps / 1000Mbps. 2. Power transmission: Transmits power directly over the Ethernet cable.

[0006] The spaceborne PoE telemetry, telemetry and data transmission system adopts PoE technology and has only one external network port, which simultaneously enables power supply and data transmission for the telemetry, telemetry and data transmission system.

[0007] Problems with existing technology:

[0008] (1) Traditional spaceborne FPGA UDP data framing is mostly based on single-channel interface data reception, which cannot realize multi-channel parallel data reception.

[0009] (2) Traditional spaceborne FPGA UDP data framing uses a serial framing method, which has a low rate and requires waiting for the previous frame of data to be sent before the next frame of UDP data framing and verification can be started.

[0010] (3) Traditional spaceborne telemetry, tracking and command data transmission interfaces are complex. Summary of the Invention

[0011] In view of this, the present invention aims to propose a spaceborne PoE telemetry, tracking and command data transmission multi-interface UDP data transmission system and method to solve at least one of the problems existing in the above-mentioned prior art.

[0012] To achieve the above objectives, the technical solution of the present invention is implemented as follows:

[0013] In a first aspect, the present invention provides a spaceborne POE telemetry and control data transmission multi-interface UDP data transmission system, including a multi-channel packet assembly module and a pipeline frame assembly module, wherein the multi-channel packet assembly module is connected to the pipeline frame assembly module.

[0014] The multi-channel packet assembly module includes an arbitration module and multiple channels, each of which includes an interface and a FIFO;

[0015] The interface is connected to the FIFO, and the FIFO is connected to the arbitration module;

[0016] The pipeline framing module includes a UDP checksum calculation module, a MAC framing module, and multiple FIFOs;

[0017] The UDP checksum calculation module is connected to a certain FIFO, and multiple FIFOs output to the MAC framing module. The MAC framing module is connected to the PHY chip through the GMII bus.

[0018] Secondly, based on the same concept, this invention also provides a method for sending multi-interface UDP data in spaceborne PoE telemetry and control data transmission, comprising the following steps:

[0019] S1. Based on multiple channels, the multi-channel packet assembly module assembles data in parallel to form UDP data packets and sends the UDP data packets to the pipeline framing module.

[0020] S2. Based on multiple FIFO buffers, the pipeline framing module assembles UDP packets in a pipeline manner to form Ethernet data frames.

[0021] In step S1, based on multiple channels, the multi-channel packet assembly module assembles data in parallel to form UDP data packets and sends the UDP data packets to the pipeline framing module, including:

[0022] S11, Set the channel priority;

[0023] S12. Based on the cached telemetry data of Channel 1, the telemetry data is packetized and sent to the pipeline framing module under the set conditions according to the priority of Channel 1.

[0024] S13. Based on the second channel of cached betting data, the betting data is packaged and sent to the pipeline framing module under the set conditions according to the priority of the second channel.

[0025] S14. Based on channel three or channel four of the cached remote control data, the remote control data is packetized, and based on the priority of channel three or channel four, under the set conditions, the remote control data packet is sent to the pipeline framing module.

[0026] In step S2, based on the buffers of multiple FIFOs, the pipelined framing module assembles UDP packets in a pipelined manner to form Ethernet data frames, including:

[0027] S21. Set the depth of each FIFO;

[0028] S22. FIFO5 based on cached checksums caches the checksums of UDP packets;

[0029] S23. Based on FIFO6 for caching valid data, cache the valid data of UDP packets;

[0030] S24. Based on the FIFO7 cache destination port number, cache the destination port number of UDP packets;

[0031] S25. Based on the buffer data length, use FIFO8 to buffer the data length of UDP packets;

[0032] S26. Under the set conditions, read the buffers of each FIFO, assemble UDP packets, and send them to the MAC framing module;

[0033] S27. Based on the UDP data packets from step S26, the MAC framing module assembles Ethernet data frames.

[0034] Furthermore, in step S11, the channel priority is set, including:

[0035] The priority value of channel one, which caches telemetry data, is set to 1;

[0036] The priority value of channel 2 for caching the data is set to 2;

[0037] The priority value of channel three, which caches 125 bytes of remote control data, is set to 3;

[0038] The priority value of channel four, which caches 1024 bytes of remote control data, is set to 4;

[0039] The arbitration rules in the arbitration module include: the smaller the priority value, the higher the priority.

[0040] Furthermore, in step S12, based on channel one with cached telemetry data, the telemetry data is packetized, and based on the priority of channel one, under set conditions, the telemetry data packets are sent to the pipeline framing module, including:

[0041] S121, Set the depth of FIFO1;

[0042] S122. Based on the write clock CLK1, write telemetry data into FIFO1;

[0043] S123. Set N1 to 40. If the write count is greater than or equal to N1, a FIFO1 read operation is triggered: read N1 lengths of data from FIFO1 and send the read valid data, destination port number dst_port1, and data length N1 to the pipeline framing module.

[0044] Furthermore, in step S13, based on channel two which caches the betting data, the betting data is packetized, and based on the priority of channel two, under set conditions, the betting data packet is sent to the pipeline framing module, including:

[0045] S131, Set the depth of FIFO2;

[0046] S132. Based on the write clock CLK2, write the up-before data into FIFO2;

[0047] S133. Set N2 to 886. If the write count is greater than or equal to N2 and the FIFO1 read condition is not triggered, then trigger a FIFO2 read operation: read N2 length data from FIFO2 and send the read valid data, destination port number dst_port2 and data length N2 to the pipeline framing module.

[0048] Furthermore, in step S14, based on channel three or channel four of the cached remote control data, the remote control data is packetized, and based on the priority of channel three or channel four, under set conditions, the remote control data packet is sent to the pipeline framing module, including:

[0049] S141. Set the depth of FIFO3; Set the depth of FIFO4;

[0050] S142. Write to buffer FIFO3 based on write clock CLK3; write to buffer FIFO4 based on write clock CLK4.

[0051] S143. Set N3 to 125. If the write count is greater than or equal to N3 and the read conditions of FIFO2 and FIFO1 are not triggered, then trigger a FIFO3 read operation: read N3 length data from FIFO3 and send the read valid data, destination port number dst_port3 and data length N3 to the pipeline framing module.

[0052] The value of N4 is set to 1024. If the write count is greater than or equal to N4 and the read conditions of FIFO3, FIFO2, and FIFO1 are not triggered, a FIFO4 read operation is triggered: read N4 lengths of data from FIFO4 and send the read valid data, the destination port number dst_port4, and the data length N4 to the pipeline framing module.

[0053] Furthermore, in step S22, the checksum is cached based on FIFO5 of the cached checksum, including:

[0054] Based on UDP packets, the UDP checksum calculation module calculates the checksum and caches it in FIFO5.

[0055] Furthermore, in step S26, under set conditions, the buffers of each FIFO are read, UDP packets are formed, and they are sent to the MAC framing module, including:

[0056] If the reset signal is valid or the previous Ethernet data frame transmission has been completed, and FIFO5 is not empty, then read the buffers of FIFO8 and FIFO7 to obtain the length L of the data to be read and the destination port number Port. Read the address of FIFO5 to obtain the checksum sum of the data to be sent. Using the data length L, read the data of length L from FIFO6 to obtain the valid UDP data to be sent, and send the obtained L, Port, data, and sum to the MAC framing module.

[0057] Furthermore, in step S27, based on the UDP packets from step S26, the MAC framing module assembles an Ethernet data frame, including:

[0058] Based on UDP packets, IP packets are assembled according to the IP protocol;

[0059] Ethernet data frames are composed of IP packets according to the Ethernet protocol.

[0060] Compared with existing technologies, the spaceborne PoE telemetry, tracking, and command (PTC) data transmission multi-interface UDP data transmission system and method described in this invention have the following advantages:

[0061] (1) Traditional spaceborne FPGA UDP data framing is mostly based on single-channel interface data reception. This invention achieves parallel reception of multiple data channels through multiple buffers and arbitration. Multiple data channels can simultaneously support different lengths, different rates and different port numbers.

[0062] (2) Traditional spaceborne FPGA UDP data framing uses a serial framing method, which has a low rate. It is necessary to wait for the previous frame of data to be sent before the next frame of UDP data framing can begin. In contrast, this invention caches the data, checksum, length and port simultaneously. The UDP data transmission packet assembly adopts a pure pipeline method. The next frame of data can be started before the previous frame of data is sent (after the current frame of data is assembled), which improves the UDP data transmission rate by nearly 100%.

[0063] (3) Traditional spaceborne telemetry and control data transmission has complex external interfaces, while POE telemetry and control data transmission has only one network port, which can complete all data transmission and power supply work. Attached Figure Description

[0064] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0065] Figure 1 This is a schematic diagram of the overall structure according to an embodiment of the present invention;

[0066] Figure 2 This is a schematic diagram of the overall process described in an embodiment of the present invention.

[0067] Figure 3 This is a schematic diagram of the multi-channel packet assembly module process described in an embodiment of the present invention;

[0068] Figure 4 This is a schematic diagram of the pipeline framing module process described in an embodiment of the present invention. Detailed Implementation

[0069] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0070] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0071] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art will understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0072] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0073] like Figures 1 to 4 As shown, the spaceborne PoE telemetry, tracking, and command (PTC) data transmission multi-interface UDP data transmission system includes a multi-channel packet assembly module and a pipelined framing module. The multi-channel packet assembly module is connected to the pipelined framing module. The multi-channel packet assembly module includes an arbitration module and multiple channels. Each channel includes an interface and a FIFO (First In First Out in FPGA is a first-in-first-out data buffer implemented based on dual-port RAM, mainly used for cross-clock domain data transmission and rate matching). The interface is connected to the FIFO, and the FIFO is connected to the arbitration module. The pipelined framing module includes a UDP checksum calculation module, a MAC framing module, and multiple FIFOs. The UDP checksum calculation module is connected to a specific FIFO, and all FIFOs output to the MAC framing module. The MAC framing module is connected to the PHY chip via the GMII bus.

[0074] The method for sending UDP data via multiple interfaces in a spaceborne PoE telemetry and control system includes the following steps:

[0075] S1. Based on multiple channels, the multi-channel packet assembly module assembles data in parallel to form UDP data packets and sends the UDP data packets to the pipeline framing module.

[0076] S2. Based on multiple FIFO buffers, the pipeline framing module assembles UDP packets in a pipeline manner to form Ethernet data frames.

[0077] Specifically as follows:

[0078] The main functions of the satellite PoE telemetry, telemetry, and data transmission integrated unit are to receive satellite-to-ground remote control data, and to transmit satellite-to-ground telemetry and payload data. The PoE telemetry, telemetry, and data transmission integrated unit has lower-level machine functions, capable of responding to satellite administrator polling, completing its own telemetry data acquisition and transmission, and receiving indirect commands from satellite administrators. The main functions of the PoE telemetry, telemetry, and data transmission integrated unit are as follows:

[0079] (1) Remote control: satellite-to-ground remote control data reception;

[0080] (2) Telemetry: Transmission of satellite-to-ground telemetry data;

[0081] (3) High-speed uplink: It has a high-speed uplink channel to realize high-speed uplink of load data;

[0082] (4) Data transmission: The load data is transmitted down through the data transmission channel;

[0083] (5) Lower-level machine: self-telemetry data acquisition and response to satellite polling (self-telemetry data transmission and indirect command reception).

[0084] Among them, the remote control, high-speed injection, and lower-level machine self-telemetry acquisition (single-machine self-telemetry) all require the telemetry and control data transmission to receive and packetize the corresponding data, and output the data through the network port according to the UDP protocol.

[0085] Single-unit telemetry frame: The OBC polls the telemetry and control data transmission for the status of the single unit at a frequency of 1 second / time. The telemetry and control data transmission packages its own status and sends it to the OBC. The length of the single-unit telemetry frame is 40 bytes.

[0086] High-speed uploading frame: The telemetry and control data transmission will send the uploading data to the destination single machine via UDP packets. The data length of the UDP packet is 886 bytes. The data stream is a continuous high-speed data stream when the uploading mode is valid.

[0087] Remote control frame: The length of the uplink remote control frame is 125 Bytes, 1024 Bytes, etc., and it is generally once per second.

[0088] like Figure 2 As shown, the overall process involves processing telemetry data generated by the FPGA itself, or high-speed uploading data or remote control data acquired through the satellite-to-ground telemetry and control link, into packets of different lengths.

[0089] It mainly includes 4 steps:

[0090] 1. Telemetry data generated by the FPGA itself, or high-speed uploading data or remote control data acquired through the satellite-to-ground telemetry and control link, are packetized, buffered, and arbitrated for output according to different lengths;

[0091] 2. Pipeline UDP data framing is performed on the packet output data of the multi-channel packet assembly module, and the pipeline framing module obtains a complete UDP packet field.

[0092] 3. Obtain a complete UDP packet field, and then insert the UDP packet field into it according to the IP protocol to form an IP packet data frame; after obtaining a complete IP packet, insert the IP packet field into it according to the Ethernet frame structure protocol to form an Ethernet frame packet data frame.

[0093] 4. An Ethernet frame packet is then sent to the PHY chip via the GMII or RGMII interface. The PHY chip converts the data into an electrical signal that can be transmitted via a network cable and then sends it to other devices.

[0094] like Figure 3 As shown, the telemetry data generated by the FPGA itself, or the high-precision data or remote control data obtained through the satellite-to-ground telemetry and control link, are packetized and cached according to different lengths.

[0095] For its own telemetry, it writes to the buffer FIFO1 according to the write clock CLK1. If the write count is ≥ N1 (N1=40), it triggers a FIFO1 read operation, reads N1 length of data from FIFO1, and gives the read data, destination port number dst_port1 and data length N1 to the subsequent pipelined UDP data sending framing module.

[0096] For high-speed data uploading, write to buffer FIFO2 according to the write clock CLK2. If the write count is ≥ N2 (N2=886) and the FIFO1 read condition is not triggered, then a FIFO2 read operation is triggered to read N2 length data from FIFO2, and the read data, destination port number dst_port2 and data length N2 are given to the subsequent pipelined UDP data sending framing module.

[0097] For 125-byte remote control data, write it to buffer FIFO3 according to the write clock CLK3. If the write count is ≥ N3 (N3=125) and the read conditions of FIFO2 and 1 are not triggered, then a FIFO3 read operation is triggered to read N3-byte data from FIFO3. The read data, the destination port number dst_port3, and the data length N3 are given to the subsequent pipelined UDP data transmission framing module.

[0098] For 1024-byte remote control data, write it to buffer FIFO4 according to the write clock CLK4. If the write count is greater than or equal to N4 (N4=1024) and the read conditions of FIFO3, 2, and 1 are not triggered, then a FIFO4 read operation is triggered to read N4-byte data from FIFO4. The read data, the destination port number dst_port4, and the data length N4 are then given to the subsequent pipelined UDP data framing module.

[0099] When two or more of the above four judgment conditions are valid at the same time, the arbitration module is required to determine which channel data to read. The arbitration is based on setting the priority of the four channels, with the priority of the four channels defined as 1 to 4, where priority 1 is the highest and priority 4 is the lowest. If multiple conditions are met at the same time, the branch data with the highest priority will be read first. The priority can be set according to the use case and the importance of the data.

[0100] The depth of FIFO1 is 512 bytes; the depth of FIFO2 is 8192 bytes; the depth of FIFO3 is 1024 bytes; and the depth of FIFO4 is 8192 bytes. This ensures that all data can be buffered for at least 8 frames. The FIFO depth can be set according to the usage scenario and data rate.

[0101] The input to the pipeline framing module is the data output from the previous stage, the port number, and the UDP data length L. The data is buffered in four buffers. Since the data, data checksum, port number, data length, and other information need to be used in UDP checksum calculation, and the UDP packet assembly also needs length and port information after the checksum calculation is completed, as well as the length information in the IP protocol, while other information is basically a fixed value or a value that can be directly calculated, so it does not need to be buffered.

[0102] If each time the UDP checksum is calculated first based on the input data, then the UDP data and header are obtained according to the length and destination port number, the IP header content is obtained according to the length, the data is assembled according to the MAC protocol, and then output to the PHY chip through the GMII bus, then the subsequent UDP checksum framing process can only begin after the current MAC frame data has been transmitted.

[0103] like Figure 4 As shown, in order to improve the throughput rate, a pipelined framing module is adopted. By caching the input data, checksum, length and port number information, it is possible to approximately achieve relatively independent UDP data pipeline checksum and subsequent MAC protocol framing.

[0104] The data is processed by performing UDP header checksum calculation on the data based on the N bytes of data, length, destination port number, IP address, and other information read from the previous level. The checksum is then stored in FIFO5.

[0105] At the same time, N bytes of data are cached and stored in FIFO6;

[0106] At the same time, the destination port number data is cached and stored in FIFO7;

[0107] At the same time, the data length is cached and stored in FIFO8;

[0108] The depth of FIFO6 is 32 bytes; the depth of FIFO7 is 16384 bytes; the depth of FIFO8 is 32 bytes. It guarantees that at least 16 frames of data, or a length or port number, will be buffered; the FIFO depth can be set according to the usage scenario and data rate.

[0109] As long as FIFO5 is not full, the pipeline framing module can continuously receive data from the multi-channel packet assembly module and buffer the data, checksum, length, and port number. If FIFO5 is full, it will pause receiving data from the multi-channel packet assembly module.

[0110] When the reset signal is valid or the previous frame of MAC data has been sent through interfaces such as GMII, and FIFO5 is not empty, then an address FIFO8 and FIFO7 buffer are read to obtain the current data length L to be read and the destination port number Port. An address FIFO5 is read to obtain the current data checksum sum to be sent. Then, using the data length L to be read, L address data are read from the FIFO6 buffer to obtain the current UDP data part data to be sent. The obtained L, Port, data, and sum are given to the subsequent MAC framing module.

[0111] This completes the UDP packet assembly, which involves obtaining the UDP packet header and data portion. The header includes the sender's (fixed value) and receiver's ports, as well as the UDP length (calculated based on L, equal to L+8) and UDP checksum. Table 1 shows the UDP packet header fields.

[0112] Table 1

[0113]

[0114] This gives you a complete UDP packet field.

[0115] A complete UDP packet field is obtained, and then the UDP packet field is inserted into an IP packet data frame according to the IP protocol.

[0116] The data area is filled with the UDP packet fields obtained, while the others, such as version, service type, header length, time to live, protocol, source IP address, destination IP address, and options, are all fixed values.

[0117] The total IP length is calculated based on L, which equals L+28. The header checksum is also calculated directly from the data.

[0118] Once a complete IP packet is obtained, the IP packet fields are then inserted into the data area of ​​the Ethernet frame according to the Ethernet frame structure protocol. Other fields, such as preamble, SFD, destination address, source address, and type, are fixed values, and the CRC is calculated directly from the data.

[0119] Once a complete Ethernet frame packet is obtained, it is sent to the PHY chip via an interface such as GMII. The PHY chip converts the data into differential electrical signals that can be transmitted via Ethernet cable and then sends them to the satellite computer or other devices such as switches. Commonly used PHY chips include 88E1111.

[0120] After the current Ethernet frame packet data frame transmission is completed, the next frame of UDP data transmission will be enabled. If FIFO5 is not empty, the address FIFO8 and FIFO7 buffers will be read again to obtain the current data length L and Port to be read; the address FIFO5 will be read to obtain the current single data checksum sum; and the L address data will be read from the FIFO6 buffer through the read L to obtain the current UDP data part data to be sent; the obtained L, Port, data, and sum will be given to the subsequent MAC framing module; and then the above operation will be repeated.

[0121] This method is applicable to transmission rates of 10Mbps, 100Mbps, 1000Mbps, and other situations with more input data interfaces. At the same time, by increasing the number of buffer types in the pipeline framing module, it can also be applied to situations where information such as IP address and MAC address changes.

[0122] Advantages and beneficial effects of the present invention:

[0123] (1) Traditional spaceborne FPGA UDP data framing is mostly based on single-channel interface data reception. This invention achieves parallel reception of multiple data channels through multiple buffers and arbitration. Multiple data channels can simultaneously support different lengths, different rates and different port numbers.

[0124] (2) Traditional spaceborne FPGA UDP data framing uses a serial framing method, which has a low rate. It is necessary to wait for the previous frame of data to be sent before the next frame of UDP data framing can begin. In contrast, this invention caches the data, checksum, length and port simultaneously. The UDP data transmission packet assembly adopts a pure pipeline method. The next frame of data can be started before the previous frame of data is sent (after the current frame of data is assembled), which improves the UDP data transmission rate by nearly 100%.

[0125] (3) Traditional spaceborne telemetry and control data transmission has complex external interfaces, while POE telemetry and control data transmission has only one network port, which can complete all data transmission and power supply work.

[0126] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for transmitting multi-interface UDP data in spaceborne PoE telemetry and control data transmission, characterized in that: The method is realized by a satellite-borne POE measurement and control data transmission multi-interface UDP data sending system, and comprises the following steps: S1, based on multiple channels, a multi-channel packet assembly module assembles data in a parallel manner to form UDP data packets and sends the UDP data packets to a pipeline framing module; S2, based on the buffering of multiple FIFOs, the pipeline framing module frames the UDP data packets in a pipeline manner to form Ethernet data frames; In step S1, based on multiple channels, a multi-channel packet assembly module assembles data in a parallel manner to form UDP data packets and sends the UDP data packets to a pipeline framing module, comprising: S11, setting the priority of the channel; S12, based on channel one buffering telemetry data, assembling telemetry data, based on the priority of channel one, under the set conditions, sending the telemetry data packet to the pipeline framing module; S13, based on channel two buffering uplink data, assembling uplink data, based on the priority of channel two, under the set conditions, sending the uplink data packet to the pipeline framing module; S14, based on channel three or channel four buffering remote control data, assembling remote control data, based on the priority of channel three or channel four, under the set conditions, sending the remote control data packet to the pipeline framing module; In step S2, based on the buffering of multiple FIFOs, the pipeline framing module frames the UDP data packets in a pipeline manner to form Ethernet data frames, comprising: S21, setting the depth of each FIFO; S22, based on FIFO5 buffering the checksum, buffering the checksum of the UDP data packet; S23, based on FIFO6 buffering valid data, buffering the valid data of the UDP data packet; S24, based on FIFO7 buffering the destination port number, buffering the destination port number of the UDP data packet; S25, based on FIFO8 buffering the data length, buffering the data length of the UDP data packet; S26, under the set conditions, reading the buffering of each FIFO, assembling the UDP data packet, and sending it to the MAC framing module; S27, based on the UDP data packet of step S26, the MAC framing module assembles the Ethernet data frame; The satellite-borne POE measurement and control data transmission multi-interface UDP data sending system comprises a multi-channel packet assembly module and a pipeline framing module, the multi-channel packet assembly module is connected with the pipeline framing module; The multi-channel packet assembly module comprises an arbitration module and multiple channels, each channel comprises an interface and a FIFO; The interface is connected with the FIFO, and the FIFO is connected with the arbitration module; The pipeline framing module comprises a UDP checksum calculation module, a MAC framing module and multiple FIFOs; The UDP checksum calculation module is connected with a certain FIFO, multiple FIFOs are output to the MAC framing module, and the MAC framing module is connected with a PHY chip through a GMII bus.

2. The space-borne POE TT&C multi-interface UDP data sending method according to claim 1, characterized in that: In step S11, setting the priority of the channel, comprising: The priority value of channel one buffering telemetry data is set to 1; The priority value of channel two buffering uplink data is set to 2; The priority value of channel three which caches 125 bytes of remote control data is set to 3; The priority value of channel four which caches 1024 bytes of remote control data is set to 4; The arbitration rule of the arbitration module includes: the smaller the priority value, the higher the priority.

3. The space-borne POE TT&C multi-interface UDP data sending method according to claim 2, characterized in that: In step S12, based on channel one which caches telemetry data, the telemetry data is packetized, and based on the priority of channel one, the telemetry data packet is sent to the pipeline framing module under the set condition, including: S121, set the depth of FIFO1; S122, based on the write clock CLK1, write the telemetry data into FIFO1; S123, set the value of N1 to 40, if the write count >= N1, trigger a FIFO1 read operation once: read N1 length data from FIFO1, and send the read valid data, destination port number dst_port1 and data length N1 to the pipeline framing module.

4. The space-borne POE TT&C multi-interface UDP data sending method according to claim 3, characterized in that: In step S13, based on channel two which caches updata, the updata is packetized, and based on the priority of channel two, the updata packet is sent to the pipeline framing module under the set condition, including: S131, set the depth of FIFO2; S132, based on the write clock CLK2, write the updata into FIFO2; S133, set the value of N2 to 886, if the write count >= N2, and the FIFO1 read condition is not triggered, trigger a FIFO2 read operation once: read N2 length data from FIFO2, and send the read valid data, destination port number dst_port2 and data length N2 to the pipeline framing module.

5. The space-borne POE TT&C data transmission multi-interface UDP data sending method according to claim 4, characterized in that: In step S14, based on channel three or channel four which caches remote control data, the remote control data is packetized, and based on the priority of channel three or channel four, the remote control data packet is sent to the pipeline framing module under the set condition, including: S141, set the depth of FIFO3; set the depth of FIFO4; S142, based on the write clock CLK3, write into the cache FIFO3; based on the write clock CLK4, write into the cache FIFO4; S143, set the value of N3 to 125, if the write count >= N3, and the FIFO2, FIFO1 read condition is not triggered, trigger a FIFO3 read operation once: read N3 length data from FIFO3, and send the read valid data, destination port number dst_port3 and data length N3 to the pipeline framing module; Set the value of N4 to 1024, if the write count >= N4, and the FIFO3, FIFO2, FIFO1 read condition is not triggered, trigger a FIFO4 read operation once: read N4 length data from FIFO4, and send the read valid data, destination port number dst_port4 and data length N4 to the pipeline framing module.

6. The space-borne POE TT&C multi-interface UDP data sending method according to claim 1, characterized in that: In step S22, based on the FIFO5 which caches checksum, the checksum is cached, including: Based on the UDP data packet, the UDP checksum calculation module calculates the checksum and caches it to FIFO5.

7. The space-borne POE TT&C data transmission multi-interface UDP data sending method according to claim 1, characterized in that: In step S26, under the set condition, the cache of each FIFO is read, a UDP data packet is formed, and it is sent to the MAC framing module, including: If the reset signal is valid or the previous Ethernet data frame transmission has been completed, and FIFO5 is not empty, then the cache of address FIFO8 and FIFO7 is read to obtain the data length L to be read and the destination port number Port, the address FIFO5 is read to obtain the checksum sum of the data to be sent, the L length data is read from FIFO6 according to the data length L to be read to obtain the effective data data to be sent, and the obtained L, Port, data, and sum are sent to the MAC framing module.

8. The space-borne POE TT&C multi-interface UDP data sending method according to claim 1, characterized in that: In step S27, based on the UDP data packet of step S26, the MAC framing module forms an Ethernet data frame, including: Based on the UDP data packet, an IP data packet is formed according to the IP protocol; Based on the IP data packet, an Ethernet data frame is formed according to the Ethernet protocol.

Images