Communication connection identification method and system based on redundant dual channels

Abstract

This invention relates to the field of communication connection technology, and more particularly to a communication connection identification method and system based on redundant dual-channel architecture. It is applied between a first communication node and a second communication node, where an adaptation layer connection is established between them. This adaptation layer connection carries at least two transport layer connections. When one of the transport layer connections is disconnected and re-established, the first communication node sends a connection identification packet to the second communication node. The connection identification packet carries device identification information of the first and / or second communication nodes, as well as a verification field for verifying the device identification information. The second communication node receives the connection identification packet and identifies the affiliation of the re-established transport layer connection based on the device identification information and the verification field. Combined with a robust mechanism for handling abnormal retransmissions and duplicate connections, this invention constructs a low-overhead, robust communication management closed loop, possessing practical engineering value and protocol compatibility.

Description

Technical Field

[0001] This invention relates to the field of communication connection technology, and in particular to a communication connection identification method and system based on redundant dual channels. Background Technology

[0002] In the CTCS-3 level train control system, the Radio Block Center (RBC) and the Automatic Train Protection (ATP) typically exchange critical business information on redundant dual channels via an adaptation layer protocol. In this communication architecture, multiple transport layer connections (such as TCP connections) are established below the adaptation layer to achieve physical link redundancy. In the initial stage of establishing an adaptation layer connection, the communicating parties confirm their identities and establish link associations by exchanging handshake messages containing device identification information. Once the connection is successfully established, to pursue high transmission efficiency, subsequent business data packets typically no longer carry device identification information, but instead identify different communicating entities solely through the established mapping transport layer connection channels.

[0003] However, in real-world operating environments, the transport layer IP addresses of vehicle-mounted mobile terminals are often dynamically assigned by the network and are not fixed. When one of the transport layer connections in the redundant dual-channel configuration is disconnected due to network fluctuations and attempts to re-establish it, the new IP address obtained by the vehicle-mounted terminal may change, causing the ground terminal to be unable to identify the affiliation of the newly arrived connection through address information. Since the adaptation layer connection is still active at this time, and subsequent interaction messages lack the necessary identification fields, the ground terminal cannot associate the newly established transport layer connection with the corresponding vehicle-mounted device, resulting in the redundancy channel failing to recover and reducing the system's communication reliability. Existing methods that modify all data packet formats to add identification information, while solving the identification problem, significantly increase the additional overhead of communication bandwidth and require substantial modifications to the existing protocol architecture, making it difficult to balance communication efficiency and backward compatibility. Summary of the Invention

[0004] The purpose of this invention is to address the aforementioned shortcomings in the prior art by proposing a communication connection identification method and system based on redundant dual channels.

[0005] To achieve the above objectives, the present invention provides a communication connection identification method based on redundant dual channels, for use between a first communication node and a second communication node, wherein an adaptation layer connection is established between the first communication node and the second communication node, and the adaptation layer connection is carried on at least two transport layer connections; the method includes: When one of the transport layer connections is disconnected and re-established, the first communication node sends a connection identification packet to the second communication node. The connection identification packet carries the device identification information of the first communication node and / or the second communication node, as well as a verification field for verifying the device identification information. The second communication node receives the connection identification packet and identifies the affiliation of the re-established transport layer connection based on the device identification information and the verification field; If the identification is successful, the second communication node sends a response identification packet to the first communication node to restore the data interaction of the adaptation layer connection on the re-established transport layer connection.

[0006] In one possible implementation, the device identification information includes a sending device identifier and a receiving device identifier; the verification field is obtained by the sending end using the session key negotiated by the first communication node and the second communication node when establishing the adaptation layer connection, to perform encrypted calculations on the sending device identifier and the receiving device identifier.

[0007] In one possible implementation, the transmission sequence number in the header field of the connection identification packet is set to a fixed preset value, and the connection identification packet does not contain service data payload.

[0008] In one possible implementation, the transmission sequence number is fixed at 0 to distinguish regular service data packets and avoid affecting the sliding window processing of the adaptation layer protocol.

[0009] In one possible implementation, the second communication node performs attribution identification on the re-established transport layer connection based on the device identification information and the verification field, including: verifying whether the receiving device identifier in the connection identification packet is consistent with the device identifier of this node; if consistent, performing local calculation on the device identification information in the packet using a pre-stored session key to obtain a local verification value; comparing whether the local verification value is consistent with the verification field in the connection identification packet, and determining that the identification is successful if consistent.

