Data security guarantee method and device, storage medium and equipment

Abstract

The application discloses a data security guarantee method and device, a storage medium and equipment. The method comprises the following steps: obtaining a target data security rule from a data rule table based on a flight number and a date shown by a data query command input by a user; obtaining civil aviation business data requested by the data query command from a civil aviation booking system and displaying the obtained civil aviation business data to the user through a preset interface in the case that a proxy account of the user, a user level, and a type of the civil aviation business data requested by the data query command all meet the target data security rule and the type of the civil aviation business data allowed to be read by the user in the target data security rule. The method determines the reading permission of various civil aviation business data (including flight data, passenger order data and electronic ticket data) through a data security rule, ensures that various civil aviation business data is only queried by a user with the reading permission, and improves the safety of various civil aviation business data in the civil aviation booking system.

Description

Technical Field

[0001] This application relates to the field of aviation information technology, and in particular to a method, apparatus, storage medium and device for ensuring data security. Background Technology

[0002] Currently, the core business of the civil aviation reservation system mainly involves three types of civil aviation business data: flight data, passenger order data, and e-ticket data. Although these data are stored in different files, they are interconnected through passenger information. For a long time, querying and controlling these data within the civil aviation reservation system has relied on independent command systems, resulting in their isolation and the lack of a comprehensive, multi-layered security protection process. When there are urgent needs for system information and data security, it is impossible to take immediate and feasible measures to protect this data, restrict unauthorized access, or prevent malicious acquisition and tampering. This could lead to the risk of data leakage and adverse consequences for critical flight, passenger order, and ticket data.

[0003] Therefore, improving the security of various civil aviation business data in the civil aviation reservation system has become an urgent problem to be solved in this field. Summary of the Invention

[0004] This application provides a method, apparatus, storage medium, and device for ensuring data security, with the aim of improving the security of various civil aviation business data in the civil aviation reservation system.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] A data security protection method includes:

[0007] Based on the flight number and date indicated by the user-input data query command, target data security rules are retrieved from a preset data rule table. These target data security rules include data security rules that meet preset conditions. The preset conditions are: the flight number indicated by the data security rule is the same as the flight number indicated by the data query command, and the date indicated by the data query command is within the date range indicated by the data security rule. The data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data.

[0008] If the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rules, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface.

[0009] Optional, also includes:

[0010] If the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is different from the type of civil aviation business data that the user is allowed to read in the target data rules, an error message will be displayed to the user through the preset interface.

[0011] Optional, also includes:

[0012] If the user's agent account and user level do not both meet the target data rules, an error message will be displayed to the user through the preset interface.

[0013] Optionally, the step of retrieving target data security rules from a preset data rule table based on the flight number and date indicated by the user-input data query command includes:

[0014] After receiving a data query command input by the user, determine whether the data query command contains a flight number and a date;

[0015] If the data query command contains the flight number and the date, determine whether the preset data security rule table contains the target data security rule;

[0016] If the target data security rule is contained in the data security rule table, the target data security rule is extracted from the data security rule table.

[0017] Optionally, after determining whether the data query command contains a flight number and a date, the method further includes:

[0018] If the data query command does not contain the flight number and the date, but contains passenger reservation records, the flight segment is extracted from the passenger reservation records, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command.

[0019] Optionally, after determining whether the data query command contains a flight number and a date, the method further includes:

[0020] If the data query command does not contain the flight number and the date, but contains the ticket number, the flight segment is extracted from the ticket number, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command.

[0021] Optionally, after determining whether the preset data security rule table contains the target data security rule, the method further includes:

[0022] If the target data security rule is not included in the data security rule table, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface.

[0023] A data security protection device includes:

[0024] The rule acquisition unit is used to acquire target data security rules from a preset data rule table based on the flight number and date indicated by the user-input data query command. The target data security rules include data security rules that meet preset conditions. These preset conditions are: the flight number indicated by the data security rule is the same as the flight number indicated by the data query command, and the date indicated by the data query command is within the date range indicated by the data security rule. The data security rules include the correspondence between flight numbers, date ranges, agent accounts, user levels, and read permissions for various types of civil aviation business data.

[0025] The data display unit is used to obtain the civil aviation business data requested by the data query command from the civil aviation reservation system when the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rules, and to display the obtained civil aviation business data to the user through a preset interface.

