A recommendation method, system, device and medium based on a regional pass mechanism

Abstract

This application belongs to the field of data processing technology, and particularly relates to a recommendation method, system, device, and medium based on a regional package ticket mechanism. The method includes: configuring an initial package ticket product; receiving a user's purchase request, verifying availability, generating an actual package ticket order, and making payment; generating the first ticket and corresponding record after successful payment, and then generating the remaining tickets and records one by one; monitoring order completion status, converting the remaining tickets into tickets without fixed itineraries, and retaining the record number and ticket number; receiving user requests to confirm or change their itinerary within the validity period, and if the departure point or destination is within the region, supporting city selection, rescheduling, or rebooking operations, and generating the target order. This application improves the efficiency of package ticket itinerary changes.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and in particular relates to a recommendation method, system, device and medium based on a regional ticketing mechanism. Background Technology

[0002] The core business logic of regional travel packages is that after purchasing a set of ticket rights with a fixed number of uses, passengers can freely choose any city within a designated geographical area as their departure or destination within the product's validity period, flexibly arranging their travel plans to meet the core needs of passengers with no fixed itinerary and multiple destinations. However, in the existing technology, the standardized rules of the civil aviation passenger ticketing system and the underlying reservation system are fundamentally in conflict with the flexible business requirements of regional travel packages.

[0003] When passengers purchase regional tickets, although they specify a fixed destination for the underlying ticketing process, the product range displayed to them in the front-end workflow should be a specific region, not a default destination. However, the underlying code for regions does not exist at the IATA layer, therefore the website needs to construct virtual regions. The construction of regions includes flexible configuration options such as the range of cities included in the region, the default ticketing city, and the region name, allowing for easy deployment of new regional package products in the future. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a recommendation method, system, device, and medium based on a regional ticketing mechanism. It employs a virtual regional configuration combined with an adaptation processing scheme that integrates existing civil aviation reservation rules. This satisfies the business requirements of flexible city selection and batch itinerary determination for regional tickets, while also adapting to the underlying rules of the existing civil aviation ticketing system. This effectively solves the technical problem that the underlying reservation system in the prior art cannot adapt to the flexible business requirements of regional tickets.

[0005] Firstly, this application provides a recommendation method based on a regional package mechanism, the method comprising: Configure initial package product information; Receive user's regional package purchase request information, perform a sellability verification based on the initial package product information and purchase request information, generate the corresponding actual package order based on the verification result and initiate the payment process; Monitor payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, and generate the remaining tickets in the actual package order one by one based on the first ticket information and the first passenger reservation record as several second tickets, and obtain the second ticket information and the second passenger reservation record. Monitor the actual completion status of the package ticket orders, and based on the monitoring results, perform segment clearing on several second tickets, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; Receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, and if the departure point or destination of the target itinerary is within the area range configured in the actual package ticket order, support mutual selection of cities within the area, and perform rescheduling or ticket reissue operations accordingly to generate the target package ticket order.

[0006] Furthermore, Based on the initial package product information and purchase request information, a sellability verification is performed, specifically including: Extract the default ticketing city, available date verification parameters, product inapplicable date range, and target cabin class rules from the initial package product information; The verification time range for the default trip date is determined based on the available date verification parameters; Within the verification time range, based on the default ticketing city of the region as the take-off and landing benchmark, valid flights that meet the target cabin class rules are searched sequentially. If the current search date falls within the date range that the product is not applicable, it is automatically skipped until the full search of the entire verification time range is completed and several valid flights are obtained. Verify whether the number of available seats in the target cabin corresponding to the valid flight is greater than or equal to the total number of tickets purchased in the purchase request information, and whether the ticket allocation requirements in the purchase request information are met, and obtain the first verification result; Verify whether the published fare for the target cabin class corresponding to the valid flight matches the package pricing fare rules in the initial package product information to obtain a second verification result; Based on the first verification result and the second verification result, determine the availability of the package ticket, obtain the determination result, generate the corresponding actual package ticket order and initiate the payment process, or terminate the current purchase process and return an unavailable message.

[0007] Furthermore, Based on the first verification result and the second verification result, the availability of the ticket package is determined, and the determination result is obtained, specifically including: If the first verification result is that the number of available seats in the target cabin class corresponding to the valid flight is greater than or equal to the total number of tickets purchased, and meets the ticket allocation requirements in the purchase request information, and the second verification result is that the published fare of the target cabin class corresponding to the valid flight is completely matched with the ticket pricing fare rules in the initial ticket product information, then the valid flight is determined to meet the requirements for sale. If there is at least one valid flight that meets the sale requirements within the verification time range, the saleability verification of the package ticket is deemed to have passed, and a saleability determination result is generated. If there are no valid flights that meet the requirements for sale within the specified verification time range, the ticket availability verification is deemed to have failed, and an unsaleable result is generated.

[0008] Furthermore, Based on the first ticket information and the first passenger's reservation record, the remaining tickets in the actual package order are generated one by one, specifically including: The passenger identity information, fare information, and cabin class information in the first ticket information will be used as the basis for ticketing. An asynchronous automatic process is initiated, following the rule that one ticket corresponds to one independent passenger reservation record. For each remaining ticket in the actual package order, the ticketing reference information is reused to generate second ticket information and second passenger reservation records one by one.

[0009] Furthermore, Based on the monitoring results, several second-tier tickets will undergo segment clearing, specifically including: Once it is detected that all tickets in the actual package order have been issued, the flight segment clearing operation is performed on the second passenger reservation record corresponding to the second ticket through the civil aviation reservation system. Once the segment clearing operation is completed, the corresponding second ticket will be converted into a ticket without a fixed itinerary; The segment clearing operation only deletes the valid segment information of the fixed flight number, travel date, and departure and arrival cities bound in the second passenger reservation record, releases the corresponding locked flight seat inventory, and retains the second passenger reservation record number and the ticket number of the corresponding second ticket information throughout the process.

[0010] Furthermore, Update the second passenger's reservation record based on the target itinerary information, specifically including: Identify the types of requests initiated by users, including initial itinerary confirmation requests for passengers without fixed-itinerary tickets and itinerary change requests for passengers with existing fixed-itinerary tickets; If it is the first trip confirmation request, then the updated passenger reservation record is reconstructed based on the target trip information selected by the user, the corresponding ticket number is disconnected from the second passenger reservation record, and bound to the updated passenger reservation record; If the departure and destination of the target itinerary are consistent with the default ticketing city in the initial package product information, the ticket number and fare base will be retained. If it is a request to change the itinerary, the old flight segment information in the second passenger's booking record is released, and a new flight segment that conforms to the package product rules is rebooked based on the target itinerary information, thus completing a full update of the second passenger's booking record.

[0011] Furthermore, If the departure or destination of the target itinerary falls within the area configured in the actual package order, then city selection within the area is supported, and rescheduling or ticket reissue operations will be performed accordingly, specifically including: The list of available cities or airports within the region configured in the initial package product information is obtained in advance as the legal range for city selection; When the departure and destination of the target itinerary are exactly the same as the original ticketing city, only the rescheduling operation is performed. The travel date and corresponding flight are changed based on the second passenger booking record, without changing the ticket number and fare base. When the departure or destination of the target itinerary falls within the legal range of the selected cities and is inconsistent with the original ticketing city, a ticket re-issuance operation is performed, generating a re-issuance passenger reservation record and a corresponding re-issuance ticket number.

[0012] Secondly, based on the same inventive concept, this application provides a recommendation system based on a regional ticketing mechanism, the system comprising: The configuration module is used to configure the initial package product information; The package ticket generation module is used to receive the user's regional package ticket purchase request information, perform a sellability verification based on the initial package ticket product information and purchase request information, generate the corresponding actual package ticket order based on the verification result, and initiate the payment process. The ticket generation module is connected to the package ticket generation module to monitor the payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, and generate the remaining tickets in the actual package ticket order one by one based on the first ticket information and the first passenger reservation record, as several second tickets, and obtain the second ticket information and the second passenger reservation record. The clearing module is used to monitor the completion status of the actual package order, and based on the monitoring results, perform segment clearing on several second tickets, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; The update module is used to receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, and if the departure point or destination of the target itinerary is within the area range configured in the actual package ticket order, it supports mutual selection of cities within the area and performs the rescheduling or ticket reissue operation accordingly to generate the target package ticket order.

[0013] Thirdly, this application also provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the steps of any of the recommendation methods based on a regional ticketing mechanism as described above.

[0014] Fourthly, this application also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the regional ticketing mechanism-based recommendation methods described above.

[0015] Compared with the prior art, this application has the following advantages: 1. This application achieves automated closed-loop management of the entire process of package ticketing, from purchase and ticketing to itinerary change, by configuring the initial package ticket product, performing availability verification to generate an order and make payment, generating the first ticket and corresponding passenger reservation record after payment, generating the remaining tickets one by one and retaining their respective passenger reservation records and ticket numbers, and clearing the flight segment of the unused second ticket after the order is completed and converting it into a ticket without a fixed itinerary. Within the validity period, the corresponding passenger reservation record is updated based on the target itinerary and supports inter-city selection for rescheduling or re-issuance within the region. This greatly improves the processing efficiency of package ticket itinerary changes and enhances the flexibility of package ticket products and user travel adaptability through the inter-city selection mechanism.

