Rail transit ticket business processing system and method

Abstract

The invention discloses a rail transit ticket business processing system and method, the system comprises a ticket business subsystem, a clearing subsystem and a station device, the ticket business subsystem comprises a ticket price calculation module, the ticket price calculation module synchronizes ticket price parameters from the clearing subsystem, and the station device sends a ticket price calculation request to the ticket business subsystem when detecting a ticket counting event, the ticket price calculation module calculates the ticket price according to the ticket price parameter when receiving the ticket price calculation request and returns the ticket price to the station equipment, and the station equipment executes the fee deduction processing service according to the ticket price, so that the ticket price is calculated at the cloud end, centralized management and unified ticket price calculation rules are provided at the cloud end, and the provided ticket price data is accurate and consistent; in addition, the cloud calculation of the ticket price can enhance the flexibility of business development and has the advantage of expandability, the ticket price preferential policy can be adjusted conveniently, higher efficiency and better user experience are brought to rail transit operation, station equipment does not need to be maintained one by one during ticket price rule maintenance, and the maintenance cost is reduced.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of rail transit technology, and in particular to a rail transit ticket processing system and method. Background Art

[0002] Rail transit is an important part of urban public transportation. During the operation of rail transit, fare calculation directly affects the travel cost and experience of passengers.

[0003] At present, the fare calculation in the rail transit systems of many cities mainly relies on the station equipment reader / writer, that is, the station equipment reader / writer calculates the passenger's fare by reading the ticket information held by the passenger, and deducts the fare through the station equipment reader / writer when the passenger leaves the station. Although the fare calculation by the station equipment reader / writer can meet the daily operation needs of rail transit, there are still the following problems in actual application:

[0004] (1) Since fare calculation is scattered among various station devices, when the fare calculation rules need to be adjusted or the system needs to be upgraded, all relevant station devices must be updated one by one, which increases the maintenance workload and high maintenance costs;

[0005] (2) Each station device calculates fares independently. Inconsistent fare calculation rules of station devices can easily lead to inconsistent deductions for passengers at different stations, making it difficult to ensure data consistency.

[0006] (3) With the continuous expansion of the rail transit network and the introduction of new services, the original computing models in station equipment cannot flexibly adapt to new changes in demand and have poor scalability. Summary of the invention

[0007] The embodiment of the present invention provides a rail transit ticket processing system and method to solve the problems of high maintenance cost, inconsistent deduction and poor scalability in calculating ticket prices using station equipment.

[0008] In a first aspect, an embodiment of the present invention provides a rail transit ticket processing system, including a ticketing subsystem, a clearing subsystem, and a station device, wherein the station device and the clearing subsystem both communicate with the ticketing subsystem, and the ticketing subsystem includes a fare calculation module;

[0009] The fare calculation module is used to synchronize fare parameters from the clearing subsystem;

[0010] The station equipment is used to send a fare calculation request to the ticketing subsystem when a ticket counting event is detected;

[0011] The fare calculation module is also used to calculate the fare according to the fare parameters when receiving the fare calculation request, and return the fare to the station device;

[0012] The station equipment is used to execute fee deduction processing business according to the ticket price.

[0013] Optionally, the fare calculation module includes a parameter synchronization unit, and the clearing subsystem includes an operation management module;

[0014] The parameter synchronization unit is used to send a parameter synchronization request to the operation management module when a synchronization event is detected;

[0015] The operation management module is used to return the fare parameter to the parameter synchronization unit upon receiving the parameter synchronization request;

[0016] The parameter synchronization unit is used to store the fare parameter.

[0017] Optionally, the fare calculation module further includes a device connection unit and a device heartbeat processing unit;

[0018] The device connection unit is used to determine whether the station device is a device in the whitelist upon receiving a connection request from the station device, and if so, establish a connection with the station device; if not, disconnect the connection with the station device;

[0019] The device heartbeat processing unit is used to determine that the station device is offline and release the communication interface connected to the station device if no message from the station device is received within a preset time after the device connection unit establishes a connection with the station device and the communication interface connected to the station device is released.

