A method and apparatus for centralized control of departure flight planning

Abstract

The application provides a method and device for departure flight plan centralized control, and relates to the field of civil aviation passenger transportation. If the received work area change request of the target flight corresponds to the request initiated by the user of the airport where the target flight is located and / or the centralized control user, the original work area corresponding to the target identifier in the FDC system and the departure flight data control system is changed to the centralized control work area indicated by the work area identifier. If the received flight plan change request is the request initiated by the user of the airport where the target flight is located and / or the centralized control user, the to-be-changed flight plan corresponding to the target flight in the FDC system is changed. Based on the authority granted by the FDC system to the departure flight data control system, the backup flight plan change data of the departure flight data control system is changed. The application makes each flight to be subjected to the centralized control of the departure flight plan of the target airline as the target flight, and realizes the centralized control of the departure flight plan of each flight by the centralized control user.

Description

Technical Field

[0001] The present application relates to the field of civil aviation passenger transportation, and in particular to a method and apparatus for centralized control of departure flight plans. Background Art

[0002] Currently, each airline establishes its own work area at each airport based on the flight season, and assigns relevant staff to be stationed at the airport to formulate and modify departure flight plans. Due to the large number of airports, for each airline, having staff at each airport independently formulate and modify departure flight plans is not conducive to unified flight scheduling.

[0003] Therefore, there is an urgent need for a method in which the departure flight plans of each flight of the same airline can be controlled by an airport staff so as to uniformly dispatch flights. Summary of the Invention

[0004] In view of this, the present application provides a method and apparatus for centralized control of departure flight plans, the technical solution of which is as follows:

[0005] In a first aspect, a method for centralized control of departure flight plans is provided, which is applied to a pre-established open flight data control system, wherein the open flight data control system includes at least all functions of a departure flight data control system;

[0006] The method for centralized control of departure flight plans includes:

[0007] receiving a workspace change request corresponding to a target flight, wherein the workspace change request is a request for changing a workspace initiated at any time before a preset centralized control date, the target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule, and the workspace change request includes a workspace identifier for indicating a centralized control workspace corresponding to a centralized control user and a target identifier for indicating the target flight, wherein the centralized control user is a preset user with centralized control authority over all flights of the target airline;

[0008] If the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located, the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system is changed to the centralized control work area indicated by the work area identifier, wherein the original work area refers to the work area at the airport where the target flight is located;

[0009] After receiving a flight plan change request corresponding to the target flight, if the flight plan change request is initiated by a user at the airport where the target flight is located and / or the centralized control user, modifying the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request to obtain flight plan change data;

[0010] The flight plan change data is backed up in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

[0011] In a second aspect, a device for centralized control of departure flight plans is provided, which is applied to a pre-established open flight data control system, wherein the open flight data control system includes at least all functions of a departure flight data control system;

[0012] The centralized control device for departure flight plans includes:

[0013] a work area change request receiving module, configured to receive a work area change request corresponding to a target flight, wherein the work area change request is a request for changing a work area initiated at any time before a preset centralized control date, the target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule, and the work area change request includes a work area identifier for indicating the centralized control work area corresponding to a centralized control user and a target identifier for indicating the target flight, wherein the centralized control user is a preset user with centralized control authority over all flights of the target airline;

[0014] a work area changing module configured to change the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system to the centralized control work area indicated by the work area identifier, if the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located; wherein the original work area refers to the work area at the airport where the target flight is located;

[0015] a flight plan change module configured to, upon receiving a flight plan change request corresponding to the target flight, modify the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request if the flight plan change request is initiated by a user at the airport where the target flight is located and / or the centralized control user, thereby obtaining flight plan change data;

[0016] A data backup module is used to back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

[0017] It can be seen from the above technical solution that the method for centralized control of departure flight plans provided by the present application, in view of the limitations of the departure flight data control system, that is, a flight can only be established in one work area, and the centralized control user can only control the departure flight plan of the flight established in the centralized control work area, therefore, if the centralized control user is to realize the change control of the departure flight plan of the target flight, it is necessary to receive the work area change request corresponding to the target flight, and the work area change request is initiated by the user of the airport where the target flight is located and / or the centralized control user, and then change the work area corresponding to the target identifier in the open flight data control system and the departure flight data control system to the work area indicated by the work area identifier. After changing the work area, if a flight plan change request corresponding to the target flight is received, and the flight plan change request is a request initiated by a centralized control user, then this application can change the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request, and obtain flight plan change data. Furthermore, this application can enable the departure flight data control system to grant authority to the open flight data control system, through which the flight plan change data can be backed up in the departure flight data control system, thereby achieving data consistency between the open flight data control system and the departure flight data control system, and ensuring that the centralized control user successfully changes the departure flight plan of the target flight. In this application, all flights under the target airline that require centralized control of departure flight plans can be used as target flights to change the centralized control work area and the departure flight plan, thereby achieving centralized control of all flights under the target airline that require centralized control of departure flight plans by the centralized control user, which facilitates the subsequent unified automatic processing of flight plans by the target airline.

[0018] Furthermore, considering that centralized control users may not handle business in a timely manner when encountering business backlogs, in order to improve the timeliness of changes to the target flight's departure flight plan, this application can also, when the flight plan change request is initiated by a user at the airport where the target flight is located, change the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request, obtain flight plan change data, and back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system. This enables the user at the airport where the target flight is located to control changes to the target flight's departure flight plan, thereby improving the efficiency of changing the target flight's departure flight plan. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0020] Figure 1 A flowchart of a method for centralized control of departure flight plans provided in an embodiment of the present application;

[0021] Figure 2 A schematic diagram of the structure of a device for centralized control of departure flight plans provided in an embodiment of the present application;

