Digital phased array antenna synchronization method and device

By inserting synchronization anchor frames into the digital phased array antenna system and performing error detection code verification, the alignment offset and steady-state length are calculated, solving the phase inconsistency problem caused by changes in the calibration synchronization information and the service data path, and achieving the stability and reliability of alignment.

CN121814281AInactive Publication Date: 2026-04-07SHAANXI SHENGSHI QIANYUAN TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610019694.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-01-08
Publication Date
2026-04-07
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In digital phased array antenna systems, changes in the path and state of calibration synchronization information and actual service data can lead to phase inconsistencies between subarrays, resulting in unstable beamforming that is difficult to detect and locate.

Method used

By inserting the first and second synchronization anchor frames at the sending end, carrying the alignment epoch identifier and the sending sampling counter count value, and verifying the error detection code at the receiving end, calculating the alignment offset and the forward anchor step steady-state length, generating an alignment proof message, and checking the sending buffer record table, the alignment trust level update and resynchronization request are realized.

Benefits of technology

Ensure that alignment offsets are traceable and verifiable, reduce the risk of misjudgment, improve the reliability of alignment updates, achieve a collaborative closed loop of alignment establishment, alignment activation and alignment maintenance, and reduce invalid switching and long-term drift.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121814281A_ABST
    Figure CN121814281A_ABST
Patent Text Reader

Abstract

The invention discloses a digital phased-array antenna synchronization method and device, particularly relates to the field of digital communication, and is used for solving the problem that framing boundaries and time identifier mapping of service data streams are difficult to stably align under the conditions of cache jitter and clock micro-drift. The sending end inserts a first synchronous anchor frame and a second synchronous anchor frame after the calibration synchronization is triggered, writes an alignment element identifier and a count value of a sending sampling counter, and registers a sending cache record table; a receiving end verifies the error detection code, pairs anchor frames according to a fixed anchor spacing rule, calculates an alignment offset and a forward inter-anchor stepping steady-state length, and generates an alignment proof message; checking the sending cache record table and the proof code, counting that the return proof reaches consistent continuity, indexing an offline training confidence matrix and outputting an alignment credibility level, and when conditions are met, updating framing boundary and time identifier mapping and sending a mapping effective message; and the receiving end starts the mapping version identifier, rechecks the stability of the alignment offset by means of the monitoring anchor frame, and sends a resynchronization request when the alignment offset fails.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of digital communications, and more specifically, to a method and apparatus for synchronizing a digital phased array antenna. Background Technology

[0002] In digital phased array antenna systems, to enable coherent synthesis of multiple subarray outputs in the central processing unit, it is typically necessary to unify the sampling times and phase references of each subarray. Current practices generally involve a calibration synchronization process before the system enters amplitude and phase correction: calibration equipment provides each subarray with the same reference trigger or reference signal, ensuring alignment under the same reference. Furthermore, the initial phase information of the digital frequency synthesis unit within each subarray is acquired, and this information is then incorporated as compensation into the amplitude and phase correction results of each channel. Upon system restart, calibration synchronization is performed again to acquire and compensate for the phase changes compared to the previous restart. This aims to minimize random phase differences between subarrays and maintain stable and consistent beamforming without significantly increasing hardware resources.

[0003] However, in engineering implementation, calibration synchronization information and actual business data are not always naturally linked. During transmission, buffering, cross-clock domain processing, and link reconnection, the synchronization trigger or calibration reference may undergo different paths and state changes than the business data. This can lead to a situation where calibration synchronization appears complete, but the boundary of the business data corresponding to the calibration moment has unknowingly shifted. Consequently, the initial phase or phase change obtained during the calibration phase may be aligned with the calibration event but not with the data actually involved in beamforming. The compensation amount is applied to an incorrect alignment relationship, ultimately resulting in imperceptible phase inconsistencies remaining between subarrays. This problem is insidious because the system often does not experience obvious loss of lock or transmission interruption, and the calibration process may complete step by step. However, once the actual synthesis processing begins, phenomena such as decreased synthesis gain, abnormal sidelobes, or deteriorated beam stability may occur. Furthermore, the fault appears and disappears intermittently depending on the link state and operational process, making it difficult to locate.

[0004] To address the aforementioned problems, a technical solution is provided. Summary of the Invention

[0005] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a digital phased array antenna synchronization method and apparatus. The transmitting end inserts a first synchronization anchor frame and a second synchronization anchor frame after calibration synchronization is triggered, writes an alignment epoch identifier and a transmission sampling counter count value, and registers the data in the transmission buffer record table. The receiving end verifies the error detection code and pairs anchor frames according to the fixed anchor spacing rule, calculates the alignment offset and the forward anchor step steady-state length, and generates an alignment proof message. It checks the transmission buffer record table and the proof code, statistically analyzes the consistency continuity of the returned proof, and indexes the alignment confidence level output by the offline training confidence matrix. When the conditions are met, it updates the mapping between the frame boundary and the time identifier and sends a mapping activation message. The receiving end enables the mapping version identifier and verifies the stability of the alignment offset by monitoring the anchor frames. If it fails, it sends a resynchronization request to solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides the following technical solution: A method for synchronizing a digital phased array antenna includes the following steps: S1. After receiving the calibration synchronization trigger, the sending end inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream, following the fixed anchor spacing rule. The anchor frame carries the alignment epoch identifier and the transmission sampling counter count value, along with the error detection code. The sending end writes the anchor frame sequence and the count value into the transmission buffer record table. S2. The receiving end locates the candidate synchronization anchor frame and verifies the error detection code. It completes anchor frame pairing according to the fixed anchor spacing rule, calculates the difference between the receiving sampling counters of the two anchor frames and checks the difference between the sending sampling counters. When the difference is consistent, it generates an alignment offset. The receiving end calculates the forward anchor step steady-state length based on the service frame step sequence. S3. The receiving end generates an alignment proof message, writing the alignment epoch identifier, the count values ​​of the two anchor frame transmission sampling counters, the count values ​​of the two anchor frame reception sampling counters, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by combining the alignment epoch identifier and the count values ​​of the two anchor frames according to the fixed anchor spacing rule. The message includes an error detection code and is sent through the control channel. S4. The sending end receives the alignment proof message and checks the sending buffer record table. After verifying the proof code, it generates a consistent marker sequence and counts the consistency continuity of the returned proof. It reads the steady-state length of the forward anchor step and outputs the alignment confidence level according to the offline trained confidence matrix. When the alignment confidence level meets the effective conditions, it updates the mapping between the frame boundary and the time identifier, generates the mapping version identifier and sends the mapping effective message. If it does not meet the conditions, it sends a re-anchoring request. S5. After receiving the mapping effective message, the receiving end enables the mapping version identifier and interprets the service data according to the effective start frame order. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end reviews the alignment offset stability and verifies the monitoring anchor frames. If the review fails, a resynchronization request is sent and the failure event is recorded.

[0007] In a preferred embodiment, step S1 includes: after receiving the alignment synchronization trigger, the transmitting end obtains the current frame sequence from the service frame transmission state machine, generates a first synchronization anchor frame and a second synchronization anchor frame, the frame sequence of the first synchronization anchor frame is taken from the current frame sequence, the alignment epoch identifier is generated by the transmitting end synchronization state machine incrementing and written into the load fields of the two synchronization anchor frames, the transmission sampling counter count value is latched and written into the load field at the framing time of the two synchronization anchor frames respectively, the service frame transmission scheduler determines the frame sequence of the second synchronization anchor frame according to the fixed anchor spacing rule and inserts it into the service data stream, the anchor frame type field is written into the header field of the two synchronization anchor frames, the error detection code is generated from the header field and the load field of the two synchronization anchor frames and written into the tail field, and the alignment epoch identifier, the frame sequence of the two synchronization anchor frames and the transmission sampling counter count value are registered in the transmission buffer record table.

