Blockchain-based track traffic intelligent ticketing data witnessing method and system

Abstract

The application discloses a kind of track traffic wisdom ticket data witnessing method and system based on blockchain, the application is each operating subject and adds blockchain node, ticket data witnessing chain is set in each blockchain node, forms track traffic blockchain network, and selects a ticket management system from each operating subject, and ticket management system is responsible for the transaction data clearing settlement of cross operating subject, non-write-back type ticket business rule management of boarding voucher, ticket data witnessing chain is used to witness OD transaction data, supplementing data, clearing settlement data and so on of cross operating subject and write ticket data witnessing chain.This application realizes the real-time sharing, clearing settlement and mutual trust mechanism of ticket data, improves the interoperability, security and maintenance efficiency of ticket data.

Description

Technical Field

[0001] This invention relates to urban rail transit data management technology, and more particularly to a blockchain-based smart ticketing data verification method and system for rail transit. Background Technology

[0002] With the continuous expansion and improvement of urban rail transit networks, many regions have completed the construction and planning of multiple inter-provincial / inter-city (suburban) lines. Therefore, the interconnection and interoperability of ticketing data in rail transit automatic fare collection systems has become crucial.

[0003] However, current automated fare collection systems for rail transit generally adopt a centralized structure, which involves setting up a central service node for data storage and processing. This centralized structure leads to problems such as poor data interoperability, low security, and low maintenance efficiency among ticketing systems of different operators and cities, severely hindering the integrated development of smart ticketing management for rail transit. Summary of the Invention

[0004] To address the problems existing in the prior art, the purpose of this invention is to provide a blockchain-based smart ticketing data witnessing method and system for rail transit that features strong interoperability, high security, and high maintenance efficiency.

[0005] To achieve the above-mentioned objectives, the present invention provides the following technical solution:

[0006] A blockchain-based method for verifying smart ticketing data in rail transit includes:

[0007] Add blockchain nodes to each operating entity, set up a ticketing data witness chain in each blockchain node to form a rail transit blockchain network, and select one of the operating entities to set up a ticketing management system;

[0008] When an entry event is triggered on the entry device of the automatic fare collection system of each operator, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the entry device is obtained and written into the ticket certificate as the entry identifier; when an exit event is triggered on the exit device, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the exit device is obtained and written into the ticket certificate as the exit identifier, and an exit transaction record is generated based on the entry identifier, exit identifier and ticket certificate information in the ticket certificate and uploaded to the data management center of the automatic fare collection system.

[0009] When the data management center of the automatic fare collection system receives the exit transaction record, it generates OD transaction data based on the exit transaction record, and determines whether it is an OD transaction across operating entities based on the entry and exit identifiers in the OD transaction data. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node where it is located.

[0010] When the station supplementary registration terminal of the automatic fare collection system of each operator receives a one-sided supplementary registration request, it obtains the identification code of the operator to which the entry / exit equipment of the ticket to be supplemented belongs as the entry / exit identifier, and generates supplementary registration data based on the entry identifier and exit identifier, and uploads it to the data management center of the automatic fare collection system;

[0011] When the data management center of the automatic ticketing system receives the supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node where it is located.

[0012] When the clearing and settlement time arrives, the data management center of the ticketing management system reads the OD transaction data and supplementary data from the ticketing data witness chain, and performs clearing and settlement for each operating entity according to the preset clearing rules, forming clearing and settlement data. The clearing and settlement data is then recorded and written into the ticketing data witness chain through the blockchain node.

[0013] Furthermore, the method also includes:

[0014] When an entry / exit event is triggered on the entry / exit equipment of each automatic fare collection system, and the ticket that triggered the event is a non-write-back ticket, the identification code of the operating entity to which the entry / exit equipment belongs is obtained as the entry / exit identifier, and an entry / exit transaction record is generated based on the entry / exit identifier and the ticket information and uploaded to the data management center of the ticketing management system.

[0015] When the data management center of the ticketing management system receives the exit transaction record of a non-write-back ticket voucher, it pairs the entry and exit transaction records to generate OD transaction data. Based on the entry and exit identifiers in the OD transaction data, it determines whether it is an OD transaction across operating entities. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node.

[0016] Furthermore, the method also includes:

[0017] When the online supplementary registration terminal of the ticketing management system receives a one-sided supplementary registration request, it obtains the identification code of the operating entity of the entry / exit equipment of the ticket voucher that needs to be supplemented, uses it as the entry / exit identifier, and generates supplementary registration data based on the entry and exit identifiers, and uploads it to the data management center of the ticketing management system.

[0018] When the data management center of the ticketing management system receives supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node.

[0019] Furthermore, the method also includes:

[0020] The data management center of each automated fare collection system reads the clearing and settlement data from the ticketing data witness chain of its blockchain node and audits and verifies it with the transaction data stored locally. If there is a dispute, the disputed data is recorded and written into the ticketing data witness chain.

[0021] Furthermore, when an entry event is triggered on the entry equipment of the automatic fare collection system of each operating entity, and the ticket that triggered the event is a write-back ticket, an entry transaction record is generated based on the entry identifier and the ticket, and uploaded to the data management center of the automatic fare collection system to which the entry is located.

[0022] A blockchain-based smart ticketing data witnessing system for rail transit includes: automatic fare collection systems of each operating entity and a ticketing management system set up on one of the operating entities. Each operating entity's automatic fare collection system is equipped with a blockchain node, and each blockchain node is equipped with a ticketing data witnessing chain, forming a rail transit blockchain network.

[0023] Each automatic fare collection system is equipped with entry devices, exit devices, station registration terminals, and a data management center. The entry devices, when an entry event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the entry identifier and write it into the ticket. The exit devices, when an exit event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the exit identifier and write it into the ticket. Based on the entry identifier, exit identifier, and ticket information, they generate an exit transaction record and upload it to the corresponding data management center. The station registration terminal, upon receiving a unilateral registration request, obtains the operator's identification code of the entry / exit device of the ticket requiring registration as the entry / exit identifier, generates registration data based on the entry and exit identifiers, and uploads it to its respective data management center.

[0024] The data management center of the automatic ticketing system includes a first data discrimination module and a second data discrimination module. The first data discrimination module is used to generate OD transaction data based on the outbound transaction record when it receives the outbound transaction record, and to determine whether it is an OD transaction across operating entities based on the inbound and outbound identifiers in the OD transaction data. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node where it is located. The second data discrimination module is used to determine whether it is a supplementary registration transaction across operating entities based on the inbound and outbound identifiers in the supplementary registration data when it receives the supplementary registration data. If so, the supplementary registration data is recorded and written into the ticketing data witness chain through the blockchain node where it is located.

[0025] The ticketing management system is equipped with a data management center, which includes a clearing and settlement module. When the clearing and settlement time arrives, the clearing and settlement module reads the OD transaction records and unilateral supplementary records from the ticketing data witness chain, performs clearing and settlement for each operating entity according to the preset clearing rules, forms clearing and settlement data, and writes the clearing and settlement data into the ticketing data witness chain through the blockchain node.

[0026] Furthermore, the automatic fare collection system's entry / exit equipment is also used to obtain the identification code of the operating entity to which the entry / exit equipment belongs as an entry / exit identifier when an entry / exit event is triggered and the ticket voucher that triggered the event is a non-write-back type ticket voucher. The system then generates an entry / exit transaction record based on the entry / exit identifier and the ticket voucher information and uploads it to the data management center of the ticketing management system.

[0027] The data management center of the ticketing management system also includes a first data discrimination module, which is used to match the entry transaction record and the exit transaction record when receiving the exit transaction record of the non-write-back ticket voucher, generate OD transaction data, and determine whether it is an OD transaction across operating entities based on the entry identifier and exit identifier in the OD transaction data. If so, the OD transaction data is written into the ticketing data witness chain through the blockchain node.

[0028] Furthermore, the ticketing management system is also equipped with an online supplementary registration terminal, which is used to obtain the identification code of the operating entity of the entry / exit equipment of the ticket voucher that needs to be supplemented when a unilateral supplementary registration request is received, as the entry / exit identifier, and generate supplementary registration data based on the entry and exit identifiers, and upload it to the data management center;

[0029] The data management center of the ticketing management system also includes a second data discrimination module, which is used to determine whether a supplementary registration transaction is a cross-operating entity based on the entry and exit identifiers in the supplementary registration data when receiving supplementary registration data. If so, the supplementary registration data is recorded and written into the ticketing data witness chain through the blockchain node.

