Gate passing method, medium, equipment and fare collection system

Abstract

The invention discloses a lockage passing method, a medium, equipment and a fare collection system. The lockage passing method comprises the following steps: in response to a received lockage request initiated by a ticket card account, detecting whether a traffic permit of the ticket card account is valid or not; in response to the fact that the traffic permit is in an effective state, traffic permit code data are sent to the user side, so that the user side is allowed to generate a first pass code associated with the traffic permit based on the traffic permit code data; and in response to the fact that the traffic pass is in the invalid state, sending the common ticket card code data to the user side to allow the user side to generate a second pass code associated with the common ticket card based on the common ticket card code data. According to the method, switching can be flexibly carried out between various configurable traffic permits and common ticket cards, non-inductive switching of the traffic rules is achieved, the ticket card relevance is improved while the gate passing requirements of different users are met, the operation efficiency of rail transit is improved, and the operation cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of rail transit technology, and in particular to a gate-passing method, medium, equipment and ticket selling and checking system. Background Art

[0002] In the target rail transit, the whole process of rail transit ticket sales, ticket checking, billing, charging, clearing, and management is automated through the Automatic Fare Collection (AFC) system. The existing subway automatic ticket collection system mainly uses ordinary tickets such as single-trip tickets, regular tickets, and ride tickets. Among them, the single-trip ticket uses a single ride deduction method, and deducts fees from the physical card, electronic card or payment platform according to the single entry and exit trip, distance, duration, etc.; the regular ticket uses a limited ride validity period deduction method, and no additional fees will be charged for rides within the predetermined period after purchase; the ride ticket uses a limited ride number deduction method, and no additional fees will be charged for rides within the preset number of times after purchase.

[0003] However, these ticket types have many inconveniences in actual application. First, there is often no correlation between the different tickets held by passengers, and passengers need to manually select and switch different types of tickets according to their travel needs, which not only increases the complexity of passengers' travel, but may also lead to misuse or loss due to improper ticket management. At the same time, when there is an abnormality in the ticket, the intervention of station staff is often required to resolve the abnormal state, which not only affects the travel efficiency of passengers, but also increases the operating costs of the station. In addition, with the rapid development of urban rail transit and the diversification of passenger travel needs, traditional ticket media and ticket type attributes have become increasingly difficult to meet the different needs of passengers. For example, some passengers may want to buy a ticket that can be used multiple times within a limited time, while others may prefer to buy a ticket that can be used unlimited times within a limited mileage. Summary of the invention

[0004] The present application mainly provides a gate-passing method, medium, equipment and ticket selling and checking system, aiming to solve the existing technical problem of low gate-passing efficiency.

[0005] In order to solve the above technical problems, the technical solution adopted by the present application is: to provide a gate-passing method. The gate-passing method includes: in response to receiving a gate-passing request initiated by a ticket card account, detecting whether the traffic pass of the ticket card account is valid; in response to the traffic pass being in a valid state, sending traffic pass code data to the user terminal to allow the user terminal to generate a first pass code associated with the traffic pass based on the traffic pass code data; in response to the traffic pass being in an invalid state, sending ordinary ticket card code data to the user terminal to allow the user terminal to generate a second pass code associated with an ordinary ticket card based on the ordinary ticket card code data; wherein, the traffic pass is restricted according to the preset usage rule range of the corresponding pass type, and the first pass code and the second pass code are used to indicate the corresponding gate device to open the gate passage.

[0006] In some embodiments, each of the pass types corresponds to a different range of preset usage rules; the preset usage rule range is determined based on at least one of a configurable validity date, daily validity time, maximum number of passes, daily number of passes, maximum mileage, and daily mileage.

[0007] In some embodiments, before the response to receiving a gate-pass request initiated by a ticket card account and detecting whether the transportation pass of the ticket card account is valid, it also includes: receiving an account registration request initiated by the user terminal; performing account configuration based on the account registration request to generate the ticket card account, and feeding back the account information of the ticket card account to the user terminal; receiving a contract signing request initiated by the user terminal based on the account information, establishing contract signing information synchronization with the user terminal, so as to activate the ordinary ticket card associated with the ticket card account.

[0008] In some embodiments, before the response to receiving a gate pass request initiated by the ticket card account and detecting whether the transportation pass of the ticket card account is valid, it also includes: receiving a pass generation request initiated by the user terminal, parsing the payment information and the corresponding pass type included in the pass generation request; in response to determining that the payable fare of the pass type corresponds to the payment amount of the payment information, activating the transportation pass associated with the ticket card account.

[0009] In some embodiments, before sending the transportation pass code data to the user terminal in response to the transportation pass being in a valid state, it also includes: in response to determining that the transportation pass associated with the ticket account is in an activated state and the use of the transportation pass is within the preset usage rules, determining that the transportation pass is in a valid state.

