Networked ticketing system and method of interaction of a networked ticketing system

Abstract

The application discloses a kind of networking ticketing system and the interactive method of networking ticketing system, the system includes ticket information acquisition module, ticket information cleaning module, ticket information configuration module and ticketing module, by obtaining and cleaning ticket information, obtain cleaning data, according to configuration information binding cleaning data, to generate ticket information, and by ticketing module establishes the association of ticket information and passenger information.The application obtains the ticket information of traditional station service system and cloud station service system, cleans ticket information and binds configuration information, to adapt to the ticketing situation corresponding to different stations, finally, according to the ticketing instruction received by ticketing module, ticket information is associated with passenger information, which reduces the cost of passenger transport ticketing system, improves stability, and effectively supervises the whole area station, at the same time, improves the passenger upgrade convenience, and improves the passenger ticketing experience.

Description

Technical Field

[0001] This invention relates to the field of passenger transport technology, and in particular to a networked ticketing system and an interactive method for the networked ticketing system. Background Technology

[0002] With railways, airplanes, and other modes of transportation already offering online ticketing, road passenger transport companies, also within the transportation sector, are facing pressure to implement online ticketing. To meet passenger demand, traditional stations and transport companies are actively exploring single-station versions of online ticketing that connect directly to the station's management system (deployed in the station's local computer room), allowing users to purchase tickets via the station's official WeChat account. However, this method and deployment of online ticketing presents the following problems:

[0003] (1) Due to limitations in hardware conditions and maintenance capabilities, the station's local computer room cannot provide a stable 24 / 7 ticketing service;

[0004] (2) Each station independently builds its own online ticketing system, so users can only buy tickets for routes departing from these stations. For the return trip or if they need to book a route departing from other stations, they need to follow the official accounts of those stations, which results in a very poor user experience.

[0005] (3) The lack of coordination among stations in the construction of their own online ticketing systems has resulted in a lack of unified interface standards and data specifications for each station's own online ticketing systems. This makes it impossible to sell tickets across platforms or upload data to the regulatory platform in accordance with standard data specifications, making it difficult for regulatory agencies to accurately supervise and analyze the development of the industry.

[0006] (4) Due to the reasons mentioned above, such as the independent construction of each station and the lack of uniform standards, when the stations are integrated and the area needs to be connected, the system needs to be rebuilt according to the new rules, resulting in redundant construction and new costs.

[0007] (5) When new industry standards emerge, the existing online ticketing systems of each station struggle to respond quickly, and some have completely lost their ability to iterate and upgrade, causing the new standards to be slow to be implemented (e.g., electronic tickets). Therefore, how to reduce the cost of passenger ticketing systems, improve their stability, effectively supervise all stations in the region, improve the convenience of passenger upgrades, and enhance the passenger ticketing experience is a technical problem that urgently needs to be solved.

[0008] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0009] The main objective of this invention is to provide a networked ticketing system and an interaction method for the networked ticketing system, aiming to solve the technical problems of current passenger ticketing systems, such as being independent, having high operating costs, poor stability, being difficult to supervise, lacking convenience, and providing a poor ticket purchasing experience for passengers.

[0010] To achieve the above objectives, the present invention provides a networked ticketing system, the networked ticketing system comprising:

[0011] The ticketing information acquisition module is used to receive the first ticketing information provided by the cloud station management system and the second ticketing information collected by the front-end system from the corresponding station management system;

[0012] The ticketing information cleaning module is used to clean the first ticketing information and the second ticketing information.

[0013] The ticketing information configuration module is used to obtain the first configuration information corresponding to the cloud station management system and the second configuration information corresponding to the station management system of the front-end system, and bind the first configuration information with the first ticketing information, and bind the second configuration information with the second ticketing information;

[0014] The ticketing module is used to receive ticket purchase instructions, match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and establish the association between the first ticketing information or second ticketing information and passenger information.