[0030] Furthermore, the data management center of the automated ticketing system also includes a data audit module, which is used to read the clearing and settlement data from the ticketing data witness chain of the blockchain node and audit and verify it with the transaction data stored locally. If there is a dispute, the disputed data is recorded and written into the ticketing data witness chain.

[0031] Furthermore, the entry device of the automatic fare collection system is also used to generate an entry transaction record based on the entry identifier and the ticket when an entry event is triggered and the ticket is a write-back ticket, and upload it to the data management center of the automatic fare collection system to which it belongs.

[0032] Compared with existing technologies, the beneficial effects of this invention are as follows: This invention provides a blockchain-based smart ticketing data witnessing method for rail transit. It establishes a ticketing data witnessing chain in the blockchain, realizes the sharing, clearing, settlement and mutual trust mechanism of transaction data across operating entities within the metropolitan area, breaks down the data interoperability barriers of traditional centralized systems, improves data interoperability, security and maintenance efficiency, reduces operating costs, and promotes the integrated process of rail transit ticketing management in the metropolitan area. Attached Figure Description

[0033] Figure 1 This is a flowchart illustrating the blockchain-based smart ticketing data witnessing method for rail transit provided in an embodiment of the present invention.

[0034] Figure 2 This is a schematic diagram of the blockchain-based smart ticketing data witnessing system for rail transit provided in an embodiment of the present invention. Detailed Implementation

[0035] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0036] Example 1

[0037] This invention provides a blockchain-based method for witnessing smart ticketing data in rail transit, such as... Figure 1 As shown, it includes the following steps:

[0038] S1. Add blockchain nodes to each operating entity, set up a ticketing data witness chain in each blockchain node to form a rail transit blockchain network, and select one of the operating entities to set up a ticketing management system.

[0039] Rail transit systems in different cities and provinces are generally operated by different operators, while rail transit systems within the same city are generally operated by the same operator. Therefore, different operators typically represent different cities. The rail transit blockchain network used in this invention is as follows: Figure 2 As shown, each automated fare collection system connects to the blockchain network through its blockchain nodes, employing a consensus mechanism to maintain the stable operation of the blockchain. Each blockchain node establishes a ticketing data witnessing chain to witness data such as OD transaction data, unilateral supplementary registration data, clearing and settlement data, and disputed data across operating entities, ensuring the authenticity and integrity of data across operating entities within the metropolitan area. The ticketing data witnessing chain uses blockchain technology to ensure data consistency across all blockchain nodes, guaranteeing data interoperability and improving security and maintenance efficiency.

[0040] The ticketing management system is responsible for managing ticketing operations under unified rules, such as managing transaction data clearing and settlement across operating entities and managing ticketing rules for non-write-back travel vouchers.

[0041] S2. When an entry event is triggered on the entry equipment of the automatic fare collection system of each operator, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the entry equipment is obtained and written into the ticket certificate as the entry identifier. When an exit event is triggered on the exit equipment, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the exit equipment is obtained and written into the ticket certificate as the exit identifier. An exit transaction record is generated based on the entry identifier, exit identifier and ticket certificate information in the ticket certificate and uploaded to the data management center of the automatic fare collection system.

[0042] Among them, write-back tickets refer to tickets on which data can be written, such as prepaid transportation cards and disposable transportation cards. The encoding rules for the operating entity identification code can be the same as the city code encoding rules, or they can be uniformly defined according to the characteristics of metropolitan areas and city clusters; the rules are not limited.

[0043] The write-back type ticket voucher records the entry and exit identifiers and voucher information, as well as entry and exit times, device number, and other information. The generated exit transaction record includes the entry station code, entry station line code, entry identifier, entry time, exit station code, exit station line code, exit identifier, exit time, and the consumption amount for this trip.

[0044] Furthermore, when an entry event is triggered on the entry equipment of an automated fare collection system operated by a particular entity, and the ticket used to trigger the event is a write-back type ticket, an entry transaction record can be generated based on the entry identifier and the ticket, and uploaded to the data management center of the respective automated fare collection system. This entry transaction record can be used for data verification, matching, and supplementary entries.

[0045] S3. When the data management center of the automatic fare collection system receives the exit transaction record, it generates OD transaction data based on the exit transaction record, and determines whether it is an OD transaction across operating entities based on the entry and exit identifiers in the OD transaction data. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node.