[0026] A computer-readable storage medium includes a stored program, wherein the program executes the data security assurance method described above.

[0027] A data security protection device includes: a processor, a memory, and a bus; the processor and the memory are connected via the bus.

[0028] The memory is used to store the program, and the processor is used to run the program, wherein the data security protection method is executed when the program runs.

[0029] The technical solution provided in this application, based on the flight number and date indicated by the user's input data query command, retrieves target data security rules from a preset data rule table. The target data security rules include data security rules that meet preset conditions: the flight number indicated by the data security rules is the same as the flight number indicated by the data query command, and the date indicated by the data query command is within the date range indicated by the data security rules. The data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data. When the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data allowed to be read by the user in the target data rules, the civil aviation business data requested by the data query command is retrieved from the civil aviation reservation system, and the retrieved civil aviation business data is displayed to the user through a preset interface. This application, through data security rules, determines the read permissions for various types of civil aviation business data (including flight data, passenger order data, and electronic ticket data), ensuring that various types of civil aviation business data can only be queried by users with read permissions, thereby effectively improving the security of various types of civil aviation business data in the civil aviation reservation system. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1a A flowchart illustrating a data security protection method provided in an embodiment of this application;

[0032] Figure 1b A schematic diagram of a correspondence provided for an embodiment of this application;

[0033] Figure 2 A flowchart illustrating another data security protection method provided in this application embodiment;

[0034] Figure 3 This is a schematic diagram of the architecture of a data security protection device provided in an embodiment of this application. Detailed Implementation

[0035] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0036] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0037] It should be noted that the concepts of "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0038] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0039] The applicant discovered that, due to historical reasons, flight, passenger order, and ticket data have always been stored and managed independently. While the system controls access permissions for non-standard transactions to protect the privacy of passenger order information, it lacks a function to comprehensively block passenger data for airlines and agents who provide services such as order creation, modification, and data retrieval. Furthermore, the civil aviation reservation system lacks simple and quick measures to uniformly control access to relevant data from all business users. In certain special circumstances, such as when a flight experiences an emergency requiring closed-loop management, it is necessary to immediately block relevant business data to prevent data leakage. Therefore, it is necessary to immediately control access to the entire process of flight, order, and ticket data for that flight at the flight level.

[0040] Therefore, this application provides a data security protection method to establish a unified, multi-layered, full-process civil aviation business data security protection system to cope with sudden emergencies and special circumstances, thereby effectively improving the security of various civil aviation business data in the civil aviation reservation system.

[0041] like Figure 1aThe diagram shown is a flowchart illustrating a data security protection method provided in an embodiment of this application, which can be applied to a civil aviation reservation system and includes the following steps.

[0042] S101: Pre-configure data security rules for multiple flights.

[0043] The data security rules include the correspondence between ID, flight number, date range, agent account (user identification in the airline system), user level, access permissions for reading flight data, access permissions for reading passenger order data, and access permissions for reading electronic ticket data. In this embodiment, the date range represents the effective date of the flight; specifically, flight XX is only effective in April, and flight XX is not effective at other times.

[0044] Generally speaking, flight data mainly includes travel information such as departure and arrival cities, times, and terminals, as well as information such as sold seats, remaining available seats, and cabin status, and detailed data on historical flight creation, changes, and adjustments. These can be queried and displayed in the reservation system using corresponding commands.

[0045] Passenger order data mainly includes a list of passengers who have booked and cancelled, or reserved seats and traveled on the corresponding flight. It also includes detailed information such as each passenger's name, ID, contact information, ticket number, in-flight service requests, and airline passenger information.

[0046] Electronic ticket data is generated after a seat is reserved and payment is made on a flight, and the ticket sale is completed. This mainly consists of ET data, which includes passenger name, passenger identification, flight itinerary, flight date, flight seat, ticket number, ticket price, ticket status, and other data.

[0047] In other words, flight data, passenger order data, and e-ticket data, as civil aviation business data, are all associated with flight numbers and date ranges. Furthermore, the relationships between flight data, passenger order data, and e-ticket data are as follows: Figure 1b As shown. Therefore, multiple data security rules can be configured based on the correspondence between flight data, passenger order data, e-ticket data, flight numbers, and date ranges.

[0048] Specifically, the pre-configured data security rules for flights can be found in Table 1.

[0049] Table 1

[0050]

