Double 2-vote-2 security platform communication board and remote calling and data transceiving method thereof

By designing a remotely invoked two-by-two secure platform communication board, a layered architecture and remote invocation method are adopted. This solves the problems of inconsistent implementation and cumbersome configuration of traditional communication boards, and achieves flexible adaptation and real-time configuration to meet the needs of changing network environments.

CN121585490APending Publication Date: 2026-02-27卡斯柯信号(成都)有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511654022.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-11-12
Publication Date
2026-02-27

AI Technical Summary

Technical Problem

Traditional two-out-of-two security platform communication boards have inconsistent implementation methods, cumbersome configuration processes, and cannot meet the needs of application scenarios with real-time changes in network environment.

Method used

Design a remote, real-time callable 2x2 secure platform communication board. It adopts a layered architecture, including a device layer, a protocol layer, and a platform interface layer, and provides remote call and data transmission and reception methods to achieve flexible adaptation and real-time configuration of the communication board.

Benefits of technology

It simplifies the platform configuration process, improves the flexibility and scalability of the communication board, adapts to different hardware architectures, and meets the real-time changing needs of the network environment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121585490A_ABST
    Figure CN121585490A_ABST
Patent Text Reader

Abstract

The invention discloses a double 2-vote-2 safety platform communication board and a remote calling and data receiving and transmitting method thereof, and relates to the technical field of rail transit signals.The double 2-vote-2 safety platform comprises an operation board and a communication board which communicate with each other, an application module runs on the operation board, and the communication board comprises a device layer, a protocol layer and a platform interface layer; the equipment layer is responsible for managing all external communication interfaces on the communication board and providing an interface configuration function and a channel creation function; the protocol layer is responsible for processing a communication state and communication data, the protocol layer is used for processing channels registered to the protocol layer in advance, and input and output data of unregistered channels are directly forwarded; and the platform interface layer is responsible for processing data interaction with the operation board. Compared with a traditional communication board, the communication board is clearer in structure, more comprehensive in function and capable of being matched with communication boards of different hardware architectures. And the communication board can be used without being configured in advance, so that the complexity of platform configuration is reduced, and the use is more flexible.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the field of rail transit signal technology, and more particularly to a two-by-two voting safety platform communication board and a remote calling and data transceiving method thereof. BACKGROUND

[0002] The two-by-two voting safety platform is widely used in the field of rail transit signal, and the specific application logic is realized on the basis of the safety platform. The two-by-two voting safety platform is generally divided into an operation board and a communication board. The operation board realizes the input and output consistency comparison function of data, and the communication board realizes the data transceiving function of network, serial port, CAN, SPI and other communication interfaces. The operation board and the communication board interact with each other through internal network or bus and the like.

[0003] The implementation modes of the communication boards of traditional two-by-two voting safety platforms are different. The implementation modes of the communication boards of wayside safety platforms and on-board safety platforms are different. Even the implementation modes of the communication boards of different versions of the same safety platform are different. However, the basic functions of the communication boards are unchanged. Therefore, a same communication board architecture can be designed to adapt to different safety platforms. At the same time, the communication board of the traditional two-by-two voting safety platform needs to be configured in advance during running. Moreover, these configurations need to be calculated in advance according to the actual communication scene. This not only makes the configuration process of the platform cumbersome, but also cannot meet some network environment real-time change application scenarios. SUMMARY

[0004] In order to overcome the defects existing in the prior art, the present application discloses a two-by-two voting safety platform communication board and a remote calling and data transceiving method thereof. The purpose of the present application is to solve the problems existing in the traditional two-by-two voting safety platform communication board in the prior art, such as different implementation modes, cumbersome configuration process of the platform, and inability to meet some network environment real-time change application scenarios. The present application designs a two-by-two voting safety platform communication board which can be remotely and real-time called. The communication board becomes a real-time callable service, and is no longer constrained by architecture and configuration.