[0010] In one possible implementation, the method further includes an exception handling step: If the first communication node does not receive the response identification packet, it will resend the connection identification packet when the next upper-layer service data is triggered for transmission; or, if the second communication node does not receive service data on the newly established transport layer connection after sending the response identification packet, it will send the response identification packet to the first communication node again when the next downlink service data is triggered for transmission.

[0011] In one possible implementation, the method further includes a repeat connection processing step: When the second communication node receives a transport layer connection request from the same device identifier while an adaptation layer connection already exists, it determines the data type of the first packet after the transport layer connection is established: if it is a connection request packet type, it disconnects the existing adaptation layer connection and all its corresponding transport layer connections; if it is the connection identification packet type, it only disconnects the existing transport layer connections with the same sequence number and accepts the newly established transport layer connection.

[0012] Secondly, the present invention also provides a communication system based on redundant dual channels, comprising a first communication node and a second communication node, wherein: The first communication node is an on-board automatic protection device (ATP), which has a dynamically allocated IP address; The second communication node is a Radio Block Center (RBC) with a static IP address; The ATP and the RBC are identified by a redundant dual-channel communication connection identification method after the transmission layer connection is reconstructed.

[0013] Thirdly, the present invention also provides an electronic device, comprising: a memory for storing program instructions; A processor is configured to invoke program instructions stored in the memory and execute the steps of the method described in any one of the first aspects according to the obtained program instructions.

[0014] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method described in any one of the first aspects.

[0015] Compared with the prior art, the communication connection identification method and system based on redundant dual channels disclosed in this invention have the following significant advantages: This invention solves the technical challenge of identifying device affiliation after transport layer connection reconstruction in a dynamic IP environment by introducing a dedicated connection identification packet. This method no longer relies on source address information from the physical link layer or transport layer, but instead uses adaptation layer logical identifiers for precise matching. This ensures that onboard equipment can still automatically identify affiliation and restore links even when IP addresses change. This not only significantly improves the utilization rate of redundant dual channels in the train control system under complex network environments, but also guarantees the continuity and high availability of train-to-ground communication during single-path fault switching, providing a solid communication guarantee for the safe operation of trains.

[0016] On the other hand, this invention effectively enhances the security of the connection reconstruction process by integrating a session key-based encrypted verification field into the connection identification packet and cooperating with a two-way handshake verification process, thus preventing the risk of unauthorized access or incorrect connection association. Simultaneously, because the identification packet employs a special design with a fixed transmission sequence number and no service load, it minimizes the impact of auxiliary signaling on normal service communication bandwidth and avoids interference with existing protocol sliding window processing mechanisms. Combined with a robust mechanism for handling abnormal retransmissions and duplicate connections, this invention constructs a low-overhead, robust communication management closed loop, possessing practical engineering value and protocol compatibility. Attached Figure Description

[0017] Figure 1 This is a schematic diagram illustrating the establishment of a dual TCP connection provided in an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the establishment of an ALE connection provided in an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the reconstruction of a connection after it has been disconnected, as provided in an embodiment of the present invention. Figure 4 A flowchart of transport layer connection disconnection and reconnection and the sending of connection identification packets provided in an embodiment of the present invention; Figure 5 A flowchart illustrating the attribution identification and response of an RBC as provided in an embodiment of the present invention; Figure 6 A flowchart illustrating the ATP reception response and data recovery interaction provided in this embodiment of the invention; Figure 7 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0018] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0019] Example 1: This application provides a communication system based on redundant dual channels, which is mainly used in rail transit train control systems, as detailed below: The system includes a first communication node and a second communication node. In one possible implementation, the first communication node is an Automatic Protection Device (ATP), acting as the client for communication; the second communication node is a Radio Block Center (RBC), acting as the server for communication.

[0020] The first communication node integrates multiple mobile terminal modules (such as MT1 and MT2) to establish physical connections through different wireless network access points or physical channels. The second communication node connects to the external network through interface units (such as interface unit I series and interface unit II series) and has a fixed static IP address.

[0021] The communication protocol stack between the first and second communication nodes, from bottom to top, includes the physical layer, data link layer, transport layer, adaptation layer, security layer, and application layer.

[0022] The transport layer connection preferably uses the TCP protocol. The adaptation layer, built on top of the transport layer, is used to manage redundant channels, distribute data, and perform redundancy removal. The security layer, built on top of the adaptation layer, is used to ensure the integrity and security of business data.