[0051] The content shown in Table 1 above is for illustrative purposes only. Specifically, "15Apr / 01May" represents the range of dates from April 15th to May 1st, "09Apr / 09Apr" represents the range of dates from April 9th ​​to April 9th ​​(i.e., April 9th ​​itself), "10Apr / 30Apr" represents the range of dates from April 10th to April 30th, "Can I access flight data?" represents the permission to read flight data, "Can I access passenger order data?" represents the permission to read passenger order data, and "Can I close access to e-ticket data?" represents the permission to read e-ticket data.

[0052] S102: Delete the data security rules that meet the preset verification requirements from each data security rule, and write the remaining data security rules into the preset data security rule table.

[0053] The preset verification requirements are: the flight number, date range, agent account, and user level of the data security rule must be the same as those of other data security rules.

[0054] It should be noted that the remaining data security rules are written into the preset data security rule table. The purpose of this is to make it convenient for users to query the data security rule table at any time, learn about the data security rules for each flight, and facilitate the maintenance and updating of the data security rules.

[0055] Optionally, a data security rules table can be displayed to users through a preset interface.

[0056] S103: After receiving the data query command input by the user, determine whether the data query command contains flight number and date.

[0057] If the data query command contains flight number and date, execute S104; otherwise, execute S109.

[0058] S104: Determine whether the data security rule table contains the target data security rule.

[0059] If the data security rule table contains the target data security rule, then execute S105; otherwise, execute S108.

[0060] The target data security rules include data security rules that meet preset conditions. In this embodiment, the preset conditions are: the flight number shown in the data security rule is the same as the flight number shown in the data query command, and the date shown in the data query command is within the date range shown in the data security rule.

[0061] S105: Extract the target data security rules from the data security rule table and determine whether the user's agent account and user level both meet the target data security rules.

[0062] If the user's agent account and user level both meet the target data security rules, then execute S106; otherwise, execute S107.

[0063] Among them, the user's agent account and user level are user information carried by the data query command.

[0064] It should be noted that a user's agent account can only be considered to meet the target data security rules if it is identical to the agent account specified in the target data security rules. Furthermore, a user's user level can only be considered to meet the target data security rules if the user's user level is not lower than the user level specified in the target data security rules.

[0065] S106: If the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rule, retrieve the civil aviation business data requested by the data query command from the civil aviation reservation system, and display the retrieved civil aviation business data to the user through a preset interface.

[0066] The system can display acquired civil aviation business data to users through a preset interface. It can also display different types of civil aviation business data according to their respective formats; for example, flight data, passenger order data, and e-ticket data are all displayed in different formats. Furthermore, the acquisition of civil aviation business data requires processing and calculation. Specifically, for flight data, flight data and historical flight information need to be extracted; for passenger order data, order lists, order data, and order messages need to be extracted; and for e-ticket data, ticket data, ticket lists, and fare information need to be extracted.

[0067] In this embodiment of the application, if the type requested by the data query command is flight data, and the read permission of the flight data indicated by the target data rule indicates that the flight data allows the user to read it, then the flight data requested by the data query command (including but not limited to flight segment, cabin class, seat, sales status, and seat sales rules) is obtained from the civil aviation reservation system, and the obtained flight data is displayed to the user through a preset interface.

[0068] If the data query command requests passenger order data, and the read permission for passenger order data indicated by the target data rule allows users to read the passenger order data, then the passenger order data requested by the data query command (including but not limited to flight segment, name, and passenger reservation record) is obtained from the civil aviation reservation system, and the obtained passenger order data is displayed to the user through a preset interface.

[0069] If the data query command requests electronic ticket data, and the read permission for electronic ticket data indicated by the target data rule allows users to read the electronic ticket data, then the electronic ticket data requested by the data query command (including but not limited to flight segment, name, and ticket number) is obtained from the civil aviation reservation system, and the obtained electronic ticket data is displayed to the user through a preset interface.

[0070] Optionally, if the type of civil aviation business data requested by the data query command is different from the type of civil aviation business data that the user is allowed to read in the target data rule, an error message (such as an emergency lockout message) will be displayed to the user through a preset interface.

[0071] Specifically, if the data query command requests flight data, and the target data rules indicate that the flight data read permission is not allowed to be read by users, the passenger order data read permission is allowed to be read by users, and the electronic ticket data read permission is allowed to be read by users, then an error message will be displayed to the user through a preset interface.