[0022] Figure 3 A hardware structure block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0024] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0025] As used herein, the term "including" and its variations are open-ended, 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," and the term "some embodiments" means "at least some embodiments." Relevant definitions of other terms are provided in the following description.

[0026] It should be noted that the concepts of "first", "second", etc. mentioned in this disclosure 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.

[0027] It should be noted that the modifications of “one” and “multiple” mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as “one or more”.

[0028] In order to facilitate the description of the centralized control method for departure flight plans provided by this application, the relevant terms used in this application are now explained.

[0029] Departure Control System (DCS): A real-time computer network system consisting of a departure flight data control system (used to control and manage departure flight data, such as departure flight schedule data), a passenger check-in system, and a loading system. It is a large-scale online transaction processing system operated by users through command lines.

[0030] Open Flight Data Control System (FDC): A new system built on an open server. The Open Flight Data Control System includes at least all the functions of the Departure Flight Data Control System. Therefore, the Open Flight Data Control System can replace the Departure Flight Data Control System in the future.

[0031] Work Area: The control area to which a flight belongs, consisting of three letters and three numbers. Each flight number has a unique work area, which is used for DCS data permission verification.

[0032] Flight season: Airlines have two flight seasons a year: summer and autumn: from the last Sunday in March to the last Saturday in October; winter and spring: from the last Sunday in October to the last Saturday in March of the following year.

[0033] In order to enable the departure flight plans of all flights of the same airline to be controlled by one airport staff member (for the convenience of subsequent introduction, this one airport staff member is defined as a centralized control user below), the inventor of this case conducted in-depth research. Given the limitations of the departure flight data control system, namely that a flight can only be established in one workspace, in order to enable a centralized control user with centralized control authority to centrally control the departure flight plans of all flights of the target airline, the inventors of this case initially conceived of the following: airport staff (here airport staff refers to staff at the airport where the flight to be centralized controlled is located) can divide the departure flight plans in the departure flight data control system into two parts, namely, departure flight plans with a date range before the centralized control date, and departure flight plans with a date range after the centralized control date. Then, the departure flight plans with a date range after the centralized control date in the departure flight data control system are deleted. On the day before the centralized control date, after the flight takes off, the departure flight plans with a date range before the centralized control date in the departure flight data control system are deleted again. Finally, the departure flight plans with a date range after the centralized control date are established in the centralized control workspace (the centralized control workspace refers to the workspace corresponding to the centralized control user with centralized control authority).

[0034] For example, Air China's Beijing departure control room wants to centrally control flights to Wuhan (hereinafter referred to as target flights) on April 16, 2023. However, Wuhan has already established the flight schedule for the entire summer and autumn season from March 26, 2023 to October 28, 2023, under the Wuhan workspace. If the flight schedule is to be established under the Beijing workspace from April 16, 2023, the following process will be used:

[0035] The first step is to split the departure flight schedule. Specifically, the Wuhan departure control personnel (hereinafter referred to as the user at the target flight's airport) split the flight schedule from March 26 to October 28 into two date segments: one from March 26 to April 15, and the other from April 16 to October 28. At this point, the Beijing departure control personnel (the centralized control user mentioned above) have no authority.

[0036] The second step is to delete the departure flight plans after the centralized control date from the departure flight data control system. Specifically, the Wuhan departure control personnel will delete the flight plans from April 16 to October 28. At this time, the Beijing departure control personnel have no authority.

[0037] The third step is to delete departure flight plans before the centralized control date from the departure flight data control system. Specifically, on April 15, after the flight took off, the Wuhan departure control personnel deleted the departure plans before April 15. At this time, the Beijing departure control personnel had no authority.

[0038] The fourth step is to establish a departure flight plan after the centralized control date in the departure flight data control system. Specifically, after receiving the deletion notice from Wuhan, the Beijing departure control personnel will establish a flight plan from April 16 to October 28 in the Beijing work area. At this time, the Wuhan personnel have no operational authority.

[0039] Through the above process, Beijing departure control personnel can control changes to the departure flight plans of Air China flights at Wuhan Airport. All flights at each airport that require control by Beijing departure control personnel are executed according to the above steps, allowing Beijing departure control personnel to centrally control the departure flight plans of flights at each airport, which is conducive to unified flight scheduling. However, the above centralized control solution of first dividing the dates, then deleting and creating new departure flight plans has the problems of complex process and low efficiency. There is also the problem that only one airport user has flight control authority in a time period, and flights within the centralized control date are deleted, resulting in passengers being unable to check in two days in advance.

[0040] In order to further solve the above problems under the premise of realizing that "the departure flight plans of all flights of the same airline can be controlled by one airport staff", the inventors of this case continued their research and finally proposed a method for centralized control of departure flight plans.

[0041] In this application, the method for centralized control of departure flight schedules can be applied to a pre-established open flight data control system (FDC), which includes at least all the functions of a departure flight data control system. This FDC system can break through the limitations of the existing workspace and meet the requirements of centralized control of one airport (i.e., the airport corresponding to the centralized control user in this application) and decentralized control of other airports (i.e., the airport where the target flight is located in this application).

[0042] In order to enable those skilled in the art to better understand the present application, the method for centralized control of departure flight plans provided by the present application will be described in detail through the following embodiments.

[0043] See also Figure 1 , shows a flow chart of a method for centralized control of departure flight plans provided by an embodiment of the present application. The method for centralized control of departure flight plans may include:

[0044] Step S101: Receive a work area change request corresponding to a target flight.

[0045] Here, the work area change request refers to a request for changing the work area initiated at any time before the preset centralized control date, for example, the work area change request is a request for changing the work area initiated one day before the centralized control date.

[0046] The above-mentioned centralized control date refers to the date on which the centralized control user with centralized control authority over the departure flight schedule of the target flight plans to conduct centralized control over each flight of the airline.

[0047] In an optional embodiment, the embodiment of the present application can provide an interface for inputting relevant parameters required to generate a workspace change request. The centralized control user and / or the user at the airport where the target flight is located (here, the target flight refers to the flight under the target airline that is to undergo centralized control of the departure flight plan. In the embodiment of the present application, any flight in any airport of the airline where the centralized control user is located can be used as a target flight) can input relevant parameters in the interface to obtain a workspace change request. The workspace change request can be sent to the FDC system through a preset interface, and the FDC system can then receive the workspace change request.

[0048] Optionally, the relevant parameters required to generate the workspace change request include: a target identifier and a workspace identifier. That is, in this embodiment, the workspace change request includes the target identifier and the workspace identifier.

[0049] The above-mentioned target identifier is used to indicate the target flight; optionally, the target identifier includes the identifier of the target airline and the identifier of the target flight. Optionally, the identifier of the target flight may be the flight number of the target flight, such as flight number CA123S; optionally, if the target flights include all flights of the target airline at an airport, the target identifier may include the identifier of the target airline and the identifier of the airport.

[0050] The above workspace identifier is the identifier of the centralized control workspace corresponding to the centralized control user, that is, the above workspace identifier is used to indicate the centralized control workspace corresponding to the centralized control user. For example, the workspace identifier is the identifier of the Beijing workspace corresponding to the Beijing departure control personnel in the previous example.

[0051] In this embodiment of the present application, the centralized control user is a user who is pre-set to have centralized control authority over all flights of the target airline. Because the centralized control user has centralized control authority, regardless of which flight of the target airline the target flight is, the centralized control user can centrally control the departure schedule of the target flight after the workspace is changed.

[0052] Step S102: If the work area change request is initiated by a user at the airport where the target flight is located and / or a centralized control user, the original work area corresponding to the target identifier in the open flight data control system and the departure flight data control system is changed to the centralized control work area indicated by the work area identifier.

[0053] The original work area refers to the work area under the airport where the target flight is located, such as the Wuhan work area in the example above.

[0054] In this embodiment, the FDC system and the departure flight data control system each store a correspondence between flights and workspaces. Upon receiving a workspace change request, the FDC system can update the correspondence stored in its own system. Specifically, the original workspace corresponding to the target identifier in its own system can be changed to the centralized control workspace indicated by the workspace identifier. For example, if the original workspace corresponding to the target identifier is the Wuhan workspace corresponding to flight CA123S, and the centralized control workspace is the Beijing workspace, then the aforementioned "correspondence between flight CA123S and the Wuhan workspace" can be updated to the correspondence between flight CA123S and the Beijing workspace.

[0055] In order to ensure the normal operation of all systems of the current airline, it is necessary to keep the data of the FDC system consistent with that of the departure flight data control system. To this end, it is also necessary to change the original work area corresponding to the target identifier in the departure flight data control system to the centralized control work area indicated by the work area identifier.

[0056] Through the above-mentioned workspace change process, the centralized control problem is solved. That is, workspace change requests are generated based on all flights of the target airline that are to be centrally controlled for departure flight plans, and then workspace changes are performed based on all generated workspace change requests. After the workspace is changed, the centralized control user can uniformly and centrally control the departure flight plans of all flights of the target airline that are to be centrally controlled for departure flight plans.

[0057] In a preferred case, the above-mentioned "all flights of the target airline whose departure flight plans are to be centrally controlled" can be all flights of the target airline. In this case, the centralized control user can control the departure flight plans of all flights of the target airline, solving the problem of inconsistent flight scheduling.

[0058] Step S103: After receiving the flight plan change request corresponding to the target flight, if the flight plan change request is initiated by a user at the airport where the target flight is located and / or a centralized control user, the flight plan to be changed corresponding to the target flight in the open flight data control system is changed based on the flight plan change request to obtain flight plan change data.

[0059] Here, the user at the airport where the target flight is located is, for example, the Wuhan departure control personnel in the previous example.

[0060] Specifically, the FDC system has pre-opened flight plan change permissions for users at the airport where the target flight is located and centralized control users, so that only when users at the airport where the target flight is located and centralized control users initiate flight plan change requests corresponding to the target flight, can the flight plan to be changed corresponding to the target flight in the open flight data control system be changed based on the flight plan change request and obtain flight plan change data.

[0061] It should be noted that the purpose of the FDC system in this embodiment granting flight plan change permissions to users at the airport where the target flight is located is: when the target flight includes multiple flights, especially when the target flights are all flights of the target airline, the centralized control user needs to control the departure flight plans of many flights. If flight plan change requests corresponding to multiple flights are received in a short period of time, due to the limited processing capacity of the centralized control user, a backlog of flight plan change services may occur. Failure to change the departure flight plan in a timely manner may affect passenger travel and even cause airport disturbances. The FDC system grants flight plan change permissions to users at the airport where the target flight is located. When the centralized control user is unable to handle the departure flight plan change service of a certain flight in a timely manner, the user at the airport where the flight is located can handle it. This ensures that the departure flight plan change service of the flight is handled in a timely manner and avoids airport disturbances.

[0062] Step S104: Back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

[0063] As mentioned above, the data in the FDC system needs to be consistent with that in the departure flight data control system. To this end, the departure flight data control system needs to grant permissions to the FDC system. This permission enables the data in the FDC system to be backed up to the departure flight data control system, thereby keeping the data in the FDC system consistent with the departure flight data control system.

[0064] Optionally, the process of "backing up flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system" may include: sending the flight plan change data to the departure flight data control system based on the authority granted by the departure flight data control system to the FDC system, and receiving information fed back by the departure flight data control system; if the information fed back by the departure flight data control system indicates that the backup of the flight plan change data has been successful, then the process is terminated; if the information fed back by the departure flight data control system indicates that the backup of the flight plan change data has failed, then an error is reported, and the error information can be, for example, a DCS error or a departure flight error. The data control system has an error. Optionally, in the event of an error, when the departure flight plan of the target flight on the FDC system has been changed to flight plan change data, the changed flight plan change data can be withdrawn so that the FDC system can restore the data before step S103, so that the FDC system and the departure flight data control system maintain data consistency; if the departure flight data control system does not respond within the timeout period, an error can be reported. The error message can be, for example, DCS timeout or departure flight data control system timeout. Similarly, the changed flight plan change data can be withdrawn in the FDC system so that the FDC system and the departure flight data control system maintain data consistency.

[0065] Optionally, after the departure flight plan is changed, the change time and the person who made the change can be recorded. Generally, the person who made the change is the initiator of the flight plan change request.

[0066] The method for centralized control of departure flight plans provided in the present application takes into account the limitations of the departure flight data control system, namely, that a flight can only be established in one workspace, and the centralized control user can only control the departure flight plan of the flight established in the centralized control workspace. Therefore, in order to implement the centralized control user's control over changes to the departure flight plan of the target flight, it is necessary to change the workspace corresponding to the target identifier in both the open flight data control system and the departure flight data control system to the workspace indicated by the workspace identifier upon receiving a workspace change request corresponding to the target flight, and the workspace change request is initiated by a user at the airport where the target flight is located and / or a centralized control user. After changing the work area, if a flight plan change request corresponding to the target flight is received, and the flight plan change request is a request initiated by a centralized control user, then this application can change the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request, and obtain flight plan change data. Furthermore, this application can enable the departure flight data control system to grant authority to the open flight data control system, through which the flight plan change data can be backed up in the departure flight data control system, thereby achieving data consistency between the open flight data control system and the departure flight data control system, and ensuring that the centralized control user successfully changes the departure flight plan of the target flight. In this application, all flights under the target airline that require centralized control of departure flight plans can be used as target flights to change the centralized control work area and the departure flight plan, thereby achieving centralized control of all flights under the target airline that require centralized control of departure flight plans by the centralized control user, which facilitates the subsequent unified automatic processing of flight plans by the target airline.

[0067] Furthermore, considering that centralized control users may not handle business in a timely manner when encountering business backlogs, in order to improve the timeliness of changes to the target flight's departure flight plan, this application can also, when the flight plan change request is initiated by a user at the airport where the target flight is located, change the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request, obtain flight plan change data, and back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system. This enables the user at the airport where the target flight is located to control changes to the target flight's departure flight plan, thereby improving the efficiency of changing the target flight's departure flight plan.

[0068] Since the above steps do not require date segmentation or deletion or creation of departure flight plans, the process is simpler. The FDC system enables flight plan change permissions for users at the airport where the target flight is located and centralized control users, allowing multiple airport users to have flight control permissions within a time period without affecting passenger check-in, thereby improving flight control efficiency.

[0069] In some embodiments of the present application, in actual applications, a workspace change request may not meet the requirements, for example, the workspace change request lacks parameters, etc. In order to successfully change the workspace in step S102, the workspace change request may be verified before changing the workspace.

[0070] In a first optional embodiment, after receiving the work area change request corresponding to the target flight, it is possible to verify whether the work area change request meets the preset mandatory items and format requirements. If the verification result is yes, step S102 is executed, that is, "If the work area change request is a request initiated by a user and / or a centralized control user at the airport where the target flight is located, the original work area corresponding to the target identifier in the open flight data control system and the departure flight data control system is changed to the centralized control work area indicated by the work area identifier."

[0071] Optionally, if the workspace change request does not meet the preset mandatory fields and format requirements, an error message may be reported: format error.

[0072] This embodiment can avoid adverse effects on subsequent workspace changes caused by missing parameters or non-compliant formats in the workspace change request by verifying required items and format requirements, thereby improving the efficiency of workspace changes.

[0073] In a second optional embodiment, the above-mentioned process of "changing the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier" may include: determining the flight number of the target flight based on the target identifier, judging whether the flight number of the target flight exists and is effective; if so, changing the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier.

[0074] Specifically, only when the target flight exists and the target flight has been effective, changing the work area is meaningful. Based on this, the present embodiment can first determine whether the flight number of the target flight already exists and has been effective before changing the work area, and if so, then change the work area.

[0075] Optionally, this embodiment can also first verify whether the flight number of the target flight exists. If so, it can further verify whether the flight number of the target flight exists to be effective. If it does not exist to be effective, that is, the target flight has been effective, then the original work area corresponding to the target identifier in the open flight data control system and the departure flight data control system will be changed to the centralized control work area indicated by the work area identifier.

[0076] Optionally, if the flight number of the target flight does not exist, an error message will be reported: flight number does not exist; if the flight number of the target flight exists and is pending, an error message will be reported: flight pending.

[0077] The embodiment of the present application can ensure that the workspace that is subsequently changed is as error-free as possible through multiple checks.

[0078] In the embodiment of the present application, after the above verification is completed, the work area can be changed. In order to make those skilled in the art better understand the work area change process of the embodiment of the present application, it is introduced as follows.

[0079] Optionally, the process of "changing the original work areas corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control work areas indicated by the work area identifiers" may include: sending a work area change request to the departure flight data control system so that the departure flight data control system changes the original work area corresponding to the target identifier in its own system to the centralized control work area indicated by the work area identifier, and feeding back response information indicating whether the work area change is successful to the open flight data control system; if response information indicating that the work area change is successful is received, the original work area corresponding to the target identifier in the open flight data control system is changed to the centralized control work area indicated by the work area identifier.

[0080] Specifically, the process of the departure flight data control system changing the original workspace corresponding to the target identifier in its own system to the centralized control workspace indicated by the workspace identifier may succeed or fail. To avoid the departure flight data control system failing to change the workspace after the FDC system changes the workspace, resulting in data inconsistency between the FDC system and the departure flight data control system, this embodiment can send a workspace change request to the departure flight data control system and wait for a response message from the departure flight data control system indicating whether the workspace change was successful. If the departure flight data control system returns a response message indicating that the workspace change was successful, it means that the original workspace corresponding to the target identifier in the departure flight data control system has been successfully changed to the centralized control workspace indicated by the workspace identifier. Then, the FDC system can change the original workspace corresponding to the target identifier in its own system to the centralized control workspace indicated by the workspace identifier.

[0081] Optionally, if the departure flight data control system feeds back response information indicating that the work area change failed, it means that the original work area corresponding to the target identifier in the departure flight data control system has not been successfully changed to the centralized control work area indicated by the work area identifier, then the FDC system can report an error, and the error information can be, for example, a DCS error or a departure flight data control system error. At this time, the FDC system will no longer change the work area; if the departure flight data control system does not feed back response information within the timeout period, the FDC system cannot receive the response information within the timeout period, then an error is reported, and the error information can be, for example, a DCS timeout or a departure flight data control system timeout.

[0082] Of course, the above process of "changing the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier" is only an example. In addition, there may be other implementation methods. For example, the process of "changing the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier" may also include: changing the original workspace corresponding to the target identifier in the FDC system to the centralized control workspace indicated by the workspace identifier based on the workspace change request, obtaining workspace change data, and sending the workspace change data to the departure flight data control system. The departure flight data control system is used to back up the work area change data of the departure flight data control system, and to feedback the response information indicating whether the work area change is successful to the FDC system; if the response information indicating that the work area change is successful is received, the process is terminated; if the response information indicating that the work area change fails is received, an error is reported, and the error information may be, for example, a DCS error or a departure flight data control system error, and the previously changed work area is rolled back; if no reply is received from the departure flight data control system within the timeout period, an error is reported, and the error information may be, for example, a DCS timeout or a departure flight data control system timeout, and the previously changed work area is rolled back.

[0083] Optionally, after the workspace is changed through the above process, this embodiment may further record the change time and the changer. Generally, the changer is the initiator of the workspace change request.

[0084] It's worth noting that the aforementioned workspace modification process does not affect any flight days in the target flight's scheduled date period. For example, it does not affect flights that have already been initialized but departed, allowing normal changes to flight dynamic information, such as the estimated arrival time; it does not affect flights that have already been initialized but not departed, allowing normal passenger reception and seat locks; and it does not affect uninitialized flights, allowing normal changes to flight schedules and flight dynamic information. In other words, this embodiment allows users with centralized control permissions to modify the workspace of flights on the target airline that are undergoing centralized control of their departure schedules.

[0085] In summary, through the above process, this embodiment can change the workspace in the FDC system and the departure flight data control system respectively. By changing the workspace, centralized control of the departure flight plans of each flight of the target airline to be centrally controlled can be achieved.

[0086] In other embodiments of the present application, the workspace change request and the flight plan change request in the above embodiments can be respectively used as target requests, and the process of determining whether the target request is a request initiated by a centralized control user can include: determining whether the initiator of the target request has a centralized control authority identifier; if so, determining that the target request is a request initiated by a centralized control user.

[0087] Specifically, when this embodiment receives a target request, it may carry the role identifier of the initiator of the target request. If the role identifier is a centralized control authority identifier, it can be determined that the target request is a request initiated by a centralized control user.

[0088] Optionally, if the role identifier is not a centralized control authority identifier, the judgment result of "judging whether the initiator of the target request has the centralized control authority identifier" in this embodiment is no, and an error may be reported: authority control.

[0089] For example, when determining in step S102 whether the workspace change request is a request initiated by a centralized control user, it is possible to determine whether the initiator of the workspace change request has a centralized control authority identifier based on the role identifier carried when the workspace change request is received. If so, it is determined that the workspace change request is a request initiated by a centralized control user. If not, an error is reported, and the error message is "authority control".

[0090] Optionally, the process of determining whether the flight plan change request is a request initiated by a user at the airport where the target flight is located may include: determining whether the initiator of the flight plan change request has both a first attribute and a second attribute, wherein the first attribute is the target airline and the second attribute is the airport where the target flight is located; if so, determining that the flight plan change request is a request initiated by a user at the airport where the target flight is located.

[0091] Taking the target airline as Air China and the airport where the target flight is located as Wuhan as an example, this embodiment can use the two attributes "Air China" and "Wuhan" to determine whether the target request is a request initiated by the departure control personnel of Air China Wuhan. If so, the departure flight plan of the target flight is changed according to the subsequent process. If not, an error is reported, and the error message is "Authorization Control".

[0092] Optionally, the process of determining whether the workspace change request is a request initiated by a user at the airport where the target flight is located can correspond to the "process of determining whether the flight plan change request is a request initiated by a user at the airport where the target flight is located". For details, please refer to the above introduction and will not be repeated here.

[0093] In summary, the embodiments of the present application adopt different authority verification methods for centralized control users and users at the airport where the target flight is located. Through authority verification, it can ensure that the departure flight plan of the target flight is successfully changed, and avoid that non-centrally controlled users and users at the airport where the target flight is located change the departure flight plan of the target flight, thereby improving the security of the change of the departure flight plan of the target flight.

[0094] Although the 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.

[0095] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0096] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving 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 may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0097] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of 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 than that 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 flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0098] An embodiment of the present application also provides a device for centralized control of departure flight plans. The device for centralized control of departure flight plans provided in an embodiment of the present application is described below. The device for centralized control of departure flight plans described below and the method for centralized control of departure flight plans described above can be referenced to each other.