[0015] Optionally, the first configuration information and the second configuration information include station basic data, station role data, permission data, scheduling rule data, transmission encryption data, data synchronization rules, sales rules, and payment data.

[0016] Optionally, the online ticketing system and the front-end system use a symmetric encryption algorithm to transmit data.

[0017] Optionally, the online ticketing system connects to at least one supplier system; wherein the supplier system, station administration system, and cloud station administration system synchronize data using timed synchronization, full synchronization, or hotspot synchronization.

[0018] Optionally, the online ticketing system further includes a business information configuration module, which is used to configure the ticket association information of the first ticket information and the second ticket information, and to configure the associated product information of the first ticket information and the second ticket information according to the product configuration instructions.

[0019] Optionally, the ticketing-related information may include ticket type, identification document, electronic ticket, or prohibited sales scope.

[0020] Optionally, the associated product information includes associated insurance information, associated coupon information, associated pick-up and drop-off service information, or associated product information.

[0021] Optionally, the ticketing module includes:

[0022] The online ticketing unit is used to obtain the passenger's ticket purchase instruction to access the cloud station service system, and match the ticket purchase instruction with the corresponding first ticketing information or second ticketing information, and establish the ticket purchase information that associates the first ticketing information or second ticketing information with the passenger information;

[0023] The station and offline ticketing unit is used to obtain the ticket purchase instructions from passengers accessing the station service system or offline ticketing equipment, and to match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and to establish the association between the first ticketing information or second ticketing information and passenger information.

[0024] The ticketing unit is used to obtain ticket purchase instructions from a third-party ticketing system connected to the online ticketing system, match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and establish the association between the first ticketing information or second ticketing information and passenger information.

[0025] Optionally, the online ticketing system also includes an online ticketing distribution module, which is used to send the cleaned and configured first ticketing information and second ticketing information to a third-party ticketing system, so that the third-party ticketing system can perform ticket display, query and reservation tasks based on the first ticketing information and second ticketing information.

[0026] Optionally, the online ticketing system further includes a ticketing traffic distribution module. The ticketing traffic distribution module is used to send the ticketing instruction to the corresponding third-party ticketing system when it receives the ticketing instruction from the offline ticketing device, and to match the ticketing instruction with corresponding first ticketing information or second ticketing information, and establish the ticketing information that associates the first ticketing information or second ticketing information with passenger information.

[0027] Furthermore, to achieve the above objectives, the present invention also provides an interaction method for an online ticketing system, the interaction method comprising the following steps:

[0028] The ticketing information acquisition module receives the first ticketing information provided by the cloud station administration system and the second ticketing information collected by the front-end system from the corresponding station administration system.

[0029] The ticketing information cleaning module cleans the first and second ticketing information.

[0030] The ticketing information configuration module obtains the first configuration information corresponding to the cloud station management system and the second configuration information corresponding to the station management system of the front-end system, and binds the first configuration information with the first ticketing information and the second configuration information with the second ticketing information.

[0031] The ticketing module receives ticket purchase instructions, matches the corresponding first or second ticketing information to the ticket purchase instructions, and establishes an association between the first or second ticketing information and passenger information.

[0032] This invention proposes a networked ticketing system and its interaction method. The system includes a ticketing information acquisition module, a ticketing information cleaning module, a ticketing information configuration module, and a ticketing module. By acquiring and cleaning ticketing information to obtain cleaned data, and binding the cleaned data according to configuration information, ticketing information is generated. The ticketing module then establishes a link between the ticketing information and passenger information. This invention acquires ticketing information from traditional station management systems and cloud station management systems, cleans the ticketing information, and binds it to configuration information to adapt to different station ticketing scenarios. Finally, the ticketing module associates the ticketing information with passenger information based on received purchase instructions. This reduces the cost of the passenger ticketing system, improves stability, and enables effective monitoring of stations across the entire region. Simultaneously, it enhances the convenience of passenger transport upgrades and improves the passenger ticketing experience. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the structure of the online ticketing system in an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram illustrating the principle of ticket information acquisition in an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram illustrating the principle of ticket data cleaning in an embodiment of the present invention;