[0008] In a preferred embodiment, step S2 includes: the receiving end parses the service frame header and identifies the anchor frame type field; when the anchor frame type field satisfies the value of the synchronization anchor frame type, error detection code verification is performed; the error detection code verification uses the synchronization anchor frame header field and the synchronization anchor frame payload field to form an input bit sequence and uses bitwise shift register operation to recalculate the error detection code; when the recalculated error detection code is consistent with the error detection code at the end of the synchronization anchor frame, the synchronization anchor frame is written into the anchor frame buffer queue in frame order and the alignment epoch identifier is retained; when the recalculated error detection codes are inconsistent, the synchronization anchor frame is discarded and the abnormal type is registered.

[0009] In a preferred embodiment, step S2 further includes: the receiving end completes the pairing of the first synchronization anchor frame and the second synchronization anchor frame in the anchor frame buffer queue according to the preset frame interval of the fixed anchor spacing rule and verifies the consistency of the alignment epoch identifier; reads the transmission sampling counter count value of the two synchronization anchor frames to calculate the transmission difference; latches the reception sampling counter count value at the arrival time of the two synchronization anchor frames to calculate the reception difference; subtracts the transmission difference from the reception difference to obtain the deviation amount; performs a circular operation according to the number of sampling points per frame to obtain the alignment offset amount; at the same time, latches the reception sampling counter count value at the service frame boundary to form a service frame step sequence and generate a steady-state mark sequence; the forward anchor step steady-state length is taken as the lower limit of the length of the preceding continuous steady-state frame and the length of the following continuous steady-state frame.

[0010] In a preferred embodiment, step S3 includes: the receiving end generates an alignment proof message and writes the alignment epoch identifier and message sequence number into the message header, and sequentially writes the first synchronization anchor frame transmission sampling counter count value, the second synchronization anchor frame transmission sampling counter count value, the first synchronization anchor frame reception sampling counter count value, the second synchronization anchor frame reception sampling counter count value, alignment offset, and forward anchor step steady-state length into the message payload, with the fields arranged using a fixed byte order and a fixed field length.

[0011] In a preferred embodiment, step S3 further includes: the receiving end concatenates the alignment epoch identifier, the first synchronization anchor frame transmission sampling counter count value, the second synchronization anchor frame transmission sampling counter count value, and the preset frame interval of the fixed anchor spacing rule in a fixed byte order to form a proof input string, and uses a linear feedback shift register to perform bit-by-bit operations to generate a proof code, which is then written into the alignment proof message; the receiving end concatenates the message header field, message payload field, and proof code field in a fixed byte order, and uses a linear feedback shift register to perform bit-by-bit operations to generate an error detection code, which is then written into the tail of the alignment proof message; the alignment proof message enters the control channel logic queue and is sent in a first-in-first-out order.

[0012] In a preferred embodiment, step S4 includes: after receiving the alignment proof message, the sending end recalculates the message error detection code and verifies its consistency; extracts the alignment epoch identifier, message sequence number, first synchronization anchor frame transmission sampling counter count value, second synchronization anchor frame transmission sampling counter count value, alignment offset, and forward anchor step steady-state length; retrieves the transmission buffer record table according to the alignment epoch identifier and verifies the consistency of the two synchronization anchor frame transmission sampling counter count values; and recalculates the proof code and verifies its consistency according to the alignment epoch identifier, the two synchronization anchor frame transmission sampling counter count values, and the preset frame interval of the fixed anchor spacing rule.

[0013] In a preferred embodiment, step S4 further includes: the sending end performs deduplication on the alignment proof message and constructs a consistency marker sequence under the same alignment epoch identifier; the maximum segment length where the consistency marker is continuously true is taken when the backhaul proof reaches the consistency continuity; the forward anchor step steady-state length is mapped to a steady-state level identifier; the backhaul proof reaches the consistency continuity is mapped to a consistency level identifier and the offline training confidence matrix is ​​indexed to obtain the alignment confidence level; when the alignment confidence level reaches the effective level threshold, the framing boundary and time identifier mapping is updated and a mapping version identifier and effective start frame sequence are generated and written into the mapping effective message for transmission; when the alignment confidence level does not reach the effective level threshold, a re-anchoring request is sent.

[0014] In a preferred embodiment, step S5 includes: the receiving end recalculates the error detection code of the mapping effective message and verifies its consistency; registers the mapping version identifier and the effective start frame sequence; when the current service frame sequence is not less than the effective start frame sequence, the frame boundary corresponding to the mapping version identifier is used to map the time identifier; after receiving the monitoring anchor frame, the receiving end recalculates the error detection code and latches the transmit sampling counter count value and the receive sampling counter count value; calculates the instantaneous offset and calculates the offset change between adjacent monitoring anchor frames; when the offset change exceeds the stability threshold, a resynchronization request is generated and written to the alignment epoch identifier and the mapping version identifier; and at the same time, the failure event record is registered.

[0015] A digital phased array antenna synchronization device, comprising: Anchor Frame Insertion Module: After the transmitting end receives the calibration synchronization trigger, it inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream according to the fixed anchor spacing rule. The anchor frame is written with the alignment epoch identifier and the transmission sampling counter count value and an error detection code. The anchor frame sequence and count value are registered in the transmission buffer record table. Pairing and verification module: The receiving end locates the candidate synchronization anchor frame and completes the error detection code verification. The receiving end pairs two anchor frames according to the fixed anchor spacing rule. The receiving end calculates the difference of the receiving sampling counter and verifies the difference of the sending sampling counter. When the difference is consistent, the alignment offset is generated and the forward anchor step steady-state length is calculated. The proof feedback module: The receiving end generates an alignment proof message and writes the alignment epoch identifier, the count value of the two anchor frame transmission sampling counter, the count value of the two anchor frame reception sampling counter, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by binding the alignment epoch identifier and the anchor frame count value according to the fixed anchor spacing rule. The message is sent via the control channel with an error detection code attached. Trusted Activation Module: After receiving the alignment proof message, the sending end checks the sending cache record table and verifies the proof code. The sending end generates a consistency mark sequence and counts the consistency continuity of the returned proof. The sending end combines the forward anchor step steady-state length index to train the confidence matrix offline and outputs the alignment confidence level. When the activation conditions are met, the frame boundary and time identifier mapping is updated and the mapping activation message is sent. When the conditions are not met, a re-anchoring request is sent. Continuous monitoring module: After receiving the mapping effective message, the receiving end interprets the service data according to the mapping version identifier and the effective start frame sequence. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end verifies the monitoring anchor frames and reviews the alignment offset stability. If the review fails, a resynchronization request is sent and the failure event is recorded.

[0016] This invention discloses a digital phased array antenna synchronization method and apparatus, which relates to data security technology, and its technical effects and advantages are as follows: 1. The first and second synchronization anchor frames are generated by calibration synchronization trigger. The anchor frame payload is simultaneously written with the alignment epoch identifier and the transmission sampling counter count value. The anchor frame tail is written with the error detection code covering the anchor frame header field and payload field. The service data stream is inserted according to the fixed anchor spacing rule and the transmission buffer record table is registered. This enables the receiver to stably identify and match anchor frames in complex link buffer and jitter environments, ensuring that the source of the alignment offset is traceable and verifiable, and avoiding the use of damaged or mismatched anchor frames as the synchronization basis, which would cause the frame boundary to drift.

