A method and system for data aggregation and distribution of gateway stations and reverse positioning repair

Abstract

The application discloses a kind of gateway station data convergence distribution and reverse positioning repair method and system, the method includes: receiving satellite link original data frame, establishing source data interval and source positioning record;According to the boundary of check block and processing input dependence, determine the minimum reconstructable source data block;Generation distribution data unit is generated by protocol analysis, data splicing and format conversion, and conversion mapping chain is constructed;Obtain data unit version and abnormal output interval, when version is consistent, reverse traverse conversion mapping chain, locate the source data block to be repaired;When local cache is not hit, request satellite retransmission according to source positioning record;According to the operation mark and parameter version, reconstruct repair data unit, and send to distribution target.The application realizes the reverse positioning of abnormal output to source data and local reconstruction, reduces the amount of retransmission data, improves the utilization rate of satellite-ground link and abnormal repair efficiency.

Description

Technical Field

[0001] This invention relates to the field of satellite communication and data processing technology, and in particular to a method and system for gateway station data aggregation and distribution and reverse positioning and repair. Background Technology

[0002] With the development of low-Earth orbit satellite constellations, satellite internet, and integrated space-ground information networks, the number of satellites and the scale of satellite-to-ground data interaction are constantly increasing. As a data interaction node between the satellite network and the terrestrial network, the gateway station needs to receive raw data such as telemetry data, remote sensing data, payload data, and status monitoring data transmitted from the satellite link. It then performs verification, protocol parsing, data splicing, format conversion, caching, and distribution processing on the received raw data before sending the processed data to ground data centers, service platforms, or other distribution targets.

[0003] Raw data transmitted via satellite links typically arrives at the gateway station in the form of data frames. Due to satellite transit time, link status, and transmission environment, different raw data frames may belong to different satellites, receiving tasks, receiving arcs, or virtual channels. When processing raw data frames, a single distributed data unit may be generated from multiple discontinuous or cross-frame source data intervals. The same source data interval may also undergo protocol parsing, data concatenation, and distribution format conversion to form multiple output intervals. Therefore, a multi-level, many-to-many data conversion relationship may exist between source data and distributed data.

[0004] When the distribution target detects missing data, inconsistent verification, or localized data anomalies in a distribution data unit, the returned anomaly information typically points to the distribution data unit and its abnormal output range, rather than directly to the original data range transmitted via the satellite link. When a continuous mapping record between the source and output data ranges is missing, the gateway station struggles to accurately determine the original data frame and its range that generated the anomaly based on the abnormal output range. This usually necessitates reprocessing a larger range of cached data or re-acquiring the entire satellite data corresponding to the data unit, thereby increasing data read volume, reprocessing volume, and link transmission volume.

[0005] Furthermore, satellite-to-ground links are characterized by bandwidth limitations, limited available time windows, and dynamic changes in link status. If the data to be repaired has been released from the local cache, it is necessary to re-request satellite data based on the satellite, receiving task, receiving arc, virtual channel, and original frame position corresponding to the original data. How to retain sufficient data relationships to support reverse anomaly localization during data processing and distribution, and how to determine the range of source data capable of independently completing verification and reprocessing when local anomalies occur in the distributed data, are technical issues that need to be considered during the data aggregation and distribution process at gateway stations.

[0006] For example, the invention patent application with publication number CN114513247A, entitled "A Method for Distributing Multi-Satellite Control and Management Data Information," discloses configuring a distribution strategy according to the link establishment and packet processing requirements of satellite control and management data in the telemetry and control plan, and processing and distributing satellite data products sent by the telemetry and control station or information products sent by the user center according to the configured distribution strategy. The distribution strategy includes source end address and port, service data, transmission protocol, data conversion format, target end address and port, storage method, key identifier, transmission start time and transmission stop time, and determines whether to retransmit data based on the data distribution status returned by the target end. Summary of the Invention

[0007] This invention is applied to the process of a gateway station receiving and distributing satellite data. The gateway station receives raw data frames transmitted via the satellite link, performs verification, protocol parsing, data splicing, and distribution format conversion on the raw data frames, and sends the generated distribution data units to a ground data center, service platform, or other distribution targets. When a distribution target reports a local anomaly in a distribution data unit, the gateway station reverse-engineers the corresponding source data range based on the anomaly output interval, obtains the corresponding source data, and re-executes the necessary processing operations to complete the local repair of the anomaly data.

[0008] When a local anomaly occurs in the distributed data at an existing gateway station, it is difficult to accurately locate the corresponding source data range from the abnormal output range. This often requires reprocessing a large range of cached data or re-acquiring the satellite data corresponding to the entire distributed data unit, resulting in a large amount of duplicated data processing and increased data retransmission overhead of the satellite-to-ground link.

[0009] Based on this, the technical problem to be solved by the present invention is to provide a method and system for data aggregation, distribution and reverse positioning repair at gateway stations, so as to establish a conversion mapping relationship between the source data range and the distribution data output range, and when a local anomaly occurs in the distribution data, determine the range of source data that can be independently verified and reprocessed according to the abnormal output range, thereby narrowing the range of data reprocessing and the range of satellite data retransmission.

[0010] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0011] A method for data aggregation, distribution, and reverse location repair at a gateway station includes:

[0012] Receive raw data frames transmitted from the satellite link, and establish source data intervals and source positioning records based on satellite identifier, receiving task identifier, receiving arc segment identifier, virtual channel identifier, raw frame sequence number and data offset;

[0013] Based on the boundary of the verification block and the input dependency range of protocol parsing, data splicing and distribution format conversion, the source data range is expanded until the expanded data range can independently complete the verification and corresponding processing, and the smallest reconfigurable source data block with block identifier is obtained.

[0014] Perform protocol parsing, data splicing, and distribution format conversion on the smallest reconfigurable source data block to generate distribution data units; for each processing operation record, input data block, input range, output data block, output range, operation identifier, and parameter version, construct a transformation mapping chain according to the processing order, and record the data unit identifier and current version of the distribution data unit in the last-level transformation mapping record of the transformation mapping chain;

[0015] Obtain the abnormal data unit identifier, distribution data unit version, and abnormal output range returned by the distribution target; when the distribution data unit version is consistent with the current version recorded in the transformation mapping chain, traverse the transformation mapping chain in reverse from the abnormal output range to expand the obtained source data range to the boundary of the corresponding smallest reconstructable source data block, and obtain the source data block to be repaired.

[0016] Query the local cache; if a source data block to be repaired exists, read the source data block to be repaired; if no source data block to be repaired exists, generate a satellite data retransmission request based on the source positioning record and obtain the source data block to be repaired.

[0017] Based on the operation identifier and parameter version of the transformation mapping chain record, the corresponding processing operation is re-executed to generate a repair data unit containing the replacement output range. The repair data unit is sent to the distribution target, and the repair status of the corresponding transformation mapping record is updated.

[0018] Preferably, establishing the source data range includes:

[0019] The original data frames are grouped according to the satellite identifier, receiving task identifier, receiving arc segment identifier, and virtual channel identifier;

[0020] Sort and verify each group of original data frames according to the original frame sequence number and data offset;