[0036] Figure 4 This is a schematic diagram illustrating the principle of ticketing service synchronization in an embodiment of the present invention;

[0037] Figure 5 This is a schematic diagram illustrating the principle of business information configuration in an embodiment of the present invention;

[0038] Figure 6 This is a schematic diagram illustrating the principle of ticket sales traffic distribution in an embodiment of the present invention;

[0039] Figure 7 This is a flowchart illustrating the interaction method of the online ticketing system in an embodiment of the present invention.

[0040] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0041] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0042] With railways, airplanes, and other modes of transportation already offering online ticketing, road passenger transport companies, also within the transportation sector, are facing pressure to implement online ticketing. To meet passenger demand, traditional stations and transport companies are actively exploring single-station versions of online ticketing that connect directly to the station's management system (deployed in the station's local computer room), allowing users to purchase tickets via the station's official WeChat account. However, this method and deployment of online ticketing presents the following problems:

[0043] (1) Due to limitations in hardware conditions and maintenance capabilities, the station's local computer room cannot provide a stable 24 / 7 ticketing service;

[0044] (2) Each station independently builds its own online ticketing system, so users can only buy tickets for routes departing from these stations. For the return trip or if they need to book a route departing from other stations, they need to follow the official accounts of those stations, which results in a very poor user experience.

[0045] (3) The lack of coordination among stations in the construction of their own online ticketing systems has resulted in a lack of unified interface standards and data specifications for each station's own online ticketing systems. This makes it impossible to sell tickets across platforms or upload data to the regulatory platform in accordance with standard data specifications, making it difficult for regulatory agencies to accurately supervise and analyze the development of the industry.

[0046] (4) Due to the reasons mentioned above, such as the independent construction of each station and the lack of uniform standards, when the stations are integrated and the area needs to be connected, the system needs to be rebuilt according to the new rules, resulting in redundant construction and new costs.

