CN112258023A - Flight plan management method, system and storage medium - Google Patents
Flight plan management method, system and storage medium Download PDFInfo
- Publication number
- CN112258023A CN112258023A CN202011125653.4A CN202011125653A CN112258023A CN 112258023 A CN112258023 A CN 112258023A CN 202011125653 A CN202011125653 A CN 202011125653A CN 112258023 A CN112258023 A CN 112258023A
- Authority
- CN
- China
- Prior art keywords
- flight
- flight plan
- management system
- information
- plan management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 193
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000000694 effects Effects 0.000 claims abstract description 23
- 230000008859 change Effects 0.000 claims abstract description 15
- 238000012508 change request Methods 0.000 claims description 17
- 238000012423 maintenance Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010200 validation analysis Methods 0.000 description 22
- 238000012545 processing Methods 0.000 description 9
- 230000010006 flight Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000008676 import Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001502 supplementing effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06315—Needs-based resource requirements planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Educational Administration (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a flight plan management method, a system and a storage medium, the method can automatically receive an SSIM file imported by a user by providing a flight plan management system, acquire information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user, change the code sharing flight corresponding relation or flight plan information in the flight plan management system based on the information in the specified date range, release the changed code sharing flight corresponding relation in the flight plan management system, generate a flight to be validated based on the changed flight plan information, release the flight to be validated after the flight to be validated takes effect, realize the automatic change of the code sharing flight corresponding relation and the flight plan information and the automatic release of the code sharing flight corresponding relation and the flight to be validated flight, thereby realizing the automatic management of the flight plan, the automatic management mode can shorten the management time and improve the management efficiency.
Description
Technical Field
The present application relates to the field of information processing technologies, and in particular, to a flight plan management method, system, and storage medium.
Background
Although the ticket selling of civil aviation passengers is automated, the sales can be carried out by an ICS (internet Control System) System. However, flight plan (e.g., code sharing flight plan) management is still accomplished by manually entering instructions into the ICS system.
However, the manual management of flight schedules is inefficient.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In order to solve the above technical problem, embodiments of the present application provide a flight plan management method, a flight plan management system, and a storage medium, where the technical scheme is as follows:
a flight plan management method is applied to a flight plan management system and comprises the following steps:
receiving an SSIM file imported by a user;
acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user;
based on the information in the appointed date range, changing the corresponding relation of the code sharing flight in the flight plan management system and/or changing the flight plan information;
after the corresponding relation of the code sharing flight in the flight plan management system is changed, the changed corresponding relation of the code sharing flight in the flight plan management system is issued;
after flight plan information in the flight plan management system is changed, generating a flight to be validated based on the changed flight plan information;
and issuing the flight to be validated after the flight to be validated takes effect.
A flight plan management system, comprising:
the receiving module is used for receiving the SSIM file imported by the user;
the acquisition module is used for acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user;
the first changing module is used for changing the corresponding relation of the code sharing flight in the flight plan management system and/or the flight plan information based on the information in the appointed date range;
the first issuing module is used for issuing the changed code sharing flight corresponding relation in the flight plan management system after the code sharing flight corresponding relation in the flight plan management system is changed;
the generating module is used for generating a flight to be validated based on the changed flight plan information after the flight plan information in the flight plan management system is changed;
and the second issuing module is used for issuing the flight to be validated after the flight to be validated takes effect.
A computer storage medium having a computer program stored thereon for execution by a processor to perform the steps of a flight plan management method as claimed in any one of the preceding claims.
Compared with the prior art, the beneficial effect of this application is:
in the application, by providing a flight plan management system, an SSIM file imported by a user can be automatically received, information in a specified date range is obtained from the SSIM file according to the type of the SSIM file imported by the user, a code sharing flight corresponding relation in the flight plan management system and/or flight plan information is changed based on the information in the specified date range, a changed code sharing flight corresponding relation in the flight plan management system is issued, a to-be-generated flight is generated based on the changed flight plan information, the to-be-generated flight is issued after the to-be-generated flight takes effect, automatic change of the code sharing flight corresponding relation and the flight plan information and automatic issue of the code sharing flight corresponding relation and the to-be-generated flight are realized, and automatic management of the flight plan is realized, the automatic management mode can shorten the management time and improve the management efficiency.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
Fig. 1 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 1 of the present application;
fig. 2 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 2 of the present application;
fig. 3 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 3 of the present application;
fig. 4 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 4 of the present application;
fig. 5 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 5 of the present application;
fig. 6 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 6 of the present application;
fig. 7 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 7 of the present application;
fig. 8 is a flowchart of a flight plan management method applied to a flight plan management system according to embodiment 8 of the present application;
fig. 9 is a schematic diagram of a logical structure of a flight plan management system provided in the present application.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "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". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
Referring to fig. 1, a flow chart of a flight plan management method applied to a flight plan management system provided in embodiment 1 of the present application is shown in fig. 1, where the method may include, but is not limited to, the following steps:
and step S11, receiving the SSIM file imported by the user.
In this embodiment, the flight plan management system is provided with a file import interface, and a user can import the SSIM file through the file import interface. And the flight schedule management system receives the SSIM file imported by the user through the file import interface.
And step S12, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
After receiving the SSIM file imported by the user, the SSIM file type may be determined according to the name of the SSIM file. If the name is CAXX, the head indicates that the SSIM file is a full flight plan file carried by CA; the designation CAUA head indicates that the SSIM file is UA as the carrier and CA as the marketer's full flight plan file.
And after receiving the SSIM file imported by the user, the information of the SSIM file (e.g., recording file name, operator, total number of messages in the file, successful number of message processing, failed number of message processing, status, etc.) may be recorded in a file table of the database for query.
The process of determining the successful number of message processing may be: judging whether the message format, flight information and flight rule configuration in the SSIM file are correct, and if so, considering that the message can be successfully processed; and counting the number of the messages which can be successfully processed as the message processing success number.
The process for determining the number of message processing failures comprises the following steps: judging whether the message format, flight information and flight rule configuration in the SSIM file are correct or not, and if not, determining that the message is failed to be processed; and counting the number of the messages which can fail to be processed as the number of the message processing failures.
In this embodiment, a specified date range may be specifically searched in Record2 of the SSIM file, and after the specified date range is found, information in the specified date range is acquired from the SSIM file according to the type of the SSIM file imported by the user.
Since different types of SSIM files contain different information, it is necessary to acquire information within a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
The types of SSIM files imported by the user may include: and characterizing the market party as the category of the navigation system belonging to the flight plan management system, or characterizing the carrier as the category of the navigation system belonging to the flight plan management system.
And step S13, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Based on the information in the specified date range, the change of the code sharing flight correspondence in the flight plan management system can be understood as:
s131, searching the corresponding relation of the code sharing flights in the appointed date range from a flight plan management system, and forming the searched corresponding relation of the code sharing flights into a corresponding relation set of the code sharing flights to be changed;
s132, comparing the corresponding relation of the code sharing flight in the information in the appointed date range with the corresponding relation set of the code sharing flight to be changed to obtain a comparison result;
s133, determining a first code sharing flight corresponding relation, a second code sharing flight corresponding relation or a third code sharing flight corresponding relation based on the comparison result;
the first code sharing flight corresponding relation is a corresponding relation which is in the information in the specified date range acquired from the SSIM file but is not in the code sharing flight corresponding relation set to be changed;
the second code sharing flight corresponding relation is the corresponding relation in the information in the specified date range acquired from the SSIM file and in the code sharing flight corresponding relation set to be changed;
the third code sharing flight corresponding relation is the corresponding relation in the information in the specified date range acquired from the SSIM file but in the code sharing flight corresponding relation set to be changed;
s134, adding the corresponding relation of the first code sharing flight to a flight set management system;
or, replacing the corresponding relationship of the code sharing flight in the flight set management system with the corresponding relationship of the second code sharing flight;
or, the state of the third code sharing flight corresponding relation in the code sharing flight corresponding relation set to be changed is modified to be invalid.
Changing the flight schedule information in the flight schedule management system based on the information in the specified date range may be understood as:
s135, searching the flight plan information in the appointed date range from the flight plan management system, and forming the searched flight plan information into a flight plan information set to be changed;
s136, comparing flight schedule information in the specified date range with the flight schedule information set to be changed to obtain a comparison result;
s137, determining first flight scheduling information, second flight scheduling information or third flight scheduling information based on the comparison result;
the first flight schedule information is flight schedule information which is in the information in the specified date range acquired from the SSIM file but is not in the flight schedule information set to be changed;
the second flight schedule information is flight schedule information in the set of flight schedule information to be changed in the information in the specified date range acquired from the SSIM file;
the third flight schedule information is flight schedule information in the specified date range acquired from the SSIM file but in the flight schedule information set to be changed;
s138, adding the first flight schedule information into a flight set management system;
or, replacing the second flight plan information with corresponding flight plan information in the flight set management system;
or, the state of the third flight plan information in the flight plan information set to be changed is modified to be invalid.
Step S14, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
In this embodiment, the flight plan management system provides a code sharing file validation interface, a user may input a confirmation instruction and a validation instruction to the flight plan management system through the code sharing file validation interface, and the flight plan management system confirms the correspondence relationship of the changed code sharing flight and performs validation operation.
Of course, the flight schedule management system may also actively confirm the correspondence relationship of the code sharing flights after the change, and perform the validation operation.
The flight plan management system can generate effective batches in sequence, take effect on the corresponding relation of the code sharing flights, and automatically release the changed corresponding relation of the code sharing flights to other systems in a standard SSM message form after the effective batches take effect.
If no abnormal condition appears in the whole effective process, the user does not need to intervene and can check the current effective progress and state on the effective monitoring page; if abnormity occurs in the validation process, the user can also check specific error details through the validation monitoring page, and temporarily adjust or cancel the error batch or flight so as to ensure that the validation continues normally.
And step S15, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
Generating a flight to be validated based on the changed flight schedule information may include:
s151, setting the flight state in a flight schedule of a database of a flight schedule management system as a flight to be cancelled based on the first flight schedule information;
the first flight plan information is flight plan information which is in the information within the specified date range acquired from the SSIM file but is not in the set of flight plan information to be changed.
Or S152, generating a new flight plan based on the second flight plan information, supplementing the flight information according to the rules set by the user and the system basic data, recording the flight plan in the flight plan table, and juxtaposing the flight state of the generated trusted flight plan as the to-be-validated flight so that the generated new flight plan is taken as the to-be-validated flight.
Or, based on the third flight plan information, the flight plan in the flight plan management system is updated, the flight information is supplemented according to the rules set by the user and the system basic data, the flight information is recorded in the flight plan table, the flight state of the updated flight plan is set to be validated, the updated flight plan is used as a to-be-validated flight, and meanwhile, the original flight plan state corresponding to the third flight plan information is set to be cancelled.
In this embodiment, if the flight schedule information in the specified date range is compared with the set of flight schedule information to be changed, and the obtained comparison result is that the flight schedule information in the specified date range is consistent with the flight schedule information in the set of flight schedule information to be changed, only the status of the flight schedule information may be recorded as successful processing, and no flight change is required, so as to reduce resource occupation and system processing efficiency.
And step S16, issuing the flight to be validated after the flight to be validated takes effect.
In this embodiment, the flight plan management system provides a flight validation interface, and a user may input a confirmation instruction and a validation instruction to the flight plan management system through the flight validation interface, and the flight plan management system confirms and validates the changed flight to be validated.
Of course, the flight plan management system may also actively confirm the flight to be validated and perform validation operation.
The flight plan management system can generate effective batches in sequence, the flight to be effective takes effect, and after the flight to be effective takes effect, the flight to be effective is automatically issued to other systems in a standard SSM message mode.
If no abnormal condition appears in the whole effective process, the user does not need to intervene and can check the current effective progress and state on the effective monitoring page; if abnormity occurs in the validation process, the user can also check specific error details through the validation monitoring page, and temporarily adjust or cancel the error batch or flight so as to ensure that the validation continues normally.
As another alternative embodiment of the present application, referring to fig. 2, there is provided a flowchart of an embodiment 2 of a flight plan management method provided in the present application, where this embodiment is mainly a refinement of the flight plan management method described in the above embodiment 1, as shown in fig. 2, the method may include, but is not limited to, the following steps:
and step S21, receiving the SSIM file imported by the user.
Step S22, if the category of the SSIM file imported by the user indicates that the market party is the airline department to which the flight plan management system belongs, acquiring the code sharing flight corresponding relation and flight plan message in the specified date range from the SSIM file.
When the category of the SSIM file imported by the user indicates that the market party is the airline driver to which the flight plan management system belongs, the code sharing flight correspondence in the flight plan management system needs to be changed based on the code sharing flight correspondence between the carrier and the market party in the SSIM file imported by the user, and the flight plan information serving as the market party in the flight plan management system needs to be changed based on the flight plan information of the carrier in the SSIM file imported by the user.
Step S22 is a specific implementation manner of step S12 in example 1.
And step S23, changing the correspondence of the code sharing flight in the flight plan management system based on the correspondence of the code sharing flight in the specified date range.
And step S24, changing flight schedule information in the flight schedule management system based on the flight schedule message in the specified date range.
Steps S23-S24 are a specific implementation of step S13 in example 1.
Step S25, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S26, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S27, issuing the flight to be validated after the flight to be validated takes effect.
The detailed procedures of steps S25-S27 can be found in the related descriptions of steps S14-S16 in embodiment 1, and are not repeated herein.
As another alternative embodiment of the present application, referring to fig. 3, there is provided a flowchart of an embodiment 3 of a flight plan management method provided in the present application, where this embodiment is mainly a refinement of the flight plan management method described in the above embodiment 1, as shown in fig. 3, the method may include, but is not limited to, the following steps:
and step S31, receiving the SSIM file imported by the user.
Step S32, if the type representation carrier of the SSIM file imported by the user is the airline driver to which the flight plan management system belongs, obtaining the code sharing flight corresponding relation in the specified date range from the SSIM file.
When the type representation carrier of the SSIM file imported by the user is the airline department to which the flight plan management system belongs, only the code sharing flight correspondence relationship is recorded in the SSIM file imported by the user, so that the code sharing flight correspondence relationship in the flight plan management system can be changed based on the code sharing flight correspondence relationship in the SSIM file imported by the user.
Step S32 is a specific implementation manner of step S12 in example 1.
And step S23, changing the correspondence of the code sharing flight in the flight plan management system based on the correspondence of the code sharing flight in the specified date range.
Step S23 is a specific implementation manner of step S13 in example 1.
Step S34, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
The detailed process of step 34 can be referred to the related description of step S14 in embodiment 1, and is not described herein again.
As another alternative embodiment of the present application, referring to fig. 4, a flowchart of an embodiment 4 of a flight plan management method provided by the present application is provided, where this embodiment is mainly an extension of the flight plan management method described in the foregoing embodiment 1, as shown in fig. 4, the method may include, but is not limited to, the following steps:
and step S41, receiving the SSIM file imported by the user.
And step S42, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
And step S43, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Step S44, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S45, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S46, issuing the flight to be validated after the flight to be validated takes effect.
The detailed procedures of steps S41-S46 can be found in the related descriptions of steps S11-S16 in embodiment 1, and are not repeated herein.
And step S47, pushing the changed flight schedule information in the flight schedule management system and/or the flight schedule information before the change to the passenger protection system.
And pushing the changed flight schedule information in the flight schedule management system and/or the flight schedule information before the change to the passenger protection system so that the passenger protection system confirms the flight protection state.
As another alternative embodiment of the present application, referring to fig. 5, a flowchart of an embodiment 5 of a flight plan management method provided by the present application is provided, where this embodiment is mainly an extension of the flight plan management method described in the foregoing embodiment 1, as shown in fig. 5, the method may include, but is not limited to, the following steps:
and step S51, receiving the SSIM file imported by the user.
And step S52, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
And step S53, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Step S54, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S55, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S56, issuing the flight to be validated after the flight to be validated takes effect.
The detailed procedures of steps S51-S56 can be found in the related descriptions of steps S11-S16 in embodiment 1, and are not repeated herein.
And step S57, displaying a protocol maintenance adjustment page, and responding to the flight correspondence change request when the flight correspondence change request input by the user is acquired in the protocol maintenance adjustment page, so as to change the code sharing flight correspondence in the flight plan management system.
In this embodiment, the flight plan management system displays the protocol maintenance adjustment page, which can be used at least for the user to input a flight correspondence change request on the protocol maintenance adjustment page, so as to ensure that the user can change a small number of code sharing flight correspondences, and adjust the code sharing flight correspondences more intuitively.
The flight correspondence change request input by the user may include: a new request, an update request, or a delete request.
As another alternative embodiment of the present application, referring to fig. 6, there is provided a flowchart of an embodiment 6 of a flight plan management method provided by the present application, where this embodiment is mainly an extension of the flight plan management method described in the foregoing embodiment 5, as shown in fig. 6, the method may include, but is not limited to, the following steps:
and step S61, receiving the SSIM file imported by the user.
And step S62, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
And step S63, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Step S64, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S65, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S66, issuing the flight to be validated after the flight to be validated takes effect.
And step S67, displaying a protocol maintenance adjustment page, and responding to the flight correspondence change request when the flight correspondence change request input by the user is acquired in the protocol maintenance adjustment page, so as to change the code sharing flight correspondence in the flight plan management system.
The detailed procedures of steps S61-S67 can be found in the related descriptions of steps S51-S57 in embodiment 5, and are not repeated herein.
Step S68, if an effective request of the user for the correspondence relationship of the changed code sharing flight in the flight plan management system is obtained in the protocol maintenance adjustment page, the correspondence relationship of the changed code sharing flight in the flight plan management system is made effective.
In this embodiment, the flight plan management system may further provide an validation interface on the protocol maintenance adjustment page, which is used to receive an validation request input by the user, and validate the correspondence relationship of the code sharing flight that is changed in the flight plan management system when the validation request of the user for the correspondence relationship of the code sharing flight that is changed in the flight plan management system is obtained, so as to ensure that the flight plan management system takes effect in time.
As another alternative embodiment of the present application, referring to fig. 7, there is provided a flowchart of an embodiment 7 of a flight plan management method, where this embodiment is mainly an extension of the flight plan management method described in the foregoing embodiment 1, as shown in fig. 7, the method may include, but is not limited to, the following steps:
and step S71, receiving the SSIM file imported by the user.
And step S72, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
And step S73, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Step S74, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S75, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S76, issuing the flight to be validated after the flight to be validated takes effect.
The detailed procedures of steps S71-S76 can be found in the related descriptions of steps S11-S16 in embodiment 1, and are not repeated herein.
And step S77, displaying a flight adjustment page, responding to the flight plan change request when the flight adjustment page acquires the flight plan change request input by the user, changing the flight plan information in the flight plan management system, and generating the flight to be used based on the changed flight plan information.
In this embodiment, the flight plan management system displays the protocol maintenance adjustment page, which can be used at least for the user to input a flight plan change request on the protocol maintenance adjustment page, so as to ensure that the user can change a small number of flight plans and adjust the flight plans more intuitively.
The flight plan change request input by the user may include: a new request, an update request, or a delete request.
As another alternative embodiment of the present application, referring to fig. 8, a flowchart of an embodiment 8 of a flight plan management method provided by the present application is provided, where this embodiment is mainly an extension of the flight plan management method described in the above embodiment 7, as shown in fig. 8, the method may include, but is not limited to, the following steps:
and step S81, receiving the SSIM file imported by the user.
And step S82, acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user.
And step S83, based on the information in the specified date range, changing the code-sharing flight correspondence and/or flight schedule information in the flight schedule management system.
Step S84, after the code sharing flight correspondence relationship in the flight plan management system is changed, issuing the changed code sharing flight correspondence relationship in the flight plan management system.
And step S85, after the flight schedule information in the flight schedule management system is changed, generating a flight to be validated based on the changed flight schedule information.
And step S86, issuing the flight to be validated after the flight to be validated takes effect.
And step S87, displaying a flight adjustment page, responding to the flight plan change request when the flight adjustment page acquires the flight plan change request input by the user, changing the flight plan information in the flight plan management system, and generating the flight to be used based on the changed flight plan information.
The detailed procedures of steps S81-S87 can be found in the related descriptions of steps S71-S77 in embodiment 1, and are not repeated herein.
Step S88, if an effective request of the user for the flight to be used is obtained in the flight adjustment page, taking effect on the flight to be used.
In this embodiment, the flight plan management system may further provide an effective interface on the agreement maintenance adjustment page, and is configured to receive an effective request input by the user, and take effect on the flight to be used when the effective request of the user for the flight to be used is obtained, so as to ensure that the flight to be used takes effect in time.
It is to be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
Next, the flight plan management system provided in the present application will be described, and the flight plan management system described below and the flight plan management method described above may be referred to in correspondence with each other.
Referring to fig. 9, the flight plan management system includes: the system comprises a receiving module 100, an obtaining module 200, a first changing module 300, a first publishing module 400, a generating module 500 and a second publishing module 600.
A receiving module 100, configured to receive an SSIM file imported by a user;
the acquisition module 200 is configured to acquire information within a specified date range from the SSIM file according to the type of the SSIM file imported by the user;
a first changing module 300, configured to change a code-sharing flight correspondence relationship in the flight plan management system and/or flight plan information based on the information in the specified date range;
a first publishing module 400, configured to, after a code sharing flight correspondence relationship in the flight plan management system is changed, publish the changed code sharing flight correspondence relationship in the flight plan management system;
the generating module 500 is configured to generate a flight to be validated based on the changed flight schedule information after the flight schedule information in the flight schedule management system is changed;
and a second issuing module 600, configured to issue the flight to be validated after the flight to be validated takes effect.
In this embodiment, the obtaining module 200 may be specifically configured to:
and if the category representation market party of the SSIM file imported by the user is the airline driver to which the flight plan management system belongs, acquiring the code sharing flight corresponding relation and the flight plan message in the specified date range from the SSIM file.
Accordingly, the first changing module 300 may specifically be configured to:
changing the corresponding relation of the code sharing flight in the flight plan management system based on the corresponding relation of the code sharing flight in the appointed date range;
and changing the flight plan information in the flight plan management system based on the flight plan message in the specified date range.
In this embodiment, the obtaining module 200 may be specifically configured to:
if the type representation carrier of the SSIM file imported by the user is the airline driver of the flight plan management system, acquiring the code sharing flight corresponding relation in the specified date range from the SSIM file;
accordingly, the first changing module 300 may specifically be configured to:
and changing the corresponding relation of the code sharing flight in the flight plan management system based on the corresponding relation of the code sharing flight in the specified date range.
In this embodiment, the flight plan management system may further include:
and the pushing module is used for pushing the changed flight plan information in the flight plan management system and/or the flight plan information before the change to the passenger protection system.
In this embodiment, the flight plan management system may further include:
and the second changing module is used for displaying a protocol maintenance adjustment page, responding to the flight corresponding relation changing request and changing the code sharing flight corresponding relation in the flight plan management system when the flight corresponding relation changing request input by the user is acquired in the protocol maintenance adjustment page.
In this embodiment, the flight plan management system may further include:
and the first validation module is used for validating the corresponding relation of the changed code sharing flight in the flight plan management system if a validation request of a user for the corresponding relation of the changed code sharing flight in the flight plan management system is acquired in the protocol maintenance adjustment page.
In this embodiment, the flight plan management system may further include:
and the third changing module is used for displaying a flight adjusting page, responding to the flight plan changing request when the flight adjusting page obtains the flight plan changing request input by the user, changing the flight plan information in the flight plan management system, and generating the flight to be used based on the changed flight plan information.
In this embodiment, the flight plan management system may further include:
and the second validation module is used for validating the flight to be used if the validation request of the user for the flight to be used is acquired from the flight adjustment page.
The modules described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a module does not in some cases constitute a limitation of the module itself, for example, the first obtaining module may also be described as a "module for obtaining at least one ticket change request".
The functions described herein above 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 a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In another embodiment of the application, a computer storage medium is provided, on which a computer program is stored, the computer program being executable by a processor to perform the steps of the flight plan management method as described in any one of method embodiments 1-8.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (10)
1. A flight plan management method is applied to a flight plan management system and comprises the following steps:
receiving an SSIM file imported by a user;
acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user;
based on the information in the appointed date range, changing the corresponding relation of the code sharing flight in the flight plan management system and/or changing the flight plan information;
after the corresponding relation of the code sharing flight in the flight plan management system is changed, the changed corresponding relation of the code sharing flight in the flight plan management system is issued;
after flight plan information in the flight plan management system is changed, generating a flight to be validated based on the changed flight plan information;
and issuing the flight to be validated after the flight to be validated takes effect.
2. The method as claimed in claim 1, wherein the obtaining information in a specified date range from the SSIM file according to the category of the SSIM file imported by the user comprises:
if the category representation market party of the SSIM file imported by the user is the airline driver to which the flight plan management system belongs, acquiring a code sharing flight corresponding relation and a flight plan message in the specified date range from the SSIM file;
the changing the code sharing flight corresponding relation in the flight plan management system and/or the flight plan information based on the information in the specified date range comprises:
changing the corresponding relation of the code sharing flight in the flight plan management system based on the corresponding relation of the code sharing flight in the appointed date range;
and changing the flight plan information in the flight plan management system based on the flight plan message in the specified date range.
3. The method as claimed in claim 1, wherein the obtaining information in a specified date range from the SSIM file according to the category of the SSIM file imported by the user comprises:
if the type representation carrier of the SSIM file imported by the user is the airline driver of the flight plan management system, acquiring the code sharing flight corresponding relation in the specified date range from the SSIM file;
the changing the code sharing flight corresponding relation in the flight plan management system and/or the flight plan information based on the information in the specified date range comprises:
and changing the corresponding relation of the code sharing flight in the flight plan management system based on the corresponding relation of the code sharing flight in the specified date range.
4. The method of claim 1, further comprising:
and pushing the changed flight schedule information in the flight schedule management system and/or the flight schedule information before the change to a passenger protection system.
5. The method of claim 1, further comprising:
and displaying a protocol maintenance adjustment page, and responding to the flight corresponding relation change request when the flight corresponding relation change request input by the user is acquired in the protocol maintenance adjustment page, and changing the code sharing flight corresponding relation in the flight plan management system.
6. The method of claim 5, further comprising:
and if an effective request of a user for the corresponding relation of the changed code sharing flight in the flight plan management system is acquired in the protocol maintenance adjustment page, the corresponding relation of the changed code sharing flight in the flight plan management system is effective.
7. The method of claim 1, further comprising:
and displaying a flight adjustment page, responding to the flight plan change request when the flight adjustment page acquires the flight plan change request input by the user, changing the flight plan information in the flight plan management system, and generating the flight to be used based on the changed flight plan information.
8. The method of claim 7, further comprising:
and if the flight adjusting page obtains an effective request of the user for the flight to be used, the flight to be used is taken into effect.
9. A flight plan management system, comprising:
the receiving module is used for receiving the SSIM file imported by the user;
the acquisition module is used for acquiring information in a specified date range from the SSIM file according to the type of the SSIM file imported by the user;
the first changing module is used for changing the corresponding relation of the code sharing flight in the flight plan management system and/or the flight plan information based on the information in the appointed date range;
the first issuing module is used for issuing the changed code sharing flight corresponding relation in the flight plan management system after the code sharing flight corresponding relation in the flight plan management system is changed;
the generating module is used for generating a flight to be validated based on the changed flight plan information after the flight plan information in the flight plan management system is changed;
and the second issuing module is used for issuing the flight to be validated after the flight to be validated takes effect.
10. A computer storage medium having stored thereon a computer program for execution by a processor to perform the steps of a flight plan management method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011125653.4A CN112258023A (en) | 2020-10-20 | 2020-10-20 | Flight plan management method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011125653.4A CN112258023A (en) | 2020-10-20 | 2020-10-20 | Flight plan management method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112258023A true CN112258023A (en) | 2021-01-22 |
Family
ID=74245473
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011125653.4A Pending CN112258023A (en) | 2020-10-20 | 2020-10-20 | Flight plan management method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112258023A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023130614A1 (en) * | 2022-01-10 | 2023-07-13 | 中国民航信息网络股份有限公司 | Flight schedule vacancy filling method, apparatus and device, and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110093301A1 (en) * | 2008-10-15 | 2011-04-21 | Jamie Walker | System and method for negotiating a shared flight itinerary |
| US20130131970A1 (en) * | 2010-04-22 | 2013-05-23 | Bae Systems Plc | Flight planning methods and systems |
| CN109873873A (en) * | 2019-03-15 | 2019-06-11 | 北京恒赢智航科技有限公司 | A kind of flight data delivery system, flight variation and message treatment method |
| CN110322231A (en) * | 2019-07-10 | 2019-10-11 | 中国民航信息网络股份有限公司 | A kind of flight planning method for automatically releasing and system |
| CN110322233A (en) * | 2019-07-10 | 2019-10-11 | 中国民航信息网络股份有限公司 | A kind of method and system for forbidding sale of ticket based on flight cancellation message |
| CN111784295A (en) * | 2020-06-30 | 2020-10-16 | 中国民航信息网络股份有限公司 | Flight validation method and device |
-
2020
- 2020-10-20 CN CN202011125653.4A patent/CN112258023A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110093301A1 (en) * | 2008-10-15 | 2011-04-21 | Jamie Walker | System and method for negotiating a shared flight itinerary |
| US20130131970A1 (en) * | 2010-04-22 | 2013-05-23 | Bae Systems Plc | Flight planning methods and systems |
| CN109873873A (en) * | 2019-03-15 | 2019-06-11 | 北京恒赢智航科技有限公司 | A kind of flight data delivery system, flight variation and message treatment method |
| CN110322231A (en) * | 2019-07-10 | 2019-10-11 | 中国民航信息网络股份有限公司 | A kind of flight planning method for automatically releasing and system |
| CN110322233A (en) * | 2019-07-10 | 2019-10-11 | 中国民航信息网络股份有限公司 | A kind of method and system for forbidding sale of ticket based on flight cancellation message |
| CN111784295A (en) * | 2020-06-30 | 2020-10-16 | 中国民航信息网络股份有限公司 | Flight validation method and device |
Non-Patent Citations (1)
| Title |
|---|
| 张通国;张世平;: "中国民航航班计划信息的处理与分析", 中国民用航空, no. 05, 20 May 2007 (2007-05-20) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023130614A1 (en) * | 2022-01-10 | 2023-07-13 | 中国民航信息网络股份有限公司 | Flight schedule vacancy filling method, apparatus and device, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115757400B (en) | Data table processing method, device, electronic equipment and computer readable medium | |
| CN112015971A (en) | Recommendation method and device for cloud product, electronic equipment and computer readable medium | |
| CN110737655B (en) | Method and device for reporting data | |
| CN111338869B (en) | Configuration parameter management method, device, equipment and storage medium | |
| CN112258023A (en) | Flight plan management method, system and storage medium | |
| CN110648126A (en) | Payment type configuration method, device, server and storage medium | |
| CN112488730B (en) | Product recall task processing method, device and equipment | |
| CN110443034B (en) | Risk program file identification method and device, computing equipment and medium | |
| CN115357469A (en) | Abnormal alarm log analysis method and device, electronic equipment and computer medium | |
| CN112204527A (en) | Method and system for processing engineering data in a multi-engineering system environment | |
| CN115526587A (en) | Method and device for generating customs message | |
| CN114418482A (en) | Order information processing method and device, electronic equipment and computer readable medium | |
| CN110688355A (en) | Method and device for changing container state | |
| CN114418625A (en) | Information display method and device, electronic equipment and computer readable medium | |
| CN113722315A (en) | Data generation method and device, electronic equipment and computer readable medium | |
| CN113742321A (en) | Data updating method and device | |
| CN112084114A (en) | Method and apparatus for testing an interface | |
| CN113077352B (en) | Insurance service article recommending method based on user information and insurance related information | |
| CN113743807B (en) | Scheduling information generation method, device, electronic equipment and computer readable medium | |
| CN117057974B (en) | GPU big data platform, electronic equipment and storage medium | |
| US11468026B2 (en) | Information processing apparatus, information processing method, and recording medium recording information processing program | |
| CN110851131B (en) | Script generation method, script generation device, electronic equipment and computer readable storage medium | |
| CN117331990A (en) | Abnormal data display method, device and equipment for data application sharing platform | |
| CN116821117A (en) | Stream data processing method, system, equipment and storage medium | |
| CN113962782A (en) | Order information processing method and device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |