Method and apparatus for processing code sharing relationship, electronic device, and storage medium

Abstract

The present disclosure provides a code sharing relationship processing method and device, electronic equipment and storage medium. The method is applied to an open flight data control system. After receiving a code sharing message issued by an open flight plan management system in the case of a change in the code sharing relationship, the change type and the target field corresponding to the change type in the code sharing message are analyzed, and then the target code sharing relationship that meets the target field in the open flight data control system is determined, and the target code sharing relationship is processed according to the change type. In the present disclosure, the open flight data control system can process the relevant code sharing relationship in real time according to the code sharing message issued by the open flight plan management system, ensure the accuracy of the departure flight code sharing relationship, and ensure the smooth travel of passengers.

Description

Technical Field

[0001] This disclosure relates to the field of software technology, and more specifically, to a method, apparatus, electronic device, and storage medium for processing code-sharing relationships. Background Technology

[0002] Code-sharing is a common marketing practice in the international civil aviation industry. Against the backdrop of increasingly fierce competition in the international aviation market, code-sharing, as an important means of cooperation among airlines within alliances or between airlines, is receiving more and more attention and use. For passengers, it allows for connecting check-in, enabling a single ticket for the entire journey and facilitating travel management. The reservation system (ICS) and departure system (DCS) share a single code-sharing relationship, and for the departure system, there is a timeliness requirement for data usage. For example, if a code-sharing relationship needs to be changed at the time of flight departure, and the reservation system fails to update the code-sharing relationship in a timely manner, passengers will be unable to complete departure procedures normally.

[0003] Currently, the Open Flight Data Control System (FDC) receives code-share relationships synchronized from the Open Flight Scheduling Management System (SCH) (referred to as "automatic synchronization"). To address the aforementioned issues, the FDC manually maintains these code-share relationships via an open interface (referred to as "manual maintenance") to synchronize downstream systems. Therefore, the FDC's code-share relationships originate from two sources: automatic synchronization and manual maintenance. However, as the number of data sources increases, the complexity of data processing increases, potentially affecting data accuracy. Summary of the Invention

[0004] In view of this, to solve the above problems, this disclosure provides a method, apparatus, electronic device, and storage medium for processing code-sharing relationships, the technical solution of which is as follows:

[0005] A method for handling code-sharing relationships, the method being applied to an open flight data control system, the method comprising:

[0006] Receive code-sharing messages from the Open Flight Schedule Management System when code-sharing relationships change;

[0007] The code-sharing message is parsed to determine the change type and the target field corresponding to the change type. The target field is a field that matches the Open Flight Data Control System and the Open Flight Planning Management System.

[0008] Determine the target code sharing relationship in the open flight data control system that satisfies the target field, and process the target code sharing relationship according to the change type.

[0009] An apparatus for processing code-sharing relationships, the apparatus comprising:

[0010] The message receiving module is used to receive code-sharing messages sent by the Open Flight Schedule Management System when the code-sharing relationship changes;

[0011] The message processing module is used to parse the change type and the target field corresponding to the change type in the code-sharing message, wherein the target field is a field that matches the Open Flight Data Control System and the Open Flight Planning Management System; determine the target code-sharing relationship in the Open Flight Data Control System that satisfies the target field, and process the target code-sharing relationship according to the change type.

[0012] An electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor invokes the application program stored in the memory, the application program being used to implement the code-sharing relationship processing method.

[0013] A storage medium storing computer program code, wherein the computer program code, when executed, implements the method for handling the code-sharing relationship.

[0014] Compared to existing technologies, the beneficial effects achieved by this disclosure are as follows:

[0015] This disclosure provides a method, apparatus, electronic device, and storage medium for processing code-sharing relationships. The method is applied to an open flight data control system. Upon receiving a code-sharing message from an open flight scheduling management system indicating a change in code-sharing relationships, the method parses the change type and the corresponding target field in the code-sharing message. This allows the system to determine the target code-sharing relationship within the open flight data control system that satisfies the target field, and then processes the target code-sharing relationship according to the change type. This open flight data control system can process relevant code-sharing relationships in real time based on code-sharing messages from the open flight scheduling management system, ensuring the accuracy of departing flight code-sharing relationships and guaranteeing smooth travel for passengers. Attached Figure Description

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

[0017] Figure 1 A flowchart illustrating the method for handling code sharing relationships provided in this embodiment of the disclosure;

[0018] Figure 2 This is a partial flowchart of the method for handling code sharing relationships provided in the embodiments of this disclosure;

[0019] Figure 3 This is another part of the method flowchart for handling code sharing relationships provided in the embodiments of this disclosure;

[0020] Figure 4 A schematic diagram of the structure of the code-sharing relationship processing apparatus provided in the embodiments of this disclosure;