[0047] (5) When new industry standards emerge, the existing online ticketing systems of each station struggle to respond quickly, and some have completely lost their ability to iterate and upgrade, causing the new standards to be slow to be implemented (e.g., the Ministry of Transport's electronic ticketing system). Therefore, how to reduce the cost of passenger ticketing systems, improve their stability, effectively supervise stations across the region, and enhance the convenience of passenger upgrades and improve the passenger ticketing experience is a technical problem that urgently needs to be solved.

[0048] To address this issue, various embodiments of the online ticketing system and its interaction method are proposed in this invention. The online ticketing system provided by this invention acquires ticketing information from traditional station management systems and cloud station management systems, cleans the ticketing information, and binds it with configuration information to adapt to different station ticketing scenarios. Finally, the ticketing module associates the ticketing information with passenger information based on received purchase instructions, reducing the cost of the passenger ticketing system, improving stability, and enabling effective monitoring of stations across the entire region. Simultaneously, it enhances the convenience of passenger transport upgrades and improves the passenger ticketing experience.

[0049] This invention provides an online ticketing system, referring to... Figure 1 , Figure 1 This is a schematic diagram of an embodiment of the online ticketing system of the present invention.

[0050] In this embodiment, the online ticketing system includes a ticketing information acquisition module, a ticketing information cleaning module, a ticketing information configuration module, and a ticketing module.

[0051] It should be noted that, in this embodiment, the online ticketing system includes an application layer, a network layer, a gateway, an interface layer, a business layer, a basic layer, a data layer, a data middleware platform, station front-end services, and system monitoring, etc.

[0052] The application layer includes mobile apps, mini-programs, H5 pages, PC stations, smart waiting hall electronic signs, cabinet-type self-service machines, thin-screen self-service machines, small-screen self-service machines, window ticketing terminals, and other ticketing terminals that can interact with the networked ticketing system.

[0053] The aforementioned ticketing terminals request and convert data through a gateway. The gateway distributes the requests to the business layer, which then accesses either the business middle platform or the supply layer based on the scenario. The business middle platform provides common scenario functions and returns data to the business layer, while the supply layer system bridges the station management system and cloud-based station systems, returning data to the business layer. The business layer collaborates with the data layer to complete data encapsulation and storage. The stored data can be subsequently used by the data middle platform to output reports such as operational visualization, and can also be uploaded to the road passenger transport supervision platform to assist relevant units such as transportation administration and public security in real-time supervision, statistical analysis, and other requirements.

[0054] The system monitoring module monitors all relevant systems. Depending on the system type, the monitoring method varies. For example, the gateway is monitored by parsing network operating parameters; the business service layer is monitored through read / write test interfaces; and the front-end module is monitored by sending back status pings.

[0055] Specifically, such as Figure 2 As shown, the ticketing information acquisition module is used to receive first ticketing information provided by the cloud station management system and second ticketing information collected by the front-end system from the corresponding station management system; the ticketing information cleaning module is used to clean the first ticketing information and the second ticketing information; the ticketing information configuration module is used to acquire first configuration information corresponding to the cloud station management system and second configuration information corresponding to the front-end system from the corresponding station management system, and bind the first configuration information with the first ticketing information, and bind the second configuration information with the second ticketing information; the ticketing module is used to receive ticket purchase instructions, match the corresponding first ticketing information or second ticketing information for the ticket purchase instructions, and establish the association relationship between the first ticketing information or second ticketing information and passenger information.

[0056] As is easily understood, the first and second configuration information include station basic data, station role data, permission data, scheduling rule data, transmission encryption data, data synchronization rules, sales rules, and payment data.

[0057] Specifically, the ticketing information acquisition module is used to integrate ticketing information from various scattered stations, including traditional offline stations and cloud-based stations.

[0058] It's important to clarify that traditional offline bus stations involve vehicles undergoing security checks and baggage screenings before boarding and then traveling to another station. Cloud-based bus stations, on the other hand, represent a decentralized passenger transport model with a cloud-based platform. This model features at least one boarding point and at least one alighting point. Vehicles undergo security checks and register at the vehicle checkpoints. Upon receiving a departure order, the vehicle proceeds to at least one boarding point to wait for passengers and to at least one alighting point for disembarkation. By replacing traditional large bus stations with smart waiting halls at multiple boarding and alighting points, and by supplementing essential security checks with vehicle and baggage screening equipment, this model addresses the problems of traditional road passenger transport stations serving only passengers on their own routes, resulting in low utilization rates of facilities, information systems, and hardware, low production efficiency, and significant waste of social resources.

[0059] The front-end system serves as the data transmission middleware between traditional stations and the online ticketing system. It connects externally to self-service ticket machines, integrated ticket windows, parcel delivery systems, and online ticketing centers. The cloud-based station directly interfaces with the online ticketing system through the distribution interface of the cloud station affairs SaaS platform. The combination of the front-end system and the cloud station affairs SaaS platform distribution interface integrates ticketing information from both traditional and cloud-based stations into the online ticketing system.

[0060] like Figure 3 As shown, after obtaining the first and second ticketing information, considering that the ticketing data structure of each offline station and the cloud station does not have a unified standard, the ticketing information that needs to be integrated into the online ticketing system through the ticketing information cleaning module needs to undergo data cleaning to standardize its data structure so that it can be sold using the same standard.

[0061] The ticketing service module in the online ticketing system provides standard schedule and transaction service interfaces to the outside world; the ticketing service pulls schedule data from the station administration system, third-party technical service provider interfaces, and cloud station administration system, converts it into standard schedule data for sale.

[0062] In some embodiments, the online ticketing system and the front-end system use a symmetric encryption algorithm to transmit data.

[0063] As is easily understood, the online ticketing API interface service uses symmetric encryption to ensure the security of data transmission; the online ticketing platform service and web client use symmetric encryption to ensure the security of data transmission.

[0064] In another embodiment, such as Figure 4 As shown, the online ticketing system connects to at least one supplier system; wherein, the supplier system, station administration system, and cloud station administration system synchronize data using timed synchronization, full synchronization, or hotspot synchronization.

[0065] As is easily understood, the bus ticket online ticketing service uses timed synchronization, full synchronization, and hotspot synchronization to keep the data fresh when synchronizing data with the station management system, technology suppliers, and cloud station management system; OTAs, BAT companies, ticket agents, and other partners use customized synchronization strategies and methods to synchronize the latest data with the bus ticket service.

[0066] Furthermore, such as Figure 5 As shown, the online ticketing system also includes a business information configuration module, which is used to configure the ticket association information of the first ticket information and the second ticket information, and to configure the associated product information of the first ticket information and the second ticket information according to the product configuration instructions.

[0067] As is easily understood, ticketing-related information includes ticket type, identification document, e-ticket, or prohibited items. Related product information includes related insurance information, related coupon information, related transportation service information, or related merchandise information.

[0068] The business information configuration module manages the business rules for bus tickets, including bus tickets and bundled products, and outputs information on bus ticket products and other value-added products available for users to order. After cleaning, the bus schedules and routes need to be categorized by departure station, and then the supported ticket types, certificates, e-tickets, and prohibited items for each departure station are configured and managed. In addition to bus tickets, a series of value-added products can be configured for bus tickets, allowing users to purchase other value-added products while ordering bus tickets and then combine the payment for the entire order.

[0069] Furthermore, the ticketing module includes online ticketing units, station and offline ticketing units, and ticket agency units.

[0070] It should be noted that the ticketing module's sales models mainly include online direct sales, ticket sales at stations and offline smart ticket vending / collection terminals, and distribution through agency channels. The business process for all three models is the same: inquiry -> ticket locking -> payment -> ticket purchase -> ticket collection or refund. Specifically:

[0071] (1) Inquiry: Users can inquire about train schedules by departure city / station and arrival city / station. The schedule information includes train type, departure time, price, available tickets, train type, etc. The pre-sale period is generally about 5 days on non-holidays and about 15 days on holidays.

[0072] (2) Ticket locking: After selecting a specific train or bus, the user enters passenger information, including name, ID type, ID number, mobile phone number, etc. After clicking submit, the ticketing center locks the seat information for the user. Generally, the seat is locked for 10 minutes. After this time, the seat is released for other people to purchase.

[0073] (3) Payment: During the ticket lock-in period, users can make online payments through WeChat Pay, Alipay, UnionPay, etc. (some smart ticketing terminals at some stations in Shanghai support cash payments).

[0074] (4) Ticket purchase: After the ticketing center system detects that the user has paid, it immediately requests the station administration system to purchase the ticket for the user (changing the ticket from the locked state to the issued state).

[0075] (5) Ticket collection or refund: After successful purchase, users can collect their paper tickets or electronic tickets through various smart ticketing terminals at stations or through the user's app. Refunds can also be processed through station windows or online clients. Station windows will refund in cash, while online customers will receive a refund via the original payment method.

[0076] Specifically, the online ticketing unit is used to obtain ticket purchase instructions from passengers accessing the cloud station management system, and match the ticket purchase instructions with corresponding first or second ticket information, establishing a relationship between the first or second ticket information and passenger information; the station and offline ticketing unit is used to obtain ticket purchase instructions from passengers accessing the station management system or offline ticketing devices, and match the ticket purchase instructions with corresponding first or second ticket information, establishing a relationship between the first or second ticket information and passenger information; the agency ticketing unit is used to obtain ticket purchase instructions from third-party agency ticketing systems connected to the online ticketing system, and match the ticket purchase instructions with corresponding first or second ticket information, establishing a relationship between the first or second ticket information and passenger information. Wherein:

[0077] (1) Online direct sales matrix, PC, mini program, APP and H5 are self-operated independent ticketing terminals, providing complete bus ticket sales, collection and refund services; relying on the public platform of BAT, it is integrated into the travel service of urban services; a diversion method during peak hours, users scan the code and go through the simple online ticket purchase process, which reduces the queuing pressure at station windows while converting offline traffic to online.

[0078] (2) Station and offline intelligent ticket sales / collection terminal matrix, smart waiting hall self-service machines: For cloud-based stations, self-service ticket terminals are moved into the smart waiting hall to enable the smart waiting hall to have on-site ticket sales capabilities; cabinet-type self-service machines, thin-screen self-service machines, and small-screen self-service machines: deployed on the site of traditional offline stations, the ticket purchase process is basically the same as the online client, which is used to relieve the pressure of window ticket sales; window ticket sales tablets and window payment boxes: through these two devices, the station windows have the ability to make mobile payments; at the same time, the window traffic has the possibility of secondary distribution.

[0079] After purchasing tickets through various online direct-sale ticketing terminals and ticket agents, users can print paper tickets or paper electronic ticket vouchers through the aforementioned smart ticketing / collection terminals.

[0080] (3) Distribution through agency channels: For online agency channels, this mainly includes OTA agency channels and BAT agency channels. The business processes of OTA and BAT agency channels are basically the same as those of online direct ticket sales, mainly including inquiry -> ticket locking -> ticket purchase -> ticket refund -> reconciliation. Before opening sales permissions, agency channels need to prepay a portion of the ticket price, which is called a prepayment. After each ticket is sold, the agency channel will deduct the ticket price from the prepayment. When the prepayment is insufficient, the system will close the agency channel's sales permissions, and the prepayment must be paid again before sales can continue. For offline agency channels, this mainly consists of traditional ticket outlets and supermarkets in transportation hubs. The biggest difference between this type of agency channel and other agency channels is that paper tickets can be printed. The company will equip each outlet of this type of channel with a printer and ticket receipts. After successful printing, users can use this ticket to board the train at the station.

[0081] The online ticketing system also includes an online ticketing distribution module, which is used to send the cleaned and configured first ticketing information and second ticketing information to a third-party ticketing system so that the third-party ticketing system can perform ticket display, query and reservation tasks based on the first ticketing information and second ticketing information.

[0082] Furthermore, the online ticketing system also includes a ticketing traffic distribution module. When the ticketing traffic distribution module receives a ticketing instruction from an offline ticketing device, it sends the ticketing instruction to the corresponding third-party ticketing system and matches the ticketing instruction with corresponding first ticketing information or second ticketing information, establishing a ticketing information association between the first ticketing information or second ticketing information and passenger information.

[0083] Easy to understand, such as Figure 6As shown, different traffic receiving channels are pre-configured with sorting, supported payment methods, and receiving rules. When users purchase tickets using smart ticketing terminals in stations and other offline scenarios, the smart ticketing terminals can convert this offline ticketing behavior into online orders. The traffic distribution system determines the current first-priority receiving channel based on the user's selected payment method and the pre-configured receiving rules.

[0084] The specific business operation process is as follows:

[0085] (1) In accordance with the contractual agreements with each traffic acquisition channel partner, daily minimum and daily volume limits are set for different regions and payment methods in the traffic acquisition channel management;

[0086] (2) Configure traffic acceptance rules for each traffic acceptance channel in traffic acceptance channel management (by restricting the peak, trough, time period and other dimensions to make the traffic reach the daily minimum and daily limit smoothly and evenly).

[0087] (3) Set the target traffic receiving channel range for the smart ticketing terminal;

[0088] (4) When a user purchases a ticket on a smart ticketing terminal, the system determines which traffic receiving channel is the first priority based on the payment method selected by the user, the target traffic receiving channel of the machine, and the minimum and maximum traffic limits and traffic receiving rules of the corresponding channel. Then, the system pushes the order to the corresponding traffic receiving channel and requests the payment QR code.

[0089] (5) Users scan the QR code on the smart ticketing terminal to jump to the ticketing terminal of the corresponding channel to complete the payment. At this step, the distribution of traffic has been realized (OTA / BAT obtains the information flow and capital flow that come with the order, as well as a certain proportion of new users).

[0090] (6) After the intelligent ticketing terminal detects that the user has completed payment in the corresponding traffic receiving channel, it randomly prints a ticket or boarding pass.

[0091] At this point, after the bus tickets are sold through the above methods, the online ticketing system will synchronize the ticket sales data to each station, and the station will organize transportation capacity to fulfill the contract service; at the same time, the online ticketing system will upload the bus ticket details to the clearing and settlement system to complete the subsequent reconciliation -> settlement -> payment operation.

[0092] This embodiment provides a networked ticketing system and its interaction method. The system includes a ticketing information acquisition module, a ticketing information cleaning module, a ticketing information configuration module, and a ticketing module. By acquiring and cleaning ticketing information to obtain cleaned data, and binding the cleaned data according to configuration information, ticketing information is generated. The ticketing module then establishes a correlation between the ticketing information and passenger information. This invention acquires ticketing information from traditional station management systems and cloud station management systems, cleans the ticketing information, and binds it to configuration information to adapt to different station ticketing scenarios. Finally, the ticketing module associates the ticketing information with passenger information based on received purchase instructions. This reduces the cost of the passenger ticketing system, improves stability, and provides effective monitoring of stations across the entire region. Simultaneously, it enhances the convenience of passenger transport upgrades and improves the passenger ticketing experience.

[0093] For ease of understanding, please refer to Figure 7 , Figure 7 This is a flowchart illustrating an embodiment of the interactive method of the online ticketing system of the present invention. Based on... Figure 1 The illustrated embodiment of the online ticketing system proposes an embodiment of the interaction method for the online ticketing system, as detailed below:

[0094] like Figure 7 As shown in the embodiment of the present invention, the interaction method of the online ticketing system includes the following steps:

[0095] S100 receives the first ticketing information provided by the cloud station management system and the second ticketing information collected by the front-end system from the corresponding station management system through the ticketing information acquisition module;

[0096] S200, the ticketing information cleaning module cleans the first ticketing information and the second ticketing information.

[0097] S300: The ticketing information configuration module obtains the first configuration information corresponding to the cloud station management system and the second configuration information corresponding to the station management system of the front-end system, and binds the first configuration information with the first ticketing information and binds the second configuration information with the second ticketing information.

[0098] S400 receives a ticket purchase instruction through the ticketing module, matches the ticket purchase instruction with corresponding first ticketing information or second ticketing information, and establishes an association between the first ticketing information or second ticketing information and passenger information.

[0099] Other embodiments or specific implementations of the interaction method of the online ticketing system of the present invention can be referred to the embodiments of the above-mentioned online ticketing systems, and will not be repeated here.

[0100] Furthermore, embodiments of the present invention also propose a storage medium storing a cloud-based station interaction program. When executed by a processor, the cloud-based station interaction program implements the steps of the interaction method of the online ticketing system described above. Therefore, it will not be repeated here. Additionally, the beneficial effects of using the same method will not be repeated here either. For technical details not disclosed in the computer-readable storage medium embodiments related to this application, please refer to the description of the method embodiments of this application. As an example, program instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0101] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0102] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided by this invention, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.

