Bill data processing method, electronic equipment and storage medium

Abstract

The invention provides a bill data processing method, electronic equipment and a storage medium. The method comprises the steps that an original bill file is acquired, and the original bill file comprises original service bill data corresponding to a target user; metadata information is determined based on the original bill file, and the metadata information is used for representing the mapping relation between the target user identification and the file absolute path; a target bill file is generated according to the metadata information, and the target bill file comprises encrypted service bill data corresponding to the target user; and sending the target bill file to the target user by using a target transmission mode, the target transmission mode being determined from a plurality of candidate transmission modes. According to the invention, the technical problems of insufficient security, low processing efficiency and poor flexibility of a bill data processing method provided in the related technology are solved.

Description

Technical Field

[0001] The present disclosure relates to the field of civil aviation information services, and in particular to a bill data processing method, electronic equipment and storage medium. Background Art

[0002] Foreign airline service billing data, as an important basis for airlines' financial analysis and decision-making, carries detailed transaction records and key business information. The accuracy and security of its processing and transmission are crucial to maintaining the economic interests of airlines and customer trust. The billing data processing methods in related technologies usually use manual or semi-automatic methods to format, verify and send bills. However, the above two billing data processing methods have problems with low security and processing efficiency and poor flexibility. The data lacks effective encryption protection during transmission and is prone to unauthorized access or tampering. At the same time, the billing processing process is rigid and difficult to adapt to the personalized needs of different users or business scenarios for bill formats and transmission methods. It is difficult to provide efficient and flexible billing data services while ensuring data security.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present disclosure provide a bill data processing method, an electronic device, and a storage medium to at least solve the technical problems of insufficient security, low processing efficiency, and poor flexibility of the bill data processing methods provided in the related art.

[0005] According to one aspect of an embodiment of the present disclosure, a billing data processing method is provided, including: obtaining an original billing file, wherein the original billing file includes original service billing data corresponding to a target user; determining metadata information based on the original billing file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path; generating a target billing file based on the metadata information, wherein the target billing file includes encrypted service billing data corresponding to the target user; and sending the target billing file to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

[0006] Optionally, obtaining the original bill file includes: obtaining original file information from the configuration center, wherein the original file information includes: service bill type, original bill path and original bill format; determining a preset file directory based on the original bill path; scanning and processing the preset file directory to obtain the original bill file.

[0007] Optionally, determining metadata information based on the original bill file includes: obtaining regularized expression information based on the original bill format; verifying the original bill file using the regularized expression information and the service bill type to obtain a file verification result; in response to determining that the original bill file has passed the verification based on the file verification result, determining a target user identifier based on the file identifier of the original bill file, and determining an absolute file path based on the original bill path, the file identifier of the original bill file, and the file format; determining metadata information based on the target user identifier and the absolute file path.

[0008] Optionally, generating a target bill file based on metadata information includes: obtaining user file information from a configuration center, wherein the user file information includes: a processing date field; in response to determining that the original bill file is in an unprocessed state based on the processing date field, using the metadata information to construct a file matching relationship, wherein the file matching relationship is used to represent the association relationship between the original bill file and the target bill file; encrypting the original bill file based on the file matching relationship to obtain an encryption result; formatting the encryption result to generate a target bill file.

[0009] Optionally, the original bill file is encrypted based on the file matching relationship to obtain the encryption result, including: obtaining user key information in response to the file matching relationship being verified; and encrypting the original bill file using a symmetric encryption algorithm and the user key information to obtain an encryption result.

[0010] Optionally, obtaining the user key information includes: obtaining the user key information from a configuration center, or generating the user key information using random characters.

[0011] Optionally, the bill data processing method further includes: in response to successfully sending the target bill file to the target user using the target transmission method, updating the processing date field.

[0012] According to another aspect of an embodiment of the present disclosure, a billing data processing device is also provided, including: an acquisition module, used to acquire an original billing file, wherein the original billing file includes original service billing data corresponding to a target user; a determination module, used to determine metadata information based on the original billing file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path; a generation module, used to generate a target billing file based on the metadata information, wherein the target billing file includes encrypted service billing data corresponding to the target user; and a sending module, used to send the target billing file to the target user using a target transmission method, wherein the target transmission method is determined from multiple candidate transmission methods.

[0013] Optionally, the acquisition module is also used to: obtain original file information from the configuration center, wherein the original file information includes: service bill type, original bill path and original bill format; determine a preset file directory based on the original bill path; scan and process the preset file directory to obtain the original bill file.