[0023] In this embodiment, an adaptation layer connection is established between the first communication node and the second communication node. This adaptation layer connection is carried over at least two transport layer connections, thereby achieving redundant dual-channel communication. From the perspective of the adaptation layer and above, there is only one logical connection between the two parties, but at the transport layer and below, there are multiple parallel physical data paths.

[0024] S01: Link Initialization In the initial stage of system operation, the first communication node and the second communication node need to complete the end-to-end link initialization.

[0025] First, the first communication node controls its internal MT1 module to establish a first transport layer connection with the first server address (e.g., IP_A1) of the interface unit I of the second communication node via a first IP address (e.g., IP_B1). Simultaneously, it controls its internal MT2 module to establish a second transport layer connection with the second server address (e.g., IP_A2) of the interface unit II of the second communication node via a second IP address (e.g., IP_B2). At this point, the two independent transport layer connections at the bottom layer are established.

[0026] Subsequently, over the two established transport layer connections, the first communication node and the second communication node perform an adaptation layer handshake. The first communication node sends a connection request packet to the second communication node through either transport layer connection. This connection request packet carries the device identification information of the first communication node (such as the local CTCS). ID) and the device identification information of the second communication node (such as the peer CTCS) ID).

[0027] After receiving the connection request packet, the second communication node verifies the device identification information and returns a connection confirmation packet upon confirmation. Through this handshake process, the first and second communication nodes negotiate a set of session keys for subsequent communication. In one possible implementation, the session key is chosen as KSMAC (Session Key for Message Authentication Code).

[0028] After the adaptation layer handshake is completed, the adaptation layer connection is successfully established. At this point, the security layer and the application layer begin exchanging business data. When sending data, the adaptation layer will send the same business data packet from the upper layer once on each of the two transport layer connections; after receiving the packet, the receiving adaptation layer will perform redundancy removal based on the transmission sequence number in the packet header, retaining only one valid copy of the data and submitting it to the security layer.

[0029] S02: Transport Layer Connection Reconstruction and Identification Process During the existence of the aforementioned adaptation layer connection, if one of the transport layer connections is disconnected (for example, due to network switching, base station signal fading, etc.), the adaptation layer connection is maintained due to the existence of the other transport layer connection.

[0030] When a disconnected transport layer connection attempts to be re-established, the second communication node cannot identify the affiliation of the new connection solely through the physical address because the first communication node may have acquired a new dynamic IP address (e.g., from IP_B1 to IP_B1′).

[0031] In a preferred embodiment, the identification is performed using the following detailed steps: S0201: The first communication node re-establishes the transport layer connection. After the MT1 module of the first communication node detects a link disconnection, it initiates a reconstruction request to re-establish a transport layer connection with the interface unit of the second communication node. At this point, the two parties successfully handshake at the transport layer, but the adaptation layer has not yet included this physical link in the logical channel pool.

[0032] S0202: The first communication node sends a connection identification packet. The first communication node sends a connection identification packet to the second communication node through the newly established transport layer connection.

[0033] The connection identification packet has a specific message structure. It carries device identification information for the first and / or second communication nodes, as well as a verification field for verifying the device identification information.

[0034] Specifically, the device identification information includes the sending device identifier (i.e., the identifier of the first communication node) and the receiving device identifier (i.e., the identifier of the second communication node).

[0035] The generation logic of the verification field is as follows: The first communication node calls the session key negotiated during the initial connection phase and uses a specific encryption algorithm (such as 3DES or SM4) to perform encryption calculation on the original data block composed of the sender device identifier and the receiver device identifier. The resulting ciphertext is used as the verification field.

[0036] To ensure that this identification packet does not affect existing adaptation layer flow control, the transmission sequence number in the header field of the connection identification packet is fixed to a preset value of 0. Furthermore, this connection identification packet is defined as a signaling packet and does not contain any service data payload.

[0037] S0203: The second communication node performs home identification. The second communication node receives the data packet from the newly established transport layer connection. Since the data packet type in the header is identified as a connection identification packet, the second communication node enters the home identification procedure: Identifier verification: The second communication node first extracts the receiver device identifier from the packet and compares it with the node's preset device identifier. If they do not match, it is determined to be an illegal or erroneous connection, and the transport layer connection is directly disconnected.

