Integrity verification method and system supporting satellite-borne virtual load migration state

Abstract

The invention discloses an integrity verification method and system supporting a satellite-borne virtual load migration state, and the method comprises the steps: extracting a task execution log of a source satellite node, constructing a combined structure path of an operation segment, an access segment and a thread migration segment, recognizing a migration interruption trigger point, and forming a trigger path group; further comparing the time sequence difference between the operation fragment and the access fragment, identifying a fragment with an asymmetric structure, mapping the fragment to a target node, constructing a migration mapping relation group, and quantifying a structure offset level; finally, credibility judgment and structure injection or rollback are completed based on the segment tail chain complementary relation. The method has high interpretability, low resource overhead and engineering adaptability, and improves the state verification capability of satellite-borne task migration.

Description

Technical Field

[0001] This invention relates to the field of satellite computing task scheduling and status verification technology, specifically to a method and system for verifying the integrity of the migration status of onboard virtual payloads. Background Technology

[0002] With the development of shared constellation systems, an increasing number of satellite platforms support the deployment of multiple virtual payload instances via virtualization. This allows different mission users to flexibly rent computing or sensor resources across onboard nodes, forming a multi-tenant virtual payload management model. To meet the needs of dynamic mission scheduling, operations such as virtual payload migration, suspension and recovery, and fault takeover between satellites are becoming increasingly frequent.

[0003] In traditional trusted computing systems, trusted execution environments (TEEs) are often used to isolate and protect critical operations during execution to ensure runtime security. However, TEE mechanisms are mostly built on fixed nodes and lack the ability to track and verify the state evolution of virtual payloads during cross-node migration, making it difficult to meet the requirements for verifying the integrity of migration states in a spaceborne environment.

[0004] Existing integrity verification mechanisms, such as chained hashing, full task backtracking, or Merkle tree signatures, while theoretically capable of securely confirming execution paths, generally suffer from high computational resource consumption, significant communication overhead, and strong hardware dependencies. These limitations make them difficult to directly adapt to the practical constraints of spaceborne platforms, such as limited computing power, high communication latency, and power sensitivity. Furthermore, existing methods typically rely on complete structural consistency as the criterion, lacking analysis of the structural correspondence between operation paths and access calls during thread migration. They fail to identify inconsistencies such as offsets, misalignments, or cross-thread mappings in operation accesses, and lack a refined offset-level evaluation system, thus limiting their ability to assess the reliability of fault-tolerant or partially abnormal migrations.

[0005] In view of this, the present invention provides a method and system for verifying the integrity of the migration state of onboard virtual payloads, thereby solving the above-mentioned problems. Summary of the Invention

[0006] The purpose of this invention is to provide a method and system for verifying the integrity of onboard virtual payload migration states, thereby solving the problem of the lack of a lightweight, interpretable, and non-static structural integrity verification mechanism in the prior art during the migration process of onboard virtual payloads.

[0007] To achieve the above objectives, the present invention provides the following technical solution: In a first aspect, the present invention provides an integrity verification method for supporting the migration state of onboard virtual payloads, comprising the following steps: S101: Extract the task execution log of the virtual payload instance to be migrated in the source star node, and parse out three types of marker fragments: operation segment marker, thread migration segment boundary and memory access segment boundary. Based on the thread offset and time marker of the access segment, construct the initial associated fragment set. S102: Based on the operation segment markers and thread migration segment boundaries in the initial associated segment set, construct a combined segment path; according to the topology and return sequence of the combined segment path, locate the migration interruption trigger point in the scheduling cache history, and aggregate the structural segments covered by the trigger point into a trigger path group; S103: Based on the temporal relationship of the segments in the trigger path group, match the reverse rearranged operation group with the original call order to form the thread operation corresponding group, and identify the structurally asymmetric segment group based on the order difference and time correlation of operation-access segments. S104: Map the structurally asymmetric segment group to the resource scheduling segment of the target star node, construct a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculate the structural offset level of the migration; S105: Based on whether the structural offset level displayed by the migration mapping relationship group is acceptable, and at the same time check the segment tail mark of the trigger path group, construct the segment tail chain group through the segment tail swap relationship; if the structural offset level meets the credibility standard and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a credible migration structure and structural injection is performed; otherwise, the original structure rollback process is triggered.

[0008] As a preferred embodiment of the first aspect of the present invention, the construction logic of the initial associated fragment set is as follows: In the source star node task execution log, each access segment is identified and assigned an intra-thread offset index according to its arrangement order within its respective thread segment, so as to form the basic structure sequence inside the thread segment. Extract the time stamp of each operation segment from all operation segments, arrange the operation segments in chronological order according to the time stamp, retrieve the operation segment time stamp corresponding to the first access segment from the arrangement result, and obtain the reference time stamp corresponding to the access segment. The intra-thread offset index, corresponding thread number, and reference timestamp of the accessed segment are integrated into a ternary combination unit and recorded in the index record table; Based on thread number, all ternary combination units are aggregated according to thread segments, and arranged in ascending order of offset index within each aggregation group to form a temporal structure chain between the access segment and its reference time marker. All thread segments are combined in the order of their corresponding temporal structure chains according to their thread numbers to generate an initial set of associated segments with offset indices and time stamps as the core structure.

[0009] As a preferred embodiment of the first aspect of the present invention, the method of forming a temporal structure chain between the access segment and its reference time marker includes: For each thread segment, based on the position of the accessed segment within the thread segment, a continuous offset number is generated for it, and the offset number is recorded as the offset order index of the accessed segment; Each offset index and its corresponding reference time stamp are combined to form an offset-time key-value pair, and this key-value pair is used as the basic element to form a graph node, thus forming an offset-time node set; Connect the nodes in the offset-time node set one by one in ascending order of time stamps to construct a time-continuous path chain for accessing fragments in a single-threaded dimension; For multiple thread segments, the time-continuous path chains they construct are grouped together using the thread identifier as the index identifier, and the grouping structure is used to form a cross-thread access-time mapping graph. Using the access-time map as a local indexing framework for the temporal structure chain allows the internal temporal structure of access segments across threads to be expressed in a fixed graph-level structure.

[0010] As a preferred embodiment of the first aspect of the present invention, the method of matching the reversed operation group with the original calling order to form a corresponding thread operation group includes: In the reverse-arranged operation group, record the position index of each operation fragment in the rearranged sequence, and at the same time record the thread identifier corresponding to the operation fragment in the original task execution log to form the rearranged index record of the operation fragment. Extract the original occurrence order of the access segment within each thread segment, and establish an access segment order sequence based on the access segment order to preserve the access call order within the thread. Using the thread identifier as the association key, a corresponding record is established between the rearranged index of the operation segment and the access segment sequence. The candidate segment pairing table is formed by screening based on whether the operation segment and the access segment have an adjacency relationship in the time stamp region of the original log. Select fragment pairs that are thread-consistent and have adjacent timestamps from the candidate fragment pairing table, record them as operation-access fragment correspondence entries, and group and classify them according to thread number; The operation-access segment correspondence entries within each thread group are combined to form a thread operation correspondence group, providing a paired structural expression between operation paths and access logic.

