Historical data query method and device, electronic equipment and storage medium

Abstract

The invention discloses a historical data query method and device, electronic equipment and a storage medium, and relates to the technical field of data processing.The query method comprises the steps that a historical data query request is received, and a historical record is queried on a query system based on query information, determining an authorized user identifier and an authorized system code corresponding to the historical record, determining a current user account logging in the query system, and determining a user identifier and a system code corresponding to the current user account; and when it is detected that an authorized user identifier and an authorized system code matched with both the user identifier and the system code exist, sending historical records corresponding to the authorized user identifier and the authorized system code to a target communication address associated with the current user account. According to the method and the device, the technical problem of passenger information leakage easily caused by more users having the authority to query historical data in related technologies is solved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and more specifically, to a historical data query method and device, electronic equipment, and storage medium. Background Art

[0002] Currently, aviation systems generally perform historical data queries based on host technology to determine whether users of the aviation system (i.e., airline staff) have the authority to query a certain record. This is generally done based on organizational attribute fields such as basic OFFICE (i.e., the airline's department code), airline code, and airport three-letter code.

[0003] For example, two different Agents (i.e., work numbers in the aviation system, used to distinguish authorized users), such as Agent A and Agent B, as long as they belong to the same OFFICE, are deemed to have the same PNR (Passenger Name Record) historical data query permissions, that is, the information visible to Agent A is also visible to Agent B. For two different Agents A and Agent B, as long as they belong to the same airline code, they are deemed to have the same ticket historical data query permissions; for two different Agents A and Agent B, as long as they belong to the same airport three-letter code, they are deemed to have the same historical check-in record query permissions.

[0004] However, the number of agents belonging to the same OFFICE, the same airline code or the same airport code may be a few, dozens, or even hundreds. From the above situation, it can be seen that the PNR record that records the passenger's reservation information can be queried by Agent A (i.e., the booker, who can be regarded as the original person who accepts the passenger's reservation commission) who created the PNR record and all agents belonging to the same OFFICE as Agent A, usually dozens or even hundreds of agents. The passenger's ticket information can be queried by Agent A (i.e., the issuer) who created the ticket and other agents belonging to the same OFFICE as Agent A and other agents with the same airline code as the ticket. The passenger's check-in record can be queried by Agent A (i.e., the check-in staff) who handles the check-in operation for the passenger's ticket and other agents belonging to the same airport code as Agent A.

[0005] Therefore, the current historical data query will make a large number of agents have the right to query a certain record at the same time, which may easily lead to the leakage of passenger information.

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

[0007] The embodiments of the present invention provide a method and device for querying historical data, an electronic device and a storage medium, so as to at least solve the technical problem in the related art that there are many users with the authority to query historical data, which easily leads to leakage of passenger information.

[0008] According to one aspect of an embodiment of the present invention, a method for querying historical data is provided, comprising: receiving a historical data query request, wherein the historical data query request comprises at least: query information; based on the query information, querying historical records on a query system, and determining an authorized user identifier and an authorized system code corresponding to the historical records; determining a current user account logged into the query system, and determining a user identifier and a system code corresponding to the current user account; and upon detecting the existence of an authorized user identifier and an authorized system code that match both the user identifier and the system code, sending the historical records corresponding to the authorized user identifier and the authorized system code to a target communication address associated with the current user account.

[0009] Furthermore, before receiving the historical data query request, it also includes: receiving a user registration request initiated by a user through a user terminal, wherein the user registration request includes at least: a user identity identifier, a user terminal number, and a communication address; initiating a binding request when the user identity identifier, the user terminal number, and the communication address are verified; receiving the user identifier and the system code returned by the user terminal based on the binding request, and initiating a selection request when there are multiple pairs of user identifiers and system codes; receiving the target user identifier and the target system code returned by the user terminal based on the selection request, and generating a user account for the user, wherein the user account is the credential for the user to log in to the query system to query historical data.

[0010] Further, in the case where the historical data query request is a historical passenger booking record query request, the query information includes at least: passenger name, flight number, flight date, and based on the query information, querying the historical records on the query system, and determining the authorized user identifier and the authorized system code corresponding to the historical records, includes: constructing a query condition based on the query information, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; using the query condition, querying the historical passenger booking records on the query system; in the case where at least one historical passenger booking record is queried, obtaining the authorized user identifier and the authorized system code that created or modified the historical passenger booking record from a first preset database, wherein the first preset database stores multiple historical passenger booking records, and each historical passenger booking record is associated with all user identifiers and all system codes that created or modified the historical passenger booking record.

[0011] Further, in the case where the historical data query request is a historical electronic ticket face query request, the query information at least includes: the electronic ticket number, based on the query information, querying the historical record on the query system, and determining the authorized user identifier and the authorization system code corresponding to the historical record, and also includes: based on the query information, constructing a query condition, wherein the query condition is a condition consisting of the electronic ticket number; using the query condition, querying the historical electronic ticket face information on the query system; in the case where the historical electronic ticket face information is queried, obtaining the authorized user identifier and the authorization system code for creating the historical electronic ticket face information from a second preset database, wherein the second preset database stores multiple historical electronic ticket face information, and each historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information.

[0012] Further, in the case where the historical data query request is a historical passenger check-in record query request, the query information includes at least: passenger name, flight number, flight date, and based on the query information, querying the historical records on the query system, and determining the authorized user identifier and the authorized system code corresponding to the historical records, further includes: constructing query conditions based on the query information, wherein the query conditions are conditions consisting of the passenger name, flight number, and flight date; using the query conditions, querying the historical passenger check-in records on the query system; when at least one historical passenger check-in record is queried, obtaining the authorized user identifier and the authorized system code for creating the historical passenger check-in record from a third preset database, wherein the third preset database stores multiple historical passenger check-in records, and each historical passenger check-in record is associated with all user identifiers and all system codes for creating the historical passenger check-in record.

[0013] Furthermore, after determining the user identifier and system code corresponding to the current user account, it also includes: matching the user identifier and system code with the authorized user identifier and authorized system code corresponding to each historical record queried; in the event that there is no authorized user identifier and authorized system code corresponding to any historical record that matches both the user identifier and the system code, returning an unauthorized query result; in the event that there is an authorized user identifier and authorized system code corresponding to a historical record that matches both the user identifier and the system code, determining the historical record indicated by the authorized user identifier and authorized system code that matches both the user identifier and the system code as the target historical record.

