A deep space K-band ground high-speed data injection method and system

Abstract

The application discloses a deep space K-band ground high-speed data injection method and system, and the method comprises the following steps: obtaining a remote control injection demand instruction through front-end software; obtaining category information of the remote control injection demand instruction, determining a matching target coding strategy based on the category information; coding the remote control injection demand instruction based on the target coding strategy to obtain a coded file; forwarding the coded file to station control software and one or more other demand receivers based on a preset multi-software layered transmission protocol, and then transparently forwarding the coded file to baseband software to obtain transmission result data; determining a dynamic regulation and control strategy based on a data flow rate monitored by the baseband software, and adjusting the cache size of a cache space based on the dynamic regulation and control strategy to obtain a target cache space for caching the transmission result data. Through diversified injection data processing, a multi-software layered transmission protocol and dynamic caching, the application realizes efficient, stable and reliable remote control data injection of the K-band ground section in a deep space task.

Description

Technical Field

[0001] This application relates to the field of deep space exploration communication technology, and in particular to a ground-based high-speed data injection method and system for the K-band deep space. Background Technology

[0002] Highly efficient remote-controlled injection technology is one of the key technologies in deep space exploration missions, mainly used for the remote control and data management of spacecraft and scientific payloads. This technology sends commands, parameters, software updates, and fault recovery strategies to the spacecraft through a ground system, supporting the autonomous operation of the spacecraft in complex space environments. It is a core guarantee for achieving dynamic adjustments to scientific missions and extending their on-orbit lifespan.

[0003] Currently, efficient remote control injection technology relies on the efficient data processing and reliable transmission capabilities of ground software systems. In terms of data processing, traditional uplink injection protocols simply categorize requirements into remote control command injection and software refactoring injection, making it difficult to handle complex scenarios such as refined data types and large file segmentation, resulting in low coding efficiency. At the transmission level, ground system software at different levels often uses a single transmission protocol without differentiated design based on real-time or data volume requirements. Furthermore, fixed caching mechanisms cannot adapt to dynamic changes in data flow, easily leading to transmission delays or data loss.

[0004] In other words, current remote injection technology suffers from several problems: insufficient flexibility in the injection protocol, making it difficult to quickly handle diverse and large-volume injection needs, thus limiting uplink efficiency; unreasonable selection of software interface transmission protocols, with real-time commands and large data transmissions not optimized as needed, leading to response delays or reduced reliability; and rigid cache management strategies, which cannot dynamically adjust resources according to the data inflow rate, causing cache overflow or resource waste, affecting the overall system performance and task security.

[0005] Therefore, improving the processing efficiency, transmission efficiency, and injection reliability of uplink injected data from the spacecraft's ground segment is an urgent problem to be solved. Summary of the Invention

[0006] To address the aforementioned issues, embodiments of this application provide a method and system for high-speed ground data injection in the deep space K-band, an electronic device, a computer-readable storage medium, and a computer program product.

[0007] Firstly, in order to solve the above-mentioned technical problems, this application provides a method for high-speed ground data injection in the deep space K-band, comprising:

[0008] The remote control injection requirement command is obtained by acquiring the interactive interface through the front-end software.

[0009] Obtain the type information of the remote control injection request command, and determine the matching target encoding strategy based on the type information;

[0010] The remote control injection request command is encoded based on the target encoding strategy to obtain an encoded file;

[0011] Based on a preset multi-software layered transmission protocol, the encoded file is forwarded to the station control software and one or more other receiving parties. After the station control software receives the encoded file, it is transparently forwarded to the baseband software to obtain the transmission result data.

[0012] A dynamic control strategy is determined based on the data flow rate monitored in real time by the baseband software, and the cache size of the cache space is adjusted based on the dynamic control strategy to obtain a target cache space, which is used to cache the transmission result data for reading.

[0013] The beneficial effects are:

[0014] In the technical solution provided by the embodiments of this application, remote control injection request commands collected by the interactive interface are obtained through front-end software; the type information of the remote control injection request commands is obtained, and a matching target encoding strategy is determined based on the type information; the remote control injection request commands are encoded based on the target encoding strategy to obtain an encoded file; based on a preset multi-software layered transmission protocol, the encoded file is forwarded to the station control software and one or more other request receivers, and after being received by the station control software, the encoded file is transparently forwarded to the baseband software to obtain transmission result data; a dynamic control strategy is determined based on the data flow rate monitored in real time by the baseband software, and the cache size of the cache space is adjusted based on the dynamic control strategy to obtain a target cache space for caching transmission result data for reading. Therefore, this application, through the front-end software, station control software, and baseband software of the ground software system, realizes diversified injection data processing according to the type information of remote control injection request commands, multi-software layered transmission protocol design, and dynamic cache design, thereby improving the processing efficiency, transmission efficiency, and injection reliability of K-band ground segment uplink injection data in deep space missions, and effectively solving problems in injection data processing efficiency, software transmission efficiency and reliability, and high-speed transmission data loss.

[0015] Furthermore, the step of obtaining the type information of the remote control injection request instruction and determining the matching target encoding strategy based on the type information includes:

[0016] Obtain the demand type and corresponding execution method of the remote control injection demand instruction, as well as the internal CAN message injection format of the remote control injection demand;

[0017] Based on the demand type, the execution method, and the internal CAN message injection format, the type information of the remote control injection demand command is obtained;

[0018] Based on the pre-defined correspondence between category information and function identifiers, the target function identifier corresponding to the category information is determined;

[0019] Based on the matching relationship between preset function identifiers and encoding strategies, a target encoding strategy that matches the target function identifier is determined.

[0020] Furthermore, when the remote injection request instruction is a software reconstruction injection request for a large file, the matching target encoding strategy is a parallel distributed encoding strategy.

[0021] The process of encoding the remote control injection request command based on the target encoding strategy to obtain an encoded file includes:

[0022] Obtain the segmentation requirements for the large file in the software refactoring injection requirements, and segment the large file based on the segmentation requirements to obtain multiple sub-file index blocks;

[0023] Obtain the file hash value and sub-file block number of the sub-file corresponding to the multiple sub-file index blocks;

[0024] Parallel encoding processing is performed on multiple encoding nodes based on the file hash value and the sub-file block sequence number to obtain encoded data blocks corresponding to multiple sub-file index blocks; each sub-file index block corresponds one-to-one with an encoding node.

[0025] The encoding result corresponding to each sub-file index block is obtained based on the sub-file information and the encoded data block;

