CN114596640B - Automatic monitoring method, device, equipment and medium for ticket checking system - Google Patents

Automatic monitoring method, device, equipment and medium for ticket checking system Download PDF

Info

Publication number
CN114596640B
CN114596640B CN202011310510.0A CN202011310510A CN114596640B CN 114596640 B CN114596640 B CN 114596640B CN 202011310510 A CN202011310510 A CN 202011310510A CN 114596640 B CN114596640 B CN 114596640B
Authority
CN
China
Prior art keywords
ticket checking
passenger flow
flow volume
servers
standby
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.)
Active
Application number
CN202011310510.0A
Other languages
Chinese (zh)
Other versions
CN114596640A (en
Inventor
张广鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BYD Co Ltd
Original Assignee
BYD Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by BYD Co Ltd filed Critical BYD Co Ltd
Priority to CN202011310510.0A priority Critical patent/CN114596640B/en
Publication of CN114596640A publication Critical patent/CN114596640A/en
Application granted granted Critical
Publication of CN114596640B publication Critical patent/CN114596640B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07BTICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B11/00Apparatus for validating or cancelling issued tickets
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/10Movable barriers with registering means
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)

Abstract

The application discloses an automatic monitoring method, device, equipment and medium for a ticket checking system. The method comprises the following steps: acquiring real-time passenger flow of at least one line; searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data; and determining to turn on or off at least one standby ticket checking server based on the passenger flow volume interval and the passenger flow volume standard data. The problem of the data processing resource waste in the ticket checking system is solved.

Description

