CN116681572A

CN116681572A - Flight plan integration method and device

Info

Publication number: CN116681572A
Application number: CN202310721787.XA
Authority: CN
Inventors: 赵禹; 赵东洲; 牛品菽; 张雪彬; 张珊
Original assignee: China Travelsky Technology Co Ltd
Current assignee: China Travelsky Technology Co Ltd
Priority date: 2023-06-16
Filing date: 2023-06-16
Publication date: 2023-09-01

Abstract

The application discloses a flight schedule integration method and device, which are used for grouping flight schedules to be validated respectively corresponding to flight numbers according to flight attributes, wherein the flight attributes are the same as one group, and an attribute group of each flight number is obtained. And then, the first two data in the attribute group are used as data to be combined, the data are combined according to a preset combining rule, if the combination is successful, the data after the combination is continued to be integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date are integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined. Therefore, the method integrates the data of the flight plans to be validated corresponding to each flight number when the flight plans are changed, reduces the flight plans of the single flight number, has simpler and more convenient changing operation, and reduces the changing validation time of the system, thereby improving the issuing efficiency of the flight plans.

Description

Flight plan integration method and device

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a flight plan integration method and apparatus.

Background

The flight schedule is composed of flight number, flight date range, period and route, departure arrival time, machine type and other flight information, and is a data record of the scheduled and managed flight of the flight company.

Flight plan change is one of the most common services in civil aviation, and usually requires flight management personnel of an airline company to operate in an aviation management system (English: passenger Service System, PSS), wherein the flight management personnel can manually adjust the flight plan on a front end page of the PSS system, or perform flight plan change through messages such as ASM/source specific multicast SSM messages, custom messages and the like of any source of international air transport association (English: international Air Transport Association, IATA) standards, and perform flight plan release after the change takes effect.

However, when the flight plan is changed, a plurality of flight plans of the same flight number may be changed at the same time, and the more the number of flight plans of a single flight number is, the more complicated the changing operation is, the longer the change effective time required by the system is, thereby affecting the distribution efficiency of the flight plans.

Disclosure of Invention

In view of the above, the embodiment of the application provides a flight plan integration method and device.

In a first aspect, an embodiment of the present application provides a flight plan integration method, where the method includes:

grouping the flight plans to be validated corresponding to each flight number according to the flight attributes, wherein the flight attributes are the same as one group, and an attribute group of each flight number is obtained;

the first two data in the attribute group are used as data to be combined, and are combined according to a preset combining rule;

if the combination is successful, the data after the combination is successful are continuously integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date is integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined.

In a second aspect, an embodiment of the present application provides a flight plan integration apparatus, including:

the grouping module is used for grouping the flight plans to be validated corresponding to each flight number according to the flight attributes, wherein the flight attributes are the same as one group, and an attribute group of each flight number is obtained;

the judging module is used for taking the first two data in the attribute group as data to be combined and combining the first two data according to a preset combining rule;

And the integration module is used for continuously integrating the successfully integrated data with the next data in the attribute group if the combination is successful, and integrating the data with large starting date with the next data in the attribute group if the combination is unsuccessful until the integration of each flight number is completed, wherein the starting date is the minimum date of the union of the date ranges in the data to be combined.

In a third aspect, an embodiment of the present application provides a flight plan integration apparatus, including:

a memory for storing a computer program;

a processor, configured to execute the computer program, so that the device executes the flight plan integration method described in the foregoing first aspect.

In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where a computer program is stored, and when the computer program is executed, a device running the computer program implements the flight plan integration method described in the foregoing first aspect.

Compared with the prior art, the embodiment of the application has the following beneficial effects:

the embodiment of the application provides a flight plan integration method and device, which are characterized in that firstly, flight plans to be validated, which correspond to each flight number respectively, are grouped according to flight attributes, the flight attributes are the same as one group, and an attribute group of each flight number is obtained. And then, the first two data in the attribute group are used as data to be combined, the data are combined according to a preset combining rule, if the combination is successful, the data after the combination is continued to be integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date are integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined. Therefore, by means of the method, when the flight schedule is changed, the data integration is carried out on the flight schedule to be validated corresponding to each flight number, the flight schedule of a single flight number is reduced, the change operation is simpler and more convenient, the change validation time required by the system is reduced, and accordingly the release efficiency of the flight schedule is improved.

Drawings

In order to more clearly illustrate this embodiment or the technical solutions of the prior art, the drawings that are required for the description of the embodiment or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

The above and other features, advantages and aspects of embodiments of the present application will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a flow chart of a flight plan integration method according to an embodiment of the present application;

FIG. 2 is a flowchart of another method for integrating flight plans according to an embodiment of the application;

FIG. 3 is a flowchart of a flight rule integration method according to an embodiment of the present application;

FIG. 4 is a flowchart of another method for integrating flight plans according to an embodiment of the application;

FIG. 5 is a timing chart of a flight schedule integration method according to an embodiment of the present application;

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a flight plan integrating apparatus according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While the application is susceptible of embodiment in the drawings, it is to be understood that the application may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided to provide a more thorough and complete understanding of the application. It should be understood that the drawings and embodiments of the application are for illustration purposes only and are not intended to limit the scope of the present application.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like herein are merely used for distinguishing between different devices, modules, or units and not for limiting the order or interdependence of the functions performed by such devices, modules, or units.

