Seat protection method, apparatus, electronic device, and computer readable medium

Abstract

The application provides a seat protection method, device, electronic equipment and computer readable medium. The method receives a seat protection request. If the trigger cause of the seat protection request is to change the passenger reservation record of a specific passenger, the method reads flight data, passenger reservation record data, seat protection rule data and seat map data in response to the seat protection request. Then, according to the original seat data corresponding to the original seat of the specific passenger in the passenger reservation record and the seat protection rule data, the specific passenger is allocated a new seat on the target flight. Since the new seat map of the source flight and the new seat map of the target flight are not regenerated when the passenger reservation record of a single specific passenger is changed, the seat protection process is simpler than the existing seat protection process, and the change of the seats booked by the passengers except the specific passenger due to the regeneration of the new seat map is avoided, thereby improving the processing efficiency of the seat protection request and the passenger experience.

Description

Technical Field

[0001] This invention relates to the field of seat protection technology, and more particularly to a seat protection method, device, electronic device, and computer-readable medium. Background Technology

[0002] Seat protection is the process of reserving a seat for a passenger on a target flight (the flight the passenger was on after the reassignment) based on the passenger's original seat reservation on the source flight (the flight the passenger was on before the reassignment). In existing seat protection procedures, to avoid changes in seat maps due to changes in aircraft type or layout, the main maps of both the source and target flights are reread upon receiving each seat protection request. A new seat map is then generated for the source flight based on its main map, and a new seat map for the target flight is generated based on its main map. Finally, based on the new seat maps for the source and target flights, a new seat is reserved for the passenger on the new seat map of the target flight, according to the passenger's original reservation on the new seat map of the source flight.

[0003] As airline services continue to improve, the scenarios that can trigger seat protection requests are increasing, leading to a corresponding increase in the number of seat protection requests that need to be processed. For example, airlines have added a service that allows adjustments to individual passenger booking records to accommodate passengers' rescheduling requests. However, the existing seat protection process is too cumbersome and inefficient, making it difficult to handle the large number of seat protection requests. Therefore, it is necessary to simplify the existing seat protection process to improve processing efficiency. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a seat protection method, apparatus, electronic device, and computer-readable medium to simplify the seat protection process and improve the efficiency of processing seat requests.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] In a first aspect, embodiments of this application disclose a seat protection method, including:

[0007] Receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection;

[0008] If the seat protection request is triggered by a change in the passenger reservation record of a specific passenger, then in response to the seat protection request, flight data, passenger reservation record data, seat protection rule data, and seat map data are read.

[0009] Based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, a new seat is assigned to the specific passenger on the target flight; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight.

[0010] Secondly, embodiments of this application disclose a seat protection device, including:

[0011] A receiving unit is used to receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the triggering reason for seat protection;

[0012] The first reading unit is used to read flight data, passenger reservation record data, seat protection rule data, and seat map data in response to the seat protection request if the triggering reason of the seat protection request is a change in the passenger reservation record of a single specific passenger.

[0013] A seat protection unit is used to assign a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight.

[0014] Thirdly, embodiments of this application disclose an electronic device, including a memory and a processor;

[0015] The memory is used to store computer programs;

[0016] The processor is used to execute the computer program, specifically to implement the seat protection method as described in any one of the first aspects.

[0017] Fourthly, embodiments of this application disclose a computer-readable medium for storing a computer program, which, when executed, is specifically used to implement the seat protection method as described in any of the first aspects above.

[0018] Based on the seat protection method provided in the above embodiments of the present invention, after receiving a seat protection request, if the triggering reason for the seat protection request is a change in the passenger reservation record of a specific passenger, then in response to the seat protection request, the flight data, passenger reservation record data, seat protection rule data, and seat map data are directly read. Then, based on the original seat data corresponding to the original seat in the passenger reservation record and the seat protection rule data, a new seat on the target flight is assigned to the specific passenger. Since changing the passenger reservation record data of a specific passenger does not involve changes in the aircraft type, layout, or seat protection rules of the source and target flight segments, and other passenger reservation record data are not affected except for the specific customer's passenger reservation record data, it is not necessary to regenerate a new seat map for the source flight and a new seat map for the target flight to directly assign a new seat on the target flight to the specific passenger. This is not only simpler than the existing seat protection process, but also avoids changes in the reserved seats of passengers other than the specific passenger due to the regeneration of a new seat map, thus improving the processing efficiency of seat protection requests and passenger experience. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0020] Figure 1 This is a diagram illustrating the entity connection of a seat protection system as proposed in an embodiment of this application.

[0021] Figure 2 This is a schematic flowchart of a seat protection method proposed in an embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating a method for modifying and synchronizing seating charts and PNR data according to an embodiment of this application.

[0023] Figure 4a This is a flowchart illustrating another seat protection method proposed in an embodiment of this application;

[0024] Figure 4b An embodiment of this application is provided. Figure 4a A flowchart illustrating step S405 in the process;

[0025] Figure 4c An embodiment of this application is provided. Figure 4b A flowchart illustrating step S4051 in the process;

[0026] Figure 4d An embodiment of this application is provided. Figure 4a A flowchart illustrating step S409 in the process;

[0027] Figure 5a This is a schematic diagram of a field of PNR data according to an embodiment of this application;

[0028] Figure 5b A schematic diagram of the fields of the seat map of the source flight proposed in the embodiments of this application. Figure 1 ;

[0029] Figure 5c This is a schematic diagram of a flight list field proposed in an embodiment of this application;

[0030] Figure 5d A schematic diagram of the fields of the seat map of the target flight proposed in the embodiments of this application. Figure 1 ;

[0031] Figure 5e This is a schematic diagram of a field for PNR change data according to an embodiment of this application;

[0032] Figure 5f A schematic diagram of the fields of the seat map of the target flight proposed in the embodiments of this application. Figure 2 ;

[0033] Figure 5g A schematic diagram of the fields of the seat map of the source flight proposed in the embodiments of this application. Figure 2 ;

[0034] Figure 5h This is a schematic diagram of the protection result message proposed in the embodiments of this application;

[0035] Figure 6 This is a schematic diagram of the composition of the seat protection component proposed in the embodiments of this application;

[0036] Figure 7 This is a schematic diagram of the structure of a seat protection device proposed in an embodiment of this application;

[0037] Figure 8 This is a schematic diagram of the structure of an electronic device proposed in an embodiment of this application. Detailed Implementation

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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".

[0042] To facilitate understanding of the technical solution of this invention, relevant concepts that may be involved will be introduced first.

[0043] The ASR instruction is used to reserve seats on an aircraft in advance. When booking a flight, you reserve a specific seat number on the plane. There are two types of reservation methods: seat reservation before flight initialization and seat reservation after flight initialization.

[0044] Passenger Name Record (PNR) refers to passenger reservation information, which includes details such as name, flight segment, date, cabin class, fare, ID number, and seat.

[0045] The main image is the basic template for the seat distribution diagram set by the airline according to the aircraft type layout (it can also be called the sales layout template), and it is the basis for generating the seat diagram.

[0046] Seating chart, a map showing the distribution of seats on an aircraft according to flight / cabin class, represented by a matrix. Each element represents a position, categorized as free seats, paid seats, X-lock seats, C-lock seats, aisle seats, unavailable seats, etc.

[0047] Aircraft cabins are primarily divided into several seating areas, including First Class, Business Class, Premium Economy, and Economy Class. Generally, First Class offers the highest price and comfort, followed by Business Class, with Economy Class offering the lowest.

[0048] Sub-cabins are logically divided into multiple sub-cabins based on different pricing discounts, on the basis of a cabin class.

[0049] Seat attributes, such as spaciousness, seat width, window seat, aisle seat, front / back seat, are all important factors. Currently, all domestic flights in China are smoke-free.

[0050] Seat locks are X-locks or C-locks that airlines set on the main chart or seat map. If a seat is set with an X-lock, the seat is unavailable; if a seat is set with a C-lock, only the airline's control officer can reserve the seat.

[0051] Additional services are services offered by airlines in addition to air travel, such as seat reservations, unaccompanied minor pick-up and drop-off, wheelchair access, and pet transport.

[0052] Seat classes are defined by the airlines, assigning value levels to seats on the seat map. Seats of different classes have different prices, and seat protection is generally limited to seats of the same value class, unless the airline has defined separate rules for cross-class seat protection.

[0053] Seat protection repositions passengers with seat reservations on the flight to the seat map. Due to changes in the seat map / price class map, there is a probability that a passenger's reservation record cannot be repositioned to the original seat number.