[0099] The device for centralized control of departure flight plans provided in the embodiment of the present application can be applied to a pre-established open flight data control system, which at least includes all the functions of the departure flight data control system.

[0100] See also Figure 2 , shows a schematic diagram of the structure of the device for centralized control of departure flight plans provided by an embodiment of the present application, such as Figure 2 As shown, the device for centralized control of departure flight plans may include:

[0101] The work area change request receiving module 201 is configured to receive a work area change request corresponding to a target flight, wherein a work area change request is a request for changing a work area initiated at any time before a preset centralized control date. The target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule. The work area change request includes a work area identifier for indicating the centralized control work area corresponding to a centralized control user and a target identifier for indicating the target flight. The centralized control user is a user who has preset centralized control authority over all flights of the target airline.

[0102] The work area changing module 202 is configured to change the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system to the centralized control work area indicated by the work area identifier, if the work area change request is initiated by a user at the airport where the target flight is located and / or a centralized control user. The original work area is the work area at the airport where the target flight is located.

[0103] The flight plan change module 203 is configured to, upon receiving a flight plan change request corresponding to a target flight, modify the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request if the flight plan change request is initiated by a user at the airport where the target flight is located and / or a centralized control user, thereby obtaining flight plan change data.

[0104] The data backup module 204 is configured to back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

