A parallel interface module and its fault-tolerant method for data physical link failure

Abstract

This invention belongs to the technical field of communication interfaces, and more specifically, relates to a parallel interface module and its fault-tolerant method for data physical link failures. Specifically, it includes: S1 loading default configuration; the decision unit sends initial local configuration and initial peer configuration to the execution unit; the execution unit uses this to implement the mapping relationship between the service frames and data transmission pins and data reception pins of the sending and receiving ends, proceeding to S2; S2 confirming the role of the local end in the subsequent reconstruction process; if the received peer fault information is generated by the local end, the local end acts as the reconstruction requester, proceeding to S3; if the received local fault information is generated by the peer and sent via a reconstruction request frame, the local end acts as the reconstruction responder, proceeding to S4; S3 initiating reconstruction negotiation; S4 responding to the reconstruction negotiation. This invention solves the problem that traditional parallel interfaces lack data physical link fault tolerance capabilities when facing data physical link failures, and cannot automatically recover communication when a failure occurs.

Description

Technical Field

[0001] This invention belongs to the technical field of communication interfaces, and more specifically, relates to a parallel interface module and its fault-tolerant method for data physical link failures. Background Technology

[0002] A failure in the physical data link of a communication interface (referring to the complete connection from the data transmission pin at the transmitting end to the data reception pin at the receiving end via the transmission path) will lead to communication interruption. In scenarios with extremely stringent reliability requirements, such as aerospace and industrial control, interfaces operate under harsh conditions such as vibration, drastic temperature changes, and strong electromagnetic interference for extended periods. Microscopic defects in physical connections such as pins and solder joints are more likely to evolve into open circuits, short circuits, and other faults, making the reliability of the physical data link particularly prominent. Parallel interfaces contain a large number of data pins, amplifying the probability of physical data link failures. However, traditional parallel interfaces lack physical data link fault tolerance capabilities and cannot automatically restore communication when a physical data link failure occurs.

[0003] Chinese invention patent CN118585479A discloses a parallel interface signal transmission method and related equipment based on configurable state signals. It sets the clock length of multiple protocol signals in their corresponding configuration states according to the read / write operation timing; sets the high and low levels of multiple protocol signals in their corresponding configuration states according to the level switching state; and determines the target protocol type corresponding to the target device accessed by the parallel interface. This demonstrates reconfigurability at the communication protocol layer, achieving timing adaptation for multiple parallel protocols through configurable state signals. However, the core of this solution lies in solving compatibility issues caused by protocol differences and does not address fault tolerance handling for data physical link failures. Chinese invention patent CN120670356A discloses a configurable peripheral interface and controller system. It implements UART, SPI, and IIC functions through a PSC controller, eliminating the need for integrated independent UART, SPI, and IIC modules and significantly reducing pin count. It demonstrates reconfigurability at the physical resource mapping layer, achieving dynamic mapping between serial protocol functions such as UART, SPI, and IIC and shared pins through a PSC controller. However, the core of this solution lies in achieving functional reuse of pin resources across different communication protocols.

[0004] In summary, looking at the innovations in parallel interfaces and other communication interfaces, their design ideas are generally based on the premise of "intact physical connection". They do not really address the fault tolerance of the aforementioned physical data link failures. Traditional parallel interfaces lack the ability to tolerate physical data link failures and cannot automatically restore communication when a failure occurs. Summary of the Invention

[0005] The present invention aims to overcome at least one of the defects of the prior art and provide a parallel interface module method to solve the problems of traditional parallel interfaces lacking data physical link fault tolerance and being unable to recover communication on their own when a fault occurs.

[0006] The detailed technical solution of this invention is as follows:

[0007] A parallel interface module is used to connect two user terminals to achieve interaction. Each user terminal is implemented through an FPGA / ASIC. The parallel interface module interacts with other user logic within the FPGA / ASIC through a data bus. Specifically, it includes: a decision unit, an execution unit, a protocol unit, and a management frame listening unit.

[0008] The decision-making unit is used for:

[0009] Initialize configuration by sending the initial local configuration and initial peer configuration to the execution unit;

[0010] Information reception and fault judgment, while receiving the reported information from the protocol unit, arbitrating according to the reported information and built-in rules, and confirming the role of this end as the reconstruction requester or reconstruction responder;

[0011] Configuration management: when acting as a refactoring responder during the refactoring process, it generates the refactoring local configuration; when acting as a refactoring requester during the refactoring process, it receives the refactoring peer configuration; it issues mode switching instructions and configuration loading instructions to the execution unit.

[0012] Command scheduling sends framing commands to protocol units, driving the transmission of reconstruction request frames, reconstruction response frames, and reconstruction synchronization frames.

[0013] The execution unit is used for:

[0014] Configuration loading and mapping are performed based on service frames and management frames: initial local configuration and local configuration reconstruction are executed, service frames and management frames of the protocol unit are received, and the mapping of service frames or management frames to corresponding data transmission pins is realized; initial peer configuration and peer configuration reconstruction are executed, the mapping of corresponding data reception pins to service frames is realized, and service frames of the peer are received and transmitted to the protocol unit.

[0015] Mode switching: The execution decision unit executes the mode switching instruction to control the transmitting end to switch between parallel mode and multi-channel concurrent serial mode;

[0016] The protocol unit is used for:

[0017] Service frame processing: The service frames from the execution unit are parsed and verified. If the verification is correct, they are submitted to the data bus. If the verification fails, the service frame is discarded. If the verification finds a persistent error, it indicates that the physical data link in the corresponding direction may be faulty. The fault information of the other end is generated and reported to the decision unit.

[0018] Management frame processing: The management frames identified and reported by the management frame monitoring unit are parsed and verified, and the specific information in the management frames is extracted and reported to the decision unit.

[0019] Service frame framing: Assemble the service data of the data bus into service frames and send them to the execution unit;

[0020] Management frame framing: Upon receiving the framing instruction and related information from the decision unit, assemble the specified management frame and send it to the execution unit;

[0021] The management frame listening unit includes a set of independent asynchronous serial parsers. Each asynchronous serial parser is directly connected to a corresponding data receiving pin and performs the mapping from the data receiving pin to the management frame. After frame type identification, if it is a valid management frame, it is sent to the protocol unit; otherwise, it is discarded. This enables multi-channel independent listening to potential management frames on all data receiving pins.

[0022] Furthermore, the control transmitter switches between parallel mode and multi-channel concurrent serial mode, specifically as follows:

[0023] In the receiving direction of the parallel interface, the service frame is received in parallel interface mode, the initial peer configuration is executed, the peer configuration is reconstructed to realize the mapping of data receiving pins to service frames, and the service frame is sent to the protocol unit.

[0024] In the transmission direction of the parallel interface, the receiving protocol unit sends service frames or management frames. According to the mode switching instruction, when sending service frames, it switches to the parallel interface mode and realizes the mapping of service frames to data transmission pins according to the initial local configuration and the reconfiguration of local configuration; when sending management frames, it switches to the multi-channel concurrent serial mode to realize the mapping of management frames to data transmission pins.

[0025] Parallel mode refers to mapping the service frame to be sent to multiple data transmission pins in the transmission direction of the parallel interface. This mode is the normal working mode of the parallel interface.

[0026] Multi-channel concurrent serial mode refers to the following: in the transmission direction of the parallel interface, the management frame to be transmitted is copied to all available data transmission pins, and each pin independently and concurrently transmits the same content in a serial manner.

[0027] Furthermore, the built-in rules for conducting arbitration include:

[0028] First arbitration condition: If the received information is a fault message generated by this end, it means that this end has detected an abnormal transmission from the other end, and this end shall act as the reconstruction requester.

[0029] Second arbitration condition: If the received information is a fault message detected by the peer and sent through a reconstruction request frame, it means that the peer detected an abnormality in the transmission of this end, and this end shall act as the reconstruction responder.

[0030] Conflict arbitration rule: If both fault information from the other end and fault information from the local end are received simultaneously, the local end shall take precedence as the reconstructing responder.

[0031] Furthermore, the information reported by the receiving protocol unit used for arbitration includes:

[0032] Peer fault information: Originating from an abnormal verification of received service data, it indicates that the physical data link in the receiving direction of this end / the sending direction of the peer end may be faulty. Ultimately, it is necessary to send peer fault information to the peer end through a reconstruction request frame.

[0033] Local fault information: obtained by parsing the received reconstruction request frame, indicating that the physical data link in the local sending direction / receiving direction of the other end may be faulty.

[0034] The aforementioned fault information from the peer end and the fault information from the local end are collectively referred to as data physical link fault information, which is used to transmit the physical link status between two user ends.

[0035] Furthermore, the management frame includes a fixed frame header for frame delimitation and type identification, which has a different format from the service frame to ensure reliable identification in mixed data streams.

[0036] Furthermore, the asynchronous serial parser has a strict frame format verification capability. It only determines that the received data is a valid frame to be reported when it fully conforms to the complete format of the management frame, thereby avoiding accidental triggering during business data transmission.

[0037] A fault-tolerant method for data physical link failures based on a parallel interface module, the method comprising:

[0038] S1, Default Configuration Loading: The decision unit sends the initial local configuration and the initial peer configuration to the execution unit. The execution unit implements the mapping of service frames to the corresponding data transmission pins according to the initial local configuration and the mapping of the corresponding data reception pins to the service frames according to the initial peer configuration, and then proceeds to S2.

[0039] S2. Continuous monitoring and fault diagnosis:

[0040] S2.1 The execution unit maintains parallel mode and transmits service frames. During this period, the protocol unit performs dual monitoring: first, it verifies the service frames received from the execution unit; second, it parses the management frames received from the management frame monitoring unit. If it is a reconstruction request frame, it reports the local fault information contained therein to the decision unit.

[0041] S2.2 The decision-making unit determines its role in the subsequent reconstruction process based on the information reported by the protocol unit. If the received information is fault information generated by the peer, the unit acts as the reconstruction requester and proceeds to S3. If the received information is fault information detected by the peer and sent through a reconstruction request frame, the unit acts as the reconstruction responder and proceeds to S4. If both peer fault information and local fault information are received, the unit takes priority as the reconstruction responder.

[0042] S3. Initiate reconstruction negotiation, i.e., this end acts as the reconstruction requester;

[0043] S3.1 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S3.2;

[0044] S3.2 The decision unit issues a framing instruction to the protocol unit. The protocol unit generates a reconstruction request frame and sends it to the execution unit. Finally, the execution unit sends it in a multi-channel concurrent serial mode and enters S3.3.

[0045] S3.3 The management frame listening unit sends the received reconstruction response frame to the protocol unit for parsing. The protocol unit sends the parsed reconstruction peer configuration to the decision unit, and then proceeds to S3.4.

