Heterogeneous joint ticket checking method and device, computer equipment and storage medium
By identifying and verifying multiple ticket systems, using the technology of safe isolation zones, the problems of data interoperability between railways and local rail transit ticketing systems are solved, and multiple ticket systems are verified on one ticket checking machine. Improve travel efficiency and system security.
Patent Information
- Application Number
- CN202411241909.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-05
- Publication Date
- 2024-12-03
AI Technical Summary
In the prior art, there are security risks and regulatory loopholes in data interoperability processing between the heterogeneous ticketing systems of railways and local rail transit ticketing systems, resulting in inefficient travel, complex operation, high operational costs, and inability to verify on a ticket machine. Multiple ticket systems.
By obtaining user ticket system verification requests, identifying the type of ticket system and sending it to the corresponding ticket system verification module, realizing ticket system identification and verification, adopting a secure isolation area to reduce the risk of horizontal attacks, supporting joint ticket inspections of multiple ticket systems, and opening Data channel, supporting railway electronic tickets and seat management.
It realizes the verification of multiple ticket systems on one ticket checking machine, improves travel efficiency, reduces operating costs, enhances system security, and improves passenger experience.
Smart Images

Figure CN119068563A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of ticket verification, and in particular, to a heterogeneous joint ticket checking method, apparatus, computer equipment and storage medium. Background Art
[0002] At present, it is necessary to make full use of the comparative advantages of multi-system rail transit, promote the "four-network integration" and integrated development of regional multi-level rail transit, and help build a strong transportation country. The ticketing systems and operating entities of local rail transit are different. Especially in the relatively closely connected railway trunk lines and local rail transit hubs, passengers expect to be able to achieve unified verification, information exchange and unified management of railway ticket systems and local ticket systems on one gate, so as to achieve "one ticket for all" and improve travel efficiency. Based on this, many metropolitan areas are actively promoting the research on the hardware and software compatibility of railway trunk lines and local rail transit ticket inspection systems, in order to achieve the sharing and sharing of entry and exit gates and channel space layout. However, the safety standards and regulatory requirements of railway and local rail transit ticketing systems are different. There are security risks and regulatory loopholes in data intercommunication processing between heterogeneous ticket inspection systems that need to be overcome, and the working mechanism of the security domain of heterogeneous ticket inspection systems needs to be studied.
[0003] In the related technology, due to the differences in ticketing systems, ticket types, passenger information management, etc. between railways and local rail transit systems, the current integrated transportation hub involves interconnection and interoperability between the two types of rail transit involving railways and local ticket systems. The technical solution is to set up separate ticket gates in the transfer area for segmented entry and exit. The existing railway gates complete the ticket entry and exit of the railway ticket system, and the gates of the local rail transit company complete the ticket entry and exit of the local ticket system. However, multiple ticket inspections are inefficient: inter-trip travel requires switching between different gates, which increases the complexity of interconnection, reduces the efficiency of transfer, and easily leads to congestion in the station. In addition, the operation is complicated and the passenger experience is not good: the two gates are set adjacent to each other. On the one hand, it is difficult for passengers to distinguish during use, resulting in wrong swipes. On the other hand, passengers need to perform multiple verifications and ticket inspections, which increases the complexity of operation and reduces the travel experience of passengers. At the same time, the operating costs of the two sets of equipment are high: while the investment cost of building two sets of equipment is high, the maintenance and management of the separately set railway gates and local rail transit gate systems require more manpower and material resources.
[0004] In the related technology, a physical combination of rail and subway gates has been introduced for passengers' step-by-step travel. The solution integrates the industrial control modules of the two systems in series in the same gate. The local system controls the gate through the railway industrial control equipment. Passengers can use railway train tickets, public transportation cards and local electronic ticketing systems on the same gate. However, since the data channel is not opened, the railway module is offline and passengers need to buy railway paper tickets at the station to take the train. However, the gate cannot support railway electronic tickets; passengers who choose the railway ticket system need to prepay in advance; and seat management is not supported. Summary of the invention
[0005] The embodiments of the present application provide a heterogeneous joint ticket checking method and apparatus, a computer device and a storage medium.
[0006] A first aspect of an embodiment of the present application provides a heterogeneous joint ticket checking method, comprising:
[0007] Obtain a user's ticket verification request, and send the user's ticket verification request to multiple preset ticket recognition modules;
[0008] When the preset ticket system identification module identifies the ticket system type in the user's ticket system verification request, the ticket system identification module that identifies the ticket system type is used as the target ticket system identification module, and the target ticket system identification module sends a ticket system identification success message to the non-target ticket system identification module, so that the non-target ticket system identification module stops working;
[0009] According to the ticket system type identified by the target ticket system identification module, the user ticket system verification request is sent to the ticket system verification module corresponding to the target ticket system identification module;
[0010] When the ticket system verification module determines that the ticket system in the user's ticket system verification request does not meet the preset requirements, it sends the user's ticket system verification pass information or the user's ticket system verification fail information.
[0011] In an optional embodiment of the present application, the step of sending the user ticket system verification request to a ticket system verification module corresponding to the target ticket system identification module includes:
[0012] In the case where the ticket system verification module corresponding to the target ticket system identification module is the first ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module;
[0013] When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module, and the first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, wherein the security level of the first ticket system verification module is higher than that of the second ticket system verification module.
[0014] In an optional embodiment of the present application, the first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, including:
[0015] The first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module via the security isolation zone, wherein the security isolation zone is set between the first ticket system verification module and the second ticket system verification module.
[0016] In an optional embodiment of the present application, when the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information includes:
[0017] In the case where the ticket system verification module is the first ticket system verification module, when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the first ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the target ticket system identification module;
[0018] When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, and when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the second ticket system verification module sends the user's ticket system verification pass information or the user's ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module.
[0019] In an optional embodiment of the present application, the second ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module, including:
[0020] The second ticket system verification module sends the user ticket system verification pass information or the user ticket system verification fail information to the security isolation area. After the user ticket system verification pass information or the user ticket system verification fail information is verified in the security isolation area, the user ticket system verification pass information or the user ticket system verification fail information is sent to the gate controller via the first ticket system verification module and the target ticket system identification module.
[0021] In an optional embodiment of the present application, when the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information includes:
[0022] Based on the correspondence between the ticket system type and the ticket system verification pass rule, the ticket system verification pass rule is determined according to the ticket system type in the current user ticket system verification request;
[0023] According to the ticket system verification pass rules of the ticket system in the current user ticket system verification request, determine whether the ticket system in the user ticket system verification request meets the preset requirements;
[0024] If the ticket system in the user ticket system verification request meets the preset requirements, send the user ticket system verification pass information;
[0025] If the ticket system in the user ticket system verification request does not meet the preset requirements, a user ticket system verification failure message is sent.
[0026] In an optional embodiment of the present application, the method further includes:
[0027] Obtain the number of tickets of all ticket types from the target start time to the target end time in real time;
[0028] When the number of tickets exceeds the preset threshold, determine whether the current time has reached the target end time;
[0029] If the current time has not reached the target end time, stop the step of obtaining the user ticket verification request.
[0030] A second aspect of the embodiment of the present application provides a heterogeneous joint ticket checking device, including:
[0031] An acquisition module, used to acquire a user's ticket system verification request and send the user's ticket system verification request to a plurality of preset ticket system recognition modules;
[0032] A ticket system identification module is used to, when identifying the ticket system type in the user's ticket system verification request, use the ticket system identification module that identifies the ticket system type as the target ticket system identification module, send ticket system identification success information to the non-target ticket system identification module, so that the non-target ticket system identification module stops working, and according to the ticket system type identified by the target ticket system identification module, send the user's ticket system verification request to the ticket system verification module corresponding to the target ticket system identification module;
[0033] The ticket system verification module is used to send user ticket system verification pass information or user ticket system verification fail information when determining whether the ticket system in the user ticket system verification request meets the preset requirements.
[0034] According to a third aspect of an embodiment of the present application, a computer device is provided, comprising: a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of any of the above heterogeneous joint ticket checking methods are implemented.
[0035] A fourth aspect of the embodiments of the present application provides a computer-readable storage medium on which a computer program is stored, characterized in that when the computer program is executed by a processor, the steps of the heterogeneous joint ticket checking method as described in any one of the above items are implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0037] Figure 1 A flow chart of a heterogeneous joint ticket checking method provided in one embodiment of the present application;
[0038] Figure 2 An application system structure diagram of a heterogeneous joint ticket checking method provided in one embodiment of the present application;
[0039] Figure 3 A working principle diagram of an application system of a heterogeneous joint ticket checking method provided in one embodiment of the present application;
[0040] Figure 4 Another working principle diagram of an application system of a heterogeneous joint ticket checking method provided by an embodiment of the present application;
[0041] Figure 5 A schematic diagram of the structure of a heterogeneous combined ticket checking device provided in one embodiment of the present application;
[0042] Figure 6 A schematic diagram of the computer device structure provided for one embodiment of the present application. DETAILED DESCRIPTION
[0043] In the process of implementing the present application, the inventor discovered that it is currently impossible to verify multiple ticket systems on one ticket checking machine.
[0044] In response to the above problems, a heterogeneous joint ticket checking method is provided in an embodiment of the present application, which obtains a user ticket system verification request and sends the user ticket system verification request to multiple preset ticket system identification modules; when the preset ticket system identification module identifies the ticket system type in the user ticket system verification request, the ticket system identification module that identifies the ticket system type is used as the target ticket system identification module, and the target ticket system identification module sends a ticket system identification success message to the non-target ticket system identification module, so that the non-target ticket system identification module stops working; according to the ticket system type identified by the target ticket system identification module, the user ticket system verification request is sent to the ticket system verification module corresponding to the target ticket system identification module; when the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, it sends the user ticket system verification pass message or the user ticket system verification fail message, so that multiple ticket systems can be verified on one ticket checking machine.
[0045] The solutions in the embodiments of the present application can be implemented using various computer languages, for example, the object-oriented programming language Java and the interpreted scripting language JavaScript.
[0046] In order to make the technical solutions and advantages in the embodiments of the present application more clearly understood, the exemplary embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than an exhaustive list of all the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.
[0047] See also Figure 1 The heterogeneous joint ticket checking method provided in the embodiment of the present application includes the following steps:
[0048] S1, obtain the user's ticket system verification request, and send the user's ticket system verification request to multiple preset ticket system recognition modules.
[0049] In an optional embodiment of the present application, the preset ticket system identification module includes but is not limited to a railway ticket identification module and a local ticket identification module.
[0050] S2. When the preset ticket system identification module identifies the ticket system type in the user's ticket verification request, the ticket system identification module that identifies the ticket system type is used as the target ticket system identification module. The target ticket system identification module sends a ticket system identification success message to the non-target ticket system identification module, causing the non-target ticket system identification module to stop working.
[0051] In an optional embodiment of the present application, the ticket types include railway tickets and local tickets, wherein railway tickets are tickets used for taking trunk railways or intercity railways, and local tickets are tickets used for suburban railways or subways.
[0052] S3, according to the ticket system type identified by the target ticket system identification module, sending the user ticket system verification request to the ticket system verification module corresponding to the target ticket system identification module.
[0053] In an optional embodiment of the present application, the step of sending the user ticket system verification request to a ticket system verification module corresponding to the target ticket system identification module includes:
[0054] In the case where the ticket system verification module corresponding to the target ticket system identification module is the first ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module;
[0055] When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module, and the first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, wherein the security level of the first ticket system verification module is higher than that of the second ticket system verification module.
[0056] In an optional embodiment of the present application, the first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, including:
[0057] The first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module via the security isolation zone, wherein the security isolation zone is set between the first ticket system verification module and the second ticket system verification module.
[0058] like Figure 2 and Figure 3 As shown, in the case where the ticket types include railway tickets and local tickets, the actual system architecture of the present application includes a jointly-established ticket checking terminal, a railway center passenger ticket network and a local ticketing system that are interconnected, wherein the jointly-established ticket checking terminal includes a railway ticket control module and a local ticket control module, the railway center passenger ticket network includes a railway ticket center and a security domain access area (external access area), the railway ticket center includes a first ticket system verification module, the local ticketing system includes a second ticket system verification module, the railway ticket control module is used to identify the railway ticket in the user's ticket system verification request, and the local ticket control module is used to identify the local ticket in the user's ticket system verification request.
[0059] In an optional embodiment of the present application, the security domain access area constructed in the railway center passenger ticket network is based on the concept of "no trust, always verify", and the different security networks are divided into multiple security domains. The isolation between security domains is achieved through network isolation technology to reduce the risk of lateral attacks. Low-level data access outside the higher-level railway ticketing network is regarded as high risk, and stricter network security is achieved through identity authentication, access control and other technologies. The security domain access area includes: firewalls, security gateways, security isolation and information exchange systems.
[0060] In this application, based on the research foundation of physical ticket checking combined terminals and the existing network and security planning of railway bureau-level and station-level ticket systems, in order to solve the problem of different security levels of railway ticket systems and local ticket systems and the data interconnection problem of combined ticket checking terminals, a local ticket card external access area is added to the railway bureau-level ticket network for secure access to the urban railway system, and firewalls, security gateways, security isolation and information exchange systems and other equipment are deployed in the external access area.
[0061] See also Figure 3 The station-level terminal area is divided into the railway business domain and the local business domain. After the passenger's ticket card is swiped through the gate, the card reader in the gate machine verifies the legality of the ticket card, and then pushes the railway ticket card data and the local ticket card data to their respective businesses for business processing; the railway business module is connected to the railway passenger ticket system of the railway central passenger ticket network to complete the real-name verification and seat application. After the verification is successful and the seat application is successful, the instruction is returned to the terminal railway business module to control the gate to open; the local ticket card business module is connected to the external access area of the railway central passenger ticket network through the railway passenger ticket system of the railway central passenger ticket network, and the real-name verification and ticket card and terminal data are pushed to the local ticketing system access domain through the external access area security channel. After completing the real-name verification, the instruction is returned to the terminal local business domain control module through the secure access area to control the gate to open.
[0062] In an optional embodiment of the present application, the ticket system type, the ticket system identification module and the ticket system verification module correspond to each other. When the ticket system type is a railway ticket, the ticket system identification module is a railway ticket identification module, and the ticket system verification module is a railway ticket verification module; when the ticket system type is a local ticket, the ticket system identification module is a local ticket identification module, and the ticket system verification module is a local ticket verification module.
[0063] S4. When the ticket system verification module determines that the ticket system in the user's ticket system verification request does not meet the preset requirements, it sends the user's ticket system verification pass information or the user's ticket system verification fail information.
[0064] In an optional embodiment of the present application, when the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information includes:
[0065] In the case where the ticket system verification module is the first ticket system verification module, when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the first ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the target ticket system identification module;
[0066] When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, and when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the second ticket system verification module sends the user's ticket system verification pass information or the user's ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module.
[0067] In an optional embodiment of the present application, the second ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module, including:
[0068] The second ticket system verification module sends the user ticket system verification pass information or the user ticket system verification fail information to the security isolation area. After the user ticket system verification pass information or the user ticket system verification fail information is verified in the security isolation area, the user ticket system verification pass information or the user ticket system verification fail information is sent to the gate controller via the first ticket system verification module and the target ticket system identification module.
[0069] In an optional embodiment of the present application, when the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information includes:
[0070] Based on the correspondence between the ticket system type and the ticket system verification pass rule, the ticket system verification pass rule is determined according to the ticket system type in the current user ticket system verification request;
[0071] According to the ticket system verification pass rules of the ticket system in the current user ticket system verification request, determine whether the ticket system in the user ticket system verification request meets the preset requirements;
[0072] If the ticket system in the user ticket system verification request meets the preset requirements, send the user ticket system verification pass information;
[0073] If the ticket system in the user ticket system verification request does not meet the preset requirements, a user ticket system verification failure message is sent.
[0074] In an optional embodiment of the present application, the method further includes:
[0075] After sending the user ticket verification pass information or the user ticket verification fail information, the non-target ticket system identification module is controlled to start working.
[0076] In an optional embodiment of the present application, the method further includes:
[0077] Obtain the number of tickets of all ticket types from the target start time to the target end time in real time;
[0078] When the number of tickets exceeds the preset threshold, determine whether the current time has reached the target end time;
[0079] If the current time has not reached the target end time, stop the step of obtaining the user ticket verification request.
[0080] See also Figure 4 Based on the research foundation of physical ticket inspection terminal, the start and stop inspection command interaction is realized between the railway ticket control module and the local ticket control module through RS232 serial communication, forming a multi-standard ticket inspection passenger flow control method. In order to solve the problem of train overcrowding control, the railway ticket inspection system controls the total ticket quota according to the train seats. When the railway ticket control module in the ticket inspection terminal receives the stop inspection command issued by the railway ticketing system, the railway ticket inspection function is stopped and the stop inspection command is sent to the local ticket control module. The local ticket module stops swiping the gate to inspect tickets, and finally realizes the joint ticket inspection passenger flow control of different standard tickets.
[0081] This application does not need to change the existing architecture of the two ticketing systems. On the basis of jointly setting up ticket checking terminals, the ticket checking terminal software communication plus the background system data sharing mode realizes the integration of multi-standard ticket checking services. It has both the connection to the railway passenger ticket center system and the connection to the local rail transit ticketing system on one gate machine. The background system business processing does not interfere with each other, and all tickets of each system can be supported. In order to solve the difficult problems of different security standards of the two systems and the difficult problems of asynchronous start, stop and inspection time of the two systems, a local rail transit ticketing system access domain is added to the railway passenger ticket system security domain. The local ticket business data is connected with the local rail transit ticket checking system and the station system through the railway passenger ticket system security boundary to complete the business processing. At the same time, the railway ticketing system obtains the start, stop and inspection plan data in real time, and realizes unified passenger flow control through the security domain and the exchange of start, stop and inspection commands with the local ticket system.
[0082] This application focuses on the difficult issues of heterogeneous ticket checking transaction data interaction and different system security levels. It divides security domains in the railway ticketing system and adds secure access areas to verify and be compatible with data access from lower-level or other ticketing systems of the same level, breaking through data security barriers and building a cross-domain service connectivity method between layered ticketing system networks. It also builds the interaction of start, stop and check commands between the railway ticket control module and the local ticket control module based on the joint ticket checking terminal, forming a multi-standard ticket joint ticket checking passenger flow control method.
[0083] It should be understood that, although the various steps in the flow chart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0084] See also Figure 5 One embodiment of the present application provides a heterogeneous joint ticket checking device, comprising:
[0085] The acquisition module 11 is used to acquire the user's ticket system verification request and send the user's ticket system verification request to multiple preset ticket system recognition modules;
[0086] The ticket system identification module 12 is used to, when identifying the ticket system type in the user's ticket system verification request, use the ticket system identification module that identifies the ticket system type as the target ticket system identification module, send ticket system identification success information to the non-target ticket system identification module, so that the non-target ticket system identification module stops working, and according to the ticket system type identified by the target ticket system identification module, send the user's ticket system verification request to the ticket system verification module corresponding to the target ticket system identification module;
[0087] The ticket system verification module 13 is used to send user ticket system verification pass information or user ticket system verification fail information when determining whether the ticket system in the user ticket system verification request meets the preset requirements.
[0088] For the specific limitations of the above-mentioned heterogeneous joint ticket checking device, please refer to the limitations of the heterogeneous joint ticket checking method above, which will not be repeated here. Each module in the above-mentioned heterogeneous joint ticket checking device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0089] In one embodiment, a computer device is provided, the internal structure diagram of which can be as follows: Figure 6 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a heterogeneous joint ticket checking method as described above is implemented. It includes: a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, any step in the heterogeneous joint ticket checking method as described above is implemented.
[0090] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, any step in the above heterogeneous joint ticket checking method can be implemented.
[0091] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0092] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0093] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0094] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0095] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.
[0096] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A heterogeneous joint ticket checking method, characterized in that: include: Obtain a user's ticket verification request, and send the user's ticket verification request to multiple preset ticket recognition modules; When the preset ticket system identification module identifies the ticket system type in the user's ticket system verification request, the ticket system identification module that identifies the ticket system type is used as the target ticket system identification module, and the target ticket system identification module sends a ticket system identification success message to the non-target ticket system identification module, so that the non-target ticket system identification module stops working; According to the ticket system type identified by the target ticket system identification module, the user ticket system verification request is sent to the ticket system verification module corresponding to the target ticket system identification module; When the ticket system verification module determines that the ticket system in the user's ticket system verification request does not meet the preset requirements, it sends the user's ticket system verification pass information or the user's ticket system verification fail information.
2. The method according to claim 1, characterized in that The step of sending the user ticket system verification request to the ticket system verification module corresponding to the target ticket system identification module includes: In the case where the ticket system verification module corresponding to the target ticket system identification module is the first ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module; When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, the target ticket system identification module sends the user ticket system verification request to the first ticket system verification module connected to the target ticket system identification module, and the first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, wherein the security level of the first ticket system verification module is higher than that of the second ticket system verification module.
3. The method according to claim 2, characterized in that The first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module, including: The first ticket system verification module sends the user ticket system verification request to the second ticket system verification module connected to the first ticket system verification module via the security isolation zone, wherein the security isolation zone is set between the first ticket system verification module and the second ticket system verification module.
4. The method according to claim 2, characterized in that: When the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information, including: In the case where the ticket system verification module is the first ticket system verification module, when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the first ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the target ticket system identification module; When the ticket system verification module corresponding to the target ticket system identification module is the second ticket system verification module, and when the first ticket system verification module determines whether the ticket system in the user's ticket system verification request meets the preset requirements, the second ticket system verification module sends the user's ticket system verification pass information or the user's ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module.
5. The method according to claim 4, characterized in that The second ticket system verification module sends user ticket system verification pass information or user ticket system verification fail information to the gate controller via the first ticket system verification module and the target ticket system identification module, including: The second ticket system verification module sends the user ticket system verification pass information or the user ticket system verification fail information to the security isolation area. After the user ticket system verification pass information or the user ticket system verification fail information is verified in the security isolation area, the user ticket system verification pass information or the user ticket system verification fail information is sent to the gate controller via the first ticket system verification module and the target ticket system identification module.
6. The method according to claim 1, characterized in that When the ticket system verification module determines that the ticket system in the user ticket system verification request does not meet the preset requirements, sending user ticket system verification pass information or user ticket system verification fail information, including: Based on the correspondence between the ticket system type and the ticket system verification pass rule, the ticket system verification pass rule is determined according to the ticket system type in the current user ticket system verification request; According to the ticket system verification pass rules of the ticket system in the current user ticket system verification request, determine whether the ticket system in the user ticket system verification request meets the preset requirements; If the ticket system in the user ticket system verification request meets the preset requirements, send the user ticket system verification pass information; If the ticket system in the user ticket system verification request does not meet the preset requirements, a user ticket system verification failure message is sent.
7. The method according to claim 1, characterized in that The method further comprises: Obtain the number of tickets of all ticket types from the target start time to the target end time in real time; When the number of tickets exceeds the preset threshold, determine whether the current time has reached the target end time; If the current time has not reached the target end time, stop the step of obtaining the user ticket verification request.
8. A heterogeneous joint ticket checking device, characterized in that: include: An acquisition module, used to acquire a user's ticket system verification request and send the user's ticket system verification request to a plurality of preset ticket system recognition modules; A ticket system identification module is used to, when identifying the ticket system type in the user's ticket system verification request, use the ticket system identification module that identifies the ticket system type as the target ticket system identification module, send ticket system identification success information to the non-target ticket system identification module, so that the non-target ticket system identification module stops working, and according to the ticket system type identified by the target ticket system identification module, send the user's ticket system verification request to the ticket system verification module corresponding to the target ticket system identification module; The ticket system verification module is used to send user ticket system verification pass information or user ticket system verification fail information when determining whether the ticket system in the user ticket system verification request meets the preset requirements.
9. A computer device comprising: The method comprises a memory and a processor, wherein the memory stores a computer program, and is characterized in that the processor implements the steps of the heterogeneous joint ticket checking method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the heterogeneous joint ticket checking method according to any one of claims 1 to 7 are implemented.