[0105] Optionally, when determining whether a workspace change request is initiated by a centrally controlled user, the workspace change module is specifically used to determine whether the initiator of the workspace change request has a centrally controlled authority identifier; if so, determine that the workspace change request is a request initiated by a centrally controlled user.

[0106] Correspondingly, when the above-mentioned flight plan change module determines whether the flight plan change request is a request initiated by a centralized control user, it is specifically used to: determine whether the initiator of the flight plan change request has a centralized control authority identifier; if so, determine that the flight plan change request is a request initiated by a centralized control user.

[0107] Optionally, when determining whether the flight plan change request is a request initiated by a user at the airport where the target flight is located, the flight plan change module is specifically used to: determine whether the initiator of the flight plan change request has both the first attribute and the second attribute; if so, determine that the flight plan change request is a request initiated by a user at the airport where the target flight is located, wherein the first attribute is the target airline and the second attribute is the airport where the target flight is located.

[0108] Optionally, when the above-mentioned work area change module changes the original work areas corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control work areas indicated by the work area identifier, it is specifically used to: determine the flight number of the target flight according to the target identifier, and judge whether the flight number of the target flight exists and is effective; if so, change the original work area corresponding to the target identifier in the open flight data control system to the centralized control work area indicated by the work area identifier, and change the original work area corresponding to the target identifier in the departure flight data control system to the centralized control work area indicated by the work area identifier.