[0046] S3.4 The decision unit sends a framing instruction to the protocol unit. The protocol unit generates a reconstructed synchronization frame and sends it to the execution unit. Finally, the execution unit sends it in a multi-channel concurrent serial mode and enters S3.5.

[0047] S3.5 The decision unit sends a mode switching instruction and reconfigures the peer configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local receiving data receiving pin to the service frame according to the reconfigured peer configuration, and then enters S2.

[0048] S4, Responding to the reconstruction negotiation means that this end acts as the reconstruction responder;

[0049] S4.1 The management frame listening unit sends the received reconstruction request frame to the protocol unit for parsing. The protocol unit sends the parsed local fault information to the decision unit, and then proceeds to S4.2.

[0050] S4.2. Based on the fault information and the normal pins on the local end, the decision unit generates a reconfigurable local end configuration and proceeds to S4.3.

[0051] S4.3 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S4.4;

[0052] S4.4 The decision unit sends a framing instruction to the protocol unit. The protocol unit generates a reconstruction response frame based on the local reconstruction configuration and sends the frame to the execution unit. Finally, the execution unit sends the frame in a multi-channel concurrent serial mode and enters S4.5.

[0053] S4.5 The management frame listening unit sends the received reconstruction synchronization frame to the protocol unit for parsing. The protocol unit reports the result of "reconstruction synchronization confirmation" to the decision unit and proceeds to S4.6.

[0054] S4.6 The decision unit sends a mode switching instruction and reconfigures the local configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local sending service frames to the data sending pins according to the reconfigured local configuration, and then enters S2.

[0055] Further, preferably, the transmission of service frames specifically includes: in the receiving direction of the parallel interface, the execution unit sends the received service frame to the protocol unit, the protocol unit parses and verifies the service frame, if the verification is correct, the service frame is sent to other user logic through the data bus; if the verification is incorrect, the protocol unit discards the service frame, and if a continuous verification error occurs, indicating that the physical data link in the corresponding direction may be faulty, then a peer fault information is generated and reported to the decision unit;

[0056] In the transmission direction of the parallel interface, the protocol unit assembles the data on the data bus into service frames and sends them to the execution unit, which then maps the service frames to the corresponding data transmission pins.

[0057] In another aspect of the invention, an electronic device is also provided, comprising:

[0058] At least one processor; and

[0059] The memory stores instructions that, when executed by the at least one processor, cause the at least one processor to perform a parallel interface module as described above and its fault-tolerant method for data physical link failures.

[0060] In another aspect of the invention, a computer-readable storage medium is also provided, which stores executable instructions that, when executed, cause the machine to perform a parallel interface module as described above and a fault-tolerant method for data physical link failures.

[0061] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0062] (1) The present invention provides a parallel interface module and a fault-tolerant method for data physical link failure. Through the module and method, when a data physical link failure occurs, the interface can automatically reconstruct the mapping relationship between the service frame and the data receiving pin / data sending pin, so that communication can be maintained.

[0063] (2) The parallel interface module and its fault-tolerant method for data physical link failure provided by the present invention, from fault monitoring, decision, reconstruction negotiation to pin remapping, complete fault-tolerant process, is autonomously completed by the hardware logic consisting of protocol unit, decision unit, execution unit and management frame listening unit, without external and protocol upper layer intervention, thus realizing the autonomy of the recovery process.

[0064] (3) The parallel interface module and its fault tolerance method for data physical link failure provided by the present invention constructs a management frame transmission mechanism independent of the service channel through the management frame listening unit and multi-channel concurrent serial mode, ensuring that the management frame can still be reliably transmitted when some data physical links fail; through the centralized arbitration of the decision unit, the negotiation conflict caused by the simultaneous reconstruction of both ends is avoided, further improving the reliability of the fault tolerance mechanism. Attached Figure Description

[0065] Figure 1 This is a schematic diagram of a parallel interface module architecture according to the present invention.

[0066] Figure 2 This is a diagram of the parallel interface module architecture in Embodiment 1 of the present invention.

[0067] Figure 3 This is the reconstructed interaction flowchart in Embodiment 2 of the present invention. Detailed Implementation

[0068] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0069] It should be noted that the following detailed descriptions are exemplary and intended to provide further illustration of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0070] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0071] Without conflict, the embodiments in the present invention and the features in the embodiments may be combined with each other.

[0072] Embodiment 1

[0073] Refer Figure 1 , this embodiment provides a parallel interface module, which is used to connect two client terminals to achieve interaction, and each client terminal is implemented by FPGA / ASIC; the parallel interface module interacts with other user logics in the FPGA / ASIC through a data bus (since a client terminal has more than just a parallel interface module, other modules within the terminal are collectively referred to as other user logics).

[0074] Specifically, the parallel interface module includes: a decision-making unit, an execution unit, a protocol unit, and a management frame monitoring unit, as Figure 2 shown.

[0075] The decision-making unit is used for:

[0076] (1) Initialization configuration, sending the initial local configuration and the initial peer configuration to the execution unit;

[0077] (2) Information reception and fault judgment, receiving the reported information from the protocol unit, arbitrating according to the reported information and built-in rules, and confirming that the local role is a reconstruction requestor or a reconstruction responder S22;