[0103] Through the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus necessary general-purpose hardware, and of course, it can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memory, special components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for the present invention, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, portable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

Claims

1. A networked ticketing system, characterized in that, The online ticketing system includes: The ticketing information acquisition module is used to receive the first ticketing information provided by the cloud station management system and the second ticketing information collected by the front-end system from the corresponding station management system; The ticketing information cleaning module is used to clean the first ticketing information and the second ticketing information. The ticketing information configuration module is used to obtain the first configuration information corresponding to the cloud station management system and the second configuration information corresponding to the station management system of the front-end system, and bind the first configuration information with the first ticketing information, and bind the second configuration information with the second ticketing information; The ticketing module is used to receive ticket purchase instructions, match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and establish the association between the first ticketing information or second ticketing information and passenger information; The first configuration information and the second configuration information include station basic data, station role data, permission data, scheduling rule data, transmission encryption data, data synchronization rules, sales rules, and payment data; The online ticketing system and the front-end system use a symmetric encryption algorithm to transmit data; The ticketing information acquisition module includes a front-end system, which is used to collect second ticketing information from the traditional station service system. The front-end system acts as a data transmission middleware and is linked to self-service ticket vending machines, integrated windows, and small parcel express delivery systems.

2. The online ticketing system as described in claim 1, characterized in that, The online ticketing system connects to at least one supplier system; wherein, the supplier system, station administration system, and cloud station administration system synchronize data using timed synchronization, full synchronization, or hotspot synchronization.