[0017] 2. The receiving end filters out candidate synchronization anchor frames based on the anchor frame type field and error detection code. After pairing according to the fixed anchor spacing rule, it simultaneously calculates the transmission difference and the reception difference to obtain the alignment offset. It then uses the service frame boundary latch to latch the reception sampling counter count value to form a service frame step sequence and a steady-state mark sequence to obtain the forward anchor step steady-state length. The above results are then encapsulated into an alignment proof message, and the proof code is used to achieve anchor consistency binding. This allows the sending end to complete the evidence chain closure verification without relying on the service channel delay model, reducing misjudgments caused by cross-round mixing and out-of-order retransmission, and improving the credibility of the alignment update decision.

[0018] 3. The sending end performs message error detection code verification, proof code recalculation verification, and transmission buffer record table check on the alignment proof message. Combined with deduplication and consistency mark sequence statistics, it obtains the consistency continuity of the returned proof. Then, together with the forward anchor step steady-state length, it completes the grading mapping and indexes the offline training confidence matrix to output the alignment confidence level. When the effective level threshold is reached, it updates the frame boundary and time identifier mapping and issues the mapping version identifier and effective start frame sequence. After the receiving end is enabled, it monitors the anchor frame to verify the stability of the alignment offset and sends a resynchronization request when it fails. This realizes the collaborative closed loop of alignment establishment, alignment effectiveness, and alignment maintenance, reducing invalid switching and long-term drift accumulation. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating a digital phased array antenna synchronization method according to the present invention.

[0020] Figure 2 This is a schematic diagram of the structure of a digital phased array antenna synchronization device according to the present invention. Detailed Implementation

[0021] 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 only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0022] Example 1: Figure 1 This invention provides a method for synchronizing a digital phased array antenna, comprising: S1. After receiving the calibration synchronization trigger, the sending end inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream, following the fixed anchor spacing rule. The anchor frame carries the alignment epoch identifier and the transmission sampling counter count value, along with an error detection code. The sending end writes the anchor frame sequence and the count value into the transmission buffer record table.

[0023] S2. The receiving end locates the candidate synchronization anchor frame and verifies the error detection code. It completes the anchor frame pairing according to the fixed anchor spacing rule, calculates the difference between the receiving sampling counters of the two anchor frames and checks the difference between the sending sampling counters. When the difference is consistent, an alignment offset is generated. The receiving end calculates the forward anchor step steady-state length based on the service frame step sequence.

[0024] S3. The receiving end generates an alignment proof message, which includes the alignment epoch identifier, the count values ​​of the two anchor frame transmission sampling counters, the count values ​​of the two anchor frame reception sampling counters, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by combining the alignment epoch identifier and the count values ​​of the two anchor frames according to the fixed anchor spacing rule. The message includes an error detection code and is sent through the control channel.

[0025] S4. The sending end receives the alignment proof message and checks the sending buffer record table. After verifying the proof code, it generates a consistency mark sequence and counts the consistency continuity of the returned proof. It reads the steady-state length of the forward anchor step and outputs the alignment confidence level according to the offline trained confidence matrix. When the alignment confidence level meets the effective conditions, it updates the mapping between the frame boundary and the time identifier, generates the mapping version identifier, and sends the mapping effective message. If it does not meet the conditions, it sends a re-anchoring request.

[0026] S5. After receiving the mapping effective message, the receiving end enables the mapping version identifier and interprets the service data according to the effective start frame order. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end reviews the alignment offset stability and verifies the monitoring anchor frames. If the review fails, a resynchronization request is sent and the failure event is recorded.

[0027] When the transmitter on the subarray side prepares a synchronization anchor frame, it needs to ensure that the position of the synchronization anchor frame in the service data stream is predictable, that the information carried by the synchronization anchor frame is traceable, and that the synchronization anchor frame can be stably identified and paired by the receiver after the link transmission. When there is buffering and reordering in the link, a single synchronization marker is easily misused as an alignment basis. By using paired synchronization anchor frames in conjunction with fixed anchor spacing rules and transmission sampling counter count values, the alignment semantics can be elevated from a single-point event to an inter-anchor consistency constraint, making it easier to fix the service alignment relationship corresponding to the synchronization trigger.

[0028] S101. Write the fields of the first synchronization anchor frame and the second synchronization anchor frame.

[0029] Upon arrival of the synchronization trigger, the service frame transmission state machine outputs the current frame sequence, and the transmitting end writes the current frame sequence into the first synchronization anchor frame's frame sequence field. The transmitting end's synchronization state machine increments the alignment epoch marker once, and writes the alignment epoch marker into the first synchronization anchor frame's payload field. The second synchronization anchor frame's payload field also writes the same alignment epoch marker, ensuring that the same alignment epoch marker is used in the same round of synchronization triggering. At the moment the first synchronization anchor frame is framed, the transmitting end latches the transmission sampling counter value in the transmission sampling clock domain, and writes the transmission sampling counter value into the first synchronization anchor frame's payload field. At the moment the second synchronization anchor frame is framed, the transmitting end latches the transmission sampling counter value and writes it into the second synchronization anchor frame's payload field. The header fields of the first and second synchronization anchor frames are written into the anchor frame type field. The anchor frame type field is used by the receiving end to distinguish between candidate synchronization anchor frames and ordinary service frames when parsing the service frame header. The synchronization anchor frame field is latched at the moment of framing, and a stable correspondence is formed between the transmission sampling counter value and the anchor frame sequence. Based on this, the receiving end can verify the consistency of the inter-anchor difference after anchor frame pairing, reducing dependence on the transient state of the link.

[0030] S102. The fixed anchor spacing rule determines the insertion position of the second synchronous anchor frame.

[0031] Synchronization anchor frame pairing relies on stable anchor interval semantics. This anchor interval semantics must fall within the service frame order definition to avoid ambiguity caused by differences in link bit-level details. The service frame transmission scheduler reads the fixed anchor interval rule, which includes a preset frame interval representing the number of service frames spanned between the first and second synchronization anchor frames. The service frame transmission scheduler determines the second synchronization anchor frame order as the first synchronization anchor frame order plus the preset frame interval. The scheduler reserves an anchor frame insertion slot at the second synchronization anchor frame order position. Ordinary service frames between the first and second synchronization anchor frames maintain their original frame order and transmission sequence. The fixed anchor interval rule uses frame order as the anchoring object, allowing the receiving end to complete pairing verification using the same preset frame interval. Anchor frame pairing is independent of transmission delay jitter, resulting in higher stability.

[0032] S103. Error detection code generation and transmission cache record table registration.

[0033] Bit flips may occur after the synchronization anchor frame traverses physical encoding and exchange buffers. The receiving end needs to determine the completeness and consistency of the anchor frame content before pairing. The error detection code generation process needs to be explicitly defined down to bit-by-bit operations to ensure consistency between the sending and receiving ends. The sending end concatenates the header field and payload field of the first synchronization anchor frame according to a pre-defined byte order to form an input bit sequence, which does not include the error detection code field. The sending end pads the input bit sequence with the same number of zero bits as the error detection code, resulting in a zero-padded bit sequence. The sending end performs bit-by-bit operations using a preset error detection code generation rule. This rule employs a linear feedback shift register structure, with the linear feedback tap position fixed by the link configuration. The sending end feeds the zero-padded bit sequence bit by bit from the most significant bit to the least significant bit into the shift register, performing a shift and feedback XOR operation for each input bit. The final register content serves as the error detection code for the first synchronization anchor frame and is written to the tail field of the first synchronization anchor frame. The error detection code for the second synchronization anchor frame is generated using the same process and written to the tail field of the second synchronization anchor frame. The sending end registers the alignment epoch identifier, the first synchronization anchor frame sequence number, the first synchronization anchor frame transmission sampling counter value, the second synchronization anchor frame sequence number, and the second synchronization anchor frame transmission sampling counter value in the transmission buffer record table. The transmission buffer record table is indexed by the alignment epoch identifier and retrieved using the anchor frame sequence number. The error detection code coverage is fixed in the anchor frame header and anchor frame payload fields. After recalculation by the receiving end according to the same generation rule, it can reliably filter out damaged anchor frames. The transmission buffer record table provides traceability, and the sending end can complete a consistent verification when the alignment proof message arrives, resulting in a lower probability of mismatch triggering.

