System for data processing with locked execution cycle, fixing a data snapshot and cycle log

Abstract

(Main claim) Data processing system (100) with a stepwise interlocked execution cycle for processing multi-source data on a digital platform, comprehensive processing and storage resources set up for enforcing operational restrictions and for reference-based structural verification during operation, and comprehensive: (10) a data acquisition unit, (20) a unit for fixing an operational data snapshot, (30) a unit for standardized transformation, (40) a stepwise merging unit for forming a composite operating state, (50) a unit for generating operational categories, (60) a reference matching unit, (70) a sequence-based processing unit within a category, (80) a structural verification unit, as well as (90) a cycle log and execution state management unit, characterized by that the system (100) is set up in such a way, that an execution cycle is performed solely on the basis of a fixed operational data snapshot, that a change to the input reference is prevented during the execution cycle, that an overlap of simultaneous cycles on shared resources is prevented as a result of different or conflicting references, that output or reuse of an intermediate result is prevented before the cycle has achieved complete internal consistency and a final cycle protocol has been finalized. and that the use of intermediate results outside the cycle log associated with the operational data snapshot is prevented.

Description

Technical field

[0001] The invention relates to data processing systems operated on digital platforms, and in particular to a system that enforces a multi-stage interlocked execution cycle for processing multi-source data, based on fixing a referenced operational data snapshot, forming composite operating states, generating referenced operating categories, and internally restricted, sequence-based processing, and which includes an internal cycle protocol and a verification mechanism that prevents overlap and fragmentation and prevents output before internal consistency is achieved, wherein the invention represents an internal operating mechanism that influences system behavior during execution by controlling concurrency, reference stability, rejection rules, and completeness indicators, and wherein said units are implemented by processing and storage components.which are set up to enforce operational restrictions and for reference-based testing during ongoing system operation. Technical background

[0002] Known systems for processing matching data use processing mechanisms that allow the generation of incremental or partial outputs during execution. These mechanisms also permit data updates during processing or the execution of concurrent operations on the same resources, leading to divergent outputs when the same inputs are repeated or conflicts resulting from overlapping execution. Furthermore, some systems allow the reuse of intermediate results outside the context of a complete cycle, without a reference protocol to demonstrate completeness and the sequence of stages. This results in the absence of internal operational constraints that prevent race situations and overlaps, and that halt output before internal consistency is achieved within a referenced processing cycle. Technical problem

[0003] The technical problem lies in the lack of an internal operational mechanism to fix a data reference for the cycle and prevent input changes during execution; the lack of a mechanism to prevent overlapping simultaneous processing cycles on the same resources; the lack of stepwise completeness indicators that prevent output before internal consistency is achieved; and the lack of rejection rules that prevent the reuse of intermediate results outside of a complete cycle log. This leads to unstable outputs and a lack of reproducibility when the same inputs are repeated under the same operating conditions, as well as the possibility of overlapping execution or mixing of different references, resulting in operational conflicts within the system.The core technical problem lies in the inability to ensure operational consistency during processing due to overlapping execution cycles on shared resources and changing data references during operation, rather than in the selection or sorting of outputs per se. Technical solution

[0004] The problem is solved by a data processing system (100) comprising interconnected operating units that operate according to a mandatory execution sequence and include the following: • Data acquisition unit (10) • Unit for fixing the operational data snapshot (20) • Unit for normalized transformation (30) • Stepwise merging unit for forming the composite operating state (40) • Unit for generating business categories (50) • Reference matching unit (60) • Sequence-based processing unit within category (70) • Structural verification unit (80) • Cycle log and execution state management unit (90)

[0005] The core comprises a mechanism for fixing the snapshot reference for the cycle, a verification mechanism that prevents output if the snapshot reference deviates or if the stepwise execution indicators are incomplete, and a rejection mechanism that prevents the use of an intermediate result outside the cycle log associated with the operational snapshot, so that the system is not merely a logical procedure for sorting outputs, but an internal operational mechanism that enforces execution restrictions, prevents overlap, prevents partial results and prevents the mixing of references during execution.

[0006] The system further includes a referential identification mechanism for intermediate results, such that each intermediate result is linked to the cycle reference and the reference of the operational data snapshot, and it prevents an intermediate result from being passed to a subsequent stage or to output unless it matches the reference of the current cycle, with immediate rejection being executed if a reference deviation is detected.