3. The online ticketing system as described in claim 1, characterized in that, The online ticketing system also includes a business information configuration module, which is used to configure the ticket association information of the first ticket information and the second ticket information, and to configure the associated product information of the first ticket information and the second ticket information according to the product configuration instructions.

4. The online ticketing system as described in claim 3, characterized in that, The ticketing-related information includes ticket type, ID, electronic ticket, or prohibited items; the related product information includes related insurance information, related coupon information, related pick-up and drop-off service information, or related merchandise information.

5. The online ticketing system as described in claim 1, characterized in that, The ticketing module includes: The online ticketing unit is used to obtain the passenger's ticket purchase instruction to access the cloud station service system, and match the ticket purchase instruction with the corresponding first ticketing information or second ticketing information, and establish the ticket purchase information that associates the first ticketing information or second ticketing information with the passenger information; The station and offline ticketing unit is used to obtain the ticket purchase instructions from passengers accessing the station service system or offline ticketing equipment, and to match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and to establish the association between the first ticketing information or second ticketing information and passenger information. The ticketing unit is used to obtain ticket purchase instructions from a third-party ticketing system connected to the online ticketing system, match the ticket purchase instructions with corresponding first ticketing information or second ticketing information, and establish the association between the first ticketing information or second ticketing information and passenger information.