[0021] Figure 5 Another schematic diagram of the structure of the processing apparatus for code sharing relationships provided in the embodiments of this disclosure;

[0022] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0023] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0024] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based 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". Definitions of other terms will be given in the description below.

[0025] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0026] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0027] To facilitate understanding of this disclosure, the relevant concepts of this disclosure will be explained below:

[0028] The Inventory Control System (ICS) is a real-time computer network system that provides functions such as flight availability information inquiry, passenger reservation and ticketing, onboard seat control, flight changes and passenger protection, and frequent flyer identification. It is a large-scale online transaction processing system operated by users via command line.

[0029] Departure Control System (DCS): A real-time computer network system consisting of a flight data control system, a passenger check-in system, and a load control system. It is a large-scale online transaction processing system operated by users via command line.

[0030] Open Flight Data Control (FDC): Flight Data Control is a flight data control system for the Departure Control System (DCS) implemented through a small server. It performs functions such as flight plan maintenance and release for the departure system and provides a graphical user interface.

[0031] Open Flight Schedule Management (SCH): Schedule Management uses a small server to implement functions such as maintaining and publishing flight schedules for the Seating System (ICS), and provides a graphical user interface.

[0032] Code-sharing: A flight marketed by one airline but operated by another. This means that if a passenger purchases a ticket from airline A for part of their journey or the entire trip, but actually travels on a flight operated by airline B, then this flight number is a code-share between A and B. The flight that provides the actual transportation or other services to passengers is called the carrier flight, as opposed to the marketing flight.

[0033] Operation and maintenance identifier: An operation and maintenance identifier is generated when data is updated through manual operation and maintenance.

[0034] Codeshare types are divided into two main categories: blockspace and free sale. Blockspace means the market-partner airline can obtain a predetermined number of seats for sale; free sale means the market-partner airline can obtain seats on the carrier's flights in real time and only pays for the seats actually sold and used. Free sale includes: free sale, SMAP, and duplex flight.

[0035] Host airline: An airline that uses the China TravelSky Passenger Service System for its flight management and inventory management system.

[0036] Non-Host Airlines: Airlines that do not use the China TravelSky Passenger Service System for flight management and inventory management.

[0037] FREESALE: FREE SALE, meaning free sale. In flight management systems, it specifically refers to a free sale between a host airline and a non-host airline, requiring the establishment of a market-side flight.

[0038] SMAP: Seat Mapping. In flight management systems, it specifically refers to code-sharing between two host airlines, without requiring the creation of marketing flights.

[0039] This disclosure is for use in the civil aviation passenger transport sector; see [link / reference]. Figure 1 , Figure 1 This is a flowchart illustrating a method for handling code-sharing relationships according to an embodiment of the present disclosure. This method is applied to an open flight data control system (FDC) and includes the following steps:

[0040] S10 receives code-sharing messages from the Open Flight Schedule Management System when code-sharing relationships change.

[0041] In this embodiment of the disclosure, the flight plan of the Open Flight Scheduling Management System (SCH) includes code-sharing relationships. When there are changes to the code-sharing relationships, the code-sharing relationships will be synchronized to downstream systems, including the Open Flight Data Control System (FDC).

[0042] When a code-sharing relationship changes in the Open Flight Scheduling Management System (SCH), the code-sharing message can be forwarded to the Open Flight Data Control System (FDC) using a real-time update method. Upon receiving the upstream code-sharing message, the Open Flight Data Control System (FDC) can adopt different processing schemes based on the type of change in the code-sharing message to handle the code-sharing relationship.

[0043] See Table 1 below, which is an example of the content of the code-sharing message provided in this disclosure. The code-sharing message contains three parts: fields, format, and M / O / C. The example is a content example. The fields include change type, operating airline, operating flight number, operating flight suffix, market airline, market flight number, market flight suffix, shared flight segment or segment, code-sharing type, code-sharing relationship start date, code-sharing relationship end date, flight schedule, and virtual flight identifier. The format indicates the format requirements for the fields. In M / O / C, "M" indicates mandatory, "O" indicates optional, and "C" indicates conditional transmission.

[0044] Table 1

[0045]

[0046] It should be noted that the information of the operating airline consists of the operating airline, the operating flight number, and the operating flight suffix, such as the operating airline CA123A; the information of the market airline consists of the market airline, the market flight number, and the market flight suffix, such as the market airline UA4521A; the shared flight segment or segment can be referred to as the shared flight segment or shared segment; the start date and end date of the code-sharing relationship constitute the date range of the code-sharing relationship.

[0047] S20, parse the change type and the target field corresponding to the change type in the code-sharing message. The target field is the field that matches the Open Flight Data Control System and the Open Flight Schedule Management System.

[0048] In this embodiment of the disclosure, after the Open Flight Data Control System (FDC) receives a code-sharing message from the Open Flight Scheduling Management System (SCH), when processing the code-sharing message, it can identify the change type of the code-sharing relationship through the change type label defined in the message, including addition, deletion, and modification. Modification consists of addition and deletion. Due to the diversity of change types, corresponding processing schemes are provided for each type of code-sharing message:

[0049] Based on the comparison of data from the carrier (i.e., the operating airline), the market operator (i.e., the market airline), the shared flight schedule (or segment), the code-sharing relationship date range, and the flight schedule, the data from the open Flight Data Control System (FDC) and the open Flight Schedule Management System (SCH) will be compared. For code-sharing relationships that have overlap or no overlap (i.e., target code-sharing relationships), the code-sharing type and operation and maintenance identifier will be compared again according to the different needs of the change type. Then, the data will be further added, deleted, and modified.

[0050] In the process of comparing maintenance identifiers, there is a priority relationship. If the code-sharing relationship is inconsistent with the code-sharing relationship manually maintained by the Open Flight Data Control System (FDC), the code-sharing relationship manually maintained by the open flight data control system (FDC) shall prevail. If the code-sharing relationship is consistent with the code-sharing relationship manually maintained by the open flight data control system (FDC), the data automatically synchronized by the Open Flight Schedule Management System (SCH) shall be used to overwrite the manual maintenance data of the open flight data control system (FDC).

[0051] In some embodiments, to ensure the legitimacy of the code-sharing message, before performing step S20 to parse the change type and target field in the code-sharing message, the following steps may also be performed:

[0052] The code-sharing message is verified, and if the verification passes, step S20 is executed.

[0053] In this embodiment of the disclosure, the open flight data control system (FDC) verifies whether the data in the code-sharing message meets the required fields and format requirements. If it does, the normal flow continues; otherwise, an error is reported: illegal request.

[0054] S30, determine the target code sharing relationship that satisfies the target field in the open flight data control system, and process the target code sharing relationship according to the change type.

[0055] In this embodiment of the disclosure, the Open Flight Data Control System (FDC) processes code-share relationships differently depending on the change type in the Open Flight Scheduling Management System (SCH) code-share message. In some scenarios, the Open Flight Scheduling Management System (SCH) code-share message only contains code-share relationships with a change type of deletion, i.e., code-share deletion.

[0056] See Figure 2 , Figure 2 This disclosure provides a partial flowchart of a method for handling code-sharing relationships. In its specific implementation, the change type includes deletion, and the target fields include the operating airline, the market airline, the shared flight schedule, the code-sharing relationship date range, and the flight schedule.

[0057] Step S30, "Determine the target code sharing relationship that satisfies the target field in the open flight data control system, and process the target code sharing relationship according to the change type," can be performed using the following steps:

[0058] S3011, Identify the first code-sharing relationship in the open flight data control system that intersects with the target field's carrier, market airline, shared flight season, code-sharing relationship date range, and flight schedule.

[0059] In this embodiment of the disclosure, the Open Flight Data Control System (FDC) determines whether there exists a code-sharing relationship in its own system that overlaps with the carrier, market airline, shared flight period, code-sharing relationship date range, and flight schedule in the code-sharing message, i.e., the first code-sharing relationship.

[0060] For code-sharing relationships that do not overlap, it means no changes have been made and no action will be taken.

[0061] S3012, It is determined that there is a first sub-code-sharing relationship with a newly added operation and maintenance identifier in the first code-sharing relationship.

[0062] In this embodiment, the newly added operation and maintenance identifier indicates that the code-sharing relationship is manually operated and the method is newly added. Therefore, the code-sharing relationship with the newly added operation and maintenance identifier (i.e., the first sub-code-sharing relationship) in the first code-sharing relationship is not changed.

[0063] S3013, Do not change the first sub-code sharing relationship; and delete the other code sharing relationships in the first code sharing relationship except for the first sub-code sharing relationship.

[0064] In this embodiment of the disclosure, the other code-sharing relationships in the first code-sharing relationship besides the first sub-code-sharing relationship include code-sharing relationships without an operation and maintenance identifier and code-sharing relationships with an operation and maintenance identifier that has been deleted. These code-sharing relationships are physically deleted. It should be noted that deleting the operation and maintenance identifier indicates that the code-sharing relationship is manually operated and maintained, and the method is deletion.

[0065] In other scenarios, the Open Flight Scheduling Management System (SCH) code-share messages only contain code-share relationships with the change type "new", i.e., new code-shares.