[0014] Furthermore, after determining the historical record indicating the authorized user identification and the authorized system code that match both the user identification and the system code as the target historical record, it also includes: encrypting the target historical record to obtain an encrypted historical record; naming the encrypted historical record based on the query information and the query time to obtain a record name; generating a decryption password for the encrypted historical record, and generating prompt information based on the record name; sending the prompt information and the decryption password to the user terminal number associated with the current user account, and sending the encrypted historical record to the target communication address associated with the current user account.

[0015] According to another aspect of an embodiment of the present invention, a historical data query device is also provided, including: a receiving unit, used to receive a historical data query request, wherein the historical data query request includes at least: query information; a query unit, used to query historical records on a query system based on the query information, and determine an authorized user identifier and an authorized system code corresponding to the historical records; a determination unit, used to determine a current user account that logs into the query system, and determine a user identifier and a system code corresponding to the current user account; and a sending unit, used to send the historical records corresponding to the authorized user identifier and the authorized system code to a target communication address associated with the current user account when detecting the existence of an authorized user identifier and an authorized system code that match both the user identifier and the system code.

[0016] Furthermore, the query device also includes: a first receiving module, used to receive a user registration request initiated by a user through a user terminal before receiving a historical data query request, wherein the user registration request includes at least: a user identity identifier, a user terminal number, and a communication address; a first initiating module, used to initiate a binding request when the user identity identifier, the user terminal number, and the communication address are verified; a second receiving module, used to receive the user identifier and system code returned by the user terminal based on the binding request, and to initiate a selection request when there are multiple pairs of user identifiers and system codes; a third receiving module, used to receive the target user identifier and target system code returned by the user terminal based on the selection request, and generate a user account for the user, wherein the user account is the credential for the user to log in to the query system to query historical data.

[0017] Further, in the case where the historical data query request is a historical passenger booking record query request, the query information includes at least: passenger name, flight number, and flight date, and the query unit includes: a first construction module, used to construct a query condition based on the query information, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; a first query module, used to use the query condition to query the historical passenger booking record on the query system; a first acquisition module, used to, when at least one historical passenger booking record is queried, obtain an authorized user identifier and an authorized system code that have created or modified the historical passenger booking record from a first preset database, wherein the first preset database stores multiple historical passenger booking records, and each historical passenger booking record is associated with all user identifiers and all system codes that have created or modified the historical passenger booking record.

[0018] Further, in the case where the historical data query request is a historical electronic ticket face query request, the query information at least includes: the electronic ticket number. Based on the query information, the query unit further includes: a second construction module, which is used to construct a query condition based on the query information, wherein the query condition is a condition composed of the electronic ticket number; a second query module, which is used to use the query condition to query the historical electronic ticket face information on the query system; a second acquisition module, which is used to obtain the authorized user identifier and the authorized system code for creating the historical electronic ticket face information from a second preset database when the historical electronic ticket face information is queried, wherein the second preset database stores multiple historical electronic ticket face information, and each historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information.

[0019] Further, in the case where the historical data query request is a historical passenger check-in record query request, the query information includes at least: passenger name, flight number, and flight date, and the query unit also includes: a third construction module, used to construct a query condition based on the query information, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; a third query module, used to use the query condition to query the historical passenger check-in records on the query system; a third acquisition module, used to obtain the authorized user identifier and authorized system code for creating the historical passenger check-in record from a third preset database when at least one historical passenger check-in record is queried, wherein the third preset database stores multiple historical passenger check-in records, and each historical passenger check-in record is associated with all user identifiers and all system codes for creating the historical passenger check-in record.

[0020] Furthermore, the query device also includes: a first matching module, which is used to match the user identifier and system code with the authorized user identifier and authorized system code corresponding to each historical record queried after determining the user identifier and system code corresponding to the current user account; a first return module, which is used to return an unauthorized query result if there is no authorized user identifier and authorized system code corresponding to any historical record that matches the user identifier and system code; and a first determination module, which is used to determine the historical record indicated by the authorized user identifier and authorized system code that matches both the user identifier and system code as the target historical record if there is an authorized user identifier and authorized system code corresponding to the historical record that matches the user identifier and system code.

[0021] Furthermore, the query device also includes: a first encryption module, which is used to encrypt the target historical record after determining the historical record that matches the authorized user identification and the authorized system code indication with both the user identification and the system code as the target historical record, so as to obtain an encrypted historical record; a first naming module, which is used to name the encrypted historical record based on the query information and the query time, so as to obtain a record name; a first generation module, which is used to generate a decryption password for the encrypted historical record, and to generate prompt information based on the record name; a first sending module, which is used to send the prompt information and the decryption password to the user terminal number associated with the current user account, and to send the encrypted historical record to the target communication address associated with the current user account.

[0022] According to another aspect of an embodiment of the present invention, a computer program product is also provided, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the historical data query method described in any one of the above items is implemented.

[0023] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned historical data query methods.

[0024] In the present invention, a historical data query request is received, and based on the query information, the historical records are queried on the query system, and the authorized user identifier and the authorized system code corresponding to the historical records are determined, the current user account logged into the query system is determined, and the user identifier and the system code corresponding to the current user account are determined. When it is detected that there is an authorized user identifier and an authorized system code that match both the user identifier and the system code, the historical records corresponding to the authorized user identifier and the authorized system code are sent to the target communication address associated with the current user account, thereby solving the technical problem in the related art that there are many users with the authority to query historical data, which easily leads to leakage of passenger information.

[0025] In the present invention, by detecting whether the user identification and system code of the current user account match the authorized user identification and authorized system code of the queried historical records, and after a successful match, the matching historical records are sent to the target communication address associated with the current user account, accurate authorized query of historical data is achieved, the security and privacy of the data are effectively guaranteed, and the technical effect of enhancing the protection of passengers' privacy information is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] Figure 1 is a flowchart of an optional historical data query method according to an embodiment of the present invention;

[0028] Figure 2 is a schematic diagram of an optional passenger booking record query process according to an embodiment of the present invention;

[0029] Figure 3 is a schematic diagram of an optional electronic ticket face query process according to an embodiment of the present invention;

[0030] Figure 4 is a schematic diagram of an optional passenger check-in record query process according to an embodiment of the present invention;

[0031] Figure 5 is a schematic diagram of an optional historical data query device according to an embodiment of the present invention;

[0032] Figure 6 The present invention is a hardware structure block diagram of an electronic device (or mobile device) for a method for querying historical data according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention 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 interchanged where appropriate, so that the embodiments of the present invention 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.

[0035] To facilitate those skilled in the art to understand the present invention, some terms or nouns involved in the embodiments of the present invention are explained below:

[0036] Aviation system: a system used for ticket booking and sales, flight control, and departure check-in operations.

[0037] PID: Abbreviation of Physical Device Identifier, terminal ID (identification) in aviation system, used to distinguish the identity of the terminal that transmits information to the background server, usually represented by 2-6 digits.

