Cross-system event timing anchoring method based on high precision time reference

Abstract

The application discloses a cross-system event timing anchoring method based on a high-precision time reference, which is realized based on a three-level hierarchical architecture, wherein a high-precision time source is only arranged in a primary reference node; the primary reference node generates a physical time reference through a multi-source time source cluster and synchronizes the physical time reference to a secondary service node; the secondary service node performs clock taming and generates a five-tuple timing anchor point; a three-level access node extracts a semantic-free timing meta-information and initiates a request; the legality of the anchor point is confirmed through threefold verification of a time window, TemporalIndex monotonicity and a digital signature; and timing tracing is realized through chainwise association of a ChainProof field. The timing synchronization error of the application is controlled within a preset threshold, and the application is suitable for scenes such as high-frequency trading in finance, industrial pipeline control and government cross-department cooperation.

Description

Technical Field

[0001] This invention relates to the field of time synchronization and digital infrastructure technology, and specifically to a cross-system event timing anchoring method based on a high-precision time reference. Background Technology

[0002] With the advancement of digitalization, scenarios such as high-frequency financial trading, industrial production control, government collaboration across all sectors, and high-concurrency internet interactions are increasingly demanding consistency in the timing of cross-system events. Existing technical solutions suffer from the following problems: Existing solutions rely on protocols such as NTP and SNTP for time synchronization, with time errors reaching the level of hundreds of milliseconds. This results in insufficient accuracy in scenarios with high timing precision requirements, such as high-frequency trading in finance and industrial assembly line control.

[0003] Existing high-precision time reference solutions require the deployment of high-precision time sources such as atomic clocks at multiple nodes, resulting in high deployment costs and cost constraints for large-scale implementation across the industry.

[0004] Existing time-series identification schemes are tied to business scenarios, and time-series anchors contain business-related information. Cross-industry adaptation and access costs are high, and there are risks to business data privacy.

[0005] Existing solutions often generate time sequence anchors from a single node, lacking an effective time sequence consistency verification mechanism in cross-node scenarios, resulting in insufficient traceability of time sequence links.

[0006] The following terms have the following meanings in this specification: High-precision time reference: A globally unified physical time reference with controllable error generated by multiple time sources (atomic clocks, satellite time synchronization, high-precision network protocols, etc.) and stored in the local memory of the primary reference node, not limited to specific technology implementation.

[0007] TemporalIndex: A globally unique, strictly monotonically increasing integer value generated by the secondary service node processor based on a global high-precision time base. It is used only to identify the relative order of events and is stored in the local memory of the secondary service node.

[0008] TimeWindow: The event occurrence time confidence interval [earliest, latest] calculated based on a high-precision time base, used for time sequence validity verification, and stored in the local memory of the secondary service node.

[0009] TimeAnchorID: A semantically null 5-tuple data structure that carries event timing information. It is generated by the secondary service node processor and contains five fields: TimeAnchorID, TemporalIndex, TimeWindow, NodeFingerprint, and Signature.

[0010] Chained time-series association: The ChainProof field enables subsequent time-series anchors to contain cryptographic hash references of earlier anchors, forming a traceable time-series link.

[0011] Clock discipline algorithm: The algorithm used by the secondary service node processor to synchronize the local clock to the global time base is selected from one of adaptive PLL / FLL hybrid control and Kalman filter clock error estimation and compensation. Summary of the Invention

[0012] The present invention proposes a cross-system event timing anchoring method based on a high-precision time base, which can solve the following technical problems: insufficient cross-system timing anchoring accuracy, coupling of timing anchors with business semantics, high deployment cost of high-precision solutions, and lack of cross-node timing consistency verification, resulting in limited cross-system high consistency collaboration.

[0013] To achieve the above objectives, the present invention adopts the following technical solution: A cross-system event timing anchoring method based on a high-precision time benchmark, the core technical solution of which is as follows: A high-precision time source is centrally deployed only at a primary benchmark node, and time benchmark parameters are distributed to secondary service nodes through a hierarchical synchronization mechanism. The secondary service nodes synchronize to the global benchmark using a clock discipline algorithm. The tertiary access node only extracts semantically meaningless timing metadata to initiate anchoring requests. The secondary service nodes generate five-tuple timing anchors, and the validity of the timing anchors is ensured through a triple mechanism of time window verification, TemporalIndex monotonicity verification, and digital signature. Chain-based timing association enables end-to-end traceability. The method includes the following steps: Implemented based on a three-tiered architecture, the high-precision time source is deployed only on the first-level reference node, while the second-level service nodes and the third-level access nodes do not deploy high-precision time sources; the method includes: A. Time series reference construction process: The primary reference node generates a high-precision physical time reference through a multi-source time source cluster, and uses a time window confidence interval algorithm to fuse the outputs of the multi-source time sources to generate a globally unified physical time reference; the primary reference node sends time reference parameters to the secondary service node through an encrypted channel, and the secondary service node executes a clock discipline algorithm to synchronize its local clock to the global time reference. B. Time Anchor Generation Process: When the event to be anchored is triggered, the Level 3 access node reads the current clock reading from the local clock, reads the node's unique identifier hash value and the local event sequence number from the local memory, generates a time-series metadata triplet that does not contain event business data, and sends a time-series anchoring request containing only the triplet to the Level 2 service node; the Level 2 service node reads the current global time base parameter from the local memory, assigns a monotonically increasing TemporalIndex value to the event, calculates the TimeWindow confidence interval, calculates the TimeAnchorID using a cryptographic hash algorithm, and generates a 5-tuple time-series anchor; the Level 2 service node generates a Signature field using its private key through a digital signature algorithm, and sends the complete 5-tuple time-series anchor to the Level 3 access node through an encrypted channel; the Level 3 access node writes the TimeAnchorID into the local event log storage and stores it in association with the corresponding event. C. Timing Consistency Verification Process: The third-level access node initiating the verification sends the TimeAnchorID to the second-level service node. The second-level service node returns the TemporalIndex, TimeWindow, and Signature fields of the corresponding time anchor point. The third-level access node performs overlap verification on the TimeWindow confidence interval and the current global time base real-time window. It determines the relative order of events by comparing the TemporalIndex values ​​of each anchor point. It performs digital signature verification on the Signature field using the public key of the second-level service node. If all three verifications pass, the anchor point is deemed valid. D. End-to-end time-series tracing process: When a new time-series anchor is generated, the third-level access node reads the TimeAnchorID of the upstream associated event, calculates the ChainProof field value using a cryptographic hash algorithm, and writes it to the current time-series anchor. When initiating tracing, the upstream TimeAnchorID is extracted from the ChainProof field of the target time-series anchor, and the TemporalIndex of each upstream anchor is requested from the second-level service node level by level. The end-to-end time-series order of the events is restored according to the TemporalIndex value order.