[0010] In some embodiments, after the response to receiving a gate pass request initiated by the ticket card account and detecting whether the transportation pass of the ticket card account is valid, it also includes: performing an anti-duplication check on the ticket card account to determine whether the ticket card account meets the single gate pass condition; performing a legitimacy verification on the ticket card account to determine whether the ticket card account meets the legal gate pass condition; in response to determining that the ticket card account meets the single gate pass condition and the legal gate pass condition, allowing the gate device to open a gate pass channel after identifying the first pass code or the second pass code; wherein the legitimacy verification includes at least one of ticket card account field verification, pass credential verification, whitelist verification, signature data verification and entry status verification.

[0011] In some embodiments, the ticket account is associated with the transportation pass and the ordinary ticket, and when the transportation pass is valid, the priority of the transportation pass is greater than the priority of the ordinary ticket.

[0012] In order to solve the above technical problems, another technical solution adopted in the present application is: providing a storage medium having program data stored thereon, characterized in that the program data implements the steps of the gate passing method as described above when executed by a processor.

[0013] In order to solve the above technical problems, another technical solution adopted in the present application is: to provide a computer device, which includes a processor and a memory connected to each other, the memory stores a computer program, and when the processor executes the computer program, the steps of the gate passing method as mentioned above are implemented.

[0014] In order to solve the above-mentioned technical problems, another technical solution adopted in the present application is: to provide a ticket selling and checking system, which includes a ticketing subsystem, a user terminal, an entry site subsystem and an exit site subsystem; the entry site subsystem and the exit site subsystem are both deployed with at least one gate device that supports pass code recognition; the ticketing subsystem is communicated with the site subsystem, the exit site subsystem and the user terminal respectively, and the ticketing subsystem is deployed with the computer device as mentioned above.

[0015] The beneficial effects of the present application are as follows: Different from the prior art, the present application discloses a gate-passing method, medium, equipment and ticket selling and checking system. The present application introduces a traffic pass that is restricted in communication according to the preset usage rules of the pass type, and by judging whether the traffic pass is valid to generate different pass codes, it can flexibly switch between various configurable traffic passes and ordinary tickets, and realize seamless connection between ticket card accounts and user terminals, so that passengers can pass through the gate more conveniently and quickly when they need to pass through the gate, effectively improving the gate-passing efficiency, simplifying the gate-passing process for passengers, reducing the complexity of operation, and improving the ticket-card association, and can realize flexible management of different ticket types to meet the diverse travel needs of passengers. At the same time, in this way, only one account medium, that is, the pass code of the user terminal, can be used to automatically switch tickets and pass through the gate, without the need for additional intervention of relevant staff for ticket processing, so as to realize non-sensing gate-passing, which is conducive to improving the smoothness and comfort of the passengers passing through the gate. In addition, based on this application, operators can also automatically configure different types of transportation passes according to operational needs, flexibly respond to market changes, effectively improve the operational efficiency of rail transit, and reduce card production and operating costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0017] Figure 1 It is a flow chart of an embodiment of a gate-passing method provided by the present application;

[0018] Figure 2 yes Figure 1 A schematic diagram of a flow chart of an embodiment before step 10 in the embodiment;

[0019] Figure 3 yes Figure 1 A schematic diagram of a flow chart of another embodiment before step 10 in the embodiment;

[0020] Figure 4 yes Figure 1 A schematic diagram of a flow chart of an embodiment after step 10 in the embodiment;

[0021] Figure 5 It is a structural schematic diagram of an embodiment of a storage medium provided by the present application;

[0022] Figure 6 is a structural schematic diagram of an embodiment of a computer device provided by the present application;

[0023] Figure 7 It is a structural diagram of an embodiment of a ticket selling and checking system provided by the present application. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0025] The terms "first", "second", "third" in the embodiments of the present application are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first", "second", "third" can expressly or implicitly include at least one of the features. In the description of the present application, the meaning of "multiple" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.

[0026] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0027] This application provides a method for passing through a gate, see Figure 1 , Figure 1 1 is a flow chart of an embodiment of a gate-passing method provided by the present application, and the gate-passing method comprises:

[0028] Step 10: In response to receiving a gate pass request initiated by the ticket card account, check whether the transportation pass of the ticket card account is valid.

[0029] Step 20: In response to the traffic pass being in a valid state, sending the traffic pass code data to the user terminal to allow the user terminal to generate a first pass code associated with the traffic pass based on the traffic pass code data.

[0030] Step 30: In response to the transportation pass being in an invalid state, sending ordinary ticket card code data to the user terminal to allow the user terminal to generate a second pass code associated with the ordinary ticket card based on the ordinary ticket card code data.

[0031] Among them, the traffic pass restricts access according to the preset usage rules of the corresponding pass type, and the first pass code and the second pass code are used to instruct the corresponding gate device to open the gate channel.

