Satellite-borne solid-state storage system and method based on control information and file handle

Abstract

The application discloses a satellite-borne solid-state storage system based on control information and a file handle, which comprises a storage module, a processing module and a file handle control protocol. The storage module is used for providing a storage function and comprises a solid-state storage unit and a master FPGA. The master FPGA is used for receiving high-speed load data, acquiring and writing the solid-state storage unit based on the high-speed load data and transmitting data to a load unit or a ground unit based on an instruction. The processing module is used for managing data and controlling data forwarding. The processing module is connected with the storage module through a signal. The interaction communication between the storage module and the processing module adopts the file handle control protocol.

Description

Technical Field

[0001] This invention pertains to spacecraft data storage, and particularly relates to a spaceborne solid-state storage system and method based on control information and file handles. Background Technology

[0002] With the rapid development of aerospace technology, the data acquisition capabilities of spaceborne payloads (such as ultra-high resolution optical cameras, interferometric synthetic aperture radar, and hyperspectral imagers) have increased by orders of magnitude. Data output rates have jumped from the traditional hundreds of megabits per second to tens of thousands of megabits per second (tens of gigabits per second). Moreover, mission modes often require multiple payloads to work simultaneously, generating concurrent data streams. This poses unprecedented challenges to the storage capacity, write bandwidth, read / write efficiency, and reliability of spaceborne storage systems.

[0003] NAND Flash solid-state storage has become the mainstream medium for high-capacity spaceborne storage due to its advantages such as high density and low power consumption. However, existing spaceborne storage solutions still face many bottlenecks in addressing the aforementioned challenges: 1) High overhead of common protocols: Many systems adopt or borrow common storage protocols (such as eMMC, UFS, or even subsets of NVMe) or file systems (such as FAT32, YAFFS2) from the terrestrial computing field. These protocols are not designed for space applications, and their command layer and metadata management are complex, with high redundancy in interactive information. Implementing these protocols on limited on-board computing resources will consume a lot of logical resources and processor bandwidth, becoming a bottleneck for system performance and making it difficult to fully utilize the original bandwidth potential of Flash media.

[0004] 2) Inefficient file management: Traditional management methods often delegate the entire file system to upper-layer software or employ "raw device" management followed by software reorganization. The former incurs significant overhead and latency due to frequent creation, writing, and closing of massive numbers of small files; the latter increases the complexity of ground data processing and cannot support real-time on-orbit retrieval and rapid descent. Furthermore, complex metadata structures are more prone to errors under the influence of space single-event effects, leading to logical corruption of the file system.

[0005] 3) Insufficient concurrent processing capability: When faced with the requirement of writing multiple 10 Gigabit load data at the same time, the arbitration strategy and cache management of the traditional architecture may become bottlenecks, leading to data blocking or loss, and failing to guarantee the real-time requirements of all channels.

[0006] 4) Lack of reliability design: Many solutions do not have targeted radiation hardening design for critical metadata of the file system (such as space allocation table and file index table). Once these data are corrupted due to single-event upset (SEU), it may lead to the loss of data in the entire storage partition or even the entire storage system. Summary of the Invention

[0007] To address the aforementioned issues, this invention proposes a spaceborne solid-state storage system and method based on control information and file handles. Through a hardware-software co-design approach, the file system functionality is rationally divided between the upper-layer software and the lower-layer FPGA hardware, and a simple and efficient interaction protocol is designed to achieve high-performance and high-reliability spaceborne data storage.

[0008] A first aspect of the present invention provides a spaceborne solid-state storage system based on control information and file handles, comprising: The storage module provides storage functionality and includes a solid-state storage unit and a main control FPGA. The main control FPGA is used to receive high-speed payload data, acquire and write the high-speed payload data to the solid-state storage unit, and transmit the data to the payload unit or ground unit based on instruction-driven data transmission. The processing module is used to manage data and control data forwarding, and the processing module is connected to the storage module via a signal. The communication between the storage module and the processing module uses a file handle control protocol.

[0009] Preferably, the length of the data written to the solid-state storage unit is a preset length, and the data written to the solid-state storage unit is continuously mapped to the physical storage address space of the solid-state storage array.

[0010] Preferably, the solid-state storage unit adopts a bitmap structure to manage the file system storage space. The bit data of the bitmap is adapted to the minimum addressable storage unit of the solid-state storage unit. The status of the minimum addressable storage unit is identified based on the bit data. The working data includes at least occupied and idle states.