[0014] In another aspect, the present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the method described above.

[0015] In another aspect, the present invention also discloses a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method described above.

[0016] As can be seen from the above technical solution, the cross-system event timing anchoring method based on a high-precision time base of the present invention belongs to the fields of distributed systems, time synchronization, and digital infrastructure technology. Addressing the problems of insufficient cross-system time synchronization accuracy, coupling between timing anchors and business semantics, and inability to verify cross-node timing consistency in existing technologies, the present invention proposes the following technical solution: A primary reference node deploys multiple time sources, generates a high-precision physical time base using a time window confidence interval algorithm, stores it in local memory, and sends time base parameters to secondary service nodes through an encrypted channel; the secondary service node processor synchronizes its local clock to the global reference using a clock discipline algorithm; the tertiary access node processor extracts semantically unrelated timing metadata and initiates a timing anchor generation request to the secondary service node; the secondary service node processor generates a five-tuple timing anchor, writes it to local memory, and sends it through an encrypted channel; during verification, the anchor's legality is confirmed through triple verification using time window validity, TemporalIndex monotonicity, and digital signature; timing traceability is achieved through chained association of the ChainProof field. The timing synchronization error of this invention is controlled within a preset threshold, making it suitable for scenarios such as high-frequency financial trading, industrial assembly line control, and cross-departmental government collaboration.

[0017] Specifically, the beneficial effects of the present invention are as follows: (1) High-precision time alignment: The multi-source time source fusion algorithm of the first-level reference node controls the time error within the preset threshold, and the TemporalIndex is globally monotonically increasing to meet the time accuracy requirements of scenarios such as financial high-frequency trading and industrial assembly line control. (2) Reduce deployment costs: High-precision time sources are only centrally deployed at the primary reference nodes, and secondary and tertiary nodes do not need to deploy atomic clocks. A unified time reference is obtained through a hierarchical synchronization mechanism, reducing the overall network deployment cost; (3) Semantic isolation: Each node's network interface only transmits time-series metadata and TimeAnchorID identifiers, and does not transmit business data. The third-level access node only needs to write the TimeAnchorID into the local log storage, without modifying the core logic of the business system. (4) Triple security verification: Time window validity verification, TemporalIndex monotonicity verification, and SM2 digital signature verification provide triple protection against time sequence forgery, tampering, and rollback attacks; (5) End-to-end time-series tracing: The ChainProof chain-linked structure supports tracing back to the source of an event from any anchor point, meeting the needs of reconciliation audit, responsibility division, and compliance supervision; (6) Adaptation to weak network scenarios: The local caching mechanism of the three-level access node ensures that the event timing metadata is not lost during network interruption, and incremental synchronization is completed after the network is restored; (7) Compatible with event anchoring system: TimeAnchorID can be used as one of the inputs of AnchorID to form a technical closed loop between time anchoring layer and event anchoring layer. Attached Figure Description

[0018] Figure 1 This is a flowchart of the present invention; Figure 2 This is a flowchart of the timing reference construction and hierarchical synchronization process of this invention; Figure 3 This is a flowchart of the timing anchor point generation process of the present invention; Figure 4 This is a flowchart of the triple timing consistency check of the present invention; Figure 5 This is a schematic diagram of the full-link time-series chain-like association structure of the present invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are some embodiments of the present invention, but not all embodiments.

[0020] like Figure 1 As shown in the figure, the cross-system event timing anchoring method based on a high-precision time base described in this embodiment includes the following steps: Implemented based on a three-tiered architecture, the high-precision time source is deployed only on the first-level reference node, while the second-level service nodes and the third-level access nodes do not deploy high-precision time sources; the method includes: A. Time series reference construction process: The primary reference node generates a high-precision physical time reference through a multi-source time source cluster, and uses a time window confidence interval algorithm to fuse the outputs of the multi-source time sources to generate a globally unified physical time reference; the primary reference node sends time reference parameters to the secondary service node through an encrypted channel, and the secondary service node executes a clock discipline algorithm to synchronize its local clock to the global time reference. B. Time Anchor Generation Process: When the event to be anchored is triggered, the Level 3 access node reads the current clock reading from the local clock, reads the node's unique identifier hash value and the local event sequence number from the local memory, generates a time-series metadata triplet that does not contain event business data, and sends a time-series anchoring request containing only the triplet to the Level 2 service node; the Level 2 service node reads the current global time base parameter from the local memory, assigns a monotonically increasing TemporalIndex value to the event, calculates the TimeWindow confidence interval, calculates the TimeAnchorID using a cryptographic hash algorithm, and generates a 5-tuple time-series anchor; the Level 2 service node generates a Signature field using its private key through a digital signature algorithm, and sends the complete 5-tuple time-series anchor to the Level 3 access node through an encrypted channel; the Level 3 access node writes the TimeAnchorID into the local event log storage and stores it in association with the corresponding event. C. Timing Consistency Verification Process: The third-level access node initiating the verification sends the TimeAnchorID to the second-level service node. The second-level service node returns the TemporalIndex, TimeWindow, and Signature fields of the corresponding time anchor point. The third-level access node performs overlap verification on the TimeWindow confidence interval and the current global time base real-time window. It determines the relative order of events by comparing the TemporalIndex values ​​of each anchor point. It performs digital signature verification on the Signature field using the public key of the second-level service node. If all three verifications pass, the anchor point is deemed valid. D. End-to-end time-series tracing process: When a new time-series anchor is generated, the third-level access node reads the TimeAnchorID of the upstream associated event, calculates the ChainProof field value using a cryptographic hash algorithm, and writes it to the current time-series anchor. When initiating tracing, the upstream TimeAnchorID is extracted from the ChainProof field of the target time-series anchor, and the TemporalIndex of each upstream anchor is requested from the second-level service node level by level. The end-to-end time-series order of the events is restored according to the TemporalIndex value order.