Currently, airline flight management typically makes flight schedule changes, validations, and releases in the PSS flight management system. The flight manager can manually adjust the flight plan through the front-end page of the PSS system, or carry out flight plan change through IATA standard ASM/SSM messages, custom messages and other messages, and carry out flight plan release after the change takes effect.

Based on the above, in order to solve the above problems, the embodiments of the present application provide a flight plan integration method and apparatus, which integrate flight plans corresponding to flight numbers, reduce the number of flight plans, and improve the distribution efficiency of flight plans.

The following describes in detail, by way of embodiments, a specific implementation manner of a flight plan integration method and apparatus according to an embodiment of the present application with reference to the accompanying drawings.

Only basic information such as flight number, date range, route, departure arrival time, machine type and the like is contained in the flight plan changing message or manual adjustment request, and the flight plan is further matched with flight rules to supplement other additional information in the changing process, for example, all flight attributes such as cabin layout, on-board service and the like are required to be assigned through matching with the flight rules, so that the flight plan is perfected. Wherein deleting the flight schedule does not require matching the flight rules. After the flight schedule is changed, a flight schedule to be validated is generated, and a flight manager can select the flight schedule to be validated to take effect in batches. After validation is completed, the flight plan may be published.

The flight plan change mainly comprises a newly built flight plan, a modified flight plan and a deleted flight plan, and the main scene of the flight plan change and the flight plan validation scene are respectively accepted below.

A new flight plan refers to a flight plan that is newly created in the system and that has no flight day intersections in the existing flight plans. In one possible implementation, the newly built flight plan matches tens of flight rules one by one, and each time a flight rule is matched, the flight plan is segmented according to the valid date range and the period of the matched flight rule. As an example, the date in the flight plan message ranges from 2022, 12, 20 (monday) to 2022, 12, 22 (thursday), and the period 24 matches the e-ticket identification ET rules. If the ET rule matched contains two records, rule a has an effective period of 2022, 12, 20 (tuesday) to 2022, 12, 20 (tuesday), and a period of shift 2, rule B has an effective period of 2022, 12, 22 (tuesday), to 2022, 12, 22 (tuesday), and shift 4, then after matching the ET rule with the newly created flight plan, the newly created flight plan is split into two flight plans, with a plan 1 date ranging from 2022, 12, 20 (tuesday), to 2022, 12, 20 (tuesday), shift 2, and a plan 2 date ranging from 2022, 12, 22 (tuesday), to 2022, 12, 22 (tuesday), and shift 4. The new or changed current flight plan can be matched with dozens of flight rules, and each time one rule is matched, the flight plan can be split according to the corresponding matching result. Wherein, the type of the matching rule is not specified in the flight schedule change message, and the matching flight rule is basically fixed.

Modifying a flight plan refers to changing an existing flight plan in the system. Modifying a flight schedule generally only changes a message or a flight day in a request, and if the existing flight schedule and the date range in the change message are different, the existing flight schedule needs to be split first, and then the change and the flight rule matching are performed after the split is consistent with the change message. For example, the date in the change message ranges from 2022, 12, 20 (tuesday) to 2022, 12, 22 (tuesday), and the period 24, and the existing flight schedule date in the system ranges from 2022, 12, 20 (tuesday) to 2022, 12, 22 (tuesday), and the period 234. In the changing process, firstly, according to whether a flight intersection exists, the existing flight schedule is split into two, wherein the date range of the schedule 1 is 2022, 12, month and 20 (Tuesday) to 2022, 12, month and 22 (Tuesday), the period 24, and the date range of the schedule 2 is 2022, 12, month and 21 (Tuesday) to 2022, 12, month and 21 (Tuesday), and the period 3; then, the flight schedule changing messages are matched with the flight rules one by one, and a flight schedule to be validated is generated.

Deleting a flight plan refers to deleting an existing flight plan in the system. In the changing process, the existing flight plan is split first, then the rules are not matched, and the flight plan to be validated is generated.

The flight schedule to be validated is generated after the flight schedule is changed, a flight manager can select the flight schedule to be validated, the system groups the flight schedule to be validated into batches according to a certain rule, flight validation batches are generated, validation is carried out batch by batch, and the corresponding flight schedule release is carried out after each batch validation is completed.

Referring to fig. 1, the flow chart of a flight plan integration method provided by the embodiment of the present application, with reference to fig. 1, may specifically include:

s101: and grouping the flight plans to be validated corresponding to the flight numbers respectively according to the flight attributes, wherein the flight attributes are the same as one group, and the attribute group of each flight number is obtained.

After the flight schedule is changed, a flight schedule to be validated is generated, the flight schedule to be validated is divided into a plurality of validation batches according to a certain rule, then the flight schedule is validated according to the validation batches, and after the validation is completed, the flight schedule can be issued.

Because a plurality of flight plans of a flight number are often changed at the same time, for example, a plurality of flight plan change messages or a plurality of manual adjustments are generated, repeated flight plans may occur, and for scenes in which different date ranges of the same flight number are changed at the same time, the same flight number is validated in the same batch in the process of generating the effect, and the flight plans can be integrated in the batch before the validation.

In addition, when the flight is changed, there is a case where the flight schedule information is unchanged before and after the change, and in this case, the system does not generate a flight schedule to be validated, and does not change the existing flight schedule.