[0054] RE stands for Reassignment, meaning a passenger is reassigned to another flight on the same route. RebookPNR means a specific individual passenger is reassigned to another flight on the same route. RebookPNR is one scenario within RE.

[0055] Flight changes: The airline modifies flight information in the flight management system and the changes take effect. Maintenance tools: Image refresh, repositioning all passengers with seat reservations on the flight onto the seating chart.

[0056] SRA, a maintenance tool, is used to refresh the seat map, repositioning all passengers with seat reservations on the flight onto the seat map.

[0057] Host-Airlines is a list of airline group relationships hosted by the route system and handles inventory-based bookings and other passenger-related services for airlines.

[0058] Flight initialization occurs when the flight control system (also known as the reservation system) sends a flight list to the departure system. This typically happens three days before departure or at the agreed-upon time. At this point, the decision-making power for seat reservations is transferred to the departure system.

[0059] UN means that the valid flight segment in the passenger's booking record has been cancelled, resulting in the cancellation of related ticket, seat and other information.

[0060] See Figure 1To more clearly illustrate the relationships between the various related concepts mentioned above, this application provides an entity relationship diagram for flight seat protection. For example... Figure 1 As shown, the main image can be generated by matching the aircraft type, cabin class, and layout of a flight. The main image is set by the airline. Based on a flight's main image and multiple dates, seating charts for the flight on different dates can be created. Figure 1 In this context, "1" represents one, and "*" represents multiple. The seating chart for each flight / segment / cabin class stores seat information, including a seat matrix (representing the layout of each seat) and seat data for each seat, which includes seat number, seat type, and seat attributes. Seat protection rules include a seat class table and seat class protection rules (e.g., ...). Figure 1 (The cross-class protection rules are shown). The seat class table is set by the airline and is obtained by matching aircraft type parameters and layout parameters. It can be used to protect paid seats. Seat protection is triggered in three scenarios: flight schedule change, rebooking, and SRA (Seat Reservation and Reservation). Flight seat protection uses data such as flight, date (day), seat class table, and seat map to execute seat protection.

[0061] As is known from the background art, in existing seat protection processes, upon receiving any seat protection request, a new seat map for the source and destination flights is regenerated before assigning new seats to passengers. When there are too many seat protection requests, this cumbersome process leads to low efficiency and struggles to meet the demands of handling a large number of requests. Furthermore, each time a new seat map for the source and destination flights is regenerated, seats reserved for all passengers need to be reassigned on the new map. This reassignment process can easily cause changes to passengers' original seat reservations, resulting in a poor booking experience. To improve the efficiency of seat protection and enhance the passenger experience, this application proposes... Figure 2 The seat protection method shown specifically includes the following steps:

[0062] S201. Receive a seat protection request, wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection.

[0063] In step S201, seat protection is triggered in scenarios such as flight schedule changes, SRA (Scheduled Rescheduled Flight), and RE (Rescheduled Flight), and the flight control system receives a corresponding seat protection request. For example, in the RE scenario, the flight control system receives a seat protection request from a specific passenger sent from their terminal. Specifically, when a specific passenger changes their ticket from flight A to flight B on their computer, the flight control system receives a seat protection request. In this case, flight A is the source flight, and flight B is the destination flight. The seat protection request includes identification data for both flight A (e.g., flight number) and flight B.

[0064] The source flight identification data refers to data unique to the source flight, such as its flight number, segment data, and flight data. Similarly, the target flight identification data refers to data unique to the target flight, such as its flight number, segment data, and flight data.

[0065] Optionally, in a specific embodiment of this application, the seat protection request may also carry one or more data such as the date of the source flight, the date of the destination flight, the reason for triggering the seat protection request, the time of triggering the seat protection request, and flight segment information. For example, if the scenario triggering the seat protection request is a passenger modifying a single passenger's reservation record, the seat protection request may also carry key data of that passenger's reservation record. The flight segment information includes the flight number, departure point, destination, and flight date.

[0066] It should be noted that the source flight and the target flight in the seat protection request can be different flights or the same flight, depending on the specific scenario that triggers seat protection. This application embodiment does not impose any restrictions on this.

[0067] S202. Determine whether the reason for triggering the seat protection request is a change in the passenger reservation record of a specific passenger.

[0068] If step S202 determines that the seat protection request was triggered by a change in the reservation record of a specific passenger, then step S203 is executed, which involves assigning a new seat to the specific passenger without regenerating a new seat map for the target and source flights. Specifically, when a passenger reservation record is changed, only the specified PNR is actually affected; other PNRs are not affected. The detailed analysis is as follows:

[0069] (1) Changing the reservation record of a single passenger will not modify the aircraft type or layout of the source segment (the segment of the source flight) and the destination segment (the segment of the destination flight).

[0070] (2) Based on the foregoing Figure 1As can be seen from the relevant descriptions, if the aircraft type and layout of the flight segment remain unchanged, the main map and seat class table of the flight segment will also remain unchanged. Therefore, it can be deduced that when changing the reservation record of a single specific passenger, the main map and seat class table corresponding to the source flight segment will not be changed, nor will the main map and seat class table corresponding to the target flight segment.

[0071] (3) Except for the PNR of a specific passenger, other PNRs on the source and destination flights should not be affected by changes to the passenger reservation records of a single specific passenger.

[0072] Therefore, the seat charts for the source and destination flights will not change, and there is no need to regenerate a new seat chart. Step S203 can be executed directly, thereby simplifying the seat protection process and improving seat protection efficiency.

[0073] If step S202 determines that the reason for the seat protection request is not a change in the reservation record of a single specific passenger, the process ends, and seat protection can be performed according to the existing seat protection procedure. Since the reason for the seat protection request is not a change in the reservation record of a single specific passenger, changes in aircraft type or layout may lead to changes in the seat map. Therefore, it is necessary to read the main maps of the source and target flights, generate a new seat map for the source flight based on the source flight's main map, and generate a new seat map for the target flight based on the target flight's main map. Then, based on the new seat maps of the source and target flights, and according to the seat reserved by the passenger on the new seat map of the source flight, a corresponding seat is re-reserved for the passenger on the new seat map of the target flight. Specifically, all PNR data, main maps, and seat protection rules for the source and target flight segments are reread. The process of matching to obtain the main map is as described above. Figure 1 The relevant descriptions are omitted here. Then, a new seating chart for the source flight is generated based on the main chart of the source flight, and a new seating chart for the target flight is generated based on the main chart of the target flight.

[0074] Then, for each seat in the PNR data for the target segment, based on the attributes and class of the original seat number, it checks whether the attributes and class of the original seat number on the new seat map of the target flight match. If they match, they remain unchanged. If they don't match, then based on the class and attributes of the seat in the PNR, it searches for a matching new seat number in the new seat map of the target flight and assigns it to the PNR, canceling the original seat number. If no matching new seat number can be found, the original seat number is canceled.

[0075] Similarly, for each seat in the source flight segment's PNR data, based on the original seat number's attributes and class, the system checks if the original seat number's attributes and class on the source flight's new seat map match. If a match is found, the original seat remains unchanged. If not, a matching new seat number is found in the source flight's new seat map based on the PNR's seat class and attributes and assigned to that PNR; the original seat number is then cancelled. If no matching new seat number is found, the original seat number is cancelled. Here, the original seat number refers to the seat number in the PNR data before modification, and the new seat number is the seat number obtained after re-matching the seats in the PNR.

[0076] Then, based on the original seat data and seat protection rule data corresponding to the original seat in the passenger's booking record after the aforementioned changes, a new seat on the target flight is assigned to the passenger. The original seat is the seat booked by the specific passenger on the source flight. The new seat is the seat booked by the specific passenger on the target flight. The original seat data is the seat data corresponding to the original seat number in the seat map of the source flight.

[0077] S203. In response to a seat protection request, read flight data, passenger reservation record data, seat protection rule data, and seat map data.

[0078] The flight control system reads flight data, passenger reservation record data, seat protection rule data, and seat map data based on the source and destination flight identification data included in the seat protection request. These data are required for reallocating specific passengers; therefore, upon receiving a seat protection request, the system needs to read these data accordingly.