[0011] As a preferred embodiment of the first aspect of the present invention, the method for constructing the pairing relationship between the operation fragment index and the access fragment index includes: Record the rearranged sequence number of each operation segment from the reverse rearranged operation group, use this number as the operation index of the operation segment, and summarize it in the record table; Within a thread segment, a sequential number is generated for each access segment according to its original order of appearance. This number is used as the access index for the access segment, and the call time range of the access segment is recorded. Based on the thread identifier of the operation segment and the thread identifier of the access segment, a candidate matching matrix is ​​constructed, and the candidate pairing combination that satisfies the condition of whether the time range of the operation index and the access index overlaps is selected. Operation segments and access segments that meet the conditions of time overlap and sequential connection are recorded as valid segment pairing groups, and operation-access dual index record entries are created for each combination; All valid fragment combination entries corresponding to all threads are integrated to form a dual-path connection index group, which serves as the basis for the composition of the corresponding thread operation group.

[0012] As a preferred embodiment of the first aspect of the present invention, the method for identifying the structurally asymmetric segment group includes: Extract each operation-access segment pair from the corresponding group of thread operations, and record the order number of the occurrence of the operation segment and access segment in the original thread segment; Using the order of operation segments as a reference, the difference in the order number of each pair of operation-access segments is marked as an order offset, and the offset and the thread identifier are combined to form an order difference tuple; Filter all entries with non-zero offsets in the sequence difference tuples and verify whether the offset has a skip sequence reversal feature, i.e., the access segment appears after the operation segment; Tuples with cross-order reversal characteristics are grouped by thread identifier, and the corresponding fragment pairs in each group are used as candidate fragment combinations for structural asymmetry. All candidate segments with structural asymmetry are combined, deduplicated, and renumbered to obtain a set of structural asymmetric segments, which represents the set of key locations where there is a structural offset between the operation-access call path.

[0013] As a preferred embodiment of the first aspect of the present invention, the method for verifying the skip-type order reversal feature of order difference tuples includes: The difference in the order number of each operation-access segment combination is defined as the operation precedence. If this value is less than zero, it is judged that there may be an abnormal situation where the access segment takes precedence over the operation segment. For all combinations of operations with negative pre-conditions, summarize the corresponding access segments by thread identifier and retrieve their actual call times in the execution log; If the access segment is invoked later than its associated operation segment, it is considered a pseudo-reversal combination and is removed; otherwise, it is considered a valid order reversal. All valid order reversal combinations are constructed into fragment pairs with offset labels, and each combination is appended with a cross feature identifier to support subsequent mapping analysis; The combinations with the crossing feature identifiers are summarized into a structural asymmetry confirmation set, and structural asymmetry fragment groups are extracted from it to further support the structural consistency comparison process.

[0014] As a preferred embodiment of the first aspect of the present invention, the construction logic of the migration mapping relationship group is as follows: Extract fragment entities from the target star node that have the same number as the asymmetric fragment group in the source node structure, and label each fragment entity with its thread number and offset position within the fragment. The thread number and offset position of each structurally asymmetric segment in the source node are used as the source label, and a mapping pair is constructed with the position features of the segment with the same number in the target star node. If the positional characteristics of the same numbered segment in the target node show changes in thread number or offset order, it is considered a valid structural offset mapping entry and recorded as a structural variation pair. Reconstruct all structural variant pairs into position offset trajectories according to fragment number, and generate a thread-offset trajectory mapping table; All mapping entries in the mapping table that have undergone position changes or thread switching are organized into migration mapping relationship groups to serve as the input basis for migration consistency analysis.

[0015] As a preferred embodiment of the first aspect of the present invention, the method for calculating the structural offset level of the migration includes: The total number of segment numbers in the asymmetric segment group is counted, and a summary table of numbers is constructed as the original structural reference set. Extract all fragment entries that have undergone offset or thread number changes from the migration mapping relationship group to form a mapping offset set; Calculate the coverage ratio of the segment numbers in the mapped offset set in the original structural reference set, and construct a ratio analysis table; Set the structural offset ratio threshold range, and mark it as high offset, medium offset or low offset level according to the coverage ratio range in the ratio analysis table; The offset level is used as an indicator of the consistency level of the migration state, and the final consistency verification result is generated in the indicator system.

[0016] In a second aspect, the present invention provides an integrity verification system that supports the migration state of onboard virtual payloads. Based on the implementation of the first aspect, it includes a log parsing module, a path construction module, an operation pairing module, a mapping analysis module, and a consistency verification module. Data is transmitted between the modules via wired and / or wireless means. The log parsing module extracts the task execution logs of the virtual payload instance to be migrated in the source star node, and parses out three types of marker fragments: operation segment marker, thread migration segment boundary, and memory access segment boundary. Based on the thread offset and time marker of the access segment, an initial set of associated fragments is constructed. The path construction module constructs a combined segment path based on the operation segment markers and thread migration segment boundaries in the initial associated segment set; according to the topology and return sequence of the combined segment path, it locates the migration interruption trigger point in the scheduling cache history, and aggregates the structural segments covered by the trigger point into a trigger path group; The operation matching module matches the reverse-ordered operation group with the original call order based on the temporal relationship of the segments in the trigger path group, forming a corresponding group of thread operations, and identifies the structurally asymmetric segment group based on the order difference and temporal correlation of operation-access segments. The mapping analysis module maps the structurally asymmetric segment group to the resource scheduling segment of the target star node, constructs a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculates the structural offset level of the migration. The consistency verification module checks whether the structural offset level displayed by the migration mapping relationship group is acceptable, and at the same time checks the segment tail mark of the trigger path group. It constructs a segment tail chain group through the segment tail swap relationship. If the structural offset level meets the trust criteria and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a trustworthy migration structure and the structure injection is performed; otherwise, the original structure rollback process is triggered.

[0017] The technical effects and advantages provided by the present invention in the above technical solution are as follows: This invention constructs operation-access structure pairing relationships and identifies structurally asymmetric fragment groups. It can accurately perceive the structural offset of critical states during virtual payload migration without relying on heavy encryption calculations and full path comparison. Combined with the complementary interleaved verification mechanism of the segment tail chain group, it not only improves the robustness of migration consistency judgment, but also significantly reduces the computational and communication overhead of performing integrity verification under the condition of limited on-board resources, thereby ensuring the reliable migration capability and mission continuity of virtual payloads in a shared constellation environment. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0019] Figure 1 This is a flowchart of the integrity verification method for the migration state of onboard virtual payloads supported by the present invention; Figure 2 This is a schematic diagram illustrating the initial associated fragment and combined segment path construction of the present invention; Figure 3 This is a framework diagram of the system supporting the integrity verification of the migration state of onboard virtual payloads according to the present invention. Detailed Implementation