[0021] The following is a detailed explanation: An embodiment of the present invention provides a cross-system event timing anchoring method based on a high-precision time base, implemented using a three-level layered architecture. The high-precision time source is deployed only on the first-level reference node, while the second-level service nodes and the third-level access nodes do not deploy high-precision time sources. The method includes the following four steps: A. Timing baseline construction process: A1 Multi-source time source deployment: The multi-source time source cluster of the primary reference node generates a high-precision physical time reference. The multi-source time sources are selected from one or more of the following groups: atomic clock cluster, global satellite navigation system timing module, network-based high-precision time synchronization protocol combined with hardware timestamp; the primary reference node processor fuses the outputs of the multi-source time sources through the time window confidence interval algorithm to generate a globally unified physical time reference, and writes the time window parameters into the local memory of the primary reference node. The upper limit of the time error is a preset threshold. A2 Reference Parameter Hierarchical Synchronization: The primary reference node processor sends time reference parameters to the secondary service node through an encrypted channel. The time reference parameters include the time window confidence interval, the time source drift compensation coefficient, and the reference update period. After receiving the above parameters, the secondary service node processor executes a clock discipline algorithm selected from the group consisting of adaptive phase-locked loop and frequency-locked loop hybrid control and clock error estimation and compensation based on Kalman filtering to synchronize the local clock to the global time reference. The synchronization result is written to the local memory of the secondary service node. A3 Reference Dynamic Calibration: The secondary service node processor monitors the deviation between the local clock and the global reference in real time, and periodically reports the clock drift data to the primary reference node through an encrypted channel; the primary reference node processor dynamically adjusts the drift compensation coefficient based on the drift data, and sends the updated compensation coefficient to each secondary service node processor through an encrypted channel and writes it into the local memory of the secondary service node. like Figure 1 As shown in the overall flowchart and Figure 2 As shown in the flowchart (time series reference construction and hierarchical synchronization), steps A1-A3 together constitute the time series reference construction process, in which... Figure 1 This demonstrates the overall data flow of the three-tiered architecture. Figure 2 It details the complete closed loop from multi-source time source fusion at the primary reference node, to clock discipline and synchronization at the secondary service node, and then to dynamic calibration feedback.

[0022] Figure 1 Process A continuously runs and maintains the timing baseline; Process B executes each time an event occurs; Process C executes each time a verification is performed; Process D executes each time a trace is performed. Throughout the entire process, the network interfaces of each node only transmit timing metadata and TimeAnchordD, and do not transmit business data.

[0023] Figure 2 The core constraints of the architecture include: 1) High-precision time sources are deployed only at the primary reference node; atomic clocks and other high-precision time sources are not deployed at the secondary and tertiary nodes. 2) Second-level nodes synchronize to the global baseline through a clock discipline algorithm, and third-level nodes obtain unified timing information from the second-level nodes; 3) In the extended networking mode, secondary nodes can selectively deploy backup time sources, which are only used for fault redundancy and do not participate in the generation of global baselines.

[0024] B. Timing Anchor Point Generation Process: B1 Time Series Meta Information Extraction: When the anchoring event is triggered, the Level 3 access node processor reads the current clock reading from the local clock, reads the node's unique identifier hash value and the local event sequence number from the local memory, generates a time series meta information triplet, and writes it to the Level 3 access node's local cache; the time series meta information does not contain event service data. B2 Time Anchor Construction: The Level 3 access node processor sends a time anchoring request to the nearest Level 2 service node through the network interface. The request only contains a triplet of time meta information. The Level 2 service node processor reads the current global time base parameters from the local memory, assigns a monotonically increasing TemporalIndex value to the event, calculates the TimeWindow confidence interval [earliest, latest], calculates the TimeAnchorID through a cryptographic hash algorithm, generates a quintuple time anchor, and writes it to the local memory of the Level 2 service node. B3 Anchor Secure Distribution: The secondary service node processor uses its private key to generate a Signature field from the core fields of the time-series anchor using the SM2 digital signature algorithm. It then distributes the complete five-tuple time-series anchor to the tertiary access node processor via a point-to-point encrypted channel. The tertiary access node processor writes the TimeAnchorID to its local event log storage and stores it in association with the corresponding event. like Figure 3 As shown in the flowchart for generating time-series anchors, steps B1-B3 together constitute the time-series anchor generation process. Figure 1 This demonstrates the request-response relationship between the third-level access node and the second-level service node. Figure 3 It details the complete processing logic from extracting time-series metadata, generating quintuples, to encrypted distribution.