[0011] A second aspect of the present invention provides a spaceborne solid-state storage method based on control information and file handles, comprising: The control data of a preset length is sent to the storage module. The control data includes at least an operation code, a channel identifier, a logical block address, and a transmission length. The operation code is used to specify the command type, the channel identifier is used to identify the data source of several channels, and the logical block address and transmission length are used to specify the operation start position and the amount of operation data. Based on the first control data, the storage module obtains file data adapted to each data channel through data packet encapsulation, pipeline processing, and arbitration scheduling. The storage space of the storage module is managed by bitmap marking. The bitmap is mapped to the file index table through file handles to realize fast combination retrieval of combined elements. The bit data of the bitmap is adapted to the smallest addressable storage unit of the solid-state storage unit.

[0012] Preferably, the step of managing the storage space of the storage module using a bitmap tagging method further includes: The state data based on bitmap tags is mapped one-to-one with the logical address of the solid-state storage unit.

[0013] Preferably, the step of mapping a bitmap to a file index table via a file handle to achieve fast combined element retrieval further includes: The file handle is allocated and generated by the storage control unit when the file is created. Its value is the array index number of the file bitmap in memory. The complete bitmap metadata of the file can be obtained through this index.

[0014] Preferably, the storage module receives and sends payload data and controls the physical layer of the solid-state storage unit through a high-speed serial interface protocol.

[0015] Preferably, the step of the storage module receiving and sending payload data via a high-speed serial interface protocol further includes: The payload data is received through a high-speed serial interface protocol and the first payload data is obtained by processing a frame of preset length. Based on the first payload data, it is written to the solid-state storage unit through the storage frame sequence of the storage module.

[0016] Preferably, the step of writing the first payload data into the solid-state storage unit based on the storage frame sequence of the storage module further includes: Based on the first load data, multiple channels are processed in parallel through the caching and real-time arbitration mechanism of the storage module; each channel has independent file storage.

[0017] Preferably, the addressing unit of the control data is the minimum operating space of the storage module, and the file attribute control flag transmits the file logical address and transmission channel identification information.

[0018] The present invention, by adopting the above technical solution, has the following advantages and positive effects compared with the prior art: 1) Extremely efficient interaction: By using 8-byte fixed-length control data and file handle mechanism, the lengthy file path name, attribute information and other interaction overhead in the traditional protocol are completely eliminated, which improves communication efficiency by more than 90%, and is particularly beneficial for the rapid operation of a large number of small files.

[0019] Powerful concurrent processing capabilities: Through hardware-based pipelines, cache arbitration mechanisms, and channel identifier-based data routing, it can process multi-channel data writes and reads at 10 Gigabit rates in parallel without blocking, resulting in high system throughput.

[0020] 3) Inherent high reliability: The bitmap management structure is simple, making it easy to implement multi-copy storage and atomic update operations, which greatly enhances the metadata's resistance to single-event flips. The file handle indexing mechanism also avoids error propagation that may be caused by complex pointer structures.

[0021] 4) Flexible scalability: Customized instruction sets and protocol structures can be flexibly tailored and expanded according to specific task requirements, facilitating function customization and upgrades. Attached Figure Description

[0022] The specific embodiments of the present invention will be further described in detail below with reference to the accompanying drawings, wherein: Figure 1 This is a structural framework diagram of the processing module in this invention; Figure 2 This is the control layer data layer information flow of the storage module of the present invention; Figure 3 This is a schematic diagram of bitmap marker structure management in this invention; Figure 4 This is a schematic diagram of an embodiment of the control information frame in this invention; Figure 5 This is a schematic diagram of an embodiment of the opcode in this invention. Detailed Implementation

[0023] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The advantages and features of the present invention will become clearer from the following description and claims. It should be noted that the drawings are all in a very simplified form and use non-precise ratios, and are only used to facilitate and clarify the illustration of the embodiments of the present invention.

[0024] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0025] First Embodiment See Figure 1 The first aspect of the present invention provides a spaceborne solid-state storage system based on control information and file handles, comprising: The storage module provides storage functionality and includes a solid-state storage unit and a main control FPGA. The main control FPGA is used to receive high-speed payload data, acquire and write the high-speed payload data to the solid-state storage unit, and transmit the data to the payload unit or ground unit based on instructions. The processing module is used to manage data and control data forwarding. The processing module is connected to the storage module via signals. The communication between the storage module and the processing module uses a file handle control protocol.

