Ticket refund method, device, equipment and storage medium when ticket system fails

Abstract

In an embodiment of the present application, a method, device, equipment and storage medium for refunding tickets when a ticket system fails are provided, the method comprising: in the event of a ticket system failure, sending a received refund request to a target server; storing each refund request on the target server and recording the time of receipt of each refund request; when the ticket system returns to normal, responding to the refund request on the target server, determining the refund fee according to the time of receipt of each refund request; sending the refund result to a target object corresponding to the refund request; after recording the time of receipt of each refund request, sending the received ticket purchase request to the target server; when the time of receipt of the ticket purchase request corresponding to the same target object is later than the refund request, releasing the restriction on the target object to purchase a ticket again on the target server, which can solve the problem that passengers cannot refund tickets in time when a failure occurs or the system is busy.

Description

Technical Field

[0001] The present application relates to the technical field of ticket systems, and in particular to a ticket refund method, device, computer equipment and storage medium when a ticket system fails. Background Art

[0002] The current passenger regulations stipulate that the refund fee rate is directly related to the departure time. No refund fee will be charged for refunds made 8 days or more before departure; 5% of the ticket price will be charged for refunds made more than 48 hours before the departure time at the boarding station on the ticket face, 10% of the ticket price will be charged for refunds made more than 24 hours but less than 48 hours before the departure time at the boarding station on the ticket face, and 20% of the ticket price will be charged for refunds made less than 24 hours before the departure time at the boarding station on the ticket face.

[0003] When the system fails or is busy, the system cannot process refund requests and passengers cannot get refunds. The system's inability to refund tickets will cause queues at passenger windows and customer complaints.

[0004] At the same time, since there is a deadline for refunding tickets, and the refund fee is based on the refund time, the system problem will affect the actual interests of passengers if the ticket cannot be refunded. In addition, since the ticket has not been refunded, the itinerary conflict judgment currently implemented by the railway will affect the travel of passengers. This has a great impact on the railway department and passengers.

[0005] When a passenger normally handles a ticket refund, the system first checks whether the ticket is refundable and calculates the refund fee rate. After the passenger clicks to confirm the refund, the system officially refunds the ticket and initiates a refund command. Summary of the invention

[0006] The embodiments of the present application provide a ticket refund method, device, computer equipment and storage medium when a ticket system failure occurs.

[0007] A first aspect of an embodiment of the present application provides a ticket refund method when a ticket system fails, comprising:

[0008] In case of a failure in the ticket system, the received refund request is sent to the target server;

[0009] storing each refund request on the target server and recording the time point of receiving each refund request;

[0010] When the ticket system returns to normal, respond to the refund request on the target server, determine the refund fee according to the time point of receiving each refund request, and perform the refund operation;

[0011] Send the refund result to the target object corresponding to the refund request;

[0012] After recording the time point of receiving each ticket refund request, sending the received ticket purchase request to the target server;

[0013] When the ticket purchase request corresponding to the same target object is received later than the ticket refund request, the target server releases the restriction on the target object to purchase the ticket again.

[0014] In an optional embodiment of the present application, after performing the ticket refund operation, the method further includes:

[0015] Send the refund result to the target object corresponding to the refund request.

[0016] In an optional embodiment of the present application, after performing the ticket refund operation, the method further includes:

[0017] Determine whether the type of failure in the ticket system is a historical failure type;

[0018] In the case where the type of failure in the ticket system is a historical failure type, the ticket system is restored according to a pre-stored restoration operation corresponding to the current historical failure type;

[0019] In the case where the type of fault occurring in the ticket system is a new fault type, the current new fault type is recorded, and the recovery operation corresponding to the current new fault type is stored.

[0020] A second aspect of the embodiments of the present application provides a ticket refund device when a ticket system fails, comprising:

[0021] A first sending module, used for sending the received ticket refund request to a target server in case of a failure in the ticket system;

[0022] A recording module, used to store each refund request on the target server and record the time point of receiving each refund request;