[0014] Optionally, the determination module is also used to: obtain regularized expression information based on the original bill format; use the regularized expression information and the service bill type to verify the original bill file to obtain a file verification result; in response to determining that the original bill file has passed the verification based on the file verification result, determine the target user identifier based on the file identifier of the original bill file, and determine the absolute file path based on the original bill path, the file identifier and the file format of the original bill file; determine the metadata information based on the target user identifier and the absolute file path.

[0015] Optionally, the generation module is also used to: obtain user file information from the configuration center, wherein the user file information includes: a processing date field; in response to determining that the original bill file is in an unprocessed state based on the processing date field, construct a file matching relationship using metadata information, wherein the file matching relationship is used to represent the association relationship between the original bill file and the target bill file; encrypt the original bill file based on the file matching relationship to obtain an encryption result; format the encryption result to generate a target bill file.

[0016] Optionally, the generation module is also used to: obtain user key information in response to the file matching relationship being verified; encrypt the original bill file using a symmetric encryption algorithm and the user key information to obtain an encryption result.

[0017] Optionally, the generation module is further used to: obtain user key information from a configuration center, or generate user key information using random characters.

[0018] According to another aspect of an embodiment of the present disclosure, an electronic device is also provided, including: a processor; a memory for storing processor executable instructions; wherein the processor is configured to execute instructions to implement the bill data processing method in the embodiment of the present disclosure.

[0019] According to another aspect of an embodiment of the present disclosure, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein when the executable program runs, the device where the storage medium is located is controlled to execute the bill data processing method in the embodiment of the present disclosure.

[0020] According to another aspect of the embodiments of the present disclosure, a computer program product is further provided. The computer program product includes computer instructions. When the computer instructions are executed by a processor, the bill data processing method in the embodiments of the present disclosure is implemented.

[0021] In the disclosed embodiment, by obtaining the original service bill data corresponding to the target user, determining the metadata information based on the original bill data, and then generating a target bill file based on the metadata information, and finally using the target transmission method to send the target bill file to the target user, the purpose of efficiently and securely transmitting the target user's service bill is achieved, thereby achieving the technical effect of improving the security, efficiency and flexibility of bill data processing, and thus solving the technical problems of insufficient security, low processing efficiency and poor flexibility of the bill data processing methods provided in the relevant technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The illustrative embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation on the present disclosure. In the drawings:

[0023] Figure 1 is a flow chart of a bill data processing method according to one embodiment of the present disclosure;

[0024] Figure 2 is a schematic diagram of a bill data processing method according to one embodiment of the present disclosure;

[0025] Figure 3 is a schematic diagram of a file collection unit according to one embodiment of the present disclosure;

[0026] Figure 4 is a schematic diagram of a file processing unit according to one embodiment of the present disclosure;

[0027] Figure 5 is a schematic diagram of a file sending unit according to one embodiment of the present disclosure;

[0028] Figure 6 It is a structural block diagram of a bill data processing device according to one embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the scheme of the present disclosure, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present disclosure.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0031] The bill data processing methods in the related art usually use manual or semi-automatic methods to format, verify and send bills. However, the above two bill data processing methods have problems such as low security and processing efficiency, poor flexibility, lack of effective encryption protection during data transmission, and are prone to unauthorized access or tampering. At the same time, the bill processing process is rigid and difficult to adapt to the personalized needs of different users or business scenarios for bill formats and transmission methods. Therefore, it is difficult to provide efficient and flexible bill data services while ensuring data security.

[0032] Specifically, the three laws, namely, the Data Security Law of the People's Republic of China, the Personal Information Protection Law of the People's Republic of China and the Cybersecurity Law of the People's Republic of China, constitute a solid foundation in the field of data protection, jointly promoting the improvement of my country's top-level design and overall layout in the field of cybersecurity, and establishing a legal framework for data security protection. Data security refers to taking necessary measures to ensure that data is in a state of effective protection and legal use, while having the ability to ensure a continuous state of security. In order to regulate data outbound activities, protect personal information rights and interests, safeguard national security and social public interests, and promote the safe and free flow of data across borders, the Measures for Data Outbound Security Assessment clearly require that when data processors and overseas recipients sign legal documents, they must specify in detail the responsibilities and obligations of data security protection, including but not limited to the purpose, method and scope of data outbound, the overseas recipient's intention to use the data and the method of processing the data, etc.