[0005] In order to achieve the above purpose, the technical scheme adopted by the present application is as follows: In a first aspect, the present application provides a two-by-two voting safety platform communication board. The two-by-two voting safety platform includes an operation board and a communication board which communicate with each other. An application module runs on the operation board. The communication board includes a device layer, a protocol layer and a platform interface layer, wherein: The device layer is responsible for managing all external communication interfaces on the communication board, and provides interface configuration function and channel creation function; The protocol layer is responsible for handling communication status and data, including establishing a secure connection with external devices, parsing input data from external devices according to protocol specifications, and packaging application output data from the operation board according to protocol specifications. The protocol layer processes channels that have been registered in advance, and unregistered channels will have their input and output data directly forwarded. The platform interface layer is responsible for handling data interaction between the operation board, including parsing call commands from application modules, calling related service interfaces of the device layer and the protocol layer, forwarding output data of the application module to the protocol layer, forwarding input data processed by the protocol layer to the operation board, forwarding all channel states to the operation board, and forwarding all interface states to the operation board.

[0006] Preferably, the functions provided by the device layer are called through the following service interfaces: Open communication interface: openAdapter; Close communication interface: closeAdapter; Create communication channel: createChannel; Close communication channel: destroyChannel; Send communication data: writeData.

[0007] Preferably, the functions provided by the protocol layer are called through the following service interfaces: Register communication protocol: registerProtocol; Periodic processing logic: cycleProcess; Parse communication data: decodeData; Package communication data: encodeData.

[0008] Preferably, the functions provided by the platform interface layer are called through the following service interfaces: Upload communication data: uploadData; Upload channel state: uploadChannelState; Upload interface state: uploadAdapterState; Upload protocol state: uploadProtocolState.

[0009] Preferably, the communication board enters initialization after power-on, and the initialization includes: The device layer initializes all communication interfaces and creates various receiving tasks corresponding to the communication interfaces; The protocol layer loads all protocol modules by extending library or code integration, and creates protocol cycle processing task; The platform interface layer registers to the platform bus, and creates receiving task of bus data.

[0010] Preferably, after the communication board enters normal operation state, the application module on the operation board sends remote call command to the communication board through bus, and the communication board and the operation board include three communication interfaces, namely ADAPTER interface, CHANNEL interface and DATA interface. The application module configures parameters of specified communication interface on the communication board through the ADAPTER interface; The application module notifies the communication board to create communication channel through the CHANNEL interface; The application module sends channel data to the communication board through the DATA interface.

[0011] Preferably, the data frame format used by the ADAPTER interface is as follows:

[0012] Among them: Adapter ID represents the number corresponding to network port, serial port, CAN, SPI interface on the communication board; Operate represents opening or closing interface operation; When Operate is opening, Parameter represents the parameters corresponding to the interface; When Operate is opening, the platform interface layer will call the device layer openAdapter interface to open the corresponding interface; When Operate is closing, the platform interface layer will call the device layer closeAdapter to close the corresponding interface.

[0013] Preferably, the data frame format used by the CHANNEL interface is as follows:

[0014] Among them: Session ID represents session ID, and all channels opened on the communication board have unique Session ID; Operate represents creating or closing channel, and only when Operate is creating channel, the subsequent fields of the command exist, otherwise the command only includes Session ID and Operate two fields; Adapter ID represents the communication interface based on which the channel is created, which is consistent with the ADAPTER interface; Interface represents the type of communication interface, including TCP, UDP, serial port, CAN, SPI; When the highest bit of Interface is 1, Parameter1 field exists, indicating the parameters related to Interface; When the highest bit of Interface is 0, Parameter1 field does not exist; Protocol represents the protocol module that the channel needs to be associated with; When the highest bit of Protocol is 1, Parameter2 field exists, indicating the parameters related to Protocol; When the highest bit of Protocol is 0, Parameter2 field does not exist; Role represents the communication role, including client and server roles, and this field only takes effect when Interface is TCP; Parameter3 is an optional field; When Operate is create, the platform interface layer will call the device layer createChannel interface to create the corresponding channel; When Operate is close, the platform interface layer will call the device layer destroyChannel interface to close the corresponding channel; When Protocol is not 0, the platform interface layer will call the protocol layer registerProtocol interface to bind the channel with the corresponding protocol module.

[0015] Preferably, the data frame format used by the DATA interface is as follows;