[0023] A determination module, which is used to respond to the refund request on the target server when the ticket system returns to normal, determine the refund fee according to the receiving time point of each refund request, and perform the refund operation;

[0024] A second sending module, used for sending the refund result to a target object corresponding to the refund request;

[0025] A third sending module is used to send the received ticket purchase request to the target server after recording the receiving time point of each ticket refund request;

[0026] The release module is used to release the restriction on the target object to purchase the ticket again on the target server when the receipt time point of the ticket purchase request corresponding to the same target object is later than the ticket refund request.

[0027] A third aspect of the embodiments of the present application provides a ticket management method, which is applied to a ticket system. In addition to the ticket refund method when a ticket system fails, the ticket management method also includes a ticket recommendation method, wherein the ticket recommendation method includes:

[0028] For each travel day, obtain the sales and inspection volume of train tickets and single-day tickets in real time, where train tickets are tickets for travel by train number, and single-day tickets are tickets for travel by travel date;

[0029] Determine the predicted passenger flow on a specified ride date based on historical passenger flow;

[0030] Receive a ticket purchase request from a user, and determine whether to recommend train tickets and day tickets for the travel date based on the target travel date, departure station and arrival station in the ticket purchase request, as well as the predicted passenger flow on the target travel date, sales volume of train tickets and day tickets, and ticket inspection volume.

[0031] In an optional embodiment of the present application, the ticket management method further includes an automatic ticket refund method for a suspended train ticket system, wherein the automatic ticket refund method for a suspended train ticket system includes:

[0032] Receive the suspension information of the target train and collect all the target tickets corresponding to the target train;

[0033] Automatically initiate a refund request for all target tickets according to the preset time in the suspension information;

[0034] The refund operation is performed according to the refund request corresponding to each target ticket.

[0035] In an optional embodiment of the present application, the ticket management method further includes a rare character processing method, wherein the rare character processing method includes:

[0036] Receive user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, obtain the glyph outline of the current character from a local database according to the encoding and attributes of the current character;

[0037] In the case that the glyph outline of the current character does not exist in the local database, the encoding and attributes of the current character are stored in the local database to determine whether the current character is an uncommon word;

[0038] In the case where the current character is an uncommon word, querying the glyph outline of the current character from a target database, wherein the target database is different from the local database;

[0039] In the case that the target database does not have the glyph outline of the current character, a manual processing request is sent;

[0040] In the case that the target database has the glyph outline of the current character, the encoding, attributes and glyph outline of the current character are stored in the target database.

[0041] In an optional embodiment of the present application, the ticket management method further includes a ticket system information management method, and the ticket system information management method includes:

[0042] Acquire ticket system information data and preprocess it, and extract feature vectors of the preprocessed ticket system information data;

[0043] Construct a ticket system information data sensitivity scoring model to evaluate the sensitivity of ticket system information data and classify it, and encrypt the sensitive data of ticket system information data based on the classification results;

[0044] The exchanged data is decrypted and stored to obtain the ticket system information data, and a visual interface is constructed to display the ticket system information data in real time.

[0045] According to a fourth aspect of an embodiment of the present application, a computer device is provided, comprising: a memory and a processor, the memory storing a computer program, and the processor implementing the steps of any of the above ticket refund method or ticket management method when a ticket system failure occurs when executing the computer program.

[0046] According to a fifth aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the ticket refund method or ticket management method when a ticket system failure occurs are implemented as described in any of the above items. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] 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:

[0048] Figure 1 A flowchart of a ticket refund method when a ticket system fails provided in one embodiment of the present application;

[0049] Figure 2 A schematic diagram of the structure of a ticket refund device when a ticket system failure occurs provided by one embodiment of the present application;

[0050] Figure 3 A schematic diagram of the computer device structure provided for one embodiment of the present application. DETAILED DESCRIPTION

[0051] In the process of realizing the present application, the inventor discovered that passengers cannot refund their tickets in time when the current ticket system fails or the system is busy.

[0052] 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.

[0053] 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.