[0016] 2. This application extracts the default ticketing city, available date verification parameters, product inapplicable date range, and target cabin class rules for the region. Within the verification time range, it sequentially searches for valid flights based on the default ticketing city and automatically skips inapplicable dates. Then, it verifies the number of seats and matches fare rules for valid flights. This achieves refined availability verification for regional package ticket characteristics, effectively avoiding order generation failures due to unavailable flights or mismatched fares, and improving the reliability and user experience of package ticket purchases.

[0017] 3. This application determines that a single valid flight meets the requirements for sale by simultaneously meeting the dual conditions of having an available number of seats greater than or equal to the total number of tickets purchased and the ticket allocation requirements, and that the published fare is completely consistent with the fare rules for package pricing. Furthermore, the verification is considered successful if there is at least one valid flight that meets the requirements within the verification time frame. This achieves a strict and efficient logic for determining availability, which ensures fare consistency and avoids excessive rejection of valid purchase requests due to individual flights being sold out.

[0018] 4. This application uses the passenger identity information, fare information, and cabin class of the first ticket as the basis for ticketing and initiates an asynchronous automatic process to generate the remaining tickets one by one, following the rule that one ticket corresponds to one independent passenger reservation record. This achieves high-concurrency asynchronous automatic ticketing of batch tickets, significantly shortening the overall ticketing time for multiple ticket packages. At the same time, it ensures that the passenger reservation record for each ticket is independent, which facilitates the independent change management of subsequent individual tickets, thereby improving ticketing efficiency and the flexibility of ticket management.

[0019] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application 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 some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart illustrating a recommendation method based on a regional package mechanism according to an embodiment of this application is shown. Figure 2 A structural block diagram of a recommendation system based on a regional ticketing mechanism according to an embodiment of this application is shown. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] In this application embodiment, PNR is the abbreviation for Passenger Name Record, which reflects the passenger's journey, the number of seats occupied on the flight, and passenger information; A package ticket refers to a service where passengers purchase and use multiple tickets as a set or group. A region refers to multiple adjacent cities grouped together according to ticketing rules. For example, the East China region may include multiple cities or airports within the East China region.

[0024] Figure 1 A flowchart illustrating a recommendation method based on a regional package mechanism according to an embodiment of this application is shown, such as... Figure 1 As shown, the recommendation method based on the regional ticket mechanism in this application includes, S1, Configure initial package product information; In this embodiment of the application, the initial package product information includes regional attribute configuration information, basic product rule information, availability verification rule information, and fare and benefits configuration information; The regional attribute configuration information includes product regional type identifier, regional unique code, regional name, list of three-letter codes of civil airports covered by the region, three-letter code of the default departure airport of the region, and three-letter code of the default destination airport of the region, which are used to provide a basis for selecting cities within the region and issuing tickets for default itineraries; The basic rules information for the product includes the product's unique identifier, the airline information, the itinerary type identifier, the product's sales validity period, the package ticket's validity period, the range of applicable passengers, the total number of tickets for the package, the maximum number of tickets that can be allocated to a single passenger, and the sales channel distribution rules. These rules are used to provide a business benchmark for package ticket order generation, ticket issuance, and multi-person shared use scenarios. The availability verification rules information includes availability date verification benchmark parameters N and X, round trip return interval benchmark parameter M, product sales prohibition and inapplicable date range, target available cabin class rules, and flight application restriction rules, which are used to provide execution benchmarks for availability verification during the package purchase stage; The fare and benefits configuration information, including the unified fare locking rules for package tickets, the same-price control rules for the same passenger, the rules for free rescheduling and reissue rights, the refund rules, and the rules for mutual selection of airports within the region, are used to provide the basis for the execution of fares and benefits for ticket issuance, itinerary changes, and ticket reissue. S2, Receive the user's regional package ticket purchase request information, perform a sellability verification based on the initial package ticket product information and purchase request information, generate the corresponding actual package ticket order based on the verification result and initiate the payment process; In this embodiment of the application, step S2 specifically includes: S21, extract the default ticketing city, available date verification parameters, product inapplicable date range, and target cabin class rules from the initial package product information; S22, determine the verification time range of the default trip date based on the available date verification parameters; S23, within the verification time range, using the default ticketing city of the region as the take-off and landing benchmark, sequentially search for valid flights that meet the target cabin class rules. If the current search date falls within the date range that the product is not applicable, it will be automatically skipped until the full search of the entire verification time range is completed and several valid flights are obtained. S24, verify whether the number of available seats in the target cabin corresponding to the valid flight is greater than or equal to the total number of tickets purchased in the purchase request information, and whether the ticket allocation requirement in the purchase request information is met, and obtain the first verification result; S25, verify whether the published fare for the target cabin class corresponding to the valid flight matches the package pricing fare rules in the initial package product information, and obtain the second verification result; S26. Based on the first verification result and the second verification result, determine the availability of the package ticket, obtain the determination result, generate the corresponding actual package ticket order and initiate the payment process based on the determination result, or terminate the current purchase process and return an unavailable message.