[0020] Optionally, the station equipment includes a cloud fare calculation interface module, a local fare calculation module and a reader / writer;

[0021] The cloud fare calculation interface module is used to send a fare calculation request to the fare calculation module when the reader detects a ticket counting event, receive the fare returned by the fare calculation module, and return the fare to the reader;

[0022] The local fare calculation module is used to calculate the fare when the cloud fare calculation interface module fails, and return the fare to the reader / writer.

[0023] Optionally, the fare calculation module includes a minimum fare calculation unit;

[0024] The station equipment is also used to generate a minimum fare verification request and send it to the fare calculation module when detecting that a passenger enters the station, wherein the minimum fare verification request includes the passenger's ticket information and station information;

[0025] The minimum fare calculation unit is used to query the minimum fare of the station where the passenger enters the station according to the ticket information and the station information, and return the minimum fare to the station equipment;

[0026] The station equipment is also used to confirm whether the passenger is allowed to enter the station based on the minimum fare.

[0027] Optionally, the fare calculation module includes a trip fare calculation unit;

[0028] The station equipment is also used to generate a trip fare calculation request and send it to the trip fare calculation unit when detecting that a passenger is leaving the station, wherein the trip fare calculation request includes the ticket information of the passenger;

[0029] The travel fare calculation unit is used to calculate the travel fare of the passenger according to the ticket information of the passenger and the fare parameter, and return the travel fare to the station equipment.

[0030] Optionally, the station equipment is also used to determine whether the balance of the passenger's ticket is greater than or equal to the trip fare. If so, the trip fare is deducted from the ticket and the exit gate is controlled to open; if not, the exit gate is controlled to close and a prompt message of insufficient balance is generated.

[0031] Optionally, the ticketing subsystem further includes a transaction management module;

[0032] The station equipment is also used to generate ticket transaction data and upload it to the transaction management module after executing the fee deduction business processing.

[0033] Optionally, the fare calculation module further includes a service monitoring unit;

[0034] The service monitoring unit is used to record the time when the fare calculation request is received as the service start time, and record the time when the fare calculation is completed as the service end time, and calculate the service time according to the service start time and the service end time.

[0035] In a second aspect, an embodiment of the present invention provides a rail transit ticket processing method, which is applied to the rail transit ticket processing system described in any one of the first aspects, including:

[0036] Synchronize fare parameters from the clearing subsystem;

[0037] receiving a fare calculation request, wherein the fare calculation request is a request generated when a station device detects a ticket counting event;

[0038] Calculate the fare according to the fare parameters;

[0039] The fare is returned to the station equipment, and the station equipment is used to perform fee deduction processing according to the fare.

[0040] In the embodiment of the present invention, a fare calculation module is set in the ticketing subsystem, and fare parameters can be synchronized from the clearing subsystem. When the station equipment needs to calculate the fare, a fare calculation request is sent to the fare calculation module, thereby triggering the fare calculation module of the ticketing subsystem to calculate the fare, and returning the fare to the station equipment to execute the deduction business processing. There is no need to calculate the fare in the station equipment, and the calculation of passenger fares in the cloud is realized. The cloud has centralized management and unified fare calculation rules, and the fare data provided is accurate and consistent. Calculating fares in the cloud can also enhance business development flexibility and scalability, facilitate adjustment of fare preferential policies, and bring higher efficiency and better user experience to rail transit operations. When maintaining fare rules, there is no need to maintain station equipment one by one, which simplifies the equipment maintenance process and reduces maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of a rail transit ticket processing system provided by an embodiment of the present invention;

[0042] Figure 2 A schematic diagram of a rail transit ticket processing system provided by another embodiment of the present invention;

[0043] Figure 3 This is a schematic diagram of the framework of the fare calculation module;

[0044] Figure 4 A flowchart of an example of fare parameter synchronization;

[0045] Figure 5 A flowchart of an example of station equipment connection and heartbeat processing;

[0046] Figure 6 A flow chart of an example of fare processing for a station device;