[0038] Agent: A work number in the aviation system, used to distinguish authorized users. Users with Agent identity can perform various operations in the host system (i.e., the aviation system). It is equivalent to the user's identifier, usually represented by 2-6 digits.

[0039] OFFICE: Short for OFFICE NUMBER, it is a department code, usually assigned by city or department, in the format of a three-letter city code + a three-digit six-digit string. In the aviation system, it is defined as a company or a business department within a company. A PID belongs to an OFFICE, and an Agent can belong to one or more OFFICEs.

[0040] Airline code: uniformly coded by the International Air Transport Association, each airline has a separate code, using two characters to identify, they can be composed of two letters or a letter plus a number, or a number plus a letter.

[0041] Airport three-letter code: uniformly coded by the International Air Transport Association. Each airport has a unique code, which is identified by three characters, usually consisting of three letters.

[0042] Passenger reservation record: also known as PNR, the abbreviation of Passenger Name Record, is used to represent the passenger reservation record in the reservation system. It contains information such as passenger personal information, flight itinerary, and the number of occupied flight seats.

[0043] Air ticket: It is a kind of transport voucher. Each ticket has a unique ticket number, which consists of 13 digits. According to the different information carriers of the voucher, it is divided into paper tickets and electronic tickets. Paper tickets are paper tickets with voucher numbers. Electronic tickets are electronic forms of tickets, which are stored in the system database and are a substitute for paper tickets.

[0044] Passenger check-in record: Check-in is a travel procedure, which means that before the flight takes off, passengers check in their tickets, valid documents, boarding passes, baggage check-in and other procedures at the airline counter or self-service check-in front end to confirm the passenger's boarding information. Passenger check-in record is a related record generated during the passenger's check-in process, including the flight boarding gate, passenger boarding number, seat number, check-in time and other information.

[0045] Host technology: Provides airlines with facilities for inventory-based processing, reservations, check-in and other passenger-related functions. Different from open technology, it mainly refers to the core technologies of the three main host systems: DCS, ICS and CRS.

[0046] Open technology: It is a computer technology system that uses an X86-based CPU (Central Processing Unit) and a Linux-based operating system as a server.

[0047] DCS system: (Departure Control System) is a host system for handling passenger departure services provided by airlines and airport ground service departments. The DCS host is connected to the terminal equipment through the network to realize the automatic transmission and processing of flight / passenger information and the host system. The host system code of DCS is J.

[0048] ICS system: (Inventory Control System) is a host system that provides passenger reservation services for airline users. The ICS host is connected to the terminal device through the network to realize the automatic transmission and processing of flight / passenger information and the host system. The ICS host is connected to the departure system, passenger system, electronic ticket system and other systems. The ICS host provides airline users with flight data control, flight availability information query, passenger reservation and ticketing, onboard seat control, flight changes and passenger protection, frequent flyer identification and other functions. The host system code of ICS is B.

[0049] CRS system: (Computer Reservation System) is a host system that provides passenger reservation services for airline users. It is connected to terminal devices through the network to realize the automatic transmission and processing of flight / passenger information and the host system. The CRS host is connected to the ICS host, electronic ticket system and other systems to provide airline users with information query, passenger reservation and ticketing, on-board seat reservation and other functions. The host system code of CRS is C.

[0050] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) collected and involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with the relevant laws, regulations and standards of the relevant regions, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set between the system and the relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0051] After implementing the real-name authentication of Agent, we can accurately know who is the actual user of a certain Agent A, including his / her name, ID number, mobile phone number, email address, as well as the OFFICE to which the Agent belongs, airline code, airport three-letter code and other information. In this way, Agent can be used to accurately distinguish the actual operator of key operations such as PNR reservation, ticket issuance, and check-in. Based on this, the present invention proposes a historical data query method based on an open environment to enhance the ability to protect passenger privacy. Compared with the historical data query method based on a host environment in the related art, this method achieves the following beneficial effects:

[0052] (1) Only agents who have created or modified PNR records, ticket information, and check-in records are allowed to query the historical data of the PNR records, ticket information, and check-in records. Even if they belong to the same office, the same airline code, or the same airport code, agents who have not created or modified the PNR records, ticket information, and check-in records are not authorized to query the historical data;

[0053] (2) Compared with the host environment, the use of agents that have created or modified records to control permissions based on the same office, the same airline code, or the same airport three-letter code is more accurate. When the business can be handled normally, the scope of knowledge of passengers' personal privacy information is smaller, thereby enhancing the protection of passengers' privacy information.

[0054] The present invention is described in detail below in conjunction with various embodiments.

[0055] Embodiment 1

[0056] According to an embodiment of the present invention, an embodiment of a method for querying historical data 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.

[0057] Figure 1 is a flowchart of an optional historical data query method according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0058] Step S101: receiving a historical data query request, wherein the historical data query request at least includes: query information.

[0059] In the embodiment of the present invention, historical data query is divided into: historical passenger booking record query, historical electronic ticket face query, and historical passenger check-in record query.

[0060] In the embodiment of the present invention, passengers can initiate corresponding historical data query requests to the aviation system according to their needs (for example, the need to print reimbursement vouchers, the need to trace itinerary, etc.), including: historical passenger booking record query requests, historical electronic ticket face query requests, historical passenger check-in record query requests, etc. In addition, the historical data query request carries query information.

[0061] Step S102: Based on the query information, query the historical records on the query system, and determine the authorized user identification and the authorized system code corresponding to the historical records.

[0062] In the embodiment of the present invention, the aviation system can query relevant historical records (historical passenger booking record query, historical electronic ticket face or historical passenger check-in record, etc.) on the query system according to the received query information, and then determine the authorized user identification and authorization system code corresponding to the queried historical records, that is, the Agent and host system codes that created or modified these historical records.

[0063] In an optional embodiment, if one or more historical records are found, the Agent (ie, authorized user identification) and host system code (ie, authorized system code) that created or modified the historical records are further obtained one by one.

[0064] Step S103, determining the current user account for logging into the query system, and determining the user identifier and system code corresponding to the current user account.

[0065] In an embodiment of the present invention, the current user account of the login query system can be determined based on the login information of the current user who logs in to the query system, and the user identifier and system code corresponding to the current user account can be obtained based on the Agent and host system code previously bound to the current user account.

[0066] Step S104, when it is detected that there is an authorized user identifier and an authorized system code that match both the user identifier and the system code, the historical records corresponding to the authorized user identifier and the authorized system code are sent to the target communication address associated with the current user account.

