Method, device, computer equipment and storage medium for processing rare characters

Abstract

The embodiments of the present application provide a method, apparatus, computer equipment and storage medium for processing rare characters, the method comprising: receiving user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, obtaining a glyph outline of the current character from a local database according to the encoding and attributes of the current character; if the glyph outline of the current character does not exist in the local database, storing the encoding and attributes of the current character in the local database to determine whether the current character is an rare word; if the current character is an rare word, querying the glyph outline of the current character from a target database; if the glyph outline of the current character does not exist in the target database, sending a manual processing request; from all links in the entire process of issuing electronic invoices, predicting and processing rare characters in names in advance, and performing manual intervention in advance for rare characters that cannot be displayed, to ensure the correct display of rare characters and improve user experience.

Description

Technical Field

[0001] The present application relates to the technical field of invoice issuance, and in particular, to a method, device, computer equipment and storage medium for processing rare characters. Background Art

[0002] At present, in the process of issuing electronic invoices, the processing of uncommon characters in names mostly focuses on the generation of layout files. When issuing electronic invoices, a word-by-word search is performed on the name to see if the character exists in the font library. If not, it is displayed as empty in the layout file. If it exists, it is determined whether it is an uncommon character. If it is an uncommon character, the character information or glyph outline is embedded in the layout file.

[0003] However, the identification and processing of rare characters only occurs during the generation of the layout file. The display of rare characters mainly depends on the font library on the layout service server. If the font is missing on the server, it cannot be displayed normally. In addition, it is only after the electronic invoice is issued that it can be found whether the rare characters are missing. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, computer device and storage medium for processing rare characters.

[0005] A first aspect of an embodiment of the present application provides a method for processing rare characters, which is applied to a ticket system and includes:

[0006] 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;

[0007] 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;

[0008] 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;

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

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

[0011] In an optional embodiment of the present application, when 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, determining whether the current character is an uncommon word, and when the current character is an uncommon word, querying the glyph outline of the current character from the target database includes:

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

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

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

[0015] In an optional embodiment of the present application, the method further includes:

[0016] If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character;

[0017] When the current character is an uncommon character, the encoding, attributes and glyph outline of the current character are stored in the local database;

[0018] If the current character is not an uncommon character, no action is performed.

[0019] In an optional embodiment of the present application, the method further includes:

[0020] receiving an invoice download request, and for a specified character in the invoice download request, obtaining a glyph outline of the current character from a local database and a target database according to the encoding and attributes of the current character;

[0021] If the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, the glyph outline of the current character is provided.

[0022] In an optional embodiment of the present application, when the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, providing the glyph outline of the current character includes:

[0023] If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character;

[0024] When the current character is an uncommon character, provide the glyph outline of the current character;

[0025] When the current character is not an uncommon character, the encoding and attributes of the current character are provided.

[0026] In an optional embodiment of the present application, the method further includes:

[0027] When the glyph outline of the current character does not exist in the local database, the glyph outline of the current character is obtained from the target database according to the encoding and attributes of the current character;

[0028] In the case that the target database has a glyph outline of the current character, determining whether the current character is a rare character;

[0029] When the current character is an uncommon character, provide the glyph outline of the current character;

[0030] If the current character is not a rare character, provide the encoding and attributes of the current character;

[0031] When the target database does not have the glyph outline of the current character, a manual processing request is sent.

[0032] In an optional embodiment of the present application, the method further includes:

[0033] An invoice is generated according to the glyph outline of the current character and provided to the invoice download requesting end.

[0034] A second aspect of the embodiments of the present application provides a device for processing rare characters, including:

[0035] The acquisition module is used to receive user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, acquire the glyph outline of the current character from a local database according to the encoding and attributes of the current character;

[0036] A determination module, used for storing the encoding and attributes of the current character in the local database to determine whether the current character is an uncommon word when the glyph outline of the current character does not exist in the local database;

[0037] A query module, used for querying the glyph outline of the current character from a target database when the current character is an uncommon word, wherein the target database is different from the local database;

[0038] A sending module, used for sending a manual processing request when the target database does not have the glyph outline of the current character;

[0039] The storage module is used to store the encoding, attributes and glyph outline of the current character in the target database when the glyph outline of the current character exists in the target database.

[0040] 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 rare character processing methods are implemented.

[0041] According to a fourth 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 any of the above rare-character processing methods are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0043] Figure 1 A flowchart of a method for processing rare characters provided in one embodiment of the present application;

[0044] Figure 2 A flowchart of a method for processing rare characters in a system registration link provided by an embodiment of the present application;