Automatic monitoring method, device, equipment and medium for ticket checking system
Technical Field
The application relates to the technical field of rail transit, in particular to an automatic monitoring method, device, equipment and medium of a ticket checking system.
Background
The automatic ticket selling and checking system (Automatic Fare Collection System, AFC) is a system for realizing ticket selling, ticket checking, charging, statistical analysis, management and other functions in the rail transit operation process.
In an automatic ticket vending and checking system, a ticket checking system for realizing a ticket checking function generally comprises a gate and a ticket checking server, wherein after the gate acquires inbound information or outbound information, a ticket checking request can be sent to the ticket checking server, and whether the gate is opened for a user to pass is determined based on a ticket checking request result returned by the ticket checking server.
In the related art, in a rail transit, a plurality of ticket checking servers are usually deployed for performing ticket checking service, and when the passenger flow is smaller, some ticket checking servers are in an idle running state, so that data processing resources are wasted.
Disclosure of Invention
In view of the foregoing drawbacks or shortcomings in the prior art, it is desirable to provide a ticketing system automatic monitoring method, apparatus, device, and medium that can rationally allocate data processing resources.
In a first aspect, the present application provides a method for automatically monitoring a ticket checking system, including:
acquiring real-time passenger flow of at least one line;
searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data;
determining to turn on or off at least one standby ticket server based on the passenger flow volume interval and the passenger flow volume standard data;
in a second aspect, the present application provides a computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor being adapted to implement the method as in the first aspect when the program is executed;
in a third aspect, the present application provides a computer readable storage medium having stored thereon a computer program for implementing a method as in the first aspect.
The technical scheme provided by the embodiment of the application can comprise the following beneficial effects:
the automatic monitoring method, the device, the equipment and the medium of the ticket checking system provided by the embodiment of the application can acquire the real-time passenger flow of at least one line; searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data; based on the passenger flow volume interval and the passenger flow volume standard data, at least one standby ticket checking server is determined to be started or stopped, and the ticket checking server can be flexibly allocated according to the real-time passenger flow volume, so that the waste of data processing resources is prevented.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 is a schematic diagram of an implementation environment of an automatic monitoring method of a ticket checking system according to an embodiment of the present application;
FIG. 2 is a schematic flow chart of an automatic monitoring method for a ticket checking system according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of another automatic monitoring method for ticket checking system according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an interaction flow of an automatic monitoring method of a ticket checking system according to an embodiment of the present application;
FIG. 5 is a schematic flow chart of another automatic monitoring method for ticket checking system according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an interaction flow of another automatic monitoring method for a ticket checking system according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an automatic monitoring device of a ticket checking system according to an embodiment of the present application;
FIG. 8 is a schematic structural diagram of another automatic monitoring device for ticket checking system according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
The application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be noted that, for convenience of description, only the portions related to the application are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
Fig. 1 is a schematic diagram of an implementation environment of an automatic monitoring method of a ticket checking system according to an embodiment of the present application. As shown in fig. 1, the implementation environment includes: the cloud monitoring device 110 is connected with each ticket checking server 120, the cloud monitoring device 110 is also connected with the manager terminal 140, the gate 130 is connected with the ticket checking server 120, the gates can be connected to the same ticket checking server 120, and the database server 150 is respectively connected with the cloud monitoring device 110 and each ticket checking server 120, wherein the connection mode can be a wired network or a wireless network connection.
The gate 130 is configured to send a ticket checking request to the ticket checking server 120 after obtaining the inbound information or the outbound information, the ticket checking server 120 may generate a ticket checking request result based on the ticket checking request, send the ticket checking request result to the gate 130, and the gate 130 determines whether to open the gate for the user to pass based on the ticket checking request result, and meanwhile, the ticket checking server 120 sends the ticket checking request result to the database server 150 for storage.
The database server 150 is configured to receive the ticket checking request result sent by the ticket checking server 120, add 1 to the passenger flow volume of the line corresponding to the gate 130 if the ticket checking request result is that the user is allowed to pass, and store the updated passenger flow volume.
For each line, the cloud monitoring device 110 is configured to obtain real-time traffic of the line from the database server 150, and search a traffic zone corresponding to the real-time traffic based on predetermined traffic standard data; and determining to turn on or turn off at least one standby ticket checking server based on the passenger flow volume interval and the passenger flow volume standard data.
The cloud monitoring device 110 is further configured to send device information of a ticket checking server 120 to the administrator terminal 140 after determining that the ticket checking server 120 is turned on or turned off, so that an administrator can know the real-time running condition of the ticket checking server in time.
It can be understood that the cloud monitoring device 110 may be a computer, a server or a terminal with data processing capability, and may be applied to railway track traffic or underground track traffic to monitor the working state and number of ticket checking servers, and allocate the ticket checking servers to prevent the waste of data processing resources.
The embodiment of the application provides an automatic monitoring method of a ticket checking system, which is applied to cloud monitoring equipment shown in fig. 1, and the embodiment of the application uses the cloud monitoring equipment to explain the automatic monitoring method of the ticket checking system in underground rail transit, and as shown in fig. 2, the method comprises the following steps:
step 201, obtaining real-time passenger flow volume of at least one line.
In the embodiment of the application, the underground rail transit generally comprises a plurality of running lines, the cloud monitoring equipment can monitor the ticket checking system corresponding to at least one line, wherein the number of the lines which can be monitored by the cloud monitoring equipment can be determined based on actual needs, and the embodiment of the application is not limited to the above.
In this step, for at least one line monitored by the cloud monitoring device, when it is determined that the current time is the line start time, the real-time passenger flow volume of the at least one line may be obtained from the database server.
For example, assuming that a subway in a city has 12 lines, the subway starts to run at 6 o 'clock every day, and the cloud monitoring device needs to monitor a ticket checking system of the 12 lines, the cloud monitoring device determines that when the current time is 6 o' clock at a am, real-time passenger flow of each line in 1 minute at the current time is read from a database server every 50 ms.
Step 202, searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data.
In the embodiment of the application, the passenger flow standard data can be divided into two types according to the types of ticket checking servers in the ticket checking system, wherein at least two ticket checking servers with different data processing capacities exist in the first type of ticket checking system, and the data processing capacities of each ticket checking server in the second type of ticket checking system are the same.
Optionally, when the ticket checking system is a first type ticket checking system, the standard passenger flow data may be a corresponding relation between a passenger flow interval and a standard ticket checking processing capability value, so as to indicate that when the real-time passenger flow belongs to the passenger flow interval, the ticket checking processing capability value of the ticket checking server currently in a ticket checking request authentication state (running state) is ensured to be the standard ticket checking processing capability value, so that normal ticket checking of the gate can be ensured, no burden is caused to the ticket checking server processing data, and no empty running state of the ticket checking server occurs; the ticket checking processing capability value is a standardized value of the data processing capacity of the ticket checking server, and in the embodiment of the application, the smaller the value is, the weaker the data processing capability of the ticket checking server is.
The determining process for determining the ticket checking processing capability value may be: and determining the data processing amount of each ticket checking server, and determining the ratio of the data processing amount of each ticket checking server to the data quantization standard based on the data quantization standard, wherein the ratio is the ticket checking processing capacity value of the ticket checking server. For example, assuming that the data quantization standard is 200 persons/min, the data processing capacity of one ticket checking server can process ticket checking request authentication of 200 persons per minute in a standard state; if the data processing capacity of a certain ticket checking server is 400 persons/min, the ticket checking processing capacity value of the ticket checking server is 2. It will be appreciated that the data quantization criteria may be determined based on actual needs, and the embodiments of the present application are not limited in this regard.
When the ticket checking system is the second type ticket checking system, the passenger flow standard data can be the corresponding relation between the passenger flow interval and the standard ticket checking server number, and is used for indicating that when the real-time passenger flow belongs to the passenger flow interval, the normal ticket checking of the gate can be ensured as long as the ticket checking server number in the ticket checking request authentication state (running state) is ensured to be the standard ticket checking server number.
It may be appreciated that, for at least one line, before the system is put into use, standard passenger flow data corresponding to the line may be predetermined, after the real-time passenger flow of the line is obtained, the number of standby ticket checking servers corresponding to the real-time passenger flow may be determined based on the real-time passenger flow and the passenger flow standard data, the number of standby ticket checking servers corresponding to the number of standby ticket checking servers may be turned on or off, and the data processing resource configuration of the ticket checking system may be optimized.
Optionally, for each line, the implementation manner of determining the passenger flow volume standard data corresponding to the line may be: the manager determines the standard data of the passenger flow volume corresponding to the line based on the actual experience and the historical data corresponding to the line, or the cloud monitoring equipment performs big data analysis on the historical data based on the historical data to determine the standard data of the passenger flow volume corresponding to the line. It may be understood that, in the embodiment of the present application, after a specified period of time, the cloud monitoring device may update the traffic standard data corresponding to the line, and the process of updating the traffic standard data may refer to the process of determining the traffic standard data corresponding to the line based on the historical data, which is not described in detail in the embodiment of the present application.
When the ticket checking system is a first type ticket checking system, the cloud monitoring device determines the passenger flow standard data corresponding to the line based on the historical data, which may be: acquiring and counting a plurality of historical passenger flows in a historical period from a database server, and acquiring historical ticket checking processing capacity values corresponding to each historical passenger flow; determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable; determining a historical ticket checking processing capacity value corresponding to the historical passenger flow belonging to each passenger flow interval; determining a mode of the plurality of historical ticket checking processing capability values as a standard ticket checking processing capability value corresponding to the passenger flow volume interval; and determining a plurality of passenger flow volume intervals and standard ticket checking processing capacity values corresponding to each passenger flow volume interval as passenger flow volume standard data.
The passenger flow variable is the difference between the maximum value and the minimum value of the passenger flow interval, and can be determined based on actual requirements, which is not limited by the embodiment of the application; the history period is a history time length for acquiring the historical passenger flow volume, and can also be determined based on actual needs, which is not limited by the embodiment of the application, and the history period can be one quarter or one month before the date of determining the passenger flow volume standard data.
When the ticket checking system is a first type of ticket checking system, the cloud monitoring device may determine, based on the historical data, a passenger flow standard data process corresponding to the line as follows: acquiring a plurality of historical passenger flows in a historical period and the number of ticket checking servers corresponding to each historical passenger flow; determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable; for each passenger flow volume interval, determining the number of historical ticket checking servers corresponding to each historical passenger flow volume belonging to the passenger flow volume interval; determining the mode in the number of the historical ticket checking servers as the number of standard ticket checking servers corresponding to the passenger flow volume interval; and determining a plurality of passenger flow volume intervals and the number of ticket checking servers corresponding to each passenger flow volume interval as passenger flow volume standard data.
As shown in table 1, table 1 is standard data of passenger flow volume corresponding to a certain line, wherein the standard data of passenger flow volume includes three passenger flow volume sections, the passenger flow volume variable is 200 persons, the passenger flow volume sections are respectively passenger flow volume sections with passenger flow volume less than or equal to 200 persons, the standard ticket checking processing capacity value corresponding to the passenger flow volume sections is 1, the passenger flow volume is more than 200 persons and less than or equal to 400 persons, the standard ticket checking processing capacity value corresponding to the passenger flow volume sections is 2, the passenger flow volume is more than or equal to 400 persons, and the standard ticket checking processing capacity value corresponding to the passenger flow volume sections is 3. Assuming that the real-time passenger flow volume is 236, the gate and the ticket checking server can be ensured to be in a normal running state as long as the ticket checking processing capacity value of the ticket checking server currently in the ticket checking request authentication state is ensured to be 2.
TABLE 1
Ticket checking processing capability value Passenger flow volume section (person)
1 Passenger flow is less than or equal to 200 people
2 200 people<Passenger flow is less than or equal to 400 people
3 400 people<Passenger flow volume is less than or equal to 600 people
In this step, the passenger flow volume interval corresponding to the real-time passenger flow volume may be determined by searching the predetermined passenger flow volume standard data.
And 203, determining to turn on or turn off at least one standby ticket checking server based on the passenger flow volume interval and the passenger flow volume standard data.
In the embodiment of the application, when each line is determined that the current time is the line starting time, the corresponding relation between the line stored in the database server and the ticket checking server can be read, an opening instruction is sent to a main ticket checking server corresponding to the line, when the ticket checking system is a first type ticket checking system, the ticket checking processing capacity value of the main ticket checking server can be determined, and the ticket checking processing capacity value of the main ticket checking server is determined as the current ticket checking processing capacity value corresponding to the line; when the ticket checking system is the second type of ticket checking system, the number of current ticket checking servers corresponding to the line can be determined to be 1.
The corresponding relation between the line and the ticket checking server is used for representing the ticket checking server which can provide ticket checking request authentication service for the gate on the line, the ticket checking server comprises a main ticket checking server and at least one standby ticket checking server, the main ticket checking server always provides ticket checking request authentication service for the gate corresponding to the line when the line starts to operate, and when the main ticket checking server fails, or the passenger flow volume on the line changes, the cloud monitoring equipment can control the standby ticket checking server to be opened or closed by sending an opening command or a closing command, so that the gate corresponding to the line is ensured to normally operate.
In this step, as shown in fig. 3, the process of determining to turn on or off at least one standby ticket server based on the traffic interval and traffic standard data may include:
step 2031, determining the number of standby ticket checking servers corresponding to the real-time passenger flow based on the passenger flow volume interval and the passenger flow volume standard data.
It can be appreciated that, in the embodiment of the present application, the process of determining the number of standby ticket checking servers corresponding to the real-time passenger flow may also have the following two alternative implementations according to the type of ticket checking system:
in an alternative implementation, when the ticket checking system is a first type of ticket checking system, the determining the number of standby ticket checking servers corresponding to the real-time passenger flow may include: based on the passenger flow standard data, searching a standard ticket checking processing capacity value corresponding to the passenger flow interval; determining a current ticket checking processing capacity value; determining a difference value between the current ticket checking processing capacity value and the standard ticket checking processing capacity value; and determining the number of the standby ticket checking servers corresponding to the difference as the number of the standby ticket checking servers corresponding to the real-time passenger flow.
Wherein, the process of determining the number of standby ticket servers corresponding to the difference value may be; and determining the ticket checking processing capacity value of each standby ticket checking server, selecting at least one standby ticket checking server, enabling the sum value of the ticket checking processing capacity values of the at least one standby ticket checking server to be equal to the difference value, and determining the at least one standby ticket checking server as the number of standby ticket checking servers corresponding to the difference value.
In another alternative implementation, when the ticket checking system is a second type of ticket checking system, the determining the number of standby ticket checking servers corresponding to the real-time passenger flow may include: searching the number of standard ticket checking servers corresponding to the passenger flow volume interval based on the passenger flow volume standard data; determining the number of current ticket checking servers; determining a difference between the number of standard ticket checking servers and the number of current ticket checking servers; and determining the difference value as the number of standby ticket checking servers corresponding to the real-time passenger flow.
Step 2032, turning on or off the standby ticket server corresponding to the standby ticket server number based on the standby ticket server number.
In this step, the process of starting or closing the standby ticket checking servers corresponding to the number of standby ticket checking servers based on the number of standby ticket checking servers may also have the following two alternative implementation manners according to the type of the ticket checking system:
in an alternative real-time manner, when the ticketing system is of a first type, the process includes: when the current ticket checking capacity value is larger than the standard ticket checking capacity value, sending a server closing instruction to standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control closing of the standby ticket checking servers; and when the current ticket checking processing capacity value is smaller than the standard ticket checking processing capacity value, sending a server starting instruction to the standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control the standby ticket checking servers to be started.
In another alternative real-time manner, when the ticket checking system is a second type of ticket checking system, the process of turning on or off the at least one standby ticket checking server includes: when the number of the current ticket checking servers is greater than that of the standard ticket checking servers, a server closing instruction is sent to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the standby ticket checking servers to be closed; and when the number of the current ticket checking servers is smaller than the number of the standard ticket checking servers, sending a server starting instruction to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the starting of the standby ticket checking servers.
It will be appreciated that in the embodiment of the present application, after the standby ticket server is turned on or off, the current ticket processing capability value or the number of front servers corresponding to the line needs to be determined and stored again.
For example, assuming that the standard data of the passenger flow volume of a certain line S1 is shown in table 1, and the ticket checking system is a first type ticket checking system, as shown in fig. 4, when the cloud monitoring device determines that the current time is the line starting time, an opening instruction is sent to a main ticket checking server corresponding to the line S1, the main ticket checking server is controlled to perform ticket checking request authentication, the ticket checking processing capability value of the main ticket checking server is determined to be 1, and the ticket checking processing capability value 1 of the main ticket checking server is determined to be the current ticket checking processing capability value corresponding to the line S1.
The main ticket checking server processes ticket checking request authentication sent by the gate on the line S1, and after each successful processing of ticket checking request authentication, the processing result can be sent to the database server, and the database server increases the passenger flow volume of the line S1 by 1 and stores the passenger flow volume.
Further, the cloud monitoring device acquires and counts real-time passenger flow of the line S1 within nearly 1 minute from the database server every 50ms, if the real-time passenger flow counted at a certain moment is 356 persons, the passenger flow standard data are read, a passenger flow interval corresponding to the 356 persons is found to be 200 persons < passenger flow less than or equal to 400 persons based on the passenger flow standard data, a standard ticket processing capacity value corresponding to the passenger flow interval is found to be 2 based on the passenger flow standard data, a difference value between the standard ticket processing capacity value 2 and the current ticket processing capacity value 1 is determined to be 1, the standard ticket processing capacity value 2 is larger than the current ticket processing capacity value 1, a standby ticket server needing to be started is determined to be increased, a ticket processing capacity value of at least one standby ticket server corresponding to the line S1 can be determined to be 0.5 or 1 based on the passenger flow standard data, a required ticket processing capacity value of the standby ticket server is determined to be started, and the required ticket processing capacity of the standby ticket server is determined to be 1; an open command may be sent to one standby ticket server with a ticket checking capability of 1, or an open command may be sent to two standby ticket checking servers with a ticket checking capability of 0.5, to control the open of the standby ticket checking servers, and to determine the current ticket checking capability value as 2.
In summary, the monitoring method of the ticket checking device provided by the embodiment of the application can obtain the real-time passenger flow of at least one line; searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data; based on the passenger flow volume interval and the passenger flow volume standard data, at least one standby ticket checking server is determined to be started or stopped, and the ticket checking server can be flexibly allocated according to the real-time passenger flow volume, so that the waste of data processing resources is prevented.
The embodiment of the application provides a ticket checking device monitoring method, which is applied to cloud monitoring equipment shown in fig. 1, and as shown in fig. 5, the method comprises the following steps:
step 401, obtaining real-time passenger flow volume of at least one line.
In this step, the process of obtaining the real-time passenger flow volume of at least one line may refer to step 201 in the above embodiment, which is not described herein.
Step 402, searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data.
In this step, the process of searching the passenger flow volume interval corresponding to the real-time passenger flow volume based on the predetermined passenger flow volume standard data may refer to step 202 in the above embodiment, which is not described in detail in the present embodiment.
And step 403, determining to turn on or turn off at least one standby ticket checking server based on the passenger flow volume interval and the passenger flow volume standard data.
In this step, the process of determining to turn on or off at least one standby ticket server based on the traffic interval and the traffic standard data may refer to step 203 in the above embodiment, which is not described in detail in the present embodiment.
Step 404, transmitting device information of at least one standby ticket server to the administrator terminal.
In this step, after determining to turn on the standby ticket server or turn off at least one standby ticket server, the device information of the at least one standby ticket server may be sent to the administrator terminal, so that the administrator may even learn about the operation condition of the ticket server, where the device information of the standby ticket server may include information such as a physical address, a network address, and a device status of the standby ticket server.
Optionally, in the embodiment of the present application, as shown in fig. 6, for a ticket checking server corresponding to each line, the cloud monitoring device may further send a heartbeat packet to each ticket checking server in an operation state according to a preset period; if a heartbeat packet response message returned by the ticket checking server is received within a preset time period, sending the heartbeat state information of the ticket checking server to a database server for storage; if the number of times exceeds the preset number of times, not receiving a heartbeat packet response message returned by any ticket checking server in an operation state within the preset time; determining a fault of the ticket checking server, and sending a server opening instruction to the standby ticket checking server so as to control the standby ticket checking server to be opened; and transmits the device information of the failed ticket checking server to the administrator terminal. The ticket checking server may include a main ticket checking server, or the ticket checking server may include a main ticket checking server and a standby ticket checking server. The management personnel can conveniently grasp the equipment information of the failed ticket checking server in time, and the troubleshooting efficiency of the failed ticket checking server is improved.
In summary, the monitoring method of the ticket checking device provided by the embodiment of the application can obtain the real-time passenger flow of at least one line; searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data; based on the passenger flow volume interval and the passenger flow volume standard data, at least one standby ticket checking server is determined to be started or stopped, equipment information of the at least one standby ticket checking server is sent to an administrator terminal, the ticket checking server can be flexibly allocated according to the real-time passenger flow volume, waste of data processing resources is prevented, an administrator is helped to know the running state of the ticket checking server in time, and the maintenance of a fault server is facilitated.
An embodiment of the present application provides an automatic monitoring device for a ticket checking system, as shown in fig. 7, the device 50 includes:
an acquisition module 501 configured to acquire real-time traffic of at least one line;
a first determining module 502 configured to search a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data;
a second determining module 503 is configured to determine to turn on or off at least one standby ticket server based on the passenger flow volume interval and the passenger flow volume standard data.
Optionally, the second determining module 503 is configured to:
determining the number of standby ticket checking servers corresponding to the real-time passenger flow based on the passenger flow interval and the passenger flow standard data;
and opening or closing the standby ticket checking servers corresponding to the standby ticket checking servers based on the standby ticket checking servers.
Optionally, the second determining module 503 is configured to:
searching the number of standard ticket checking servers corresponding to the passenger flow volume interval based on the passenger flow volume standard data;
determining the number of current ticket checking servers;
determining a difference between the number of standard ticket checking servers and the number of current ticket checking servers;
and determining the difference value as the number of standby ticket checking servers corresponding to the real-time passenger flow.
Optionally, the second determining module 503 is configured to:
based on the passenger flow standard data, searching a standard ticket checking processing capacity value corresponding to the passenger flow interval;
determining a current ticket checking processing capacity value;
determining a difference value between the current ticket checking processing capacity value and the standard ticket checking processing capacity value;
and determining the number of the standby ticket checking servers corresponding to the difference as the number of the standby ticket checking servers corresponding to the real-time passenger flow.
Optionally, the second determining module 503 is configured to:
when the number of the current ticket checking servers is greater than that of the standard ticket checking servers, a server closing instruction is sent to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the standby ticket checking servers to be closed;
and when the number of the current ticket checking servers is smaller than the number of the standard ticket checking servers, sending a server starting instruction to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the starting of the standby ticket checking servers.
Optionally, the second determining module 503 is configured to:
when the current ticket checking capacity value is larger than the standard ticket checking capacity value, sending a server closing instruction to standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control closing of the standby ticket checking servers;
and when the current ticket checking processing capacity value is smaller than the standard ticket checking processing capacity value, sending a server starting instruction to the standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control the standby ticket checking servers to be started.
Optionally, the second determining module 503 is further configured to:
acquiring a plurality of historical passenger flows in a historical period and historical ticket checking processing capacity values corresponding to each historical passenger flow;
determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable;
for each passenger flow volume interval, determining a historical ticket checking processing capacity value corresponding to each historical passenger flow volume belonging to the passenger flow volume interval;
determining a mode of the plurality of historical ticket checking processing capability values as a standard ticket checking processing capability value corresponding to the passenger flow volume interval;
and determining a plurality of passenger flow volume intervals and standard ticket checking processing capacity values corresponding to each passenger flow volume interval as passenger flow volume standard data.
Optionally, the second determining module 503 is further configured to:
acquiring a plurality of historical passenger flows in a historical period and the number of historical ticket checking servers corresponding to each historical passenger flow;
determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable;
for each passenger flow volume interval, determining the number of historical ticket checking servers corresponding to each historical passenger flow volume belonging to the passenger flow volume interval;
determining the mode in the number of the historical ticket checking servers as the number of standard ticket checking servers corresponding to the passenger flow volume interval;
and determining a plurality of passenger flow volume intervals and the number of ticket checking servers corresponding to each passenger flow volume interval as passenger flow volume standard data.
Optionally, as shown in fig. 8, the apparatus 50 further includes a sending module 504 configured to:
and transmitting the equipment information of the at least one standby ticket checking server to the manager terminal.
Optionally, as shown in fig. 8, the apparatus 50 further includes a detection module 505 configured to:
sending a heartbeat packet to each ticket checking server in an operation state according to a preset period;
if the number of times exceeds the preset number, the heartbeat packet response message returned by any ticket checking server in the running state is not received;
determining a fault of the ticket checking server, and sending a server opening instruction to the standby ticket checking server so as to control the standby ticket checking server to be opened;
and sending the equipment information of the failed ticket checking server to the manager terminal.
In summary, the automatic monitoring device for a ticket checking system provided by the embodiment of the application can obtain the real-time passenger flow of at least one line; searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data; and determining to turn on or off at least one standby ticket checking server based on the passenger flow volume interval and the passenger flow volume standard data. The ticket checking server can be flexibly allocated according to the real-time passenger flow, so that the waste of data processing resources is prevented.
Fig. 9 is a computer device shown according to an exemplary embodiment, the computer system including a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for system operation are also stored. The CPU601, ROM602, and RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output section including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drives are also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, the processes described above in fig. 2-6 may be implemented as computer software programs according to embodiments of the present application. For example, various embodiments of the application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via a communication portion, and/or installed from a removable medium. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 601.
The computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of methods, apparatus and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases. The described units or modules may also be provided in a processor, for example, as: a processor includes an acquisition module, a first determination module, and a second determination module. The names of these units or modules do not in any way limit the unit or module itself, for example, the acquisition module may also be described as "acquisition module for acquiring real-time passenger traffic of at least one line".
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by one of the electronic devices, cause the electronic device to implement the ticket checking system automatic monitoring method as described in the above embodiments.
The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application referred to in the present application is not limited to the specific combinations of the technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the inventive concept. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.