[0025] In this embodiment, the available-for-sale date verification configuration parameters include N and X. The default itinerary verification time range for a one-way ticket is from the current system date + N days to the current system date + N + X days. If the product is a round-trip ticket, the return interval parameter M is set, defining the default return itinerary verification time range as the outbound default date + M days. Here, N, X, and M are all positive integers pre-set according to actual business needs. This explicit verification time range setting allows for accurate and efficient evaluation of the ticket's availability.

[0026] In practice, this verification method fully considers the characteristics of different types of ticket packages and users' travel needs. For one-way tickets, it can plan and filter eligible flights in advance based on the user's possible travel time; for round-trip tickets, it can reasonably arrange the outbound and return times to avoid time conflicts or unreasonable itinerary arrangements. Simultaneously, during the search process, if the current search date falls within a product's applicable date range, it is automatically skipped. This mechanism effectively excludes dates that do not meet sales rules, improving search efficiency and accuracy.

[0027] In this embodiment, by verifying whether the number of available seats is greater than or equal to the total number of tickets to be purchased in the purchase request information, and ensuring that the ticket allocation requirements are met, it is guaranteed that the user's purchase request can be fulfilled, avoiding sales failures due to insufficient seats. Verifying whether the published fare matches the fare rules for package tickets ensures that the package ticket price conforms to business settings, maintaining market price stability and fairness. Based on these verification results, the availability of the package ticket is determined, which then decides whether to generate an actual package ticket order and initiate the payment process, or terminate the purchase process and return an unsold notification, providing a reliable decision-making basis for the entire recommendation based on the regional package ticket mechanism.

[0028] In this embodiment of the application, step S26 specifically includes: S261, if the first verification result is that the number of available seats in the target cabin corresponding to the valid flight is greater than or equal to the total number of tickets purchased and meets the ticket allocation requirements in the purchase request information, and the second verification result is that the published fare of the target cabin corresponding to the valid flight is completely matched with the ticket pricing fare rules in the initial ticket product information, then the valid flight is determined to meet the requirements for sale. S262, if there is at least one valid flight that meets the sale requirements within the verification time range, the saleability verification of the package ticket is determined to be passed, and a saleability determination result is generated; S263, if there are no valid flights that meet the sale requirements within the verification time range, the saleability verification of the package ticket is determined to fail, and an unsaleable determination result is generated.

[0029] In this embodiment of the application, if the itinerary type marked in the initial package product information is a round-trip package, it is necessary to simultaneously verify that the flights corresponding to the default date combination of the outbound and return trips both meet the availability requirements and the fare matching requirements before it can be determined that the flights corresponding to the date combination meet the requirements for sale.

[0030] S3, monitor the payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, generate the remaining tickets in the actual package order one by one based on the first ticket information and the first passenger reservation record, as several second tickets, and obtain the second ticket information and the second passenger reservation record. In this embodiment of the application, step S3 specifically includes: S31, use the passenger identity information, fare information and cabin class in the first ticket information as the ticketing basis information; S32, start the asynchronous automatic process, following the rule that one ticket corresponds to one independent passenger reservation record, for each remaining ticket in the actual package order, reuse the ticketing reference information to generate second ticket information and second passenger reservation record one by one.

[0031] In this embodiment of the application, the Civil Aviation IBE / host reservation interface is called sequentially to complete the ticketing operation of the second ticket corresponding to each second passenger reservation record.

[0032] In this embodiment of the application, the asynchronous automatic process completes the ticketing process for all remaining tickets within a preset time. If a second passenger's reservation record fails to secure a seat on the flight, the civil aviation system's K-position mechanism is automatically triggered to ensure the ticketing is completed.