[0045] Figure 3 A flowchart of a method for processing rare characters in an invoice application process provided as an embodiment of the present application;

[0046] Figure 4 A flowchart of a method for processing rare characters in an invoice downloading process provided by an embodiment of the present application;

[0047] Figure 5 A flowchart of a method for compensating for uncommon characters in a system registration link and an invoice application link provided in an embodiment of the present application;

[0048] Figure 6 A schematic diagram of the structure of a device for processing rare characters provided in one embodiment of the present application;

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

[0050] In the process of realizing the present application, the inventor discovered that, when currently issuing an invoice, if the format service server lacks rare characters that need to be displayed, the rare characters cannot be displayed normally.

[0051] In response to the above problems, an embodiment of the present application provides a method for processing uncommon characters, which receives user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, obtains the glyph outline of the current character from a local database according to the encoding and attributes of the current character; if the glyph outline of the current character does not exist in the local database, stores the encoding and attributes of the current character in the local database, and determines whether the current character is an uncommon word; if the current character is an uncommon word, queries the glyph outline of the current character from a target database, wherein the target database is different from the local database; if the glyph outline of the current character does not exist in the target database, sends a manual processing request; if the glyph outline of the current character exists in the target database, stores the encoding, attributes and glyph outline of the current character in the target database, and predicts and processes the uncommon characters in the name in advance in all links of the entire process of issuing electronic invoices, and performs manual intervention in advance for uncommon characters that cannot be displayed, to ensure the correct display of uncommon characters, thereby improving user experience.