[0032] In this embodiment, the ticket card account refers to the carrier associated with the passenger's personal identity information and is used to manage and record the passenger's ticket information, gate pass records, asset data and other information. The ticket card account is stored and managed in electronic form and deployed on the server and user sides. By registering the ticket card account, the registration, activation, contract, reset, balance inquiry and transaction record of the relevant tickets can be designed and implemented, and the relevant information of the ticket card account can be synchronized on the server and user sides of the relevant ticketing system. After registration, there is no need for a constant connection between the server and the user side. It is only necessary to establish synchronous communication when changes are made on the server and the user side, and synchronize the changes in relevant information to the other side in a timely manner. Subsequently, the relevant information of the ticket card account in the corresponding ticketing system server can be used to verify and synchronize the account of the user side.

[0033] In this embodiment, the gate request indicates that the passenger needs to enter or exit the station through the gate equipment, which is initiated by the passenger through the user-end carrier of the ticket card account, such as a mobile device or a recognizable ticket card, and then received by the gate equipment or a specific identification device and establishes synchronous communication with the server to process the relevant gate request. The gate request is associated with the ticket card account. Specifically, the gate request may include the identity information, ticket information, gate record, asset data of the corresponding ticket card account, and the time, station and related gate equipment of the request. Subsequently, based on this information, it is judged whether to pass through the gate, and the gate situation and related impacts of the relevant ticket card account are recorded, for example, the asset data changes and identity information changes after passing through the gate are recorded.

[0034] In this embodiment, the ticket card account is associated with a transit pass (TP), and the transit pass is restricted according to the preset usage rules of the corresponding pass type. Specifically, the transit pass is a virtualized and digitized ticket card that can be identified by a specific card reader and then process related tickets. It can be an interactive program deployed in a mobile device and a recognizable card medium, or it can interact with the card reader through recognizable image encoding technologies such as QR codes and bar codes, or through recognizable communication technologies such as NFC (Near Field Communication) and RFID (Radio Frequency Identification), so as to process tickets and control the passage through the gate. The pass type is a specific transit pass based on operational needs. The preset usage rules of each transit pass are used to control the permissions of the relevant transit passes according to operational needs. For example, a pass may be limited to a specific date range, limited to a certain number of uses, and limited to a specific mileage range. The setting of these preset usage rules allows operators to flexibly adjust and manage the usage conditions of tickets according to different operating strategies and market demands.

[0035] Optionally, each pass type corresponds to a different range of preset usage rules; the preset usage rule range is determined based on at least one of a configurable validity date, daily validity time, maximum number of passes, daily number of passes, maximum mileage, and daily mileage.

[0036] In this optional embodiment, various parameters that can be used to configure the preset usage rule range are specified, among which the validity date refers to the validity period of the traffic pass of the corresponding pass type. For example, if the validity date is configured to be valid in December of a certain year, then the traffic pass is only valid in December of that year; the daily validity time refers to the specific time period during which the traffic pass is allowed to be used in a day. For example, the traffic pass can be configured to be valid from 10:00 to 12:00 and from 14:00 to 16:00 every day to avoid the morning and evening rush hours for work commuting; the maximum number of passes is the number of times allowed to pass the The maximum number of times a traffic pass can pass through the gate. For example, if the maximum number of passes is configured as 10, it is valid for 10 passes and invalid after exceeding the limit. The number of passes per day refers to the number of times a traffic pass is allowed to pass through the gate in one day. For example, a maximum of 5 passes are allowed per day. The maximum mileage refers to the maximum mileage that a traffic pass allows passengers to travel within the preset usage rules. For example, a maximum of 5,000 kilometers is allowed. The daily mileage refers to the mileage that a traffic pass allows passengers to travel in one day. For example, a maximum of 20 kilometers is allowed per day.

[0037] In this optional embodiment, the preset usage range of the pass type can be configured according to at least one of these configurable parameters to be applicable to different operation scenarios. For example, a time-based transportation pass can be configured with an effective date and a daily pass number to limit the number of rides allowed per day for the relevant passenger; a trip-based transportation pass can be configured with an effective date and a maximum pass number to limit the number of rides allowed per day for the relevant passenger; a mileage-based transportation pass can be configured with an effective date and a maximum pass number to limit the mileage that the relevant passenger can ride within the effective date.

[0038] In this optional embodiment, since only the configuration of the relevant configurable parameters is required, it is possible to provide only the configuration interface to the relevant operating personnel to meet the setting of various pass types and various access needs and operational needs. It should be understood that the pass type can be extended through configuration to obtain more types. For example, the above-mentioned mileage-based traffic pass can set the maximum passable mileage to a maximum value that is difficult to achieve, such as 99999, so that the relevant traffic pass is equivalent to no mileage limit. For another example, the above-mentioned time-based traffic pass can set the validity period to 2000-01-01 to 2999-12-31, so that the pass based on the relevant traffic pass is equivalent to only limiting the number of passes per day.