[0026] After obtaining the encoding results of all encoding nodes, the encoded data blocks in the encoding results are parsed to obtain parsed data;

[0027] Based on the sub-file block sequence number, the parsed data corresponding to multiple sub-file index blocks are sorted to obtain the encoded file corresponding to the remote control injection requirement instruction.

[0028] Furthermore, based on a preset multi-software layered transmission protocol, the encoded file is forwarded to the station control software and one or more other receiving parties. After receiving the encoded file, the station control software transparently forwards it to the baseband software to obtain transmission result data, including:

[0029] The front-end software encapsulates the encoded file to obtain UDP data packets;

[0030] Based on a preset multi-software layered transmission protocol, the UDP data packets are forwarded to the station control software and one or more other receiving parties via UDP multicast transmission.

[0031] After receiving the UDP data packet, the station control software transparently forwards the UDP data packet to the baseband software via the TCP protocol to obtain the transmission result data.

[0032] Furthermore, the step of encapsulating the encoded file using the front-end software to obtain UDP data packets includes:

[0033] A real-time data frame transmission protocol is adopted, and real-time transmission data frames are obtained based on the frame header and the data field corresponding to the encoded file.

[0034] The real-time transmitted data frame is encapsulated as an application data field using UDP to obtain the corresponding UDP data packet.

[0035] Furthermore, the step of forwarding the UDP data packets to the station control software and one or more other receiving parties via UDP multicast transmission includes:

[0036] Within a preset time period, the UDP data packets are forwarded three times consecutively to the station control software and one or more other receiving parties via UDP multicast transmission.

[0037] If the number of UDP packets received by the station control software within the preset time period is greater than or equal to 2, a successful reception flag is sent to the front-end software.

[0038] If the number of UDP packets received by the station control software within the preset time period is less than 2, a retransmission flag is fed back to the front-end software so that the front-end software can retransmit the UDP packets based on the retransmission flag.

[0039] Furthermore, after receiving the UDP data packet, the station control software transparently forwards the UDP data packet to the baseband software via the TCP protocol to obtain transmission result data, including:

[0040] After the station control software receives the UDP data packet, it unpacks the UDP data packet to obtain the processed data;

[0041] The processed data is encapsulated into TCP packets, and a TCP connection is established with the baseband software.

[0042] The TCP packets are transparently forwarded to the baseband software via the TCP connection.

[0043] Furthermore, the data flow rate includes the data inflow rate and the data outflow rate, and the dynamic control strategy includes a dynamic expansion strategy and a dynamic reduction strategy;

[0044] The process of determining a dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and adjusting the cache size of the cache space based on the dynamic control strategy to obtain the target cache space, includes:

[0045] Get the current cache utilization rate;

[0046] When the data inflow rate is greater than the data outflow rate and the cache utilization rate is greater than or equal to a preset upper limit threshold, the cache size of the cache space is expanded based on a dynamic expansion strategy to obtain the target cache space;

[0047] When the data inflow rate is less than the data outflow rate and the cache utilization rate is less than a preset lower threshold, the cache size of the cache space is reduced based on a dynamic reduction strategy to obtain the target cache space.

[0048] Furthermore, the method also includes:

[0049] Obtain the actual cache size of the cache space;

[0050] Obtain the capacity difference between the actual cache size and the capacity threshold of the cache space;

[0051] When the capacity difference is less than or equal to a preset difference threshold, a buffer overflow and underload warning mechanism is executed, and a warning signal is issued.

[0052] Secondly, the present invention provides a ground-based high-speed data injection system for the deep space K-band, comprising:

[0053] The data injection unit is used to obtain remote injection request commands collected from the interactive interface through the front-end software.

[0054] The strategy matching unit is used to obtain the type information of the remote control injection request instruction and determine the matching target encoding strategy based on the type information.

[0055] An encoding unit is used to encode the remote control injection request command based on the target encoding strategy to obtain an encoded file;

[0056] The layered transmission unit is used to forward the encoded file to the station control software and one or more other receiving parties based on a preset multi-software layered transmission protocol, and after the station control software receives the encoded file, it transparently forwards the encoded file to the baseband software to obtain the transmission result data.

[0057] A dynamic caching unit is used to determine a dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and to adjust the cache size of the cache space based on the dynamic control strategy to obtain a target cache space for caching the transmission result data for reading.

[0058] Thirdly, this application also provides an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to implement the deep space K-band ground high-speed data injection method as described above.

[0059] Fourthly, this application also provides a computer-readable storage medium storing computer-readable instructions thereon, which, when executed by a computer's processor, cause the computer to perform the deep space K-band ground high-speed data injection method as described above.

[0060] Fifthly, this application also provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the deep space K-band ground high-speed data injection method provided in the various alternative embodiments described above.

[0061] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0062] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0063] Figure 1 This is a flowchart illustrating an exemplary embodiment of the present application of a deep space K-band ground high-speed data injection method;

[0064] Figure 2 This is a schematic diagram illustrating the type information of remotely injected demand instructions in an exemplary embodiment of this application;

[0065] Figure 3 This is a schematic diagram illustrating the correspondence between category information and function identifiers in an exemplary embodiment of this application;

[0066] Figure 4 This is a flowchart illustrating a parallel distributed coding strategy in an exemplary embodiment of this application;

[0067] Figure 5This is a schematic diagram of the transmission protocol used by the application layer in an exemplary embodiment of this application;

[0068] Figure 6 This is a schematic diagram of splicing real-time transmitted data frames in an exemplary embodiment of this application;

[0069] Figure 7 This is a schematic diagram illustrating the implementation process of high-speed data uploading in the deep space K-band in an exemplary embodiment of this application;

[0070] Figure 8 This is a block diagram illustrating a ground-based high-speed data injection system for the K-band deep space spectrum, as shown in an exemplary embodiment of this application.

[0071] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0072] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0073] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0074] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0075] In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0076] In related technologies, when carrying out deep space exploration missions, spacecraft and their onboard scientific payloads serve as core experimental platforms and need to perform high-precision scientific experimental tasks for extended periods without human intervention.

[0077] Efficient remote injection is a key technology for ensuring the safety and mission flexibility of spacecraft and scientific payloads in orbit. It involves sending orbital correction commands, scientific payload configuration parameters, software update data, and fault recovery strategies to the spacecraft in real time from the ground control center, ensuring the spacecraft maintains normal operation in complex space environments and in unattended scenarios. Especially in deep-space long-latency communication scenarios, inefficient remote injection can lead to spacecraft or scientific payloads deviating from their intended operating state due to command delays, or premature termination of scientific missions due to the inability to promptly repair faults.