[0033] Foreign airline service billing data products include a variety of business types, such as Passenger Name Record (PNR), namely PNR booking, tickets, additional services, New Distribution Capability (NDC), branded fares, etc. Its data contains detailed transaction records, with high accuracy and reliability, privacy and security, and has diverse sources and formats, which contains rich business value. The above characteristics make billing data an important basis for foreign airlines to conduct financial management, risk control and business decision-making. However, the traditional billing data product generation function generates billing file names, file types and sending methods for all users under the same business type in a fixed mode. Although the above standardized operations improve the convenience and consistency of operations, with the continuous expansion of billing business types and users' personalized needs for bill formats, the current system has certain limitations in maintainability, scalability, flexibility and manageability, making it difficult to adapt to the rapidly changing needs of the market.

[0034] According to an embodiment of the present disclosure, a method embodiment of a bill data processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0035] The method embodiment can be executed in an electronic device or a similar computing device including a memory and a processor. Taking running on a computer terminal as an example, the computer terminal may include one or more processors (processors may include but are not limited to central processing units (CPU), graphics processing units (GPU), digital signal processing (DSP) chips, microprocessors (MCU), programmable logic devices (Field Programmable Gate Array, FPGA), neural network processors (Neural-network Processor Unit, NPU), tensor processors (TensorProcessing Unit, TPU), artificial intelligence (Artificial Intelligence, AI) type processors and other processing devices) and a memory for storing data. Optionally, the above-mentioned computer terminal may also include a transmission device, an input and output device, and a display device for communication functions. It can be understood by those of ordinary skill in the art that the above-mentioned structural description is only for illustration, and it does not limit the structure of the above-mentioned computer terminal. For example, the computer terminal may also include more or fewer components than the above-mentioned structural description, or have a configuration different from the above-mentioned structural description.

[0036] The memory can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the bill data processing method in the embodiment of the present disclosure. The processor executes various functional applications and data processing by running the computer program stored in the memory, that is, the above-mentioned bill data processing method is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories can be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0037] The transmission device is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device can be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet wirelessly.

[0038] The display device may be, for example, a touch screen type liquid crystal display (LCD) and a touch display (also referred to as a "touch screen" or "touch display screen"). The liquid crystal display may enable a user to interact with a user interface of a mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI), and a user may interact with the GUI by finger contacts and / or gestures on a touch-sensitive surface, wherein the human-computer interaction functions here may optionally include the following interactions: creating web pages, drawing, word processing, making electronic documents, games, video conferencing, instant messaging, sending and receiving emails, call interfaces, playing digital videos, playing digital music and / or web browsing, etc. The executable instructions for executing the above human-computer interaction functions are configured / stored in a computer program product or readable storage medium executable by one or more processors.

[0039] Figure 1 is a flow chart of a bill data processing method according to one embodiment of the present disclosure, such as Figure 1 As shown, the method comprises the following steps:

[0040] Step S11, obtaining an original bill file, wherein the original bill file includes original service bill data corresponding to the target user;

[0041] Step S12, determining metadata information based on the original bill file, wherein the metadata information is used to indicate a mapping relationship between a target user identifier and an absolute file path;

[0042] Step S13, generating a target billing file according to the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user;

[0043] Step S14, sending the target bill file to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

[0044] The above metadata information refers to the key attribute data about the file generated and maintained by the system during the processing of the original bill file, including but not limited to the target user ID and the absolute path of the original bill file on the server. By analyzing and extracting specific patterns in the file name and its storage path, the system can build a mapping table to associate specific bill files with the corresponding target users.

[0045] The above absolute file path refers to the complete path from the root directory of the server to the storage of the specific original bill file, including each level of directory from the root directory to the file, as well as the name of the file. It is the unique identifier for the system to locate a specific file on the server or storage device. For example, in a Windows system, the absolute path of a file may be "C:\Users\Username\Documents\file.txt"; while in a Unix-like system, it may be " / home / username / Documents / file.txt".

[0046] The candidate transmission methods mentioned above refer to a variety of methods pre-set in the system for sending bill files to target users, including but not limited to email, Secure File Transfer Protocol (SFTP), File Transfer Protocol (FTP), Hypertext Transfer Protocol Secure (HTTPS), etc. Users or system administrators can select one of them as the target transmission method based on actual needs, security considerations or network environment to ensure that the transmission of bill files meets both efficiency requirements and security specifications.