In one possible implementation manner, the user can manually change the flight plan on the front-end page, or the user processes the flight plan change message on the front-end page, then the flight plan is matched with the flight rule, more flight information of the flight plan is changed, when the flight plan is changed, the flight plan to be validated is not generated, the flight plan to be validated is generated under other conditions, then the user selects the flight plan to be validated to validate, and the flight plan to be validated generates validation batches, and validates the flight plan by batch.

The flights to be validated of the same flight number are arranged in the same batch, the flights in the same batch are grouped according to the flight number, the flights to be validated of the same flight number are arranged in a group, and data integration is carried out on each flight number group.

Firstly deleting the flight plans to be validated, if the number of the rest flight plans to be validated in the flight number group is greater than one, integrating the data of the flight number group, grouping the flight plans to be validated in each flight number group according to the flight attribute, wherein the flight attribute is the same as one group, and obtaining the attribute group of each flight number.

The flight attributes include flight basic information, attribute information of a flight level, section basic information, section attribute information, section basic information, and code sharing information. The flight basic information comprises an airline company, a flight number and a flight suffix; the attribute information of the flight level comprises an electronic ticket identifier, a national international identifier, a night flight and a T5 item; the basic information of the navigation section comprises a departure station, an arrival station, departure time of the navigation section, departure date deviation of the navigation section, arrival time of the navigation section, arrival date deviation of the navigation section, cabin position layout PRBD of the navigation section, sales layout and model type; the aviation section attribute information comprises a T3 item, a flight status telegraph address table number STAB, a meal, a seat protection identifier ASR and on-board service; the basic information of the leg comprises a starting leg of the leg and an arriving leg of the leg; the navigation segment attribute information comprises a T4 item, a traffic restriction code and an automatic post-compensation confirmation; the code sharing information comprises a partner side airline company, a partner side flight number, a partner side flight suffix, a partner side sharing section, a partner side code sharing type, a cabin corresponding table number and a virtual flight identification. The flight number is composed of an airline company, a flight number and a flight suffix and is used for uniquely identifying one flight. For example, CA110A, etc. The date range is composed of a start date and an end date, and the end date is equal to or greater than the start date. An airline refers to an air traffic line where flights perform flights, including take-off airports, arrival airports, and stopped airports.

S102: and taking the first two data in the attribute group as data to be combined, and combining according to a preset combining rule.

In one possible implementation manner, all attribute groups are traversed, the data in each attribute group are combined and integrated, if the group contains only 1 piece of data, the group integration is completed, if the data in the group is greater than 1, the data integration is continued, and the data can be ordered from small to large according to the starting date in the date range. And then, taking the first two data in the attribute group as data to be combined, and combining according to a preset combining rule.

The preset merging rule comprises the steps of obtaining a union set of date ranges in data to be merged, wherein the union set comprises a maximum date and a minimum date, if the difference value between the maximum date and the minimum date of the data to be merged is less than or equal to seven, the data can be merged into data of one date segment, the union set of the minimum date, the maximum date and the shift of the data to be merged is used as merging success data, namely the minimum date is used as a starting date, the maximum date is used as an ending date, and the union set of the shift of the two data to be merged is used as merging success data. As an example, the data to be combined is data a and data B, the date of start of data a is 20230517, the date of end is 20230517, the period is 3, the date of start of data B is 20230518, the date of end is 20230518, the period is 4, the two date ranges are combined, the maximum date is 20230518, the minimum date is 20230517, the difference between the two is less than 7, and the two are combined, the combined start date is 20230517, the end date is 20230518, and the period is 34.

If the shift of the data to be combined is the same and only has one digit, the start date of one data in the data to be combined is a first start date B1, the end date is a first end date E1, the start date of the other data in the data to be combined is a second start date B2, the end date is a second end date E2, the difference between the second start date B2 and the first end date E1 or the difference between the first start date B1 and the second end date E2 is seven, the minimum value in the first start date and the second start date is taken as the start date of the data which is successfully combined, and the maximum value of the first end date and the second end date is taken as the end date of the data which is successfully combined. As an example, data a has a start date of 20230517, an end date of 20230524, a shift of 3, a start date of 20230531, an end date of 20230607, a shift of 3, the shift of both being identical and having only one digit, and data B has a start date of less than data a and an end date of 7, and the two are combined, the combined start date is 20230517, and the end date is 20230607, and the shift is 3.

If the shift periods of the data to be combined are the same, and the difference between the maximum date and the minimum date after the data to be combined are obtained by combining is greater than seven, the shift period of the difference between the second starting date B2 and the first ending date E1 or the shift period of the difference between the first starting date B1 and the second ending date E2 is different from the shift period of the data to be combined, the minimum value in the first starting date and the second starting date is used as the starting date of the data which is successfully combined, and the maximum value in the first ending date and the second ending date is used as the ending date of the data which is successfully combined. As an example, data a has a start date of 20230517, an end date of 20230525, a shift of 34, data B has a start date of 20230531, an end date of 20230608, a shift of 34, the shift of 34, and the like, and the date ranges of both are the same, the maximum date 20230608 minus the minimum date 20230517 after union is greater than 7, data B has a start date minus the end date of data a of 20230526-20230530, a shift of 12567, and the combined start date of 20230517, the end date of 20230608, and the shift of 34 are combined, unlike the shifts of data a and data B.

Wherein, the period refers to the week in which the flight is executing within a week, represented by numerals 1 to 7, 1 represents monday, 2 represents tuesday, and so on, and 7 represents sunday. For example, the shift 24 represents the two days of tuesday and tuesday of a flight.