[0078] Therefore, efficient remote injection is not only the foundation for improving the success rate of deep space exploration missions, but also the core support for achieving dynamic optimization of scientific objectives and extending on-orbit lifespan.

[0079] Besides the long communication latency caused by space distance, the efficiency of remote-controlled injection in deep space exploration missions also depends on both efficient processing and reliable transmission between ground software systems. Efficient processing involves quickly and accurately encoding the injected data, while reliable transmission involves quickly and reliably transmitting data between multiple software programs. However, current spacecraft data uploading technologies have shortcomings in both efficient processing and reliable transmission.

[0080] In terms of injected data processing, traditional uplink injection protocols have simple requirements, categorizing injection needs into only two main types: remote control command injection and software reconfiguration injection. When faced with more refined requirements, a wider variety of data types, and large file segmentation, it's difficult to quickly encode the injected data, leading to low uplink injection efficiency due to low data processing efficiency. Regarding software interface transmission efficiency, the choice of transmission methods between different levels of software in the ground software system is inappropriate. Information exchange between various software programs often uses a single transmission protocol, without fully considering the characteristics and data transmission needs of each software level. For command transmission with high real-time requirements, using a highly reliable but inefficient transmission protocol can lead to command transmission delays, affecting the spacecraft's timely response. Conversely, for software update transmission with large data volumes, using a highly efficient but unreliable protocol can easily result in data loss or errors, reducing the success rate of transmission. In terms of caching mechanisms, when the ground software system performs high-speed data transmission, the baseband software lacks effective caching management strategies when receiving large amounts of data. The cache size is fixed and cannot be adjusted in real time according to the dynamic changes in data traffic. When the data inflow rate suddenly increases, the cache is prone to overflow, causing subsequent data to be lost because it cannot be stored properly. When the data inflow rate is low, it will waste cache resources and affect the overall performance of the system.

[0081] To address the above-mentioned problems, embodiments of this application propose a method and system for high-speed ground data injection in the deep space K-band, as well as electronic devices and computer-readable storage media. The main focus is on the high-speed ground data injection technology in the deep space K-band, which is included in deep space exploration communication technology. These embodiments will be described in detail below.

[0082] Please refer to the following first. Figure 1 , Figure 1 This is a flowchart illustrating a ground-based high-speed data injection method in the deep space K-band, as shown in an exemplary embodiment of this application. This method can be applied to... Figure 1 The implementation environment shown is specifically executed by ground software, which includes front-end software, station control software, and baseband software. In other implementation environments, this method can be executed by equipment in those environments; this embodiment does not impose any limitations on this.

[0083] like Figure 1 As shown in an exemplary embodiment, the deep space K-band ground high-speed data injection method may include steps S101 to S105, which are described in detail below:

[0084] Step S101: Obtain the remote control injection requirement command collected from the interactive interface through the front-end software.

[0085] Step S102: Obtain the type information of the remote control injection requirement command, and determine the matching target encoding strategy based on the type information.

[0086] Step S103: Encode the remote control injection requirement command based on the target encoding strategy to obtain the encoded file.

[0087] Step S104: Based on the preset multi-software layered transmission protocol, the encoded file is forwarded to the station control software and one or more other receiving parties. After the station control software receives the encoded file, it is transparently forwarded to the baseband software to obtain the transmission result data.

[0088] Step S105: Determine the dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and adjust the cache size of the cache space based on the dynamic control strategy to obtain the target cache space, which is used to cache the transmission result data for reading.

[0089] As can be seen from the above, the method provided in this embodiment achieves diversified injection data processing through the front-end software of the ground software system. On the other hand, it adapts to the interaction characteristics and needs of different software stages based on the preset multi-software layered transmission protocol, and a dynamic caching mechanism is set in the baseband software. This improves the processing efficiency, transmission efficiency and injection reliability of K-band ground segment uplink injection data in deep space missions, effectively solving problems in injection data processing efficiency, software transmission efficiency and reliability, and high-speed transmission data loss, laying a solid foundation for the development of spacecraft communication.

[0090] In an exemplary embodiment of this application, the specific steps of obtaining the type information of the remote control injection request instruction and determining the matching target encoding strategy based on the type information may include:

[0091] Obtain the request type and corresponding execution method of the remote control injection request, as well as the internal CAN (Controller Area Network) message injection format of the remote control injection request;

[0092] Based on the demand type, execution method, and internal CAN message injection format, the type information of remote control injection demand commands is obtained;

[0093] Based on the pre-defined correspondence between category information and function identifiers, the target function identifier corresponding to the category information is determined;

[0094] Based on the matching relationship between preset function identifiers and coding strategies, a target coding strategy that matches the target function identifier is determined.

[0095] In this embodiment, the remote control injection requirement commands in deep space exploration missions are mainly divided into two categories: remote control command injection and software reconfiguration injection. The execution methods are divided into immediate execution and deferred execution. For these two categories of injection requirements, based on the different internal CAN message injection formats, they are further divided into four categories: single-frame injection messages, composite-frame injection messages, internal event injection messages, and software reconfiguration injection messages. The requirement type, execution method, and internal CAN message injection format together form the type information of the remote control injection requirement commands, such as... Figure 2 As shown, Figure 2 This is a schematic diagram illustrating the type information of remote injection requirement instructions in an exemplary embodiment of this application.

[0096] To address the complex and diverse nature of remote control injection commands, the coding strategy is categorized based on actual usage requirements and the function identifiers set in the injection frame protocol. Please refer to [link / reference]. Figure 3 , Figure 3 This is a schematic diagram illustrating the correspondence between category information and functional identifiers in an exemplary embodiment of this application. For example... Figure 3As shown, the functions are divided into two main categories: remote control data injection (covering both delayed and immediate execution modes) and software reconfiguration injection. The delayed execution type includes three CAN message formats: single-frame injection message, composite frame injection message, and internal event injection message. The immediate execution type includes four CAN message injection formats: single-frame injection message, composite frame injection message, internal event injection message, and software reconfiguration injection message. Clear distinctions are achieved by assigning a unique function identifier to each category.

[0097] Thus, through the above embodiments, this application can accurately match the corresponding encoding strategy based on the actual functional attributes of the data during data encoding, ensuring that different functional data can be accurately encoded and processed, effectively solving the problem of processing chaos caused by multiple encoding requirements.