[0025] Figure 3 middle, 1) The time-series metadata does not contain any business data; 2) The SM2 private key is stored in the hardware security module of the secondary node; 3) In batch mode, third-level nodes can submit multiple event anchoring requests at once, and second-level nodes can generate and package them in batches and distribute them.

[0026] C. Timing consistency verification process: C1 Verification Parameter Acquisition: The third-level access node processor that initiates the verification sends the TimeAnchorID to the second-level service node through the network interface. The second-level service node processor reads the three verification fields TemporalIndex, TimeWindow, and Signature of the corresponding time anchor point from the local memory and returns them to the initiating processor through the network interface. C2 Time Window Validity Verification: The Level 3 Access Node processor extracts the TimeWindow confidence interval [earliest, latest] and performs overlap verification with the real-time window of the current global time base obtained from the Level 2 Service Node; if the two windows have valid overlap, the verification pass result is written; otherwise, the invalid anchor point result is written. C3 Timing Sequence Verification: The Level 3 access node processor determines the relative order of events by comparing the TemporalIndex values ​​of multiple timing anchors for the same event link. The anchor with the larger TemporalIndex value corresponds to the event that occurred later. The verification result is written to the local memory. C4 Signature Integrity Verification: The Level 3 Access Node Processor reads the Level 2 Service Node Public Key from the local storage and performs SM2 signature verification on the Signature field of the time-series anchor. If the signature verification passes and the C2 time window verification passes, the processor determines that the anchor is valid and writes it into the verification result storage. like Figure 4 As shown, steps C1-C4 together constitute the timing consistency verification process, wherein... Figure 1 This demonstrates the position of the verification process within the overall architecture. Figure 4 The parallel processing logic and decision path of triple verification (time window verification, TemporalIndex monotonicity verification, and SM2 digital signature verification) are shown in detail.

[0027] Figure 4 The three checks are executed sequentially; if any one fails, the anchor point is deemed invalid. Only if all three checks pass is the anchor point deemed valid. C2 prevents timing forgery and rollback attacks; C4 prevents anchor point tampering.

[0028] D. End-to-end time-series tracing process: D1 Chained Time-Sequence Association: When generating a new time-sequence anchor, the third-level access node processor reads the TimeAnchorID of the upstream associated event from the local memory, calculates the ChainProof field value through a cryptographic hash algorithm, writes it into the ChainProof field of the current time-sequence anchor, and stores it in the local memory. D2 Time-series link tracing: The processor that initiates the tracing extracts the upstream TimeAnchorID from the ChainProof field of the target time-series anchor point, requests the TemporalIndex of each upstream anchor point from the secondary service node through the network interface, restores the full-link time sequence of events according to the TemporalIndex value order, and writes the tracing result to the local memory. D3 Distributed Time Series Summary Synchronization: The secondary service node processor periodically synchronizes the TemporalIndex and TimeWindow summary of the time series anchor point to other secondary service node processors through a Merkle tree structure to calculate the summary root, and writes it to the local memory of each node in batches via the network interface, without the need for full anchor point data to be broadcast across nodes.

[0029] like Figure 5 As shown in the diagram (a schematic diagram of the end-to-end time-series chain structure), the above steps D1-D3 together constitute the end-to-end time-series tracing process, in which... Figure 1 This demonstrates the data flow in the traceability process. Figure 5 It details the chain-like association structure of the preceding and following anchor hash pointers formed by the ChainProof field, as well as the tracing path from the target anchor back to the source anchor.

[0030] Figure 5 Explanation: 1) ChainProof=H(Current anchor core field II upstream TimeAnchorlD), the symbol = indicates byte string concatenation; 2) Each anchor point is stored in the local memory of the corresponding node; the tracing process requests the Temporalindex from the secondary nodes level by level through the network interface, without obtaining business data.

[0031] Specifically, in step A1, the multi-source time source cluster adopts one or more of the following architectures: dual redundancy of local atomic clock and off-site backup atomic clock; hybrid redundancy of atomic clock and global satellite navigation system timing module; and combined redundancy of high-precision PTP time source and atomic clock.

[0032] In step B2, the five-tuple time-series anchor structure is <TimeAnchorID, TemporalIndex, TimeWindow, NodeFingerprint, Signature>, and each field is generated by the secondary service node processor and written to local memory, specifically: The TimeAnchorID field is a globally unique identifier calculated by a cryptographic hash algorithm after concatenating TemporalIndex, TimeWindow, NodeFingerprint and a random salt value. It is stored in the local storage of the secondary service node. TemporalIndex field: A monotonically increasing integer value generated based on a global high-precision time base. The processor increments this value by 1 for each time a time anchor point is generated. It is used only to identify the relative order of events and is stored in the local memory of the secondary service node. The TimeWindow field is the event occurrence time confidence interval [earliest, latest] calculated based on a high-precision time base. The window width is dynamically adjusted by the processor according to the current clock precision and stored in the local memory of the secondary service node. The NodeFingerprint field is an irreversible hash fingerprint obtained by cryptographic hashing the public key of the third-level access node and stored in the local storage of the second-level service node. Signature field: The secondary service node processor generates a digital signature for the first four fields using the SM2 digital signature algorithm with its own private key, and stores it in the local memory of the secondary service node.

[0033] The quintuple time-series anchor structure adopts a functionally equivalent data structure containing the above five fields, including either merging multiple fields into a single composite field or splitting a field into multiple subfields; the cryptographic hash algorithm is selected from one of the groups consisting of the SM3 national cryptographic hash algorithm and the SHA-256 algorithm.