[0109] The units described in the embodiments of the present disclosure may be implemented in software or hardware. In some cases, the name of a unit does not limit the unit itself. For example, a workspace change request receiving module may also be described as a "workspace change request acquiring unit."

[0110] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and 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 chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0111] See also Figure 3 , which shows a schematic structural diagram of an electronic device (such as a terminal device or server) 500 suitable for implementing the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 3 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0112] like Figure 3 As shown, the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. Various programs and data required for the operation of the electronic device 500 are also stored in the RAM 503. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0113] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 506 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 3 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0114] An embodiment of the present disclosure also provides a computer-readable medium, which carries one or more programs. When the above one or more programs are executed by the electronic device, the electronic device executes the method for centralized control of departure flight plans provided by any embodiment of the present application.

[0115] In the context of the present disclosure, a computer-readable medium can be a tangible medium that can contain or store a program for use by or in combination with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0116] It should be noted that the computer-readable medium mentioned above in the present disclosure may 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 electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0117] The computer-readable storage medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0118] According to one or more embodiments of the present disclosure, the above embodiments provide a method for centralized control of departure flight plans, which is applied to a pre-established open flight data control system, which includes at least all functions of a departure flight data control system;

[0119] Centralized control methods for departure flight plans include:

[0120] Receive a workspace change request corresponding to a target flight, where the workspace change request is a request for changing a workspace initiated at any time before a preset centralized control date. The target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule. The workspace change request includes a workspace identifier for indicating the centralized control workspace corresponding to a centralized control user and a target identifier for indicating the target flight. The centralized control user is a preset user with centralized control authority over all flights of the target airline.

[0121] If the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located, the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system will be changed to the centralized control work area indicated by the work area identifier, where the original work area refers to the work area at the airport where the target flight is located;

[0122] Upon receiving a flight plan change request corresponding to a target flight, if the flight plan change request is initiated by a user at the airport where the target flight is located and / or a centralized control user, the flight plan to be changed corresponding to the target flight in the open flight data control system is changed based on the flight plan change request to obtain flight plan change data;

[0123] Based on the authority granted by the departure flight data control system to the open flight data control system, the flight plan change data is backed up in the departure flight data control system.

[0124] According to one or more embodiments of the present disclosure, in the method for centralized control of departure flight plans provided by the present disclosure, a process of using a workspace change request and a flight plan change request as target requests, and determining whether the target request is a request initiated by a centralized control user, includes:

[0125] Determine whether the initiator of the target request has a centralized control authority identifier;

[0126] If so, it is determined that the target request is a request initiated by the centralized control user.