[0054] See also Figure 1 The ticket refund method provided in the embodiment of the present application when a ticket system failure occurs includes the following steps S1-S3:

[0055] S1, in the event of a failure in the ticket system, sending the received ticket refund request to a target server, wherein the target server is connected to the server where the ticket system is located;

[0056] S2, storing each refund request on the target server and recording the time point of receiving each refund request;

[0057] S3, when the ticket system returns to normal, respond to the refund request on the target server, determine the refund fee according to the time point of receiving each refund request, and perform the refund operation;

[0058] S4, sending the refund result to the target object corresponding to the refund request;

[0059] S5, after recording the receiving time point of each ticket refund request, sending the received ticket purchase request to the target server;

[0060] S6. When the receipt time of the ticket purchase request corresponding to the same target object is later than that of the ticket refund request, the target server releases the restriction on the target object to purchase the ticket again, wherein the restriction is caused by the itinerary conflict between the ticket refund request and the ticket purchase request of the target object.

[0061] In an optional embodiment of the present application, after performing the ticket refund operation, the method further includes:

[0062] Send the refund result to the target object corresponding to the refund request.

[0063] In an optional embodiment of the present application, after performing the ticket refund operation, the method further includes:

[0064] Determine whether the type of failure in the ticket system is a historical failure type;

[0065] In the case where the type of failure in the ticket system is a historical failure type, the ticket system is restored according to a pre-stored restoration operation corresponding to the current historical failure type;

[0066] In the case where the type of fault occurring in the ticket system is a new fault type, the current new fault type is recorded, and the recovery operation corresponding to the current new fault type is stored.

[0067] In the present application, the ticket system can quickly recover from system failures by restoring the ticket system according to pre-stored recovery operations corresponding to the current historical failure type, and by recording the current new failure type and storing the recovery operations corresponding to the current new failure type, the failure type can be updated to prepare for subsequent rapid recovery of system failures.

[0068] In this application, in order to process ticket refund services when the system fails or the system is busy, without affecting normal business processing and passenger experience, after a server failure, the system will no longer continue to process refund services at the failed node, and will point to the target server, where the target server is an emergency server. After the passenger submits a refund request, the passenger is prompted whether to refund the ticket. After the passenger clicks OK, the passenger's refund request is recorded on the emergency server. At this time, the time point when the passenger applies for a refund is recorded, and no refund fee calculation, refund, and other operations are performed. After the refund request is successfully accepted, the passenger can purchase other tickets without being affected by the itinerary conflict of the ticket for which the refund is applied. After the server is restored, the server processes the passenger's refund request, calculates the refund fee according to the recorded time point when the passenger applied for a refund, and processes the refund. After the business is completed, the system notifies the passenger of the refund result and waits to receive the refund.

[0069] This application optimizes the user experience of passengers by accepting the application first and then processing it. When a refund request is received, the restriction on the target person to purchase a ticket again is released without affecting the passenger's travel. After the system is restored, the refund is processed according to the rate at the time of the request.

[0070] This application avoids the situation where system failure affects passengers’ ticket refunds, resulting in passengers being unable to refund tickets and changes in refund fees, and solves the problem where passengers are unable to purchase tickets again due to itinerary conflicts when they were unable to refund tickets before.

[0071] The embodiment of the present application further provides a ticket management method, which is applied to a ticket system and includes, in addition to the above-mentioned ticket refund method when a ticket system fails, a ticket recommendation method, wherein the ticket recommendation method includes:

[0072] For each travel day, obtain the sales and inspection volume of train tickets and single-day tickets in real time, where train tickets are tickets for travel by train number, and single-day tickets are tickets for travel by travel date;

[0073] Determine the predicted passenger flow on a specified ride date based on historical passenger flow;

[0074] Receive a ticket purchase request from a user, and determine whether to recommend train tickets and day tickets for the travel date based on the target travel date, departure station and arrival station in the ticket purchase request, as well as the predicted passenger flow on the target travel date, sales volume of train tickets and day tickets, and ticket inspection volume.