[0026] The system comprises a storage unit and a processing unit. The storage unit includes a solid-state storage unit and a main control FPGA, responsible for high-speed data reception, processing, storage, and playback. The processing unit is used for file system management and control information forwarding. First, the processing unit employs a bitmap structure for storage space management, with each bit corresponding to the smallest operating unit of the storage medium, achieving efficient and reliable space allocation and reclamation. An innovative fixed-length instruction data packet is designed for interaction between the main control FPGA and upper-layer software. This packet integrates fields such as opcode, channel identifier, logical block address, and transmission length, abstracting complex file operations into simplified instruction interactions, significantly reducing communication overhead. Finally, through a file handle mechanism, a unique handle is allocated by the storage unit as a file index when a file is created, and all subsequent operations are performed through this handle, avoiding the transmission of lengthy pathnames. This invention, through the collaborative design of software bitmap management and simplified hardware instructions, achieves a balance between the flexibility of file system macro management and the ultimate efficiency of underlying data flow control, significantly improving the storage efficiency and real-time performance of massive data, especially multiple 10 Gigabit concurrent data streams, in a spaceborne environment. It effectively solves the problems of high management overhead, low small file read / write performance, and metadata corruption caused by single-event flips in massive data storage in spaceborne environments, and significantly improves the overall throughput and reliability of the system.

[0027] The storage module in this embodiment can be configured as follows, or other configurations can be used without limitation.

[0028] 1. Main Control FPGA: Employs an industrial-grade high-performance FPGA, the Xilinx Virtex-7 series XC7VX690T-FFG1761. Its internal logic functions include: High-speed interface controller: Implements physical connections and protocol parsing with the payload data source (10 Gigabit Ethernet) and downlink channel (AURORA). Data path engine: Includes a multi-channel DMA controller and a data frame formatting module. Storage controller: Implements Flash Transport Layer (FTL) functions, including wear leveling, bad block management, garbage collection (GC), and ECC encoding / decoding. Command parser: Dedicated to parsing the 8-byte control information frames defined in this invention. File handle management module: Maintains a file information table, responsible for the allocation, reclamation, and querying of file handles. Bitmap caching and management: Caches some bitmap information in the FPGA's internal BRAM resources to accelerate allocation decisions.

[0029] 2. Storage Module: Composed of multiple solid-state storage units connected to the FPGA via multiple parallel channels. Each channel can operate independently to achieve concurrent access and bandwidth aggregation.

[0030] Preferably, the length of the data written to the solid-state storage unit is a preset length, and the data written to the solid-state storage unit is continuously mapped to the physical storage address space of the solid-state storage array.

[0031] By pre-mapping fixed-length data blocks to physical addresses, high-speed sequential read / write and pipelined parallel processing are achieved, significantly improving storage throughput and response speed. Real-time bitmap marking of storage status, combined with fast file handle indexing, ensures efficient storage space allocation, controllable data integrity, and reduced management complexity. Standardized data unit design and atomic operation mechanisms adapt to the space radiation environment, guaranteeing long-term operational stability and meeting the core requirements of aerospace missions for highly reliable storage.

[0032] Preferably, the solid-state storage unit uses a bitmap structure to manage the file system storage space. The bit data of the bitmap is adapted to the smallest addressable storage unit of the solid-state storage unit. The status of the smallest addressable storage unit is identified based on the bit data. The working data includes at least occupied and idle states.

[0033] Bitmap-based bit-level mapping enables granular state tracking of storage units, accurately identifying the occupied / idle status of each smallest addressable unit. This bitmap-based state interpretation mechanism allows the storage controller to quickly locate available blocks and execute read / write operations, significantly improving data access efficiency and task scheduling timeliness. Real-time monitoring of storage unit status via bit-level state markers effectively prevents data corruption caused by single-event upsets due to radiation.

[0034] Second Embodiment See Figure 2 , Figure 4 and Figure 5 A second aspect of the present invention provides a spaceborne solid-state storage method based on control information and file handles, comprising: Send control data of a preset length to the storage module. The control data includes at least an opcode, a channel identifier, a logical block address, and a transmission length. The opcode is used to specify the command type, the channel identifier is used to identify the data source of several channels, and the logical block address and transmission length are used to specify the operation start position and the amount of operation data. Based on the first control data, the storage module obtains file data that is compatible with each data channel through data packet encapsulation, pipeline processing and arbitration scheduling; The storage space of the storage module is managed by bitmap marking. The bitmap is mapped to the file index table through file handles to realize fast combination retrieval of combined elements. The bit data of the bitmap is adapted to the smallest addressable storage unit of the solid-state storage unit.