[0078] (3) Configuration management, generating a reconstruction local configuration when acting as a reconstruction responder during the reconstruction process, or receiving a reconstruction peer configuration (uploaded by the protocol unit) when acting as a reconstruction requestor during the reconstruction process; sending a mode switching instruction and a configuration loading instruction to the execution unit;

[0079] (4) Instruction scheduling, sending a frame assembly instruction to the protocol unit to drive the transmission of a reconstruction request frame, a reconstruction response frame, and a reconstruction synchronization frame.

[0080] Further, the built-in rules for arbitration include:

[0081] The first arbitration condition: If the received is the peer fault information generated by the local end, it means that the local end detects an abnormal transmission of the peer end, then the local end acts as a reconstruction requestor;

[0082] The second arbitration condition: If the received is the local end fault information detected by the peer end and sent through the reconstruction request frame, it means that the peer end detects an abnormal transmission of the local end, then the local end acts as a reconstruction responder;

[0083] Conflict arbitration rule: If both peer fault information and local end fault information are received simultaneously, the local end prefers to act as a reconstruction responder. [[ID=4i]]

[0084] Furthermore, the information reported by the receiving protocol unit used for arbitration includes:

[0085] Peer fault information: Originating from an abnormal verification of received service data, it indicates that the physical data link in the receiving direction (i.e. the sending direction of the peer) may be faulty. Ultimately, it is necessary to send peer fault information to the peer through a reconstruction request frame.

[0086] Local fault information: obtained by parsing the received reconstruction request frame, indicating that the physical data link in the local sending direction (i.e. the receiving direction of the other end) may be faulty.

[0087] The aforementioned fault information from the peer end and the fault information from the local end are collectively referred to as data physical link fault information, which is used to transmit the physical link status between two user ends.

[0088] There are two independent paths between the two user terminals. For one terminal, such as terminal A, the local terminal is configured to tell terminal A how to send data to its peer terminal, and the peer terminal is configured to tell terminal A how to receive and parse the data sent by the peer terminal.

[0089] In this embodiment, the local configuration refers to a file generated by the local end that describes the mapping timing between the local end's data transmission pins and service frames. This file is used to guide the local end's execution unit in mapping service frames to data transmission pins and to guide the remote end's execution unit in mapping data reception pins to service frames in the transmission direction from the local end to the remote end. The initial local configuration refers to the default local configuration loaded during the initialization phase, while the reconfigured local configuration refers to the new local configuration generated after reconfiguration negotiation.

[0090] In this embodiment, the peer configuration refers to a file generated by the peer describing the mapping timing of its data transmission pins and service frames. This file guides the local execution unit to map data reception pins to service frames and the peer execution unit to map service frames to data transmission pins in the transmission direction from the peer to the local unit. The initial peer configuration refers to the default peer configuration loaded during the initialization phase, while the reconfigured peer configuration refers to the new peer configuration generated after reconfiguration negotiation.

[0091] The execution unit is used for:

[0092] (1) Configure loading and mapping based on service frames and management frames: execute initial local configuration, reconstruct local configuration, receive service frames and management frames from protocol units, and realize the mapping of service frames or management frames to corresponding data transmission pins; execute initial peer configuration, reconstruct peer configuration, realize the mapping of corresponding data reception pins to service frames, receive peer service frames and transmit them to protocol units;

[0093] (2) Mode switching: The mode switching instruction of the decision unit is executed to control the sending end to switch between parallel mode and multi-channel concurrent serial mode.

[0094] In the receiving direction of the parallel interface, the service frame is received in parallel interface mode, the initial peer configuration is executed, the peer configuration is reconstructed to realize the mapping of data receiving pins to service frames, and the service frame is sent to the protocol unit.

[0095] In the transmission direction of the parallel interface, the receiving protocol unit sends service frames or management frames. According to the mode switching instruction, when sending service frames, it switches to the parallel interface mode and realizes the mapping of service frames to data transmission pins according to the initial local configuration and the reconfiguration of local configuration. When sending management frames, it switches to the multi-channel concurrent serial mode to realize the mapping of management frames to data transmission pins.

[0096] Preferably, the reconstruction requester and reconstruction responder are determined by the direction of the reconstruction, while the sender and receiver depend only on who sent the current frame. For example, when the reconstruction requester sends a reconstruction request frame, the requester acts as the sender and the responder acts as the receiver; however, when the reconstruction responder sends a reconstruction response frame, the responder acts as the sender and the requester acts as the receiver.

[0097] The protocol unit is used for:

[0098] (1) Service frame processing: The service frames from the execution unit are parsed and verified. If the verification is correct, they are submitted to the data bus. If the verification is incorrect, the service frame is discarded. If the verification finds a persistent error, it indicates that the physical data link in the corresponding direction may be faulty. The fault information of the other end is generated and reported to the decision unit.

[0099] (2) Management frame processing: The management frames identified and reported by the management frame monitoring unit are parsed and verified, and the specific information in the management frames is extracted and reported to the decision unit. The specific information includes: local fault information, reconfiguration of peer configuration, and reconfiguration synchronization confirmation.

[0100] (3) Service frame assembly: The service data of the data bus is assembled into service frames and sent to the execution unit;

[0101] (4) Management frame assembly: Upon receiving the framing instruction from the decision unit (including peer fault information and local configuration reconfiguration), assemble the specified management frame and send it to the execution unit. The management frame includes: reconfiguration request frame, reconfiguration response frame, and reconfiguration synchronization frame.