[0072] If the data query command requests passenger order data, and the target data rules indicate that passenger order data is not allowed to be read, flight data is allowed to be read, and e-ticket data is allowed to be read, then an error message will be displayed to the user through the preset interface.

[0073] If the data query command requests electronic ticket data, and the read permission for electronic ticket data indicated by the target data rule is that electronic ticket data is not allowed to be read by users, the read permission for flight data is that flight data is allowed to be read by users, and the read permission for passenger order data is that passenger order data is allowed to be read by users, then an error message will be displayed to the user through the preset interface.

[0074] Specifically, let's take the data security rule shown in Table 2 as an example, which is the only data security rule in the data security rule table.

[0075] Table 2

[0076]

[0077] Assume the user's data query command requests flight data, the flight number CA1351 specified in the query command matches the data security rules shown in Table 2, and the date 25Apr (April 25th) falls within the date range specified in Table 2. Furthermore, the user information carried in the query command is: the user's agent account is 10761, and the user level is ordinary agent. Clearly, the user with agent account 10761 has permission to read the flight data for flight CA1351 on April 25th. Therefore, the flight data for flight CA1351 is displayed to this user through a pre-defined interface.

[0078] Assume the user's data query command requests flight data, the flight number CA1351 specified in the command matches the data security rules shown in Table 2, and the date 25Apr (April 25th) falls within the date range specified in Table 2. Furthermore, the user information carried in the query command is: the user's agent account is 9993, and the user level is ordinary agent. Clearly, the user with agent account 9993 does not have permission to read flight data for CA1351 on April 25th. Therefore, an error message is displayed to this user through a pre-defined interface.

[0079] Assume the user's query command requests passenger order data, the flight number CA1351 matches the data security rules in Table 2, and the date 15Apr (April 15th) falls within the date range specified in Table 2. Furthermore, the user information carried in the query command is: the user's agent account is 10671, and the user level is ordinary agent. Clearly, the user with agent account 10671 has permission to read passenger order data for flight CA1351 on April 15th. Therefore, the passenger order data is displayed to this user through a pre-defined interface.

[0080] Assume the user's query command requests passenger order data for civil aviation services. The flight number CA1351 in the query command matches the data security rules shown in Table 2, and the date 15Apr (April 15th) falls within the date range specified in Table 2. Furthermore, the user information carried in the query command is: the user's agent account is 9993, and the user level is ordinary agent. Clearly, the user with agent account 9993 does not have permission to read passenger order data for flight CA1351 on April 15th. Therefore, an error message is displayed to this user through a pre-defined interface.

[0081] Assume the user's data query command requests electronic ticket data, the flight number CA1351 in the query command matches the data security rules shown in Table 2, and the date 15Apr (April 15th) in the query command falls within the date range specified in Table 2. Furthermore, the user information carried in the query command is: the user's agent account is 10671, and the user level is ordinary agent. Clearly, the user with agent account 10671 has permission to read the electronic ticket data for flight CA1351 on April 15th. Therefore, the electronic ticket data is displayed to this user through a pre-defined interface.

[0082] It should be noted that the above specific implementation process is only for illustrative purposes.

[0083] S107: Display error messages to users through a preset interface.

[0084] The error message displayed to the user through the preset interface is essentially a notification to the user that they do not have permission to access the data.

[0085] S108: Obtain the civil aviation business data requested by the data query command from the civil aviation reservation system, and display the obtained civil aviation business data to the user through a preset interface.

[0086] If the data security rules table does not contain the target data security rules, it means that the civil aviation business data requested by the data query command does not have data security rules set. In other words, the flight requested by the data query command can be queried by anyone. Therefore, the civil aviation business data requested by the data query command can be obtained directly from the civil aviation reservation system and the obtained civil aviation business data can be displayed to the user through a preset interface.

[0087] Specifically, taking the data security rule shown in Table 2 as the only data security rule in the data security rule table as an example.

[0088] Assuming the user's query command requests passenger order data, the flight number CA1316 in the query command is different from the data security rules shown in Table 2, and the date in the query command is 16Apr (April 16th), then it is determined that the data security rule table does not contain the target data security rule. Therefore, the passenger order data for flight CA1316 on April 16th is directly retrieved from the civil aviation reservation system and displayed to the user through a preset interface.