[0034] After the first and second synchronization anchor frames are framed and inserted, a pair of anchor consistency constraints are formed under the same alignment epoch identifier. The fixed anchor spacing rule fixes the anchor relationship at the service frame sequence level. The transmit sampling counter value binds the anchor frame semantics to the sampling time. The error detection code constrains the integrity of the anchor frame fields to a recalcible range. The transmit buffer record table registers the key information of the anchor frame as a verifiable record. When the receiving end enters anchor frame identification, the anchor frame type field and error detection code verification support the screening of candidate synchronization anchor frames, the fixed anchor spacing rule supports anchor frame pairing, and the transmit sampling counter value supports difference verification and generates alignment offset.

[0035] After the first and second synchronization anchor frames are inserted into the service data stream by the sending end, the primary issue facing the receiving end is not alignment calculation, but verifying the reliability of the synchronization anchor frame content and the pairing relationship. Buffer reordering and short-term interference often do not block transmission, but they can mix false or damaged synchronization anchor frames into the data stream. As long as the candidate synchronization anchor frames pass the error detection code verification and meet the fixed anchor spacing rule for pairing, the difference between the sending sampling counter value and the receiving sampling counter value can be used to derive the alignment offset. At the same time, the step pattern of the service frame boundary can be used to quantify the forward anchor step steady-state length.

[0036] S201. Candidate synchronization anchor frame location and error detection code verification.

[0037] The anchor frame type field is used to separate synchronization anchor frames from ordinary service frames, preventing alignment calculations from mistakenly including them in ordinary service frames. After the receiver parses the service frame header, if the anchor frame type field meets the synchronization anchor frame type value, the candidate synchronization anchor frame enters the error detection code verification process. The error detection code verification uses the same shift register operation as the transmitter. The input bit sequence is obtained by concatenating the candidate synchronization anchor frame header field and the candidate synchronization anchor frame payload field according to the agreed byte order. The input bit sequence does not contain the error detection code field. The receiver pads the input bit sequence with the same number of zero bits as the number of error detection code bits. The receiver feeds the zero-padded bit sequence bit by bit from the most significant bit to the least significant bit into the shift register. Each input bit is shifted once, and a feedback XOR is performed according to the tap position. The final content of the register is used as the recalculated error detection code. When the recalculated error detection code matches the error detection code at the end of the candidate synchronization anchor frame, the candidate synchronization anchor frame is written into the anchor frame buffer queue and the frame order and alignment epoch identifier are retained. When the recalculated error detection code does not match, the candidate synchronization anchor frame is discarded and the exception type is registered, so that the anchor frame buffer queue only retains synchronization anchor frames with consistent fields, and the pairing process is more stable.

[0038] S202. Fixed anchor spacing rules for pairing synchronous anchor frames.

[0039] The fixed anchor spacing rule applies pairing constraints to the service frame order, avoiding the use of arrival time rhythm as the pairing basis, thus reducing the impact of buffer jitter on pairing. The receiver retrieves the earliest-order synchronization anchor frame from the anchor frame buffer queue as the first synchronization anchor frame candidate, and reads the first synchronization anchor frame's frame order and alignment epoch identifier. The fixed anchor spacing rule provides a preset frame interval; the receiver adds the first synchronization anchor frame's frame order to the preset frame interval to obtain the target frame order of the second synchronization anchor frame. When the anchor frame buffer queue contains a synchronization anchor frame with the target frame order and the same alignment epoch identifier, the first synchronization anchor frame and the target synchronization anchor frame form a paired anchor frame group, and the target synchronization anchor frame is defined as the second synchronization anchor frame. When the anchor frame buffer queue does not contain a synchronization anchor frame with the target frame order, the first synchronization anchor frame candidate waits and enters the next round of retrieval. When the anchor frame buffer queue contains a synchronization anchor frame with the target frame order but the alignment epoch identifier is inconsistent, the first synchronization anchor frame candidate abandons pairing and is removed from the anchor frame buffer queue, ensuring that the paired anchor frame group always corresponds to the same alignment epoch identifier.

[0040] S203. Send difference, receive difference, deviation, alignment offset calculation.

[0041] The transmit sampling counter value and the receive sampling counter value have the same dimensions. The difference calculation can reflect the sampling advancement relationship between anchors and avoid introducing the absolute starting point offset into the alignment judgment. The receiving end reads the transmit sampling counter value of the first synchronization anchor frame from the first synchronization anchor frame load field and the transmit sampling counter value of the second synchronization anchor frame from the second synchronization anchor frame load field. The transmit difference is equal to the transmit sampling counter value of the second synchronization anchor frame minus the transmit sampling counter value of the first synchronization anchor frame, and the dimension of the transmit difference is the sampling point. The receiving end latches the receive sampling counter value of the first synchronization anchor frame at the arrival time of the first synchronization anchor frame and latches the receive sampling counter value of the second synchronization anchor frame at the arrival time of the second synchronization anchor frame. The receive difference is equal to the receive sampling counter value of the second synchronization anchor frame minus the receive sampling counter value of the first synchronization anchor frame, and the dimension of the receive difference is the sampling point. The deviation is equal to the receive difference minus the transmit difference, and the dimension of the deviation is the sampling point. The receiver performs a circular calculation on the deviation based on the number of sampling points per frame. The circular calculation first calculates the deviation by dividing it by the number of sampling points per frame to obtain a quotient and a remainder. The quotient is rounded down, and the remainder equals the deviation minus the quotient multiplied by the number of sampling points per frame. The remainder falls within the length of one frame. The receiver converts the remainder into a shortest displacement expression. If the remainder is in the first half of a frame, the receiver aligns the offset and takes the remainder. If the remainder is in the second half of a frame, the receiver aligns the offset and takes the remainder minus the number of sampling points per frame. The dimensions of the alignment offset remain at the sampling point level, and the amplitude satisfies the shortest displacement standard, resulting in smoother buffer read boundary adjustments.

[0042] S204. Calculation of the steady-state length of the forward anchor step sequence of the steady-state marker sequence of the service frame step sequence.

[0043] The sampling count step pattern at the service frame boundary directly reflects whether the buffer read / write boundary has shifted. Compressing the step pattern into a forward anchor step steady-state length allows boundary stability to be expressed with a small number of fields. Starting from the end of the first synchronization anchor frame, the receiver latches the receive sampling counter value once at each service frame boundary until the end of the second synchronization anchor frame, forming a sequence of receive sampling counter values. The service frame step sequence is obtained by subtracting two adjacent latched values, with each item in the service frame step sequence having the dimension of a sampling point. The steady-state marker sequence is generated according to an item-by-item matching rule. When the corresponding item in the service frame step sequence equals the number of sampling points per frame, the corresponding item in the steady-state marker sequence is recorded as one; when the corresponding item in the service frame step sequence does not equal the number of sampling points per frame, the corresponding item in the steady-state marker sequence is recorded as zero. The receiver sequentially scans the steady-state marker sequence starting from the back of the first synchronization anchor frame. The number of consecutive 1s is recorded as the length of the preceding consecutive steady-state frame. The receiver then scans the steady-state marker sequence in reverse order from the front of the second synchronization anchor frame. The number of consecutive 1s is recorded as the length of the following consecutive steady-state frame. The forward anchor step steady-state length is taken as the lower limit of the lengths of the preceding and following consecutive steady-state frames. The dimension is the service frame. The stability characterization caliber near the anchor frame boundary is clearly defined.

