Urban rail transit signal system vehicle door switch acquisition IO sharing processing method

Abstract

The invention discloses a vehicle door switch acquisition IO sharing processing method for an urban rail transit signal system. The method comprises the following steps: step 1, configuring two sets of ATP subsystems at a single end of a vehicle-mounted signal system; 2, when one of the main system and the standby system collects a door closing button IO and the other ATP subsystem does not collect the door closing button IO, the ATP subsystem which collects the door closing button IO initiates IO data sharing to the ATP subsystem which does not collect the door closing button IO, the IO data is sent to the ATP subsystem which does not collect the door closing button IO through the vehicle-mounted switch, and the ATP subsystem which does not collect the door closing button IO is sent to the ATP subsystem which does not collect the door closing button IO through the vehicle-mounted switch. Generating a sending completion information identifier; and step 3, the ATP subsystem which does not collect the door closing button IO obtains IO data through the vehicle-mounted switch and then generates a successful receiving information identifier, and a vehicle door closing button IO collection and sharing processing process is completed once. The reliability, safety and operation and maintenance efficiency of the system are integrally improved, resource utilization is optimized, and stable operation of rail transit vehicle door control is guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of rail transit technology, and in particular to a method for sharing I / O data collected by a door switch in an urban rail transit signaling system. Background Art

[0002] Currently, the CBTC signaling system (CC) uses two ATP subsystems (A / B dual-system hot standby) on a single end. The CC's A / B subsystems each collect the status of two door closing button signals via hardwired data acquisition. The door mode is typically "automatic open, manual close." When an operator presses the door closing button, the signal is collected separately by the CC's primary and backup subsystems, with the primary subsystem performing the calculations and outputting the output. When System A is active and System B is standby, in long-term operations, due to the electrical characteristics and aging of the door closing buttons, operators may occasionally experience power to one subsystem while the other is not. This means that System A (the primary subsystem) fails to receive the door closing activation signal, while System B (the backup subsystem) does. Consequently, the CC's primary subsystem is unable to complete the door closing calculations and output, causing doors to fail to close properly, impacting platform efficiency. Summary of the Invention

[0003] The purpose of the present invention is to overcome the defects in the prior art that the CC main system cannot complete the door closing centralized acquisition and output due to problems such as the electrical characteristics and aging of the door closing button, resulting in the problem that the door cannot be closed normally, affecting the operating efficiency of the operating platform, and provide a door switch acquisition IO sharing processing method for the urban rail transit signal system.

[0004] The purpose of the present invention is achieved through the following technical solutions: The urban rail transit signal system door switch acquisition IO sharing processing method includes the following steps: Step 1: Two ATP subsystems are configured on a single end of the vehicle signal system. One ATP subsystem is the primary system, and the other is the backup system. Both ATP subsystems start working. Step 2: When both the primary and backup systems collect the door close button IO signals simultaneously, or when neither the primary nor the backup system collects the door close button IO signals, IO data sharing does not occur between the primary and backup systems. When one of the primary and backup systems collects the door close button IO signals, and the other ATP subsystem does not collect the door close button IO signals, the ATP subsystem that collects the door close button IO signals initiates IO data sharing with the ATP subsystem that does not collect the door close button IO signals. The IO data is sent to the ATP subsystem that does not collect the door close button IO signals via the onboard switch, and a sending completion information flag is generated. Step 3: The ATP subsystem that has not collected the door closing button IO obtains the IO data through the vehicle switch and generates a reception success information identifier, completing a door closing button IO collection and sharing processing process.

[0005] Preferably, in step 2, whether the IO data needs to be shared is determined by defining a label for the IO data, and a label value of 1 is assigned to the data that needs to be shared, and a label value of 0 is assigned to the data that does not need to be shared.

[0006] Preferably, in step 1, a judgment condition is further set to judge whether the two ATP subsystems initiate sharing, specifically: If the ATP subsystem loses communication status or the operator operates the on-board signal system to force only one ATP subsystem to run, the ATP subsystem will not initiate sharing.

[0007] Preferably, the step 2 further includes a step of verifying whether to initiate data sharing, specifically: Before the ATP subsystem that has collected the door-closing button IO initiates IO data sharing with the ATP subsystem that has not collected the door-closing button IO, the timing starts. After the set time, if the ATP subsystem that has not collected the door-closing button IO still has not collected the door-closing button IO, the ATP subsystem that has collected the door-closing button IO initiates IO data sharing with the ATP subsystem that has not collected the door-closing button IO.