[0038] Validity verification: If the receiver identifier is correct, the second communication node retrieves the existing adaptation layer connection context corresponding to the sender device identifier and extracts the corresponding session key.

[0039] Local verification: The second communication node uses the extracted session key to perform the same encryption calculation on the sender device identifier and the receiver device identifier in the packet to obtain the local verification value.

[0040] Consistency determination: The local verification value is compared bit by bit with the verification field carried in the connection identification packet. If they match completely, it proves that the sender is indeed the communication peer holding the legitimate key, and the attribution identification is successful.

[0041] S0204: Second Communication Node Feedback Response Identification Packet After successful identification, the second communication node sends a response identification packet to the first communication node.

[0042] The structure of the response identification packet is similar to that of the connection identification packet. It also carries the identifier of the sender (which is the second communication node at this time), the identifier of the receiver (which is the first communication node at this time), and the response verification field calculated using the same session key.

[0043] S0205: The first communication node verifies and resumes data interaction. After receiving the response identification packet, the first communication node executes verification logic similar to step S103. Upon successful verification, the first communication node confirms that the transport layer connection has been successfully associated with the existing adaptation layer connection.

[0044] Subsequently, the first communication node resumed data interaction on the newly established transport layer connection. The adapter layer connection then returned to redundant dual-channel operating mode.

[0045] This embodiment solves the problem of redundant channels being unable to be identified in a dynamic IP environment by introducing a connection identification packet containing device identification information and verification fields after the transport layer connection is re-established. Even if the first communication node (such as the vehicle-mounted terminal) obtains a different IP address due to network switching, the second communication node (such as the ground terminal) can still accurately match the existing connection context through the adaptation layer identifier, thereby achieving rapid and automatic association between the physical link and the logical channel. This mechanism ensures the high availability of the redundant dual-channel architecture in complex wireless environments, avoids the interruption of adaptation layer or even application layer connections caused by fluctuations in a single physical connection, and greatly improves the continuity and robustness of critical business communications such as train control systems.

[0046] Furthermore, this embodiment ensures both identification efficiency and communication security and protocol compatibility. By using the session key negotiated in the initial phase to encrypt and verify the identification information, a two-way handshake verification mechanism is constructed, effectively preventing the risk of unauthorized node access or incorrect connection association. Simultaneously, the connection identification packet employs a special design with a fixed transmission sequence number of 0 and no service load, cleverly avoiding the sliding window and redundancy removal logic of the adaptation layer, achieving deep isolation between the signaling plane and the data plane. This not only minimizes bandwidth overhead during link recovery but also ensures the transparency and stability of the original service data interaction, demonstrating its engineering application value.

[0047] In real-world, complex electromagnetic environments, packet loss or timing discrepancies are common. In one possible implementation, this system ensures robustness through the following methods: If the first communication node does not receive a corresponding response packet within a preset time after sending the connection identification packet, the system will not immediately disconnect the connection. However, when the first communication node has new upper-layer service data to send, the adaptation layer will trigger the sending of the connection identification packet again.

[0048] If the second communication node has sent a response identification packet, but no subsequent service data inflow has been detected on the re-established transport layer connection, the second communication node can resend the response identification packet to the first communication node when downlink service data (sent from the server to the client) is triggered again.

[0049] On the other hand, since the adaptation layer protocol usually uses a sliding window mechanism for message sending and receiving, if the identification packet occupies the normal transmission sequence number, it will cause the window to move or the retransmission buffer logic to become disordered.

[0050] In one possible implementation, the transmission sequence number of the connection identification packet can be forced to be fixed at 0. When the adaptation layer receives and processes the packet, once it identifies a packet with a sequence number of 0 and a packet type of identification packet, it will not include it in the incremental count of the sliding window, nor will it trigger any redundancy removal logic for the service data, thereby achieving complete isolation between the signaling plane and the data plane.

[0051] By introducing a retransmission mechanism triggered by service data and a fixed sequence number strategy, the robustness and protocol stability of the communication system under harsh electromagnetic environments can be significantly improved. The logic of triggering the retransmission of identification packets using uplink and downlink service data effectively compensates for connection recovery interruptions caused by network packet loss, ensuring the reliability of link reconstruction. Furthermore, forcibly fixing the transmission sequence number of the connection identification packet to 0 cleverly achieves deep isolation between the signaling plane and the data plane, fundamentally preventing auxiliary signaling from interfering with the adaptation layer's sliding window and redundancy removal mechanisms, thus ensuring the continuity of existing service data transmission and the accuracy of flow control logic during complex link reconstruction.

