CN114579586A - Flight life process data association method based on flight identification number - Google Patents
Flight life process data association method based on flight identification number Download PDFInfo
- Publication number
- CN114579586A CN114579586A CN202210054548.9A CN202210054548A CN114579586A CN 114579586 A CN114579586 A CN 114579586A CN 202210054548 A CN202210054548 A CN 202210054548A CN 114579586 A CN114579586 A CN 114579586A
- Authority
- CN
- China
- Prior art keywords
- flight
- identification number
- data
- date
- marketing
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000008569 process Effects 0.000 title claims abstract description 5
- 230000010006 flight Effects 0.000 claims abstract description 10
- 230000001360 synchronised effect Effects 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 3
- 230000004888 barrier function Effects 0.000 description 3
- 238000011156 evaluation Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
-
- 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/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G06Q50/40—
Abstract
The invention discloses a flight life process data correlation method based on flight identification numbers, which can adjust flights in real time according to a flight planning system, creating an operation domain flight identification number and a marketing flight identification number for the newly added flight in the flight center, respectively sending the operation domain flight identification number and the marketing flight identification number to an operation domain business department and a marketing domain business department of an airline company, updating flight information for the existing flight, marking the cancelled flight with failure, each operation domain service department and each marketing domain service department respectively use the operation domain flight identification number and the marketing domain flight identification number as unique identifications of corresponding flights to synchronize operation domain service data and marketing domain service data to the flight center database, so that the operation domain service department and the marketing domain service department can respectively inquire any operation domain service data or marketing domain service data of the corresponding flights to the flight center database through the operation domain flight identification number and the marketing domain flight identification number; therefore, the invention realizes the real-time intercommunication and interconnection of flight data.
Description
Technical Field
The invention relates to a civil aviation flight data association method, in particular to a flight life flow data association method based on flight identification numbers.
Background
The south navigation runs 2000 flights every day, nearly 300 stations all over the world are spread, a flight production chain relates to a plurality of business departments, data generated in each link are numerous and complicated, and data such as flight planning, sales, engineering, operation and the like cannot be interconnected and communicated in real time. Therefore, each business unit is more and more eagerly hoped to acquire timely, accurate and complete flight data.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method is used for solving the problem that flight related data of each business department of an airline company cannot be communicated and interconnected in real time in the prior art.
The technical scheme adopted by the invention is as follows:
a flight life process data association method based on flight identification numbers is characterized by comprising the following steps:
step S1, establishing a flight center capable of carrying out data communication with a flight planning system of an airline company, and synchronizing the flight centers according to a preset time interval so as to synchronize flight planning data in the flight planning system, which belong to a preset flight planning takeoff time range, to the flight center;
step S2, the flight center judges the operation type of each piece of flight planning data synchronized in step S1:
if the flight corresponding to the flight planning data does not exist in the flight center database of the flight center, the operation type is increased, and the flight corresponding to the flight planning data is represented as an added flight;
if the flight corresponding to the flight planning data exists in the flight center database of the flight center, the operation type is updated, and the flight corresponding to the flight planning data is an existing flight;
if the flight center database records the previously recorded flight schedule data belonging to the preset flight schedule takeoff time range, but the flight corresponding to the previously recorded flight schedule data does not exist in the flight schedule data synchronized in the step S1, marking the previously recorded flight schedule data as invalid, and indicating that the flight corresponding to the flight schedule data is a cancelled flight;
step S3, the flight center performs corresponding operations according to the operation types, including:
step S3-1, aiming at the flight plan data with the operation type of being newly added, the flight center marks the flight plan data as valid and records the valid flight plan data into the flight center database, creates an operation domain flight identification number and a marketing flight identification number for the flight corresponding to the flight plan data, sends the operation domain flight identification number of the flight to each operation domain service department (such as an operation control system, a flight service system, a ground service system and the like) of the airline company, and sends the marketing flight identification number of the flight to each marketing domain service department (such as a marketing system, a flight planning system and the like) of the airline company;
step S3-2, regarding the flight schedule data with the operation type being updated, the flight center marks the flight schedule data as valid, and uses the flight schedule data to update the flight information of the existing flights in the flight center database (including updating of flight information such as predicted arrival time, flight nature, specific takeoff time and the like);
step S4, each operation domain business department of the airline company takes the operation domain flight identification number as the unique identification of the corresponding flight, and synchronizes the operation domain business data of the corresponding flight to the flight center database through the operation domain flight identification number;
each marketing domain business department of the airline company takes the marketing domain flight identification number as a unique identification of a corresponding flight, and synchronizes marketing domain business data of the corresponding flight to the flight center database through the marketing domain flight identification number;
step S5, any operation domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight from the flight center database through the operation domain flight identification number;
and any marketing domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight from the flight center database through the marketing domain flight identification number.
Therefore, the invention realizes the real-time intercommunication and interconnection of flight life flow data from flight plan generation to post-flight evaluation among all business departments of the airline company, so that all business departments can obtain timely, accurate and complete flight data, the original data barrier among all business departments is broken, the problem of flight information matching among systems of the airline company is solved, and the timeliness and the accuracy of the data are ensured.
Preferably: in the step S2, the manner of determining whether the flight corresponding to the flight schedule data synchronized in the step S1 exists in the flight center database is as follows:
if the previously recorded flight planning data recorded in the flight center database is the same as the five keywords of the flight planning data, determining that the flight corresponding to the flight planning data exists in the flight center database of the flight center; otherwise, determining that the flight corresponding to the flight planning data does not exist in a flight center database of the flight center; wherein, the five keywords are: the method comprises the steps of setting a flight segment local date, an airline three-character code, a postfix-containing flight number, a planned take-off station and a planned arrival station, wherein the flight segment local date represents a take-off airport local date corresponding to the planned take-off date of a flight.
As a preferred embodiment of the present invention: in the step S3-1, the flight identification number of the operation domain is composed of six keywords, namely, the local date of the flight segment, the three-character code of the airline company, the flight number, the suffix of the flight number, the planned take-off station and the planned arrival station; the step S3-1 is to create one operation domain flight identification number for each common flight, where the local date of the leg of the operation domain flight identification number is the local date of the takeoff airport corresponding to the planned takeoff date of the common flight; in the step S3-1, two operation domain flight identification numbers are created for each online flight, the local date of the flight segment of the first operation domain flight identification number is the local date of the takeoff airport corresponding to the first segment planned takeoff date of the online flight, and the local date of the flight segment of the second operation domain flight identification number is the local date of the takeoff airport corresponding to the second segment planned takeoff date of the online flight.
In the step S3-1, the marketing flight identification number is composed of four keywords, i.e., a local time date, an airline second word code, a flight number, and a flight number suffix; for the common flight, the local time date is the local date of the takeoff airport corresponding to the planned takeoff date of the flight, and for the link flight, the local time date is the local date of the takeoff airport corresponding to the first section of planned takeoff date of the link flight.
Preferably: in step S1, the flight center is synchronized with the flight planning system through an ETL tool.
Preferably: in step S1, the time interval for the flight center to synchronize is 20 minutes.
Preferably: in step S1, the preset scheduled takeoff time range of the flight is: the scheduled departure time for the flight is from day 3 in the future of the synchronization date to day 62 in the future of the synchronization date.
In addition:
preferably: the flight center may further provide different data interfaces such as a flight domain, a dynamic domain, an airport domain, an airplane domain, and the like, and other downstream systems of the airline company may query the flight center database for the operation domain service data and the marketing domain service data synchronized in step S4 through the corresponding data interfaces, and the query may be implemented in a micro service form through an API manner, so as to improve the data utilization rate and reduce the data development cost.
Preferably: the technical framework of the flight center adopts a special cloud edas + slb + api gateway + springclosed-Alibaba + springboot + springing + mybatis + ETL tool to build a high-availability flexible service framework.
Compared with the prior art, the invention has the following beneficial effects:
the invention can adjust the flight in real time according to the flight planning system, uniformly creates the operation domain flight identification number and the marketing flight identification number for the newly added flight in the flight center and respectively sends the operation domain flight identification number and the marketing flight identification number to the operation domain business department and the marketing domain business department of the airline company, updates the flight information for the existing flight, marks the failure of the cancelled flight, and each operation domain service department and the marketing domain service department synchronize operation domain service data and marketing domain service data to the flight center database by taking the operation domain flight identification number and the marketing domain flight identification number as unique identifications of corresponding flights respectively, the operation domain business department and the marketing domain business department can respectively inquire any operation domain business data or marketing domain business data of corresponding flights to the flight center database through the operation domain flight identification number and the marketing domain flight identification number; therefore, the invention realizes the real-time intercommunication and interconnection of flight life flow data from flight plan generation to post-flight evaluation among all business departments of the airline company, so that all business departments can obtain timely, accurate and complete flight data, the original data barrier among all business departments is broken, the problem of flight information matching among systems of the airline company is solved, and the timeliness and the accuracy of the data are ensured.
Drawings
The invention is described in further detail below with reference to the following figures and specific examples:
fig. 1 is a flow chart of a flight life flow data association method according to the present invention.
Detailed Description
The present invention will be described in detail with reference to the following embodiments and the accompanying drawings to help those skilled in the art to better understand the inventive concept of the present invention, but the scope of the claims of the present invention is not limited to the following embodiments, and all other embodiments obtained without inventive efforts by those skilled in the art will fall within the scope of the present invention without departing from the inventive concept of the present invention.
Example one
As shown in fig. 1, the invention discloses a flight life flow data association method based on flight identification numbers, which includes:
step S1, establishing a flight center capable of carrying out data communication with a flight planning system of an airline company, and synchronizing the flight centers according to a preset time interval so as to synchronize flight planning data in the flight planning system, which belong to a preset flight planning takeoff time range, to the flight center;
step S2, the flight center performs operation type judgment on each piece of flight plan data synchronized in step S1:
if the flight corresponding to the flight planning data does not exist in the flight center database of the flight center, the operation type is increased, and the flight corresponding to the flight planning data is represented as an added flight;
if the flight corresponding to the flight planning data exists in the flight center database of the flight center, the operation type is updated, and the flight corresponding to the flight planning data is an existing flight;
if the flight center database records the previously recorded flight schedule data belonging to the preset flight schedule takeoff time range, but the flight corresponding to the previously recorded flight schedule data does not exist in the flight schedule data synchronized in the step S1, marking the previously recorded flight schedule data as invalid, and indicating that the flight corresponding to the flight schedule data is a cancelled flight;
step S3, the flight center performs corresponding operations according to the operation types, including:
step S3-1, aiming at the flight plan data with the operation type of being newly added, the flight center marks the flight plan data as valid and records the valid flight plan data into the flight center database, creates an operation domain flight identification number and a marketing flight identification number for the flight corresponding to the flight plan data, sends the operation domain flight identification number of the flight to each operation domain service department (such as an operation control system, a flight service system, a ground service system and the like) of the airline company, and sends the marketing flight identification number of the flight to each marketing domain service department (such as a marketing system, a flight planning system and the like) of the airline company;
step S3-2, aiming at the flight planning data with the operation type being updated, the flight center marks the flight planning data as valid, and uses the flight planning data to update the flight information of the existing flights in the flight center database (including the update of the flight information such as the estimated arrival time, the flight property, the specific departure time and the like);
step S4, each operation domain business department of the airline company takes the operation domain flight identification number as the unique identification of the corresponding flight, and synchronizes the operation domain business data of the corresponding flight to the flight center database through the operation domain flight identification number;
each marketing domain business department of the airline company takes the marketing domain flight identification number as a unique identification of a corresponding flight, and synchronizes marketing domain business data of the corresponding flight to the flight center database through the marketing domain flight identification number;
step S5, any operation domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight from the flight center database through the operation domain flight identification number;
and any marketing domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight from the flight center database through the marketing domain flight identification number.
Therefore, the invention realizes the real-time intercommunication and interconnection of flight life flow data from flight plan generation to post-flight evaluation among all business departments of the airline company, so that all business departments can obtain timely, accurate and complete flight data, the original data barrier among all business departments is broken, the problem of flight information matching among systems of the airline company is solved, and the timeliness and the accuracy of the data are ensured.
The above is a basic implementation manner of the first embodiment, and further optimization, improvement and limitation may be performed on the basis of the basic implementation manner:
preferably, the following components: in the step S2, the manner of determining whether the flight corresponding to the flight schedule data synchronized in the step S1 exists in the flight center database is as follows:
if the previously recorded flight planning data recorded in the flight center database is the same as the five keywords of the flight planning data, determining that the flight corresponding to the flight planning data exists in the flight center database of the flight center; otherwise, determining that the flight corresponding to the flight planning data does not exist in a flight center database of the flight center; wherein the five keywords are: the method comprises the steps of setting a flight segment local date, an airline three-character code, a postfix-containing flight number, a planned take-off station and a planned arrival station, wherein the flight segment local date represents a take-off airport local date corresponding to the planned take-off date of a flight.
Preferably: in step S1, the flight center is synchronized with the flight planning system through an ETL tool.
Preferably: in step S1, the time interval for the flight center to synchronize is 20 minutes.
Preferably: in step S1, the preset scheduled takeoff time range of the flight is: the scheduled departure time for the flight is from day 3 in the future of the synchronization date to day 62 in the future of the synchronization date.
Example two
On the basis of the first embodiment, the second embodiment also adopts the following preferred embodiments:
in the step S3-1, the flight identification number of the operation domain is composed of six keywords, namely, the local date of the flight segment, the three-character code of the airline company, the flight number, the suffix of the flight number, the planned take-off station and the planned arrival station; the step S3-1 is to create one operation domain flight identification number for each common flight, where the local date of the leg of the operation domain flight identification number is the local date of the takeoff airport corresponding to the planned takeoff date of the common flight; in the step S3-1, two operation domain flight identification numbers are created for each online flight, the local date of the flight segment of the first operation domain flight identification number is the local date of the takeoff airport corresponding to the first segment planned takeoff date of the online flight, and the local date of the flight segment of the second operation domain flight identification number is the local date of the takeoff airport corresponding to the second segment planned takeoff date of the online flight.
In the step S3-1, the marketing flight identification number is composed of four keywords, i.e., a local time date, an airline second word code, a flight number, and a flight number suffix; for the common flight, the local time date is the local date of the takeoff airport corresponding to the planned takeoff date of the flight, and for the link flight, the local time date is the local date of the takeoff airport corresponding to the first section of planned takeoff date of the link flight.
In addition:
preferably: the flight center may further provide different data interfaces such as a flight domain, a dynamic domain, an airport domain, an airplane domain, and the like, and other downstream systems of the airline company may query the flight center database for the operation domain service data and the marketing domain service data synchronized in step S4 through the corresponding data interfaces, and the query may be implemented in a micro service form through an API manner, so as to improve the data utilization rate and reduce the data development cost.
Preferably, the following components: a technical framework of the flight center adopts a special cloud edas + slb + api gateway + spring bound-Alibaba + spring boot + spring + mybatis + ETL tool to build a high-availability flexible service framework.
The present invention is not limited to the above embodiments, and various other equivalent modifications, substitutions and alterations can be made without departing from the basic technical concept of the invention as described above, according to the common technical knowledge and conventional means in the field.
Claims (7)
1. A flight life process data association method based on flight identification numbers is characterized by comprising the following steps:
step S1, establishing a flight center capable of carrying out data communication with a flight planning system of an airline company, and synchronizing the flight centers according to a preset time interval so as to synchronize flight planning data in the flight planning system, which belong to a preset flight planning takeoff time range, to the flight center;
step S2, the flight center judges the operation type of each piece of flight planning data synchronized in step S1:
if the flight corresponding to the flight planning data does not exist in the flight center database of the flight center, the operation type is newly increased;
if the flight corresponding to the flight planning data exists in a flight center database of a flight center, the operation type is updating;
if the flight center database records the previously recorded flight schedule data belonging to the preset flight schedule takeoff time range, but the flight corresponding to the previously recorded flight schedule data does not exist in the flight schedule data synchronized in the step S1, marking the previously recorded flight schedule data as invalid;
step S3, the flight center performs corresponding operations according to the operation types, including:
step S3-1, aiming at the newly added flight plan data with the operation type, the flight center marks the flight plan data as valid and records the valid flight plan data into the flight center database, creates an operation domain flight identification number and a marketing flight identification number for the flight corresponding to the flight plan data, sends the operation domain flight identification number of the flight to each operation domain business department of the airline company, and sends the marketing flight identification number of the flight to each marketing domain business department of the airline company;
step S3-2, aiming at the flight planning data with the operation type being updated, the flight center marks the flight planning data as valid and uses the flight planning data to update the flight information of the existing flights in the flight center database;
step S4, each operation domain business department of the airline company takes the operation domain flight identification number as the unique identification of the corresponding flight, and synchronizes the operation domain business data of the corresponding flight to the flight center database through the operation domain flight identification number;
each marketing domain business department of the airline company takes the marketing domain flight identification number as a unique identification of a corresponding flight, and synchronizes marketing domain business data of the corresponding flight to the flight center database through the marketing domain flight identification number;
step S5, any operation domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight to the flight center database through the operation domain flight identification number;
and any marketing domain business department of the airline company inquires any operation domain business data or marketing domain business data of the corresponding flight from the flight center database through the marketing domain flight identification number.
2. The method of claim 1, wherein the method further comprises the step of associating flight life-cycle data based on the flight identification number: in the step S2, the manner of determining whether the flight corresponding to the flight schedule data synchronized in the step S1 exists in the flight center database is as follows:
if the previously recorded flight planning data recorded in the flight center database is the same as the five keywords of the flight planning data, determining that the flight corresponding to the flight planning data exists in the flight center database of the flight center; otherwise, determining that the flight corresponding to the flight planning data does not exist in a flight center database of the flight center; wherein, the five keywords are: the method comprises the steps of setting a flight segment local date, an airline three-character code, a postfix-containing flight number, a planned take-off station and a planned arrival station, wherein the flight segment local date represents a take-off airport local date corresponding to the planned take-off date of a flight.
3. The method for associating flight life-flow data based on flight identification number as claimed in claim 1 or 2, wherein: in the step S3-1, the flight identification number of the operation domain is composed of six keywords, namely, the local date of the flight segment, the three-character code of the airline company, the flight number, the suffix of the flight number, the planned take-off station and the planned arrival station; the step S3-1 is to create one operation domain flight identification number for each common flight, where the local date of the leg of the operation domain flight identification number is the local date of the takeoff airport corresponding to the planned takeoff date of the common flight; in the step S3-1, two operation domain flight identification numbers are created for each round of online flights, the local date of the flight segment of the first operation domain flight identification number is the local date of the takeoff airport corresponding to the first segment of planned takeoff date of the online flight, and the local date of the flight segment of the second operation domain flight identification number is the local date of the takeoff airport corresponding to the second segment of planned takeoff date of the online flight.
4. The method of claim 3, wherein the flight life-cycle data association is based on a flight identification number, and wherein: in the step S3-1, the marketing flight identification number is composed of four keywords, i.e., a local time date, an airline second word code, a flight number, and a flight number suffix; for the common flight, the local time date is the local date of the takeoff airport corresponding to the planned takeoff date of the flight, and for the link flight, the local time date is the local date of the takeoff airport corresponding to the first section of planned takeoff date of the link flight.
5. The method for associating flight life-flow data based on flight identification number as claimed in claim 1 or 2, wherein: in step S1, the flight center is synchronized with the flight planning system through an ETL tool.
6. The method for associating flight life-flow data based on flight identification number as claimed in claim 1 or 2, wherein: in step S1, the time interval for the flight center to synchronize is 20 minutes.
7. The method for associating flight life-flow data based on flight identification number as claimed in claim 1 or 2, wherein: in the step S1, the preset scheduled takeoff time range of the flight is: the scheduled departure time for the flight is from day 3 in the future of the synchronization date to day 62 in the future of the synchronization date.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210054548.9A CN114579586A (en) | 2022-01-18 | 2022-01-18 | Flight life process data association method based on flight identification number |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210054548.9A CN114579586A (en) | 2022-01-18 | 2022-01-18 | Flight life process data association method based on flight identification number |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114579586A true CN114579586A (en) | 2022-06-03 |
Family
ID=81771401
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210054548.9A Withdrawn CN114579586A (en) | 2022-01-18 | 2022-01-18 | Flight life process data association method based on flight identification number |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579586A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116701408A (en) * | 2023-08-02 | 2023-09-05 | 中国民用航空总局第二研究所 | Flight service primary key processing method and device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090063219A1 (en) * | 2007-09-04 | 2009-03-05 | Amadeus S.A.S. | Revenue monitoring method and system, in particular for airline companies |
| CN105448140A (en) * | 2015-12-30 | 2016-03-30 | 北京招通致晟科技有限公司 | Method and device for obtaining dynamic information of flight |
| CN111078687A (en) * | 2019-11-14 | 2020-04-28 | 青岛民航空管实业发展有限公司 | Flight operation data fusion method, device and equipment |
-
2022
- 2022-01-18 CN CN202210054548.9A patent/CN114579586A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090063219A1 (en) * | 2007-09-04 | 2009-03-05 | Amadeus S.A.S. | Revenue monitoring method and system, in particular for airline companies |
| CN105448140A (en) * | 2015-12-30 | 2016-03-30 | 北京招通致晟科技有限公司 | Method and device for obtaining dynamic information of flight |
| CN111078687A (en) * | 2019-11-14 | 2020-04-28 | 青岛民航空管实业发展有限公司 | Flight operation data fusion method, device and equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116701408A (en) * | 2023-08-02 | 2023-09-05 | 中国民用航空总局第二研究所 | Flight service primary key processing method and device, electronic equipment and storage medium |
| CN116701408B (en) * | 2023-08-02 | 2023-10-20 | 中国民用航空总局第二研究所 | Flight service primary key processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10580309B2 (en) | Resilient enhancement of trajectory-based operations in aviation | |
| CN202549080U (en) | Fusion system of radar data, flight plan data and ADS-B data | |
| US7715943B2 (en) | Microserver for managing an assembly or repair of a product | |
| US20120143405A1 (en) | Data synchronisation for a flight information system | |
| Xu et al. | Cloud-based fleet management for prefabrication transportation | |
| US6161097A (en) | Automated traffic management system and method | |
| US8170988B2 (en) | System and method for synchronizing databases | |
| CN111078687B (en) | Flight operation data fusion method, device and equipment | |
| CN103136249A (en) | System and method of multiplex mode isomerous data integration | |
| CN112328642B (en) | Aviation multi-source data entity alignment method and device and readable storage medium | |
| CN114579586A (en) | Flight life process data association method based on flight identification number | |
| CN106126729A (en) | A kind of electronic chart kilometer stone data acquisition and update method | |
| CN103678572B (en) | Method and system for searching for Internet of Things information based on two layers of DHTs | |
| CN107798444B (en) | Hot-rolled strip steel MES system parallel debugging data acquisition method | |
| EP2881903A1 (en) | Managing design updates in a manufacturing execution system | |
| CN101266661A (en) | Requirement analysis method for information system integration service | |
| CN102496084A (en) | Automatic processing method of civil aviation approval message | |
| CN105701220A (en) | Internal business data system and processing method of enterprise | |
| CN111696389B (en) | Aircraft fuel estimation method and system based on flight plan | |
| CN108900497B (en) | Data synchronization method and system between heterogeneous systems | |
| JP3706004B2 (en) | Train control simulator | |
| CN115952471A (en) | Method, apparatus, computing device and medium for fusing data of different data sources | |
| CN110224926A (en) | A kind of aviation unit builds the system and method for group automatically | |
| Qing et al. | The aircraft service life and maintenance early warning management based on configuration | |
| GB2447638A (en) | Global air traffic control mechanism |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20220603 |