[0033] S4, monitor the actual completion status of the package order, and based on the monitoring results, perform segment clearing on several second tickets, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; In this embodiment of the application, step S4 specifically includes: S41, after monitoring that all tickets in the actual package order have been issued, the flight segment clearing operation is performed on the second passenger reservation record corresponding to the second ticket through the civil aviation reservation system; S42, Once the segment clearing operation is completed, the corresponding second ticket will be converted into a ticket without a fixed itinerary; The segment clearing operation only deletes the valid segment information of the fixed flight number, travel date, and departure and arrival cities bound in the second passenger reservation record, releases the corresponding locked flight seat inventory, and retains the second passenger reservation record number and the ticket number of the corresponding second ticket information throughout the process.

[0034] S5, receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, if the departure point or destination of the target itinerary is within the area range configured in the actual package ticket order, support mutual selection of cities within the area, and perform the rescheduling or ticket reissue operation accordingly to generate the target package ticket order.

[0035] In this embodiment of the application, step S5 specifically includes: S51, identify the type of request initiated by the user, the request type includes initial itinerary confirmation request for passengers without fixed itinerary tickets and itinerary change request for passengers with existing fixed itinerary tickets; S52, if it is the first trip confirmation request, then based on the target trip information selected by the user, the updated passenger reservation record is reconstructed, the corresponding ticket number is disconnected from the second passenger reservation record, and bound to the updated passenger reservation record; S53. If the departure point and destination of the target itinerary are consistent with the default ticketing city in the initial package product information, the ticket number and fare base will be retained. S54, if it is an itinerary change request, release the old flight segment information in the second passenger reservation record, rebook a new flight segment that conforms to the package product rules based on the target itinerary information, and complete the full information update of the second passenger reservation record.

[0036] In this embodiment of the application, step S5 further includes: S55, if the departure or destination of the target itinerary falls within the area configured in the actual package order, then city selection within the area is supported, and rescheduling or ticket reissue operations are performed accordingly, specifically including: S56, obtain in advance the list of available cities or airports within the region configured in the initial package product information, as the legal range for city selection; S57. When the departure point and destination of the target itinerary are exactly the same as the original ticketing city, only the rescheduling operation is performed. The travel date and corresponding flight are changed based on the second passenger booking record, without changing the ticket number and fare base. S58, when the departure or destination of the target itinerary is within the legal range of the selected cities and is inconsistent with the original ticketing city, execute the ticket exchange operation and generate the exchanged passenger reservation record and the corresponding exchanged ticket number.

[0037] Example 1: Passengers need to purchase a regional pass consisting of 5 round-trip tickets from Hong Kong to East China (set to allow travel at four airports: SHA, PVGHGH, and NKG).

[0038] Business definition product: This product is for this region and specifies the basic product rules. For example, in East China, the default booking and ticketing is Shanghai Pudong (PVG), and the default destination is set to PVG. The number of people and tickets applicable to this product are set according to the business rules (such as 1 person or 2 people with a total of 5 round-trip tickets).

[0039] The passenger selects and purchases a package of 5 tickets from Hong Kong to East China. Due to revenue sharing considerations in business settlement, ticketing is required after the purchase. Therefore, when entering the specific purchase process, the system needs to verify whether the actual fare or flight schedule of the package meets the conditions for sale.

[0040] Available-for-sale verification: When the front-end does not require passengers to specify travel dates and destinations, the system's underlying mechanism defaults to the product's defined destination (PVG) for ticketing. The travel date, according to sales rules, needs to be checked within days N to N+X (where X represents checking N+1, N+2, up to a maximum of N+X days) to see if there are flights available for the product's fare class. N and X are flexible configuration values, allowing for timely adjustments based on flight schedules. The specific design scheme for this part is as follows: The system needs to support setting the value N+X. This value determines the time range within which the system needs to verify whether there are sufficient cabin classes available for booking and ticketing.

[0041] Default travel date: When booking a round-trip ticket, after confirming the specific value of day N, it is also necessary to confirm the default return date, such as N+3, to determine whether there are available fares for the date combination of day N / N+3 of the outbound journey, so as to ensure that an accurate price can be obtained and sold.

[0042] Ticket allocation: For example, if a package contains 5 tickets, the service allows one passenger to purchase all 5 tickets at once, or two passengers (A and B) to purchase 2 tickets each and 3 tickets respectively. Based on the product definition, the sales process requires the purchaser to allocate the 5 tickets to the designated number of people.