[0102] The service frame refers to a data interaction frame between other user logic within two parallel interface modules connected by the parallel interface, implemented through the parallel interface modules. During transmission, the parallel interface modules perform integrity checks on the service frames to monitor link quality, but do not parse or modify the user data they carry.

[0103] The management frame includes a fixed frame header for frame delimitation and type identification, and its format differs from that of the service frame to ensure reliable identification in mixed data streams. The management frame is transmitted in a multi-channel concurrent serial mode and received at the other end in a management frame listening unit. It operates between the parallel interface modules of the local and remote ends, is imperceptible to other user logic on both ends, and is used to implement fault tolerance.

[0104] The management frame listening unit includes a set of independent asynchronous serial parsers. Each asynchronous serial parser is directly connected to a corresponding data receiving pin and performs the mapping from the data receiving pin to the management frame. After frame type identification, if it is a valid management frame, it is sent to the protocol unit; otherwise, it is discarded. This enables multi-channel independent listening to potential management frames on all data receiving pins.

[0105] The asynchronous serial parser has a strict frame format verification capability. It only determines that the received data is a valid frame to be reported when it fully conforms to the complete format of the management frame, thereby avoiding accidental triggering during business data transmission.

[0106] In this embodiment, the parallel interface module is a source-synchronous full-duplex architecture, meaning it includes two independent communication directions: transmission and reception. In both communication directions, the transmitting end outputs a source-synchronous clock signal that is strictly phase-aligned with the data signal to be transmitted in the same direction. Specifically, the transmission direction of the parallel interface includes several data transmission pins and at least one clock transmission pin; correspondingly, the reception direction includes several data reception pins and at least one clock reception pin, each corresponding to a pin in the transmission direction of the other end.

[0107] In the transmission direction of this end, the data transmission pin of this end is connected to the data reception pin of the other end through the transmission path (PCB trace, connector, cable) to form a physical data link from this end to the other end; the clock transmission pin of this end is connected to the clock reception pin of the other end through the transmission path to form a physical clock link from this end to the other end.

[0108] In the receiving direction at this end, a physical data link is formed by connecting the data transmit pin at the other end to the data receive pin at this end via a transmission path; a physical clock link is formed by connecting the clock transmit pin at the other end to the clock receive pin at this end via a transmission path. Each physical data link corresponds to a specific pair of data transmit and data receive pins. In a source-synchronous full-duplex architecture, the physical clock and data links in the two communication directions are independent of each other; within the same communication direction, the clock signal and the data signal in that direction are strictly synchronized.

[0109] The effective implementation of the fault-tolerance method described in this embodiment relies on the following premise: both physical clock links in the two communication directions are functioning normally, and at least one physical data link in each communication direction is functioning normally. For extreme fault situations that do not meet the above premises, fault-tolerance processing can be handled by system-level reset or upper-layer software protocol. This module focuses on the hardware autonomous reconfiguration mechanism that meets this premise.

[0110] To facilitate understanding of the mode switching function of the execution unit in the transmission direction in this embodiment, the two operating modes involved and their technical significance are explained below:

[0111] Parallel mode refers to mapping the service frame to be sent to multiple data transmission pins in the transmission direction of the parallel interface. This mode is the normal working mode of the parallel interface.

[0112] Multi-channel concurrent serial mode refers to the following: in the transmission direction of the parallel interface, the management frame to be transmitted is copied to all available data transmission pins, and each pin independently and concurrently transmits the same content in a serial manner.

[0113] The switching between the two modes is controlled by the decision unit through mode switching instructions to control the execution unit: parallel mode is used when transmitting service frames, and multi-channel concurrent serial mode is switched when transmitting management frames.

[0114] The significance of using a multi-channel concurrent serial mode to send management frames is that when only a portion of the physical data link is available due to a failure of the parallel interface, if management frames are still sent in parallel mode, the other end will not be able to receive them correctly due to the lack of bit width. However, the multi-channel concurrent serial mode can copy the same management frame to all available data transmission pins for independent output. As long as there is at least one intact physical data link between the two ends, the management frame can be captured by the management frame listening unit of the other end, thus providing a reliable communication channel for negotiation after the failure.

[0115] Specifically, the parallel interface module described in this embodiment is implemented using hardware logic such as FPGA and ASIC.

[0116] Example 2

[0117] This embodiment provides a fault-tolerant method for data physical link failures based on a parallel interface module, the method comprising:

[0118] S1, Default configuration loaded;

[0119] The decision unit sends the initial local configuration and the initial peer configuration to the execution unit. The execution unit maps the service frame to the corresponding data transmission pin according to the initial local configuration and maps the corresponding data reception pin to the service frame according to the initial peer configuration, and then enters S2.

[0120] S2, Continuous monitoring and fault diagnosis;

[0121] S2.1 The execution unit maintains parallel mode and transmits service frames. During this period, the protocol unit performs dual monitoring: first, it parses and verifies the service frames received from the execution unit; second, it parses the management frames received from the management frame monitoring unit. If it is a reconstruction request frame, it reports the local fault information contained therein to the decision unit.

[0122] Preferably, the service frame transmission specifically includes: in the receiving direction of the parallel interface, the execution unit sends the received service frame to the protocol unit, the protocol unit parses and verifies the service frame, if the verification is correct, the service frame is sent to other user logic through the data bus; if the verification is incorrect, the protocol unit discards the service frame, and if a continuous verification error occurs, it indicates that the physical data link in the corresponding direction may be faulty, so the peer fault information is generated and reported to the decision unit;