[0098] In the embodiments provided in this application, the single-frame injected message data is small, has a single function, and needs to be executed immediately. Therefore, it is suitable for an encoding strategy that encapsulates the complete instruction code and key information such as the target address within a standard-length CAN data frame for transmission. No segmentation or complex assembly is required; it can be directly parsed and executed.

[0099] Composite frame injection messages contain large amounts of data, exceeding the capacity of a single frame. However, logically they constitute a unified set of instructions or parameters. Therefore, an encoding strategy that segments the data and adds a sequence number, total number of segments, and checksum to each segment is suitable. At the receiving end, the data is reassembled and checked according to the sequence number to ensure the integrity and correct order of the long data packet.

[0100] Internal event injection messages are instructions that trigger specific state machines or processes, possessing specific timing or conditional dependencies. Therefore, they are suitable for encoding strategies that assign a unique "event ID" or "command code" to the message based on standard instruction encoding. During parsing, they are not executed as direct actions, but rather mapped as internal events, which are responded to and processed by dedicated event handlers or state machines, thereby achieving complex logical control.

[0101] In an exemplary embodiment of this application, when the remote injection request instruction is a software reconstruction injection request for a large file, the matching target encoding strategy is a parallel distributed encoding strategy; the specific steps for obtaining the encoded file through the parallel distributed encoding strategy may include:

[0102] Obtain the segmentation requirements for large files in the software refactoring injection requirements, and split the large files based on the segmentation requirements to obtain multiple sub-file index blocks;

[0103] Retrieve the file hash value and subfile block number of the subfile corresponding to multiple subfile index blocks;

[0104] Parallel encoding processing is performed on multiple encoding nodes based on file hash value and sub-file block sequence number to obtain encoded data blocks corresponding to multiple sub-file index blocks; each sub-file index block corresponds one-to-one with an encoding node.

[0105] The encoding result corresponding to each sub-file index block is obtained based on the sub-file information and encoded data blocks of the sub-files;

[0106] After obtaining the encoding results of all encoding nodes, the encoded data blocks in the encoding results are parsed to obtain the parsed data;

[0107] Based on the sub-file block sequence number, sort the parsed data corresponding to multiple sub-file index blocks to obtain the encoded file corresponding to the remote control injection requirement command.

[0108] In this embodiment, a parallel distributed encoding architecture was designed to address the software reconstruction injection requirements for large files, which can significantly improve the speed of large file segmentation encoding. Please refer to [link / reference]. Figure 4 , Figure 4 This is a flowchart illustrating a parallel distributed coding strategy in an exemplary embodiment of this application.

[0109] like Figure 4 As shown, the parallel distributed encoding architecture applies a parallel distributed encoding strategy as follows: Based on the number of bytes in a large file and segmentation requirements, it is divided into multiple sub-file index blocks. File hash values ​​and sub-file block numbers are generated based on these sub-file blocks, and these are distributed across multiple encoding nodes for simultaneous encoding processing. This yields encoded data blocks corresponding to the multiple sub-file index blocks, and encoded data blocks are added to the sub-file information. After all encoding nodes have finished, the encoded data block information is parsed to obtain the parsed data. Then, the data is sorted in ascending order according to the block number, and the encoded data is concatenated sequentially. Header metadata is removed to generate the final encoded file.

[0110] Each sub-file index block corresponds one-to-one with an encoding node. Each encoding node has independent encoding resources and processing capabilities, enabling it to execute encoding tasks in parallel, which greatly shortens the overall encoding time.

[0111] Thus, through the above embodiments, this application significantly improves the processing of data injection requirements by using coding strategy classification and parallel distributed coding, especially for the injection of ultra-large files, and can meet various complex requirements such as spacecraft remote control injection and software reconstruction. Furthermore, during the parallel coding process, an efficient inter-node communication mechanism ensures the collaborative work between various coding nodes, guaranteeing the consistency and integrity of the coding results. This solves the problem that existing technologies cannot efficiently handle diverse and refined injection command requirements and large file segmented order-preserving coding requirements, leading to significant data processing delays in the initial stage of the data injection process.

[0112] In an exemplary embodiment of this application, the specific steps of forwarding the encoded file to the station control software and one or more other receiving parties based on a preset multi-software layered transmission protocol, and then transparently forwarding the encoded file to the baseband software after receiving it, to obtain the transmission result data, may include:

[0113] The encoded file is encapsulated using front-end software to obtain UDP data packets;

[0114] Based on a preset multi-software layered transmission protocol, UDP data packets are forwarded to the station control software and one or more other receiving parties via UDP multicast transmission.

[0115] After the station control software receives the UDP data packet, it transparently forwards the UDP data packet to the baseband software via the TCP protocol to obtain the transmission result data.

[0116] In this embodiment, taking into full account the interaction characteristics and requirements of software at different stages of the ground software system, a layered and differentiated transmission method is adopted, which uses UDP (User Datagram Protocol) multicast transmission between the front end and the station control, and TCP (Transmission Control Protocol) transmission between the station control and the baseband.

[0117] Specifically, the front-end software is primarily responsible for user interaction and initial command processing, requiring high real-time performance. Therefore, the front-end software encapsulates the command data to be transmitted into UDP packets and sets multicast addresses and port numbers. Employing arbitrary source multicast, the front-end software can quickly and concurrently send data to multiple receiving parties via the IGMP (Internet Group Management Protocol), meeting the high real-time command transmission requirements.

[0118] As the core control node of the ground software system, the station control software needs to further process and forward data. Data transmission between the station control software and the baseband software requires extremely high reliability; therefore, the TCP protocol is used. The TCP protocol has a reliable connection mechanism and error retransmission function, ensuring that data is transmitted accurately from the station control software to the baseband software.

[0119] Thus, through the above embodiments, this application adapts the interaction characteristics and needs of software at different stages of the ground software system using a multi-software layered transmission protocol. By employing layered and differentiated transmission, it fully leverages the advantages of UDP and TCP protocols, ensuring both transmission efficiency and data transmission reliability, thereby improving the overall transmission performance of the software system. This solves the problem of traditional methods using a uniform transmission method across different software layers, which fails to fully utilize the advantages of each transmission method. For example, if TCP is used exclusively, although transmission reliability is high, transmission efficiency is low and cannot meet real-time requirements; if UDP is used exclusively, although transmission speed is fast, reliability is insufficient and data loss is likely.