[0021] Merge consecutively sequenced and verified original data frames into a source data interval; when there is a missing sequence number between adjacent original data frames, or when there is an original data frame that fails verification, determine the end position of the previous verified original data frame as the end position of the source data interval, and record the corresponding missing data range in the source positioning record.

[0022] Preferably, obtaining the minimum reconfigurable source data block includes:

[0023] Determine the initial data range based on the boundaries of the check block;

[0024] Determine the range of input data that each processing operation depends on to generate the corresponding output data;

[0025] When the input data range exceeds the initial data range, the initial data range is extended to the adjacent check block that contains the corresponding input data range, and it is re-evaluated whether the extended data range contains all the input data on which each processing operation depends.

[0026] Until the expanded data range includes all the input data on which each processing operation depends, the expanded data range is determined as the minimum reconfigurable source data block, and a corresponding block identifier is generated for the minimum reconfigurable source data block.

[0027] Preferably, the transformation mapping chain includes multiple transformation mapping records, each non-primary transformation mapping record records at least its predecessor transformation mapping record identifier, and each non-final transformation mapping record records at least its successor transformation mapping record identifier;

[0028] For any output interval, when the output interval is generated by multiple input data blocks, the multiple input data blocks and the corresponding input interval are recorded as the set of input data blocks for the output interval;

[0029] For any input data block, when the input data block participates in the generation of multiple output intervals, a transformation mapping record between the input data block and each output interval is established respectively to form a multi-level many-to-many transformation mapping relationship between the minimum reconfigurable source data block and the distributed data unit.

[0030] Preferably, the distribution target returns abnormal feedback information, which includes the distribution target identifier, abnormal data unit identifier, distribution data unit version, and abnormal output range, and includes the reception verification value corresponding to the abnormal output range when the abnormal output range has been fully received.

[0031] The final-level conversion mapping record of the conversion mapping chain also records the current version corresponding to each distribution target, each output interval, and the transmission verification value corresponding to each output interval according to the distribution target identifier. When the version of the distribution data unit is consistent with the current version corresponding to the distribution target identifier, and at least one of the following conditions is met, the abnormal feedback information is determined to be valid abnormal feedback information: the abnormal output interval was not completely received; the abnormal output interval has been completely received and the received verification value is inconsistent with the transmission verification value corresponding to the same output interval.

[0032] Preferably, the reverse traversal transformation map chain includes:

[0033] Filter out the final-level transformation mapping records from the transformation mapping chain where the output range overlaps with the abnormal output range;

[0034] Based on the identifier of the preceding transformation mapping record of each final-level transformation mapping record, the corresponding transformation mapping record is searched level by level in reverse order of processing until the primary transformation mapping record with the source data range as input data is found.

[0035] The source data ranges corresponding to the found primary transformation mapping records are merged, and the merged source data range is extended to the boundary of the corresponding smallest reconstructable source data block to obtain the source data block to be repaired.

[0036] Preferably, obtaining the source data block to be repaired includes:

[0037] Query the local cache index based on the block identifier of the source data block to be repaired;

[0038] When the corresponding local cache address is found, the source data block to be repaired is read from the local cache address and verified.

[0039] When no corresponding local cache address is found, a pre-established task association record is queried based on the satellite identifier, receiving task identifier, and receiving arc identifier in the source positioning record to obtain the corresponding onboard data storage task identifier. The task association record records the correspondence between the satellite identifier, receiving task identifier, receiving arc identifier, and onboard data storage task identifier. The source data range corresponding to the source data block to be repaired is converted into a satellite retransmission range. A satellite data retransmission request is generated based on the satellite identifier, onboard data storage task identifier, virtual channel identifier, start original frame sequence number, end original frame sequence number, and boundary data offset. The received retransmission data is verified, and the retransmission data that passes the verification and completely covers the satellite retransmission range is identified as the source data block to be repaired.

[0040] Preferably, the generation and processing of the repair data unit includes:

[0041] According to the processing order, operation identifier and parameter version of the transformation mapping chain record, the corresponding processing operation is re-executed on the source data block to be repaired to obtain repair output data covering the abnormal output range;

[0042] Read the current version of the distribution data unit corresponding to the distribution target that returned valid exception feedback information, determine the current version as the base version, and increment the base version to obtain the repair version; calculate the verification value of the repair output data to obtain the repair verification value; based on the exception data unit identifier, distribution target identifier, base version, repair version, replacement output range corresponding to the repair output data, repair verification value, and repair output data, encapsulate to obtain the repair data unit;

[0043] Send the repair data unit to the distribution target that returned valid error feedback information;

[0044] Each transformation mapping record also records the distribution status and repair status; a reference count is set for each minimum reconfigurable source data block, which is the number of transformation mapping records that reference the corresponding minimum reconfigurable source data block and satisfy any of the following states: the distribution status is unconfirmed, or the repair status is pending repair or repairing.

[0045] After receiving the distribution confirmation or repair confirmation information returned by the distribution target, update the distribution status or repair status of the corresponding transformation mapping record, and redetermine the reference count of the corresponding minimum reconfigurable source data block; when the reference count is zero, release the cache space occupied by the corresponding minimum reconfigurable source data block.

[0046] This invention also provides a gateway station data aggregation, distribution, and reverse positioning and repair system, comprising:

[0047] The source data organization module is used to receive raw data frames transmitted from the satellite link and establish source data intervals and source positioning records based on satellite identifier, receiving task identifier, receiving arc segment identifier, virtual channel identifier, raw frame sequence number and data offset.

[0048] The reconstructed block determination module is used to expand the source data range based on the boundary of the verification block and the input dependency range of protocol parsing, data splicing and distribution format conversion, until the expanded data range can independently complete the verification and corresponding processing, and obtain the smallest reconstructable source data block with block identifier.

[0049] The convergence mapping module is used to perform protocol parsing, data splicing, and distribution format conversion on the smallest reconfigurable source data block to generate distribution data units. For each processing operation record, the module constructs a transformation mapping chain according to the processing order, based on the input data block, input range, output data block, output range, operation identifier, and parameter version. The module also records the data unit identifier and current version of the distribution data unit in the last-level transformation mapping record of the transformation mapping chain.

[0050] The anomaly localization module is used to obtain the anomaly feedback information returned by the distribution target. The anomaly feedback information includes the anomaly data unit identifier, the distribution data unit version, and the anomaly output range. When the distribution data unit version is consistent with the current version recorded in the transformation mapping chain, the transformation mapping chain is traversed in reverse by the anomaly output range to expand the obtained source data range to the boundary of the corresponding minimum reconstructable source data block, thereby obtaining the source data block to be repaired.

[0051] The repair acquisition module is used to query the local cache. If the source data block to be repaired exists in the local cache, it reads the source data block to be repaired. If the source data block to be repaired does not exist in the local cache, it generates a satellite data retransmission request based on the source positioning record and obtains the source data block to be repaired.

[0052] The repair distribution module is used to re-execute the corresponding processing operation based on the operation identifier and parameter version of the transformation mapping chain record, generate repair data units containing the replacement output range, send the repair data units to the distribution target, and update the repair status of the corresponding transformation mapping record.