[0067] In an embodiment of the present invention, if it is detected that there is an authorized user identifier and an authorized system code that match both the user identifier and the system code, it can indicate that the current user account has the authority to query the historical records (i.e., the historical records corresponding to the authorized user identifier and the authorized system code), and then these historical records can be encrypted and sent to the target communication address associated with the current user account (for example, an email address pre-bound to the current user account).

[0068] In an embodiment of the present invention, the password for encrypting the historical record may be sent to the user terminal number associated with the current user account, so that the user can decrypt the historical record.

[0069] In summary, by detecting whether the user ID and system code of the current user account match the authorized user ID and authorized system code of the queried historical records, and after a successful match, the matching historical records are sent to the target communication address associated with the current user account, accurate authorized query of historical data is achieved, effectively ensuring the security and privacy of data, and achieving the technical effect of enhancing the protection of passenger privacy information, thereby solving the technical problem in related technologies that there are many users with the authority to query historical data, which easily leads to leakage of passenger information.

[0070] In order to generate a user account for a user, in the historical data query method provided in Example 1 of the present application, before receiving a historical data query request, a user registration request initiated by the user through a user terminal is received, wherein the user registration request includes at least: a user identity identifier, a user terminal number, and a communication address; if the user identity identifier, the user terminal number, and the communication address are verified, a binding request is initiated; the user identifier and the system code returned by the user terminal based on the binding request are received, and if there are multiple pairs of user identifiers and system codes, a selection request is initiated; the target user identifier and the target system code returned by the user terminal based on the selection request are received, and a user account for the user is generated, wherein the user account is the credential for the user to log in to the query system to query historical data.

[0071] In the embodiment of the present invention, the user needs to complete the real-name registration and authentication in advance, register the user name as the user terminal number, bind the Agent and host system code in the aviation system, and provide the real-name ID card information for verification. Only after the above registration is completed can the historical data query function of the corresponding host system be activated.

[0072] Here, the host system is divided into three major systems: B (i.e. ICS system), C (i.e. CRS system), and J (i.e. DCS system). Agent is a 2-6 digit number. The same user has only one Agent in the same host system, but can have another Agent in a different host system. For example, a user can have Agent123 in the ICS system and Agent456 in the CRS system, but there is no necessary connection between Agent123 in the ICS system and Agent456 in the CRS system. Usually, a user has only one Agent in a host system. In special cases, there can be multiple Agents in multiple host systems. Users with multiple Agents can select a commonly used host system and Agent in advance as the main host system and main Agent.

[0073] In the embodiment of the present invention, the host system can receive a user registration request initiated by a user through his terminal (such as a mobile phone or a computer). This request contains at least three key information: user identification (such as an ID card number), user terminal number (such as a mobile phone number), and communication address (such as an email address). The collection of these three pieces of information is to ensure that the system can communicate effectively with the user and verify the legitimacy of the user in subsequent steps.

[0074] In an embodiment of the present invention, after receiving a user registration request, the user identity, user terminal number and communication address may be verified. This step is to confirm the authenticity of the user information and prevent false registration or malicious access. After the verification is passed, the host system may initiate a binding request, requiring the user terminal to return a specific user identity (such as an agent in an aviation system) and a system code (such as a host system code of ICS, CRS, and DCS). If the user has agents in multiple systems, that is, there are multiple pairs of user identities and system codes, the system will further initiate a selection request to allow the user to select a primary identity and system code. The user selects one of the multiple agents and system codes as the primary one according to his or her needs. The system receives the target user identity and target system code returned by the user terminal based on the selection request, and then generates a user account. This account is the credential for the user to log in to the query system and query historical data. The user account is generated based on the user terminal number, the target user identity and the target system code, so as to ensure that each user can accurately access the historical records that he or she is entitled to view.

[0075] Optionally, in the case where the historical data query request is a historical passenger booking record query request, the query information at least includes: passenger name, flight number, and flight date. In order to improve the accuracy of querying historical records, in the historical data query method provided in Example 1 of the present application, based on the query information, a query condition is constructed, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; the query condition is used to query the historical passenger booking record on the query system; when at least one historical passenger booking record is queried, the authorized user identifier and the authorized system code that have created or modified the historical passenger booking record are obtained from the first preset database, wherein the first preset database stores multiple historical passenger booking records, and each historical passenger booking record is associated with all user identifiers and all system codes that have created or modified the historical passenger booking record.

[0076] In the embodiment of the present invention, if the historical data query request is a historical passenger booking record query request, the received query information needs to include: passenger name (supporting Chinese and English names), flight number, and flight date.

[0077] In the embodiment of the present invention, the function of querying the historical passenger booking record is limited to the use after the user with the ICS system or CRS system Agent logs in. The Web (network) page or application end sets the user to input the query conditions: passenger name, flight number, flight date, and the query condition is constructed based on the query information carried by the historical passenger booking record query request.

[0078] Here, the passenger name can be a Chinese name, Chinese pinyin or English name. Fuzzy search is not supported. The flight number format is the airline code plus 3-4 digits of the flight number, such as CA1234 or MU789. The flight date supports one year and can be selected and input in calendar form. For example, if the current day is T, flights between T-365 and T-3 can be queried; flights within T-3 are not expired, and users can check them through commands in the host ICS system or CRS system.

[0079] In the embodiment of the present invention, when the user inputs a flight number in an incorrect format, a prompt is displayed indicating that the flight number is in an incorrect format; flight dates outside the allowed query range are displayed in gray and cannot be selected.

[0080] In the embodiment of the present invention, the query system can automatically bring in the Agent and host system code or the Agent and host system code selected by the user according to the user login information. Moreover, after the user inputs the query conditions and clicks the query, the query system retrieves the relevant passenger booking records from the historical database of passenger booking records (i.e., the first preset database, which stores multiple historical passenger booking records, and each historical passenger booking record is associated with all user identifiers and all system codes that have created or modified the historical passenger booking records) according to the passenger name, flight number, and flight date input by the user, and then determines whether the user has the right to view the passenger booking records according to the creation and modification agent of the passenger booking records and the agent logged in by the user.

[0081] In the embodiment of the present invention, if there is no Agent and host system code that has created or modified the passenger booking record and includes the logged-in Agent and host system code, the page displays that the user has no right to query the passenger booking record. If there is no corresponding passenger booking record according to the query condition, the page displays that there is no booking record for the passenger.

[0082] Optionally, in the case where the historical data query request is a historical electronic ticket face query request, the query information at least includes: the electronic ticket number. In order to improve the accuracy of querying historical records, in the historical data query method provided in the first embodiment of the present application, based on the query information, a query condition is constructed, wherein the query condition is a condition composed of the electronic ticket number; the query condition is used to query the historical electronic ticket face information on the query system; when the historical electronic ticket face information is queried, the authorized user identifier and the authorized system code for creating the historical electronic ticket face information are obtained from the second preset database, wherein the second preset database stores multiple historical electronic ticket face information, and each historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information.