[0120] In another exemplary embodiment, the specific steps of encapsulating the encoded file into UDP packets using front-end software in the above embodiments may include:

[0121] The real-time data frame transmission protocol is adopted, and the real-time data frame is obtained based on the data field corresponding to the frame header and the encoded file.

[0122] The real-time transmitted data frames are encapsulated into UDP as application data fields to obtain the corresponding UDP data packets.

[0123] In this embodiment, a three-layer data frame transmission method is used between the front-end software and the station control software, including the network layer, transport layer, and application layer. The first layer, the network layer, uses the IP protocol and can be implemented according to RFC 791; the second layer, the transport layer, uses the UDP protocol and can be implemented according to RFC 768; the third layer, the application layer, uses a real-time data frame transmission protocol, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of the transmission protocol used by the application layer in an exemplary embodiment of this application.

[0124] When the front-end software transmits encoded files to the station control software, it uses the following at the application layer: Figure 5 The transmission protocol shown sets the frame header corresponding to the remote control injection request command and obtains the data field corresponding to the encoded file. Then, based on the frame header and data field, a real-time transmission data frame is formed. At the transport layer, this complete real-time transmission data frame is used as the application data field and placed into a UDP packet. The UDP packet has its own header, containing the source and destination port numbers. At the network layer, the entire UDP packet is placed into an IP packet. The IP packet header contains the source IP address and the destination multicast IP address.

[0125] In other embodiments, the data field in the real-time transmitted data frame can be divided into data items such as measurement and control instructions, stop measurement and control instructions, measurement and control instructions transmission results, and small loop comparison results, as follows: (1) After receiving the measurement and control instructions, the device immediately forwards the remote control frame sequence according to the time requirements in the format, and returns or does not return the small loop comparison results according to the requirements of the small loop return identifier in the format; (2) After receiving the stop measurement and control instructions, the baseband device immediately or at a specified time executes the stop measurement and control instructions according to the requirements. When executing the stop measurement and control instructions, if the instruction code is currently being sent, the instruction is stopped after the current instruction code is sent; if the execution pulse is currently being sent, the subsequent execution pulse code unit is stopped immediately after the code unit of the current execution pulse is sent. (2) While executing the stop measurement and control command, clear all commands waiting to be sent in the device cache; (3) If the stop measurement and control command time specified in the format is earlier than the current time, or T=FFFFFFFFH, then execute the stop measurement and control command immediately; (4) If the current time is earlier than the stop measurement and control command time specified in the format, then execute the stop measurement and control command at the time specified in the format.

[0126] Furthermore, to improve transmission efficiency, the data field can be processed using stream concatenation of instruction data frames. During processing, multiple related data points are sequentially concatenated according to their frame sequence numbers, forming a continuous transmission frame. This frame is then sent to the transport layer as a real-time transmission data frame, enabling more effective data to be carried in a single transmission and reducing the number of transmission frames and transmission overhead. For example... Figure 6 As shown, Figure 6 This is a schematic diagram illustrating the splicing of real-time transmitted data frames in an exemplary embodiment of this application. The condition for stream-based splicing of remote control command frames is that the source address, destination address, frame identifier, frame count, segment identifier, and the joint identifier generated by the frame count are consecutive. If the identifiers of two consecutive frames are inconsistent, data frame splicing is not performed.

[0127] Thus, through the above embodiments, this application further improves transmission efficiency and accuracy by setting a three-layer data frame transmission method adapted to data transmission between front-end software and station control software.

[0128] In another exemplary embodiment, due to frame loss in UDP transmission, a transmission mechanism involving three-way transmission with two-way judgment and data retransmission is used between software to ensure the effectiveness of injected data transmission. Therefore, the specific steps for forwarding UDP packets to the station control software and one or more other receiving parties via UDP multicast transmission may include:

[0129] Within a preset time period, UDP packets are forwarded three times consecutively to the station control software and one or more other receiving parties via UDP multicast transmission.

[0130] If the station control software receives more than or equal to 2 UDP packets within a preset time period, it sends a successful reception flag to the front-end software.

[0131] If the number of UDP packets received by the station control software within a preset time period is less than 2, a retransmission flag is sent back to the front-end software so that the front-end software can resend UDP packets based on the retransmission flag.

[0132] Thus, through the above embodiments, this application can effectively ensure the reliability of UDP transmission by setting a transmission mechanism of sending three times and judging two times and data retransmission.

[0133] In another exemplary embodiment, after the station control software receives a UDP data packet, the specific steps for transparently forwarding the UDP data packet to the baseband software via the TCP protocol to obtain the transmission result data may include:

[0134] After the station control software receives the UDP data packet, it unpacks the UDP data packet to obtain the processed data;

[0135] The processed data is encapsulated into TCP packets, and a TCP connection is established with the baseband software.

[0136] Transparently forward TCP packets to the baseband software via a TCP connection.

[0137] In this embodiment, the station control software and other receiving parties join the corresponding multicast group, listen on a designated port, and receive UDP packets sent by the front-end software to parse and process them. Specifically, the parsing and processing process involves the station control software unpacking the data packets layer by layer, removing the IP header to obtain the UDP packet, and then removing the UDP header to obtain the real-time transmission data frame. Finally, the frame header is parsed according to the preset real-time transmission protocol format, each field is read, and the data field is located based on the Length field. The final required instruction is then extracted and processed.

[0138] Between the station control software and the baseband software, the station control software encapsulates the processed data into TCP packets and establishes a TCP connection with the baseband software. The station control software then calls the data forwarding module to send the packets to the baseband software through the established TCP connection. The baseband software receives the TCP packets and sends an acknowledgment. If the station control software does not receive an acknowledgment, it retransmits the data to ensure that the data is transmitted to the baseband software accurately.

[0139] Thus, through the above embodiments, this application improves data transmission efficiency and data validity by setting adaptive transmission methods between the station control software and the baseband software.

[0140] In an exemplary embodiment of this application, the data flow rate includes the data inflow rate and the data outflow rate, and the corresponding dynamic control strategy includes a dynamic expansion strategy and a dynamic reduction strategy. Therefore, the specific steps of determining the dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and adjusting the cache size of the cache space based on the dynamic control strategy to obtain the target cache space may include:

[0141] Get the current cache utilization rate;

[0142] When the data inflow rate is greater than the data outflow rate and the cache utilization rate is greater than or equal to the preset upper limit threshold, the cache size is expanded based on the dynamic expansion strategy to obtain the target cache space;