[0046] Origin-Destination Transaction (OD) data refers to a complete travel transaction record completed by a passenger in rail transit from the origin to the destination. When the OD transaction data involves multiple operating entities (i.e., the entry and exit identifiers are inconsistent), it is written to the ticketing data witness chain. If it does not involve multiple operating entities (i.e., the entry and exit identifiers are consistent), it can be stored locally without uploading.

[0047] S4. When the station supplementary registration terminal of the automatic fare collection system of each operator receives a unilateral supplementary registration request, it obtains the identification code of the operator to which the entry / exit equipment of the ticket voucher to be supplemented belongs as the entry / exit identifier, and generates supplementary registration data based on the entry identifier and exit identifier, and uploads it to the data management center of the automatic fare collection system.

[0048] Among them, one-sided supplementary data refers to transaction data that only has entry or exit transaction records and cannot be matched by OD (Original Department) pairing. After supplementation, the data can be used for fare settlement. Each operator's automatic fare collection system has a station supplementary data terminal at the station, which can perform one-sided data supplementation. The supplementary data after completion includes the entry station code, entry station line code, entry identifier, entry time, exit station code, exit station line code, exit identifier, exit time, supplementary amount, and entry supplementary data mark or exit supplementary data mark, etc.

[0049] S5. When the data management center of the automatic fare collection system receives the supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node.

[0050] S6. When the clearing and settlement time arrives, the data management center of the ticketing management system reads the OD transaction data and supplementary data from the ticketing data witness chain, and performs clearing and settlement for each operating entity according to the preset clearing rules, forming clearing and settlement data, and writes the clearing and settlement data into the ticketing data witness chain through the blockchain node.

[0051] The clearing and settlement time can be a fixed time every day or a fixed time every few days, whichever needs to be set. The clearing and settlement data should include detailed clearing and settlement information for each transaction, especially the allocation details of the amount for each operating entity.

[0052] S7. When an entry / exit event is triggered on the entry / exit equipment of each automatic fare collection system, and the ticket that triggered the event is a non-write-back ticket, the identification code of the operating entity to which the entry / exit equipment belongs is obtained as the entry / exit identifier. Based on the entry / exit identifier and the ticket information, an entry / exit transaction record is generated and uploaded to the data management center of the ticketing management system.

[0053] Non-write-back boarding passes generally refer to a new type of boarding pass where ticketing is processed through an upper-level system. These are passes where the entry / exit equipment cannot rewrite the internal information of the pass during entry / exit operations; instead, the upper-level system must perform business logic checks. Examples include electronic boarding QR codes. In such cases, a ticketing management system is needed for unified management.

[0054] S8. When the data management center of the ticketing management system receives the exit transaction record of a non-write-back ticket voucher, it pairs the entry transaction record and the exit transaction record to generate OD transaction data. Based on the entry and exit identifiers in the OD transaction data, it determines whether it is an OD transaction across operating entities. If so, it writes the OD transaction data into the ticketing data witness chain through the blockchain node.

[0055] S9. When the online supplementary registration terminal of the ticketing management system receives a unilateral supplementary registration request, it obtains the identification code of the operating entity to which the entry / exit equipment of the ticket voucher to be supplemented belongs, uses it as the entry / exit identifier, and generates supplementary registration data based on the entry identifier and exit identifier, and uploads it to the data management center of the ticketing management system.

[0056] In addition to the registration terminals at the station, the ticketing management system also has an online registration terminal on the Internet for registration.

[0057] S10. When the data management center of the ticketing management system receives the supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded and written into the ticketing data witness chain through the blockchain node.

[0058] S11. The data management center of each automatic ticketing system reads the clearing and settlement data from the ticketing data witness chain of its blockchain node and audits and verifies it with the transaction data stored locally. If there is a dispute, the disputed data is recorded and written into the ticketing data witness chain.

[0059] Disputed data can be reviewed by the ticketing management system and uploaded to the ticketing data witness chain.

[0060] This invention provides a blockchain-based smart ticketing data witnessing method for rail transit, establishing a shared, clearing, settlement, and mutual trust mechanism for transaction data across operating entities within a metropolitan area. This breaks down the data interoperability barriers of traditional centralized systems, improves data interoperability, enhances the security and maintenance efficiency of the ticketing system, reduces operating costs, and promotes the integrated process of rail transit ticketing management in metropolitan areas.