[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 rare character processing method provided in the embodiment of the present application is applied to the ticket system, and includes the following steps S1 to S4:

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

[0056] S2, if the local database does not have the glyph outline of the current character, store the encoding and attributes of the current character in the local database to determine whether the current character is an uncommon word;

[0057] S3, when 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;

[0058] S4, when the target database does not have the glyph outline of the current character, sending a manual processing request;

[0059] S5: If the target database has the glyph outline of the current character, store the encoding, attributes and glyph outline of the current character in the target database.

[0060] In an optional embodiment of the present application, when 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, determining whether the current character is an uncommon word, and when the current character is an uncommon word, querying the glyph outline of the current character from the target database includes:

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

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

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

[0064] In an optional embodiment of the present application, the method further includes:

[0065] If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character;

[0066] When the current character is an uncommon character, the encoding, attributes and glyph outline of the current character are stored in the local database;

[0067] If the current character is not an uncommon character, no action is performed.

[0068] In an optional embodiment of the present application, the method further includes:

[0069] receiving an invoice download request, and for a specified character in the invoice download request, obtaining a glyph outline of the current character from a local database and a target database according to the encoding and attributes of the current character;

[0070] If the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, the glyph outline of the current character is provided.

[0071] In an optional embodiment of the present application, when the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, providing the glyph outline of the current character includes:

[0072] If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character;

[0073] When the current character is an uncommon character, provide the glyph outline of the current character;

[0074] When the current character is not an uncommon character, the encoding and attributes of the current character are provided.

[0075] In an optional embodiment of the present application, the method further includes:

[0076] When the glyph outline of the current character does not exist in the local database, the glyph outline of the current character is obtained from the target database according to the encoding and attributes of the current character;

[0077] In the case that the target database has a glyph outline of the current character, determining whether the current character is a rare character;

[0078] When the current character is an uncommon character, provide the glyph outline of the current character;

[0079] If the current character is not a rare character, provide the encoding and attributes of the current character;

[0080] When the target database does not have the glyph outline of the current character, a manual processing request is sent.

[0081] In an optional embodiment of the present application, the method further includes:

[0082] An invoice is generated according to the glyph outline of the current character and provided to the invoice download requesting end.

[0083] In this application, uncommon characters are detected and processed in each link of electronic invoice issuance (user registration, invoice application, electronic invoice generation, etc.). In the user registration and invoice application environment, the system accepts the character encoding and font attribute information of each character in the name and obtains the glyph outline. (1) If the glyph outline does not exist locally (front end), the character encoding and font attribute information are saved in the database, and the character is marked as having no glyph outline in the front end. The backend compensation system uniformly supplements the glyph outline for these characters without glyph outlines; if the character still does not have glyph outline information after the compensation mechanism, the system will send a notification message for manual intervention. (2) If the glyph outline exists locally (front end), the system needs to determine whether the character is an uncommon character. If it is an uncommon character, the character encoding, font attribute information, and glyph outline information are saved in the database. Otherwise, the character is a common character and does not need to be processed. In the link of generating the electronic invoice layout file, the system first obtains the uncommon character information from the local font library. If it does not exist locally, the saved uncommon character information is obtained from the database and embedded into the layout file.

[0084] In this application, the method for processing rare characters in the system registration link is as follows Figure 2The main process of the method for processing rare characters in the system registration process includes:

[0085] 1. The system accepts information such as name;

[0086] 2. The system obtains information such as the glyph outline based on information such as character encoding and character attributes;

[0087] 3. If the glyph outline and other information are not obtained, the character information is saved in the database, and the glyph outline information is marked, and the process ends.

[0088] 3.1 If the information such as the glyph outline is obtained and the character is an uncommon character, the character information including the glyph outline is saved in the database, and the process ends;

[0089] 3.2 If the information such as the glyph outline is obtained, the character is not an uncommon character and the process ends.

[0090] In this application, the method for handling rare characters in the invoice application process is as follows Figure 3 As shown, the following steps are included:

[0091] 1. The system accepts the buyer's name and other information;

[0092] 2. The system obtains information such as the glyph outline based on information such as character encoding and character attributes;

[0093] 3. If the glyph outline and other information are not obtained, the character information is saved in the database, and the glyph outline information is marked, and the process ends.

[0094] 3.1 If the information such as the glyph outline is obtained and the character is an uncommon character, the character information including the glyph outline is saved in the database, and the process ends;

[0095] 3.2 If the information such as the glyph outline is obtained, the character is not an uncommon character and the process ends.

[0096] In this application, the method for processing rare characters in the invoice downloading link is as follows Figure 4 As shown, the following steps are included:

[0097] 1. The system accepts character information;

[0098] 2. The system obtains information such as glyph outline from the local font library based on information such as character encoding and character attributes;

[0099] 3. If the glyph outline and other information are obtained, the process ends.

[0100] 3.1 If the glyph outline and other information are not obtained, the system obtains the glyph outline and other information from the database based on the character encoding, character attributes and other information;

[0101] 3.2 If the glyph outline and other information are obtained, the process ends;

[0102] 3.3 If the glyph outline and other information are not obtained, SMS notification will be sent for manual intervention.

[0103] In this application, the method of compensating for uncommon characters in the system registration and invoice application process is as follows: Figure 5 As shown, the following steps are included:

[0104] 1. The system regularly scans the missing table of rare characters;

[0105] 2. If the glyph outline and other information are not missing, the process ends;

[0106] 3. If the information such as the glyph outline is missing, the system obtains the information such as the glyph outline based on the character encoding, character attributes and other information;

[0107] 4. If the information such as the glyph outline is not missing, complete the missing table of rare characters and the process ends;

[0108] 4.12. If information such as the glyph outline is missing, a text message will be sent to notify manual intervention and the process will end.

[0109] 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 rare character processing method, a ticket recommendation method, wherein the ticket recommendation method includes:

[0110] 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;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0125] In an optional embodiment of the present application, the ticket management method further includes a ticket refund method when a ticket system fails, and the ticket refund method when a ticket system fails includes:

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

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

[0128] 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;

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

[0130] In an optional embodiment of the present application, the ticket refund method when a ticket system failure occurs further includes:

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

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

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

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

[0135] 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;

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

[0137] 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;

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

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

[0140] ,

[0141] 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;

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

[0143] ;

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

[0145] ,

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

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

[0148] ;

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

[0150] 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;

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

[0152] ,

[0153] in is sensitive data;

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

[0155] ;

[0156] Construct the encryption formula:

[0157] ;

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

[0159] 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;

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

[0161] ;

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

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

[0164] When the gate detects that the target passenger 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;

[0165] 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 passenger;

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

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

[0168] See also Figure 6 An embodiment of the present application provides a device for processing rare characters, including:

[0169] The acquisition module 11 is used to receive user registration information or invoice application information, and for a specified character in the user registration information or invoice application information, acquire the glyph outline of the current character from a local database according to the encoding and attributes of the current character;

[0170] A determination module 12, for storing the encoding and attributes of the current character in the local database to determine whether the current character is an uncommon word when the glyph outline of the current character does not exist in the local database;

[0171] A query module 13, used for querying the glyph outline of the current character from a target database when the current character is an uncommon word, wherein the target database is different from the local database;

[0172] A sending module 14, used for sending a manual processing request when the target database does not have the glyph outline of the current character;

[0173] The storage module 15 is used to store the code, attribute and glyph outline of the current character in the target database when the glyph outline of the current character exists in the target database.