[0089] It should be noted that the above specific implementation process is only for illustrative purposes.

[0090] S109: If the data query command contains passenger reservation records, extract the flight segment from the passenger reservation records, and obtain the flight number containing the flight segment, the flight date of the flight segment, and identify the obtained flight number as the flight number shown in the data query command, and the flight date of the flight segment as the date shown in the data query command from the civil aviation reservation system.

[0091] Optionally, if the data query command contains a ticket number, the flight segment can be extracted from the ticket number, and the flight number containing the flight segment and the flight date of the flight segment can be obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command.

[0092] It should be emphasized that after determining the flight number and date shown in the data query command, you can return to execute S104.

[0093] Based on the processes shown in S101-S109 above, a unified and multi-layered end-to-end data security solution for flight data, passenger order data, and electronic ticket data can be established. This solution can be used in the end-to-end data management of various civil aviation business data. By constructing a unified and multi-layered civil aviation business data security system, it solves the data leakage risk caused by the independent storage and management of various types of civil aviation business data in certain situations. Specifically, this embodiment constructs a multi-layered civil aviation business data security architecture from three dimensions. It can quickly and accurately protect the security of relevant civil aviation business data based on different user needs, avoid the risk of related data leakage, reduce security risks in the civil aviation reservation system, protect civil aviation business data and passenger privacy, and provide a good solution for end-to-end data security, which has high application value.

[0094] Compared to existing technologies, this embodiment can be used to solve data security issues in various civil aviation business data management. It constructs a data security protection system for orders and tickets based on flight granularity, preventing business data leakage in certain scenarios such as flight accidents, protecting user privacy and civil aviation business data. It has high scalability, provides good scalability for future segmented needs in various scenarios, is ingeniously designed, and has low consumption costs for the civil aviation reservation system, making it very valuable.

[0095] In summary, this embodiment uses data security rules to determine the read permissions for various types of civil aviation business data (including flight data, passenger order data, and electronic ticket data), ensuring that such data can only be queried by users with read permissions, thereby effectively improving the security of various types of civil aviation business data in the civil aviation reservation system.

[0096] It should be noted that S101 mentioned in the above embodiments is an optional implementation of the data security protection method shown in the embodiments of this application. Furthermore, S109 mentioned in the above embodiments is also an optional implementation of the data security protection method shown in the embodiments of this application. Therefore, the process mentioned in the above embodiments can be summarized as follows: Figure 2 The method shown.

[0097] like Figure 2 The diagram shown is a flowchart illustrating another data security protection method provided in this application embodiment, including the following steps.

[0098] S201: Based on the flight number and date shown in the user-input data query command, retrieve the target data security rule from the preset data rule table.

[0099] The target data security rules include data security rules that meet preset conditions. The preset conditions are: the flight number shown in the data security rule is the same as the flight number shown in the data query command, and the date shown in the data query command is within the date range shown in the data security rule. The data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data.

[0100] S202: If the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rules, retrieve the civil aviation business data requested by the data query command from the civil aviation reservation system, and display the retrieved civil aviation business data to the user through a preset interface.

[0101] In summary, this embodiment uses data security rules to determine the read permissions for various types of civil aviation business data (including flight data, passenger order data, and electronic ticket data), ensuring that such data can only be queried by users with read permissions, thereby effectively improving the security of various types of civil aviation business data in the civil aviation reservation system.

[0102] It should be noted that although the operations are described in a specific order, this should not be interpreted as requiring these operations to be executed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0103] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0104] Furthermore, computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0105] Corresponding to the data security protection method provided in the above embodiments of this application, the embodiments of this application also provide a data security protection device.

[0106] like Figure 3 The diagram shown is an architectural schematic of a data security protection device provided in an embodiment of this application, including the following units.

[0107] The rule acquisition unit 100 is used to obtain target data security rules from a preset data rule table based on the flight number and date shown in the user's input data query command. The target data security rules include data security rules that meet preset conditions. The preset conditions are: the flight number shown in the data security rule is the same as the flight number shown in the data query command, and the date shown in the data query command is within the date range shown in the data security rule. The data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data.

[0108] Optionally, the rule acquisition unit 100 is specifically used for: after receiving a data query command input by the user, determining whether the data query command contains a flight number and a date; if the data query command contains a flight number and a date, determining whether the preset data security rule table contains a target data security rule; if the data security rule table contains a target data security rule, extracting the target data security rule from the data security rule table.