[0066] See Figure 3 , Figure 3 This disclosure provides a partial flowchart of a method for handling code-sharing relationships in its embodiments. In the specific implementation, the change type includes adding new information, and the target fields include the operating airline, the market airline, the shared flight schedule, the code-sharing relationship date range, the flight schedule, and the code-sharing type.

[0067] Step S30, "Determine the target code sharing relationship that satisfies the target field in the open flight data control system, and process the target code sharing relationship according to the change type," can be performed using the following steps:

[0068] S3021, Identify a second code-sharing relationship in the code-sharing message that is different from the code-sharing relationship in the Open Flight Data Control System, and add the second code-sharing relationship to the Open Flight Data Control System.

[0069] In this embodiment of the disclosure, the Open Flight Data Control System (FDC) determines whether there is a code-sharing relationship in its own system that is different from (i.e. has no overlap with) its own system, namely a second code-sharing relationship, and directly adds the second code-sharing relationship to its own system.

[0070] S3022, Identify the third code-sharing relationship in the open flight data control system that intersects with the target field's carrier, market carrier, shared flight festival, code-sharing relationship date range, and flight schedule.

[0071] In this embodiment of the disclosure, the Open Flight Data Control System (FDC) determines whether there exists a third code-sharing relationship in its system that overlaps with the carrier, market airline, shared flight period, code-sharing relationship date range, and flight schedule in the code-sharing message.

[0072] S3023, determine that the third code-sharing relationship includes a second sub-code-sharing relationship with a deleted operation and maintenance identifier, a third sub-code-sharing relationship with a newly added operation and maintenance identifier, and a fourth sub-code-sharing relationship without an operation and maintenance identifier.

[0073] In this embodiment, the code-sharing relationships in the third code-sharing relationship where the maintenance identifier has been deleted (i.e., the second sub-code-sharing relationship) are not modified, so as to facilitate comparison with the code-sharing relationship of the Open Flight Scheduling Management System (SCH) when needed later. Currently, there are three code-sharing types in the system: BLOCKSPACE, FREESALE, and SMAP. For the third code-sharing relationship, it is also necessary to determine whether the code-sharing types of the code-sharing relationships in the Open Flight Scheduling Management System (SCH) and the Open Flight Data Control System (FDC) where the maintenance identifier has been added are consistent (i.e., the third sub-code-sharing relationship). If they are consistent, the newly added maintenance identifier is deleted; otherwise, if they are inconsistent, the manual maintenance is used, and the data is not modified.

[0074] In addition, for the part of the code-sharing relationship that does not have an operation and maintenance identifier in the third code-sharing relationship (i.e., the fourth sub-code-sharing relationship), the Open Flight Schedule Management System (SCH) data is used to overwrite it.

[0075] S3024, the second sub-code-sharing relationship is not modified; and, from the third sub-code-sharing relationship, a first part of the code-sharing relationship that is the same as the code-sharing type in the target field and a second part of the code-sharing relationship that is different from the code-sharing type in the target field are determined; and, the fourth sub-code-sharing relationship is overridden with the code-sharing relationship in the code-sharing message that is the same as the fourth sub-code-sharing relationship.

[0076] In this embodiment of the disclosure, for the third code-sharing relationship, the part of the code-sharing relationship that is consistent with the code-sharing type in the target field (i.e., the first part of the code-sharing relationship) will have its newly added operation and maintenance identifier deleted, while the part of the code-sharing relationship that is inconsistent with the code-sharing type in the target field (i.e., the second part of the code-sharing relationship) will be subject to manual operation and maintenance, and the data will not be changed.

[0077] S3025, delete the newly added operation and maintenance identifier in the first part of the code sharing relationship, and do not make any changes to the second part of the code sharing relationship.

[0078] In this embodiment of the disclosure, manual maintenance of the code-sharing relationship has a higher priority than automatic synchronization to prevent the required data from being overwritten by automatic synchronization, thereby ensuring the accuracy of the code-sharing relationship of departing flights and ensuring smooth travel for passengers.

[0079] In other scenarios, the change type in the Open Flight Scheduling Management System (SCH) codeshare message is "modification," including adding and deleting codeshare relationships, i.e., modifying codeshare relationships. In response, the Open Flight Data Control System (FDC) can determine whether both adding and deleting codeshare relationships exist in the codeshare message based on the target fields: operating airline, market airline, shared flight period, codeshare relationship date range, flight schedule, and codeshare type.

[0080] Compare all fields of the newly added and deleted code-sharing relationships. If the relationship exists only in the deleted code-sharing relationship, it is considered a deleted code-sharing relationship, and proceed with steps S3011 to S3013 above. If the relationship exists only in the newly added code-sharing relationship, it is considered a newly added code-sharing relationship, and proceed with steps S3021 to S3025 above. This disclosure will not repeat the details here. Furthermore, if both the newly added and deleted code-sharing relationships exist, it is considered a newly added code-sharing relationship, and proceed with steps S3021 to S3025 above.