[0061] Example 2

[0062] Figure 2 This is a schematic diagram of a blockchain-based smart ticketing data witnessing system for rail transit provided in an embodiment of the present invention. The system can be implemented using software and / or hardware, and includes: automatic fare collection systems for each operating entity and a ticketing management system installed on one of the operating entities. Each operating entity's automatic fare collection system has a blockchain node, and each blockchain node contains a ticketing data witnessing chain, forming a rail transit blockchain network. Figure 2 The diagram shows the automated ticketing systems for cities A, B, C, ..., N. City A is the central city, which houses a metropolitan area ticketing management system. Each of the automated ticketing systems in cities A, B, C, ..., N has a blockchain node A, B, C, ..., N, and each of these blockchain nodes has a ticketing data witness chain.

[0063] Each automated fare collection system is equipped with entry devices, exit devices, station registration terminals, and a data management center. The entry devices, when an entry event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the entry identifier, write it into the ticket, and generate an entry transaction record based on the entry identifier and ticket, uploading it to the data management center of their respective automated fare collection system. The exit devices, when an exit event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the exit identifier, write it into the ticket, and generate an exit transaction record based on the entry identifier, exit identifier, and ticket information, uploading it to the corresponding data management center. The station registration terminal, upon receiving a unilateral registration request, obtains the operator's identification code of the entry / exit device of the ticket requiring registration as the entry / exit identifier, generates registration data based on the entry and exit identifiers, and uploads it to its respective data management center. The entry / exit equipment is also used to obtain the identification code of the operating entity to which the entry / exit equipment belongs when an entry / exit event is triggered and the ticket certificate that triggered the event is a non-write-back ticket certificate. This code serves as the entry / exit identifier, and the equipment generates an entry / exit transaction record based on the entry / exit identifier and the ticket certificate information, which is then uploaded to the data management center of the ticketing management system.

[0064] The data management center of the automated fare collection system includes a first data discrimination module, a second data discrimination module, and a data auditing module. The first data discrimination module, upon receiving an outbound transaction record, generates OD (Original Departure) transaction data based on the record. It then determines whether the OD transaction is a cross-operating entity transaction based on the entry and exit identifiers within the OD transaction data. If so, the OD transaction data is recorded and written to the ticketing data witness chain through the relevant blockchain node. The second data discrimination module, upon receiving supplementary registration data, determines whether it is a cross-operating entity supplementary registration transaction based on the entry and exit identifiers within the supplementary registration data. If so, the supplementary registration data is recorded and written to the ticketing data witness chain through the relevant blockchain node. The data auditing module reads the clearing and settlement data from the ticketing data witness chain on the relevant blockchain node and audits and verifies it against the transaction data stored locally. If a dispute exists, the disputed data is recorded and written to the ticketing data witness chain.

[0065] The ticketing management system has an online registration terminal and a data management center. When a unilateral registration request is received, the online registration terminal obtains the identification code of the operating entity of the entry / exit equipment of the ticket that needs to be registered, which serves as the entry / exit identifier, and generates registration data based on the entry and exit identifiers, and uploads it to the data management center.

[0066] The ticketing management system's data management center includes a clearing and settlement module, a first data discrimination module, and a second data discrimination module. The clearing and settlement module, when the clearing and settlement time arrives, reads OD transaction records and unilateral supplementary registration records from the ticketing data witness chain, performs clearing and settlement for each operating entity according to preset clearing rules, forms clearing and settlement data, and writes this data into the ticketing data witness chain through its respective blockchain node. The first data discrimination module, upon receiving a non-write-back type ticket voucher's exit transaction record, pairs the entry and exit transaction records to generate OD transaction data. Based on the entry and exit identifiers in the OD transaction data, it determines whether it is an OD transaction across operating entities. If so, it writes the OD transaction data into the ticketing data witness chain through its respective blockchain node. The second data discrimination module, upon receiving supplementary registration data, determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, it writes the supplementary registration data into the ticketing data witness chain through its respective blockchain node.

[0067] The system provided in this embodiment of the invention can be used to execute the method provided in Embodiment 1 of the invention, and has the corresponding functions and beneficial effects of executing the method.

[0068] It is worth noting that in the embodiments of the above system, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy distinction between each other and are not used to limit the scope of protection of the present invention.

