A method and system for multi-terminal synchronization login of a CTC station

Abstract

This invention relates to a method and system for simultaneous login across multiple terminals at a CTC (Central Transportation Center) station. The system includes a requesting terminal and a target terminal interconnected via a communication server. Users log in or log out of their user information on the target terminal. The method includes the following steps: the requesting terminal sends a request message to the target terminal to request user information, which is forwarded to the target terminal by the communication server; upon receiving the request message, the target terminal identifies the corresponding requesting terminal and sends the user information to the requesting terminal via the communication server; the requesting terminal receives the user information from the target terminal, thus synchronizing the user information with the target terminal. This invention enables users to log out or change user information on one terminal and synchronize it to other terminals when multiple terminals are online simultaneously, improving the work efficiency of station personnel.

Description

Technical Field

[0001] This invention relates to the field of multi-terminal synchronous login in railway stations, and specifically to a method and system for multi-terminal synchronous login in CTC stations. Background Technology

[0002] The method and device for simultaneous login and interoperability of multiple terminals in CTC3.0 (Centralized Railway Dispatching System 3.0) stations can facilitate shift handover login for station personnel and improve their work efficiency. Typically, CTC3.0 stations deploy multiple terminals such as track occupancy maps, track occupancy boards, and train operation terminals. Login to multiple terminals during shift handover can be very cumbersome, especially when these terminals are located in different operations rooms or work locations.

[0003] Currently, the station's CTC3.0 equipment, including the Track Gauge Chart (TWG), Track Gauge Board (T3Term), and Train Operation Terminal (STPC), mostly uses A / B machines for redundancy (each device has an A / B version). Information is synchronized between A / B machines of the same type. When station personnel log in on machine A, their login information is automatically synchronized to machine B; similarly, logging out of machine A also automatically synchronizes to machine B. When a duty officer is responsible for the Track Gauge Chart, Train Operation Terminal, and Track Gauge Board simultaneously, they need to log in to either machine A or B, and then log in to both the Train Operation Terminal and Track Gauge Board.

[0004] This device allows users to log in only on the line occupancy map when the station has a line occupancy map, train operation terminal, and line occupancy board; user information is automatically synchronized to other terminals. When only a train operation terminal and line occupancy board are available, users can log in only on the train operation terminal; user information is automatically synchronized to the line occupancy board. If the station only has a line occupancy board, then the board itself also needs login functionality. Summary of the Invention

[0005] The purpose of this invention is to overcome the defects of the prior art and provide a method and system for multi-terminal synchronous login and interoperability of CTC3.0 stations to improve work efficiency and operation efficiency.

[0006] The objective of this invention can be achieved through the following technical solution: According to this invention, a multi-terminal synchronous login method for a CTC station is provided. The CTC station includes a request terminal and a target terminal interconnected via a communication server. The user logs in or logs out of user information on the target terminal. The method includes the following steps:

[0007] S1. The requesting terminal sends a request message to the target terminal to request user information. The request message includes a request entity number for identifying the requesting terminal and a first message header for identifying the information type. The target entity number is attached to the request message and sent to the communication server, which then forwards it to the target terminal.

[0008] S2. After receiving the request message, the target terminal identifies the corresponding requesting terminal by the request entity number and sends a request receipt message containing user information to the requesting terminal through the communication server.

[0009] S3. After receiving the request receipt message from the target terminal, the requesting terminal parses the request receipt message and obtains user information to synchronize the user information with the target terminal.

[0010] Furthermore, the request message sent by the requesting terminal to the target terminal in S1 includes the following:

[0011] S11. Determine whether the requesting terminal is connected to the communication server;

[0012] S12. If the requesting terminal is not connected to the communication server, the request message is not processed; if they are connected, it is determined whether the target terminal is connected to the communication server.

[0013] S13. If the target terminal is connected to the communication server, a request message is sent to the target terminal through the communication server.

[0014] Furthermore, the request message received by the target terminal in S2 includes the following:

[0015] S21. The target terminal receives and parses the request message, and confirms the first message header;

[0016] S22. If the first message header is correct, determine whether the parsed request entity is valid;

[0017] S23. If the request entity is valid, a request receipt message containing user information is sent to the requesting terminal. The request receipt message includes the user login status, user ID, user description, target entity number for identifying the target terminal, and a second message header for identifying the message type.

[0018] Furthermore, the user information received by the requesting terminal in S3 includes the following:

[0019] S31. The requesting terminal receives and parses the request receipt message, and confirms the second message header;