[0034] In step C3, the timing sequence verification supports cross-secondary node scenarios: different secondary service node processors generate TemporalIndex based on the same global time base parameter. The processors compare the anchor point TemporalIndex values ​​generated by different nodes to achieve unified determination of event timing sequence across regions and nodes, and the determination result is written to local memory.

[0035] In step D1, the ChainProof field is generated by the processor by concatenating the core field of the current time-series anchor point with the upstream TimeAnchorID, and then using a cryptographic structure selected from the group consisting of Merkle hash digest structure, hash pointer linked list structure, and accumulator aggregation verification structure, and is written into the current anchor point storage record.

[0036] In step B3, the timing anchor point distribution supports batch mode: the third-level access node processor submits the timing metadata of multiple events at once through the network interface, the second-level service node processor generates the corresponding timing anchor points in batches, packages them, and distributes them to the third-level access node processor at once through an encrypted channel, and writes them to the local event log storage.

[0037] In step C, the timing consistency verification supports an offline batch verification mode: the third-level access node processor writes the batch TimeAnchorID list into the local cache, submits it to the second-level service node processor in batches through the network interface, the second-level service node processor completes the three verifications in batches and returns the result list, which is then written to the local storage of the third-level access node.

[0038] In step A, the primary reference node adopts a multi-node off-site disaster recovery deployment, and multiple primary reference node processors execute consensus algorithms to synchronize time reference parameters through network interfaces; the secondary service node processors are of equal status, and the tertiary access node processors can freely select and switch secondary service nodes through network interfaces.

[0039] In this embodiment, an extended networking mode is also included: secondary service nodes can selectively deploy time sources, and the secondary node time sources do not participate in the generation of the global time series reference; when the communication between the secondary service node and the primary reference node is interrupted, the processor of the secondary service node switches to the local time source to maintain the time series anchor point generation service; after the communication is restored, the processor maps the local time series during the interruption back to the global time reference and updates and writes it to the local memory.

[0040] It also includes weak network fault tolerance processing: when the processor of the third-level access node detects a network interruption with the second-level service node, the processor writes the timing metadata of the event to be anchored into the local cache in the local timing order; after the network is restored, the processor uploads the timing metadata in the cache in batches through the network interface, the processor of the second-level service node allocates a global TemporalIndex for it and returns the complete timing anchor point, which is then written into the local event log storage of the third-level access node.

[0041] The time-series anchor ID (TimeAnchorID) and the event anchor ID (AnchorID) establish a compatible relationship: the third-level access node processor uses TimeAnchorID as one of the inputs to generate AnchorID, or implements a bidirectional mapping between TimeAnchorID and AnchorID through the neutral adaptation layer processor, and the mapping relationship is written into the local memory of the adaptation layer.

[0042] The method is applicable to scenarios such as high-frequency financial trading timing anchoring, industrial production line control timing synchronization, cross-departmental government collaborative event anchoring, high-concurrency Internet event processing, IoT terminal interaction, and multi-agent collaboration. In each scenario, the three-level access node processor only needs to write the TimeAnchorID to the local event log storage without modifying the core logic of the business system.

[0043] In this specification, both "time anchor" and "TimeAnchorID" refer to the 5-tuple data structure and its unique identifier. The symbol ∥ indicates a byte string concatenation operation. Local memory includes node-local storage devices such as RAM, Flash memory, and database storage media.

[0044] The following are examples: Example 1: High-Frequency Financial Trading Scenario The primary reference node deploys three off-site rubidium atomic clocks and a BeiDou GNSS timing module, forming a triple redundant time source.

[0045] A1: The primary reference node processor fuses the outputs of three time sources through a time window confidence interval algorithm to generate a global high-precision time reference with a time error controlled within 7ms, and writes the time window parameters into local memory.

[0046] A2: The primary reference node processor sends time reference parameters to 10 provincial secondary service nodes across the country via an encrypted dedicated line; each provincial secondary service node processor executes an adaptive PLL+FLL hybrid clock discipline algorithm to synchronize the local clock to the global reference, with a synchronization error of no more than 4ms, and writes it to the local memory; the secondary nodes do not deploy atomic clocks.

[0047] A3: Each secondary service node processor monitors the clock deviation in real time and reports drift data every 10 seconds via an encrypted dedicated line; the primary reference node processor dynamically adjusts the drift compensation coefficient and distributes it.

[0048] B1: After the high-frequency trading system's level 3 access node processor completes the transaction matching, it reads the current reading from the local clock, reads the node identifier hash value (256 bits) and the transaction sequence number from the local memory, generates a time-series metadata triplet, and writes it to the local cache.

[0049] B2: The Level 3 access node processor sends a timing anchoring request to the East China Level 2 service node through the network interface; the Level 2 service node processor reads the current global time base parameters, allocates the TemporalIndex value (set to 10000001), calculates the TimeWindow as [1699999990000, 1699999990007] (unit: milliseconds), executes TimeAnchorID =SM3(10000001∥[1699999990000,1699999990007]∥NodeFingerprint∥random salt value), and generates a quintuple timing anchor point which is written to the local memory.

[0050] B3: The secondary service node processor uses the node's private key to execute SM2 (the first four fields) to generate the Signature field, and distributes the complete quintuple through the TLS encrypted channel; the tertiary access node processor writes the TimeAnchorID into the local transaction log storage.

[0051] C: The processor of the tertiary access node of the clearing institution submits the TimeAnchorID through the network interface, and obtains three verification fields, namely TemporalIndex (10000001), TimeWindow and Signature, from the secondary service node; the processor verifies that the TimeWindow has a valid overlap with the current global reference window; verifies the validity of the SM2 signature through the public key of the secondary node; determines the transaction matching order through TemporalIndex (10000001 <1000000>2 < …); and writes the triple verification result into the local storage.