[0020] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that the description of this disclosure will be more complete and fully convey the concept of the exemplary embodiments to those skilled in the art. The drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0021] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments. Numerous specific details are provided in the following description to give a full understanding of exemplary embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure may be practiced with one or more specific details omitted, or methods, components, steps, etc. In other instances, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0022] Example 1 like Figure 1 As shown, this invention provides an integrity verification method for supporting the migration state of onboard virtual payloads, comprising the following steps: S101: Extract the task execution log of the virtual payload instance to be migrated in the source star node, and parse out three types of marker fragments: operation segment marker, thread migration segment boundary and memory access segment boundary. Based on the thread offset and time marker of the access segment, construct the initial associated fragment set. In this embodiment, the task execution log refers to the structured sequence of behavioral events recorded by the source node during its local execution. Essentially, it is a time-series information set that traces the execution status, primarily used to support migration status assessment, resource scheduling decisions, and anomaly backtracking analysis. The log includes function call information identified by event type, thread context switching records, and memory access operations, which can be organized into a complete execution chain based on timestamps. Call events that identify functional module boundaries are identified as operation segment markers, thread ID changes or switching events are identified as thread migration segment boundaries, and operations involving physical address or resource segment access are identified as memory access segment boundaries. These three types of marker fragments constitute key segmentation points for the virtual payload's structural behavior, such as... Figure 2 As shown, by combining thread number, timestamp and fragment position, an initial set of associated fragments is generated. Based on operation segment and migration boundary, a combined segment path is constructed. By combining the cross sequence and return structure in the combined path, the trigger point of migration interruption is located in the scheduling cache history. Finally, all structural fragments covering the trigger point are aggregated into a trigger path group, which serves as the key input for integrity verification.

[0023] Specifically, the construction logic of the initial associated fragment set is as follows: In the source star node task execution log, each access segment is identified and assigned an intra-thread offset index according to its arrangement order within its respective thread segment, so as to form the basic structure sequence inside the thread segment. This can be understood as follows: The system iterates through each event record in the task execution log, identifies events belonging to the memory access category, and marks them as access fragments. For each thread, it records the position of the first occurrence of an access fragment within that thread, and assigns it a consecutive number starting from 0, denoted as an offset index, according to the order of its occurrence. This offset index is used to represent the position sequence of the access fragment within the current thread.

[0024] Extract the time stamp of each operation segment from all operation segments, arrange the operation segments in chronological order according to the time stamp, retrieve the operation segment time stamp corresponding to the first access segment from the arrangement result, and obtain the reference time stamp corresponding to the access segment. To further explain, each operation segment is typically identified by the starting log of the task function call and includes its own event timestamp. The system extracts timestamp information from all operation segments and constructs a time index sequence sorted in ascending order. For each access segment, the system compares its own timestamp with the operation segment sequence and selects the timestamp of the first operation segment whose time is later than the access time as the reference timestamp for that access segment.

[0025] The intra-thread offset index, corresponding thread number, and reference timestamp of the accessed segment are integrated into a ternary combination unit and recorded in the index record table; This can be understood as follows: the offset index, the thread number to which the accessed segment belongs, and the calculated reference timestamp are combined into a structured triple, and the triple is registered in the index record table. This record table is divided into multiple thread sub-tables according to the thread number. Each record contains the sequential position of the accessed segment and its external time reference, forming a basic set of index structures.

[0026] Based on thread number, all ternary combination units are aggregated according to thread segments, and arranged in ascending order of offset index within each aggregation group to form a temporal structure chain between the access segment and its reference time marker. This can be understood as follows: Triples are grouped according to thread IDs, with each group corresponding to a thread segment; within each group, access segments are arranged in ascending order according to their offset indices, forming a structured access sequence. In each thread structure chain, each access segment retains its original execution order and is also bound to a reference time, thus forming a time-structure composite sequence that can be used for graph-level representation.

[0027] Combine the temporal structure chains corresponding to all thread segments in order of thread number to generate an initial set of associated segments with offset index and time stamp as the core structure. This can be understood as: concatenating all thread structure chains in ascending order of thread number to form a cross-thread integrated structure; in this structure, each access segment retains both the offset order within the original thread and the temporal location within the global operation segment, thus forming an initial set of associated segments with dual-dimensional features (structural dimension and temporal dimension).

[0028] Furthermore, the method of forming the temporal structure chain between the access segment and its reference time marker includes: For each thread segment, based on the position of the accessed segment within the thread segment, a continuous offset number is generated for it, and the offset number is recorded as the offset order index of the accessed segment; In this embodiment, access segments within the same thread segment are assigned consecutive offset numbers starting from zero, based on their actual order of appearance within that thread segment. Each number uniquely corresponds to an access segment, representing its structural position within the thread's execution sequence. The offset index, serving as a structural description field for the access segment, ensures the stability and consistency of the segment order representation within the thread.

[0029] Each offset index and its corresponding reference time stamp are combined to form an offset-time key-value pair, and this key-value pair is used as the basic element to form a graph node, thus forming an offset-time node set; In this embodiment, each accessed segment simultaneously possesses structural location information (offset index) and external reference time information (reference time stamp). The system combines these two into offset-time key-value pairs, where the offset index expresses the structural order within the thread, and the reference time stamp expresses the segment's temporal position within the global operation segment sequence. All offset-time key-value pairs are collected to form an offset-time node set.

[0030] Connect the nodes in the offset-time node set one by one in ascending order of time stamps to construct a time-continuous path chain for accessing fragments in a single-threaded dimension; Based on the reference time marker in each offset-time node, all nodes within the same thread segment are sorted in ascending order of time, and the connection relationship between nodes is established sequentially according to the sorting result, thereby forming a single-threaded time continuous path chain, reflecting the actual execution order of the access segment as time progresses within the thread, so that the structural dimension and the time dimension are expressed synchronously in the same thread.

[0031] For multiple thread segments, the time-continuous path chains they construct are grouped together using the thread identifier as the index identifier, and the grouping structure is used to form a cross-thread access-time mapping graph. After constructing a time-continuous path chain for each thread segment, the system groups all thread path chains based on their thread IDs. Each thread ID corresponds to an independent set of path chain nodes. Subsequently, the system integrates these thread-level path chains into an access-time mapping graph that includes multi-threaded relationships. Each sub-chain in the mapping graph retains its own thread attributes, enabling cross-thread access behavior to express the collaborative relationships between different threads on the time axis in a graph structure.

[0032] Using the access-time map as a local indexing framework for the temporal structure chain allows the internal temporal structure of access segments across threads to be expressed in a fixed graph-level structure.

[0033] In this embodiment, the access-time map is used as a structured graph indexing framework. Its nodes represent the positions of access segments in both structural and temporal dimensions, and the edges represent the temporal progression relationships of access behaviors. Through this map, all access sequences within a thread and the relative temporal relationships between threads can be expressed in a unified graph-level structure, achieving a visual representation and stable index of structural behaviors, and ensuring the consistency and traceability of cross-thread temporal structures.

[0034] S102: Based on the operation segment markers and thread migration segment boundaries in the initial associated segment set, construct a combined segment path; and locate the migration interruption trigger point in the scheduling cache history according to the intersection segment order and return segment sequence of the combined segment path; then combine the structural segments covered by the interruption trigger point into a trigger path group; To achieve the above objectives, the system uses the operation segment markers extracted from the initial associated segment set as starting nodes and the thread migration segment boundaries as bridging nodes to construct composite segment paths containing multi-threaded segments. During this process, the system traverses all thread segments in the initial associated segment set, searches for adjacent thread migration events for each operation boundary, and establishes connections between operation segments and migration segments accordingly. Each composite path consists of a complete operation unit and its preceding and following thread migration chains, forming multiple cross-thread path segment clusters.

[0035] A structure index table is established for each combined segment path to record metadata such as the operation segment number at the starting point of the path, the event identifier of the migration point, and the set of thread numbers to which the path segment belongs. This information is used to support subsequent topology identification and backtracking analysis of return segments, ensuring that the combined segment path has a stable tracking identifier during execution.