[0174] For the specific definition of the above-mentioned uncommon character processing device, please refer to the definition of the uncommon character processing method in the above text, which will not be repeated here. Each module in the above-mentioned uncommon character processing device can be implemented in whole or in part by software, hardware and a combination thereof. Each of 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 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.

[0175] In one embodiment, a computer device is provided, the internal structure diagram of which can be as follows: Figure 7 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 via a network connection. When the computer program is executed by the processor, a method for processing rare characters 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 processing rare characters as described above is implemented.

[0176] 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 rare character processing method can be implemented.

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

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

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

[0180] 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 The steps for the functions specified in one or more boxes.

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

[0182] 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: Applied to the ticket system, it includes not only the method for processing rare characters, but also the method for managing ticket system information. The method for processing rare characters comprises: 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; If the local database does not contain the glyph outline of the current character, store the encoding and attributes of the current character in the local database, determine whether the current character is an uncommon word, and if the current character is an uncommon word, query 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; If 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. Wherein, when 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, determining whether the current character is an uncommon word, and when the current character is an uncommon word, querying the glyph outline of the current character from the target database, including: When the local database does not have the glyph outline of the current character, the current character is marked as a glyph-missing character; The rare characters among the missing characters are stored in the rare character missing table; For each character in the missing rare character table, query the glyph outline of the current character from the target database. The method further comprises: receiving an invoice download request, and for a specified character in the invoice download request, obtaining a glyph outline of the current character from a local database and a target database according to the encoding and attributes of the current character; If the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, the glyph outline of the current character is provided. The method further comprises: Generate an invoice based on the glyph outline of the current character and provide it to the invoice download request end. Among them, the method of compensating for rare characters in the system registration and invoice application process includes the following steps: The system regularly scans the missing table of rare characters; If the glyph outline information is not missing, the process ends; If the glyph outline information is missing, the system obtains the glyph outline information based on the character encoding and character attribute information; If the glyph outline information is not missing, complete the missing table of rare characters and the process ends; If the glyph outline information is missing, a short message will be sent to notify manual intervention and the process will end. The ticket system information management method also 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; Decrypt the exchanged data and store the ticket system information data, build a visual interface to display the ticket system information data in real time, The step of constructing a ticket system information data sensitivity scoring model to evaluate the ticket system information data sensitivity and classify the ticket system information data refers to collecting historical ticket system information data and extracting historical feature vectors, and calculating the mean of the historical feature vectors and setting them as the benchmark data vectors; Collect ticket system information data in real time and extract real-time feature vectors. Use the clustering analysis algorithm K-means to cluster the real-time feature vectors, and select the center point of each cluster as the reference feature vector. 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: ， 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; Logarithmic transformation of the cumulative similarity A(x) , the formula is: ； 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: ， Where M is the number of reference eigenvectors, is the jth reference eigenvector; Construct a sensitivity scoring model to evaluate the sensitivity score of the feature vector of the ticket system information data , the formula is: ； 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 or 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.

2. The method according to claim 1, characterized in that The method comprises: storing the encoding and attributes of the current character in the local database when the local database does not have the glyph outline of the current character, determining whether the current character is an uncommon word, and querying the glyph outline of the current character from the target database when the current character is an uncommon word, including: When the local database does not have the glyph outline of the current character, the current character is marked as a glyph-missing character; The rare characters among the missing characters are stored in the rare character missing table; For each character in the rare character missing table, the glyph outline of the current character is queried from the target database.

3. The method according to claim 1, characterized in that The method further comprises: If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character; When the current character is an uncommon character, the encoding, attributes and glyph outline of the current character are stored in the local database; If the current character is not an uncommon character, no action is performed.

4. The method according to claim 1, characterized in that: When the glyph outline of the current character exists in the local database or the target database and the current character is an uncommon character, providing the glyph outline of the current character comprises: If the local database has the glyph outline of the current character, determine whether the current character is an uncommon character; When the current character is an uncommon character, provide the glyph outline of the current character; When the current character is not an uncommon character, the encoding and attributes of the current character are provided.

5. The method according to claim 1, characterized in that The method further comprises: When the glyph outline of the current character does not exist in the local database, the glyph outline of the current character is obtained from the target database according to the encoding and attributes of the current character; In the case that the target database has a glyph outline of the current character, determining whether the current character is a rare character; When the current character is an uncommon character, provide the glyph outline of the current character; If the current character is not a rare character, provide the encoding and attributes of the current character; When the target database does not have the glyph outline of the current character, a manual processing request is sent.

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