[0047] Exemplarily, in the process of bill data processing, the original bill data corresponding to the target user is first obtained. Assuming that the target user is identified as "AA" and its file absolute path is " / DATA / prod_data / bidt / 202401 / AA_Bidt202401.txt", a key-value mapping relationship between the target user and the absolute file path can be constructed, that is, the key "AA" is mapped to the value " / DATA / prod_data / bidt / 202401 / AA_Bidt202401.txt". Further, based on the above mapping relationship, the encrypted service bill data corresponding to the target user is generated. Finally, the obtained encrypted service bill data is sent to the target user using SFTP.

[0048] Based on the above steps S11 to S15, by obtaining the original service bill data corresponding to the target user, and determining the metadata information based on the original bill data, and then generating a target bill file based on the metadata information, and finally using the target transmission method to send the target bill file to the target user, the purpose of efficiently and securely transmitting the target user's service bill is achieved, thereby achieving the technical effect of improving the security, efficiency and flexibility of bill data processing, and thus solving the technical problems of insufficient security, low processing efficiency and poor flexibility of the bill data processing methods provided in the relevant technologies.

[0049] The following is a further introduction to the bill data processing method in the embodiment of the present disclosure.

[0050] Optionally, in step S11, obtaining the original bill file includes:

[0051] Step S111, obtaining original file information from the configuration center, wherein the original file information includes: service bill type, original bill path and original bill format;

[0052] Step S112, determining a preset file directory based on the original bill path;

[0053] Step S113, scanning the preset file directory to obtain the original bill file.

[0054] The above-mentioned service bill types refer to various bill categories predefined in the system. The above-mentioned bill categories are usually represented by numbers or codes, corresponding to specific service types in the airline business (such as 1-PNR booking, 2-ticket sales, 3-additional services, 4-NDC transactions, etc.), and are used to simplify bill identification and classification in the logical processing process.

[0055] The original bill path refers to the specific location information of the original bill file on the server or storage device, that is, the complete path from the server root directory to the directory where the original bill file is stored. For example, " / DA TA / prod_data / bidt / YYYYMM / DD" represents the standard path for storing bill data of a certain month and day, where "YYYYMM" and "DD" represent the specific year, month and day.

[0056] The above original bill format refers to the regular expression used to describe the naming and formatting rules of the original bill file, which is the basis for the system to check and verify whether the file belongs to a specific bill type. For example, "[AZ]{2}_Bidt[0-9]{6}.txt" is a regular expression, which means that the file name should start with two uppercase letters, followed by the "_Bidt" prefix, followed by 6 digits, and finally the .txt extension, which is used to ensure that the files processed by the system comply with the specified bill file naming rules and format requirements.

[0057] The above-mentioned preset file directory refers to the specific server directory determined by the system based on the original bill path information and used to store and retrieve specific types of original bill files. When the system obtains the original file information, namely the service bill type, original bill path and original bill format, from the configuration center, it will determine a preset file directory based on the original bill path, which contains all bill files related to the service bill type.

[0058] For example, the original file information obtained from the configuration center is shown in Table 1:

[0059] Table 1 Original file information

[0060] Field Name Field Type Fields Service Bill Type character varying(2) 1 Original bill path character varying(50) / DATA / prod_data / bidt / YYYYMM / DD Original bill format character varying(50) [AZ]{2}_Bidt[0-9]{6}.txt

[0061] In Table 1, the service bill type is 1, i.e., PNR booking; the original bill path is " / DATA / prod_data / bidt / YYYYMM / DD"; the original bill format is "[AZ]{2}_Bidt[0-9]{6}.txt"; character varying (*) indicates a variable-length character field, whose maximum length is * characters.

[0062] For example, assuming that the original bill path information is " / DATA / prod_data / bidt / YYYYMM / DD", where "YYYYMM" and "DD" represent year, month and day, the system will use " / DATA / prod_data / bidt / " as the basic path of the preset file directory. If the current billing cycle is the PNR booking bill on January 10, 2024, the system will use " / DATA / prod_data / bidt / 202401 / 10" as the preset file directory, and scan the preset file directory to obtain the original bill file.

[0063] Based on the above optional embodiments, through the original file information provided by the configuration center, the system can not only intelligently identify and locate original bill files of specific types and formats, but also determine the preset file directory based on the original bill path, and further efficiently scan the directory, so as to accurately obtain the original bill files to be processed, thereby improving the automation level of bill data processing, reducing errors and redundant work, and at the same time, improving the efficiency and security of the entire bill data processing process.