[0007] The system further includes a mechanism for controlling concurrent execution on the same resources, based on snapshot references and the cycle log, to prevent protocol overlap between concurrent cycles, thus preventing the sharing of intermediate results, completeness indicators, or composite operating states between logs of different cycles, and generating no output if an overlap of references or logs is detected during execution. Description of the drawings • Figure (1): General block diagram of the system architecture (100). • Figure (2): Flowchart of the multi-stage interlocked execution cycle. • Figure (3): Diagram of the mechanism for fixing the operational data snapshot (20) and its reference. • Figure (4): Diagram of the cycle protocol (90) as well as the completeness indicators and rejection rules. Detailed description of an embodiment

[0008] As shown in Figure (1), the system (100) includes a data acquisition unit (10) configured to receive multi-source operational data. The data acquisition unit (10) is connected to the operational data snapshot fix unit (20), which is configured to generate a fixed operational snapshot for the cycle, encompassing the inputs used exclusively within a single execution cycle, and to generate an internal reference for the snapshot and to register this reference in the cycle log, such that the snapshot reference is a mandatory requirement for any subsequent processing within the cycle.

[0009] In one embodiment, the operational data snapshot is fixed by generating a permanent copy of the inputs required for the cycle and storing it in a cycle-specific execution area. In another embodiment, the snapshot is fixed by freezing the versions of the elements it contains, by registering a version identifier for each element, such that any subsequent deviation of the version identifier is considered a change to the snapshot reference. In all embodiments, the snapshot fixing unit (20) generates a snapshot identifier and a cycle identifier and links them to the cycle log (90), and each element within the snapshot is provided with a reference mark that includes the cycle identifier, the snapshot identifier, and the element's version identifier, and any element that does not match this reference is rejected.

[0010] The unit for fixing the operational data snapshot (20) is connected to the unit for normalized transformation (30), which is set up to convert raw elements into normalized representations according to specified transformation rules, preventing a raw element from being entered into subsequent processing before the normalized transformation is completed and registered within the snapshot reference, and preventing the acceptance of a normalized representation if it is not linked to the snapshot reference of the cycle.

[0011] The normalized transformation unit (30) is connected to the stepwise merging unit (40), which is set up to form a composite operating state for each service provider based on normalized representations within the snapshot reference, preventing the generation of an outputtable intermediate result before the formation of the composite operating state is completed and a stepwise completeness indicator is registered in the cycle log, and preventing the use of a composite operating state if it was not generated within the same snapshot reference.

[0012] The stepwise merging unit (40) is connected to the operating category generation unit (50), which is configured to generate a referenced operating category for each composite operating state according to internal transition limits, such that the category is generated within the snapshot reference and registered in the cycle log, preventing any generation outside the snapshot reference or using an intermediate result not registered in the cycle log, and preventing the retrieval of categories or states from another cycle during the execution of the current cycle.

[0013] The operating category generation unit (50) is connected to the reference matching unit (60), which is configured to generate a reference for an operating category of the cycle based on a reference value fixed within the snapshot reference, and to register the selected reference category in the cycle log, preventing a transition to sequence-based processing before a completeness indicator for the reference category is verified, and preventing reference matching from being performed on inputs not fixed within the snapshot reference.

[0014] The reference matching unit (60) is connected to the sequence-based processing unit within the category (70), which is set up to generate internal values ​​linked to the snapshot reference for each composite operating state within the reference category, and to fix these values ​​in the cycle log, and subsequently to generate an internally restricted sequence within the reference category based on the fixed internal values, preventing any output before the completeness indicators of the sequence-based processing are verified, and preventing any partial or stepwise output before the completeness of the registered stepwise indicators.

[0015] The sequence-based processing unit within category (70) is connected to the structural verification unit (80), which is set up to verify the completeness of all stages according to the mandatory execution sequence, to verify the stability of the reference of the operational data snapshot during execution, to verify the non-overlap of references from different cycles, and to enforce rejection rules that prevent output in the event of a snapshot change, reference deviation, or an attempt to use an intermediate result outside the cycle protocol, whereby the structural verification acts as an internal operational constraint that prevents race situations and overlap and prevents the mixing of results between concurrent cycles on the same resources.