[0016] Among them: Session ID represents the session ID, and the communication board finds the corresponding channel through Session ID; Length represents the data length; Data Content represents the data content; After receiving the DATA message, the platform interface layer will call the protocol layer encodeData interface for protocol encapsulation, and then the protocol layer will call the device layer writeData to send data to the external device.

[0017] Preferably, the communication board protocol layer task real-time calls the cycleProcess interface of the registered protocol module to handle periodic tasks and collects the state of each protocol module, and calls the platform interface layer uploadProtocolState interface to send the protocol state to the operation board. The communication board device layer task reads peripheral device data in real time, and if the data reading is successful, a decodeData interface of the protocol layer is called to parse the data, and after the protocol layer parses the data, an uploadData interface of the platform interface layer is called to send the peripheral device data to the operation board; The communication board device layer task judges whether the communication interface state changes, or collects all communication interface states at the end of each reading period, and calls an uploadAdapterState interface of the platform interface layer to send the communication interface state to the operation board; The communication board device layer task judges whether the channel state changes, or collects all channel states at the end of each reading period, and calls an uploadChannelState interface of the platform interface layer to send the channel state to the operation board; The application module on the operation board judges whether the communication interface is successfully opened according to the communication interface state, judges whether the channel is successfully created or the connection is normal according to the channel state, and judges whether the protocol communication process is normal according to the protocol state.

[0018] In the second aspect, based on the above two two-out-of-two safety platform communication board, the application further provides a remote calling method of a two two-out-of-two safety platform communication board, comprising the following steps: After the communication board is successfully initialized, the application module on the operation board sends an interface configuration command to the communication board using an ADAPTER message; The platform interface layer of the communication board receives the ADAPTER message and calls a device layer openAdapter service to configure the related interface; If the interface configuration is successful, the device layer calls an uploadAdapterState service of the platform interface layer to send the interface configuration success state to the application module; If the interface configuration fails, the device layer adds the interface configuration command to the interface management queue and performs periodic repeated execution until the interface configuration is successful or the application module actively closes the interface; After the interface configuration is successful, the application module on the operation board sends a create channel command to the communication board using a CHANNEL message; The platform interface layer of the communication board receives the CHANNEL message and calls a createChannel service of the device layer to create the corresponding channel; The platform interface layer of the communication board receives the CHANNEL message and calls a registerProtocol service of the protocol layer to bind the channel number with the related protocol module; If the channel creation is successful, the device layer calls an uploadChannelState service of the platform interface layer to send the channel creation success state to the application module; If the channel creation fails, the device layer adds the channel creation command to the channel management queue and periodically repeats the execution until the channel creation succeeds or the application module actively destroys the channel.

[0019] In a third aspect, based on the two-out-of-two security platform communication board, the application further provides a data receiving and sending method of the two-out-of-two security platform communication board, comprising the following steps: After the channel creation succeeds, the application module on the operation board sends the application data to be output to the communication board using a DATA message; After the communication board platform interface layer receives the DATA message, the protocol layer encodeData service is called to protocol encapsulate the application data; The protocol layer judges whether the channel is bound with a certain protocol module, if yes, the protocol module is called to perform the packet processing, and the processed data is sent to the external device by calling the device layer writeData service, if not, the device layer writeData service is directly called to send the data to the external device; The receiving task of each interface of the device layer reads the data of each channel in real time, after successfully reading the data of the external device, the protocol layer decodeData service is called to perform the protocol unpacking; The protocol layer judges whether the channel is bound with a certain protocol module, if yes, the protocol module is called to perform the unpacking processing, and the processed data is sent to the operation board by calling the platform interface layer uploadData service, if not, the platform interface layer uploadData service is directly called to send the data to the operation board; The device layer periodically collects the states of each communication interface, and calls the platform interface layer uploadAdapterState service to send the interface states to the operation board; The device layer periodically collects the states of each communication channel, and calls the platform interface layer uploadChannelState service to send the channel states to the operation board; The protocol layer periodically calls the cycleProcess interface to process the periodic tasks of each protocol module, and collects the protocol states, and calls the platform interface layer uploadProtocolState service to send the protocol states to the operation board.