[0143] When the data inflow rate is less than the data outflow rate and the cache utilization rate is less than the preset lower threshold, the cache size is reduced based on a dynamic reduction strategy to obtain the target cache space.

[0144] Deep space exploration missions utilize the K-band frequency, providing considerable room for broadband spacecraft communication. Its uplink injection rate can reach the MB level, thus posing a significant challenge to the transmission rate and caching mechanism of the ground software system. In this embodiment, the front-end software and station control software can set multiple instructions during transmission according to the transmission protocol. Therefore, a single transmission will contain multiple sets of instructions. After receiving the instructions, the baseband software will store each set in a buffer, waiting to be sent frame by frame.

[0145] Therefore, this embodiment incorporates a dynamic caching mechanism in the baseband software to achieve efficient storage. Specifically, during data transmission, the baseband software monitors the data inflow and outflow rates in real time. When the data inflow rate exceeds the outflow rate and the cache utilization reaches a set upper limit threshold, the system automatically determines that the cache size needs to be increased. It then dynamically allocates system memory resources to expand the cache capacity, preventing data loss due to cache overflow, and stores newly received data in the expanded cache. Conversely, when the data inflow rate is less than the outflow rate and the cache utilization is below a set lower limit threshold, the system automatically reduces the cache size, releasing excess memory resources. Newly received data is then stored in the cache in arrival order, improving system resource utilization.

[0146] At the same time, a first-in, first-out (FIFO) cache management strategy is adopted, which retrieves data from the cache according to the first-in, first-out principle when reading data, to ensure the order and integrity of the data.

[0147] In addition, during initialization, the baseband software sets the initial cache size based on system configuration and historical data traffic, and monitors the data inflow and outflow rates in real time through the device status detection module.

[0148] Thus, through the above embodiments, in order to meet the needs of high-speed data transmission, this application designs a dynamic caching mechanism through baseband software, which can dynamically adjust the cache size according to data traffic and system processing capabilities.

[0149] In an exemplary embodiment of this application, a buffer overflow and underload warning mechanism is also provided, the specific implementation steps of which may include:

[0150] Get the actual cache size of the cache space;

[0151] Obtain the capacity difference between the actual cache size and the cache space capacity threshold;

[0152] When the capacity difference is less than or equal to the preset difference threshold, the buffer overflow and underload warning mechanism is executed, and a warning signal is issued.

[0153] In this embodiment, by monitoring the relationship between the actual cache size and the capacity threshold in real time, a warning signal can be issued in a timely manner when the cache is about to overflow or become underloaded, so that the system can take corresponding measures, such as adjusting the data transmission rate or increasing system resources, thus solving the problem of data loss during high-speed transmission.

[0154] Please see Figure 7 , Figure 7 This is a schematic diagram illustrating the implementation process of high-speed data uploading in the deep space K-band in an exemplary embodiment of this application. Figure 7 As shown, during implementation, the front-end software collects user injection request instructions through an interactive interface and completes injection data acquisition through parameter settings, including immediate execution and delayed execution. The software's data encoding module quickly locates the corresponding encoding strategy and encapsulates the data based on the instruction's function identifier. For large file injection requests, users upload files through the front-end software interface, set the number of sub-file segments, and then call the data encoding module to perform parallel distributed encoding of the injection file request. The encoding result order is consistent with the original file. After encoding, the transmission header is encapsulated according to the transmission protocol, and the data frame is sent to the multicast address via the UDP multicast transmission protocol.

[0155] Between the front-end software, station control software, and other requesters, the front-end software encapsulates the instruction data to be transmitted into UDP packets and sets a multicast address and port number. Then, the front-end software calls the data sending module to send the packets to the specified multicast address and port via UDP multicast. The station control software and other receivers join the corresponding multicast group, listen on the specified port, receive the UDP packets sent by the front-end software, and parse and process them. Between the station control software and the baseband software, the station control software encapsulates the processed data into TCP packets and establishes a TCP connection with the baseband software. The station control software calls the data forwarding module to send the packets to the baseband software through the established TCP connection. The baseband software receives the TCP packets and sends an acknowledgment. If the station control software does not receive an acknowledgment, it retransmits the data to ensure accurate transmission to the baseband software.

[0156] During transmission, the front-end software needs to send three instruction data frames consecutively within 500ms. After receiving two or more identical data frames consecutively, the station control software sends three instruction transmission results consecutively. Otherwise, it sends three instruction transmission result frames with retransmission information (including the lost data frame number) consecutively. After receiving the instruction transmission results, the front-end software retransmits the data.

[0157] During data transmission, the baseband software provides a device status monitoring module to monitor data inflow and outflow rates in real time. When the data inflow rate exceeds the outflow rate and the buffer utilization reaches a certain threshold, the buffer size is automatically increased; when the data inflow rate is less than the outflow rate and the buffer utilization is below a certain threshold, the buffer size is automatically decreased. Furthermore, the baseband software employs a first-in, first-out (FIFO) buffer management strategy, storing newly received data in the buffer in the order of arrival, and retrieving data from the buffer according to the FIFO principle, ensuring data order and integrity.

[0158] At the same time, a cache overflow and underload warning mechanism is set up. When the cache is about to overflow or become underloaded, a warning signal is issued in a timely manner so that the system can take corresponding measures, such as adjusting the data transmission rate or increasing system resources.

[0159] Furthermore, through practical application, the ground high-speed data injection method for deep space K-band provided in this application has successfully supported the verification of a 190,000-kilometer K-band measurement and communication link. During the data injection process, the ground software system achieved a stable injection rate of 102.3 kbps, with a command transmission success rate of 100%, meaning that the transmission reliability between various software interaction interfaces reached 100%, and there was no data overflow in the baseband equipment buffer. Compared with the existing UXB and non-coherent spread spectrum system (which supports a maximum uplink rate of 1000 bps), the efficiency of large file data injection is improved by nearly 100 times.

[0160] Figure 8 This is a block diagram illustrating a deep-space K-band ground-based high-speed data injection system 800, as shown in an exemplary embodiment of this application. Figure 8 As shown, the system includes:

[0161] The data injection unit 801 is used to obtain remote control injection request commands collected from the interactive interface through the front-end software.

[0162] The strategy matching unit 802 is used to obtain the type information of the remote control injection request instruction and determine the matching target encoding strategy based on the type information.