[0069] The embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art will clearly understand that each implementation can be achieved using software plus necessary general-purpose hardware platforms, or it can be implemented solely through hardware, as long as the function or purpose can be achieved.

[0070] It should be noted that in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0071] It should be understood that the embodiments and descriptions above are only the principles, main features and advantages of the present invention. Various changes and modifications can be made to the present invention without departing from the spirit and scope of the invention, and all such changes and modifications fall within the protection scope of the present invention.

Claims

1. A blockchain-based method for witnessing smart ticketing data in rail transit, characterized in that, include: Add blockchain nodes to each operating entity, set up a ticketing data witness chain in each blockchain node to form a rail transit blockchain network, and select one of the operating entities to set up a ticketing management system; When an entry event is triggered on the entry device of the automatic fare collection system of each operator, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the entry device is obtained and written into the ticket certificate as the entry identifier; when an exit event is triggered on the exit device, and the ticket certificate that triggered the event is a write-back ticket certificate, the operator's identification code of the exit device is obtained and written into the ticket certificate as the exit identifier, and an exit transaction record is generated based on the entry identifier, exit identifier and ticket certificate information in the ticket certificate and uploaded to the data management center of the automatic fare collection system. When the data management center of the automatic fare collection system receives the exit transaction record, it generates OD transaction data based on the exit transaction record, and determines whether it is an OD transaction across operating entities based on the entry and exit identifiers in the OD transaction data. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node where it is located. When the station supplementary registration terminal of the automatic fare collection system of each operator receives a one-sided supplementary registration request, it obtains the identification code of the operator to which the entry / exit equipment of the ticket to be supplemented belongs as the entry / exit identifier, and generates supplementary registration data based on the entry identifier and exit identifier, and uploads it to the data management center of the automatic fare collection system; When the data management center of the automatic ticketing system receives the supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node where it is located. When the clearing and settlement time arrives, the data management center of the ticketing management system reads the OD transaction data and supplementary data from the ticketing data witness chain, and performs clearing and settlement for each operating entity according to the preset clearing rules, forming clearing and settlement data. The clearing and settlement data is then recorded and written into the ticketing data witness chain through the blockchain node.

2. The blockchain-based smart ticketing data witnessing method for rail transit according to claim 1, characterized in that, The method further includes: When an entry / exit event is triggered on the entry / exit equipment of each automatic fare collection system, and the ticket that triggered the event is a non-write-back ticket, the identification code of the operating entity to which the entry / exit equipment belongs is obtained as the entry / exit identifier, and an entry / exit transaction record is generated based on the entry / exit identifier and the ticket information and uploaded to the data management center of the ticketing management system. When the data management center of the ticketing management system receives the exit transaction record of a non-write-back ticket voucher, it pairs the entry and exit transaction records to generate OD transaction data. Based on the entry and exit identifiers in the OD transaction data, it determines whether it is an OD transaction across operating entities. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node.

3. The blockchain-based smart ticketing data witnessing method for rail transit according to claim 1, characterized in that, The method further includes: When the online supplementary registration terminal of the ticketing management system receives a one-sided supplementary registration request, it obtains the identification code of the operating entity of the entry / exit equipment of the ticket voucher that needs to be supplemented, uses it as the entry / exit identifier, and generates supplementary registration data based on the entry and exit identifiers, and uploads it to the data management center of the ticketing management system. When the data management center of the ticketing management system receives supplementary registration data, it determines whether it belongs to a supplementary registration transaction across operating entities based on the entry and exit identifiers in the supplementary registration data. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node.

4. The blockchain-based smart ticketing data witnessing method for rail transit according to claim 1, characterized in that, The method further includes: The data management center of each automated fare collection system reads the clearing and settlement data from the ticketing data witness chain of its blockchain node and audits and verifies it with the transaction data stored locally. If there is a dispute, the disputed data is recorded and written into the ticketing data witness chain.

5. The blockchain-based smart ticketing data witnessing method for rail transit according to claim 1, characterized in that, When an entry event is triggered on the entry equipment of the automatic fare collection system of each operator, and the ticket that triggered the event is a write-back ticket, an entry transaction record is generated based on the entry identifier and the ticket, and uploaded to the data management center of the automatic fare collection system to which the record belongs.