[0020] The application has the following beneficial effects: The application provides a communication board layered design method, compared with the traditional communication board, the structure is clearer, the function is more comprehensive, and the communication board can be adapted to different hardware architectures.

[0021] The application designs a communication board remote calling method, so that the communication board can be used without early configuration, which not only reduces the complexity of platform configuration, but also is more flexible and has stronger expansibility. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 The figure is a layered structure diagram of the communication board of the application; Figure 2 The figure is a power-on initialization flowchart of the communication board of the application; Figure 3 The figure is an opening communication interface and creating communication channel flowchart of the application; Figure 4 The figure is a sending application data and uploading state message flowchart of the application. DETAILED DESCRIPTION

[0023] The application will be described below in combination with embodiments and drawings to make the concept, specific structure and generated technical effects of the application clear, complete, so as to fully understand the purpose, features and effects of the application.

[0024] A two-by-two voting security platform communication board, specifically as follows: 1. The two-by-two voting security platform is composed of an operation board, a communication board and other IO board cards, the operation board runs an application module, the communication board runs a communication module, and the operation board and the communication board communicate through a bus; 2. The communication module on the communication board is composed of three parts, namely a device layer, a protocol layer and a platform interface layer, each layer is responsible for different functions, and these functions can be called through the service interface provided by each layer.

[0025] 3. The device layer is responsible for managing all external communication interfaces on the communication board, including network ports, serial ports, CAN, SPI interfaces, etc., providing interface configuration functions and channel creation functions, such as configuring network port addresses, creating TCP server and client channels, creating UDP channels, creating serial port channels, and generating channel states, the functions provided by the device layer are called through the following service interfaces; Opening communication interface: openAdapter(adapterID, paramter); Closing communication interface: closeAdapter(adapterID); Creating communication channel: createChannel(adapterID, interface, paramter1, role, paramter2); Closing communication channel: destroyChannel(sessionID); Send communication data: writeData(sessionID, data, length); 4. The protocol layer is responsible for handling communication status and communication data, including establishing a secure connection with the external device, parsing the input data from the external device according to the protocol specification, and packaging the application output data from the operation board according to the protocol specification. The protocol layer only processes channels that have been registered in advance, and the input and output data of unregistered channels will be directly forwarded. The functions provided by the protocol layer are called through the following service interfaces; Register communication protocol: registerProtocol(sessionID, protocol, parameter); Periodic processing logic: cycleProcess(); Parse communication data: decodeData(sessionID, data, length); Package communication data: encodeData(sessionID, data, length); 5. The platform interface layer is responsible for handling data interaction between the operation board and the application module, including parsing the call command from the application module, calling the relevant service interfaces of the device layer and the protocol layer, forwarding the output data of the application module to the protocol layer, forwarding the input data processed by the protocol layer to the operation board, forwarding all channel states to the operation board, and forwarding all interface states to the operation board. The functions provided by the platform interface layer are called through the following service interfaces; Upload communication data: uploadData(sessionID, data, length); Upload channel state: uploadChannelState(channelState); Upload interface state: uploadAdapterState(adapterState); Upload protocol state: uploadProtocolState(protocolState); 6. After the communication board is powered on, the functions of each layer are initialized first. The device layer initializes all communication interfaces and creates various communication interface receiving tasks. The protocol layer loads all protocol modules through extension library or code integration and creates protocol cycle processing tasks. The platform interface layer is registered on the platform bus and creates bus data receiving tasks; 7. After the communication board enters the normal running state, the application module on the operation board can send remote call commands to the communication board through the bus. The communication board and the operation board contain ADAPTER, CHANNEL, and DATA three kinds of communication interfaces.

[0026] 7.1 Application module configures the parameters of the specified communication interface on the communication board through the ADAPTER interface, and the data frame format used by the ADAPTER interface is as follows:

[0027] Wherein: Adapter ID represents the number corresponding to the network port, serial port, CAN, SPI interface on the communication board; Operate represents the opening or closing of the interface operation; When Operate is open, Parameter represents the parameters corresponding to the interface, for example, when Adapter ID is a certain network port, Parameter includes: network address (IP address), subnet mask (Subset mask), gateway (Gateway) and other fields; When Operate is open, the platform interface layer will call the device layer openAdapter interface to open the corresponding interface; When Operate is closed, the platform interface layer will call the device layer closeAdapter to close the corresponding interface; 7.2 Application module notifies the communication board to create a communication channel through the CHANNEL interface, and the data frame format used by the CHANNEL interface is as follows:

[0028] Wherein: Session ID represents the session ID, and all channels opened on the communication board have a unique Session ID; Operate represents the creation or closing of the channel, and only when Operate is create channel, the subsequent fields of the command exist, otherwise the command only contains Session ID and Operate two fields; Adapter ID represents the communication interface based on which the channel is created, which is consistent with the ADAPTER interface; Interface represents the communication interface type, including TCP, UDP, serial port, CAN, SPI, etc.; When the highest bit of Interface is 1, Parameter1 field exists, which represents Interface related parameters, for example, when Interface is TCP interface, Parameter1 can represent the configuration of TCP related parameters, such as retransmission timeout, configuration of keep-alive parameters, etc. When the highest bit of Interface is 0, Parameter1 field does not exist; Protocol indicates the protocol module that the channel needs to be associated with; When the highest bit of Protocol is 1, Parameter2 field exists, indicating the protocol related parameters, for example, when Protocol is RSSP-I protocol, Parameter2 can indicate the SID, SINIT and other parameters of RSSP-I protocol; When the highest bit of Protocol is 0, Parameter2 field does not exist; Role indicates the communication role, including client and server roles, and this field only takes effect when Interface is TCP; Parameter3 is an optional field, for example, when Interface is TCP or UDP, Parameter3 can include local communication address and remote communication address and other fields.

[0029] When Operate is create, the platform interface layer will call the device layer createChannel interface to create the corresponding channel; When Operate is close, the platform interface layer will call the device layer destroyChannel interface to close the corresponding channel; When Protocol is not 0, the platform interface layer will call the protocol layer registerProtocol interface to bind the channel with the corresponding protocol module; 7.3 The application module sends channel data to the communication board through the DATA interface, and the data frame format used by the DATA interface is as follows:

[0030] Among them: Session ID indicates the session ID, and the communication board finds the corresponding channel through the Session ID; Length indicates the data length; Data Content indicates the data content; After receiving the DATA message, the platform interface layer will call the protocol layer encodeData interface for protocol encapsulation, and then the protocol layer calls the device layer writeData to send data to the external device.

[0031] 8、Communication board protocol layer task calls cycleProcess interface of registered protocol module to handle some periodic tasks such as connection timeout processing, timing calculation, etc., and collects states of each protocol module, and calls uploadProtocolState interface of platform interface layer to send protocol states to operation board; 9、Communication board device layer task reads channel data in real time, and if reading data is successful, decodeData interface of protocol layer is called to analyze data, and after protocol layer analyzes data, uploadData interface of platform interface layer is called to send data to operation board; 10、Communication board device layer task judges that communication interface state changes, or collects all communication interface states at the end of each reading period, and calls uploadAdapterState interface of platform interface layer to send communication interface states to operation board; 11、Communication board device layer task judges that channel state changes, or collects all channel states at the end of each reading period, and calls uploadChannelState interface of platform interface layer to send channel states to operation board; 12、Application module on operation board judges whether communication interface is successfully opened according to communication interface state, judges whether channel is successfully created or connection is normal according to channel state, and judges whether protocol communication process is normal according to protocol state.

[0032] Reference Figure 1 Communication function module on communication board is divided into three layers in structure, which are platform interface layer, protocol layer and device layer.