[0123] In the transmission direction of the parallel interface, the protocol unit assembles the data on the data bus into service frames and sends them to the execution unit, which then maps the service frames to the corresponding data transmission pins.

[0124] S2.2 The decision-making unit determines its role in the subsequent reconstruction process based on the information reported by the protocol unit. If the received information is a fault message from the peer generated by the local end, it means that the local end has detected a transmission anomaly from the peer, and the local end acts as the reconstruction requester, proceeding to S3. If the received information is a fault message from the peer detected by the local end and sent through a reconstruction request frame, it means that the peer has detected a transmission anomaly from the local end, and the local end acts as the reconstruction responder, proceeding to S4. Figure 2 As shown; if fault information from both the peer and the local end is received simultaneously, the local end shall take priority as the refactoring responder.

[0125] S3. Initiate reconstruction negotiation (this end acts as the reconstruction requester).

[0126] S3.1 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S3.2;

[0127] S3.2 The decision unit issues a framing instruction (including peer fault information) to the protocol unit. The protocol unit generates a reconstruction request frame and sends it to the execution unit. Finally, the execution unit sends the reconstruction request frame to the peer in a multi-channel concurrent serial mode, and then proceeds to S3.3.

[0128] S3.3 The management frame listening unit sends the received reconstruction response frame to the protocol unit for parsing. The protocol unit sends the parsed reconstruction peer configuration to the decision unit, and then proceeds to S3.4.

[0129] S3.4 The decision unit sends a framing instruction (including confirmation information for reconstructing the peer configuration) to the protocol unit. The protocol unit generates a reconstruction synchronization frame and sends it to the execution unit. Finally, the execution unit sends it in a multi-channel concurrent serial mode and enters S3.5.

[0130] S3.5 The decision unit sends a mode switching instruction and reconfigures the peer configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local receiving data receiving pin to the service frame according to the reconfigured peer configuration, and then enters S2.

[0131] S4. Respond to the reconstruction negotiation (this end acts as the reconstruction responder).

[0132] S4.1 The management frame listening unit sends the received reconstruction request frame to the protocol unit for parsing. The protocol unit sends the parsed local fault information to the decision unit, and then proceeds to S4.2.

[0133] S4.2. Based on the fault information and the normal pins on the local end, the decision unit generates a reconfigurable local end configuration and proceeds to S4.3.

[0134] S4.3 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S4.4;

[0135] S4.4 The decision unit sends a framing instruction (including reconstructing the local configuration) to the protocol unit. The protocol unit generates a reconstruction response frame based on the reconstructed local configuration and sends the frame to the execution unit. Finally, the execution unit sends the reconstruction response frame to the peer in a multi-channel concurrent serial mode, and then proceeds to S4.5.

[0136] S4.5 The management frame listening unit sends the received reconstruction synchronization frame to the protocol unit for parsing. The protocol unit reports the result of "reconstruction synchronization confirmation" to the decision unit and proceeds to S4.6.

[0137] S4.6 The decision unit sends a mode switching instruction and reconfigures the local configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local sending service frame to the data sending pin according to the reconfigured local configuration, and then enters S2.

[0138] In this embodiment, the fault-tolerant process corresponding to S1-S4 will remain in S2 without exiting if there are no errors.

[0139] During the reconfiguration negotiation process, the configuration information exchanged by both parties follows the "cross-correspondence" principle. The "reconfiguration local end configuration" generated by the reconfiguration responder is used to guide the pin remapping in its own sending direction (i.e., the receiving direction of the peer end); after this configuration is sent to the reconfiguration requester, it is called the "reconfiguration peer end configuration," which the requester uses to configure its own receiving direction. The reverse is also true. This naming convention clearly defines the source and direction of the configuration.

[0140] Furthermore, the parallel interface module has bidirectional data pins that can be dynamically configured as data receiving pins and data sending pins.

[0141] In the parallel interface module, each data receiving pin is simultaneously connected to the execution unit and the management frame listening unit. The management frame listening unit has n asynchronous serial parsers used to independently listen to the n data receiving pins. The execution unit is used to map the normal pins among the n data receiving pins to service frames, such as... Figure 1 As shown, from data receive pin 1 to data receive pin n.

[0142] In the parallel interface module, each data transmission pin is controlled by an execution unit, such as... Figure 1 As shown, from data transmission pin 1 to data transmission pin n, this unit controls the data transmission pins to switch between parallel mode and multi-channel concurrent serial mode. In parallel mode, it performs the mapping transmission of service frames to data transmission pins, and in multi-channel concurrent serial mode, it performs the mapping transmission of management frames to data transmission pins.

[0143] Optionally, the local configuration and the peer configuration can be reconstructed and written to on-chip or off-chip non-volatile memory as the initial local configuration and initial peer configuration upon the next power-on.

[0144] Optionally, to further improve the reliability of the reconstructed link, after loading the default configuration or completing the reconstruction, a link verification process is executed to confirm the connectivity of the physical data link. Both parties can complete this process by exchanging specific verification frames and confirming the response.

[0145] In the method, the transmission of management frames follows a response priority principle: the transmission priority of link acknowledgment frames is higher than that of link verification frames, and the transmission priority of reconstruction response frames is higher than that of reconstruction request frames, in order to avoid negotiation deadlock.

[0146] Example 3

[0147] This embodiment also provides an electronic device, including:

[0148] At least one processor; and

[0149] The memory stores instructions that, when executed by the at least one processor, cause the at least one processor to perform the wire foreign object detection method based on the improved YOLOv11 as described above.

[0150] In this embodiment, the electronic device may include, but is not limited to: personal computer, server computer, workstation, desktop computer, laptop computer, notebook computer, mobile computing device, smartphone, tablet computer, cellular phone, personal digital assistant (PDA), handheld device, messaging device, wearable computing device, consumer electronic device, etc.

[0151] Example 4

[0152] This embodiment also provides a machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the wire foreign object detection method based on the improved YOLOv11 as described above.

[0153] Specifically, a system or apparatus equipped with a readable storage medium may be provided, on which software program code implementing the functions of any of the embodiments described above is stored, and the computer or processor of the system or apparatus can read and execute the instructions stored in the readable storage medium.

[0154] In this case, the program code read from the readable medium itself can perform the functions of any of the above embodiments, and therefore the machine-readable code and the readable storage medium storing the machine-readable code constitute a part of this specification.

[0155] Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer or the cloud via a communication network.

[0156] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0157] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0158] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0159] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0160] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the technical solutions of the present invention, and are not intended to limit the specific implementation of the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the claims of the present invention should be included within the protection scope of the claims of the present invention.

Claims

1. A parallel interface module for connecting two user terminals to achieve interaction, each user terminal being implemented via FPGA / ASIC, characterized in that, The parallel interface module interacts with other user logic within the FPGA / ASIC via a data bus, including: a decision unit, an execution unit, a protocol unit, and a management frame listening unit; The decision-making unit is used for: Issue the initial local configuration and initial peer configuration to the execution unit; Receive information reported by the protocol unit, arbitrate based on the reported information and built-in rules, and confirm the local role as the refactoring requester or the refactoring responder; When acting as a refactoring responder during the refactoring process, generate the refactoring local configuration; or when acting as a refactoring requester during the refactoring process, receive the refactoring peer configuration; issue mode switching instructions and configuration loading instructions to the execution unit. The protocol unit sends a framing command to drive the transmission of reconstruction request frames, reconstruction response frames, and reconstruction synchronization frames; The execution unit is used for: Configuration loading and mapping are performed based on service frames and management frames: initial local configuration and local configuration reconstruction are executed, service frames and management frames of the protocol unit are received, and the mapping of service frames or management frames to corresponding data transmission pins is realized; initial peer configuration and peer configuration reconstruction are executed, the mapping of corresponding data reception pins to service frames is realized, and service frames of the peer are received and transmitted to the protocol unit. The execution decision unit executes mode switching instructions to control the transmitting end to switch between parallel mode and multi-channel concurrent serial mode; The protocol unit is used for: The service frames from the execution unit are parsed and verified. If the verification is correct, they are submitted to the data bus. If the verification fails, the service frames are discarded. If the verification finds a persistent error, it indicates that the physical data link in the corresponding direction may be faulty. The fault information of the other end is generated and reported to the decision unit. The management frames identified and reported by the management frame monitoring unit are parsed and verified, and the specific information in the management frames is extracted and reported to the decision unit. The service data from the data bus is assembled into service frames and sent to the execution unit; Upon receiving the framing instruction and related information from the decision-making unit, assemble the specified management frame and send it to the execution unit; The management frame listening unit includes a set of independent asynchronous serial parsers. Each asynchronous serial parser is directly connected to a corresponding data receiving pin and performs the mapping from the data receiving pin to the management frame. After frame type identification, if it is a valid management frame, it is sent to the protocol unit; otherwise, it is discarded. This enables multi-channel independent listening to potential management frames on all data receiving pins.

2. The parallel interface module according to claim 1, characterized in that, The information reported by the receiving protocol unit used for arbitration includes: Peer fault information: It originates from an abnormal verification of the received service data, indicating that the physical data link in the receiving direction of this end may be faulty. Ultimately, it is necessary to send peer fault information to the peer end through a reconstruction request frame. Local fault information: obtained by parsing the received reconstruction request frame, indicating that the physical data link in the local transmission direction may be faulty.

3. A parallel interface module according to claim 1, characterized in that, The built-in rules for arbitration include: First arbitration condition: If the received information is a fault message generated by the local end, i.e., the local end detects an abnormal transmission from the peer end, then the local end shall be the party requesting the reconstruction. Second arbitration condition: If the received information is a fault message detected by the peer and sent through a reconstruction request frame, i.e., the peer detected an abnormality in the transmission of this end, then this end shall act as the reconstruction responder. Conflict arbitration rule: If both fault information from the other end and fault information from the local end are received simultaneously, the local end shall take precedence as the reconstructing responder.

4. A parallel interface module according to claim 1, characterized in that, The control transmitter switches between parallel mode and multi-channel concurrent serial mode, specifically as follows: In the receiving direction of the parallel interface, the service frame is received in parallel interface mode, the initial peer configuration is executed, the peer configuration is reconstructed to realize the mapping of data receiving pins to service frames, and the service frame is sent to the protocol unit. In the transmission direction of the parallel interface, the receiving protocol unit sends service frames or management frames. According to the mode switching instruction, when sending service frames, it switches to the parallel interface mode and realizes the mapping of service frames to data transmission pins according to the initial local configuration and the reconfiguration of local configuration; when sending management frames, it switches to the multi-channel concurrent serial mode to realize the mapping of management frames to data transmission pins. Parallel mode refers to mapping the service frame to be sent to multiple data transmission pins in the transmission direction of the parallel interface. This mode is the normal working mode of the parallel interface. Multi-channel concurrent serial mode refers to the following: in the transmission direction of the parallel interface, the management frame to be transmitted is copied to all available data transmission pins, and each pin independently and concurrently transmits the same content in a serial manner.