[0035] In this embodiment, the processing unit software runs on the onboard computer (OBC), and its main responsibilities include: providing application programming interfaces (APIs) for task applications to call, such as file_create(), file_write(), file_read(), and file_close(); maintaining a global storage space bitmap. Each bit in this bitmap represents the free / occupied status of a minimum operating unit (1MB) in the solid-state storage system; maintaining a file index database to record macro-level metadata such as filename, file handle, file size, and creation time; and converting file operation API calls into standard 8-byte control instructions, which are then sent to the main control FPGA via the bus.

[0036] The main control FPGA internally establishes an independent input FIFO for each data channel. When multiple data streams arrive simultaneously, an arbiter (Round-Robin algorithm) serves each channel in turn, packaging the data retrieved from their respective FIFOs into fixed-length storage frames (8KB). Each storage frame is appended with a HEADER containing channel ID information. These frames are then written to the corresponding channel's independent solid-state storage unit, naturally forming independent file streams. This hardware-level concurrent processing mechanism ensures high throughput and real-time performance. A global bitmap and file information table are the core metadata. The software stores three copies of these in multiple different physical blocks within the solid-state storage unit. Any update operation employs atomic operations (first writing to the internal cache, then to the high-end backup area, and finally updating the information in the non-volatile memory), ensuring that at least one complete copy is available at any time, preventing metadata corruption due to single-event upsets or unexpected power outages. Each 8-byte control frame is contained in the CCSDS remote control frame format (including XOR and checksum), guaranteeing its correctness at the transport layer. Solid-state storage management: The FTL implemented within the solid-state storage system includes robust bad block management, ECC, and wear leveling algorithms to ensure the reliability of the underlying media.

[0037] By using pre-defined length control data (including opcodes / channel identifiers / logical addresses), deterministic operations on solid-state storage units are achieved, ensuring independent control and atomic execution of multi-source data streams. Real-time bitmap marking of storage status, combined with direct mapping of file handles to the index table, enables nanosecond-level response times for data retrieval and storage allocation, significantly improving read / write efficiency. Based on bit-level space management and a pipelined data processing architecture, it effectively resists spatial radiation interference, ensuring data integrity and long-term operational stability under high-throughput conditions.

[0038] The specific process includes the following: Storage module management is implemented by a global bitmap at the upper layer. This bitmap is a contiguous array of bits, with the total number of bits matching the size of the logical block address (LBA) space of the storage module. When a file needs to be created, the software searches for free bits consecutively in the bitmap based on the file size, marks them as occupied, and associates these contiguous LBA spaces with a file. File handle generation and usage: When the upper-layer software requests file creation, it sends an 8-byte control data to the main FPGA. Upon receiving the instruction, the main FPGA searches for a free entry in its file information table. This table is a pre-allocated array structure, with each entry corresponding to an open file, storing its bitmap metadata (starting LBA, size, status, etc.). The main FPGA returns the array index number of this entry as a file handle to the upper-layer software. Afterward, for all read and write operations on this file, the software only needs to use this handle in the instructions, without needing to transmit detailed information such as the LBA address. The main FPGA directly indexes the file information table entry through the handle to obtain all its physical storage information. Simplified control information frame format and interaction flow: Instructions are defined in a fixed 8-byte (64-bit) format; see [link to specific format] for details. Figure 4 This embodiment does not impose any format restrictions. Figure 4 Field descriptions: valid: 1 indicates that the address block is valid; Send_id[1:0] channel identifier; Cmd[7:0] opcode, see details for specific format. Figure 5 Tot_sec[15:0] Sector count per operation (unit: 512B); Start_lba[31:0] Logical block address: starting lba address (unit: 512B).

[0039] See Figure 3 Preferably, the step of managing the storage space of the storage module through bitmap marking further includes: The state data based on bitmap tags is mapped one-to-one with the logical address of the solid-state storage unit.

[0040] By employing a 1:1 mapping between bitmaps and logical addresses, storage unit-level status awareness is achieved within seconds, supporting real-time space allocation and conflict avoidance, thus eliminating the risk of resource contention. Address translation overhead is eliminated, and data flows directly to the physical storage area. Combined with a pipelined architecture, throughput approaches the theoretical limits of the medium, meeting the demands of high-speed data transmission. Bitmap-redundant storage and EDAC verification construct a radiation-resistant barrier, reducing anomaly recovery time to milliseconds, ensuring the integrity and maintainability of long-term on-orbit data.