[0016] In one embodiment, before an intermediate result is passed to a subsequent stage, a mandatory reference matching check is performed. This check verifies that the reference marker of the intermediate result matches the reference of the current cycle, the data snapshot reference, and the cycle log. Any reference discrepancy results in immediate rejection. In another embodiment, immediate rejection is also performed if a required stage-level completeness indicator is missing or if an attempt is made to use an intermediate result that is not recorded in the cycle log associated with the snapshot reference. Upon the occurrence of a rejection condition, the current cycle is immediately terminated, and the rejection state and its cause are recorded in the cycle log without affecting other running cycles or resources not associated with the cycle identifier.

[0017] In one embodiment, an execution restriction is created that is linked to the cycle identifier and the resource area used, so that the system prevents the sharing of intermediate results, completeness indicators, or composite operating states between protocols of different cycles. In another embodiment, the resource area is divided into sub-areas, and the restriction is applied to the sub-area that corresponds to the data group to be processed, thereby preventing protocol overlap when executing simultaneously on the same resources.

[0018] The structural verification unit (80) is connected to the cycle log and execution state management unit (90), which is set up to register the snapshot reference, stage progress indicators, stage completeness indicators and rejection rules, and to manage stage execution states of the cycle, including the states of snapshot fixing, completion of normalized transformation, completion of compound operating state formation, completion of category generation, completion of reference category selection, completion of sequence-based processing and completion of structural verification.In one embodiment, cycle protocols are distributed across multiple processing units, maintaining a uniform reference for the snapshot and cycle identifier, so that the verification and rejection rules remain effective regardless of the number of concurrent cycles.

[0019] In one embodiment, the system includes a recovery mechanism that allows the reactivation of an incomplete cycle from the last stepwise completeness state registered in the cycle log, whereby the reference adjustment is reapplied before execution continues.

[0020] No output is generated until a final completeness indicator is verified by the structural verification unit (80) and the final cycle log is fixed within the cycle log and execution state management unit (90), so that each output is linked to a referenced cycle log and cannot be generated without executing the same mandatory sequence within the same snapshot reference. Reference symbol list 100 data processing systems with locked execution cycle 10 Data acquisition unit 20 units for fixing the operational data snapshot 30 units on standardized transformation 40 units for gradual integration 50 units for generating business categories 60 Reference Matching Unit 70 Sequence-based processing unit within the category 80 Structural Verification Unit 90 Cycle Log and Execution State Management Unit Key technical impact

[0021] The main technical effect consists of enforcing a multi-stage interlocked execution cycle based on fixing a referenced operational data snapshot and registering it in an internal cycle log, preventing input changes during execution, preventing overlap of concurrent cycles on the same resources through snapshot and log references, imposing an execution restriction, preventing output before the internal consistency indicators are complete, enforcing rejection rules that include immediate rejection if the reference of an intermediate result deviates or if an attempt is made to pass on an intermediate result not linked to the reference of the current cycle, and preventing the reuse of intermediate results outside of a complete cycle log.so that an equivalent output cannot be generated without re-executing the same cycle with the same snapshot reference and the same operating settings within a complete mandatory execution sequence.

[0022] Explanations of the characters: Fig. Figure 1 shows the general block diagram of the system architecture (100) with the operating units (10-90) that are linked together in a defined execution sequence and together form a multi-stage interlocked execution cycle. Fig. Figure 2 shows the flowchart of the multi-stage interlocked execution cycle, starting with the fixing of an operational data snapshot (20), followed by the normalized transformation (30), the stepwise merging (40), the generation of referenced operational categories (50), the reference matching (60), the sequence-based processing (70), the structural verification (80), and the fixing of the cycle log (90) before output. Fig. Figure 3 shows the mechanics for fixing the operational data snapshot (20) including the generation of a snapshot reference and a cycle identifier, the referential marking of individual elements, and the rejection logic in case of reference deviation during execution. Fig.Figure 4 shows the structure of the cycle protocol (90) with registration of the snapshot reference, the stepwise completeness indicators, the reference matching results and the rejection states, whereby an output is only released after verification of all consistency conditions.

Claims