[0047] Figure 7 A flowchart for an example of minimum fare processing;

[0048] Figure 8 A flowchart for an example of itinerary fare processing;

[0049] Fig. 9 A schematic diagram of a rail transit ticket processing system provided by another embodiment of the present invention;

[0050] Fig.10 It is a flow chart of a rail transit ticket processing method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0051] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0052] Figure 1 A schematic diagram of a rail transit ticket processing system provided by an embodiment of the present invention is shown in FIG. Figure 1 As shown, the rail transit ticket processing system of the embodiment of the present invention includes a ticketing subsystem 1, a clearing subsystem 2 and a station device 3. The station device 3 and the clearing subsystem 2 both communicate with the ticketing subsystem 1, and the ticketing subsystem 1 includes a fare calculation module.

[0053] Rail transit may refer to a type of transportation vehicle or transportation system in which operating vehicles need to travel on specific tracks, such as a city subway. The rail transit ticket processing system of this embodiment may be an automated system based on computer, communication, network, automatic control and other technologies to realize the entire process of rail transit ticket sales, ticket checking, billing, charging, clearing, and management.

[0054] Among them, the ticketing subsystem 1 can be an operation system that uses Internet technology to realize the virtualization and digitization of tickets and cards, and realizes functions such as ticket sales, ticket inspection, and billing based on the platform, while providing various management functions for the operation process. The clearing subsystem 2 can be a rail transit automatic ticket sales and inspection clearing center system, which is used to issue and manage urban rail transit tickets, settle and clear tickets and money for different lines in the line network, and has a clearing function with other payment cards for passenger consumption in the urban rail transit line network. The station equipment 3 can be a station entry and exit gate, passenger affairs processing equipment, etc. In this embodiment, the fare can refer to the fare for passengers to take rail transit.

[0055] In the ticketing subsystem 1, the fare calculation module is used to synchronize the fare parameters from the clearing subsystem 2. The station equipment 3 is used to send a fare calculation request to the ticketing subsystem 1 when a ticket counting event is detected. The fare calculation module is also used to calculate the fare according to the fare parameters and return the fare to the station equipment 3 when receiving the fare calculation request. The station equipment 3 is used to execute the deduction processing service according to the fare.

[0056] Specifically, the fare parameters may be data including fare calculation rules and information required for fare calculation. By way of example, the fare parameters may include data such as entry lines, entry stations, exit lines, exit stations, fare amounts, boarding limit time, overtime penalty amounts, etc. The ticket counting events may be passenger entry or exit events, such as a passenger swiping a physical ticket card on a reader / writer of a station device to enter or exit the station. The fare calculation request may include data such as the passenger's entry line, entry station, entry time, passenger's ticket type, exit line, exit time, and exit station. The fare calculation module may calculate the passenger's rail transit fare based on the data in the fare calculation request and the fare parameters, and return the fare to the station device so that the deduction processing service can be executed on the reader / writer of the station device.

[0057] Since the fare calculation module is set in the ticketing subsystem, the fare parameters can be synchronized from the clearing subsystem. When the station equipment needs to calculate the fare, it sends a fare calculation request to the fare calculation module, thereby triggering the fare calculation module in the ticketing subsystem to calculate the fare and return it to the station equipment to execute the deduction business processing. There is no need to calculate the fare on the station equipment, and the passenger fare is calculated in the cloud. It has centralized management and unified fare calculation rules in the cloud, and the fare data provided is accurate and consistent. Calculating fares in the cloud can also enhance business development flexibility and scalability, facilitate adjustment of fare preferential policies, and bring higher efficiency and better user experience to rail transit operations. When maintaining fare rules, there is no need to maintain station equipment one by one, which simplifies the equipment maintenance process and reduces maintenance costs.

[0058] In an alternative embodiment, if Figure 2 As shown, the clearing system 2 includes an operation management module, such as Figure 3 As shown, the fare calculation module includes a parameter synchronization unit. In the clearing subsystem 2, the operation management module is used to configure the fare parameters. The parameter synchronization unit is used to send a parameter synchronization request to the operation management module when a synchronization event is detected. The operation management module is used to return the fare parameters to the parameter synchronization unit when receiving the parameter synchronization request. The parameter synchronization unit is used to store the fare parameters.