S103: if the combination is successful, the data after the combination is successful is continuously integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date is integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined.

If the two pieces of data to be combined are successfully combined, the combined data are integrated with the next piece of data in the attribute group, and if the two pieces of data to be combined are not successfully combined, the data with larger starting date in the data to be combined are integrated with the next piece of data in the attribute group until all the flight number groups are traversed.

In addition, the integrated flight schedule to be validated can be validated, and the flight schedule can be issued.

The above method for integrating flight plans provided by the embodiment of the application firstly groups the flight plans to be validated corresponding to each flight number according to the flight attribute, wherein the flight attributes are the same as one group, and the attribute group of each flight number is obtained. And then, the first two data in the attribute group are used as data to be combined, the data are combined according to a preset combining rule, if the combination is successful, the data after the combination is continued to be integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date are integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined. Therefore, by means of the method, when the flight schedule is changed, the data integration is carried out on the flight schedule to be validated corresponding to each flight number, the flight schedule of a single flight number is reduced, the change operation is simpler and more convenient, the change validation time required by the system is reduced, and accordingly the release efficiency of the flight schedule is improved.

Referring to fig. 2, the flow chart of another flight schedule integration method according to the embodiment of the present application, with reference to fig. 2, may specifically include:

s201: the flight schedule to be validated generates a validation batch.

Taking effect according to the effective batches, wherein the flight plans to be taken effect of the same flight number are the same batch, the flight plans in the same effective batch are grouped according to the flight number, and the flight plans to be taken effect of the same flight number are a group.

S202: and traversing each flight number group to integrate data.

S203: and deleting the flight schedule to be validated, which is cancelled by the flights in the flight number group.

S204: the number of data in the flight number group is greater than 1.

When the number of data in the flight number group is not greater than 1, the process can jump to S222, which means that only one flight plan corresponding to the flight number is provided, and data integration is not required, so that data integration can be performed on the next flight number group. Wherein one piece of data within the flight number group may be information contained in the flight plan.

S205: traversing the flight number group data, and grouping according to the flight attribute.

S206: traversing the attribute groups of all flight numbers.

S207: the number of data pieces of the attribute group is greater than 1.

When the number of data pieces in the attribute group is less than 1, the process goes to S218.

S208: the data within the property group is ordered according to the date range.

The data is ordered from small to large by the start date in the date range.

S209: the first two data in the attribute group are used as data to be combined.

S210: and merging according to the first condition of the preset merging rule.

The first condition of the preset merging rule is to take the union of date ranges in the data to be merged, wherein the union comprises a maximum date and a minimum date, if the difference value between the maximum date and the minimum date of the data to be merged is less than or equal to seven, the data can be merged into one date segment, the union of the minimum date, the maximum date and the shift of the data to be merged is taken as successful merging data, namely the minimum date is taken as a starting date, the maximum date is taken as an ending date, and the union of the shift of the two data to be merged is taken as successful merging data. The merging successfully jumps to S213, and the merging does not successfully jump to S211.

S211: and merging according to the second condition of the preset merging rule.

The second condition of the preset merging rule is that if the shift of the data to be merged is the same and only has one digit, the start date of one data in the data to be merged is a first start date B1, the end date is a first end date E1, the start date of the other data in the data to be merged is a second start date B2, the end date is a second end date E2, the difference between the second start date B2 and the first end date E1 or the difference between the first start date B1 and the second end date E2 is seven, the minimum value of the first start date and the second start date is taken as the start date of the data which is successfully merged, and the maximum value of the first end date and the second end date is taken as the end date of the data which is successfully merged. The merging successfully jumps to S213, and the merging does not successfully jump to S212.

S212: and merging according to a third condition of a preset merging rule.

The third condition of the preset merging rule is that if the shift periods of the data to be merged are the same, the difference between the maximum date and the minimum date after the data to be merged are merged is greater than seven, the shift period of the difference between the second starting date B2 and the first ending date E1 or the shift period of the difference between the first starting date B1 and the second ending date E2 is different from the shift period of the data to be merged, the minimum value in the first starting date and the second starting date is taken as the starting date of the data which is successfully merged, and the maximum value in the first ending date and the second ending date is taken as the ending date of the data which is successfully merged.

S213: and if the merging is successful, whether the next piece of data exists in the attribute group.

The next piece of data is not included in the attribute group and the process goes to S217.

S214: and continuously integrating the data after successful combination with the next piece of data.

S215: merging is unsuccessful, and whether the next piece of data exists in the attribute group.

S216: and (5) if the merging is unsuccessful, selecting the data with large starting date from the data to be merged and continuously integrating the data with the next piece of data.

S217: whether the next property group is contained.

S218: the next property group is integrated.

S219: until all the property groups have been traversed.

S220: until all the flight number groups are traversed.

S221: and validating and issuing the integrated flight schedule to be validated.

S222: whether the next flight number group is included.

When the next flight number group is included in the validation lot, the process may jump to S203. When the next flight number group is not included, the process may jump to S220.

In addition, the booking host system in PSS has a limit to the number of flight plans for a single flight number, for example, the number of flight plans for a single flight number cannot exceed 240, and the number of flight plans exceeding the limit cannot be issued to the booking host system. Therefore, as few flight plans as possible are required.

In the change of the flight plan, the flight rule is matched, the date range is segmented according to the matched flight rule, and the smaller the data of the flight rule is, the fewer the situation that the date range is needed to be segmented in the matching process is. Therefore, when the flight rules are changed, the situation that the two flight rules are changed identically due to multiple changes can occur, the flight rule data can be integrated, and the situation that date range segmentation is needed in the matching process can be reduced.

Wherein, the flight rule is to add additional information to the specification to be followed on the flight plan, and the flight rule is composed of a rule name, a rule level, a rule factor value of the corresponding rule level, a rule value, and a rule valid date range (start date+end date+shift). The rule hierarchy is present to uniquely determine the rule value that should be matched, and when there are a plurality of rules that satisfy the same condition, the matching rule takes the rule with the highest hierarchy. The non-repeating rule factor composition hierarchy may also be arbitrarily selected, and then the priority relationships between the rule hierarchies are specified. After establishing a rule hierarchy and designating the priority relation of the hierarchy, a rule can be newly established on the hierarchy.

At the same time, only the rule factors included in the hierarchy can be assigned and must be assigned, and the factors not included cannot be assigned. The rule condition is an applicable condition of the rule value, and when the data satisfies the rule condition, the rule value of the rule can be applied. Whereas the rule condition is made up of several rule factors. The rule factor may be some attribute value of the flight, such as the flight number, master Office, etc. The rule factors are mutually independent. The rule hierarchy is made up of a combination of several rule factors. The rule name is a class of flight rules, and the class of flight rules in the current system includes a terminal building, an on-board service, automatic candidate validation, STAB, ASR, ET, PRBD, T3, T4, T5, a flight deck switch, a route type, a sales layout offload, a pilot offload, a crew offload, a security agent offload, a mission offload, a layout (a cabin correspondence), a traffic restriction code, a safe flight, a SMAP, a free sales, a package seat, an entity inner generation, and the like.

In one possible implementation, the user may change the flight rules on the front-end page, including creating a new flight rule, modifying a flight rule, or deleting a flight rule. And then storing the changed flight rule, integrating the flight rule data of the type, and independently storing the integrated flight rule data. As an example, when the user changes the flight rule on the front-end page, the background system stores the changed flight rule and stores the flight rule in the flight rule data table, returns to the front-end page to display that the change is successful, and triggers the background system to integrate the flight rule data.

Referring to fig. 3, the flow chart of a flight rule integration method provided by the embodiment of the present application, with reference to fig. 3, may specifically include:

s301: traversing the data in the flight rules to be integrated, and grouping the data in the flight rules according to the rule attribute.

In one possible implementation, the flight rule attribute groups may be obtained by grouping three items of data, which are identical in content, according to a rule hierarchy, a rule factor corresponding to the rule hierarchy, and a rule value. As an example, one flight rule data includes three attributes, the rule data of one e-ticket identifier is that the rule hierarchy is a flight number, the rule factor is CA110, and the rule value is Y. The three attributes are equally divided into a group in the electronic ticket identification rule.

S302: and traversing all the flight rule attribute groups to integrate data.

S303: the number of data pieces of the flight rule attribute group is greater than 1.

When the number of data pieces in the flight rule attribute group is less than 1, the process goes to S313.

S304: and ordering the data in the flight rule attribute group according to the date range.

The data is ordered from small to large by the start date in the date range.

S305: traversing the sequenced flight rule attribute group, and taking the first two data in the flight rule attribute group as data to be combined.

S306: and merging according to the first condition of the preset merging rule.

The data to be combined is combined according to the preset combining rule, and the first case of the preset combining rule is the same as the preset combining rule in S210, and will not be described herein. The combination successfully jumps to S309, and the combination does not successfully jump to S307.

S307: and merging according to the second condition of the preset merging rule.

The second case of the preset merge rule is the same as the preset merge rule in S211, and will not be described here again. The merging successfully jumps to S309, and the merging unsuccessfully jumps to S308.

S308: and merging according to a third condition of a preset merging rule.

The third case of the preset merge rule is the same as the preset merge rule in S212, and will not be described here.

S309: and if the combination is successful, whether the next piece of data exists in the flight rule attribute group.

The next piece of data is not included in the flight rule attribute group and the process goes to S313.

S310: and continuously integrating the data after successful combination with the next piece of data.

S311: and if the merging is unsuccessful, whether the next piece of data exists in the flight rule attribute group.

S312: and (5) if the merging is unsuccessful, selecting the data with large starting date from the data to be merged and continuously integrating the data with the next piece of data.

S313: and integrating the next flight rule attribute group until all the flight rule attribute groups are traversed.

And storing the integrated data into a flight rule integrated data table to replace the original flight rule data, and subsequently using the newly stored flight rule integrated data table to carry out flight rule matching.

Therefore, the data in the flight rules are integrated when the flight rules are changed by the method, the flight rule data are reduced, the number of the flight plans is reduced as the flight plans need to be subjected to date range segmentation in the flight rule matching process, the number of the flight plans is controlled to be not more than the limit of the number of the systems, and the management efficiency of the flights is further improved.

In one embodiment, the flight management software initiates an expiration data delete every early morning, issues a data maintenance job such as a flight full flight schedule file, and the flight schedule is not changed or validated during the data maintenance. The flight plans of all the flight numbers are integrated in the data maintenance period, so that the number of the flight plans of the single flight number can be further reduced, the number of the flight plans is controlled to not exceed the number limit of the system, and the management efficiency of flights is improved.