[0163] The encoding unit 803 is used to encode the remote control injection requirement command based on the target encoding strategy to obtain an encoded file;

[0164] The layered transmission unit 804 is used to forward the encoded file to the station control software and one or more other receiving parties based on a preset multi-software layered transmission protocol, and after the station control software receives the encoded file, it transparently forwards the encoded file to the baseband software to obtain the transmission result data.

[0165] The dynamic caching unit 805 is used to determine the dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and adjust the cache size of the cache space based on the dynamic control strategy to obtain the target cache space, which is used to cache the transmission result data for reading.

[0166] This system applies the ground high-speed data injection method for the K-band deep space provided in this application. By implementing diversified injection data processing according to the type of remote control injection command information in the front-end software, station control software, and baseband software of the ground software system, as well as multi-software layered transmission protocol design and dynamic caching design, it improves the processing efficiency, transmission efficiency, and injection reliability of K-band ground segment uplink injection data in deep space missions. It effectively solves the problems in injection data processing efficiency, software transmission efficiency and reliability, and high-speed transmission data loss.

[0167] In another exemplary embodiment, the strategy matching unit 802 is further configured to obtain the demand type and corresponding execution method of the remote control injection demand instruction, as well as the internal CAN message injection format of the remote control injection demand; obtain the type information of the remote control injection demand instruction based on the demand type, execution method and internal CAN message injection format; determine the target function identifier corresponding to the type information based on the preset correspondence between the type information and the function identifier; and determine the target encoding strategy that matches the target function identifier based on the preset matching relationship between the function identifier and the encoding strategy.

[0168] In another exemplary embodiment, when the remote injection request instruction is a software reconstruction injection request for a large file, the matching target encoding strategy is a parallel distributed encoding strategy; the encoding unit 803 is further configured to obtain the segmentation requirements for the large file in the software reconstruction injection request, and to segment the large file based on the segmentation requirements to obtain multiple sub-file index blocks; obtain the file hash value and sub-file block sequence number of the sub-file corresponding to the multiple sub-file index blocks; perform parallel encoding processing on multiple encoding nodes based on the file hash value and sub-file block sequence number to obtain the encoded data blocks corresponding to the multiple sub-file index blocks; the sub-file index blocks correspond one-to-one with the encoding nodes; obtain the encoding result corresponding to each sub-file index block based on the sub-file information and the encoded data blocks; after obtaining the encoding results of all encoding nodes, parse the encoded data blocks in the encoding results to obtain parsed data; sort the parsed data corresponding to the multiple sub-file index blocks based on the sub-file block sequence number to obtain the encoded file corresponding to the remote injection request instruction.

[0169] In another exemplary embodiment, the layered transmission unit 804 is further configured to encapsulate the encoded file through the front-end software to obtain UDP data packets; based on a preset multi-software layered transmission protocol, forward the UDP data packets to the station control software and one or more other receiving parties via UDP multicast transmission; after the station control software receives the UDP data packets, it transparently forwards the UDP data packets to the baseband software via the TCP protocol to obtain the transmission result data.

[0170] In another exemplary embodiment, the layered transmission unit 804 is further configured to use a real-time data frame transmission protocol to obtain a real-time transmission data frame based on the data field corresponding to the frame header and the encoded file; and to encapsulate the real-time transmission data frame as a payload into a UDP packet to obtain the corresponding UDP data packet.

[0171] In another exemplary embodiment, the layered transmission unit 804 is further configured to forward UDP data packets three times consecutively to the station control software and one or more other receiving parties via UDP multicast transmission within a preset time period; if the number of UDP data packets received by the station control software within the preset time period is greater than or equal to 2, a successful reception flag is sent to the front-end software; if the number of UDP data packets received by the station control software within the preset time period is less than 2, a retransmission flag is sent to the front-end software so as to receive the UDP data packets retransmitted by the front-end software based on the retransmission flag.

[0172] In another exemplary embodiment, the layered transmission unit 804 is further configured to, after the station control software receives the UDP data packet, unpack the UDP data packet to obtain processed data; encapsulate the processed data into a TCP data packet and establish a TCP connection with the baseband software; and transparently forward the TCP data packet to the baseband software through the TCP connection.

[0173] In another exemplary embodiment, the data flow rate includes the data inflow rate and the data outflow rate, and the dynamic control strategy includes a dynamic expansion strategy and a dynamic reduction strategy; the dynamic caching unit 805 is further configured to obtain the current cache utilization rate of the cache space; when the data inflow rate is greater than the data outflow rate and the cache utilization rate is greater than or equal to a preset upper limit threshold, the cache size of the cache space is expanded based on the dynamic expansion strategy to obtain the target cache space; when the data inflow rate is less than the data outflow rate and the cache utilization rate is less than a preset lower limit threshold, the cache size of the cache space is reduced based on the dynamic reduction strategy to obtain the target cache space.

[0174] In another exemplary embodiment, the system further includes:

[0175] The space warning unit is used to obtain the actual cache size of the cache space; obtain the capacity difference between the actual cache size and the capacity threshold of the cache space; and execute the cache overflow and underload warning mechanism and issue a warning signal when the capacity difference is less than or equal to the preset difference threshold.

[0176] It should be noted that the deep space K-band ground high-speed data injection system and the deep space K-band ground high-speed data injection method provided in the above embodiments belong to the same concept. The specific operation methods of each module and unit have been described in detail in the method embodiments and will not be repeated here. In practical applications, the deep space K-band ground high-speed data injection system provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. This is not a limitation here.

[0177] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the electronic device to implement the deep space K-band ground high-speed data injection method provided in the above embodiments.

[0178] Figure 9 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 9 The computer system 900 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0179] like Figure 9As shown, the computer system 900 includes a Central Processing Unit (CPU) 901, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on a program stored in Read-Only Memory (ROM) 902 or a program loaded from Storage Section 908 into Random Access Memory (RAM) 903. The RAM 903 also stores various programs and data required for system operation. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. An Input / Output (I / O) interface 905 is also connected to the bus 904.

[0180] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. Removable media 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 910 as needed so that computer programs read from them can be installed into storage section 908 as needed.

[0181] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs various functions defined in the system of this application.

[0182] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0183] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0184] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0185] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned deep-space K-band ground high-speed data injection method. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0186] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the deep space K-band ground high-speed data injection method provided in the various embodiments described above.