[0033] Reference Figure 2 After communication board is powered on, initialization process is entered, which includes the following steps: Step 100, device layer checks states of all network ports, serial ports, CAN and SPI interfaces, and creates a receiving task for each type of interface, and after interface state check is passed and receiving task creation is successful, step 101 is entered, otherwise device layer will repeat initialization process until initialization is successful; Step 101, protocol layer loads all protocol extension library interfaces, and creates periodic timing task, and after initialization is successful, step 102 is entered, otherwise protocol layer will repeat initialization process until initialization is successful; Step 102, platform interface layer registers communication board to platform internal bus, and starts bus receiving task, and after initialization is successful, communication board starts to provide services to security platform, otherwise platform interface layer will repeat initialization process; Reference Figure 3 Remote calling method of communication board interface configuration and channel creation is introduced, which includes the following steps: Step 103: After the communication board is successfully initialized, the application module on the computing board uses the ADAPTER message to send an interface configuration command to the communication board. Step 104: After receiving the message, the communication board platform interface layer calls the device layer openAdapter service to configure the relevant interfaces, such as configuring the local IP address, subnet mask and default gateway parameters of the specified network port. Step 105: If the interface configuration is successful, the device layer calls the platform interface layer's uploadAdapterState service to send the successful interface configuration status to the application module. Step 106: If the interface configuration fails, the device layer adds the interface configuration command to the interface management queue and executes it repeatedly periodically until the interface configuration is successful or the application module actively closes the interface. Step 107: After successful interface configuration, the application module on the computing board sends a channel creation command to the communication board using a CHANNEL message; Step 108: After receiving the message, the communication board platform interface layer calls the device layer createChannel service to create the corresponding channel, such as creating a TCP client channel on a certain network interface. Step 109: After receiving the message, the communication board platform interface layer calls the protocol layer's registerProtocol service to bind the channel number with the relevant protocol module, such as binding the channel with the SNMP protocol. Step 110: If the channel is created successfully, the device layer calls the platform interface layer uploadChannelState service to send the channel creation success status to the application module. Step 111: If channel creation fails, the device layer adds the channel creation command to the channel management queue and executes it repeatedly periodically until the channel is successfully created or the application module actively destroys the channel. refer to Figure 4 This paper introduces the methods for data transmission and reception processing on the communication board, including the following steps: Step 112: After the channel is successfully created, the application module on the computing board uses the DATA message to send the application's output data to the communication board. Step 113: After receiving the message, the communication board platform interface layer calls the protocol layer's encodeData service to encapsulate the application data using the protocol. Step 114: The protocol layer determines whether the channel is bound to a certain protocol module. If it is bound, the protocol module is called to perform packet processing, and the processed data is sent to the external device by calling the device layer's writeData service. If the channel is not bound to any protocol module, the protocol layer directly calls the device layer's writeData service to send the data to the external device. Step 115, the receiving task of each interface of the device layer reads the data of each channel in real time, and after successfully reading the data of the external device, calls the decodeData service of the protocol layer to perform protocol unpacking; Step 116, the protocol layer judges whether the channel is bound to a certain protocol module, if bound, calls the protocol module to perform unpacking processing, and sends the processed data to the operation board by calling the uploadData service of the platform interface layer, if the channel is not bound to any protocol module, the protocol layer directly sends the data to the operation board by calling the uploadData service of the platform interface layer; Step 117, the device layer periodically collects the states of each communication interface, and sends the states to the operation board by calling the uploadAdapterState service of the platform interface layer; Step 118, the device layer periodically collects the states of each communication channel, and sends the states to the operation board by calling the uploadChannelState service of the platform interface layer; Step 119, the protocol layer periodically calls the cycleProcess interface to process the periodic tasks of each protocol module, and collects the states of each protocol, and sends the states to the operation board by calling the uploadProtocolState service of the platform interface layer.

[0034] The above describes the embodiments of the present application, but the present application is not limited to the above-mentioned embodiments, and those skilled in the art can make various equivalent modifications or replacements without departing from the spirit of the present application, and these equivalent modifications or replacements are all included in the scope defined by the claims of the present application.

Claims

1. A two-out-of-two secure platform communication board, characterized in that, The two-out-of-two secure platform includes a computing board and a communication board that communicate with each other. The computing board runs an application module, and the communication board includes a device layer, a protocol layer, and a platform interface layer, wherein: The device layer is responsible for managing all external communication interfaces on the communication board and provides interface configuration and channel creation functions. The protocol layer is responsible for handling communication status and communication data, including establishing a secure connection with external devices, parsing input data from external devices according to protocol specifications, and assembling application output data from the computing board according to protocol specifications. The protocol layer processes channels that have been pre-registered with the protocol layer, while the input and output data of unregistered channels will be directly forwarded. The platform interface layer is responsible for handling data interaction with the computing board, including parsing call commands from application modules, calling relevant service interfaces of the device layer and protocol layer, forwarding output data of application modules to the protocol layer, forwarding input data processed by the protocol layer to the computing board, forwarding all channel statuses to the computing board, and forwarding all interface statuses to the computing board.