Claims (11)

1. An automatic monitoring method for a ticket checking system, comprising:
acquiring real-time passenger flow of at least one line;
searching a passenger flow volume interval corresponding to the real-time passenger flow volume based on predetermined passenger flow volume standard data;
determining to turn on or off at least one standby ticket server based on the passenger flow volume interval and the passenger flow volume standard data;
the searching the passenger flow volume interval corresponding to the real-time passenger flow volume based on the predetermined passenger flow volume standard data comprises the following steps:
determining the number of standby ticket checking servers corresponding to the real-time passenger flow based on the passenger flow volume interval and the passenger flow volume standard data;
based on the number of the standby ticket checking servers, turning on or turning off the standby ticket checking servers corresponding to the number of the standby ticket checking servers;
the types of ticket checking servers are divided into two types, wherein at least two ticket checking servers with different data processing capacities exist in a first type ticket checking system, and the data processing capacities of each ticket checking server in a second type ticket checking system are the same;
when the ticket checking system is a first type ticket checking system, the passenger flow standard data is the corresponding relation between the passenger flow interval and the standard ticket checking processing capacity value; when the ticket checking system is a second type ticket checking system, the passenger flow standard data is the corresponding relation between the passenger flow interval and the number of standard ticket checking servers, wherein the mode in the historical ticket checking processing capacity values is determined as the standard ticket checking processing capacity value corresponding to the passenger flow interval.
2. The method of claim 1, wherein the determining the number of standby ticketing servers corresponding to the real-time traffic based on the traffic interval and the traffic criteria data comprises:
searching the number of standard ticket checking servers corresponding to the passenger flow volume interval based on the passenger flow volume standard data;
determining the number of current ticket checking servers;
determining a difference between the number of standard ticketing servers and the number of current ticketing servers;
and determining the difference value as the number of standby ticket checking servers corresponding to the real-time passenger flow volume.
3. The method of claim 1, wherein the determining the number of standby ticketing servers corresponding to the real-time traffic based on the traffic interval and the traffic criteria data comprises:
searching a standard ticket checking processing capacity value corresponding to the passenger flow volume interval based on the passenger flow volume standard data;
determining a current ticket checking processing capacity value;
determining a difference between the current ticket checking capability value and the standard ticket checking capability value;
and determining the number of the standby ticket checking servers corresponding to the difference as the number of the standby ticket checking servers corresponding to the real-time passenger flow.
4. The method of claim 2, wherein the turning on or off the standby ticket server corresponding to the number of standby ticket servers based on the number of standby ticket servers comprises:
when the number of the current ticket checking servers is larger than the number of the standard ticket checking servers, a server closing instruction is sent to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the standby ticket checking servers to be closed;
and when the number of the current ticket checking servers is smaller than the number of the standard ticket checking servers, sending a server starting instruction to the standby ticket checking servers corresponding to the number of the standby ticket checking servers so as to control the standby ticket checking servers to be started.
5. The method of claim 3, wherein said turning on or off the standby ticket server corresponding to the number of standby ticket servers based on the number of standby ticket servers comprises:
when the current ticket checking processing capacity value is larger than the standard ticket checking processing capacity value, a server closing instruction is sent to the standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control the standby ticket checking servers to be closed;
and when the current ticket checking processing capacity value is smaller than the standard ticket checking processing capacity value, a server starting instruction is sent to the standby ticket checking servers corresponding to the standby ticket checking servers in number so as to control the standby ticket checking servers to be started.
6. The method of claim 1, wherein determining traffic standard data comprises:
acquiring a plurality of historical passenger flows in a historical period and historical ticket checking processing capacity values corresponding to each historical passenger flow;
determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable;
for each passenger flow volume interval, determining a historical ticket checking processing capacity value corresponding to each historical passenger flow volume belonging to the passenger flow volume interval;
determining the mode in the historical ticket checking processing capacity values as a standard ticket checking processing capacity value corresponding to the passenger flow volume interval;
and determining a plurality of passenger flow volume intervals and standard ticket checking processing capacity values corresponding to each passenger flow volume interval as passenger flow volume standard data.
7. The method of claim 1, wherein determining traffic standard data comprises:
acquiring a plurality of historical passenger flows in a historical period and the number of historical ticket checking servers corresponding to each historical passenger flow;
determining a plurality of passenger flow volume intervals based on the minimum historical passenger flow volume, the maximum historical passenger flow volume, and the passenger flow volume variable;
for each passenger flow volume interval, determining the number of historical ticket checking servers corresponding to each historical passenger flow volume belonging to the passenger flow volume interval;
determining the mode in the number of the historical ticket checking servers as the number of standard ticket checking servers corresponding to the passenger flow volume interval;
and determining a plurality of passenger flow volume intervals and the number of ticket checking servers corresponding to each passenger flow volume interval as passenger flow volume standard data.
8. The method of claim 1, wherein after determining to turn on or off at least one standby ticketing server, the method further comprises:
and transmitting the equipment information of at least one standby ticket checking server to an administrator terminal.
9. The method according to any one of claims 1 to 8, further comprising:
sending a heartbeat packet to each ticket checking server in an operation state according to a preset period;
if the number of times exceeds the preset number, the heartbeat packet response message returned by any one of the ticket checking servers in the running state is not received;
determining the fault of the ticket checking server, and sending a server opening instruction to the standby ticket checking server so as to control the standby ticket checking server to be opened;
and sending the equipment information of the failed ticket checking server to the manager terminal.
10. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor for implementing the method according to any one of claims 1-9 when the program is executed.
11. A computer-readable storage medium, having stored thereon a computer program, the computer program
For implementing the method according to any one of claims 1-9.
CN202011310510.0A 2020-11-20 2020-11-20 Automatic monitoring method, device, equipment and medium for ticket checking system Active CN114596640B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011310510.0A CN114596640B (en) 2020-11-20 2020-11-20 Automatic monitoring method, device, equipment and medium for ticket checking system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011310510.0A CN114596640B (en) 2020-11-20 2020-11-20 Automatic monitoring method, device, equipment and medium for ticket checking system