[0075] In an optional embodiment of the present application, the step of determining whether to recommend train tickets and day tickets for the travel date according to the target travel date, the departure station and the arrival station in the ticket purchase request, the passenger flow forecast for the target travel date, the sales volume of train tickets and day tickets, and the ticket inspection volume includes:

[0076] When the sales volume of single-day tickets for the target travel date in the ticket purchase request reaches the preset threshold for single-day tickets, the single-day tickets are displayed as out of stock, wherein the preset threshold for single-day tickets is determined based on the predicted passenger flow for the target travel date.

[0077] In an optional embodiment of the present application, the ticket management method further includes an automatic ticket refund method for a suspended train ticket system, and the automatic ticket refund method for a suspended train ticket system includes:

[0078] Receive the suspension information of the target train and collect all the target tickets corresponding to the target train;

[0079] Automatically initiate a refund request for all target tickets according to the preset time in the suspension information;

[0080] The refund operation is performed according to the refund request corresponding to each target ticket.

[0081] In an optional embodiment of the present application, the aggregating all target tickets corresponding to the target train includes:

[0082] All purchased target train tickets are regarded as all target tickets corresponding to the target train.

[0083] In an optional embodiment of the present application, automatically initiating a refund request for all target tickets according to the preset time in the suspension information includes:

[0084] Automatically initiate a full refund for target tickets that have been purchased before the preset time and have not been changed or refunded;

[0085] For target tickets purchased before the preset time and charged a change fee, automatically initiate a refund of the change fee;

[0086] For target tickets that have been purchased before the preset time and for which a refund fee is charged, a refund of the refund fee is automatically initiated.

[0087] In an optional embodiment of the present application, the ticket management method further includes a rare character processing method, wherein the rare character processing method includes:

[0088] Receive user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, obtain the glyph outline of the current character from a local database according to the encoding and attributes of the current character;

[0089] In the case that the glyph outline of the current character does not exist in the local database, the encoding and attributes of the current character are stored in the local database to determine whether the current character is an uncommon word;

[0090] In the case where the current character is an uncommon word, querying the glyph outline of the current character from a target database, wherein the target database is different from the local database;

[0091] In the case that the target database does not have the glyph outline of the current character, a manual processing request is sent;

[0092] In the case that the target database has the glyph outline of the current character, the encoding, attributes and glyph outline of the current character are stored in the target database.

[0093] In an optional embodiment of the present application, when the local database does not have the glyph outline of the current character, storing the encoding and attributes of the current character in the local database, and when the current character is an uncommon word, querying the glyph outline of the current character from the target database includes:

[0094] When the local database does not have the glyph outline of the current character, the current character is marked as a glyph-missing character;

[0095] The rare characters among the missing characters are stored in the rare character missing table;

[0096] For each character in the rare character missing table, the glyph outline of the current character is queried from the target database.

[0097] In an optional embodiment of the present application, the ticket management method further includes a ticket system information management method, and the ticket system information management method includes:

[0098] Acquire ticket system information data and preprocess it, and extract feature vectors of the preprocessed ticket system information data;

[0099] Construct a ticket system information data sensitivity scoring model to evaluate the sensitivity of ticket system information data and classify it, and encrypt the sensitive data of ticket system information data based on the classification results;

[0100] The exchanged data is decrypted and stored to obtain the ticket system information data, and a visual interface is constructed to display the ticket system information data in real time.

[0101] In an optional embodiment of the present application, the construction of a ticket system information data sensitivity scoring model to evaluate the ticket system information data sensitivity and classify it refers to collecting historical ticket system information data and extracting historical feature vectors, calculating the mean of the historical feature vectors and setting them as the benchmark data vector;

[0102] Collect ticket system information data in real time and extract real-time feature vectors. Use the K-means clustering analysis algorithm to cluster the real-time feature vectors, and select the center point of each cluster as the reference data vector.

[0103] Combining the RBF kernel function with the integral, the cumulative similarity A(x) between the benchmark data vector and the feature vector of the ticket system information data is calculated. The formula is:

[0104] ,