[0052] During periods of severe network jitter, extreme situations may arise where old connections have not yet been released while new connections have already arrived. In one possible implementation, different conflict handling strategies are employed based on the data type of the first packet arriving at the new connection: When the second communication node receives a connection request packet (CR) from ID_X from a new transport layer connection, provided that an adapter layer connection for device identifier ID_X already exists, the connection request packet (CR) is already in place. (ALEPKT). At this point, it is determined that the first communication node may have experienced a cold start or system reset, and the existing adaptation layer context has become invalid. The second communication node immediately disconnects the existing adaptation layer connection for ID_X and all (two) subordinate transport layer connections, clears the state machine, and restarts the initial connection process.

[0053] When the second communication node receives a connection identification packet with the same device identifier while an adaptation layer connection already exists, it is determined that the single-path connection reconstruction is due to network fluctuations, and the overall adaptation layer connection is healthy. The second communication node only disconnects the existing transport layer connection with the same sequence number (for example, if the new identification packet comes from channel 1, the old channel 1 is disconnected), and accepts the newly established transport layer connection, keeping the adaptation layer connection and another normal transport layer connection unaffected.

[0054] By intelligently identifying the data type of the first packet in a newly established transport layer connection, a refined conflict resolution strategy is constructed, which significantly enhances the system's self-healing capability and resource management accuracy under extreme network fluctuations or node anomalies. By distinguishing between connection request packets and connection identification packets, the system can accurately identify whether the peer node is in a cold start reset or a single physical link reconnection state: for the former, by thoroughly cleaning up existing expired contexts and restarting the connection process, it effectively prevents communication logic disorder and resource consumption caused by zombie connections; for the latter, a precise replacement strategy is adopted, disconnecting only damaged old connections with the same sequence number while maintaining the overall operation of the adaptation layer and the other normal channel. This differentiated conflict resolution mechanism not only ensures the consistency of the state machine among communication nodes but also maximizes the communication continuity under the redundant dual-channel architecture, reducing the impact of underlying link instability on upper-layer critical services.

[0055] Example 2 This embodiment provides an exemplary implementation method, as detailed below: refer to Figures 1-6 In this embodiment, the first communication node is specifically a client, optionally an onboard ATP (Automatic Train Protection System). The second communication node is specifically a server, optionally an RBC (Radio Block Center). The adaptation layer connection is specifically an ALE connection, and the transport layer connection is specifically a TCP connection. The connection identification packet and response identification packet are specifically newly added ALE type 5 data packets (hereinafter referred to as ALE type 5 packets), the device identification information is specifically CTCS-ID, and the connection request packet is specifically an ALE type 1 packet.

[0056] S201: Establish multiple transport layer connections and adaptation layer connections As an ATP, it controls the vehicle communication module (such as MT1, MT2) and establishes a transport layer connection with the RBC interface unit (such as the I series, II series). Optionally, MT1 establishes a first TCP connection with the interface unit I series through an IP address, and MT2 establishes a second TCP connection with the interface unit II series through another IP address. That is, the adaptation layer connection is carried on at least two transport layer connections.

[0057] After the TCP connection is established, ATP and RBC exchange connection request packets and connection confirmation packets to complete the ALE connection establishment. During the establishment of the adaptation layer connection, ATP and RBC negotiate a session key, which is used for encryption and verification calculations during subsequent data exchange. Optionally, the aforementioned session key is KSMAC.

[0058] S202: Transport layer connection disconnection and reconnection and sending connection identification packet If one transport layer connection fails and is disconnected while the other transport layer connection remains normal, and the adapter layer connection is already established and maintained, the ATP will reacquire an IP address and re-establish the disconnected transport layer connection with the RBC.

[0059] Once the transport layer connection is re-established, the ATP uses the pre-negotiated session key to encrypt and calculate the device identification information (including the sender's device identifier, i.e., the sender's CTCS-ID, and the receiver's device identifier, i.e., the receiver's CTCS-ID) to derive the verification field. Subsequently, the ATP assembles the sender's CTCS-ID, the receiver's CTCS-ID, and the verification field into a connection identification packet and sends it to the RBC over the re-established transport layer connection.