[0052] D: The processor of the regulatory authority extracts the TimeAnchorIDs of the order submission, fund freezing and risk control review links step by step from the ChainProof field through the TimeAnchorID of the target transaction, restores the full-link time sequence in the order of TemporalIndex, and writes it into the trace result storage; no business data such as transaction amount and user information is obtained throughout the whole process.

[0053] Embodiment 2: Industrial production pipeline control scenario The primary reference node at the headquarters of the automotive group is deployed with 2 local rubidium atomic clocks and 1 remote backup atomic clock, and is connected to GNSS timing for backup.

[0054] A1-A3: The processor of the primary reference node generates a unified high-precision time reference for the whole plant, with the time error controlled within 5ms; distributes the time reference parameters to the secondary service nodes of 8 production bases through the industrial private line, and the processor of each secondary service node completes clock synchronization, with the error from the global reference not exceeding 3ms, and writes the result into the local storage; neither the secondary nodes nor the production line terminals are deployed with atomic clocks.

[0055] B: When the processor of the tertiary access node of the pipeline control system issues a welding instruction to the robotic arm, it extracts the local clock reading, node hash, and instruction sequence number, and initiates a time anchoring request to the secondary service node of the production line; the processor of the secondary service node generates the TimeAnchorID and the monotonically increasing TemporalIndex, and distributes them through the encrypted channel; the processor of the control system writes the TimeAnchorID into the instruction log storage, and does not transmit business data such as welding parameters.

[0056] C: The quality inspection system processor obtains the verification field from the secondary service node through TimeAnchorID and performs triple verification; it determines the relative order of instruction issuance, robotic arm execution, and quality inspection through TemporalIndex, and writes the verification result to local memory.

[0057] D: When a batch of finished products has a quality problem, the processor traces the TimeAnchorID of the welding, painting, assembly and material delivery stages step by step from the ChainProof field of the TimeAnchorID of the finished product inspection. It restores the execution order of each process according to the TemporalIndex order and writes it into the traceability result storage. The traceability process does not obtain business data such as welding parameters and process formulas.

[0058] Example 3: Cross-departmental government collaboration scenario The provincial government cloud deploys a multi-source rubidium atomic clock cluster at the primary reference node, with time error controlled within 9ms. Reference parameters are distributed to 64 secondary government service nodes in various cities and counties through an encrypted dedicated line on the government intranet. The processors of the secondary nodes complete clock synchronization, with an error of no more than 5ms from the global reference. The atomic clock is deployed only at the primary node throughout the entire process.

[0059] B: After the market supervision department's third-level access node processor completes the acceptance of the enterprise establishment application, it initiates a time-series anchoring request to the local second-level service node to obtain the TimeAnchorID and write it into the acceptance log storage; it only transmits the TimeAnchorID to the tax, social security, and public security departments, and does not transmit the enterprise's confidential application materials.

[0060] C: The tax department processor initiates a triple verification to the local secondary service node through TimeAnchorID to confirm the validity of the time sequence of the accepted event. After the verification is successful, the subsequent processing procedure is started.

[0061] D: The government audit department processor uses the TimeAnchorID chain structure to restore the processing time sequence of each department, verify the compliance of time limits, and trace the process without obtaining confidential information of enterprises.

[0062] Example 4: Extended Networking Mode Scenario A national-level data center adopts an extended networking mode, deploying backup atomic clocks at secondary service nodes in three core regions: East China, North China, and South China.

[0063] During normal operation, the secondary node processor only synchronizes the time base of the primary node, while the backup atomic clock is in standby mode and does not participate in the generation of the global time base.

[0064] When the communication link between the primary node and the secondary node is interrupted, the secondary node processor switches to the local backup atomic clock to continue providing time-series anchor point generation services for the tertiary access node, and TimeAnchorID is written to the local memory.

[0065] After the link is restored, the secondary node processor resynchronizes the primary node time base, maps the local timing during the interruption back to the global time base, and updates and writes it to the local memory.

[0066] Example 5: TimeAnchorID and AnchorID Collaboration Scenarios A large financial institution uses TimeAnchorID for time-series alignment between its internal systems. In external clearing scenarios, the Level 3 access node processor takes TimeAnchorID as input, executes AnchorID = SM3(TimeAnchorID∥TemporalIndex∥NodeFingerprint), generates AnchorID, and writes it to local storage. The neutral adaptation layer processor maintains a bidirectional mapping table between TimeAnchorID and AnchorID, writes it to the adaptation layer's local storage, and allows internal and external scenarios to query it as needed.

[0067] In another aspect, the present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the method described above.

[0068] In another aspect, the present invention also discloses a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method described above.

[0069] It is understood that the systems, devices, and storage media provided in the embodiments of the present invention correspond to the methods provided in the embodiments of the present invention, and the explanations, examples, and beneficial effects of the relevant content can be referred to the corresponding parts of the above methods.

[0070] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. 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 integrates one or more 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 (e.g., solid-state disk (SSD)).

[0071] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0072] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0073] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for cross-system event timing anchoring based on a high-precision time base, characterized in that: include, A. Time reference construction: The primary reference node generates a global physical time reference through a multi-source time source cluster and distributes it to the secondary service node through an encrypted channel. The secondary service node executes a clock discipline algorithm to synchronize its local clock. B. Time Anchor Generation: The third-level access node extracts time-series metadata that does not contain business data and sends a request to the second-level service node. The second-level service node generates a time-series anchor based on the time-series benchmark, which consists of five fields: Time Anchor ID, Temporal Index, Time Window, Node Fingerprint, and Signature. The anchor is then sent out through an encrypted channel. C. Timing Consistency Verification: The third-level access node that initiates the verification sends the timing anchor ID TimeAnchorID to the second-level service node. The second-level service node returns the corresponding timing index value, time window, and digital signature. The third-level access node that initiates the verification confirms the legality of the anchor point through triple verification of time window validity, timing index value monotonicity comparison, and digital signature verification. D. End-to-end time-series tracing: The third-level access node that initiates the tracing requests the time-series index values ​​of each upstream anchor point from the second-level service node through the chain association of the chained verification fields, thereby realizing the step-by-step tracing from the target anchor point to the source. High-precision time sources are deployed only on the primary reference nodes, while they are not deployed on the secondary service nodes and the tertiary access nodes.