[0053] Preferably, the gateway station data aggregation and distribution and reverse positioning repair system also includes a satellite link interface, a data buffer, and a terrestrial network interface;

[0054] The satellite link interface is connected to the source data organization module and the repair acquisition module respectively, and is used to receive the original data frame, send satellite data retransmission request and receive the corresponding retransmission data.

[0055] The data cache is connected to the source data organization module, the aggregation mapping module, the anomaly location module, and the repair acquisition module, respectively, and is used to store the source data range, the minimum reconfigurable source data block, the source location record, and the transformation mapping chain.

[0056] The ground network interface is connected to the convergence mapping module and the repair distribution module, respectively, and is used to send distribution data units and repair data units to the distribution target, and to receive abnormal feedback information, distribution confirmation information and repair confirmation information returned by the distribution target.

[0057] Compared with the prior art, the present invention has at least the following beneficial effects:

[0058] (1) This invention establishes a conversion mapping chain for processing operations such as protocol parsing, data splicing and distribution format conversion, so that the output range of the distributed data can be back-linked to the corresponding source data range, providing a data basis for the accurate location of local abnormal data.

[0059] (2) The present invention extends the range of source data obtained by reverse positioning to the boundary of the smallest reconfigurable source data block, so that the data to be repaired can be independently verified and reprocessed, and can avoid repeated processing of a large range of source data that is unrelated to the abnormal output range, thereby reducing the amount of data read and the consumption of computing resources.

[0060] (3) The present invention can preferentially obtain the source data block to be repaired from the local cache, and generate a satellite data retransmission request based on the source positioning record when the corresponding data does not exist in the local cache, thereby narrowing the satellite data retransmission range and reducing the occupation of satellite-to-ground link resources.

[0061] (4) The present invention re-executes the processing operation according to the processing order, operation identifier and parameter version recorded in the transformation mapping chain, and maintains the data unit version for different distribution targets. The current version corresponding to the distribution target is used as the base version to generate the repair version. The distribution target only uses the repair output data to replace the corresponding output range when the base version is consistent, thereby avoiding the old version repair data from overwriting the current data and preventing the repair version of one distribution target from affecting other distribution targets, thus improving the accuracy of local data repair.

[0062] (5) The present invention sets reference counts based on the distribution and repair status of the conversion mapping record, and releases the corresponding cache space when there are no unconfirmed distribution tasks or incomplete repair tasks, so that the retention period of cached data matches the data distribution and repair process, thereby improving the utilization rate of the gateway station cache space. Attached Figure Description

[0063] Figure 1 A flowchart illustrating the data aggregation, distribution, and reverse positioning repair method for gateway stations provided in this embodiment of the invention;

[0064] Figure 2 This is a schematic diagram of the source data range, the minimum reconfigurable source data block, and the transformation mapping chain provided in an embodiment of the present invention.

[0065] Figure 3 This is a schematic diagram of the abnormal data reverse location and repair process provided in an embodiment of the present invention;

[0066] Figure 4 This is a schematic diagram of the module composition of the gateway station data aggregation, distribution, and reverse positioning and repair system provided in an embodiment of the present invention. Detailed Implementation

[0067] The technical solution of the present invention will be further described below with reference to the accompanying drawings. It should be understood that the following embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the present invention. Equivalent substitutions made by those skilled in the art to relevant parameters, device models, or specific algorithms without departing from the concept of the present invention are all possible implementations of the technical solution of the present invention.

[0068] Example 1

[0069] This embodiment provides a method and system for gateway station data aggregation, distribution, and reverse positioning repair, applicable to gateway stations with satellite link receiving capabilities, local data processing capabilities, data caching capabilities, and terrestrial network distribution capabilities.

[0070] The gateway station receives raw data frames transmitted via satellite link, performs verification, protocol parsing, data splicing, and distribution format conversion on the raw data frames, and sends the generated distribution data units to the ground data center, service platform, or other distribution targets. When a distribution target reports that a distribution data unit has missing data or verification anomalies, the gateway station reverse-engineers the corresponding source data range based on the abnormal output range, retrieves the corresponding source data from its local cache or satellite link, and re-executes the processing operations required to generate the abnormal output range, forming a repair data unit.

[0071] like Figure 1 As shown, the data aggregation, distribution, and reverse positioning repair method of the gateway station includes the following steps.

[0072] Step S101: Receive the raw data frames transmitted from the satellite link and establish the source data range and source positioning record.

[0073] The gateway station receives raw data frames via the satellite link interface. Raw data frames can be telemetry frames, remote sensing data frames, payload data frames, or other transmission frames conforming to satellite communication protocols. Raw data frames must at least have a header field to distinguish the data source and frame location.

[0074] The gateway station obtains the satellite identifier, reception task identifier, reception arc identifier, virtual channel identifier, original frame sequence number, and data offset from the frame header, reception task configuration, and link reception record of the original data frame. Among them, the reception arc identifier is used to distinguish the data reception process formed by the same satellite at different transit times; the data offset is used to indicate the position of the valid data in the data field of the original data frame.

[0075] When the original frame sequence number is looped around, the gateway station combines the receiving arc segment identifier and the arrival order of adjacent original data frames to convert the original frame sequence number into an extended frame sequence number that monotonically increases within the current receiving arc segment, so as to avoid the original data frames before and after the loop being incorrectly classified into the same continuous data range.

[0076] The gateway station groups the raw data frames according to the satellite identifier, receiving task identifier, receiving arc identifier, and virtual channel identifier, and sorts and verifies each group of raw data frames according to the extended frame sequence number and data offset. The verification includes frame length, frame header validity, channel decoding result, and frame check value.

[0077] For raw data frames with consecutive sequence numbers and passing verification, the gateway station merges them into source data intervals according to the original frame sequence number and data offset. The source data interval is represented by a start source position and an end source position, and each source position includes at least the original frame sequence number and the intra-frame data offset.

[0078] In this embodiment, the source data range, input interval, and output interval are all represented using left-closed, right-open intervals. For example, the interval [a, b) represents the data range starting from offset position a and ending before offset position b, with an interval length of ba. Two intervals overlap if their intersection is not empty. Using a unified interval representation method avoids duplicate calculations or omissions of the original frame boundaries, input interval boundaries, and replaced output interval boundaries.

[0079] When there is a missing sequence number between adjacent raw data frames, or when a raw data frame fails verification, the gateway station determines the end position of the previously verified raw data frame as the end position of the current source data interval and records the corresponding missing data range in the source location record. The missing data range includes at least the missing or failed original frame sequence number and its corresponding data offset.

[0080] The source location record includes satellite identifier, receiving task identifier, receiving arc identifier, virtual channel identifier, starting original frame sequence number, ending original frame sequence number, boundary data offset, receiving time, and verification status. It is used to convert the logical data range used within the gateway station into the original frame range that can be re-acquired through the satellite link.

[0081] Step S102: Determine the minimum reconfigurable source data block based on the boundary of the verification block and the input dependency range of the processing operation.

[0082] In this embodiment, the smallest range of source data capable of independently completing data verification, protocol parsing, data concatenation, and distribution format conversion is defined as the minimum reconfigurable source data block. The minimum reconfigurable source data block is not divided according to a fixed byte length, but rather determined based on the data verification method and the actual range of input data that each processing operation depends on.