(Main claim) Data processing system (100) with a stepwise interlocked execution cycle for processing multi-source data on a digital platform, comprising processing and storage means configured for enforcing operational restrictions and for reference-based structural verification during operation, and comprising: (10) a data acquisition unit, (20) a unit for fixing an operational data snapshot, (30) a unit for normalized transformation, (40) a stepwise merging unit for forming a composite operating state, (50) a unit for generating operational categories, (60) a reference matching unit, (70) a sequence-based processing unit within a category, (80) a structural verification unit, and (90) a cycle log and execution state management unit, characterized in that the system (100) is configured such thatthat an execution cycle is performed exclusively on the basis of a fixed operational data snapshot, that a change to the input reference is prevented during the execution cycle, that an overlap of concurrent cycles on shared resources is prevented as a result of different or conflicting references, that the output or reuse of an intermediate result is prevented before the cycle has achieved full internal consistency and a final cycle log has been fixed, and that the use of intermediate results outside the cycle log associated with the operational data snapshot is prevented. System according to claim 1, characterized in that the unit for fixing the operational data snapshot (20) is configured to generate a fixed operational data snapshot which includes exclusively the inputs used within a single execution cycle, to generate an internal snapshot reference and to register this in the cycle log (90), such that the snapshot reference is a mandatory requirement for any subsequent processing within the cycle. System according to claim 2, characterized in that the operational data snapshot is fixed by generating a fixed copy of the inputs required for the cycle and stored in a cycle-specific execution area. System according to claim 2, characterized in that the operational data snapshot is fixed by freezing version identifiers of the contained elements, wherein any subsequent deviation of a version identifier is considered a reference deviation of the cycle. System according to one of claims 2 to 4, characterized in that the snapshot fixing unit (20) generates a snapshot identifier and a cycle identifier and links these to the cycle protocol (90), wherein each element within the snapshot is provided with a reference mark that determines its membership in the cycle and the operational data snapshot, and wherein each element that does not meet these references is rejected by the system. System according to claim 1, characterized in that the unit for normalized transformation (30) is configured to convert raw elements into normalized representations according to specified transformation rules, wherein further processing of raw elements is prevented as long as the normalized transformation is not completed and registered within the snapshot reference. System according to claim 1, characterized in that the stepwise merging unit (40) is configured to form a composite operating state for each entity or processed element exclusively on the basis of standardized representations within the same snapshot reference, and to prevent use outside this reference. System according to claim 1, characterized in that the unit for generating operational categories (50) is configured to generate a referenced operational category for each composite operating state within the current execution cycle and to prevent the use of categories from other cycles. System according to claim 1, characterized in that the reference matching unit (60) is configured to release a reference category only if an associated stepwise completeness indicator is registered in the cycle protocol (90). System according to claim 1, characterized in that the sequence-based processing unit (70) is configured to generate, fix and register internal quantities for sequence formation exclusively within the fixed snapshot reference in the cycle protocol (90). System according to claim 1, characterized in that the system has a reference identification mechanism for intermediate results, wherein each intermediate result is linked to the cycle identifier and the reference of the operational data snapshot, and the transmission of non-reference-compliant intermediate results is prevented. System according to claim 11, characterized in that the structural verification unit (80) is configured to perform a mandatory reference check before each transmission of an intermediate result and to trigger an immediate system rejection in the event of any deviation. System according to claim 12, characterized in that an immediate rejection is also triggered if a required stepwise completeness indicator is missing or an intermediate result is not registered in the cycle log (90) linked to the snapshot reference. System according to claim 12 or 13, characterized in that when a rejection condition occurs, the current execution cycle is terminated and the rejection state and its cause are recorded in the cycle log (90) without affecting other running cycles. System according to claim 1, characterized in that the system has a mechanism for controlling simultaneous execution on shared resources, based on snapshot references and cycle identifiers to prevent an overlap of protocols of different cycles. System according to claim 15, characterized in that an execution restriction is generated which is linked to the cycle identifier and a resource area used, so that a shared use of intermediate results or protocols of different cycles is prevented. System according to claim 16, characterized in that the resource area is divided into sub-areas and the execution restriction is applied to the respective sub-area that corresponds to the data group to be processed. System according to claim 1, characterized in that the cycle log and execution state management unit (90) is configured to register and manage snapshot references, stepwise completeness indicators, rejection rules and execution states of the cycle. System according to claim 18, characterized in that cycle logs are distributed across multiple processing units, while maintaining a uniform snapshot reference and cycle identifier. System according to claim 18, characterized in that the system has a recovery mechanism which enables reactivation of an incomplete cycle from the last registered stepwise completeness state, wherein the reference adjustment is reapplied before continuation. System according to claim 1, characterized in that no output is generated before a final completeness indicator is verified by the structural verification unit (80) and the final cycle protocol is fixed, such that each output is necessarily linked to a referenced cycle protocol.

Images