[0064] Optionally, in step S12, determining metadata information based on the original bill file includes:

[0065] Step S121, obtaining regularized expression information based on the original bill format;

[0066] Step S122, using the regularized expression information and the service bill type to verify the original bill file and obtain a file verification result;

[0067] Step S123, in response to determining that the original bill file passes the verification based on the file verification result, determining the target user identifier based on the file identifier of the original bill file, and determining the absolute file path based on the original bill path, the file identifier of the original bill file, and the file format;

[0068] Step S124, determining metadata information according to the target user identifier and the absolute path of the file.

[0069] For example, assuming that the monthly bill for AA airline PNR booking service is located in the directory of " / DATA / prod_data / bidt / 202401", the file name and format are "AA_Bidt202401.txt", and the acquisition module scans the directory file and compares it with the original file information. Assuming that it meets the regular expression "[0-9A-Z]{2}_Bidt[0-9]{6}.txt" under the service bill type "1-booking", the file is matched to this service bill type, and the first two fields in the file name are intercepted as the two-character code corresponding to the airline user, and then the airline user and the absolute path of the file are stored in the form of key-value as shown in Table 2.

[0070] Table 2 Metadata information

[0071] key value AA / DATA / prod_data / bidt / 202401 / AA_Bidt202401.txt

[0072] In Table 2, "AA" represents the two-letter code corresponding to the airline user, that is, the user ID; " / DATA / prod_data / bid t / 202401 / AA_Bidt202401.txt" represents the absolute path of the file corresponding to "AA".

[0073] Based on the above optional embodiments, through the above verification processing, it is possible to ensure that the processed original bill file meets the predefined format and type requirements, thereby avoiding erroneous files from being included in the processing flow. At the same time, based on the files that have passed the verification, the system can accurately identify the location information of the target user and the file, thereby improving the accuracy and efficiency of data processing, and also enhancing data security and the reliability of bill generation.

[0074] Optionally, in step S13, generating a target bill file according to the metadata information includes:

[0075] Step S131, obtaining user file information from the configuration center, wherein the user file information includes: a processing date field;

[0076] Step S132, in response to determining that the original bill file is in an unprocessed state based on the processing date field, constructing a file matching relationship using metadata information, wherein the file matching relationship is used to represent an association relationship between the original bill file and the target bill file;

[0077] Step S133, encrypting the original bill file based on the file matching relationship to obtain an encryption result;

[0078] Step S134, formatting the encryption result to generate a target billing file.

[0079] The above-mentioned user file information refers to the file processing configuration data related to each user stored in the system, covering the personalized needs and preference settings of the account, ensuring that the system can generate and send bills according to the specific instructions and requirements of each user.

[0080] Specifically, user file information includes but is not limited to identifier, transmission method, user identifier, formal file format, service bill type, transmission destination, and processing date field. Among them, the identifier is a system self-valued value, has no business meaning, and is used to identify the uniqueness of each piece of data; the formal file format refers to the formal file name and file format sent to the user with custom settings, which is used to meet personalized needs; the transmission method includes but is not limited to email transmission (M) and SFTP transmission (F); the transmission destination refers to the user recipient address information, which is the user mailbox information for email transmission and the transit server address path for SFTP transmission; the processing date field refers to the latest processing date of each file recorded by the system, which is used to track and manage the processing status of the file.

[0081] For example, the latest processing date in the configuration center user file information is used to check the processing status. If the current execution date is less than or equal to the latest processing date, it means that the original file has been processed and no further processing is required. Otherwise, it means that the file corresponding to the current date has not been processed. In this case, the key-value information under each service bill type needs to be associated with the original bill file to the target bill file through the service bill type and user identifier.

[0082] The above-mentioned format processing refers to a series of processing operations performed by the system on the encryption results after the file is encrypted, according to the formal file format requirements in the user's file information, to meet the user's personalized needs and transmission format requirements, including but not limited to file renaming, file compression, adjusting the arrangement format of file content, converting file encoding or adding additional metadata, etc.

[0083] For example, if the user requests that the file be sent in ".zip" format, the system will compress the encrypted file; if the user has specific file naming requirements, the system will modify the file name as required; if the user's file information contains a custom file content structure, the system will also adjust the encrypted file content to meet specific format requirements.

[0084] For example, the user file information obtained from the configuration center is shown in Table 3:

[0085] Table 3 User file information