6. A blockchain-based smart ticketing data verification system for rail transit, characterized in that, include: Each operating entity has its own automatic fare collection system and a ticketing management system set up on one of the operating entities. Each operating entity's automatic fare collection system has a blockchain node set up, and each blockchain node has a ticketing data witness chain set up, forming a rail transit blockchain network. Each automatic fare collection system is equipped with entry devices, exit devices, station registration terminals, and a data management center. The entry devices, when an entry event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the entry identifier and write it into the ticket. The exit devices, when an exit event is triggered and the ticket is a write-back type ticket, obtain the operator's identification code as the exit identifier and write it into the ticket. Based on the entry identifier, exit identifier, and ticket information, they generate an exit transaction record and upload it to the corresponding data management center. The station registration terminal, upon receiving a unilateral registration request, obtains the operator's identification code of the entry / exit device of the ticket requiring registration as the entry / exit identifier, generates registration data based on the entry and exit identifiers, and uploads it to its respective data management center. The data management center of the automatic ticketing system includes a first data discrimination module and a second data discrimination module. The first data discrimination module is used to generate OD transaction data based on the outbound transaction record when it receives the outbound transaction record, and to determine whether it is an OD transaction across operating entities based on the inbound and outbound identifiers in the OD transaction data. If so, the OD transaction data is recorded and written into the ticketing data witness chain through the blockchain node where it is located. The second data discrimination module is used to determine whether a supplementary registration transaction is a cross-operating entity based on the entry and exit identifiers in the supplementary registration data when the supplementary registration data is received. If so, the supplementary registration data is recorded in the ticketing data witness chain through the blockchain node where it is located. The ticketing management system is equipped with a data management center, which includes a clearing and settlement module. When the clearing and settlement time arrives, the clearing and settlement module reads the OD transaction records and unilateral supplementary records from the ticketing data witness chain, performs clearing and settlement for each operating entity according to the preset clearing rules, forms clearing and settlement data, and writes the clearing and settlement data into the ticketing data witness chain through the blockchain node.

7. The blockchain-based smart ticketing data witnessing system for rail transit according to claim 6, characterized in that: The automatic fare collection system's entry / exit equipment is also used to obtain the identification code of the operating entity to which the entry / exit equipment belongs as an entry / exit identifier when an entry / exit event is triggered and the ticket certificate that triggered the event is a non-write-back type ticket certificate. The entry / exit equipment is then used to generate an entry / exit transaction record based on the entry / exit identifier and the ticket certificate information, and upload it to the data management center of the ticketing management system. The data management center of the ticketing management system also includes a first data discrimination module, which is used to match the entry transaction record and the exit transaction record when receiving the exit transaction record of the non-write-back ticket voucher, generate OD transaction data, and determine whether it is an OD transaction across operating entities based on the entry identifier and exit identifier in the OD transaction data. If so, the OD transaction data is written into the ticketing data witness chain through the blockchain node.

8. The blockchain-based smart ticketing data witnessing system for rail transit according to claim 6, characterized in that: The ticketing management system is also equipped with an online supplementary registration terminal, which is used to obtain the identification code of the operating entity of the entry / exit equipment of the ticket voucher that needs to be supplemented when a unilateral supplementary registration request is received, as the entry / exit identifier, and generate supplementary registration data based on the entry and exit identifiers, and upload it to the data management center; The data management center of the ticketing management system also includes a second data discrimination module, which is used to determine whether a supplementary registration transaction is a cross-operating entity based on the entry and exit identifiers in the supplementary registration data when receiving supplementary registration data. If so, the supplementary registration data is recorded and written into the ticketing data witness chain through the blockchain node.

9. The blockchain-based smart ticketing data witnessing system for rail transit according to claim 6, characterized in that: The data management center of the automated ticketing system also includes a data auditing module, which is used to read the clearing and settlement data from the ticketing data witness chain of the blockchain node and audit and verify it with the transaction data stored locally. If there is a dispute, the disputed data is recorded and written into the ticketing data witness chain.

10. The blockchain-based smart ticketing data witnessing system for rail transit according to claim 6, characterized in that, The automatic fare collection system's entry equipment is also used to generate an entry transaction record based on the entry identifier and the ticket when an entry event is triggered and the ticket is a write-back type ticket, and then upload it to the data management center of the automatic fare collection system.

Images