[0044] After step S2 is completed, the anchor frame buffer queue only retains the synchronous anchor frames that have passed the error detection code verification. The first synchronous anchor frame and the second synchronous anchor frame form a paired anchor frame group according to the fixed anchor spacing rule and the alignment epoch identifier. The transmit difference, receive difference, deviation amount, and alignment offset amount form the shortest displacement aperture expression. The service frame step sequence and the steady-state mark sequence are compressed to obtain the forward anchor step steady-state length.

[0045] After the first and second synchronization anchor frames form a paired anchor frame group in step S2, the alignment offset and the forward anchor step steady-state length have clear physical meaning and dimensions. The receiving end needs to firmly bind this information with the alignment epoch identifier before sending it to the control channel. When retransmissions and out-of-order events occur in the control channel, relying solely on the message sequence number can easily lead to the problem of evidence being mis-assembled. The proof code pushes the anchor frame count evidence and the preset frame interval of the fixed anchor spacing rule into the same verification result. After recalculation by the sending end, it can be confirmed whether the message content comes from the same round of calibration synchronization triggering.

[0046] S301. Align the header and payload fields of the proof message to form a frame.

[0047] The alignment epoch identifier is used to distinguish different alignment synchronization trigger rounds, and the message sequence number is used to constrain the message arrangement order within the control channel. When the receiver generates the alignment proof message, the alignment epoch identifier and message sequence number are written sequentially into the message header, with the message sequence number monotonically increasing according to the control channel transmission order. The message payload sequentially includes the first synchronization anchor frame transmission sampling counter count value, the second synchronization anchor frame transmission sampling counter count value, the first synchronization anchor frame reception sampling counter count value, the second synchronization anchor frame reception sampling counter count value, the alignment offset, and the forward anchor step steady-state length. The field arrangement adopts a fixed byte order and fixed field length, and the field splicing boundary does not depend on the running state, so that the sender will not have field misalignment when reconstructing the proof input string.

[0048] S302. Prove that the input string is concatenated and the proof code is generated bit by bit.

[0049] When out-of-order events occur in the control channel, the proof code needs to lock the alignment epoch identifier and anchor frame count evidence into the same semantic domain to prevent evidence from different anchor frame pairs from being mixed with the same alignment epoch identifier. The receiver concatenates the alignment epoch identifier, the first synchronization anchor frame transmission sampling counter value, the second synchronization anchor frame transmission sampling counter value, and the preset frame interval of the fixed anchor spacing rule in a fixed byte order to form the proof input string. The proof input string does not contain the alignment offset or the forward anchor step steady-state length. The receiver executes the proof code generation rule on the proof input string. The proof code generation rule uses a linear feedback shift register structure, with the shift register length equal to the proof code field length, and the tap position fixed by the link configuration. The receiver feeds the proof input string bit by bit into the shift register, performing a shift operation after each bit is fed in. When the feedback condition is met, an XOR feedback is performed according to the tap position. After the entire proof input string is fed in, the same number of zero bits as the shift register length are fed in. The final content of the shift register is written into the proof code field. The proof code binds the anchor frame count evidence together with the preset frame interval, so that when the sending end checks the sending buffer record table, it can simultaneously confirm that the anchor frame pair is consistent with the anchor interval rule.

[0050] S303. Generation and writing of alignment proof message error detection code.

[0051] When the alignment proof message traverses the control channel, there is a risk of bit flipping. The error detection code covering the message header, message payload, and proof code fields allows for separate processing of message integrity and content authenticity checks. The receiving end concatenates the alignment proof message header, payload, and proof code fields in a fixed byte order to form the message input bit sequence, which does not include the error detection code field. The receiving end executes the error detection code generation rule on the message input bit sequence. This rule also uses a linear feedback shift register structure, with the shift register length equal to the error detection code field length, and the tap positions fixed by the link configuration. The receiving end feeds the message input bit sequence bit by bit into the shift register, performing a shift operation and a feedback XOR operation based on the tap position after each bit is input. After the entire message input bit sequence is fed in, the same number of zero bits as the shift register length are added. The final content of the shift register is written into the error detection code field and placed at the end of the alignment proof message. The sender's recalculation error detection code can reliably filter out corrupted messages, and the verification code and the check against the sender's buffer record table only face trusted input.

[0052] S304. Consistency constraints for transmission and retransmission of control channel logical queues.

[0053] The control channel employs a logical queue separate from the service channel. The logical queue dequeues messages according to a first-in, first-out (FIFO) rule, and the message sequence number matches the dequeue order. When the receiving end writes the alignment proof message into the logical queue, it simultaneously registers the alignment epoch identifier, message sequence number, first synchronization anchor frame sequence, and second synchronization anchor frame sequence. This registration information is only used for local tracing and is not included in the message fields. When a retransmission occurs on the control channel, the receiving end maintains the alignment epoch identifier, message sequence number, proof code, and error detection code unchanged and retransmits the same alignment proof message, avoiding splitting the same evidence chain into multiple different verification results. Based on this, the sending end can identify duplicate arrivals as the same message instance, making it easier to maintain the stability of the consistency marker generation rules.

[0054] After step S3 is completed, the alignment proof message, under the alignment epoch identifier, includes the transmit sampling counter count value and receive sampling counter count value of the first and second synchronization anchor frames, the alignment offset, and the forward anchor step steady-state length. The proof code is generated bit-by-bit by bit operation of the alignment epoch identifier, the transmit sampling counter count values ​​of the two anchor frames, and the preset frame interval according to the fixed anchor spacing rule. The error detection code is generated bit-by-bit by bit operation of the message header field, message payload field, and proof code field. The control channel logical queue maintains the message sequence number consistent with the transmission order. When the sending end enters step S4, the message error detection code verification, proof code verification, and transmission buffer record table check have a unique implementation path and consistent field caliber.

[0055] After the alignment proof message is sent from the receiver to the sender via the control channel, the key action for the sender is not to immediately rewrite the mapping between the frame boundary and the time identifier, but to confirm that the alignment proof message comes from the same alignment epoch identifier, from the same pair of synchronization anchor frame evidence chains, and from the same preset frame interval with the same fixed anchor spacing rule. When there are bit flips, out-of-order issues, or duplicate retransmissions in the control channel, judging a single field is prone to false triggering. However, by incorporating the message error detection code, proof code, transmission buffer record table, and message sequence number order into the judgment, the mapping update action can be limited to the moment when the evidence is consistent.

[0056] S401. Message error detection code verification and field extraction.

[0057] Control channel transmission carries a risk of bit flipping. Performing message error detection code verification beforehand isolates corrupted alignment proof messages from the statistical chain. The sending end concatenates the message header, message payload, and proof code fields according to the predetermined byte order of the alignment proof message to form the message input bit sequence. This input bit sequence does not include the message error detection code field. The sending end uses a linear feedback shift register to recalculate the message error detection code bit by bit. The recalculation process includes bit-by-bit input, XORing based on tap positions, padding with a fixed number of zero bits after input, and reading the final register content. When the recalculated message error detection code matches the error detection code at the end of the alignment proof message, the sending end extracts the alignment epoch identifier, message sequence number, the first synchronization anchor frame transmission sampling counter value, the second synchronization anchor frame transmission sampling counter value, alignment offset, and forward anchor step steady-state length, and writes them to the alignment proof message archive area. If they do not match, the alignment proof message is discarded and the exception type is registered. The consistency continuity statistics of the returned proof are not affected by corrupted content.

[0058] S402. Send cache record table for verification and proof code recalculation.