[0081] During data processing, code-sharing relationships involve date ranges and flight schedules, thus requiring date segmentation logic. It's necessary to compare the code-sharing relationships between the Open Flight Scheduling Management System (SCH) and the Open Flight Data Control System (FDC), filtering out overlapping or non-overlapping data. Then, the filtered dates are automatically truncated according to the flight schedules, ultimately ensuring no code-sharing relationships are lost. For example, comparing two date ranges, A and B, will generate overlapping and non-overlapping data, and each result will then be automatically truncated to the valid dates according to the flight schedules.

[0082] To address this, step S3011, "Determining the first code-sharing relationship in the open flight data control system that intersects with the target fields of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule," can be performed using the following steps:

[0083] Identify the code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field; according to the date range and flight schedule of the code-sharing relationships in the target field, segment the data of the code-sharing relationships that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field to obtain the first code-sharing relationship.

[0084] Step S3022, "Identifying third-party code-sharing relationships in the open flight data control system that intersect with the target fields of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule," can be performed using the following steps:

[0085] Identify the code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field; according to the date range and flight schedule of the code-sharing relationships in the target field, segment the data of the code-sharing relationships that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field to obtain the third code-sharing relationship.

[0086] See Table 2 below, which provides an example of the data segmentation provided in this disclosure.

[0087] Table 2

[0088]

[0089] In some embodiments, after changes are made to the Open Flight Data Control System (FDC), the FDC publishes a code-sharing relationship with the Departure Control System (DCS) to achieve data synchronization between the FDC and the DCS. Specifically, the following steps can be taken:

[0090] The processed target code sharing relationship is sent to the departure system.

[0091] The code-sharing relationship handling method disclosed herein utilizes both automatic synchronization and manual maintenance data. When only manual maintenance is available, the manual maintenance data takes precedence. If the automatic synchronization data matches the manual maintenance data, the automatic synchronization data overwrites the manual maintenance data; if the overwrite is a deletion, it is a physical deletion. If the date ranges of automatic and manual synchronization are inconsistent, date segmentation is performed. This ensures the accuracy of departing flight code-sharing relationships and guarantees smooth travel for passengers.

[0092] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0093] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

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

[0095] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0096] Based on the code-sharing relationship processing method provided in the above embodiments, this disclosure provides an apparatus for executing the above code-sharing relationship processing method, the structural schematic diagram of which is shown below. Figure 4 As shown, it includes:

[0097] Message receiving module 10 is used to receive code-sharing messages sent by the Open Flight Schedule Management System when the code-sharing relationship changes;

[0098] The message processing module 20 is used to parse the change type and the target field corresponding to the change type in the code-sharing message. The target field is the field that matches the Open Flight Data Control System and the Open Flight Schedule Management System. It determines the target code-sharing relationship in the Open Flight Data Control System that satisfies the target field and processes the target code-sharing relationship according to the change type.

[0099] Optionally, the message processing module 20 is also used for:

[0100] The code-sharing message is validated, and if the validation passes, the change type and target field in the code-sharing message are parsed.

[0101] Optionally, the above device further includes the following modules, as shown in the structural diagram below. Figure 5 As shown:

[0102] The message publishing module 30 is used to send the processed target code sharing relationship to the departure system.

[0103] Optionally, the change type includes deletion, and the target fields include the carrier, market carrier, shared flight schedule, code-share relationship date range, and flight schedule;

[0104] The message processing module 20, used to determine target code sharing relationships that satisfy target fields in the open flight data control system and to process target code sharing relationships according to change types, is specifically used for:

[0105] Identify the first code-sharing relationship in the open flight data control system that intersects with the target fields of operating airline, market airline, shared flight season, code-sharing relationship date range, and flight schedule; identify the first sub-code-sharing relationship within the first code-sharing relationship that contains a newly added maintenance identifier; leave the first sub-code-sharing relationship unchanged; and delete all other code-sharing relationships within the first code-sharing relationship except for the first sub-code-sharing relationship.

[0106] Optionally, the message processing module 20, used to determine the first code-sharing relationship in the open flight data control system that intersects with the target fields of the operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule, is specifically used for:

[0107] Identify the code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field; according to the date range and flight schedule of the code-sharing relationships in the target field, segment the data of the code-sharing relationships that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field to obtain the first code-sharing relationship.

[0108] Optionally, the change type includes adding, and the target fields include the carrier, market carrier, shared flight schedule, code-share relationship date range, flight schedule, and code-share type;

[0109] The message processing module 20, used to determine target code sharing relationships that satisfy target fields in the open flight data control system and to process target code sharing relationships according to change types, is specifically used for:

[0110] Identify a second code-sharing relationship in the code-sharing message that differs from the code-sharing relationship in the Open Flight Data Control System (AFDS), and add the second code-sharing relationship to the AFDS; identify a third code-sharing relationship in the AFDS that intersects with the carrier, market carrier, shared flight festival, code-sharing relationship date range, and flight schedule in the target fields; identify a second sub-code-sharing relationship within the third code-sharing relationship that has a deleted maintenance identifier, a third sub-code-sharing relationship that has a newly added maintenance identifier, and a fourth sub-code-sharing relationship that does not have a maintenance identifier; leave the second sub-code-sharing relationship unchanged; identify a first part of the code-sharing relationship from the third sub-code-sharing relationship that has the same code-sharing type as the target field, and a second part of the code-sharing relationship that has a different code-sharing type than the target field; overwrite the fourth sub-code-sharing relationship with the code-sharing relationship in the code-sharing message that has the same code-sharing relationship as the fourth sub-code-sharing relationship; delete the newly added maintenance identifier in the first part of the code-sharing relationship, and leave the second part of the code-sharing relationship unchanged.

[0111] Optionally, the message processing module 20, used to determine third code-sharing relationships in the open flight data control system that intersect with the target fields of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule, is specifically used for:

[0112] Identify the code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field; according to the date range and flight schedule of the code-sharing relationships in the target field, segment the data of the code-sharing relationships that intersect with the carrier airlines, market airlines, and shared flight schedules in the target field to obtain the third code-sharing relationship.

[0113] It should be noted that the detailed functions of each module in the embodiments of this disclosure can be found in the corresponding disclosure section of the above-mentioned method for handling code sharing relationships, and will not be repeated here.

[0114] It should also be noted that the modules described in the embodiments of this disclosure can be implemented in software or in hardware. Furthermore, the name of a module does not necessarily limit the module itself; for example, the first module unit can also be described as "a module for acquiring at least two Internet Protocol addresses".

[0115] See Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. The electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement a method for handling code-sharing relationships.

[0116] The electronic devices in this disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (e.g., vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0117] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 606 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0118] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 606 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0119] This disclosure also provides a storage medium storing computer program code, and a method for handling code-sharing relationships when the computer program code is executed.

[0120] In the context of this disclosure, a storage medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A storage medium can be a machine-readable signal medium or a machine-readable storage medium. Storage media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

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

[0122] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0123] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 609, or installed from storage device 606, or installed from ROM 602. When the computer program is executed by processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0124] According to one or more embodiments of this disclosure, a method for processing code-sharing relationships is provided, the method being applied to an open flight data control system, the method comprising:

[0125] Receive code-sharing messages from the Open Flight Schedule Management System when code-sharing relationships change;

[0126] Parse the change type and the target field corresponding to the change type in the code-sharing message. The target field is the field that matches the Open Flight Data Control System and the Open Flight Schedule Management System.

[0127] Determine the target code sharing relationships that satisfy the target fields in the open flight data control system, and process the target code sharing relationships according to the change type.

[0128] According to one or more embodiments of this disclosure, the method further includes:

[0129] The code-sharing message is validated, and if the validation passes, the change type and target field in the code-sharing message are parsed.

[0130] According to one or more embodiments of this disclosure, the method further includes:

[0131] The processed target code sharing relationship is sent to the departure system.

[0132] According to one or more embodiments of this disclosure, the change type includes deletion, and the target fields include carrier, market carrier, shared flight schedule, code-share relationship date range, and flight schedule;

[0133] Identify the target code sharing relationships that satisfy the target fields in the open flight data control system, and process the target code sharing relationships according to the change type, including:

[0134] Identify the first code-sharing relationship in the open flight data control system that intersects with the target fields for carrier, market airline, shared flight festival, code-sharing relationship, date range, and flight schedule;

[0135] Identify a first sub-code-sharing relationship with a newly added operation and maintenance identifier within the first code-sharing relationship;

[0136] The first sub-code sharing relationship remains unchanged; and all other code sharing relationships in the first code sharing relationship, except for the first sub-code sharing relationship, are deleted.

[0137] According to one or more embodiments of this disclosure, determining a first code-sharing relationship in an open flight data control system that intersects with the target fields of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule includes:

[0138] Identify code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight segments in the target field;

[0139] Based on the date range and flight schedule of the code-sharing relationship in the target field, the code-sharing relationships that intersect with the carrier, market airline, and shared flight schedule in the target field are segmented to obtain the first code-sharing relationship.

[0140] According to one or more embodiments of this disclosure, the change type includes addition, and the target fields include carrier, market carrier, shared flight schedule, code-share relationship date range, flight schedule and code-share type;