2. The method for cross-system event timing anchoring based on a high-precision time base according to claim 1, characterized in that, Step A includes, A1 Multi-Source Time Source Deployment: The multi-source time source cluster of the primary reference node generates a high-precision physical time reference. The multi-source time source is selected from one or more of the following groups: atomic clock cluster, global satellite navigation system timing module, network-based high-precision time synchronization protocol combined with hardware timestamp; The primary reference node processor fuses the outputs of multiple time sources through the time window confidence interval algorithm to generate a globally unified physical time reference. The time window parameters are written into the local memory of the primary reference node, and the upper limit of the time error is a preset threshold. A2 Baseline Parameter Hierarchical Synchronization: The primary baseline node processor sends time baseline parameters to the secondary service node through an encrypted channel. The time baseline parameters include the time window confidence interval, the time source drift compensation coefficient, and the baseline update cycle. After receiving the above parameters, the secondary service node processor executes a clock discipline algorithm selected from the group consisting of adaptive phase-locked loop and frequency-locked loop hybrid control and clock error estimation and compensation based on Kalman filtering, to synchronize the local clock to the global time base, and writes the synchronization result to the local memory of the secondary service node. A3 reference dynamic calibration: The secondary service node processor monitors the deviation between the local clock and the global reference in real time, and periodically reports the clock drift data to the primary reference node through an encrypted channel; The primary reference node processor dynamically adjusts the drift compensation coefficient based on the drift data, and sends the updated compensation coefficient to each secondary service node processor through an encrypted channel, writing it into the local memory of the secondary service node.

3. The method for cross-system event timing anchoring based on a high-precision time base according to claim 2, characterized in that, Step B includes, B1 Timing Meta-information Extraction: When the anchoring event is triggered, the Level 3 Access Node processor reads the current clock reading from the local clock, reads the node's unique identifier hash value and the local event sequence number from the local memory, generates a timing meta-information triplet, and writes it to the Level 3 Access Node's local cache. The time-series metadata does not include event service data; B2 Time Anchor Construction: The Level 3 access node processor sends a time anchoring request to the nearest Level 2 service node through the network interface. The request only contains a triplet of time meta information. The Level 2 service node processor reads the current global time base parameters from the local memory, assigns a monotonically increasing TemporalIndex value to the event, calculates the TimeWindow confidence interval [earliest, latest], calculates the TimeAnchorID through a cryptographic hash algorithm, generates a quintuple time anchor, and writes it to the local memory of the Level 2 service node. B3 Secure Distribution of Time Anchor Points: The secondary service node processor uses its own private key to generate a Signature field from the core field of the time anchor point using the SM2 digital signature algorithm, and distributes the complete five-tuple time anchor point to the tertiary access node processor through a point-to-point encrypted channel. The Level 3 access node processor writes the TimeAnchorID to the local event log storage and stores it in association with the corresponding event.

4. The cross-system event timing anchoring method based on a high-precision time base according to claim 3, characterized in that, Step C includes, C1 verification parameter acquisition: The third-level access node processor that initiates the verification sends TimeAnchorID to the second-level service node through the network interface. The second-level service node processor reads the three verification fields TemporalIndex, TimeWindow and Signature of the corresponding time anchor point from the local memory and returns them to the initiating processor through the network interface. C2 Time Window Validity Verification: The Level 3 access node processor that initiates the verification extracts the TimeWindow confidence interval [earliest, latest] and performs overlap verification with the real-time window of the current global time reference obtained from the Level 2 service node; If the two windows have valid overlap, write the verification result; otherwise, write the invalid anchor point result. C3 Timing Sequence Verification: The Level 3 access node processor that initiates the verification determines the relative order of events by comparing the TemporalIndex values ​​of multiple timing anchors in the same event link. The anchor with the larger TemporalIndex value corresponds to the event that occurred later. The verification result is written to the local memory. C4 Signature Integrity Verification: The third-level access node processor that initiates the verification reads the public key of the second-level service node from the local storage and performs SM2 signature verification on the Signature field of the time-series anchor. If the signature verification is successful and the C2 time window verification is successful, the processor determines that the anchor is valid and writes it into the verification result storage.

5. The cross-system event timing anchoring method based on a high-precision time base according to claim 4, characterized in that, D includes, D1 Chained Time-Sequence Association: When generating a new time-sequence anchor, the third-level access node processor reads the TimeAnchorID of the upstream associated event from the local memory, calculates the ChainProof field value through a cryptographic hash algorithm, writes it into the ChainProof field of the current time-sequence anchor, and stores it in the local memory. D2 Time-Series Link Tracing: The third-level access node processor that initiates the tracing extracts the upstream TimeAnchorID from the ChainProof field of the target time-series anchor point, requests the TemporalIndex of each upstream anchor point from the second-level service node through the network interface, restores the full-link time sequence of the event according to the TemporalIndex value order, and writes the tracing result into the local memory. D3 Distributed Time Series Digest Synchronization: The secondary service node processor periodically calculates the digest root of the TemporalIndex and TimeWindow of the time series anchor point through a Merkle tree structure, and synchronizes it in batches to other secondary service node processors through the network interface, and writes it to the local memory of each node, without the need for full anchor point data to be broadcast across nodes.