[0079] The passenger reservation record data in step S203 includes passenger reservation record data for the source flight and passenger reservation record data for the target flight. The passenger reservation record data includes one or more types of data such as the passenger's name, flight segment, date, cabin class, fare, ID number, and seat number. The passenger reservation record data includes at least the passenger reservation record data for the source flight; in other embodiments, it may also include passenger reservation record data for the target flight. Optionally, in a specific embodiment of this application, the passenger reservation record data can be read by: obtaining flight segment data matching the current flight and date (day) based on the read flight data, and obtaining the matching passenger reservation record data based on the obtained flight segment data.

[0080] Seating map data includes seating map data for both the source and target flights. Seating map data can be used to represent the seat distribution of a flight on a given day. Optionally, seating map data can be represented by a matrix, where each element represents a location. Optionally, seating map data specifically includes seat attribute data, seat status data, and seat type data for each seat. Seating attribute data can be found in the preceding introduction to related concepts and will not be repeated here. Seating status data indicates whether a seat has been reserved by a passenger. Seating type data describes the type of seat; specifically, seat types can include free seats, paid seats, X-lock seats, C-lock seats, aisle seats, and unavailable seats.

[0081] Optionally, seat map data can be generated based on master map data. The master map can be understood as the basic template for the seat map. The master map is set by the airline; specifically, it can be obtained by matching the aircraft type, cabin class, and layout parameters of the flight. The cabin class parameters describe the cabin types included in the flight. For example, the cabin class parameters of the source flight include First Class, Business Class, Premium Economy, and Economy Class. The layout parameters describe the number of each cabin class. For example, the layout parameters of the source flight are: 1 First Class, 1 Business Class, 4 Premium Economy, and 5 Economy Class. Optionally, one implementation method for reading seat map data includes: reading the seat map data based on the flight, date (day), and cabin class.

[0082] The seat protection rule data in step S203 includes seat protection rule data for the active flight and seat protection rule data for the target flight. The seat protection rule data includes a seat class table and seat class protection rules. The seat class table specifies the seat class of each seat in the flight's seating chart. Seat classes are predefined value classes by the airline, with different seat classes having different selling prices. Seat class protection rules are used to specify the seat class for new seats assigned to passengers on the target flight. Seat class protection rules generally stipulate that protection can only be applied to seats within the same seat class, unless the airline has defined separate cross-class seat protection rules.

[0083] Optionally, in a specific embodiment of this application, after reading flight data, passenger reservation record data, seat protection rule data, and seat map data, the flight data, passenger reservation record data, seat protection rule data, and seat map data can be verified separately to determine the availability and legality of the data. For example, the verification of flight data can verify whether the source flight and the target flight are controlled flights and whether the seat reservation function is enabled. The verification process of seat map data can include verifying whether the seat map is activated. Another example is the verification process of PNR data, which can include verifying whether there are confirmed PNR data on the flight. If any data in the flight data, passenger reservation record data, seat protection rule data, or seat map data does not meet the availability or legality requirements, the process ends, and seat protection is not implemented.

[0084] In existing technologies, when executing step S203, it is necessary to re-read the main maps of the source and target segments based on the aircraft type and layout of the source and target segments, and then generate the seat map for the source segment based on the main map of the source segment, and the seat map for the target segment based on the main map of the target segment. However, in step S203 of this embodiment, since it has already been determined in step S202 that the seat protection request is a change to the PNR of a single specific passenger, the seat map data corresponding to the source segment and the target segment can be directly read, eliminating the need to regenerate the seat map data. This simplifies the seat protection process and improves its efficiency. It also avoids the problem of affecting the reservation status of other passengers due to regenerating the seat map.

[0085] S204. Based on the original seat data and seat protection rule data corresponding to the original seat in the passenger reservation record, assign a new seat to the specific passenger on the target flight, wherein the original seat is the seat reserved by the specific passenger on the source flight, the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight, and the new seat is the seat reserved by the specific passenger on the target flight.

[0086] Seat data can specifically include seat class, seat attributes, seat number, seat type, seat status, and other relevant seat information. Based on the original seat data and seat protection rules, a new seat on a target flight that matches the original seat data can be assigned according to the seat protection rules. For example, if a specific passenger has booked seat 10A (class 2) in cabin A of the source flight, when applying paid seat protection, a paid seat of class 2 on the target flight's seat map needs to be selected. If a seat is selected, the seat protection is successful, and a new seat on the target flight is successfully assigned to the passenger. If no seat is selected (e.g., all seats of class 2 on the target flight are already occupied), the seat protection fails.

[0087] Optionally, see Figure 3 In a specific embodiment of this application, after performing step S204, the method further includes:

[0088] S301. Modify passenger reservation record data and seat map data according to the new seats.

[0089] The new seat is the seat on the target flight that was reassigned to the specific passenger in step S204 above. When step S204 is successfully executed, that is, a new seat on the target flight is successfully selected for the specific passenger, the passenger's reservation record data and seat map data need to be modified accordingly based on the new seat since the passenger's reserved seat has changed.

[0090] Specifically, during step S301, data related to a specific passenger's original seat reservation in the seat map data and data related to a passenger's original seat reservation in the passenger reservation record are deleted. Data related to a specific passenger's new seat reservation is added to the seat map data and to the passenger reservation record, ensuring that the current passenger reservation record data and seat map data related to the specific passenger are consistent with the data after the new seats are reassigned.

[0091] Optionally, in one specific embodiment of this application, one implementation of step S301 includes:

[0092] In the seating chart data, remove the reserved seat markers from the original seats and add reserved seat markers for new seats. Also, in the passenger reservation records, cancel the original seat reservation records for a specific passenger and generate a new seat reservation record for that specific passenger.

[0093] Specifically, on the seat map of the source flight in the seat map data, the seat reservation mark for a specific passenger in their original seat is removed, and on the seat map of the target flight in the seat map data, a seat reservation mark for the specific passenger in their new seat is added. The seat reservation mark indicates that the seat is reserved. A seat without a reservation mark indicates that the seat is not reserved. The specific form of the seat reservation mark can be varied; for example, it could be a mark of a specific shape, or it could be achieved by changing the color of the seat in the seat map, etc. This application embodiment does not limit this.

[0094] In the retrieved passenger reservation records, it is also necessary to UN (delete) the records of specific passengers booking their original seats and add records of specific passengers booking new seats. Specifically, delete the records of passengers booking their original seats from the source flight's passenger reservation records. Then, add the records of passengers booking new seats to the target flight's passenger reservation records.

[0095] It should be noted that the order of modifying passenger reservation records and modifying seat map data described above is not limited in this application embodiment, and they can also be executed in parallel without affecting the implementation of this application embodiment.

[0096] S302. Synchronize the protection result message representing the seat protection result to the surrounding system, wherein the surrounding system includes at least the seat system.

[0097] The seat protection result is mainly used to explain the changes to the seat map data after executing step S301. There are various specific display formats for the protection result message. For example, the protection result message may include the seat map data of the source flight and the target flight after executing step S301. Or, the protection result message may include the seat map data changed in step S301.

[0098] The surrounding systems can be understood as systems related to seat change information, such as the seat system. After synchronizing the protection result message to the seat system, the seat system can synchronously modify the locally stored seat map for the source and destination flights based on the protection result message. In addition, the surrounding systems may also include computer distribution systems and departure systems.

[0099] S303. Synchronize passenger reservation record change data with the airline's main control system.

[0100] Passenger reservation record change data (i.e., PNR change data) is sent to the airline's main control room to alert all airlines to changes in passenger reservations.

[0101] It should be noted that the order in which steps S302 and S303 are executed does not affect the implementation of the embodiments of this application, and the embodiments of this application do not impose any restrictions on this.

[0102] Optionally, the data can be sent synchronously only to the airlines whose passenger booking record change data is involved, without having to notify all airlines' controllers.

[0103] Optionally, in a specific embodiment of this application, the following is performed: Figure 2 The step S204 shown is followed by:

[0104] If the process of assigning a new seat to a specific passenger on a target flight fails, the original seat reservation mark will be removed from the seat map data, and the passenger's reservation record for the original seat will be cancelled from the passenger reservation record.

[0105] As described above regarding step S204, in certain situations, such as when a new seat meeting the seat protection rules cannot be selected on the target flight, or when a new seat meeting the seat protection rules exists on the target flight but is already occupied and unavailable, step S204 may fail, and a new seat on the target flight may not be successfully assigned to the specific passenger. In such cases, the occupied seat marker for the original seat is simply removed from the seat map data of the source flight, and the passenger's reservation record for the original seat is cancelled in the passenger reservation record of the source flight. That is, a new seat is not assigned to the specific passenger, but the original seat is cancelled to meet the seat protection request. Subsequently, after learning that the reserved original seat has been cancelled, the specific passenger can rebook a seat according to their actual situation.