[0109] The rule acquisition unit 100 is also used to: extract flight segments from passenger reservation records when the data query command does not contain flight numbers and dates, but contains passenger reservation records, and obtain the flight number containing the flight segment and the flight date of the flight segment from the civil aviation reservation system, and identify the obtained flight number as the flight number shown in the data query command, and the flight date of the flight segment as the date shown in the data query command.

[0110] The rule acquisition unit 100 is also used to: extract the flight segment from the ticket number when the data query command does not contain the flight number and date, but contains the ticket number, and obtain the flight number containing the flight segment and the flight date of the flight segment from the civil aviation reservation system, and identify the obtained flight number as the flight number shown in the data query command, and the flight date of the flight segment as the date shown in the data query command.

[0111] The rule acquisition unit 100 is also used to: obtain the civil aviation business data requested by the data query command from the civil aviation reservation system when the data security rule table does not contain the target data security rule, and display the obtained civil aviation business data to the user through a preset interface.

[0112] The data display unit 200 is used to retrieve the civil aviation business data requested by the data query command from the civil aviation reservation system when the user's agent account and user level meet the target data rules and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rules, and to display the retrieved civil aviation business data to the user through a preset interface.

[0113] Optionally, the data display unit 200 is also used to: display an error message to the user through a preset interface when the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is different from the type of civil aviation business data that the user is allowed to read in the target data rules.

[0114] The data display unit 200 is also used to display error messages to users through a preset interface when the user's agent account and user level do not both meet the target data rules.

[0115] In summary, this embodiment uses data security rules to determine the read permissions for various types of civil aviation business data (including flight data, passenger order data, and electronic ticket data), ensuring that such data can only be queried by users with read permissions, thereby effectively improving the security of various types of civil aviation business data in the civil aviation reservation system.

[0116] It should be noted that the units described in the embodiments of this application can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0117] Furthermore, the functions described above in the embodiments of this application can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SOCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0118] This application also provides a computer-readable storage medium including a stored program, wherein the program executes the data security protection method provided in this application.

[0119] This application also provides a data security protection device, including a processor, a memory, and a bus. The processor and the memory are connected via the bus. The memory is used to store programs, and the processor is used to run the programs. When the programs run, they execute the data security protection method provided in this application, including the following steps:

[0120] Based on the flight number and date indicated by the user-input data query command, target data security rules are retrieved from a preset data rule table. These target data security rules include data security rules that meet preset conditions. The preset conditions are: the flight number indicated by the data security rule is the same as the flight number indicated by the data query command, and the date indicated by the data query command is within the date range indicated by the data security rule. The data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data.

[0121] If the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data rules, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface.

[0122] Specifically, based on the above embodiments, it also includes:

[0123] If the user's agent account and user level both meet the target data rules, and the type of civil aviation business data requested by the data query command is different from the type of civil aviation business data that the user is allowed to read in the target data rules, an error message will be displayed to the user through the preset interface.

[0124] Specifically, based on the above embodiments, it also includes:

[0125] If the user's agent account and user level do not both meet the target data rules, an error message will be displayed to the user through the preset interface.

[0126] Specifically, based on the above embodiments, the step of obtaining target data security rules from a preset data rule table based on the flight number and date indicated by the user-input data query command includes:

[0127] After receiving a data query command input by the user, determine whether the data query command contains a flight number and a date;

[0128] If the data query command contains the flight number and the date, determine whether the preset data security rule table contains the target data security rule;

[0129] If the target data security rule is contained in the data security rule table, the target data security rule is extracted from the data security rule table.

[0130] Specifically, based on the above embodiments, after determining whether the data query command contains a flight number and a date, the method further includes:

[0131] If the data query command does not contain the flight number and the date, but contains passenger reservation records, the flight segment is extracted from the passenger reservation records, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command.

[0132] Specifically, based on the above embodiments, after determining whether the data query command contains a flight number and a date, the method further includes:

[0133] If the data query command does not contain the flight number and the date, but contains the ticket number, the flight segment is extracted from the ticket number, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command.

[0134] Specifically, based on the above embodiments, after determining whether the preset data security rule table contains the target data security rule, the method further includes:

[0135] If the target data security rule is not included in the data security rule table, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface.