[0127] According to one or more embodiments of the present disclosure, in the method for centralized control of departure flight plans provided by the present disclosure, the process of determining whether a flight plan change request is initiated by a user at the airport where the target flight is located includes:

[0128] Determine whether the initiator of the flight plan change request has both a first attribute and a second attribute, where the first attribute is the target airline and the second attribute is the airport where the target flight is located;

[0129] If so, it is determined that the flight plan change request is a request initiated by a user at the airport where the target flight is located.

[0130] According to one or more embodiments of the present disclosure, the method for centralized control of departure flight plans provided by the present disclosure further includes:

[0131] Verify whether the work area change request meets the preset mandatory items and format requirements, so that if the verification result is yes, execute it. If the work area change request is initiated by the user and / or centralized control user at the airport where the target flight is located, the original work area corresponding to the target identifier in the open flight data control system and the departure flight data control system will be changed to the centralized control work area indicated by the work area identifier.

[0132] According to one or more embodiments of the present disclosure, in the method for centralized control of departure flight plans provided by the present disclosure, the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system are changed to the centralized control workspace indicated by the workspace identifier, including:

[0133] Determine the flight number of the target flight according to the target identifier;

[0134] Determine whether the flight number of the target flight exists and is valid;

[0135] If so, the original work area corresponding to the target identifier in the open flight data control system is changed to the centralized control work area indicated by the work area identifier, and the original work area corresponding to the target identifier in the departure flight data control system is changed to the centralized control work area indicated by the work area identifier.

[0136] According to one or more embodiments of the present disclosure, in a method for centralized control of departure flight plans provided by the present disclosure, changing an original workspace corresponding to a target identifier in an open flight data control system to a centralized control workspace indicated by a workspace identifier, and changing an original workspace corresponding to a target identifier in a departure flight data control system to a centralized control workspace indicated by the workspace identifier, includes:

[0137] Sending a work area change request to the departure flight data control system so that the departure flight data control system changes the original work area corresponding to the target identifier in its own system to the centralized control work area indicated by the work area identifier, and feeding back a response message indicating whether the work area change is successful to the open flight data control system;

[0138] If a response message indicating that the work area change is successful is received, the original work area corresponding to the target identifier in the open flight data control system is changed to the centralized control work area indicated by the work area identifier.

[0139] According to one or more embodiments of the present disclosure, the above embodiments further provide a device for centralized control of departure flight plans, which is applied to a pre-established open flight data control system, wherein the open flight data control system includes at least all functions of the departure flight data control system;

[0140] Departure flight plan centralized control device, including:

[0141] a workspace change request receiving module, configured to receive a workspace change request corresponding to a target flight, wherein a workspace change request is a request for changing a workspace initiated at any time before a preset centralized control date, and a target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule. The workspace change request includes a workspace identifier for indicating the centralized control workspace corresponding to a centralized control user and a target identifier for indicating the target flight. The centralized control user is a preset user with centralized control authority over all flights of the target airline;

[0142] A work area change module is configured to change the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system to the centralized control work area indicated by the work area identifier, if the work area change request is initiated by a user at the airport where the target flight is located and / or a centralized control user. The original work area refers to the work area at the airport where the target flight is located.

[0143] A flight plan change module is configured to, upon receiving a flight plan change request corresponding to a target flight, modify the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request if the flight plan change request is initiated by a user at the airport where the target flight is located and / or a centralized control user, and obtain flight plan change data;

[0144] The data backup module is used to back up flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

[0145] According to one or more embodiments of the present disclosure, in the apparatus for centralized control of departure flight plans provided by the present disclosure, when determining whether a workspace change request is a request initiated by a centralized control user, a workspace change module is specifically configured to: determine whether the initiator of the workspace change request has a centralized control authority identifier; if so, determine that the workspace change request is a request initiated by the centralized control user;

[0146] When determining whether a flight plan change request is a request initiated by a centralized control user, the flight plan change module is specifically used to: determine whether the initiator of the flight plan change request has a centralized control authority identifier; if so, determine that the flight plan change request is a request initiated by a centralized control user.

[0147] According to one or more embodiments of the present disclosure, in the device for centralized control of departure flight plans provided by the present disclosure, the flight plan change module, when determining whether the flight plan change request is a request initiated by a user at the airport where the target flight is located, is specifically used to: determine whether the initiator of the flight plan change request has both a first attribute and a second attribute; if so, determine that the flight plan change request is a request initiated by a user at the airport where the target flight is located, wherein the first attribute is the target airline and the second attribute is the airport where the target flight is located.

[0148] According to one or more embodiments of the present disclosure, in the apparatus for centralized control of departure flight plans provided by the present disclosure, when changing the original workspaces corresponding to target identifiers in both the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier, the workspace changing module is specifically configured to: determine the flight number of the target flight based on the target identifier, determine whether the flight number of the target flight exists and is effective, and if so, change the original workspace corresponding to the target identifier in the open flight data control system to the centralized control workspace indicated by the workspace identifier, and change the original workspace corresponding to the target identifier in the departure flight data control system to the centralized control workspace indicated by the workspace identifier.

[0149] 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-readable medium, and the computer program includes a 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 509, or installed from the storage device 506, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0150] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should 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 merely example forms of implementing the claims.

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

[0152] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

Claims

1. A method for centralized control of departure flight plans, characterized in that: Applied to a pre-established open flight data control system, the open flight data control system at least including all functions of a departure flight data control system; The method for centralized control of departure flight plans includes: receiving a workspace change request corresponding to a target flight, wherein the workspace change request is a request for changing a workspace initiated at any time before a preset centralized control date, the target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule, and the workspace change request includes a workspace identifier for indicating a centralized control workspace corresponding to a centralized control user and a target identifier for indicating the target flight, wherein the centralized control user is a preset user with centralized control authority over all flights of the target airline; If the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located, the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system is changed to the centralized control work area indicated by the work area identifier, wherein the original work area refers to the work area at the airport where the target flight is located; After receiving a flight plan change request corresponding to the target flight, if the flight plan change request is initiated by a user at the airport where the target flight is located and / or the centralized control user, modifying the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request to obtain flight plan change data; The flight plan change data is backed up in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