[0020] S32. If the second message header is correct, determine whether the parsed target entity number is consistent with the target entity number in step S1.

[0021] S33. If the target entity number is inconsistent, no action is taken; if the target entity number is consistent, the login status is parsed.

[0022] S34. If the login status is logged out, change the requesting terminal from logged-in to logged-out; if it is logged in, save the user ID and user description to the local machine of the requesting terminal, and then determine whether the requesting terminal has a login window.

[0023] S35. If the user is in the login window, synchronize the user information to the interface and log in; if there is no login window, it means that the user has entered the user interface, and synchronize and update the user information to the user interface.

[0024] Furthermore, when a station deploys three terminals simultaneously—train operation terminal, line occupancy board, and line occupancy map—the requesting terminal is the train operation terminal and the line occupancy board, and the target terminal is the line occupancy map.

[0025] When a station deploys both a train operation terminal and a busy signal board, the requesting terminal is the busy signal board, and the target terminal is the train operation terminal.

[0026] Furthermore, the vehicle operation terminal can designate itself as a target terminal or a requesting terminal based on the terminal deployment situation at the station.

[0027] Furthermore, the requesting terminal periodically sends user request messages to the target terminal.

[0028] Furthermore, after the requesting terminal sends a user request message to the target terminal, if it does not receive user information from the target terminal within a predetermined time, it will automatically set the default user to a logged-in state.

[0029] Furthermore, in step S2, after receiving the request message from the requesting terminal, the target terminal saves the request entity number of the requesting terminal.

[0030] Furthermore, when the user login status of the target terminal changes, including user changes or user logout, the target terminal sends user information to the corresponding requesting terminal based on the saved request entity number.

[0031] The above method is based on a CTC station multi-terminal synchronous login system, which includes:

[0032] The target terminal for users to log in or log out of user information;

[0033] The requesting terminal that establishes a communication connection with the target terminal;

[0034] A communication server that is communicatively connected to both the target terminal and the requesting terminal, the communication server being used to relay communication information between the target terminal and the requesting terminal;

[0035] The requesting terminal is a vehicle service terminal and / or a busy signal board;

[0036] The target terminal includes a vehicle service terminal or a busy signal diagram.

[0037] Preferably, both the target terminal and the requesting terminal are configured with dual-machine redundancy backup.

[0038] In summary, this invention enables users to log off or change user information on one terminal and synchronize the changes to other terminals when multiple terminals are online simultaneously, thereby improving the work efficiency of station staff. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the system according to the first embodiment of the present invention;

[0040] Figure 2 This is a schematic diagram of a system according to a second embodiment of the present invention. Detailed Implementation

[0041] The following detailed description, in conjunction with the accompanying drawings and specific embodiments, provides a further detailed explanation of the CTC station multi-terminal synchronous login method and system proposed in this invention.

[0042] This invention provides a multi-terminal synchronous login method for CTC stations, implemented based on a system comprising the following terminals: a target terminal for users to log in or log out; a request terminal communicating with the target terminal; and a communication server communicating with both the target terminal and the request terminal. The communication server relays communication information between the target terminal and the request terminal. The request terminal may be a train operation terminal and / or a busy signal board configured at the CTC station; the target terminal includes a train operation terminal or a busy signal board configured at the CTC station. Both the target terminal and the request terminal are configured with dual-machine redundancy backup.

[0043] Specifically, when a station deploys three terminals simultaneously—a train operation terminal, a line occupancy display, and a line occupancy map—the requesting terminal is either the train operation terminal or the line occupancy display, and the target terminal is the line occupancy map. When a station deploys two terminals simultaneously—a train operation terminal and a line occupancy display—the requesting terminal is the line occupancy display, and the target terminal is the train operation terminal. Depending on the station's terminal deployment, the train operation terminal needs to configure itself to be either the target terminal or the requesting terminal.

[0044] First Embodiment

[0045] Based on the above system configuration, when the CTC system deploys a line occupancy map, train operation terminal, and line occupancy board at the station, users can log in or log out of their user information on the line occupancy map. Users do not need to manually log in to the train operation terminal or line occupancy board; instead, the train operation terminal and line occupancy board, acting as requesting terminals, will send request messages to the target terminal on the line occupancy map. Figure 1 As shown, the specific steps include:

[0046] S1. The requesting terminal sends a request message to the target terminal. This request message includes a request entity number to identify the requesting terminal and a first message header to identify the information type. The target entity number is appended to the request message, which is then sent to the communication server, which forwards it to the target terminal. Preferably, the requesting terminal sends user request messages to the target terminal periodically (generally every 2 minutes). Preferably, after sending a user request message to the target terminal, if the requesting terminal does not receive a request message from the target terminal within a predetermined time (generally 5 seconds), it automatically sets itself as the default user (this default user data is fixed preset user data), and the requesting terminal is set to a logged-in state.