[0036] In each combined segment path, the system searches for segment identifiers indicating thread number backtracking or event time backtracking. If found, the segment is extracted as a return fragment. In this invention, return fragments are used to identify migration callbacks, reentrant calls, or nested exception recovery behaviors that occur during program execution. By comparing the timestamps of events and the trend of thread numbers in the path fragments, it can be determined whether a path segment is accessed in reverse order or is activated in a nested manner. Return fragments are constructed as topology nodes with return tags and connected to combined segment paths to form a topology chain group with a return structure. Various return nodes are labeled in the topology structure to facilitate causal chain backtracking in subsequent trigger point location.

[0037] Search the task scheduling cache log for the call history of path segments intersecting with the composite segment path, and extract the timestamps of events such as resource binding exceptions, migration interruptions, and thread blocking. The scheduling cache history is a historical record of the system's operations on each thread, task, and resource mapping during migration scheduling, including binding time, call delay, task switching, and failure events. Based on the trigger time point of the return segment in the composite segment path topology, trace back the scheduling history event chain to locate the first exception trigger point that caused the composite path to break or fail to execute. If there are multiple candidate points, prioritize the event with the event label of resource switching failure, thread wake-up failure, or interruption unrecovered.

[0038] The combined segment path nodes affected by the aforementioned trigger points are extended forward and backward by N steps (by default, 2-3 segments are expanded according to the structural dependency boundary) to form the structural coverage area. The determination of the extension area does not depend on specific numerical thresholds, but rather on the existence of dependencies between structural segments as the extension condition, until there are no more dependencies or control flow pointing in the path. All structural segments within the coverage area are aggregated to form trigger path groups, and each group is labeled with its start and end operation segments, migration segment intersection points, corresponding return labels, and other information.

[0039] In the specific implementation process, there is no need to set a fixed threshold for migration interruption events. Instead, the core is based on the cross topology of structurally dependent paths and the causal chain of historical records to ensure that the results are interpretable and traceable. The logic described in this step can be fully implemented on the basis of existing scheduling logs and execution path structure, with strong adaptability, low computational resource overhead, and practical engineering applicability.

[0040] S103: Based on the temporal relationship of the segments in the trigger path group, match the reverse rearranged operation group with the original call order to form the thread operation corresponding group, and identify the structurally asymmetric segment group based on the order difference and time correlation of operation-access segments. The method of matching the reversed operation group with the original call order to form the corresponding thread operation group includes: In the reverse-ordered operation group, each operation fragment is recorded with its position index in the rearranged sequence, and the corresponding thread identifier in the original task execution log is also recorded to form the rearranged index record of the operation fragment. During actual migration, due to changes in thread scheduling, resource mapping delays, or nested calls, the execution order of operation fragments may differ from their call order in the original task execution log. This step constructs a thread operation correspondence group by bidirectionally mapping the rearranged operation fragments to the original access fragments, representing the correspondence between the logical structure and actual execution.

[0041] Specifically, the pairing relationship between the operation fragment index and the access fragment index is constructed in the following ways: Record the rearranged sequence number of each operation fragment from the reverse rearranged operation group, use this number as the operation index of the operation fragment, and summarize it in the record table; extract all operation fragments from the trigger path group and assign numbers according to their order of appearance in the actual execution path. This number is the operation index, which is used to express the position of the operation fragment in the rearranged logical sequence.

[0042] Within each thread segment, consecutive sequential numbers are generated for the access segments based on their original order of appearance. These numbers serve as the access index for each access segment, and the call time range of the access segment is recorded. The access segments are traversed in the order of their appearance in the original log, and consecutive numbers are assigned sequentially to form the access index. Simultaneously, the call time range of each access segment is extracted for subsequent time adjacency screening.

[0043] Based on the thread identifiers of the operation segment and the access segment, a candidate matching matrix is ​​constructed. The overlap of the time ranges of the operation index and the access index is used as a filtering condition to select candidate pairings that satisfy both the same thread and adjacent time ranges. Using the thread number as the matching key, a candidate pairing matrix is ​​constructed between each operation segment and each access segment, where each element represents an operation-access combination. The system further calculates whether the time ranges of the operation segment and the access segment in each combination overlap or are adjacent. If they are temporally adjacent, they are selected as candidate pairings.

[0044] Operation segments and access segments that meet the conditions of time overlap and sequential connection are recorded as valid segment pairing groups, and operation-access dual index record entries are created for each combination. In the candidate combination, if the operation index and access index meet the following two conditions: they belong to the same thread and their time intervals overlap or are adjacent, then the operation-access combination can be determined as a valid pairing group, and a dual index entry is created for it, that is, the pairing relationship between the operation index and the access index is recorded at the same time to support subsequent sequential comparison.

[0045] All valid fragment combination entries corresponding to all threads are integrated to form a dual-path join index group, which serves as the basis for the composition of thread operation correspondence groups. All valid pairing groups in each thread are collected into a thread operation correspondence group and uniformly recorded in the dual-path join index group. This structure preserves the actual order of operations and accesses while maintaining their relative positions in the original thread structure, which is used for subsequent extraction and analysis of asymmetric fragment groups.

[0046] Extract the original occurrence order of the access segment within each thread segment, and establish an access segment sequence based on the access segment order to preserve the access call order within the thread; restore the calling logic of the access segment within the thread. In this step, establish a sequence of access segments based on their occurrence order in the original execution log.

[0047] Specifically, the system sorts the set of access segments corresponding to each thread number in ascending order of timestamps, and assigns sequential numbers according to the sorting result, starting from 0 and incrementing to form an access segment sequence. This sequence is used to indicate the original execution order of the access segments in the logical structure chain.

[0048] Using the thread identifier as the association key, corresponding records are established between the rearranged index of the operation segment and the access segment sequence. The candidate segment pairing table is formed by screening based on whether the operation segment and the access segment have an adjacency relationship in the time stamp region in the original log. Based on the operation segment rearranged index and the access segment sequence, this step constructs the matching relationship between the two to form the candidate segment pairing table to be screened.

[0049] Specifically, the system uses the thread ID as the primary key to attempt to pair operation segments with access segments. For each candidate pair, it further checks whether they belong to a time contiguous region in the original log, that is, whether the timestamps of the operation segment and the access segment differ within an acceptable window (e.g., within the same execution function or between two adjacent scheduling intervals). If the condition is met, it is added to the candidate pairing table.

[0050] Select fragment pairs from the candidate fragment pairing table that are thread-consistent and have adjacent timestamps, record them as operation-access fragment correspondence entries, and group them according to thread number; the established pairing relationship has stability and context consistency. This step extracts fragment pairs that meet the two key conditions from the candidate pairing table and records them as valid correspondences.

[0051] Specifically, the system filters fragment combinations that meet the following conditions: the operation fragment and the access fragment belong to the same thread, the difference between their timestamps is within an acceptable range, and the call sequence shows that the access fragment time immediately follows the operation fragment time. After filtering, all valid entries are grouped by thread number to form a set of operation-access fragment pairing entries divided by thread.

[0052] The system combines the operation-access fragment correspondence entries within each thread group to form a thread operation correspondence group, which provides a pairing structure expression between operation paths and access logic. After filtering all thread pairing entries, the system integrates the valid operation-access combinations within each thread into a group, which is the thread operation correspondence group.