2. The method for centralized control of departure flight plans according to claim 1, characterized in that: The process of taking the work area change request and the flight plan change request as target requests, and determining whether the target requests are requests initiated by the centralized control user, includes: Determining whether the initiator of the target request has a centralized control authority identifier; If so, it is determined that the target request is a request initiated by the centralized control user.

3. The method for centralized control of departure flight plans according to claim 1, characterized in that: The process of determining whether the flight plan change request is initiated by a user at the airport where the target flight is located includes: Determining whether the initiator of the flight plan change request has both a first attribute and a second attribute, wherein the first attribute is the target airline and the second attribute is the airport where the target flight is located; If so, it is determined that the flight plan change request is a request initiated by a user at the airport where the target flight is located.

4. The method for centralized control of departure flight plans according to claim 1, characterized in that: Also includes: Verify whether the work area change request meets preset mandatory items and format requirements, so that if the verification result is yes, execute the following: if the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located, then change the original work area corresponding to the target identifier in the open flight data control system and the departure flight data control system to the centralized control work area indicated by the work area identifier.

5. The method for centralized control of departure flight plans according to claim 1, characterized in that: The step of changing the original workspaces corresponding to the target identifiers in the open flight data control system and the departure flight data control system to the centralized control workspace indicated by the workspace identifier includes: Determining the flight number of the target flight according to the target identifier; Determine whether the flight number of the target flight exists and is valid; If so, the original work area corresponding to the target identifier in the open flight data control system is changed to the centralized control work area indicated by the work area identifier, and the original work area corresponding to the target identifier in the departure flight data control system is changed to the centralized control work area indicated by the work area identifier.

6. The method for centralized control of departure flight plans according to claim 5, characterized in that: The step of changing the original work area corresponding to the target identifier in the open flight data control system to the centralized control work area indicated by the work area identifier, and changing the original work area corresponding to the target identifier in the departure flight data control system to the centralized control work area indicated by the work area identifier, includes: sending the work area change request to the departure flight data control system so that the departure flight data control system changes the original work area corresponding to the target identifier in its own system to the centralized control work area indicated by the work area identifier, and feeding back a response message indicating whether the work area change is successful to the open flight data control system; If response information indicating that the work area change is successful is received, the original work area corresponding to the target identifier in the open flight data control system is changed to the centralized control work area indicated by the work area identifier.

7. A device for centralized control of departure flight plans, characterized in that: Applied to a pre-established open flight data control system, the open flight data control system at least including all functions of a departure flight data control system; The centralized control device for departure flight plans includes: a work area change request receiving module, configured to receive a work area change request corresponding to a target flight, wherein the work area change request is a request for changing a work area initiated at any time before a preset centralized control date, the target flight is a flight of a target airline that is to undergo centralized control of a departure flight schedule, and the work area change request includes a work area identifier for indicating the centralized control work area corresponding to a centralized control user and a target identifier for indicating the target flight, wherein the centralized control user is a preset user with centralized control authority over all flights of the target airline; a work area changing module configured to change the original work area corresponding to the target identifier in both the open flight data control system and the departure flight data control system to the centralized control work area indicated by the work area identifier, if the work area change request is initiated by a user and / or a centralized control user at the airport where the target flight is located; wherein the original work area refers to the work area at the airport where the target flight is located; a flight plan change module configured to, upon receiving a flight plan change request corresponding to the target flight, modify the flight plan to be changed corresponding to the target flight in the open flight data control system based on the flight plan change request if the flight plan change request is initiated by a user at the airport where the target flight is located and / or the centralized control user, thereby obtaining flight plan change data; A data backup module is used to back up the flight plan change data in the departure flight data control system based on the authority granted by the departure flight data control system to the open flight data control system.

8. The device for centralized control of departure flight plans according to claim 7, characterized in that: When determining whether the work area change request is a request initiated by the centralized control user, the work area change module is specifically configured to: determine whether the initiator of the work area change request has a centralized control authority identifier, and if so, determine that the work area change request is a request initiated by the centralized control user; When determining whether the flight plan change request is a request initiated by the centralized control user, the flight plan change module is specifically used to: determine whether the initiator of the flight plan change request has the centralized control authority identifier; if so, determine that the flight plan change request is a request initiated by the centralized control user.

9. The device for centralized control of departure flight plans according to claim 7, characterized in that: When determining whether the flight plan change request is a request initiated by a user at the airport where the target flight is located, the flight plan change module is specifically used to: determine whether the initiator of the flight plan change request has both a first attribute and a second attribute; if so, determine that the flight plan change request is a request initiated by a user at the airport where the target flight is located, wherein the first attribute is the target airline and the second attribute is the airport where the target flight is located.

10. The device for centralized control of departure flight plans according to claim 7, characterized in that: When changing the original work areas corresponding to the target identifiers in both the open flight data control system and the departing flight data control system to the centralized control work area indicated by the work area identifier, the work area changing module is specifically configured to: determine the flight number of the target flight based on the target identifier, determine whether the flight number of the target flight exists and is valid, and if so, change the original work area corresponding to the target identifier in the open flight data control system to the centralized control work area indicated by the work area identifier, and change the original work area corresponding to the target identifier in the departing flight data control system to the centralized control work area indicated by the work area identifier.

Images