[0047] S2. After receiving the request message, the target terminal identifies the corresponding requesting terminal by the request entity number and sends a request receipt message to the requesting terminal. Preferably, after receiving the request message from the requesting terminal, the target terminal saves the request entity number of the requesting terminal.

[0048] S3. After receiving the request receipt message from the target terminal, the requesting terminal parses the request receipt message and obtains user information to synchronize the user information with the target terminal.

[0049] In the CTC system, the process of the requesting terminal sending a request message to the target terminal in S1 includes the following:

[0050] S11. Determine whether the requesting terminal is connected to the communication server;

[0051] S12. If the requesting terminal is not connected to the communication server, the request message is not processed, and the judgment is made again in the next communication cycle; if they are connected, the judgment is made on whether the target terminal is connected to the communication server.

[0052] S13. If the target terminal is connected to the communication server, a request message is sent to the target terminal through the communication server.

[0053] It should be noted that the information format of the sent request message is XML format. This XML format message contains a first message header and a request entity number. The first message header is "STA_USER_REQ". Taking the requesting terminal as a vehicle service terminal as an example, the vehicle service terminal writes this XML format message into the communication server and adds four bytes of target entity number, i.e., the line diagram entity information, before the above XML format message.

[0054] The XML request message is forwarded to the target terminal via the communication server, i.e., the busy signal. In step S2, the target terminal receives a request message containing the following:

[0055] S21. The target terminal receives and parses the request message, and determines whether the first message header is "STA_USER_REQ". If the first message header is "STA_USER_REQ", then it continues to parse the message content.

[0056] S22. Determine whether the parsed request entity is valid (whether it is an entity configured in the local entity configuration file entity.cfg, which configures all entities of the CTC system associated with the line diagram);

[0057] S23. If the request entity is valid, a request receipt message containing user information is sent to the requesting terminal, i.e., the vehicle terminal or the busy line. The request receipt message contains the user login status, user ID, user description, target entity number for identifying the target terminal, and a second message header for identifying the message type, which is “STA_USER_UPDATE”.

[0058] The message header is used to distinguish the message type, determining whether it is a request message or a request for receipt message. Each terminal sends a request message containing the first message header "STA_USER_REQ" to distinguish it from a request for receipt message, using the second message header "STA_USER_UPDATE".

[0059] After the requesting terminal receives the request receipt message in S3, that is, after the vehicle terminal or the busy line board receives the information, the specific process is as follows:

[0060] S31. The requesting terminal receives and parses the request receipt message, and confirms the second message header;

[0061] S32. If the second message header is “STA_USER_UPDATE”, then determine whether the parsed target entity number is consistent with the target entity number in step S1.

[0062] S33. If the target entity number is inconsistent, no action is taken; if the target entity number is consistent, the login status is parsed.

[0063] S34. If the login status is logged out, change the requesting terminal from logged-in to logged-out; if it is logged in, save the user ID and user description to the local machine of the requesting terminal, and then determine whether the requesting terminal has a login window.

[0064] S35. If the user is in the login window, synchronize the user information to the interface and log in; if there is no login window, it means that the user has entered the user interface, and synchronize and update the user information to the user interface.

[0065] Second Embodiment

[0066] like Figure 2As shown, when the station only deploys a train operation terminal and a busy line board, users need to log in on the train operation terminal, and user information is automatically synchronized to the busy line board.

[0067] Similar to the above, when it is confirmed that the communication server, vehicle terminal, and busy signal board are all communicating normally, the busy signal board implements user information synchronization through the following process:

[0068] After receiving a busy user request message, the vehicle terminal checks whether the message header is "STA_USER_REQ". If so, it parses the message.

[0069] Parse out the request entity; if the entity number is valid, add it to the request entity number list maintained by the vehicle terminal.

[0070] The terminal sends a message to the requesting entity, consisting of its own login status, user ID, and user description, along with the message header "STA_USER_UPDATE".

[0071] Similar to the first embodiment described above, when the vehicle terminal switches users or logs out a user, it sends the user information or login status to the request entities in the request list (here referring to each busy line).

[0072] The logic for handling busy signals is the same as in the first embodiment, and will not be repeated here.

[0073] Through the above steps and methods, the vehicle service terminal synchronizes its user information and login status with the busy board.