[0086] Field Name Field Type Fields Identifier integer 1 Transmission method character varying(2) F User ID character varying(3) AA Formal document format character varying(50) AA_BidtYYYYMM_encrypt.zip Service Bill Type character varying(2) 1 Transfer destination character varying(500) / bidtfile / Processing Date date 2024-01-01

[0087] In Table 3, the identifier of the current user file information is 1; the transmission method is SFTP; the user identifier is "AA"; the official file format is "AA_BidtYYYYMM_encrypt.zip"; the service bill type is 1, that is, PNR booking; the transmission destination is " / bidtfile / "; the latest processing date is "2024-01-01", and its field type is "date".

[0088] Based on the above optional embodiment, by obtaining user file information from the configuration center and checking the processing date field, the system can intelligently determine whether the original bill file is in an unprocessed state, and then use the retained metadata information to build a file matching relationship. At the same time, the original bill file is encrypted based on the constructed matching relationship to ensure the security of data transmission. After obtaining the encryption processing result, it is formatted according to the formal file format requirements specified in the user file information, and finally a target bill file that meets the user's personalized needs is generated, which not only ensures the automation and efficiency of data processing, but also enhances the security of data and meets the user's diverse needs for bill files, realizing an effective combination of flexible, secure, automated and personalized services.

[0089] Optionally, in step S133, the original bill file is encrypted based on the file matching relationship, and the encryption result obtained includes:

[0090] Step S1331, in response to the file matching relationship being verified, obtaining user key information;

[0091] Step S1332, encrypt the original bill file using a symmetric encryption algorithm and user key information to obtain an encryption result.

[0092] Exemplarily, when the matching relationship between the original bill file and the target bill file is passed, that is, the above two bill files are successfully mapped, the user key information obtained by the configuration center and the internationally accepted symmetric encryption algorithm (Advanced Encryption Standard with 256-bit key, AES-256) are used to encrypt the original bill file of the absolute path in the associated information. In the process of encryption using AES-256, the Cipher Block Chaining (CBC) mode is used to enhance encryption security. First, a random initialization vector (IV) is selected, and the IV is used to perform an XOR operation with the first plaintext data block in the original bill data to ensure that even the same plaintext data will produce different ciphertext outputs, thereby improving the randomness and security of encryption. Next, for each data block, the result obtained by performing an XOR operation with the ciphertext of the previous data block is encrypted by the AES-256 encryption algorithm. The encryption process of the first data block uses IV to perform XOR with the plaintext before encryption. The output of each encrypted data block becomes the input for the encryption of the next data block, forming a chain encryption process, thereby ensuring that even similar plaintext data blocks have different encrypted outputs due to their different relationships with the current and previous ciphertext blocks, thereby increasing the complexity and security of data encryption.

[0093] Based on the above optional embodiment, the original bill file is encrypted using a symmetric encryption algorithm and user key information, which can ensure the integrity and security of the original bill file during transmission.

[0094] Optionally, in step S1331, obtaining user key information includes: obtaining user key information from a configuration center, or generating user key information using random characters.

[0095] For example, before performing the encryption operation, the system will obtain the user key information from the configuration center. If the configuration center has the key information corresponding to the user, it will directly call this key for encryption. If the configuration center does not pre-store the user key information, the key generation process will be automatically triggered, and a new 256-bit key will be generated by using random characters to encrypt the original bill file.

[0096] Based on the above optional embodiments, for users who already have secret keys, directly using their secret keys can save resources and improve efficiency. For new users or when secret keys are missing, automatically generating secret keys and properly storing them can ensure the security of data transmission, thereby not only simplifying the secret key management process, but also enhancing the flexibility and security of bill data processing.

[0097] Optionally, the bill data processing method further includes: in response to successfully sending the target bill file to the target user using the target transmission method, updating the processing date field.

[0098] Exemplarily, when the target bill file is successfully sent to the target user using the transmission method selected by the target user (such as email or SFTP), the system will immediately update the "processing date field" related to the bill file, that is, update the latest processing date with the current execution date.

[0099] Based on the above optional embodiment, by automatically updating the processing date field, the life cycle of the bill file can be effectively managed, and the efficiency and accuracy of bill data processing can be improved.

[0100] Figure 2 is a schematic diagram of a bill data processing method according to one embodiment of the present disclosure, such as Figure 2 As shown, the method includes the following steps: first, the original bill data is obtained from the specified directory, and the user file generation status is checked. Further, when the original bill file matches the target bill file, the file encryption, file format processing, and file renaming are completed to generate a formal bill file. Finally, the formal bill file is sent to the target user, and the user file processing status is updated.