[0105] Where x is the feature vector of ticket system information data, is the benchmark data vector, is the historical feature vector of the i-th ticket system information data;

[0106] Logarithmic transformation of the cumulative similarity A , the formula is:

[0107] ;

[0108] The hyperbolic tangent function is introduced to smooth the accumulated similarity of the reference feature vector, and the accumulated similarity after smoothing is obtained. , the formula is:

[0109] ,

[0110] Where M is the number of reference eigenvectors, is the jth reference eigenvector;

[0111] Construct a sensitivity scoring model to evaluate the sensitivity score of the feature vector of the ticket system information data , the formula is:

[0112] ;

[0113] The sensitivity scores of historical ticket system information data are collected to set an evaluation threshold, and the sensitivity scores of the feature vectors of the ticket system information data are compared with the evaluation threshold. If the sensitivity score of the feature vector of the ticket system information data is greater than and equal to the evaluation threshold, it is determined to be sensitive data; if the sensitivity score of the feature vector of the ticket system information data is less than the evaluation threshold, it is determined to be ordinary data.

[0114] In an optional embodiment of the present application, encrypting the sensitive data of the ticket system information data based on the classification result refers to randomly generating a key K using a random number generator;

[0115] Use exponential function and sine function to perform nonlinear transformation on sensitive data to obtain results that meet the nonlinear transformation requirements. , the formula is:

[0116] ,

[0117] in is sensitive data;

[0118] Use logarithmic function and smooth inverse tangent function to perform nonlinear transformation on sensitive data to obtain multi-level nonlinear transformation results , the formula is:

[0119] ;

[0120] Construct the encryption formula:

[0121] ;

[0122] Bring sensitive data into the encryption formula for encryption.

[0123] In an optional embodiment of the present application, decrypting the exchanged data to store the ticket system information data refers to receiving the transmitted encrypted data and the corresponding key K;

[0124] Use the decryption formula to decrypt the received data and obtain the decrypted sensitive data , the formula is:

[0125] ;

[0126] The collected ticket system information and sensitive data generated by the analysis are stored in the database, the ticket system information and sensitive data generated by the analysis in the database are backed up in the cloud, and the backup data are regularly checked for integrity.

[0127] In an optional embodiment of the present application, the ticket management method further includes:

[0128] When the gate detects that the target object corresponding to the first target ticket has not boarded the train, recommend other tickets for the date corresponding to the first target ticket according to the travel interval of the first target ticket;

[0129] In the case that there are no other tickets for the date corresponding to the first target ticket, feeding back ticket purchase preferential information to the target object;

[0130] A second target ticket for a train seat corresponding to the first target ticket is released on the ticket system, wherein the starting station of the travel section of the second target ticket is a station subsequent to the starting station of the first target ticket.

[0131] 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.

[0132] See also Figure 2 An embodiment of the present application provides a ticket refund device when a ticket system fails, comprising:

[0133] A first sending module 11 is used to send the received ticket refund request to a target server when a ticket system failure occurs;

[0134] A recording module 12, used to store each refund request on the target server and record the time point of receiving each refund request;

[0135] The determination module 13 is used to determine the refund fee and perform the refund operation in response to the refund request on the target server according to the receiving time point of each refund request when the ticket system returns to normal;

[0136] The second sending module 14 is used to send the refund result to the target object corresponding to the refund request;

[0137] The third sending module 15 is used to send the received ticket purchase request to the target server after recording the receiving time point of each ticket refund request;

[0138] The release module 16 is used to release the restriction on the target object to purchase a ticket again at the target server when the ticket purchase request corresponding to the same target object is received later than the ticket refund request.

[0139] The specific definition of the ticket refund device when the ticket system fails can be found in the definition of the ticket refund method when the ticket system fails, which will not be repeated here. Each module in the ticket refund device when the ticket system fails can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above 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 in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0140] In one embodiment, a computer device is provided, the internal structure diagram of which can be as follows: Figure 3 As shown. The computer device includes a processor, a memory, a network interface and a database connected through 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 method for refunding a ticket or a method for managing a ticket when a ticket system fails 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 method for refunding a ticket or a method for managing a ticket when a ticket system fails as described above is implemented.