[0059] The synchronization event may be a pre-configured time, such as 00:00 every morning. Of course, the synchronization event may also be the receipt of a manual synchronization operation instruction, etc. This embodiment does not limit the synchronization event. Figure 4 The synchronization process of fare parameters is explained by taking the synchronization event as a pre-configured timing as an example. Figure 4 The flowchart shown is an example of fare parameter synchronization. Figure 4In the example shown, a scheduled schedule can be set for parameter synchronization. When the system time reaches the pre-configured scheduled time, parameter synchronization is triggered, and the parameter synchronization unit sends a request to read the fare parameters to the clearing subsystem. The clearing subsystem synchronizes the fare parameters from the operation management module, extracts the entry route, entry station, exit route, exit station, fare amount, boarding limit time, overtime penalty amount, etc. of the physical ticket as fare parameters and returns them to the parameter synchronization unit. After receiving the returned fare parameters, the parameter synchronization unit saves them in the memory of the ticketing subsystem and caches them to the Redis server, and generates a synchronization log, and further returns the synchronization result whether the synchronization is successful. By regularly synchronizing the fare parameters from the clearing subsystem, the latest fare parameters can be used to accurately calculate the fare, and the synchronized fare parameters can be cached to the Redis server, which can improve the performance of fare calculation and improve the efficiency of fare calculation.

[0060] In an alternative embodiment, if Figure 3 As shown, the fare calculation module also includes a device connection unit and a device heartbeat processing unit. The device connection unit is used to determine whether the station device is a device in the whitelist when receiving a connection request from the station device. If so, establish a connection with the station device; if not, disconnect the connection with the station device. The device heartbeat processing unit is used to determine that the station device is offline and release the communication interface connected to the station device if no message (including heartbeat message) from the station device is received within a preset time after the device connection unit establishes a connection with the station device.

[0061] Specifically, Figure 5 The flowchart shown is an example of station equipment connection and heartbeat processing. Figure 5 In the example shown, the fare calculation module can use the socket long connection communication protocol to connect to the station equipment to process the device whitelist verification and device periodic heartbeat detection. Exemplarily, when the station equipment initiates a device connection request including the device ID, the device connection unit of the fare calculation module in the ticketing subsystem determines whether the device is legal based on the device ID in the request, for example, whether the device ID is in the pre-configured whitelist. If so, the station equipment is allowed to connect and the connection is successful. If not, it is determined to be an illegal device and the connection is disconnected, so that only legal devices can successfully connect, ensuring the security of the entire system.

[0062] After the station equipment is successfully connected, when the station equipment sends a message to the fare calculation module of the ticketing subsystem, or starts timing after receiving a message from the fare calculation module, and there is no message sending or receiving within the next 30 seconds (this time is configurable), a heartbeat request is initiated to the fare calculation module in the 30th second, and the fare calculation module responds with a heartbeat to determine the survival of the socket channel and the renewal of the connection. If the fare calculation module does not receive a message (including a heartbeat or other interface request) from the station equipment within 35 seconds (starting from the time of the last message sending or receiving), it is determined that the socket connection is disconnected, the station equipment is offline, and the fare calculation module forcibly disconnects and releases the socket connection. If a message (including a heartbeat or other interface request) is received from the station equipment within 35 seconds (starting from the time of the last message sending or receiving), it is determined that the connection is normal.

[0063] On the one hand, this embodiment performs whitelist verification on station equipment through the device connection unit, which can avoid network security problems caused by illegal equipment access to the system and ensure the network security of the system. On the other hand, the heartbeat processing unit can confirm the connection status between the station equipment and the system, and release the communication interface in time when the station equipment is offline, avoiding the problem of system resource consumption caused by communication interface occupation, thereby improving the utilization rate of system resources.

