Method and device for cross validation of stop flight multi-source passenger data and market size calculation
By cross-checksum integration of multi-source data for suspended flights, data reliability and accuracy problems are solved, the accuracy of market size calculations is improved, and airlines are helped to design route networks more scientifically, optimize flight plans, and improve operations benefit.
Patent Information
- Application Number
- CN202411052254.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-02
- Publication Date
- 2024-11-22
AI Technical Summary
In the prior art, there are data reliability and accuracy problems in cross-verification and market size calculation of multi-source passenger data for suspended flights, resulting in deviations in airlines in route network design and business decisions.
By extracting flight information from the LDM message of the flight industry after departure, the PDD system after departure, and the civil aviation settlement system RA, a data table unique index is established, the passenger number consistency of the flight operation data is verified, and the number of passengers in the flight operation data is generated. Integrate data, calculate passenger errors and mismatch rates, and finally count the size of the OD market and data credibility.
It improves the accuracy and granularity of market size calculations, ensures high matching rate and reliability of passenger data, reduces route network decision-making deviations caused by data errors, and improves the operating efficiency of airlines.
Smart Images

Figure CN119006046A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of civil aviation route network management, and in particular to a method for cross-validating multi-source passenger data of stopover flights and calculating the OD market size. Background Art
[0002] In the airline market competition, route network is the first step in implementing the airline's business strategy. The judgment of market size is an important prerequisite for airlines to design route networks, compile flight plans, aircraft scheduling, crew scheduling and revenue management. The airline route network design must change with the changes in the domestic and international civil aviation markets, seize market trends, and allocate the airline's most important flight rights, aircraft and crew resources to markets with large market space to improve the economic benefits of the airline. The general practice is to estimate the market size of the same flight season next year based on the existing market historical passenger travel data. Therefore, it is important to accurately determine the market size based on historical passenger data.
[0003] There are direct flights, stopover flights and transfer flights in the market. Routes with good markets are not only direct flights, but also have high frequencies. However, airlines cannot lose the market of routes with average markets. Generally, they operate the market with stopover flights, especially international flights, to supplement passengers and increase flight occupancy rate through stopovers.
[0004] Airlines have many different sources of passenger data, including the post-flight PDD system that records the number of passengers in different cabins of departing passengers, the flight passenger statistics entered in the LDM message of the flight load system after departure and the mission book recorded by the pilot, and the revenue data of each cabin in the civil aviation revenue settlement system RA that is entered and counted based on the passenger ticket data. In order to ensure the quality of the passenger data used, it is necessary to cross-verify the data consistency of multi-source passenger data in advance, especially for stopover flights, which are prone to statistical errors for different data sources. This patent design is within a reasonable error range to relatively accurately count the market size of this flight season. Summary of the invention
[0005] The embodiments of the present application provide a method for cross-validating multi-source passenger data of stopover flights and calculating market size, so as to solve the problems of data reliability and market size calculation in related technologies and improve the calculation accuracy and granularity of market size.
[0006] In a first aspect, an embodiment of the present application provides a method for cross-validating multi-source passenger data of stopover flights and calculating market size, comprising:
[0007] Select a flight and obtain flight information, including but not limited to flight number, flight date, departure point, arrival point, aircraft number, and aircraft cabin configuration;
[0008] The number of passengers in each segment is extracted from the LDM message of the flight payload system after departure according to the flight information, which is called LDM data. The number of passengers in each segment is the number of passengers in the first class cabin (denoted as F), the number of passengers in the business class cabin (denoted as C), the number of passengers in the economy class cabin (denoted as Y), the number of adults (denoted as A), the number of children (denoted as C), the number of infants (denoted as I), and the total number of passengers in each segment (Segment / Leg) of the flight.
[0009] Passenger data on the flight (Leg) is extracted from the airline's post-flight PDD system after the flight departs based on the flight information, which is called PDD data. The PDD data includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats;
[0010] The flight segment data of each itinerary collected from the civil aviation settlement system RA based on the flight information is called RA data, which includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each cabin (F / C / Y) of the aircraft, and the fare revenue of each cabin (F / C / Y);
[0011] Establish a unique index of flight information in the data tables of the LDM data, PDD data and RA data, verify the consistency of the number of passengers (F / C / Y) of each leg Leg according to the flight information by checking the flight operation data LDM data and PDD data according to the verification logic, calculate the mismatch rate, and generate LDM / PDD integrated data;
[0012] According to the flight information, the flight operation LDM / PDD integrated data is compared with the flight settlement RA data to calculate the passenger error;
[0013] Calculate the passenger mismatch rate based on the RA data of the LDM / PDD integration and settlement;
[0014] Based on the flight settlement RA data, the market size of each OD and the credibility of flight passenger data are calculated.
[0015] In a second aspect, an embodiment of the present application provides a device for cross-validating multi-source passenger data of a stopover flight and calculating market size, comprising:
[0016] A flight acquisition unit, used to select a flight and acquire flight information, including but not limited to flight number, flight date, departure point, arrival point, aircraft number, and aircraft cabin configuration;
[0017] The LDM acquisition unit is used to extract the number of passengers in the flight segment from the LDM message of the flight payload system after departure according to the flight information, which is called LDM data. The number of passengers in the flight segment is the number of first class passengers F, business class passengers C, economy class passengers Y, adults, children, infants, and the total number of passengers in each segment (Segment / Leg) operated by the flight;
[0018] The PDD acquisition unit is used to extract the passenger data on the flight (Leg) from the airline's post-departure PDD system according to the flight information, which is called PDD data. The PDD data includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats;
[0019] RA acquisition unit, used to count the flight segment data in each itinerary from the civil aviation settlement system RA according to the flight information, which is called RA data. The RA data includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each cabin (F / C / Y) of the aircraft, and the fare revenue of each cabin (F / C / Y);
[0020] An operation data comparison unit is used to establish a unique index of flight information in the data tables of the LDM data, PDD data and RA data, verify the consistency of the number of passengers (F / C / Y) of each leg Leg by comparing the flight operation data LDM data and PDD data according to the verification logic according to the flight information, calculate the mismatch rate, and generate LDM / PDD integrated data;
[0021] A settlement data verification unit, used to compare the flight operation LDM / PDD integrated data with the flight settlement RA data according to the flight information, and calculate the passenger error;
[0022] The passenger mismatch unit is used to calculate the passenger mismatch rate based on the operation data LDM / PDD and the settled RA data;
[0023] The OD market calculation unit is used to calculate the size of each OD market and the credibility of flight passenger data based on flight settlement RA data.
[0024] Compared with the prior art, this application has the following advantages:
[0025] According to the embodiment of the present application, in order to accurately count the number of passengers of airlines in various markets, relevant data sources such as post-departure PDD system data, aircraft load LDM system data and revenue settlement system RA data are integrated together, and the consistency of passenger data is verified by a cross-check method to ensure a high matching rate of passenger data, so that the statistical OD market size is more reliable and accurate. Since flights often change during flight operations, such as flight cancellations due to airline reasons and weather reasons, frequent changes in flight models, mergers, etc., and passenger disembarkation due to passenger reasons, flight passenger data will also change accordingly. Single data sources often have errors and the granularity of a single data source is not enough. Passenger data is inconsistent due to different data sources. Sometimes the statistical method is not rigorous, resulting in data quality problems. Sometimes the data cannot be verified manually, and existing data is used habitually. This causes data-driven route network decisions to have certain deviations, affecting airline operations.
[0026] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments according to the present application and should not be regarded as limiting the scope of the present application.
[0028] Figure 1 is a flow chart showing a method for cross-validation of stopover flight data and calculation of market size according to an embodiment of the present application;
[0029] Figure 2 is a data verification flow chart of LDM and PDD showing an embodiment of the present application;
[0030] Figure 3 is a data verification flow chart of LDM / PDD and RA showing an embodiment of the present application; and
[0031] Figure 4 2 is a structural diagram showing a device for cross-validation of stopover flight data and calculation of market size according to an embodiment of the present application. DETAILED DESCRIPTION
[0032] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the concept or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary in nature and not restrictive.
[0033] To facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the related technologies of the embodiments of the present application. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.
[0034] Aircraft are the most valuable assets of airlines, and air rights are an indispensable resource for airlines. In order to maximize benefits, airlines design and optimize route networks to make full use of the airlines' aircraft and air rights resources. Generally speaking, airlines use revenue-exclusive direct flights and stopover routes in mainstream markets, and other airlines use revenue-sharing code-sharing flights in mainstream markets. For markets to be developed and without air rights, flight connection methods are used to share market revenue. Therefore, it is very important to fully understand the market size and peak and off-peak seasons of your own airline. This patent invents a method of cross-checking multi-source data and accurately counting the size of the aviation market to purposefully design the airline's own route network.
[0035] An embodiment of the present application provides a method for cross-checking and accurately counting the size of the aviation market using multi-source data. In this embodiment of the present application, in order to grasp the operating performance of the year, the airline takes stock of the route operation results, prepares for the next flight season, and optimizes the flight plan. In order to accurately count the performance of the airline market, it is necessary to know the size of the airline in each market and the market share of the airline in the market from the historical passenger data. There are three sources of passenger data for flight operation history data: one is the PDD data of confirmed departing passengers after the flight leaves; the second is the LDM data on the number of passengers in the flight segment parsed from the LDM message; and the third is the RA data on revenue data parsed from the ticket coupon. If a single data source is used, errors are inevitable in system entry statistics. Although verification is time-consuming and labor-intensive, it can improve the accuracy of the data. The cross-check of multi-source data and the accurate statistical method of aviation market size can develop a computer system, which can be executed on computer devices, especially on the computer devices of airlines. Of course, it can also be executed in the cloud through cloud computing. No matter which computer entity is executed, it can be shared among all airlines through uploading and sharing, or accurately statistically calculate the size of the aviation market within the authorized airlines, so as to better build future flight plans, better meet the travel requirements of passengers, and maximize the benefits of airlines. The following will refer to Figure 1 The multi-source data cross-checking and accurate statistical method of aviation market size in this application are explained. Figure 11 is a flowchart showing a multi-source data cross-check method and a method for calculating market size according to an embodiment of the present application. Figure 1 As shown, the multi-source data cross-check and market size calculation method may include the following steps S100 to S800. Steps S100 to S800 will be described below in conjunction with specific embodiments.
[0036] First, enter step S100. In step S100, a flight is selected and flight information is obtained, wherein the flight information includes but is not limited to flight number, flight date, departure place, arrival place, aircraft number, and aircraft seat configuration.
[0037] In one embodiment, a stopover flight CA2535 is selected, the route is TFU-AHJ-LXA, from Chengdu Tianfu Airport to Lhasa Airport in Tibet Autonomous Region, with a stopover at Aba Hongyuan Airport. In order to illustrate this method, only actual flight data of three times 20231010, 20231021, and 20231024 are selected as demonstrations.
[0038] Next, enter step S200. In step S200, the number of passengers in the flight segment is extracted from the LDM message of the flight payload system after departure according to the flight information, which is called LDM data. The number of passengers in the flight segment is the number of first-class passengers (denoted as F), business-class passengers (denoted as C), economy-class passengers (denoted as Y), the total number of passengers, and the number of adults (denoted as A), children (denoted as C), and infants (denoted as I) in each segment (Segment / Leg) of the flight.
[0039] In one embodiment, LDM data is OD market-level data. In the historical data of CA2535 of three flight dates, the three flight segment market data of each flight are obtained according to the unique index of flight number, flight date, departure place and arrival place: TFU-LXA, TFU-AHJ, AHJ-LXA, which are displayed respectively by the number of first class passengers (F), the number of business class passengers (C), the number of economy class passengers (Y), the total number of passengers, and the number of adults (A), the number of children (C), and the number of infants (I). The LDM passenger information data table (Table 1) is as follows:
[0040] Table 1: LDM passenger information
[0041] Serial number Flight number O D date model Configuration F C Y Total number of people aldult child baby 1 CA2535 TFU LX 20231010 319 8 / 119 0 1 79 80 80 0 0 2 CA2535 TFU AHJ 20231010 319 8 / 119 0 1 25 26 26 0 0 3 CA2535 AHJ LX 20231010 319 8 / 119 0 4 2 6 5 1 1 4 CA2535 TFU LX 20231021 319 8 / 119 0 0 15 15 15 0 0 5 CA2535 TFU AHJ 20231021 319 8 / 119 0 0 8 8 8 0 0 6 CA2535 AHJ LX 20231021 319 8 / 119 0 5 7 12 12 0 0 7 CA2535 TFU LX 20231024 319 8 / 119 0 0 14 14 14 0 0 8 CA2535 TFU AHJ 20231024 319 8 / 119 0 5 75 80 80 0 0 9 CA2535 AHJ LX 20231024 319 8 / 119 0 5 0 5 5 0 0
[0042] Next, enter step S300. In step S300, according to the flight information, the passenger data on the flight (Leg) is extracted from the airline's post-departure PDD system, which is called PDD data. The PDD data includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats.
[0043] In one embodiment, the PDD data is provided to facilitate flight attendants to count the number of passengers after boarding the plane to prevent passengers from boarding the wrong plane or losing passengers. It is flight leg-level data. The post-flight PDD system data is the number of passengers boarding after departure, including flight data such as flight number, origin (O), destination (D), flight date, aircraft type, aircraft type (F / C / Y), number of first-class passengers (F), number of business-class passengers (C), number of economy-class passengers (Y), and total number of passengers departing. Since CA2535 is a stopover flight, there are two flight legs, the first leg is TFU-AHJ, and the second leg is AHJ-LXA. The airline's ground service staff only cares about how many passengers are on board each flight and whether it is consistent with the ticket booking staff. They do not care about the actual origin and destination of the passengers. The F / C / Y passenger number and total number data are obtained from the post-flight PDD system after CA2535 leaves the plane to obtain the post-flight PDD data table ( Figure 2 )as follows:
[0044] Table 2: PDD passenger information
[0045] Serial number Flight number O D date model Configuration F C Y Total number of people 1 CA2535 TFU AHJ 20231010 319 0 / 8 / 119 0 2 104 106 2 CA2535 AHJ LX 20231010 319 0 / 8 / 119 0 5 81 86 3 CA2535 TFU AHJ 20231021 319 0 / 8 / 119 0 0 23 23 4 CA2535 AHJ LX 20231021 319 0 / 8 / 119 0 5 22 27 5 CA2535 TFU AHJ 20231024 319 0 / 8 / 119 0 5 89 94 6 CA2535 AHJ LX 20231024 319 0 / 8 / 119 0 5 14 19
[0046] Next, enter step S400. In step S400, the flight segment data in each itinerary is counted from the civil aviation settlement system RA according to the flight information, which is called RA data. The RA data includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each class (F / C / Y) of the aircraft, and the fare revenue of each class (F / C / Y).
[0047] In one embodiment, flight CA2535 flies from Chengdu Tianfu Airport (TFU) to Lhasa Airport (LXA) in Tibet Autonomous Region, and stops at Aba Hongyuan Airport. This flight has three segments: one is TFU-LXA segment, one is TFU-AHJ segment, and one is AHJ-LXA segment. After calculating the number of passengers and revenue in first class (F), business class (C), and economy class (Y), and counting the total number of passengers and total revenue in the segment, the RA passenger information data table (Table 3) is obtained as follows:
[0048] Table 3: RA passenger information
[0049]
[0050] Next, enter step S500. In step S500, a flight information uniqueness index is established in the data tables of the LDM data, PDD data and RA data, and the flight operation data LDM data and PDD data are verified according to the flight information according to the verification logic to verify the consistency of the number of (F / C / Y) passengers in each leg Leg, calculate the mismatch rate, and use the LDM infant number to complete and generate LDM / PDD integrated data.
[0051] See below for more information. Figure 2 Explain the data verification process of LDM and PDD, Figure 2 For the data verification flow chart of LDM and PDD, see Figure 2 The data verification method of LDM and PDD is described, including steps S510 to S550. A brief description is given in conjunction with a specific embodiment as follows:
[0052] In step S510, the number of passengers in the first leg of the flight is obtained from the PDD, and the number of passengers in the first class cabin F / business class cabin C / economy class cabin Y / total number of passengers are compared with the number of passengers in the LDM according to the verification logic;
[0053] In step S520, the number of passengers in the second leg of the flight is obtained from the PDD, and the number of passengers in the first class cabin F / business class cabin C / economy class cabin Y / total number of passengers is compared with the number of passengers in the LDM according to the verification logic;
[0054] In step S530, the error between the total number of passengers on each flight of PDD and LDM is calculated;
[0055] In step S540, the PDD data is supplemented with the number of infants in the LDM data to form LDM / PDD integrated data aligned with the RA;
[0056] In step S550, the LDM and PDD mismatch ratio is calculated.
[0057] In one embodiment, data verification of LDM and PDD is performed. For the same flight number and date, the following formulas (1) and (2) are used to verify data consistency, with first class F, business class C, economy class Y and the total number of passengers respectively.
[0058] The verification logic for comparing the LDM data with the PDD data is the difference between the number of departures of the flight Leg in the PDD and the sum of the number of passengers in all flight segments associated with the flight Leg in the LDM data.
[0059] In one embodiment, two flight operation data sources LDM and PDD data of the flight are obtained, and the post-flight passenger data of the flight is obtained, and a cross-check is performed below. In order to facilitate the explanation of the verification logic, it is assumed that the stopover flight is from departure point A to destination B, with a stopover point C, and the route is ACB. In the PDD, there is a flight Leg divided into two segments. The first segment Leg is AC, and the number of passengers departing is expressed as PDD (AC). The second segment Leg is CB, and the number of passengers departing is also expressed as PDD (CB). In LDM, there are two segments associated with the first segment of PDD, expressed as LDM (AC) and LDM (AB). Similarly, in LDM, there are two segments associated with the second segment of PDD, expressed as PDD (CB) and LDM (AB), LDM (CB). The verification is also divided into two separate verifications, as shown below:
[0060] The first section AC: PDD(AC) and LDM(AC)+LDM(AB) (1)
[0061] Second paragraph CB: Are PDD(CB) equal to LDM(AB)+LDM(CB) (2)? If it is zero, it means that the number of passengers in LDM is exactly the same as the number of passengers in PDD. If it is not zero, there is a data error. The error in calculating the total number of passengers for each flight is
[0062] Passenger number error = PDD(AC).Total number of passengers + PDD(CB).Total number of passengers -
[0063] [LDM(AC).Total number of people + 2*LDM(AB).Total number of people + LDM(CB).Total number of people](3)
[0064] In one embodiment, necessary explanation is made for the calculation results of Table 4. Referring to Tables 1 and 2, only the flights of 20231024 have passenger errors. For cabin F, there are no passengers, so the error of F is naturally 0. For cabin C, PDD(TFU-AHJ)+PDD(AHJ-LXA)=5+5, LDM(TFU-AHJ)+2*LDM(TFU-LXA)+LDM(AHJ-LXA)=5+2*0+5=10, and its passenger error is 10-10=0. Similarly, the passenger error of cabin Y is 0 using the same calculation method, so the passenger error of this flight is 0+0=0. The passenger errors of the flights on the other two dates are zero.
[0065] Table 4: LDM and PDD passenger errors
[0066]
[0067] This indicates that the number of passengers in the three flights is exactly the same as that in the LDM data and the PDD data.
[0068] In one embodiment, during the flight guarantee process, there is a data difference between the PDD data source and the flight revenue settlement RA data source. The number of infants who do not occupy a seat is not counted in the PDD, but the number of infants is counted in the flight settlement RA data, because infant tickets have revenue, which is 10% of the adult ticket price. In order to facilitate alignment with RA, the number of infants in the LDM data is supplemented to the flight operation data source LDM / PDD to generate LDM / PDD integrated data, which is aligned with the RA data. In this way, the total number of people including infants is obtained for each flight segment. Its flight operation data source LDM / PDD is as follows:
[0069] Table 5: LDM / PDD passenger information
[0070] Serial number Flight number O D date model Configuration F C Y baby Total number of people 1 CA2535 TFU LX 20231010 319 8 / 119 0 1 79 0 80 2 CA2535 TFU AHJ 20231010 319 8 / 119 0 1 25 0 26 3 CA2535 AHJ LX 20231010 319 8 / 119 0 4 2 1 7 4 CA2535 TFU LX 20231021 319 8 / 119 0 0 15 0 15 5 CA2535 TFU AHJ 20231021 319 8 / 119 0 0 8 0 8 6 CA2535 AHJ LX 20231021 319 8 / 119 0 5 7 0 12 7 CA2535 TFU LX 20231024 319 8 / 119 0 0 14 0 14 8 CA2535 TFU AHJ 20231024 319 8 / 119 0 5 75 0 80 9 CA2535 AHJ LX 20231024 319 8 / 119 0 5 0 0 5
[0071] Next, the process proceeds to step S600. In step S600, the flight operation LDM / PDD integrated data is compared with the flight settlement RA data according to the flight information to calculate the passenger error.
[0072] See below for more information. Figure 3 Explain the data verification process of LDM / PDD and RA, Figure 3 For the data verification flow chart of LDM / PDD integration and RA, see Figure 3 The method for verifying LDM / PDD and RA data includes steps S610 to S650. A brief description is given below in conjunction with a specific embodiment:
[0073] In step S610, an OD is obtained from the RA in sequence;
[0074] In step S620, the number of first class F passengers in LDM / PDD is compared with that in RA;
[0075] In step S630, the number of business class C passengers in LDM / PDD is compared with that in RA;
[0076] In step S640, compare the LDM / PDD with the number of economy class Y passengers in the RA;
[0077] In step S650, LDM / PDD and RA passenger error are calculated.
[0078] In one embodiment, when verifying the data of the flight operation LDM / PDD integrated data and the flight settlement RA, for the same flight number and date, the following formulas (1), (2) and (3) are used to verify the data consistency, and the first class, business class and economy class and the total number of passengers are verified according to the following expressions respectively:
[0079] First segment LDM / PDD(AB) and RA(AB) (1)
[0080] Second Segment LDM / PDD(AC) and RA(AC) (2)
[0081] Are LDM / PDD(CB) and RA(CB) (3) equal for the third leg? If they are zero, it means that the number of passengers in RA is exactly the same as the number of passengers in LDM / PDD. If they are not zero, there is a data error. The error in calculating the total number of passengers for each flight is
[0082] Passenger number error = [LDM / PDD(AC).Total number of passengers + LDM / PDD(AB).Total number of passengers + LDM / PDD(CB).Total number of passengers]
[0083] -[RA(AC).Total number of people + RA(AB).Total number of people + RA(CB).Total number of people](4)
[0084] In one embodiment, the calculation results of LDM / PDD and RA passenger errors in Table 6 are necessary to explain. Referring to Tables 3 and 5, only the flights of 20231024 have passenger errors. For cabin F, since there are no passengers, the F error is naturally 0. For cabin C, LDM / PDD(TFU-AHJ)+LDM / PDD(TFU-LXA)+LDM / PDD(AHJ-LXA)=5+0+5=10, RA(TFU-AHJ)+RA(TFU-LXA)+RA(AHJ-LXA)=5+0+0. The passenger error of business class C calculated by formula (4) is 10-5=5. Similarly, the passenger error of cabin Y obtained by the same calculation method is -1, so the passenger error of this flight is 5-1=4. The passenger errors of the flights on the other two dates are zero.
[0085] Table 6: LDM / PDD and RA passenger errors
[0086]
[0087] The RA data and LDM / PDD data of the three flights are not exactly the same, and the passenger error value of flight CA535 on 20231024 is calculated and shown in Table 6.
[0088] Next, the process proceeds to step S700. In step S700, the passenger number matching rate, ie, the flight data credibility, is calculated based on the operation data LDM / PDD and the settled RA data.
[0089] In one embodiment, the mismatch rate of LDM / PDD and RA is calculated, and the mismatch rate of LDM / PDD and RA passengers is equal to the percentage of the absolute value of the error in the total number of passengers to the total number of RA passengers.
[0090] In one embodiment, necessary explanation is made for the calculation results of Table 7. Referring to Table 6, only the flight 20231024 has a passenger error. The passenger mismatch rate of this flight is the passenger number error 4 divided by the total number of passengers on this flight 14+76+5=95 (refer to Table 3), which is equal to 4.2%. The passenger errors of other flights are zero, and their passenger mismatch rates are also 0%.
[0091] Table 7: Mismatch rate between LDM and RA passengers
[0092] Serial number Flight number O D date Stopover Configuration Passenger mismatch rate 1 CA2535 TFU LX 20231010 AHJ 0 / 8 / 119 0 / 113=0% 2 CA2535 TFU LX 20231021 AHJ 0 / 8 / 119 0 / 35=0% 3 CA2535 TFU LX 20231024 AHJ 0 / 8 / 119 4 / 95=4.2%
[0093] Next, the process proceeds to step S800. In step S800, the market size and data credibility of each OD are calculated.
[0094] Calculate the mismatch rate of flight LDM / PDD and RA, that is, the flight passenger mismatch rate is equal to the percentage of the absolute value of the error in the total number of passengers and the total number of passengers in RA.
[0095] In one embodiment, referring to Table 3-7, the overall mismatch rate calculated by using passenger error and the total number of flight passengers is 4 / (109+110+24)=1.6%, and the overall matching rate is 98.4%, which is equivalent to the weighted credibility of the overall data being 98.4%; based on this statistical credibility, the size of all markets in three days is calculated to be equal to the total number of segmented ODs in RA, as shown in Table 3. For TFU-LXA, the OD size is 80+15+14=109, and similarly, TFU-AHJ is 110, and AHJ-LXA is 24, indicating that AHJ-LXA has less passenger traffic. For flight CA2535, the smallest model A319 is a suitable arrangement. The calculation results are shown in Table 8.
[0096] Table 8: OD market size over three days
[0097] Serial number O D OD Size 1 TFU LX 109 2 TFU AHJ 110 3 AHJ LX 24
[0098] It should be noted that 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. In certain circumstances, multitasking and parallel processing may be advantageous.
[0099] It should be understood that the various steps described in the method embodiments disclosed in the present application can 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 application is not limited in this respect.
[0100] and Figure 1 Corresponding to the method described above, the embodiment of the present application also provides a device for cross-validation of multi-source passenger data of stopover flights and a method for calculating market size, which is used to Figure 1 The specific implementation of the method is shown in the following diagram: Figure 4 As shown, the device includes: a flight acquisition unit, an LDM acquisition unit, a PDD acquisition unit, an RA acquisition unit, an operation data comparison unit, a settlement data verification unit, a passenger mismatch rate unit and an OD market calculation unit. Specifically including:
[0101] A flight acquisition unit, used to select a flight and acquire flight information, including but not limited to flight number, flight date, departure point, arrival point, aircraft number, and aircraft cabin configuration;
[0102] The LDM acquisition unit is used to extract the number of passengers in the flight segment from the LDM message after departure according to the flight information, which is called LDM data. The number of passengers in the flight segment is the number of first-class passengers (denoted as F), business-class passengers (denoted as C), economy-class passengers (denoted as Y), adults (denoted as A), children (denoted as C), infants (denoted as I), and the total number of passengers in each segment (Segment / Leg) of the flight;
[0103] The PDD acquisition unit is used to extract the passenger data on the flight (Leg) from the airline's post-departure PDD system according to the flight information, which is called PDD data. The PDD data includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats;
[0104] RA acquisition unit, used to count the flight segment data in each itinerary from the civil aviation settlement system RA according to the flight information, which is called RA data. The flight segment data includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each cabin (F / C / Y) of the aircraft, and the fare revenue of each cabin (F / C / Y);
[0105] An operation data comparison unit is used to establish a unique index of flight information in the data tables of the LDM data, PDD data and RA data, verify the consistency of the number of passengers (F / C / Y) of each leg Leg by comparing the flight operation data LDM data and PDD data according to the verification logic according to the flight information, calculate the mismatch rate, and generate LDM / PDD integrated data;
[0106] A settlement data verification unit, used to compare the flight operation LDM / PDD integrated data with the flight settlement RA data according to the flight information, and calculate the passenger error;
[0107] The passenger mismatch rate unit is used to calculate the passenger number mismatch rate based on the operation data LDM / PDD and the settled RA data;
[0108] The OD market calculation unit is used to calculate the size of each OD market and the credibility of flight passenger data based on flight settlement RA data.
[0109] The functions of each unit module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.
[0110] The market size is crucial for the design and adjustment of airline route networks. This patent only designs a multi-source data verification method for special flights, namely stopover flights, to determine the OD market size in this scenario under certain data credibility. There are three common types of general flights: a direct flight (commonly domestic), a stopover flight (domestic or international), and a transfer flight (common code-sharing). The calculation of the OD market size of each airline is nothing more than these three flight types. Only by accurately calculating the market size can we control market changes, and we cannot simply use the number of passengers on the flight as the basis for decision-making.
[0111] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.
[0112] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.
[0113] Any process or method described in the flow chart or otherwise described herein can be understood as a module, fragment or portion of a code representing one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.
[0114] The logic and / or steps described in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or used in combination with these instruction execution systems, devices or apparatuses.
[0115] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope recorded in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A method for cross-checking multi-source passenger data of a stopover flight Thru and calculating market size, characterized by: Select a flight and obtain flight information, including but not limited to flight number, flight date, departure point, arrival point, aircraft number, and aircraft cabin configuration; The number of passengers in each segment is extracted from the LDM message of the flight payload system after departure according to the flight information, which is called LDM data. The number of passengers in each segment is the number of passengers in the first class cabin (denoted as F), the number of passengers in the business class cabin (denoted as C), the number of passengers in the economy class cabin (denoted as Y), the number of adults (denoted as A), the number of children (denoted as C), the number of infants (denoted as I), and the total number of passengers in each segment (Segment / Leg) of the flight. Passenger data on the flight (Leg) extracted from the PDD system of the airline after the flight departs based on the flight information is called PDD data, which includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats; The flight segment data of each itinerary collected from the revenue settlement system RA based on the flight information is called RA data, which includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each cabin (F / C / Y) of the aircraft, and the fare revenue of each cabin (F / C / Y); Establish a unique index of flight information in the data tables of the LDM data, PDD data and RA data, verify the consistency of the number of passengers (F / C / Y) of each leg Leg by checking the flight operation data LDM data and PDD data according to the flight information, calculate the mismatch rate, and generate LDM / PDD data; According to the flight information, the flight operation LDM / PDD data is compared with the flight settlement RA data to calculate the passenger error; Calculate the passenger mismatch rate based on the operational data LDM / PDD and the settled RA data; Based on the flight settlement RA data, the market size of each OD and the credibility of flight passenger data are calculated.
2. The method according to claim 1, wherein: The stopover flight (Thru) is a route with the same flight number and a stopover terminal in the middle. The leg is a single flight segment of a direct flight, and the segment is a flight segment with a stopover point, which is composed of several legs.
3. The method according to claim 1, wherein: The unique index is a joint index of flight number, flight date, departure place, and arrival place, which represents the uniqueness of the flight.
4. The method according to claim 1, wherein: The verification logic for comparing the LDM data with the PDD data is the difference between the number of departing passengers of the flight Leg in the PDD and the sum of the number of passengers of all flight segments associated with the flight Leg in the LDM data. The passenger error calculation method is the sum of the differences, and the mismatch rate is further calculated. The LDM infant number is used to complete and generate the LDM / PDD data.
5. The method according to claim 4, wherein: The LDM / PDD data is compared with the RA data. The verification logic is to compare the number of passengers in each class F / C / Y / in each flight segment in the LDM / PDD with the number of passengers in the corresponding flight segment in the RA data. The passenger difference is calculated as the difference between the total number of passengers in the LDM / PDD and the total number of passengers in the RA data.
6. The method according to claim 5, wherein: The mismatch rate between the LDM / PDD data and the RA data is the ratio of passenger errors to the total number of RA passengers.
7. The method according to claim 1, wherein: The OD market size is the number of passengers from the real origin (O) to the real destination (D). After cross-checking of multi-source data, the OD market size and data weighted credibility are calculated according to RA records.
8. A device for cross-checking multi-source passenger data of a stopover flight Thru and calculating market size, comprising: A flight acquisition unit, used to select a flight and acquire flight information, including but not limited to flight number, flight date, departure point, arrival point, aircraft number, and aircraft cabin configuration; The LDM acquisition unit is used to extract the number of passengers in the flight segment from the LDM message after departure according to the flight information, which is called LDM data. The number of passengers in the flight segment is the number of first class F passengers, business class C passengers, economy class Y passengers, adults, children, infants, and the total number of passengers in each segment (Segment / Leg) of the flight; The PDD acquisition unit is used to extract the passenger data on the flight (Leg) from the PDD system of the airline after the flight departs according to the flight information, which is called PDD data. The PDD data includes but is not limited to flight information, the number of passengers in each class (F / C / Y) and the total number of passengers occupying seats; RA acquisition unit, used to calculate the flight segment data in each itinerary from the revenue settlement system RA according to the flight information, which is called RA data. The RA data includes but is not limited to flight information, the number of passengers in the market sub-class, the number of passengers in each cabin (F / C / Y) of the aircraft, and the fare revenue of each cabin (F / C / Y); An operation data comparison unit is used to establish a unique index of flight information in the data tables of the LDM data, PDD data and RA data, verify the consistency of the number of passengers (F / C / Y) of each leg Leg by comparing the flight operation data LDM data and PDD data according to the flight information according to the verification logic, calculate the mismatch rate, and generate LDM / PDD data; A settlement data verification unit, for comparing the flight operation LDM / PDD data with the flight settlement RA data according to the flight information, and calculating the passenger error; The passenger mismatch rate unit is used to calculate the passenger number mismatch rate based on the operation data LDM / PDD and the settled RA data; the OD market calculation unit is used to calculate the size of each OD market and the credibility of flight passenger data based on the flight settlement RA data.