[0141] 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 of the ticket refund method or ticket management method when a ticket system fails can be implemented.

[0142] 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 combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0143] 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.

[0144] 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 comprising 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.

[0145] 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.

[0146] 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.

[0147] 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 ticket management method, characterized in that: The ticket management method is applied to the ticket system. In addition to the ticket refund method when the ticket system fails, the ticket management method also includes a ticket recommendation method, wherein the ticket recommendation method includes: For each travel day, obtain the sales and inspection volume of train tickets and single-day tickets in real time, where train tickets are tickets for travel by train number, and single-day tickets are tickets for travel by travel date; Determine the predicted passenger flow on a specified ride date based on historical passenger flow; Receive a ticket purchase request from a user, and determine whether to recommend train tickets and day tickets for the travel date based on the target travel date, departure station and arrival station in the ticket purchase request, as well as the passenger flow forecast for the target travel date, the sales volume of train tickets and day tickets, and the ticket inspection volume. The ticket refund method when a ticket system failure occurs includes: In case of a failure in the ticket system, the received refund request is sent to the target server; storing each refund request on the target server and recording the time point of receiving each refund request; When the ticket system returns to normal, respond to the refund request on the target server, determine the refund fee according to the time point of receiving each refund request, and perform the refund operation; Send the refund result to the target object corresponding to the refund request; After recording the time point of receiving each ticket refund request, sending the received ticket purchase request to the target server; If the purchase request corresponding to the same target object is received later than the refund request, the target server releases the restriction on the target object to purchase the ticket again. Wherein, the ticket management method also includes a ticket system information management method, and the ticket system information management method includes: Acquire ticket system information data and preprocess it, and extract feature vectors of the preprocessed ticket system information data; Construct a ticket system information data sensitivity scoring model to evaluate the sensitivity of ticket system information data and classify it, and encrypt the sensitive data of ticket system information data based on the classification results; The exchanged data is decrypted and stored to obtain the ticket system information data, and a visual interface is constructed to display the ticket system information data in real time.

2. The ticket management method according to claim 1, characterized in that: After performing the ticket refund operation, the method further includes: Send the refund result to the target object corresponding to the refund request.

3. The ticket management method according to claim 1, characterized in that: After performing the ticket refund operation, the method further includes: Determine whether the type of failure in the ticket system is a historical failure type; In the case where the type of failure in the ticket system is a historical failure type, the ticket system is restored according to a pre-stored restoration operation corresponding to the current historical failure type; In the case where the type of fault occurring in the ticket system is a new fault type, the current new fault type is recorded, and the recovery operation corresponding to the current new fault type is stored.

4. The ticket management method according to claim 1, characterized in that: The ticket management method also includes an automatic ticket refund method for a suspended train ticket system, wherein the automatic ticket refund method for a suspended train ticket system includes: Receive the suspension information of the target train and collect all the target tickets corresponding to the target train; Automatically initiate a refund request for all target tickets according to the preset time in the suspension information; The refund operation is performed according to the refund request corresponding to each target ticket.

5. The ticket management method according to claim 1, characterized in that: The ticket management method further includes a method for processing rare characters, wherein the method for processing rare characters includes: Receive user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, obtain the glyph outline of the current character from a local database according to the encoding and attributes of the current character; In the case that the glyph outline of the current character does not exist in the local database, the encoding and attributes of the current character are stored in the local database to determine whether the current character is an uncommon word; In the case where the current character is an uncommon word, querying the glyph outline of the current character from a target database, wherein the target database is different from the local database; In the case that the target database does not have the glyph outline of the current character, a manual processing request is sent; In the case that the target database has the glyph outline of the current character, the encoding, attributes and glyph outline of the current character are stored in the target database.

6. 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 ticket management method according to any one of claims 1 to 5 when executing the computer program.

7. 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 ticket management method according to any one of claims 1 to 5 are implemented.

Images