In one possible implementation, published flight schedule integration is triggered during daily timing data maintenance, with data integration for each flight number until the flight schedule integration for all flight numbers is complete.

Referring to fig. 4, the flowchart of another flight schedule integration method according to the embodiment of the present application is shown in fig. 4, and may specifically include:

s401: traversing the published flight plans, and grouping the published flight plans according to the flight attributes.

And grouping the flight plans respectively corresponding to the flight numbers according to the flight attributes, wherein the flight attributes are the same as one group, so that the attribute group of each flight number can be obtained.

The flight attributes include flight basic information, attribute information of a flight level, section basic information, section attribute information, section basic information, and code sharing information. The flight basic information comprises an airline company, a flight number and a flight suffix; the attribute information of the flight level comprises an electronic ticket identifier, a national international identifier, a night flight and a T5 item; the basic information of the navigation section comprises a departure station, an arrival station, departure time of the navigation section, departure date deviation of the navigation section, arrival time of the navigation section, arrival date deviation of the navigation section, PRBD of the navigation section, sales layout and model; the aviation section attribute information comprises T3 items, STAB, meal, ASR and on-board service; the basic information of the leg comprises a starting leg of the leg and an arriving leg of the leg; the navigation segment attribute information comprises a T4 item, a traffic restriction code and an automatic post-compensation confirmation; the code sharing information comprises a partner side airline company, a partner side flight number, a partner side flight suffix, a partner side sharing section, a partner side code sharing type, a cabin corresponding table number and a virtual flight identification.

S402: and traversing all attribute groups to integrate data.

S403: the number of data pieces of the attribute group is greater than 1.

When the number of data pieces in the attribute group is less than 1, the process goes to S413.

S404: the data within the property group is ordered according to the date range.

The data is ordered from small to large by the start date in the date range.

S405: traversing the sorted attribute groups, and taking the first two data in the attribute groups as data to be combined.

S406: and merging according to the first condition of the preset merging rule.

The data to be combined is combined according to the preset combining rule, and the first case of the preset combining rule is the same as the preset combining rule in S210, and will not be described herein. The merging successfully jumps to S409, and the merging does not successfully jump to S407.

S407: and merging according to the second condition of the preset merging rule.

The second case of the preset merge rule is the same as the preset merge rule in S211, and will not be described here again. The merging successfully jumps to S409, and the merging does not successfully jump to S408.

S408: and merging according to a third condition of a preset merging rule.

S409: and if the merging is successful, whether the next piece of data exists in the attribute group.

The next piece of data is not included in the attribute group and the process goes to S413.

S410: and continuously integrating the data after successful combination with the next piece of data.

S411: merging is unsuccessful, and whether the next piece of data exists in the attribute group.

S412: and (5) if the merging is unsuccessful, selecting the data with large starting date from the data to be merged and continuously integrating the data with the next piece of data.

S413: and integrating the next attribute group until all the flight number groups are traversed.

In one possible implementation, the integrated flight data is updated into the database's flight schedule data table for replacing the original flight schedule data for that flight number.

Therefore, the method integrates the flight plans of all the flight numbers in the timing data maintenance period, and reduces the number of the flight plans, so that the problem that the flight plans cannot be issued to a seat booking system due to the fact that the number of the flight plans of a single flight number exceeds the system limit is avoided, and further the flight management efficiency is improved.

In one embodiment, all flight rules may be queried, created, modified, and deleted by the flight rule management component, while the flight rule data may be integrated. The method comprises the steps of inquiring a flight plan through a flight plan management component, processing a message change request, processing a manual adjustment flight plan request, matching flight rules, generating a flight plan to be validated and validating the flight plan. The flight plan data of all the flight numbers can also be integrated by the flight plan integration component.

Referring to fig. 5, the timing chart of a flight schedule integration method according to an embodiment of the present application, with reference to fig. 5, may specifically include:

s501: the flight manager 510 changes the flight rules on the front page.

S502: the flight rules management component 520 maintains the changed flight rules.

S503: the flight rules management component 520 feeds back to the front page of the flight manager 510 that the change was successful.

S504: the flight rules management component 520 integrates flight rules.

S505: the flight manager 510 changes the flight plan on the front page.

The flight personnel manually changes the flight plan at the front-end page or processes the flight plan change message at the front-end page.

S506: the flight plan management component 530 matches flight rules according to the flight rule management component 520.

S507: the flight schedule management component 530 returns the to-be-validated flight schedule to the front page of the flight manager 510.

S508: the flight manager 510 selects a flight schedule to take effect.

S509: the flight plan management component 530 generates an effective lot.

S510: the flight plan management component 530 returns the effective lot to the front page of the flight manager 510.

S511: the flight schedule management component 530 performs data integration within the lot, and performs validation post-integration.

S512: the flight plan integration component 540 triggers data integration.

The flight plan integration component triggers data integration during data maintenance at daily times.

S513: the flight plan integration component 540 performs data integration on the flight plan for each flight number.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The names of messages or information interacted between the various components in embodiments of the present application are for illustrative purposes only and are not intended to limit the scope of such messages or information.

Although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous.

It should be understood that the various steps recited in the method embodiments of the present application may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the application is not limited in this respect.

In addition, computer program code for carrying out operations of the present application may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The application further provides a corresponding device and electronic equipment based on the specific implementation modes of the flight plan integration method provided by the embodiment of the application.