[0039] In this embodiment, in addition to being associated with a transportation pass, the ticket account is also associated with an ordinary ticket. Among them, an ordinary ticket is a traditional ticket form, usually used for single or multiple rides, including one-way tickets, regular tickets, and trip tickets, etc. For details, please refer to the description of the background technology. An ordinary ticket is different from a transportation pass. It has no preset usage rules. Passengers can use ordinary tickets to ride at any time, but the number of times it is used and the validity period are usually limited. Due to the fixedness of its usage rules and the irregularity in actual use, it may have an adverse effect on the smoothness and safety of the operation and management of rail transit. Therefore, transportation passes can be used first to achieve more regular and controllable operation and management. Higher pricing or stricter verification methods can be used for ordinary tickets to reduce the adverse effects caused by the use of ordinary tickets.

[0040] Optionally, the ticket account is associated with a transportation pass and an ordinary ticket. When the transportation pass is valid, the priority of the transportation pass is higher than the priority of the ordinary ticket.

[0041] In this optional embodiment, both the transportation pass and the ordinary ticket card can be associated with the ticket card account, so that when passing through the gate based on the ticket card account, it is possible to flexibly switch between the two types of tickets and cards. Since the transportation pass has more targeted operational support, the priority of the transportation pass associated with the ticket card account is set higher than the priority of the ordinary ticket card, so that the use of the ticket card can better meet the diverse travel needs. When the transportation pass associated with the ticket card account is in an invalid state, the ordinary ticket card becomes the main way to pass through the gate, so that passengers can still use ordinary tickets to pass through the gate without a valid transportation pass. It not only improves the efficiency of passing through the gate, simplifies the process of passengers passing through the gate, but also reduces the operating cost. At the same time, it provides the operator with a flexible ticket management method to meet the diverse travel needs of passengers.

[0042] Optionally, see Figure 2 , before detecting whether the traffic pass of the ticket card account is valid in response to receiving the gate pass request initiated by the ticket card account, it also includes:

[0043] Step 01: Receive an account registration request initiated by the user;

[0044] Step 02: Perform account configuration based on the account registration request to generate a ticket card account, and feed back the account information of the ticket card account to the user end;

[0045] Step 03: Receive a contract signing request initiated by the user based on the account information, and establish contract signing information synchronization with the user to activate the common ticket card associated with the ticket card account.

[0046] This optional embodiment specifies the registration process of the ticket card account. Specifically, the account registration request is initiated by the passenger through the user terminal, for example, by opening the registration interface of the relevant application or web page and filling in the account registration information in the registration form, by passing the card of the relevant media through a specific card making device, etc. The account registration request may include the account name, password and other basic information and the account usage scope, personalization and other configuration requirements, which are used to create a new ticket card account.

[0047] In this optional embodiment, after receiving the account registration request, the relevant account configuration can be performed. For example, the account information can be saved to the server according to the request, the account ID (Identity document) and ticket card authorization can be allocated, etc., to complete the registration and generate a ticket card account. After successful registration, the account information will be sent to the user end so that the passenger can use this information for subsequent ticketing operations. The contract signing request is initiated by the user end after registering the account, indicating that the user is willing to accept the relevant agreements and agreements to enjoy the relevant passage services. During the contract signing process, the user end may be required to make a payment. The payment method can be specifically through a third-party payment channel or through a recharge channel to meet different contract signing requirements. The synchronization of contract signing information is to ensure that the status of the ticket card account on the user end and the server end is consistent, and to ensure the accuracy and security of ticket processing. In this way, while passengers enjoy more convenient and personalized gate-passing services, the operator can also manage the ticketing system more effectively and improve overall operational efficiency.

[0048] In this optional embodiment, the association between the ordinary ticket card and the ticket card account can be permanent, and the ordinary ticket card can be generated together when the ticket card account is registered, so that the ticket card account can be switched to the ordinary ticket card for passage at any time, meeting the basic passage needs of passengers. Through the ticket card account registration method, the gate-passing method provided by this application can effectively improve the gate-passing efficiency, simplify the gate-passing process for passengers, reduce the complexity of operation, and provide the operator with a flexible ticket card management method to meet the diverse travel needs of passengers, and effectively improve the operational efficiency of rail transit and reduce card making and operating costs.

[0049] Optionally, see Figure 3 , before detecting whether the traffic pass of the ticket card account is valid in response to receiving the gate pass request initiated by the ticket card account, it also includes:

[0050] Step 04: Receive the pass generation request initiated by the user terminal, and parse the payment information and corresponding pass type included in the pass generation request.

[0051] Step 05: In response to determining that the fare payable for the pass type corresponds to the payment amount of the payment information, activating the transportation pass associated with the ticket account.