[0101] Exemplarily, the original service bill files of various businesses generated by foreign airline billing are obtained from the designated directory of the billing cycle, and the file format is checked. Furthermore, the latest processing date of the user file is checked, and whether the file has been generated is determined based on the date. Subsequently, the collected original service bill files of various businesses are associated and matched with the billing type. For the successfully matched files, the files are encrypted, and the format is processed and renamed according to the business requirements to generate the formal bill file. Finally, according to the transmission form selected by the user, the corresponding formal bill file is sent to the target user, and the latest processing date of the corresponding file is updated.

[0102] Figure 3 is a schematic diagram of a file collection unit according to one embodiment of the present disclosure, such as Figure 3 As shown, in the file collection unit, first, the original bill file is obtained from the specified directory through the configuration center; secondly, the file name format is checked according to the regular expression. If the check result is passed, the original bill file is input into the file processing unit; if the check result is not passed, the process ends.

[0103] Figure 4 is a schematic diagram of a file processing unit according to one embodiment of the present disclosure, such as Figure 4As shown, in the file processing unit, first, the user file generation status is checked based on the configuration center. If the user file has been generated, the current process is terminated; if the user file has not been generated, when the original bill file matches the account opening type, the file classification is completed. When the original bill file does not match the target bill file, the current process is terminated. Furthermore, when the original bill file matches the target bill file, the user key is read. If the user key does not exist, a new user key is generated and stored in the configuration center. If the user key exists, the file is encrypted based on the user key. After the file is encrypted, determine whether a custom file name is required. If so, change the file name according to specific requirements; otherwise, determine whether a custom file format is required. If a custom file format is required, customize the file format according to specific requirements. Finally, input the data processed as above into the file sending unit.

[0104] Figure 5 is a schematic diagram of a file sending unit according to one embodiment of the present disclosure, such as Figure 5 As shown, in the file sending unit, the transmission method is first obtained based on the configuration center, where the transmission methods are divided into two types: the file is sent to the user via email and the file is sent to the user via a secure file transfer protocol; further, after the file is sent to the customer via the transmission method, the user file processing status is updated and the latest user file processing status is stored in the configuration center.

[0105] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present disclosure, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0106] In the embodiments of the present disclosure, a bill data processing device is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0107] Figure 6 is a structural block diagram of a bill data processing device according to one embodiment of the present disclosure, such as Figure 6 As shown, the device comprises:

[0108] An acquisition module 601 is used to acquire an original billing file, wherein the original billing file includes original service billing data corresponding to the target user;

[0109] A determination module 602 is used to determine metadata information based on the original bill file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path;

[0110] A generating module 603 is used to generate a target billing file according to the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user;

[0111] The sending module 604 is used to send the target bill file to the target user by using the target transmission mode, wherein the target transmission mode is determined from a plurality of candidate transmission modes.

[0112] Optionally, the acquisition module 601 is also used to: obtain original file information from the configuration center, wherein the original file information includes: service bill type, original bill path and original bill format; determine the preset file directory based on the original bill path; scan and process the preset file directory to obtain the original bill file.

[0113] Optionally, the determination module 602 is also used to: obtain regularized expression information based on the original bill format; use the regularized expression information and the service bill type to verify the original bill file to obtain a file verification result; in response to determining that the original bill file has passed the verification based on the file verification result, determine the target user identifier based on the file identifier of the original bill file, and determine the absolute file path based on the original bill path, the file identifier and the file format of the original bill file; determine the metadata information based on the target user identifier and the absolute file path.

[0114] Optionally, the generation module 603 is also used to: obtain user file information from the configuration center, wherein the user file information includes: a processing date field; in response to determining that the original bill file is in an unprocessed state based on the processing date field, construct a file matching relationship using metadata information, wherein the file matching relationship is used to represent the association relationship between the original bill file and the target bill file; encrypt the original bill file based on the file matching relationship to obtain an encryption result; format the encryption result to generate a target bill file.

[0115] Optionally, the generation module 603 is further used to: obtain user key information in response to the file matching relationship being verified; and encrypt the original bill file using a symmetric encryption algorithm and the user key information to obtain an encryption result.

[0116] Optionally, the generating module 603 is further used to: obtain user key information from a configuration center, or generate user key information using random characters.