6. The method for cross-system event timing anchoring based on a high-precision time base according to claim 2, characterized in that, In step A1, the multi-source time source cluster adopts one or more of the following architectures: dual redundancy of local atomic clock and off-site backup atomic clock, hybrid redundancy of atomic clock and global satellite navigation system timing module, and combined redundancy of high-precision PTP time source and atomic clock.

7. The cross-system event timing anchoring method based on a high-precision time base according to claim 3, characterized in that, In step B2, the five-tuple time-series anchor structure consists of TimeAnchorID, TemporalIndex, TimeWindow, NodeFingerprint, and Signature. Each field is generated by the secondary service node processor and written to local memory, specifically as follows: The TimeAnchorID field is a globally unique identifier calculated by a cryptographic hash algorithm after concatenating TemporalIndex, TimeWindow, NodeFingerprint and a random salt value. It is stored in the local storage of the secondary service node. TemporalIndex field: A monotonically increasing integer value generated based on a global high-precision time base. The processor increments this value by 1 for each time a time anchor point is generated. It is used only to identify the relative order of events and is stored in the local memory of the secondary service node. The TimeWindow field is the event occurrence time confidence interval [earliest, latest] calculated based on a high-precision time base. The window width is dynamically adjusted by the processor according to the current clock precision and stored in the local memory of the secondary service node. The NodeFingerprint field is an irreversible hash fingerprint obtained by cryptographic hashing the public key of the third-level access node and stored in the local storage of the second-level service node. Signature field: The secondary service node processor generates a digital signature for the first four fields using the SM2 digital signature algorithm with its own private key, and stores it in the local memory of the secondary service node.

8. The method for cross-system event timing anchoring based on a high-precision time base according to claim 7, characterized in that, The five-tuple time-series anchor structure adopts a functionally equivalent data structure containing the above five fields, namely the TimeAnchorID field, TemporalIndex field, TimeWindow field, NodeFingerprint field, and Signature field, including one of merging multiple fields into a single composite field or splitting a field into multiple subfields; the cryptographic hash algorithm is selected from one of the groups consisting of the SM3 national cryptographic hash algorithm and the SHA-256 algorithm.

9. The cross-system event timing anchoring method based on a high-precision time base according to claim 4, characterized in that, In step C3, the timing sequence verification supports cross-secondary node scenarios: different secondary service node processors generate TemporalIndex based on the same global time base parameter. The processors compare the anchor point TemporalIndex values ​​generated by different nodes to achieve unified determination of event timing sequence across regions and nodes, and the determination result is written to local memory.

10. The cross-system event timing anchoring method based on a high-precision time base according to claim 5, characterized in that, In step D1, the ChainProof field is generated by the processor by concatenating the core field of the current time-series anchor point with the upstream TimeAnchorID, and then using a cryptographic structure selected from the group consisting of Merkle hash digest structure, hash pointer linked list structure, and accumulator aggregation verification structure, and is written into the current anchor point storage record.

11. The cross-system event timing anchoring method based on a high-precision time base according to claim 3, characterized in that, In step B3, the timing anchor point distribution supports batch mode: the third-level access node processor submits the timing metadata of multiple events at once through the network interface, the second-level service node processor generates the corresponding timing anchor points in batches, packages them and distributes them to the third-level access node processor at once through an encrypted channel, and writes them to the local event log storage.

12. The cross-system event timing anchoring method based on a high-precision time base according to claim 1, characterized in that, In step C, the timing consistency verification supports an offline batch verification mode: the third-level access node processor writes the batch TimeAnchorID list into the local cache, submits it to the second-level service node processor in batches through the network interface, the second-level service node processor completes the three verifications in batches and returns the result list, which is then written to the local storage of the third-level access node.

13. The cross-system event timing anchoring method based on a high-precision time base according to claim 1, characterized in that, In step A, the primary reference node adopts a multi-node off-site disaster recovery deployment, and multiple primary reference node processors execute a consensus algorithm through a network interface to synchronize time reference parameters. The secondary service node processors are of equal status, and the tertiary access node processors can freely select and switch secondary service nodes through the network interface.

14. The method for cross-system event timing anchoring based on a high-precision time base according to claim 1, characterized in that, It also includes extended networking modes: Secondary service nodes can selectively deploy backup time sources. These backup time sources do not participate in the generation of the global time series benchmark and are redundant time sources independent of the high-precision time source. When communication between the secondary service node and the primary baseline node is interrupted, the processor of the secondary service node switches to the local backup time source to maintain the time sequence anchor point generation service. Once communication is restored, the processor maps the local timing data from the interrupt period back to the global time base and updates it in local memory.

15. The cross-system event timing anchoring method based on a high-precision time base according to claim 1, characterized in that, It also includes fault tolerance processing for weak networks: When the Level 3 access node processor detects a network interruption with the Level 2 service node, the processor writes the timing metadata of the events to be anchored into the local cache in local timing order. After the network is restored, the processor uploads the timing metadata in the cache in batches through the network interface. The Level 2 service node processor allocates a global TemporalIndex for it and returns the complete timing anchor point, which is then written into the Level 3 access node's local event log storage.

16. The cross-system event timing anchoring method based on a high-precision time base according to claim 1, characterized in that, The time-series anchor ID (TimeAnchorID) of the time-series anchor is compatible with the anchor ID (AnchorID) of the event-existence anchor: the third-level access node processor uses the time-series anchor ID (TimeAnchorID) as one of the inputs to generate the anchor ID (AnchorID) of the event-existence anchor, or implements a bidirectional mapping between the time-series anchor ID (TimeAnchorID) and the anchor ID (AnchorID) through the neutral adaptation layer processor, and the mapping relationship is written to the local memory of the adaptation layer.

Images