[0064] like Figure 3 As shown, in another embodiment, the station equipment may include a cloud fare calculation interface module, a local fare calculation module and a reader / writer, wherein the reader / writer is used to read and write physical tickets to realize reading ticket card information and deduction processing, the cloud fare calculation interface module is used to call the fare calculation module of the ticketing subsystem to calculate the fare, and the local fare calculation module is used to calculate the fare locally in the station equipment. The cloud fare calculation interface module is used to send a fare calculation request to the fare calculation module when the reader / writer detects a ticket counting event, and receives the fare returned by the fare calculation module, and returns the fare to the reader / writer, and the local fare calculation module is used to calculate the fare when the cloud fare calculation interface module fails, and return the fare to the reader / writer.

[0065] Specifically, Figure 6 The flowchart shown is an example of fare processing performed by station equipment. Figure 6In the example shown, the station device generates a reader / writer business instruction when a passenger enters or exits the station. The reader / writer distributes and processes the business instruction and further determines whether it is necessary to calculate the fare (excluding free rides). If it is necessary to calculate the fare, the reader / writer processes the fare data and sends the fare data and the fare interface instruction to the station device through the reader / writer interface. When the station device receives the fare interface instruction, it calls the cloud fare calculation interface module of the ticketing subsystem to request the fare calculation module in the ticketing subsystem to calculate the fare based on the fare data. After calculating the fare, the ticketing subsystem returns the fare result to the station device. The station device transmits the fare result to the reader / writer. The reader / writer confirms whether it is normal based on the fare result, such as whether the fare is obtained. If the reader / writer confirms that the fare result is normal, it continues to execute the fare processing business. The service is to upload the transaction processing data after deduction processing. If the cloud fare calculation interface module fails and cannot obtain the fare due to network failure, the reader / writer calls the local fare calculation module to calculate the fare and then continues to execute the fare processing service, thereby realizing the addition of a cloud fare calculation interface module to the station equipment. When the fare needs to be calculated, the fare calculation module in the ticketing subsystem on the cloud is preferentially requested to calculate the fare. When the fare cannot be calculated from the cloud due to network failure, the local fare calculation module of the station equipment is called to calculate the fare. The dual guarantee of cloud and local fare calculation is realized, which improves the reliability of the system and avoids the inability to obtain the fare when the cloud cannot calculate the fare, resulting in passengers waiting for a long time or even being unable to exit the station. The fare can be calculated in a timely and reliable manner, which improves the passenger's riding experience.

[0066] like Figure 3 As shown, in another embodiment, the fare calculation module also includes a minimum fare calculation unit, and the station equipment is also used to generate a minimum fare verification request and send it to the fare calculation module when detecting that a passenger enters the station. The minimum fare verification request includes the passenger's ticket information and station information. The minimum fare calculation unit is used to query the minimum fare of the station where the passenger enters the station according to the ticket information and station information, and return the minimum fare to the station equipment. The station equipment is also used to confirm whether the passenger is allowed to enter the station according to the minimum fare. Among them, the ticket information may include the passenger's ticket type, ticket balance, ticket ID and other data, and the station information may include the station entry line, entry station and other data.

[0067] Specifically, Figure 7 A flowchart showing an example of minimum fare processing is shown in Figure 7In the example shown, a passenger enters the station by swiping a ticket card on a reader / writer of a station device (such as an entry gate) at an entry station. The reader / writer of the station device reads the ticket card information and waits for processing to determine whether to open the gate to allow the passenger to enter the station, such as reading the ticket card balance, ticket card type, entry route, entry station and other data, and generating a minimum fare verification request including the ticket card type, entry route, entry station and other data, and sending the request to the fare calculation module of the ticketing subsystem to request the fare calculation module to query the minimum fare of the station where the passenger enters the station. The minimum fare calculation unit in the fare calculation module obtains the minimum fare according to the ticket card type, entry route, entry station and other data, and returns the minimum fare to the station device. The station device determines whether the ticket card balance of the passenger's ticket card is greater than or equal to the minimum fare. If so, the gate is controlled to open and allow the passenger to enter the station. If not, the gate is controlled to remain closed to prohibit the passenger from entering the station, and a prompt message of insufficient balance is generated as a result and returned to the passenger, such as displaying insufficient balance on the display screen of the entry gate or alarming through a buzzer to prompt the passenger that the balance is insufficient.