[0106] It should be noted that the order in which the original seat reservation mark is removed from the seat map data and the record of a specific passenger's original seat reservation is removed from the passenger reservation record does not affect the implementation of the embodiments of this application, and the embodiments of this application do not impose any restrictions on this.

[0107] The seat protection method provided in this embodiment of the invention, upon receiving a seat protection request, if the triggering reason for the seat protection request is a change in the passenger reservation record of a specific passenger, directly reads flight data, passenger reservation record data, seat protection rule data, and seat map data in response to the seat protection request. Then, it directly assigns a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger reservation record and the seat protection rule data. Since changing the passenger reservation record data of a specific passenger does not involve changes in the aircraft type, layout, or seat protection rules of the source and target flight segments, and other passenger reservation record data are unaffected except for the specific customer's passenger reservation record data, it is not necessary to regenerate a new seat map for the source flight and a new seat map for the target flight to directly assign a new seat on the target flight to the specific passenger. This is not only simpler than the existing seat protection process, but also avoids changes in the reserved seats of passengers other than the specific passenger due to the regeneration of a new seat map, thus improving the processing efficiency of seat protection requests and passenger experience.

[0108] See Figure 4a Based on the above Figure 2 The seat protection method shown in this application embodiment also proposes another seat protection method, which specifically includes the following steps:

[0109] S401. Receive a seat protection request, wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection.

[0110] The execution process and principle of step S401 can be found in the aforementioned text. Figure 2 Step S201 shown will not be repeated here.

[0111] S402. Determine whether the reason for triggering the seat protection request is a change in the passenger reservation record of a specific passenger.

[0112] If step S402 determines that the reason for triggering the seat protection request is a change in the passenger reservation record of a specific individual passenger, then step S403 is executed. If step S402 determines that the reason for triggering the seat protection request is not a change in the passenger reservation record of a specific individual passenger, then the process ends, that is, the existing seat protection process continues to be executed.

[0113] The execution process and principle of step S402 can be found in the aforementioned text. Figure 2 Step S202 shown will not be repeated here.

[0114] S403. In response to the seat protection request, read the flight data and determine whether the segment information of the source flight is the same as the segment information of the target flight.

[0115] The flight data includes at least the segment information of the source flight and the segment information of the target flight. The segment information includes the flight number, departure point, destination, and flight date. The flight data can be retrieved based on the representation data of the source and target flights in the seat protection request. A description of the flight data can be found above. Figure 2 The relevant description of step S203 shown will not be repeated here.

[0116] From the retrieved flight data, the segment information of the source flight and the target flight can be obtained, thus determining whether the segment information of the source flight is the same as that of the target flight. Specifically, if the flight number, departure point, destination, and flight date of the source flight are exactly the same as those of the target flight, then the segment information of the source flight is considered to be the same as that of the target flight. Otherwise, it is determined that the segment information of the source flight is not the same as that of the target flight.

[0117] When step S403 determines that the segment information of the source flight is the same as that of the target flight, steps S404 and S405 are executed. When step S403 determines that the segment information of the source flight is different from that of the target flight, it means that the source flight and the target flight do not share the same segment, therefore steps S406 to S409 are executed. That is, the seat protection process executed when the segment information is determined to be the same differs from the process executed when the segment information is determined to be different, in order to further improve the processing efficiency of seat protection requests. See the subsequent description of steps S404 to S408 for details.

[0118] S404: Read flight data, passenger reservation record data, seat protection rule data, and seat map data.

[0119] The execution process and principle of step S404 can be referred to the above. Figure 2 Step S203 shown will not be repeated here.

[0120] S405. Based on the original seat data and seat protection rule data corresponding to the original seat in the passenger reservation record, assign a new seat to the specific passenger on the target flight.

[0121] The execution process and principle of step S405 can be referred to the aforementioned step S204, and will not be repeated here.

[0122] Optionally, see Figure 4b One implementation of step S405 includes:

[0123] S4051. Based on the original seat data and seat protection rule data corresponding to the original seat in the passenger reservation record, determine whether the seat number of the original seat is available in the seat map of the target flight.

[0124] The original seat number refers to the seat number reserved by a specific passenger on the source flight. For example, if a specific passenger reserved seat number 32A on the source flight, then the original seat number corresponds to seat 32A in the seat map of the target flight.

[0125] If it is determined that the seat number of the original seat is unavailable in the seat map of the target flight, then proceed to step S4052. If it is determined that the seat number of the original seat is available in the seat map of the target flight, and since step S403 has already determined that the segment information of the source flight is the same as that of the target flight, the seat map data of the source flight is also consistent with that of the target flight. Therefore, there is no need to reassign a new seat, and the original seat reserved by the specific passenger can continue to be used. That is, the process ends without reassigning a new seat to the specific passenger, thereby simplifying the seat protection process and improving the efficiency of seat protection.

[0126] Optionally, see Figure 4c In one specific embodiment of this application, one implementation of step S4051 includes:

[0127] S501. From the seat map data and seat protection rule data, obtain the seat data and original seat data corresponding to the original seat number in the seat map of the target flight. The seat data includes at least seat attribute data and seat class data.

[0128] The relevant information regarding seat map data and protection rule data can be found in step S203 above, and will not be repeated here. Specifically, during step S501, the seat number of the original seat reserved by the specific passenger is first obtained from the PNR data. Then, from the source flight's seat map data, seat attribute data and other seat data are read using the original seat number. Next, from the source flight's seat map data and seat protection rule data, the corresponding seat class data for the original seat number is read using the original seat number. Furthermore, from the target flight's seat map data, seat attribute data and other seat data for the original seat number in the target flight's seat map are read using the original seat number. Finally, from the target flight's seat map data and seat protection rule data, the corresponding seat class data for the original seat number in the target flight's seat map is read using the original seat number.

[0129] S502. Determine whether the seat data corresponding to the original seat number in the seat map of the target flight matches the original seat data.

[0130] Specifically, if the seat number of the original seat is found to match the corresponding seat data in the target flight's seat map, then the seat corresponding to the original seat number in the target flight's seat map is available. If the seat number of the original seat is not found in the target flight's seat map, then the seat corresponding to the original seat number in the target flight's seat map is unavailable.

[0131] It should be noted that if the seat attribute data and seat class data corresponding to the original seat number in the seat map of the target flight are consistent with the seat attribute data and seat class data in the original seat data, it means that the seat data corresponding to the original seat number in the seat map of the target flight matches the original seat data; otherwise, it means that they do not match.

[0132] S4052. Select a seat in the seat map of the target flight that matches the original seat data of the specific passenger in the passenger reservation record.

[0133] Since step S403 has already determined that the segment information of the source flight is the same as that of the target flight, the seat map of the target flight in step S4052 is essentially the same as the seat map of the source flight. Because the original seat number is unavailable in the target flight's seat map, it is necessary to reselect a seat for the specific passenger on the target flight's (the target flight in step S4053 is the source flight) seat map that matches the original seat data in the passenger's booking record. The relevant information about the original seat data can be found in step S204 above, and will not be repeated here.

[0134] Optionally, the seat data includes at least seat attribute data and seat class data. The seat in the target flight's seat map that matches the original seat data refers to an unoccupied (i.e., unreserved) seat in the target flight's seat map that has the same seat attribute data and seat class data as the original seat data.

[0135] When executing step S4052, there are two possible outcomes: either a seat matching the original seat data of the specific passenger in the passenger reservation record is selected in the seat map of the target flight, or no seat matching the original seat data of the specific passenger in the passenger reservation record is selected in the seat map of the target flight.

[0136] If step S4052 selects a seat in the seat map of the target flight that matches the original seat data corresponding to the original seat in the passenger reservation record of the specific passenger, then step S4053 is executed.

[0137] If step S4052 fails to select a seat in the seat map of the target flight that matches the original seat data corresponding to the original seat in the passenger reservation record of the specific passenger, the process can be terminated directly, i.e., seat protection fails, or step S4054 can be executed.

[0138] S4053. The selected seat is used as a new seat and assigned to a specific passenger, and the original seat of the specific passenger is cancelled.

[0139] Optionally, after performing step S4053, the aforementioned steps can also be performed. Figure 3 The process shown will not be repeated here.

[0140] S4054. Cancel the original seat of a specific passenger.