[0052] In this embodiment, the pass generation request is initiated by the user end and is used to generate a specific type of traffic pass. When the user end initiates the pass generation request, it is necessary to provide payment information and select the type of pass it wishes to obtain. For example, a passenger can purchase a traffic pass in the application software of the user end such as a mobile phone, tablet or ticket machine, select the type of traffic pass it wants to purchase, and then the user end will display the payable fare for the passenger to confirm whether to pay. After the passenger completes the payment through a third-party payment channel or a recharge channel, a pass generation request including payment information and the type of pass can be generated, and then the activation of the traffic pass corresponding to the ticket account is completed through steps such as preparing ticket card data, data assembly, data signing and data preservation, and the synchronization of the ticket card accounts of the user end and the server end is performed, so that the passenger can pass through the traffic pass.

[0053] In this optional embodiment, the ticket card structure of the transportation pass may specifically include the pass code version, pass code data length, issuer public key certificate, payment account number, card account number, issuer number, code issuing platform number, card account type, upper limit of single consumption amount, payment account user public key, payment account system authorization expiration time, pass code validity time, user ID, trip serial number, ticket card logical card number, ticket status, last ticket station code, last ticket processing time, industry data expiration time, entry channel, payment channel, ticket card type, pass code validity start time, pass code validity start time, maximum number of trips per day, maximum number of trips within the validity period, maximum mileage within the validity period, ticket purchase order number, issuer authorization signature, pass code generation time and payment account user private key signature and other information. This information uses different data lengths and data formats, and is automatically generated according to relevant registration requests or actively filled in based on configuration needs.

[0054] In this embodiment, the pass type can be set by the operator to meet the operator's different pricing strategies and operation plans, and the pass type corresponding to the request is selected by the user. The corresponding transportation pass is activated based on the pass type and payment amount corresponding to the request, thereby realizing the diversification of transportation pass types, meeting the travel needs of different users, and ensuring the personalized needs of ticket processing. This not only improves service efficiency, but also enhances user experience, allowing passengers to flexibly purchase and use transportation passes according to their travel plans, while also providing operators with effective ticket management methods.

[0055] Optionally, before sending the transportation pass code data to the user terminal in response to the transportation pass being in a valid state, it also includes: in response to determining that the transportation pass associated with the ticket account is in an activated state and the use of the transportation pass is within the scope of preset usage rules, determining that the transportation pass is in a valid state.

[0056] This optional embodiment specifies a method for determining the effective status. When the transportation pass associated with the ticket account is in an activated state, it indicates that the ticket account can use the transportation pass to perform pass operations. If the use of the transportation pass is within the preset usage rules, it indicates that the access rights of the relevant ticket account comply with the rules set by the operator, such as time, location, number of times, and other restrictions. Only when the pass meets both conditions will it be confirmed that the transportation pass is in a valid state, and then the transportation pass code data will be sent to the user end. In this way, when using the transportation pass, passengers can ensure that their travel behavior complies with the regulations of the operator, while ensuring the legality and security of ticket processing, which not only improves the efficiency of ticket processing, but also enhances the security of the system and the trust of users.

[0057] Optionally, see Figure 4 , in response to receiving a gate pass request initiated by a ticket card account, after detecting whether the traffic pass of the ticket card account is valid, it also includes:

[0058] Step 11: Perform an anti-duplication check on the ticket card account to determine whether the ticket card account meets the single gate pass conditions;

[0059] Step 12: Verify the legitimacy of the ticket card account to determine whether the ticket card account meets the legal gate-passing conditions;

[0060] Step 13: in response to determining that the ticket card account meets the single gate pass condition and the legal gate pass condition, allowing the gate device to open the gate pass channel after identifying the first pass code or the second pass code;

[0061] Among them, the legitimacy verification includes at least one of ticket card account field verification, pass credential verification, whitelist verification, signature data verification and entry status verification.

[0062] In this optional embodiment, the single gate-passing condition means that the ticket card account can only perform a gate-passing operation once within a certain period of time. The anti-duplicate check on the ticket card account is to judge whether the single gate-passing condition is met. The anti-duplicate check method can be specifically implemented by recording the gate-passing timestamp and gate-passing frequency of the ticket card account, so as to ensure that the ticket card account will not pass the gate repeatedly within the set time window. For example, if the set time window is 5 minutes, then within 5 minutes, the gate-passing authorization of the ticket card account can be temporarily closed by the relevant gate equipment, or the same ticket card account can be prohibited from passing the gate again by generating erroneous transaction data to remind the service end or other user end, so as to prevent repeated gate-passing. This can ensure the uniqueness and security of the ticket card account, and avoid the chaos in the operational order caused by the repeated use or abuse of the traffic pass or ordinary ticket card in the ticket card account.