Publications (2)

Publication Number Publication Date
CN114596640A CN114596640A (en) 2022-06-07
CN114596640B true CN114596640B (en) 2023-10-17

Family

ID=81802686

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011310510.0A Active CN114596640B (en) 2020-11-20 2020-11-20 Automatic monitoring method, device, equipment and medium for ticket checking system

Country Status (1)

Country Link
CN (1) CN114596640B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115249120B (en) * 2022-06-16 2024-03-22 北京轨道交通路网管理有限公司 Method and device for determining equipment startup plan and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120105A (en) * 2019-03-29 2019-08-13 成都信息工程大学 Method, system, server and the terminal of person-carrying vehicle automatic fare collection
WO2019184724A1 (en) * 2018-03-30 2019-10-03 卡斯柯信号有限公司 Real-time passenger flow-based intelligent operation adjustment system and method for trains
JP2020154679A (en) * 2019-03-20 2020-09-24 株式会社東芝 Ticket examination system

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170171082A1 (en) * 2015-12-15 2017-06-15 Le Holdings (Beijing) Co., Ltd. Method and electronic device for updating client data
CN106790546A (en) * 2016-12-23 2017-05-31 广州地铁设计研究院有限公司 A kind of AFC system based on cloud computing
JP2019012494A (en) * 2017-07-03 2019-01-24 株式会社日立製作所 Human flow estimating device, human flow estimating system and human flow estimating method
CN207337472U (en) * 2017-11-09 2018-05-08 浙江国际海运职业技术学院 A kind of scenic spot ticket check gate system
CN110457138A (en) * 2019-08-20 2019-11-15 网易(杭州)网络有限公司 Management method, device and the electronic equipment of game server cluster
CN111611133B (en) * 2020-05-21 2022-04-29 莫毓昌 Data center energy consumption management method based on intelligent monitoring

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019184724A1 (en) * 2018-03-30 2019-10-03 卡斯柯信号有限公司 Real-time passenger flow-based intelligent operation adjustment system and method for trains
JP2020154679A (en) * 2019-03-20 2020-09-24 株式会社東芝 Ticket examination system
CN110120105A (en) * 2019-03-29 2019-08-13 成都信息工程大学 Method, system, server and the terminal of person-carrying vehicle automatic fare collection