[0141] The process of canceling a specific passenger's original seat is as follows: On the seat map of the source flight in the seat map data, the seat reservation mark for the specific passenger in the original seat is removed. In the retrieved passenger reservation records, the record of the specific passenger's original seat reservation is deleted (UN).

[0142] Optionally, in a specific embodiment of this application, the method for triggering step S4054 may be as follows: if, in step S4052, it is determined that no seat matching the original seat data corresponding to the original seat in the passenger's reservation record is selected in the seat map of the target flight, then it is marked that only the original seat of the specific passenger is cancelled. When it is detected that only the original seat of the specific passenger is cancelled, step S4054 is triggered.

[0143] S406. Determine whether the target flight has been initialized.

[0144] Flight initialization can be understood as the stage where the departure system has established the flight plan. Before the target flight is initialized, the flight plan for the target flight is only created in the flight control system; the departure system has not yet created a flight plan for the source flight. During this pre-initialization stage, seat reservations and seat map generation control for the target flight are handled by the seat management system. When the target flight enters the flight initialization stage, the departure system creates the flight plan for the target flight and then receives the passenger list report from the flight control system. Subsequent reservation operations and seat map generation control for the target flight are then handled by the departure system.

[0145] The flight plans for target flights created by the departure system are based on the actual operation of the airlines. The flight plans for target flights created by the departure system may not be completely consistent with the flight plans created by the flight control system in the uninitialized phase. For example, the aircraft type may change depending on the current operating conditions.

[0146] The flight control system sends a passenger list report to the departure system. The passenger list report contains key data from the passenger reservation records of the flight, thereby achieving the purpose of synchronizing the passenger reservation record data of the current flight with the departure system.

[0147] Optionally, in one specific embodiment of this application, one implementation of step S406 includes:

[0148] The system determines whether the flight control system has sent the passenger list for the target flight to the departure system. If the flight control system has sent the passenger list for the source flight to the departure system, the target flight is determined to have been initialized. If the flight control system has not sent the passenger list for the target flight to the departure system, the target flight is determined not to have been initialized. The passenger list for the target flight must include at least key data related to passenger booking records.

[0149] Optionally, one implementation of determining whether the flight control system has sent the passenger list report of the target flight to the departure system is as follows: the flight control system reads the flight data of the target flight based on the identification data of the target flight carried in the seat protection request, and then determines whether the passenger list report of the source flight has been sent to the departure system (i.e., whether the target flight has been initialized) based on the flight data of the target flight.

[0150] If it is determined that the target flight has been initialized, it is considered that the target flight is about to depart, and the PNR data and seat map data of the target flight are not suitable for further modification. That is, it is not possible to reassign new seats on the target flight to specific passengers. Therefore, step S407 is executed directly.

[0151] If it is determined that the target flight has not been initialized, it means that seats can be reassigned to specific passengers, so step S408 is executed.

[0152] S407. Cancel the original seat of a specific passenger.

[0153] Specifically, the seat reservation mark for the original seat is removed from the seat map data of the source flight, and the reservation record for the original seat for a specific passenger is cancelled in the passenger reservation record. That is, a new seat on the target flight is not assigned to the specific passenger and the original seat of the specific passenger is cancelled to meet the needs of the seat protection request. After the specific passenger learns that the original seat reservation has been cancelled, he / she can rebook the seat according to his / her actual situation.

[0154] It should be noted that the order in which the original seat reservation mark is removed from the seat map data and the passenger reservation record is removed from the passenger reservation record does not affect the implementation of the embodiments of this application, and the embodiments of this application do not limit this.

[0155] In this embodiment of the application, when it is determined that the target flight has been initialized, only the original seat of the specific passenger is canceled, and no new seat of the target flight is assigned to the specific passenger, which simplifies the seat protection process and improves the processing efficiency of seat protection requests.

[0156] Optionally, in a specific embodiment of this application, the execution step S407 can be triggered by marking that only the original seats of specific passengers are cancelled when it is determined in step S406 that the target flight has been initialized. When it is detected that only the original seats of specific passengers are cancelled, the execution step S407 is triggered.

[0157] S408: Read flight data, passenger reservation record data, seat protection rule data, and seat map data.

[0158] Since the segment information of the source flight is different from that of the target flight, and the target flight has not yet been initialized, it is still possible to assign new seats to specific passengers from the target flight's seating chart. Before assigning new seats, it is necessary to first read the flight data, passenger reservation record data, seat protection rule data, and seating chart data required for reallocating new seats.

[0159] The execution process and principle of step S408 can be referred to the above. Figure 4a Step S404, as shown, will not be repeated here.

[0160] S409. Based on the original seat data and seat protection rule data corresponding to the original seat in the passenger's booking record, assign a new seat on the target flight to the specific passenger.

[0161] The execution process and principle of step S409 can be referred to the aforementioned step S405, and will not be repeated here.

[0162] Optionally, see Figure 4d In one specific embodiment of this application, one implementation of step S409 includes:

[0163] S4091. Based on the original seat data and seat protection rule data corresponding to the original seat in the passenger reservation record, determine whether the seat number of the original seat is available in the seat map of the target flight.

[0164] The execution process and principle of step S4091 can be referred to the aforementioned step S4051. The main difference is that the source segment and the target segment are the same in step S4051, while the source segment and the target segment are different in step S4091. This will not be elaborated here.

[0165] If step S4091 determines that the seat number of the original seat is available in the seat map of the target flight, then proceed to step S4092. If step S4091 determines that the seat number of the original seat is not available in the seat map of the target flight, then proceed to step S4093.

[0166] S4092. The original seat number is assigned as the new seat in the target flight's seating chart, and the original seat of the specific passenger is cancelled.

[0167] Since the original seat number has a corresponding available seat in the target flight's seating chart, it can be reassigned as a new seat to a specific passenger. After the seat is reassigned, although the source flight has changed to the target flight, the seat number, seat class data, and seat attribute data remain consistent with the specific passenger's original seat, thus protecting the seat and improving the passenger experience for the specific passenger.

[0168] The process and principles for allocating new seats to specific passengers and canceling their original seats can be found in the aforementioned text. Figure 4b The difference between step S4053 and step S4092 is that the new seat in step S4053 is selected, while in step S4092 the seat number of the original seat is used directly as the seat corresponding to the seat in the target flight's seat map. Also, in step S4053 the source segment and the target segment are the same, while in step S4092 the source segment and the target segment are different.

[0169] S4093. Select a seat in the seat map of the target flight that matches the original seat data of the specific passenger in the passenger reservation record.

[0170] Since the original seat number is not available in the target flight's seat map, it is necessary to select a seat from all seats in the target flight's seat map that matches the original seat data of the specific passenger in the passenger's booking record.

[0171] The execution process and principle of step S4093 can be referred to the above. Figure 4b The only difference between step S4052 and step S4093 is that the source segment and the target segment are the same in step S4052, while they are different in step S4093. This will not be elaborated further here.

[0172] If a seat matching the original seat data of a specific passenger in the passenger reservation record is selected in step S4093, then step S4094 is executed. If no seat matching the original seat data of a specific passenger in the passenger reservation record is selected in step S4093, the process can be terminated directly, i.e., seat protection fails, or step S4095 is executed.

[0173] S4094. The selected seat is used as a new seat and assigned to a specific passenger, and the original seat of the specific passenger is cancelled.

[0174] The execution process and principle of step S4094 can be referred to the above. Figure 4b The only difference between step S4053 and step S4094 is that the source segment and the target segment are the same in step S4053, while they are different in step S4094. This will not be elaborated further here.

[0175] S4095. Cancel the original seat of a specific passenger.

[0176] The execution process and principle of step S4095 can be referred to the above. Figure 4b The only difference between step S4054 and step S4095 is that the source segment and the target segment are the same in step S4054, while they are different in step S4095. This will not be elaborated further here.

[0177] For example, in a specific application scenario of any of the seat protection methods proposed in the embodiments of this application, during the processing of a seat protection request for a single specific passenger's PNR change: relevant fields of a PNR are extracted, such as... Figure 5a As shown, the "**ELECTRONIC TICKET PNR**" field represents the electronic ticket PNR. In serial numbers 1 to 4: "TEST / ATEST / B" is the passenger's name. "NWS8S1" is the identification data for this PNR. "CZ2878" is the flight number, "N" indicates N class, "SU" indicates Tuesday, "12JUN" is the flight date in the PNR, "WUHCKG" indicates the departure and destination is Wuhan to Chongqing, and "RR3" indicates three tickets purchased and confirmed. "1145" is the departure time, "1315" is the arrival time, "E" indicates the electronic ticket segment, and "T3" indicates gate T3.

