Multi-interface data interaction communication method based on crossbar
By adopting a Crossbar-based multi-interface data interaction communication method in satellite communication systems, the problem of large overhead of interface data flow interaction resources in traditional systems is solved, and the effect of reducing system complexity and cost and improving reliability and flexibility is achieved.
Patent Information
- Application Number
- CN202411818643.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-11
- Publication Date
- 2025-03-28
AI Technical Summary
In traditional satellite communication systems, the cost of interface data flow interaction resources is high, resulting in high system design complexity, high cost and difficulty in ensuring reliability.
Using a multi-interface data interaction communication method based on Crossbar, by setting cache and cross-clock domain processing in the interface processing module, an internal standard interface is designed to connect to the Crossbar switching module for scheduling arbitration and response, realizing communication frame format decoupling and data interaction of different types of interfaces, different rates, and different protocols.
It reduces the complexity and cost of system design, improves product development efficiency, supports a large number of real-time control interfaces and medium- and low-speed service interface interaction requirements at different rates and protocols, and achieves high reliability and flexible data interaction.
Smart Images
Figure CN119729249A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the technical field of satellite communication, relates to satellite-borne digital processing, and specifically to a crossbar-based multi-interface data interactive communication method. Background Art
[0002] With the development trend of satellite communication systems towards large-scale, integrated and networked systems, the number of digital processing payload services and control interfaces has increased, the business volume and internal interaction requirements have increased, and the complexity of interface protocols has increased. The traditional data interaction communication mechanism adopts an interface-to-interface design, which has the problems of large resource overhead, poor software code versatility, low reuse, and difficulty in ensuring reliability. Summary of the invention
[0003] In view of the shortcomings of the prior art, the purpose of the present invention is to provide a multi-interface data interaction communication method based on crossbar to solve the technical problem of high resource overhead of interface data stream interaction in the prior art.
[0004] In order to solve the above technical problems, the present invention adopts the following technical solutions to achieve the above problems:
[0005] A multi-interface data interactive communication method based on crossbar, the method comprising the following steps:
[0006] Step 1: Design of multi-interface data interaction communication mechanism:
[0007] Step 101: any interface processing module sets a buffer for receiving and sending and performs cross-clock domain processing. All interface processing modules are connected to a Crossbar switching module through an internal standard interface.
[0008] Step 102, when a certain interface needs to send data to other interfaces, a data exchange application is submitted through the internal standard interface, and the Crossbar switching module performs scheduling arbitration and gives a response. The input interface that receives the response can send data in the next clock.
[0009] Step 2: Internal standard interface design:
[0010] The internal standard interface contains at least three elements. The first element is the port request of the Crossbar switching module. The valid range of the request signal covers the number of ports of the Crossbar switching module. The second element is the port request response of the Crossbar switching module. The bit width is consistent with the request. The third element is that the data is sent in a packet burst format, and an enable signal is given to indicate the start and end of valid data.
[0011] Step three: Design the internal sending method of interface data.
[0012] Step 4: Design the internal receiving method of interface data.
[0013] Step 5: Interface data exchange reliability design:
[0014] A timeout mechanism is added when sending a response ACK of a waiting port scheduling request inside the interface processing module, and a timer is started when a switch request REQ is sent. After the timeout, the switch request REQ is cleared, and then the switch request REQ is resent or the current data packet is discarded.
[0015] The present invention also has the following technical features:
[0016] The specific method of step three includes the following steps:
[0017] Step 301: The interface processing module sets a receiving buffer, and first stores the received and processed data packets into the receiving buffer.
[0018] Step 302: read the data packet from the receiving buffer and obtain the destination port information of the Crossbar switching module to which the data packet is destined.
[0019] Step 303: Generate a switch request REQ according to the destination port information obtained in step 302 and send it to the Crossbar switch module.
[0020] Step 304, after a certain interface processing module in step 303 sends an output request, when the requested output interface does not have multiple inputs, the arbitrator of the Crossbar switching module gives a response ACK after waiting for 1 clock cycle; when the requested output interface has multiple input requests, the Crossbar switching module performs port scheduling, and the interface processing module cannot send data before receiving the response ACK.
[0021] Step 305: When the interface processing module receives the response ACK and it is consistent with the request port, the data packet is output to the Crossbar switching module in the next clock cycle, and the switching request REQ is cleared at the same time.
[0022] Step 306: The internal sending of subsequent data packets repeats steps 302 to 305.
[0023] The specific method of step 4 includes the following steps:
[0024] Step 401: The interface processing module sets a sending buffer, and the sending buffer is used to buffer data packets received from the Crossbar.
[0025] Step 402, the interface processing module detects the receiving signal of the internal standard interface of the Crossbar switching module in real time, starts receiving data when the data enable is valid, and ends the reception of a data packet when the enable end indication is given.
[0026] Step 403: while receiving the data packet from the Crossbar switching module, store the data packet in the sending buffer.
[0027] Step 404: read the data packet from the sending buffer and send it according to the interface sending protocol.
[0028] Step 405 , the internal reception and interface transmission of subsequent data packets repeat steps 402 to 404 .
[0029] Compared with the prior art, the present invention has the following technical effects:
[0030] (I) The multi-interface data interaction communication method of the present invention can solve the problem of large resource overhead of interface data stream interaction in wireless communication systems, especially satellite communication systems, and can reduce the complexity and cost of system design, improve product development efficiency, and is suitable for application scenarios with a large number of real-time control interfaces with different rates and protocols and medium and low-speed business interface interaction requirements in digital processing loads of all projects and models.
[0031] (II) Aiming at the real-time interaction requirements of a large number of medium and low-speed control interfaces in the design of large-scale digital processing loads, the present invention proposes a multi-interface data interaction communication method based on Crossbar. By setting cache and cross-clock domain processing in the transceiver interface processing module, and designing an internal standard interface to connect to the Crossbar switching module for scheduling arbitration and response, the communication frame format is decoupled, and data interaction between transceiver interfaces of different types of interfaces, different rates, and different protocols is supported, and the number and rate of interfaces and the on-demand expansion of the rate are supported.
[0032] (III) The present invention supports data exchange between any interfaces, while the traditional method can only transmit data one-to-one.
[0033] (IV) The present invention supports interface interaction data of different medium and low rates and protocols. The interface interaction is decoupled from the interface communication frame format. The interface cache design can support coarse-grained interface interaction rate control of upper-layer applications.
[0034] (V) The present invention can be implemented using FPGA, has low power consumption, and can be IP-based and universal.
[0035] (VI) The present invention introduces a timeout mechanism to make the crossbar-based interface interactive communication method highly reliable when applied in a space environment.
[0036] (VII) The method of the present invention is simple to implement, has reliable communication, adjustable throughput, expandable interface scale, and strong IP-based module versatility. After simulation and actual test verification, the above-mentioned device can support 3.2Gbps data throughput at 50MHz working clock through 16 interfaces, and communication interaction rates below 200Mbps between interfaces can be processed at line speed. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Figure 1 It is a structural diagram of the multi-interface data interactive communication method module based on Crossbar.
[0038] Figure 2 This is a schematic diagram of the structure of a 16-interface communication interaction device of a multi-interface data interaction communication method based on Crossbar in an application example.
[0039] Figure 3 It is a schematic diagram of the frame start signal and enable signal of the internal standard interface data packet in the application example.
[0040] Figure 4 The figure is a schematic diagram of the internal transmission process of interface data in the application example.
[0041] Figure 5 This is a schematic diagram of the frame start signal and enable signal when the interface data is internally sent in the application example.
[0042] The specific contents of the present invention are further explained in detail below in conjunction with embodiments. DETAILED DESCRIPTION
[0043] It should be noted that, unless otherwise specified, all modules and methods in the present invention adopt modules and methods known in the prior art.
[0044] Specific embodiments of the present invention are given below. It should be noted that the present invention is not limited to the following specific embodiments, and all equivalent changes made on the basis of the technical solution of this application fall within the protection scope of the present invention.
[0045] Example:
[0046] This embodiment provides a multi-interface data interactive communication method based on crossbar, such as Figure 1 As shown, the method comprises the following steps:
[0047] Step 1: Design of multi-interface data interaction communication mechanism:
[0048] Step 101: any interface processing module sets a buffer for receiving and sending and performs cross-clock domain processing. All interface processing modules are connected to a Crossbar switching module through an internal standard interface.
[0049] Step 102, when a certain interface needs to send data to other interfaces, a data exchange application is submitted through the internal standard interface, and the Crossbar switching module performs scheduling arbitration and gives a response. The input interface that receives the response can send data in the next clock.
[0050] In this step, the interface processing module adopts a commonly used interface processing module known in the art.
[0051] In this step, the Crossbar switching module adopts a commonly used Crossbar switching module known in the art. The Crossbar switching module only provides scheduling and data exchange functions, does not perform data buffering internally, is decoupled from all interface communication frame formats, and can realize interaction of any type of interface and any frame format.
[0052] The technical advantage of step one is that the mechanism for interface data interaction based on Crossbar supports flexible intercommunication between interfaces of different rates and protocols through Crossbar and can be adjusted as needed. The universality of the Crossbar interface data interaction mechanism is achieved through standardization of internal standard interfaces and IP-based Crossbar switching modules.
[0053] Step 2: Internal standard interface design:
[0054] The internal standard interface contains at least three elements. The first element is the port request of the Crossbar switching module. The valid range of the request signal covers the number of ports of the Crossbar switching module. The second element is the port request response of the Crossbar switching module. The bit width is consistent with the request. The third element is that the data is sent in a packet burst format, and an enable signal is given to indicate the start and end of valid data.
[0055] In this step, the Crossbar switching module works according to the enable signal to achieve decoupling of the interactive data and the interface communication frame format.
[0056] In this step, the data bit width and working clock of the internal interaction of the Crossbar switching module can be adjusted according to the interface and overall interaction bandwidth requirements. For example, if a single interface is required to have a maximum rate of 100Mbps and 16 interfaces are required to interact, and considering that the exchange acceleration ratio of the Crossbar switching module is at least 2, the data bit width can be designed to be 8bit and the clock to be 25MHz, supporting the line-speed interaction of 16 100Mbps interfaces.
[0057] The technical advantage of step 2 is that the start and end of data interaction are located through the internal standard interface design, so that the internal data exchange is decoupled from the frame format of each interface.
[0058] Step 3: Design of internal transmission method of interface data:
[0059] Step 301: The interface processing module sets a receiving buffer, and stores the received and processed data packets into the receiving buffer first.
[0060] Step 302: read the data packet from the receiving buffer and obtain the destination port information of the Crossbar switching module to which the data packet is destined.
[0061] In step 302, the Crossbar destination port information may be obtained by carrying it in the frame header, determining it according to the relationship between frame type data flow, or external input.
[0062] Step 303: Generate a switch request REQ according to the destination port information obtained in step 302 and send it to the Crossbar switch module.
[0063] In step 303, the exchange request REQ may be in the form of a bitmap, where each bit corresponds to a Crossbar port.
[0064] Step 304, after an interface processing module in step 303 sends an output request, when the requested output interface does not have multiple inputs, the arbitrator of the Crossbar switching module gives a response ACK after waiting for 1 clock cycle; when the requested output interface has multiple input requests, the Crossbar switching module performs port scheduling, and the interface processing module cannot send data before receiving the response ACK, otherwise an output interface data conflict will occur.
[0065] Step 305: When the interface processing module receives the response ACK and it is consistent with the request port, the data packet is output to the Crossbar switching module in the next clock cycle, and the switching request REQ is cleared at the same time.
[0066] Step 306: The internal sending of subsequent data packets repeats steps 302 to 305.
[0067] Step 4: Design of internal receiving method of interface data:
[0068] Step 401: The interface processing module sets a sending buffer, and the sending buffer is used to buffer data packets received from the Crossbar.
[0069] Step 402, the interface processing module detects the receiving signal of the internal standard interface of the Crossbar switching module in real time, starts receiving data when the data enable is valid, and ends the reception of a data packet when the enable end indication is given.
[0070] Step 403: while receiving the data packet from the Crossbar switching module, store the data packet in the sending buffer.
[0071] Step 404: read the data packet from the sending buffer and send it according to the interface sending protocol.
[0072] Step 405 , the internal reception and interface transmission of subsequent data packets repeat steps 402 to 404 .
[0073] Step 5: Interface data exchange reliability design:
[0074] In this step, for the request-response multi-interface data interactive communication mechanism in step one, the response data may be erroneous due to factors such as single particle flips in a space radiation environment, and the interface processing module cannot receive the correct request response ACK information, resulting in a reliability risk problem in which the internal sending module of the interface is stuck.
[0075] A timeout mechanism is added when sending a response ACK for waiting port scheduling request inside the interface processing module. A timer is started when the exchange request REQ is sent (the timeout period can be flexibly set). After the timeout, the exchange request REQ is cleared, and then the exchange request REQ is resent or the current data packet is discarded.
[0076] The technical advantage of step five is that by introducing a timeout mechanism in the sending state of the interface processing module, when the port scheduling request response information is erroneous due to factors such as the space environment, the reliability problem of internal sending stuck can be solved.
[0077] Application examples:
[0078] This application example provides a crossbar-based multi-interface data interactive communication method based on the above embodiment, and the method includes the following steps:
[0079] Step 1: Design of multi-interface data interaction communication mechanism:
[0080] This application example provides a design of a 16-interface communication interaction device, which can better support data line-speed interaction between 16 interfaces with different rates and protocol requirements. Figure 2 The internal standard interfaces REQ and ACK are designed according to bitmap mapping, the data width is designed to be 8 bits, the clock is 50MHz, and it can support single-port 200Mbps line speed interaction, and the overall data throughput is 3.2Gbps.
[0081] Step 2: Internal standard interface design:
[0082] In this application example, Figure 3 As shown, each internal standard interface contains 8 signals, which are defined as follows:
[0083] Step 201, req[15:0]: the interface processing module sends an output interface request signal to the Crossbar switch module. Each bit corresponds to one output interface. '1' means the request is valid, and '0' means the request is invalid.
[0084] Step 202, ack[15:0]: Crossbar switch module output interface request response, any bit is '1' indicates that the corresponding port output request is passed.
[0085] Step 203, i_sof: the data start positioning signal sent by the interface processing module to the Crossbar switching module, marking the first 8-bit data, '1' is valid.
[0086] Step 204, i_dv: data enable signal sent by the interface processing module to the Crossbar switching module, '1' is valid, and the data is valid only when dv is valid.
[0087] Step 205, i_data[7:0]: data signal sent from the interface processing module to the Crossbar switching module, with a bit width of 8 bits.
[0088] Step 206, o_sof: a data start positioning signal output by the Crossbar switching module, identifying the first 8-bit data, '1' is valid.
[0089] Step 207, o_dv: data enable signal output by the Crossbar switching module, '1' is valid, and the data is valid only when dv is valid.
[0090] Step 208, o_data[7:0]: data signal output by the Crossbar switching module, 8 bits wide.
[0091] Step 3: Design of internal transmission method of interface data:
[0092] The schematic diagram of the internal transmission process of the interface data in this application example is as follows Figure 4 shown.
[0093] Step 301, the enable signal of each data packet should be continuously pulled high during the entire packet transmission process, and the frame start signal is only pulled high for one clock transmission cycle to indicate the start of the frame, and the data bit width is 8 bits. The frame start signal and the enable signal are shown in Figure 5 shown.
[0094] Step 302, if the data meets the conditions of step 301, the interface processing module processes the data packet and receives the buffer according to the 8-bit width, then reads the data from the receiving buffer and obtains the Crossbar destination port information to which the data is going. The following use case uses a certain byte in the first 4-byte internal header of the data frame to indicate the destination port of the data packet.
[0095] XX 02XX XX FF FF FF FF 00 0C 03 04 05 06 07 08 09 0A 73 85
[0096] Step 303, generating a switching request REQ according to the destination port information. For example, in step 302, the request generated by the use case is REQ=0x0002, that is, the second bit (starting from 1) is set to '1'.
[0097] Note: An input interface can output to multiple ports at the same time, such as REQ=0x0802.
[0098] Step 304, after port 2 sends an output request in step 303, when output interface 2 does not have multiple inputs, the Crossbar arbitrator gives a response after waiting for 1 clock cycle (according to the use case ACK=0x0002); when output interface 2 has multiple input requests, the Crossbar arbitrator performs output scheduling matching according to a certain scheduling algorithm, and the interface processing module cannot send data before receiving the response ACK.
[0099] Step 305, when the interface processing module receives the response signal and it is consistent with the request port, according to the above use case when ACK = REQ = 0x0002, the next clock cycle can output the data packet to the Crossbar switching module, and clear REQ at the same time; i_sof corresponding to the first 8-bit data outputs 1, and i_dv is valid; when the data packet is sent, the enable signal i_dv is pulled low and invalid.
[0100] Step 306: The subsequent data frame is sent and the process from step 302 to step 305 is repeated.
[0101] Step 4: Design of internal receiving method of interface data:
[0102] Step 401: The interface processing module sets an 8-bit sending buffer for buffering data packets received from the Crossbar.
[0103] Step 402, the interface processing module detects the receiving signal of the Crossbar standard interface in real time, and starts receiving data when the data start o_sof and the data enable o_dv are both pulled high and valid, and indicates that the reception of a data packet is completed when the enable o_dv is pulled low.
[0104] Step 403: While receiving the data packet from the Crossbar, store it in the 8-bit transmission buffer.
[0105] Step 404, read the data packet from the sending buffer and send it according to the interface sending protocol. The sending module can be associated with the communication frame format to perform frame format validity detection, or it can be sent in a frame format decoupled manner.
[0106] Step 405, the subsequent data packets are internally received and sent through the interface, repeating steps 402 to 405.
[0107] Step 5: Interface data exchange reliability design:
[0108] A timeout mechanism is added when sending a response ACK of a waiting port scheduling request inside the interface processing module, and a timer is started when a switch request REQ is sent. After the timeout, the switch request REQ is cleared, and then the switch request REQ is resent or the current data packet is discarded.
[0109] In this application example, after simulation and actual test verification, the 16 interfaces can support a data throughput of 3.2 Gbps at a 50 MHz operating clock, and the communication interaction rate between interfaces below 200 Mbps can be processed at line speed.
Claims
1. A multi-interface data interactive communication method based on crossbar, characterized in that: The method comprises the following steps: Step 1: Design of multi-interface data interaction communication mechanism: Step 101, any interface processing module receives and sends data and sets a buffer and performs cross-clock domain processing. All interface processing modules are connected to a Crossbar switching module through an internal standard interface. Step 102, when a certain interface needs to send data to other interfaces, a data exchange application is submitted through the internal standard interface, and the Crossbar switching module performs scheduling arbitration and gives a response. The input interface that receives the response can send data in the next clock; Step 2: Internal standard interface design: The internal standard interface contains at least three elements. The first element is the port request of the Crossbar switch module. The valid range of the request signal covers the number of ports of the Crossbar switch module. The second element is the port request response of the Crossbar switch module. The bit width is consistent with the request. The third element is that the data is sent in a packet burst format, and an enable signal is given to indicate the start and end of the valid data. Step 3: Design of internal transmission method of interface data; Step 4: Design of internal receiving method of interface data; Step 5: Interface data exchange reliability design: A timeout mechanism is added when sending a response ACK of a waiting port scheduling request inside the interface processing module, and a timer is started when a switch request REQ is sent. After the timeout, the switch request REQ is cleared, and then the switch request REQ is resent or the current data packet is discarded.
2. The crossbar-based multi-interface data interactive communication method according to claim 1, characterized in that: The specific method of step three includes the following steps: Step 301, the interface processing module sets a receiving buffer, and first stores the received and processed data packets into the receiving buffer; Step 302, read the data packet from the receiving buffer and obtain the destination port information of the Crossbar switching module to which the data packet is destined; Step 303: Generate a switch request REQ according to the destination port information obtained in step 302 and send it to the Crossbar switch module; Step 304, after a certain interface processing module in step 303 sends an output request, when the requested output interface does not have multiple inputs, the arbitrator of the Crossbar switching module gives a response ACK after waiting for 1 clock cycle; when the requested output interface has multiple input requests, the Crossbar switching module performs port scheduling, and the interface processing module cannot send data before receiving the response ACK; Step 305, when the interface processing module receives the response ACK and it is consistent with the request port, the next clock cycle data packet is output to the Crossbar switching module, and the switching request REQ is cleared at the same time; Step 306: The internal sending of subsequent data packets repeats steps 302 to 305.
3. The crossbar-based multi-interface data interactive communication method according to claim 1, characterized in that: The specific method of step 4 includes the following steps: Step 401, the interface processing module sets a sending buffer, and the sending buffer is used to buffer the data packets received from the Crossbar; Step 402, the interface processing module detects the receiving signal of the internal standard interface of the Crossbar switching module in real time, starts receiving data when the data enable is valid, and ends the reception of a data packet when the enable end indication is given; Step 403, while receiving the data packet from the Crossbar switching module, the data packet is stored in the transmission buffer; Step 404, read the data packet from the sending buffer and send it according to the interface sending protocol; Step 405 , the internal reception and interface transmission of subsequent data packets repeat steps 402 to 404 .