[0141] Identify the target code sharing relationships that satisfy the target fields in the open flight data control system, and process the target code sharing relationships according to the change type, including:

[0142] Identify a second code-sharing relationship in the code-sharing message that differs from the code-sharing relationship in the Open Flight Data Control System, and add the second code-sharing relationship to the Open Flight Data Control System;

[0143] Identify third code-sharing relationships in the open flight data control system that intersect with the target fields of operating airlines, market airlines, shared flight festivals, and code-sharing relationships in the date range and flight schedule.

[0144] It was determined that the third code-sharing relationship included a second sub-code-sharing relationship with a deleted operation and maintenance identifier, a third sub-code-sharing relationship with a newly added operation and maintenance identifier, and a fourth sub-code-sharing relationship without an operation and maintenance identifier.

[0145] The second sub-code-sharing relationship remains unchanged; and, from the third sub-code-sharing relationship, a first part of the code-sharing relationship that is the same as the code-sharing type in the target field and a second part of the code-sharing relationship that is different from the code-sharing type in the target field are determined; and, the fourth sub-code-sharing relationship is overridden with the code-sharing relationship in the code-sharing message that is the same as the fourth sub-code-sharing relationship.

[0146] Remove the newly added maintenance identifier from the first part of the code-sharing relationship, and leave the second part of the code-sharing relationship unchanged.

[0147] According to one or more embodiments of this disclosure, identifying a third code-sharing relationship in an open flight data control system that intersects with the target fields of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule includes:

[0148] Identify code-sharing relationships in the open flight data control system that intersect with the carrier airlines, market airlines, and shared flight segments in the target field;

[0149] Based on the date range and flight schedule of the code-sharing relationship in the target field, the code-sharing relationships that intersect with the carrier, market airline, and shared flight schedule in the target field are segmented to obtain the third code-sharing relationship.

[0150] According to one or more embodiments of this disclosure, a code-sharing relationship processing apparatus is provided, the apparatus comprising:

[0151] The message receiving module is used to receive code-sharing messages sent by the Open Flight Schedule Management System when the code-sharing relationship changes;

[0152] The message processing module is used to parse the change type and the target field corresponding to the change type in the code-sharing message. The target field is the field that matches the Open Flight Data Control System and the Open Flight Schedule Management System. It determines the target code-sharing relationship in the Open Flight Data Control System that satisfies the target field and processes the target code-sharing relationship according to the change type.

[0153] According to one or more embodiments of the present disclosure, an electronic device is provided, characterized in that the electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement a method for handling code-sharing relationships.

[0154] According to one or more embodiments of the present disclosure, a storage medium is provided, characterized in that the storage medium stores computer program code, and the computer program code, when executed, implements a method for handling code-sharing relationships.

[0155] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

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

[0157] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A method for handling code-sharing relationships, characterized in that, The method is applied to an open flight data control system, and the method includes: Receive code-sharing messages from the Open Flight Schedule Management System when code-sharing relationships change; The code-sharing message is parsed to determine the change type and the target field corresponding to the change type. The target field is a field that matches the Open Flight Data Control System and the Open Flight Schedule Management System. The target field includes the operating airline, the market airline, the shared flight season, the code-sharing relationship date range, the flight schedule, and the code-sharing type. The process of parsing the change type in the code-sharing message is as follows: the change type of the code-sharing relationship is identified based on the change type label defined in the code-sharing message. The data from the Open Flight Data Control System and the Open Flight Schedule Management System are compared based on the operating airline, market airline, shared flight schedule, code-share relationship date range, and flight schedule. For code-share relationships that overlap or do not overlap, the code-share type and maintenance identifier are compared again according to the different needs of the change type. If the code-share relationship is inconsistent with the code-share relationship manually maintained by the Open Flight Data Control System, the manually maintained code-share relationship shall prevail. If the code-share relationship is consistent with the code-share relationship manually maintained by the Open Flight Data Control System, the data automatically synchronized by the Open Flight Schedule Management System is used to overwrite the manually maintained data of the Open Flight Data Control System. The maintenance identifier is generated by updating data through manual maintenance. The target code sharing relationship that satisfies the target field in the open flight data control system is determined, and the target code sharing relationship is processed according to the change type, wherein different change types correspond to different processing, and the change type includes addition and / or deletion.

2. The method according to claim 1, characterized in that, The method further includes: The code-sharing message is validated, and if the validation passes, the change type and target field in the code-sharing message are parsed.

3. The method according to claim 1, characterized in that, The method further includes: The processed target code sharing relationship is sent to the departure system.