[0083] In the embodiment of the present invention, the electronic ticket has a unique passenger name and ticket number, and has a maximum of 4 flight segments. Each flight segment has a departure airport, an arrival airport, a flight number, a flight date, and a flight segment status. The flight segment status represents the usage of the flight segment of the ticket, including "OPEN FOR USE (the segment of the ticket is not used)", "USED / FLOWN (the segment of the ticket is used)", "VOID (the segment of the ticket is invalid)", "REFOUND (the segment of the ticket is refunded)", "EXCH (the segment of the ticket is exchanged)" and other flight segment statuses. After a ticket is issued, all flight segments are in the "OPEN FOR USE" state. If an error is found on the day of issuance, the issuing agent can invalidate the ticket, and all flight segments of the ticket are in the "VOID" state. The ticket can be invalidated only on the day of issuance and if it is not used; thereafter, the ticket status can only be refunded or used as scheduled or rescheduled or exchanged. The status of a used segment is "USED / FLOWN", the status of a refunded segment is "REFOUND", and the status of an exchanged segment is "EXCH". If one of the segments on the ticket is "OPEN FOR USE", its status is valid for 13 months from the date of ticket issuance, and the ticket expires after 13 months. If all the segments of the ticket are not "OPEN FOR USE", the ticket expires after 30 days from the last status change date.

[0084] In the embodiment of the present invention, if the historical data query request is a historical electronic ticket face query request, the received query information needs to include: the electronic ticket number.

[0085] In the embodiment of the present invention, the function of querying the face value of historical electronic tickets is limited to users who have logged in with the ICS system or CRS system agent. The web page or application end sets the user input query condition: electronic ticket number. The query condition is constructed based on the query information carried by the historical electronic ticket face query request.

[0086] Here, the electronic ticket number consists of 13 digits, such as 9991234567890, where the first three digits are the airline ticket code and the last ten digits are the recurring ticket number.

[0087] In the embodiment of the present invention, the query system can automatically bring in the Agent and host system code or the Agent and host system code selected by the user according to the user login information. Then, the query system retrieves the relevant expired electronic ticket face information from the historical database (i.e., the second preset database, which stores multiple historical electronic ticket face information, and each historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information) according to the query condition entered by the user, i.e., the ticket number, and then determines whether the user has the right to view it according to the creation agent of the historical electronic ticket face information and the agent logged in by the user.

[0088] For example, assuming the ticket number is 9991234567890, obtain the creator Agent and host system code of the ticket. Assuming it is Agent123 of the CRS system, if the user is Agent123 of the ICS system, due to the inconsistency of the host system code, he has no right to view the ticket information. Only when the querying user is Agent123 of the CRS system can he view it.

[0089] In the embodiment of the present invention, if the Agent and host system code of the creator of the ticket are inconsistent with the Agent and host system code of the queryer, the page will display that the user has no right to query the ticket information. If the corresponding ticket number does not exist according to the query condition, the page will display that the ticket does not exist.

[0090] Optionally, in the case where the historical data query request is a historical passenger check-in record query request, the query information includes at least: passenger name, flight number, and flight date. In order to improve the accuracy of querying historical records, in the historical data query method provided in Example 1 of the present application, based on the query information, a query condition is constructed, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; the query condition is used to query the historical passenger check-in record on the query system; in the case where at least one historical passenger check-in record is queried, the authorized user identifier and the authorized system code for creating the historical passenger check-in record are obtained from the third preset database, wherein the third preset database stores multiple historical passenger check-in records, and each historical passenger check-in record is associated with all user identifiers and all system codes for creating the historical passenger check-in record.

[0091] In the embodiment of the present invention, if the historical data query request is a historical passenger check-in record query request, the received query information needs to include: passenger name, flight number, and flight date.

[0092] In the embodiment of the present invention, the function of querying historical passenger check-in records is limited to users with DCS system Agent after logging in. The web page or application end sets the user input query conditions: passenger name, flight number, flight date. The query condition is constructed based on the query information carried by the historical passenger check-in record query request.

[0093] Here, the passenger name can be in Chinese, Chinese pinyin or English. Fuzzy search is not supported. The flight number format is the airline code plus 3-4 digits of the flight number, such as CA1234 or MU789. The date supports one year and can be selected and input in calendar form. For example, if the current date is T, flights between T-365 and T-3 can be queried. Flights within T-3 have not expired and users can check them through commands in the DCS system.

[0094] In the embodiment of the present invention, when the user inputs a flight number in an incorrect format, a prompt is displayed indicating that the flight number is in an incorrect format; flight dates outside the allowed query range are displayed in gray and cannot be selected.

[0095] In the embodiment of the present invention, the query system can automatically bring in the Agent and host system code or the Agent and host system code selected by the user according to the user login information. After the user enters the query conditions and clicks the query, the query system can retrieve the relevant passenger check-in records from the historical database of passenger check-in records (i.e., the third preset database, which stores multiple historical passenger check-in records, each of which is associated with all user identifiers and all system codes that created the historical passenger check-in records) according to the passenger name, flight number, and flight date entered by the user, and then compare the creation Agent in the passenger check-in record with the Agent logged in by the user. If they are consistent, the Agent has the right to view, and if they are inconsistent, the Agent has no right to view.

[0096] In the embodiment of the present invention, if there is no Agent and host system code that creates the passenger check-in record and the Agent and host system code that are consistent with the query, the page displays that the user has no right to query the passenger check-in record. If there is no corresponding passenger check-in record retrieved according to the query condition, the page displays that there is no check-in record for the passenger.

[0097] In order to accurately determine the user's authority to query historical records, in the historical data query method provided in Example 1 of the present application, after determining the user identifier and system code corresponding to the current user account, the user identifier and system code are matched with the authorized user identifier and authorized system code corresponding to each historical record queried; if there is no authorized user identifier and authorized system code corresponding to any historical record that matches the user identifier and system code, an unauthorized query result is returned; if there is an authorized user identifier and authorized system code corresponding to a historical record that matches the user identifier and system code, the historical record indicated by the authorized user identifier and authorized system code that matches both the user identifier and system code is determined as the target historical record.