[0008] Preferably, the set time matches the high level residual time of the door closing button 10 hard line acquisition signal.

[0009] As a preference, the urban rail transit signal system door switch acquisition IO shared processing method also considers the communication protocol data processing time, and the set time is the sum of the high-level residual time of the door closing button IO hard-wire acquisition signal and the communication protocol data processing time.

[0010] Preferably, after completing IO data sharing, the ATP subsystem synchronizes the shared status information to the vehicle maintenance terminal for generating a device status log.

[0011] Preferably, the sending completion information is identified as PFM_IO_Share_SendProcessed, which is used to indicate that the ATP subsystem that has collected the door closing button IO has completed the sending of shared data, and the receiving success information is identified as PFM_IO_Share_GetSucc, which is used to indicate that the ATP subsystem that has not collected the door closing button IO has successfully obtained the shared data.

[0012] The beneficial effects of the present invention are as follows: by adopting a shared processing mechanism for collecting door closing IO, the present invention solves the problem of the main signal system being unable to collect the corresponding door closing IO due to the electrical characteristics and aging of the door button, thereby improving the operating efficiency of the platform; Improves the availability of the signal system itself and avoids the impact of abnormal status of external interface devices; Reduce the daily maintenance level of the door closing button for operators, saving manpower input; The overall system reliability, safety and operation and maintenance efficiency have been improved, resource utilization has been optimized, and the stable operation of rail transit door control has been ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a flow chart of the present invention; Figure 2 This is the definition diagram of the door close button IO sharing mechanism; Figure 3 This is the IO shared data flow diagram of the door closing button; Figure 4 This is a diagram of stopping IO sharing in special scenarios; Figure 5 This is a diagram of IO sharing under ideal conditions; Figure 6 This is a diagram of IO sharing in actual state; Figure 7 This is a diagram of IO sharing in a tolerant state. DETAILED DESCRIPTION

[0014] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art.

[0015] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0016] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0017] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0018] Example: Urban rail transit signal system door switch acquisition IO sharing processing method, such as Figure 1 As shown, the following steps are included: Step 1: Two ATP subsystems are configured on a single end of the vehicle signal system. One ATP subsystem is the primary system, and the other is the backup system. Both ATP subsystems start working. The two ATP subsystems are referred to as A and B below. Step 2: When both the primary and backup systems collect the door close button IO signals simultaneously, or when neither the primary nor the backup system collects the door close button IO signals, IO data sharing does not occur between the primary and backup systems. When one of the primary and backup systems collects the door close button IO signals, and the other ATP subsystem does not collect the door close button IO signals, the ATP subsystem that collects the door close button IO signals initiates IO data sharing with the ATP subsystem that does not collect the door close button IO signals. The IO data is sent to the ATP subsystem that does not collect the door close button IO signals via the onboard switch, and a sending completion information flag is generated. Step 3: The ATP subsystem that has not collected the door closing button IO obtains the IO data through the vehicle switch and generates a reception success information identifier, completing a door closing button IO collection and sharing processing process.

[0019] In step 2, the IO data is labeled to determine whether it needs to be shared. If it needs to be shared, the label is assigned a value of 1, and if it does not need to be shared, the label is assigned a value of 0. Figure 2 As shown, define PFM_IO_Share as sharable: Define PFM_IO_SHARE_LOGO=1 / / "0" means not sharing this IO, "1" means sharing this IO.

[0020] like Figure 3As shown, when system A (the primary system) fails to collect the door close button IO data, but system B (the backup system) does, system B sends the door close button IO data (PFM_IO_SendProcessed) to the other system via the onboard switch. After system A obtains the PFM_IO data, it automatically generates the information identifier (PFM_IO_GetSucc), completing a normal door close button IO collection and sharing mechanism. Both the primary and backup systems can serve as the initiator and receiver of the door close button IO sharing mechanism. This embodiment uses the backup system as the initiator and the primary system as the receiver.

[0021] In step 1, a judgment condition is also set to determine whether the two ATP subsystems initiate sharing, specifically: like Figure 4 As shown, if the ATP subsystem loses communication status or the operator operates the on-board signal system to force a single ATP subsystem to run, the ATP subsystem does not initiate sharing. In the door closing IO sharing mechanism, the door closing button IO sharing processing (i.e., PFM_IO_SendStop) is not performed in the following scenarios.