[0063] In this optional embodiment, the legal gate-passing conditions refer to a series of conditions that the ticket card account must meet when performing gate-passing operations, including but not limited to the validity of the ticket card account, the consistency of the ticket card account and the pass, whether the ticket card account is in the white list, the correctness of the signature data, and the legality of the entry status. The legality verification accordingly includes checking whether the card issuer code is consistent, judging whether the current time exceeds the pass code expiration time, whether the device code is in the white list, verifying the signature data of the pass code, etc., so as to ensure that the use of the ticket card account complies with the regulations of the operator, prevent the ticket card account that has been illegally forged or tampered with from passing through the gate, and ensure the safety and order of the entire transportation system.

[0064] In this optional embodiment, if it is determined that the ticket card account meets the single gate pass condition and the legal gate pass condition, it means that the ticket card account is qualified to pass the gate legally and compliantly. At this time, the gate device will be authorized to recognize the first pass code or the second pass code and then open the gate pass. The whole process can effectively identify and reject illegal or invalid gate pass requests, thereby maintaining the normal operation of the ticketing system service end and the legitimate rights and interests of passengers, which not only improves the pass efficiency, but also ensures the rigor and accuracy of ticket management, and provides passengers with a convenient and safe pass experience.

[0065] In this embodiment, after the above steps, it is possible to accurately determine whether the traffic pass is valid, and enable the corresponding gate device to open a gate passage through the relevant first pass code or second pass code, thereby realizing an account-based ticketing (ABT). The pass code can be a recognizable coded image such as a QR code and a bar code, or an electronic tag such as a near field communication tag and a radio frequency identification tag, and the traffic pass and ordinary ticket card can be identified through the application software or recognizable physical medium of the user end, and the relevant identification technology is used. These pass codes will be embedded with the corresponding account information of the ticket card account when they are generated, so that after receiving the pass code, the gate device will identify and decode the pass code through the built-in or connected reading device, and compare it with the account information of the ticket card account stored in the server to verify the validity of the pass code. If the pass code is valid, the gate device will automatically open and allow passengers to pass; if it is invalid, the gate will remain closed and provide corresponding prompt information to the passengers.

[0066] In this embodiment, the traffic pass code data is data used to generate the first pass code, and the traffic pass code data may include a unique identifier of the ticket account, preset usage rules of the traffic pass, gate access authority information, validity period information, and encryption keys required to generate the pass code. When generating the first pass code, a unique, non-forgeable pass code can be generated based on the current status and authority information of the ticket account in combination with an encryption algorithm. After the pass code is scanned on the gate device, it will be verified in real time to ensure that it has not been tampered with and has not expired, thereby ensuring the security and reliability of the entire gate access process. The ordinary ticket code data is data used to generate the second pass code, which is similar to the processing of the traffic pass code data and will not be repeated here. The first pass code and the second pass code generated in this way, whether corresponding to a traffic pass or an ordinary ticket card, can ensure their legality and security during use.

[0067] In this embodiment, the structural data of the code data corresponding to the traffic pass or ordinary ticket of the ticket account is preferably encrypted based on the national secret SM2 algorithm, wherein the national secret SM2 algorithm is implemented based on the elliptic curve cryptography (ECC), which can provide extremely high security strength, and can effectively prevent the risk of data leakage during transmission and storage, and ensure the data security of the ticketing system server. During the encryption process, the public and private key pairs of SM2 can be pre-generated, wherein the private key is encrypted and saved on the server side, and is used to add a verification signature to the traffic pass code structure data. The signature is attached to the end of the code structure, and the public key is sent to the user side for storage, which is used to verify whether the signature is consistent when scanning the code, and to achieve the corresponding legality verification.

[0068] In this embodiment, after sending the traffic pass code data to the user terminal in response to the traffic pass being in a valid state, and sending the ordinary ticket card code data to the user terminal in response to the traffic pass being in an invalid state, the application software at the user terminal will automatically select the corresponding first pass code or second pass code for display according to the received code data type. When the user aligns the pass code on the mobile phone or other device with the code reading area of ​​the gate, the built-in or connected reading device of the gate device will recognize and decode the pass code. If the pass code is valid, the gate device will automatically open to allow the user to pass; if the pass code is invalid, the gate will remain closed and display an error prompt to the user, informing the user of the reason why the pass code is invalid, such as expired, tampered, or not matching the ticket card account, etc.

[0069] In this embodiment, more specifically, the gate device is connected to the device gateway of the server, and the gate device program sends a message to the device gateway of the server through the set SOCKET channel or other protocol communication channel to request the traffic pass to monitor the gate and upload the ticket transaction data. The traffic pass is swiped on the gate, and the gate sends a gate monitoring request to the server. The server quickly determines whether the ticket is repeatedly entered and exited, whether it is legal, etc., and then returns the judgment result to the gate device, realizing the background of business logic and reducing the transformation and maintenance costs of the gate device. After the ticket card account holder passes the gate, the gate device uploads the entry and exit ticket transaction data of the traffic pass through the channel communicating with the server, realizing real-time processing and real-time monitoring. This design not only improves the efficiency of traffic, but also ensures the strictness and accuracy of ticket management. It can flexibly switch between a variety of configurable transportation passes and ordinary tickets, realize seamless switching of traffic rules, and improve the correlation between tickets and cards while meeting the gate-passing needs of different users, which is conducive to improving the operational efficiency of rail transit and reducing card production and operating costs.