[0083] A checksum block is a range of data with independent verification criteria. When a raw data frame has an independent frame checksum, that raw data frame constitutes a checksum block; when multiple raw data frames share a checksum, those multiple raw data frames constitute a checksum block; when a protocol data packet has an independent packet checksum, the source data range corresponding to the complete protocol data packet can also be used as a checksum block.

[0084] The gateway first selects a verification block containing the data to be processed as the initial data range, and then obtains the input dependency range of each processing operation according to the processing order.

[0085] Each processing operation is configured with an input dependency description, which includes at least the operation identifier, the output range to be generated, the dependent input data blocks, the dependent input range, and the input completeness conditions. The protocol parsing operation determines the range of original data that the generation of a complete protocol data packet depends on based on the first packet pointer, protocol data packet length, and packet checksum field in the frame header; the data splicing operation determines the set of data fragments that the generation of a complete data object depends on based on the data object identifier, fragment sequence number, and total number of fragments; the distribution format conversion operation determines the range of input fields that the generation of the output range depends on based on the correspondence between the output fields and input fields in the distribution format template.

[0086] For the output range to be generated, the gateway station starts with the distribution format conversion operation and obtains the dependent input ranges corresponding to each processing operation in reverse order of processing sequence. The obtained dependent input ranges are merged and extended to the boundary of the check block. If the extended data range causes the previous processing operation to generate new input dependencies, the merging and boundary extension are continued until the data ranges obtained in the two steps are the same. The final data range is then determined as the smallest reconfigurable source data block.

[0087] For protocol parsing operations, when a complete protocol data packet crosses the boundary of the initial data range, the initial data range is extended to include the adjacent checksum block containing that protocol data packet. For data concatenation operations, when a complete data object is composed of multiple data fragments, the initial data range is extended to include all data fragments required to complete the concatenation. For distribution format conversion operations, when an output range is generated by multiple input fields, the initial data range is extended to include all input fields.

[0088] After each expansion, the gateway station re-evaluates whether the expanded data range includes all input data on which each processing operation depends. If input dependencies still exist beyond the current range, expansion continues to the adjacent check block; if all input dependencies are included within the current range, expansion stops, and the current data range is determined as the minimum reconfigurable source data block.

[0089] If the data needed during the boundary expansion process falls within the missing data range, the current data range is marked as pending completion. Boundary expansion continues after the corresponding missing data is obtained and verified.

[0090] The gateway station generates a block identifier for each minimal reconfigurable source data block. The block identifier can be generated by combining the satellite identifier, receiving task identifier, receiving arc identifier, virtual channel identifier, start original frame number, end original frame number, and boundary data offset. Alternatively, a digest can be calculated from the above fields, and the digest value is used as the block identifier. A correspondence is established between the block identifier and the source location record.

[0091] Step S103: Process the smallest reconfigurable source data block to generate a distribution data unit and construct a transformation mapping chain.

[0092] The gateway station sequentially performs protocol parsing, data concatenation, and distribution format conversion on the smallest reconfigurable source data block. Protocol parsing is used to extract protocol data packets and service fields from the original data frame; data concatenation is used to combine multiple data fragments into a complete data object according to the data object identifier, fragment sequence number, and total number of fragments; distribution format conversion is used to convert the complete data object into the corresponding file, data packet, or continuous data stream according to the distribution target requirements, forming a distribution data unit.

[0093] When a gateway station performs each processing operation, it establishes a corresponding transformation mapping record. Each transformation mapping record records at least:

[0094] The record identifier corresponding to the processing operation;

[0095] Input data blocks and input ranges;

[0096] Output data blocks and output ranges;

[0097] Operation identifier and parameter version;

[0098] At least one of the preceding transformation mapping record identifier and the following transformation mapping record identifier;

[0099] Distribute data unit identifiers and data unit versions;

[0100] Distribution status and repair status.

[0101] The operation identifier points to a handler that can be invoked again, such as a protocol parser, data splicer, or distribution format converter. The parameter version points to the protocol field configuration, splicing rules, or distribution format template used when performing this processing operation. Even after the handler or configuration parameters are updated, the gateway station can still invoke the same handler and configuration parameters as the original process based on the operation identifier and parameter version.

[0102] Input and output intervals are represented by the start and end offsets within the corresponding data blocks. When an output interval is generated by multiple input data blocks, the transformation mapping record records the multiple input data blocks and their corresponding input intervals, forming an input data block set. When an input data block participates in generating multiple output intervals, transformation mapping records are established between the input data block and each output interval separately.

[0103] The transformation mapping records are connected in the processing order to form a transformation mapping chain that points from the smallest reconfigurable source data block to the distributed data unit via protocol parsing results, data concatenation results, and distribution format conversion results. The transformation mapping chain can form multi-level many-to-many directed mapping relationships, and does not require a one-to-one relationship between adjacent processing operations.

[0104] After the distribution data unit is generated, the gateway station assigns a data unit identifier and an initial version to it, writes the current version, the transmission check value of the corresponding output interval, and the distribution target identifier into the final-level conversion mapping record, and sends the distribution data unit to the distribution target through the ground network interface.

[0105] like Figure 2 As shown below, the formation process of the source data range, the minimum reconfigurable source data block, and the transformation mapping chain is illustrated with a set of specific data.

[0106] The gateway station continuously receives raw data frames F1200, F1201, F1202, and F1203 under the same satellite identifier, receiving task identifier, receiving arc identifier, and virtual channel identifier. The data field length of each raw data frame is 1024 bytes, and each has an independent frame check value.

[0107] All four original data frames passed verification and their frame numbers are consecutive. Therefore, the four original data frames are merged into one source data interval. According to the logical offset representation within the source data interval, F1200, F1201, F1202 and F1203 correspond to [0, 1024), [1024, 2048), [2048, 3072) and [3072, 4096) respectively.

[0108] The protocol parsing operation extracts protocol data packets P1, P2, and P3 from the source data range. Among them:

[0109] P1 is formed by the combination of [768, 1024) of F1200 and [0, 512) of F1201;

[0110] P2 is formed by the combination of [512, 1024) of F1201 and [0, 512) of F1202;

[0111] P3 is formed by the combination of [512, 1024) of F1202 and [0, 512) of F1203.

[0112] In this embodiment, protocol data packets are concatenated according to adjacent overlapping processing windows. The first processing window W1 covers the acquisition time periods corresponding to P1 and P2, and the second processing window W2 covers the acquisition time periods corresponding to P2 and P3. The first processing window W1 and the second processing window W2 overlap in the acquisition time period corresponding to P2. The data concatenation operation concatenates P1 and P2 within the first processing window W1 into an intermediate data block C1, and concatenates P2 and P3 within the second processing window W2 into an intermediate data block C2. Therefore, P2, as overlapping data from two adjacent processing windows, participates in the generation of both C1 and C2.

[0113] The distribution format conversion operation converts C1 to the output range [0, 2048) of the distribution data unit D7, and converts C2 to the output range [2048, 4096] of D7.