[0178] In section 5, the "4006817206" field is the phone number, and "B2C" is the channel name. In section 6, "T" is the ticketing identifier, and "APT" is the channel name. In section 7, the "BA" field is the settlement identifier, and "ECARD ALDY PAMTOT CNY" indicates that payment has been settled in Chinese. In section 8, "SSR" is the special service identifier. "SEAT" is the seat selection service identifier. "CZ HK1 WUHCKG" is the airline. "HK1" is the action code. "WUHCKG" is the flight segment. "2878" is the flight number, and "N12JUN" is the cabin class and date. "41CN / P3 / RS" indicates seat number / area / unissued ticket identifier. The meanings of the fields in parts 9 and 10 can be found in the explanation in part 8 above, and will not be repeated here. In part 11, "SSR" is the special service identifier, "FOID" is the ID card number, CZ is the airline, HK1 is the travel code, "NI421122198805117XXX" is the ID card identifier and ID card number, and P1 is the passenger serial number.

[0179] Figure 5a The seating chart shown is for the segment in the PNR (i.e., flight number CZ2878, N class, date 12JUN, departure and destination WUHCKG). Figure 5b As shown, where Figure 5b In this diagram, N represents a region identifier, [ represents the wing area, * indicates that the seat is free and available for purchase, ! indicates that the seat has been sold, X indicates that the seat is locked and cannot be purchased, =" represents an aisle, E represents an entrance / exit, R represents the right side, L represents the left side, and A / B / C / H / J / K are column numbers from left to right. "3 / 4 / 5" represents the starting row number; for example, 3 represents 30, and adding 5 below indicates that this row is the 35th row. Figure 5b As can be seen, 41A, 41B, and 41C are free seats on the left. 41A is by the window, and 41C is by the aisle. The three of them are traveling together and are seated in the same row, but not in the first row.

[0180] Continue searching and Figure 5a The list of other flights on the same route as the affected PNR shows, for example: Figure 5c The fields shown. Among them, Figure 5c The “12JUN(SUN)WUHCKG VIA CZ” shown indicates a list of CZ Airlines flights from Wuhan to Chongqing on the date of 21JUN. Figure 5c In section 1, "CZ6175" is the flight number, "WUHCKG" indicates the departure and destination is Wuhan to Chongqing, "0725" is the departure time of CZ6175, "0855" is the arrival time of CZ6175, and "73D0" indicates the aircraft type is 73D 0daychange. "S" indicates ASR functionality, "E" indicates an electronic ticket, and "JA" indicates that the J cabin status is A. The meanings of the remaining fields "CA", "DA", "IA", etc., are similar to those of the "JA" field and will not be repeated here. "T3" indicates gate T3. The meanings of the fields in sections 2 and 3 are similar to those in section 1 and will not be repeated here.

[0181] because Figure 5c The search results for CZ5769 show that it is controlled by the same airline as the original flight CZ2878, which meets the airline's seat protection requirements. Therefore, the flight is selected. Figure 5c Flight CZ5769 was selected as the target flight. The seating chart for flight CZ5769, N class, flight date 12JUN, departure and destination WUHCKG was viewed to obtain the following information. Figure 5d The fields shown. Among them, Figure 5d The meanings of the symbols in the fields can be found in the preceding text. Figure 5b The relevant descriptions are omitted here. Figure 5dAs shown in the seating chart, seats 41A, 41B, and 41C are also free seats, just like in the seating chart for CZ2878. Furthermore, none of them are in the first row; 41A is by the window, and 41C is by the aisle. 41A, 41B, and 41C are consecutive seats on the left side. Therefore, it can be considered... Figure 5a The PNR shown for NWS8S1 was assigned from Class N of flight CZ2878, flight date 12JUN, to Class N of flight CZ5769, flight date 12JUN.

[0182] In this case, the segment information of the source flight is different from that of the target flight, and the seat data of the original seat number on the seat map of the target flight completely matches the original seat data of the original seat number on the seat map of the source flight. Therefore, seats 41A, 41B, and 41C on CZ5769 / 12JUN were assigned to... Figure 5a The PNR of NWS8S1 is shown. The specific PNR change fields after assigning a new seat are as follows: Figure 5e As shown. Among them, Figure 5e The descriptions of each field can be found in the preceding text. Figure 5a This will not be elaborated upon here. Figure 5e Fields 4 and 5 show that three reserved seats in CZ2878 were unreserved (UN), while three new seats (TK) were added in CZ5769. Fields 9 through 11 show that seats 41A, 41B, and 41C were unreserved in CZ2878. Fields 12 through 14 show that seats 41A, 41B, and 41C were newly reserved in CZ5769.

[0183] After seat protection, the seating chart for flight CZ5769, N class, flight date 12JUN, departure and destination WUHCKG is as follows: Figure 5f As shown, Figure 5f As can be seen from the seating chart of the target flight CZ5769, seats 41A, B, and C are already occupied.

[0184] After seat protection, the seating chart for flight CZ2878, N class, flight date 12JUN, departure and destination WUHCKG is as follows: Figure 5g As shown, it can be seen that compared to Figure 5b , Figure 5g The seat reservation signs for seats 41A, 41B, and 41C have been removed.

[0185] After modifying the seat map and PNR data for the source and target flights, a protection result message characterizing the seat protection outcome is sent to surrounding systems. This message is as follows: Figure 5h As shown, Figure 5hThe “SITRMCZ” shown is the message destination address, “.PEKRMCA 1E / 291559” is the message source address, and “SEAT-PROT-START” indicates the start of the protection result message.

[0186] “SITTXNID / 0000872022032162302452000” is the transaction ID.

[0187] “FR:CZ2878 / 12JUN22” indicates that the source flight number is CZ2878 and the departure date is 12JUN22 (i.e., June 12). “TO:CZ5769 / 12JUN22” indicates that the target flight number is CZ5769 and the departure date is 12JUN22 (i.e., June 12). “SEAT-PROT-END” indicates the end of the protection result message. “1 / CZ2878 / 12JUN22 WUHCKG / Y / 46K / 46J / 48K” indicates that after the seat protection ends, the booked seats for flight CZ2878 are 46K, 46J, and 48K. "2 / CZ5769 / 12JUNWUHCKG / Y / 41A / 41B / 41C / 41K" indicates that after the seat protection period ends, the reserved seats for CZ5769 are 41A, 41B, 41C, and 41K.

[0188] Optionally, see Figure 6 Based on the seat protection method proposed in the above embodiments of this application, this application proposes a seat protection component diagram. In the seat protection method proposed in this application, data can be initialized in advance in the initial stage, and then triggered to enter the data reading and verification stage after receiving a seat protection request. In the data reading and verification stage, data reading and verification can be achieved through a component for reading flight data, verifying flight data, determining whether the flight has been initialized, reading seat map data, verifying seat map data, reading PNR data, verifying PNR data, reading seat protection rule data, determining whether the source segment is the same as the target segment, and verifying seat protection rule data.

[0189] Specifically, the flight data reading component retrieves the corresponding flight data based on the flight number. The flight data verification component verifies whether the retrieved flight data belongs to a controlled flight and whether the seat reservation function is enabled (i.e., verifies the availability and legality of the flight data). The seat map data reading component retrieves seat map data based on the flight, date, and cabin class. The seat map data verification component verifies the legality and availability of the seat map data. The PNR data reading component retrieves PNR data matching the flight segment data included in the flight data. The PNR data verification component verifies the legality and availability of the PNR data. The seat protection rule data reading component retrieves seat protection rule data, and the seat protection rule data verification component verifies the legality and availability of the seat protection rule data. The "Determine if Initialized Flight" component determines whether the source flight has been initialized. If initialized, it calls the departure system to execute seat protection; if not initialized, the flight control system directly executes seat protection. The "Determine if Source Segment is the Same as Target Segment" component determines whether the segment information of the source flight is equal to the segment information of the target flight.

[0190] Continue reading Figure 6 In the seat protection method proposed in this application, seat protection is implemented during the seat protection phase through a seat reassignment component, a seat map data modification component, a PNR data modification / synchronization component, and a next-processing system invocation component. The seat reassignment component allocates a new seat on the target flight to the passenger based on the original seat data and seat protection rule data in the passenger's booking record. The PNR data modification / synchronization component modifies the PNR data and synchronizes the PNR change data based on the execution result of the reassignment component (i.e., whether the allocation of a new seat is successful or unsuccessful). The seat map data modification component modifies the seat map data based on the execution result of the reassignment component. The next-processing system invocation component, if the current system determines that the current seat protection request is not within its responsibility, invokes the next system for processing, allowing the next system to continue processing the current seat protection request.

[0191] Continue reading Figure 6 In the seat protection method proposed in this application embodiment, during the data synchronization phase, seat protection result synchronization is achieved through a seat protection result synchronization component. The seat protection result synchronization component is used to synchronize the protection result message representing the seat protection result to the surrounding system.

[0192] It should be noted that, Figure 6 The execution process and principle of each component shown can be referred to the seat protection method proposed in the aforementioned embodiments of this application, and will not be repeated here.

[0193] See Figure 7Based on the seat protection method proposed in the above embodiments of this application, this application proposes a seat protection device, which includes: a receiving unit 701, a first reading unit 702, and a seat protection unit 703.

[0194] The receiving unit 701 is used to receive seat protection requests. The seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection.

[0195] The first reading unit 702 is used to read flight data, passenger reservation record data, seat protection rule data, and seat map data in response to a seat protection request if the reason for triggering the seat protection request is a change in the passenger reservation record of a specific passenger.

[0196] The seat protection unit 703 is used to assign a new seat on a target flight to a specific passenger based on the original seat data corresponding to the original seat in the passenger's booking record and the seat protection rule data. The original seat is the seat booked by the specific passenger on the source flight. The original seat data is the seat data corresponding to the original seat number in the seat map of the source flight. The new seat is the seat booked by the specific passenger on the target flight.

[0197] Optionally, in a specific embodiment of this application, it further includes: a first determining unit and a first judging unit.

[0198] The first determining unit is used to read flight data and determine whether the segment information of the source flight is the same as the segment information of the target flight.

[0199] The first judgment unit is used to determine whether the target flight has been initialized if it is determined that the segment information of the source flight is not the same as the segment information of the target flight.

[0200] The seat protection unit 703 includes a first seat protection unit subunit, which is used to assign a new seat on the target flight to a specific passenger if the segment information of the source flight is not the same as the segment information of the target flight and the target flight has not been initialized, or if the segment information of the source flight is the same as the segment information of the target flight, based on the original seat data corresponding to the original seat in the passenger reservation record and the seat protection rule data.

[0201] Optionally, in a specific embodiment of this application, it further includes: a first cancellation unit, used to cancel the original seat of a specific passenger if the segment information of the source flight is not the same as the segment information of the target flight and the target flight has been initialized.

[0202] Optionally, in a specific embodiment of this application, when the first seat protection unit subunit assigns a new seat on the target flight to a specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, it is used for:

[0203] Based on the original seat data and seat protection rules data of the original seat in the passenger's booking record, determine whether the seat number of the original seat is available in the seat map of the target flight.

[0204] If it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is not the same as the segment information of the target flight, then the seat number of the original seat is used as the new seat in the seat map of the target flight and assigned to the specific passenger, and the original seat of the specific passenger is cancelled.

[0205] If it is determined that the original seat number is unavailable in the seat map of the target flight, then a seat that matches the original seat data of the specific passenger in the passenger booking record will be selected in the seat map of the target flight.

[0206] If a seat matching the original seat data of a specific passenger in the passenger booking record is selected in the seat map of the target flight, the selected seat will be assigned as the new seat to the specific passenger, and the specific passenger's original seat will be cancelled.

[0207] Optionally, in a specific embodiment of this application, when the first seat protection unit subunit performs the function of determining whether the seat number of the original seat is available in the seat map of the target flight based on the original seat data and seat protection rule data corresponding to the original seat in the passenger reservation record of a specific passenger, it is used for:

[0208] From the seat map data and seat protection rule data, obtain the seat data corresponding to the original seat number in the target flight's seat map, as well as the original seat data. The seat data includes at least seat attribute data and seat class data.

[0209] Determine whether the seat number of the original seat matches the seat data in the seat map of the target flight.

[0210] If the seat number of the original seat matches the seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is available.

[0211] If the seat number of the original seat does not match the corresponding seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is unavailable.

[0212] Optionally, in a specific embodiment of this application, it further includes: a termination unit and a second cancellation unit.

[0213] The termination unit is used to end the process if it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is the same as the segment information of the target flight.

[0214] The second cancellation unit is used to cancel the original seat of a specific passenger if no seat matching the original seat data in the passenger reservation record is selected in the seat map of the target flight.

[0215] Optionally, in a specific embodiment of this application, it further includes: a modification unit and a synchronization unit.

[0216] The modification unit is used to modify passenger reservation record data and seat map data based on the new seats.

[0217] The synchronization unit is used to synchronize the protection result message, which represents the seat protection result, to the surrounding systems. It also synchronizes passenger reservation record change data to the airline's main control system. The surrounding systems include at least the seat system.

[0218] The execution process and principle of each unit and subunit in the seat protection device proposed in this application embodiment can be found in the seat protection method proposed in the aforementioned embodiment of this application, and will not be repeated here.

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

[0220] In the seat protection device proposed in this application embodiment, after receiving a seat protection request, if the triggering reason for the seat protection request is a change in the passenger reservation record of a specific passenger, the first reading unit 702 responds to the seat protection request by directly reading flight data, passenger reservation record data, seat protection rule data, and seat map data. Then, the seat protection unit 703 directly assigns a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger reservation record and the seat protection rule data. Since the passenger reservation record data of a specific passenger does not involve changes in the aircraft type, layout, or seat protection rules of the source and target flights, and other passenger reservation record data are unaffected except for the specific customer's passenger reservation record data, it is not necessary to regenerate a new seat map for the source flight and a new seat map for the target flight to directly assign a new seat on the target flight to the specific passenger. This is not only simpler than the existing seat protection process, but also avoids changes in the reserved seats of passengers other than the specific passenger due to the regeneration of a new seat map, thus improving the processing efficiency of seat protection requests and passenger experience.

[0221] This application also discloses an electronic device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program, specifically for implementing the seat protection method as described in any of the preceding embodiments.

[0222] The following is for reference. Figure 8 This illustration shows a structural diagram of an electronic device (e.g., a terminal device or a server) 800 suitable for implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0223] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 806 into a random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the electronic device 800. The processing device 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0224] Typically, the following devices can be connected to I / O interface 805: input devices 806 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 807 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 806 including, for example, magnetic tapes, hard disks, etc.; and communication devices 809. Communication device 809 allows electronic device 800 to communicate wirelessly or wiredly with other devices to exchange data. Although... Figure 8 An electronic device 800 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.