[0022] Step 2 also includes a step of verifying whether to initiate data sharing, specifically: Before the ATP subsystem that has collected the door close button IO data initiates IO data sharing with the ATP subsystem that has not, a timer begins. After the set timer expires, if the ATP subsystem that has not collected the door close button IO data still has not collected the door close button IO data, the ATP subsystem that has collected the door close button IO data initiates IO data sharing with the ATP subsystem that has not. The set timer matches the duration of the high level of the hard-wired collected signal from the vehicle door close button IO.

[0023] Specifically, the door close button IO collection and sharing processing mechanism under the desired ideal state is as follows: Figure 5 However, under normal circumstances (communication delay exists), IO sharing will cause the CC's A-series input IO sharing to have a high level residual in the T1-T2 period (such as Figure 6 As shown in Figure 2, during this period, the real door closing button IO hard-line acquisition signal (ie, digital input) changes directly from high level to low level, thus causing IO conflict.

[0024] To avoid IO conflicts caused by high-level residuals in the IO acquisition shared processing mechanism, such as Figure 7 As shown in the figure, when the IO signal in the original digital input message collected by this system changes from high to low, the main and standby systems will close the IO sharing after tolerating T1-T2 cycles.

[0025] The urban rail transit signal system door switch acquisition IO shared processing method also takes into account the communication protocol data processing time. The set time is the sum of the high-level residual time of the door closing button IO hard-wire acquisition signal and the communication protocol data processing time.

[0026] After completing IO data sharing, the ATP subsystem synchronizes the shared status information to the vehicle maintenance terminal for generating a device status log.

[0027] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0028] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0029] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. The urban rail transit signal system door switch acquisition IO sharing processing method is characterized by: The following steps are involved: Step 1: Two ATP subsystems are configured on a single end of the vehicle signal system. One ATP subsystem is the primary system, and the other is the backup system. Both ATP subsystems start working. Step 2: When both the primary and backup systems collect the door close button IO signals simultaneously, or when neither the primary nor the backup system collects the door close button IO signals, IO data sharing does not occur between the primary and backup systems. When one of the primary and backup systems collects the door close button IO signals, and the other ATP subsystem does not collect the door close button IO signals, the ATP subsystem that collects the door close button IO signals initiates IO data sharing with the ATP subsystem that does not collect the door close button IO signals. The IO data is sent to the ATP subsystem that does not collect the door close button IO signals via the onboard switch, and a sending completion information flag is generated. Step 3: The ATP subsystem that has not collected the door closing button IO obtains the IO data through the vehicle switch and generates a reception success information identifier, completing a door closing button IO collection and sharing processing process.

2. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 1 is characterized in that: In step 2, whether the IO data needs to be shared is determined by defining a label for the IO data. A label value of 1 is assigned to the IO data that needs to be shared, and a label value of 0 is assigned to the IO data that does not need to be shared.

3. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 1, characterized in that: In step 1, a judgment condition is also set to determine whether the two ATP subsystems initiate sharing, specifically: If the ATP subsystem loses communication status or the operator operates the on-board signal system to force only one ATP subsystem to run, the ATP subsystem will not initiate sharing.

4. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 1, characterized in that: Step 2 also includes a step of verifying whether to initiate data sharing, specifically: Before the ATP subsystem that has collected the door-closing button IO initiates IO data sharing with the ATP subsystem that has not collected the door-closing button IO, the timing starts. After the set time, if the ATP subsystem that has not collected the door-closing button IO still has not collected the door-closing button IO, the ATP subsystem that has collected the door-closing button IO initiates IO data sharing with the ATP subsystem that has not collected the door-closing button IO.

5. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 4 is characterized in that: The set time matches the high level residual time of the door closing button IO hard line acquisition signal.

6. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 5 is characterized in that: The communication protocol data processing time is also considered. The set time is the sum of the high-level residual time of the door closing button IO hard line acquisition signal and the communication protocol data processing time.

7. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 1, characterized in that: After completing IO data sharing, the ATP subsystem synchronizes the shared status information to the vehicle maintenance terminal for generating a device status log.

8. The urban rail transit signal system door switch acquisition IO sharing processing method according to claim 1 is characterized in that: The sending completion information is identified as PFM_IO_Share_SendProcessed, which is used to indicate that the ATP subsystem that has collected the door closing button IO has completed the sending of shared data. The receiving success information is identified as PFM_IO_Share_GetSucc, which is used to indicate that the ATP subsystem that has not collected the door closing button IO has successfully obtained the shared data.

Images