Also Published As

Publication number Publication date
CN114596640A (en) 2022-06-07

Similar Documents

Publication Publication Date Title
CN111127778B (en) Bank self-service terminal recommendation method and device
CN104394366B (en) The method and system of distributed video streaming media transcoding access control
CN113704063B (en) Performance monitoring method, device, equipment and storage medium of cloud mobile phone
CN110347694B (en) Equipment monitoring method, device and system based on Internet of things
CN114596640B (en) Automatic monitoring method, device, equipment and medium for ticket checking system
CN111984495A (en) Big data monitoring method and device and storage medium
CN107985350A (en) A kind of inter-linked controlling method and correlating center at Metro Network center
CN113627792A (en) Unmanned vehicle scheduling management method, device, equipment, storage medium and program
CN111930454B (en) Interface display method and device, terminal equipment and medium
CN114328132A (en) Method, device, equipment and medium for monitoring state of external data source
WO2022088803A1 (en) System information analysis method and apparatus based on cloud environment, electronic device, and medium
CN113159464A (en) Data processing method and device and server
CN106781677B (en) Statistical method and system for idle parking spaces of parking lot
CN116701787A (en) Cloud-based destination recommendation method, device and storage medium
CN115801764A (en) File transmission method, device, equipment and storage medium
CN112783637B (en) Resource regulation and control method and device
CN115473910A (en) Data management method and device, electronic equipment and storage medium
CN108345650A (en) Electronic invoice business monitors method for early warning and system in real time
CN113269339A (en) Method and system for automatically creating and distributing network appointment tasks
CN112381386A (en) Vehicle inspection and control method and device, electronic equipment and storage medium
CN113409957B (en) Visiting system and method thereof
CN115292081B (en) Information sending method, device, electronic equipment and medium
CN115497191B (en) Derailment original data polling reporting method and device for running part monitoring system
CN112906655B (en) User state judging method and device
CN118200319A (en) Method for monitoring operation state of service system in private cloud environment and related equipment

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
GR01 Patent grant
GR01 Patent grant