[0043] Multiple PNRs for the same order: In the general ticket sales process, a single booking can only support one registration for the same passenger (i.e., one ticket issued). However, a package ticket requires a single booking to issue a specified number of tickets for passenger A. Therefore, the booking process for a package ticket needs to consider distributing the passenger across different PNRs and booking the corresponding number of tickets through these PNRs.

[0044] Multiple PNRs for Ticketing: After a passenger completes payment, multiple tickets need to be issued. When calling the underlying IBE interface or host interface, each PNR needs to be issued sequentially. Therefore, the ticketing process should first ensure that the first ticket in the package is issued. The subsequent PNRs and ticketing actions should be executed automatically by the system process, and the remaining PNRs should be called to issue tickets sequentially within the shortest possible time (e.g., within 2 minutes).

[0045] Once all the above steps have been completed normally, the sales center will notify the passenger that the package ticket order has been issued and provide proof of the ticket associated with the order.

[0046] During the process of purchasing the aforementioned package tickets, the sales platform also needs to consider the determination of dates on which the package ticket price does not apply. If an inapplicable date range is set during the product definition stage of the package ticket, the inapplicable dates must also be avoided when determining the available booking dates. For example, if an inapplicable date range is found when searching for day N, the inapplicable date range must be skipped, and the search must proceed sequentially to day N+1. The search will go up to day N+X at most. If no available flights are found, the purchase process cannot continue.

[0047] Another consideration is that after the first ticket is issued, the PNR (Purchase No.) for subsequent tickets needs to be generated using the same price information for the same passenger, and these PNRs should be generated sequentially through an automated process. In the system design, since the previous steps have already determined that there are sufficient slots available for package bookings on the default travel dates, under normal circumstances, after the time difference in the purchase process, the subsequent ticketing process should be able to secure a PNR and issue tickets. If, due to timing issues or interface-based slot reservation problems, a PNR is not secured, the system will normally guarantee ticket issuance using the K-slot mechanism.

[0048] After the ticketing process is completed, since the passenger's travel plans are not yet finalized, the ticket itinerary needs to be changed to an OPEN ticket to avoid reserving a seat.

[0049] Example 2: After purchasing a package ticket for the East China region, it was specified that both passenger A and passenger B could simultaneously arrange their travel plans for the two tickets in the order and flexibly reschedule their travel plans.

[0050] After a package ticket order is successfully issued, passengers can use or reschedule the package within a certain period of their order.

[0051] The subsequent application of the package ticket involves determining the itinerary, which is divided into two scenarios: the first use and subsequent rescheduling based on tickets with travel dates.

[0052] First-time use: This is the first time a passenger's empty ticket itinerary has been set with specific travel segments and dates. At this time, a new PNR needs to be reconstructed according to the passenger's selected itinerary. This ticket number should be disconnected from the original PNR recorded in the sales center and linked to the new PNR for ticketing. If the HKGPVG OD remains unchanged, the ticket number must remain unchanged, and the price field of the new ticket must also remain unchanged.

[0053] Rescheduling: When the original itinerary changes, this type of package ticket supports multiple free reschedulings. Rescheduling may involve only rescheduling or rebooking.

[0054] Rescheduling: This requires rebooking a new flight segment based on the original PNR, releasing the old segment. For example, if the ticket was issued for a flight from Hong Kong to Shanghai Pudong, and the passenger's departure / destination remains the same, this is a change of travel date based on the original ticket.

[0055] Rebooking: The passenger's initial purchase was from Hong Kong to Pudong, but during the process of finalizing the itinerary or rescheduling, the flight may be from Hong Kong to Hangzhou (assuming the departure / destination in Hangzhou changes). The list of selectable cities comes from the list of cities included in the region in the product configuration. When the departure or destination changes, a new PNR needs to be generated to create a new ticket number.

[0056] For passengers, both of the above business scenarios are based on orders to determine travel plans. The order center's processing involves constructing a new itinerary PNR from the original ticket's PNR content, and may issue a new ticket number (e.g., the original ticket number 800-3939848422 is reissued as a new ticket number 800-3940848098 due to the new itinerary plan).

[0057] The following two important aspects need to be addressed.

[0058] Reconstructing the PNR: Since this is not a new ticket booking but a change based on the original ticket, the focus of the order processing is on constructing the FC (Fulfilled Cost) content items. This requires using NUC (Number of Costs) and ROE (Return on Equity) to create a price identical to the original ticket, aligning with the business objective of not charging for ticket changes. In addition to the free rule, these orders may also have the right to multiple rescheduling. Multiple rescheduling is mainly achieved by reusing the rights multiple times; the basic steps are essentially the same as steps 1) and 2) in this example.