[0136] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

[0137] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0138] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for ensuring data security, characterized in that, include: Based on the flight number and date shown in the user's input data query command, retrieve the target data security rules from the preset data rule table; The target data security rules include data security rules that meet preset conditions; the preset conditions are: the flight number shown in the data security rules is the same as the flight number shown in the data query command, and the date shown in the data query command is within the date range shown in the data security rules; the data security rules include the correspondence between flight number, date range, agent account, user level, and read permissions for various types of civil aviation business data; If the user's agent account and user level both meet the target data security rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data security rules, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface. The method of retrieving target data security rules from a preset data rule table based on the flight number and date indicated by the user-input data query command includes: After receiving a data query command input by the user, determine whether the data query command contains a flight number and a date; If the data query command contains the flight number and the date, determine whether the preset data security rule table contains the target data security rule; If the target data security rule is contained in the data security rule table, the target data security rule is extracted from the data security rule table. If the data query command does not contain the flight number and the date, but contains passenger reservation records, the flight segment is extracted from the passenger reservation records, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command. If the data query command does not contain the flight number and the date, but contains the ticket number, the flight segment is extracted from the ticket number, and the flight number containing the flight segment and the flight date of the flight segment are obtained from the civil aviation reservation system. The obtained flight number is identified as the flight number shown in the data query command, and the flight date of the flight segment is identified as the date shown in the data query command. If the target data security rule is not included in the data security rule table, the civil aviation business data requested by the data query command is obtained from the civil aviation reservation system, and the obtained civil aviation business data is displayed to the user through a preset interface.

2. The method according to claim 1, characterized in that, Also includes: If the user's agent account and user level both meet the target data security rules, and the type of civil aviation business data requested by the data query command is different from the type of civil aviation business data that the user is allowed to read in the target data security rules, an error message will be displayed to the user through the preset interface.

3. The method according to claim 1, characterized in that, Also includes: If the user's agent account and user level do not both meet the target data security rules, an error message will be displayed to the user through the preset interface.

4. A data security protection device, characterized in that, include: The rule acquisition unit is used to acquire target data security rules from a preset data rule table based on the flight number and date indicated by the user-input data query command. The target data security rules include data security rules that meet preset conditions. These preset conditions are: the flight number indicated by the data security rule is the same as the flight number indicated by the data query command, and the date indicated by the data query command is within the date range indicated by the data security rule. The data security rules include the correspondence between flight numbers, date ranges, agent accounts, user levels, and read permissions for various types of civil aviation business data. The data display unit is used to obtain the civil aviation business data requested by the data query command from the civil aviation reservation system when the user's agent account and user level both meet the target data security rules, and the type of civil aviation business data requested by the data query command is the same as the type of civil aviation business data that the user is allowed to read in the target data security rules, and to display the obtained civil aviation business data to the user through a preset interface. The rule acquisition unit is specifically used for: after receiving a data query command input by a user, determining whether the data query command contains a flight number and a date; if the data query command contains a flight number and a date, determining whether the preset data security rule table contains a target data security rule; if the data security rule table contains a target data security rule, extracting the target data security rule from the data security rule table. The rule acquisition unit is also used to: extract the flight segment from the passenger reservation record when the data query command does not contain the flight number and date, but contains the passenger reservation record, and obtain the flight number containing the flight segment and the flight date of the flight segment from the civil aviation reservation system, and identify the obtained flight number as the flight number shown in the data query command, and the flight date of the flight segment as the date shown in the data query command. The rule acquisition unit is also used to: extract the flight segment from the ticket number when the data query command does not contain the flight number and date, but contains the ticket number, and obtain the flight number containing the flight segment and the flight date of the flight segment from the civil aviation reservation system, and identify the obtained flight number as the flight number shown in the data query command, and the flight date of the flight segment as the date shown in the data query command. The rule acquisition unit is also used to: obtain the civil aviation business data requested by the data query command from the civil aviation reservation system when the data security rule table does not contain the target data security rule, and display the obtained civil aviation business data to the user through a preset interface.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program executes the data security protection method according to any one of claims 1-3.

6. A data security protection device, characterized in that, include: Processor, memory, and bus; The processor and the memory are connected via the bus; The memory is used to store a program, and the processor is used to run the program, wherein the program executes the data security protection method according to any one of claims 1-3 when it runs.

Images