[0059] The anchor frame count evidence carried in the alignment proof message needs to be traced back to the original registration on the sending side to confirm a one-to-one correspondence between the alignment proof message and the first and second synchronization anchor frames inserted by the sending end. The sending end retrieves the transmission buffer record table using the alignment epoch identifier, reading the frame sequence of the first and second synchronization anchor frames, the transmission sampling counter value of the first and second synchronization anchor frames registered under the same alignment epoch identifier. The sending end compares the transmission sampling counter value of the first synchronization anchor frame in the alignment proof message with the value registered in the transmission buffer record table, and compares the transmission sampling counter value of the second synchronization anchor frame in the alignment proof message with the value registered in the transmission buffer record table. If both comparisons are consistent, the transmission buffer record table verification is considered successful. The proof code verification uses a recalculation method. The sending end concatenates the alignment epoch identifier, the transmission sampling counter value of the first and second synchronization anchor frames, and the preset frame interval according to the fixed anchor spacing rule in a fixed byte order to form the proof input bit sequence. The proof input bit sequence does not include the alignment offset and the forward anchor step steady-state length. The sending end uses a linear feedback shift register to recalculate the proof code bit by bit. The recalculation process is the same as that for message error detection code recalculation. The proof code verification is considered successful when the recalculated proof code matches the proof code in the aligned proof message. When the verification of the sending buffer record table and the proof code verification are both successful, the evidence chain binding relationship is clear, and the probability of cross-round mis-splitting is significantly reduced.

[0060] S403. Construction of Consistent Marked Sequences and Backpropagation Proof of Consistent Continuity Statistics.

[0061] The control channel experiences retransmissions of duplicate and out-of-order messages. The consistency continuity of the return proof needs to reflect stable order, not retransmission noise. The sender groups alignment proof messages in the archiving area by alignment epoch identifier. Within each group, a deduplication rule is first executed. This rule limits the retention of only the earliest arriving alignment proof message if the message sequence number is the same, the error detection code verification is successful, the proof code verification is successful, and the sender's buffer record table check is successful. Subsequent duplicate messages are not included in the order statistics. The deduplicated message sequence is scanned in arrival order. The sender generates a consistency flag for each message. A true consistency flag requires simultaneous fulfillment of the following conditions: the error detection code verification is successful, the proof code verification is successful, the sender's buffer record table check is successful, and the message sequence number increments by one relative to the previous message sequence number included in the statistics. The sender uses a continuity counter to count the length of consecutive true consistency flags. The continuity counter increments by one when a consistency flag is true and resets to zero when a consistency flag is false. Simultaneously, a maximum consecutive segment length is maintained, which is used as the consistency continuity of the return proof and written into the alignment epoch identifier status record. After combining deduplication rules with continuous segment statistics, the return proof of consistent continuity is more consistent with the true order of the control channel, and the input stability of the offline training confidence matrix is ​​stronger.

[0062] S404. Classification Mapping and Offline Training Confidence Matrix Index.

[0063] The forward anchor step steady-state length and the returned proof of reaching consensus continuity have different dimensions, and direct comparison would introduce ambiguity. Tier mapping converts these different dimensions into a unified tier index space. The sending end reads the forward anchor step steady-state length carried in the alignment proof message and performs interval classification based on the steady-state tier threshold sequence. The interval classification process involves comparing segments starting from the minimum threshold interval, and outputting the steady-state tier identifier after a matching inclusion relationship is found. The sending end reads the returned proof of reaching consensus continuity from the alignment epoch identifier state record and performs interval classification based on the consensus tier threshold sequence. The classification process is the same as for the steady-state tier identifier, and outputs the consensus tier identifier. The sending end uses the steady-state tier identifier as the row index and the consensus tier identifier as the column index to read the alignment confidence level from the offline trained confidence matrix and write it into the alignment epoch identifier state record. The tier index is a discrete integer, and the indexing process does not introduce floating-point estimation error, ensuring the deterministic output of the alignment confidence level.

[0064] S405. Validation determination and framing boundary and time marker mapping update.

[0065] The framing boundary and time stamp mapping update is a critical control action. Effectiveness determination requires establishing a clear relationship between the alignment confidence level and the effectiveness level threshold. The sending end reads the alignment confidence level and compares it with the effectiveness level threshold. If the alignment confidence level reaches the effectiveness level threshold, it enters the mapping update path; otherwise, it enters the re-anchor request path. In the mapping update path, the sending end writes the alignment offset into the offset entry of the framing boundary and time stamp mapping table. The unit of the offset entry remains the sampling point. When interpreting the service frame boundary, the mapping table corrects it by adding the offset entry to the baseline boundary position. If the corrected boundary position exceeds the number of sampling points per frame, it performs circular normalization based on the number of sampling points per frame to ensure the boundary position falls back to the range of one frame. The sending end increments the mapping version identifier to generate and writes it into the mapping effectiveness message. Simultaneously, it reads the second synchronization anchor frame sequence from the transmission buffer record table. The effectiveness start frame sequence is taken as the next service frame sequence after the second synchronization anchor frame sequence. The mapping effectiveness message is written with the mapping version identifier and the effectiveness start frame sequence and sent through the control channel. In the re-anchor request path, the sending end generates a re-anchor request, writes the alignment epoch identifier, and sends it. The mapping table remains unchanged. The mapping update boundary is clear, the mapping switching process is consistent with the anchor frame evidence chain, and the risk of coherent timing misalignment caused by erroneous updates is reduced.

[0066] After step S4, the sending end completes message error detection code verification, proof code verification, sending cache record table check, deduplication and consistency marker sequence statistics to obtain the consistency continuity of the returned proof; the sending end completes the tiered mapping of the forward anchor step steady-state length and the consistency continuity of the returned proof and indexes the offline training confidence matrix, outputting the alignment confidence level; the sending end executes the mapping update or re-anchoring request according to the alignment confidence level, and writes the mapping version identifier and effective starting frame sequence into the mapping effective message.

[0067] After the mapping version identifier and effective start frame sequence are sent from the sending end, the receiving end begins to switch the mapping of the framing boundary and the time identifier using the frame sequence as coordinates. During operation, link buffering and clock drift often do not immediately manifest as frame loss, but they cause the sampling count to shift slowly over a long time scale. A single alignment offset cannot reflect this evolution trend. However, by monitoring the anchor frame and bringing the sending sampling counter value into the service flow, and then latching the receiving sampling counter value at the receiving end, the offset change can be directly quantified into a verifiable evidence of stability.

[0068] S501. Mapping Validation Message Verification and Mapping Enablement.

[0069] When bit flips occur in the control channel, if the mapping version identifier and the effective start frame sequence are corrupted, a version jump will occur in the interpretation of the service frame. The receiver performs error detection code recalculation on the mapping effective message. The recalculation method uses a linear feedback shift register for bit-by-bit operation. The input bit sequence is obtained by concatenating the mapping effective message header field and the mapping effective message payload field in a fixed byte order. The input bit sequence does not contain the error detection code field. After being fed in bit by bit, zero bits of the same length as the error detection code are added. The final content of the shift register is read as the recalculated error detection code. When the recalculated error detection code matches the error detection code at the end of the mapping effective message, the receiver reads the mapping version identifier and the effective start frame sequence. The receiver writes the mapping version identifier and the effective start frame sequence into the local mapping table and marks it as pending effectiveness. During the service frame interpretation phase, the current service frame sequence is read. If the current service frame sequence is not less than the effective start frame sequence, the receiver uses the framing boundary and time identifier mapping corresponding to the mapping version identifier. If the current service frame sequence is less than the effective start frame sequence, the receiver maintains the original framing boundary and time identifier mapping. Once the mapping switching boundary is fixed at the frame sequence coordinates, jitter in the control channel will not change the mapping activation time.

[0070] S502. Monitoring anchor frame verification and counting latch.