[0074] Compared with the prior art, the present invention has the following beneficial effects:

[0075] This invention enables the automatic synchronization of user information to other terminals when one terminal logs off or a shift changes, thus improving the work efficiency of station staff.

[0076] Although the present invention has been described in detail through the preferred embodiments above, it should be understood that the above description should not be considered as a limitation of the present invention. Various modifications and substitutions to the present invention will be apparent to those skilled in the art after reading the above description. Therefore, the scope of protection of the present invention should be defined by the appended claims.

Claims

1. A CTC station multi-terminal synchronous login method, the CTC station comprising a request terminal and a target terminal interconnected through a communication server, characterized in that, The user logs in or logs out the user information on the target terminal, comprising the following steps: S1, the request terminal sends a request message to the target terminal to request to obtain the user information, the request message comprising a request entity number for identifying the request terminal and a first message header for identifying the information type, and the target entity number is attached to the request message and sent to the communication server, and forwarded to the target terminal by the communication server; S2, after the target terminal receives the request message, the corresponding request terminal is identified through the request entity number, and the request terminal is sent a request reply message comprising the user information by the communication server; S3, after the request terminal receives the request reply message of the target terminal, the request reply message is parsed to obtain the user information and realize the user information synchronization with the target terminal; When the station simultaneously deploys the train terminal, the busy board and the busy chart, the request terminal is the train terminal and the busy board, and the target terminal is the busy chart; When the station simultaneously deploys the train terminal and the busy board, the request terminal is the busy board, and the target terminal is the train terminal; The request message received by the target terminal in S2 comprises the following contents: S21, the target terminal receives and parses the request message, and confirms the first message header; S22, if the first message header is correct, it is judged whether the parsed request entity is valid; S23, if the request entity is valid, the request terminal is sent a request reply message comprising the user information, the request reply message comprising the user login state, the user code, the user description, and the target entity number for identifying the target terminal, and the second message header for identifying the message type; The request terminal receives the user information in S3, comprising the following contents: S31, the request terminal receives and parses the request reply message, and confirms the second message header; S32, if the second message header is correct, it is judged whether the parsed target entity number is consistent with the target entity number in S1; S33, if the target entity number is not consistent, it is not processed; if the target entity number is consistent, the login state is parsed; S34, if the login state is the logout state, the request terminal is changed from the login state to the logout state; if it is the login state, the user code and the user description are saved to the local of the request terminal, and it is judged whether the request terminal has a login window; S35, if it is in the login window interface, the user information is synchronized to the interface and logged in; If there is no login interface, it means that the user interface has been entered, and the user information is synchronized and updated to the user interface.

2. The CTC station multi-terminal simultaneous login method of claim 1, wherein, The request terminal sends the request message to the target terminal in S1, comprising the following contents: S11, it is judged whether the request terminal is connected with the communication server; S12, if the request terminal is not connected with the communication server, the request message is not processed; if it is connected, it is judged whether the target terminal is connected with the communication server; S13, if the target terminal is connected with the communication server, the request message is sent to the target terminal through the communication server.

3. The CTC station multi-terminal simultaneous login method of claim 1, wherein, The train terminal is configured to be the target terminal or the request terminal according to the deployment of the terminal in the station.

4. The CTC station multi-terminal simultaneous login method of claim 1, wherein, The request terminal sends the user request message to the target terminal in a timely manner.

5. The CTC station multi-terminal simultaneous login method of claim 4, wherein, If the request terminal does not receive the user information fed back by the target terminal within a predetermined time after sending the user request message to the target terminal, the request terminal is automatically set as the default user in the logged-in state.

6. The CTC station multi-terminal simultaneous login method of claim 1, wherein, In S2, the target terminal saves the request entity number of the request terminal after receiving the request message from the request terminal.

7. The CTC station multi-terminal simultaneous login method of claim 6, wherein, When the user login state of the target terminal changes, including user change and user logout, the target terminal sends the user information to the corresponding request terminal according to the saved request entity number.

8. A CTC station multi-terminal synchronous login system for implementing the login method according to any one of claims 1 to 7, characterized in that, Comprise: A target terminal for user login or logout of user information; A request terminal in communication connection with the target terminal; A communication server in communication connection with the target terminal and the request terminal, and used for transferring the communication information of the target terminal and the request terminal; The request terminal is a train operation terminal and / or a busy board; The target terminal includes a train operation terminal or a busy board.

9. The CTC station multi-terminal synchronous login system according to claim 8, wherein, Both the target terminal and the request terminal are set as dual-machine redundant backup.

Images