4. The method according to claim 1, characterized in that, The change type includes deletion; The step of determining the target code-sharing relationship in the open flight data control system that satisfies the target field, and processing the target code-sharing relationship according to the change type, includes: Determine the first code-sharing relationship in the open flight data control system that intersects with the target field in terms of the carrier, market airline, shared flight festival, code-sharing relationship date range, and flight schedule; It is determined that a first sub-code-sharing relationship with a newly added operation and maintenance identifier exists within the first code-sharing relationship; The first sub-code sharing relationship remains unchanged; and all other code sharing relationships in the first code sharing relationship, except for the first sub-code sharing relationship, are deleted.

5. The method according to claim 4, characterized in that, The process of determining the first code-sharing relationship in the open flight data control system that intersects with the target field of the operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule includes: Determine the code-sharing relationships in the open flight data control system that intersect with the carriers, market airlines, and shared flight segments in the target field; Based on the date range and flight schedule of the code-sharing relationship in the target field, the code-sharing relationships that intersect with the carrier, market airline, and shared flight schedule in the target field are segmented to obtain the first code-sharing relationship.

6. The method according to claim 1, characterized in that, The change types include additions; The step of determining the target code-sharing relationship in the open flight data control system that satisfies the target field, and processing the target code-sharing relationship according to the change type, includes: Identify a second code-sharing relationship in the code-sharing message that is different from the code-sharing relationship in the Open Flight Data Control System, and add the second code-sharing relationship to the Open Flight Data Control System; Identify a third code-sharing relationship in the open flight data control system that intersects with the target field in terms of the carrier, market airline, shared flight festival, code-sharing relationship date range, and flight schedule; It is determined that the third code-sharing relationship includes a second sub-code-sharing relationship with a deleted operation and maintenance identifier, a third sub-code-sharing relationship with a newly added operation and maintenance identifier, and a fourth sub-code-sharing relationship without an operation and maintenance identifier; The second sub-code-sharing relationship is not modified; and, from the third sub-code-sharing relationship, a first part of the code-sharing relationship that is the same as the code-sharing type in the target field and a second part of the code-sharing relationship that is different from the code-sharing type in the target field are determined; and, the fourth sub-code-sharing relationship is overwritten with the code-sharing relationship in the code-sharing message that is the same as the fourth sub-code-sharing relationship. Delete the newly added operation and maintenance identifier in the first part of the code sharing relationship, and do not make any changes to the second part of the code sharing relationship.

7. The method according to claim 6, characterized in that, The process of determining the third code-sharing relationship in the open flight data control system that intersects with the target field in terms of operating airline, market airline, shared flight festival, code-sharing relationship date range, and flight schedule includes: Determine the code-sharing relationships in the open flight data control system that intersect with the carriers, market airlines, and shared flight segments in the target field; Based on the date range and flight schedule of the code-sharing relationship in the target field, the code-sharing relationships that intersect with the carrier, market airline, and shared flight schedule in the target field are segmented to obtain the third code-sharing relationship.

8. A processing apparatus for code-sharing relationships, characterized in that, The device is used in an open flight data control system, and the device includes: The message receiving module is used to receive code-sharing messages sent by the Open Flight Schedule Management System when the code-sharing relationship changes; The message processing module is used to parse the change type and the target field corresponding to the change type in the code-sharing message. The target field is a field that matches the Open Flight Data Control System and the Open Flight Planning Management System. The target field includes the operating airline, the market airline, the shared flight schedule, the code-sharing relationship date range, the flight schedule, and the code-sharing type. The process of parsing the change type in the code-sharing message is as follows: the change type of the code-sharing relationship is identified based on the change type label defined in the code-sharing message; the data of the Open Flight Data Control System and the Open Flight Planning Management System are compared according to the operating airline, the market airline, the shared flight schedule, the code-sharing relationship date range, and the flight schedule. For code-sharing messages with or without overlap... For code-sharing relationships, depending on the different change types, the code-sharing type and maintenance identifier are compared again. If they are inconsistent with the code-sharing relationships manually maintained by the Open Flight Data Control System, the manually maintained code-sharing relationships shall prevail. If they are consistent with the code-sharing relationships manually maintained by the Open Flight Data Control System, the data automatically synchronized by the Open Flight Schedule Management System is used to overwrite the manually maintained data of the Open Flight Data Control System. The maintenance identifier is generated by updating data through manual maintenance. The target code-sharing relationships that satisfy the target fields in the Open Flight Data Control System are determined, and the target code-sharing relationships are processed according to the change types. Different change types correspond to different processing, and the change types include addition and / or deletion.

9. An electronic device, characterized in that, The electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement the code-sharing relationship processing method according to any one of claims 1-7.

10. A storage medium, characterized in that, The storage medium stores computer program code, which, when executed, implements the code-sharing relationship processing method according to any one of claims 1-7.

Images