CN111698329A - Station server communication method and system - Google Patents
Station server communication method and system Download PDFInfo
- Publication number
- CN111698329A CN111698329A CN202010539046.6A CN202010539046A CN111698329A CN 111698329 A CN111698329 A CN 111698329A CN 202010539046 A CN202010539046 A CN 202010539046A CN 111698329 A CN111698329 A CN 111698329A
- Authority
- CN
- China
- Prior art keywords
- server
- station
- communication
- sle
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Medical Informatics (AREA)
- Cardiology (AREA)
- Hardware Redundancy (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a station server communication system, which comprises an SC system, an LC and an SLE, wherein the SC system comprises: the communication server is an interface between the SC system and the SLE and is used for communicating with each SLE, forwarding the data sent by the SLE to the LC system in a classified manner, and sending the data and the instruction of the LC system to the designated SLE; the execution server is connected with the communication server; and the Rabbit server is used for realizing mutual communication between the execution servers through the MQ message middleware cluster. The invention discloses a station server communication method. When a certain server in a certain central server system fails, the central server system can be processed by corresponding servers in other central server systems, and the central server system cannot work normally.
Description
Technical Field
The invention relates to the technical field of rail transit, in particular to a station server communication method and system.
Background
With the rapid development of electronic commerce and cloud computing, enterprises pay more and more attention to the reliability of data services, if data is lost or damaged, huge losses can be caused to the enterprises, and a central management technology can ensure that a system can continuously provide services, so that the central management technology is a key technology for ensuring the reliability of the enterprise services. In the urban rail transit field, the architecture and future definitions of SC (station management) systems are constantly explored and tried from place to place across the country in order to adapt more quickly to changes in new payment modes, multiple operating agents and management modes. Because the SC system is closely coupled with the devices in each station in terms of service function and operation, and the SC system needs to manage numerous station devices, the normal operation of the SC system will have a significant impact on the station to which it belongs, and based on this, the SC system should first ensure extremely high reliability and operation speed.
For urban rail transit, a server failure can cause a serious problem, and the reasons for the server failure are many, and may be equipment failure, operating system failure, or software failure. When the server fails, the server can normally operate again only by removing the failures one by one, and the shutdown of the server before the normal operation is less than dozens of minutes and more than dozens of hours. For an urban rail transit system with extremely large pedestrian flow, the server system cannot work normally due to any server failure, and serious consequences can be caused.
When the SC system connection is interrupted, a reconnection is required. In the prior art, a rabbitmq component broken link reconnection mechanism or an automatic reconnection mechanism of a JBoss connection pool is adopted.
In the mechanism for disconnecting and reconnecting the rabbitmq component, a status is set for the rabbitmq when the SC system is started, the rabbitmq is changed into true when the connection is established for the first time, a timer is started by the rabbitmq client when the client is initialized, a thread is started at intervals, the state of the current status is inquired, and if the status is changed into false, the connection (including connection of connection and channel) is reestablished.
In an automatic reconnection mechanism of a JBoss connection pool, the JBoss connection pool is not set to be automatically reconnected by default, and a data source configuration file needs to be modified when the JBoss connection pool is set. Xml (this is a data source configuration file installed by default). To this file, add the configuration of the failed connection check class as follows:
<exception-sorter-class-name>
org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
</exception-sorter-class-name>
this class is used to check for failed connections in the connection pool, i.e. connections that have been interrupted from the database and are invalid, and after checking out, removes the failed connections from the connection pool, preventing the user from obtaining the invalid connections. Therefore, once the invalid connection is disconnected, the invalid connection is moved out of the connection pool, if the network is recovered, the user cannot acquire the invalid connection, and the connection pool can acquire a new database connection again. The existing rabbitMQ reconnection mechanism is based on a characteristic of the rabbitMQ, when the rabbitMQ cannot realize the reconnection, or a problem occurs in a current environment network, the reconnection fails, so that the problem that a production environment system cannot normally operate occurs, and the system paralysis can be caused under the condition to influence the stability and the reliability of the production system. The automatic reconnection of the JBoss connection pool is also based on the detection of the JBoss connection pool, a background system cannot acquire the abnormal condition of the database, and the system still transmits data to the database, so that the data loss and the incomplete condition of the data are caused.
In summary, after the communication connection of the existing SC system is interrupted, the adopted reconnection mechanisms all lack flexible adaptability and cannot completely adapt to the operation requirements.
Disclosure of Invention
In order to solve the technical problems in the background art, the invention provides a station server communication method and a station server communication system, which are used for solving the problem that a station server system cannot work normally due to server failure.
The station server communication system provided by the invention is characterized by comprising an SC system, an LC and an SLE, wherein the SC system comprises:
the communication server is an interface between the SC system and the SLE and is used for communicating with each SLE, forwarding the data sent by the SLE to the LC system in a classified manner, and sending the data and the instruction of the LC system to the designated SLE;
the execution server is connected with the communication server;
and the Rabbit server is used for realizing mutual communication between the execution servers through the MQ message middleware cluster.
Preferably, the execution server is divided into a service server, a data processing server, a state server and an archiving server.
Preferably, the rabbitserver specifically includes: taking the deviceId of the target server as a binding _ key, and judging whether the target server is online or not; if the target server is on line, the target server can automatically establish a temporary queue of the target server and bind the temporary queue to the exchange and the key, and then data transceiving is carried out between the SLE and each execution server and between the communication server and each execution server through a RabbitMQ.
Preferably, the target server is a communication server or an execution server.
The invention provides a station server communication method, which comprises the following steps:
the Rabbit server sends exchange messages of each execution server in the SC system to the target server, and the messages carry the deviceId of the target server;
the Rabbit server takes the deviceId of the target server as a binding _ key and judges whether the target server is online or not;
if the target server is on line, the target server can automatically establish a temporary queue of the target server and bind the temporary queue to the exchange and the key, and then data transceiving is carried out between the SLE and each execution server and between the communication server and each execution server through a RabbitMQ;
if the target server is not on-line, all messages sent by the Rabbit server to the target server are automatically discarded.
Preferably, the data uploaded by the SLE includes station notification data, station state data and station transaction data.
Preferably, the target server is a communication server or SLE.
In the invention, the resources of the urban station server system are called as much as possible, and the data retention caused by busy corresponding stations in a certain period and insufficient self processing capacity of the central server system is avoided, and meanwhile, the resources of the central server system are idle. Meanwhile, when a certain server in a certain central server system fails, the failure can be processed by corresponding servers in other central server systems, and the central server system cannot work normally. As a further improvement of a communication method and a server system, data uploaded by the station computer system comprise station notification data, station state data and station transaction data, and data transceiving is performed through the RabbitMQ, so that the advantages of high concurrency and simple cluster deployment of the RabbitMQ are fully exerted, and the reliability of data classification transceiving and the stability of the system are improved.
Drawings
Fig. 1 is a structural diagram of a station server communication system according to an embodiment of the present invention;
fig. 2 is a flowchart of a station server communication method according to an embodiment of the present invention.
Detailed Description
Embodiment 1 of the present invention provides a station server communication system, as shown in fig. 1, including an SC (station management) system, an LC (line center), and an SLE (station terminal equipment). Wherein the content of the first and second substances,
the SC system is used for station operation control, ticket management, operation monitoring, operation parameter management, report providing and the like; the specific operation process comprises the following steps: receiving AFC (automatic fare collection) parameters sent by the LC and sending the AFC parameters to the SLE; and receiving the state and the operation data sent by the SLE, monitoring the station operation condition, realizing the control and the field management of the SLE, and sending the operation data to the LC.
And the LC is used for managing the operation of the line system and managing each station system in the line. The specific operation process comprises the following steps: LC downloads ticket operation parameters from ACC (clearing center), and defines AFC system parameters in combination with line operation management; sending the AFC system parameters to an SC system for use; the LC receives the SLE state uploaded by the SC system and carries out operation monitoring; the LC receives the operation data uploaded by the SC system and processes the operation data; the LC transmits the transaction data required by the ACC to the ACC, and the transaction data and the ACC are cleared and reconciled; and the LC controls the access of personnel in each station through authority management and records various operation conditions.
The SLE is a passenger service terminal in a station AFC system and is used for selling, checking and checking tickets. The specific operation process comprises the following steps: receiving a command and a parameter sent by the SC system, and operating according to the command and the parameter to realize a corresponding function; collecting ticket transaction data generated by the TPU (ticket processing unit), generating operation data and information of each state and the like, and uploading the operation data and the information to the SC system.
In the invention, the SC system comprises a communication server, an execution server and a Rabbit server. The invention is based on a plurality of server cluster systems, a plurality of SC systems are mutually redundant and backup, a Rabbit server in the SC system is connected with a communication server of the SC system and is also connected with communication servers of other SC systems; the communication server of the SC system is connected with the execution server of the SC system and is also connected with the execution servers of other SC systems. And the Rabbit server of each SC system is connected with the SLE corresponding to the SC system. Each SC system processes the station related data corresponding to the SC system in a normal state, when the communication server and the execution server of the SC system are busy and have no idle thread or the servers are in failure, the corresponding Rabbit server can search the communication servers available for the idle thread in other SC systems for classified delivery processing, and meanwhile, the communication server can also search the corresponding execution servers available for the idle thread in other SC systems for processing.
The communication server is an interface between the SC system and the SLE, and is used for communicating with each SLE, forwarding data sent by the SLE to the LC system in a classified manner, and sending data and instructions of the LC system to the designated SLE;
and the execution server is connected with the communication server and is divided into a business server, a data processing server, a state server, a filing server and the like according to different functions.
(1) And the service server is used for processing various AFC core services, including maintenance of various time sequences, operation management, parameter and software management, authority management, ticket management, account checking management, audit management and the like.
(2) The data processing server is used for managing the original transaction and storing the data processing result in a database; and (4) performing time sequence control and parameter updating management on various service functions predefined in the system.
(3) The state server is used for monitoring and counting the states of all relevant equipment on each station in real time; the system is responsible for calculating the comprehensive station state value according to the state of the station equipment; and sending the station and equipment state information for making the subscription to the corresponding workstation according to the station and equipment state information subscribed by the MLC workstation.
(4) And the archiving server is used for receiving the transaction data from the Rabbit server, storing different transaction data in different directories respectively and archiving different transaction data. The aim of the archive server is to store data entering the SC system, whether from the SLE or the LC, uniformly, and avoid writing files everywhere by each other background server.
The Rabbit server is used for realizing the mutual communication among 4 execution servers such as a service server, a state server, a data processing server, an archiving server and the like, and the five servers are communicated with each other through the MQ message middleware cluster. The Rabbit server is used for sending the messages of all the execution servers in the SC system to a plurality of communication servers and a plurality of workstations; since the number and existence of messages cannot be determined in advance, no corresponding persistent queue is established between the n communication servers and the m workstations, so if an execution server wants to send a message to a certain communication server or workstation, only an exchange message needs to be sent to a target server, and the deviceId (device address) of the target server is used as a binding _ key; if the target server is on line, the target server can automatically establish a temporary queue of the target server and bind the temporary queue to the exchange and the key, and then the target server can receive the message sent by the execution server; if the target server is not online, all messages sent to the target server will be automatically discarded.
The resource backup of the communication server, the execution server and the RabbitMQ server is mainly completed through main-standby switching, and when the memory of one server overflows or the system crashes, the standby server is switched. In addition, resource backup can be realized, and interactive information such as transaction, command, parameters and the like can be stored to a backup filing server at regular time or in real time, so that the later search is facilitated.
Embodiment 1 of the present invention provides a station server communication method, as shown in fig. 2, including the following steps:
And step 104, if the target server is not on line, automatically discarding all messages sent to the target server by the Rabbit server.
The invention provides a station server communication method, wherein a plurality of upper and lower interactions exist in the establishment of connection between a station SC and a station LC, the establishment of connection between the station SC and the station LC is taken as an example to describe the communication interaction between an SC system and the station LC, the conventional socket connection mode is broken, Rabbit is adopted for direct connection, corresponding data can be obtained directly by binding required key values on a queue, and the data transmission is more stable and convenient, and the specific steps comprise:
step 201, the SC system sends a connection authentication request to the LC, where the request carries information such as an SC system IP address and an SC system ID; the LC checks whether the information such as the SC system IP address, the SC system ID and the like is consistent with the deployment information in the LC, and if not, the information is illegal.
Step 202, when the SC system is illegal, the synchronization sequence is stopped, the LC returns authentication failure, and the SC system disconnects the RabbitMQ circuit; when the SC system is legal, the deviceId of the SC system is used as the binding _ key, the temporary queue of the SC system can be automatically established and bound to the key, and the message sent by the LC can be received.
Step 203, the SC system uses NTP protocol to carry out clock synchronization with LC; if the operation days before and after the clock synchronization are inconsistent, local operation day switching is firstly carried out; then, executing a sub-time sequence of parameter synchronization, wherein the sub-time sequence comprises two conditions, namely when an upper level initiates a parameter synchronization process with a lower level; one is referred to by the set-up connection sequence.
And step 204, after the sub-sequence is completed, the SC system reports the operation state of the SC system to the LC, wherein the operation state comprises the operation mode of a station, the 24-hour operation state, the extended operation state and the like.
Step 205, the LC checks the operation state of the SC system, and issues a corresponding control command to the state inconsistent with the upper requirement;
if the SC operation mode is inconsistent with the LC, the LC reissues an operation mode control command to the SC, and the SC uploads operation mode state change data to the LC; if the SC 24-hour operation state is inconsistent with the LC, the LC reissues a 24-hour operation control command to the SC, and the SC uploads 24-hour operation state change data to the LC; if the SC extended operation state is not consistent with the LC, the LC transmits an extended operation time command to the SC, and the SC uploads extended operation state change data to the LC. The operation mode, the 24-hour operation state and the extended operation state are the working states of the specified station and equipment.
And step 206, when the LC determines that no new operation state control command needs to be sent, sending an upper synchronization data completion notification to the SC system, indicating that the LC has sent all the information in the time sequence. When the LC considers that no new operation state control command needs to be sent again, the LC sends a 'upper synchronous data completion notice' to the SC system, which indicates that the LC has sent all the completion information in the synchronous sequence.
Step 207, the SC system reports the current states of all the online SLEs to the LC (after the SC receives the "upper synchronization data completion notification" sent by the LC, the SC system reports the current state of the online SLE of the station to the LC, and the reporting is not required when the station is not online).
Step 208, the SC system reports the SC complete status to the LC (sends the SC complete status to the LC, and then the "SC-LC connection establishment" synchronization sequence is normally ended); the end of the whole time sequence is indicated at the moment; at this point, the SC system can continue its next operation and, if there is no data to be uploaded, immediately start uploading the data.
Step 209, the SC system uploads the transaction/service data that is not uploaded, including the clock difference service data generated in the time sequence and the program/parameter version change service data.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be considered to be within the technical scope of the present invention, and the technical solutions and the inventive concepts thereof according to the present invention should be equivalent or changed within the scope of the present invention.
Claims (7)
1. The station server communication system is characterized by comprising an SC system, an LC and an SLE, wherein the SC system comprises:
the communication server is an interface between the SC system and the SLE and is used for communicating with each SLE, forwarding the data sent by the SLE to the LC system in a classified manner, and sending the data and the instruction of the LC system to the designated SLE;
the execution server is connected with the communication server;
and the Rabbit server is used for realizing mutual communication between the execution servers through the MQ message middleware cluster.
2. The station server communication system according to claim 1, wherein the execution server is divided into a service server, a data processing server, a status server, and an archive server.
3. The station server communication system according to claim 1, wherein the rabbitserver specifically includes: taking the deviceId of the target server as a binding _ key, and judging whether the target server is online or not; if the target server is on line, the target server can automatically establish a temporary queue of the target server and bind the temporary queue to the exchange and the key, and then data transceiving is carried out between the SLE and each execution server and between the communication server and each execution server through a RabbitMQ.
4. The station server communication system according to claim 3, wherein the target server is a communication server or an execution server.
5. A station server communication method is characterized by comprising the following steps:
the Rabbit server sends exchange messages of each execution server in the SC system to the target server, and the messages carry the deviceId of the target server;
the Rabbit server takes the deviceId of the target server as a binding _ key and judges whether the target server is online or not;
if the target server is on line, the target server can automatically establish a temporary queue of the target server and bind the temporary queue to the exchange and the key, and then data transceiving is carried out between the SLE and each execution server and between the communication server and each execution server through a RabbitMQ;
if the target server is not on-line, all messages sent by the Rabbit server to the target server are automatically discarded.
6. The station server communication method according to claim 5, wherein the data uploaded by the SLE includes station notification data, station state data, and station transaction data.
7. The station server communication method according to claim 5, wherein the target server is a communication server or an SLE.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010539046.6A CN111698329A (en) | 2020-06-13 | 2020-06-13 | Station server communication method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010539046.6A CN111698329A (en) | 2020-06-13 | 2020-06-13 | Station server communication method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111698329A true CN111698329A (en) | 2020-09-22 |
Family
ID=72480915
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010539046.6A Pending CN111698329A (en) | 2020-06-13 | 2020-06-13 | Station server communication method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111698329A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106453541A (en) * | 2016-09-30 | 2017-02-22 | 厦门中控生物识别信息技术有限公司 | Data synchronization method, server and data synchronization system |
| JP2018092535A (en) * | 2016-12-07 | 2018-06-14 | 株式会社東芝 | Station service system, server and station service terminal |
| CN109741121A (en) * | 2018-09-29 | 2019-05-10 | 比亚迪股份有限公司 | AFC system and Rail Transit System based on ActiveMQ |
| CN110428167A (en) * | 2019-07-31 | 2019-11-08 | 郑州地铁集团有限公司 | Method and system are assigned in a kind of rail traffic server parameter order |
| CN110535924A (en) * | 2019-07-31 | 2019-12-03 | 郑州地铁集团有限公司 | A kind of rail traffic server communications method and system |
-
2020
- 2020-06-13 CN CN202010539046.6A patent/CN111698329A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106453541A (en) * | 2016-09-30 | 2017-02-22 | 厦门中控生物识别信息技术有限公司 | Data synchronization method, server and data synchronization system |
| JP2018092535A (en) * | 2016-12-07 | 2018-06-14 | 株式会社東芝 | Station service system, server and station service terminal |
| CN109741121A (en) * | 2018-09-29 | 2019-05-10 | 比亚迪股份有限公司 | AFC system and Rail Transit System based on ActiveMQ |
| CN110428167A (en) * | 2019-07-31 | 2019-11-08 | 郑州地铁集团有限公司 | Method and system are assigned in a kind of rail traffic server parameter order |
| CN110535924A (en) * | 2019-07-31 | 2019-12-03 | 郑州地铁集团有限公司 | A kind of rail traffic server communications method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109901949B (en) | Application disaster recovery system and method for double-activity data center | |
| CN103226502B (en) | A kind of data calamity is for control system and data reconstruction method | |
| CN110535924B (en) | Rail transit server communication method and system | |
| US7593351B1 (en) | Method and system for collecting and consolidating network traffic information | |
| CN108712501B (en) | Information sending method and device, computing equipment and storage medium | |
| CN102355368B (en) | Fault processing method of network equipment and system | |
| CN101751415B (en) | Metadata service system, metadata synchronized method and writing server updating method | |
| CN102088490B (en) | Data storage method, device and system | |
| EP2723017A1 (en) | Method, apparatus and system for implementing distributed auto-incrementing counting | |
| US8301750B2 (en) | Apparatus, system, and method for facilitating communication between an enterprise information system and a client | |
| CN108512753B (en) | Method and device for transmitting messages in cluster file system | |
| CN102195786B (en) | Intelligent data exchange platform and method | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN103929455A (en) | Asynchronous file transmission system and method comprising network storage equipment | |
| CN112637277A (en) | Station center system based on cloud platform and control method | |
| KR100205953B1 (en) | Charging data transmitter and method for processing integrative charge in full-electronic exchange | |
| CN111698329A (en) | Station server communication method and system | |
| CN109039427B (en) | Ship monitoring management device | |
| CN111601299B (en) | Information association backfill system under 5G framework | |
| CN114978885A (en) | Log management method and device, computer equipment and system | |
| CN114422335A (en) | Communication method, communication device, server and storage medium | |
| KR100970211B1 (en) | Method and Apparatus for Monitoring Service Status Via Special Message Watcher in Authentication Service System | |
| CN114625578A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN103023697B (en) | A kind of management method, Apparatus and system of array multipath | |
| US7644306B2 (en) | Method and system for synchronous operation of an application by a purality of processing units |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200922 |