[0070] See also Figure 5 , Figure 5 It is a structural diagram of an embodiment of the storage medium provided by the present application.

[0071] The storage medium 40 stores program data 41. When the program data 41 is executed by the processor, the following is achieved: Figures 1 to 4 The described method of passing through the gate.

[0072] The program data 41 is stored in a storage medium 40, and includes a number of instructions for enabling a network device (such as a router, a personal computer, a server, or other network device) or a processor to execute all or part of the steps of the methods of the various embodiments of the present application.

[0073] Optionally, the storage medium 40 may be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, or other medium that can store the program data 41 .

[0074] See also Figure 6 , Figure 6 It is a structural schematic diagram of an embodiment of a computer device provided by the present application.

[0075] The computer device 50 includes a processor 52 and a memory 51 connected to each other. The memory 51 stores a computer program. When the processor 52 executes the computer program, the following is achieved: Figures 1 to 4 The described gate-passing method. The memory 51 may include the storage medium 40, or may be other independently developed memory.

[0076] See also Figure 7, Figure 7 60 includes a ticketing subsystem 61, a user terminal 62, an entry site subsystem 63, and an exit site subsystem 64; the entry site subsystem 63 and the exit site subsystem 64 are each deployed with at least one gate device that supports pass code recognition; the ticketing subsystem 61 is communicated with the site subsystem, the exit site subsystem 64, and the user terminal 62, respectively; the ticketing subsystem 61 is deployed with the following Figure 6 Computer equipment described.

[0077] In this embodiment, the gate equipment can specifically identify the pass code through a built-in identification device or connected to an identification device. The ticket sales and inspection system 60 can be specifically applied to rail transit, and can also be applied to other occasions where ticket management is required, such as airports, public transportation systems, stadiums, etc. In the ticket sales and inspection system 60, the ticketing subsystem 61 is responsible for processing the business logic related to ticketing, including the management of ticket card accounts, the issuance of ticket cards, payment processing, statistical analysis of ticket data, etc. The user terminal 62 provides passengers with services such as ticket purchase, inquiry, and payment, and can also display the pass code for gate identification. The entry site subsystem 63 and the exit site subsystem 64 are responsible for managing the gate equipment at each site to ensure that passengers can enter and exit the station smoothly. In addition, the ticket sales and inspection system 60 can also be integrated with a third-party payment platform, an identity verification system, etc. to provide a safer and more convenient ticketing service.

[0078] In this embodiment, in actual application, the ticketing system 60 connects each subsystem through a network to ensure real-time update and synchronization of data. The ticketing subsystem 61 will dynamically adjust the ticket price, preferential activities and other information according to the operator's strategy and rules, and send it to each site subsystem in time. The user end 62 obtains the latest ticketing information through communication with the ticketing subsystem 61, and provides it to the user for ticket card account registration, traffic pass purchase, and gate entry and exit operations. The entry site subsystem 63 and the exit site subsystem 64 are responsible for monitoring the status of the gate equipment, ensuring its normal operation, and processing gate-passing requests. When a passenger passes through the gate, the system will record the gate-passing data in real time and upload it to the ticketing subsystem 61 for processing and storage. The ticketing subsystem 61 can be deployed in the line network center of rail transit. In addition to ticket card account management, the ticketing subsystem 61 can also integrate functional modules such as transaction management and operation management, process transactions of the entry site subsystem 63 and the exit site subsystem 64, and manage related operation strategies.

[0079] The ticketing system 60 of this embodiment not only improves the efficiency of ticket processing and reduces operating costs, but also improves the passenger's travel experience. Through intelligent ticket management, the system can effectively cope with the passenger flow pressure during peak hours and reduce waiting time in queues. At the same time, through data analysis, the operator can better understand the travel habits of passengers and provide data support for future operational decisions. In addition, the security design of the system ensures the security of ticket transactions, prevents fraud and illegal transactions, and protects the interests of passengers and operators.

[0080] Different from the prior art, the present application discloses a gate-passing method, medium, equipment and ticket selling and checking system. By introducing a traffic pass that restricts communication according to the preset usage rules of the pass type, and by judging whether the traffic pass is valid to generate different pass codes, it is possible to flexibly switch between various configurable traffic passes and ordinary tickets, and achieve seamless connection between the ticket account and the user end, so that passengers can pass through the gate more conveniently and quickly when they need to pass through the gate, effectively improving the gate-passing efficiency, simplifying the gate-passing process for passengers, reducing the complexity of operation, and improving the ticket-card association. It can realize flexible management of different ticket types and meet the diverse travel needs of passengers. At the same time, in this way, only one account medium, that is, the pass code of the user end, can be used to automatically switch tickets and pass through the gate, without the need for additional intervention of relevant staff for ticket processing, so as to achieve seamless gate-passing, which is conducive to improving the smoothness and comfort of passengers passing through the gate. In addition, based on this application, operators can also automatically configure different types of transportation passes according to operational needs, flexibly respond to market changes, effectively improve the operational efficiency of rail transit, and reduce card production and operating costs.