[0053] Specifically, the system creates a list of structures for each thread, organizing all operation-access fragment pairs within it uniformly, and establishing a cross-index join mapping table to record metadata such as the operation index, access order, timestamp, and thread number for each pair. This structure preserves both the operation logic and the call sequence, laying the foundation for subsequent structure offset analysis and reliability assessment.

[0054] In addition, the identification methods for the structurally asymmetric segment groups include: Extract each operation-access fragment pair from the corresponding group of thread operations, and record the order number of the operation fragment and access fragment in the original thread fragment; extract each pair of operation-access fragments from the aforementioned corresponding group of thread operations, and further record the position (i.e., order number) of the two fragments in the pair in the original thread fragment.

[0055] Specifically, the operation segment sequence number can be directly derived from the position of the operation segment in the reordered index; the access segment sequence number is derived from the access sequence within the thread in the original log. Both use consecutive numbers starting from 0.

[0056] Using the operation segment order as a reference, the difference in the order number of each pair of operation-access segments is marked as the order offset, and the offset and the thread identifier form an order difference tuple; calculate the order difference in each operation-access combination, that is, the operation segment order minus the access segment order, as the order offset, and form an order difference tuple together with the thread number.

[0057] Specifically, the order offset can be positive or negative, representing whether the access action is earlier or later than the operation action. For example, if the operation order is 3 and the access order is 1, then the offset is +2, indicating that the access segment is 2 positions earlier.

[0058] Filter all entries with non-zero offsets in the sequence difference tuples and verify whether the offset has a skip sequence reversal feature, i.e., the access segment appears after the operation segment. Not all sequence offsets indicate anomalies. This step filters out combinations with non-zero offsets and the feature that the access segment is actually located after the operation segment, i.e., identifies tuples with skip sequence reversal features.

[0059] Specifically, if the offset is negative, it means that the operation segment is delayed in execution, while the access segment is executed first. At the same time, combined with the timestamp, if the time of the access segment is earlier than that of the operation segment, it can be confirmed that a structural reversal has occurred.

[0060] Tuples with the leap-type order reversal feature are grouped by thread identifier, and the corresponding fragment pairs in each group are used as candidate fragment combinations for structural asymmetry. All tuples with the leap-type order reversal feature are grouped by thread number, and their corresponding operation-access fragment combinations are extracted as candidate fragment combinations for structural asymmetry.

[0061] Specifically, each thread corresponds to a set of candidate asymmetric combinations, reflecting the potential inconsistent access behavior in that thread, and has structural offset characteristics.

[0062] All candidate asymmetric fragment combinations are deduplicated and renumbered to obtain a set of asymmetric fragment groups, representing the key locations where structural offsets exist between operation-access call paths. To avoid redundant analysis and misjudgments, the system deduplicates all candidate asymmetric combinations and renumbers the remaining combinations, ultimately forming the set of asymmetric fragment groups.

[0063] Specifically, the numbering is generated using a combination of thread number and its reversed position to ensure that each asymmetric segment group has a unique identifier. This structure set is the core data foundation for subsequent migration integrity verification and the generation of reliable migration criteria.

[0064] More specifically, the method for verifying the leapfrog order reversal feature of order difference tuples includes: The difference in the order number of each operation-access segment combination is defined as the operation precedence. The operation precedence is used to express whether the access segment is in the structural order before its corresponding operation segment. It is a quantitative indicator for identifying potential structural reversals. For each pair of operation segment and access segment combinations, the difference in their order numbers is calculated. If the value is less than zero, it is judged that there may be an abnormal situation where the access segment is prioritized over the operation segment. For all combinations with negative pre-operation values, the corresponding access segments are summarized by thread identifier, and their actual call times in the execution log are retrieved. Structural order offset does not necessarily mean execution abnormality; it is also necessary to verify whether it is a true reversal by combining time information. All combinations with pre-operation values ​​less than zero are grouped by thread number, and the timestamp information of their access segments in the task execution log is extracted. Then, the timestamps of operation segments in the same combination are retrieved as a reference for the actual call time.

[0065] If the call time of an access segment is later than the call time of its associated operation segment, it is considered a pseudo-reversal combination and is discarded; otherwise, it is considered a valid order reversal. If an access segment has an earlier structural order but its actual execution time is later than that of an operation segment, the offset is considered to be due to scheduling delay or structural compression optimization and is not considered an anomaly. For each combination, a time comparison is performed. If the call time of the access segment is greater than or equal to the call time of the operation segment, it is marked as a pseudo-reversal combination and removed from the structural asymmetry analysis. Only when the call time of the access segment is earlier than that of the operation segment is it considered a valid order reversal.

[0066] All valid order reversal combinations are constructed into fragment pairs with offset labels, and each combination is given a cross-feature identifier to support subsequent mapping analysis; for all valid order reversal combinations that pass the verification, the system converts them into structural units with structural offset attributes for subsequent structural mapping and comparison processes.

[0067] Specifically, the system adds the following tag information to each valid combination: Offset labels (such as -1, -2, etc., structural order offsets); Time offset (time difference during call); Crossing characteristic markers (such as whether it crosses a thread migration boundary or whether thread skipping occurs); Construct fragment pairs with offset labels and treat them as logical nodes with actual offset behavior.

[0068] The combinations with the crossing feature identifiers mentioned above are summarized into a structural asymmetry confirmation set, and structural asymmetry fragment groups are extracted from it to further support the structural consistency comparison process. All valid offset fragment pairs with crossing features are aggregated to form a structural asymmetry confirmation set, which serves as the core candidate set for formally participating in consistency comparison and trusted migration assessment.

[0069] Specifically, the confirmation set is cross-aligned with the aforementioned trigger path group, and the combination with the most inconsistent structural position and the largest time offset is extracted as the structural asymmetric segment group, which is used for credibility calculation, rollback condition triggering and visualization annotation in subsequent steps.

[0070] S104: Map the structurally asymmetric segment group to the resource scheduling segment of the target star node, construct a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculate the structural offset level of the migration; This can be understood as follows: by comparing the structurally asymmetric fragment groups identified in the source star node across nodes, finding the corresponding fragments on the target star node, and calculating the degree of structural change between the two in terms of thread number and fragment order, a migration mapping relationship group is formed, and the structural consistency or offset risk during the migration process is assessed accordingly.

[0071] The construction logic of the migration mapping relationship group is as follows: Extract fragment entities from the target star node that have the same number as the asymmetric fragment group in the source node structure, and label each fragment entity with its thread number and offset position within the fragment. Specifically, the system first retrieves the resource scheduling log or state snapshot from the target star node and identifies the segment entity with the corresponding number in the asymmetric segment group of the source node. For each segment, the system reads its current thread number and the segment's offset position within the current thread (such as its relative index in the scheduling block sequence).

[0072] The thread number and offset position of each structurally asymmetric segment in the source node are used as source labels, and a mapping pair is constructed corresponding to the positional features of the segment with the same number in the target star node. Each structurally asymmetric segment has a source label, which is its thread number and offset index. This step compares the source labels with the structural positions of the segments with the same number extracted from the target node to construct a structural mapping pair.

[0073] If the positional characteristics of the same numbered segment in the target node show changes in thread number or offset order, it is considered a valid structural offset mapping entry and recorded as a structural variation pair. If the mapping pair shows changes in the thread number or offset position of the segment in the target node, the mapping entry is considered to have structural differences and constitutes a structural variation pair.