[0114] For the above processing, the gateway station establishes conversion mapping records for the output intervals [0, 2048) from F1200 and F1201 to P1, from F1201 and F1202 to P2, from F1202 and F1203 to P3, from P1 and P2 to C1, from P2 and P3 to C2, from C1 to D7, and from C2 to D7, respectively.

[0115] Generating C1 requires complete P1 and P2, and this embodiment uses the complete original data frame as the check block. Therefore, the data range consisting of F1200, F1201, and F1202 is determined as the minimum reconfigurable source data block B1. Generating C2 requires complete P2 and P3. Therefore, the data range consisting of F1201, F1202, and F1203 is determined as the minimum reconfigurable source data block B2. B1 and B2 may have overlapping original data frames, but they can each independently generate their corresponding distribution output intervals.

[0116] After a distribution data unit is generated, the gateway station assigns it a data unit identifier and an initial version, and calculates a transmission checksum according to the output intervals corresponding to the final-level transformation mapping record. The final-level transformation mapping record stores the distribution data unit identifier, distribution target identifier, current version, output interval, and the corresponding transmission checksum. The transmission checksum can be a cyclic redundancy checksum or a digest value. The gateway station then sends the distribution data unit, the boundary information of each output interval, and the corresponding transmission checksum to the distribution target.

[0117] When the same data unit is sent to multiple distribution targets, the gateway station uses a combination of the data unit identifier and the distribution target identifier as a version index to maintain the current version of the data unit for each distribution target. When each distribution target receives the same data unit for the first time, their initial versions can be the same; if the version of a data unit corresponding to one distribution target changes due to repair, the versions of data units corresponding to other distribution targets are not changed. The distribution target identifier in the anomaly feedback information is used to query the current version corresponding to that distribution target.

[0118] When the same data distribution unit corresponds to multiple distribution targets, the gateway station establishes a target-specific transformation mapping record for each distribution target, and each group of target-specific transformation mapping records maintains the corresponding distribution status and repair status; the reference count of the minimum reconfigurable source data block is determined according to the status of each group of target-specific transformation mapping records.

[0119] Step S104: Obtain the abnormal feedback information returned by the distribution target, and reversely determine the source data block to be repaired.

[0120] After receiving the distributed data unit, the distribution target performs an integrity check based on the data unit identifier, data unit version, data length, segment sequence number, and checksum. If a data segment is missing or the checksum is inconsistent, the distribution target generates an anomaly feedback message. This feedback message includes the distribution target identifier, the abnormal data unit identifier, the distributed data unit version, and the abnormal output range. If the abnormal output range has been fully received, the feedback message also includes the corresponding reception checksum.

[0121] After receiving the abnormal feedback information, the gateway station queries the corresponding target-specific conversion mapping record based on the abnormal data unit identifier and the distribution target identifier, and reads the current version corresponding to the distribution target and the transmission verification value of the output range to which the abnormal output range belongs.

[0122] When the version of the distribution data unit carried in the abnormal feedback information is inconsistent with the current version corresponding to the distribution target, the repair is not initiated based on the abnormal feedback information, and version mismatch information is returned to the distribution target to avoid the abnormal feedback of the old version triggering the repair of the current version data.

[0123] When the version of the distributed data unit is consistent with the current version corresponding to the distribution target, the abnormal feedback information shall be determined as valid abnormal feedback information if at least one of the following conditions is met: the abnormal output interval was not fully received; the abnormal output interval has been fully received and the received check value is inconsistent with the sent check value corresponding to the same output interval.

[0124] When an abnormal output interval is not fully received, the gateway station determines the validity of the abnormal feedback information based on the missing interval information and does not require the distribution target to calculate the receive checksum corresponding to the missing data. When an abnormal output interval has been fully received but the data verification fails, the output interval corresponding to the receive checksum and the transmit checksum are the same. When an abnormal output interval spans multiple final-level transformation mapping records, the distribution target returns the receive checksum corresponding to each output interval, and the gateway station performs checksum comparisons for each.

[0125] The gateway station filters out final-level transformation mapping records from the transformation mapping chain where the output range overlaps with the abnormal output range, and adds the filtered records to the set of records to be traversed. Then, based on the identifier of the preceding transformation mapping record of each final-level transformation mapping record, it searches for the corresponding transformation mapping record level by level in reverse order of processing until the primary transformation mapping record with the source data range as input data is found.

[0126] For processing operations such as splicing, rearranging, or combining fields, where the input range cannot be calculated by offset ratio, the set of input data blocks and the corresponding input range stored in the conversion mapping record are read directly, and the input range is not calculated based on the output range ratio.

[0127] The gateway merges the source data range corresponding to the primary transformation mapping record found, and extends the merged source data range to the boundary of the corresponding minimum reconstructable source data block to obtain the source data block to be repaired.

[0128] Step S105: Obtain the source data block to be repaired from the local cache or satellite link.

[0129] The gateway station queries its local cache index based on the block identifier of the source data block to be repaired. The cache index records at least the block identifier, cache address, data length, cache check value, and cache status.

[0130] When the corresponding cache address is found, the gateway station reads the source data block to be repaired from that cache address and recalculates the checksum. If the calculated checksum matches the cache checksum in the cache index, the read data is used for subsequent reprocessing. If the checksum does not match, the cached data is determined to be unusable and processed as if no cached data was found.

[0131] When no corresponding cache address is found, the gateway station converts the logical source data range corresponding to the source data block to be repaired into a satellite retransmission range based on the source location record. The satellite retransmission range includes the starting original frame number, the ending original frame number, and the boundary data offset.

[0132] The gateway station pre-establishes a task association record between the receive arc identifier and the onboard data storage task identifier. This task association record includes at least the satellite identifier, receive task identifier, receive arc identifier, onboard data storage task identifier, virtual channel identifier, and original frame sequence number range. The receive arc identifier is used by the gateway station to distinguish between different satellite transit reception processes, while the onboard data storage task identifier is used by the satellite to query corresponding historical stored data.

[0133] When generating a satellite data retransmission request, the gateway station queries the task association record based on the satellite identifier, receiving task identifier, and receiving arc segment identifier to obtain the corresponding onboard data storage task identifier. Then, it generates the satellite data retransmission request based on the satellite identifier, receiving task identifier, receiving arc segment identifier, onboard data storage task identifier, virtual channel identifier, start original frame sequence number, end original frame sequence number, and boundary data offset. The satellite data retransmission request retains the receiving arc segment identifier, which is used by the gateway station to associate the satellite data retransmission request with the retransmitted data.

[0134] Satellite data retransmission requests can be sent to satellites with historical data storage capabilities via the satellite uplink, or they can be converted into satellite data retransmission tasks by the satellite mission management platform and sent to the satellite within the subsequent available communication window.

[0135] After receiving a satellite data retransmission request, the satellite reads the corresponding original data from the onboard memory based on the onboard data storage task identifier, virtual channel identifier, start original frame sequence number, and end original frame sequence number. For the start and end original frames, the satellite determines the range of data that needs to be retransmitted according to the boundary data offset, and carries the onboard data storage task identifier, original frame sequence number, and corresponding source location identifier in the retransmitted data.