[0060] In this embodiment, the connection identification packet uses an ALE type 5 packet, which is dedicated to home identification when reconstructing a TCP connection, and its packet structure does not contain service data payload. Furthermore, to avoid affecting the reception of other adaptation layer protocol data packets and sliding window processing, the transmission sequence number in the header field of this ALE type 5 packet is fixed to a preset value of 0.

[0061] The following is an example of the structure of an ALE type 5 package in a specific implementation: Table 1. ALE Type 5 Packages

[0062] Table 2 ALE Type 5 Header

[0063] S203: RBC performs attribution identification and responds. After receiving the connection identification packet, RBC identifies the affiliation of the newly established transport layer connection based on the device identification information and verification field in the packet. The specific process is as follows: RBC verifies whether the receiver device identifier (receiver CTCS-ID) in the connection identification packet matches the device identifier of this node. If they do not match, it means that the destination device ID sent by the other party does not match the local device ID, the verification fails, and RBC actively disconnects the newly established transport layer connection. If they match, RBC further uses the pre-stored session key to perform local calculations on the device identification information in the packet to obtain a local verification value; The local verification value is compared with the verification field in the connection identification packet. If they do not match, the verification fails and the connection is closed; if they match, the attribution identification is successful.

[0064] After successful identification, the RBC also uses the session key to calculate the authentication field from its own device identification information, assembles it into a response identification packet (i.e., a reply ALE type 5 packet), and sends it to the ATP over the re-established transport layer connection. At this point, from the RBC's perspective, the identification process for connection reconstruction is complete.

[0065] S204: ATP Receiver Response and Recovery Data Interaction After receiving the response identification packet from the RBC, the ATP performs the same verification process as described above: first, it verifies whether the receiver device identifier is consistent with its own, and then it uses the session key to verify whether the verification field is correct.

[0066] If the ATP verification passes, the connection reconstruction process is confirmed to be complete. Both communicating parties can then resume data interaction on the newly established transport layer connection. In practice, the ATP can first send normal service data on the reconstructed channel, and the RBC, upon receiving this, can begin sending normal service data on the same channel; alternatively, both communicating parties can directly begin sending normal service data on the reconstructed channel after determining that their connection reconstruction is complete.

[0067] Error handling steps: (1) ALE type 5 packet lost: 1) If the ALE type 5 packet sent by ATP is lost, it will not be able to receive the reply from RBC. The next time the client sends service data from the upper layer, it will trigger it to send the type 5 packet again. 2) If the ALE type 5 packet returned by RBC is lost: Option: "The decision is still made by ATP. If no reply is received, the upper-layer business data of ATP will trigger the retransmission of type 5 packets." Alternatively, you can select "Let the RBC determine itself; if no normal service data is received on the re-established channel, then trigger the retransmission of type 5 packets when the RBC sends the next layer of service data."

[0068] (2) The RBC receives a TCP connection with the same ATP while the ALE and TCP connections are still open, and the first packet after the TCP connection is an ALE type 1 packet: 1) Option: "Disconnect existing ALE and TCP connections via RBC, and accept new TCP and ALE connections"; 2) Alternatively, you can select "Disconnect existing ALE and TCP connections by RBC, and also disconnect newly arrived TCP connections and reject the corresponding ALE connections".

[0069] Table 3 ALE Type 1 Package

[0070] (3) The RBC receives a TCP connection with the same ATP while the ALE and TCP connections are still open, and the first packet after the TCP connection is an ALE type 5 packet: 1) Option: "Disconnect existing TCP connections by RBC and accept new TCP connections"; 2) Alternatively, you can select "Disconnect the existing TCP connection by RBC, and also disconnect the newly arrived TCP connection".

[0071] Example 3 Having described the methods of exemplary embodiments of this application, we will now describe an electronic device according to another exemplary embodiment of this application.

[0072] The following reference Figure 7 To describe an electronic device 130 implemented according to this embodiment of the present application. Figure 7 The electronic device 130 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0073] like Figure 7 As shown, electronic device 130 is represented in the form of a general electronic device. The components of electronic device 130 may include, but are not limited to: at least one processor 131, at least one memory 132, and a bus 133 connecting different system components (including memory 132 and processor 131).

[0074] Bus 133 represents one or more of several bus structures, including a memory bus or memory controller, peripheral bus, processor, or local bus using any of the various bus structures.

[0075] The memory 132 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 1321 and / or cache memory 1322, and may further include read-only memory (ROM) 1323.