[0074] Reconstruct all structural mutation pairs into position offset trajectories according to fragment numbers and generate a thread-offset trajectory mapping table; reconstruct the position change behavior in each structural mutation pair into an offset trajectory using fragment numbers as indexes, and record its change path from the source state to the target state.

[0075] All mapping entries in the mapping table that exhibit position changes or thread switches are organized into migration mapping relationship groups, serving as the input basis for migration consistency analysis. All structural variant pairs with position changes (thread number or sequence offset) are included in the migration mapping relationship groups, representing the set of corresponding offset behaviors between the source and target star nodes at the structural mapping layer. The migration mapping relationship groups record the manifestations of post-migration structural rearrangement, binding transfers, scheduling delays, and other behaviors, forming the core data foundation for migration consistency analysis and reliability assessment.

[0076] To further explain, the method for calculating the structural offset level of the migration includes: The total number of all segment numbers in the asymmetric segment group is counted, and a summary table of numbers is constructed as the original structural baseline set. Before evaluating the structural consistency after migration, the system needs to establish a structural reference baseline, which is the complete set of numbers of the asymmetric segment group in the source star node.

[0077] Extract all fragment entries that have undergone offset or thread number change from the migration mapping relationship group to form a mapping offset set. Fragment entries include fragments with changed thread numbers and fragments with changed offset positions. Collect all fragment numbers that meet any of the above conditions and record the corresponding offset type, offset magnitude and target position status. Calculate the coverage ratio of the segment numbers in the mapped offset set in the original structural reference set, and construct a ratio analysis table to reflect the coverage degree of the offset segments in the entire structural reference.

[0078] Set the structural offset ratio threshold range, and mark it as high offset, medium offset, or low offset level according to the coverage ratio range in the ratio analysis table; the specific threshold division is as follows: High offset level: Coverage ratio ≥70%; Mid-offset level: 40% ≤ coverage ratio < 70%; Low offset level: Coverage ratio <40%; Based on the offset ratio range in the ratio analysis table, assign an offset level label to the current migration task.

[0079] The offset level is used as the consistency level indicator of the migration state, and the final consistency verification result is generated in the indicator system to characterize the consistency of the structural behavior during the virtual load migration process. This level indicator is included in the consistency verification system along with other dimension information (such as the number of interruptions, thread latency, etc.) and a migration verification result report is generated, which includes: mapping offset ratio, offset level label (high / medium / low) and recommended handling measures (structural injection / rollback / manual intervention). Example: If the migration offset of a certain task is 75%, the system marks it as a high offset level and generates a verification result: consistency verification failed, and it is recommended to trigger the structure rollback mechanism.

[0080] S105: Based on whether the structural offset level displayed by the migration mapping relationship group is acceptable, and at the same time check the segment tail mark of the trigger path group, construct the segment tail chain group through the segment tail swap relationship; if the structural offset level meets the credibility standard and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a credible migration structure and structural injection is performed; otherwise, the original structure rollback process is triggered.

[0081] In this embodiment, the final determination of migration integrity relies on dual verification of structural offset quantization and context boundary qualitative analysis.

[0082] (1) Determination of the credibility standard for structural offset level: The low offset level is set as the credibility standard. If it is a medium offset level, it is judged as secondarily credible and needs to be further verified by the complementary interleaving relationship; if it is a high offset level, it is directly judged as uncredible.

[0083] (2) Construction logic of the segment tail chain group: Extract all segment tail markers (such as the end marker of the operation segment and the completion marker of the thread migration) from the trigger path group. In the target star node, the system finds the recovery start marker corresponding to these segment tail markers. The segment tail swap relationship is to establish the pairing between the segment tail marker of the source node and the recovery marker of the target node to form the segment tail chain group.

[0084] (3) Determination of complementary interleaving relationship: The complementary interleaving relationship means that all corresponding pairings of the tail chain groups in the tail chain group satisfy the following conditions: Timing connection: If the timestamp of the source node segment tail is earlier than the timestamp of the target node recovery tag, and the time difference is within the preset scheduling delay threshold, it indicates that the connection is tight.

[0085] Context consistency: The thread ID or resource context of the source node segment tail marker is consistent with or acceptablely mapped to the thread ID or resource context of the target node recovery marker.

[0086] When all pairings meet the above conditions, it is determined that there is a complementary and interleaved relationship, indicating that the migration boundary is complete and undamaged.

[0087] (4) Final determination: If the structural offset level is low and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a reliable migration structure and structural injection is performed; otherwise, the original structure rollback process is triggered.

[0088] Example 2 This embodiment, based on Embodiment 1, provides a specific application example. A shared constellation platform runs a multi-service onboard operating system, within which a virtual payload instance for image enhancement and target extraction is deployed. This instance originally resides on virtual node VN-A3 of satellite A, but during on-orbit operation, it needs to be migrated to instance VN-B2 of satellite B due to resource reallocation. To ensure the integrity of its execution state, the integrity verification method described in this invention needs to be applied to this migration process.

[0089] First, extract the task execution logs from VN-A3 for the most recent 30 seconds. The log content includes operation segment markers (such as image filtering and feature extraction calls), thread transition segment boundaries (such as a task jumping from thread t1 to t3), and memory access segment boundaries (such as accessing the camera buffer 0x01FF).

[0090] Parsing the logs yields an initial set of structure fragments, comprising: 12 operation fragments, 18 access fragments, and 5 thread migration fragments. Then construct a composite segment path that reflects the task execution flow, for example: This path represents a coherent execution sequence: the task first executes operations Op1 and Op3; then, the execution context switches from thread t1 to thread t3; next, operation Op4 is executed; and finally, memory access Access5 is performed. The purpose of constructing this path is to establish a traceable, multi-dimensional execution graph. Next, based on the sequence of return segments (e.g., non-linear calls or reentrancy) and the topological intersections of segments (overlaps between different paths) in the path, the system searches for anomalies in the scheduling cache history, locating a clear illegal memory mapping behavior in thread t1, which triggered a task suspension interruption. This specific anomaly event is identified as the trigger point for the migration interruption, determining the execution regions affected by the interruption event: Op4, Access5, and the t3 migration. The execution region represents the precise context of the task when it is interrupted or its state is frozen; that is, it is the critical state after the thread t3 switch, preparing to execute Op4 and Access5, the set of critical structural segments covered by the interruption event, and is ultimately aggregated into the trigger path group.

[0091] The operation-access fragments in the trigger path group are paired, and the following process is used to verify whether there is a misalignment: 1) Matching the reversed operation group with the original call order: Logically rearrange the operation sequence received by the target star node and compare it with the original access order on the source star node to establish the corresponding group of thread operations.

[0092] 2) Identify Priority Differences: Calculate the priority offset for each paired operation segment (e.g., Op4) and access segment (e.g., Access5). In this example, the priority difference between operation Op4 and access Access5 is found to be -1.

[0093] Sequence differences alone are insufficient to prove structural anomalies; further time-based verification is required. Time Verification: The system verifies whether the actual call time of Access5 is later than the call time of its associated operation Op4. If Access5 is in the earlier order (negative offset) but is delayed in time, it is confirmed to constitute a skip order reversal. This eliminates false reversals caused by simple scheduling delays and identifies the real structural error.