[0071] Operational verification requires unified observation points. When the monitoring anchor frame carries the transmit sampling counter value, the receiver only needs to latch the receive sampling counter value at the arrival time of the monitoring anchor frame to form a paired observation. The receiver identifies the anchor frame type field in the data reception path. When the anchor frame type field meets the monitoring anchor frame type value, error detection code verification is performed. The error detection code verification recalculation process is consistent with the mapping effective message. When the error detection code verification passes, the receiver reads the transmit sampling counter value from the monitoring anchor frame payload field. The receiver latches the receive sampling counter value at the arrival time of the monitoring anchor frame and records the monitoring anchor frame sequence and mapping version identifier. When the error detection code verification fails, the monitoring anchor frame is discarded and the exception type is registered. After the monitoring anchor frame observation point is fixed, the source of offset change is clear, reducing the probability of mistakenly identifying ordinary service frame boundary jitter as alignment drift.

[0072] S503. Instantaneous offset calculation and offset change determination.

[0073] Fixed propagation and processing delays shift the transmit and receive sampling counter values ​​as a whole. Directly comparing single differences can easily mistake this shift for drift. Therefore, stability is determined by the change between adjacent monitoring anchor frames. For each monitoring anchor frame that passes error detection, the receiver first calculates the instantaneous offset, which equals the receive sampling counter value minus the transmit sampling counter value. When either the transmit or receive sampling counter value wraps around, the receiver first performs wraparound compensation according to the counter wraparound period, then performs the subtraction operation. The wraparound compensation rule is that if the later count value is less than the earlier count value, the later count value is added to the counter wraparound period. After saving the instantaneous offsets of two adjacent monitoring anchor frames, the receiver calculates the offset change, which equals the later instantaneous offset minus the earlier instantaneous offset. Wraparound compensation is also performed according to the counter wraparound period to ensure that the change is not amplified by wraparound. The receiver compares the magnitude of the offset change with a stability threshold. If the magnitude does not exceed the stability threshold, the alignment offset is considered stable; if the magnitude exceeds the stability threshold, the alignment offset is considered unstable. After eliminating the fixed shift, the offset change only retains the evolution trend, making the stability determination closer to the true behavior of clock drift and buffer drift.

[0074] S504. Failure handling and failure event recording.

[0075] Continuing to use the mapping version identifier when alignment offset stability fails will cause the frame boundary and time identifier mapping to gradually deviate from the true boundary. The receiver needs to explicitly transmit the failure status and retain the chain of evidence. When alignment offset stability fails, the receiver generates a resynchronization request, which is written with the alignment epoch identifier and mapping version identifier and sent via the control channel. The receiver also generates a failure event and writes it to the failure event record table. The failure event record includes the monitoring anchor frame sequence, the transmit sampling counter count value of the two monitoring anchor frames, the receive sampling counter count value of the two monitoring anchor frames, the instantaneous offset of the two monitoring anchor frames, the offset change, and the stability threshold judgment result. When alignment offset stability passes, the receiver updates the most recent pass record and retains the observation pair of the two most recent monitoring anchor frames. The failure event record table places the failure triggering condition in the recalculation field. With the resynchronization request carrying the alignment epoch identifier and mapping version identifier, the sender can more directly locate the problematic round and mapping version.

[0076] After step S5 is completed, the receiver enables the mapping of the frame boundary and time identifier corresponding to the mapping version identifier at the effective starting frame sequence. The receiver continuously latches the sending sampling counter count value and the receiving sampling counter count value by monitoring the anchor frame and calculates the instantaneous offset and offset change. The receiver outputs the alignment offset stability result based on the offset change and the stability threshold. In case of failure, a resynchronization request is sent and the evidence is written into the failure event record table.

[0077] Example 2: Figure 2 The present invention discloses a digital phased array antenna synchronization device, comprising: Anchor Frame Insertion Module: After the transmitting end receives the calibration synchronization trigger, it inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream according to the fixed anchor spacing rule. The anchor frame is written with the alignment epoch identifier and the transmission sampling counter count value and an error detection code. The anchor frame sequence and count value are registered in the transmission buffer record table.

[0078] Pairing and verification module: The receiving end locates the candidate synchronization anchor frame and completes the error detection code verification. The receiving end pairs two anchor frames according to the fixed anchor spacing rule. The receiving end calculates the difference between the receiving sampling counter and verifies the difference between the sending sampling counter. When the differences are consistent, the alignment offset is generated and the forward anchor step steady-state length is calculated.

[0079] The proof return module: The receiving end generates an alignment proof message and writes the alignment epoch identifier, the count value of the two anchor frame transmission sampling counter, the count value of the two anchor frame reception sampling counter, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by binding the alignment epoch identifier and the anchor frame count value according to the fixed anchor spacing rule. The message is sent via the control channel with an error detection code attached.

[0080] Trustworthy activation module: After receiving the alignment proof message, the sending end checks the sending cache record table and verifies the proof code. The sending end generates a consistency mark sequence and counts the consistency continuity of the returned proof. The sending end combines the forward anchor step steady-state length index to train the confidence matrix offline and outputs the alignment trust level. When the activation conditions are met, the frame boundary and time identifier mapping is updated and the mapping activation message is sent. When the conditions are not met, a re-anchoring request is sent.

[0081] Continuous monitoring module: After receiving the mapping effective message, the receiving end interprets the service data according to the mapping version identifier and the effective start frame sequence. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end verifies the monitoring anchor frames and reviews the alignment offset stability. If the review fails, a resynchronization request is sent and the failure event is recorded.

[0082] Specifically, the above description is only a preferred embodiment of this application and is not intended to limit this application.

[0083] In the description of this specification, references to terms such as "an embodiment," "example," and "specific example" indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0084] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to any specific implementation. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A method for synchronizing a digital phased array antenna, characterized in that, Including the following steps: S1. After receiving the calibration synchronization trigger, the sending end inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream, following the fixed anchor spacing rule. The anchor frame carries the alignment epoch identifier and the transmission sampling counter count value, along with the error detection code. The sending end writes the anchor frame sequence and the count value into the transmission buffer record table. S2. The receiving end locates the candidate synchronization anchor frame and verifies the error detection code. It completes anchor frame pairing according to the fixed anchor spacing rule, calculates the difference between the receiving sampling counters of the two anchor frames and checks the difference between the sending sampling counters. When the difference is consistent, it generates an alignment offset. The receiving end calculates the forward anchor step steady-state length based on the service frame step sequence. S3. The receiving end generates an alignment proof message, writing the alignment epoch identifier, the count values ​​of the two anchor frame transmission sampling counters, the count values ​​of the two anchor frame reception sampling counters, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by combining the alignment epoch identifier and the count values ​​of the two anchor frames according to the fixed anchor spacing rule. The message includes an error detection code and is sent through the control channel. S4. The sending end receives the alignment proof message and checks the sending buffer record table. After verifying the proof code, it generates a consistent marker sequence and counts the consistency continuity of the returned proof. It reads the steady-state length of the forward anchor step and outputs the alignment confidence level according to the offline trained confidence matrix. When the alignment confidence level meets the effective conditions, it updates the mapping between the frame boundary and the time identifier, generates the mapping version identifier and sends the mapping effective message. If it does not meet the conditions, it sends a re-anchoring request. S5. After receiving the mapping effective message, the receiving end enables the mapping version identifier and interprets the service data according to the effective start frame order. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end reviews the alignment offset stability and verifies the monitoring anchor frames. If the review fails, a resynchronization request is sent and the failure event is recorded.