[0081] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the storage medium embodiment, computer device embodiment and ticket sales and inspection system embodiment, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0082] In the several embodiments provided in this application, it should be understood that the disclosed methods, storage media, computer devices, and ticket sales and inspection systems can be implemented in other ways. For example, the ticket sales and inspection system embodiments described above are only illustrative, for example, the division of modules, units, or subsystems is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0083] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0084] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0085] The above descriptions are merely embodiments of the present application and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for passing through a gate, characterized in that: include: In response to receiving a gate pass request initiated by a ticket card account, detecting whether the transportation pass of the ticket card account is valid; In response to the transportation pass being in a valid state, sending transportation pass code data to a user terminal to allow the user terminal to generate a first pass code associated with the transportation pass based on the transportation pass code data; In response to the transportation pass being in an invalid state, sending the ordinary ticket card code data to the user terminal to allow the user terminal to generate a second pass code associated with the ordinary ticket card based on the ordinary ticket card code data; The traffic pass is restricted according to the preset usage rules of the corresponding pass type, and the first pass code and the second pass code are used to instruct the corresponding gate device to open the gate passage.

2. The gate-passing method according to claim 1, characterized in that: Each of the pass types corresponds to a different range of the preset usage rules; The preset usage rule range is determined based on at least one of a configurable effective date, a daily effective time, a maximum passable number of times, a daily passable number of times, a maximum passable mileage, and a daily passable mileage.

3. The gate-passing method according to claim 1, characterized in that: Before the method of detecting whether the traffic pass of the ticket account is valid in response to receiving the gate-passing request initiated by the ticket account, the method further includes: Receiving an account registration request initiated by the user terminal; Performing account configuration based on the account registration request to generate the ticket card account, and feeding back account information of the ticket card account to the user terminal; Receive a contract signing request initiated by the user terminal based on the account information, and establish contract signing information synchronization with the user terminal to activate the common ticket card associated with the ticket card account.

4. The gate-passing method according to claim 1, characterized in that: Before the method of detecting whether the traffic pass of the ticket account is valid in response to receiving the gate-passing request initiated by the ticket account, the method further includes: Receiving a pass generation request initiated by the user terminal, parsing the payment information and the corresponding pass type included in the pass generation request; In response to determining that the fare payable for the pass type corresponds to the payment amount of the payment information, the transportation pass associated with the fare card account is activated.

5. The gate-passing method according to claim 1, characterized in that: Before sending the traffic pass code data to the user terminal in response to the traffic pass being in a valid state, the method further includes: In response to determining that the transportation pass associated with the ticket account is in an activated state and usage of the transportation pass is within the preset usage rules, it is determined that the transportation pass is in a valid state.

6. The gate-passing method according to claim 1, characterized in that: After the method of detecting whether the traffic pass of the ticket account is valid in response to receiving the gate pass request initiated by the ticket account, the method further includes: Performing an anti-duplication check on the ticket card account to determine whether the ticket card account meets the single gate pass conditions; Verify the legitimacy of the ticket card account to determine whether the ticket card account meets the legal gate-passing conditions; In response to determining that the ticket card account satisfies the single gate-passing condition and the legal gate-passing condition, allowing the gate device to open a gate-passing channel after recognizing the first pass code or the second pass code; Among them, the legitimacy verification includes at least one of ticket card account field verification, pass credential verification, whitelist verification, signature data verification and entry status verification.

7. The gate-passing method according to claim 1, characterized in that: The ticket account is associated with the transportation pass and the ordinary ticket. When the transportation pass is valid, the priority of the transportation pass is greater than the priority of the ordinary ticket.

8. A storage medium having program data stored thereon, characterized in that: When the program data is executed by a processor, the steps of the gate passing method according to any one of claims 1 to 7 are implemented.

9. A computer device, characterized in that: The method comprises a processor and a memory connected to each other, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the gate-passing method as claimed in any one of claims 1 to 7 are implemented.

10. A ticket selling and checking system, characterized in that: The ticket sales and inspection system includes a ticketing subsystem, a user terminal, an entry site subsystem and an exit site subsystem; The entry site subsystem and the exit site subsystem are both deployed with at least one gate device supporting pass code recognition; The ticketing subsystem is communicatively connected with the site subsystem, the outbound site subsystem and the user terminal respectively, and the computer device as claimed in claim 9 is deployed in the ticketing subsystem.

Images