[0059] Simultaneous rescheduling for multiple people: Package tickets are applicable to multiple people (such as two people, A and B). Therefore, if A and B have the same travel plans, rescheduling will be processed simultaneously. The characteristics of package ticket orders (one ticket, one PNR record) mean that the two tickets of passengers A and B belong to different PNR records. It is necessary to have the ability to update the two PNRs to ensure that passengers A and B can reschedule to new, identical itineraries at the same time.

[0060] Based on the above method, this application also provides a recommendation system based on a regional ticketing mechanism corresponding to the above method. Figure 2 A structural block diagram of a recommendation system based on a regional ticketing mechanism according to an embodiment of this application is shown. See also... Figure 2 As shown, the system includes: Configuration module 10 is used to configure the initial package product information; The package ticket generation module 20 is used to receive the user's regional package ticket purchase request information, perform a sellability verification based on the initial package ticket product information and purchase request information, generate the corresponding actual package ticket order based on the verification result, and initiate the payment process. The ticket generation module 30 is connected to the package ticket generation module 20. It is used to monitor the payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, and generate the remaining tickets in the actual package ticket order one by one based on the first ticket information and the first passenger reservation record, as several second tickets, and obtain the second ticket information and the second passenger reservation record. The clearing processing module 40 is used to monitor the actual package order completion status, perform segment clearing processing on several second tickets based on the monitoring results, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; The update module 50 is used to receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, and if the departure point or destination of the target itinerary is within the area configured in the actual package ticket order, it supports mutual selection of cities within the area and performs the rescheduling or ticket reissue operation accordingly to generate the target package ticket order.

[0061] Based on the same inventive concept disclosed above, this application also provides an electronic device. The electronic device of this application includes at least one processor and at least one memory electrically connected to the processor. The memory is electrically connected to the processor, wherein the memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the method described above.

[0062] It should be noted that the electrical connection between the above-mentioned units does not necessarily mean the connection between lines. The indirect connection method can be applied to the embodiments of this application as long as it achieves the purpose of this application.

[0063] Based on the same inventive concept, this application also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the steps of the above method.

[0064] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A recommendation method based on a regional package ticket mechanism, characterized in that, The method includes, Configure initial package product information; Receive user's regional package purchase request information, perform a sellability verification based on the initial package product information and purchase request information, generate the corresponding actual package order based on the verification result and initiate the payment process; Monitor payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, and generate the remaining tickets in the actual package order one by one based on the first ticket information and the first passenger reservation record as several second tickets, and obtain the second ticket information and the second passenger reservation record. Monitor the actual completion status of the package ticket orders, and based on the monitoring results, perform segment clearing on several second tickets, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; Receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, and if the departure point or destination of the target itinerary is within the area range configured in the actual package ticket order, support mutual selection of cities within the area, and perform rescheduling or ticket reissue operations accordingly to generate the target package ticket order.

2. The method according to claim 1, characterized in that, Based on the initial package product information and purchase request information, a sellability verification is performed, specifically including: Extract the default ticketing city, available date verification parameters, product inapplicable date range, and target cabin class rules from the initial package product information; The verification time range for the default trip date is determined based on the available date verification parameters; Within the verification time range, based on the default ticketing city of the region as the take-off and landing benchmark, valid flights that meet the target cabin class rules are searched sequentially. If the current search date falls within the date range that the product is not applicable, it is automatically skipped until the full search of the entire verification time range is completed and several valid flights are obtained. Verify whether the number of available seats in the target cabin corresponding to the valid flight is greater than or equal to the total number of tickets purchased in the purchase request information, and whether the ticket allocation requirements in the purchase request information are met, and obtain the first verification result; Verify whether the published fare for the target cabin class corresponding to the valid flight matches the package pricing fare rules in the initial package product information to obtain a second verification result; Based on the first verification result and the second verification result, determine the availability of the package ticket, obtain the determination result, generate the corresponding actual package ticket order and initiate the payment process, or terminate the current purchase process and return an unavailable message.

3. The method according to claim 2, characterized in that, Based on the first verification result and the second verification result, the availability of the ticket package is determined, and the determination result is obtained, specifically including: If the first verification result is that the number of available seats in the target cabin class corresponding to the valid flight is greater than or equal to the total number of tickets purchased, and meets the ticket allocation requirements in the purchase request information, and the second verification result is that the published fare of the target cabin class corresponding to the valid flight is completely matched with the ticket pricing fare rules in the initial ticket product information, then the valid flight is determined to meet the requirements for sale. If there is at least one valid flight that meets the sale requirements within the verification time range, the saleability verification of the package ticket is deemed to have passed, and a saleability determination result is generated. If there are no valid flights that meet the requirements for sale within the specified verification time range, the ticket availability verification is deemed to have failed, and an unsaleable result is generated.