[0136] After receiving retransmitted data, the gateway station verifies the onboard data storage task identifier based on the received arc segment identifier and task association record. It then sorts the retransmitted data according to the original frame sequence number and source location identifier, and performs frame sequence number continuity checks, boundary range checks, and checksum checks. If the retransmitted data passes verification and completely covers the satellite retransmission range, it is grouped into a source data block to be repaired. If the retransmitted data does not completely cover the satellite retransmission range, a new satellite data retransmission request is generated based on the uncovered original frame range.

[0137] Step S106: Re-execute the corresponding processing operation to generate and send the repair data unit.

[0138] Based on the transformation mapping records that participated in the reverse traversal, the gateway station reads the operation identifier and parameter version in the original processing order, and re-executes protocol parsing, data splicing and distribution format conversion on the source data block to be repaired, so as to obtain repair output data covering the abnormal output range.

[0139] When the distribution format conversion operation uses the complete output segment as the smallest processing unit, the replacement output range corresponding to the repaired output data can be larger than the abnormal output range, but does not include other output segments that are unrelated to this repair.

[0140] The gateway station reads the current version of the data unit corresponding to the distribution target that returned valid exception feedback information, determines this current version as the base version, and increments the base version to obtain the repair version. The gateway station calculates the check value of the repair output data to obtain the repair check value, and encapsulates the exception data unit identifier, distribution target identifier, base version, repair version, replacement output range, repair check value, and repair output data into a repair data unit.

[0141] The gateway station sends the repair data unit to the distribution target that returned valid error feedback information and updates the repair status of the relevant transformation mapping record from "Pending Repair" to "Repairing". Upon receiving the repair data unit, the distribution target compares the base version with the locally stored data unit version. If they match, the distribution target replaces the corresponding output range with the repair output data, updates the locally stored data unit version to the repaired version, and re-performs integrity verification. If they do not match, no data replacement is performed, and version mismatch information is returned to the gateway station. Upon receiving the repair confirmation information, the gateway station updates the current version of the data unit corresponding to the distribution target to the repaired version and updates the transmission checksum and repair status in the final-level transformation mapping record.

[0142] like Figure 3 As shown, the above reverse positioning and repair process is illustrated using a local anomaly in the data distribution unit D7 as an example.

[0143] After receiving version 3 of D7, distribution target T1 finds that the output range [2304, 2560) has not been completely received, and returns an anomaly feedback message to the gateway station. This anomaly feedback message includes the distribution target identifier T1, the anomaly data unit identifier D7, the distribution data unit version 3, and the anomaly output range [2304, 2560]. Since the anomaly output range was not completely received, this anomaly feedback message does not carry the corresponding receive checksum value.

[0144] The gateway station determines the current version of D7 corresponding to distribution target T1 based on the distribution target identifier T1. Therefore, the feedback version is consistent with the current version. Since the abnormal output range was not fully received, this abnormal feedback information is determined to be valid abnormal feedback information.

[0145] The abnormal output range [2304, 2560) is located within the output range [2048, 4096) of D7. The gateway station first locates the intermediate data block C2 that generated this output range, then reverses from C2 to P2 and P3, and then reverses to F1201, F1202, and F1203. After extending the source data range obtained from the reverse location to the corresponding check block boundary, the source data block to be repaired is determined to be B2.

[0146] The gateway station queries its local cache based on the block identifier of B2. If B2 exists in the local cache and the verification passes, B2 is read directly; if B2 does not exist in the local cache, a satellite data retransmission request is generated based on the source positioning record corresponding to B2, and F1201, F1202 and F1203 are obtained and verified, and combined into B2.

[0147] According to the processing order of the conversion mapping chain record, the gateway station calls the protocol parser of the original parameter version to regenerate P2 and P3, calls the data splicer of the original parameter version to regenerate C2, and then calls the distribution format converter of the original parameter version to generate the output range of D7 [2048, 4096].

[0148] The gateway station determines the current version 3 of D7 corresponding to distribution target T1 as the base version, and increments the base version to obtain repair version 4. The gateway station calculates the repair check value of the regenerated output data, and encapsulates the abnormal data unit identifier D7, distribution target identifier T1, base version 3, repair version 4, replacement output range [2048, 4096), repair check value, and repair output data into a repair data unit. The version update corresponding to distribution target T1 does not change the current version of D7 for other distribution targets.

[0149] After receiving the repair data unit, distribution target T1 compares the base version 3 with the locally stored D7 version. If they match, the output range [2048, 4096] of D7 is replaced with the repair output data, the locally stored D7 version is updated to 4, and integrity verification is performed again. If they do not match, data replacement is not performed, and version mismatch information is returned. After the integrity verification passes, distribution target T1 returns repair confirmation information containing the abnormal data unit identifier D7, distribution target identifier T1, repair version 4, and repair success status. After receiving the repair confirmation information, the gateway station updates the current D7 version corresponding to distribution target T1 to 4, updates the transmission check value in the final-level conversion mapping record, and updates the repair status of the relevant conversion mapping record to completed.

[0150] After the transformation mapping record is established, the distribution status is initialized to unconfirmed, and the repair status is initialized to no repair required. Upon receiving distribution confirmation information from the distribution target, the gateway station updates the distribution status of the corresponding transformation mapping record to confirmed; upon receiving valid exception feedback information and identifying the source data block to be repaired, it updates the repair status of the relevant transformation mapping record to pending repair; after sending the repair data unit, it updates the repair status of the relevant transformation mapping record to repairing; and upon receiving a repair confirmation message indicating successful repair, it updates the repair status of the relevant transformation mapping record to completed.

[0151] To control cache space usage, each transformation mapping record also records the identifier of its associated minimum reconfigurable source data block. The gateway station sets a reference count for each minimum reconfigurable source data block. The reference count equals the number of transformation mapping records that reference the corresponding minimum reconfigurable source data block and satisfy any of the following states: distribution status is unconfirmed, or repair status is pending or under repair. A transformation mapping record satisfying both states is counted only once.

[0152] Upon receiving distribution confirmation or repair confirmation from the distribution target, the gateway station updates the distribution status or repair status of the corresponding transformation mapping record and recalculates the reference count of the corresponding minimum reconfigurable source data block. When the reference count is zero, the cache space occupied by the minimum reconfigurable source data block is released.

[0153] The data content of the smallest reconfigurable source data block is released. The source positioning record, transformation mapping chain, and parameter version information are retained until the preset exception feedback validity period expires. Therefore, even if the data content has been released but valid exception feedback information is still received, the gateway station can still complete reverse positioning based on the transformation mapping chain and generate a satellite data retransmission request based on the source positioning record.

[0154] like Figure 4 As shown, the gateway station data aggregation, distribution, and reverse positioning repair system that implements the above method includes a source data organization module, a reconstruction block determination module, an aggregation mapping module, an anomaly positioning module, a repair acquisition module, and a repair distribution module. It also includes a satellite link interface, a data buffer, and a ground network interface.

[0155] The satellite link interface connects to satellite communication equipment and is used to receive raw data frames transmitted downlink from the satellite link, send satellite data retransmission requests, and receive corresponding retransmission data.