[0068] This embodiment sets a minimum fare calculation unit in the ticketing subsystem in the cloud. When the minimum fare calculation unit processes the passenger's entry into the station, it triggers the station equipment to send a minimum fare verification request, so as to query the minimum fare in the ticketing subsystem in the cloud, and further determine whether to allow the passenger to enter the station based on the minimum fare, thereby realizing the calculation of the minimum fare for each station through unified rules in the cloud.

[0069] like Figure 3 As shown, in one embodiment, the fare calculation module also includes a trip fare calculation unit, which is used to calculate the fare of the passenger's ride on the track transportation. Specifically, the station equipment is also used to generate a trip fare calculation request and send it to the trip fare calculation unit when detecting that the passenger is leaving the station. The trip fare calculation request includes the passenger's ticket information. The trip fare calculation unit is used to calculate the passenger's trip fare based on the passenger's ticket information and fare parameters, and return the trip fare to the station equipment. The station equipment is also used to determine whether the balance of the passenger's ticket is greater than or equal to the trip fare. If so, the trip fare is deducted from the ticket and the exit gate is controlled to open. If not, the exit gate is controlled to close and a prompt message of insufficient balance is generated. Among them, the ticket information includes data such as ticket type, ticket number, entry line station, entry time, exit line station, exit time, joint ride threshold number, and joint ride accumulated amount.

[0070] Specifically, Figure 8 A flowchart showing an example of itinerary fare processing is shown in Figure 8In the example shown, after the passenger arrives at the destination station by rail transit, he swipes the card at the reader / writer of the exit gate and waits to exit the station. The reader / writer of the station equipment reads the card and waits for processing, reads the ticket type, ticket number, entry line station, entry time, exit line station, exit time, joint ride threshold number, joint ride accumulated amount and other data of the ticket, and generates a trip fare calculation request containing the above data and sends it to the fare calculation module to request the fare calculation module to calculate the trip fare. The trip fare calculation unit in the fare calculation module can calculate the trip fare based on the read ticket type, ticket number, entry line station, The trip fare is calculated based on data such as entry time, exit line station, exit time, number of combined ride thresholds, accumulated combined ride amount, and the latest synchronized fare parameters, and the trip fare is returned to the station equipment. The station equipment compares the ticket balance with the trip fare. If the ticket balance is less than the trip fare, the exit gate is refused to open, prohibiting the passenger from exiting the station, and generates a prompt message of insufficient balance and returns it to the passenger. If the ticket balance is greater than or equal to the trip fare, the reader / writer performs a card write operation on the ticket, deducts the trip fare from the ticket balance to deduct the fee, opens the exit gate to allow the passenger to exit, and generates the transaction data for upload.

[0071] This embodiment sets up a trip fare calculation unit in the ticketing subsystem in the cloud, and uses the trip fare calculation unit to process the trip fare calculation request sent by the station equipment when the passenger leaves the station, so as to calculate the passenger's trip fare, and further determines whether to release the passenger from the station based on the trip fare, thereby realizing the calculation of the passenger's travel fare based on unified rules in the cloud.

[0072] like Figure 3 As shown, the fare calculation module also includes a service monitoring unit, which is used to record the time when the fare calculation request is received as the service start time, and record the time when the fare calculation is completed as the service end time, and calculate the service time consumption based on the service start time and the service end time. The service time consumption can be used to analyze the performance and efficiency of the fare calculation.

[0073] like Fig. 9 As shown, in one embodiment, the ticketing subsystem also includes a transaction management module. After the station equipment writes the ticket card to perform the deduction business processing, it can generate ticketing transaction data and upload it to the transaction management module so that the transaction data can be managed in the transaction management module.