2. The two-out-of-two secure platform communication board as described in claim 1, characterized in that, The device layer provides the following function call service interfaces: open communication interface: openAdapter; close communication interface: closeAdapter; create communication channel: createChannel; close communication channel: destroyChannel; send communication data: writeData; The protocol layer provides the following functional call service interfaces: registerProtocol; cycleProcess; decodeData; encodeData; and encodeData. The platform interface layer provides the following function call service interfaces: upload communication data: uploadData; upload channel status: uploadChannelState; upload interface status: uploadAdapterState; upload protocol status: uploadProtocolState.

3. The two-out-of-two secure platform communication board as described in claim 1, characterized in that, The communication board enters initialization after power-on, and the initialization includes: The device layer initializes all communication interfaces and creates receiving tasks corresponding to various communication interfaces; The protocol layer loads all protocol modules through extension libraries or code integration and creates protocol cycle processing tasks; The platform interface layer registers with the platform bus and creates a task to receive bus data.

4. The two-out-of-two secure platform communication board as described in claim 1, characterized in that, After the communication board enters normal operation, the application modules on the computing board send remote call commands to the communication board via the bus. The communication board and the computing board have three communication interfaces: ADAPTER, CHANNEL, and DATA. The application module configures the parameters of a specified communication interface on the communication board through the ADAPTER interface; The application module notifies the communication board to create a communication channel via the CHANNEL interface; The application module sends channel data to the communication board through the DATA interface.

5. The two-out-of-two secure platform communication board as described in claim 4, characterized in that, The data frame format used by the ADAPTER interface is as follows: in: The Adapter ID represents the number corresponding to the network port, serial port, CAN, and SPI interface on the communication board. Operate indicates an operation to open or close the interface; When Operate is enabled, Parameter represents the parameters corresponding to the interface; When Operate is enabled, the platform interface layer will call the device layer's openAdapter interface to open the corresponding interface; When Operate is off, the platform interface layer will call the device layer closeAdapter to close the corresponding interface.

6. The two-out-of-two secure platform communication board as described in claim 4, characterized in that, The data frame format used by the CHANNEL interface is as follows: in: Session ID represents the session ID; all channels opened on the communication board have a unique Session ID. Operate indicates the creation or closure of a channel. The subsequent fields of this command only exist when Operate is used to create a channel; otherwise, the command only contains the Session ID and Operate fields. The Adapter ID indicates the communication interface on which the channel is created, and it should be consistent with the ADAPTER interface. Interface indicates the type of communication interface, including TCP, UDP, serial port, CAN, and SPI; When the highest bit of the Interface is 1, the Parameter1 field exists, indicating the Interface-related parameters; When the highest bit of the Interface is 0, the Parameter1 field does not exist; Protocol indicates the protocol module that the channel needs to be associated with; When the highest bit of Protocol is 1, the Parameter2 field exists, indicating Protocol-related parameters; When the highest bit of Protocol is 0, the Parameter2 field does not exist; Role indicates the communication role, including client and server roles. This field is only effective when Interface is TCP. Parameter3 is an optional field; When Operate is created, the platform interface layer will call the device layer's createChannel interface to create the corresponding channel; When Operate is off, the platform interface layer will call the device layer's destroyChannel interface to close the corresponding channel; When Protocol is not 0, the platform interface layer will call the protocol layer's registerProtocol interface to bind the channel to the corresponding protocol module.

7. The two-out-of-two secure platform communication board as described in claim 4, characterized in that, The data frame format used by the DATA interface is as follows; in: Session ID represents the session ID, and the communication board uses the Session ID to find the corresponding channel; Length indicates the data length; Data Content refers to the data content; After receiving the DATA message, the platform interface layer will call the protocol layer's encodeData interface to encapsulate the protocol, and then the protocol layer will call the device layer's writeData to send the data to the external device.