[0156] The source data organization module is connected to the satellite link interface to obtain the satellite identifier, receiving task identifier, receiving arc identifier, virtual channel identifier, original frame sequence number and data offset corresponding to the original data frame. It then groups, sorts and verifies the original data frames to establish source data intervals and source positioning records.

[0157] The reconstructed block determination module is connected to the source data organization module. It is used to read the boundary of the verification block and the input dependency range of each processing operation, iteratively expand the source data range until the expanded data range can independently complete the verification, protocol parsing, data splicing and distribution format conversion, and generate the smallest reconstructable source data block with a block identifier.

[0158] The convergence mapping module is connected to the reconstructed block determination module. It is used to call the protocol parser, data splicer, and distribution format converter to process the smallest reconstructable source data block and generate distribution data units. For each processing operation record, the input data block, input range, output data block, output range, operation identifier, and parameter version are recorded. The conversion mapping chain is constructed according to the processing order, and the distribution data unit identifier, distribution target identifier, and corresponding current version are recorded in the final conversion mapping record.

[0159] The anomaly localization module is connected to the ground network interface and the data buffer. It is used to receive anomaly feedback information returned by the distribution target, perform version consistency and anomaly validity judgment, and reverse traverse the transformation mapping chain according to the anomaly output range to obtain the source data block to be repaired.

[0160] The repair acquisition module is connected to the anomaly location module, the data cache, and the satellite link interface, respectively, and is used to query the local cache index based on the block identifier. When the source data block to be repaired exists in the local cache, the source data block to be repaired is read and verified; when the source data block to be repaired does not exist in the local cache, a satellite data retransmission request is generated based on the source location record, and the verified retransmission data is combined into the source data block to be repaired.

[0161] The repair distribution module connects to the repair acquisition module, the convergence mapping module, and the ground network interface. It is used to re-execute the corresponding processing operations based on the processing order, operation identifier, and parameter version of the transformation mapping chain record, generate repair data units, and send them to the distribution target via the ground network interface. The repair distribution module also updates the distribution status, repair status, and reference count of the transformation mapping record based on distribution confirmation information and repair confirmation information.

[0162] The data cache is connected to the source data organization module, the aggregation mapping module, the anomaly location module, and the repair acquisition module, respectively. It stores source data ranges, minimum reconfigurable source data blocks, source location records, cache indexes, transformation mapping chains, parameter versions, data unit identifiers, and the current version corresponding to each distribution target. The source data organization module writes the source data ranges and source location records to the data cache; the aggregation mapping module writes the minimum reconfigurable source data blocks, transformation mapping chains, parameter versions, data unit identifiers, and the current version corresponding to each distribution target to the data cache; the anomaly location module reads the transformation mapping chains, data unit identifiers, and the current version of the corresponding distribution target from the data cache; and the repair acquisition module queries the cache index based on the block identifier and reads the source data block to be repaired from the corresponding cache address.

[0163] The data cache consists of a data cache area and a mapping metadata area. The data cache area stores the raw data and the minimum reconfigurable source data block, while the mapping metadata area stores source location records, cache indexes, transformation mapping chains, parameter versions, data unit identifiers, and the current version corresponding to each distribution target. When the reference count of the minimum reconfigurable source data block reaches zero, the corresponding data in the data cache area is released, and the relevant records in the mapping metadata area are retained for the preset exception feedback validity period.

[0164] The ground network interface communicates with the distribution target to send distribution data units and repair data units, and to receive anomaly feedback information, distribution confirmation information, and repair confirmation information.

[0165] The modules described above can be deployed as software functional modules on the same gateway server, or they can be deployed separately on multiple processing nodes connected via an internal network. Each module transmits block identifiers, cache addresses, and processing status via shared memory, message queues, or an internal data bus. The data cache can be memory, solid-state storage, or a tiered cache composed of memory and solid-state storage.

[0166] During system operation, raw data frames enter the source data organization module through the satellite link interface. After being processed by the reconstruction block determination module and the aggregation mapping module, they are formed into distribution data units and sent to the distribution target through the ground network interface. Anomaly feedback information enters the anomaly location module through the ground network interface. After the anomaly location module determines the source data block to be repaired, the repair acquisition module obtains the corresponding data, and then the repair distribution module generates and sends the repair data unit. This forms a complete processing link of data reception, data aggregation, data distribution, anomaly location, and local repair.

[0167] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for data aggregation, distribution, and reverse positioning repair at a gateway station, characterized in that, include: Receive raw data frames transmitted from the satellite link, and establish source data intervals and source positioning records based on satellite identifier, receiving task identifier, receiving arc segment identifier, virtual channel identifier, raw frame sequence number and data offset; The source data range is expanded based on the boundary of the verification block and the input dependency range of protocol parsing, data splicing and distribution format conversion until the expanded data range can independently complete the verification and corresponding processing, thus obtaining the smallest reconfigurable source data block with a block identifier. The minimum reconfigurable source data block is subjected to protocol parsing, data splicing, and distribution format conversion to generate a distribution data unit; for each processing operation record, the input data block, input range, output data block, output range, operation identifier, and parameter version are recorded, and a conversion mapping chain is constructed according to the processing order. The data unit identifier and current version of the distribution data unit are recorded in the last-level conversion mapping record of the conversion mapping chain. Obtain the abnormal data unit identifier, distribution data unit version, and abnormal output range returned by the distribution target; when the distribution data unit version is consistent with the current version recorded by the transformation mapping chain, traverse the transformation mapping chain in reverse by the abnormal output range, and extend the obtained source data range to the boundary of the corresponding minimum reconfigurable source data block to obtain the source data block to be repaired. Query local cache; If the source data block to be repaired exists, the source data block to be repaired is read; if the source data block to be repaired does not exist, a satellite data retransmission request is generated based on the source positioning record and the source data block to be repaired is obtained. Based on the operation identifier and parameter version of the transformation mapping chain record, the corresponding processing operation is re-executed to generate a repair data unit containing the replacement output range. The repair data unit is then sent to the distribution target, and the repair status of the corresponding transformation mapping record is updated.

2. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 1, characterized in that, The establishment of the source data range includes: The original data frames are grouped according to the satellite identifier, the receiving task identifier, the receiving arc segment identifier, and the virtual channel identifier; Each group of original data frames is sorted and verified according to the original frame sequence number and the data offset; The original data frames with consecutive sequence numbers and passing verification are merged into the source data interval; when there is a missing sequence number between adjacent original data frames, or when there is an original data frame that fails verification, the end position of the previous original data frame that passed verification is determined as the end position of the source data interval, and the corresponding missing data range is recorded in the source positioning record.

3. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 1, characterized in that, The obtained minimum reconfigurable source data block includes: The initial data range is determined based on the boundary of the verification block; Determine the range of input data that each of the aforementioned processing operations depends on to generate the corresponding output data; When the input data range exceeds the initial data range, the initial data range is extended to the adjacent verification block that includes the corresponding input data range, and it is re-determined whether the extended data range includes all the input data on which each processing operation depends. Until the expanded data range includes all the input data on which each of the processing operations depends, the expanded data range is determined as the minimum reconfigurable source data block, and a corresponding block identifier is generated for the minimum reconfigurable source data block.

4. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 1, characterized in that, The transformation mapping chain includes multiple transformation mapping records. Each non-primary transformation mapping record records at least its predecessor transformation mapping record identifier, and each non-final transformation mapping record records at least its successor transformation mapping record identifier. For any of the output intervals, when the output interval is generated by a plurality of the input data blocks, the plurality of input data blocks and the corresponding input intervals are recorded as the set of input data blocks for the output interval; For any input data block, when the input data block participates in generating multiple output intervals, a conversion mapping record between the input data block and each output interval is established respectively to form a multi-level many-to-many conversion mapping relationship between the minimum reconfigurable source data block and the distribution data unit.

5. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 4, characterized in that, The distribution target returns abnormal feedback information, which includes the distribution target identifier, the abnormal data unit identifier, the distribution data unit version, and the abnormal output range, and includes a reception verification value corresponding to the abnormal output range when the abnormal output range has been fully received. The final-level conversion mapping record of the conversion mapping chain also records the current version corresponding to each distribution target, each output interval, and the transmission verification value corresponding to each output interval according to the distribution target identifier. When the version of the distribution data unit is consistent with the current version corresponding to the distribution target identifier, and at least one of the following conditions is met, the abnormal feedback information is determined to be valid abnormal feedback information: the abnormal output interval was not completely received; the abnormal output interval has been completely received and the reception verification value is inconsistent with the transmission verification value corresponding to the same output interval.

6. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 5, characterized in that, The reverse traversal transformation mapping chain includes: Filter out the final-level transformation mapping records from the transformation mapping chain whose output intervals overlap with the abnormal output intervals; Based on the identifier of the preceding transformation mapping record of each of the final-level transformation mapping records, the corresponding transformation mapping record is searched level by level in reverse order of the processing order until the primary transformation mapping record with the source data range as input data is found. The source data ranges corresponding to the found primary transformation mapping records are merged, and the merged source data range is extended to the boundary of the corresponding minimum reconfigurable source data block to obtain the source data block to be repaired.

7. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 6, characterized in that, The acquisition of the source data block to be repaired includes: Query the local cache index based on the block identifier of the source data block to be repaired; When the corresponding local cache address is found, the source data block to be repaired is read from the local cache address and verified. When no corresponding local cache address is found, a pre-established task association record is queried based on the satellite identifier, receiving task identifier, and receiving arc identifier in the source positioning record to obtain the corresponding onboard data storage task identifier. The task association record records the correspondence between the satellite identifier, receiving task identifier, receiving arc identifier, and onboard data storage task identifier. The source data range corresponding to the source data block to be repaired is converted into a satellite retransmission range. The satellite data retransmission request is generated based on the satellite identifier, the onboard data storage task identifier, the virtual channel identifier, the start original frame sequence number, the end original frame sequence number, and the boundary data offset. The received retransmission data is verified, and the retransmission data that passes the verification and completely covers the satellite retransmission range is determined as the source data block to be repaired.

8. The method for data aggregation, distribution, and reverse positioning repair of a gateway station according to claim 7, characterized in that, The generation and processing of the repair data unit includes: According to the processing order, operation identifier and parameter version recorded in the transformation mapping chain, the corresponding processing operation is re-executed on the source data block to be repaired to obtain repaired output data covering the abnormal output range; Read the current version of the distribution data unit corresponding to the distribution target that returned the valid exception feedback information, determine the current version as the base version, and increment the base version to obtain the repair version; calculate the verification value of the repair output data to obtain the repair verification value; encapsulate the repair data unit according to the exception data unit identifier, the distribution target identifier, the base version, the repair version, the replacement output range corresponding to the repair output data, the repair verification value, and the repair output data. The repair data unit is sent to the distribution target that returns the valid error feedback information; Each of the aforementioned transformation mapping records also records the distribution status and the repair status; a reference count is set for each of the aforementioned minimum reconfigurable source data blocks, the reference count being the number of transformation mapping records that reference the corresponding minimum reconfigurable source data block and satisfy any of the following states: the distribution status is unconfirmed, or the repair status is pending repair or repairing; Upon receiving the distribution confirmation or repair confirmation information returned by the distribution target, the distribution status or repair status of the corresponding transformation mapping record is updated, and the reference count of the corresponding minimum reconfigurable source data block is re-determined; when the reference count is zero, the cache space occupied by the corresponding minimum reconfigurable source data block is released.

9. A data aggregation, distribution, and reverse positioning and repair system for gateway stations, characterized in that, include: The source data organization module is used to receive raw data frames transmitted from the satellite link and establish source data intervals and source positioning records based on satellite identifier, receiving task identifier, receiving arc segment identifier, virtual channel identifier, raw frame sequence number and data offset. The reconstructed block determination module is used to expand the source data range based on the boundary of the verification block and the input dependency range of protocol parsing, data splicing and distribution format conversion, until the expanded data range can independently complete the verification and corresponding processing, and obtain the smallest reconstructable source data block with block identifier. The convergence mapping module is used to perform protocol parsing, data splicing, and distribution format conversion on the minimum reconfigurable source data block to generate distribution data units; for each processing operation record input data block, input range, output data block, output range, operation identifier, and parameter version, a conversion mapping chain is constructed according to the processing order, and the data unit identifier and current version of the distribution data unit are recorded in the last-level conversion mapping record of the conversion mapping chain; An anomaly localization module is used to obtain anomaly feedback information returned by the distribution target. The anomaly feedback information includes an anomaly data unit identifier, a distribution data unit version, and an anomaly output range. When the distribution data unit version is consistent with the current version recorded in the transformation mapping chain, the transformation mapping chain is traversed in reverse by the anomaly output range to extend the obtained source data range to the boundary of the corresponding minimum reconfigurable source data block, thereby obtaining the source data block to be repaired. The repair acquisition module is used to query the local cache, read the source data block to be repaired when the source data block to be repaired exists in the local cache, and generate a satellite data retransmission request based on the source positioning record and obtain the source data block to be repaired when the source data block to be repaired does not exist in the local cache. The repair distribution module is used to re-execute the corresponding processing operation based on the operation identifier and parameter version of the transformation mapping chain record, generate a repair data unit containing the replacement output range, send the repair data unit to the distribution target, and update the repair status of the corresponding transformation mapping record.

10. A gateway station data aggregation, distribution, and reverse positioning repair system according to claim 9, characterized in that, It also includes satellite link interfaces, data buffers, and terrestrial network interfaces; The satellite link interface is connected to the source data organization module and the repair acquisition module respectively, and is used to receive the original data frame, send the satellite data retransmission request and receive the corresponding retransmission data. The data cache is connected to the source data organization module, the convergence mapping module, the anomaly location module, and the repair acquisition module, respectively, and is used to store the source data range, the minimum reconfigurable source data block, the source location record, and the transformation mapping chain; The ground network interface is connected to the convergence mapping module and the repair distribution module respectively, and is used to send the distribution data unit and the repair data unit to the distribution target, and receive the abnormal feedback information, distribution confirmation information and repair confirmation information returned by the distribution target.

Images