[0098] In the embodiment of the present invention, the query system will compare the Agent (user ID) and host system code (system code) of the currently logged-in user with the authorized user ID and the authorized system code corresponding to each historical record queried. If there is no creation or modification Agent and host system code corresponding to any historical record that matches the Agent and host system code of the currently logged-in user, the query system will return an "unauthorized query result". This means that the current user has no authority to view any queried historical records. If there is a historical record created or modified Agent and host system code that matches the information of the currently logged-in user, then the historical record will be determined as a "target historical record". The user has query authority for these target historical records.

[0099] In order to enhance the protection of passenger information, in the historical data query method provided in Example 1 of the present application, after the historical record indicating the authorized user identifier and the authorized system code that match both the user identifier and the system code is determined as the target historical record, the target historical record is encrypted to obtain an encrypted historical record; based on the query information and the query time, the encrypted historical record is named to obtain a record name; a decryption password for the encrypted historical record is generated, and a prompt message is generated based on the record name; the prompt message and the decryption password are sent to the user terminal number associated with the current user account, and the encrypted historical record is sent to the target communication address associated with the current user account.

[0100] In an embodiment of the present invention, in order to protect the security of data and the privacy of passengers, the target historical record can be encrypted to generate an encrypted historical record. In addition, the encrypted historical record can be named according to the query information (such as passenger name, flight number, flight date) and query time entered by the user to obtain a unique record name. For example, if the query is the booking record of passenger A taking flight CA1234 on January 1, 2024, and the query time is 09:00:00.001 on February 1, 2024, then the file name may be named "passenger A_CA1234_20240101_20240201090000001.zip". This naming method ensures the traceability and uniqueness of the record. Then, a unique decryption password corresponding to the decrypted historical record can be generated, and this password is usually composed of random letters and numbers, such as x1y2z3. At the same time, a prompt message can be constructed based on the record name to inform the user of the queried historical record information, file name and decryption password, so as to facilitate the user to decrypt and view the record.

[0101] In the embodiment of the present invention, the constructed prompt information and decryption password can be sent to the user's user terminal number via SMS, and the encryption history record can be sent to the user's pre-registered email address (i.e., the target communication address associated with the current user account) in the form of an email. This ensures that the user can safely receive and decrypt data, and the SMS notification can serve as an instant guide for decryption.

[0102] Exemplarily, for users who have the right to view passenger booking records, the passenger booking records can be compressed and encrypted in the form of a table file, and the file name is named "Passenger Name_Flight Number_Flight Date_Query Time". For example, the passenger name is A, the flight number is CA1234, the flight date is January 1, 2024, and the query time is February 1, 2024 09:00:00.001, accurate to milliseconds, then the file name is "A_CA1234_20240101_20240201090000001". The password is a randomly generated six-digit password containing letters and numbers, such as x1y2z3. When the encrypted query result file is sent to the user's mailbox, a text message is sent to the user's mobile phone number, "The result of your query of the booking record of passenger A, flight number CA1234, and flight date 20240101 has been sent to your mailbox. The file name is "A_CA1234_20240101_20240201090000001.zip", and the decryption password is x1y2z3". If there is no Agent and host system code that has created or modified the passenger booking record and includes the logged-in Agent and host system code, the page will display that the user has no right to query the passenger booking record.