[0041] Preferably, the step of mapping a bitmap to a file index table via a file handle to achieve fast combined element retrieval further includes: The file handle is assigned and generated by the storage control unit when the file is created. Its value is the array index number of the file bitmap in memory. The complete bitmap metadata of the file can be obtained through this index.

[0042] The file handle serves as an index number for the memory array, establishing a unique mapping between the file and the bitmap, enabling O(1) time complexity retrieval of file metadata and significantly improving the location speed of the target file. Complete bitmap metadata can be directly extracted via the handle, supporting logical association and rapid reassembly across storage blocks, meeting the retrieval needs of multi-payload data fusion storage. The handle generation and bitmap binding mechanism isolates the impact of physical storage changes on upper-layer applications, ensuring the reliability of file system addressing and operations during long-term on-orbit missions.

[0043] Preferably, the storage module receives and sends payload data and controls the physical layer of the solid-state storage unit through a high-speed serial interface protocol.

[0044] A high-speed serial interface is used to achieve Gbps-level direct data connection, eliminating the signal synchronization delay of traditional parallel buses and meeting the real-time access requirements of massive data such as remote sensing images and scientific exploration. The read / write timing, voltage margin, and ECC verification mechanism of the solid-state storage unit are directly controlled, ensuring the data integrity of NAND / FRAM chips in the space radiation environment from a hardware perspective. A standardized serial protocol unifies the interaction interface between the payload and the storage module, reducing board-level wiring complexity and improving the resource scheduling efficiency and system scalability of the onboard computer.

[0045] Preferably, the step of the storage module receiving and sending payload data via a high-speed serial interface protocol further includes: The payload data is received through a high-speed serial interface protocol and the first payload data is obtained by processing a frame of preset length. The first payload data is written to the solid-state storage unit through the storage frame sequence of the storage module.

[0046] By processing data in pre-defined length frames, payload data is broken down into fixed-length units, matching the optimal read / write granularity of solid-state storage, eliminating the overhead caused by variable-length data, and achieving continuous write throughput. The storage frame serialization mechanism strictly constrains the data write order, avoiding write conflicts caused by parallel contention, and, combined with the deterministic latency characteristics of the high-speed serial interface, meets the strong real-time requirements of remote sensing satellites and other missions for data persistence.

[0047] See Figure 5 Preferably, the step of writing the first payload data into the solid-state storage unit based on the storage frame sequence of the storage module further includes: Based on the first load data, multiple channels are processed in parallel through the caching of the storage module and the real-time arbitration mechanism; each channel has independent file storage.

[0048] Reference Figure 5 File write interaction example: The software calls the file_write API. The software layer generates 8 bytes of control data: see figure opcode = 8'h10 (write operation), channel ID = target channel, LBA = starting address found through the handle, length = length of data to be written. This control frame is sent to the FPGA via the bus. The FPGA's command parser decodes the frame and prepares to receive data based on the LBA and length. The FPGA replies with a "ready" signal, and the software layer / data source begins transmitting payload service data. The FPGA writes the data to the specified physical location of the solid-state storage system and updates its internal state upon completion.

[0049] By dynamically scheduling multi-channel data streams through caching and real-time arbitration mechanisms, simultaneous writing of multiple load sources to solid-state storage is achieved. Throughput increases with the number of channels, meeting the demands of high-concurrency data transmission. Each channel is configured with an independent file storage area, physically isolating data streams from different tasks. This avoids I / O contention caused by cross-interference and provides dedicated storage bandwidth for critical tasks. Based on the arbitration mechanism, working channels can be flexibly added or removed. In the event of a single channel failure, only local data is affected, not non-resident tasks. Combined with the independent storage structure, precise isolation of fault domains is achieved, significantly improving system robustness.

[0050] Preferably, the addressing unit for control data is the minimum operating space of the storage module, and the file attribute control flag transmits the file logical address and transmission channel identification information.

