Flight status change monitoring method, device and related equipment
By implementing the method of inputting monitoring conditions on the front-end page in the flight status monitoring system and calling the back-end interface to query the database regularly, the problems of unintuitive operations and unclear feedback in the existing technology are solved, and the efficiency and user experience of flight status change monitoring are improved , reduces costs.
Patent Information
- Application Number
- CN202310035690.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-10
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2043-01-10
AI Technical Summary
The existing flight status monitoring system is not intuitive to operate, and the newly enrolled personnel are prone to errors inadequate experience, and the feedback is unclear, which affects efficiency and cost.
It provides a flight status change monitoring method, input monitoring conditions through the front-end page, and call the backend interface regularly to query the database after verification, display flight status change information, and record error information, supporting filtering and retry operations of warning and failure information.
Improves the intuitiveness and work efficiency of flight status change monitoring, reduces operational errors and costs, and enhances the usability and user experience of the system.
Smart Images

Figure CN116052480B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of aviation data processing, and in particular to a flight status change monitoring method, device and related equipment. Background Art
[0002] With the development of the civil aviation industry, it is common to change the status of flights based on the original plan, such as temporary changes in flight schedules and aircraft models. Due to the impact of the epidemic, flight delays and cancellations, and changes in aircraft models or cabin space are becoming more frequent. For airport or airline personnel, every operator may perform flight status change operations. Therefore, it is necessary to provide a system for the control room personnel to monitor the status change operations of all flights.
[0003] In the prior art, the traditional flight status monitoring system monitors the flight status through black screen instructions. Airlines and airports need to train their personnel. Moreover, new personnel lack experience and are prone to operating errors or repeated operations. In addition, the existing flight status monitoring system's feedback on operation results (such as the processing results of status changes, specific information of status changes, etc.) is not intuitive, which can easily cause a relatively large impact. Summary of the invention
[0004] In view of this, an embodiment of the present invention provides a flight status change monitoring method, device and related equipment to achieve the purpose of intuitively monitoring flight status changes, improving work efficiency and reducing costs.
[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:
[0006] A first aspect of an embodiment of the present invention discloses a flight status change monitoring method, the method comprising:
[0007] When the logged-in user has the operation authority for the current page of the front end, obtaining the monitoring condition input by the logged-in user through the current page of the front end, the monitoring condition at least including the monitoring frequency preset by the logged-in user;
[0008] Verifying the monitoring conditions;
[0009] If the monitoring condition passes the verification, according to the monitoring frequency preset by the logged-in user, a pre-established background interface is called regularly to query whether there is flight status change information matching the monitoring condition in the pre-established database;
[0010] If so, the current page of the front end displays the flight status change information in a list form;
[0011] If it does not exist, the first error information obtained is recorded in the error log.
[0012] Optionally, before the logged-in user has the operation permission for the current page on the front end, it also includes:
[0013] When it is detected that the logged-in user exists in the front end, the account information of the logged-in user is obtained;
[0014] According to the account information, determine whether the logged-in user has the operation authority of the current page;
[0015] If not, record the operation of the logged-in user in the user operation log;
[0016] If so, execute the step of obtaining the monitoring conditions input by the logged-in user through the current page of the front end.
[0017] Optionally, also include:
[0018] Obtain the warning label selected by the logged-in user through the current page of the front end;
[0019] According to the warning tag, the first flight status change information matching the warning tag in the flight status change information is filtered, so that the current page of the front end displays the first flight status change information.
[0020] Optionally, also include:
[0021] Obtain the failed tag selected by the logged-in user through the current page of the front end;
[0022] According to the failure tag, filtering the second flight status change information that matches the failure tag in the flight status change information, so that the current page of the front end displays the second flight status change information;
[0023] Obtain any second flight status change information and retry tag selected by the logged-in user through the current page of the front end;
[0024] Based on the second flight status change information, obtaining a message corresponding to the second flight status change information, re-calling the background interface, and modifying the second flight status change information;
[0025] For the second flight status change information that has been successfully modified, setting the status corresponding to the second flight status change information to operation success;
[0026] For the second flight status change information that fails to be modified, the obtained retry error information is recorded in the error log.
[0027] Optionally, also include:
[0028] Obtaining multiple pieces of second flight status change information and batch retry tags selected by the logged-in user through the current page of the front end;
[0029] Based on the plurality of pieces of second flight status change information, obtaining messages corresponding to the plurality of pieces of second flight status change information, re-calling the background interface, and modifying the plurality of pieces of second flight status change information;
[0030] For the second flight status change information that has been successfully modified, setting the status corresponding to the plurality of pieces of the second flight status change information to operation success;
[0031] For the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, so that the current page of the front end displays the processing result details of the second flight status change information that failed to be modified.
[0032] A second aspect of an embodiment of the present invention discloses a flight status change monitoring device, the device comprising:
[0033] A first acquisition module, used for acquiring monitoring conditions input by the logged-in user through the current page of the front end when the logged-in user has the operation authority of the current page of the front end, wherein the monitoring conditions at least include the monitoring frequency preset by the logged-in user;
[0034] A verification module, used for verifying the monitoring conditions;
[0035] A query module, for periodically calling a pre-established backend interface according to the monitoring frequency preset by the logged-in user if the monitoring condition passes the verification, to query whether there is flight status change information matching the monitoring condition in the pre-established database;
[0036] A display module, for, if present, causing the current page of the front end to display the flight status change information in a list form;
[0037] The first recording module is used to record the obtained first error information in an error log if it does not exist.
[0038] Optionally, before the first acquisition module is used when the logged-in user has the operation authority of the current page of the front end, it also includes:
[0039] A second acquisition module is used to acquire the account information of the logged-in user when it is detected that the logged-in user exists in the front end;
[0040] A judgment module, used for judging whether the logged-in user has the operation authority of the current page according to the account information, and if not, executing the second recording module; if yes, executing the first obtaining module;
[0041] The second recording module is used to record the operations of the logged-in user in a user operation log.
[0042] Optionally, also include:
[0043] A third acquisition module is used to acquire the warning label selected by the logged-in user through the current page of the front end;
[0044] The first filtering module is used to filter the first flight status change information matching the warning tag in the flight status change information according to the warning tag, so that the current page of the front end displays the first flight status change information.
[0045] A third aspect of an embodiment of the present invention discloses an electronic device, which is used to run a program, wherein when the program is run, the flight status change monitoring method as described in any one of the first aspect of the embodiment of the present invention is executed.
[0046] A fourth aspect of an embodiment of the present invention discloses a storage medium, which includes a flight status change monitoring program, wherein when the program is executed by a processor, the flight status change monitoring method as described in any one of the first aspect of the embodiment of the present invention is implemented.
[0047] Based on the above-mentioned embodiment of the present invention, a flight status change monitoring method, device and related equipment are provided, the method includes: when the logged-in user has the operation authority of the current page of the front end, obtaining the monitoring conditions input by the logged-in user through the current page of the front end, the monitoring conditions at least include the monitoring frequency preset by the logged-in user; verifying the monitoring conditions; if the monitoring conditions pass the verification, according to the monitoring frequency preset by the logged-in user, regularly calling the pre-established background interface to query whether there is flight status change information matching the monitoring conditions in the pre-established database; if there is, the current page of the front end displays the flight status change information in the form of a list; if not, the first error information obtained is recorded in the error log. In this scheme, if the monitoring conditions pass the verification, after the backend interface is regularly called to query the database for flight status change information matching the monitoring conditions, the front end is displayed The flight status change information is, thereby facilitating flight status change monitoring, improving work efficiency and reducing costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0049] Figure 1 A schematic diagram of the architecture of a flight status change monitoring system provided by an embodiment of the present invention;
[0050] Figure 2 A flowchart of a flight status change monitoring method provided by an embodiment of the present invention;
[0051] Figure 3 A flowchart of an operation of checking flight status change information with a processing result of warning based on displayed flight status change information provided by an embodiment of the present invention;
[0052] Figure 4 A schematic diagram of a flow chart of retrying flight status change information with a failed processing result based on displayed flight status change information provided by an embodiment of the present invention;
[0053] Figure 5 A schematic diagram of the structure of a flight status change monitoring device provided by an embodiment of the present invention;
[0054] Figure 6 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0055] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 are within the scope of protection of the present invention.
[0056] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part 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". The relevant definitions of other terms will be given in the following description.
[0057] It should be noted that the concepts such as "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 or interdependence of the functions performed by these devices, modules or units.
[0058] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0059] As can be seen from the background technology, the traditional flight status monitoring system monitors the flight status through black screen instructions. Airlines and airports need to train personnel. Moreover, new personnel are inexperienced and prone to operating errors or repeated operations. In addition, the existing flight status monitoring system's feedback on operation results (such as the processing results of status changes, specific information of status changes, etc.) is not intuitive, which can easily cause a relatively large impact.
[0060] Therefore, an embodiment of the present invention provides a flight status change monitoring method, device and related equipment. If the monitoring conditions pass the verification, after the background interface is called periodically to query the database for flight status change information that matches the monitoring conditions, the front end will display the flight status change information, thereby facilitating flight status change monitoring, improving work efficiency and reducing costs.
[0061] First, a schematic diagram of the architecture of a flight status change monitoring system to which a flight status change monitoring method / device of the present application is applicable is introduced. Figure 1 As shown, the flight status change monitoring system includes: an authority control module 11, a front end 12, a log processing module 13, a timed task module 14 and a server 15.
[0062] The authority control module 11 is used to determine whether to display certain information or whether certain functions are allowed to be operated based on the information (airline, terminal, level) bound to the work number used by the operator when logging in.
[0063] Among them, the front end 12 intercepts the operations that are not allowed, thereby reducing the request pressure of the background interface.
[0064] For example, Air China staff cannot operate flights of other airlines. For another example, accounts with the role of controller cannot perform certain functions (such as operations on locked flights). These functions can only be performed by accounts with the role of director of control.
[0065] The front end 12 provides an intuitive page display for users to perform corresponding flight status change monitoring operations. Users can set monitoring conditions in the front end 12 page, establish monitoring tasks through the scheduled task module 14, and the results will be displayed in the page in the form of a list. Users can filter failed tasks in the front end 12 page and perform a "retry" operation.
[0066] The log processing module 13 records all operations performed by operators, whether successful or failed, in logs (including user operation logs, front-end and back-end interaction logs, error logs, etc.). Some abnormal logs or sensitive operation logs will be transmitted back when the system is idle, and manual transmission of logs or snapshot information when an abnormality occurs is also provided for developers to optimize.
[0067] The user operation log is used to record the user's operations, for example, what button was clicked and when, and what page was entered.
[0068] The error log is used to record system error information.
[0069] The server 15 is used to process the relevant operations of specifically implementing the flight status change monitoring.
[0070] based on Figure 1 The process of implementing flight status change monitoring in the public flight status change monitoring system is as follows:
[0071] The authority control module 11 detects whether there is a logged-in user in the front end 12, and when it is detected that there is a logged-in user in the front end, obtains the account information of the logged-in user.
[0072] The authority control module 11 determines whether the logged-in user has the operation authority for the current page based on the account information.
[0073] If not, the log processing module 13 records the operation of the logged-in user in the user operation log.
[0074] If so, the logged-in user inputs the monitoring conditions through the front end 12 .
[0075] The monitoring conditions include at least the monitoring frequency preset by the logged-in user.
[0076] The server 15 obtains the monitoring conditions input by the logged-in user through the front-end page and verifies the monitoring conditions.
[0077] If the monitoring conditions pass the verification, the pre-established background interface will be called regularly according to the monitoring frequency preset by the logged-in user to query whether there is flight status change information matching the monitoring conditions in the pre-established database.
[0078] If it exists, the current page on the front end will display the flight status change information in list form.
[0079] If it does not exist, the first error information obtained is recorded in the error log.
[0080] When a logged-in user needs to view flight status change information with a processing result of a warning, the server end 15 obtains the warning tag selected by the logged-in user through the current page of the front end, and based on the warning tag, filters the first flight status change information in the flight status change information that matches the warning tag, so that the current page of the front end displays the first flight status change information.
[0081] When a logged-in user needs to retry the flight status change information whose processing result is failed, the server end 15 obtains the failure tag selected by the logged-in user through the current page of the front end, and based on the failure tag, filters the second flight status change information that matches the failure tag in the flight status change information, so that the current page of the front end displays the second flight status change information.
[0082] The server side 15 obtains different quantities of second flight status change information and retry type tags selected by the logged-in user through the current page of the front end.
[0083] Among them, the retry type tags include retry tags and batch retry tags.
[0084] The server 15 obtains messages corresponding to different numbers of second flight status change information based on different numbers of second flight status change information and retry type tags.
[0085] Re-call the background interface to modify the status change information of the second flight with different quantities.
[0086] If the modification is successful, the status corresponding to the second flight status change information is set to operation successful.
[0087] If the recognition is modified, the resulting retry error information will be recorded in the error log.
[0088] It should be noted that this system does not involve underlying data processing, and all data comes from the corresponding background interface. This system replaces the black screen with a graphical interface, and replaces the editing of instructions with the interaction of input boxes and buttons. After the user operates (enters data + clicks the button), this system will automatically assemble the required instructions, call the background interface, and display the echo in the graphical interface after a certain rendering (for example, the monitoring result list will display the data involved in the result in a flat and intuitive manner).
[0089] Based on the above-mentioned embodiment of the present invention, a flight status change monitoring system is provided. If the monitoring conditions pass the verification, after the background interface is called regularly to query the database for flight status change information that matches the monitoring conditions, the front end will display the flight status change information, thereby facilitating flight status change monitoring, improving work efficiency and reducing costs.
[0090] Based on the flight status change monitoring system shown above, Figure 2 , which is a flow chart of a flight status change monitoring method provided by an embodiment of the present invention.
[0091] The flight status change monitoring method mainly includes the following steps:
[0092] Step S201: Check whether there is a logged-in user at the front end. If so, execute step S202; if not, end the operation.
[0093] In the process of implementing step S201, the user logs in to the flight status change monitoring system through the front end using his account password. The flight status change monitoring system detects the user's login status. If the user has successfully completed the login, it means that the user is a logged-in user, and step S202 is executed. If not, it means that the user has not completed the login, and the operation is terminated directly.
[0094] Step S202: Obtain the account information of the logged-in user.
[0095] In the specific implementation of step S202, when it is determined that there is a logged-in user at the front end, the flight status change monitoring system obtains the account information of the logged-in user.
[0096] Step S203: Based on the account information, determine whether the logged-in user has the operation authority for the current page. If so, execute step S204; if not, execute step S208.
[0097] In the process of implementing step S203, it is determined based on the account information whether the logged-in user has the authority to operate the flight status change monitoring system. Specifically, it is determined whether the logged-in user has the operation authority of the current page of the front end. If so, step S204 is executed. If not, it means that the logged-in user cannot perform any operation on the flight status change monitoring system, and step S208 is executed.
[0098] Step S204: Acquire the monitoring conditions input by the logged-in user through the current page of the front end.
[0099] In step S204, the monitoring condition at least includes the monitoring frequency preset by the logged-in user.
[0100] Optionally, monitoring conditions also include airline and flight number.
[0101] In the process of specifically implementing step S204, when it is determined that the logged-in user has the authority to operate the flight status change monitoring system, that is, when it is determined that the logged-in user has the authority to operate the current page of the front end, the logged-in user inputs the monitoring conditions through the current page of the front end, and the flight status change monitoring system obtains the monitoring conditions input by the logged-in user through the current page of the front end.
[0102] It should be noted that in actual applications, after the user enters the monitoring conditions, the monitoring process is triggered after clicking the "Start Monitoring" button.
[0103] Step S205: Verify the monitoring conditions. If the verification passes, execute step S206. If the verification fails, return to execute step S204.
[0104] Take an example to illustrate how to verify the monitoring conditions. For example, the flight status change monitoring system verifies that the airline company input must comply with the rules (two alphanumeric characters), the flight number must be legal (3-4 digits + 0-1 letter suffix), and the monitoring frequency must be legal (minimum 5 minutes, maximum 30 minutes).
[0105] In the process of implementing step S205, the flight status change monitoring system verifies the monitoring conditions. If the verification is passed, step S206 is executed. If the verification is not passed, a pop-up window is displayed on the front end to prompt the user to re-enter the information, and the system returns to step S204.
[0106] Step S206: According to the monitoring frequency preset by the logged-in user, the pre-established background interface is called regularly to query whether there is flight status change information matching the monitoring conditions in the pre-established database. If so, execute step S207; if not, execute step S209.
[0107] In the process of implementing step S206, when it is determined that the monitoring conditions have passed the verification, the pre-established background interface is called at a fixed time according to the monitoring frequency preset by the logged-in user, and the flight status change information matching the monitoring conditions in the pre-established database is queried. Specifically, the background "Query Real-time Task Details" interface is called to query whether there is flight status change information matching the monitoring conditions in the pre-established database. If so, it is determined that the query is successful, and step S207 is executed. If not, it is determined that the query fails, and step S209 is executed.
[0108] Step S207: The current page of the front end displays the flight status change information in a list format.
[0109] In the specific implementation of step S207, when it is determined that there is flight status change information matching the monitoring condition in the database, the current page of the front end displays the flight status change information in a list form.
[0110] Step S208: Record the operations of the logged-in user in the user operation log.
[0111] In the specific implementation of step S208, when it is determined that the logged-in user does not have the authority to operate the flight status change monitoring system, that is, when it is determined that the logged-in user does not have the operation authority of the current page, the operation of the logged-in user is recorded in the user operation log and the operation is exited.
[0112] Step S209: Record the obtained first error information in the error log.
[0113] The first error message is illustrated by an example, for example, a background interface call timeout, a network exception, etc.
[0114] In the specific implementation of step S209, when it is determined that no flight status change information matching the monitoring condition is found in the database, the obtained first error information is recorded in the error log.
[0115] Optionally, based on the flight status change monitoring method provided above, after the flight status change information matching the monitoring condition is found in the database, the front-end page displays the flight status change information in the form of a list, and based on the displayed flight status change information, the operation of checking the flight status change information with a processing result of warning is performed, as follows: Figure 3 As shown, it mainly includes the following steps:
[0116] Step S301: Obtain the warning label selected by the logged-in user through the current page of the front end.
[0117] In the process of implementing step S301, after the front-end page displays the flight status change information in the form of a list, the logged-in user clicks the "Warning" button on the front-end page, specifically clicks the "Warning" label above the result list, thereby triggering a filtering operation. The flight status change monitoring system then obtains the warning label selected by the logged-in user through the current page of the front end.
[0118] Step S302: According to the warning tag, the first flight status change information matching the warning tag is filtered in the flight status change information, so that the current page of the front end displays the first flight status change information.
[0119] In the process of implementing step S302, the flight status change monitoring system filters out the flight status change information with a processing result of "warning" in the result list according to the warning label, and then displays its detailed information. In other words, the first flight status change information that matches the warning label in the flight status change information is filtered out, so that the current page of the front end displays the first flight status change information.
[0120] It should be noted that the detailed information includes but is not limited to the change type, processing flow, processing result details, operation time and operator.
[0121] Optionally, based on the flight status change monitoring method provided above, after the flight status change information matching the monitoring condition is found in the database, the front-end page displays the flight status change information in the form of a list, and based on the displayed flight status change information, a retry operation is performed on the flight status change information with a failed processing result, as follows: Figure 4 As shown, it mainly includes the following steps:
[0122] Step S401: Obtain the failed tag selected by the logged-in user through the current page of the front end.
[0123] In the process of implementing step S401, after the front-end page displays the flight status change information in the form of a list, the logged-in user clicks the "Failure" button on the front-end page, specifically clicks the "Failure" label above the result list, thereby triggering a filtering operation. The flight status change monitoring system then obtains the failure label selected by the logged-in user through the current page of the front end.
[0124] Step S402: According to the failure tag, the second flight status change information matching the failure tag in the flight status change information is filtered, so that the current page of the front end displays the second flight status change information.
[0125] In the process of implementing step S402, the flight status change monitoring system filters out the flight status change information with a processing result of "failure" in the result list according to the failure label, and then displays its detailed information. In other words, the second flight status change information that matches the failure label in the flight status change information is filtered out, so that the current page of the front end displays the second flight status change information.
[0126] It should be noted that if the logged-in user selects a second flight status change information and a retry tag through the current page of the front end, step S403 is executed.
[0127] If the logged-in user selects multiple second flight status change information and batch retry tags through the current page of the front end, step S407 is executed.
[0128] Step S403: Obtain any second flight status change information and retry tag selected by the logged-in user through the current page of the front end.
[0129] In the process of implementing step S403, after the front-end page displays the second flight status change information in the form of a list, the logged-in user selects one of the second flight status change information and clicks the "Retry" button on the front-end page to trigger a single change failure retry operation. The flight status change monitoring system then obtains any second flight status change information and retry label selected by the logged-in user through the current page of the front end.
[0130] Step S404: Based on the second flight status change information, a message corresponding to the second flight status change information is obtained, and the background interface is re-called to modify the second flight status change information.
[0131] In the process of specifically implementing step S404, after the flight status change monitoring system obtains the second flight status change information, it obtains the message corresponding to the second flight status change information, and then re-calls the background interface to modify the second flight status change information. Specifically, the background "change flight status" interface is re-called to modify the second flight status change information. In other words, the flight status change monitoring system obtains the message corresponding to the change, and re-calls the background flight status change interface to send the message for operation. That is to say, the flight status change monitoring system obtains the message corresponding to the change, and re-sends the message operation.
[0132] It should be noted that, if the message sending operation finds that an operation to modify the flight status (modify the departure time) has failed, then the interface for modifying the flight departure time can be called again to perform the operation.
[0133] Step S405: For the second flight status change information that has been successfully modified, the status corresponding to the second flight status change information is set to operation successful.
[0134] In the specific implementation of step S405, a table showing the successfully modified second flight status change information is determined on the front end, and the corresponding status in the processing result in the table is set to successful operation.
[0135] Step S406: For the second flight status change information that fails to be modified, the obtained retry error information is recorded in the error log.
[0136] In the specific implementation of step S406, relevant retry error information is obtained for the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, and a front-end pop-up window is displayed to prompt the user.
[0137] Step S407: Acquire multiple pieces of second flight status change information and batch retry tags selected by the logged-in user through the current page of the front end.
[0138] In the process of specifically implementing step S407, after the front-end page displays the second flight status change information in the form of a list, the logged-in user selects multiple pieces of second flight status change information, that is, the logged-in user checks multiple pieces of second flight status change information and clicks the "Batch Retry" button on the front-end page to trigger multiple change failure retry operations. The flight status change monitoring system then obtains the multiple pieces of second flight status change information and batch retry tags selected by the logged-in user through the current page of the front-end.
[0139] Step S408: Based on the multiple pieces of second flight status change information, messages corresponding to the multiple pieces of second flight status change information are obtained, and the background interface is re-called to modify the multiple pieces of second flight status change information.
[0140] In the process of specifically implementing step S408, after the flight status change monitoring system obtains multiple second flight status change information, it obtains the messages corresponding to the selected multiple second flight status change information, and then re-calls the background interface to modify these second flight status change information. Specifically, the background "change flight status" interface is re-called to modify these second flight status change information. In other words, the flight status change monitoring system obtains the messages corresponding to these changes, and re-calls the background flight status change interface to send the message for operation. That is to say, the flight status change monitoring system obtains the messages corresponding to these changes and re-sends the message operation.
[0141] Step S409: For the second flight status change information that has been successfully modified, the statuses corresponding to the plurality of second flight status change information are set to operation success.
[0142] In the specific implementation of step S409, a table showing multiple pieces of second flight status change information that have been successfully modified is determined, and the corresponding status in the processing result in the table is set to successful operation.
[0143] In actual applications, other systems are called to modify flight status information. After receiving a reply that the modification is successful, the flight status change monitoring system then modifies the result of the information.
[0144] Step S410: For the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, so that the current page of the front end displays the processing result details of the second flight status change information that failed to be modified.
[0145] Provide examples to illustrate the details of the processing results, such as the reason for the modification failure, the time of the modification failure, and the error code returned by the background.
[0146] In the process of specifically implementing step S410, relevant retry error information is obtained for the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, and the current page of the front end is made to display the processing result details of the second flight status change information that failed to be modified. That is to say, a table in which the front end displays multiple pieces of second flight status change information that failed to be modified, and the processing result details are added to the corresponding rows in the table.
[0147] Based on the above description, it can be understood that, for a flight, if an operation to change its status is performed (for example, the departure time is modified), the operation will be recorded in a database.
[0148] In the embodiment of the present invention, monitoring refers to monitoring all operation records of the flight within a certain time range.
[0149] For example, for a flight CA123, the query results are as follows:
[0150] 1. Modify the take-off time, operator XX, operation time XX, operation result - success;
[0151] 2. Modify the boarding gate, operator XX, operation time XX, operation result - failure (retry button).
[0152] It should be noted that for a flight, many roles will intensively modify the flight status within a period of time (such as the check-in role modifies the check-in counter, the boarding role modifies the boarding gate take-off time, etc.). As a control room, what is monitored is the operation record of all the modified status information summarized.
[0153] In the embodiment of the present invention, the control room can be understood as a server side.
[0154] Based on the flight status change monitoring method provided by the above-mentioned embodiment of the present invention, if the monitoring conditions pass the verification, after the background interface is called regularly to query the database for flight status change information that matches the monitoring conditions, the front end will display the flight status change information, thereby facilitating flight status change monitoring, improving work efficiency and reducing costs.
[0155] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of the boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0156] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.
[0157] The above-mentioned embodiment of the present invention Figure 2 Corresponding to the flight status change monitoring method shown in FIG. , the embodiment of the present invention also provides a flight status change monitoring device, such as Figure 5 As shown, the flight status change monitoring device includes: a first acquisition module 501, a verification module 502, a query module 503, a display module 504 and a first recording module 505.
[0158] The first acquisition module 501 is used to acquire the monitoring conditions input by the logged-in user through the current page of the front end when the logged-in user has the operation authority of the current page of the front end.
[0159] The monitoring conditions include at least the monitoring frequency preset by the logged-in user.
[0160] The verification module 502 is used to verify the monitoring conditions.
[0161] The query module 503 is used to, if the monitoring conditions pass the verification, periodically call the pre-established background interface according to the monitoring frequency preset by the logged-in user to query whether there is flight status change information matching the monitoring conditions in the pre-established database. If so, execute the display module; if not, execute the first recording module.
[0162] The display module 504 is used to display the flight status change information in a list format on the current page of the front end.
[0163] The first recording module 505 is used to record the obtained first error information in an error log.
[0164] Optional, based on the above Figure 5 The flight status change monitoring device shown is combined with Figure 5 Before the first acquisition module 501 is used when the logged-in user has the operation authority of the current page of the front end, the flight status change monitoring device is further provided with a second acquisition module, a judgment module and a second recording module.
[0165] The second acquisition module is used to acquire the account information of the logged-in user when it is detected that there is a logged-in user on the front end.
[0166] The judgment module is used to judge whether the logged-in user has the operation authority of the current page according to the account information. If not, the second recording module is executed; if yes, the first acquisition module is executed.
[0167] The second recording module is used to record the operations of the logged-in user in the user operation log.
[0168] Optional, based on the above Figure 5 The flight status change monitoring device shown is combined with Figure 5 The flight status change monitoring device is further provided with a third acquisition module and a first screening module.
[0169] The third acquisition module is used to obtain the warning label selected by the logged-in user through the current page of the front end.
[0170] The first filtering module is used to filter the first flight status change information matching the warning tag in the flight status change information according to the warning tag, so that the current page of the front end displays the first flight status change information.
[0171] Optional, based on the above Figure 5 The flight status change monitoring device shown is combined with Figure 5 The flight status change monitoring device is further provided with a fourth acquisition module, a second screening module, a fifth acquisition module, a first setting module and a third recording module.
[0172] The fourth acquisition module is used to obtain the failed tag selected by the logged-in user through the current page of the front end.
[0173] The second filtering module is used to filter the second flight status change information matching the failure tag in the flight status change information according to the failure tag, so that the current page of the front end displays the second flight status change information.
[0174] The fifth acquisition module is used to obtain any second flight status change information and retry label selected by the logged-in user through the current page of the front end; based on the second flight status change information, obtain the message corresponding to the second flight status change information, re-call the background interface, and modify the second flight status change information.
[0175] The first setting module is used to set the status corresponding to the second flight status change information as operation success for the successfully modified second flight status change information.
[0176] The third recording module is used to record the obtained retry error information in the error log for the second flight status change information that failed to be modified.
[0177] Optional, based on the above Figure 5 The flight status change monitoring device shown is combined with Figure 5 The flight status change monitoring device is further provided with a sixth acquisition module, a second setting module and a fourth recording module.
[0178] The sixth acquisition module is used to obtain multiple second flight status change information and batch retry tags selected by the logged-in user through the current page of the front end; based on the multiple second flight status change information, obtain the messages corresponding to the multiple second flight status change information, re-call the background interface, and modify the multiple second flight status change information.
[0179] The second setting module is used to set the status corresponding to the multiple pieces of second flight status change information as operation success for the successfully modified second flight status change information.
[0180] The fourth recording module is used to record the obtained retry error information in the error log for the second flight status change information that failed to be modified, so that the current page of the front end displays the processing result details of the second flight status change information that failed to be modified.
[0181] It should be noted that the specific principles and execution processes of each module in the flight status change monitoring device disclosed in the above embodiment of the present invention are the same as those of the flight status change monitoring method implemented in the above embodiment of the present invention. Please refer to the corresponding parts of the flight status change monitoring method disclosed in the above embodiment of the present invention, and will not be repeated here.
[0182] Based on the above-mentioned embodiment of the present invention, a flight status change monitoring device is provided. If the monitoring conditions pass the verification, after the background interface is called regularly to query the database for flight status change information that matches the monitoring conditions, the front end will display the flight status change information, thereby facilitating flight status change monitoring, improving work efficiency and reducing costs.
[0183] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0184] Another embodiment of the present application provides an electronic device, such as Figure 6 , which shows a schematic diagram of the structure of an electronic device 60 suitable for implementing an embodiment of the present invention. The electronic device in the embodiment of the present invention may include but is not limited to electronic devices such as desktop computers, laptop computers, tablet computers, and vehicle-mounted terminals.
[0185] like Figure 6 As shown, the electronic device 60 includes one or more processing devices 601, such as a central processing unit, a graphics processing unit, etc., and a memory 602, on which one or more programs are stored. When the one or more programs are executed by the one or more processing devices 601, the one or more processing devices 601 implement the flight status change monitoring method provided in any of the above embodiments.
[0186] Optionally, the electronic device may also include other components, see also Figure 6 , the processing device 601, the read-only memory ROM602 and the random access memory RAM603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604. Typically, the following devices can be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display, a speaker, a vibrator, etc., a storage device 608 including, for example, a magnetic tape, a hard disk, etc., and a communication device 609. The communication device 609 can allow the electronic device 60 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device 60 is shown with various devices, but it should be understood that it is not required to implement or have all the devices shown. More or fewer devices may be implemented or have instead.
[0187] Another embodiment of the present application provides a computer storage medium for storing a program, which, when executed, is used to implement the flight status change monitoring method provided in any one of the above embodiments.
[0188] Computer storage media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0189] Another embodiment of the present application provides a computer program product, which, when executed, is used to execute any of the above-mentioned flight status change monitoring methods.
[0190] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer storage medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 606, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.
[0191] In the detailed description section, this application repeats all the contents protected in the form of claims in the following form:
[0192] According to one or more embodiments disclosed in this application, Figure 2 A flight status change monitoring method is provided, comprising:
[0193] When the logged-in user has the operation authority for the current page of the front end, obtaining the monitoring condition input by the logged-in user through the current page of the front end, the monitoring condition at least including the monitoring frequency preset by the logged-in user;
[0194] Verifying the monitoring conditions;
[0195] If the monitoring condition passes the verification, according to the monitoring frequency preset by the logged-in user, a pre-established background interface is called regularly to query whether there is flight status change information matching the monitoring condition in the pre-established database;
[0196] If so, the current page of the front end displays the flight status change information in a list form;
[0197] If it does not exist, the first error information obtained is recorded in the error log.
[0198] According to one or more embodiments disclosed in this application, Figure 2 A method is provided when a logged-in user has the operation authority of the current page of the front end, and also includes:
[0199] When it is detected that the logged-in user exists in the front end, the account information of the logged-in user is obtained;
[0200] According to the account information, determine whether the logged-in user has the operation authority of the current page;
[0201] If not, record the operation of the logged-in user in the user operation log;
[0202] If so, execute the step of obtaining the monitoring conditions input by the logged-in user through the current page of the front end.
[0203] According to one or more embodiments disclosed in this application, Figure 3 Provides a method for viewing flight status change information with a warning result, including:
[0204] Obtain the warning label selected by the logged-in user through the current page of the front end;
[0205] According to the warning tag, the first flight status change information matching the warning tag in the flight status change information is filtered, so that the current page of the front end displays the first flight status change information.
[0206] According to one or more embodiments disclosed in this application, Figure 4 A method is provided to retry the flight status change information whose processing result is failed, including:
[0207] Obtain the failed tag selected by the logged-in user through the current page of the front end;
[0208] According to the failure tag, filtering the second flight status change information that matches the failure tag in the flight status change information, so that the current page of the front end displays the second flight status change information;
[0209] Obtain any second flight status change information and retry tag selected by the logged-in user through the current page of the front end;
[0210] Based on the second flight status change information, obtaining a message corresponding to the second flight status change information, re-calling the background interface, and modifying the second flight status change information;
[0211] For the second flight status change information that has been successfully modified, setting the status corresponding to the second flight status change information to operation success;
[0212] For the second flight status change information that fails to be modified, the obtained retry error information is recorded in the error log.
[0213] According to one or more embodiments disclosed in this application, Figure 4 A method for retrying flight status change information with a failed processing result is provided, and further includes:
[0214] Obtaining multiple pieces of second flight status change information and batch retry tags selected by the logged-in user through the current page of the front end;
[0215] Based on the plurality of pieces of second flight status change information, obtaining messages corresponding to the plurality of pieces of second flight status change information, re-calling the background interface, and modifying the plurality of pieces of second flight status change information;
[0216] For the second flight status change information that has been successfully modified, setting the status corresponding to the plurality of pieces of the second flight status change information to operation success;
[0217] For the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, so that the current page of the front end displays the processing result details of the second flight status change information that failed to be modified.
[0218] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, 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. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.
[0219] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope disclosed in the present application. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0220] The above description is only a preferred embodiment disclosed in this application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the disclosure of this application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the disclosure of this application (but not limited to) to form a technical solution.
Claims
1. A flight status change monitoring method, characterized in that: The method comprises: When the logged-in user has the operation authority of the current page of the front end, obtaining the monitoring conditions input by the logged-in user through the current page of the front end, the monitoring conditions at least including the monitoring frequency preset by the logged-in user; Verifying the monitoring conditions; If the monitoring condition passes the verification, according to the monitoring frequency preset by the logged-in user, a pre-established background interface is called regularly to query whether there is flight status change information matching the monitoring condition in the pre-established database; If so, the current page of the front end displays the flight status change information in a list form; If it does not exist, the first error information obtained is recorded in the error log; Obtain the warning label selected by the logged-in user through the current page of the front end; According to the warning tag, the first flight status change information matching the warning tag in the flight status change information is filtered, so that the current page of the front end displays the first flight status change information.
2. The method according to claim 1, characterized in that Before the logged in user has the operation permission of the current page of the front end, it also includes: When it is detected that the logged-in user exists in the front end, the account information of the logged-in user is obtained; According to the account information, determine whether the logged-in user has the operation authority of the current page; If not, record the operation of the logged-in user in the user operation log; If so, execute the step of obtaining the monitoring conditions input by the logged-in user through the current page of the front end.
3. The method according to claim 1, characterized in that Also includes: Obtain the failed tag selected by the logged-in user through the current page of the front end; According to the failure tag, filtering the second flight status change information that matches the failure tag in the flight status change information, so that the current page of the front end displays the second flight status change information; Obtain any second flight status change information and retry tag selected by the logged-in user through the current page of the front end; Based on the second flight status change information, obtaining a message corresponding to the second flight status change information, re-calling the background interface, and modifying the second flight status change information; For the second flight status change information that has been successfully modified, setting the status corresponding to the second flight status change information to operation success; For the second flight status change information that fails to be modified, the obtained retry error information is recorded in the error log.
4. The method according to claim 3, characterized in that Also includes: Obtaining multiple pieces of second flight status change information and batch retry tags selected by the logged-in user through the current page of the front end; Based on the plurality of pieces of second flight status change information, obtaining messages corresponding to the plurality of pieces of second flight status change information, re-calling the background interface, and modifying the plurality of pieces of second flight status change information; For the second flight status change information that has been successfully modified, setting the status corresponding to the plurality of pieces of the second flight status change information to operation success; For the second flight status change information that failed to be modified, the obtained retry error information is recorded in the error log, so that the current page of the front end displays the processing result details of the second flight status change information that failed to be modified.
5. A flight status change monitoring device, characterized in that: The device comprises: A first acquisition module, used for acquiring monitoring conditions input by the logged-in user through the current page of the front end when the logged-in user has the operation authority of the current page of the front end, wherein the monitoring conditions at least include the monitoring frequency preset by the logged-in user; A verification module, used for verifying the monitoring conditions; A query module, for periodically calling a pre-established backend interface according to the monitoring frequency preset by the logged-in user if the monitoring condition passes the verification, to query whether there is flight status change information matching the monitoring condition in the pre-established database; A display module, for, if present, causing the current page of the front end to display the flight status change information in a list form; A first recording module, used for recording the obtained first error information in an error log if the first error information does not exist; A third acquisition module is used to acquire the warning label selected by the logged-in user through the current page of the front end; The first filtering module is used to filter the first flight status change information matching the warning tag in the flight status change information according to the warning tag, so that the current page of the front end displays the first flight status change information.
6. The device according to claim 5, characterized in that Before the first acquisition module is used when the logged-in user has the operation authority of the current page of the front end, it also includes: A second acquisition module is used to acquire the account information of the logged-in user when it is detected that the logged-in user exists in the front end; A judgment module, used for judging whether the logged-in user has the operation authority of the current page according to the account information, and if not, executing the second recording module; if yes, executing the first obtaining module; The second recording module is used to record the operations of the logged-in user in a user operation log.
7. An electronic device, characterized in that: The electronic device is used to run a program, wherein the flight status change monitoring method according to any one of claims 1 to 4 is executed when the program is run.
8. A storage medium, characterized in that: The storage medium comprises a flight status change monitoring program, wherein the program, when executed by a processor, implements the flight status change monitoring method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Airport flight information display system
CN101150591A
Cooperated discharging system for air station departure flight
CN101344995A
Flight information data acquisition unit and processing method thereof
CN101609610A
Transit management system and method for hub airport
CN102073937A
Flight data processing method and scene monitoring front-end processor
CN104361769A