[0187] The above are merely preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for injecting high-speed ground data in the K-band of deep space, characterized in that, Applied to a ground-based software system, the ground-based software system including front-end software, station control software, and baseband software, the method includes: The remote control injection requirement command is obtained by acquiring the interactive interface through the front-end software. Obtain the type information of the remote control injection request command, and determine the matching target encoding strategy based on the type information; The remote control injection request command is encoded based on the target encoding strategy to obtain an encoded file; Based on a preset multi-software layered transmission protocol, the encoded file is forwarded to the station control software and one or more other receiving parties. After the station control software receives the encoded file, it is transparently forwarded to the baseband software to obtain the transmission result data. A dynamic control strategy is determined based on the data flow rate monitored in real time by the baseband software, and the cache size of the cache space is adjusted based on the dynamic control strategy to obtain a target cache space for caching the transmission result data for reading. The pre-defined multi-software layered transmission protocol forwards the encoded file to the station control software and one or more other receiving parties. After receiving the encoded file, the station control software transparently forwards it to the baseband software, obtaining transmission result data, including: The front-end software encapsulates the encoded file to obtain UDP data packets; Based on a preset multi-software layered transmission protocol, the UDP data packets are forwarded to the station control software and one or more other receiving parties via UDP multicast transmission. After receiving the UDP data packet, the station control software transparently forwards the UDP data packet to the baseband software via the TCP protocol to obtain the transmission result data; Among them, the multi-software layered transmission protocol adopts a layered and differentiated transmission method, which uses UDP multicast transmission between the front end and the station control and TCP transmission between the station control and the baseband. The data flow rate includes the data inflow rate and the data outflow rate, and the dynamic control strategy includes the dynamic expansion strategy and the dynamic reduction strategy. The process of determining a dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and adjusting the cache size of the cache space based on the dynamic control strategy to obtain the target cache space, includes: Get the current cache utilization rate; When the data inflow rate is greater than the data outflow rate and the cache utilization rate is greater than or equal to a preset upper limit threshold, the cache size of the cache space is expanded based on a dynamic expansion strategy to obtain the target cache space; When the data inflow rate is less than the data outflow rate and the cache utilization rate is less than a preset lower threshold, the cache size of the cache space is reduced based on a dynamic reduction strategy to obtain the target cache space.

2. The method according to claim 1, characterized in that, The step of obtaining the type information of the remote control injection request instruction and determining the matching target encoding strategy based on the type information includes: Obtain the demand type and corresponding execution method of the remote control injection demand instruction, as well as the internal CAN message injection format of the remote control injection demand; Based on the demand type, the execution method, and the internal CAN message injection format, the type information of the remote control injection demand command is obtained; Based on the pre-defined correspondence between category information and function identifiers, the target function identifier corresponding to the category information is determined; Based on the matching relationship between preset function identifiers and encoding strategies, a target encoding strategy that matches the target function identifier is determined.

3. The method according to claim 1, characterized in that, When the remote injection request instruction is a software reconstruction injection request for a large file, the matching target encoding strategy is a parallel distributed encoding strategy. The process of encoding the remote control injection request command based on the target encoding strategy to obtain an encoded file includes: Obtain the segmentation requirements for the large file in the software refactoring injection requirements, and segment the large file based on the segmentation requirements to obtain multiple sub-file index blocks; Obtain the file hash value and sub-file block number of the sub-file corresponding to the multiple sub-file index blocks; Parallel encoding processing is performed on multiple encoding nodes based on the file hash value and the sub-file block sequence number to obtain encoded data blocks corresponding to multiple sub-file index blocks; each sub-file index block corresponds one-to-one with an encoding node. The encoding result corresponding to each sub-file index block is obtained based on the sub-file information and the encoded data block; After obtaining the encoding results of all encoding nodes, the encoded data blocks in the encoding results are parsed to obtain parsed data; Based on the sub-file block sequence number, the parsed data corresponding to multiple sub-file index blocks are sorted to obtain the encoded file corresponding to the remote control injection requirement instruction.

4. The method according to claim 1, characterized in that, The step of encapsulating the encoded file using the front-end software to obtain UDP data packets includes: A real-time data frame transmission protocol is adopted, and real-time transmission data frames are obtained based on the frame header and the data field corresponding to the encoded file. The real-time transmitted data frame is encapsulated as an application data field using UDP to obtain the corresponding UDP data packet.

5. The method according to claim 1, characterized in that, The forwarding of the UDP data packets to the station control software and one or more other receiving parties via UDP multicast transmission includes: Within a preset time period, the UDP data packets are forwarded three times consecutively to the station control software and one or more other receiving parties via UDP multicast transmission. If the number of UDP packets received by the station control software within the preset time period is greater than or equal to 2, a successful reception flag is sent to the front-end software. If the number of UDP packets received by the station control software within the preset time period is less than 2, a retransmission flag is fed back to the front-end software so that the front-end software can retransmit the UDP packets based on the retransmission flag.

6. The method according to claim 1, characterized in that, After receiving the UDP data packet, the station control software transparently forwards the UDP data packet to the baseband software via the TCP protocol to obtain transmission result data, including: After the station control software receives the UDP data packet, it unpacks the UDP data packet to obtain the processed data; The processed data is encapsulated into TCP packets, and a TCP connection is established with the baseband software. The TCP packets are transparently forwarded to the baseband software via the TCP connection.

7. The method according to claim 1, characterized in that, The method further includes: Obtain the actual cache size of the cache space; Obtain the capacity difference between the actual cache size and the capacity threshold of the cache space; When the capacity difference is less than or equal to a preset difference threshold, a buffer overflow and underload warning mechanism is executed, and a warning signal is issued.

8. A deep-space K-band ground-based high-speed data injection system, employing the method described in any one of claims 1 to 7, characterized in that, include: The data injection unit is used to obtain remote injection request commands collected from the interactive interface through the front-end software. The strategy matching unit is used to obtain the type information of the remote control injection request instruction and determine the matching target encoding strategy based on the type information. An encoding unit is used to encode the remote control injection request command based on the target encoding strategy to obtain an encoded file; The layered transmission unit is used to forward the encoded file to the station control software and one or more other receiving parties based on a preset multi-software layered transmission protocol, and after the station control software receives the encoded file, it transparently forwards the encoded file to the baseband software to obtain the transmission result data. A dynamic caching unit is used to determine a dynamic control strategy based on the data flow rate monitored in real time by the baseband software, and to adjust the cache size of the cache space based on the dynamic control strategy to obtain a target cache space for caching the transmission result data for reading.

Images