[0051] By using the smallest operating space as the addressing unit, byte-level or even finer-grained data manipulation is achieved. Combined with a direct file logical address transmission mechanism, absolute accuracy in data writing / reading is ensured, avoiding redundant read / write operations caused by traditional page alignment methods. Logical addresses and transmission channel identifiers are synchronously transmitted through file attribute control flags, enabling the storage controller to dynamically associate data stream sources with target storage areas. This achieves resource mapping between spaces and channels for multi-load tasks, optimizing bandwidth utilization. The design of minimum operating space addressing and file attribute binding naturally supports atomic transaction operations: a single control data packet can complete the entire process of address resolution, channel verification, and data writing, effectively reducing the risk of data inconsistency caused by interruptions.

[0052] In the description of this application, it should be noted that the terms "inner" and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship commonly used when the product is in use. They are used only for the convenience of describing this application and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Furthermore, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0053] It should also be noted that, unless otherwise explicitly specified and limited, the terms "setup" and "connection" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0054] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific identification content executed by the system and device described above can be referred to the corresponding process in the foregoing method embodiments.

[0055] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they shall still fall within the protection scope of the present invention.

Claims

1. A spaceborne solid-state storage system based on control information and file handles, characterized in that, include: The storage module provides storage functionality and includes a solid-state storage unit and a main control FPGA. The main control FPGA is used to receive high-speed payload data, acquire and write the high-speed payload data to the solid-state storage unit, and transmit the data to the payload unit or ground unit based on instruction-driven data transmission. The processing module is used to manage data and control data forwarding, and the processing module is connected to the storage module via a signal. The communication between the storage module and the processing module uses a file handle control protocol.

2. The spaceborne solid-state storage system based on control information and file handles according to claim 1, characterized in that, The length of the data written to the solid-state storage unit is a preset length, and the data written to the solid-state storage unit is continuously mapped to the physical storage address space of the solid-state storage array.

3. The spaceborne solid-state storage system based on control information and file handles according to claim 1, characterized in that, The solid-state storage unit uses a bitmap structure to manage the file system storage space. The bit data of the bitmap is adapted to the minimum addressable storage unit of the solid-state storage unit. The status of the minimum addressable storage unit is identified based on the bit data. The working data includes at least occupied and idle states.

4. A spaceborne solid-state storage method based on control information and file handles, characterized in that, include: The control data of a preset length is sent to the storage module. The control data includes at least an operation code, a channel identifier, a logical block address, and a transmission length. The operation code is used to specify the command type, the channel identifier is used to identify the data source of several channels, and the logical block address and transmission length are used to specify the operation start position and the amount of operation data. Based on the first control data, the storage module obtains file data adapted to each data channel through data packet encapsulation, pipeline processing, and arbitration scheduling. The storage space of the storage module is managed by bitmap marking. The bitmap is mapped to the file index table through file handles to realize fast combination retrieval of combined elements. The bit data of the bitmap is adapted to the smallest addressable storage unit of the solid-state storage unit.

5. The spaceborne solid-state storage method based on control information and file handles according to claim 4, characterized in that, The step of managing the storage space of the storage module using bitmap marking further includes: The state data based on bitmap tags is mapped one-to-one with the logical address of the solid-state storage unit.

6. The spaceborne solid-state storage method based on control information and file handles according to claim 4, characterized in that, The steps for quickly combining and retrieving elements by mapping a bitmap to a file index table using a file handle further include: The file handle is allocated and generated by the storage control unit when the file is created. Its value is the array index number of the file bitmap in memory. The complete bitmap metadata of the file can be obtained through this index.

7. The spaceborne solid-state storage method based on control information and file handles according to claim 4, characterized in that, The storage module receives and sends payload data and controls the physical layer of the solid-state storage unit through a high-speed serial interface protocol.

8. The spaceborne solid-state storage method based on control information and file handles according to claim 7, characterized in that, The step of the storage module receiving and sending payload data via a high-speed serial interface protocol further includes: The payload data is received through a high-speed serial interface protocol and the first payload data is obtained by processing a frame of preset length. Based on the first payload data, it is written to the solid-state storage unit through the storage frame sequence of the storage module.

9. The spaceborne solid-state storage method based on control information and file handles according to claim 7, characterized in that, The step of writing the first payload data into the solid-state storage unit through the storage frame sequence of the storage module further includes: Based on the first load data, multiple channels are processed in parallel through the caching and real-time arbitration mechanism of the storage module; each channel has independent file storage.

10. The spaceborne solid-state storage method based on control information and file handles according to claim 4, characterized in that, The addressing unit of the control data is the minimum operating space of the storage module, and the file attribute control flag transmits the file logical address and transmission channel identification information.

Images