Referring now to fig. 6, a schematic diagram of an electronic device (e.g., server in fig. 1) 600 suitable for use in implementing embodiments of the present application is shown. The electronic device shown in fig. 6 is only an example and should not be construed as limiting the functionality and scope of use of the embodiments of the application.

As shown in fig. 6, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 606 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 606 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a non-transitory computer readable storage medium, the computer program comprising program code for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 606, or from ROM 602. The above-described functions defined in the method of the embodiment of the present application are performed when the computer program is executed by the processing means 601.

The apparatus provided by the embodiment of the present application will be described in terms of functional modularization.

Referring to fig. 7, which is a schematic structural diagram of a flight schedule integrating apparatus 700 according to an embodiment of the present application, the apparatus 700 may include:

the grouping module 701 is configured to group to-be-validated flight plans corresponding to each flight number according to a flight attribute, where the flight attributes are the same as one group, and obtain an attribute group of each flight number;

the judging module 702 is configured to combine the first two data in the attribute group according to a preset combining rule, wherein the first two data are used as data to be combined;

And the integrating module 703 is configured to integrate the successfully integrated data with the next data in the attribute group if the merging is successful, and integrate the data with a large start date with the next data in the attribute group if the merging is unsuccessful until the integration of each flight number is completed, where the start date is the minimum date of the union of the date ranges in the data to be merged.

In the embodiment of the present application, by matching the grouping module 701, the judging module 702 and the integrating module 703, the to-be-validated flight plans corresponding to each flight number are grouped according to the flight attribute, and the flight attributes are the same as one group, so as to obtain the attribute group of each flight number. Then, the first two data in the attribute group are used as data to be combined, and are combined according to a preset combining rule; if the combination is successful, the data after the combination is successful is continuously integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date is integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined. Therefore, by means of the method, when the flight schedule is changed, the data integration is carried out on the flight schedule to be validated corresponding to each flight number, the flight schedule of a single flight number is reduced, the change operation is simpler and more convenient, the change validation time required by the system is reduced, and accordingly the release efficiency of the flight schedule is improved.

As an implementation manner, the preset merging rule in the determining module 702 includes:

the acquisition unit is used for acquiring a union set of date ranges in the data to be combined, wherein the union set comprises a maximum date and a minimum date;

the first merging unit is used for taking the union of the minimum date, the maximum date and the shift of the data to be merged as the data of successful merging if the difference value between the maximum date and the minimum date of the data to be merged is less than or equal to seven;

the second merging unit is used for taking the minimum value of the first starting date and the second starting date as the starting date of the data which is successfully merged, and taking the maximum value of the first ending date and the second ending date as the ending date of the data which is successfully merged if the shift of the data to be merged is the same and only one digit, the starting date of one data in the data to be merged is the first starting date, the ending date is the first ending date, the starting date of the other data in the data to be merged is the second starting date, and the ending date is the second ending date, and the difference between the second starting date and the first ending date or the difference between the first starting date and the second ending date is seven;

and the third merging unit is used for taking the minimum value of the first starting date and the second starting date as the starting date of the data successfully merged and taking the maximum value of the first ending date and the second ending date as the ending date of the data successfully merged if the shift period of the data to be merged is the same and the difference between the maximum date and the minimum date is more than seven and the shift period of the difference between the second starting date and the first ending date or the difference between the first starting date and the second ending date is different from the shift period of the data to be merged.

As one embodiment, the flight plan integration apparatus 700 further includes:

the first grouping unit is used for grouping the flight plans corresponding to the flight numbers respectively according to the flight attributes, wherein the flight attributes are the same as one group, the attribute group of each flight number is obtained, and the flight plans are published flight plans;

the first judging unit is used for taking the first two data in the attribute group as data to be combined and combining the first two data according to a preset combining rule;

and the first integration unit is used for continuously integrating the successfully integrated data with the next data in the attribute group if the combination is successful, and integrating the data with large starting date with the next data in the attribute group if the combination is unsuccessful until the integration of each flight number is completed, wherein the starting date is the minimum date of the union of the date ranges in the data to be combined.

As one embodiment, the flight plan integration apparatus 700 further includes:

the second grouping unit is used for grouping the data in the flight rules according to the rule attributes to obtain a flight rule attribute group;

the second judging unit is used for taking the first two data in the flight rule attribute group as data to be combined, and combining the first two data according to a preset combining rule;

And the second integration unit is used for continuously integrating the successfully integrated data with the next data in the flight rule attribute group if the combination is successful, and integrating the data with large starting date with the next data in the flight rule attribute group if the combination is unsuccessful until the data integration in the flight rule is completed, wherein the starting date is the minimum date of the union of the date ranges in the data to be combined.

As an embodiment, the second packet unit is specifically configured to:

and grouping the data in the flight rules according to the rule levels, the rule factors and the rule values of the corresponding rule levels, wherein the rule levels, the rule factors and the rule values of the corresponding rule levels are the same as one group, and the flight rule attribute group is obtained.

The units involved in the embodiments of the present application may be implemented in software or in hardware. The name of the unit does not in any way constitute a limitation of the unit itself, for example the first acquisition unit may also be described as "unit acquiring at least two internet protocol addresses".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

The embodiment of the application also provides corresponding equipment and a computer readable storage medium, which are used for realizing the scheme provided by the embodiment of the application.

The device comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor is used for executing the computer program so as to enable the device to execute the flight plan integration method according to any embodiment of the application.