[0074] Fig.10 A flow chart of a rail transit ticket processing method provided in an embodiment of the present invention. The rail transit ticket processing method in an embodiment of the present invention is applicable to the case of processing rail transit tickets. The method can be executed by a rail transit ticket processing system, such as Fig.10 As shown, the rail transit ticket processing method of the embodiment of the present invention may specifically include the following steps:

[0075] S101. Synchronize fare parameters from the clearing subsystem.

[0076] like Figure 1 As shown, the rail transit ticket processing system includes a ticketing subsystem 1, a billing subsystem 2 and a station device 3. The station device 3 and the billing subsystem 2 both communicate with the ticketing subsystem 1. The ticketing subsystem 1 includes a fare calculation module.

[0077] Synchronization events can be pre-configured in the ticketing subsystem 1, such as configuring a timing time. When the system time reaches the configured timing time, the fare calculation module sends a parameter synchronization request to the clearing subsystem 2 to synchronize the fare parameters from the clearing subsystem. After receiving the parameter synchronization request, the clearing subsystem returns the entry line, entry station, exit line, exit station, fare amount, boarding limit time, overtime penalty amount, etc. as fare parameters to the ticketing subsystem.

[0078] S102: Receive a fare calculation request, where the fare calculation request is a request generated when a station device detects a ticket counting event.

[0079] In one embodiment, the fare calculation request may be a minimum fare verification request, for example, a station device may generate a minimum fare verification request when detecting a passenger entering the station, and the minimum fare verification request includes the passenger's ticket information and station information.

[0080] In another embodiment, the fare calculation request may be a trip fare calculation request, for example, the station equipment is also used to generate a trip fare calculation request when detecting that a passenger is exiting the station. The trip fare calculation request may include the passenger's ticket information, such as ticket type, ticket number, entry line station, entry time, exit line station, exit time, joint ride threshold number, joint ride accumulated amount and other data.

[0081] S103. Calculate the fare according to the fare parameters.

[0082] In one embodiment, when calculating the minimum fare, the minimum fare for the passenger's entry station can be queried based on the station line, station information, and ticket type of the passenger's entry station.

[0083] In another embodiment, when calculating the trip fare, the trip fare can be calculated based on the ticket type, ticket number, entry line station, entry time, exit line station, exit time, joint ride threshold number, joint ride accumulated amount and other data of the read ticket and the latest synchronized fare parameters.

[0084] It should be noted that those skilled in the art can set specific calculation rules for the minimum fare and the trip fare based on factors such as the economic level of the location of the rail transit and the characteristics of the rail transit. The embodiment of the present invention does not limit the specific calculation rules for the minimum fare and the trip fare.

[0085] S104: Return the ticket price to the station equipment, which is used to execute the deduction processing business according to the ticket price.

[0086] After the fare calculation module of the ticketing subsystem calculates the fare, it can return the fare to the station equipment. The station equipment will execute the deduction processing business according to the fare. For example, if a passenger enters the station, it can determine whether to let the passenger enter the station based on the minimum fare and the ticket card balance. If the passenger leaves the station, it can determine whether to let the passenger enter the station based on the trip fare and the ticket card balance, and execute the card writing to deduct the trip fare.

[0087] It should be noted that, for the method embodiment, since it is basically similar to the rail transit ticket processing embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the rail transit ticket processing embodiment.

[0088] The rail transit ticket processing method provided by the embodiment of the present invention is applied to the rail transit ticket processing system provided by the embodiment of the present invention, so that the rail transit ticket processing method has corresponding beneficial effects.

[0089] Through the above description of the implementation methods, the technicians in the relevant field can clearly understand that the present invention can be implemented by means of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute the rail transit ticket processing method described in each embodiment of the present invention.

[0090] It is worth noting that in the above-mentioned embodiment of the rail transit ticket processing system, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0091] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A rail transit ticket processing system, characterized in that: It includes a ticketing subsystem, a clearing subsystem and station equipment, the station equipment and the clearing subsystem are in communication with the ticketing subsystem, and the ticketing subsystem includes a fare calculation module; The fare calculation module is used to synchronize fare parameters from the clearing subsystem; The station equipment is used to send a fare calculation request to the ticketing subsystem when a ticket counting event is detected; The fare calculation module is also used to calculate the fare according to the fare parameters when receiving the fare calculation request, and return the fare to the station device; The station equipment is used to execute fee deduction processing business according to the ticket price.