[0117] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0118] According to another aspect of an embodiment of the present disclosure, an electronic device is also provided, including: a processor; a memory for storing processor executable instructions; wherein the processor is configured to execute instructions to implement the bill data processing method in the embodiment of the present disclosure.

[0119] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0120] S1, obtaining an original bill file, wherein the original bill file includes original service bill data corresponding to the target user;

[0121] S2, determining metadata information based on the original bill file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path;

[0122] S3, generating a target billing file based on the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user;

[0123] S4, sending the target bill file to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

[0124] According to another aspect of an embodiment of the present disclosure, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein when the executable program runs, the device where the storage medium is located is controlled to execute the bill data processing method in the embodiment of the present disclosure.

[0125] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0126] S1, obtaining an original billing file, wherein the original billing file includes original service billing data corresponding to the target user;

[0127] S2, determining metadata information based on the original bill file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path;

[0128] S3, generating a target billing file based on the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user;

[0129] S4, sending the target bill file to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

[0130] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0131] According to another aspect of the embodiments of the present disclosure, a computer program product is further provided. The computer program product includes computer instructions. When the computer instructions are executed by a processor, the bill data processing method in the embodiments of the present disclosure is implemented.

[0132] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0133] S1, obtaining an original billing file, wherein the original billing file includes original service billing data corresponding to the target user;

[0134] S2, determining metadata information based on the original bill file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path;

[0135] S3, generating a target billing file based on the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user;

[0136] S4, sending the target bill file to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

[0137] The serial numbers of the above-mentioned embodiments of the present disclosure are only for description and do not represent the advantages or disadvantages of the embodiments.

[0138] In the above embodiments of the present disclosure, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0139] In the several embodiments provided in the present disclosure, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

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

[0142] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0143] The above is only a preferred embodiment of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present disclosure. These improvements and modifications should also be regarded as the scope of protection of the present disclosure.

Claims

1. A bill data processing method, characterized in that: include: Obtaining an original billing file, wherein the original billing file includes original service billing data corresponding to the target user; Determining metadata information based on the original bill file, wherein the metadata information is used to represent a mapping relationship between a target user identifier and an absolute file path; Generate a target billing file according to the metadata information, wherein the target billing file contains encrypted service billing data corresponding to the target user; The target bill file is sent to the target user using a target transmission method, wherein the target transmission method is determined from a plurality of candidate transmission methods.

2. The bill data processing method according to claim 1, characterized in that: Obtaining the original bill file includes: Obtaining original file information from the configuration center, wherein the original file information includes: service bill type, original bill path, and original bill format; Determine a preset file directory based on the original bill path; The preset file directory is scanned to obtain the original bill file.

3. The bill data processing method according to claim 2, characterized in that: Determining the metadata information based on the original bill file includes: Obtaining regularized expression information based on the original bill format; Using the regularized expression information and the service bill type to verify the original bill file, to obtain a file verification result; In response to determining that the original bill file passes verification based on the file verification result, determining the target user identifier based on the file identifier of the original bill file, and determining the absolute file path based on the original bill path, the file identifier and the file format of the original bill file; The metadata information is determined according to the target user identifier and the absolute path of the file.

4. The bill data processing method according to claim 1, characterized in that: Generating the target bill file according to the metadata information includes: Acquire user file information from a configuration center, wherein the user file information includes: a processing date field; In response to determining that the original bill file is in an unprocessed state based on the processing date field, constructing a file matching relationship using the metadata information, wherein the file matching relationship is used to represent an association relationship between the original bill file and the target bill file; Encrypting the original bill file based on the file matching relationship to obtain an encryption result; The encryption result is formatted to generate the target bill file.

5. The bill data processing method according to claim 4, characterized in that: The original bill file is encrypted based on the file matching relationship, and the encryption result obtained includes: In response to the file matching relationship being verified, obtaining user key information; The original bill file is encrypted using a symmetric encryption algorithm and the user secret key information to obtain the encryption result.

6. The bill data processing method according to claim 5, characterized in that: Obtaining the user key information includes: The user key information is obtained from the configuration center, or the user key information is generated using random characters.

7. The bill data processing method according to claim 4, characterized in that: The method further comprises: In response to successfully sending the target bill file to the target user by using the target transmission method, the processing date field is updated.

8. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the bill data processing method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is run, the device where the storage medium is located is controlled to execute the bill data processing method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The computer program product comprises computer instructions, which, when executed by a processor, implement the bill data processing method described in any one of claims 1 to 7.

Images