8. The two-out-of-two secure platform communication board as described in claim 1, characterized in that, The communication board's protocol layer tasks call the cycleProcess interface of the registered protocol modules in real time to process periodic tasks, collect the status of each protocol module, and call the uploadProtocolState interface of the platform interface layer to send the protocol status to the computing board. The communication board device layer task reads peripheral data in real time. If the data reading is successful, it calls the protocol layer decodeData interface to parse the data. After the protocol layer parses the data, it calls the platform interface layer uploadData interface to send the peripheral data to the computing board. The communication board device layer task determines if the communication interface status has changed, or collects all communication interface statuses at the end of each reading cycle and calls the platform interface layer uploadAdapterState interface to send the communication interface status to the computing board. The communication board device layer task determines if the channel status has changed, or collects all channel statuses at the end of each reading cycle and calls the platform interface layer uploadChannelState interface to send the channel status to the computing board. The application module on the computing board determines whether the communication interface has been successfully opened based on the communication interface status, whether the channel has been successfully created or whether the connection is normal based on the channel status, and whether the protocol communication process is normal based on the protocol status.

9. A remote invocation method for a two-out-of-two secure platform communication board based on any one of claims 1-8, characterized in that, Includes the following steps: After the communication board is successfully initialized, the application module on the computing board uses the ADAPTER message to send interface configuration commands to the communication board. After receiving the ADAPTER message, the communication board platform interface layer calls the device layer openAdapter service to configure the relevant interfaces. If the interface configuration is successful, the device layer calls the platform interface layer's uploadAdapterState service to send the successful interface configuration status to the application module. If the interface configuration fails, the device layer adds the interface configuration command to the interface management queue and executes it repeatedly periodically until the interface configuration is successful or the application module actively closes the interface. After the interface is successfully configured, the application module on the computing board uses a CHANNEL message to send a channel creation command to the communication board. After receiving the CHANNEL message, the communication board platform interface layer calls the device layer's createChannel service to create the corresponding channel. After receiving the CHANNEL message, the communication board platform interface layer calls the protocol layer's registerProtocol service to bind the channel number with the relevant protocol module; If the channel is successfully created, the device layer calls the platform interface layer's uploadChannelState service to send the successful channel creation status to the application module. If channel creation fails, the device layer adds the channel creation command to the channel management queue and executes it repeatedly periodically until the channel is successfully created or the application module actively destroys the channel.

10. A data transmission and reception method for a two-out-of-two secure platform communication board based on any one of claims 1-8, characterized in that, Includes the following steps: After the channel is successfully created, the application module on the computing board uses the DATA message to send the application's output data to the communication board. After receiving the DATA message, the communication board platform interface layer calls the protocol layer's encodeData service to encapsulate the application data using the protocol. The protocol layer determines whether the channel is bound to a certain protocol module. If it is bound, it calls the protocol module to perform packet processing and sends the processed data to the external device by calling the device layer's writeData service. If the channel is not bound to any protocol module, the protocol layer directly calls the device layer's writeData service to send the data to the external device. The receiving task of each interface in the device layer reads the data of each channel in real time. After successfully reading the data of the external device, it calls the decodeData service in the protocol layer to unpack the protocol. The protocol layer determines whether the channel is bound to a certain protocol module. If it is bound, it calls the protocol module to unpack the data and sends the processed data to the computing board by calling the uploadData service of the platform interface layer. If the channel is not bound to any protocol module, the protocol layer directly calls the uploadData service of the platform interface layer to send the data to the computing board. The device layer periodically collects the status of each communication interface and calls the uploadAdapterState service of the platform interface layer to send the interface status to the computing board. The device layer periodically collects the status of each communication channel and calls the uploadChannelState service of the platform interface layer to send the channel status to the computing board; The protocol layer periodically calls the cycleProcess interface to process the periodic tasks of each protocol module, collects the status of each protocol, and calls the uploadProtocolState service of the platform interface layer to send the protocol status to the computing board.