[0225] This application also discloses a computer-readable medium for storing a computer program, which, when executed, is specifically used to implement the seat protection method as described in any of the first aspects above.

[0226] It should be noted that the computer-readable 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 connection 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 can be any computer-readable 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 computer-readable 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.

[0227] The aforementioned computer-readable medium may be contained within an electronic device; or it may exist independently and not assembled into the electronic device.

[0228] According to one or more embodiments of this disclosure, this application is as follows Figure 4a The illustrated embodiment provides a seat protection method, the method comprising:

[0229] Receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection;

[0230] If the seat protection request is triggered by a change in the passenger reservation record of a specific individual passenger, then in response to the seat protection request, flight data, passenger reservation record data, seat protection rule data, and seat map data are read.

[0231] Based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, a new seat is assigned to the specific passenger on the target flight; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight.

[0232] Optional, according to Figure 4a In the illustrated embodiment, before reading flight data, passenger reservation record data, seat protection rule data, and seat map data, the following steps are also included:

[0233] Read flight data to determine whether the segment information of the source flight is the same as the segment information of the target flight;

[0234] If it is determined that the segment information of the source flight is not the same as the segment information of the target flight, then it is determined whether the target flight has been initialized.

[0235] The step of allocating a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data includes:

[0236] If the segment information of the source flight is not the same as the segment information of the target flight and the target flight has not been initialized, or if the segment information of the source flight is the same as the segment information of the target flight, then a new seat on the target flight is assigned to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data.

[0237] Optional, according to Figure 4a The illustrated embodiment also includes:

[0238] If the segment information of the source flight is not the same as the segment information of the target flight and the target flight has been initialized, then the original seat of the specific passenger is cancelled.

[0239] Optional, according to Figure 4a The embodiment shown includes, in this step, allocating a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, comprising:

[0240] Based on the original seat data corresponding to the original seat in the passenger booking record of the specific passenger and the seat protection rule data, determine whether the seat number of the original seat is available in the seat map of the target flight;

[0241] If it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is not the same as the segment information of the target flight, then the seat number of the original seat is used as the new seat in the seat map of the target flight and assigned to the specific passenger, and the original seat of the specific passenger is cancelled.

[0242] If it is determined that the seat number of the original seat is unavailable in the seat map of the target flight, then a seat that matches the original seat data of the specific passenger in the passenger booking record is selected in the seat map of the target flight.

[0243] If a seat is selected in the seat map of the target flight that matches the original seat data of the specific passenger in the passenger booking record, the selected seat will be assigned as a new seat to the specific passenger, and the specific passenger's original seat will be cancelled.

[0244] Optional, according to Figure 4a The embodiment shown includes determining whether the seat number of the original seat is available in the seat map of the target flight based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data.

[0245] From the seat map data and the seat protection rule data, obtain the seat data and original seat data corresponding to the original seat number in the seat map of the target flight; wherein, the seat data includes at least seat attribute data and seat class data;

[0246] Determine whether the seat data corresponding to the original seat number in the seat map of the target flight matches the original seat data;

[0247] If the seat number of the original seat matches the seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is available.

[0248] If the seat number of the original seat does not match the seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is unavailable.

[0249] Optional, according to Figure 4a In the illustrated embodiment, after determining that the seat number of the original seat corresponds to an available seat in the seat map of the target flight, the method further includes:

[0250] If it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is the same as the segment information of the target flight, then the process ends.

[0251] After selecting a seat in the seat map of the target flight that matches the original seat data corresponding to the original seat of the specific passenger in the passenger booking record, the method further includes:

[0252] If no seat matching the original seat data of the specific passenger in the passenger booking record is selected in the seat map of the target flight, the original seat of the specific passenger will be cancelled.

[0253] Optional, according to Figure 4a In the illustrated embodiment, after allocating a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, the method further includes:

[0254] Modify the passenger reservation record data and the seat map data according to the new seats;

[0255] The protection result message representing the seat protection result is synchronized to the surrounding systems; and the passenger reservation record change data is synchronized to the airline's main control system; wherein, the surrounding systems include at least the seat system.

[0256] According to one or more embodiments of this disclosure, this application is as follows Figure 7 The illustrated embodiment provides a seat protection device, the seat protection device comprising:

[0257] A receiving unit is used to receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the triggering reason for seat protection;

[0258] The first reading unit is used to read flight data, passenger reservation record data, seat protection rule data, and seat map data in response to the seat protection request if the triggering reason of the seat protection request is a change in the passenger reservation record of a single specific passenger.

[0259] A seat protection unit is used to assign a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight.

[0260] According to one or more embodiments of this disclosure, this application also discloses an electronic device, including a memory and a processor;

[0261] The memory is used to store computer programs;

[0262] The processor is used to execute the computer program, specifically to implement the seat protection method as described in any of the above.

[0263] According to one or more embodiments of this disclosure, this application also discloses a computer-readable medium for storing a computer program, which, when executed, is specifically used to implement the seat protection method as described in any of the foregoing embodiments.

[0264] 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.

[0265] 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.

[0266] 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 seat protection method, characterized in that, include: Receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the reason for triggering seat protection; If the seat protection request is triggered by a change in the passenger reservation record of a specific passenger, then in response to the seat protection request, flight data, passenger reservation record data, seat protection rule data, and seat map data are read. Based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, a new seat is assigned to the specific passenger on the target flight; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight. Before reading flight data, passenger reservation record data, seat protection rule data, and seat map data, the process also includes: Read flight data to determine whether the segment information of the source flight is the same as the segment information of the target flight; If it is determined that the segment information of the source flight is not the same as the segment information of the target flight, then it is determined whether the target flight has been initialized; wherein, if the flight control system has sent the passenger list of the target flight to the departure system, then it is determined that the target flight has been initialized. The step of allocating a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data includes: If the segment information of the source flight is not the same as the segment information of the target flight and the target flight has not been initialized, or if the segment information of the source flight is the same as the segment information of the target flight, then a new seat on the target flight is assigned to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data.

2. The method according to claim 1, characterized in that, Also includes: If the segment information of the source flight is not the same as the segment information of the target flight and the target flight has been initialized, then the original seat of the specific passenger is cancelled.

3. The method according to claim 1, characterized in that, The step of assigning a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data includes: Based on the original seat data corresponding to the original seat in the passenger booking record of the specific passenger and the seat protection rule data, determine whether the seat number of the original seat is available in the seat map of the target flight; If it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is not the same as the segment information of the target flight, then the seat number of the original seat is used as the new seat in the seat map of the target flight and assigned to the specific passenger, and the original seat of the specific passenger is cancelled. If it is determined that the seat number of the original seat is unavailable in the seat map of the target flight, then a seat that matches the original seat data of the specific passenger in the passenger booking record is selected in the seat map of the target flight. If a seat is selected in the seat map of the target flight that matches the original seat data of the specific passenger in the passenger booking record, the selected seat will be assigned as a new seat to the specific passenger, and the specific passenger's original seat will be cancelled.

4. The method according to claim 3, characterized in that, The step of determining whether the seat number of the original seat is available in the seat map of the target flight based on the original seat data corresponding to the original seat in the passenger's booking record and the seat protection rule data includes: From the seat map data and the seat protection rule data, obtain the seat data and original seat data corresponding to the original seat number in the seat map of the target flight; wherein, the seat data includes at least seat attribute data and seat class data; Determine whether the seat data corresponding to the original seat number in the seat map of the target flight matches the original seat data; If the seat number of the original seat matches the seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is available. If the seat number of the original seat does not match the seat data in the seat map of the target flight, then the seat corresponding to the original seat number in the seat map of the target flight is unavailable.

5. The method according to claim 3, characterized in that, If it is determined that the seat number of the original seat is available in the seat map of the target flight, the process further includes: If it is determined that the seat number of the original seat is available in the seat map of the target flight, and the segment information of the source flight is the same as the segment information of the target flight, then the process ends. After selecting a seat in the seat map of the target flight that matches the original seat data corresponding to the original seat of the specific passenger in the passenger booking record, the method further includes: If no seat matching the original seat data of the specific passenger in the passenger booking record is selected in the seat map of the target flight, the original seat of the specific passenger will be cancelled.

6. The method according to claim 1, characterized in that, After allocating a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data, the process further includes: Modify the passenger reservation record data and the seat map data according to the new seats; The protection result message representing the seat protection result is synchronized to the surrounding systems; and the passenger reservation record change data is synchronized to the airline's main control system; wherein, the surrounding systems include at least the seat system.

7. A seat protection device, characterized in that, include: A receiving unit is used to receive a seat protection request; wherein the seat protection request includes at least: the identification data of the source flight, the identification data of the target flight, and the triggering reason for seat protection; The first reading unit is used to read flight data, passenger reservation record data, seat protection rule data, and seat map data in response to the seat protection request if the triggering reason of the seat protection request is a change in the passenger reservation record of a single specific passenger. A seat protection unit is used to assign a new seat on the target flight to the specific passenger based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data; wherein, the original seat is the seat booked by the specific passenger on the source flight; the original seat data is the seat data corresponding to the seat number of the original seat in the seat map of the source flight; and the new seat is the seat booked by the specific passenger on the target flight. The seat protection device further includes: a first determining unit and a first judging unit; The first determining unit is used to read flight data and determine whether the segment information of the source flight is the same as the segment information of the target flight. The first judgment unit is used to determine whether the target flight has been initialized if it is determined that the segment information of the source flight is not the same as the segment information of the target flight; wherein, if the flight control system has sent the passenger list of the target flight to the departure system, it is determined that the target flight has been initialized. The seat protection unit includes a first seat protection unit subunit, used to assign a new seat on the target flight to the specific passenger if the segment information of the source flight is not the same as the segment information of the target flight and the target flight has not been initialized, or if the segment information of the source flight is the same as the segment information of the target flight, based on the original seat data corresponding to the original seat in the passenger booking record and the seat protection rule data.

8. An electronic device, characterized in that, Including memory and processor; The memory is used to store computer programs; The processor is used to execute the computer program, specifically to implement the seat protection method as described in any one of claims 1 to 6.

9. A computer-readable medium, characterized in that, Used to store a computer program, which, when executed, is specifically used to implement the seat protection method as described in any one of claims 1 to 6.

Images