[0103] In another example, for a user who has the right to view the face information of an electronic ticket, the face information of the encrypted electronic ticket 9991234567890 (including the passenger's name, ticket number, number of segments and the segment number of each segment, departure airport, arrival airport, flight number, flight date, and segment status) can be sent to the user's bound email address. If the query time is 09:00:00.001 on February 1, 2024, accurate to milliseconds, the file name is "9991234567890". 0_20240201090000001.zip", the password is a randomly generated six-digit password containing letters and numbers, such as 4A76c8. When sending the encrypted query result file to the user's email, a text message is sent to the user's mobile phone number, "The result of your query on flight ticket 9991234567890 has been sent to your email, the file name is "9991234567890_20240201090000001.zip", the decryption password is 4A76c8".

[0104] As another example, for users who have the right to view passenger check-in records, the passenger check-in records can be compressed and encrypted in the form of a table file, and the file name is named "Passenger Name_Flight Number_Flight Date_Query Time". For example, the passenger name is B, the flight number is CA1234, the flight date is January 1, 2024, and the query time is February 1, 2024 09:00:00.001, accurate to milliseconds, then the file name is "B_CA1234_20240101_20240201090000001". The password is a randomly generated six-digit password containing letters and numbers, such as d956cr. When the encrypted query result file is sent to the user's email, a text message is sent to the user's mobile phone number, "You queried the check-in record result of passenger B, flight number CA1234, and flight date 20240101. The result has been sent to your email. The file name is "B_CA1234_20240101_20240201090000001.zip", and the decryption password is d956cr".

[0105] Figure 2 is a schematic diagram of an optional passenger booking record query process according to an embodiment of the present invention, such as Figure 2 As shown, according to the query conditions (passenger name, flight number, flight date) input by the user, the current user Agent and the host system to which the Agent belongs are automatically read, and the passenger booking record is retrieved according to the user input conditions to determine whether the search result is empty. If the search result is empty, the page prompts that there is no relevant passenger booking record. If the search result is not empty, it is determined whether the user has the right to view the result. If the user does not have the right to view the result, the page prompts that the user does not have the right to view the result. If the user has the right to view the result, the encrypted passenger booking record is sent to the user's preset mailbox, and the password is sent to the user's mobile phone.

[0106] Figure 3 FIG. 1 is a schematic diagram of an optional electronic ticket face query process according to an embodiment of the present invention. Figure 3 As shown, according to the query conditions (ticket number) input by the user, the current user Agent and the host system to which the Agent belongs are automatically read, the ticket information is retrieved according to the user input conditions, and it is determined whether the search result is empty. If the search result is empty, the page prompts that there is no relevant ticket information. If the search result is not empty, it is determined whether the user has the right to view the result. If the user does not have the right to view the result, the page prompts that the user does not have the right to view the result. If the user has the right to view the result, the encrypted ticket information is sent to the user's preset mailbox and the password is sent to the user's mobile phone.

[0107] Figure 4 is a schematic diagram of an optional passenger check-in record query process according to an embodiment of the present invention, such as Figure 4 As shown, according to the query conditions (passenger name, flight number, flight date) input by the user, the current user Agent and the host system to which the Agent belongs are automatically read, and the passenger check-in record is retrieved according to the user input conditions to determine whether the search result is empty. If the search result is empty, the page prompts that there is no relevant passenger check-in record. If the search result is not empty, it is determined whether the user has the right to view the result. If the user does not have the right to view the result, the page prompts that the user does not have the right to view the result. If the user has the right to view the result, the encrypted passenger check-in record is sent to the user's preset mailbox, and the password is sent to the user's mobile phone.

[0108] In the embodiment of the present invention, the historical data query authority is controlled to a single Agent. Compared with the previous control of the historical data query authority to OFFICE, airline code, and airport three-letter code containing multiple Agents, the privacy exposure of passengers traveling by plane is smaller, which is more conducive to the protection of passenger privacy. In addition, the use of open technology to query historical records can consume less host resources than the previous host technology to query historical records.

[0109] The following is a detailed description in conjunction with another embodiment.

[0110] Embodiment 2

[0111] A historical data query device provided in this embodiment includes multiple implementation units, each of which corresponds to each implementation step in the above-mentioned embodiment 1.

[0112] Figure 5 is a schematic diagram of an optional historical data query device according to an embodiment of the present invention. Figure 5 As shown, the query device may include: a receiving unit 50, a query unit 51, a determining unit 52, and a sending unit 53.

[0113] The receiving unit 50 is used to receive a historical data query request, wherein the historical data query request at least includes: query information;

[0114] A query unit 51, configured to query the historical records on the query system based on the query information, and determine the authorized user identifier and the authorization system code corresponding to the historical records;

[0115] The determination unit 52 is used to determine the current user account that logs into the query system, and to determine the user identifier and system code corresponding to the current user account;

[0116] The sending unit 53 is used to send the historical records corresponding to the authorized user identifier and the authorized system code to the target communication address associated with the current user account when detecting that there is an authorized user identifier and an authorized system code that match both the user identifier and the system code.

[0117] The above-mentioned query device detects whether the user identification and system code of the current user account match the authorized user identification and authorized system code of the queried historical records, and after a successful match, sends the matching historical records to the target communication address associated with the current user account, thereby realizing accurate authorized query of historical data, effectively ensuring the security and privacy of data, and achieving the technical effect of enhancing the protection of passenger privacy information, thereby solving the technical problem in related technologies that there are many users with the authority to query historical data, which easily leads to leakage of passenger information.

[0118] Optionally, the query device also includes: a first receiving module, used to receive a user registration request initiated by a user through a user terminal before receiving a historical data query request, wherein the user registration request includes at least: a user identity identifier, a user terminal number and a communication address; a first initiating module, used to initiate a binding request when the user identity identifier, the user terminal number and the communication address are verified; a second receiving module, used to receive the user identifier and the system code returned by the user terminal based on the binding request, and to initiate a selection request when there are multiple pairs of user identifiers and system codes; a third receiving module, used to receive the target user identifier and the target system code returned by the user terminal based on the selection request, and generate a user account for the user, wherein the user account is the credential for the user to log in to the query system to query historical data.

[0119] Optionally, in the case where the historical data query request is a historical passenger booking record query request, the query information includes at least: passenger name, flight number, and flight date, and the query unit includes: a first construction module, used to construct a query condition based on the query information, wherein the query condition is a condition consisting of the passenger name, flight number, and flight date; a first query module, used to use the query condition to query the historical passenger booking record on the query system; a first acquisition module, used to, when at least one historical passenger booking record is queried, obtain from a first preset database an authorized user identifier and an authorized system code that have created or modified the historical passenger booking record, wherein the first preset database stores multiple historical passenger booking records, and each historical passenger booking record is associated with all user identifiers and all system codes that have created or modified the historical passenger booking record.

[0120] Optionally, in the case where the historical data query request is a historical electronic ticket face query request, the query information at least includes: the electronic ticket number, and based on the query information, the query unit further includes: a second construction module, used to construct a query condition based on the query information, wherein the query condition is a condition consisting of the electronic ticket number; a second query module, used to use the query condition to query the historical electronic ticket face information on the query system; a second acquisition module, used to obtain the authorized user identifier and the authorized system code for creating the historical electronic ticket face information from a second preset database when the historical electronic ticket face information is queried, wherein the second preset database stores multiple historical electronic ticket face information, and each historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information.

[0121] Optionally, in the case where the historical data query request is a historical passenger check-in record query request, the query information includes at least: passenger name, flight number, flight date, and the query unit also includes: a third construction module, used to construct a query condition based on the query information, wherein the query condition is a condition consisting of the passenger name, flight number and flight date; a third query module, used to use the query condition to query historical passenger check-in records on the query system; a third acquisition module, used to obtain the authorized user identifier and authorized system code for creating the historical passenger check-in record from a third preset database when at least one historical passenger check-in record is queried, wherein the third preset database stores multiple historical passenger check-in records, and each historical passenger check-in record is associated with all user identifiers and all system codes for creating the historical passenger check-in record.

[0122] Optionally, the query device also includes: a first matching module, which is used to match the user identifier and system code with the authorized user identifier and authorized system code corresponding to each historical record queried after determining the user identifier and system code corresponding to the current user account; a first return module, which is used to return an unauthorized query result if there is no authorized user identifier and authorized system code corresponding to any historical record that matches the user identifier and system code; and a first determination module, which is used to determine the historical record indicated by the authorized user identifier and authorized system code that matches both the user identifier and system code as the target historical record if there is an authorized user identifier and authorized system code corresponding to the historical record that matches the user identifier and system code.

[0123] Optionally, the query device also includes: a first encryption module, which is used to encrypt the target historical record to obtain an encrypted historical record after the historical record indicating the authorized user identifier and the authorized system code that match the user identifier and the system code is determined as the target historical record; a first naming module, which is used to name the encrypted historical record based on the query information and the query time to obtain a record name; a first generation module, which is used to generate a decryption password for the encrypted historical record, and to generate prompt information based on the record name; a first sending module, which is used to send the prompt information and the decryption password to the user terminal number associated with the current user account, and to send the encrypted historical record to the target communication address associated with the current user account.

[0124] The above-mentioned query device may also include a processor and a memory. The above-mentioned receiving unit 50, query unit 51, determination unit 52, sending unit 53, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0125] The processor includes a kernel, which retrieves the corresponding program unit from the memory. The kernel can be set to one or more, and when the kernel parameters are adjusted, when the authorized user identifier and the authorized system code that match the user identifier and the system code are detected, the historical records corresponding to the authorized user identifier and the authorized system code are sent to the target communication address associated with the current user account.

[0126] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one storage chip.

[0127] The present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps: receiving a historical data query request, querying the historical records on a query system based on the query information, and determining the authorized user identifier and the authorized system code corresponding to the historical records, determining the current user account that logs into the query system, and determining the user identifier and the system code corresponding to the current user account, and when it is detected that there is an authorized user identifier and an authorized system code that match both the user identifier and the system code, sending the historical records corresponding to the authorized user identifier and the authorized system code to a target communication address associated with the current user account.