6. The online ticketing system as described in claim 1, characterized in that, The online ticketing system also includes an online ticketing distribution module, which is used to send the cleaned and configured first ticketing information and second ticketing information to a third-party ticketing system, so that the third-party ticketing system can perform ticket display, query and reservation tasks based on the first ticketing information and second ticketing information.

7. The online ticketing system as described in claim 6, characterized in that, The online ticketing system also includes a ticketing traffic distribution module. When the ticketing traffic distribution module receives a ticketing instruction from an offline ticketing device, it sends the ticketing instruction to the corresponding third-party ticketing system and matches the ticketing instruction with corresponding first ticketing information or second ticketing information, establishing a ticketing information association between the first ticketing information or second ticketing information and passenger information.

8. An interactive method for a networked ticketing system, characterized in that, The interaction method of the online ticketing system includes the following steps: The ticketing information acquisition module receives the first ticketing information provided by the cloud station administration system and the second ticketing information collected by the front-end system from the corresponding station administration system. The ticketing information cleaning module cleans the first and second ticketing information. The ticketing information configuration module obtains the first configuration information corresponding to the cloud station management system and the second configuration information corresponding to the station management system of the front-end system, and binds the first configuration information with the first ticketing information and the second configuration information with the second ticketing information. The ticketing module receives ticket purchase instructions, matches the corresponding first or second ticketing information to the ticket purchase instructions, and establishes an association between the first or second ticketing information and passenger information.

Images