5. A fault-tolerant method for data physical link failures based on a parallel interface module, characterized in that, The method includes: S1. The decision unit sends the initial local configuration and the initial peer configuration to the execution unit. The execution unit implements the mapping of service frames to the corresponding data transmission pins according to the initial local configuration and the mapping of the corresponding data reception pins to the service frames according to the initial peer configuration, and then proceeds to S2. S2. Continuous monitoring and fault diagnosis: S2.1 The execution unit maintains parallel mode and transmits service frames. During this period, the protocol unit performs dual monitoring: first, it verifies the service frames received from the execution unit; second, it parses the management frames received from the management frame monitoring unit. If it is a reconstruction request frame, it reports the local fault information contained therein to the decision unit. S2.2 The decision-making unit determines its role in the subsequent reconstruction process based on the information reported by the protocol unit. If the received information is fault information generated by the peer, the unit acts as the reconstruction requester and proceeds to S3. If the received information is fault information detected by the peer and sent through a reconstruction request frame, the unit acts as the reconstruction responder and proceeds to S4. If both peer fault information and local fault information are received, the unit takes priority as the reconstruction responder. S3. Initiate reconstruction negotiation, i.e., this end acts as the reconstruction requester: S3.1 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S3.2; S3.2 The decision unit issues a framing instruction to the protocol unit. The protocol unit generates a reconstruction request frame and sends it to the execution unit. Finally, the execution unit sends it in a multi-channel concurrent serial mode and enters S3.

3. S3.3 The management frame listening unit sends the received reconstruction response frame to the protocol unit for parsing. The protocol unit sends the parsed reconstruction peer configuration to the decision unit, and then proceeds to S3.

4. S3.4 The decision unit sends a framing instruction to the protocol unit. The protocol unit generates a reconstructed synchronization frame and sends it to the execution unit. Finally, the execution unit sends it in a multi-channel concurrent serial mode and enters S3.

5. S3.5 The decision unit sends a mode switching instruction and reconfigures the peer configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local receiving data receiving pin to the service frame according to the reconfigured peer configuration, and then enters S2. S4, Responding to the reconstruction negotiation, i.e., this end acts as the reconstruction responder: S4.1 The management frame listening unit sends the received reconstruction request frame to the protocol unit for parsing. The protocol unit sends the parsed local fault information to the decision unit, and then proceeds to S4.

2. S4.

2. Based on the fault information and the normal pins on the local end, the decision unit generates a reconfigurable local end configuration and proceeds to S4.

3. S4.3 The decision unit sends a mode switching command to the execution unit, and the execution unit switches the interface to multi-channel concurrent serial mode, then proceeds to S4.4; S4.4 The decision unit sends a framing instruction to the protocol unit. The protocol unit generates a reconstruction response frame based on the local reconstruction configuration and sends the frame to the execution unit. Finally, the execution unit sends the frame in a multi-channel concurrent serial mode and enters S4.

5. S4.5 The management frame listening unit sends the received reconstruction synchronization frame to the protocol unit for parsing. The protocol unit reports the "reconstruction synchronization confirmation" result to the decision unit and proceeds to S4.

6. S4.6 The decision unit sends a mode switching instruction and reconfigures the local configuration to the execution unit. The execution unit switches the sending end to parallel mode and maps the local sending service frames to the data sending pins according to the reconfigured local configuration, and then enters S2.

6. The fault-tolerant method for data physical link failures based on a parallel interface module according to claim 5, characterized in that, The transmission of service frames specifically includes: In the receiving direction of the parallel interface, the execution unit sends the received service frame to the protocol unit. The protocol unit parses and verifies the service frame. If the verification is correct, the service frame is sent to other user logic through the data bus. If the verification fails, the protocol unit discards the service frame. At the same time, if a persistent verification error occurs, it indicates that the physical data link in the corresponding direction may be faulty. In this case, the peer fault information is generated and reported to the decision unit. In the transmission direction of the parallel interface, the protocol unit assembles the data on the data bus into service frames and sends them to the execution unit, which then maps the service frames to the corresponding data transmission pins.

7. A fault-tolerant method for data physical link failures based on a parallel interface module according to claim 5, characterized in that, Each data receive pin is simultaneously connected to the execution unit and the management frame listening unit. The n asynchronous serial parsers of the management frame listening unit are used to independently listen to the n data receive pins. The execution unit is used to map the normal pins among the n data receive pins to the service frames.

8. A fault-tolerant method for data physical link failures based on a parallel interface module according to claim 6, characterized in that, Each data transmission pin is controlled by an execution unit that switches between parallel mode and multi-channel concurrent serial mode. In parallel mode, the service frame is mapped to the data transmission pin, and in multi-channel concurrent serial mode, the management frame is mapped to the data transmission pin.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory that stores instructions that, when executed by the at least one processor, cause the at least one processor to perform the method as described in any one of claims 5 to 8.

10. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores executable instructions that, when executed, cause the machine to perform the method as described in any one of claims 5 to 8.

Images