[0076] The memory 132 may also include a program / utility 1325 having a set (at least one) of program modules 1324, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0077] Electronic device 130 can also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), and with one or more devices that enable a user to interact with electronic device 130, and / or with any device that enables electronic device 130 to communicate with one or more other electronic devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 135. Furthermore, electronic device 130 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 136. As shown, network adapter 136 communicates with other modules used in electronic device 130 via bus 133. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0078] In an exemplary embodiment, the electronic device of this application may include at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores a computer program executable by the at least one processor, and when the computer program is executed by the at least one processor, it enables the at least one processor to perform the steps of any method provided in the embodiments of this application.

[0079] In an exemplary embodiment, a storage medium is also provided, which enables the electronic device to perform any of the methods described above when a computer program stored in the storage medium is executed by a processor of the electronic device. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), or CD. ROM, magnetic tape, floppy disk and optical data storage devices, etc.

[0080] In an exemplary embodiment, a computer program product is also provided, which, when executed by an electronic device, enables the electronic device to implement any of the exemplary methods provided in this application.

[0081] It should be noted that although several modules or sub-modules of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more modules described above can be embodied in one module. Conversely, the features and functions of one module described above can be further divided and embodied by multiple modules.

[0082] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

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

[0084] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0085] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, then this application also includes such modifications and variations.

Claims

1. A communication connection identification method based on redundant dual channels, characterized in that, The method is applied between a first communication node and a second communication node, wherein an adaptation layer connection is established between the first communication node and the second communication node, and the adaptation layer connection is carried on at least two transport layer connections; the method includes: When one of the transport layer connections is disconnected and re-established, the first communication node sends a connection identification packet to the second communication node. The connection identification packet carries the device identification information of the first communication node and / or the second communication node, as well as a verification field for verifying the device identification information. The second communication node receives the connection identification packet and identifies the affiliation of the re-established transport layer connection based on the device identification information and the verification field; If the identification is successful, the second communication node sends a response identification packet to the first communication node to restore the data interaction of the adaptation layer connection on the re-established transport layer connection.

2. The communication connection identification method based on redundant dual channels according to claim 1, characterized in that, The device identification information includes a sending device identifier and a receiving device identifier; the verification field is obtained by the sending end using the session key negotiated by the first communication node and the second communication node when establishing the adaptation layer connection, and by encrypting and calculating the sending device identifier and the receiving device identifier.

3. The communication connection identification method based on redundant dual channels according to claim 1, characterized in that, In the header field of the connection identification packet, the transmission sequence number is set to a fixed preset value, and the connection identification packet does not contain service data payload.

4. The communication connection identification method based on redundant dual channels according to claim 3, characterized in that, The transmission sequence number is fixed at 0 to distinguish regular service data packets and avoid affecting the sliding window processing of the adaptation layer protocol.

5. The communication connection identification method based on redundant dual channels according to claim 1, characterized in that, The second communication node performs attribution identification on the re-established transport layer connection based on the device identification information and the verification field, including: Verify whether the receiver device identifier in the connection identification packet is consistent with the device identifier of this node; If they match, the device identification information in the packet is calculated locally using the pre-stored session key to obtain the local verification value; Compare the local verification value with the verification field in the connection identification packet to see if they match. If they match, the identification is deemed successful.

6. The communication connection identification method based on redundant dual channels according to claim 1, characterized in that, The method also includes an exception handling step: If the first communication node does not receive the response identification packet, it will resend the connection identification packet when the next upper-layer service data is triggered. Alternatively, if the second communication node does not receive service data on the re-established transport layer connection after sending the response identification packet, it will send the response identification packet to the first communication node again when the next downlink service data is triggered.

7. The communication connection identification method based on redundant dual channels according to claim 1, characterized in that, The method further includes a repeated connection processing step: When the second communication node receives a transport layer connection request from the same device identifier while an adaptation layer connection already exists, it determines the data type of the first packet after the transport layer connection is established: If it is a connection request packet type, then disconnect the existing adaptation layer connection and all its corresponding transport layer connections; If it is the connection identification packet type, then only the existing transport layer connections with the same sequence number are disconnected, and the newly established transport layer connection is accepted.

8. A communication system based on redundant dual channels, characterized in that, It includes a first communication node and a second communication node, wherein: The first communication node is an on-board automatic protection device (ATP), which has a dynamically allocated IP address; The second communication node is a Radio Block Center (RBC) with a static IP address; The ATP and the RBC are identified after the reconstructed transport layer connection is performed using the method described in any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 7.

Images