2. The rail transit ticket processing system according to claim 1, characterized in that: The fare calculation module includes a parameter synchronization unit, and the clearing subsystem includes an operation management module; The parameter synchronization unit is used to send a parameter synchronization request to the operation management module when a synchronization event is detected; The operation management module is used to return the fare parameter to the parameter synchronization unit upon receiving the parameter synchronization request; The parameter synchronization unit is used to store the fare parameter.

3. The rail transit ticket processing system according to claim 1, characterized in that: The fare calculation module also includes a device connection unit and a device heartbeat processing unit; The device connection unit is used to determine whether the station device is a device in the whitelist upon receiving a connection request from the station device, and if so, establish a connection with the station device; if not, disconnect the connection with the station device; The device heartbeat processing unit is used to determine that the station device is offline and release the communication interface connected to the station device if no message from the station device is received within a preset time after the device connection unit establishes a connection with the station device and the communication interface connected to the station device is released.

4. The rail transit ticket processing system according to claim 1, characterized in that: The station equipment includes a cloud fare calculation interface module, a local fare calculation module and a reader / writer; The cloud fare calculation interface module is used to send a fare calculation request to the fare calculation module when the reader detects a ticket counting event, receive the fare returned by the fare calculation module, and return the fare to the reader; The local fare calculation module is used to calculate the fare when the cloud fare calculation interface module fails, and return the fare to the reader / writer.

5. The rail transit ticket processing system according to claim 1, characterized in that: The fare calculation module includes a minimum fare calculation unit; The station equipment is also used to generate a minimum fare verification request and send it to the fare calculation module when detecting that a passenger enters the station, wherein the minimum fare verification request includes the passenger's ticket information and station information; The minimum fare calculation unit is used to query the minimum fare of the station where the passenger enters the station according to the ticket information and the station information, and return the minimum fare to the station equipment; The station equipment is also used to confirm whether the passenger is allowed to enter the station based on the minimum fare.

6. The rail transit ticket processing system according to claim 1, characterized in that: The fare calculation module includes a trip fare calculation unit; The station equipment is also used to generate a trip fare calculation request and send it to the trip fare calculation unit when detecting that a passenger is leaving the station, wherein the trip fare calculation request includes the ticket information of the passenger; The travel fare calculation unit is used to calculate the travel fare of the passenger according to the ticket information of the passenger and the fare parameter, and return the travel fare to the station equipment.

7. The rail transit ticket processing system according to claim 6, characterized in that: The station equipment is also used to determine whether the balance of the passenger's ticket is greater than or equal to the trip fare. If so, the trip fare is deducted from the ticket and the exit gate is controlled to open. If not, the exit gate is controlled to close and a prompt message of insufficient balance is generated.

8. The rail transit ticket processing system according to any one of claims 1 to 7, characterized in that: The ticketing subsystem also includes a transaction management module; The station equipment is also used to generate ticket transaction data and upload it to the transaction management module after executing the fee deduction business processing.

9. The rail transit ticket processing system according to any one of claims 1 to 7, characterized in that: The fare calculation module also includes a service monitoring unit; The service monitoring unit is used to record the time when the fare calculation request is received as the service start time, and record the time when the fare calculation is completed as the service end time, and calculate the service time according to the service start time and the service end time.

10. A rail transit ticket processing method, characterized in that: The rail transit ticket processing system applied to any one of claims 1 to 9 comprises: Synchronize fare parameters from the clearing subsystem; receiving a fare calculation request, wherein the fare calculation request is a request generated when a station device detects a ticket counting event; Calculate the fare according to the fare parameters; The fare is returned to the station equipment, and the station equipment is used to perform fee deduction processing according to the fare.

Images