[0094] Based on the above verification, the system identified three pairs of sequence exceptions in thread t3 and constructed a group of structurally asymmetric fragments, as illustrated below: ; The structurally asymmetric fragment group contains all confirmed critical execution nodes with structural misalignments. Sequence anomalies represent structural misalignments between operational logic (Op) and data access caused by migration interruptions. For example, This indicates that in thread t3, the access fragment Access5 is logically positioned one position ahead of its corresponding operation fragment Op4. This time-verified genuine reversal eliminates the possibility of a false reversal and successfully pinpoints the culprit of incomplete transition state to a specific execution node.

[0095] Searching for the fragment entities with the above-mentioned inconsistent structural numbers in the target node VN-B2, it was found that the thread numbers of two fragments in the structurally asymmetric fragment group changed (for example, from thread t3 to thread t5), and the order offset changed (from -1 to +2), indicating that the recovery process of the target node introduced new structural deviations.

[0096] Based on the discovered mutations, the risk level of migration is quantified: Calculate the offset ratio: The original structure has a total of 5 asymmetric segments, and the number of segments that actually undergo offset or thread changes is 3. Therefore, the offset ratio is 60%.

[0097] The offset ratio of 60% falls within the preset medium offset threshold range [40%, 70%]. This indicates that the migration caused a moderate degree of disturbance to the internal structure of the virtual payload. The final credibility is determined to be at the medium offset level, which is considered secondary credibility and requires boundary verification.

[0098] Looking back at the segment tail markers [tail1, tail2, tail3] of the trigger path group, in VN-B2, the segment tail chain group constructed through the segment tail swapping relationship presents the connection order of tail1, tail3 to tail2, which satisfies the complementary and interleaved relationship. This proves that although there is a 60% deviation in the internal structure, the logical end point executed by the source node and the logical start point restored by the target node achieve perfect, tight and consistent context connection.

[0099] Based on the verification results of mid-offset (sub-credible) but complementary and interlaced boundaries, the system ultimately determines that the migration structure is credible, executes the structure injection process, and completes the migration of the image processing payload. The verification process records the verification hash and the injected structure identifier; through quantitative analysis of key segments such as Op4, it is demonstrated that in a resource-constrained spaceborne environment, the dual measurement of structural offset quantization and boundary integrity (complementary and interlaced) effectively confirms and ensures the state integrity of the virtual payload migration.

[0100] Example 3 like Figure 3 As shown in the figure, the parts not described in detail in this embodiment are as shown in Embodiment 1. This embodiment provides an integrity verification system that supports the migration state of onboard virtual payloads, including a log parsing module, a path construction module, an operation pairing module, a mapping analysis module, and a consistency verification module. Data is transmitted between the modules via wired and / or wireless means. The log parsing module extracts the task execution logs of the virtual payload instance to be migrated in the source star node, and parses out three types of marker fragments: operation segment marker, thread migration segment boundary, and memory access segment boundary. Based on the thread offset and time marker of the access segment, an initial set of associated fragments is constructed. The path construction module constructs a combined segment path based on the operation segment markers and thread migration segment boundaries in the initial associated segment set; according to the topology and return sequence of the combined segment path, it locates the migration interruption trigger point in the scheduling cache history, and aggregates the structural segments covered by the trigger point into a trigger path group; The operation matching module matches the reverse-ordered operation group with the original call order based on the temporal relationship of the segments in the trigger path group, forming a corresponding group of thread operations, and identifies the structurally asymmetric segment group based on the order difference and temporal correlation of operation-access segments. The mapping analysis module maps the structurally asymmetric segment group to the resource scheduling segment of the target star node, constructs a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculates the structural offset level of the migration. The consistency verification module checks whether the structural offset level displayed by the migration mapping relationship group is acceptable, and also checks the segment tail marker of the trigger path group. It constructs a segment tail chain group through segment tail swapping relationships. If the structural offset level meets the trust criteria and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a trustworthy migration structure, and structural injection is performed; otherwise, the original structure rollback process is triggered.

[0101] This embodiment provides an integrity verification system that supports the migration state of onboard virtual payloads. It is used to execute the integrity verification method for supporting the migration state of onboard virtual payloads provided in the above embodiments of the present invention. The specific methods and processes for implementing the corresponding functions of the various structures included in the integrity verification system for supporting the migration state of onboard virtual payloads are detailed in the above embodiments of the integrity verification method for supporting the migration state of onboard virtual payloads, and will not be repeated here.

[0102] Example 4 This embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in Embodiment 1.

[0103] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless network. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0104] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0105] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0106] In the several embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only one method, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0107] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0108] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0109] The foregoing has only described certain exemplary embodiments of the present invention by way of illustration. Undoubtedly, those skilled in the art can modify the described embodiments in various ways without departing from the spirit and scope of the present invention. Therefore, the foregoing drawings and descriptions are illustrative in nature and should not be construed as limiting the scope of protection of the claims of the present invention.

Claims

1. A method for verifying the integrity of a spaceborne virtual payload's transition state, characterized in that, Includes the following steps: S101: Extract the task execution log of the virtual payload instance to be migrated in the source star node, and parse out three types of marker fragments: operation segment marker, thread migration segment boundary and memory access segment boundary. Based on the thread offset and time marker of the access segment, construct the initial associated fragment set. S102: Based on the operation segment markers and thread migration segment boundaries in the initial associated segment set, construct a combined segment path; according to the topology and return sequence of the combined segment path, locate the migration interruption trigger point in the scheduling cache history, and aggregate the structural segments covered by the trigger point into a trigger path group; S103: Based on the temporal relationship of the segments in the trigger path group, match the reverse rearranged operation group with the original call order to form the thread operation corresponding group, and identify the structurally asymmetric segment group based on the order difference and time correlation of operation-access segments. S104: Map the structurally asymmetric segment group to the resource scheduling segment of the target star node, construct a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculate the structural offset level of the migration; S105: Based on whether the structural offset level displayed by the migration mapping relationship group is acceptable, and at the same time check the segment tail mark of the trigger path group, construct the segment tail chain group through the segment tail swap relationship; if the structural offset level meets the credibility standard and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a credible migration structure and structural injection is performed; otherwise, the original structure rollback process is triggered.

2. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 1, characterized in that, The construction logic of the initial associated fragment set is as follows: In the source star node task execution log, each access segment is identified and assigned an intra-thread offset index according to its arrangement order within its respective thread segment, so as to form the basic structure sequence inside the thread segment. Extract the time stamp of each operation segment from all operation segments, arrange the operation segments in chronological order according to the time stamp, retrieve the operation segment time stamp corresponding to the first access segment from the arrangement result, and obtain the reference time stamp corresponding to the access segment. The intra-thread offset index, corresponding thread number, and reference timestamp of the accessed segment are integrated into a ternary combination unit and recorded in the index record table; Based on thread number, all ternary combination units are aggregated according to thread segments, and arranged in ascending order of offset index within each aggregation group to form a temporal structure chain between the access segment and its reference time marker. All thread segments are combined in the order of their corresponding temporal structure chains according to their thread numbers to generate an initial set of associated segments with offset indices and time stamps as the core structure.

3. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 2, characterized in that, The methods for forming a temporal structure chain between an access segment and its reference time marker include: For each thread segment, based on the position of the accessed segment within the thread segment, a continuous offset number is generated for it, and the offset number is recorded as the offset order index of the accessed segment; Each offset index and its corresponding reference time stamp are combined to form an offset-time key-value pair, and this key-value pair is used as the basic element to form a graph node, thus forming an offset-time node set; Connect the nodes in the offset-time node set one by one in ascending order of time stamps to construct a time-continuous path chain for accessing fragments in a single-threaded dimension; For multiple thread segments, the time-continuous path chains they construct are grouped together using the thread identifier as the index identifier, and the grouping structure is used to form a cross-thread access-time mapping graph. Using the access-time map as a local indexing framework for the temporal structure chain allows the internal temporal structure of access segments across threads to be expressed in a fixed graph-level structure.

4. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 1, characterized in that, The method of matching the reversed operation group with the original calling order to form the corresponding thread operation group includes: In the reverse-arranged operation group, record the position index of each operation fragment in the rearranged sequence, and at the same time record the thread identifier corresponding to the operation fragment in the original task execution log to form the rearranged index record of the operation fragment. Extract the original occurrence order of the access segment within each thread segment, and establish an access segment order sequence based on the access segment order to preserve the access call order within the thread. Using the thread identifier as the association key, a corresponding record is established between the rearranged index of the operation segment and the access segment sequence. The candidate segment pairing table is formed by screening based on whether the operation segment and the access segment have an adjacency relationship in the time stamp region of the original log. Select fragment pairs that are thread-consistent and have adjacent timestamps from the candidate fragment pairing table, record them as operation-access fragment correspondence entries, and group and classify them according to thread number; The operation-access segment correspondence entries within each thread group are combined to form a thread operation correspondence group, providing a paired structural expression between operation paths and access logic.

5. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 4, characterized in that, The pairing relationship between the operation fragment index and the access fragment index is constructed in the following ways: Record the rearranged sequence number of each operation segment from the reverse rearranged operation group, use this number as the operation index of the operation segment, and summarize it in the record table; Within a thread segment, a sequential number is generated for each access segment according to its original order of appearance. This number is used as the access index for the access segment, and the call time range of the access segment is recorded. Based on the thread identifier of the operation segment and the thread identifier of the access segment, a candidate matching matrix is ​​constructed, and the candidate pairing combination that satisfies the condition of whether the time range of the operation index and the access index overlaps is selected. Operation segments and access segments that meet the conditions of time overlap and sequential connection are recorded as valid segment pairing groups, and operation-access dual index record entries are created for each combination; All valid fragment combination entries corresponding to all threads are integrated to form a dual-path connection index group, which serves as the basis for the composition of the corresponding thread operation group.

6. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 1, characterized in that, The identification methods for the structurally asymmetric segment groups include: Extract each operation-access segment pair from the corresponding group of thread operations, and record the order number of the occurrence of the operation segment and access segment in the original thread segment; Using the order of operation segments as a reference, the difference in the order number of each pair of operation-access segments is marked as an order offset, and the offset and the thread identifier are combined to form an order difference tuple; Filter all entries with non-zero offsets in the sequence difference tuples and verify whether the offset has a skip sequence reversal feature, i.e., the access segment appears after the operation segment; Tuples with cross-order reversal characteristics are grouped by thread identifier, and the corresponding fragment pairs in each group are used as candidate fragment combinations for structural asymmetry. All candidate segments with structural asymmetry are combined, deduplicated, and renumbered to obtain a set of structural asymmetric segments, which represents the set of key locations where there is a structural offset between the operation-access call path.

7. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 1, characterized in that, The methods for verifying the leapfrog reversal feature of rank difference tuples include: The difference in the order number of each operation-access segment combination is defined as the operation precedence. If this value is less than zero, it is judged that there may be an abnormal situation where the access segment takes precedence over the operation segment. For all combinations of operations with negative pre-conditions, summarize the corresponding access segments by thread identifier and retrieve their actual call times in the execution log; If the access segment is invoked later than its associated operation segment, it is considered a pseudo-reversal combination and is removed; otherwise, it is considered a valid order reversal. All valid order reversal combinations are constructed into fragment pairs with offset labels, and each combination is appended with a cross feature identifier to support subsequent mapping analysis; The combinations with the crossing feature identifiers are summarized into a structural asymmetry confirmation set, and structural asymmetry fragment groups are extracted from it to further support the structural consistency comparison process.

8. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 1, characterized in that, The logic for constructing the migration mapping relationship group is as follows: Extract fragment entities from the target star node that have the same number as the asymmetric fragment group in the source node structure, and label each fragment entity with its thread number and offset position within the fragment. The thread number and offset position of each structurally asymmetric segment in the source node are used as the source label, and a mapping pair is constructed with the position features of the segment with the same number in the target star node. If the positional characteristics of the same numbered segment in the target node show changes in thread number or offset order, it is considered a valid structural offset mapping entry and recorded as a structural variation pair. Reconstruct all structural variant pairs into position offset trajectories according to fragment number, and generate a thread-offset trajectory mapping table; All mapping entries in the mapping table that have undergone position changes or thread switching are organized into migration mapping relationship groups to serve as the input basis for migration consistency analysis.

9. The integrity verification method for supporting the migration state of onboard virtual payloads according to claim 8, characterized in that, The method for calculating the structural offset level of the migration includes: The total number of segment numbers in the asymmetric segment group is counted, and a summary table of numbers is constructed as the original structural reference set. Extract all fragment entries that have undergone offset or thread number changes from the migration mapping relationship group to form a mapping offset set; Calculate the coverage ratio of the segment numbers in the mapped offset set in the original structural reference set, and construct a ratio analysis table; Set the structural offset ratio threshold range, and mark it as high offset, medium offset or low offset level according to the coverage ratio range in the ratio analysis table; The offset level is used as an indicator of the consistency level of the migration state, and the final consistency verification result is generated in the indicator system.

10. An integrity verification system supporting the migration state of onboard virtual payloads, based on the implementation of the integrity verification method supporting the migration state of onboard virtual payloads according to any one of claims 1-9, characterized in that, It includes a log parsing module, a path building module, an operation pairing module, a mapping analysis module, and a consistency verification module. Data is transmitted between the modules via wired and / or wireless means. The log parsing module extracts the task execution logs of the virtual payload instance to be migrated in the source star node, and parses out three types of marker fragments: operation segment marker, thread migration segment boundary, and memory access segment boundary. Based on the thread offset and time marker of the access segment, an initial set of associated fragments is constructed. The path construction module constructs a combined segment path based on the operation segment markers and thread migration segment boundaries in the initial associated segment set; according to the topology and return sequence of the combined segment path, it locates the migration interruption trigger point in the scheduling cache history, and aggregates the structural segments covered by the trigger point into a trigger path group; The operation matching module matches the reverse-ordered operation group with the original call order based on the temporal relationship of the segments in the trigger path group, forming a corresponding group of thread operations, and identifies the structurally asymmetric segment group based on the order difference and temporal correlation of operation-access segments. The mapping analysis module maps the structurally asymmetric segment group to the resource scheduling segment of the target star node, constructs a migration mapping relationship group based on the position change and thread switching information of the mapped segments, and calculates the structural offset level of the migration. The consistency verification module checks whether the structural offset level displayed by the migration mapping relationship group is acceptable, and at the same time checks the segment tail mark of the trigger path group. It constructs a segment tail chain group through the segment tail swap relationship. If the structural offset level meets the trust criteria and the segment tail chain group has a complementary and interleaved relationship, it is confirmed as a trustworthy migration structure and the structure injection is performed; otherwise, the original structure rollback process is triggered.

Images