2. The digital phased array antenna synchronization method according to claim 1, characterized in that: Step S1 includes: After the transmitting end receives the calibration synchronization trigger, it obtains the current frame sequence from the service frame transmission state machine, generates a first synchronization anchor frame and a second synchronization anchor frame, the frame sequence of the first synchronization anchor frame is taken from the current frame sequence, the alignment epoch identifier is generated by the transmitting end synchronization state machine incrementing and written into the load fields of the two synchronization anchor frames, the transmission sampling counter count value is latched and written into the load field at the framing time of the two synchronization anchor frames respectively, the service frame transmission scheduler determines the frame sequence of the second synchronization anchor frame according to the fixed anchor spacing rule and inserts it into the service data stream, the anchor frame type field is written into the header field of the two synchronization anchor frames, the error detection code is generated from the header field and the load field of the two synchronization anchor frames and written into the tail field, and the alignment epoch identifier, the frame sequence of the two synchronization anchor frames and the transmission sampling counter count value are registered in the transmission buffer record table.

3. The digital phased array antenna synchronization method according to claim 2, characterized in that: Step S2 includes: the receiving end parses the service frame header and identifies the anchor frame type field. When the anchor frame type field meets the value of the synchronization anchor frame type, error detection code verification is performed. The error detection code verification uses the synchronization anchor frame header field and the synchronization anchor frame payload field to form an input bit sequence and uses bit-by-bit shift register operation to recalculate the error detection code. When the recalculated error detection code is consistent with the error detection code at the end of the synchronization anchor frame, the synchronization anchor frame is written into the anchor frame buffer queue in frame order and the alignment epoch identifier is retained. When the recalculated error detection codes are inconsistent, the synchronization anchor frame is discarded and the exception type is registered.

4. The digital phased array antenna synchronization method according to claim 3, characterized in that: Step S2 further includes: the receiving end completes the pairing of the first synchronization anchor frame and the second synchronization anchor frame in the anchor frame buffer queue according to the preset frame interval of the fixed anchor spacing rule and verifies the consistency of the alignment epoch identifier, reads the transmission sampling counter count value of the two synchronization anchor frames to calculate the transmission difference, latches the reception sampling counter count value of the two synchronization anchor frames at the arrival time to calculate the reception difference, subtracts the transmission difference from the reception difference to obtain the deviation, and performs a circular operation according to the number of sampling points per frame to obtain the alignment offset, and latches the reception sampling counter count value at the service frame boundary to form a service frame step sequence and generate a steady-state mark sequence, and the forward anchor step steady-state length is taken as the lower limit of the length of the preceding continuous steady-state frame and the length of the following continuous steady-state frame.

5. The digital phased array antenna synchronization method according to claim 4, characterized in that: Step S3 includes: the receiving end generates an alignment proof message and writes the alignment epoch identifier and message sequence number into the message header, and sequentially writes the first synchronization anchor frame transmission sampling counter count value, the second synchronization anchor frame transmission sampling counter count value, the first synchronization anchor frame reception sampling counter count value, the second synchronization anchor frame reception sampling counter count value, alignment offset, and forward anchor step steady-state length into the message payload, with the fields arranged in a fixed byte order and a fixed field length.

6. The digital phased array antenna synchronization method according to claim 5, characterized in that: Step S3 further includes: the receiving end concatenates the alignment epoch identifier, the first synchronization anchor frame transmission sampling counter count value, the second synchronization anchor frame transmission sampling counter count value, and the preset frame interval of the fixed anchor spacing rule in a fixed byte order to form a proof input string, and uses a linear feedback shift register to perform bit-by-bit operations to generate a proof code, which is then written into the alignment proof message. The receiving end concatenates the message header field, message payload field, and proof code field in a fixed byte order and uses a linear feedback shift register to perform bit-by-bit operations to generate an error detection code, which is then written into the tail of the alignment proof message. The alignment proof message enters the control channel logic queue and is sent in a first-in-first-out order.

7. The digital phased array antenna synchronization method according to claim 6, characterized in that: Step S4 includes: after receiving the alignment proof message, the sending end recalculates the message error detection code and verifies its consistency; extracts the alignment epoch identifier, message sequence number, first synchronization anchor frame transmission sampling counter count value, second synchronization anchor frame transmission sampling counter count value, alignment offset, and forward anchor step steady-state length; retrieves the transmission buffer record table according to the alignment epoch identifier and verifies the consistency of the two synchronization anchor frame transmission sampling counter count values; and recalculates the proof code and verifies its consistency according to the alignment epoch identifier, the two synchronization anchor frame transmission sampling counter count values, and the preset frame interval of the fixed anchor spacing rule.

8. A digital phased array antenna synchronization method according to claim 7, characterized in that: Step S4 further includes: the sending end performs deduplication on the alignment proof message and constructs a consistency marker sequence under the same alignment epoch identifier; the maximum segment length where the consistency marker is continuously true is taken when the backhaul proof reaches the consistency continuity; the forward anchor step steady-state length is mapped to the steady-state position identifier; the backhaul proof reaches the consistency continuity is mapped to the consistency position identifier and the offline training confidence matrix is ​​indexed to obtain the alignment confidence level; when the alignment confidence level reaches the effective level threshold, the frame boundary and time identifier mapping is updated and the mapping version identifier and effective start frame sequence are generated and written into the mapping effective message for sending; when the alignment confidence level does not reach the effective level threshold, a re-anchoring request is sent.

9. A digital phased array antenna synchronization method according to claim 8, characterized in that: Step S5 includes: the receiving end recalculates the error detection code of the mapping effective message and verifies its consistency, registers the mapping version identifier and the effective start frame sequence, and when the current service frame sequence is not less than the effective start frame sequence, it uses the sub-frame boundary and time identifier corresponding to the mapping version identifier for mapping. After receiving the monitoring anchor frame, the receiving end recalculates the error detection code and latches the transmit sampling counter count value and the receive sampling counter count value, calculates the instantaneous offset and calculates the offset change between adjacent monitoring anchor frames. When the offset change exceeds the stability threshold, a resynchronization request is generated and written to the alignment epoch identifier and the mapping version identifier, and at the same time, the failure event record is registered.

10. A digital phased array antenna synchronization device, used to implement the digital phased array antenna synchronization method according to any one of claims 1-9, characterized in that, include: Anchor Frame Insertion Module: After the transmitting end receives the calibration synchronization trigger, it inserts the first synchronization anchor frame and the second synchronization anchor frame into the service data stream according to the fixed anchor spacing rule. The anchor frame is written with the alignment epoch identifier and the transmission sampling counter count value and an error detection code. The anchor frame sequence and count value are registered in the transmission buffer record table. Pairing and verification module: The receiving end locates the candidate synchronization anchor frame and completes the error detection code verification. The receiving end pairs two anchor frames according to the fixed anchor spacing rule. The receiving end calculates the difference of the receiving sampling counter and verifies the difference of the sending sampling counter. When the difference is consistent, the alignment offset is generated and the forward anchor step steady-state length is calculated. The proof feedback module: The receiving end generates an alignment proof message and writes the alignment epoch identifier, the count value of the two anchor frame transmission sampling counter, the count value of the two anchor frame reception sampling counter, the alignment offset, and the forward anchor step steady-state length. The proof code is generated by binding the alignment epoch identifier and the anchor frame count value according to the fixed anchor spacing rule. The message is sent via the control channel with an error detection code attached. Trusted Activation Module: After receiving the alignment proof message, the sending end checks the sending cache record table and verifies the proof code. The sending end generates a consistency mark sequence and counts the consistency continuity of the returned proof. The sending end combines the forward anchor step steady-state length index to train the confidence matrix offline and outputs the alignment confidence level. When the activation conditions are met, the frame boundary and time identifier mapping is updated and the mapping activation message is sent. When the conditions are not met, a re-anchoring request is sent. Continuous monitoring module: After receiving the mapping effective message, the receiving end interprets the service data according to the mapping version identifier and the effective start frame sequence. During operation, the sending end inserts monitoring anchor frames according to the monitoring cycle and carries the sending sampling counter count value. The receiving end verifies the monitoring anchor frames and reviews the alignment offset stability. If the review fails, a resynchronization request is sent and the failure event is recorded.