[0128] According to another aspect of an embodiment of the present invention, a computer program product is also provided, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, implementing any of the above-mentioned historical data query methods.

[0129] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement the above-mentioned historical data query method.

[0130] Figure 6 1 is a hardware structure block diagram of an electronic device (or mobile device) for a method for querying historical data according to an embodiment of the present invention. Figure 6 As shown, the electronic device may include one or more processors (e.g., Figure 6 The processor 602a, processor 602b, ..., processor 602n, etc., which may include but are not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 604 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 6 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 6 More or fewer components as shown, or with Figure 6 Different configurations are shown.

[0131] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0132] The embodiments or examples of the present disclosure are not exhaustive, but are only illustrative of some embodiments or examples, and are not intended to be specific limitations on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment or example can be implemented as an independent example, and the steps can be combined arbitrarily. For example, the scheme after removing some steps in a certain embodiment or example can also be implemented as an independent example, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be combined arbitrarily; in addition, the various embodiments or examples can be combined arbitrarily, for example, some or all steps of different embodiments or examples can be combined arbitrarily, and a certain embodiment or example can be combined arbitrarily with the optional methods or optional examples of other embodiments or examples.

[0133] In the above embodiments of the present invention, 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.

[0134] In the several embodiments provided by the present invention, 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, such as 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.

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

[0136] In addition, each functional unit in each embodiment of the present invention 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 a system functional unit.

[0137] If the integrated unit is implemented in the form of a system 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 invention, in essence, 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 system product. The computer system product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0138] The above is only a preferred embodiment of the present invention. 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 invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for querying historical data, characterized in that: include: Receiving a historical data query request, wherein the historical data query request at least includes: query information; Based on the query information, query the historical records on the query system, and determine the authorized user identification and the authorization system code corresponding to the historical records; Determine the current user account for logging into the query system, and determine the user identifier and system code corresponding to the current user account; When it is detected that there are the authorized user identifier and the authorized system code that match both the user identifier and the system code, the historical records corresponding to the authorized user identifier and the authorized system code are sent to a target communication address associated with the current user account.

2. The query method according to claim 1, characterized in that: Before receiving a historical data query request, it also includes: Receiving a user registration request initiated by a user through a user terminal, wherein the user registration request includes at least: a user identity, a user terminal number, and a communication address; Initiate a binding request when the user identity, the user terminal number and the communication address are verified; receiving the user identification and the system code returned by the user terminal based on the binding request, and initiating a selection request when there are multiple pairs of the user identification and the system code; The target user identification and the target system code returned by the user terminal based on the selection request are received, and a user account of the user is generated, wherein the user account is the credential for the user to log in to the query system to query historical data.

3. The query method according to claim 1, characterized in that: In the case where the historical data query request is a historical passenger booking record query request, the query information at least includes: passenger name, flight number, and flight date. Based on the query information, querying the historical records on the query system and determining the authorized user identifier and the authorization system code corresponding to the historical records include: Based on the query information, construct a query condition, wherein the query condition is a condition consisting of the passenger name, the flight number, and the flight date; Using the query conditions, querying historical passenger booking records on the query system; When at least one of the historical passenger booking records is found, the authorized user identifier and the authorized system code that have created or modified the historical passenger booking record are obtained from a first preset database, wherein the first preset database stores multiple historical passenger booking records, and each of the historical passenger booking records is associated with all user identifiers and all system codes that have created or modified the historical passenger booking record.

4. The query method according to claim 1, characterized in that: In the case where the historical data query request is a historical electronic ticket face query request, the query information at least includes: the electronic ticket number, and based on the query information, querying the historical records on the query system and determining the authorized user identifier and the authorization system code corresponding to the historical records, the step further includes: Based on the query information, construct a query condition, wherein the query condition is a condition formed by the electronic ticket number; Using the query conditions, querying historical electronic ticket information on the query system; When the historical electronic ticket face information is queried, the authorized user identifier and the authorized system code that created the historical electronic ticket face information are obtained from a second preset database, wherein the second preset database stores multiple pieces of the historical electronic ticket face information, and each piece of the historical electronic ticket face information is associated with all user identifiers and all system codes that created the historical electronic ticket face information.

5. The query method according to claim 1, characterized in that: In the case where the historical data query request is a historical passenger check-in record query request, the query information at least includes: passenger name, flight number, and flight date. Based on the query information, querying the historical records on the query system and determining the authorized user identifier and the authorization system code corresponding to the historical records also include: Based on the query information, construct a query condition, wherein the query condition is a condition consisting of the passenger name, the flight number, and the flight date; Using the query conditions, querying historical passenger check-in records on the query system; When at least one of the historical passenger check-in records is found, the authorized user identifier and the authorized system code for creating the historical passenger check-in record are obtained from a third preset database, wherein the third preset database stores multiple historical passenger check-in records, and each of the historical passenger check-in records is associated with all user identifiers and all system codes for creating the historical passenger check-in record.

6. The query method according to claim 1, characterized in that: After determining the user identifier and system code corresponding to the current user account, the method further includes: Matching the user identification and the system code with the authorized user identification and the authorized system code corresponding to each of the retrieved historical records; If there is no authorized user ID and the authorized system code corresponding to any of the historical records that match the user ID and the system code, returning an unauthorized query result; When the authorized user identification and the authorized system code corresponding to the historical record match the user identification and the system code, the historical record indicating the authorized user identification and the authorized system code matching the user identification and the system code is determined as the target historical record.

7. The query method according to claim 6, characterized in that: After determining the historical record indicating that both the user identifier and the system code match the authorized user identifier and the authorized system code as the target historical record, the method further includes: Encrypting the target historical record to obtain an encrypted historical record; Naming the encrypted historical record based on the query information and the query time to obtain a record name; Generate a decryption password for the encrypted historical record, and generate prompt information based on the record name; The prompt information and the decryption password are sent to the user terminal number associated with the current user account, and the encrypted historical record is sent to the target communication address associated with the current user account.

8. A historical data query device, characterized in that: include: A receiving unit, configured to receive a historical data query request, wherein the historical data query request at least includes: query information; A query unit, configured to query the historical records on the query system based on the query information, and determine the authorized user identifier and the authorization system code corresponding to the historical records; A determination unit, used to determine a current user account for logging into the query system, and to determine a user identifier and a system code corresponding to the current user account; The sending unit is used to send the historical records corresponding to the authorized user identifier and the authorized system code to the target communication address associated with the current user account when detecting that there is the authorized user identifier and the authorized system code that match both the user identifier and the system code.

9. A computer program product, characterized in that It comprises a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for querying historical data according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the historical data query method described in any one of claims 1 to 7.

Images