The computer readable storage medium stores a computer program, and when the code is executed, a device executing the computer program implements the flight plan integration method according to any embodiment of the present application.

The computer-readable storage medium carries one or more programs that, when executed by the flight plan integration apparatus, cause the apparatus to: grouping the flight plans to be validated corresponding to each flight number respectively according to the flight attributes, wherein the flight attributes are the same as one group, and obtaining attribute groups of each flight number; the first two data in the attribute group are used as data to be combined, and are combined according to a preset combining rule; if the combination is successful, the data after the combination is successful is continuously integrated with the next data in the attribute group, if the combination is unsuccessful, the data with large starting date is integrated with the next data in the attribute group until the integration of each flight number is completed, and the starting date is the minimum date of the union of date ranges in the data to be combined.

The computer-readable storage medium may be contained in the flight plan integration apparatus; or may exist alone without being assembled into the flight schedule integration apparatus.

The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

In accordance with one or more embodiments of the present application, example 1 (i.e., the flowchart of a flight plan integration method provided in fig. 1 above) provides a flight plan integration method comprising:

According to one or more embodiments of the present application, example 2 provides the method of example 1, the preset merge rule comprising:

acquiring a union of date ranges in the data to be combined, wherein the union comprises a maximum date and a minimum date;

if the difference value between the maximum date and the minimum date of the data to be combined is less than or equal to seven, the minimum date, the maximum date and the union of the shift of the data to be combined are used as successful data;

If the shift periods of the data to be combined are the same and only have one digit, the start date of one data in the data to be combined is a first start date, the end date is a first end date, the start date of the other data in the data to be combined is a second start date, the end date is a second end date, the difference value between the second start date and the first end date or the difference value between the first start date and the second end date is seven, the minimum value between the first start date and the second start date is used as the start date of the data which is successfully combined, and the maximum value between the first end date and the second end date is used as the end date of the data which is successfully combined;

if the shift periods of the data to be combined are the same, and the difference between the maximum date and the minimum date is greater than seven, the shift period of the difference between the second start date and the first end date or the shift period of the difference between the first start date and the second end date is different from the shift period of the data to be combined, the minimum value in the first start date and the second start date is used as the start date of the data successfully combined, and the maximum value in the first end date and the second end date is used as the end date of the data successfully combined.

According to one or more embodiments of the present application, example 3 provides the method of example 1, the method further comprising:

grouping the flight plans corresponding to the flight numbers respectively according to the flight attributes, wherein the flight attributes are the same as one group, and the attribute groups of the flight numbers are obtained, and the flight plans are published flight plans;

According to one or more embodiments of the present application, example 4 provides the method of example 1, the method further comprising:

grouping the data in the flight rules according to the rule attributes to obtain a flight rule attribute group;

the first two data in the flight rule attribute group are used as data to be combined, and are combined according to a preset combining rule;

If the combination is successful, the data after the combination is continued to be integrated with the next data in the flight rule attribute group, if the combination is unsuccessful, the data with large starting date is integrated with the next data in the flight rule attribute group until the data in the flight rule is integrated, and the starting date is the minimum date of the union of date ranges in the data to be combined.

According to one or more embodiments of the present application, example 5 provides the method of example 4, the grouping data in flight rules according to rule attributes to obtain a flight rule attribute group, comprising:

and grouping the data in the flight rules according to the rule levels, the rule factors and the rule values of the corresponding rule levels, wherein the rule levels, the rule factors of the corresponding rule levels and the rule values are the same as one group, and the flight rule attribute group is obtained.

According to one or more embodiments of the present application, example 6 (i.e., the structural schematic diagram of a flight plan integration apparatus provided in fig. 6 above) provides a flight plan integration apparatus, including:

According to one or more embodiments of the present application, example 7 provides the apparatus of example 6, the apparatus further comprising:

the first grouping unit is used for grouping the flight plans corresponding to the flight numbers respectively according to the flight attributes, wherein the flight attributes are the same as one group, the attribute groups of the flight numbers are obtained, and the flight plans are published flight plans;

Example 8 provides the apparatus of example 6, according to one or more embodiments of the application, the apparatus further comprising:

and the second integration unit is used for continuously integrating the successfully integrated data with the next data in the flight rule attribute group if the combination is successful, and integrating the data with a large starting date with the next data in the flight rule attribute group if the combination is unsuccessful until the data integration in the flight rule is completed, wherein the starting date is the minimum date of the union of the date ranges in the data to be combined.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

While several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in the present application is not limited to the specific combinations of technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the spirit of the disclosure. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.

Claims

1. A method of flight schedule integration, the method comprising:

2. The method of claim 1, wherein the preset merge rule comprises:

3. The method according to claim 1, wherein the method further comprises:

4. The method according to claim 1, wherein the method further comprises:

5. The method of claim 4, wherein grouping data in the flight rules according to the rule attributes to obtain a flight rule attribute set comprises:

6. A flight schedule integration apparatus, the apparatus comprising:

7. The apparatus of claim 6, wherein the apparatus further comprises:

8. The apparatus of claim 6, wherein the apparatus further comprises:

9. A flight schedule integration apparatus, the apparatus comprising:

a memory for storing a computer program;

a processor for executing the computer program to cause the apparatus to perform the steps of the flight plan integration method as claimed in any one of claims 1 to 5.

10. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program which, when executed by a processor, implements the flight plan integration method according to any one of claims 1 to 5.