4. The method according to claim 1, characterized in that, Based on the first ticket information and the first passenger's reservation record, the remaining tickets in the actual package order are generated one by one, specifically including: The passenger identity information, fare information, and cabin class information in the first ticket information will be used as the basis for ticketing. An asynchronous automatic process is initiated, following the rule that one ticket corresponds to one independent passenger reservation record. For each remaining ticket in the actual package order, the ticketing reference information is reused to generate second ticket information and second passenger reservation records one by one.

5. The method according to claim 1, characterized in that, Based on the monitoring results, several second-tier tickets will undergo segment clearing, specifically including: Once it is detected that all tickets in the actual package order have been issued, the flight segment clearing operation is performed on the second passenger reservation record corresponding to the second ticket through the civil aviation reservation system. Once the segment clearing operation is completed, the corresponding second ticket will be converted into a ticket without a fixed itinerary; The segment clearing operation only deletes the valid segment information of the fixed flight number, travel date, and departure and arrival cities bound in the second passenger reservation record, releases the corresponding locked flight seat inventory, and retains the second passenger reservation record number and the ticket number of the corresponding second ticket information throughout the process.

6. The method according to claim 1, characterized in that, Update the second passenger's reservation record based on the target itinerary information, specifically including: Identify the types of requests initiated by users, including initial itinerary confirmation requests for passengers without fixed-itinerary tickets and itinerary change requests for passengers with existing fixed-itinerary tickets; If it is the first trip confirmation request, then the updated passenger reservation record is reconstructed based on the target trip information selected by the user, the corresponding ticket number is disconnected from the second passenger reservation record, and bound to the updated passenger reservation record; If the departure and destination of the target itinerary are consistent with the default ticketing city in the initial package product information, the ticket number and fare base will be retained. If it is a request to change the itinerary, the old flight segment information in the second passenger's booking record is released, and a new flight segment that conforms to the package product rules is rebooked based on the target itinerary information, thus completing a full update of the second passenger's booking record.

7. The method according to claim 1, characterized in that, If the departure or destination of the target itinerary falls within the area configured in the actual package order, then city selection within the area is supported, and rescheduling or ticket reissue operations will be performed accordingly, specifically including: The list of available cities or airports within the region configured in the initial package product information is obtained in advance as the legal range for city selection; When the departure and destination of the target itinerary are exactly the same as the original ticketing city, only the rescheduling operation is performed. The travel date and corresponding flight are changed based on the second passenger booking record, without changing the ticket number and fare base. When the departure or destination of the target itinerary falls within the legal range of the selected cities and is inconsistent with the original ticketing city, a ticket re-issuance operation is performed, generating a re-issuance passenger reservation record and a corresponding re-issuance ticket number.

8. A recommendation system based on a regional ticket package mechanism, characterized in that, The system includes: The configuration module is used to configure the initial package product information; The package ticket generation module is used to receive the user's regional package ticket purchase request information, perform a sellability verification based on the initial package ticket product information and purchase request information, generate the corresponding actual package ticket order based on the verification result, and initiate the payment process. The ticket generation module is connected to the package ticket generation module to monitor the payment status, generate the first ticket based on the monitoring results, obtain the first ticket information and the first passenger reservation record, and generate the remaining tickets in the actual package ticket order one by one based on the first ticket information and the first passenger reservation record, as several second tickets, and obtain the second ticket information and the second passenger reservation record. The clearing module is used to monitor the completion status of the actual package order, and based on the monitoring results, perform segment clearing on several second tickets, retain the second passenger reservation record number and ticket number, and convert the corresponding second tickets into tickets without fixed itineraries; The update module is used to receive the user's itinerary confirmation request or change request within the validity period of the actual package ticket order, update the corresponding second passenger reservation record based on the target itinerary information, and if the departure point or destination of the target itinerary is within the area configured in the actual package ticket order, it supports mutual selection of cities within the area and performs the rescheduling or ticket reissue operation accordingly to generate the target package ticket order.

9. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the steps of the recommendation method based on the regional ticketing mechanism as described in any one of claims 1-7.

10. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the steps of the recommendation method based on the regional ticketing mechanism described in any one of claims 1-7.

Images